On 1/6/24 01:18, Max Nikulin wrote:
On 06/01/2024 12:18, gene heskett wrote:
On 1/5/24 23:29, Greg Wooledge wrote:
On Fri, Jan 05, 2024 at 09:01:29PM -0500, Charles Kroeger wrote:
tzdata (2023d-1) unstable; urgency=medium
upstream backward file) were moved to tzdata-legacy. This
includes the
What's wrong with NTP, too simple?
NTP and tzdata have nothing to do with each other.
I see no relation to NTP as well. Somebody decided that
/usr/share/zoneinfo is full of garbage and needs clean up:
https://lists.ubuntu.com/archives/ubuntu-devel/2023-January/042405.html
Some people prefer to not have tzdata at all:
https://fedoraproject.org/wiki/Changes/AllowRemovalOfTzdata
I do not live in one of those special locations so I assume it won't
affect me, but there is a small percentage here and in many other
country's that live in locations that don't follow DST for some reason.
DST is unrelated as well.
The change affects those who rely on POSIX-like EST5EDT timezones or on
obsolete ones like Europe/Kyiv (recently renamed from Europe/Kiev).
Those who provides various calendar services have significant
probability to face user issues.
Doesn't this change affect trixie while bookworm will stick to current
package style?
.
Well, since /usr/share/zoneinfo/UTC is a link to
/usr/share/zoneinfo/Etc/UTC now, it would save about 4 megabytes worth
of duplicates and links that is an organizational mess for the
maintainer now. On the face of it. 25 years overdue? Put all system
clocks on UTC, and then /etc/timezone is the actual string specifying
the local offset. No doubt some user confusion, but overall a lot simpler.
Related subject:
Since I have several machines on my local network here, I've just been
thru hell trying to get them all on the same page, and with debian
version of ntpsec being happy with a single pool entry pointing to the
ntpsec on this machine, it foiled my plans to reduce the load on the
debian server pool by making this machine a stratum 2 server as some,
not all, of the armbian boxes fail to sync at all with only one pool entry.
Or I'm still doing it wrong, always a possibility. If someone knows how
to reliably sync to a single pool entry, I'm all ears.
Or, if someone know how to make systemd's timesyncd actually work, I've
not been able to do that on 7 machines here, that would be appreciated
too. Lack of documentation (man pages) for that puppy is a major
blockaid here on bookworm. To me, its a potential solution in search of
a problem that with chrony or ntpsec working, doesn't exist. chrony also
claims to be an ntp server lookalike, again lack of docs to make it work
are the problem. If docs on chrony exist, where the heck are they? And
what file utility do we have to read them with that actually works?.
Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
- Louis D. Brandeis
