On 3/31/25 05:10, Andy Smith wrote:
Hi,
On Mon, Mar 31, 2025 at 03:36:20AM -0400, gene heskett wrote:
On 3/31/25 02:09, Henrik Ahlgren wrote:
I believe /run/utmp is gone in trixie, after systemd was upgraded to
256.5-2. The command `w` still works fine.
no, its dns lookup fails there also.
This conversation is about the "who" command's inability to show who is
currently logged in, not the second thing mentioned which was it not
doing DNS lookups.
The utmp database had to change because it was not year 2038 safe. who
just hasn't been updated yet. The bugs and complaints for that need to
go upstream, as much as anyone can complain over free software.
Here is the bug report you quoted but did not read:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080330
I've read it now, but I'm disappointed at how this has been treated. Pot called
the kettle black and vice versa with zero progress as bookworm is stuck on 9.1
while the rest of the planet has moved on to at least 9.4 which works.
Tbird, beta, still has broken quoting.
The dns problem is separate I guess, but does bring up my other pet
peeve. That is that no one at debian considers the effect on dns to
those of us who have been using hosts files for local dns since back in
the late 90's I have no dhcpd setup and rig my lashup so that my local
lookups are first and in the hosts file, if not it the hosts, my isp's
dns gets queried. But every new install changes things around
resolv.conf making that harder and harder to do.
What makes the debian people treat hosts file users, like 3rd class
users? Its easier to setup, needs less maintenance, and Just Works
since my first linux install in '98... Sure, we can lock NM from
tearing a working net down by making resolv.conf immutable and a real
file. We no longer have to do that with bookworm but from wheezy to
bookworm we did have to protect resolv.conf from NM. But every time we
mention it, we catch it by giving us what for w/o telling us how to make
it work. That too gets old. Why?
Bottom line: who, or its ytmp helpers,
is incapable of reading the /etc/hosts file on systems w/o a dhcpd.
This is not how processes on Linux do DNS lookups. Virtually nothing is
"capable of reading the /etc/hosts file" because that's not how any of
this works.
Sorry to disappoint you but that seems to be working Just Fine, but once
again, you make no attempt to either explain why its wrong, or to tell
us what the right way is other than demanding we waste a week making
dhcpd actually work.
Thanks,
Andy
Cheers, Gene Heskett, CET.
--
"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
