Re: NetworkManager-list Digest, Vol 49, Issue 2

[Alexander Sack <asac jwsdot com>]

On Wed, Oct 01, 2008 at 04:14:33PM -0700, Howard Chu wrote:
>> Message: 5
>> Date: Wed, 1 Oct 2008 23:58:22 +0200
>> From: Alexander Sack<asac jwsdot com>
>> Subject: [PATCH] hostname support for ifupdown plugin + allow
>> 	read-only	hostname system provider + move nm_inotify_helper to plugin
>> 	independent place (system-settings/src/)
>> To: networkmanager-list gnome org
>> Message-ID:<20081001215822 GC26713 jwsdot com>
>> Content-Type: text/plain; charset="us-ascii"
>>
>> Implement system hostname support for debian/ubuntu
>>
>> Fix "only system-setting plugins with NM_SYSTEM_CONFIG_INTERFACE_CAP_MODIFY_HOSTNAME
>> are considered a valid hostname provider"
>>
>> Make nm-inotify-helper from ifcfg-fedora plugin usable
>> for other plugins too
>
> Is any of that really necessary? Any tool that rewrites /etc/hostname is 
> also going to already call sethostname(); shouldn't you only need to call 
> gethostname() to get NM in sync? Why go thru the hassle of opening and 
> reading a file and calling sethostname() to tell the kernel what it 
> already knows?

Hmm ...

there is nothing on debian that enforces that sethostname and
/etc/hostname stay in sync.

Also tools that dont rewrite /etc/hostname include NM itself and
things like "vi /etc/hostname" or echo newhostname > /etc/hostname.

So the next step is probably to add write support for /etc/hostname to
the ifupdown plugin.

 - Alexander