https://bugzilla.novell.com/show_bug.cgi?id=440810
User kmachalkova@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=440810#c2
Katarina Machalkova
When trying to change the hostname, it is not changed in all places that rely on definition of the hostname for system purposes. Changing it in YaST Network Services succeeds in changing /etc/HOSTNAME and the 127.0.0.2 entry in /etc/hosts, but not for the first field of the 127.0.0.1 entry,
That is indeed a bug, YaST network configuration module should substitute every instance of the old hostname in /etc/hosts by the new one ...
nor for the 'hostname' line in /etc/NetworkManager/nm-system-settings.conf.
.. but this is intentional. NetworkManager uses its own settings system and YaST will not interfere with it.
b. NetworkManager could just refer to /etc/HOSTNAME, which exists precisely for the purpose of defining just that!
Afaik, NetworkManager already reads system-wide /etc/HOSTNAME, it must be fixed in some of the recent betas
YaST Network Settings would still need to save its 'hostname' setting to the first hostname field of the 127.0.0.1 entry in /etc/hosts.
If you ever happened to see '127.0.0.1 localhost linux.site localhost.localdomain' line in /etc/hosts, it's been added there by NetworkManager. Here I don't know if NM still does it in this form, or if it just uses a real hostname instead of 'linux.site', neverthless, modifying 127.0.0.1 entry was never done by YaST. YaST uses 127.0.0.2 line for remembering hostname, as a workaround for some broken apps :( -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.