On Mon Dec 25 12:01:59 2023 "Andrew M.A. Cater" <amaca...@einval.com> wrote:
> Yes - that's the obvious way. I set my machines to /etc/UTC (or > /etc/GMT) and leave them there. No daylight saving time, no offsets - > all logs unambiguous. That's why (worldwide) radio logkeeping is/was > in UTC. If you're travelling in an aircraft, you don't _need_ to know > ground time but you do need to know flight time against a reference > time. The Royal Air Force keep to UTC wherever they are in the world > for just this reason. Not just the RAF. All aviation works in UTC, to avoid problems when flights cross time zone boundaries, and to keep wide-area weather forecasts sane. Your average airline passenger never sees UTC, since airlines use it behind the scenes and convert it to local time for display purposes. (That's why you can see some strange intervals between departure and arrival times.) As a side note, a similar dichotomy applies to airport designators; passengers and baggage handlers only see the three-letter IATA codes (e.g. YYZ for Toronto), while flight plans are filed using the 4-letter ICAO codes (e.g. CYYZ for Toronto). For the most part, Canadian ICAO codes are the IATA code with a C in front, and American ICAO codes are the IATA code with a K in front - but there are exceptions. And ICAO codes cover all registered airports, not just those with scheduled airline service. -- /~\ Charlie Gibbs | Life is perverse. \ / <cgibbs@kltpzyxm.invalid> | It can be beautiful - X I'm really at ac.dekanfrus | but it won't. / \ if you read it the right way. | -- Lily Tomlin
