FreeBSD C99 & POSIX Conformance Project

diff --git a/en/projects/c99/index.sgml b/en/projects/c99/index.sgml index 3b57e148af..4f56181771 100644 --- a/en/projects/c99/index.sgml +++ b/en/projects/c99/index.sgml @@ -1,1998 +1,1998 @@ - + %includes; %developers; "> "> "> "> "> assert(3)"> printf(3)"> scanf(3)"> strtod(3)"> printf(9)"> freebsd-standards-subscribe@FreeBSD.org"> freebsd-standards@FreeBSD.org"> ]> FreeBSD C99 & POSIX Conformance Project

The FreeBSD C99 & POSIX Conformance Project aims to implement all requirements of the ISO 9899:1999 (C99) and IEEE 1003.1-2001 (POSIX) standards. In cases where aspects of these standards cannot be followed, those aspects will be documented in the c99(7) or posix(7) manuals. It is also an aim of this project to implement regression tests to ensure correctness whenever possible.

All of the initial development takes place in the 5-CURRENT branch and most changes are merged into the 4-STABLE branch. Since this is a rather large project and is being done on a volunteer basis, there is no set schedule.

The project is always looking for additional contributors. If you wish to participate, the best way to find out what is happening is to subscribe to the freebsd-standards mailing list. If you are working on a specific task relating to the project, you should contact mike@FreeBSD.org with a description of the task so that your task can be listed below.

ISO/IEC 9899:1999, also known as C99, is available for purchase in electronic form from the American National Standards Institute, or available from the International Organization for Standardization store in electronic and paper form.
IEEE Std 1003.1-2001 - The free (registration required), online version of POSIX.1-2001 and SUSv3 standard.
Are you Ready For C99? - This article discusses some of the new features in C99.
Most discussion relating to this project takes place on the &a.standards; mailing list. To subscribe to the list, send a message to &a.standards.subscribe;.
Jens Schweikhardt maintains a list with the current status of POSIX Utility Conformance in FreeBSD.

Task	Responsible	Last Updated	Status
Task	Responsible	Last Updated	5.x	4.x
Documentation
Create stdint(7) manual to document <stdint.h>.	&a.mike;	15 September 2002	&status.done;	&status.n-a;
Document standards conformity level of the API.		26 March 2002	&status.wip;	&status.blank;
Document thread safety and async-cancel safety.		26 March 2002	&status.wip;	&status.blank;
Create c99(7) and posix(7) manuals.		11 December 2001	&status.new;	&status.blank;
Document in posix(7) that the batch job management utilities are available in the port net/generic-nqs.		11 December 2001	&status.new;	&status.blank;
Document flockfile(3), ftrylockfile(3), funlockfile(3).		17 September 2002	&status.new;	&status.blank;
Document new _SC options in sysconf(3) (PR: 20528).		25 November 2002	&status.new;	&status.blank;

