Hi. On Sun, Oct 14, 2018 at 09:22:53AM -0400, Cindy-Sue Causey wrote: > On 10/14/18, to...@tuxteam.de <to...@tuxteam.de> wrote: > > On Sat, Oct 13, 2018 at 07:11:07AM +0000, Long Wind wrote: > >> Thank tomas! > >> > >> i run "cat /etc/adjtime" in jessie and it says LOCALbut in stretch > >> /etc/adjtime doesn't seem to exist > > > > I see. Perhaps this is the root of the problem. On the other > > hand, perhaps, systemd is taking care of time in stretch by > > default. In that case I can't help, since my knowledge of > > systemd is minimal. > > > I was going to bring this up yesterday, just couldn't rope the words > in together. With debootstrap, one step the user manually does is > this: > > +++ QUOTE k/t https://www.debian.org/releases/buster/amd64/apds03.en.html +++
That guide contains curious relics of the past that include, but aren't limited to: 1) 'lo' interface in /etc/network/interfaces - unneeded even with stretch's ifupdown. 2) 'hostname' record in /etc/hosts - unneeded with libnss-myhostname. 3) '.local' domain at /etc/resolv.conf - a direct violation of RFC 6762. 4) At controversial (to say the least) recommendation to use 'deb-src' of Debian main suite without actually specifying 'deb'. 5) The /etc/adjtime configuration itself. Systemd defaults to UTC - src/timedate/timedated.c in systemd source tree. If needed, one can use timedatectl(1) to produce perfectly valid /etc/adjtime. > D.3.4.3. Setting Timezone Of course, whoever wrote this certainly considered *other* init systems that Debian ships - unlike systemd-timedated, sysvinit, openrc and upstart rely on hwclock(8). But since removing systemd from modern Debian takes certain skill and determination and a reason to do so - I somehow doubt that OP's problem can be explained by an absence of /etc/adjtime. Reco
