After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 727407 - hostnamed and /etc/hostname support outside of ifupdown
hostnamed and /etc/hostname support outside of ifupdown
Status: RESOLVED FIXED
Product: NetworkManager
Classification: Platform
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2014-03-31 20:37 UTC by Josh Triplett
Modified: 2016-09-02 00:11 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Josh Triplett 2014-03-31 20:37:09 UTC 
Discussions with the Debian NetworkManager maintainer raised the issue that integration with /etc/hostname currently lives in the ifupdown plugin.  Ideally, with systemd pushing all distros to use /etc/hostname, and providing the hostnamed interface, NetworkManager should use either hostnamed or a fallback to /etc/hostname without needing to use the ifupdown plugin.  This would allow disabling the ifupdown plugin without breaking hostname support.
Comment 1 Dan Winship 2014-04-01 16:11:12 UTC 
ifcfg-rh uses /etc/hostname now too, but yeah, that should be made generic.

There's an outdated branch for using hostnamed instead of writing to /etc/hostname directly in danw/hostnamed.
Comment 2 Thomas Haller 2016-09-02 00:11:45 UTC 
this is fixed a while ago.

Handling of hostname moved from the settings plugin to NMSettings.
Also, hostnamed is supported as one of several options.

There were many changes there, so I am not going to hunt down for a particular BZ which fixed this. However, the functionality is now all in https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/src/settings/nm-settings.c