make timesync persistent

[andiradulescu]

Fixes #374 by:

• making the default system time to build time (by touching /usr/lib/clock-epoch) thus making the system time > /etc/fstab mtime (to prevent the fstab warning)
• symlinked timesyncd clock so that the last time set is set first at next boot
• validated by doing a couple of reboots and checking if 'systemctl daemon-reload' is requested

$ journalctl -u systemd-timesyncd
Sep 18 13:53:23 comma systemd[1]: Starting systemd-timesyncd.service - Network Time Synchronization...
Sep 18 13:53:23 comma (imesyncd)[3060]: systemd-timesyncd.service: ProtectHostname=yes is configured, but the kernel does not support UTS namespaces, ignoring namespace setup.
Sep 18 21:09:51 comma systemd-timesyncd[3060]: System clock time unset or jumped backwards, restored from recorded timestamp: Wed 2024-09-18 21:09:51 UTC
Sep 18 21:09:51 comma systemd[1]: Started systemd-timesyncd.service - Network Time Synchronization.
Sep 18 21:10:16 comma-cb80a5fa systemd-timesyncd[3060]: Network configuration changed, trying to establish connection.
Sep 18 21:10:29 comma-cb80a5fa systemd-timesyncd[3060]: Contacted time server 91.189.91.157:123 (ntp.ubuntu.com).
Sep 18 21:10:29 comma-cb80a5fa systemd-timesyncd[3060]: Initial clock synchronization to Wed 2024-09-18 21:10:29.738480 UTC.
$ sudo mount -o rw,remount /
$ 

[adeebshihadeh]

This breaks this.

Aside from that, I don't think we want the time to pick up where it left off. If the time is incorrect, I think I'd prefer it starting from the same point unless you have a good reason for this?

[andiradulescu]

The only reason I thought it's good to pick up from where it left off is that routes/logs are arranged in chronological order, and other events, like sentry, etc. any reasons why starting from the same point is better?