On Thu, Sep 13, 2001 at 08:03:22PM +0200, Guillaume Cottenceau wrote:
>
> Ok, as of mkinitrd-3.1.6-5mdk.i586.rpm, there is support for flags for the
> root filesystem.
>
> I can't use "rootflags" since these flags are used by the kernel to mount
> the initrd itself,
Interesting dilema. I wonder what the "owner" of the "rootflags"
option has to say about this situation. I wonder almost if the
mounting of the initrd should ignore the "rootflags" flags and if
there really is a need to pass options for mounting the initrd, a new
flag should be created (initrdflags perhaps).
In any case, I think rootflags should be reserved for mounting the
real rootfs, regardless of whether an initrd is being used or not.
Anyone care to take a quick peek at the source and see what the case
is? I can later if not.
> and they may be incompatible with notail of reiser for
> example.
Right which is why there should be separate flags for the real root
and the initrd. Since rootflags was intended for the "real root" a
new flag should be created for the initrd if needed.
> So mkinitrd uses the arguments found as #4 field of the / line of
> /etc/fstab.
But that does not solve the problem of needing to pass "one-of" flags
for mounting the real root. Like wanting to force the mount of an
ext3 with no journal (I seem to recall there is a mount option for
this) for debugging or error recovery etc.
b.
--
Brian J. Murrell
