standards/137173: `uname -n` incorrect behavior

[Garrett Wollman]

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: Wed, 29 Jul 2009 11:52:34 -0400

 <<On Wed, 29 Jul 2009 09:32:53 +0200, Andy Kosela <akosela at andykosela.com> said:
 
 > information.  Is out there some standard defining it and explaining how
 > nodename (UUCP) convention should be applied to hostname (ARPA, NFS)
 > convention?
 
 No, that's why the POSIX specification leaves it completely
 implementation-defined.
 
 You have to remember that this value originally came from a "struct
 utsname" which had fixed-length (eight?-byte) fields, and the name was
 compiled into the kernel.  (Hence UUCP names like "ihnp4", "mhuxu",
 and so on.)
 
 -GAWollman