On Wed 02 Apr 2025 at 09:12:24 (-0400), gene heskett wrote: > On 4/2/25 01:28, David Wright wrote: > > 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: > > 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. > > I can put it back in, but no one has ever explained why. And since > it's been gone for 27 years, what name goes with it? > Ack the man page, it should be coyote.coyote.den, but that has been > 192.168.71.3 for that same 27 years. [ … ] So > what should I put in there for what the man page says?: > 127.0.1.1 thishost.example.org thishost
127.0.1.1 coyote.coyote.den coyote > Experimenting I find the duplication does not seem to generate an > error, other than I now had to ping itself by address, since the name > is now found at 127.0.1.1 by pings lookup? That's what you want: as the address is in the 127.0.0.0 network, pinging it will ping itself, and it gets a reply. It doesn't require your LAN to be set up, and AIUI it's like localhost (127.0.0.1) in that it doesn't touch the network hardware. > I'll leave it in the hosts > file as a duplicate, until I find something that does not work, I don't see the point in leaving it there. If you want to send something to coyote.coyote.den, why do you want the LAN address when 127.0.1.1 is just as good. If the line is correct, it does nothing; if it's incorrect, it can cause harm. And coyote's own hosts file can't be seen by other machines trying to find coyote: they will use their local copy. Bear in mind that the same holds true for each machine on your LAN, so the hosts file will be different for each one. My master list, which I reconcile with the router's DHCP server Reservation List, is installed onto a system with a line like: # sed -E "/^[[:space:]]*192.168.1.[0-9]+[[:space:]]+$HOSTNAME.corp[[:space:]]+$HOSTNAME[#|[[:space:]]|\$]/s/[[:space:]]*([0-9.]+)[[:space:]]+(.*)\$/127.0.1.1\t\2\t# \1/" master-list >/etc/hosts That assumes 1, not 71, corp rather than coyote.den, and it would fail on your .122 line because the HOSTNAMEs are different for some reason. (I wrote the pattern to conform to my own expectations.) > but > it also has no effect on the 30 second gui freeze on opening a file I > own. I don't see why it would. But I don't have experience with DEs, so I wouldn't be much help with a problem like that anyway. I also don't know what your problem with NM and resolv.conf is all about. But static addressing with a hosts file doesn't have to be 3rd class, and I don't feel treated as such. Cheers, David.
