Re: Second (erroneous) check of rootfs?

[Andrei Borzenkov <arvidjaar@gmail.com>]

В Sun, 11 Jan 2015 15:22:54 +0300
Nikolai Zhubr <n-a-zhubr@yandex.ru> пишет:

> Hi,
> 11.01.2015 14:11, Andrei Borzenkov:
> [...]
> > By adding all needed options to rootflags="..." (modify
> > GRUB_CMDLINE_LINUX_DEFAULT and possibly GRUB_CMDLINE_LINUX_RECOVERY
> > in /etc/default/grub; you can use yast for it).
> 
> Ah, indeed.
> Although it feels a bit ugly because the consistency between fstab and 
> GRUB_CMDLINE_* will have to be verified manually forever then.
> 

It's no more ugly than using privately patched distribution package. I
did not suggest it as long term generic solution.

> > Otherwise it is functional gap between non-systemd and systemd
> > enabled dracut. Without systemd dracut will actually mount root
> > read-only, then fetch mount options from real root /etc/fstab and then
> > remount real root read-write using correct options. This all got lost
> > when converting to systemd.
> 
> Hmm, can not find any dracut-specific mailing list to ask. Apparently 
> there is none :(

There is; you keep removing it from Cc.

> Anyway, generally, why not pack a real fstab from the host into initrd 
> then? Or at least one line ("/") from it? Something prohibits this?
> 

Dracut does pack /etc/fstab in initrd if run in host-specific mode,
but right now systemd-fstab-generator will never parse /etc/fstab
for /sysroot mounts. Pre-systemd dracut would actually merge options
from rootfs /etc/fstab and rootflags.

Even if you add additional parsing of in-initrd /etc/fstab, it still
means you need to regenerate initrd every time you change /etc/fstab so
you still have the same problem as when explicitly adding rootflags -
keeping both in sync :) 
_______________________________________________
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel