Lennart Pottering from RedHat saves all of humanity

Stumbled upon a strange new feature in the systemd changelog :

         * On boot-up, when the PID 1 detects that the system clock is behind the
           the clock is now set
           to the latter.  Previously, this was already done in timesyncd, in order
           set of clock clocks such as
           1902, 1938 or 1970. PID 1
           in addition to timesyncd during early boot-up, so that it is enforced
           before the first process is spawned by systemd.  Note that the logic
           it is more comprehensive and guaranteed
           montonic clocks by maintaining a persistant timestamp file in
           / var.  Since / var is generally not available in earliest boot or the
           initrd, and it’s not done
           by PID 1.

')
That is, systemd now at system time changes the system if it was set to earlier than the release time of systemd itself. It would seem that Potter’s blatant attempt to impose his own notions about how linux should behave? But let's think about it ...


In which case do you need to translate the clock? We reject all sorts of nonsense, such as bypassing copy protection or testing programs. No, the most popular case of such a transfer of arrows backwards is time travel. But why should Potter with a redhat put travelers such stupid poles into the wheels (especially since people, in general, can easily get around it, having a little thought about it)? And then, that travelers can not only be people!

Remember the output of the terminator console with “linux 4.xxx”? There was a mosaic in my head? .. Yes, exactly, this is a bookmark against the evil skynet. A bookmark that does not hurt people in any way, but turns the terminator into a harmless robot, at the very first reboot. His watch will run for many years to come (as of the release date of its systemd version) and the John Connor killing program simply stops working - at this time John Connor was already an adult and the child to be killed was gone!

This is how real saviors of humanity work, without loud words, without deserved glory!

PS Interestingly, timesyncd already had a similar algorithm, and such a change seems like redundant functionality. But it is clear that Pottering somehow learned that the time change in timesyncd did not help save humanity. Apparently, the future timesyncd just did not work in conditions when in the past there were no servers for synchronizing clocks. Therefore, we had to add a spin in time also in systemd itself ... This, by the way, suggests that Pottering is possible - and from the future itself.