On Tue, 2014-10-07 at 19:14 +0200, Andreas Henriksson wrote:
> Control: reopen -1
> Control: found -1 2.25.1-4
Where is -4?
> Hello!
>
> I'm reopening this bug report regarding using --hctosys in the util-linux
> hwclock-set script. The change was proposed for the benefit of arm
> systems where RTC drivers are built as modules and when they get loaded
> the previous scheme didn't work.
>
> Unfortunately it was reported that the new scheme breaks systems which
> (AIUI) the hardware clock is set to local time (and using the new
> initramfs-tools 0.118 scheme where time set set up in the initramfs).
[...]
I have tested the new initramfs-tools (0.118) and util-linux (2.25.1-3)
with 'LOCAL' in /etc/adjtime, and all combinations of {busybox,klibc} in
initramfs and {systemd,sysvinit} as init system. And I got the right
system time in all cases (and we are still at UTC+0100 here).
(With older versions of util-linux this would not work, and the
versioned dependency in initramfs-tools doesn't force an upgrade from
the experimental 2.25 versions. I can bump the dependency if you think
that's worthwhile.)
Ben.
--
Ben Hutchings
Logic doesn't apply to the real world. - Marvin Minsky
Attachment:
signature.asc
Description: This is a digitally signed message part