Comment # 23 on bug 948771 from Michael Chang

(In reply to Fabian Vogt from comment #13)
> (In reply to Franck Bui from comment #9)
> > (In reply to Fabian Vogt from comment #4)
> ...
> > @Fabian: if I'm understanding the new behaviour of dracut correctly, any
> > modifications regarding the rootfs in /etc/fstab by the admin requires now
> > to regenerate the initrd, which is something that is unusual.
> Only if the location of / or critical mount options were changed.

No. This basically means we need to re-generate initrd to get everything synced
to be in safe side. It's hard to distinguish by how mount options is modified
and also it's importance. The other problem is user need to be trained to know
the new trick.

> With root= on the grub cmdline you had to regenerate the bootloader config
> and it would break in most cases, as grub2-mkconfig doesn't look at
> /etc/fstab at all AFAICS.

I don't know why grub2 (or any other boot-config) would break without
/etc/fstab. The root= is meant to tell kernel or initrd where to look up root
partition, then they can take over the control from this given information they
would need before they can proceed.

Thanks.