Task	Responsible	Last Updated	Status
Task	Responsible	Last Updated	5.0	4.x
Functions and System Calls
Add __func__ reporting to &man.assert.3;.	&a.asmodai;	27 October 2001	&status.done;	&status.n-a;
Implement imaxabs(), imaxdiv(), llabs(), lldiv().	&a.mike;	14 November 2001	&status.done;	&status.n-a;
Implement atoll(), strtoimax(), strtoumax().	&a.fenner;	27 November 2001	&status.done;	&status.n-a;
Implement new length modifiers (hh, j, t, z) and new flag (') in &man.printf.3;.	&a.wollman;, &a.fenner;	30 November 2001	&status.done;	&status.n-a;
Implement strerror_r().	&a.wes;	20 December 2001	&status.done;	&status.done;
Implement tgamma() based on Lite1's gamma().	&a.bde;	27 March 2002	&status.done;	&status.n-a;
Implement new length modifiers (hh, j, ll, t, z) in &man.scanf.3;.	&a.fenner;	20 April 2002	&status.done;	&status.n-a;
Add WCONTINUED to waitpid(2).	&a.mike;	1 June 2002	&status.done;	&status.n-a;
Implement new conversion specifiers (%j and %n) in &man.printf.9;.	&a.dd; &a.des;	3 June 2002	&status.done;	&status.n-a;
Implement fstatvfs() and statvfs() (trivial).	&a.wollman;	14 June 2002	&status.done;	&status.n-a;
Implement fmtmsg().	&a.mike;	8 August 2002	&status.done;	&status.n-a;
Implement ulimit().	&a.mkm;	8 August 2002	&status.done;	&status.n-a;
Implement C99's _Exit().	&a.wollman;	11 September 2002	&status.done;	&status.n-a;
Add required options for POSIX.1-2001 to glob(). (partial MFC)	&a.mikeh;	20 September 2002	&status.done;	&status.done;
Update sysconf(3) for POSIX.1-2001.	&a.wollman;	18 September 2002	&status.done;	&status.n-a;
Restore insque(), lsearch(), remque() from libcompat.	&a.robert;	16 November 2002	&status.done;	&status.n-a;
Implement fpclassify().	&a.das;, &a.mike;	8 February 2003	&status.done;	&status.n-a;
Implement isfinite(), isinf(), isnan(), isnormal().	&a.das;	17 February 2003	&status.done;	&status.n-a;
Implement isgreater(), isgreaterequal(), isless(), islessequal(), islessgreater().	&a.das;	17 February 2003	&status.done;	&status.n-a;
Implement signbit().	&a.mike;	17 February 2003	&status.done;	&status.n-a;
Implement sockatmark().	&a.fenner;	23 December 2002	&status.done;	&status.new;
Implement wordexp() and wordfree().	&a.tjr;	31 December 2002	&status.done;	&status.new;
Implement grantpt(), posix_openpt(), ptsname(), unlockpt().	&a.ryany;	4 February 2003	&status.done;	&status.new;
Implement getgrgid_r(), getgrnam_r().	&a.wes;	20 December 2001	&status.wip;	&status.blank;
Implement new functions that appear in <complex.h>.	&a.markm;	6 February 2002	&status.wip;	&status.blank;
Implement waitid(2).	&a.mike;	27 May 2002	&status.wip;	&status.blank;
Add floating-point support for the (') modifier in &man.printf.3;	&a.phantom;	13 June 2002	&status.wip;	&status.blank;
Add new conversion specifiers (%a and %A) to &man.printf.3;.	&a.mkm;	13 June 2002	&status.wip;	&status.blank;
Implement the utmpx family of functions.	&a.robert;	28 June 2002	&status.wip;	&status.blank;
Implement ftw() and nftw() in terms of fts().	&a.mkm;	16 August 2002	&status.wip;	&status.blank;
Add restrict type-qualifier to functions that require it.	&a.robert;	16 August 2002	&status.wip;	&status.blank;
Implement iconv(), iconv_close(), iconv_open().	&a.tjr;	8 October 2002	&status.wip;	&status.blank;
Implement getpwnam_r(), getpwuid_r().	&a.leimy2k;	8 February 2003	&status.wip;	&status.blank;
Transition to vendor (Netlib) source for strtod.c.	&a.das;	27 February 2003	&status.wip;	&status.blank;
Import Netlib's gdtoa (strtof, strtold, etc.).	&a.das;	27 February 2003	&status.wip;	&status.blank;
Implement new functions that appear in <fenv.h>.	&a.fenner;	14 November 2001	&status.new;	&status.blank;
Make non thread-safe functions thread-safe.		22 October 2001	&status.new;	&status.blank;
Make functions async-cancel safe.		22 October 2001	&status.new;	&status.blank;
Implement C99 macros fpclassify(), isfinite(), isinf(), isnan(), isnormal(), signbit().		13 April 2002	&status.new;	&status.blank;
Implement C99 macros isgreater(), isgreaterequal(), isless(), islessequal(), islessgreater(), isunordered().		13 April 2002	&status.new;	&status.blank;
Implement new hex floating-point format types (%a/%A) in &man.scanf.3;.		20 April 2002	&status.new;	&status.blank;
Implement C99 rounding functions lrint(), lrintf(), lrintl(), llrint(), llrintf(), llrintl().		30 July 2002	&status.new;	&status.blank;
Implement posix_madvise(), posix_mem_offset(), posix_typed_mem_get_info(), posix_typed_mem_open(), posix_memalign().		23 August 2002	&status.new;	&status.blank;
Obtain a64l(), l64a(), and l64a_r() (extention) from NetBSD.		9 September 2002	&status.new;	&status.blank;
Decide whether to implement legacy functions: ecvt(), fcvt(), gcvt().		9 September 2002	&status.new;	&status.blank;
Add SIG_HOLD support to signal(3)/sigaction(2).		13 October 2002	&status.new;	&status.blank;
Implement RTS functions sigqueue(), sigtimedwait(), sigwaitinfo().		13 October 2002	&status.new;	&status.blank;
Update fmtcheck(3) to recognize new printf(3) flags.		16 October 2002	&status.new;	&status.blank;

Task	Responsible	Last Updated	Status
Task	Responsible	Last Updated	5.0	4.x
Headers
Fix prototypes and hide non-conforming portions of header <arpa/inet.h>.	&a.mike;	19 February 2002	&status.done;	&status.n-a;
Implement the <stdint.h> and <inttypes.h> headers.	&a.mike;	1 March 2002	&status.done;	&status.n-a;
Add exposure control primitives to <sys/cdefs.h> (originally developed by &a.wollman).	&a.mike;	1 April 2002	&status.done;	&status.n-a;
Implement <sys/_types> to store shared MI types.	&a.mike;	1 April 2002	&status.done;	&status.n-a;
Implement header <strings.h>, and work out compatibility issues with header <string.h>.	&a.mike;	4 April 2002	&status.done;	&status.n-a;
Hide non-conforming portions, add missing types to <sys/un.h>.	&a.mike;	19 April 2002	&status.done;	&status.n-a;
Remove pollution and add missing macros to <netinet/in.h> and <netinet6/in6.h>.	&a.mike;	23 May 2002	&status.done;	&status.n-a;
Hide non-conforming portions of <sys/wait.h>.	&a.mike;	3 June 2002	&status.done;	&status.n-a;
Hide non-conforming portions of <pwd.h>.	&a.mike;	9 June 2002	&status.done;	&status.n-a;
Create <sys/statvfs.h> based on POSIX spec.	&a.wollman;	14 June 2002	&status.done;	&status.n-a;
Add nfds_t and resolve other issues in <poll.h> (actually <sys/poll.h>).	&a.mike;	8 July 2002	&status.done;	&status.n-a;
Implement the XSI header, <cpio.h>.	&a.mike;	1 August 2002	&status.done;	&status.n-a;
Implement <fmtmsg.h>.	&a.mike;	8 August 2002	&status.done;	&status.n-a;
Implement <ulimit.h>.	&a.mkm;	8 August 2002	&status.done;	&status.n-a;
Merge <machine/ansi.h> and <machine/types> into a new common header <machine/_types.h>.	&a.bde;, &a.mike;	23 August 2002	&status.done;	&status.n-a;
Fix namespaces, add missing types in <sys/mman.h>.	&a.mike;	29 August 2002	&status.done;	&status.n-a;
Fix namespace issues in <ctype.h>.	&a.mike;	9 September 2002	&status.done;	&status.n-a;
Fix namespace issues in <dlfcn.h>.	&a.wollman;, &a.mike;	11 September 2002	&status.done;	&status.n-a;
Fix namespace issues in <fcntl.h>.	&a.mike;	18 September 2002	&status.done;	&status.n-a;
Fix namespace issues in <fnmatch.h>.	&a.mike;	18 September 2002	&status.done;	&status.n-a;
Fix namespace issues in <grp.h>.	&a.mike;	18 September 2002	&status.done;	&status.n-a;
Fix namespace issues in <langinfo.h>.	&a.mike;	18 September 2002	&status.done;	&status.n-a;
Add va_copy() macro to <stdarg.h> (actually <machine/stdarg.h>).	&a.mike;	20 September 2002	&status.done;	&status.n-a;
Fix namespaces issues in <stdlib.h>.	&a.wollman;	21 September 2002	&status.done;	&status.n-a;
Add new pathname, system variable, and POSIX option constants to <unistd.h>.	&a.wollman;	21 September 2002	&status.done;	&status.n-a;
Merge two conflicting math.h headers into a single header.	&a.bde;	2 October 2002	&status.done;	&status.n-a;
Fix namespace issues in <net/if.h>.	&a.mike;	2 October 2002	&status.done;	&status.n-a;
Fix namespace issues in <netinet/tcp.h>.	&a.mike;	2 October 2002	&status.done;	&status.n-a;
Add size_t, fix regoff_t in <regex.h>.	&a.mike;	2 October 2002	&status.done;	&status.n-a;
Fix namespace issues in <sched.h> (actually <posix4/sched.h>).	&a.mike;	5 October 2002	&status.done;	&status.n-a;
Fix namespace issues in <semaphore.h> (actually <posix4/semaphore.h>).	&a.mike;	5 October 2002	&status.done;	&status.n-a;
Fix namespace issues in <setjmp.h> (actually <machine/setjmp.h>).	&a.mike;	5 October 2002	&status.done;	&status.n-a;
Fix namespace issues in <stdio.h>.	&a.wollman;	7 October 2002	&status.done;	&status.n-a;
Add missing members to struct lconv in <locale.h>.	&a.tjr;	9 October 2002	&status.done;	&status.n-a;
Fix namespace issues, add missing types in <sys/socket.h>.	&a.mike;	13 October 2002	&status.done;	&status.n-a;
Fix namespace issues, add missing types in <sys/uio.h>.	&a.mike;	13 October 2002	&status.done;	&status.n-a;
Fix namespace issues in <signal.h> (also <sys/signal.h> and <machine/signal.h>).	&a.mike;	13 October 2002	&status.done;	&status.n-a;
Eliminate <sys/_posix.h>.	&a.mike;	16 October 2002	&status.done;	&status.n-a;
Implement the header <wordexp.h>.	&a.tjr;	31 December 2002	&status.done;	&status.new;
Implement new types and prototypes in header <complex.h>.	&a.markm;	6 February 2002	&status.wip;	&status.blank;
Hide non-conforming portions, add missing types to <sys/types.h>.	&a.mike;	1 April 2002	&status.wip;	&status.blank;
Reduce namespace pollution and add missing typedefs in <unistd.h>	&a.mike;	25 March 2002	&status.wip;	&status.blank;
Implement <utmpx.h> to eventually replace <utmp.h>.	&a.robert;	28 June 2002	&status.wip;	&status.blank;
Implement <ftw.h>.	&a.mkm;	16 August 2002	&status.wip;	&status.blank;
Add missing errnos to <errno.h> (actually <sys/errno.h>).	&a.mike;	11 September 2002	&status.wip;	&status.blank;
Implement the header <iconv.h>.	&a.tjr;	7 October 2002	&status.wip;	&status.blank;
Evaluate missing features of <math.h>.	&a.ryany;	23 December 2002	&status.wip;	&status.blank;
Hide non-conforming portions, add missing types to <sys/stat.h>.	&a.mike;	27 February 2003	&status.wip;	&status.blank;
Implement the header <fenv.h>.	&a.fenner;	14 November 2001	&status.new;	&status.blank;
Add missing constants FLT_EVAL_METHOD, DECIMAL_DIG to <float.h> (actually <machine/float.h>).		17 September 2002	&status.new;	&status.blank;
Fix sizes of members in glob_t, add restrict type-qualifiers in <glob.h>.		20 September 2002	&status.new;	&status.blank;
Decide whether to remove const type-qualifiers in <libgen.h>.		20 September 2002	&status.new;	&status.blank;
Add missing constants in <limits.h>.		20 September 2002	&status.new;	&status.blank;
Fix sizes of members in datum, add missing types, fix namespace issues in <ndbm.h>.		2 October 2002	&status.new;	&status.blank;
Fix size of si_addrlen in struct addrinfo, add missing types, fix namespace issues in <netdb.h>.		2 October 2002	&status.new;	&status.blank;
Evaluate missing features of <pthread.h>.		2 October 2002	&status.new;	&status.blank;
Add missing members to struct sigevent, fix type of ss_sp in struct sigstack, add SIGEV_THREAD constant, add ucontext_t and mcontext_t in <sys/signal.h>.		13 October 2002	&status.new;	&status.blank;
Fix types for members of struct ipc_perm in <sys/ipc.h>.		16 October 2002	&status.new;	&status.blank;
Implement <tgmath.h>.		23 December 2002	&status.new;	&status.blank;

Task	Responsible	Last Updated	Status
Task	Responsible	Last Updated	5.0	4.x
Miscellaneous
Obtain a copy of Proc. ACM SIGPLAN '90 (required for &man.printf.3; %'f).	&a.fenner;	9 November 2001	&status.done;	&status.n-a;
Upgrade system compiler to GCC 3.1.	&a.obrien;	15 May 2002	&status.done;	&status.n-a;
Add regression test for each function.		17 November 2001	&status.new;	&status.blank;
Merge sys/posix4/* into regular kernel hierachy, and remove sys/posix4.		21 September 2002	&status.new;	&status.blank;
Open an Aardvark on how to deal with no newline on the last line of a file in diff(1).		25 November 2002	&status.new;	&status.blank;
Globally rename the `lint' macro to something in the implementation namespace so it can safely modify the implementation (reference).		25 November 2002	&status.new;	&status.blank;
Globally rename the `LOCORE' macro to something in the implementation namespace so it can safely modify the implementation (reference).		25 November 2002	&status.new;	&status.blank;

Task	Responsible	Last Updated	Status
Task	Responsible	Last Updated	5.0	4.x
Utility Conformance
Add -o option and base64 decoding to the uudecode utility.	&a.jmallett;	26 March 2002	&status.done;	&status.done;
Add -m option and base64 encoding to the uuencode utility.	&a.jmallett;	26 March 2002	&status.done;	&status.done;
Require atleast one file argument in paste(1). (PR: 36074)	&a.tjr;	1 April 2002	&status.done;	&status.done;
Add the -i option to the patch utility.	&a.jmallett;	9 April 2002	&status.done;	&status.done;
Add -r and -t options to the at utility.	&a.joe.halpin;	16 April 2002	&status.done;	&status.n-a;
Add the -f and -p options to the pr utility. (PR: 36243)	&a.tjr;	16 April 2002	&status.done;	&status.done;
Add the -s option to the m4 utility. (PR: 36075)	&a.tjr;	24 April 2002	&status.done;	&status.done;
Make printf(1) utility conform to POSIX.2 (1992). (PR: 35616)	&a.tjr;	2 May 2002	&status.done;	&status.done;
Correct output stream and exit status of the mesg(1) utility.	&a.tjr;	6 May 2002	&status.done;	&status.n-a;
Implement the asa utility. (PR: 36130)	&a.tjr;	15 May 2002	&status.done;	&status.n-a;
Add the tabs utility. (PR: 36126)	&a.tjr;	20 May 2002	&status.done;	&status.n-a;
Restore sccs utility from CVS attic.	&a.jmallett;	22 May 2002	&status.done;	&status.n-a;
Make expr(1) conform to POSIX.1-2001.	&a.wollman;	22 May 2002	&status.done;	&status.n-a;
Add the newgrp utility. (PR: 36190)	&a.tjr;	28 May 2002	&status.done;	&status.n-a;
Fix ctags(1)'s -t option; fix ordering with -x.	&a.tjr;	2 June 2002	&status.done;	&status.n-a;
Add -L option to the pwd utility.	&a.tjr;	20 June 2002	&status.done;	&status.done;
Fix exit status of the env(1) utility.	&a.tjr;	20 June 2002	&status.done;	&status.done;
Add the -b and -s option to the fold utility. (PR: 36245)	&a.tjr;	20 June 2002	&status.done;	&status.done;
Add -I and -L options to the xargs utility.	&a.jmallett;	20 June 2002	&status.done;	&status.done;
Implement the csplit utility. (PR: 36191)	&a.tjr;	20 June 2002	&status.done;	&status.n-a;
Fix exit status of the nice(1) utility.	&a.tjr;	20 June 2002	&status.done;	&status.done;
Add -n option to the nice utility.	&a.pavalos;	20 June 2002	&status.done;	&status.done;
Add -n option and resolve other issues in the renice utility. (PR: 36950)	&a.pavalos;, &a.maxim;	20 June 2002	&status.done;	&status.done;
Add -t option to unexpand(1) utility. (PR: 35621)	&a.tjr;	20 June 2002	&status.done;	&status.done;
Make the uniq(1) utility accept `-' as a stdin specifier.	&a.tjr;	28 June 2002	&status.done;	&status.done;
Improve join(1)'s POSIX.1-2001 conformance. (PR: 36072)	&a.tjr;	28 June 2002	&status.done;	&status.done;
Add -C option to the tr utility.	&a.tjr;	28 June 2002	&status.done;	&status.n-a;
Implement the -m, -p, and -x options in the ls utility.	&a.mkm;	8 July 2002	&status.done;	&status.done;
Reimplement the who utility. (PR: 36128)	&a.tjr;	14 July 2002	&status.done;	&status.done;
Fix exit status, stdout/stderr confusion, and add `-' stdin support to the compress(1) utility.	&a.tjr;	17 July 2002	&status.done;	&status.done;
Add the -s, -A, -j, -N, and -t options to the od utility. (PR: 36783)	&a.tjr;	24 July 2002	&status.done;	&status.done;
Add -a option to the split utility.	&a.tjr;	30 July 2002	&status.done;	&status.done;
Add -m option to the wc utility.	&a.tjr;	29 August 2002	&status.done;	&status.done;
Add -L and -P options to the cd utility (shell built-in).	&a.tjr;	7 October 2002	&status.done;	&status.done;
Reimplement command(1) (shell built-in).	&a.tjr;	7 October 2002	&status.done;	&status.done;
Add the c99 utility (similar to c89). (PR: 36087)	&a.tjr;	8 October 2002	&status.done;	&status.n-a;
Update getconf(1) for POSIX.1-2001.	&a.wollman;	12 November 2002	&status.done;	&status.done;
Add the pathchk utility.	&a.tjr;	12 November 2002	&status.done;	&status.done;
Document the -n option in the echo utility as being implementation-defined.	&a.schweikh;	8 May 2003	&status.done;	&status.done;
Add missing options to the mailx utility.	&a.mikeh;	22 December 2001	&status.wip;	&status.blank;
Add missing components to the jobs utility.	&a.mkm;	5 March 2002	&status.wip;	&status.blank;
Work out conflicting -t option in the df utility.	&a.tjr;	22 April 2002	&status.wip;	&status.blank;
Add unimplemented features to the sh utility.	&a.tjr;	20 May 2002	&status.wip;	&status.blank;
Implement the -m, -w, and -t options in the lp utility.	&a.gad;	23 May 2002	&status.wip;	&status.blank;
Implement/import the SCCS development utilities: admin, delta, get, prs, rmdel, sact, unget, val	&a.jmallett;	23 May 2002	&status.wip;	&status.blank;
Investigate adopting some of the POSIX options in the ps utility.	&a.jmallett;	6 June 2002	&status.wip;	&status.blank;
Add missing options and resolve conflicting options in the nm utility.	&a.robert;	2 August 2002	&status.wip;	&status.blank;
Implement the iconv utility.	&a.tjr;	9 October 2002	&status.wip;	&status.blank;
Implement the locale and localedef utilities.	&a.phantom;	16 October 2002	&status.wip;	&status.blank;
Add -C and -T options to the ar utility.		30 November 2001	&status.new;	&status.blank;
Investigate importing the cflow utility from the ports collection.		30 November 2001	&status.new;	&status.blank;
Add -p, -v, and -V options to the command utility (shell built-in).		30 November 2001	&status.new;	&status.blank;
Bring the cp utility up to conformance.		30 November 2001	&status.new;	&status.blank;
Implement the cxref utility.		30 November 2001	&status.new;	&status.blank;
Add the -d, -h, and -M options and fix conflicting -i option in the file utility.		30 November 2001	&status.new;	&status.blank;
Bring the make utility up to conformance.		30 November 2001	&status.new;	&status.blank;
Add -p option the more utility.		30 November 2001	&status.new;	&status.blank;
Add the qsub utility.		30 November 2001	&status.new;	&status.blank;
Make printf(1) utility conform to SUSv3.		23 April 2002	&status.new;	&status.blank;
Implement the fuser utility. (PR: 36076)		4 February 2003	&status.new;	&status.blank;

Task	Responsible	Last Updated	Status
Task	Responsible	Last Updated	5.0	4.x
Wide Character/String Support
Implement basic support for wide character I/O: getwc(), fgetwc(), getwchar(), putwc(), fputwc(), putwchar(), ungetwc(), fwide().	&a.tjr;	16 August 2002	&status.done;	&status.n-a;
Add stubs for reentrant wc handling functions btowc(), mbrlen(), mbrtowc(), mbsrtowcs(), wcrtomb(), wcsrtombs(), wctob(), wctype().	&a.tjr;	23 August 2002	&status.done;	&status.n-a;
Add stubs for reentrant wc handling functions iswalnum(), iswalpha(), iswcntrl(), iswctype(), iswdigit(), iswgraph(), iswlower(), iswprint(), iswpunct(), iswspace(), iswupper(), iswxdigit().	&a.tjr;	23 August 2002	&status.done;	&status.n-a;
Implement wcwidth().	&a.keichii;	23 August 2002	&status.done;	&status.n-a;
Implement wcswidth().	&a.ache;	23 August 2002	&status.done;	&status.n-a;
Implement wcstok().	&a.tjr;	9 September 2002	&status.done;	&status.n-a;
Implement wcstod(), wcstol(), wcstoul().	&a.tjr;	15 September 2002	&status.done;	&status.n-a;
Implement wcsftime().	&a.tjr;	15 September 2002	&status.done;	&status.n-a;
Implement fwprintf(), swprintf(), vfwprintf(), vswprintf(), vwprintf(), wprintf().	&a.tjr;	23 September 2002	&status.done;	&status.n-a;
Implement fwscanf(), swscanf(), vfwscanf(), vswscanf(), vwscanf(), wscanf().	&a.tjr;	23 September 2002	&status.done;	&status.n-a;
Implement wcstoimax(), wcstoll(), wcstoumax(), wcstoull().	&a.tjr;	23 September 2002	&status.done;	&status.n-a;
Implement wide character format types (%C, %S, %lc, %ls) in &man.printf.3;.	&a.tjr;	16 October 2002	&status.done;	&status.n-a;
Implement wcscoll(), wcsxfrm().	&a.tjr;	7 October 2002	&status.wip;	&status.blank;
Implement wide character format types (%C, %S, %lc, %ls) in &man.scanf.3;.	&a.tjr;	18 September 2002	&status.new;	&status.blank;

Legend
&status.new;	Not yet started
&status.blocked;	Blocked awaiting completion of another task
&status.wip;	Work in progress
&status.done;	Task completed
&status.n-a;	Not planned

The remainder of this page is structured as a reverse-chronological log.

31 December 2002

Jens Schweikhardt has updated his POSIX Utility Conformance in FreeBSD list. Not much works remains to complete utility conformance.

13 December 2002

A new status report on the state of the project, covering September through October, has been produced.

9 October 2002

A new status report on the state of the project, covering July through August, has been produced.

16 August 2002

A new status report on the state of the project, covering May through June, has been produced.

1 August 2002

The Open Group has generously donated several copies of the - Authorized Guide to Single UNIX Specification, Version 3, + Authorized Guide to Single &unix; Specification, Version 3, books and CD-ROMs to the project. We are greatly appreciative of their gift.

22 May 2002

A new status report on the state of the project, covering February through April, has been produced.

3 March 2002

A new status report on the state of the project, covering December and January, has been produced.

30 January 2002

The Open Group has announced the completion of SUSv3 and POSIX.1-2001 and the availability of a free, online version of the specification.

14 December 2001

A new status report on the current state of the project has been produced.

6 December 2001

The IEEE Standards Board has approved the Austin Group Specification as IEEE Std 1003.1.

28 November 2001

The project mailing list has been moved from freebsd-standards@bostonradio.org to &a.standards;.

19 October 2001

A status report on the current state of the project has been produced.

10 October 2001

This web page was created.

&footer; diff --git a/en/projects/newbies.sgml b/en/projects/newbies.sgml index 1ce232aa2f..e8640d2702 100644 --- a/en/projects/newbies.sgml +++ b/en/projects/newbies.sgml @@ -1,249 +1,249 @@ - + %includes; ]> &header;

The following resources are some of those which FreeBSD newbies have found most helpful when learning to use FreeBSD. Please send corrections and additions to FreeBSD-Newbies@FreeBSD.org.

Using the FreeBSD web site
Learning about FreeBSD
Learning about UNIX
Learning about &unix;
Learning about the X Window System
Helping other people

Using the FreeBSD web site

This web site is the main source of up to date information about FreeBSD. Newbies have found the following pages particularly helpful:

Search the Handbook and FAQ, or the whole web site, or the archives of the FreeBSD-Questions mailing list.
The Documentation page has links to the Handbook and FAQ, tutorials, information about contributing to the Documentation Project, documents in languages other than English, and much more.
Support page contains a wealth of information about FreeBSD, including mailing lists, user groups, web and FTP sites, release information, and links to some sources of - UNIX information.

Learning about FreeBSD

If you haven't installed yet, look for the latest mainstream release. (See the Handbook for why you should not be tempted by any of the other branches.) Before you begin, carefully read the installation instructions, as well as each one of the *.TXT files in the FTP directory or on the installation CD. They are there because they contain information that you will need. Also pick up the latest errata file from the web site, in case it has been updated.

If you decide to download FreeBSD, check whether these illustrated and expanded download instructions for a previous version are still available before you begin. That should make the whole process a lot clearer.
A number of short articles and tutorials are available. The short tutorial, For People New to Both FreeBSD and Unix, is popular with absolute beginners. You don't have to know much about anything to enjoy this one. It can also be downloaded in postscript or RTF format for printing.
The first thing many people need to set up is ppp, and there is a lot of documentation to help. You might start with at least those parts of the Handbook that are relevant to your needs, and explore the ppp page for links to the other valuable information and the latest updates.
The Complete FreeBSD by Greg Lehey, published by BSDi. This book assumes minimal UNIX experience and takes the beginner step by step through each stage from installation to everything you need to know to set up and run a FreeBSD system. You also get to understand what you're doing and why.
The FreeBSD Handbook and Frequently Asked Questions (FAQ) are the main documents for FreeBSD. Essential reading, they contain a lot of material for newbies as well as some pretty advanced stuff. Don't worry if you can't understand the advanced sections. The handbook contains the installation instructions and also provides lists of books and on line resources, and the FAQ has a troubleshooting section.
Join the FreeBSD-Questions mailing list to see the questions you were too afraid to ask, and their answers. Subscribe by sending mail to freebsd-questions-subscribe@FreeBSD.org. You can look up old questions and answers via the search page.
The main newsgroup for FreeBSD is comp.unix.bsd.freebsd.misc. You might want to keep an eye on comp.unix.bsd.freebsd.announce as well.
Man pages are good for reference but not always the best introduction for a novice. The more you work with man pages the more familiar they become. Some are very good for newbies, so always check them out. The ppp man page, for example, is more like a tutorial.

Learning about UNIX

Learning about &unix;

Many of the problems we have as newbies come from being unfamiliar with the UNIX commands needed to fix our FreeBSD problems. Without a UNIX background you'll be faced with two things to learn at once. Fortunately a lot of resources are available to make this easier.

There are many easy books, such as the "Dummies" guides, in any large book shop. If you want something really easy, take a look at what is available and pick one that seems to speak your language. Pretty soon you will want to move on to a book that gives more coverage.
One book mentioned frequently by newbies is UNIX for the Impatient by Paul W. Abrahams and Bruce R. Larson, published by Addison-Wesley. It is intended both as a book for learning UNIX and a reference, and includes an introduction to UNIX concepts and handy chapter on using the X Window System.
Another popular book is UNIX Power Tools by Jerry Peek, Tim O'Reilly and Mike Loukides, published by O'Reilly and Associates. It is organised as a series of short articles each of which solves a problem, and these articles are cross-referenced to other articles with related material. Though not specifically aimed at newbies, the design makes it ideal for a newbie with a burning question or the odd few minutes to browse. More elementary material is near the front of the book, but there are short easy articles throughout.
A UNIX Introductory Course from Ohio State University is available online in HTML, postscript and Acrobat PDF formats.
UNIXhelp for Users is another introductory guide which is available in HTML at a mirror site near you, or can be installed on your own system.
UNIX questions are dealt with in the newsgroup comp.unix.questions and the associated Frequently Asked Questions. You can also get a copy of the FAQ from the RMIT FTP site. Newbies are likely to be most interested in sections 1 and 2 initially.
Another interesting newsgroup is comp.unix.user-friendly which also has a FAQ. Although this newsgroup is for discussing user-friendliness, it can contain some good information for newbies. The FAQ is also available by FTP.
Many other web sites hold lists of UNIX tutorials and reference material. One of the best places to start looking is the UNIX page at Yahoo!.

Learning about the X Window System

The X Window System is used with a number of operating systems, including FreeBSD. The documentation for X can be found at The XFree86 Project, Inc. Beware, much of this documentation is reference material which is likely to be difficult for newcomers to digest.

For basic information about installing, configuring and using the X Window System, three of the books mentioned above have sections dealing with X at beginner level: The FreeBSD Handbook, The Complete FreeBSD, and UNIX for the Impatient.
There is an easy and informative section on using the X Window System in the Linux Users' Guide. Interesting material will be found elsewhere in that document too, but remember that Linux does not always work exactly the same as FreeBSD.
Before you can get X running exactly the way you like, you will need to choose a window manager. Visit the Window Managers for X page and follow the link to the introduction to find out about window managers, then return and read "The Basics". Then go back and compare the different types that are available. (Bonus: there's another beginners guide to UNIX there too.) Most if not all of these window managers are available to install from the FreeBSD ports collection.

Helping other people

Everyone has something to contribute to the FreeBSD community, even newbies! Some are busy working with the new advocacy group and some have become involved with the Documentation Project as reviewers. Other FreeBSD newbies might have particular skills and experiences to share, either computer related or not, or just want to meet new newbies and make them feel welcome. There's always people around who help others simply because they like to. Write to FreeBSD Newbies for more information.

Friends who run FreeBSD are a great resource. No book can replace chatting on the phone or across a pizza with someone who has the same interests, enjoys similar accomplishments, and faces the same challenges. If you don't have many friends who use FreeBSD, consider using your old FreeBSD CDs to create some more :-)

User groups are good places to meet other FreeBSD users. If there's not one nearby, maybe you could start one.

Before talking to real humans about your new skills, you might want to check the Pronunciation Guide and the Jargon File :-)

On line we have the FreeBSD-Newbies mailing list for non-technical discussions about matters of interest to newbies. Another mailing list, FreeBSD-Questions, answers our questions about using FreeBSD.

&footer; diff --git a/en/projects/projects.sgml b/en/projects/projects.sgml index 0ea80758ba..b2a4a7a382 100644 --- a/en/projects/projects.sgml +++ b/en/projects/projects.sgml @@ -1,489 +1,489 @@ - + %includes; ]> &header;

In addition to the mainstream development path of FreeBSD, a number of developer groups are working on the cutting edge to expand FreeBSD's range of applications in new directions. Follow the links below to learn more about these exciting projects.

If you miss a project please send the URL and a short description (3-10 lines) to www@FreeBSD.ORG

In addition, some of these projects regularly submit status reports, which can be viewed on the status reports page.

Documentation
Advocacy
Applications
Networking
Filesystem
Kernel and Security
Device drivers
Architecture
Misc

Documentation

FreeBSD Documentation Project The FreeBSD Documentation Project is a group of people who maintain and write the documentation (such as the Handbook and FAQ) for the FreeBSD project. If you want to help with the documentation project, subscribe to the freebsd-doc@FreeBSD.ORG mailing list and participate.
FreeBSD Resources for Newbies -is a list of resources to help those new to FreeBSD and UNIX in +is a list of resources to help those new to FreeBSD and &unix; in general. There is also a freebsd-newbies@FreeBSD.ORG mailing list.
FreeBSD Security How-To FreeBSD is a very secure operating system. Since source code is freely available, the OS is constantly going through the review and audit. While FreeBSD comes very secure OOB (Out-Of-Box), there are many features that can make it more secure for those of you who are "paranoid". This How-To will go over some steps which will help you increase overall security of your machine.
RELEASE/SNAP finder for FreeBSD FTP servers. A resource that would allow anyone to find a FTP server that contains particular releases and SNAP of FreeBSD. The database is updated daily at 3am Melbourne time (10 hours ahead of UTC).
The FreeBSD Diary is a collection of how-to entries aimed at UNIX novices. The aim is to provide a set of step-by-step guides to installing and configuring various ports.
A Comprehensive Guide to FreeBSD - an attempt at a more readable, "book-like" tutorial explaining the FreeBSD Operating System. Intended for people new to both FreeBSD and UNIX. Currently a work in progress.
FreeBSD How-To's for the Lazy and Hopeless is another somewhat more light-hearted attempt to provide more readable "how-to" style information on setting up and configuring FreeBSD.
The Linux+FreeBSD mini-HOWTO describes how to use Linux and FreeBSD on the same system. It introduces FreeBSD and discusses how the two operating systems can cooperate, e.g. by sharing swap space.
Install Preview for FreeBSD 2.2.7 This is a guide illustrating the FreeBSD install program for those new to unix and/or FreeBSD.
The FreeBSD Developers Handbook
The FreeBSD Cook Book Ok, you got FreeBSD installed, now what? Here are some suggested solutions to common problems you can implement with the knowledge you now have. This document is styled after the electronics cook books with some recipes for some common types of installations. Each "recipe" has some recommended minimum hardware, specific software to use, and most important the configuration information required to get the system running correctly.
The FreeBSD Corporate Networker's Guide This Web site serves as a supplement to The FreeBSD Corporate Networker's Guide, with the principal goal of enhancing its usefulness. While books like fictional novels can be used and enjoyed for hundreds of years after initial publication, technical manuals like the Networker's Guide are obsoleted in a few years by changes in the product they are written for.

Applications

Java on FreeBSD -This contains information on where to obtain the latest JDK for +
&java; on FreeBSD +This contains information on where to obtain the latest &jdk; for FreeBSD, how to install and run it, and a list of java software that you may find interesting. Please note that the JDK is unsupported on versions of FreeBSD prior to 2.2.
GNOME on FreeBSD This contains information on where to obtain the latest GNOME for FreeBSD, how to install and run it, latest project news and updates, FAQ covering FreeBSD-specific GNOME issues, application porting guidelines and much more.
MultiMedia A resource of links to information and software pertaining to the world of multimedia in the UNIX world.
FreeBSD Ports Collection The FreeBSD Ports Collection provides an easy way to compile and install a wide range of applications with a minimum amount of effort. A list of current ports is available along with a search mechanism to see if a specific application exists in the Ports Collection.
FreeBSD Ports distfiles survey is a list which checks the Ports Collection for unfetchable distfiles and provides a summary for each port.
FreshPorts provides the most up-to-date list of ports and port changes. Add your favourite ports to your watch list and receive email notification of any changes.
Bento is a server which checks the Ports Collection and keeps package building logs and error logs for each port.

Networking

ALTQ: bandwidth management for applications
KAME Project, a free IPv6/IPsec stack for BSD
Point to Point Protocol (PPP)
Secure MobileIP via IP
SYSLOG-SECURE: In August 2001 a standard of syslog was made: RFC3164. This to describe some extensions tot syslog to add security. The project I started in 2002 is to adapt RFC3164 to FreeBSD version of syslog, and to add some security extensions. At least syslog-sign. Both libc and syslogd will be modified. And optional some tools to verify/manage the security will made. All help is welcome. Send an email to albert@ons-huis.net for info.

File system

HFS and HFS Plus in FreeBSD. This project is aimed at integrating HFS support from Darwin into FreeBSD.
Arla is a free AFS client implementation. The main goal is to make a fully functional client with all capabilities of normal AFS. Other planned and implemented things are all the normal management tools and a server.
Coda is a distributed filesystem. Among its features are disconnected operation, good security model, server replication and persistent client side caching.
cryptfs encrypts file names and data pages using Blowfish.
Elephant: The File System that Never Forgets
Journaling versus Soft Updates: Asynchronous Meta-data Protection in File Systems
Mode locking
Make the namei interface reflexive
NFS client and server locking
The Design and Implementation of a DCD Device Driver for Unix
NTFS Driver for FreeBSD -This driver allows Windows NTFS partitions to be mounted by FreeBSD. +This driver allows Windows® NTFS partitions to be mounted by FreeBSD. Currently NTFS partitions can only be accessed in read-only mode, but plans are in the works for read/write access.
Rio (RAM I/O): The Rio project is investigating how to implement and use reliable memory. Reliable memory enables dramatic improvements in reliability and performance.
Soft Updates: A Solution to the Metadata Update Problem in File Systems
TCFS is a Transparent Cryptographic File System that is a suitable solution to the problem of privacy for distributed filesystem. By a deeper integration between the encryption service and the filesystem, it results in a complete transparency of use to the user applications. Files are stored in encrypted form and are decrypted before they are read. The encryption/decryption process takes place on the client machine and thus the encryption/decryption key never travels on the network.
Tertiary Disk is a storage system architecture to create large disk storage systems that avoid the disadvantages of custom built disk arrays. The name comes from twin goals: to have the cost per megabyte and capacity of tape libraries and the performance of magnetic disks. We use commodity, off the shelf components to develop a scalable, low cost, terabyte capacity disk system. Our target is to build a complete storage system with about 30-50% extra to the cost of the raw disk. Tertiary Disk uses PCs connected by a switched network to host a large number of disks. Our prototype consists of 20 200MHz PC PCs, which host 370 8GB disks. The PCs are connected through a 100Mbps Ethernet switch.
Vinum -is a logical volume manager modeled after the VERITAS volume manager. +is a logical volume manager modeled after the VERITAS volume manager™. However, it is not a clone of Veritas, and attempts to solve a number of problems more elegantly than Veritas. It also offers features that Veritas does not have.
The PathConvert project is to develop utilities which make conversion between absolute path name and relative path name. It brings benefits mainly to the users of NFS and WWW.
WAFS is a simple filesystem designed to act as a logging service for kernel subsystems. Reads and writes are keyed by log-sequence number (LSN). All writes to WAFS are sequential. Kernel subsystems can use this LSN service to enforce write-ahead logging and guarantee consistency.

Kernel, security

Drawbridge is a firewall package that was developed at Texas A&M University and was designed with a large academic environment in mind. It's greatest strength is the ability to perform high speed packet filtering for a larger number of individual hosts within an intranetwork.
Kernel Scheduler Entities: A project to enhance the threading support on FreeBSD, using a threading system similar in design to Scheduler Activations.
Lottery Scheduling Kernel: This work is based on Waldspurger's lottery scheduling algorithm, which implements proportional-share resource management. The primary advantages are that users have strict control over the relative execution rates of their processes, and users are load-insulated from each other, preventing one user from dominating the CPU.
Working LDAP for FreeBSD
Symmetric MultiProcessor Support Documentation and other information about taking advantage of multiple processors under FreeBSD.
A validation suite for testing for kernel memory leaks
SPY allows you to monitor and/or selectively block syscalls on your system. It could be used either as a safety monitoring device, policy enforcement, or debugging tool.
TrustedBSD provides a set of trusted operating system extensions to the FreeBSD operating system. This includes features such as fine-grained privileges (capabilities), Access Control Lists, and Mandatory Access Control. These features are being integrated back into the base FreeBSD distribution, as well as being ported to other BSD-derived systems.

Device drivers

BSD Driver Database Just because you don't have the time to write the driver yourself doesn't mean you can't still help. The idea behind the BSD Driver Database is to help individuals with hardware that needs supporting get in touch with driver developers with the knowledge to write the support for the hardware. This is a list of drivers currently under development that could stand to gain from time or resources you may have to offer.
busdma and SMPng driver conversion: busdma provides a portable abstraction to the Direct Memory Access (DMA) hardware primitives used by many high performance device drivers. By using this abstraction, device driver authors avoid adding platform-specific DMA management code, improving the portability of drivers between hardware architectures. This page also tracks the progress of drivers towards being SMPng-safe.
A New Device Framework for FreeBSD
BSD ATM: implementation of ATM internetworking under 4.4BSD: New computer applications in areas such as multimedia, imaging, and distributed computing demand high levels of performance from computer networks. ATM-based networking solutions provide one possible alternative to meeting these performance needs. However, the complexity of ATM over traditional networks such as Ethernet has proven to be a barrier to its being used. In this paper we present the design and implementation of BSD ATM, a light-weight and efficient ATM software layer for BSD-based operating systems that requires minimal changes to the operating system. BSD ATM can be used both for IP-based networking traffic and for ``native'' ATM traffic.
High-precision timekeeping with FreeBSD How to create a NTP stratum 1 server with state of the art performance.
Home Automation with FreeBSD such as appliance controllers, infra-red controllers, automated telephone systems, and more.
CAM: New SCSI layer for FreeBSD Details about what the new CAM SCSI layer is, and how it works.
The FreeBSD Token-Ring Project Information, files, patches, and documentation about adding Token Ring support to FreeBSD.
FreeBSD USB driver development The NetBSD USB stack has been ported to FreeBSD. Together with them we have started developing the drivers for many devices using the USB bus. Have a look on the webpage if you want to join the effort or you want to have a look on the devices that are being supported.
Setting up PnP (Plug-and-Play) and the AWE64, AWE32, or SB32 soundcards with FreeBSD.
A mailing list exists for further development of Scott Mitchell's Xircom CEM ethernet driver. Send subscribe freebsd-xircom to majordomo@lovett.com to join.
Mike Smith's list of supported RAID cards and their respective information.

Architecture

Porting FreeBSD to Alpha systems Contains information on the FreeBSD Alpha port such as the status, mailing list information, the hardware used, and other Alpha projects.
Porting FreeBSD to IA-64 systems This project is responsible for porting FreeBSD to the IA-64 architecture. Direct any questions specific to this project to the freebsd-ia64@FreeBSD.org mailing list.
Porting FreeBSD to PowerPC systems. +
Porting FreeBSD to PowerPC® systems. Contains information on the FreeBSD PPC port, such as mailing list information and so on.
Porting FreeBSD to SPARC systems +
Porting FreeBSD to SPARC® systems Contains information on the FreeBSD SPARC port including a FAQ, some early boot code, information on SPARC processors and motherboards, and other SPARC projects.
The SysVR4 Emulation page describes an SysVR4 emulator for FreeBSD. It is currently capable of running (or walking, in some -cases) a wide-ish variety of SysV executables taken from Solaris/x86 +cases) a wide-ish variety of SysV executables taken from Solaris™/x86 2.5.1 and 2.6 systems. I have reason to believe that it will also run SCO UnixWare and SCO OpenServer binaries.
The OSKit The OSKit is a framework and a set of 31 component libraries oriented to operating systems, together with extensive documentation. By providing in a modular way not only most of the infrastructure "grunge" needed by an OS, but also many higher-level components, the OSKit's goal is to lower the barrier to entry to OS R&D and to lower its costs. The OSKit makes it vastly easier to create a new OS, port an existing OS to the x86 (or in the future, to other architectures supported by the OSkit), or enhance an OS to support a wider range of devices, filesystem formats, executable formats, or network services. The OSKit also works well for constructing OS-related programs, such as boot loaders or OS-level servers atop a microkernel.
Small and embedded FreeBSD (PicoBSD) PicoBSD is a one floppy version of FreeBSD which in its different variations allows you to have secure dial-up access, small diskless router, or even a dial-in server. All of this on only one standard 1.44MB floppy disk. It runs on a minimum 386SX CPU with 8MB of RAM, and no hard drive is required!

Misc

GLOBAL is a common source code tag system that works the same way across diverse environments. Currently, it supports the shell command line, the nvi editor, web browser, the emacs editor, and the elvis editor, and the supported languages are C, Yacc, and Java.
PAO: Mobile Computing page, laptops running FreeBSD 2.2.X and 3.X Laptop users looking for PC Card (aka PCMCIA) support under FreeBSD 2.2.X and 3.X should look at the PAO project for laptop support (FreeBSD 4.X and higher are provided with laptop support).
FreeBSD cross reference. A hypertext cross referenced presentation of the FreeBSD kernel source code. The version indexed is -CURRENT, and it is updated every night.
Enteruser: A Replacement for Adduser
FreeBSD libh Project. Libh is a wrapper that allows tcl scripts to run in a sort of sandbox and interface to other libraries. Some of the stock libraries that come with libh that can be called from the Tcl scripts include a generic user interface library, which uses Turbo Vision for its console backend, and Qt for its X11 backend. Libh also includes a new package system that uses Zip archives and various per-package scripts among other things. It also includes the beginnings of a new sysinstall.
Binary Updater (binup). The FreeBSD Binary Updater Project aims to provide a secure mechanism for the distribution of binary updates for FreeBSD. This system is a client / server mechanism that allows clients to install any known "profile" or release of FreeBSD over the network. Where a specific profile might contain a specific set of FreeBSD software to install, additional packages, and configuration actions that make it more ideal for a specific environment (ie FreeBSD 4.3 Secure Web server profile).
The - FreeBSD C99 & POSIX Conformance Project aims to + FreeBSD C99 & POSIX® Conformance Project aims to implement all requirements of the ISO 9899:1999 (C99) and IEEE 1003.1-2001 (POSIX) standards.
CVSweb is a WWW interface for CVS repositories with which you can browse a file hierarchy on your browser to view each file's revision history in a very handy manner.

&footer; diff --git a/en/search/search.sgml b/en/search/search.sgml index f9edea10b7..c948496e38 100644 --- a/en/search/search.sgml +++ b/en/search/search.sgml @@ -1,556 +1,556 @@ - + %includes; ]> &header;

FreeBSD Search Services

Web pages
Mailing list archives
Message-ID
GNATS Problem Reports (Bugs) database
Manual Pages
Ports Changes
The Source Code
BSD Usenet News Searcher
Google Search BSD
GreasyDaemon, an all-in-one BSD UNIX search engine

Web pages (including FAQ and Handbook)

Mailing list archives

The mailing list archive indexes are now updated weekly!

An alternative way to read the mailing lists archives is to use the Mailman/Pipermail list archive (note that this archive only carries messages from March 2003 onward).

The mailing lists (as well as many others) have also been archived by GeoCrawler.

Search for:

Note: Use the operators AND or NOT to limit your search. Look here for more hints.

Limit the number of results to sort by Search

In archive(s):

Note: Searching more than three or four archives at once may yield inaccurate results.

General Archives

Advocacy	FreeBSD Evangelism
Announce	Important events / milestones
Chat	Random topics (sometimes) related to FreeBSD
Jobs	FreeBSD related job announcements and resumes
Newbies	New FreeBSD users activities and discussion
Questions	General questions
Security Notifications	Announcements regarding FreeBSD security issues (including, e.g., CERT notices)
User-Groups	A forum for FreeBSD user groups

System Use and Administration

Bugs	Reports and discussion of bugs
Cluster	Discussions related to using FreeBSD in clustered environments
Hardware	Discussions concerning hardware as it relates to FreeBSD
ISP	Discussions for ISPs using FreeBSD
Performance	Discussions of the performance of FreeBSD under high load or extreme conditions
Security	FreeBSD computer security issues (DES, Kerberos, etc.)
Stable	Discussion of the FreeBSD-stable branch of the development tree

Developer

+ value="freebsd-java"> &java;

Afs	Porting and using AFS (the Andrew File System) from CMU/Transarc
Alpha	Porting FreeBSD to the DEC Alpha
Arch	Architecture and design discussions
ARM	Porting FreeBSD to the StrongArm
ATM	Using ATM networking with FreeBSD
Audit	Source code audit project
Binup	Design and development of the binary update system
Bugbusters	Coordination of the Problem Report handling effort
Commit (all)	All Changes made to all FreeBSD source trees
Commit (doc)	Changes made to the FreeBSD documents source tree
Commit (ports)	Changes made to the FreeBSD ports source tree
Commit (projects)	Changes made to the FreeBSD projects source tree
Commit (src)	Changes made to the FreeBSD main source tree
Config	Development of FreeBSD installation and configuration tools
Current	Use of FreeBSD-current sources
CVSweb	Technical discussions about use, development and maintenance of FreeBSD-CVSweb
Database	Discussing database use and development under FreeBSD
Doc	Discussions concerning documentation
Emulation	Emulating other systems on FreeBSD
Firewire	Design and implementation of a Firewire (aka IEEE 1394 aka iLink) subsystem for FreeBSD
Fs	Discussions concerning FreeBSD filesystems
Gnome	Discussions concerning the FreeBSD GNOME project
Hackers	General technical discussions
I18n	FreeBSD Internationalization
i386	i386-specific issues for FreeBSD
ia32	FreeBSD on the IA32 platform
ia64	Porting FreeBSD to Intel's upcoming IA64 systems
ipfw	Technical discussion concerning the redesign of the IP firewall code
ISDN	Development of ISDN support for FreeBSD
Java	JDK porting and application development
libh	The second generation installation and package system
MIPS	Porting FreeBSD to MIPS
Multimedia	Discussions about FreeBSD as a multimedia platform
Mobile	Using FreeBSD in a mobile environment
Mozilla	Porting mozilla to FreeBSD
Net	Networking discussion and TCP/IP source code
New Bus	Technical discussions on Bus Architecture
OpenOffice	Discussions concerning the FreeBSD OpenOffice and StarOffice ports
Platforms	Cross-platform FreeBSD issues (non-Intel FreeBSD ports)
Policy	FreeBSD core team policy decisions.
Ports Bugs	Bug reports concerning FreeBSD's ports collection
Ports	Discussions concerning FreeBSD's ports collection
PPC	Porting FreeBSD to the PowerPC
QA	Discussion of quality assurance issues
Realtime	Development of realtime extensions to FreeBSD
SCSI	Discussions about FreeBSD's SCSI support
Small	Using FreeBSD in embedded applications
SMP	FreeBSD on multi-processor platforms
SPARC64	Porting FreeBSD to the SPARC64
Standards	FreeBSD Conformance to the C99 and the POSIX standards
Threads	Discussion about threading models in FreeBSD, including KSE and others
Tokenring	Support Token Ring in FreeBSD

Limited lists

Hubs	People running mirror sites (infrastructural support)
Install	Installation system development
WWW	Web site maintainers

&footer; diff --git a/en/security/security.sgml b/en/security/security.sgml index 8e2f57eecf..14b37733e7 100644 --- a/en/security/security.sgml +++ b/en/security/security.sgml @@ -1,892 +1,892 @@ - + %includes; ]> - + &header;

Introduction

This web page is designed to assist both new and experienced users in the area of FreeBSD security. FreeBSD takes security very seriously and is constantly working on making the OS as secure as possible.

Here you will find additional information, or links to information, on how to protect your system against various types of attack, on whom to contact if you find a security-related bug, and so on. There is also a section on the various ways that the systems programmer can become more security conscious so that he is less likely to introduce vulnerabilities.

Information about the FreeBSD Security Officer
Information handling policies
FreeBSD Security Advisories
FreeBSD Security Mailing Lists Information
FreeBSD Security Tips and Tricks
Secure Programming Guidelines
Other Related Security Information

The FreeBSD Security Officer and the Security Officer Team

To better coordinate information exchange with others in the security community, FreeBSD has a focal point for security-related communications: the FreeBSD Security Officer.

If you need to contact the FreeBSD Project about a possible security issue, you should therefore send mail to the Security Officer with a description of what you have found and the type of vulnerability it represents.

In order that the FreeBSD Project may respond to vulnerability reports in a timely manner, there are four members of the Security Officer mail alias: the Security Officer, the Deputy Security Officer, and two Core Team members. Therefore, messages sent to the <security-officer@FreeBSD.org> mail alias are currently delivered to:

Jacques Vidrine <nectar@FreeBSD.org>	Security Officer
Chris Faulhaber <jedgar@FreeBSD.org>	Deputy Security Officer
Robert Watson <rwatson@FreeBSD.org>	FreeBSD Core Team member, Release Engineering liaison, TrustedBSD Project liaison, system security architecture expert
Warner Losh <imp@FreeBSD.org>	FreeBSD Core Team liaison, Security Officer Emeritus

The Security Officer is supported by the Security Officer Team <security-team@FreeBSD.org>, a group of committers selected by the Security Officer. The current make up of the team is as follows:

Bill Fumerola <billf@FreeBSD.org>	FreeBSD Infrastructure liaison
Daniel Harris <dannyboy@FreeBSD.org>	Doc and ports committer
Trevor Johnson <trevor@FreeBSD.org>	ports committer
Kris Kennaway <kris@FreeBSD.org>	Port Manager liaison, Security Officer Emeritus
Wes Peters <wes@FreeBSD.org>	FreeBSD Core Team member; former security software researcher and developer for the US Air Force, Axent Technologies/Symantec, Intel, and Alcatel Internetworking.
Guido van Rooij <guido@FreeBSD.org>	Security Officer Emeritus
Dag-Erling Smorgrav <des@FreeBSD.org>

Please use the Security Officer PGP key to encrypt your messages to the Security Officer when appropriate.

Information handling policies

As a general policy, the FreeBSD Security Officer favors full disclosure of vulnerability information after a reasonable delay to permit safe analysis and correction of a vulnerability, as well as appropriate testing of the correction, and appropriate coordination with other affected parties.

The Security Officer will notify one or more of the FreeBSD Cluster Admins of vulnerabilities that put the FreeBSD Project's resources under immediate danger.

The Security Officer may bring additional FreeBSD developers or outside developers into discussion of a submitted security vulnerability if their expertise is required to fully understand or correct the problem. Appropriate discretion will be exercised to minimize unnecessary distribution of information about the submitted vulnerability, and any experts brought in will act in accordance of Security Officer policies. In the past, experts have been brought in based on extensive experience with highly complex components of the operating system, including FFS, the VM system, and the network stack.

If a FreeBSD release process is underway, the FreeBSD Release Engineer may also be notified that a vulnerability exists, and its severity, so that informed decisions may be made regarding the release cycle and any serious security bugs present in software associated with an up-coming release. If requested, the Security Officer will not share information regarding the nature of the vulnerability with the Release Engineer, limiting information flow to existence and severity.

The FreeBSD Security Officer has close working relationships with a number of other organizations, including third-party vendors that share code with FreeBSD (the OpenBSD and NetBSD projects, Apple, and other vendors deriving software from FreeBSD, as well as the Linux vendor security list), as well as organizations that track vulnerabilities and security incidents, such as CERT. Frequently vulnerabilities may extend beyond the scope of the FreeBSD implementation, and (perhaps less frequently) may have broad implications for the global networking community. Under such circumstances, the Security Officer may wish to disclose vulnerability information to these other organizations: if you do not wish the Security Officer to do this, please indicate so explicitly in any submissions.

Submitters should be careful to explicitly document any special information handling requirements.

If the submitter of a vulnerability is interested in a coordinated disclosure process with the submitter and/or other vendors, this should be indicated explicitly in any submissions. In the absence of explicit requests, the FreeBSD Security Officer will select a disclosure schedule that reflects both a desire for timely disclosure and appropriate testing of any solutions. Submitters should be aware that if the vulnerability is being actively discussed in public forums (such as bugtraq), and actively exploited, the Security Officer may choose not to follow a proposed disclosure timeline in order to provide maximum protection for the user community.

Submitters should be aware that the FreeBSD Project is an open source project, and source revision control information for every change made to the FreeBSD source tree is publicly accessible. If a disclosure schedule is provided, it should take into account both the official release of advisory, patch, and update information, as well as initial inclusion of fixes in the FreeBSD source tree. There is necessarily a lag between the inclusion of fixes in the tree and the generation and releases of advisories, patches, and binary updates, as the source control system is used to generate them.

Submissions may be protected using PGP. If desired, responses will also be protected using PGP.

FreeBSD Security Advisories

The FreeBSD Security Officer provides security advisories for several branches of FreeBSD development. These are the -STABLE Branches and the Security Branches. (Advisories are not issued for the -CURRENT Branch.)

There is usually only a single -STABLE branch, although during the transition from one major development line to another (such as from FreeBSD 4.x to 5.x), there is a time span in which there are two -STABLE branches. The -STABLE branch tags have names like RELENG_4. The corresponding builds have names like FreeBSD 4.6-STABLE.
Each FreeBSD Release has an associated Security Branch. The Security Branch tags have names like RELENG_4_6. The corresponding builds have names like FreeBSD 4.6-RELEASE-p7.

Each branch is supported by the Security Officer for a limited time only, typically through 12 months after the release. The estimated lifetimes of the currently supported branches are given below. The Estimated EoL (end-of-life) column gives the earliest date on which that branch is likely to be dropped. Please note that these dates may be extended into the future, but only extenuating circumstances would lead to a branch's support being dropped earlier than the date listed.

Branch	Release	Estimated EoL
RELENG_4	n/a	December 31, 2003
RELENG_4_6	4.6-RELEASE	May 31, 2003
RELENG_4_7	4.7-RELEASE	September 30, 2003
RELENG_4_8	4.8-RELEASE	March 31, 2004
RELENG_5_0	5.0-RELEASE	June 30, 2003

Older releases are not maintained and users are strongly encouraged to upgrade to one of the supported releases mentioned above.

Like all development efforts, security fixes are first brought into the FreeBSD-current branch. After a couple of days and some testing, the fix is retrofitted into the supported FreeBSD-stable branch(es) and an advisory is then sent out.

Some statistics about advisories released during 2002:

44 advisories of varying severity were issued for the base system.
12 advisories described vulnerabilities found only in FreeBSD. The remaining 32 were problems shared with at least one other OS (often due to shared code).
6 security notices were issued, covering a total of 95 issues in optional third party applications included in the Ports Collection.

Advisories are sent to the following FreeBSD mailing lists:

FreeBSD-security-notifications@FreeBSD.org
FreeBSD-security@FreeBSD.org
FreeBSD-announce@FreeBSD.org

Advisories are always signed using the FreeBSD Security Officer PGP key and are archived, along with their associated patches, at our FTP CERT repository. At the time of this writing, the following advisories are currently available (note that this list may be a few days out of date - for the very latest advisories please check the FTP site):

FreeBSD 4.8-RELEASE released.

FreeBSD 5.0-RELEASE released.

FreeBSD 4.7-RELEASE released.

FreeBSD 4.6.2-RELEASE released.

FreeBSD 4.6-RELEASE released.

FreeBSD 4.5-RELEASE released.

FreeBSD 4.4-RELEASE released.

FreeBSD 4.3-RELEASE released.

FreeBSD Security Mailing Lists Information

If you are administering or using any number of FreeBSD systems, you should probably be subscribed to one or more of the following lists:

freebsd-security	General security related discussion
freebsd-security-notifications	Security notifications (low-volume moderated list)

Secure Programming Guidelines

Never trust any source of input, i.e. command line arguments, environment variables, configuration files, incoming TCP/UDP/ICMP packets, hostname lookups, function arguments, etc. If the length of or contents of the date received is at all subject to outside control, then the program or function should watch for this when copying it around. Specific security issues to watch for in this are:
- strcpy() and sprintf() calls from unbounded data. Use strncpy and snprintf() when the length is known (or implement some other form of bounds-checking when the length is unknown). In fact, never ever use gets() or sprintf(), period. If you do - we will send evil dwarfs after you.
- If you have to check the user input so it does not contain bad characters of some sort, do NOT check for those bad characters. Instead simply verify that it consists ONLY of those characters that you do allow. In general concept is: disallow anything that is not explicitly allowed.
- Read man pages for strncpy() and strncat() calls. Be sure to understand how they work!!! While strncpy() might not append a terminating \0, strncat() on the other hand adds the \0.
- Watch for strvis() and getenv() abuse. With strvis() it is easy to get the destination string wrong, and getenv() can return strings much longer then the program might expect. These two functions are one of the key ways an attack is often made on a program, causing it to overwrite stack or variables by setting its environment variables to unexpected values. If your program reads environment variables, be paranoid. Be very paranoid!
- Ever time you use open() or stat() call - ask yourself: "What if it is a symbolic link?"
- Make sure to use mkstemp() instead of mktemp(), tempnam(), etc. Also make sure to look for races in /tmp in general, being aware that there are very few things which can be atomic in /tmp:
  - Creating a directory. This will either succeed or fail.
  - Opening a file O_CREAT | O_EXCL
  If you use mkstemp() the above cases will be properly handled for you. Hence all temp files should use mkstemp() to guarantee there is not race condition and that the permissions are correct.
- If an attacker can force packets to go/come from another arbitrary system then that attacker has complete control over the data that we get and NONE of it should be trusted.
- Never trust a configuration file is correctly formatted or that it was generated by the appropriate utility. Don't trust user input such as terminal names or language strings to be free of '/' or '../../../' if there is any chance that they can be used in a path name. Don't trust ANY paths supplied by the user when you are running setuid root.
- Look for holes or weaknesses in how data is stored. All temp files should have 600 permission in order to be protected from prying eyes.
- Do not just grep for the usual suspects in programs which run with elevated privileges. Look line by line for possible overflows in these cases since there are a lot more ways to cause buffer overflows than by abusing strcpy() and friends.
- Just because you drop privileges somewhere, it does not mean that no exploit is possible. The attacker may put the necessary code on the stack to regain the privileges before executing /bin/sh.
Do uid management. Do drop privileges as soon as possible, and really do drop them. Switching between euid and uid is NOT enough. Use setuid() when you can.
Never display configuration file contents on errors. A line number and perhaps position count is enough. This is true for all libs and for any suid/sgid program.
Tips for those reviewing existing code for security problems:
- If you are unsure of your security fixes, send them to a reviewer with whom you already have arrangements for a second glance over your code. Don't commit code you are not sure about since breaking something in the name of a security fix is rather embarrassing.
- Those without CVS commit privileges should make sure that a reviewer with such privileges is among the last to review the changes. That person will both review and incorporate the final version you would like to have go into the tree.
- When sending changes around for review, always use context or unidiff format diffs - this way diffs can be easily fed to patch(1). Do not simply send the whole files. Diffs are much easier to read and apply to local sources (especially those in which multiple, simultaneous changes may be taking place). All changes should be relative to the -current branch of development.
- Always directly test your changes (e.g. build and run the affected sources) before sending them to a reviewer. Nobody likes being sent obviously broken stuff for review, and it just makes it appear as though the submitter didn't even really look at what he was submitting (which is also hardly confidence building). If you need accounts on a machine with a specific version which you don't have available - just ask. The project has resources available for exactly such purposes.
- Note for committers: do not forget to retrofit -current patches into the -stable branch as appropriate.
- Do not needlessly rewrite code to suit your style/tastes - it only makes the reviewer's job needlessly more difficult. Do so only if there are clear reasons for it.
Look out for programs doing complex things with signal handlers. Many routines in the various libraries are not sufficiently reentrant to make this safe.
Pay special attention to realloc() usage - more often then not the function is not used correctly.
When using fixed size buffers, use sizeof() to prevent lossage when a buffer size is changed but the code which uses it isn't. For example:
```
         char buf[1024];
         struct foo { ... };
         ...
 BAD:
         xxx(buf, 1024)
         xxx(yyy, sizeof(struct foo))
 GOOD:
         xxx(buf, sizeof(buf))
         xxx(yyy, sizeof(yyy))
 
```
Be careful though with sizeof of pointers when you really want the size of where it points to!
Every time you see "char foo[###]", check every usage of foo to make sure that it can't be overflowed. If you can't avoid overflow (and cases of this have been seen), then at least malloc the buffer so that one can't walk on the stack.
Always close file descriptors as soon as you can - this makes it more likely that the stdio buffer contents will be discarded. In library routines, always set any file descriptors that you open to close-on-exec.

A useful auditing tool is the its4 port, located in /usr/ports/security/its4/. This is an automated C code auditor which highlights potential trouble-spots in the code. It is a useful first-pass tool, but should not be relied upon as being authoritative, and a complete audit should include human examination of the entire code.

For more information on secure programming techniques and resources, see the How to Write Secure Code resource center.

FreeBSD Security Tips and Tricks

There are several steps one must take to secure a FreeBSD system, or -in fact any Unix system:

+in fact any &unix; system:

Disabling potentially dangerous software
A lot of software has to be run as a special privileged user to make use of specific resources, by making the executable set-uid. An example is UUCP or PPP software that makes use of a serial port, or sendmail which has to write in the mail spool and bind to a privileged network port. When you are not using UUCP, it is of little use to have software on your system and it may be wise to disable it. Of course, this requires good knowledge of what can be thrown away and what not, as well as good indication whether or not you will want the functionality in the future.
Also some utilities you may find not useful enough to have around pose a possible security risk, like swapinfo. If you remove the set-uid bit for the executable (via 'chmod ug-s filename' command) you can always keep on using swapinfo when you're root. It is however not a good idea to strip so many sbits that you have to be root all the time.
Not only remove programs that you don't use, also remove services you don't want or need to provide. This can be done by editing the /etc/inetd.conf and /etc/rc.conf files and turning off all services you don't use.
Fixing software which has security bugs (or how to stay one step ahead of crackers)
Make sure you are subscribed to various FreeBSD Security mailing lists so you get updates on security bugs and fixes. Apply the fixes immediately.
Backups - repair your system if a security breach does occur
Always have backups and a clean version of the operating system (e.g. on CD-Rom). Make sure your backups do not contain corrupted data or data modified by attackers.
Install software to watch the state of the system
Programs like the tcp wrappers and tripwire (both in packages/ports) can help you to monitor activity on your system. This makes it easier to detect break-ins. Also read outputs of the /etc/security scripts which are run daily and mailed to the root account.
Educating the people who work on the system
Users should know what they are doing. They should be told to never give out their password to anyone and to also use hard-to-guess passwords. Let them understand that the security of the system/network is partly in their hands.

There is also a FreeBSD Security How-To available which provides some advanced tips on how to improve security of your system. You can find it at http://www.FreeBSD.org/~jkb/howto.html.

Security is an ongoing process. Make sure you are following the latest developments in the security arena.

What to do when you detect a security compromise

Determine the level of the security breach
What privileges did the attacker get? Did the attacker manage to get root access? Did the attacker only manage to get user level access?
Determine if the state of system (kernel or userland) has been tampered with
What software has been tampered with? Was new kernel installed? Were any of the system binaries (such as telnetd, login, etc) modified? If you believe an attacker could have done any tampering with an OS, you may want to re-install the operating system from a safe medium.
Find out how the break-in was done
Did the break-in occur via a well-known security bug? If that is the case, make sure to install the correct patches. Was the break-in successful due to a misconfiguration? Was the break-in result of a new bug? If you believe the break-in occurred via a new bug, you should warn the FreeBSD Security Officer.
Fix the security hole
Install new software or apply patches to the old one in order to fix the problems. Disable any compromised accounts.
Other resources
CERT also offers detailed information on what steps to take in case of a system compromise.

Other Related Security Information

The COAST archive contains a huge collection of security related materials.
The Center for Education and Research in Information Assurance and Security (CERIAS) is the place to start looking for security related materials. It contains hundreds of useful security pointers. Everything you always wanted to know about security... and more.
The various CERT teams such as http://www.cert.org and http://www.auscert.org.au.
Mailing lists such as Bugtraq and Firewall Wizards.

&footer diff --git a/en/smp/index.sgml b/en/smp/index.sgml index eab818578b..f666380644 100644 --- a/en/smp/index.sgml +++ b/en/smp/index.sgml @@ -1,1911 +1,1911 @@ - + %includes; Done"> In progress"> Stalled"> Not Started"> Resolved"> Unresolved"> %developers; ]> &header;

Project Goal
Project Plan
Resources and Links
Subsystems and Staffing
Tasks
Known Issues
News

Project Goal

The FreeBSD SMP project, often referred to as SMPng (SMP next generation), is focused on implementing fine-grained SMP support for the FreeBSD kernel. It debuted in 5.0-RELEASE in January of 2003. Due to FreeBSD's history, this is much like trying to fit a square peg into a round hole, and as such, the intermediate results aren't pretty in many ways. We are specifically not attempting to rewrite the kernel from scratch, nor are we on a crusade to fix all the architectural nits currently present in the kernel. This is a pragmatic project rather than a theoretical one.

Project Plan

This web page contains information related to the effort to improve SMP support in FreeBSD. In general, this project uses what it can from the BSD/OS 5.0 development kernel, and re-implements what cannot be directly used due to divergence in the code bases.

As with any free software project, a detailed schedule is not possible. We expect to have significant performance and stability issues that need to be worked through over the first several months of the project, though every effort will be made to keep -current running as well as possible.

The task list below is not intended to be complete, but does represent a set of relevant and/or important components of the overall work. The "Responsible" field identifies a developer who has expressed willingness to be responsible for completing the identified task; this doesn't preclude others working on it, but suggests that coordination with the responsible party might be appropriate so as to avoid unnecessary duplication of work, and to maximize forward progress. If beginning work on a new area of substantial size, or one that appears unclaimed, it may be worth dropping an e-mail to the FreeBSD SMP mailing list to see if any progress has been made.

The definition of the date field varies depending on the status of a task. For completed tasks, it refers to the date completed or reported completed. For in-progress tasks, it refers to the date of the last update of the entry. For stalled tasks, it refers to the date that the task was declared stalled. For new tasks, it refers to the date the task was added to the list.

Locking down of individual device drivers is tracked at the busdma and SMPng driver conversion webpage.

Tasks are sorted first by status, then by date.

Resources and Links

SMP kernel synchronization rules.
Most SMP-related discussion takes place on the freebsd-smp mailing list. You can read more about mailing lists in the Electronic Resources chapter of the FreeBSD Handbook.
Steve Passe has been maintaining a SMP project page that contains additional information, and goes back further in time than this web page.
&a.dillon; is maintaining a web page that documents the work he is doing on the SMP project.
"Locking in the Multithreaded FreeBSD Kernel" USENIX paper by &a.jhb;.

Subsystems and Staffing

This is an incomplete list of high-level kernel subsystems and current, active staff working on SMP architecture and stability.

Subsystem	Status	Last updated	Staffing
Newbus	&status.wip;		&a.imp;
VM	&status.wip;	5 February 2003	&a.alc;
Buffer cache	&status.wip;	8 February 2003	&a.jeff;, &a.phk;
VFS	&status.wip;		&a.jeff;
Processes and thread operations	&status.wip;	5 May 2003	&a.jhb;
Scheduler	&status.wip;	5 February 2003	&a.jhb;
GEOM	&status.done;	5 February 2003	&a.phk;
File descriptors	&status.done;	5 February 2003	&a.alfred;, &a.tanimura;
TTY subsystem	&status.new;
Pipe IPC	&status.done; (except for VM optimizations)	5 February 2003	&a.alfred;
Socket structures and system calls	&status.wip;		&a.tanimura;, &a.hsu;
IPv4, IPv6	&status.wip;	5 February 2003	&a.hsu;, &a.jennifer;
Network stack infrastructure	&status.wip;	5 February 2003	&a.hsu;

Tasks

Following is an incomplete list of general tasks.

Task	Responsible	Last updated	Status
Convert the giant lock from spinning to blocking, add the scheduler lock, add per-CPU idle processes.	&a.dillon;	25 June 2000	&status.done;
Port the BSD/OS locking primitives (i386).	&a.jake;	3 July 2000	&status.done;
Implement heavy-weight interrupt threads (i386).	&a.grog;	3 August 2000	&status.done;
Rewrite the low level interrupt code (i386 UP).	&a.grog;	3 August 2000	&status.done;
Demonstrated reasonable stability (self-hosted buildworld) (i386 UP).	-smp developers	12 August 2000	&status.done;
Port the BSD/OS locking primitives (alpha).	&a.dfr;	24 August 2000	&status.done;
Stub out (disable) spl()s.	&a.grog;	30 August 2000	&status.done;
Port the BSD/OS ktr code.	&a.grog;, &a.jhb;	30 August 2000	&status.done;
Rewrite the low level interrupt code (i386 SMP).	&a.jhb;	1 September 2000	&status.done;
Demonstrated reasonable stability (self-hosted buildworld) (i386 SMP).	-smp developers	6 September 2000	&status.done;
Demonstrated reasonable stability (self-hosted buildworld) (alpha).	-smp developers	6 September 2000	&status.done;
Make malloc and friends thread-safe.	&a.jasone;	10 September 2000	&status.done;
Implement msleep(), make tsleep() an msleep() wrapper.	&a.jake;	11 September 2000	&status.done;
Make fxp driver thread-safe.	&a.cp;	17 September 2000	&status.done;
Make mbuf's thread-safe.	&a.bmilekic;	29 September 2000	&status.done;
Lock manager re-work.	&a.jasone;	3 October 2000	&status.done;
Implement heavy-weight interrupt threads (alpha).	&a.jhb;, &a.dfr;	5 October 2000	&status.done;
Rewrite the low level interrupt code (alpha).	&a.dfr;, &a.jhb;	5 October 2000	&status.done;
Process accounting.	&a.tegge;, &a.jhb;	5 October 2000	&status.done;
Make ethernet drivers thread-safe.	&a.wpaul;	15 October 2000	&status.done;
Make the mutex headers mostly machine-independent.	&a.jhb;	20 October 2000	&status.done;
Rename SMP_DEBUG to MUTEX_DEBUG.	&a.jhb;	20 October 2000	&status.done;
Give each soft interrupt its own thread.	&a.cp;	25 October 2000	&status.done;
Make sf_bufs (sendfile(2)) thread-safe.	&a.bmilekic;	5 November 2000	&status.done;
Make the witness code work correctly.	&a.jhb;	18 November 2000	&status.done;
Split the ktr-specific code out of db_interface.c.	&a.jhb;	15 December 2000	&status.done;
Convert the sio driver to using a spin mutex.	&a.jhb;	18 December 2000	&status.done;
Implement condition variables.	&a.jake;, &a.jasone;	15 January 2001	&status.done;
Add a flag to mtx_init() (MTX_RECURSE) that denotes whether a mutex is allowed to recurse.	&a.bmilekic;	19 January 2001	&status.done;
Make the zone allocator thread-safe.	&a.des;	21 January 2001	&status.done;
Convert simplelocks to mutexes.	&a.jasone;	24 January 2001	&status.done;
Make kernel preemptive with respect to interrupts.	&a.jake;	31 January 2001	&status.done;
Cleanup of mutex API.	&a.bmilekic;	8 February 2001	&status.done;
Remove COM_LOCK.	&a.markm;	11 February 2001	&status.done;
Merge various scheduling classes into one run queue. Modify scheduler to support preemptable kernel.	&a.jake;	11 February 2001	&status.done;
Make priority propagation work correctly.	&a.jake;	11 February 2001	&status.done;
Make most of the interrupt thread code MI and shared between hardware and software interrupts.	&a.jhb;	18 February 2001	&status.done;
Add protection to struct jail and jail-related functionality.	&a.rwatson;	20 February 2001	&status.done;
Implement sx (shared/exclusive) locks.	&a.jasone;	5 March 2001	&status.done;
Generalize/improve witness to handle more complex locking primitives (mtx, sx).	&a.jhb;	28 March 2001	&status.done;
Convert the allproc and proctree locks from lockmgr locks to sx locks.	&a.jhb;	28 March 2001	&status.done;
Make mbuf system use condition variables instead of msleep()/wakeup().	&a.bmilekic;	2 April 2001	&status.done;
Remove <sys/mutex.h> includes from other kernel headers such as <vm/vm_zone.h>, <sys/resourcevar.h>, <sys/ucred.h>, and <sys/mbuf.h>.	&a.markm;	15 May 2001	&status.done;
Cleanup the various mp_machdep.c's, unify various SMP API's such as IPI delivery, etc.	&a.jhb;	15 May 2001	&status.done;
Make most of the forward_* and forwarded_* functions MI.	&a.jhb;	15 May 2001	&status.done;
Complete the MD support for SMP on the Alpha platform.	&a.gallatin;, &a.dfr;, &a.jhb;	15 May 2001	&status.done;
Convert select() to use condition variables.	&a.tanimura;	15 May 2001	&status.done;
Add a "giant" lock around the VM subsystem.	&a.alfred;	13 June 2001	&status.done;
Introduce a modified slab allocator for the mbuf subsystem.	&a.bmilekic;	21 June 2001	&status.done;
Add a witness_assert() function to handle lock assertions.	&a.jhb;	27 June 2001	&status.done;
Extend sx locks to support try lock operations.	&a.jhb;	27 June 2001	&status.done;
Document KTR.	&a.jhb;	28 June 2001	&status.done;
Make fork_return, fork_exit, ast, and userret MI.	&a.jhb;	29 June 2001	&status.done;
Make sched_lock's savecrit a per-process property saved and restored in mi_switch and initialized in fork_exit.	&a.jhb;	30 June 2001	&status.done;
Make ast() loop.	&a.jhb;	10 August 2001	&status.done;
Add upgrade/downgrade sx lock operations.	Alexander Kabaev, &a.jasone;	13 August 2001	&status.done;
Implement semaphores.	&a.jasone;	14 August 2001	&status.done;
Add support for upgrade/downgrades in witness.	&a.jhb;	23 August 2001	&status.done;
Make most of cpu_wait() and cpu_exit() MI.	&a.peter;	9 September 2001	&status.done;
Split NFS into client and server.	&a.peter;	18 Oct 2001	&status.done;
Lock taskqueues.	&a.arr;, &a.jhb;	25 October 2001	&status.done;
Add a per-thread ucred reference.	&a.jhb;	25 October 2001	&status.done;
Make most of the per-CPU stuff MI.	&a.jhb;	11 December 2001	&status.done;
Make critical section saved state per-thread instead of per-lock so that interlocking spin locks work properly.	&a.jhb;	17 December 2001	&status.done;
Replace the APIC-specific imen_mtx with a MI-named icu_lock to protect interrupt controllers and associated data within the kernel for both i386 and alpha.	&a.jhb;	20 December 2001	&status.done;
Use the per-thread critical section nesting level in the mutex and interrupt thread code to automatically determine when to not preempt. This makes the MTX_NOSWITCH, SWI_SWITCH, and SWI_NOSWITCH flags obsolete as the kernel will be able to figure out the proper behavior on its own.	&a.jhb;	5 January 2002	&status.done;
Lock struct filedesc and struct file.	&a.tanimura;, &a.alfred;	12 January 2002	&status.done;
Lock struct pgrp, struct session, and struct sigio.	&a.tanimura;	23 February 2002	&status.done;
Lock pipe implementation, but not sigio/fown, VM interactions	&a.alfred;	27 February 2002	&status.done;
Move to explicit reference counting for soft vnode references.	&a.phk;	8 March 2002	&status.done;
Initialize mutex pools early enough that sx locks can be used for VM.	&a.green;	14 March 2002	&status.done;
Place a global lock (sellock) around selinfo structures to fix a variety of lock order reversals, and make select() MP-safe.	&a.alfred;, &a.davidc;	14 March 2002	&status.done;
Push down Giant on read, write, pread, pwrite system calls, acquiring Giant in the per-subsystem fileop layer for sockets, VFS, etc.	&a.alfred;	15 March 2002	&status.done;
Lock down kernel module structures.	&a.arr;	18 March 2002	&status.done;
Lock down kernel linker globals.	&a.arr;	18 March 2002	&status.done;
Rewrite kernel memory allocator to be a slab allocator that uses per-cpu caches.	&a.jeff;	21 March 2002	&status.done;
Replace incorrect use of MD critical section API to disable interrupts with a specific interrupt disable API.	&a.imp;, &a.dfr;, &a.benno;, &a.jhb;	21 March 2002	&status.done;
Lock down access to the shared p_args "process arguments" structure through appropriate protection of that structure and references to it.	&a.mini;	31 March 2002	&status.done;
Move from flags/tsleep lock to sx locks to protect sysctl tree from updates during sysctl operations.	&a.mini;	1 April 2002	&status.done;
Create/port userland tool to manage KTR event dumps.	&a.jake;	1 April 2002	&status.done;
Create MTX_SYSINIT and SX_SYSINIT macros that allow for initializing locks that are subsystem independent.	&a.arr;	2 April 2002	&status.done;
Lock down the global securelevel variable.	&a.arr;	2 April 2002	&status.done;
Make grow_stack() MI. Possibly even a macro or inline.	&a.alc;	6 April 2002	&status.done;
Lock use of p_fd, which otherwise can result in corrupted p_fd panics during heavy operation. Start with a global, and move to per-proc locking.	&a.alfred;, &a.tanimura;	8 April 2002	&status.done;
Lock struct pargs.	&a.mini;	9 April 2002	&status.done;
Make {o,}sigreturn() MPSAFE.	&a.alc;	11 April 2002	&status.done;
Rewrite kernel memory allocator so that Giant is not required for malloc() or free().	&a.jeff;	2 May 2002	&status.done;
Replace complex shared/exclusive locking scheme in the VM system with a purely exclusive lockmgr locking scheme, simplifying locking and removing potential livelock/deadlock scenarios.	&a.green;, &a.alc;	3 May 2002	&status.done;
Push down Giant into readv/writev system calls in style of read/write/pread/pwrite once malloc no longer requires Giant in the handling of iovec structures for uio.	&a.alc;	9 May 2002	&status.done;
Push down Giant in mprotect(), minherit(), and madvise() so that it is no longer acquired and released directly.	&a.alc;	18 May 2002	&status.done;
Update suser() and p_can*() APIs to accept threads instead of processes.	&a.jhb;	18 May 2002	&status.done;
Broadly transition to td_ucred from p_ucred once KSE dependencies are in place.	&a.jhb;	18 May 2002	&status.done;
Add a witness_sleep() check to uma_zalloc() to catch code calling malloc() or uma_zalloc() while holding non-sleepable locks.	&a.jhb;	20 May 2002	&status.done;
Optimize UP support by changing spin locks to only perform critical section enter and exits.	&a.jhb;	21 May 2002	&status.done;
Make sleep mutexes spin if the current lock holder is executing on another CPU.	&a.jhb;	21 May 2002	&status.done;
Add support for the IA32 pause instruction to spin loops in locks.	&a.jhb;	21 May 2002	&status.done;
Make KTRACE write into tracefiles asynchronously.	&a.jhb;	7 June 2002	&status.done;
Remove Giant from jail(2).	&a.arr;	25 June 2002	&status.done;
Remove Giant from modnext(2), modfnext(2), modstat(2),and modfind(2).	&a.arr;	25 June 2002	&status.done;
Fix synchronization of TLB flushes and invlpg() on x86 SMP.	&a.peter;	12 July 2002	&status.done;
Make cpu_coredump MI.	&a.peter;	7 September 2002	&status.done;
Add a subsystem lock to the accounting code.	&a.arr;	11 September 2002	&status.done;
Fix SIGXPU and other #if 0'd things in mi_switch().	&a.jhb;	30 September 2002	&status.done;
Lock down TrustedBSD MAC implementation.	&a.rwatson;	11 November 2002	&status.done;
Lock eventhandlers.	&a.msmith;, &a.mini;, &a.jhb;	11 March 2003	&status.done;
Fix PHOLD() so that it blocks to guarantee PS_INMEM.	&a.jhb;	22 April 2003	&status.done;
Fix various procfs_machdep.c to not use sched_lock.	&a.jhb;	22 April 2003	&status.done;
Lock all references to process credentials and remove Giant from process credential-related system calls.	&a.jhb;	1 May 2003	&status.done;
Merge the procsig and sigacts structures, move the new sigacts structure out of the U-area and add appropriate locking.	&a.jhb;	13 May 2003	&status.done;
Remove Giant from the kill() and killpg() system calls.	&a.jhb;	13 May 2003	&status.done;
Lock struct proc.	&a.jhb;	20 February 2001	&status.wip;
Make the kernel fully preemptive.	&a.jhb;	7 September 2001	&status.wip;
Lock down the tty subsystem.	Dick Garner, Jeremy Scofield, &a.tmm;	2 April 2002	&status.wip;
Fix clock locking to be the same on all platforms.	&a.jhb;	16 November 2001	&status.wip;
Lock pipe implementation: sigio/fown-related evil	&a.alfred;	27 February 2002	&status.wip;
Make use of process locking and process reference counting to protect debugging interfaces (and procfs).	&a.jhb;	27 February 2002	&status.wip;
Make use of process locking to protect process monitoring sysctls, including those employed by 'ps' and related tools.	&a.jhb;	27 February 2002	&status.wip;
Lock down newbus infrastructure to support driver fine-graining.	&a.imp;	28 February 2002	&status.wip;
Remove the MP safe syscall flag from the syscall table and add explicit mtx_lock/unlock's of Giant to all syscalls.	&a.dillon;, &a.mux;	28 February 2002	&status.wip;
SMPng architecture document.	&a.jhb;, &a.rwatson;	28 February 2002	&status.wip;
Move to shared lock for VOP_GETATTR() to reduce blocking during frequent lightweight VFS operations. Modify namei() to provide a LOOKUP_SHARED flag to indicate when the lock required may be shared instead of exclusive.	&a.jeff;	11 March 2002	&status.wip;
Create mutex profiling tool for the kernel so as to measure contention and behavior of kernel mutexes.	&a.eivind;, &a.des;	31 March 2002	&status.wip;
Lock sysctl hierarchy and access methods.	&a.mini;	9 April 2002	&status.wip;
Document existing vm_map locking and verify it's correctness.	&a.alc;	18 May 2002	&status.wip;
Document existing vm_object locking and verify it's correctness.	&a.alc;	4 May 2002	&status.wip;
Implement generic turnstiles to use when blocking on non-sleepable locks.	&a.jhb;	23 May 2002	&status.wip;
Lock down linker_file_t structures in the kernel linker.	&a.arr;	19 June 2002	&status.wip;
Lock down the SysV IPC code.	&a.alfred;	13 August 2002	&status.wip;
Review locking strategy and correctness of VFS operations and fix up various failure modes associated with enabling VFS locking assertions.	&a.jeff;	10 December 2002	&status.wip;
Document in-vnode locking strategy, clean it up, remove interlock, switch to sx locks.	&a.jeff;	10 December 2002	&status.wip;
Implement lazy interrupt thread switching (context stealing) on i386.	&a.bmilekic;, &a.kan;	10 December 2002	&status.wip;
Implement lazy interrupt thread switching (context stealing) on sparc64.	&a.jake;	10 December 2002	&status.wip;
Switch from using lockmgr in VM to using a mutex or exclusive sxlock. Push down Giant on all VM except for vm_object/VFS and vm_page/pmap components.	&a.alc;	10 December 2002	&status.wip;
Create mechanism in cdevsw structure to protect thread-unsafe drivers.	&a.jhb;	15 May 2001	&status.stalled;
Make printf() safe to call in almost any situation to avoid deadlocks.	&a.cp;	15 May 2001	&status.stalled;
Add locking to NFS.		15 May 2001	&status.new;
Remove priority argument from tsleep(), msleep(), cv_wait().		12 January 2001	&status.new;
Reimplement kqueue using condition variables.	&a.jlemon;	15 March 2001	&status.new;
Conditionalize atomic ops in the SMP code that are used for debugging statistics.	&a.peter;	15 March 2001	&status.new;
Add a new witness check for exiting processes to verify that an exiting process holds no locks.	&a.jhb;	13 June 2001	&status.new;
Specify priorities for condition variables, semaphores, and sx locks.		7 September 2001	&status.new;
Axe schedpu() in favor of event driven priority updates as much as possible.		7 September 2001	&status.new;
Fix *hold (e.g. crhold) to return reference to object.		7 September 2001	&status.new;
Add witness checking for lockmgr locks.		7 September 2001	&status.new;
Add ICU spin locks on ia64.		4 January 2002	&status.new;
Fast-path push-down of Giant for VOP_READ() and VOP_WRITE().		25 February 2002	&status.new;
Lock contention measurement tool to measure heat of various locks, including Giant, and permit more directed performance and locking strategy optimization.		25 February 2002	&status.new;
Push the grabbing of Giant into Linux i386 ABI system calls.		25 February 2002	&status.new;
Push the grabbing of Giant into Linux AXP ABI system calls.		25 February 2002	&status.new;
Push the grabbing of Giant into SVR4 i386 ABI system calls.		25 February 2002	&status.new;
Push the grabbing of Giant into OSF/1 AXP ABI system calls.		25 February 2002	&status.new;
Push the grabbing of Giant into IBCS i386 ABI system calls.		25 February 2002	&status.new;
Lock pipe implementation: VM optimizations.		27 February 2002	&status.new;
Expand mutex profiling tool to also profile sx locks.	&a.eivind;, &a.des;	1 April 2002	&status.new;
Implement atomic_fetchadd() for int's and long's with acq and rel versions.		23 May 2002	&status.new;
Implement a simple reference count API using atomic operations and use this to replace locks that just protect a reference count.		23 May 2002	&status.new;
Implement a sleep queue abstraction to be used by both msleep() and condition variables. This new abstraction should use a hash table of sleep queues with a spin lock on each sleep queue chain similar to turnstile chain locks to make sched_lock finger grained.	&a.jhb;	23 May 2002	&status.new;
Add a witness_sleep() check to copyin/out() and s/fuword().	&a.jhb;	7 June 2002	&status.new;
Split witness_lock() into witness_checkorder() and witness_lock(). witness_checkorder() would be called before acquiring a lock to increase the changes of detecting and warning about a reversal prior to deadlocking. witness_lock() would simply update witness' internal state to note that a lock has been acquired.	&a.jhb;	7 June 2002	&status.new;

This table lists the todo subtasks for multithreading the network stack.

- +

Task	Responsible	Last updated	Status
Protect network interface queues.	&a.jlemon;	24 November 2000	&status.done;
Lock up IP.	&a.jennifer;, &a.hsu;	10 June 2002	&status.done;
Lock up TCP.	&a.jennifer;, &a.hsu;	10 June 2002	&status.done;
Lock up UDP.	&a.jennifer;, &a.hsu;	10 June 2002	&status.done;
Lock ifaddr reference counts.	&a.hsu;	18 December 2002	&status.done;
Lock up syncache.	&a.hsu;	19 December 2002	&status.done;
Lock up ifnet list.	&a.hsu;	21 December 2002	&status.done;
Lock radix trees.	&a.hsu;	23 December 2002	&status.done;
Lock up ARP.	&a.hsu;	16 January 2003	&status.done;
Lock routing entries.		29 January 2003	&status.wip;
Lock up raw IP.	&a.hsu;	27 February 2003	&status.wip;
Lock divert sockets.	&a.hsu;	27 February 2003	&status.wip;
Lock up Unix domain protocols.	Lock up &unix; domain protocols.	&a.hsu;	27 February 2003	&status.wip;
Lock up IPv6.		27 February 2003	&status.wip;
Lock struct ifnet.		19 January 2001	&status.new;
Lock down struct socket.	&a.tanimura;	21 April 2002	&status.wip;
Reduce contention upon locking a socket buffer by replacing tsleep() and wakeup() with a condvar.	&a.tanimura;	21 April 2002	&status.new;

Known Issues

Issue	Last updated	Status
Idle processor time is not charged to the idle processes.	20 September 2000	&status.resolved;
microuptime creeps backwards.	4 October 2000	&status.resolved;
microuptime() went backwards	4 October 2000	&status.resolved;
Process accounting is not accurate (the more CPUs, the closer to correct it is).	5 October 2000	&status.resolved;
M_DEVBUF is probably the wrong memory pool for interrupt stuff and we should think about creating a new malloc pool for that stuff.	9 February 2001	&status.resolved;
PC card eject panics due to a race condition in the interrupt thread code.	15 March 2001	&status.resolved;
SMP x86 boxes are seeing NCPU * 100 clk interrupts and NCPU * 128 rtc interrupts.	15 May 2001	&status.resolved;
Witness will infinitely recurse when it acquires Giant after sleeping with a sleepable lock.	27 June 2001	&status.resolved;
Serial gdb does not work if boot_ddb and boot_gdb options are specified.	14 July 2002	&status.resolved;
Serial gdb does not work at 115200 baud.	14 July 2002	&status.resolved;
Serial gdb never regains control once 'cont' has been entered.	14 July 2002	&status.resolved;
Profiling is broken.	20 February 2001	&status.unresolved;
jail_sysvipc_allowed is checked in an unsafe manner in the SYSV IPC syscalls.	5 March 2002	&status.unresolved;

News

The remainder of this page is structured as a reverse-chronological log.

13 January 2002

A status report was sent to the -smp mailing list.

15 May 2001

&a.grog; has made his USENIX paper available, which he will present in Boston at the end of June.

22 March 2001

A status report was sent to the -smp mailing list.

5 March 2001

A status report was sent to the -smp mailing list.

24 January 2001

A status report was sent to the -smp mailing list.

12 January 2001

A status report was sent to the -smp mailing list.

11 October 2000

&a.jhb; and &a.cp; came up with a preliminary list of rules that should be followed when working on kernel synchronization.

8 September 2000

Here's a copy of an article sent to BSDtoday and linked at Daemon News.

6 September 2000

The SMP code has been committed. All further work is being done in cvs rather than with patches.
An updated patch is available for download. This patch is probably what will actually get committed.

5 September 2000

An updated patch is available for download. This patch makes rtc a fast interrupt, uses locked instructions for mutexes in MP kernels, and corrects mtx_*() linkage within modules.

1 September 2000

The code is working for the most part now on i386 (UP and MP). Some additional coding is still necessary for the alpha, which is being done now.

30 August 2000

Updated patches for i386 and alpha are available here.

12 August 2000

Updated patches for i386 are available here. Process accounting still doesn't work correctly, but a number of other improvements have been made.

3 August 2000

Patches with functional heavy-weight threads for the i386 platform are available here. There are a couple of minor issues with this patch set. Specifically, process accounting doesn't work correctly.

6 July 2000

Sheldon Hearn has prepared a mutex(9) man page based on the BSD/OS one, which is available here.

5 July 2000

&a.jake; put an updated patch here.

3 July 2000

&a.jake; has the BSD/OS lock code working now, and has incorporated the pertinent portions of &a.dillon;'s patches (idle processes, some of the schedlock changes, etc.). His patch set is available here.

26 June 2000

&a.cp; has provided the PostScript versions of his presentation slides for the first day and second day of the SMP meeting.

25 June 2000

Here's a copy of the SMP meeting summary that was posted to the -smp mailing list.

19 June 2000

Here's a copy of the SMP project announcement that was posted to the -current mailing list.

&footer;

Using the FreeBSD web site

Learning about FreeBSD

Learning about UNIX

Learning about &unix;

Learning about the X Window System

Helping other people

Documentation

Applications

Networking

File system

Kernel, security

Device drivers

Architecture

Misc

FreeBSD Search Services

Web pages (including FAQ and Handbook)

Search for:

Mailing list archives

Search for:

In archive(s):

General Archives

System Use and Administration

Developer

Limited lists

Introduction

Table of Contents

The FreeBSD Security Officer and the Security Officer Team

Information handling policies

FreeBSD Security Advisories

FreeBSD Security Mailing Lists Information

Secure Programming Guidelines

FreeBSD Security Tips and Tricks

What to do when you detect a security compromise

Other Related Security Information

Contents

Project Goal

Project Plan

Resources and Links

Subsystems and Staffing

Tasks

Known Issues

News