Current problem reports assigned to freebsd-standards@FreeBSD.org
bugmaster at FreeBSD.org
Mon Sep 8 02:22:28 UTC 2008
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 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 <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 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
50 problems total.
Bugs can be in one of several states:
o - open
A problem report has been submitted, no sanity checking performed.
a - analyzed
The problem is understood and a solution is being sought.
f - feedback
Further work requires additional information from the
originator or the community - possibly confirmation of
the effectiveness of a proposed solution.
p - patched
A patch has been committed, but some issues (MFC and / or
confirmation from originator) are still open.
r - repocopy
The resolution of the problem report is dependent on
a repocopy operation within the CVS repository which
is awaiting completion.
s - suspended
The problem is not being worked on, due to lack of information
or resources. This is a prime candidate
for somebody who is looking for a project to do.
If the problem cannot be solved at all,
it will be closed, rather than suspended.
c - closed
A problem report is closed when any changes have been integrated,
documented, and tested -- or when fixing the problem is abandoned.
More information about the freebsd-standards