Date: Wed, 29 Jul 2009 16:00:19 GMT From: Garrett Wollman <wollman@csail.mit.edu> To: freebsd-standards@FreeBSD.org Subject: Re: standards/137173: `uname -n` incorrect behavior Message-ID: <200907291600.n6TG0J12044489@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR standards/137173; it has been noted by GNATS. From: Garrett Wollman <wollman@csail.mit.edu> To: Andy Kosela <akosela@andykosela.com> Cc: freebsd-gnats-submit@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@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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200907291600.n6TG0J12044489>