From bugmaster at FreeBSD.org Mon Dec 1 03:07:03 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Dec 1 03:09:19 2008 Subject: Current problem reports assigned to freebsd-standards@FreeBSD.org Message-ID: <200812011107.mB1B73io052699@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/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/119804 standards [timedef] [patch] Invalid (long)date format in pl_PL.I o stand/118047 standards SUGGESTION: /etc/printcap vs mergemaster 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 o kern/114578 standards [libc] wide character printing using swprintf(dst, n, 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 function 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 CR 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/72006 standards floating point formating in non-C locales 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 p stand/55112 standards glob.h, glob_t's gl_pathc should be "size_t", not "int 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 stand/25777 standards [kernel] [patch] atime not updated on exec 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 bugmaster at FreeBSD.org Mon Dec 8 03:07:04 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Dec 8 03:09:10 2008 Subject: Current problem reports assigned to freebsd-standards@FreeBSD.org Message-ID: <200812081107.mB8B73sR014412@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/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/119804 standards [timedef] [patch] Invalid (long)date format in pl_PL.I o stand/118047 standards SUGGESTION: /etc/printcap vs mergemaster 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 o kern/114578 standards [libc] wide character printing using swprintf(dst, n, 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 function 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 CR 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/72006 standards floating point formating in non-C locales 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 p stand/55112 standards glob.h, glob_t's gl_pathc should be "size_t", not "int 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 stand/25777 standards [kernel] [patch] atime not updated on exec 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 xdevaux at xdevaux.fr Tue Dec 9 07:00:11 2008 From: xdevaux at xdevaux.fr (Kevin DeVaux) Date: Tue Dec 9 07:00:21 2008 Subject: standards/129524: FreeBSD 7.0 isnt detecting my hardrives with raid5 Message-ID: <200812091451.mB9Ep7ih076848@www.freebsd.org> >Number: 129524 >Category: standards >Synopsis: FreeBSD 7.0 isnt detecting my hardrives with raid5 >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-standards >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Dec 09 15:00:10 UTC 2008 >Closed-Date: >Last-Modified: >Originator: Kevin DeVaux >Release: 7.0 >Organization: Everest Production >Environment: Freebsd doesnt detect my hardrives with raid5 >Description: ok so here it goes. I am sorry if this is the wrong person to ask for help. I am a dedicated Freebsd user. the thing is I my computer just bought a server a new ibm server zeon processors. and I have 6 hardrives with a array of raid5. each hardrive is one TB. now when I pop the cd in the cdrom its goes through to the setup but when I go to partition the hardrive array freebsd doesnt detect it at all. what should I do please help me. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: From gavin at FreeBSD.org Wed Dec 10 10:20:02 2008 From: gavin at FreeBSD.org (Gavin Atkinson) Date: Wed Dec 10 10:20:14 2008 Subject: standards/129554: lp(1) [patch] Implement -m and -t options Message-ID: <200812101746.mBAHkqoZ051291@buffy.york.ac.uk> >Number: 129554 >Category: standards >Synopsis: lp(1) [patch] Implement -m and -t options >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-standards >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Dec 10 18:20:01 UTC 2008 >Closed-Date: >Last-Modified: >Originator: Gavin Atkinson >Release: FreeBSD 7.0-STABLE amd64 >Organization: >Environment: System: FreeBSD buffy.york.ac.uk 7.0-STABLE FreeBSD 7.0-STABLE #3: Fri Jun 20 09:21:51 UTC 2008 root@buffy.york.ac.uk:/usr/obj/usr/src/sys/GENERIC amd64 >Description: lp(1) doesn't support the -t option, as required by me and POSIX. Implement it. While here, I've implemented the -m option, leaving the -w option as the only one missing for full compliance (although -o and -s are not fully implemented). Note that I have implemented the -t option because I needed it, and not because I necessarily wanted to see this utility closer to compliance. Therefore, I've not updated any reference to compliance in the code or man page (I wouldn't know if they need updating or not) >How-To-Repeat: N/A >Fix: --- lp-t-moptions.diff begins here --- Index: src-head/usr.sbin/lpr/lp/lp.1 =================================================================== RCS file: /home/ncvs/src/usr.sbin/lpr/lp/lp.1,v retrieving revision 1.18 diff -u -r1.18 lp.1 --- src-head/usr.sbin/lpr/lp/lp.1 2 Jul 2004 23:12:46 -0000 1.18 +++ src-head/usr.sbin/lpr/lp/lp.1 10 Dec 2008 17:34:18 -0000 @@ -78,6 +78,8 @@ .Ev PRINTER (with this precedence) are taken as the destination printer. +.It Fl m +Send mail upon completion. .It Fl n Ar num Specify that .Ar num @@ -91,6 +93,9 @@ Not supported, provided only as a compatibility option for .St -susv2 . +.It Fl t Ar title +Set the job title to +.Ar title . .El .Sh ENVIRONMENT As described above, the variables Index: src-head/usr.sbin/lpr/lp/lp.sh =================================================================== RCS file: /home/ncvs/src/usr.sbin/lpr/lp/lp.sh,v retrieving revision 1.7 diff -u -r1.7 lp.sh --- src-head/usr.sbin/lpr/lp/lp.sh 8 Mar 2000 10:02:11 -0000 1.7 +++ src-head/usr.sbin/lpr/lp/lp.sh 10 Dec 2008 17:36:52 -0000 @@ -41,6 +41,8 @@ ncopies="" symlink="-s" +mailafter="" +title="" # Posix says LPDEST gets precedence over PRINTER dest=${LPDEST:-${PRINTER:-lp}} @@ -51,7 +53,7 @@ # XXX We include the -s flag as a dummy. SUSv2 requires it, # although we do not yet emit the affected messages. # -while getopts "cd:n:o:s" option +while getopts "cd:mn:o:st:" option do case $option in @@ -59,12 +61,16 @@ symlink="";; d) # destination dest="${OPTARG}";; + m) # mail after job + mailafter="-m";; n) # number of copies ncopies="-#${OPTARG}";; o) # (printer option) : ;; s) # (silent option) : ;; + t) # title for banner page + title="-J${OPTARG}";; *) # (error msg printed by getopts) exit 2;; esac @@ -72,4 +78,4 @@ shift $(($OPTIND - 1)) -exec /usr/bin/lpr "-P${dest}" ${symlink} ${ncopies} "$@" +exec /usr/bin/lpr "-P${dest}" ${symlink} ${ncopies} ${mailafter} "${title}" "$@" --- lp-t-moptions.diff ends here --- >Release-Note: >Audit-Trail: >Unformatted: From gavin at FreeBSD.org Wed Dec 10 10:58:31 2008 From: gavin at FreeBSD.org (Gavin Atkinson) Date: Wed Dec 10 10:58:38 2008 Subject: standards/129554: lp(1) [patch] Implement -m and -t options In-Reply-To: <200812101820.mBAIK1eG056671@freefall.freebsd.org> References: <200812101820.mBAIK1eG056671@freefall.freebsd.org> Message-ID: <1228933679.47296.14.camel@buffy.york.ac.uk> I should have mentioned that according to http://www.freebsd.org/projects/c99/ adding these options is a work in progress in HEAD, but I can't find any PR or commit that would suggest this is the case. Gavin From gavin at FreeBSD.org Wed Dec 10 11:00:12 2008 From: gavin at FreeBSD.org (Gavin Atkinson) Date: Wed Dec 10 11:00:18 2008 Subject: standards/129554: lp(1) [patch] Implement -m and -t options Message-ID: <200812101900.mBAJ0Bh6075644@freefall.freebsd.org> The following reply was made to PR standards/129554; it has been noted by GNATS. From: Gavin Atkinson To: FreeBSD-gnats-submit@FreeBSD.org, freebsd-standards@FreeBSD.org Cc: Subject: Re: standards/129554: lp(1) [patch] Implement -m and -t options Date: Wed, 10 Dec 2008 18:27:59 +0000 I should have mentioned that according to http://www.freebsd.org/projects/c99/ adding these options is a work in progress in HEAD, but I can't find any PR or commit that would suggest this is the case. Gavin From bugmaster at FreeBSD.org Mon Dec 15 03:07:02 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Dec 15 03:09:17 2008 Subject: Current problem reports assigned to freebsd-standards@FreeBSD.org Message-ID: <200812151107.mBFB7188004487@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/129554 standards lp(1) [patch] Implement -m and -t options o stand/129524 standards FreeBSD 7.0 isnt detecting my hardrives with raid5 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/119804 standards [timedef] [patch] Invalid (long)date format in pl_PL.I o stand/118047 standards SUGGESTION: /etc/printcap vs mergemaster 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 o kern/114578 standards [libc] wide character printing using swprintf(dst, n, 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 function 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 CR 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/72006 standards floating point formating in non-C locales 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 p stand/55112 standards glob.h, glob_t's gl_pathc should be "size_t", not "int 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 stand/25777 standards [kernel] [patch] atime not updated on exec 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 53 problems total. From bugmaster at FreeBSD.org Mon Dec 22 03:06:59 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Dec 22 03:09:16 2008 Subject: Current problem reports assigned to freebsd-standards@FreeBSD.org Message-ID: <200812221106.mBMB6xjd060724@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/129554 standards lp(1) [patch] Implement -m and -t options o stand/129524 standards FreeBSD 7.0 isnt detecting my hardrives with raid5 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/119804 standards [timedef] [patch] Invalid (long)date format in pl_PL.I o stand/118047 standards SUGGESTION: /etc/printcap vs mergemaster 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 o kern/114578 standards [libc] wide character printing using swprintf(dst, n, 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 function 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 CR 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/72006 standards floating point formating in non-C locales 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 p stand/55112 standards glob.h, glob_t's gl_pathc should be "size_t", not "int 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 stand/25777 standards [kernel] [patch] atime not updated on exec 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 53 problems total. From bugmaster at FreeBSD.org Mon Dec 29 03:07:03 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Dec 29 03:09:13 2008 Subject: Current problem reports assigned to freebsd-standards@FreeBSD.org Message-ID: <200812291107.mBTB72s0024592@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/129554 standards lp(1) [patch] Implement -m and -t options o stand/129524 standards FreeBSD 7.0 isnt detecting my hardrives with raid5 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/119804 standards [timedef] [patch] Invalid (long)date format in pl_PL.I o stand/118047 standards SUGGESTION: /etc/printcap vs mergemaster 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 o kern/114578 standards [libc] wide character printing using swprintf(dst, n, 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 function 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 CR 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/72006 standards floating point formating in non-C locales 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 p stand/55112 standards glob.h, glob_t's gl_pathc should be "size_t", not "int 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 stand/25777 standards [kernel] [patch] atime not updated on exec 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 53 problems total. From bruce at cran.org.uk Tue Dec 30 16:10:06 2008 From: bruce at cran.org.uk (Bruce Cran) Date: Tue Dec 30 16:10:20 2008 Subject: standards/62858: malloc(0) not C99 compliant Message-ID: <200812301610.mBUGA3Ph096108@freefall.freebsd.org> The following reply was made to PR standards/62858; it has been noted by GNATS. From: Bruce Cran To: bug-followup@FreeBSD.org,stefan@fafoe.narf.at, phk@freebsd.org Cc: Subject: Re: standards/62858: malloc(0) not C99 compliant Date: Tue, 30 Dec 2008 16:06:21 +0000 It appears that with jemalloc in 7.0 onwards, the behaviour has changed and is now C99 compliant: malloc(0) returns a unique pointer that increments by 2 bytes each time. -- Bruce Cran From v.haisman at sh.cvut.cz Tue Dec 30 22:40:02 2008 From: v.haisman at sh.cvut.cz (Vaclav Haisman) Date: Tue Dec 30 22:40:14 2008 Subject: standards/130067: Wrong numeric limits in system headers? Message-ID: <200812302231.mBUMVUtf092910@www.freebsd.org> >Number: 130067 >Category: standards >Synopsis: Wrong numeric limits in system headers? >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-standards >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Dec 30 22:40:01 UTC 2008 >Closed-Date: >Last-Modified: >Originator: Vaclav Haisman >Release: 6.3 >Organization: SU SH >Environment: FreeBSD shell.sh.cvut.cz 6.3-PRERELEASE FreeBSD 6.3-PRERELEASE #0: Fri Jan 18 17:04:16 CET 2008 root@shell.sh.cvut.cz:/usr/obj/usr/src/sys/SHELL-SMP i386 >Description: There seems to be a problem with definition of long double limits on FreeBSD i386/6.x. shell::wilx:~/packed_vector> echo | g++ -dD -E - | sort | grep LDBL_MAX #define __LDBL_MAX_10_EXP__ 4932 #define __LDBL_MAX_EXP__ 16384 #define __LDBL_MAX__ 1.1897314953572316e+4932L shell::wilx:~/packed_vector> fgrep -rn LDBL_MAX /usr/include [...] /usr/include/machine/float.h:75:#define LDBL_MAX_EXP 16384 /usr/include/machine/float.h:76:#define LDBL_MAX 1.1897314953572317650E+4932L /usr/include/machine/float.h:77:#define LDBL_MAX_10_EXP 4932 /usr/include/float.h:75:#define LDBL_MAX_EXP 16384 /usr/include/float.h:76:#define LDBL_MAX 1.1897314953572317650E+4932L /usr/include/float.h:77:#define LDBL_MAX_10_EXP 4932 Notice the difference in definition of LDBL_MAX, the values in system headers are tiny bit larger than that defined by GCC itself. machine/float.h:76:#define LDBL_MAX 1.1897314953572317650E+4932L float.h:76:#define LDBL_MAX 1.1897314953572317650E+4932L GCC: __LDBL_MAX__ 1.1897314953572316e+4932L A simple test shows the following: shell::wilx:~/tmp> cat >longdouble.cxx #include #include #include int main () { typedef std::numeric_limits limits; std::cout << "max: " << limits::max () << "\n"; std::cout << "__LDBL_MAX__: " << __LDBL_MAX__ << "\n"; std::cout << "LDBL_MAX: " << LDBL_MAX << "\n"; } shell::wilx:~/tmp> g++ -o longdouble longdouble.cxx shell::wilx:~/tmp> ./longdouble max: 1.18973e+4932 __LDBL_MAX__: 1.18973e+4932 LDBL_MAX: inf This is on 6.3/i386. 7.1/AMD64 does not print inf for LDBL_MAX. I think this is a bug in 6.x headers or in GCC 3.4.x that it uses. LDBL_MAX should never result in "inf". >How-To-Repeat: #include #include #include int main () { typedef std::numeric_limits limits; std::cout << "max: " << limits::max () << "\n"; std::cout << "__LDBL_MAX__: " << __LDBL_MAX__ << "\n"; std::cout << "LDBL_MAX: " << LDBL_MAX << "\n"; } >Fix: >Release-Note: >Audit-Trail: >Unformatted: From brde at optusnet.com.au Wed Dec 31 13:09:01 2008 From: brde at optusnet.com.au (Bruce Evans) Date: Wed Dec 31 13:09:07 2008 Subject: standards/130067: Wrong numeric limits in system headers? In-Reply-To: <200812302231.mBUMVUtf092910@www.freebsd.org> References: <200812302231.mBUMVUtf092910@www.freebsd.org> Message-ID: <20081231215445.S3923@delplex.bde.org> On Tue, 30 Dec 2008, Vaclav Haisman wrote: > There seems to be a problem with definition of long double limits on FreeBSD i386/6.x. > > shell::wilx:~/packed_vector> echo | g++ -dD -E - | sort | grep LDBL_MAX > #define __LDBL_MAX_10_EXP__ 4932 > #define __LDBL_MAX_EXP__ 16384 > #define __LDBL_MAX__ 1.1897314953572316e+4932L > > shell::wilx:~/packed_vector> fgrep -rn LDBL_MAX /usr/include > [...] > /usr/include/machine/float.h:75:#define LDBL_MAX_EXP 16384 > /usr/include/machine/float.h:76:#define LDBL_MAX 1.1897314953572317650E+4932L > /usr/include/machine/float.h:77:#define LDBL_MAX_10_EXP 4932 > /usr/include/float.h:75:#define LDBL_MAX_EXP 16384 > /usr/include/float.h:76:#define LDBL_MAX 1.1897314953572317650E+4932L > /usr/include/float.h:77:#define LDBL_MAX_10_EXP 4932 > > Notice the difference in definition of LDBL_MAX, the values in system > headers are tiny bit larger than that defined by GCC itself. > ... > machine/float.h:76:#define LDBL_MAX 1.1897314953572317650E+4932L > float.h:76:#define LDBL_MAX 1.1897314953572317650E+4932L > GCC: __LDBL_MAX__ 1.1897314953572316e+4932L This has never worked. However, since gcc became aware of the limited precision of long doubles under FreeBSD a few years ago, it shouldn't be as broken as it is. Gcc defines __LDBL_MAX__ to have the correct value (1-2^-53)*2^1024 (rounded to 17 digits, which is enough for the actual precision of 53 bits), while FreeBSD defines LDBL_MAX as (1-2^-64)*2^1024 (rounded to 20 digits, which is perhaps not quite enough for the non-actual precision of 64 bits (either this 20 or DECIMAL_DIG's value of 21 is dubious). The wrong value in FreeBSD may have worked accidentally a few years ago, but now hit has no chance of working: - a few years ago: gcc didn't know about FreeBSD's limited precision, so it evaluated the constant in 64-bit precision and got precisely (1-2^-64)*2^1024 (only the decimal constant is imprecise). Static initialization to this value preserved the value. Actual use of the value caused it to be rounded to 53 bits. I think that still made it Infinity in most cases. - now: gcc evaluates it in 53-bit precision and gets Infinity for it consistently. Many other long double constants in FreeBSD's have never worked, and are much further from neing correct, but are fixed in gcc: >From gcc4.2 -E -dM: % #define __LDBL_MAX__ 1.1897314953572316e+4932L % #define __LDBL_MAX_EXP__ 16384 % #define __LDBL_HAS_INFINITY__ 1 % #define __LDBL_MIN__ 3.3621031431120935e-4932L % #define __LDBL_HAS_QUIET_NAN__ 1 % #define __LDBL_HAS_DENORM__ 1 % #define __LDBL_EPSILON__ 2.2204460492503131e-16L % #define __LDBL_DIG__ 15 % #define __LDBL_MANT_DIG__ 53 % #define __LDBL_MIN_EXP__ (-16381) % #define __LDBL_MAX_10_EXP__ 4932 % #define __LDBL_DENORM_MIN__ 7.4653686412953080e-4948L % #define __LDBL_MIN_10_EXP__ (-4931) >From float.h: % #define LDBL_MANT_DIG 64 Wrong; should be 53. All the other errors are derived from this (see the definitions of FLT_* for the derivations -- p must be 53 but is 64). % #define LDBL_EPSILON 1.0842021724855044340E-19L Wrong: too small by a factor of 2^13. % #define LDBL_DIG 18 Wrong: unnecessarily large (fairly harmless). % #define LDBL_MIN_EXP (-16381) Correct. % #define LDBL_MIN 3.3621031431120935063E-4932L Correct (just has more precision than needed for rounding to 53 bits). % #define LDBL_MIN_10_EXP (-4931) % #define LDBL_MAX_EXP 16384 Correct. % #define LDBL_MAX 1.1897314953572317650E+4932L Wrong: see above. % #define LDBL_MAX_10_EXP 4932 Correct. Bruce From brde at optusnet.com.au Wed Dec 31 13:10:03 2008 From: brde at optusnet.com.au (Bruce Evans) Date: Wed Dec 31 13:10:09 2008 Subject: standards/130067: Wrong numeric limits in system headers? Message-ID: <200812311310.mBVDA21N004096@freefall.freebsd.org> The following reply was made to PR standards/130067; it has been noted by GNATS. From: Bruce Evans To: Vaclav Haisman Cc: freebsd-gnats-submit@FreeBSD.org, freebsd-standards@FreeBSD.org, imp@FreeBSD.org Subject: Re: standards/130067: Wrong numeric limits in system headers? Date: Wed, 31 Dec 2008 22:26:22 +1100 (EST) On Tue, 30 Dec 2008, Vaclav Haisman wrote: > There seems to be a problem with definition of long double limits on FreeBSD i386/6.x. > > shell::wilx:~/packed_vector> echo | g++ -dD -E - | sort | grep LDBL_MAX > #define __LDBL_MAX_10_EXP__ 4932 > #define __LDBL_MAX_EXP__ 16384 > #define __LDBL_MAX__ 1.1897314953572316e+4932L > > shell::wilx:~/packed_vector> fgrep -rn LDBL_MAX /usr/include > [...] > /usr/include/machine/float.h:75:#define LDBL_MAX_EXP 16384 > /usr/include/machine/float.h:76:#define LDBL_MAX 1.1897314953572317650E+4932L > /usr/include/machine/float.h:77:#define LDBL_MAX_10_EXP 4932 > /usr/include/float.h:75:#define LDBL_MAX_EXP 16384 > /usr/include/float.h:76:#define LDBL_MAX 1.1897314953572317650E+4932L > /usr/include/float.h:77:#define LDBL_MAX_10_EXP 4932 > > Notice the difference in definition of LDBL_MAX, the values in system > headers are tiny bit larger than that defined by GCC itself. > ... > machine/float.h:76:#define LDBL_MAX 1.1897314953572317650E+4932L > float.h:76:#define LDBL_MAX 1.1897314953572317650E+4932L > GCC: __LDBL_MAX__ 1.1897314953572316e+4932L This has never worked. However, since gcc became aware of the limited precision of long doubles under FreeBSD a few years ago, it shouldn't be as broken as it is. Gcc defines __LDBL_MAX__ to have the correct value (1-2^-53)*2^1024 (rounded to 17 digits, which is enough for the actual precision of 53 bits), while FreeBSD defines LDBL_MAX as (1-2^-64)*2^1024 (rounded to 20 digits, which is perhaps not quite enough for the non-actual precision of 64 bits (either this 20 or DECIMAL_DIG's value of 21 is dubious). The wrong value in FreeBSD may have worked accidentally a few years ago, but now hit has no chance of working: - a few years ago: gcc didn't know about FreeBSD's limited precision, so it evaluated the constant in 64-bit precision and got precisely (1-2^-64)*2^1024 (only the decimal constant is imprecise). Static initialization to this value preserved the value. Actual use of the value caused it to be rounded to 53 bits. I think that still made it Infinity in most cases. - now: gcc evaluates it in 53-bit precision and gets Infinity for it consistently. Many other long double constants in FreeBSD's have never worked, and are much further from neing correct, but are fixed in gcc: From gcc4.2 -E -dM: % #define __LDBL_MAX__ 1.1897314953572316e+4932L % #define __LDBL_MAX_EXP__ 16384 % #define __LDBL_HAS_INFINITY__ 1 % #define __LDBL_MIN__ 3.3621031431120935e-4932L % #define __LDBL_HAS_QUIET_NAN__ 1 % #define __LDBL_HAS_DENORM__ 1 % #define __LDBL_EPSILON__ 2.2204460492503131e-16L % #define __LDBL_DIG__ 15 % #define __LDBL_MANT_DIG__ 53 % #define __LDBL_MIN_EXP__ (-16381) % #define __LDBL_MAX_10_EXP__ 4932 % #define __LDBL_DENORM_MIN__ 7.4653686412953080e-4948L % #define __LDBL_MIN_10_EXP__ (-4931) From float.h: % #define LDBL_MANT_DIG 64 Wrong; should be 53. All the other errors are derived from this (see the definitions of FLT_* for the derivations -- p must be 53 but is 64). % #define LDBL_EPSILON 1.0842021724855044340E-19L Wrong: too small by a factor of 2^13. % #define LDBL_DIG 18 Wrong: unnecessarily large (fairly harmless). % #define LDBL_MIN_EXP (-16381) Correct. % #define LDBL_MIN 3.3621031431120935063E-4932L Correct (just has more precision than needed for rounding to 53 bits). % #define LDBL_MIN_10_EXP (-4931) % #define LDBL_MAX_EXP 16384 Correct. % #define LDBL_MAX 1.1897314953572317650E+4932L Wrong: see above. % #define LDBL_MAX_10_EXP 4932 Correct. Bruce