It doesn't hurt performance, though it might hurt privacy[1] overriding it is still possible, and it helps with branding recognition. [1]: information leak which we tried to avoid in Avahi in: https://bugzilla.redhat.com/show_bug.cgi?id=1105647
I'm very much in favour. "fedora" is way better than "localhost". I'd even go a step further, and allow the hostname to be customized during installation. Changing the hostname is one of the things that I always do post-installation. Ideally, a suitable default would be provided, with a possibility for the user to override it. "fedora" could be this default.
FWIW, I have similar bugs filed against avahi and anaconda: https://bugzilla.redhat.com/show_bug.cgi?id=1392924 https://bugzilla.redhat.com/show_bug.cgi?id=1392926
(In reply to Zbigniew Jędrzejewski-Szmek from comment #1) > I'd even go a step further, and allow the hostname to be customized during installation. Huh? This option has been there for a while.
Related to https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/HRHAKG53Y2G3SFKFXX2FPO3FOUR7NJGA/ Maybe the default hostname could be set to something unique as requested in that thread, but the default **pretty** hostname could be set to just "Fedora" ?
Maybe. I'm not a big fan of the "pretty hostname" concept myself. We don't display the hostname in places that are visible to the newbie user, just in terminal prompts, logins, logs, and such, and in those places we might just as well use the real hostname.
Oh, I didn't notice that this is assigned to systemd. Systemd does not determine the hostname. I think the hostname should be changed during installation, and systemd should just duly display what is configured. So imho the job belongs to anaconda.
(In reply to Jan Synacek from comment #3) > Huh? This option has been there for a while. So it does. I wasn't aware. > Change default advertised hostname to "fedora" Bastien, what exactly are you asking for from systemd?
He obviously wants to end up with gazillion hosts that all pretty identify themselves as "Fedora" while everyone else wants to have uniq id to every hosts and machine or device and arguably always want to make the user set this when he installs his OS or even go as far as default all hostname hotspots and what not entries pretty or otherwise to something like the machine-id so they can be reliably differentiated from each other when they log or share something on the network. I guess the installer and a plymouth splash screen and the logo in something like details in Gnome is not good enough and obvious branding these days encase users somehow missed that fact when they DOWNLOADED AND INSTALLED FEDORA o_O
> He obviously wants to end up with gazillion hosts that all pretty identify themselves as "Fedora" Me too ;) > everyone else wants to have uniq id to every hosts and machine That too. Hence currently the proposal being hashed out on the mailing list to use "Fedora-<random-stuff>" as the default hostname upon installation. In case it wasn't clear, my question is: is there anything to change in systemd to support this?
(In reply to Zbigniew Jędrzejewski-Szmek from comment #7) > (In reply to Jan Synacek from comment #3) > > Huh? This option has been there for a while. > So it does. I wasn't aware. > > > Change default advertised hostname to "fedora" > > Bastien, what exactly are you asking for from systemd? That the default fallback hostname be changed from "localhost" to "fedora" on Fedora systems: https://github.com/systemd/systemd/blob/master/src/hostname/hostnamed.c#L284 (In reply to Jóhann B. Guðmundsson from comment #8) > He obviously wants to end up with gazillion hosts that all pretty identify > themselves as "Fedora" Jóhann, when you don't know, just don't say anything. It will save us all time.
https://github.com/systemd/systemd/pull/5175
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle. Changing version to '26'.
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
Fixed in https://github.com/systemd/systemd/pull/5175
Reopening, because the fix was never actually implemented in Fedora.
https://src.fedoraproject.org/rpms/systemd/pull-request/28 should fix it.
Though this will only change the systemd default. A change in anaconda would be needed to make this effective. My suggestion would be simply not create /etc/hostname from anaconda if the user didn't specify a hostname.
Built in rawhide.