[systemd-devel] Second (erroneous) check of rootfs?

[Andrei Borzenkov]

В Sun, 11 Jan 2015 12:45:17 -0700
Chris Murphy <lists at colorremedies.com> пишет:

> On Sun, Jan 11, 2015 at 4:57 AM, Andrei Borzenkov <arvidjaar at gmail.com> wrote:
> > В Sun, 11 Jan 2015 04:15:41 -0700
> 
> > Does it using systemd *inside* of initrd? From upstream dracut:
> >
> >     if ! dracut_module_included "systemd"; then
> >         inst_hook cmdline 95 "$moddir/parse-block.sh"
> >         inst_hook pre-udev 30 "$moddir/block-genrules.sh"
> >         inst_hook mount 99 "$moddir/mount-root.sh"
> >                                     ^^^^^^^^^^^^^ here it does it
> >     fi
> >
> > Do you have Fedora specific patches to do it differently?
> 
> So the reason it's mounting all file systems ro by default appears to
> be strictly because of the ro kernel parameter in the grub.cfg as
> created by grub-mkconfig.

Again - when using mount-root.sh it will

- *always* mount real root ro
- fetch other mount options from real root /etc/fstab
- remount real root rw with correct mount options applied

This all got lost if you use standard systemd-fstab-generator +
systemd-fsck services.

If dracut now requires all root mount options to be always present on
kernel command line instead of in system /etc/fstab - fine but then this
should be stated so.