Lennart Poettering composed on 2015-01-28 02:03 (UTC+0100): > Felix Miata wrote:
>> Both. When they occur during init they repeat during shutdown. Even when I >> let init complete and succeed to fix the typo or oversight, the init failure >> gets remembered and repeated at shutdown. Often the start job is on account >> of a volume label that has been replaced, usually along with a UUID, because >> the clone is a partition on the same HD. Fedora is particularly frustrating >> by embedding dependent root volume label and not obeying root= on cmdline >> (openSUSE obeys root=). Those typos usually have to be fixed by chroot to run >> dracut. > Hmm, Fedora doesn't obey root=? That sounds like a bug. I think it's only a problem due to Fedora's configuration of its Dracut hostonly option used by default. AFAICR, its rescue initrds have always worked. I can't remember now, but it may possibly be Mageia with hostonly enabled disobeys root= too, locking onto root's UUID when the initrd was built. It's never been a problem I've observed in openSUSE, which let dracut evolve a lot longer before switching to it from mkinitrd. > Harald? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
