From owner-freebsd-doc Mon Feb 19 11:25:11 2001 Delivered-To: freebsd-doc@freebsd.org Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id B49A537B503 for ; Mon, 19 Feb 2001 11:24:59 -0800 (PST) Received: (from peter@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f1JJOxb69114 for freebsd-doc@freebsd.org; Mon, 19 Feb 2001 11:24:59 -0800 (PST) (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 19 Feb 2001 11:24:59 -0800 (PST) Message-Id: <200102191924.f1JJOxb69114@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: FreeBSD doc list Subject: Current unassigned doc problem reports Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Current FreeBSD problem reports The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. Bugs can be in one of several states: o - open A problem report has been submitted, no sanity checking performed. a - analyzed The report has been examined by a team member and evaluated. f - feedback The problem has been solved, and the originator has been given a patch or a fix has been committed. The PR remains in this state pending a response from the originator. s - suspended The problem is not being worked on. This is a prime candidate for somebody who is looking for a project to do. If the problem cannot be solved at all, it will be closed, rather than suspended. c - closed A problem report is closed when any changes have been integrated, documented, and tested. Critical problems Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2000/07/18] docs/20028 doc ASCII docs should reflect tags o [2000/12/28] docs/23910 doc Handbook Chapter 14. Sound -- some fixes o [2001/01/05] docs/24083 doc change layout and content of kernel build o [2001/01/15] docs/24363 doc lack of explanation 4 problems total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- a [1998/07/31] docs/7456 doc dialog(3) man page outdated o [1999/04/07] docs/10997 doc Problem with query-pr-summary.cgi o [1999/09/25] docs/13950 doc webpage idea o [1999/09/25] docs/13967 doc FreeBSD Related Publications in Korea o [1999/10/06] docs/14158 doc md5(1) manpage should not claim the md5 a o [1999/10/27] docs/14565 doc ioctl() codes for device type `fd' (flopp f [2000/03/20] docs/17521 doc Proposed FAQ on assembly programming o [2000/03/25] docs/17598 doc installworld over NFS documentation no lo o [2000/04/03] kern/17774 doc stray irq7 o [2000/05/03] docs/18379 doc Information on SSH hard to find in Handbo o [2000/05/19] docs/18674 doc ntptime.htm and ntptime.8 o [2000/06/05] docs/19010 doc Bad144 obsoletion by 4.0 is undocumented; o [2000/06/23] docs/19481 doc Serial Communications chapter in Handbook o [2000/07/17] docs/19981 doc Indonesian translations o [2000/08/04] docs/20400 doc Building a kernel with debugging info sec o [2000/08/10] docs/20528 doc sysconf(3) manpage doesn't mention posix. o [2000/08/20] docs/20738 doc correction and modification to clocks(7) o [2000/08/23] docs/20794 doc Request 2 good documents under people.fre o [2000/10/07] docs/21826 doc ARP proxy feature lacks documentation o [2000/10/10] docs/21896 doc Mini-HOWTO for stp driver o [2000/10/26] docs/22333 doc share/doc/smm/07.lpd building moved in 3. o [2000/11/01] docs/22470 doc man 3 msgrcv's BUGS section needs updatin o [2000/11/08] docs/22701 doc lists missing from search options o [2000/11/11] docs/22778 doc Typo's in About.txt-Layout.txt o [2000/11/14] docs/22861 doc newsyslog man page is misleading and inco o [2000/12/01] docs/23230 doc missing index.html links o [2000/12/03] docs/23251 doc exports(5) man page erroneous in 4.2-STAB o [2000/12/04] docs/23292 doc /etc/dumpdates is not documented in secti o [2000/12/06] docs/23324 doc add information to FAQ on how to use whee o [2000/12/06] docs/23342 doc Inaccuracy of the dialup-firewall tutoria o [2000/12/11] docs/23488 doc A manpage for section 7 regarding a Toron o [2000/12/14] docs/23559 doc missing manpage for hsearch libc function o [2000/12/22] docs/23767 doc ifconfig(8) manual page does not document o [2001/01/02] docs/24035 doc ptrace(2) PT_STEP incorrect documentation o [2001/01/13] docs/24305 doc man page syscons has reference to non exi o [2001/01/24] docs/24622 doc Man page of "ugen" missing. o [2001/01/26] docs/24662 doc too many questions about source managemen o [2001/01/31] docs/24751 doc [PATCH] Digest list descriptions are out o [2001/02/01] docs/24786 doc missing FILES descriptions in sa(4) o [2001/02/02] docs/24802 doc fcntl man page does not specify what happ o [2001/02/02] docs/24809 doc info on X and securelevels o [2001/02/03] docs/24839 doc fix ether.bridge o [2001/02/05] docs/24869 doc Some text elf.5 is duplicated o [2001/02/05] docs/24887 doc "make -j# installworld" can (will?) fail o [2001/02/05] docs/24888 doc [PATCH] New FAQ entry about inappropriate o [2001/02/06] docs/24923 doc 4.2 Release Errata page has no informatio o [2001/02/11] docs/25000 doc matcd(4) SYNOPSIS is wrong o [2001/02/11] docs/25016 doc symlink(7) manpage says symlinks have no o [2001/02/12] docs/25053 doc kld(4) manpage is obsolete for -current o [2001/02/15] docs/25124 doc No man pages for quota.user(5) and/or quo o [2001/02/15] docs/25126 doc minor nits in whatis(1) command o [2001/02/16] docs/25134 doc Kernel USER_LDT option help incomplete o [2001/02/16] docs/25142 doc my e-mail address is out of date in the l o [2001/02/17] docs/25164 doc makewhatis(1) seems to be fouling up o [2001/02/18] docs/25184 doc Clean last tracks of CIRCLEQ from queue.3 o [2001/02/18] docs/25188 doc [PATCH] getaddrinfo(3) manual page has an 56 problems total. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message