Date: Tue, 13 Feb 2007 10:08:29 +0300 From: Yar Tikhiy <yar@comp.chem.msu.su> To: "Daniel O'Connor" <doconnor@gsoft.com.au> Cc: Ceri Davies <ceri@submonkey.net>, cvs-src@freebsd.org, Brooks Davis <brooks@freebsd.org>, src-committers@freebsd.org, cvs-all@freebsd.org Subject: Re: cvs commit: src/etc/rc.d hostname Message-ID: <20070213070829.GE58225@comp.chem.msu.su> In-Reply-To: <200702131558.34590.doconnor@gsoft.com.au> References: <200702101313.l1ADDX8m056868@repoman.freebsd.org> <20070212034438.GA42410@lor.one-eyed-alien.net> <20070212120908.GN13808@comp.chem.msu.su> <200702131558.34590.doconnor@gsoft.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Feb 13, 2007 at 03:58:19PM +1030, Daniel O'Connor wrote: > On Monday 12 February 2007 22:39, Yar Tikhiy wrote: > > I have no idea how many Unix hosts allow their hostname to be set > > via DHCP. I prefer to think that a Unix host is like a good ship: > > it never changes its name while furrowing the network seas. A DHCP > > assigned hostname better fits crippled hosts such as diskless > > stations etc. > > My laptop's name changes depending which network it's on. (ie the domain > part). > > It would be nice if it would try to get the name specified in hostname via > DHCP (for dynamic DNS setups), if that fails check what the DHCP server gave > it, failing that do a reverse lookup on the IP. > > Unfortunately it's not easy to do that because of how /etc/rc.d/* and dhclient > interact.. Furthermore X (for one) gets really annoyed when you change > hostname.. Yeah, there should be some apps that don't like hostname changing. I'm afraid little can be done about them. Either you make the hostname permanent (e.g., by telling dhclient not to change the hostname) and break the network policy, or you let the hostname change and break the apps. -- Yar
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070213070829.GE58225>