I am still trying to figure out what happened - fact is that on the "problematic" machine the initrd definitely has the line
./scripts/init-top/udev:udevd --daemon --resolve-names=never after upgrading to 204. Maybe it's some override script I forgot somewhere, in any case, it is very likely a local problem. I apologise, please close this bug. Cheers, I. ----- Mail original ----- De: "Michael Biebl" <bi...@debian.org> À: 723...@bugs.debian.org Cc: cont...@bugs.debian.org, "Itaï BEN YAACOV" <can...@free.fr> Envoyé: Mercredi 18 Septembre 2013 00:12:08 Objet: Re: Bug#723198: udevd not copied to initrd, system unbootable severity 723198 important thanks Am 17.09.2013 17:55, schrieb Michael Biebl: > tags 723198 + moreinfo unreproducible > thanks > > Am 17.09.2013 14:38, schrieb Michael Biebl: >> Can you attach the output of >> "grep udevd /usr/share/initramfs-tools -R" > > I've checked all packages installing an initramfs hook. > None of that calls udevd directly: > > # grep udevd /usr/share/initramfs-tools/ -R > /usr/share/initramfs-tools/scripts/init-bottom/udev:# Stop udevd, we'll miss > a few events while we run init, but we catch up > /usr/share/initramfs-tools/scripts/init-top/udev:/lib/systemd/systemd-udevd > --daemon --resolve-names=never > /usr/share/initramfs-tools/scripts/functions: if command -v udevd >/dev/null > 2>&1; then > /usr/share/initramfs-tools/hooks/udev:copy_exec /lib/systemd/systemd-udevd > /lib/systemd > > > So I'm having a hard time reproducing the problem you are seeing. > Can you attach a more verbose error log from your boot process? Downgrading severity since the problem is not reproducible and no further information was provided so far. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
