Re: Hostname v buster

[Gene Heskett <gheskett@shentel.net>]

On Saturday 29 June 2019 09:25:23 John Paul Adrian Glaubitz wrote:

> > On Jun 29, 2019, at 3:37 AM, Gene Heskett <gheskett@shentel.net>
> > wrote:
> >
> > That conversion insists the hostname is realtimepi.  In stretch I
> > could fix it to the name I'm used to by setting hostname, then sudo
> > chattr +i hostname, and it would stick over a reboot, but not in
> > buster, despite the immutable bit being set, its been reset to
> > realtimepi after a reboot, this despite an lsattr still showing the
> > i bit is still set!
>
> Try hostnamectl:
>
> # sudo hostnamectl set-hostname HOSTNAME
>
> where HOSTNAME is your new hostname.
>
> Adrian
That worked, many thanks

 but the 2nd question re the avahi BS is still screwing me up.
Outside dns lookup is working fine, and according to /etc/resolv.conf:

nameserver 192.168.71.1
search hosts nameserver

So a ping yahoo (or any site out of my local network)
root@picnc:/etc# ping yahoo.com
PING yahoo.com (98.138.219.231) 56(84) bytes of data.

resolves yahoo correctly, but

From 169.254.163.253 (169.254.163.253) icmp_seq=1 Destination Host 
Unreachable
From 169.254.163.253 (169.254.163.253) icmp_seq=2 Destination Host 
Unreachable
From 169.254.163.253 (169.254.163.253) icmp_seq=3 Destination Host 
Unreachable

I can't find a trace of those addresses anyplace in /etc so how do I get 
rid of them forever?

apt purge avahi-* gives:
[...]
The following packages will be REMOVED:
  avahi-daemon* libnss-mdns*

Is this safe on a staticly defined network?

Thanks.

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)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/gene>