systemd (when started or restarted) sets the system clock to its own "epoch" which is the highest of:
* build time of systemd * mtime of /usr/lib/clock-epoch (the thing I've patched in our raspi image builds) * mtime of /var/lib/systemd/timesync/clock The latter appears to be something systemd-timesync periodically sets to ensure there's some reasonably up-to-date mtime to initialize the system clock from (in a similar manner to fixrtc, albeit with an explicit file rather than rootfs' mount time). At first, I considered using that instead of /usr/lib/clock-epoch in the image build patch. However, we've switched to using chrony instead of systemd-timesync so that file doesn't exist by default, and I didn't want to dig into the question of what happens if it's precreated with the wrong owner (as systemd- timesync adds a systemd-timesync user to own it). So ... clock-epoch feels like a bit of a hack, but it's the simplest, cleanest way of getting the raspi stonking images to set time "reasonably" on first boot until I can get fixrtc (or something like it) implemented. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2170178 Title: Keyboard layout not working on Ubuntu Server for Raspberry Pi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-images/+bug/2170178/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
