Re: dhcpcd ignores "force_hostname=YES" on diskless clients?

2019-09-22 Thread John D. Baker
On Sun, 22 Sep 2019, Roy Marples wrote: > If the hostname is "localhost" then dhcpcd won't send it. > If the hostname is "localhost" then dhcpcd will set the hostname given via > DHCP. The hostname is not and never has been "localhost" but that's what it was explicitly set to when 'dhcpcd' was

Re: dhcpcd ignores "force_hostname=YES" on diskless clients?

2019-09-22 Thread Roy Marples
On 21/09/2019 03:01, John D. Baker wrote: On Fri, 20 Sep 2019, John D. Baker wrote: (Before the recent imports of later versions of 'dhcpcd', it failed to obtain the FQDN on a sparc system and set the hostname as "localhost".) The diskless SPARC system works properly now. Will have to check

Re: dhcpcd ignores "force_hostname=YES" on diskless clients?

2019-09-20 Thread John D. Baker
On Fri, 20 Sep 2019, John D. Baker wrote: > Will have to check other diskless clients (amd64, i386, evbmips). No need. Please disregard this thread. Next time, check that machine really IS using DHCP to configure the interface after boot. (It wasn't, but now does and it works properly.) --

Re: dhcpcd ignores "force_hostname=YES" on diskless clients?

2019-09-20 Thread John D. Baker
On Fri, 20 Sep 2019, John D. Baker wrote: > (Before the recent imports of later versions of 'dhcpcd', it failed to > obtain the FQDN on a sparc system and set the hostname as "localhost".) The diskless SPARC system works properly now. Will have to check other diskless clients (amd64, i386,

dhcpcd ignores "force_hostname=YES" on diskless clients?

2019-09-20 Thread John D. Baker
Recently updated to 9.99.12 on a diskless i386 system and when configuring the network, 'dhcpcd' is not setting the hostname at all, but leaving the machine with the boot-time short hostname provided to the kernel's builtin DHCP client. It doesn't even report "Setting hostname..." I've not tried