Package: nbd-client
Version: 1:2.9.14-2
Severity: normal
i recently gave nbd-client's init scripts a spin with LTSP, which i hadn't done
for quite some time... unfortunately if ip=dhcp is specified on the kernel boot
commandline, it fails to boot.
once upon a time this worked, and nearly identical configurations using NFS
root work without a hitch... so i'm guessing there's something that
nbd-client's initramfs hooks do that break's initramfs-tools's
configure_networking function:
+ nbdbasedev=nbd0
+ IP=dhcp
+ nbdroot=192.168.0.1,2000
+ nbdsrv=192.168.0.1
+ nbdport=2000
+ nbdrootdev=/dev/nbd0
+ nbdbasedev=nbd0
+ [ -z 2000 -o -z /dev/nbd0 ]
+ [ -z dhcp ]
+ configure_networking
+ echo configure networking....
configure networking....
+ [ -n ]
+ ipconfig -t 180 -c dhcp -d
ipconfig: invalid option -
+ [ -n ]
+ . /tmp/net-*.conf
/scripts/local-top/nbd: .: line 1: can't open '/tmp/net-*.conf'
mount: mounting /dev/nbd0 on /root failed: No such device
ipconfig's -d option expects a device.
it seems that /usr/share/initramfs-tools/scripts/local-top/nbd has a fallback
for IP, like so:
# fallback to old eth0 only behaviour
[ -z "$IP" ] && IP="eth0"
but setting the IP to the device is not really compatible the
configure_networking function in initramfs-tools/scripts/functions:
case ${IP} in
none|off)
# Do nothing
;;
""|on|any)
# Bring up device
ipconfig -t 180 ${DEVICE}
;;
dhcp|bootp|rarp|both)
ipconfig -t 180 -c ${IP} -d ${DEVICE}
;;
*)
ipconfig -t 180 -d $IP
the patch supplied in debian bug #553019 isn't really correct. it happens to
work if someone doesn't specify ip= at the boot prompt, but if they explicitly
ask for DHCP, it just plain breaks, as DEVICE is not set... *sigh*
live well,
vagrant
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
