mirror of
https://github.com/NixOS/nixpkgs.git
synced 2025-11-15 04:04:18 +01:00
d67caf3c89
When initializing a system (e.g. first boot / livecd) we have no good reference source for time. systemd-timesyncd however would revert back to its configured fallback time (in our case 01.01.1980). Since we probably don't want to hardcode a specific date as fallback we are now using the current system time (wherever that might have come from) to initialize the reference clock file. The only systems that might be remotely affected by this change are machines that have highly unreliable RTCs or those where the battery that backs the RTC is running empty. Historically these systems always had a tough time with anything time related and likely required manual intervention. For stateless systems (those that wipe / between reboots or our installer CDs) this has the consequence that time will always be reset to whatever the system comes up with on boot. This is likely the correct time coming from an RTC. No harm done here the situation is likely unchanged for them. For stateful systems (those that retain the / partition across reboots) there shouldn't be a change at all. They'll provide an initial clock value once on their lifetime (during first boot / after installation). From then onwards systemd-timesyncd will update the file with the newer fallback time (that will be picked up on the next boot). |
||
|---|---|---|
| .. | ||
| loader | ||
| binfmt.nix | ||
| emergency-mode.nix | ||
| grow-partition.nix | ||
| initrd-network.nix | ||
| initrd-openvpn.nix | ||
| initrd-ssh.nix | ||
| kernel.nix | ||
| kernel_config.nix | ||
| kexec.nix | ||
| luksroot.nix | ||
| modprobe.nix | ||
| networkd.nix | ||
| pbkdf2-sha512.c | ||
| plymouth.nix | ||
| resolved.nix | ||
| shutdown.nix | ||
| stage-1-init.sh | ||
| stage-1.nix | ||
| stage-2-init.sh | ||
| stage-2.nix | ||
| systemd-nspawn.nix | ||
| systemd.nix | ||
| timesyncd.nix | ||
| tmp.nix | ||