On Mon, May 07, 2007 at 06:58:28PM -0400, Douglas Allan Tutty wrote: > On Mon, May 07, 2007 at 03:39:07PM -0700, Andrew Sackville-West wrote: > > On Mon, May 07, 2007 at 05:12:20PM -0400, Douglas Allan Tutty wrote: > > > On Mon, May 07, 2007 at 09:03:49PM +0200, Nyizsnyik Ferenc wrote: > > > > On Mon, 7 May 2007 12:33:21 -0400 > > > > Douglas Allan Tutty <[EMAIL PROTECTED]> wrote: > > > > > /etc/hosts: > > > > > > > > > > 127.0.0.1 localhost > > > > 127.0.0.1 localhost localhost.localdomain > > > > > > > > should solve the problem of the FQDN. > > > > > > > > > 192.168.1.1 titan > > > > > > It does not. uname -n still shows 'titan'. > > > > > > > what about /etc/hostname, requires a reboot, i think. > > > > Looking at man 1 hostname, it looks like /etc/hostname is just the short > hostname. The FQDN comes from /etc/hosts.
yeah, I was only responding to the 'uname -n' part above... unless i misunderstand. I thought you were saying that changing /etc/hosts doesn't change the output of 'uname -n' and I was responding that /etc/hostname should. But, I clearly don't know what's going on in this thread so ignore me ;) > > The question isn't "how do I set a domain name" (unless it goes > somewhere in addition to hosts) but rather, should I? > > I've had one response from someone who does. Is there anyone who > _doesn't_? huh. interesting. A
signature.asc
Description: Digital signature
