I’ve been using Debian for many years and rarely had any problem. Since systemd reared its ugly head and Debian “So, summary:
– the world is not perfect
– there are many places where the time can be switched, not only through NTP.
– the hwclock mechanism was perhaps a workaround, but it worked for all of us for many years
– so make sure that something works for all of us is put in place before removing it”decided to make it the default init, all Hell has broken loose.
e.g. Bug filed in July 2014, and still release-critical today… #755722 – systemd must sync systemclock to RTC on shutdown – Debian Bug report logs.
The issue is the same as I have with the boot-times for my desktop PC, systemd makes assumptions that break Debian systems. In my case, systemd insists on every other service starting and running before attempting to start X, the thing I want up ASAP. In the case of the bug reported above, how the system time was handled over a reboot is changed with systemd. The old behaviour was that the clock was stored and retrieved so things survived reboots nicely. No more. Poettering et al have decided that time should be set by NTP or other means and systemd should not have anything to do with that although systemd is replacing the old init that did… BREAKAGE!!! Now I know why Linus swears so much! If a change to systemd breaks user’s systems, it’s a bug in systemd, not that the world needs to change to be the way Poettering wants. Putting folks who break things in charge of millions of systems is a tragedy of huge proportions. People should not have to rewrite init scripts to switch to systemd. Otherwise, systemd should get the Hell out of our way… or go away…
Fork systemd. Get it away from those fools.