[Bug 1201978] dracut assumes BIOS time is UTC closed without fixing again

[Lennart Poettering]

On Mon, 04.05.15 13:24, Zbigniew Jędrzejewski-Szmek (zbyszek at in.waw.pl) wrote:

> On Mon, May 04, 2015 at 12:00:31PM +0200, Till Maas wrote:
> > On Sun, May 03, 2015 at 03:23:24PM +0000, Zbigniew Jędrzejewski-Szmek wrote:
> > 
> > > For majority of ro-at-boot setups, changing to rw would be the best and the simplest
> > > solution. I don't think we should do that automatically (e.g. through rpm macro),
> > > but instead encourage people to switch manually. I have no idea what would
> > > be a good place to put this information though.
> > 
> > Good places would be the release notes and:
> > https://fedoraproject.org/wiki/Upgrading_Fedora_using_yum#Fedora_21_-.3E_Fedora_22_.28not_yet_released.29
> 
> On second though, where exactly is 'ro' coming from?
> On my system it comes from:
> 
> $ sudo grep ' ro ' /etc/grub.d/10_linux
>         ${linuxefi} ${rel_dirname}/${basename} root=${linux_root_device_thisversion} ro ${args}
>         linux${sixteenbit} ${rel_dirname}/${basename} root=${linux_root_device_thisversion} ro ${args}
> $ rpm -q grub2-tools
> grub2-tools-2.02-0.15.fc22.x86_64
> 
> Maybe it's enough to change it there?

Nah, I am pretty sure it should just stay, as that's what has been
done always and is what makes initrd-less boots work
correctly, as we actually need a read-only root initially then, that
is remounted rw only after fsck ran. The rw setting is applied based
on the settings from /etc/fstab for the root fs.

The kernel should initially boot with the root file system read-only,
and then remount it writable during early boot. This is also essential
for systems where the root file system shall stay read-only during
runtime, since booting ro and then remounting rw makes sense, but
booting rw and then remounting ro certainly doesn't...

Hence I think FEdora is fine as it is.

Lennart

-- 
Lennart Poettering, Red Hat