On Wed, 27.07.16 19:54, Michał Zegan ([email protected]) wrote:
> Hello.
>
> There is, it seems, a problem with the hardware clock. That is, the
> systemd does not care about it. Neither systemd nor udev rules set the
> system time using the hardware clock.
> From what I know, if the clo
On 2016-07-27 19:54, Michał Zegan wrote:
> Hello.
>
> There is, it seems, a problem with the hardware clock. That is, the
> systemd does not care about it. Neither systemd nor udev rules set the
> system time using the hardware clock.
Strictly speaking, systemd does at bootup what hwclock used to
Currently I use hwclock command directly for situations like that (with
dragonboard, pi etc) , it's automated using chef.
On Jul 27, 2016 10:55 AM, "Michał Zegan" wrote:
> Hello.
>
> There is, it seems, a problem with the hardware clock. That is, the
> systemd does not care about it. Neither sys
Hello.
There is, it seems, a problem with the hardware clock. That is, the
systemd does not care about it. Neither systemd nor udev rules set the
system time using the hardware clock.
From what I know, if the clock is a cmos rtc, the kernel always sets
time during bootup. In any other case, it sho
