This bug was fixed in the package nbd - 1:2.9.25-2ubuntu1
---
nbd (1:2.9.25-2ubuntu1) precise; urgency=low
* Merge from Debian unstable. Remaining changes (LP: #594595):
- Drop /etc/modprobe.d/nbd-client; the kernel default is already
appropriate. Ubuntu-specific change.
Fix committed in
http://anonscm.debian.org/gitweb/?p=users/wouter/nbd.git;a=commit;h=68340a2b17cd1f14f5bf1d52c7ab8c4ca8fa89d3,
thank you Wouter.
But we also need to add support for the new boot options in the sendsigs
protection code, so I'll leave the bug open until I find some time to propose
On Fri, Dec 02, 2011 at 04:20:25AM -, Alkis Georgopoulos wrote:
> 'morning Wouter, attaching my last proposal.
> I did some more testing in the ip:port/path parsing, it should cover all
> cases now. Also, up to 2 of these parameters can be omitted.
Wonderful.
I'll give it some testing and do
'morning Wouter, attaching my last proposal.
I did some more testing in the ip:port/path parsing, it should cover all cases
now. Also, up to 2 of these parameters can be omitted.
** Attachment added: "nbd-client.initrd"
https://bugs.launchpad.net/ubuntu/+source/nbd/+bug/594595/+attachment/261
...and yet another revised version. I should have linked a bzr branch
instead. :D
** Attachment added: "nbd-client.initrd"
https://bugs.launchpad.net/ubuntu/+source/nbd/+bug/594595/+attachment/2614441/+files/nbd-client.initrd
** Patch removed: "nbd-client.initrd"
https://bugs.launchpad.ne
Yup sorry in line 61 I had nbdsrv=${nbdsrv%%:*} instead of the correct
nbdsrv=${nbdsrv%:*}.
Here's a snippet to verify it should be ok now:
nbdroot='[2001:6f8:32f::39]:1234/some/nbd/path'
nbdsrv=${nbdroot%%/*}
nbdpath="/${nbdroot#*/}"
case "$nbdsrv" in
*:*)
nbdport=${nbdsrv##*:}
Hi Alkis,
On Thu, Dec 01, 2011 at 06:14:42AM -, Alkis Georgopoulos wrote:
> While the NBDROOT environment variable would allow for some flexibility, it
> still wouldn't allow LTSP to use the nbd-client.initrd script, as some LTSP
> users need to use the nbd-proxy hack.
> Also, LTSP would need
Newer version that replaces `case "$x"` with `case "$nbdroot"`.
** Attachment added: "nbd-client.initrd"
https://bugs.launchpad.net/ubuntu/+source/nbd/+bug/594595/+attachment/2614401/+files/nbd-client.initrd
** Patch removed: "nbd-client.initrd"
https://bugs.launchpad.net/ubuntu/+source/n
While the NBDROOT environment variable would allow for some flexibility, it
still wouldn't allow LTSP to use the nbd-client.initrd script, as some LTSP
users need to use the nbd-proxy hack.
Also, LTSP would need to initialize networking before nbd-client.initrd, to get
the necessary info from DH
Solved by adding support for an NBDROOT environment variable:
http://anonscm.debian.org/gitweb/?p=users/wouter/nbd.git;a=commit;h=a68fec1f04c8c95d2af704eb9629ec59d077fd2a
Thanks Wouter :)
** Changed in: nbd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you
** Tags added: patch
--
feature request: support colons in nbdroot kernel parameter
https://bugs.launchpad.net/bugs/594595
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://
Hi Wouter,
I think that with the new name-based exports and the 10809 port, we'll
need to change the pxelinux.cfg/default file provided by LTSP anyway, so
I'm not sure that supporting colons will be necessary, maybe we can just
switch to the commas syntax in LTSP.
So I think this feature request
** Patch added: "Patch for debian/nbd-client.initrd"
http://launchpadlibrarian.net/50374158/nbd.patch
--
feature request: support colons in nbdroot kernel parameter
https://bugs.launchpad.net/bugs/594595
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
13 matches
Mail list logo
