On Wed, 2008-10-01 at 16:14 -0700, Howard Chu wrote: > > Message: 5 > > Date: Wed, 1 Oct 2008 23:58:22 +0200 > > From: Alexander Sack<[EMAIL PROTECTED]> > > 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: [email protected] > > Message-ID:<[EMAIL PROTECTED]> > > 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?
It's a matter of persistent storage... when you reboot you'd probably like to have the hostname come back as what you set it before, and that means you have to store the persistent hostname somewhere on the filesystem... But it's just good programming to ensure that when that file changes, updates are recognized, because whatever wrote that file out doesn't _have_ to call sethostname(2). Dan _______________________________________________ NetworkManager-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/networkmanager-list
