Re: standards/137173: `uname -n` incorrect behavior

View: New views

6 Messages — Rating Filter: Alert me

	Re: standards/137173: `uname -n` incorrect behavior by jilles-2 :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Synopsis: `uname -n` incorrect behavior State-Changed-From-To: open->closed State-Changed-By: jilles State-Changed-When: Mon Sep 21 22:34:59 UTC 2009 State-Changed-Why: Submitter confirms this can be closed. No suitable change has been proposed. http://www.freebsd.org/cgi/query-pr.cgi?pr=137173 _______________________________________________ freebsd-standards@... mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-standards To unsubscribe, send any mail to "freebsd-standards-unsubscribe@..."
	Re: standards/137173: `uname -n` incorrect behavior by Oliver Fromme :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Just for the record: The claim that Solaris doesn't print the FQDN is incorrect. Solaris prints whatever the admin has configured in /etc/nodename. If the admin has configured the FQDN, "uname -n" will print the FQDN. AFAIK it is the same for HP-UX. So, FreeBSD really behaves the same as Solaris and HP-UX: If you configure the hostname to be the FQDN, "uname -n" will print it, just like the "hostname" command. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "Unix gives you just enough rope to hang yourself -- and then a couple of more feet, just to be sure." -- Eric Allman _______________________________________________ freebsd-standards@... mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-standards To unsubscribe, send any mail to "freebsd-standards-unsubscribe@..."
	Re: standards/137173: `uname -n` incorrect behavior by Oliver Fromme :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message The following reply was made to PR standards/137173; it has been noted by GNATS. From: Oliver Fromme <olli@...> To: freebsd-standards@..., bug-followup@..., akosela@..., jilles@... Cc: Subject: Re: standards/137173: `uname -n` incorrect behavior Date: Tue, 22 Sep 2009 19:05:23 +0200 (CEST) Just for the record: The claim that Solaris doesn't print the FQDN is incorrect. Solaris prints whatever the admin has configured in /etc/nodename. If the admin has configured the FQDN, "uname -n" will print the FQDN. AFAIK it is the same for HP-UX. So, FreeBSD really behaves the same as Solaris and HP-UX: If you configure the hostname to be the FQDN, "uname -n" will print it, just like the "hostname" command. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "Unix gives you just enough rope to hang yourself -- and then a couple of more feet, just to be sure." -- Eric Allman _______________________________________________ freebsd-standards@... mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-standards To unsubscribe, send any mail to "freebsd-standards-unsubscribe@..."
	Re: standards/137173: `uname -n` incorrect behavior by Andy Kosela-5 :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Oliver Fromme <olli@...> wrote: > Just for the record: > The claim that Solaris doesn't print the FQDN is incorrect. > Solaris prints whatever the admin has configured in /etc/nodename. > If the admin has configured the FQDN, "uname -n" will print the FQDN. > AFAIK it is the same for HP-UX. > > So, FreeBSD really behaves the same as Solaris and HP-UX: > If you configure the hostname to be the FQDN, "uname -n" will print it, > just like the "hostname" command. FYI # uname -a HP-UX vital15 B.11.23 U ia64 1058748580 unlimited-user license # uname -n vital15 # hostname vital15.testdrive.hp.com so NODENAME != HOSTNAME The startup variable NODENAME is the UUCP name which is returned by uname -n, while the HOSTNAME variable sets the networking (ARPA, NFS, etc) name, which can be 64 chars long (see /usr/include/sys/param.h for MAXHOSTNAMELEN). HOSTNAME can be much longer than 8 characters BUT only if you define an 8-character or less NODENAME in the /etc/rc.config.d/netconf file. --Andy _______________________________________________ freebsd-standards@... mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-standards To unsubscribe, send any mail to "freebsd-standards-unsubscribe@..."
	Re: standards/137173: `uname -n` incorrect behavior by Andy Kosela-5 :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message The following reply was made to PR standards/137173; it has been noted by GNATS. From: Andy Kosela <akosela@...> To: olli@..., jilles@..., freebsd-standards@..., bug-followup@... Cc: Subject: Re: standards/137173: `uname -n` incorrect behavior Date: Tue, 22 Sep 2009 23:08:26 +0200 Oliver Fromme <olli@...> wrote: > Just for the record: > The claim that Solaris doesn't print the FQDN is incorrect. > Solaris prints whatever the admin has configured in /etc/nodename. > If the admin has configured the FQDN, "uname -n" will print the FQDN. > AFAIK it is the same for HP-UX. > > So, FreeBSD really behaves the same as Solaris and HP-UX: > If you configure the hostname to be the FQDN, "uname -n" will print it, > just like the "hostname" command. FYI # uname -a HP-UX vital15 B.11.23 U ia64 1058748580 unlimited-user license # uname -n vital15 # hostname vital15.testdrive.hp.com so NODENAME != HOSTNAME The startup variable NODENAME is the UUCP name which is returned by uname -n, while the HOSTNAME variable sets the networking (ARPA, NFS, etc) name, which can be 64 chars long (see /usr/include/sys/param.h for MAXHOSTNAMELEN). HOSTNAME can be much longer than 8 characters BUT only if you define an 8-character or less NODENAME in the /etc/rc.config.d/netconf file. --Andy _______________________________________________ freebsd-standards@... mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-standards To unsubscribe, send any mail to "freebsd-standards-unsubscribe@..."
	Re: standards/137173: `uname -n` incorrect behavior by Oliver Fromme :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Andy Kosela wrote: > Oliver Fromme wrote: > > > Just for the record: > > The claim that Solaris doesn't print the FQDN is incorrect. > > Solaris prints whatever the admin has configured in /etc/nodename. > > If the admin has configured the FQDN, "uname -n" will print the FQDN. > > AFAIK it is the same for HP-UX. > > > > So, FreeBSD really behaves the same as Solaris and HP-UX: > > If you configure the hostname to be the FQDN, "uname -n" will print it, > > just like the "hostname" command. > > FYI > > # uname -a > HP-UX vital15 B.11.23 U ia64 1058748580 unlimited-user license > # uname -n > vital15 > # hostname > vital15.testdrive.hp.com > > so NODENAME != HOSTNAME > > The startup variable NODENAME is the UUCP name which is returned by > uname -n, while the HOSTNAME variable sets the networking (ARPA, NFS, > etc) name, which can be 64 chars long (see /usr/include/sys/param.h for > MAXHOSTNAMELEN). HOSTNAME can be much longer than 8 characters BUT only > if you define an 8-character or less NODENAME in the > /etc/rc.config.d/netconf file. Thanks for pointing that out. So Solaris is more modern than HP-UX. ;-) Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things." -- Doug Gwyn _______________________________________________ freebsd-standards@... mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-standards To unsubscribe, send any mail to "freebsd-standards-unsubscribe@..."

	Re: standards/137173: `uname -n` incorrect behavior by jilles-2 :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Synopsis: `uname -n` incorrect behavior State-Changed-From-To: open->closed State-Changed-By: jilles State-Changed-When: Mon Sep 21 22:34:59 UTC 2009 State-Changed-Why: Submitter confirms this can be closed. No suitable change has been proposed. http://www.freebsd.org/cgi/query-pr.cgi?pr=137173 _______________________________________________ freebsd-standards@... mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-standards To unsubscribe, send any mail to "freebsd-standards-unsubscribe@..."
	Re: standards/137173: `uname -n` incorrect behavior by Oliver Fromme :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Just for the record: The claim that Solaris doesn't print the FQDN is incorrect. Solaris prints whatever the admin has configured in /etc/nodename. If the admin has configured the FQDN, "uname -n" will print the FQDN. AFAIK it is the same for HP-UX. So, FreeBSD really behaves the same as Solaris and HP-UX: If you configure the hostname to be the FQDN, "uname -n" will print it, just like the "hostname" command. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "Unix gives you just enough rope to hang yourself -- and then a couple of more feet, just to be sure." -- Eric Allman _______________________________________________ freebsd-standards@... mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-standards To unsubscribe, send any mail to "freebsd-standards-unsubscribe@..."
	Re: standards/137173: `uname -n` incorrect behavior by Oliver Fromme :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message The following reply was made to PR standards/137173; it has been noted by GNATS. From: Oliver Fromme <olli@...> To: freebsd-standards@..., bug-followup@..., akosela@..., jilles@... Cc: Subject: Re: standards/137173: `uname -n` incorrect behavior Date: Tue, 22 Sep 2009 19:05:23 +0200 (CEST) Just for the record: The claim that Solaris doesn't print the FQDN is incorrect. Solaris prints whatever the admin has configured in /etc/nodename. If the admin has configured the FQDN, "uname -n" will print the FQDN. AFAIK it is the same for HP-UX. So, FreeBSD really behaves the same as Solaris and HP-UX: If you configure the hostname to be the FQDN, "uname -n" will print it, just like the "hostname" command. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "Unix gives you just enough rope to hang yourself -- and then a couple of more feet, just to be sure." -- Eric Allman _______________________________________________ freebsd-standards@... mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-standards To unsubscribe, send any mail to "freebsd-standards-unsubscribe@..."
	Re: standards/137173: `uname -n` incorrect behavior by Andy Kosela-5 :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Oliver Fromme <olli@...> wrote: > Just for the record: > The claim that Solaris doesn't print the FQDN is incorrect. > Solaris prints whatever the admin has configured in /etc/nodename. > If the admin has configured the FQDN, "uname -n" will print the FQDN. > AFAIK it is the same for HP-UX. > > So, FreeBSD really behaves the same as Solaris and HP-UX: > If you configure the hostname to be the FQDN, "uname -n" will print it, > just like the "hostname" command. FYI # uname -a HP-UX vital15 B.11.23 U ia64 1058748580 unlimited-user license # uname -n vital15 # hostname vital15.testdrive.hp.com so NODENAME != HOSTNAME The startup variable NODENAME is the UUCP name which is returned by uname -n, while the HOSTNAME variable sets the networking (ARPA, NFS, etc) name, which can be 64 chars long (see /usr/include/sys/param.h for MAXHOSTNAMELEN). HOSTNAME can be much longer than 8 characters BUT only if you define an 8-character or less NODENAME in the /etc/rc.config.d/netconf file. --Andy _______________________________________________ freebsd-standards@... mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-standards To unsubscribe, send any mail to "freebsd-standards-unsubscribe@..."
	Re: standards/137173: `uname -n` incorrect behavior by Andy Kosela-5 :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message The following reply was made to PR standards/137173; it has been noted by GNATS. From: Andy Kosela <akosela@...> To: olli@..., jilles@..., freebsd-standards@..., bug-followup@... Cc: Subject: Re: standards/137173: `uname -n` incorrect behavior Date: Tue, 22 Sep 2009 23:08:26 +0200 Oliver Fromme <olli@...> wrote: > Just for the record: > The claim that Solaris doesn't print the FQDN is incorrect. > Solaris prints whatever the admin has configured in /etc/nodename. > If the admin has configured the FQDN, "uname -n" will print the FQDN. > AFAIK it is the same for HP-UX. > > So, FreeBSD really behaves the same as Solaris and HP-UX: > If you configure the hostname to be the FQDN, "uname -n" will print it, > just like the "hostname" command. FYI # uname -a HP-UX vital15 B.11.23 U ia64 1058748580 unlimited-user license # uname -n vital15 # hostname vital15.testdrive.hp.com so NODENAME != HOSTNAME The startup variable NODENAME is the UUCP name which is returned by uname -n, while the HOSTNAME variable sets the networking (ARPA, NFS, etc) name, which can be 64 chars long (see /usr/include/sys/param.h for MAXHOSTNAMELEN). HOSTNAME can be much longer than 8 characters BUT only if you define an 8-character or less NODENAME in the /etc/rc.config.d/netconf file. --Andy _______________________________________________ freebsd-standards@... mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-standards To unsubscribe, send any mail to "freebsd-standards-unsubscribe@..."
	Re: standards/137173: `uname -n` incorrect behavior by Oliver Fromme :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Andy Kosela wrote: > Oliver Fromme wrote: > > > Just for the record: > > The claim that Solaris doesn't print the FQDN is incorrect. > > Solaris prints whatever the admin has configured in /etc/nodename. > > If the admin has configured the FQDN, "uname -n" will print the FQDN. > > AFAIK it is the same for HP-UX. > > > > So, FreeBSD really behaves the same as Solaris and HP-UX: > > If you configure the hostname to be the FQDN, "uname -n" will print it, > > just like the "hostname" command. > > FYI > > # uname -a > HP-UX vital15 B.11.23 U ia64 1058748580 unlimited-user license > # uname -n > vital15 > # hostname > vital15.testdrive.hp.com > > so NODENAME != HOSTNAME > > The startup variable NODENAME is the UUCP name which is returned by > uname -n, while the HOSTNAME variable sets the networking (ARPA, NFS, > etc) name, which can be 64 chars long (see /usr/include/sys/param.h for > MAXHOSTNAMELEN). HOSTNAME can be much longer than 8 characters BUT only > if you define an 8-character or less NODENAME in the > /etc/rc.config.d/netconf file. Thanks for pointing that out. So Solaris is more modern than HP-UX. ;-) Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things." -- Doug Gwyn _______________________________________________ freebsd-standards@... mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-standards To unsubscribe, send any mail to "freebsd-standards-unsubscribe@..."