On Fri 24 Mar 2023 at 17:13:31 (+0000), Albretch Mueller wrote:
> On 3/24/23, Andy Smith <a...@strugglers.net> wrote:
> > As already pointed out, the hardware clock is used in very limited
> > ways and is not the same thing as the system clock, so your result
> > is as expected.
> > What are you actually trying to do?
> >
> > What "time zone issues" do you refer to?
>
> I should have pointed out that I always go into exposed mode (use the
> Internet) with a live DVD. My laptop was always 6 hours ahead and now
> that they changed to summer time, it is 5 hours ahead.
> I used logs which names a time a la:
>
> _DT=$(date +%Y%m%d%H%M%S)
> _BN=$(basename "${_SDIR}")
> _LOG_FL="${_BN}_${_DT}.log"
> ...
> If anything, timing is one of the aspects of reality which should be
> coordinated.
Hence the existence of UTC since around 1960: Coordinated Universal Time.
But to benefit from it, you also have to coordinate your computers
/and/ their OSes. I can't imagine trying to run a laptop with its RTC
on Local time, because of time zone changes when travelling. I suppose
it's just about possible to manage it on a desktop computer in Arizona.
Like Greg, I've not used Live systems to any extent, and don't know
how they handle setting a time zone.
BTW I've only really trusted reading or setting the RTC by means of
the CMOS screens, and treat it as a one-time only process (upon
acquisition), assuming the coin-cell battery never needs replacing.
(All my computers have begun life running Windows.)
Cheers,
David.
