dhcpcd-discuss

On 22/04/20 9:45 am, Roy Marples wrote:
> force_hostname is a bad idea though.
> During the arch install you probably clicked "ok" to a default hostname.
> Check this:
> https://wiki.archlinux.org/index.php/Network_configuration#Set_the_hostname

Don't believe I am.   I'm not setting hostname anywhere other than via
dhcp.  Looking at the logs the hostname is "archlinux" from boot all the
way until dhcpcd-run-hooks changes it (or doesn't if force_hostname
isn't set).


-- Reboot --
Apr 22 10:05:51 archlinux kernel: Linux version 5.4.2-arch1-1
(linux@archlinux) (gcc version 9.2.0 (GCC)
) #1 SMP PREEMPT Thu, 05 Dec 2019 12:29:40 +0000
Apr 22 10:05:51 archlinux kernel: Command line:
BOOT_IMAGE=/vmlinuz-linux root=UUID=4adb8e93-c50c-4931-8
515-db479ee5939f ro quiet
Apr 22 10:05:51 archlinux kernel: KERNEL supported cpus:
    [...]
Apr 22 10:05:58 archlinux dhcpcd-run-hooks[555]: eth0: Setting hostname:
tmp0.home.vuw.ac.nz
Apr 22 10:05:58 tmp0.home.vuw.ac.nz dhcpcd[557]: eth0: soliciting an
IPv6 router


This used to work for me without setting force_hostname up until
sometime in 2017 and then Arch changed something (presumably set
'archlinux' as the default in the kernel).

cheers
mark