From: Mike Gilbert <floppym@gentoo.org>
To: Gentoo Dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] timezone configuration - why copying, not symlinking /etc/localtime ?
Date: Mon, 22 Mar 2021 00:07:10 -0400 [thread overview]
Message-ID: <CAJ0EP41HcxU8CmyQ--Wk15Zwhqpej6mmcT5nTZRZCxNQN6-OoQ@mail.gmail.com> (raw)
In-Reply-To: <4300ff7a-36c2-b4db-ad68-b5e1e6d8113f@gentoo.org>
On Sun, Mar 21, 2021 at 11:06 PM Thomas Deutschmann <whissi@gentoo.org> wrote:
>
> On 2021-03-22 03:06, Mike Gilbert wrote:
> > Based on that commit message, it looks systemd switched to looking at
> > the symlink target instead of /etc/timezone well *after* some major
> > distro started using a symlink for /etc/localtime. I suspect Kay
> > Sievers noticed that the content of /etc/timezone and /etc/localtime
> > were redundant on his development machine, and added a TODO entry to
> > eliminate the redundant /etc/timezone file.
> >
> > In other words, this isn't a case of systemd forcing distros to
> > symlink /etc/localtime; they were already doing that anyway.
>
> I just downloaded and tested some old distributions:
>
> Debian 9 was the first Debian release with systemd. Because of systemd,
> /etc/localtime became a symlink. In Debian 8 or when you install Debian
> 9 without systemd, it is a regular file.
>
> Ubuntu 12.04.5 is the same: No systemd, /etc/localtime is a regular
> file. Once they moved to systemd it became a symlink.
>
> In Fedora 17, which is already using systemd but a version before linked
> commit, /etc/localtime is also a regular file. But once Fedora upgraded
> to >=systemd-190 it became a symlink.
Thanks for looking into it. I wonder how Kay's system ended up that
way then. Just a curiosity.
> That's why from my P.O.V. this is clearly caused by systemd. But does
> this matter?
You're the one who brought it up; I'm not sure what the point of that
was, other than to complain about systemd.
next prev parent reply other threads:[~2021-03-22 4:07 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-20 15:37 [gentoo-dev] timezone configuration - why copying, not symlinking /etc/localtime ? Andreas K. Huettel
2021-03-20 16:04 ` Nils Freydank
2021-03-20 19:10 ` William Hubbs
2021-03-21 4:18 ` Ulrich Mueller
2021-03-21 4:48 ` Alec Warner
2021-03-21 5:27 ` Ulrich Mueller
2021-03-21 5:56 ` Alec Warner
2021-03-21 7:23 ` Ulrich Mueller
2021-03-21 7:58 ` James Le Cuirot
2021-03-22 8:59 ` Andreas Sturmlechner
2021-03-22 20:18 ` Lars Wendler
2021-03-23 3:01 ` Andreas Sturmlechner
2021-03-22 22:54 ` Andreas K. Huettel
2021-03-23 7:22 ` Jaco Kroon
2021-03-23 11:31 ` Rich Freeman
2021-03-27 21:43 ` Joshua Kinard
2021-03-27 22:16 ` James Le Cuirot
2021-03-27 22:40 ` Joshua Kinard
2021-03-28 9:25 ` James Le Cuirot
2021-03-28 23:46 ` Joshua Kinard
2021-03-29 8:06 ` James Le Cuirot
2021-04-22 18:14 ` Marek Szuba
2021-04-22 18:18 ` Marek Szuba
2021-03-28 0:32 ` William Hubbs
2021-03-28 2:51 ` Joshua Kinard
2021-03-28 20:05 ` William Hubbs
2021-03-28 23:31 ` Joshua Kinard
2021-03-29 6:07 ` William Hubbs
2021-03-28 1:00 ` Rich Freeman
2021-03-28 1:58 ` Joshua Kinard
2021-03-21 23:58 ` Thomas Deutschmann
2021-03-22 2:06 ` Mike Gilbert
2021-03-22 3:06 ` Thomas Deutschmann
2021-03-22 3:19 ` Thomas Deutschmann
2021-03-22 4:07 ` Mike Gilbert [this message]
2021-03-22 2:49 ` Mike Gilbert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJ0EP41HcxU8CmyQ--Wk15Zwhqpej6mmcT5nTZRZCxNQN6-OoQ@mail.gmail.com \
--to=floppym@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox