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;
passwd: files systemd
group: files systemd
shadow: files systemd
gshadow: files systemd
hosts: files mdns4_minimal [NOTFOUND=return] dns # myhostname
networks: files [NOTFOUND=RETURN] dns
protocols: db files
services: db files
ethers: db files
rpc: db files
netgroup: nis
#========= as installed by bookworm. Whats right, and whats wrong.
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. Here it is today:
127.0.0.1 localhost
192.168.71.1 router.coyote.den router # dd-wrt 192.168.71.2 amanda.coyote.den amanda # backup under construction
192.168.71.3 coyote.coyote.den coyote # this big tower 192.168.71.4 sixty40.coyote.den sixty40 # 6040 milling machine 192.168.71.7 vna.coyote.den vna #retired 192.168.71.8 rock64v2.coyote.den rock64v2 #retired 192.168.71.122 bpi51e5p.coyote.den bpi51 e5p #3dprinter 192.168.71.10 go704.coyote.den go704 # milling machine 192.168.71.11 tronxy400.coyote.den tronxy400 #3dprinter under construction
192.168.71.12 bpi54.coyote.den bpi54 #possible 3dprinter 192.168.71.13 rpi4.coyote.den rpi4 # Sheldon 11x54 lathe 192.168.71.21 scanner.coyote.den scanner # in inkjet brother mfc-j6922d
192.168.71.22 rock64.coyote.den rock64 #future 3dprinter 192.168.71.23 bpi52.coyote.den bpi52 #future 3dprinter 192.168.71.25 tlm.coyote.den tlm #7x12 lathe 192.168.71.50 dddprint.coyote.den dddprint # retired 3dprinter 192.168.71.55 bpi55.coyote.den bpi55 # future 3dprinter 192.168.71.56 bpi56.coyote.den bpi56 # furure 3dprinter 192.168.71.121 mkspi.coyote.den mkspi xmax3 # 3dprinter 31.184.194.81 Sci-Hub.se scihub.se # internet blacklisted
& now defunct, won't ping
What, other than the .den which I've used without a problem since 1989
with many distro's & architectures, is unconventional?.
nor whether it's
something to do with your unconventional (for Debian) /etc/hosts
that you listed in:
https://lists.debian.org/debian-user/2023/08/msg00061.html
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.
Then why the complaint?
The query still stands.
Cheers,
David.
.
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
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)