On Tue 01 Apr 2025 at 04:58:27 (-0400), gene heskett wrote:
On 3/31/25 23:02, David Wright wrote:
On Mon 31 Mar 2025 at 16:35:58 (-0400), gene heskett wrote:
On 3/31/25 13:55, David Wright wrote:
I don't know why you have problems with using /etc/hosts for lookups
on your LAN. I use it here without any problems, and it has to work
because there's no DNS server in my router (too cheap).
$ grep hosts: /etc/nsswitch.conf
hosts: files mdns4_minimal [NOTFOUND=return] dns
because files doesn't work in bookworm, I had to:
grep hosts: /etc/nsswitch.conf
hosts: files mdns4_minimal [NOTFOUND=return] dns myhostname
to make the hosts file work
I don't know why you're using libnss-myhostname,
neither do I David, it doesn't make sense, but I've just found that
file, except for that added word, is far different overall than the
man page example. So I've commented that word back out, and here is
what I have now, which bears no resemblance to the man page example;
So here you are, poking your system in one location, without taking
account of how it's configured elsewhere. Perhaps that's how you find
yourself in difficulties in the first place?
"I don't know why you're using libnss-myhostname" was an assumption
on the basis of your saying that you had to add "myhostname" to
make your system work. If you poke your system as randomly as you have
just done, then how would we have confidence in that being the one
change that originally made it work, and not anything else. We don't
even have solid evidence of (or the reason for) the libnss-myhostname
package being installed at all.
Also, changing configurations on a running system may well solve some
current problem, but it can affect how the system will boot up the
next time, and the effects may be deleterious. In any case, you said
your system is currently working, and took you a great deal of trouble
to make it do so, yet you're happy to moan about it, and then poke
around at random, and potentially remove some of the sticking plasters
that hold it all together.
you also called my hosts file unconventional, its been updated, is a
totally private network, so not planet visible as its all my side of
the router. Whats unconventional.
What Brian pointed out in the thread: the lack of 127.0.1.1, the
conventional way in which Debian ensures a host can find its own
name when the network is not up.
You seem to have taken umbrage
against it for no good reason. (ISTR there was a long discussion
on the subject some years ago on the list.) Substituting it back
is not a panacea. And no one on this list is likely prepared to
spend a week, or however long, in unravelling your system.
Just live with it.