| 1 |
On 2021-03-22 03:06, Mike Gilbert wrote: |
| 2 |
> Based on that commit message, it looks systemd switched to looking at |
| 3 |
> the symlink target instead of /etc/timezone well *after* some major |
| 4 |
> distro started using a symlink for /etc/localtime. I suspect Kay |
| 5 |
> Sievers noticed that the content of /etc/timezone and /etc/localtime |
| 6 |
> were redundant on his development machine, and added a TODO entry to |
| 7 |
> eliminate the redundant /etc/timezone file. |
| 8 |
> |
| 9 |
> In other words, this isn't a case of systemd forcing distros to |
| 10 |
> symlink /etc/localtime; they were already doing that anyway. |
| 11 |
|
| 12 |
I just downloaded and tested some old distributions: |
| 13 |
|
| 14 |
Debian 9 was the first Debian release with systemd. Because of systemd, |
| 15 |
/etc/localtime became a symlink. In Debian 8 or when you install Debian |
| 16 |
9 without systemd, it is a regular file. |
| 17 |
|
| 18 |
Ubuntu 12.04.5 is the same: No systemd, /etc/localtime is a regular |
| 19 |
file. Once they moved to systemd it became a symlink. |
| 20 |
|
| 21 |
In Fedora 17, which is already using systemd but a version before linked |
| 22 |
commit, /etc/localtime is also a regular file. But once Fedora upgraded |
| 23 |
to >=systemd-190 it became a symlink. |
| 24 |
|
| 25 |
That's why from my P.O.V. this is clearly caused by systemd. But does |
| 26 |
this matter? I doubt that systemd will even think about removing what I |
| 27 |
believe to be a false warning when systemd detects that /etc/localtime |
| 28 |
is a regular file. So let's focus on dealing with the fallout... |
| 29 |
|
| 30 |
|
| 31 |
-- |
| 32 |
Regards, |
| 33 |
Thomas Deutschmann / Gentoo Linux Developer |
| 34 |
fpr: C4DD 695F A713 8F24 2AA1 5638 5849 7EE5 1D5D 74A5 |
Archives