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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Adam Williamson composed on 2015-04-30 15:49 (UTC-0700):

> We seem to have two sides saying two fundamentally different things
> here: one claiming that all Windows/Fedora multiboot systems (that
> haven't had the hardware clock set to UTC and Windows adjusted to know
> about that) are doing fsck on boot all the time, one claiming that
> "This only trips you up if you combine two known broken settings".

> Who's correct? It seems like we should at least be able to reasonably
> establish that.

All my Fedora 21/22/23 (20+) installations are on multiboot PCs with RTC set
to local, and /etc/adjtime set to LOCAL. I can't recall if any are *not* now
taking 3 minutes or more to boot due to fsck delays that were not occurring
as recently as 3-4 months ago. Maybe kernel 3.18.3 or so was good, 3.19rc
started the fsck delays? Cauldron and Tumbleweed booting 3.19.4 kernels on
same PCs are not producing any similar delays, some booting in under 40s
without benefit of SSD or more than 2 cores.
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/
-- 
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct





[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux