Package: nbd-client Version: 1:2.9.16-2 Severity: minor nbdroot is working rather nicely now. thanks! :)
however, specifying the nbd block device via the nbdroot= parameter seems less than useful, as it also needs to be specified via the root= boot parameter, otherwise the initramfs-tools scripts/local doesn't know what root device to mount... simply specifying: nbdroot=192.168.0.1,2000,nbd0 nbd-client configures the nbd device properly, but fails to mount root. since the scripts/local-top/nbd script handles getting the root device from the root= parameter, having it also specified in nbdroot= can actually lead to inconsistant behavior between nbdroot/root that leads to a boot failure: root=/dev/nbd0 nbdroot=192.168.0.1,2000,nbd1 causes nbd1 to get configured via nbd-client, but then fails to mount root as it tries to use nbd0. if there was some way for scripts/local-top/nbd to change the root= parameter in a way that the scripts/local respects, it might be useful to keep the code for setting the nbd device with the nbdroot parameter. if that's not feasible, and there isn't some use i can't think of at the moment, probably best to drop the code handling it. live well, vagrant -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
