Scott James Remnant: > initramfs-tools shouldn't contain anything that refers to udev? > > The scripts that call udevtrigger/udevsettle are contained inside the > udev package. But, in Herd 2, /scripts/casper-bottom/23networking uses udevtrigger (with the broken "-B" and "-I" parameters!) and comes from casper, not udev.
The fix Matthias proposed and tested against Edgy has been applied by Colin agaist Feisty. But it has no effect in Feisty unless, first, the invocation of udevtrigger is fixed. The fact that udevtrigger/udevsettle is called from a script provided by casper instead of the udev package itself is not important here, IMHO. (However it probably means that casper should depend on udev, or be fixed not to use udevtrigger/udevsettle at all). > It's possible that your initramfs wasn't updated possible; either way, > please take that up with the kernel team. Matthias uses Edgy and was making an hypothesis about an issue I found on Feisty. So no non-updated initramfs on his side. (Matthias, please correct me if I'm wrong) To summarize: /scripts/casper-bottom/23networking is broken in Herd2 since it calls udevtrigger with unknown parameters and, hence, fails. This has not been fixed by the patch committed for this bug. PS: Anyway, if all these scripts are being refactored before Feisty release to be more event oriented, then this discussion has little meaning :-) -- networking script does not wait for udev to settle https://launchpad.net/bugs/77438 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
