Nabble - freebsd-standards

Current problem reports assigned to freebsd-standards@FreeBSD.org

2009-11-23T03:07:04Z

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 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 <time.h>
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
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

47 problems total.

_______________________________________________
freebsd-standards@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-standards
To unsubscribe, send any mail to "freebsd-standards-unsubscribe@..."

Current problem reports assigned to freebsd-standards@FreeBSD.org

2009-11-16T03:07:01Z

Re: timezone: long vs char*

2009-11-09T11:46:43Z

On Mon, Nov 09, 2009 at 11:31:06AM -0500, Garrett Wollman wrote:

> <<On Sun, 08 Nov 2009 19:41:03 -0500, "Joseph S. Atkinson" <jsa.bsd@...> said:
>
> > Hello. I was working on bringing audio/liboggz up to date in ports, but hit a
> > snag. liboggz expects timezone information to be long, which is (I am told) in
> > accordance with SUSv3. FreeBSD is appears to be returning char*.
>
> > I asked about this in #bsdports and was told that it appears that FreeBSD is
> > wrong in this case and should be fixed. I saw no mention of this as a known
> > issue on the standards webpage.
>
> I think the people on "#bsdports" (an IRC channel, I assume) are
> wrong. FreeBSD has never targeted conformance to any version of SUS,
> which memorializes a large number of UNIX System V's historic
> mistakes. We do target conformance to POSIX (IEEE Std. 1003.1-2008 is
> the current version).

Well, these days the SUS and POSIX standards are pretty much the same thing.

>
> In the POSIX specification, the declarations of "timezone" and
> "daylight" in <time.h> are flagged as "XSI", meaning that they are
> part of the X/Open System Interfaces extension, which in turn means
> that they are part of SUS but not POSIX.

If the POSIX specification specifies them they are very much part of POSIX,
but in this particular case an optional part of POSIX.

--
<Insert your favourite quote here.>
Erik Trulsson
ertr1013@...
_______________________________________________
freebsd-standards@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-standards
To unsubscribe, send any mail to "freebsd-standards-unsubscribe@..."

timezone: long vs char*

2009-11-09T08:31:06Z

<<On Sun, 08 Nov 2009 19:41:03 -0500, "Joseph S. Atkinson" <jsa.bsd@...> said:

> Hello. I was working on bringing audio/liboggz up to date in ports, but hit a
> snag. liboggz expects timezone information to be long, which is (I am told) in
> accordance with SUSv3. FreeBSD is appears to be returning char*.

> I asked about this in #bsdports and was told that it appears that FreeBSD is
> wrong in this case and should be fixed. I saw no mention of this as a known
> issue on the standards webpage.

I think the people on "#bsdports" (an IRC channel, I assume) are
wrong. FreeBSD has never targeted conformance to any version of SUS,
which memorializes a large number of UNIX System V's historic
mistakes. We do target conformance to POSIX (IEEE Std. 1003.1-2008 is
the current version).

In the POSIX specification, the declarations of "timezone" and
"daylight" in <time.h> are flagged as "XSI", meaning that they are
part of the X/Open System Interfaces extension, which in turn means
that they are part of SUS but not POSIX.

-GAWollman
_______________________________________________
freebsd-standards@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-standards
To unsubscribe, send any mail to "freebsd-standards-unsubscribe@..."

Current problem reports assigned to freebsd-standards@FreeBSD.org

2009-11-09T03:07:03Z

timezone: long vs char*

2009-11-08T16:41:03Z

Hello. I was working on bringing audio/liboggz up to date in ports, but hit a
snag. liboggz expects timezone information to be long, which is (I am told) in
accordance with SUSv3. FreeBSD is appears to be returning char*.

I asked about this in #bsdports and was told that it appears that FreeBSD is
wrong in this case and should be fixed. I saw no mention of this as a known
issue on the standards webpage.
_______________________________________________
freebsd-standards@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-standards
To unsubscribe, send any mail to "freebsd-standards-unsubscribe@..."

Current problem reports assigned to freebsd-standards@FreeBSD.org

2009-11-02T03:07:03Z

Current problem reports assigned to freebsd-standards@FreeBSD.org

2009-10-26T04:07:08Z

Re: junk/139946: obrqaczg

2009-10-25T01:37:14Z

Synopsis: obrqaczg

State-Changed-From-To: open->closed
State-Changed-By: linimon
State-Changed-When: Sun Oct 25 08:36:59 UTC 2009
State-Changed-Why:
garbage

