Date: Mon, 27 Jul 2009 13:26:24 GMT From: Andy Kosela <akosela@andykosela.com> To: freebsd-gnats-submit@FreeBSD.org Subject: standards/137173: `uname -n` incorrect behavior Message-ID: <200907271326.n6RDQOWF044267@www.freebsd.org> Resent-Message-ID: <200907271330.n6RDU2wA033489@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 137173
>Category: standards
>Synopsis: `uname -n` incorrect behavior
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-standards
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: change-request
>Submitter-Id: current-users
>Arrival-Date: Mon Jul 27 13:30:01 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator: Andy Kosela
>Release:
>Organization:
>Environment:
FreeBSD plotinus.lan 7.2-RELEASE FreeBSD 7.2-RELEASE #0: Sat Jun 6 15:21:16 CEST 2009 akosela@plotinus.lan:/usr/obj/usr/src/sys/GENERIC amd64
>Description:
Currently `uname -n` prints the name of the system (FQDN) to standard output. I believe this is incorrect behavior according to IEEE Std 1003.1.
-n
Write the name of this node within an implementation-defined communications network.
On the other hand though HP-UX, AIX, Solaris, Linux seems to conform to IEEE Std 1003.1 in this aspect and print only the hostname (without the domain name). This feature of uname(1) is important for some of us who rely on `uname -n` in PS1.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200907271326.n6RDQOWF044267>