One key difference might be enabled systemd-resolved by default in Fedora 34, but it is not in RHEL9. I think it should not be related directly. But could it? What does hostnamectl report after installation? What it thinks the hostname is? Would the behaviour change if you disable systemd-resolved and reboot? On 1/21/22 03:35, Thomas Cameron wrote: > On 1/20/22 20:30, Tim via users wrote: >> On Thu, 2022-01-20 at 19:45 -0600, Thomas Cameron wrote: >>> OK, so this is weird. I just kickstarted a F35 VM. When it booted >>> up, its hostname was host156.tc.camerontech.com, as I expected it to >>> be. >>> >>> The /etc/hostname file is blank - it just has a single empty line. >>> >>> After I rebooted that VM, its hostname is set to fedora >> >> It wouldn't be quite so bad if it set its hostname to the one it >> discovered (even though you'd rather it keep on discovering it), but >> changing a hostname is intolerable. >> >> Have you tried making the hostname file immutable? >> > > Thing is, the /etc/hostname file is blank! This is bizarre. I've just > tested with F33, F34, and F35. With F33, the hostname is set to > localhost. With F34 and F35, it's set to fedora. With RHEL 8.5, it's > set to the reverse DNS assigned hostname. With RHEL 9 beta, it's the > reverse DNS assigned hostname. > > This is weirder and weirder. > > Thomas > -- Petr Menšík Software Engineer Red Hat, http://www.redhat.com/ email: pemensik@xxxxxxxxxx PGP: DFCF908DB7C87E8E529925BC4931CA5B6C9FC5CB _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