http://www.freebsd.org/cgi/query-pr.cgi?pr=139946
_______________________________________________
freebsd-standards@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-standards
To unsubscribe, send any mail to "freebsd-standards-unsubscribe@..."

Re: junk/139942: vmaouctn

2009-10-25T00:53:26Z

Synopsis: vmaouctn

State-Changed-From-To: open->closed
State-Changed-By: linimon
State-Changed-When: Sun Oct 25 07:53:09 UTC 2009
State-Changed-Why:
garbage.

http://www.freebsd.org/cgi/query-pr.cgi?pr=139942
_______________________________________________
freebsd-standards@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-standards
To unsubscribe, send any mail to "freebsd-standards-unsubscribe@..."

standards/139946: obrqaczg

2009-10-25T00:50:50Z

>Number: 139946
>Category: standards
>Synopsis: obrqaczg
>Confidential: no
>Severity: serious
>Priority: high
>Responsible: freebsd-standards
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: maintainer-update
>Submitter-Id: current-users
>Arrival-Date: Sun Oct 25 08:00:12 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator: obrqaczg
>Release: obrqaczg
>Organization:

obrqaczg
>Environment:
obrqaczg
>Description:
[URL=http://ncakfket.com]riwwpxqk[/URL] ffcxcoav http://ebopbxzt.com hzzewfia qspgqgge <a href="http://fumgpndv.com">bonmjovl</a>
>How-To-Repeat:
obrqaczg
>Fix:
obrqaczg

>Release-Note:
>Audit-Trail:
>Unformatted:
_______________________________________________
freebsd-standards@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-standards
To unsubscribe, send any mail to "freebsd-standards-unsubscribe@..."

standards/139942: vmaouctn

2009-10-25T00:49:20Z

>Number: 139942
>Category: standards
>Synopsis: vmaouctn
>Confidential: no
>Severity: critical
>Priority: high
>Responsible: freebsd-standards
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: update
>Submitter-Id: current-users
>Arrival-Date: Sun Oct 25 07:50:01 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator: vmaouctn
>Release: vmaouctn
>Organization:

vmaouctn
>Environment:
vmaouctn
>Description:
drovamqj http://aiuwngyk.com jbxdkvqk othobxsm [URL=http://zybhwnyl.com]oqffmoqk[/URL] <a href="http://xnfwegdf.com">bvqltlii</a>
>How-To-Repeat:
vmaouctn
>Fix:
vmaouctn

>Release-Note:
>Audit-Trail:
>Unformatted:
_______________________________________________
freebsd-standards@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-standards
To unsubscribe, send any mail to "freebsd-standards-unsubscribe@..."

Current problem reports assigned to freebsd-standards@FreeBSD.org

2009-10-19T04:07:02Z

Re: kern/139580: oss overflow

2009-10-14T13:16:48Z

Synopsis: oss overflow

State-Changed-From-To: open->feedback
State-Changed-By: gavin
State-Changed-When: Wed Oct 14 20:12:58 UTC 2009
State-Changed-Why:
To submitter: I'm afraid you'll have to provide more details:
Firstly, I'm guessing this is related to a port you are using?
Can you tell me which port this is? The command
pkg_which `which ossinfo`
should be enough to answer that.

Thanks

Responsible-Changed-From-To: freebsd-standards->gavin
Responsible-Changed-By: gavin
Responsible-Changed-When: Wed Oct 14 20:12:58 UTC 2009
Responsible-Changed-Why:
Track.

http://www.freebsd.org/cgi/query-pr.cgi?pr=139580
_______________________________________________
freebsd-standards@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-standards
To unsubscribe, send any mail to "freebsd-standards-unsubscribe@..."

Re: standards/128546: commit references a PR

2009-10-14T13:10:04Z

The following reply was made to PR standards/128546; it has been noted by GNATS.

From: dfilter@... (dfilter service)
To: bug-followup@...
Cc:
Subject: Re: standards/128546: commit references a PR
Date: Tue, 13 Oct 2009 21:52:05 +0000 (UTC)

Author: jilles
Date: Tue Oct 13 21:51:50 2009
New Revision: 198056
URL: http://svn.freebsd.org/changeset/base/198056

Log:
ls: Make -p not inhibit following symlinks.

According to the man page, when neither -H/-L nor -F/-d/-l are given, -H is
implied. This agrees with POSIX, GNU ls and Solaris ls. This means that -p,
although it is very similar to -F, does not prevent the implicit following
of symlinks.

PR: standards/128546

Modified:
head/bin/ls/ls.c

Modified: head/bin/ls/ls.c
==============================================================================
--- head/bin/ls/ls.c Tue Oct 13 21:28:51 2009 (r198055)
+++ head/bin/ls/ls.c Tue Oct 13 21:51:50 2009 (r198056)
@@ -399,7 +399,7 @@ main(int argc, char *argv[])
* If not -F, -d or -l options, follow any symbolic links listed on
* the command line.
*/
- if (!f_longform && !f_listdir && !f_type)
+ if (!f_longform && !f_listdir && (!f_type || f_slash))
fts_options |= FTS_COMFOLLOW;

/*
_______________________________________________
svn-src-all@... mailing list
http://lists.freebsd.org/mailman/listinfo/svn-src-all
To unsubscribe, send any mail to "svn-src-all-unsubscribe@..."

>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:

_______________________________________________
freebsd-standards@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-standards
To unsubscribe, send any mail to "freebsd-standards-unsubscribe@..."

Re: standards/128546: ls -p does not follow symlinks

2009-10-14T11:29:06Z

Synopsis: ls -p does not follow symlinks

State-Changed-From-To: open->closed
State-Changed-By: jilles
State-Changed-When: Wed Oct 14 18:29:05 UTC 2009
State-Changed-Why:
Committed (r198056).

http://www.freebsd.org/cgi/query-pr.cgi?pr=128546
_______________________________________________
freebsd-standards@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-standards
To unsubscribe, send any mail to "freebsd-standards-unsubscribe@..."

standards/139580: oss overflow

2009-10-13T12:49:45Z

>Number: 139580
>Category: standards
>Synopsis: oss overflow
>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 Oct 13 19:50:01 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator: michael hax
>Release: FreeBSD 8.0-RC1
>Organization:
>Environment:

FreeBSD Vodka.Speed 8.0-RC1-p1 FreeBSD 8.0-RC1-p1 #0 r197783M: Mon Oct 5 16:50:08 UTC 2009 root@...:/usr/obj/usr/src/sys/PHENOMII amd64

>Description:
Oct 12 22:46:28 Vodka kernel: osscore: Overflow 352012200+4184, 351948800
Oct 13 00:25:56 Vodka kernel: osscore: Overflow 1497852000+6052, 1497790464
when playing a mp3 generates an overflow oss...

%ossinfo

Version info: OSS 4.2 (b 2000/200909282111) (0x00040100) BSD
Platform: FreeBSD/amd64 8.0-RC1-p1 FreeBSD 8.0-RC1-p1 #0 r197783M: Mon Oct 5 16:50:08 UTC 2009 root@...:/usr/obj/usr/src/sys/PHENOMII (Vodka.Speed)

Number of audio devices: 9
Number of audio engines: 13
Number of MIDI devices: 0
Number of mixer devices: 1

Device objects
0: oss_hdaudio0 ATI HD Audio interrupts=1771234 (1771234)
HD Audio controller ATI HD Audio
Vendor ID 0x10024383
Subvendor ID 0x10192618
Codec 0: ALC888 (0x10ec0888/0x10192618)

>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
_______________________________________________
freebsd-standards@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-standards
To unsubscribe, send any mail to "freebsd-standards-unsubscribe@..."

Current problem reports assigned to freebsd-standards@FreeBSD.org

2009-10-12T04:07:02Z

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 <time.h>
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
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

48 problems total.

_______________________________________________
freebsd-standards@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-standards
To unsubscribe, send any mail to "freebsd-standards-unsubscribe@..."

Current problem reports assigned to freebsd-standards@FreeBSD.org

2009-10-05T04:07:01Z

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 <time.h>
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
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

48 problems total.

_______________________________________________
freebsd-standards@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-standards
To unsubscribe, send any mail to "freebsd-standards-unsubscribe@..."

Re: bin/25542: sh(1) null char in quoted string

2009-10-04T10:15:43Z

Synopsis: sh(1) null char in quoted string

Responsible-Changed-From-To: freebsd-standards->jilles
Responsible-Changed-By: jilles
Responsible-Changed-When: Sun Oct 4 17:15:40 UTC 2009
Responsible-Changed-Why:
Take.

http://www.freebsd.org/cgi/query-pr.cgi?pr=25542
_______________________________________________
freebsd-standards@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-standards
To unsubscribe, send any mail to "freebsd-standards-unsubscribe@..."

Re: standards/129554: commit references a PR

2009-10-02T02:30:06Z

The following reply was made to PR standards/129554; it has been noted by GNATS.

From: dfilter@... (dfilter service)
To: bug-followup@...
Cc:
Subject: Re: standards/129554: commit references a PR
Date: Tue, 29 Sep 2009 21:29:20 +0000 (UTC)

Author: jilles
Date: Tue Sep 29 21:28:32 2009
New Revision: 197625
URL: http://svn.freebsd.org/changeset/base/197625

Log:
Fix using lp(1) without the new -t option after r194171.

PR: standards/129554
Tested by: Steve Kargl
MFC after: 1 week

Modified:
head/usr.sbin/lpr/lp/lp.sh

Modified: head/usr.sbin/lpr/lp/lp.sh
==============================================================================
--- head/usr.sbin/lpr/lp/lp.sh Tue Sep 29 21:25:59 2009 (r197624)
+++ head/usr.sbin/lpr/lp/lp.sh Tue Sep 29 21:28:32 2009 (r197625)
@@ -70,7 +70,7 @@ do
s) # (silent option)
: ;;
t) # title for banner page
- title="-J${OPTARG}";;
+ title="${OPTARG}";;
*) # (error msg printed by getopts)
exit 2;;
esac
@@ -78,4 +78,4 @@ done

shift $(($OPTIND - 1))

-exec /usr/bin/lpr "-P${dest}" ${symlink} ${ncopies} ${mailafter} "${title}" "$@"
+exec /usr/bin/lpr "-P${dest}" ${symlink} ${ncopies} ${mailafter} ${title:+-J"${title}"} "$@"
_______________________________________________
svn-src-all@... mailing list
http://lists.freebsd.org/mailman/listinfo/svn-src-all
To unsubscribe, send any mail to "svn-src-all-unsubscribe@..."

_______________________________________________
freebsd-standards@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-standards
To unsubscribe, send any mail to "freebsd-standards-unsubscribe@..."

Current problem reports assigned to freebsd-standards@FreeBSD.org

2009-09-28T04:07:04Z

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 <time.h>
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.

_______________________________________________
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

2009-09-23T01:20:11Z

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

2009-09-22T14:40:02Z

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

2009-09-22T14:08:26Z

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

2009-09-22T10:10:04Z

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

2009-09-22T10:05:23Z

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

2009-09-21T15:35:00Z

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@..."

Current problem reports assigned to freebsd-standards@FreeBSD.org

2009-09-21T04:07:05Z

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 <time.h>
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.

_______________________________________________
freebsd-standards@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-standards
To unsubscribe, send any mail to "freebsd-standards-unsubscribe@..."

Re: bin/25542: commit references a PR

2009-09-20T14:50:02Z

The following reply was made to PR bin/25542; it has been noted by GNATS.

From: dfilter@... (dfilter service)
To: bug-followup@...
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@... mailing list
http://lists.freebsd.org/mailman/listinfo/svn-src-all
To unsubscribe, send any mail to "svn-src-all-unsubscribe@..."

_______________________________________________
freebsd-standards@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-standards
To unsubscribe, send any mail to "freebsd-standards-unsubscribe@..."

Current problem reports assigned to freebsd-standards@FreeBSD.org

2009-09-14T04:07:09Z

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 <time.h>
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.

_______________________________________________
freebsd-standards@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-standards
To unsubscribe, send any mail to "freebsd-standards-unsubscribe@..."

Re: standards/138307: posix_memalign has incorrect behaviour if size == 0

2009-09-12T12:10:16Z

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
_______________________________________________
freebsd-standards@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-standards
To unsubscribe, send any mail to "freebsd-standards-unsubscribe@..."

Current problem reports assigned to freebsd-standards@FreeBSD.org

2009-09-07T04:07:08Z

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 <time.h>
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.

_______________________________________________
freebsd-standards@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-standards
To unsubscribe, send any mail to "freebsd-standards-unsubscribe@..."

Re: standards/138549: Re: standards/138307: commit references a PR

2009-09-06T11:41:33Z

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
_______________________________________________
freebsd-standards@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-standards
To unsubscribe, send any mail to "freebsd-standards-unsubscribe@..."

Re: standards/138307: posix_memalign has incorrect behaviour if size == 0

2009-09-03T07:10:06Z

The following reply was made to PR standards/138307; it has been noted by GNATS.

From: Kostik Belousov <kostikbel@...>
To: =?koi8-r?Q?Rafa=EBl_Carr=E9?= <rafael.carre@...>
Cc: bug-followup@...
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);
}

_______________________________________________
freebsd-standards@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-standards
To unsubscribe, send any mail to "freebsd-standards-unsubscribe@..."