From kostikbel at gmail.com Thu Sep 3 14:10:07 2009 From: kostikbel at gmail.com (Kostik Belousov) Date: Thu Sep 3 14:10:13 2009 Subject: standards/138307: posix_memalign has incorrect behaviour if size == 0 Message-ID: <200909031410.n83EA64m020590@freefall.freebsd.org> The following reply was made to PR standards/138307; it has been noted by GNATS. From: Kostik Belousov To: =?koi8-r?Q?Rafa=EBl_Carr=E9?= Cc: bug-followup@freebsd.org Subject: Re: standards/138307: posix_memalign has incorrect behaviour if size == 0 Date: Thu, 3 Sep 2009 16:44:38 +0300 The following patch should help. diff --git a/lib/libc/stdlib/malloc.c b/lib/libc/stdlib/malloc.c index 270d641..b56b003 100644 --- a/lib/libc/stdlib/malloc.c +++ b/lib/libc/stdlib/malloc.c @@ -5320,6 +5320,15 @@ posix_memalign(void **memptr, size_t alignment, size_t size) goto RETURN; } + if (size == 0) { + if (opt_sysv == false) + size = 1; + else { + result = NULL; + ret = 0; + goto RETURN; + } + } result = ipalloc(alignment, size); } From linimon at FreeBSD.org Sun Sep 6 18:41:33 2009 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Sun Sep 6 18:41:39 2009 Subject: standards/138549: Re: standards/138307: commit references a PR Message-ID: <200909061841.n86IfX1J080943@freefall.freebsd.org> Old Synopsis: Re: standard/138307: commit references a PR New Synopsis: Re: standards/138307: commit references a PR State-Changed-From-To: open->closed State-Changed-By: linimon State-Changed-When: Sun Sep 6 18:40:52 UTC 2009 State-Changed-Why: Misfiled followup to standards/138549; content migrated. Responsible-Changed-From-To: gnats-admin->freebsd-standards Responsible-Changed-By: linimon Responsible-Changed-When: Sun Sep 6 18:40:52 UTC 2009 Responsible-Changed-Why: http://www.freebsd.org/cgi/query-pr.cgi?pr=138549 From bugmaster at FreeBSD.org Mon Sep 7 11:07:09 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Sep 7 11:09:45 2009 Subject: Current problem reports assigned to freebsd-standards@FreeBSD.org Message-ID: <200909071107.n87B78fu010394@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o stand/138307 standards posix_memalign has incorrect behaviour if size == 0 o stand/137173 standards `uname -n` incorrect behavior o stand/135307 standards Boot Loader problem on Acer Aspire 5735 o stand/130067 standards Wrong numeric limits in system headers? o stand/129524 standards FreeBSD 7.0 isnt detecting my hardrives with raid5 o stand/129196 standards Inconsistent errno in strtol() o stand/128546 standards ls -p does not follow symlinks o bin/125855 standards sh(1) allows for multiline, non-escaped control struct o stand/124860 standards flockfile(3) doesn't work when the memory has been exh o stand/123688 standards POSIX standard changes in unistd.h and grp.h o stand/121921 standards [patch] Add leap second support to at(1), atrun(8) o stand/121568 standards [patch] ln(1): wrong "ln -s" behaviour o stand/120947 standards xsm ignores system.xsm and .xsmstartup o stand/116826 standards [patch] sh support for POSIX character classes o stand/116477 standards rm(1): rm behaves unexpectedly when using -r and relat o bin/116413 standards incorrect getconf(1) handling of unsigned constants gi o stand/116081 standards make does not work with the directive sinclude p stand/107561 standards [libc] [patch] [request] Missing SUS function tcgetsid o stand/104743 standards [headers] [patch] Wrong values for _POSIX_ minimal lim o stand/100017 standards [Patch] Add fuser(1) functionality to fstat(1) o stand/96236 standards [patch] [posix] sed(1) incorrectly describes a functio o stand/96016 standards [headers] clock_getres et al should be in o stand/94729 standards [libc] fcntl() throws undocumented ENOTTY o kern/93705 standards [headers] [patch] ENODATA and EGREGIOUS (for glibc com o stand/92362 standards [headers] [patch] Missing SIGPOLL in kernel headers a stand/86484 standards [patch] mkfifo(1) uses wrong permissions o stand/83845 standards [libm] [patch] add log2() and log2f() support for libm o stand/82654 standards C99 long double math functions are missing o stand/81287 standards [patch] fingerd(8) might send a line not ending in CRL a stand/80293 standards sysconf() does not support well-defined unistd values o stand/79056 standards [feature request] [atch] regex(3) regression tests o stand/70813 standards [patch] ls(1) not Posix compliant o stand/66357 standards make POSIX conformance problem ('sh -e' & '+' command- s kern/64875 standards [libc] [patch] [request] add a system call: fdatasync( s stand/62858 standards malloc(0) not C99 compliant o stand/56476 standards cd9660 unicode support simple hack o stand/54839 standards [pcvt] pcvt deficits o stand/54833 standards [pcvt] more pcvt deficits o stand/54410 standards one-true-awk not POSIX compliant (no extended REs) o stand/46119 standards Priority problems for SCHED_OTHER using pthreads o stand/44425 standards getcwd() succeeds even if current dir has perm 000. p stand/41576 standards POSIX compliance of ln(1) o stand/39256 standards snprintf/vsnprintf aren't POSIX-conformant for strings s stand/36076 standards Implementation of POSIX fuser command o kern/27835 standards [libc] execve() doesn't conform to execve(2) spec in s a docs/26003 standards getgroups(2) lists NGROUPS_MAX but not syslimits.h o bin/25542 standards sh(1) null char in quoted string s stand/24590 standards timezone function not compatible witn Single Unix Spec o bin/24390 standards ln(1) Replacing old dir-symlinks when using /bin/ln o stand/21519 standards sys/dir.h should be deprecated some more s bin/14925 standards getsubopt isn't poisonous enough 51 problems total. From kib at FreeBSD.org Sat Sep 12 19:10:17 2009 From: kib at FreeBSD.org (kib@FreeBSD.org) Date: Sat Sep 12 19:10:24 2009 Subject: standards/138307: posix_memalign has incorrect behaviour if size == 0 Message-ID: <200909121910.n8CJAGtd040950@freefall.freebsd.org> Synopsis: posix_memalign has incorrect behaviour if size == 0 State-Changed-From-To: open->closed State-Changed-By: kib State-Changed-When: Sat Sep 12 19:09:29 UTC 2009 State-Changed-Why: Fix is in RELENG_8. http://www.freebsd.org/cgi/query-pr.cgi?pr=138307 From bugmaster at FreeBSD.org Mon Sep 14 11:07:09 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Sep 14 11:09:37 2009 Subject: Current problem reports assigned to freebsd-standards@FreeBSD.org Message-ID: <200909141107.n8EB79f9072495@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o stand/137173 standards `uname -n` incorrect behavior o stand/135307 standards Boot Loader problem on Acer Aspire 5735 o stand/130067 standards Wrong numeric limits in system headers? o stand/129524 standards FreeBSD 7.0 isnt detecting my hardrives with raid5 o stand/129196 standards Inconsistent errno in strtol() o stand/128546 standards ls -p does not follow symlinks o bin/125855 standards sh(1) allows for multiline, non-escaped control struct o stand/124860 standards flockfile(3) doesn't work when the memory has been exh o stand/123688 standards POSIX standard changes in unistd.h and grp.h o stand/121921 standards [patch] Add leap second support to at(1), atrun(8) o stand/121568 standards [patch] ln(1): wrong "ln -s" behaviour o stand/120947 standards xsm ignores system.xsm and .xsmstartup o stand/116826 standards [patch] sh support for POSIX character classes o stand/116477 standards rm(1): rm behaves unexpectedly when using -r and relat o bin/116413 standards incorrect getconf(1) handling of unsigned constants gi o stand/116081 standards make does not work with the directive sinclude p stand/107561 standards [libc] [patch] [request] Missing SUS function tcgetsid o stand/104743 standards [headers] [patch] Wrong values for _POSIX_ minimal lim o stand/100017 standards [Patch] Add fuser(1) functionality to fstat(1) o stand/96236 standards [patch] [posix] sed(1) incorrectly describes a functio o stand/96016 standards [headers] clock_getres et al should be in o stand/94729 standards [libc] fcntl() throws undocumented ENOTTY o kern/93705 standards [headers] [patch] ENODATA and EGREGIOUS (for glibc com o stand/92362 standards [headers] [patch] Missing SIGPOLL in kernel headers a stand/86484 standards [patch] mkfifo(1) uses wrong permissions o stand/83845 standards [libm] [patch] add log2() and log2f() support for libm o stand/82654 standards C99 long double math functions are missing o stand/81287 standards [patch] fingerd(8) might send a line not ending in CRL a stand/80293 standards sysconf() does not support well-defined unistd values o stand/79056 standards [feature request] [atch] regex(3) regression tests o stand/70813 standards [patch] ls(1) not Posix compliant o stand/66357 standards make POSIX conformance problem ('sh -e' & '+' command- s kern/64875 standards [libc] [patch] [request] add a system call: fdatasync( s stand/62858 standards malloc(0) not C99 compliant o stand/56476 standards cd9660 unicode support simple hack o stand/54839 standards [pcvt] pcvt deficits o stand/54833 standards [pcvt] more pcvt deficits o stand/54410 standards one-true-awk not POSIX compliant (no extended REs) o stand/46119 standards Priority problems for SCHED_OTHER using pthreads o stand/44425 standards getcwd() succeeds even if current dir has perm 000. p stand/41576 standards POSIX compliance of ln(1) o stand/39256 standards snprintf/vsnprintf aren't POSIX-conformant for strings s stand/36076 standards Implementation of POSIX fuser command o kern/27835 standards [libc] execve() doesn't conform to execve(2) spec in s a docs/26003 standards getgroups(2) lists NGROUPS_MAX but not syslimits.h o bin/25542 standards sh(1) null char in quoted string s stand/24590 standards timezone function not compatible witn Single Unix Spec o bin/24390 standards ln(1) Replacing old dir-symlinks when using /bin/ln o stand/21519 standards sys/dir.h should be deprecated some more s bin/14925 standards getsubopt isn't poisonous enough 50 problems total. From dfilter at FreeBSD.ORG Sun Sep 20 21:50:03 2009 From: dfilter at FreeBSD.ORG (dfilter service) Date: Sun Sep 20 21:50:09 2009 Subject: bin/25542: commit references a PR Message-ID: <200909202150.n8KLo2C6093030@freefall.freebsd.org> The following reply was made to PR bin/25542; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: bin/25542: commit references a PR Date: Sun, 20 Sep 2009 21:42:52 +0000 (UTC) Author: jilles Date: Sun Sep 20 21:42:38 2009 New Revision: 197371 URL: http://svn.freebsd.org/changeset/base/197371 Log: Mention that NUL characters are not allowed in sh(1) input. I do not consider this a bug because POSIX permits it and argument strings and environment variables cannot contain '\0' anyway. PR: bin/25542 MFC after: 2 weeks Modified: head/bin/sh/sh.1 Modified: head/bin/sh/sh.1 ============================================================================== --- head/bin/sh/sh.1 Sun Sep 20 19:32:10 2009 (r197370) +++ head/bin/sh/sh.1 Sun Sep 20 21:42:38 2009 (r197371) @@ -375,6 +375,10 @@ introduces a comment if used at the begi The word starting with .Ql # and the rest of the line are ignored. +.Pp +.Tn ASCII +.Dv NUL +characters (character code 0) are not allowed in shell input. .Ss Quoting Quoting is used to remove the special meaning of certain characters or words to the shell, such as operators, whitespace, keywords, _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscribe@freebsd.org" From bugmaster at FreeBSD.org Mon Sep 21 11:07:06 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Sep 21 11:09:34 2009 Subject: Current problem reports assigned to freebsd-standards@FreeBSD.org Message-ID: <200909211107.n8LB75Lf030435@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o stand/137173 standards `uname -n` incorrect behavior o stand/135307 standards Boot Loader problem on Acer Aspire 5735 o stand/130067 standards Wrong numeric limits in system headers? o stand/129524 standards FreeBSD 7.0 isnt detecting my hardrives with raid5 o stand/129196 standards Inconsistent errno in strtol() o stand/128546 standards ls -p does not follow symlinks o bin/125855 standards sh(1) allows for multiline, non-escaped control struct o stand/124860 standards flockfile(3) doesn't work when the memory has been exh o stand/123688 standards POSIX standard changes in unistd.h and grp.h o stand/121921 standards [patch] Add leap second support to at(1), atrun(8) o stand/121568 standards [patch] ln(1): wrong "ln -s" behaviour o stand/120947 standards xsm ignores system.xsm and .xsmstartup o stand/116826 standards [patch] sh support for POSIX character classes o stand/116477 standards rm(1): rm behaves unexpectedly when using -r and relat o bin/116413 standards incorrect getconf(1) handling of unsigned constants gi o stand/116081 standards make does not work with the directive sinclude p stand/107561 standards [libc] [patch] [request] Missing SUS function tcgetsid o stand/104743 standards [headers] [patch] Wrong values for _POSIX_ minimal lim o stand/100017 standards [Patch] Add fuser(1) functionality to fstat(1) o stand/96236 standards [patch] [posix] sed(1) incorrectly describes a functio o stand/96016 standards [headers] clock_getres et al should be in o stand/94729 standards [libc] fcntl() throws undocumented ENOTTY o kern/93705 standards [headers] [patch] ENODATA and EGREGIOUS (for glibc com o stand/92362 standards [headers] [patch] Missing SIGPOLL in kernel headers a stand/86484 standards [patch] mkfifo(1) uses wrong permissions o stand/83845 standards [libm] [patch] add log2() and log2f() support for libm o stand/82654 standards C99 long double math functions are missing o stand/81287 standards [patch] fingerd(8) might send a line not ending in CRL a stand/80293 standards sysconf() does not support well-defined unistd values o stand/79056 standards [feature request] [atch] regex(3) regression tests o stand/70813 standards [patch] ls(1) not Posix compliant o stand/66357 standards make POSIX conformance problem ('sh -e' & '+' command- s kern/64875 standards [libc] [patch] [request] add a system call: fdatasync( s stand/62858 standards malloc(0) not C99 compliant o stand/56476 standards cd9660 unicode support simple hack o stand/54839 standards [pcvt] pcvt deficits o stand/54833 standards [pcvt] more pcvt deficits o stand/54410 standards one-true-awk not POSIX compliant (no extended REs) o stand/46119 standards Priority problems for SCHED_OTHER using pthreads o stand/44425 standards getcwd() succeeds even if current dir has perm 000. p stand/41576 standards POSIX compliance of ln(1) o stand/39256 standards snprintf/vsnprintf aren't POSIX-conformant for strings s stand/36076 standards Implementation of POSIX fuser command o kern/27835 standards [libc] execve() doesn't conform to execve(2) spec in s a docs/26003 standards getgroups(2) lists NGROUPS_MAX but not syslimits.h o bin/25542 standards sh(1) null char in quoted string s stand/24590 standards timezone function not compatible witn Single Unix Spec o bin/24390 standards ln(1) Replacing old dir-symlinks when using /bin/ln o stand/21519 standards sys/dir.h should be deprecated some more s bin/14925 standards getsubopt isn't poisonous enough 50 problems total. From jilles at FreeBSD.org Mon Sep 21 22:35:00 2009 From: jilles at FreeBSD.org (jilles@FreeBSD.org) Date: Mon Sep 21 22:35:07 2009 Subject: standards/137173: `uname -n` incorrect behavior Message-ID: <200909212235.n8LMZ09k040882@freefall.freebsd.org> 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 From olli at lurza.secnetix.de Tue Sep 22 17:05:46 2009 From: olli at lurza.secnetix.de (Oliver Fromme) Date: Tue Sep 22 17:05:52 2009 Subject: standards/137173: `uname -n` incorrect behavior In-Reply-To: <200909212235.n8LMZ09k040882@freefall.freebsd.org> Message-ID: <200909221705.n8MH5NEh064549@lurza.secnetix.de> 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 From olli at lurza.secnetix.de Tue Sep 22 17:10:05 2009 From: olli at lurza.secnetix.de (Oliver Fromme) Date: Tue Sep 22 17:10:21 2009 Subject: standards/137173: `uname -n` incorrect behavior Message-ID: <200909221710.n8MHA480096696@freefall.freebsd.org> The following reply was made to PR standards/137173; it has been noted by GNATS. From: Oliver Fromme To: freebsd-standards@FreeBSD.ORG, bug-followup@FreeBSD.ORG, akosela@andykosela.com, jilles@FreeBSD.ORG 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 From akosela at andykosela.com Tue Sep 22 21:34:42 2009 From: akosela at andykosela.com (Andy Kosela) Date: Tue Sep 22 21:35:14 2009 Subject: standards/137173: `uname -n` incorrect behavior In-Reply-To: <200909221705.n8MH5NEh064549@lurza.secnetix.de> References: <200909221705.n8MH5NEh064549@lurza.secnetix.de> Message-ID: <4ab93cca.vZr1+IV6M72iTd1N%akosela@andykosela.com> 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. --Andy From akosela at andykosela.com Tue Sep 22 21:40:03 2009 From: akosela at andykosela.com (Andy Kosela) Date: Tue Sep 22 21:40:09 2009 Subject: standards/137173: `uname -n` incorrect behavior Message-ID: <200909222140.n8MLe2N0067973@freefall.freebsd.org> The following reply was made to PR standards/137173; it has been noted by GNATS. From: Andy Kosela To: olli@lurza.secnetix.de, jilles@FreeBSD.ORG, freebsd-standards@FreeBSD.ORG, bug-followup@FreeBSD.ORG Cc: Subject: Re: standards/137173: `uname -n` incorrect behavior Date: Tue, 22 Sep 2009 23:08:26 +0200 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. --Andy From olli at lurza.secnetix.de Wed Sep 23 08:20:32 2009 From: olli at lurza.secnetix.de (Oliver Fromme) Date: Wed Sep 23 08:20:38 2009 Subject: standards/137173: `uname -n` incorrect behavior In-Reply-To: <4ab93cca.vZr1+IV6M72iTd1N%akosela@andykosela.com> Message-ID: <200909230820.n8N8KBDC002448@lurza.secnetix.de> 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 From bugmaster at FreeBSD.org Mon Sep 28 11:07:05 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Sep 28 11:09:29 2009 Subject: Current problem reports assigned to freebsd-standards@FreeBSD.org Message-ID: <200909281107.n8SB74Wu064174@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o stand/135307 standards Boot Loader problem on Acer Aspire 5735 o stand/130067 standards Wrong numeric limits in system headers? o stand/129524 standards FreeBSD 7.0 isnt detecting my hardrives with raid5 o stand/129196 standards Inconsistent errno in strtol() o stand/128546 standards ls -p does not follow symlinks o bin/125855 standards sh(1) allows for multiline, non-escaped control struct o stand/124860 standards flockfile(3) doesn't work when the memory has been exh o stand/123688 standards POSIX standard changes in unistd.h and grp.h o stand/121921 standards [patch] Add leap second support to at(1), atrun(8) o stand/121568 standards [patch] ln(1): wrong "ln -s" behaviour o stand/120947 standards xsm ignores system.xsm and .xsmstartup o stand/116826 standards [patch] sh support for POSIX character classes o stand/116477 standards rm(1): rm behaves unexpectedly when using -r and relat o bin/116413 standards incorrect getconf(1) handling of unsigned constants gi o stand/116081 standards make does not work with the directive sinclude p stand/107561 standards [libc] [patch] [request] Missing SUS function tcgetsid o stand/104743 standards [headers] [patch] Wrong values for _POSIX_ minimal lim o stand/100017 standards [Patch] Add fuser(1) functionality to fstat(1) o stand/96236 standards [patch] [posix] sed(1) incorrectly describes a functio o stand/96016 standards [headers] clock_getres et al should be in o stand/94729 standards [libc] fcntl() throws undocumented ENOTTY o kern/93705 standards [headers] [patch] ENODATA and EGREGIOUS (for glibc com o stand/92362 standards [headers] [patch] Missing SIGPOLL in kernel headers a stand/86484 standards [patch] mkfifo(1) uses wrong permissions o stand/83845 standards [libm] [patch] add log2() and log2f() support for libm o stand/82654 standards C99 long double math functions are missing o stand/81287 standards [patch] fingerd(8) might send a line not ending in CRL a stand/80293 standards sysconf() does not support well-defined unistd values o stand/79056 standards [feature request] [atch] regex(3) regression tests o stand/70813 standards [patch] ls(1) not Posix compliant o stand/66357 standards make POSIX conformance problem ('sh -e' & '+' command- s kern/64875 standards [libc] [patch] [request] add a system call: fdatasync( s stand/62858 standards malloc(0) not C99 compliant o stand/56476 standards cd9660 unicode support simple hack o stand/54839 standards [pcvt] pcvt deficits o stand/54833 standards [pcvt] more pcvt deficits o stand/54410 standards one-true-awk not POSIX compliant (no extended REs) o stand/46119 standards Priority problems for SCHED_OTHER using pthreads o stand/44425 standards getcwd() succeeds even if current dir has perm 000. p stand/41576 standards POSIX compliance of ln(1) o stand/39256 standards snprintf/vsnprintf aren't POSIX-conformant for strings s stand/36076 standards Implementation of POSIX fuser command o kern/27835 standards [libc] execve() doesn't conform to execve(2) spec in s a docs/26003 standards getgroups(2) lists NGROUPS_MAX but not syslimits.h o bin/25542 standards sh(1) null char in quoted string s stand/24590 standards timezone function not compatible witn Single Unix Spec o bin/24390 standards ln(1) Replacing old dir-symlinks when using /bin/ln o stand/21519 standards sys/dir.h should be deprecated some more s bin/14925 standards getsubopt isn't poisonous enough 49 problems total.