@yeti strong words there. A LOT of people run the rtc in local time, with dual boot and multiple boot.
There is no question about it. The answer is wrong. Not using it is wrong. Others use it. Linux before
systemd broke things here (too). The capability was lost, as I explained, when systemd
bit into the kernel and the relevant magic setting to make hwclock work with sysvinit scripts was lost
for a while. I put it back, using the hack I described above. So @yeti you have an opinion and you
expressed it, but face reality as it is, not as we wish it to be.

Internally the kernel fakes time as-if it would be UTC else all TZ stuff will break. This is all about how the
kernel gets initialized, there is no point in discussing whether the kernel runs in UTC-like (?) mode or real
UTC. At boot time, it has to get info from a real clock and fake or set it's internals as needed to make TZ
stuff work properly. This article is exactly about that. The need for a UTC referenced TZ is cast in stone
and POSIX required too afaik. So no way that is going to change in any way.

Re: rtc: the rtc in a local system, local to some country, will probably run on local time, with DST or not,
as specified locally. It is madness to set ONE clock on UTC out of 12 or so computer RTCs because
someone said so. People keep forgetting this, it is not good. Local is local. Not server room, not pro
IT locked down, but average office or home machine.

DST works like this: the OS which is running when DST change occurs, sets the DST mode not the
RTC. There should be no misunderstanding about it. The "other" system does not spoil it. It simply
uses the same convention. In other words: the OS which is running when the DST change occurs
changes the clock. Nothing new here. When the other system boots, it is either after or before the
DST change, so ONE system changes the clock when the DST change time occurs. There are no
mysteries to it. One system is running, one system changes the clock at midnight/etc, done. The
only trick is, both systems must agree on how the clock runs during DST time. I.e. if the RTC is
advanced during DST or if DST is implemented by a flag in the OS only between certain dates,
with RTC staying unchanged. Afaik the current LOCALTIME mode in the linux kernel and hwclock
works exactly like that in Windows, assuming the DST time change is dialed into the RTC, and not
just a flag.

Conclusion: It's okay to run RTC in LOCAL time on devuan without systemd with the howto I wrote
above. - pepe777 aka user _abc_ / ccbbaa @ irc.freenode,net