standards/137173: `uname -n` incorrect behavior
wollman at csail.mit.edu
Tue Jul 28 20:30:05 UTC 2009
The following reply was made to PR standards/137173; it has been noted by GNATS.
From: Garrett Wollman <wollman at csail.mit.edu>
To: Andy Kosela <akosela at andykosela.com>
Cc: freebsd-gnats-submit at freebsd.org
Subject: Re: standards/137173: `uname -n` incorrect behavior
Date: Tue, 28 Jul 2009 16:29:07 -0400
<<On Tue, 28 Jul 2009 08:40:03 GMT, Andy Kosela <akosela at andykosela.com> said:
> All UNIX systems I got access to prints only hostname without the domain
> information (same as 'hostname -s').
Legacy Unix implementations used the UUCP name, which was completely
unconnected to any other notion of the host's name. Few people use
UUCP any more, and in any case, they are free to set their hostname to
something other than an FQDN if they want.
> On top of that common sense tells me that "node within an
> implementation-defined communications network" is just a node name, and
> not a full domain name information. What you think?
In what way is an FQDN not a node name?
More information about the freebsd-standards