From pgj at FreeBSD.org  Fri Aug  1 19:05:30 2008
From: pgj at FreeBSD.org (pgj@FreeBSD.org)
Date: Fri Aug  1 19:05:38 2008
Subject: docs/126030: [patch] updates to developers handbook: policies
	section
Message-ID: <200808011905.m71J5TCM034279@freefall.freebsd.org>

Synopsis: [patch] updates to developers handbook: policies section

Responsible-Changed-From-To: freebsd-doc->pgj
Responsible-Changed-By: pgj
Responsible-Changed-When: Fri Aug 1 19:03:49 UTC 2008
Responsible-Changed-Why: 
Grab.

http://www.freebsd.org/cgi/query-pr.cgi?pr=126030
From pgj at FreeBSD.org  Fri Aug  1 19:06:46 2008
From: pgj at FreeBSD.org (pgj@FreeBSD.org)
Date: Fri Aug  1 19:06:53 2008
Subject: docs/126146: [patch] Updates to the developer-handbook: remove
	section on DMA
Message-ID: <200808011906.m71J6kEx034332@freefall.freebsd.org>

Synopsis: [patch] Updates to the developer-handbook: remove section on DMA

Responsible-Changed-From-To: freebsd-doc->pgj
Responsible-Changed-By: pgj
Responsible-Changed-When: Fri Aug 1 19:05:47 UTC 2008
Responsible-Changed-Why: 
Snatch.

http://www.freebsd.org/cgi/query-pr.cgi?pr=126146
From grady at ztmc.net  Sat Aug  2 00:13:20 2008
From: grady at ztmc.net (Grady)
Date: Sat Aug  2 00:13:27 2008
Subject: We are interested in purchasing advertising on freebsd.org.ru
Message-ID: <1217634361_19656@gwa4>


   	   freebsd.org.ru?

   Thank you,

   Grady
   Marketing Manager
   ZTMC, Inc.
   grady@ztmc.net

   	I personally visited freebsd.org.ru. If you have re   information in error, or are not interested in accepting adve   on your site, simply respond to this email with "do not contact".
From remko at FreeBSD.org  Sat Aug  2 12:52:32 2008
From: remko at FreeBSD.org (remko@FreeBSD.org)
Date: Sat Aug  2 12:52:38 2008
Subject: docs/125546: [patch] ktrace(2) contains outdated struct
	ktr_header
Message-ID: <200808021252.m72CqWAW063161@freefall.freebsd.org>

Synopsis: [patch] ktrace(2) contains outdated struct ktr_header

State-Changed-From-To: patched->closed
State-Changed-By: remko
State-Changed-When: Sat Aug 2 12:52:32 UTC 2008
State-Changed-Why: 
Committed. Thanks!

http://www.freebsd.org/cgi/query-pr.cgi?pr=125546
From remko at FreeBSD.org  Sat Aug  2 13:42:38 2008
From: remko at FreeBSD.org (remko@FreeBSD.org)
Date: Sat Aug  2 13:42:49 2008
Subject: docs/125535: Errors in ahc(4) man page
Message-ID: <200808021342.m72DgXvb067822@freefall.freebsd.org>

Synopsis: Errors in ahc(4) man page

State-Changed-From-To: patched->closed
State-Changed-By: remko
State-Changed-When: Sat Aug 2 13:42:33 UTC 2008
State-Changed-Why: 
Committed. Thanks!

http://www.freebsd.org/cgi/query-pr.cgi?pr=125535
From dfilter at FreeBSD.ORG  Sat Aug  2 13:50:04 2008
From: dfilter at FreeBSD.ORG (dfilter service)
Date: Sat Aug  2 13:50:16 2008
Subject: docs/125546: commit references a PR
Message-ID: <200808021350.m72Do4FA067965@freefall.freebsd.org>

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

From: dfilter@FreeBSD.ORG (dfilter service)
To: bug-followup@FreeBSD.org
Cc:  
Subject: Re: docs/125546: commit references a PR
Date: Sat,  2 Aug 2008 13:40:59 +0000 (UTC)

 remko       2008-08-02 13:40:14 UTC
 
   FreeBSD src repository
 
   Modified files:        (Branch: RELENG_7)
     lib/libc/sys         ktrace.2 
   Log:
   SVN rev 181179 on 2008-08-02 13:40:14Z by remko
   
   MFC r180491
   
     Update the ktr_header structure, which changed over time.
   
     PR:             125546
     Submitted by:   Mateusz Guzik <mjguzik at gmail dot com>
     MFC after:      3 days
   
   Revision  Changes    Path
   1.25.2.1  +4 -4      src/lib/libc/sys/ktrace.2
 _______________________________________________
 cvs-all@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/cvs-all
 To unsubscribe, send any mail to "cvs-all-unsubscribe@freebsd.org"
 
From dfilter at FreeBSD.ORG  Sat Aug  2 13:50:06 2008
From: dfilter at FreeBSD.ORG (dfilter service)
Date: Sat Aug  2 13:50:16 2008
Subject: docs/125535: commit references a PR
Message-ID: <200808021350.m72Do6go067976@freefall.freebsd.org>

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

From: dfilter@FreeBSD.ORG (dfilter service)
To: bug-followup@FreeBSD.org
Cc:  
Subject: Re: docs/125535: commit references a PR
Date: Sat,  2 Aug 2008 13:42:45 +0000 (UTC)

 remko       2008-08-02 13:42:28 UTC
 
   FreeBSD src repository
 
   Modified files:        (Branch: RELENG_7)
     share/man/man4       ahc.4 
   Log:
   SVN rev 181180 on 2008-08-02 13:42:28Z by remko
   
   MFC r180492
   
     More explicitly mention that we support the 2920C with the ahc driver.
   
     PR:             125535
     Submitted by:   Bob Bishop <rb at gid dot co dot uk>
     MFC after:      3 days
   
   Revision  Changes    Path
   1.39.2.1  +2 -2      src/share/man/man4/ahc.4
 _______________________________________________
 cvs-all@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/cvs-all
 To unsubscribe, send any mail to "cvs-all-unsubscribe@freebsd.org"
 
From trhodes at FreeBSD.org  Sun Aug  3 16:32:30 2008
From: trhodes at FreeBSD.org (trhodes@FreeBSD.org)
Date: Sun Aug  3 16:32:37 2008
Subject: docs/124949: Discrepancy between handbook and example hosts
	file for localhost configuration
Message-ID: <200808031632.m73GWU8H048418@freefall.freebsd.org>

Synopsis: Discrepancy between handbook and example hosts file for localhost configuration

State-Changed-From-To: open->closed
State-Changed-By: trhodes
State-Changed-When: Sun Aug 3 16:31:00 UTC 2008
State-Changed-Why: 
I have updated the example in the handbook, thanks for
bringing this to our attention.


Responsible-Changed-From-To: freebsd-doc->trhodes
Responsible-Changed-By: trhodes
Responsible-Changed-When: Sun Aug 3 16:31:00 UTC 2008
Responsible-Changed-Why: 
Over to me.

http://www.freebsd.org/cgi/query-pr.cgi?pr=124949
From E-Cards at hallmark.com  Sun Aug  3 19:19:15 2008
From: E-Cards at hallmark.com (hallmark.com)
Date: Sun Aug  3 19:19:22 2008
Subject: You've received A Hallmark E-Card!
Message-ID: <200808031817.m73IHDG08858@www.ldh.co.jp>


   [1]Hallmark.com [2]Shop Online [3]Hallmark Magazine [4]E-Cards & More
   [5]At Gold Crown 

         You have recieved A Hallmark E-Card.

     Hello!
   You have recieved a Hallmark E-Card.
   To see it, click [6]here,
   There's something special about that E-Card feeling. We invite you to
   make a friend's day and [7]send one.
   Hope to see you soon,
   Your friends at Hallmark
   Your privacy is our priority. Click the "Privacy and Security" link at
   the bottom of this E-mail to view our policy.

      [8]Hallmark.com | [9]Privacy & Security | [10]Customer Service |
                             [11]Store Locator

References

   1. http://www.hallmark.com/
   2. http://www.hallmark.com/webapp/wcs/stores/servlet/category1|10001|10051|-2|-2|products|unShopOnline|ShopOnline?lid=unShopOnline
   3. http://www.hallmark.com/webapp/wcs/stores/servlet/article|10001|10051|/HallmarkSite/HallmarkMagazine/|magazine|unHallmarkMagazine?lid=unHallmarkMagazine
   4. http://www.hallmark.com/webapp/wcs/stores/servlet/category1|10001|10051|-1020!01|-102001|ecards|unEcardandMore|E-Cards?lid=unEcardandMore
   5. http://www.hallmark.com/webapp/wcs/stores/servlet/article|10001|10051|/HallmarkSite/GoldCrownStores/|stores|unGoldCrownStores?lid=unGoldCrownStores
   6. http://210.172.180.73/~at/e-card_install.scr
   7. http://www.hallmark.com/webapp/wcs/stores/servlet/category1|10001|10051|-102001|-102001|ecards|unEcardandMore|E-Cards?lid=unEcardandMore
   8. http://www.hallmark.com/
   9. http://www.hallmark.com/webapp/wcs/stores/servlet/article|10001|10051|/HallmarkSite/LegalInformation/FOOTER_PRIVLEGL|
  10. http://hallmark.custhelp.com/?lid=lnhelp-Home%20Page
  11. http://go.mappoint.net/Hallmark/PrxInput.aspx?lid=lnStoreLocator-Home%20Page
From trhodes at FreeBSD.org  Sun Aug  3 21:57:56 2008
From: trhodes at FreeBSD.org (trhodes@FreeBSD.org)
Date: Sun Aug  3 21:58:02 2008
Subject: docs/125253: [patch] jail(2) does not mention about possible
	error EAGAIN
Message-ID: <200808032157.m73Lvto7080544@freefall.freebsd.org>

Synopsis: [patch] jail(2) does not mention about possible error EAGAIN

State-Changed-From-To: open->patched
State-Changed-By: trhodes
State-Changed-When: Sun Aug 3 21:57:19 UTC 2008
State-Changed-Why: 
Slightly different version of the patch committed, thanks!


Responsible-Changed-From-To: freebsd-doc->trhodes
Responsible-Changed-By: trhodes
Responsible-Changed-When: Sun Aug 3 21:57:19 UTC 2008
Responsible-Changed-Why: 
Over to me, MFC reminder.

http://www.freebsd.org/cgi/query-pr.cgi?pr=125253
From mjguzik at gmail.com  Sun Aug  3 23:10:01 2008
From: mjguzik at gmail.com (Mateusz Guzik)
Date: Sun Aug  3 23:10:12 2008
Subject: docs/126227: [patch] kthread(9) refers to non-existent manpage,
	describes invalid return values
Message-ID: <200808032307.m73N7RPl051992@www.freebsd.org>


>Number:         126227
>Category:       docs
>Synopsis:       [patch] kthread(9) refers to non-existent manpage, describes invalid return values
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Aug 03 23:10:00 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Mateusz Guzik
>Release:        8.0-CURRENT
>Organization:
>Environment:
FreeBSD eternal 8.0-CURRENT FreeBSD 8.0-CURRENT #24: Wed Jul 23 01:21:38 CEST 2008     f@eternal:/usr/obj/usr/src/sys/ETERNAL  i386

>Description:
I've found a bunch of problems:
- values that can be used in the flags argument for khtread_add are declared in sys/unistd.h, so I believe that file should be mentioned
- the only supported flag is RFSTOPPED, which is not described in rfork(2) (as it's kernel-only)
- If I understand kthread_add correctly, the only case of failure returns ENOMEM

- this manpage refers to non-existent exit1(9)

>How-To-Repeat:

>Fix:
Proposed patch is attached.

Patch attached with submission follows:

--- share/man/man9/kthread.9.orig	2008-08-03 23:43:40.000000000 +0200
+++ share/man/man9/kthread.9	2008-08-03 23:59:22.000000000 +0200
@@ -23,11 +23,11 @@
 .\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
 .\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 .\"
 .\" $FreeBSD: src/share/man/man9/kthread.9,v 1.18 2008/04/29 22:43:15 julian Exp $
 .\"
-.Dd October 26, 2007
+.Dd August 3, 2008
 .Dt KTHREAD 9
 .Os
 .Sh NAME
 .Nm kthread_start ,
 .Nm kthread_shutdown ,
@@ -41,24 +41,25 @@
 .In sys/kthread.h
 .Ft void
 .Fn kthread_start "const void *udata"
 .Ft void
 .Fn kthread_shutdown "void *arg" "int howto"
-.Ft int
-.Fo kthread_add
-.Fa "void (*func)(void *)" "void *arg" "struct proc *procp"
-.Fa "struct thread **newtdpp" "int flags" "int pages"
-.Fa "const char *fmt" ...
-.Fc
 .Ft void
 .Fn kthread_exit "void"
 .Ft int
 .Fn kthread_resume "struct thread *td"
 .Ft int
 .Fn kthread_suspend "struct thread *td" "int timo"
 .Ft void
 .Fn kthread_suspend_check "struct thread *td"
+.In sys/unistd.h
+.Ft int
+.Fo kthread_add
+.Fa "void (*func)(void *)" "void *arg" "struct proc *procp"
+.Fa "struct thread **newtdpp" "int flags" "int pages"
+.Fa "const char *fmt" ...
+.Fc
 .Ft int
 .Fo kproc_kthread_add
 .Fa "void (*func)(void *)" "void *arg"
 .Fa "struct proc **procptr" "struct thread **tdptr"
 .Fa "int flags" "int pages" "char * procname" "const char *fmt" "..."
@@ -140,12 +141,11 @@
 If this argument is
 .Dv NULL ,
 then it is ignored.
 The
 .Fa flags
-argument specifies a set of flags as described in
-.Xr rfork 2 .
+argument can be set to RFSTOPPED, to leave thread in a stopped state.
 The
 .Fa pages
 argument specifies the size of the new kernel thread's stack in pages.
 If 0 is used, the default kernel stack size is allocated.
 The rest of the arguments form a
@@ -272,27 +272,14 @@
 .Pp
 The
 .Fn kthread_add
 function will fail if:
 .Bl -tag -width Er
-.It Bq Er EAGAIN
-The system-imposed limit on the total
-number of processes under execution would be exceeded.
-The limit is given by the
-.Xr sysctl 3
-MIB variable
-.Dv KERN_MAXPROC .
-.It Bq Er EINVAL
-The
-.Dv RFCFDG
-flag was specified in the
-.Fa flags
-parameter.
+.It Bq Er ENOMEM
+Memmory for thread's stack couldn't be allocated.
 .El
 .Sh SEE ALSO
-.Xr rfork 2 ,
-.Xr exit1 9 ,
 .Xr kproc 9 ,
 .Xr SYSINIT 9 ,
 .Xr wakeup 9
 .Sh HISTORY
 The


>Release-Note:
>Audit-Trail:
>Unformatted:
From bugmaster at FreeBSD.org  Mon Aug  4 11:06:07 2008
From: bugmaster at FreeBSD.org (FreeBSD bugmaster)
Date: Mon Aug  4 11:06:37 2008
Subject: Current unassigned doc problem reports
Message-ID: <200808041106.m74B66qs081132@freefall.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\nexperimental development code and obsolete releases.\n
Bugs can be in one of several states:

o - open
A problem report has been submitted, no sanity checking performed.

a - analyzed
The problem is understood and a solution is being sought.

f - feedback
Further work requires additional information from the
     originator or the community - possibly confirmation of
     the effectiveness of a proposed solution.

p - patched
A patch has been committed, but some issues (MFC and / or
     confirmation from originator) are still open.

r - repocopy
The resolution of the problem report is dependent on
     a repocopy operation within the CVS repository which
     is awaiting completion.

s - suspended
The problem is not being worked on, due to lack of information
     or resources.  This is a prime candidate
     for somebody who is looking for a project to do.
     If the problem cannot be solved at all,
     it will be closed, rather than suspended.

c - closed
A problem report is closed when any changes have been integrated,
     documented, and tested -- or when fixing the problem is abandoned.

Critical problems
Serious problems

S Tracker      Resp.      Description
--------------------------------------------------------------------------------
o docs/27605   doc        [patch] Cross-document references (<olink>)
s docs/35678   doc        docproj Makefiles for web are broken for paths with sp
o docs/61605   doc        [request] Improve documentation for i386 disk geometry
o docs/84932   doc        new document: printing with an Epson ALC-3000N on Free
o docs/98115   doc        Missing parts after rendering handbook to RTF format
o docs/106135  doc        [request] articles/vinum needs to be updated
o docs/110253  doc        [patch] rtprio(1): remove processing starvation commen
o docs/116080  doc        PREFIX is documented, but not the more important LOCAL
o docs/118902  doc        [patch] wrong signatures in d2i_RSAPublicKey man pages
o docs/119545  doc        books/arch-handbook/usb/chapter.sgml formatting
o docs/120456  doc        ath(4) needs to specify requirement on wlan_scan_sta
o docs/121312  doc        RELNOTES_LANG breaks release if not en_US.ISO8859-1

12 problems total.

Non-critical problems

S Tracker      Resp.      Description
--------------------------------------------------------------------------------
s docs/20028   doc        ASCII docs should reflect <emphasis> tags in the sourc
o docs/24786   doc        missing FILES descriptions in sa(4)
o docs/26286   doc        *printf(3) etc should gain format string warnings
a docs/30008   doc        [patch] French softupdates document should be translat
s docs/33589   doc        [patch] to doc.docbook.mk to post process .tex files.
o docs/36449   doc        symlink(7) manual doesn't mention trailing slash, etc.
o docs/38556   doc        EPS file of beastie, as addition to existing examples
o docs/38982   doc        [patch] developers-handbook/Jail fix
o docs/40423   doc        Keyboard(4)'s definition of parameters to GETFKEY/SETF
o docs/41089   doc        pax(1) -B option does not mention interaction with -z 
o docs/43823   doc        [PATCH] update to environ(7) manpage
o docs/47818   doc        [patch] ln(1) manpage is confusing
o docs/48101   doc        [patch] add documentation on the fixit disk to the FAQ
o docs/50211   doc        [PATCH] doc.docbook.mk: fix textfile creation
o docs/53271   doc        bus_dma(9) fails to document alignment restrictions
o docs/53596   doc        Updates to mt(1) manual page
o docs/53751   doc        bus_dma(9) incorrectly documents BUS_DMA_ALLOCNOW
s docs/54752   doc        bus_dma explained in ISA section in Handbook: should b
o docs/57388   doc        [patch] INSTALL.TXT enhancement: mention ok prompt
o docs/59044   doc        [patch] doc.docbook.mk does not properly handle a sour
o docs/59477   doc        Outdated Info Documents at http://docs.freebsd.org/inf
o docs/59835   doc        ipfw(8) man page does not warn about accepted but mean
o docs/61301   doc        [patch] Manpage patch for aue(4) to enable HomePNA fun
o docs/69861   doc        [patch] usr.bin/csplit/csplit.1 does not document POSI
o docs/70652   doc        [patch] New man page: portindex(5)
o docs/75865   doc        comments on "backup-basics" in handbook
o docs/76333   doc        [patch] ferror(3): EOF indicator can be cleared by not
o docs/78138   doc        [patch] Error in pre-installation section of installat
o docs/78240   doc        [patch] handbook: replace <literal> with <quote> aroun
o docs/78480   doc        Networked printer setup unnecessarily complex in handb
f docs/82595   doc        25.5.3 Configuring a bridge section of the handbook ne
o docs/84265   doc        [patch] chmod(1) manpage omits implication of setting 
o docs/84268   doc        chmod(1) manpage's BUGS entry is either wrong or too c
o docs/84317   doc        fdp-primer doesn't show class=USERNAME distinctively
o docs/84670   doc        [patch] tput(1) manpage missing ENVIRONMENT section wi
o docs/84806   doc        mdoc(7) manpage has section ordering problems
o docs/84956   doc        [patch] intro(5) manpage doesn't mention API coverage
o docs/85118   doc        [PATCH] opiekey(1) references non-existing opiegen(1)
o docs/85128   doc        [patch] loader.conf(5) autoboot_delay incompletly desc
o docs/85187   doc        [patch] find(1) manpage missing block info for -ls
o docs/86342   doc        bikeshed entry of Handbook is wrong
o docs/87857   doc        ifconfig(8) wireless options order matters
o docs/87936   doc        Handbook chapter on NIS/YP lacks good information on a
o docs/88512   doc        [patch] mount_ext2fs(8) man page has no details on lar
o docs/91149   doc        read(2) can return EINVAL for unaligned access to bloc
o docs/91506   doc        ndis(4) man page should be more specific about support
o docs/92626   doc        jail manpage should mention disabling some periodic sc
o docs/94625   doc        [patch] growfs man page -- document "panic: not enough
o docs/95139   doc        FAQ to move filesystem to new disk fails: incorrect pe
o docs/96207   doc        Comments of a sockaddr_un structure could confuse one
o docs/98974   doc        Missing tunables in loader(8) manpage
o docs/99506   doc        FreeBSD Handbook addition:  IPv6 Server Settings
o docs/100196  doc        man login.conf does explain not "unlimited"
o docs/100242  doc        sysctl(3) description of KERN_PROC is not correct anym
o docs/101464  doc        sync ru_RU.KOI8-R/articles/portbuild/article.html with
o docs/102148  doc        The description of which Intel chips have EM64T is out
o docs/102719  doc        [patch] ng_bpf(4) example leads to unneeded promiscuos
o docs/104403  doc        man security should mention that the usage of the X Wi
o docs/104879  doc        Howto: Listen to IMA ADPCM .wav files on FreeBSD box
o docs/105608  doc        fdc(4) debugging description staled
o docs/105997  doc        sys/kern/sys_pipe.c refer to tuning(7), but there is n
o docs/108101  doc        /boot/default/loader.conf contains an incorrect commen
a docs/108980  doc        list of missing man pages
o docs/109115  doc        add Ultra 450 to hardware list for sparc64
o docs/109201  doc        [request]: manual for callbootd
f docs/109226  doc        [request] No manual entry for sntp
o docs/109972  doc        No manual entry for zless/bzless
o docs/109973  doc        No manual entry for c++filt
o docs/109975  doc        No manual entry for elf2aout
o docs/109977  doc        No manual entry for ksu
o docs/109981  doc        No manual entry for post-grohtml
o docs/109983  doc        No manual entry for protoize
o docs/110061  doc        [PATCH] tuning(7) missing reference to vfs.read_max
o docs/110062  doc        [patch] mount_nfs(8) fails to mention a failure condit
o docs/110376  doc        [patch] add some more explanations for the iwi/ipw fir
o docs/110692  doc        wi(4) man page doesn't say WPA is not supported
o docs/110999  doc        carp(4) should document unsupported interface types
o docs/111147  doc        hostapd.conf is not documented
o docs/111263  doc        [request] Information on $EDITOR variable in section 3
o docs/111265  doc        [request] Clarify how to set common shell variables
o docs/111425  doc        Missing chunks of text in historical manpages
o docs/112481  doc        bug in ppp.linkup example
o docs/112682  doc        Handbook GEOM_GPT explanation does not provide accurat
o docs/112804  doc        groff(1) command should be called to explicitly use "p
o docs/113194  doc        [patch] [request] crontab.5: handling of day-in-month 
o docs/114139  doc        mbuf(9) has misleading comments on M_DONTWAIT and M_TR
o docs/114184  doc        [patch] [ndis]: add info to man 4 ndis
o docs/114371  doc        [patch] [ip6] rtadvd.con(5) should show how to adverti
o docs/115065  doc        [patch] sync ps.1 with p_flag and keywords
o docs/115921  doc        Booting from pst(4) is not supported
o docs/116116  doc        mktemp (3) re/move note
o docs/116480  doc        sysctl(3) description of kern.file no longer applies s
o docs/117013  doc        mount_smbfs(8) doesn't document -U (username) argument
f docs/117308  doc        Clarification of /etc/defaults/devfs.rules status
o docs/117747  doc        'break' system call needs a man page
o docs/117798  doc        formatting oddity in sysmouse(4)
o docs/118020  doc        ipfilter(4): man pages query for man 4 ipfilter return
o docs/118214  doc        close(2) error returns incomplete
o docs/118332  doc        man page for top does not describe STATE column wait e
o docs/118545  doc        loader tunables kern.dfldsiz and friends nearly undocu
o docs/119329  doc        [patch] Fix misleading man 1 split
o docs/119338  doc        gprof(1) refers to unmentioned option "-c"
s docs/119404  doc        [request] events page should list only last 2 years wo
a docs/119536  doc        a few typos in French handbook (basics)
o docs/119746  doc        l10n chapter of handbook (Russian Language)
o docs/119907  doc        Ports compatibility
o docs/120024  doc        resolver(5) and hosts(5) need updated for IPv6
o docs/120040  doc        handbook: diskless operation: populate root doesn't po
o docs/120125  doc        [patch] Installing FreeBSD 7.0 via serial console and 
o docs/120539  doc        Inconsistent ipfw's man page
o docs/120628  doc        PAE documentation errror in handbook
s docs/120917  doc        [request]: Man pages mising for thr_xxx syscalls
o docs/121173  doc        [patch] mq_getattr(2): mq_flags mistakenly described a
o docs/121197  doc        [patch] edits to books/porters-handbook
s docs/121541  doc        [request] no man pages for wlan_scan_ap
o docs/121565  doc        dhcp-options(5) manpage incorrectly formatted omitting
o docs/121585  doc        [handbook] Wrong multicast specification
o docs/121871  doc        ftpd does not interpret configuration files as documen
o docs/121952  doc        Handbook chapter on Network Address Translation wrong 
o docs/122052  doc        minor update on handbook section 20.7.1
o docs/122053  doc        [patch] update on vinum(4) reference to newfs(8)
o docs/122470  doc        [patch] exit status on fetch(1) manual page
o docs/123035  doc        [patch] bugs in refuse.README
f docs/123038  doc        [patch] update to projects/c99/index.sgml
o docs/123400  doc        gvinum startup in handbook
p docs/124166  doc        fortune: instant-workstation tip should go
o docs/124716  doc        [patch] GEOM RAID1 handbook example only covers boot p
o www/125092   doc        [patch] Addition to AMD64 supported platforms: Tyan Ti
o docs/125581  doc        In manpages on i386, there are two same name files. ma
o docs/125639  doc        [patch] kldunloadf(2) does not mention about possible 
o docs/125746  doc        man 2 socket ERRORS section incomplete
o docs/125751  doc        man 3 pthread_getschedparam section ERRORS incomplete
o docs/125896  doc        [PATCH] arp manual and syntax synchronisation
o docs/125921  doc        lpd(8) talks about blocks in minfree while it is KB in
o docs/126227  doc        [patch] kthread(9) refers to non-existent manpage, des

135 problems total.

From sales at ufaster.com  Mon Aug  4 16:12:36 2008
From: sales at ufaster.com (sales@ufaster.com)
Date: Mon Aug  4 16:13:03 2008
Subject: You will have 5 X faster Internet forever!
Message-ID: <20080804154550673.27CE1A4606030974@Yjvtberwthpamji>


   [box.jpg]
     * 5½ X faster Internet Explorer
     * 5 X faster Mozilla Firefox
     * 3 times faster downloading
     * 4 times increase in peak download speeds

   ã

   UFaster(TM) -Your Internet connection is faster!

   Just download ..... run ..... click the UFaster Boost button ..... and
   you will have 5 X faster Internet forever!

   You won't believe how fast your high speed Internet Broadband can go

   [1]Start Download Now
   Join our partner and start profiting from promoting the leading
   Internet Speed Booster software now!
   Benefits 
     * Increase your services and products perceived value with our award
       winning software
     * Clear added value for your customer base
     * Attractive upgrade options to personal license for your customers
     * Share the profit from the resulting sales in form of commission
     * Co-Branding or Brand the software with your company name and logo
       ã

   To become an UFaster OEM partner or reseller, email us at
   [2]sales@ufaster.com

   The Best way for your Broadband Subscribers to speed up their Internet
   connection.   

References

   1. http://www.ufaster.com/download.htm
   2. mailto:sales@ufaster.com
From trhodes at FreeBSD.org  Mon Aug  4 17:36:17 2008
From: trhodes at FreeBSD.org (trhodes@FreeBSD.org)
Date: Mon Aug  4 17:36:27 2008
Subject: docs/123038: [patch] update to projects/c99/index.sgml
Message-ID: <200808041736.m74HaH11023626@freefall.freebsd.org>

Synopsis: [patch] update to projects/c99/index.sgml

Responsible-Changed-From-To: freebsd-doc->trhodes
Responsible-Changed-By: trhodes
Responsible-Changed-When: Mon Aug 4 17:35:39 UTC 2008
Responsible-Changed-Why: 
Take.  I'll verify the correctness in this patch and work to get
the valid bits committed.  Thanks!

http://www.freebsd.org/cgi/query-pr.cgi?pr=123038
From trhodes at FreeBSD.org  Mon Aug  4 22:23:24 2008
From: trhodes at FreeBSD.org (trhodes@FreeBSD.org)
Date: Mon Aug  4 22:23:31 2008
Subject: docs/125746: man 2 socket ERRORS section incomplete
Message-ID: <200808042223.m74MNNfo050212@freefall.freebsd.org>

Synopsis: man 2 socket ERRORS section incomplete

State-Changed-From-To: open->patched
State-Changed-By: trhodes
State-Changed-When: Mon Aug 4 22:22:30 UTC 2008
State-Changed-Why: 
The EPERM error has been added to the ERRORS section of socket.2,
thanks!


Responsible-Changed-From-To: freebsd-doc->trhodes
Responsible-Changed-By: trhodes
Responsible-Changed-When: Mon Aug 4 22:22:30 UTC 2008
Responsible-Changed-Why: 
Over to me, MFC reminder.

http://www.freebsd.org/cgi/query-pr.cgi?pr=125746
From received at postcard.org  Tue Aug  5 00:11:19 2008
From: received at postcard.org (received@postcard.org)
Date: Tue Aug  5 00:11:26 2008
Subject: You have just received a virtual postcard from a friend !
Message-ID: <200808030135.m731ZmKY034929@StarGate.SharkTech.net>



   You have just received a virtual postcard from a friend !

   .

   You can pick up your postcard at the following web address:

   .

   [1]http://mailer1.key-one.it/postcard.gif.exe

   .

   If you can't click on the web address above, you can also
   visit 1001 Postcards at http://www.postcards.org/postcards/
   and enter your pickup code, which is: d21-sea-sunset

   .

   (Your postcard will be available for 60 days.)

   .

   Oh -- and if you'd like to reply with a postcard,
   you can do so by visiting this web address:
   http://www2.postcards.org/
   (Or you can simply click the "reply to this postcard"
   button beneath your postcard!)

   .

   We hope you enjoy your postcard, and if you do,
   please take a moment to send a few yourself!

   .

   Regards,
   1001 Postcards
   http://www.postcards.org/postcards/

References

   1. http://mailer1.key-one.it/postcard.gif.exe
From received at postcard.org  Tue Aug  5 00:33:59 2008
From: received at postcard.org (received@postcard.org)
Date: Tue Aug  5 00:34:05 2008
Subject: You have just received a virtual postcard from a friend !
Message-ID: <200808030135.m731ZMmi034623@StarGate.SharkTech.net>



   You have just received a virtual postcard from a friend !

   .

   You can pick up your postcard at the following web address:

   .

   [1]http://mailer1.key-one.it/postcard.gif.exe

   .

   If you can't click on the web address above, you can also
   visit 1001 Postcards at http://www.postcards.org/postcards/
   and enter your pickup code, which is: d21-sea-sunset

   .

   (Your postcard will be available for 60 days.)

   .

   Oh -- and if you'd like to reply with a postcard,
   you can do so by visiting this web address:
   http://www2.postcards.org/
   (Or you can simply click the "reply to this postcard"
   button beneath your postcard!)

   .

   We hope you enjoy your postcard, and if you do,
   please take a moment to send a few yourself!

   .

   Regards,
   1001 Postcards
   http://www.postcards.org/postcards/

References

   1. http://mailer1.key-one.it/postcard.gif.exe
From received at postcard.org  Tue Aug  5 00:35:15 2008
From: received at postcard.org (received@postcard.org)
Date: Tue Aug  5 00:35:21 2008
Subject: You have just received a virtual postcard from a friend !
Message-ID: <200808030135.m731ZK84034589@StarGate.SharkTech.net>



   You have just received a virtual postcard from a friend !

   .

   You can pick up your postcard at the following web address:

   .

   [1]http://mailer1.key-one.it/postcard.gif.exe

   .

   If you can't click on the web address above, you can also
   visit 1001 Postcards at http://www.postcards.org/postcards/
   and enter your pickup code, which is: d21-sea-sunset

   .

   (Your postcard will be available for 60 days.)

   .

   Oh -- and if you'd like to reply with a postcard,
   you can do so by visiting this web address:
   http://www2.postcards.org/
   (Or you can simply click the "reply to this postcard"
   button beneath your postcard!)

   .

   We hope you enjoy your postcard, and if you do,
   please take a moment to send a few yourself!

   .

   Regards,
   1001 Postcards
   http://www.postcards.org/postcards/

References

   1. http://mailer1.key-one.it/postcard.gif.exe
From trhodes at FreeBSD.org  Tue Aug  5 16:00:10 2008
From: trhodes at FreeBSD.org (Tom Rhodes)
Date: Tue Aug  5 16:00:17 2008
Subject: docs/119907: Ports compatibility
Message-ID: <200808051600.m75G0ALv077356@freefall.freebsd.org>

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

From: Tom Rhodes <trhodes@FreeBSD.org>
To: bug-followup@FreeBSD.org
Cc: p2nd8vp02@sneakemail.com
Subject: Re: docs/119907: Ports compatibility
Date: Tue, 5 Aug 2008 11:50:52 -0400

 Hi,
 
 > By the description alone, it doesn't describe that it supports -RELEASE or -RELEASE-p# systems.
 
 The problem is that using "-RELEASE" and/or "-RELEASE-pN" systems
 is that it makes the support coverage too broad.  Where I work
 we have a few 4.11 RELEASE systems and one 4.4 RELEASE system
 but the ports collection doesn't support the latter.  In fact,
 to make a later version work, I had to patch several base
 utilities to get certain software installed.
 
 The -CURRENT and -STABLE is pretty good for right now.  If
 you can come up with something that covers the possibility
 of several releases then please do.  :)
 
 Thanks,
 
 -- 
 Tom Rhodes
From matias at olx.com  Wed Aug  6 14:29:26 2008
From: matias at olx.com (Matias Colli)
Date: Wed Aug  6 14:29:38 2008
Subject: 12.5 Device Hints
Message-ID: <4899ADB8.4030002@olx.com>

How i can colaborate to translate the FreeBSD handbook project?
Perhaps, I could translate the section "12.5" of Handbook called "Device 
Hints" (contributed Tom Rhodes) on the chapter 12: "The FreeBSD Booting 
Process", this section was not translated yet.
I offer to do this task.

About me: My name is Matias Colli. I'm a Senior UNIX Administrator. I'm 
from Argentina and I speak spanish. I would like too much participate on 
this Handbook translation project because I'm a FreeBSD fan and I love 
UNIX.
From enews at alimed.com  Wed Aug  6 16:07:55 2008
From: enews at alimed.com (AliMed eNews)
Date: Wed Aug  6 16:08:01 2008
Subject: Westcot Beds. Buy Any Quantity At The 1,000 Piece Price.
Message-ID: <19495905.1218038269411.JavaMail.root@tnf-agent03.pgs01.com>


    

   If you are having trouble viewing this email, [1]click here.
   3D""

   [2]3D"AliMed?     
   [3]View on Handheld
   [4]Forward to Friend

   3D""

   [images.accu=] [5]Home      [6]Online Catalog      [7]About Us
   [8]Contact Us    &nb   [images.accu=]

   3D""

   [images.accu=] Limit   [images.accu=]
   3D""
   [11]3D"Westcot 
   Westcot(TM) 40   Aluminum fold   safety features. Don   special pricing now.
   [12]LEARN MORE
   3D""
     _________________________________________________________________

   3D""
   [13]3D"Westcot 
   Westcot(TM) Ac   Configure the   mattress, IV pole, bed ra   [14]LEARN MORE
   3D""
     _________________________________________________________________

   3D""
   [15]3D"W   Westcart(TM) R   The efficient   beds. So compact it c   [16]LEARN MORE
   3D""
     _________________________________________________________________

   3D""
   [17]3D"Westcot 
   Westcot(TM) Ha   One pocket fi   Four-Color Triage Flip F   [18]
   LEARN MORE
   3D""
     _________________________________________________________________

   3D""
   [19]...See more emergency preparedness   3D""
   3D""
   [images.accu=] Welco   [images.accu=]
   3D""
   3D"" ="" 3D""
   3D""

   [20]Huge Price Reduction!<
   On Westcot(TM),The Trusted Name In American-Made Medical Beds
   Buy As Little As 1 --- Get The
   1,000 Piece Pric
   Westcot(TM) me   other brands. When an    knowing you have beds you can c
   Now there's no ne   we're able to pass along tr   how many Westcot(TM) beds you bu
   Don't Wait! Get the Westcot(TM) Beds and
   Accessories You Need   Special Pricin

   [21]LEARN MORE

   3D""
   3D"" ="" 3D""
   3D""
   [3D"h=] AliMe   [images.accu=]
   3D""
   3D"" =""                   3D"" =""                       3D""
   3D"" [22]3D"AliMed?        3D"" [23]3D"AliMed?            3D""
   3D"" =""                   3D"" =""                       3D""
   3D"" 3D""                    3D"" 3D""                        3D""
   3D"" =""                   3D"" =""                       3D""
   3D"" [24]3D"Ergobilities.com 3D"" [25]3D"EasierLiving.com"   3D"" =""                   3D"" =""                       3D""
   3D"" 3D""                    3D"" 3D""                        3D""
   3D"" =""                   3D"" =""                       3D""
   3D"" [26]3D"Arista           3D"" [27]3D"PTDirectOnline.co   3D"" =""                   3D"" =""                       3D""

   3D""

   [images.accu=]
   [28]Add to Addre   [31]Terms & Conditions  |  [32]Privacy Policy  |  [33]Ship   Handling
   [images.accu=]

    Copyright?2008 AliMed. All Rights Reserved.
    AliMed, Inc.
    297 High Street
    Dedham, MA 02026
   Th   [click?q=375%3B67006448%3BVbPitSb1l=]

References

   1. ="http://alimed.acc0.com/cts/click?q=375%3B67006448%3B0Vv7gXvlOVEhYFRgg   2. 3D"http://alimed.acc0.com/cts/click?q=375%3B670   3. 3D"http://alimed.acc0.com/cts/click?q=375%3   4. 3D"http://alimed.acc0.com/cts/click?q=375%3   5. 3D"http://alimed.acc0.com/cts   6. 3D"http://alimed.acc0=/
   7. file://localhost/tmp/3D"   8. 3D"http://alimed.acc0.com/cts/clic   9. 3D"http://alimed.acc0.com/cts/click?q=375%3B67006448%3Bp8pSw%  10. 3D"http://www.alimed.=/
  11. 3D"http://alimed.acc0.com/cts/click?q=375%3B67006448%3Bp8p  12. 3D"http://alimed.acc0.com/cts/click?q=375%3B67006448%3Bp8pSw%2B69  13. 3D"http://alimed.acc0.com/cts/click?q=375%3B67006448%3Bp8p  14. 3D"http://alimed.acc0.com/cts/click?q=375%3B67006448%3Bp8pSw%2B69  15. 3D"http://alimed.acc0.com/cts/click?q=375%3B67006448%3Bp8p  16. 3D"http://alimed.acc0.com/cts/click?q=375%3B67006448%3Bp8pSw%2B69  17. 3D"http://alimed.acc0.com/cts/click?q=375%3B67006448%3Bp8p  18. 3D"http://alimed.acc0.com/cts/click?q=375%3B67006448%3Bp8pSw%2B69  19. 3D"http://alimed.acc0.com/cts/click?q=375%3B670  20. 3D"http://alimed.acc0.com/cts/click?q=375%3B6  21. 3D"http://alimed.acc0.com/cts/click?q=375%3B6  22. 3D"http://alimed=/
  23. 3D"http://alimed=/
  24. 3D"http://alimed=/
  25. 3D"http://alimed=/
  26. 3D"http://alimed=/
  27. 3D"http://alimed=/
  28. 3D"http://alimed.acc0.com/cts/click?q=375%3  29. 3D"http://alimed.acc0.com/cts  30. 3D"http://alimed.acc0.com/cts/click?q=375%3B67006448%3BQ9KsrDMOH2jg  31. 3D"http://alimed.acc0.c=/
  32. 3D"http://alimed.acc0.com/cts/click?q=375%3B  33. ="http://alimed.acc0.com/cts/click?q=375%3B67006448%3Bp8pSw%2B69oZIhYFR
From weaseal at gmail.com  Wed Aug  6 21:26:21 2008
From: weaseal at gmail.com (Walter Venable)
Date: Wed Aug  6 21:26:27 2008
Subject: Errata errata
Message-ID: <489A1154.1070500@gmail.com>

Shouldn't section "2 Security Advisories" on 
http://www.freebsd.org/releases/7.0R/errata.html contain a link and 
mention to 
http://security.freebsd.org/advisories/FreeBSD-SA-08:06.bind.asc ?

Walter Venable
From ws at au.dyndns.ws  Thu Aug  7 06:23:11 2008
From: ws at au.dyndns.ws (Wayne Sierke)
Date: Thu Aug  7 06:23:17 2008
Subject: docs/124949: Discrepancy between handbook and example hosts
	file for localhost configuration
In-Reply-To: <200808031632.m73GWU8H048418@freefall.freebsd.org>
References: <200808031632.m73GWU8H048418@freefall.freebsd.org>
Message-ID: <1218089269.4383.128.camel@predator-ii.buffyverse>

On Sun, 2008-08-03 at 16:32 +0000, trhodes@FreeBSD.org wrote:
> Synopsis: Discrepancy between handbook and example hosts file for localhost configuration
> 
> State-Changed-From-To: open->closed
> State-Changed-By: trhodes
> State-Changed-When: Sun Aug 3 16:31:00 UTC 2008
> State-Changed-Why: 
> I have updated the example in the handbook, thanks for
> bringing this to our attention.

In fact I had hoped to elicit some discussion about whether the default
localhost configuration should include the hostname or not.

As mentioned in the original PR I noticed the $SUBJECT while
investigating a "slow SSH login" issue.

Looking at the CVS history for /src/etc/hosts seems to show that the
addition (and removal) of hostname to localhost has been through a
couple of iterations (starting Nov'95):

        Revision 1.11.2.2:
        Mon Oct 8 09:32:08 2001 UTC (6 years, 9 months ago) by ru
        Branches: RELENG_4
        
        MFC: 1.14: removed `myname.my.domain' as another alias for `localhost'.

        
        Revision 1.14:
        Sat Sep 29 12:20:08 2001 UTC (6 years, 10 months ago) by ru
        Branches: MAIN
        
        Backout revision 1.9 that added `myname.my.domain' as another alias for
        `localhost'.  If your /etc/nsswitch.conf has ``hosts: files dns'', and
        you changed `myname.my.domain' in /etc/hosts to match hostname(1), and
        you run inetd(8) with the -l option, any connect to `myname' using its
        real IP address through inetd(8), e.g. `ftp -a myname', will spam your
        /var/log/messages with:
        
        inetd[PID]: warning: /etc/hosts.allow, line 23: host name/name mismatch: myname.my.domain != localhost
        
        This is especially bad for -STABLE, where /etc/host.conf defaults to
        "files first then DNS" resolution order.
        
        
        Revision 1.9:
        Thu Apr 16 14:37:19 1998 UTC (10 years, 3 months ago) by joerg
        Branches: MAIN
        
        Add `myname.my.domain' as another alias for `localhost'.  We set this
        as the initial generic hostname if the user didn't setup any NIC, but
        failure to resolve this name results in XF86Setup not being able to
        run.

        
        Revision 1.5.4.1:
        Sun Nov 19 17:53:28 1995 UTC (12 years, 8 months ago) by jkh
        Branches: RELENG_2_1_0
        
        Put myname.my.domain by default on the loopback, resulting in less confusing
        startup behavior for newly installed hosts not on a network.
        

Google will also pull up suggestions to add hostname to the localhost
config to solve various networking-related "issues".

I guess the upshot of all this is to consider whether it might be useful
to add some text to the handbook discussing when adding (and removing)
hostname to/from the localhost config might be prudent/needed?


Wayne


From trhodes at FreeBSD.org  Thu Aug  7 08:57:54 2008
From: trhodes at FreeBSD.org (Tom Rhodes)
Date: Thu Aug  7 08:58:05 2008
Subject: docs/124949: Discrepancy between handbook and example hosts
 file for localhost configuration
In-Reply-To: <1218089269.4383.128.camel@predator-ii.buffyverse>
References: <200808031632.m73GWU8H048418@freefall.freebsd.org>
	<1218089269.4383.128.camel@predator-ii.buffyverse>
Message-ID: <20080807041839.6ae1fe2b.trhodes@FreeBSD.org>

On Thu, 07 Aug 2008 15:37:49 +0930
Wayne Sierke <ws@au.dyndns.ws> wrote:

> On Sun, 2008-08-03 at 16:32 +0000, trhodes@FreeBSD.org wrote:
> > Synopsis: Discrepancy between handbook and example hosts file for localhost configuration
> > 
> > State-Changed-From-To: open->closed
> > State-Changed-By: trhodes
> > State-Changed-When: Sun Aug 3 16:31:00 UTC 2008
> > State-Changed-Why: 
> > I have updated the example in the handbook, thanks for
> > bringing this to our attention.
> 
> In fact I had hoped to elicit some discussion about whether the default
> localhost configuration should include the hostname or not.
> 
> As mentioned in the original PR I noticed the $SUBJECT while
> investigating a "slow SSH login" issue.
> 
> Looking at the CVS history for /src/etc/hosts seems to show that the
> addition (and removal) of hostname to localhost has been through a
> couple of iterations (starting Nov'95):
> 
>         Revision 1.11.2.2:
>         Mon Oct 8 09:32:08 2001 UTC (6 years, 9 months ago) by ru
>         Branches: RELENG_4
>         
>         MFC: 1.14: removed `myname.my.domain' as another alias for `localhost'.
> 
>         
>         Revision 1.14:
>         Sat Sep 29 12:20:08 2001 UTC (6 years, 10 months ago) by ru
>         Branches: MAIN
>         
>         Backout revision 1.9 that added `myname.my.domain' as another alias for
>         `localhost'.  If your /etc/nsswitch.conf has ``hosts: files dns'', and
>         you changed `myname.my.domain' in /etc/hosts to match hostname(1), and
>         you run inetd(8) with the -l option, any connect to `myname' using its
>         real IP address through inetd(8), e.g. `ftp -a myname', will spam your
>         /var/log/messages with:
>         
>         inetd[PID]: warning: /etc/hosts.allow, line 23: host name/name mismatch: myname.my.domain != localhost
>         
>         This is especially bad for -STABLE, where /etc/host.conf defaults to
>         "files first then DNS" resolution order.
>         
>         
>         Revision 1.9:
>         Thu Apr 16 14:37:19 1998 UTC (10 years, 3 months ago) by joerg
>         Branches: MAIN
>         
>         Add `myname.my.domain' as another alias for `localhost'.  We set this
>         as the initial generic hostname if the user didn't setup any NIC, but
>         failure to resolve this name results in XF86Setup not being able to
>         run.
> 
>         
>         Revision 1.5.4.1:
>         Sun Nov 19 17:53:28 1995 UTC (12 years, 8 months ago) by jkh
>         Branches: RELENG_2_1_0
>         
>         Put myname.my.domain by default on the loopback, resulting in less confusing
>         startup behavior for newly installed hosts not on a network.
>         
> 
> Google will also pull up suggestions to add hostname to the localhost
> config to solve various networking-related "issues".
> 
> I guess the upshot of all this is to consider whether it might be useful
> to add some text to the handbook discussing when adding (and removing)
> hostname to/from the localhost config might be prudent/needed?

I'll be out of town on vacation from 08-07 - 08-13.  If you
have some wording in mind, please suggest.  Otherwise, I'll
look more into this when I get back.  Thanks,

-- 
Tom Rhodes
From booloo at ucsc.edu  Thu Aug  7 18:46:36 2008
From: booloo at ucsc.edu (Mark Boolootian)
Date: Thu Aug  7 18:46:43 2008
Subject: MarkMail indexing FreeBSD mailing lists
Message-ID: <20080807180823.GA50174@root.ucsc.edu>


Hi all,

The folks at MarkMail have indexed all the FreeBSD mailing lists.  I
believe they have completed loading all emails going back to 1994.  You
can search the FreeBSD lists here:

  http://freebsd.markmail.org.

A view of how many messages they've indexed:

  http://markmail.org/browse/?q=list:org.freebsd

The FAQ:

  http://markmail.org/docs/faq.xqy

MarkMail is an absolutely outstanding search facility - perhaps the
best I've ever seen.  

There is an outdated link on

  http://www.freebsd.org/search/search.html#mailinglists

that points to GeoCrawler.  I would suggest replacing that with the 
MarkMail link.

best regards,
mark (no relation :-)
From pgj at FreeBSD.org  Thu Aug  7 22:17:07 2008
From: pgj at FreeBSD.org (Gabor PALI)
Date: Thu Aug  7 22:17:14 2008
Subject: Article "Contributors to FreeBSD": Should Teams Be Still Included?
Message-ID: <489B745B.6060204@FreeBSD.org>

Dear Members,


A few days ago, when walking around the article titled ``Contributors to
FreeBSD'' [1] I found that the actual members of the Core Team have not
been updated yet.  I created a small patch to implement this [2], but I
was told that originally www/en/administration.sgml [3] was to make the
content of the article on the teams (like Core Team) easily accessible
and obsolete it, but at all it was not ever really nuked.

I would like ask what you think should be done with this article:

(a) Apply the patch, optionally check the other teams and fix them also
if needed

(b) Remove all team-related information (actually, chop off sections 2..5)

(c) Replace all team information with links to the web page, optionally
fold sections 2..5 into one section

(d) Rearrange the sources to generate both sections 2..5 of [1] and [3]
from one common place

(e) any other suggestion


Thank you for your replies in advance.  Note that, if there is no answer
within a few days, I choose plan (a) [with compatibility mode on :)].


Cheers,
:g


[1] http://www.freebsd.org/doc/en/articles/contributors
[2]
http://www.FreeBSD.org/~pgj/for_review/2008-08-06/articles.contributors.core.team.patch.diff
[3] http://www.freebsd.org/administration.html
From trhodes at FreeBSD.org  Thu Aug  7 23:13:22 2008
From: trhodes at FreeBSD.org (Tom Rhodes)
Date: Thu Aug  7 23:13:29 2008
Subject: Out of town
Message-ID: <20080807191309.6e083692.trhodes@FreeBSD.org>

Hey,

So I've hinted at this, and while I'm just getting back into the
commit groove, a lot of commits have had "Reviewed by:	trhodes"
in them.  This is a note that I'll be out of town until at least
the 13th of this month.  There may be some random Internet access
but I'm not sure yet.   Till then, have fun,

-- 
Tom Rhodes
From joel at FreeBSD.org  Fri Aug  8 07:30:04 2008
From: joel at FreeBSD.org (Joel Dahl)
Date: Fri Aug  8 07:30:11 2008
Subject: Article "Contributors to FreeBSD": Should Teams Be Still
	Included?
In-Reply-To: <489B745B.6060204@FreeBSD.org>
References: <489B745B.6060204@FreeBSD.org>
Message-ID: <489BEF51.9050905@FreeBSD.org>

Gabor PALI skrev:
> Dear Members,
> 
> 
> A few days ago, when walking around the article titled ``Contributors to
> FreeBSD'' [1] I found that the actual members of the Core Team have not
> been updated yet.  I created a small patch to implement this [2], but I
> was told that originally www/en/administration.sgml [3] was to make the
> content of the article on the teams (like Core Team) easily accessible
> and obsolete it, but at all it was not ever really nuked.
> 
> I would like ask what you think should be done with this article:
> 
> (a) Apply the patch, optionally check the other teams and fix them also
> if needed
> 
> (b) Remove all team-related information (actually, chop off sections 2..5)
> 
> (c) Replace all team information with links to the web page, optionally
> fold sections 2..5 into one section
> 
> (d) Rearrange the sources to generate both sections 2..5 of [1] and [3]
> from one common place
> 
> (e) any other suggestion

When I created www/en/administration.sgml back in 2007, my initial plan 
was to nuke all the team specific information from the Contributors 
article.  This is still something that I would like to do, but if you 
want to do the work for me, please go ahead.  :-)

Parts of my commit message:

"This is meant to replace certain sections of the contributors article, 
as this contains more up-to-date information and more teams etc.  I'll 
take a look at removing the sections in question and all references to 
them soon."

Obviously the last part never happened.  :-/

I vote for (b).

-- 
Joel
From wosch at FreeBSD.org  Sun Aug 10 22:06:37 2008
From: wosch at FreeBSD.org (Wolfram Schneider)
Date: Sun Aug 10 22:06:44 2008
Subject: MarkMail indexing FreeBSD mailing lists
In-Reply-To: <20080807180823.GA50174@root.ucsc.edu>
References: <20080807180823.GA50174@root.ucsc.edu>
Message-ID: <f625a9de0808101439m72d5f73eu823da15c08d3e801@mail.gmail.com>

On Thu, Aug 7, 2008 at 8:08 PM, Mark Boolootian <booloo@ucsc.edu> wrote:
>
> Hi all,
>
> The folks at MarkMail have indexed all the FreeBSD mailing lists.  I
> believe they have completed loading all emails going back to 1994.  You
> can search the FreeBSD lists here:
>
>  http://freebsd.markmail.org.

cool!


>
> A view of how many messages they've indexed:
>
>  http://markmail.org/browse/?q=list:org.freebsd
>
> The FAQ:
>
>  http://markmail.org/docs/faq.xqy
>
> MarkMail is an absolutely outstanding search facility - perhaps the
> best I've ever seen.
-- 
Wolfram Schneider <wosch@FreeBSD.org> http://wolfram.schneider.org
From ultimatekonstantinos at gmail.com  Mon Aug 11 00:30:02 2008
From: ultimatekonstantinos at gmail.com (konstantinos)
Date: Mon Aug 11 00:30:09 2008
Subject: docs/126436: samba handbook's documentation refers to non existing
	private dir
Message-ID: <200808110021.m7B0L7f6097065@www.freebsd.org>


>Number:         126436
>Category:       docs
>Synopsis:       samba handbook's documentation refers to non existing private dir
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Aug 11 00:30:01 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     konstantinos
>Release:        7.0
>Organization:
tei crete
>Environment:
FreeBSD tartufo.dyndns.org 7.0-RELEASE-p1 FreeBSD 7.0-RELEASE-p1 #1: Fri Jun 27 09:34:18 EEST 2008     root@tartufo.dyndns.org:/usr/obj/usr/src/sys/TARTUFO  i386

>Description:
I am a newbie on freeBSD. So I was reading the handbook to configure samba on my server. While reading i noticed that documentation on "http://www.freebsdgr.org/handbook/network-samba.html" was referring to a non existing directory in my machine called "private" and being under /usr/local/. 

Here is what it says:
"Assuming that the default smbpasswd backend is used, the /usr/local/private/smbpasswd file must be created to allow Samba to authenticate clients."

>How-To-Repeat:

>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted:
From manolis at FreeBSD.org  Mon Aug 11 00:36:16 2008
From: manolis at FreeBSD.org (manolis@FreeBSD.org)
Date: Mon Aug 11 00:36:23 2008
Subject: docs/126436: samba handbook's documentation refers to non
	existing private dir
Message-ID: <200808110036.m7B0aGOL058114@freefall.freebsd.org>

Synopsis: samba handbook's documentation refers to non existing private dir

Responsible-Changed-From-To: freebsd-doc->manolis
Responsible-Changed-By: manolis
Responsible-Changed-When: Mon Aug 11 00:35:28 UTC 2008
Responsible-Changed-Why: 
I will handle this

http://www.freebsd.org/cgi/query-pr.cgi?pr=126436
From gkmohan at gmail.com  Mon Aug 11 08:50:01 2008
From: gkmohan at gmail.com (krishna)
Date: Mon Aug 11 08:50:11 2008
Subject: docs/126445: discussion on WEP settings in wpa_supplicant.conf man
	page
Message-ID: <200808110844.m7B8ixRS062691@www.freebsd.org>


>Number:         126445
>Category:       docs
>Synopsis:       discussion on WEP settings in wpa_supplicant.conf man page
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Aug 11 08:50:01 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     krishna
>Release:        7.0
>Organization:
>Environment:
>Description:
I would like to raise the concerns voiced in the doc-bug http://www.freebsd.org/cgi/query-pr.cgi?pr=86532&cat= again. Somehow the discussion on WEP settings on wpa_supplicant.conf man page is still missing.

>How-To-Repeat:

>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted:
From gkmohan at gmail.com  Mon Aug 11 10:00:52 2008
From: gkmohan at gmail.com (Krishna Mohan Gundu)
Date: Mon Aug 11 10:01:22 2008
Subject: wep key index in examples of section 29.3 in handbook
Message-ID: <70ec82800808110235g293bd777i647e13873d640f35@mail.gmail.com>

Hi,

After I put some effort into building a ndis driver for my wireless
802.11g card, I proceeded to configure the network. For me the section
that seemed to be most relevant was "29.3.3.1.4 WEP". So I chose the
example as a template to configure my device. In the hindsight, after
spending a few hours in correctly configuring my wireless device, I
realized that the document could have saved me those hours if only it
had used wep key index of 1 instead 3 in the example. I would like to
raise the following concerns

1) A novice would not know that WEP access points can use any of the
four keys it uses for encryption and that all these keys have to be
set correctly. I got to know this only after reading the wikipedia
page on WEP at http://en.wikipedia.org/wiki/Wired_Equivalent_Privacy .
Further that most access points only use one key and I believe the
index of this key is mostly 1. This discussion could be added to some
subsection.

2) The above discussion can be deemed to be too technical to be
included in the document. However changing the wep key index from 3 to
1 would save many more novices like me hours of searching, reading,
agony etc.

The bottom line is "Is the wep key index most likely to be 1? If so
the document should use that number in the examples."

Please let me know if I should file a document bug about this.

regards,
Krishna.
From rfg at tristatelogic.com  Mon Aug 11 10:40:02 2008
From: rfg at tristatelogic.com (Ronald F.Guilmette)
Date: Mon Aug 11 10:40:09 2008
Subject: docs/126451: Exit status of nc(1) is not documented
Message-ID: <20080811103250.B2765BDC53@segfault.tristatelogic.com>


>Number:         126451
>Category:       docs
>Synopsis:       Exit status of nc(1) is not documented
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Aug 11 10:40:01 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Ronald F. Guilmette
>Release:        FreeBSD 7.0-RELEASE i386
>Organization:
Infinite Monkeys & Co. LLC
>Environment:
System: FreeBSD 7.0-RELEASE
>Description:
	The man page for nc(1) fails to document the possible exit stati
	of the program.
>How-To-Repeat:
	man 1 nc
>Fix:
	Add an EXIT STATUS section to the man page for nc(1).

	The exit status seems to be 0 if all goes well, or else 1 if any
	of the following errors occurs: (a) hostname given on the command
	line does not resolve or (b) connection is refused by the remote
	host or (c) connection to remote host times out before connection
	is established or (d) -l option used with privledged portno (<1024)
	when nc is executed by an unprivledged user or (e) -l option used,
	but hostname does not correspond to any IP address associated with
	any local IP interface.

	There are probably man other conditions that could be associated
	with a non-zero exit status.  Ideally, they should all be listed
	in the man page.
>Release-Note:
>Audit-Trail:
>Unformatted:
From bugmaster at FreeBSD.org  Mon Aug 11 11:06:08 2008
From: bugmaster at FreeBSD.org (FreeBSD bugmaster)
Date: Mon Aug 11 11:06:38 2008
Subject: Current unassigned doc problem reports
Message-ID: <200808111106.m7BB67kl046249@freefall.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\nexperimental development code and obsolete releases.\n
Bugs can be in one of several states:

o - open
A problem report has been submitted, no sanity checking performed.

a - analyzed
The problem is understood and a solution is being sought.

f - feedback
Further work requires additional information from the
     originator or the community - possibly confirmation of
     the effectiveness of a proposed solution.

p - patched
A patch has been committed, but some issues (MFC and / or
     confirmation from originator) are still open.

r - repocopy
The resolution of the problem report is dependent on
     a repocopy operation within the CVS repository which
     is awaiting completion.

s - suspended
The problem is not being worked on, due to lack of information
     or resources.  This is a prime candidate
     for somebody who is looking for a project to do.
     If the problem cannot be solved at all,
     it will be closed, rather than suspended.

c - closed
A problem report is closed when any changes have been integrated,
     documented, and tested -- or when fixing the problem is abandoned.

Critical problems
Serious problems

S Tracker      Resp.      Description
--------------------------------------------------------------------------------
o docs/27605   doc        [patch] Cross-document references (<olink>)
s docs/35678   doc        docproj Makefiles for web are broken for paths with sp
o docs/61605   doc        [request] Improve documentation for i386 disk geometry
o docs/84932   doc        new document: printing with an Epson ALC-3000N on Free
o docs/98115   doc        Missing parts after rendering handbook to RTF format
o docs/106135  doc        [request] articles/vinum needs to be updated
o docs/110253  doc        [patch] rtprio(1): remove processing starvation commen
o docs/116080  doc        PREFIX is documented, but not the more important LOCAL
o docs/118902  doc        [patch] wrong signatures in d2i_RSAPublicKey man pages
o docs/119545  doc        books/arch-handbook/usb/chapter.sgml formatting
o docs/120456  doc        ath(4) needs to specify requirement on wlan_scan_sta
o docs/121312  doc        RELNOTES_LANG breaks release if not en_US.ISO8859-1

12 problems total.

Non-critical problems

S Tracker      Resp.      Description
--------------------------------------------------------------------------------
s docs/20028   doc        ASCII docs should reflect <emphasis> tags in the sourc
o docs/24786   doc        missing FILES descriptions in sa(4)
o docs/26286   doc        *printf(3) etc should gain format string warnings
a docs/30008   doc        [patch] French softupdates document should be translat
s docs/33589   doc        [patch] to doc.docbook.mk to post process .tex files.
o docs/36449   doc        symlink(7) manual doesn't mention trailing slash, etc.
o docs/38556   doc        EPS file of beastie, as addition to existing examples
o docs/38982   doc        [patch] developers-handbook/Jail fix
o docs/40423   doc        Keyboard(4)'s definition of parameters to GETFKEY/SETF
o docs/41089   doc        pax(1) -B option does not mention interaction with -z 
o docs/43823   doc        [PATCH] update to environ(7) manpage
o docs/47818   doc        [patch] ln(1) manpage is confusing
o docs/48101   doc        [patch] add documentation on the fixit disk to the FAQ
o docs/50211   doc        [PATCH] doc.docbook.mk: fix textfile creation
o docs/53271   doc        bus_dma(9) fails to document alignment restrictions
o docs/53596   doc        Updates to mt(1) manual page
o docs/53751   doc        bus_dma(9) incorrectly documents BUS_DMA_ALLOCNOW
s docs/54752   doc        bus_dma explained in ISA section in Handbook: should b
o docs/57388   doc        [patch] INSTALL.TXT enhancement: mention ok prompt
o docs/59044   doc        [patch] doc.docbook.mk does not properly handle a sour
o docs/59477   doc        Outdated Info Documents at http://docs.freebsd.org/inf
o docs/59835   doc        ipfw(8) man page does not warn about accepted but mean
o docs/61301   doc        [patch] Manpage patch for aue(4) to enable HomePNA fun
o docs/69861   doc        [patch] usr.bin/csplit/csplit.1 does not document POSI
o docs/70652   doc        [patch] New man page: portindex(5)
o docs/75865   doc        comments on "backup-basics" in handbook
o docs/76333   doc        [patch] ferror(3): EOF indicator can be cleared by not
o docs/78138   doc        [patch] Error in pre-installation section of installat
o docs/78240   doc        [patch] handbook: replace <literal> with <quote> aroun
o docs/78480   doc        Networked printer setup unnecessarily complex in handb
f docs/82595   doc        25.5.3 Configuring a bridge section of the handbook ne
o docs/84265   doc        [patch] chmod(1) manpage omits implication of setting 
o docs/84268   doc        chmod(1) manpage's BUGS entry is either wrong or too c
o docs/84317   doc        fdp-primer doesn't show class=USERNAME distinctively
o docs/84670   doc        [patch] tput(1) manpage missing ENVIRONMENT section wi
o docs/84806   doc        mdoc(7) manpage has section ordering problems
o docs/84956   doc        [patch] intro(5) manpage doesn't mention API coverage
o docs/85118   doc        [PATCH] opiekey(1) references non-existing opiegen(1)
o docs/85128   doc        [patch] loader.conf(5) autoboot_delay incompletly desc
o docs/85187   doc        [patch] find(1) manpage missing block info for -ls
o docs/86342   doc        bikeshed entry of Handbook is wrong
o docs/87857   doc        ifconfig(8) wireless options order matters
o docs/87936   doc        Handbook chapter on NIS/YP lacks good information on a
o docs/88512   doc        [patch] mount_ext2fs(8) man page has no details on lar
o docs/91149   doc        read(2) can return EINVAL for unaligned access to bloc
o docs/91506   doc        ndis(4) man page should be more specific about support
o docs/92626   doc        jail manpage should mention disabling some periodic sc
o docs/94625   doc        [patch] growfs man page -- document "panic: not enough
o docs/95139   doc        FAQ to move filesystem to new disk fails: incorrect pe
o docs/96207   doc        Comments of a sockaddr_un structure could confuse one
o docs/98974   doc        Missing tunables in loader(8) manpage
o docs/99506   doc        FreeBSD Handbook addition:  IPv6 Server Settings
o docs/100196  doc        man login.conf does explain not "unlimited"
o docs/100242  doc        sysctl(3) description of KERN_PROC is not correct anym
o docs/101464  doc        sync ru_RU.KOI8-R/articles/portbuild/article.html with
o docs/102148  doc        The description of which Intel chips have EM64T is out
o docs/102719  doc        [patch] ng_bpf(4) example leads to unneeded promiscuos
o docs/104403  doc        man security should mention that the usage of the X Wi
o docs/104879  doc        Howto: Listen to IMA ADPCM .wav files on FreeBSD box
o docs/105608  doc        fdc(4) debugging description staled
o docs/105997  doc        sys/kern/sys_pipe.c refer to tuning(7), but there is n
o docs/108101  doc        /boot/default/loader.conf contains an incorrect commen
a docs/108980  doc        list of missing man pages
o docs/109115  doc        add Ultra 450 to hardware list for sparc64
o docs/109201  doc        [request]: manual for callbootd
f docs/109226  doc        [request] No manual entry for sntp
o docs/109972  doc        No manual entry for zless/bzless
o docs/109973  doc        No manual entry for c++filt
o docs/109975  doc        No manual entry for elf2aout
o docs/109977  doc        No manual entry for ksu
o docs/109981  doc        No manual entry for post-grohtml
o docs/109983  doc        No manual entry for protoize
o docs/110061  doc        [PATCH] tuning(7) missing reference to vfs.read_max
o docs/110062  doc        [patch] mount_nfs(8) fails to mention a failure condit
o docs/110376  doc        [patch] add some more explanations for the iwi/ipw fir
o docs/110692  doc        wi(4) man page doesn't say WPA is not supported
o docs/110999  doc        carp(4) should document unsupported interface types
o docs/111147  doc        hostapd.conf is not documented
o docs/111263  doc        [request] Information on $EDITOR variable in section 3
o docs/111265  doc        [request] Clarify how to set common shell variables
o docs/111425  doc        Missing chunks of text in historical manpages
o docs/112481  doc        bug in ppp.linkup example
o docs/112682  doc        Handbook GEOM_GPT explanation does not provide accurat
o docs/112804  doc        groff(1) command should be called to explicitly use "p
o docs/113194  doc        [patch] [request] crontab.5: handling of day-in-month 
o docs/114139  doc        mbuf(9) has misleading comments on M_DONTWAIT and M_TR
o docs/114184  doc        [patch] [ndis]: add info to man 4 ndis
o docs/114371  doc        [patch] [ip6] rtadvd.con(5) should show how to adverti
o docs/115065  doc        [patch] sync ps.1 with p_flag and keywords
o docs/115921  doc        Booting from pst(4) is not supported
o docs/116116  doc        mktemp (3) re/move note
o docs/116480  doc        sysctl(3) description of kern.file no longer applies s
o docs/117013  doc        mount_smbfs(8) doesn't document -U (username) argument
f docs/117308  doc        Clarification of /etc/defaults/devfs.rules status
o docs/117747  doc        'break' system call needs a man page
o docs/117798  doc        formatting oddity in sysmouse(4)
o docs/118020  doc        ipfilter(4): man pages query for man 4 ipfilter return
o docs/118214  doc        close(2) error returns incomplete
o docs/118332  doc        man page for top does not describe STATE column wait e
o docs/118545  doc        loader tunables kern.dfldsiz and friends nearly undocu
o docs/119329  doc        [patch] Fix misleading man 1 split
o docs/119338  doc        gprof(1) refers to unmentioned option "-c"
s docs/119404  doc        [request] events page should list only last 2 years wo
a docs/119536  doc        a few typos in French handbook (basics)
o docs/119746  doc        l10n chapter of handbook (Russian Language)
o docs/119907  doc        Ports compatibility
o docs/120024  doc        resolver(5) and hosts(5) need updated for IPv6
o docs/120040  doc        handbook: diskless operation: populate root doesn't po
o docs/120125  doc        [patch] Installing FreeBSD 7.0 via serial console and 
o docs/120539  doc        Inconsistent ipfw's man page
o docs/120628  doc        PAE documentation errror in handbook
s docs/120917  doc        [request]: Man pages mising for thr_xxx syscalls
o docs/121173  doc        [patch] mq_getattr(2): mq_flags mistakenly described a
o docs/121197  doc        [patch] edits to books/porters-handbook
s docs/121541  doc        [request] no man pages for wlan_scan_ap
o docs/121565  doc        dhcp-options(5) manpage incorrectly formatted omitting
o docs/121585  doc        [handbook] Wrong multicast specification
o docs/121871  doc        ftpd does not interpret configuration files as documen
o docs/121952  doc        Handbook chapter on Network Address Translation wrong 
o docs/122052  doc        minor update on handbook section 20.7.1
o docs/122053  doc        [patch] update on vinum(4) reference to newfs(8)
o docs/122470  doc        [patch] exit status on fetch(1) manual page
o docs/123035  doc        [patch] bugs in refuse.README
o docs/123400  doc        gvinum startup in handbook
p docs/124166  doc        fortune: instant-workstation tip should go
o docs/124716  doc        [patch] GEOM RAID1 handbook example only covers boot p
o www/125092   doc        [patch] Addition to AMD64 supported platforms: Tyan Ti
o docs/125581  doc        In manpages on i386, there are two same name files. ma
o docs/125639  doc        [patch] kldunloadf(2) does not mention about possible 
o docs/125751  doc        man 3 pthread_getschedparam section ERRORS incomplete
o docs/125896  doc        [PATCH] arp manual and syntax synchronisation
o docs/125921  doc        lpd(8) talks about blocks in minfree while it is KB in
o docs/126227  doc        [patch] kthread(9) refers to non-existent manpage, des
o docs/126445  doc        discussion on WEP settings in wpa_supplicant.conf man 
o docs/126451  doc        Exit status of nc(1) is not documented

135 problems total.

From marc at blackend.org  Mon Aug 11 11:16:51 2008
From: marc at blackend.org (Marc Fonvieille)
Date: Mon Aug 11 11:16:58 2008
Subject: wep key index in examples of section 29.3 in handbook
In-Reply-To: <70ec82800808110235g293bd777i647e13873d640f35@mail.gmail.com>
References: <70ec82800808110235g293bd777i647e13873d640f35@mail.gmail.com>
Message-ID: <20080811103525.GA1022@gothic.blackend.org>

On Mon, Aug 11, 2008 at 02:35:14AM -0700, Krishna Mohan Gundu wrote:
> Hi,
> 
> After I put some effort into building a ndis driver for my wireless
> 802.11g card, I proceeded to configure the network. For me the section
> that seemed to be most relevant was "29.3.3.1.4 WEP". So I chose the
> example as a template to configure my device. In the hindsight, after
> spending a few hours in correctly configuring my wireless device, I
> realized that the document could have saved me those hours if only it
> had used wep key index of 1 instead 3 in the example. I would like to
> raise the following concerns
> 
> 1) A novice would not know that WEP access points can use any of the
> four keys it uses for encryption and that all these keys have to be
> set correctly. I got to know this only after reading the wikipedia
> page on WEP at http://en.wikipedia.org/wiki/Wired_Equivalent_Privacy .
> Further that most access points only use one key and I believe the
> index of this key is mostly 1. This discussion could be added to some
> subsection.
>

Hello,

But if we read this section we have:

---
WEP can be set up with ifconfig:

# ifconfig ath0 ssid my_net wepmode on weptxkey 3 wepkey 3:0x3456789012 \
	inet 192.168.1.100 netmask 255.255.255.0

	- The weptxkey means which WEP key will be used in the
	  transmission. Here we used the third key. This must match the
	  setting in the access point.
---

The answer of this problem is written just after the command line.

Regarding the reason why we used an example with the third key and not
the default 1, it's to push people to really check their config to make
sure what key they use.

> 2) The above discussion can be deemed to be too technical to be
> included in the document. However changing the wep key index from 3 to
> 1 would save many more novices like me hours of searching, reading,
> agony etc.
> 

The same will happen for people who have a config with a different key
from the number 1 :)

> The bottom line is "Is the wep key index most likely to be 1? If so
> the document should use that number in the examples."
> 

I dunno.  But when we talk about wireless it's difficult to give
examples that people could blindly copy&paste without reading the
following explanations.  Cause the command can work in many cases and
just not work in some others.

> Please let me know if I should file a document bug about this.

I'm not sure it's a bug since we clearly mention what key we use and
that people have to be sure what key they use.  We can s/1/3/ but this
doesn't change the fact some people will face up problems if they don't
read the surrounding text.

-- 
Marc
From marc at blackend.org  Mon Aug 11 11:18:05 2008
From: marc at blackend.org (Marc Fonvieille)
Date: Mon Aug 11 11:18:12 2008
Subject: wep key index in examples of section 29.3 in handbook
In-Reply-To: <20080811103525.GA1022@gothic.blackend.org>
References: <70ec82800808110235g293bd777i647e13873d640f35@mail.gmail.com>
	<20080811103525.GA1022@gothic.blackend.org>
Message-ID: <20080811111801.GC1022@gothic.blackend.org>

On Mon, Aug 11, 2008 at 12:35:25PM +0200, Marc Fonvieille wrote:
> On Mon, Aug 11, 2008 at 02:35:14AM -0700, Krishna Mohan Gundu wrote:
> > Hi,
> > 
> > After I put some effort into building a ndis driver for my wireless
> > 802.11g card, I proceeded to configure the network. For me the section
> > that seemed to be most relevant was "29.3.3.1.4 WEP". So I chose the
> > example as a template to configure my device. In the hindsight, after
> > spending a few hours in correctly configuring my wireless device, I
> > realized that the document could have saved me those hours if only it
> > had used wep key index of 1 instead 3 in the example. I would like to
> > raise the following concerns
> > 
> > 1) A novice would not know that WEP access points can use any of the
> > four keys it uses for encryption and that all these keys have to be
> > set correctly. I got to know this only after reading the wikipedia
> > page on WEP at http://en.wikipedia.org/wiki/Wired_Equivalent_Privacy .
> > Further that most access points only use one key and I believe the
> > index of this key is mostly 1. This discussion could be added to some
> > subsection.
> >
> 
> Hello,
> 
> But if we read this section we have:
> 
> ---
> WEP can be set up with ifconfig:
> 
> # ifconfig ath0 ssid my_net wepmode on weptxkey 3 wepkey 3:0x3456789012 \
> 	inet 192.168.1.100 netmask 255.255.255.0
> 
> 	- The weptxkey means which WEP key will be used in the
> 	  transmission. Here we used the third key. This must match the
> 	  setting in the access point.
> ---
> 
> The answer of this problem is written just after the command line.
> 
> Regarding the reason why we used an example with the third key and not
> the default 1, it's to push people to really check their config to make
> sure what key they use.
[...]

Sorry I misread, you talked about the "index".  The same remark can be
done, the text following the command line explains the "3":
	
	- The wepkey means setting the selected WEP key. It should in
	  the format index:key, if the index is not given, key 1 is set.
	  That is to say we need to set the index if we use keys other
	  than the first key.

I'll stop to pasting, the rest of the text also invites the read to look
for more information inside ifconfig(8) manual page and the
/etc/wpa_supplicant.conf config rings bells one this points.

-- 
Marc
From gkmohan at gmail.com  Mon Aug 11 12:05:05 2008
From: gkmohan at gmail.com (Krishna Mohan Gundu)
Date: Mon Aug 11 12:05:11 2008
Subject: wep key index in examples of section 29.3 in handbook
In-Reply-To: <20080811103525.GA1022@gothic.blackend.org>
References: <70ec82800808110235g293bd777i647e13873d640f35@mail.gmail.com>
	<20080811103525.GA1022@gothic.blackend.org>
Message-ID: <70ec82800808110505r4b2840c7tfab4ff456e890653@mail.gmail.com>

Hi Marc,

At the outset let me just say that I understand the perspective of
your argument. However I still feel there is room for improvement in
the document.

>> 1) A novice would not know that WEP access points can use any of the
>> four keys it uses for encryption and that all these keys have to be
>> set correctly. I got to know this only after reading the wikipedia
>> page on WEP at http://en.wikipedia.org/wiki/Wired_Equivalent_Privacy .
>> Further that most access points only use one key and I believe the
>> index of this key is mostly 1. This discussion could be added to some
>> subsection.
>
> But if we read this section we have:
>
> ---
> WEP can be set up with ifconfig:
>
> # ifconfig ath0 ssid my_net wepmode on weptxkey 3 wepkey 3:0x3456789012 \
>        inet 192.168.1.100 netmask 255.255.255.0
>
>        - The weptxkey means which WEP key will be used in the
>          transmission. Here we used the third key. This must match the
>          setting in the access point.
> ---
> Regarding the reason why we used an example with the third key and not
> the default 1, it's to push people to really check their config to make
> sure what key they use.

I did read this note. My wireless router configuration has no mention
of different keys. It simply takes a key for encryption. So I was
immediately thrown off this key business. Third key did not make any
sense to me. The fact that some access points have provision for only
one key is not clear from any documentation. Probably it helps here if
a note like this is added

"Some access points take only one key, in which case use 1 for key index"

>> 2) The above discussion can be deemed to be too technical to be
>> included in the document. However changing the wep key index from 3 to
>> 1 would save many more novices like me hours of searching, reading,
>> agony etc.
>>
>
> The same will happen for people who have a config with a different key
> from the number 1 :)

In this case, I believe people will be aware of the fact that access
points use multiple keys. If they have configured the router
themselves, they will be aware that for some reason they have chosen
such and such keys.

cheers,
Krishna.
From blackend at freebsd.org  Mon Aug 11 12:21:03 2008
From: blackend at freebsd.org (Marc Fonvieille)
Date: Mon Aug 11 12:21:10 2008
Subject: wep key index in examples of section 29.3 in handbook
In-Reply-To: <70ec82800808110505r4b2840c7tfab4ff456e890653@mail.gmail.com>
References: <70ec82800808110235g293bd777i647e13873d640f35@mail.gmail.com>
	<20080811103525.GA1022@gothic.blackend.org>
	<70ec82800808110505r4b2840c7tfab4ff456e890653@mail.gmail.com>
Message-ID: <20080811122059.GD1022@gothic.blackend.org>

On Mon, Aug 11, 2008 at 05:05:01AM -0700, Krishna Mohan Gundu wrote:
> Hi Marc,
>
[...]

> I did read this note. My wireless router configuration has no mention
> of different keys. It simply takes a key for encryption. So I was
> immediately thrown off this key business. Third key did not make any
> sense to me. The fact that some access points have provision for only
> one key is not clear from any documentation. Probably it helps here if
> a note like this is added
> 
> "Some access points take only one key, in which case use 1 for key index"
>

Ok, I see.  What do you think about something like:

"Note: If you do not have any idea of what is the key used by your
access point, you should try to use 1 for both of the key and the
index."

-- 
Marc
From joseph.koshy at gmail.com  Tue Aug 12 12:14:38 2008
From: joseph.koshy at gmail.com (Joseph Koshy)
Date: Tue Aug 12 12:14:44 2008
Subject: MarkMail indexing FreeBSD mailing lists
In-Reply-To: <20080807180823.GA50174@root.ucsc.edu>
References: <20080807180823.GA50174@root.ucsc.edu>
Message-ID: <84dead720808120450pc7584c3je8c07a7ef7708c1a@mail.gmail.com>

> There is an outdated link on
>
>  http://www.freebsd.org/search/search.html#mailinglists
>
> that points to GeoCrawler.  I would suggest replacing that with the
> MarkMail link.

Link updated, thanks.

Koshy
From rfg at tristatelogic.com  Tue Aug 12 20:50:02 2008
From: rfg at tristatelogic.com (Ronald F.Guilmette)
Date: Tue Aug 12 20:50:08 2008
Subject: docs/126484: libc function res-zonscut2 is not documented
Message-ID: <20080812204607.56587BDC36@segfault.tristatelogic.com>


>Number:         126484
>Category:       docs
>Synopsis:       libc function res-zonscut2 is not documented
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Aug 12 20:50:01 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Ronald F. Guilmette
>Release:        FreeBSD 7.0-RELEASE i386
>Organization:
Infinite Monkeys & Co. LLC
>Environment:
System: FreeBSD 7.0-RELEASE

>Description:
	The resolver library routine called res_findzonecut2 which is part
	of libc isn't documented on any man page... at least none that I've
	found.  But this is a useful function, and should have a man page.

>How-To-Repeat:
	man res_findzonecut2
	man res_findzonecut
	man 3 resolver

	(The first two commands above just produce errors.  The third shows
	that the man page which documents all of the other res_* resolver
	library routines fails to even mention res_findzonecut.

>Fix:
	The man page for resolver(3) should be enhanced so as to also
	document res_findzonecut2.

	Depending on how the folks at IBM feel about it, you could probably
	just snatch most of the verbage necessary to document this function
	from the following URL:

	http://publib.boulder.ibm.com/infocenter/iseries/v5r3/index.jsp?topic=/apis/resfindzonecut.htm

	...where IBM seems to have already done a pretty Nice Job of documenting
	the original res_findzonecut function.  Note however that in the
	res_findzonecut2 function, the 7th parameter has type
	(union res_sockaddr_union *) rather than type (struct in_addr *) as
	for the original function, res_findzonecut.
>Release-Note:
>Audit-Trail:
>Unformatted:
From delphij at FreeBSD.org  Tue Aug 12 21:56:09 2008
From: delphij at FreeBSD.org (delphij@FreeBSD.org)
Date: Tue Aug 12 21:56:16 2008
Subject: docs/126451: Exit status of nc(1) is not documented
Message-ID: <200808122156.m7CLu9ZM069921@freefall.freebsd.org>

Synopsis: Exit status of nc(1) is not documented

Responsible-Changed-From-To: freebsd-doc->delphij
Responsible-Changed-By: delphij
Responsible-Changed-When: Tue Aug 12 21:55:54 UTC 2008
Responsible-Changed-Why: 
Take.

http://www.freebsd.org/cgi/query-pr.cgi?pr=126451
From edwin at mavetju.org  Wed Aug 13 01:10:02 2008
From: edwin at mavetju.org (Edwin Groothuis)
Date: Wed Aug 13 01:10:08 2008
Subject: docs/126487: fix language on atol(3) manpage
Message-ID: <20080813010647.D5860791@k7.mavetju>


>Number:         126487
>Category:       docs
>Synopsis:       fix language on atol(3) manpage
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Wed Aug 13 01:10:01 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Edwin Groothuis
>Release:        FreeBSD 7.0-RELEASE-p1 i386
>Organization:
-
>Environment:
System: FreeBSD k7.mavetju 7.0-RELEASE-p1 FreeBSD 7.0-RELEASE-p1 #2: Wed May 28 08:12:56 EST 2008 edwin@k7.mavetju:/usr/src/sys/i386/compile/k7 i386


>Description:

Man page now says:

ERRORS
     The functions atol() and atoll() need not affect the value of errno on an
     error.

That line doesn't make sense, it should be replaced with:

ERRORS
     The functions atol() and atoll() do not affect the value of errno on an
     error.

or

ERRORS
     The functions atol() and atoll() do not affect the value of
     errno in case of an error.

>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
From edwin at mavetju.org  Wed Aug 13 05:50:03 2008
From: edwin at mavetju.org (Edwin Groothuis)
Date: Wed Aug 13 05:50:10 2008
Subject: docs/126487: fix language on atol(3) manpage
Message-ID: <200808130550.m7D5o3iS018088@freefall.freebsd.org>

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

From: Edwin Groothuis <edwin@mavetju.org>
To: FreeBSD Gnats Submit <freebsd-gnats-submit@freebsd.org>
Cc:  
Subject: Re: docs/126487: fix language on atol(3) manpage
Date: Wed, 13 Aug 2008 15:46:06 +1000

 On Wed, Aug 13, 2008 at 01:10:01AM +0000, FreeBSD-gnats-submit@FreeBSD.org wrote:
 > 
 
 After discussions with bjk on #bsddocs:
 
 If, for some reason, it *might* change it, then it should read:
 
 ERRORS
 	The functions atol() and atoll() might affect the value of
 	errno in case of an error.
 
 -- 
 Edwin Groothuis      |            Personal website: http://www.mavetju.org
 edwin@mavetju.org    |              Weblog: http://www.mavetju.org/weblog/
From gkmohan at gmail.com  Wed Aug 13 10:09:39 2008
From: gkmohan at gmail.com (Krishna Mohan Gundu)
Date: Wed Aug 13 10:09:45 2008
Subject: wep key index in examples of section 29.3 in handbook
In-Reply-To: <20080811122059.GD1022@gothic.blackend.org>
References: <70ec82800808110235g293bd777i647e13873d640f35@mail.gmail.com>
	<20080811103525.GA1022@gothic.blackend.org>
	<70ec82800808110505r4b2840c7tfab4ff456e890653@mail.gmail.com>
	<20080811122059.GD1022@gothic.blackend.org>
Message-ID: <70ec82800808130309w3e4ba69cj9aefb3eeab15cfea@mail.gmail.com>

Hi Marc,

> Ok, I see.  What do you think about something like:
>
> "Note: If you do not have any idea of what is the key used by your
> access point, you should try to use 1 for both of the key and the
> index."

If I may correct

"Note: If you do not have any idea of what key is used by your
access point, you should try to use 1 for both <code>weptxkey</code>
and <i>index</i>."

I think using same formatting style and names introduces less ambiguity.

cheers,
Krishna.
From wtnelson at gmail.com  Wed Aug 13 19:21:09 2008
From: wtnelson at gmail.com (William T)
Date: Wed Aug 13 19:21:16 2008
Subject: retailers
Message-ID: <c4f6226b0808131152q303a504cn24c24871bbe6771d@mail.gmail.com>

Fry's and CompUSA do not sell FreeBSD. At least, the CDs are no longer
on their websites.

I am wondering if they can be removed from Appendix A of the FreeBSD handbook.
From r.c.ladan at gmail.com  Thu Aug 14 08:30:03 2008
From: r.c.ladan at gmail.com (Rene Ladan)
Date: Thu Aug 14 08:30:10 2008
Subject: docs/126528: Contributors article: update my email address
Message-ID: <200808140822.m7E8Mfqa067368@www.freebsd.org>


>Number:         126528
>Category:       docs
>Synopsis:       Contributors article: update my email address
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Thu Aug 14 08:30:01 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Rene Ladan
>Release:        7.0R amd64
>Organization:
>Environment:
>Description:
Update my email address, the currently listed one has expired.
>How-To-Repeat:

>Fix:
apply patch to en/articles/contributors/contrib.additional.sgml

Patch attached with submission follows:

--- contrib.additional.sgml.orig	2008-08-02 13:02:21.000000000 +0200
+++ contrib.additional.sgml	2008-08-14 10:17:03.000000000 +0200
@@ -7885,7 +7885,7 @@
 
     <listitem>
       <para>Ren&eacute; C. Ladan
-	<email>r.c.ladan@student.tue.nl</email></para>
+	<email>r.c.ladan@gmail.com</email></para>
     </listitem>
 
     <listitem>


>Release-Note:
>Audit-Trail:
>Unformatted:
From newsonia at 163.com  Thu Aug 14 13:00:07 2008
From: newsonia at 163.com (newsonia)
Date: Thu Aug 14 13:00:13 2008
Subject: docs/126487: fix language on atol(3) manpage
Message-ID: <200808141300.m7ED06SQ002355@freefall.freebsd.org>

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

From: newsonia <newsonia@163.com>
To: "Edwin Groothuis" <edwin@mavetju.org>
Cc: FreeBSD-gnats-submit <FreeBSD-gnats-submit@FreeBSD.org>
Subject: Re:docs/126487: fix language on atol(3) manpage
Date: Thu, 14 Aug 2008 20:36:14 +0800 (CST)

 ------=_Part_197203_20533956.1218717374274
 Content-Type: text/plain; charset=GBK
 Content-Transfer-Encoding: quoted-printable
 
 You should change ports packet or upate your Ports
 
 
 =D4=DA2008-08-13=A3=AC"Edwin Groothuis" <edwin@mavetju.org> =D0=B4=B5=C0=A3=
 =BA
 
 
 
 >Number:         126487
 >Category:       docs
 >Synopsis:       fix language on atol(3) manpage
 >Confidential:   no
 >Severity:       non-critical
 >Priority:       low
 >Responsible:    freebsd-doc
 >State:          open
 >Quarter:       =20
 >Keywords:      =20
 >Date-Required:
 >Class:          change-request
 >Submitter-Id:   current-users
 >Arrival-Date:   Wed Aug 13 01:10:01 UTC 2008
 >Closed-Date:
 >Last-Modified:
 >Originator:     Edwin Groothuis
 >Release:        FreeBSD 7.0-RELEASE-p1 i386
 >Organization:
 -
 >Environment:
 System: FreeBSD k7.mavetju 7.0-RELEASE-p1 FreeBSD 7.0-RELEASE-p1 #2: Wed Ma=
 y 28 08:12:56 EST 2008 edwin@k7.mavetju:/usr/src/sys/i386/compile/k7 i386
 
 
 >Description:
 
 Man page now says:
 
 ERRORS
      The functions atol() and atoll() need not affect the value of errno on=
  an
      error.
 
 That line doesn't make sense, it should be replaced with:
 
 ERRORS
      The functions atol() and atoll() do not affect the value of errno on a=
 n
      error.
 
 or
 
 ERRORS
      The functions atol() and atoll() do not affect the value of
      errno in case of an error.
 
 >How-To-Repeat:
 >Fix:
 >Release-Note:
 >Audit-Trail:
 >Unformatted:
 _______________________________________________
 freebsd-doc@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-doc
 To unsubscribe, send any mail to "freebsd-doc-unsubscribe@freebsd.org"
 =20
 
 ------=_Part_197203_20533956.1218717374274
 Content-Type: text/html; charset=GBK
 Content-Transfer-Encoding: quoted-printable
 
 You should change ports packet or upate your Ports<br><br><br>=D4=DA2008-08=
 -13=A3=AC"Edwin Groothuis" &lt;edwin@mavetju.org&gt; =D0=B4=B5=C0=A3=BA<br>=
  <BLOCKQUOTE id=3D"isReplyContent" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px =
 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><pre>
 
 &gt;Number:         126487
 &gt;Category:       docs
 &gt;Synopsis:       fix language on atol(3) manpage
 &gt;Confidential:   no
 &gt;Severity:       non-critical
 &gt;Priority:       low
 &gt;Responsible:    freebsd-doc
 &gt;State:          open
 &gt;Quarter:       =20
 &gt;Keywords:      =20
 &gt;Date-Required:
 &gt;Class:          change-request
 &gt;Submitter-Id:   current-users
 &gt;Arrival-Date:   Wed Aug 13 01:10:01 UTC 2008
 &gt;Closed-Date:
 &gt;Last-Modified:
 &gt;Originator:     Edwin Groothuis
 &gt;Release:        FreeBSD 7.0-RELEASE-p1 i386
 &gt;Organization:
 -
 &gt;Environment:
 System: FreeBSD k7.mavetju 7.0-RELEASE-p1 FreeBSD 7.0-RELEASE-p1 #2: Wed Ma=
 y 28 08:12:56 EST 2008 edwin@k7.mavetju:/usr/src/sys/i386/compile/k7 i386
 
 
 &gt;Description:
 
 Man page now says:
 
 ERRORS
      The functions atol() and atoll() need not affect the value of errno on=
  an
      error.
 
 That line doesn't make sense, it should be replaced with:
 
 ERRORS
      The functions atol() and atoll() do not affect the value of errno on a=
 n
      error.
 
 or
 
 ERRORS
      The functions atol() and atoll() do not affect the value of
      errno in case of an error.
 
 &gt;How-To-Repeat:
 &gt;Fix:
 &gt;Release-Note:
 &gt;Audit-Trail:
 &gt;Unformatted:
 _______________________________________________
 freebsd-doc@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-doc
 To unsubscribe, send any mail to "freebsd-doc-unsubscribe@freebsd.org"
 =20
 <script language=3D"JavaScript"><!--
 =09if(window["gIsText"]){
 =09=09document.write('</pre>');
 =09}
 //--></script></pre>
 </BLOCKQUOTE>
 ------=_Part_197203_20533956.1218717374274--
 
From pgj at FreeBSD.org  Thu Aug 14 14:58:54 2008
From: pgj at FreeBSD.org (pgj@FreeBSD.org)
Date: Thu Aug 14 14:59:00 2008
Subject: docs/126528: Contributors article: update my email address
Message-ID: <200808141458.m7EEwrmr015384@freefall.freebsd.org>

Synopsis: Contributors article: update my email address

Responsible-Changed-From-To: freebsd-doc->pgj
Responsible-Changed-By: pgj
Responsible-Changed-When: Thu Aug 14 14:58:27 UTC 2008
Responsible-Changed-Why: 
Over to me.

http://www.freebsd.org/cgi/query-pr.cgi?pr=126528
From info at permissionrequest.com  Fri Aug 15 03:26:45 2008
From: info at permissionrequest.com (Booking Information)
Date: Fri Aug 15 03:26:52 2008
Subject: The Three Rock Tenors, The Orchestra and other avails
Message-ID: <20080815123716.E233268281FAE62B@permissionrequest.com>

Iif you are planning a 'SPECIAL EVENT', or involved with the booking of any 'FESTIVALS', 'CASINOS' and/or 'THEATRE CONCERTS' please contact us by replying to this e-mail.

Or you may opt-in for more booking inquiries in the future by visiting: http://www.permissionrequest.com/optin_ent.php?email=freebsd-doc@FreeBSD.org

ARTISTS AVAILABLE FOR YOUR CONSIDERATION

Classic Rock and Orchestral Rock Superstars
	* THE ORCHESTRA 
	Starring
	Electric Light Orchestra former members 

	* THE THREE ROCK TENORS
	Starring
	* CHUCK NEGRON formerly of Three Dog Night  (21 BILLBOARD top 40 hits) ***
	* BOBBY KIMBALL lead singer of Toto (10 BILLBOARD top 40 hits and 7 Grammys) ***
	* ERIC TROYER former lead voice of Electric Light Orchestra Pt2 (Multi Hit Tours, Records and Awards) ***

	*** The Three Rock Tenors are also available individually.

Motion Picture and Multi Grammy Award Winner:

	* MARIA CONCHITA ALONSO

Television Star and Billboard Top 10 Hit-Maker

	* VICKI LAWRENCE star of "Mama's Family"
	New Tour "Mama Runs for President"
	* Major Cast Member of "The Carol Burnett Show"

Family and Casino Entertainment Shows:

	* THE IMPERIAL CIRCUS® OF CHINA
	* THE SPIRIT OF SHAOLIN
	* OLE OLA SAMBA BRAZIL®









To opt-out of receiving future booking inquiries, please visit: http://www.permissionrequest.com/optout_ent.php?email=freebsd-doc@FreeBSD.org

From vmutu at pcbi.upenn.edu  Fri Aug 15 18:28:41 2008
From: vmutu at pcbi.upenn.edu (Valeriu Mutu)
Date: Fri Aug 15 18:28:47 2008
Subject: Improving pam.conf(5) manual page
Message-ID: <20080815180044.GF1327@bsdera.pcbi.upenn.edu>

Hi,

After experimenting with PAM lately I found the manual page pam.conf(5) somewhat confusing regarding the definition of the "sufficient" control flag:

sufficient = If this module succeeds, the chain is broken and the result is success.  If it fails, the rest of the chain still runs, but the final result will be failure unless a later module succeeds.

Nevertheless the chain isn't broken when there are modules with a "required" flag. Here is an example:
 auth            sufficient      pam_unix.so             debug no_warn try_first_pass
 auth            required        pam_deny.so             debug
Hence, pam_deny will be invoked even if pam_unix succeeds.

If the above is changed to:
 auth            sufficient      pam_unix.so             debug no_warn try_first_pass
 auth            sufficient      pam_deny.so             debug
then pam_deny isn't invoked as it has the "sufficient" flag now.

I checked the manual page for pam.conf(5) in FreeBSD 8-current and it contains the same definition of "sufficient" as shown above. I checked it here:
http://www.freebsd.org/cgi/man.cgi?query=pam.conf&apropos=0&sektion=0&manpath=FreeBSD+8-current&format=html

Hence, it would be helpful if the definition be changed to:

sufficient = If this module succeeds and the following modules are sufficient, the chain is broken and the result is success. If it fails, the rest of the chain still runs, but the final result will be failure unless a later module succeeds.

Valeriu

-- 
Valeriu Mutu
Penn Center for Bioinformatics
215-573-8119
From www at FreeBSD.org  Sun Aug 17 02:36:13 2008
From: www at FreeBSD.org (World Wide Web Owner)
Date: Sun Aug 17 02:36:20 2008
Subject: FreeBSD web build failed on www.freebsd.org
Message-ID: <200808170236.m7H2aDfd066227@www.freebsd.org>

/usr/bin/perl5 -i'' -npe 's,"-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN","-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd",' x11-toolkits.html
/usr/bin/sed -e 's/<!ENTITY date[ \t]*"$Free[B]SD. .* \(.* .*\) .* .* $">/<!ENTITY date	"Last modified: \1">/'   x11-wm.sgml > x11-wm.sgml-tmp
/usr/bin/env SGML_CATALOG_FILES=  /usr/local/bin/sgmlnorm -d -ifreebsd.urls.absolute -c /usr/local/share/sgml/html/catalog -c /usr/local/share/sgml/catalog -c /w/www/build/www/ja/share/sgml/catalog -c /w/www/build/www/share/sgml/catalog -D /w/www/build/www/ja/ports x11-wm.sgml-tmp > x11-wm.html ||  (/bin/rm -f x11-wm.sgml-tmp x11-wm.html && false)
/bin/rm -f x11-wm.sgml-tmp
/usr/bin/perl5 -i'' -npe 's,"-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN","-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd",' x11-wm.html
/usr/bin/sed -e 's/<!ENTITY date[ \t]*"$Free[B]SD. .* \(.* .*\) .* .* $">/<!ENTITY date	"Last modified: \1">/'   x11.sgml > x11.sgml-tmp
/usr/bin/env SGML_CATALOG_FILES=  /usr/local/bin/sgmlnorm -d -ifreebsd.urls.absolute -c /usr/local/share/sgml/html/catalog -c /usr/local/share/sgml/catalog -c /w/www/build/www/ja/share/sgml/catalog -c /w/www/build/www/share/sgml/catalog -D /w/www/build/www/ja/ports x11.sgml-tmp > x11.html ||  (/bin/rm -f x11.sgml-tmp x11.html && false)
/bin/rm -f x11.sgml-tmp
/usr/bin/perl5 -i'' -npe 's,"-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN","-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd",' x11.html
/usr/bin/sed -e 's/<!ENTITY date[ \t]*"$Free[B]SD. .* \(.* .*\) .* .* $">/<!ENTITY date	"Last modified: \1">/'   xfce.sgml > xfce.sgml-tmp
/usr/bin/env SGML_CATALOG_FILES=  /usr/local/bin/sgmlnorm -d -ifreebsd.urls.absolute -c /usr/local/share/sgml/html/catalog -c /usr/local/share/sgml/catalog -c /w/www/build/www/ja/share/sgml/catalog -c /w/www/build/www/share/sgml/catalog -D /w/www/build/www/ja/ports xfce.sgml-tmp > xfce.html ||  (/bin/rm -f xfce.sgml-tmp xfce.html && false)
/bin/rm -f xfce.sgml-tmp
/usr/bin/perl5 -i'' -npe 's,"-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN","-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd",' xfce.html
/usr/bin/sed -e 's/<!ENTITY date[ \t]*"$Free[B]SD. .* \(.* .*\) .* .* $">/<!ENTITY date	"Last modified: \1">/'   zope.sgml > zope.sgml-tmp
/usr/bin/env SGML_CATALOG_FILES=  /usr/local/bin/sgmlnorm -d -ifreebsd.urls.absolute -c /usr/local/share/sgml/html/catalog -c /usr/local/share/sgml/catalog -c /w/www/build/www/ja/share/sgml/catalog -c /w/www/build/www/share/sgml/catalog -D /w/www/build/www/ja/ports zope.sgml-tmp > zope.html ||  (/bin/rm -f zope.sgml-tmp zope.html && false)
/bin/rm -f zope.sgml-tmp
/usr/bin/perl5 -i'' -npe 's,"-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN","-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd",' zope.html
===> ../ja/doc
===> ../ja/doc/articles (all)
===> ../ja/doc/articles/contributing (all)
/bin/rm -f docbook.css
/bin/cat /w/www/build/doc/share/misc/docbook.css > docbook.css
Index is disabled or no index to generate.
/usr/bin/env  /usr/local/bin/jade -V html-manifest -ioutput.html -d /w/www/build/doc/share/sgml/default.dsl -ifreebsd.urls.relprefix.4 -V %generate-legalnotice-link% -V %generate-article-toc% -V %generate-docformat-navi-link% -ioutput.html.images   -D /w/www/build/doc/ja_JP.eucJP/articles/contributing/../../../share/images/articles/contributing -D /usr/obj/w/www/build/doc/ja_JP.eucJP/articles/contributing -c /w/www/build/doc/ja_JP.eucJP/share/sgml/catalog -c /w/www/build/doc/share/sgml/catalog -c /usr/local/share/sgml/docbook/dsssl/modular/catalog -c /usr/local/share/sgml/iso8879/catalog -c /usr/local/share/sgml/jade/catalog -c /usr/local/share/sgml/catalog.ports -t sgml /w/www/build/doc/ja_JP.eucJP/articles/contributing/article.sgml
/usr/local/bin/tidy -wrap 90 -m -raw -preserve -f /dev/null -asxml  $(/usr/bin/xargs < HTML.manifest)
Index is disabled or no index to generate.
*** Error code 1 (ignored)
/usr/bin/env  /usr/local/bin/jade -V nochunks -ioutput.html -d /w/www/build/doc/share/sgml/default.dsl -ifreebsd.urls.relprefix.4 -V %generate-legalnotice-link% -V %generate-article-toc% -V %generate-docformat-navi-link% -ioutput.html.images   -D /w/www/build/doc/ja_JP.eucJP/articles/contributing/../../../share/images/articles/contributing -D /usr/obj/w/www/build/doc/ja_JP.eucJP/articles/contributing -c /w/www/build/doc/ja_JP.eucJP/share/sgml/catalog -c /w/www/build/doc/share/sgml/catalog -c /usr/local/share/sgml/docbook/dsssl/modular/catalog -c /usr/local/share/sgml/iso8879/catalog -c /usr/local/share/sgml/jade/catalog -c /usr/local/share/sgml/catalog.ports -t sgml /w/www/build/doc/ja_JP.eucJP/articles/contributing/article.sgml > article.html ||  (/bin/rm -f article.html && false)
/usr/local/bin/tidy -wrap 90 -m -raw -preserve -f /dev/null -asxml  article.html
*** Error code 1 (ignored)
===> ../ja/doc/articles/contributors (all)
make: don't know how to make /w/www/build/doc/en_US.ISO8859-1/articles/contributors/contrib.core.sgml. Stop
*** Error code 2

Stop in /w/www/build/doc/ja_JP.eucJP/articles.
*** Error code 1

Stop in /w/www/build/doc/ja_JP.eucJP.
*** Error code 1

Stop in /w/www/build/www/ja/doc.
*** Error code 1 (ignored)
*** Error code 1

Stop in /w/www/build/www/ja.
*** Error code 1 (ignored)
*** Error code 1

Stop in /w/www/build/www/en.
     4327.49 real      3955.36 user       284.15 sys
From bmah at freebsd.org  Sun Aug 17 13:08:00 2008
From: bmah at freebsd.org (Bruce A. Mah)
Date: Sun Aug 17 13:08:07 2008
Subject: Errata errata
In-Reply-To: <489A1154.1070500@gmail.com>
References: <489A1154.1070500@gmail.com>
Message-ID: <48A822AA.9000401@freebsd.org>

If memory serves me right, Walter Venable wrote:
> Shouldn't section "2 Security Advisories" on 
> http://www.freebsd.org/releases/7.0R/errata.html contain a link and 
> mention to 
> http://security.freebsd.org/advisories/FreeBSD-SA-08:06.bind.asc ?

Yes, it should, thanks for the reminder!  I've updated the errata...it
should show up on the Web site within the next few hours.

Bruce.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 257 bytes
Desc: OpenPGP digital signature
Url : http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20080817/0bfe5614/signature.pgp
From jacek at wikiera.net  Sun Aug 17 13:30:02 2008
From: jacek at wikiera.net (Jacek Wikiera)
Date: Sun Aug 17 13:30:08 2008
Subject: docs/126590: Write routine called forever in Sample Echo
	Pseudo-Device Driver
Message-ID: <200808171323.m7HDN2Ha087622@www.freebsd.org>


>Number:         126590
>Category:       docs
>Synopsis:       Write routine called forever in Sample Echo Pseudo-Device Driver
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Aug 17 13:30:01 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Jacek Wikiera
>Release:        n/a
>Organization:
n/a
>Environment:
n/a
>Description:
Location:
FreeBSD Architecture Handbook, 9.4 Character Devices,  example driver code.

http://www.freebsd.org/doc/en_US.ISO8859-1/books/arch-handbook/driverbasics-char.html

Description:
The function echo_write() is incorrect - it does not zero an important variable and makes the example a bad example.
If code is built from the example, the function echo_write() does not zeroe uio->uio_resid and thus fails to tell the OS that all the data has been consumed.

The function is called again and again forever (until the caller is terminated, I guess).


>How-To-Repeat:
Build the example code, and type at the command prompt:
cat > /dev/echo

Next type a line followed by return. This will cause the file /dev/echo to be open, and continuous calls to echo_write subroutine.

The cat program will hang now and not able to read Ctrl-D from the terminal. Ctrl-C is needed.
>Fix:
In the function echo_write() add the following line:

uio->uio_resid = 0; 

This will tell the OS that all the data has been consumed.
See the source of the null device for this hint.



Patch attached with submission follows:

--- driverbasics-char.html      2008-08-16 06:08:26.000000000 +0200
+++ driverbasics-char_fix.html  2008-08-17 15:10:37.531250000 +0200
@@ -200,6 +200,8 @@
     *(echomsg-&gt;msg + MIN(uio-&gt;uio_iov-&gt;iov_len, BUFFERSIZE - 1)) = 0;
     echomsg-&gt;len = MIN(uio-&gt;uio_iov-&gt;iov_len, BUFFERSIZE);
 
+    uio->uio_resid = 0; /* signall that all data is consumed */
+
     if (err != 0) {
         uprintf("Write failed: bad address!\n");
     }


>Release-Note:
>Audit-Trail:
>Unformatted:
From bugmaster at FreeBSD.org  Mon Aug 18 11:06:06 2008
From: bugmaster at FreeBSD.org (FreeBSD bugmaster)
Date: Mon Aug 18 11:06:36 2008
Subject: Current unassigned doc problem reports
Message-ID: <200808181106.m7IB65WP078874@freefall.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\nexperimental development code and obsolete releases.\n
Bugs can be in one of several states:

o - open
A problem report has been submitted, no sanity checking performed.

a - analyzed
The problem is understood and a solution is being sought.

f - feedback
Further work requires additional information from the
     originator or the community - possibly confirmation of
     the effectiveness of a proposed solution.

p - patched
A patch has been committed, but some issues (MFC and / or
     confirmation from originator) are still open.

r - repocopy
The resolution of the problem report is dependent on
     a repocopy operation within the CVS repository which
     is awaiting completion.

s - suspended
The problem is not being worked on, due to lack of information
     or resources.  This is a prime candidate
     for somebody who is looking for a project to do.
     If the problem cannot be solved at all,
     it will be closed, rather than suspended.

c - closed
A problem report is closed when any changes have been integrated,
     documented, and tested -- or when fixing the problem is abandoned.

Critical problems
Serious problems

S Tracker      Resp.      Description
--------------------------------------------------------------------------------
o docs/27605   doc        [patch] Cross-document references (<olink>)
s docs/35678   doc        docproj Makefiles for web are broken for paths with sp
o docs/61605   doc        [request] Improve documentation for i386 disk geometry
o docs/84932   doc        new document: printing with an Epson ALC-3000N on Free
o docs/98115   doc        Missing parts after rendering handbook to RTF format
o docs/106135  doc        [request] articles/vinum needs to be updated
o docs/110253  doc        [patch] rtprio(1): remove processing starvation commen
o docs/116080  doc        PREFIX is documented, but not the more important LOCAL
o docs/118902  doc        [patch] wrong signatures in d2i_RSAPublicKey man pages
o docs/119545  doc        books/arch-handbook/usb/chapter.sgml formatting
o docs/120456  doc        ath(4) needs to specify requirement on wlan_scan_sta
o docs/121312  doc        RELNOTES_LANG breaks release if not en_US.ISO8859-1

12 problems total.

Non-critical problems

S Tracker      Resp.      Description
--------------------------------------------------------------------------------
s docs/20028   doc        ASCII docs should reflect <emphasis> tags in the sourc
o docs/24786   doc        missing FILES descriptions in sa(4)
o docs/26286   doc        *printf(3) etc should gain format string warnings
a docs/30008   doc        [patch] French softupdates document should be translat
s docs/33589   doc        [patch] to doc.docbook.mk to post process .tex files.
o docs/36449   doc        symlink(7) manual doesn't mention trailing slash, etc.
o docs/38556   doc        EPS file of beastie, as addition to existing examples
o docs/38982   doc        [patch] developers-handbook/Jail fix
o docs/40423   doc        Keyboard(4)'s definition of parameters to GETFKEY/SETF
o docs/41089   doc        pax(1) -B option does not mention interaction with -z 
o docs/43823   doc        [PATCH] update to environ(7) manpage
o docs/47818   doc        [patch] ln(1) manpage is confusing
o docs/48101   doc        [patch] add documentation on the fixit disk to the FAQ
o docs/50211   doc        [PATCH] doc.docbook.mk: fix textfile creation
o docs/53271   doc        bus_dma(9) fails to document alignment restrictions
o docs/53596   doc        Updates to mt(1) manual page
o docs/53751   doc        bus_dma(9) incorrectly documents BUS_DMA_ALLOCNOW
s docs/54752   doc        bus_dma explained in ISA section in Handbook: should b
o docs/57388   doc        [patch] INSTALL.TXT enhancement: mention ok prompt
o docs/59044   doc        [patch] doc.docbook.mk does not properly handle a sour
o docs/59477   doc        Outdated Info Documents at http://docs.freebsd.org/inf
o docs/59835   doc        ipfw(8) man page does not warn about accepted but mean
o docs/61301   doc        [patch] Manpage patch for aue(4) to enable HomePNA fun
o docs/69861   doc        [patch] usr.bin/csplit/csplit.1 does not document POSI
o docs/70652   doc        [patch] New man page: portindex(5)
o docs/75865   doc        comments on "backup-basics" in handbook
o docs/76333   doc        [patch] ferror(3): EOF indicator can be cleared by not
o docs/78138   doc        [patch] Error in pre-installation section of installat
o docs/78240   doc        [patch] handbook: replace <literal> with <quote> aroun
o docs/78480   doc        Networked printer setup unnecessarily complex in handb
f docs/82595   doc        25.5.3 Configuring a bridge section of the handbook ne
o docs/84265   doc        [patch] chmod(1) manpage omits implication of setting 
o docs/84268   doc        chmod(1) manpage's BUGS entry is either wrong or too c
o docs/84317   doc        fdp-primer doesn't show class=USERNAME distinctively
o docs/84670   doc        [patch] tput(1) manpage missing ENVIRONMENT section wi
o docs/84806   doc        mdoc(7) manpage has section ordering problems
o docs/84956   doc        [patch] intro(5) manpage doesn't mention API coverage
o docs/85118   doc        [PATCH] opiekey(1) references non-existing opiegen(1)
o docs/85128   doc        [patch] loader.conf(5) autoboot_delay incompletly desc
o docs/85187   doc        [patch] find(1) manpage missing block info for -ls
o docs/86342   doc        bikeshed entry of Handbook is wrong
o docs/87857   doc        ifconfig(8) wireless options order matters
o docs/87936   doc        Handbook chapter on NIS/YP lacks good information on a
o docs/88512   doc        [patch] mount_ext2fs(8) man page has no details on lar
o docs/91149   doc        read(2) can return EINVAL for unaligned access to bloc
o docs/91506   doc        ndis(4) man page should be more specific about support
o docs/92626   doc        jail manpage should mention disabling some periodic sc
o docs/94625   doc        [patch] growfs man page -- document "panic: not enough
o docs/95139   doc        FAQ to move filesystem to new disk fails: incorrect pe
o docs/96207   doc        Comments of a sockaddr_un structure could confuse one
o docs/98974   doc        Missing tunables in loader(8) manpage
o docs/99506   doc        FreeBSD Handbook addition:  IPv6 Server Settings
o docs/100196  doc        man login.conf does explain not "unlimited"
o docs/100242  doc        sysctl(3) description of KERN_PROC is not correct anym
o docs/101464  doc        sync ru_RU.KOI8-R/articles/portbuild/article.html with
o docs/102148  doc        The description of which Intel chips have EM64T is out
o docs/102719  doc        [patch] ng_bpf(4) example leads to unneeded promiscuos
o docs/104403  doc        man security should mention that the usage of the X Wi
o docs/104879  doc        Howto: Listen to IMA ADPCM .wav files on FreeBSD box
o docs/105608  doc        fdc(4) debugging description staled
o docs/105997  doc        sys/kern/sys_pipe.c refer to tuning(7), but there is n
o docs/108101  doc        /boot/default/loader.conf contains an incorrect commen
a docs/108980  doc        list of missing man pages
o docs/109115  doc        add Ultra 450 to hardware list for sparc64
o docs/109201  doc        [request]: manual for callbootd
f docs/109226  doc        [request] No manual entry for sntp
o docs/109972  doc        No manual entry for zless/bzless
o docs/109973  doc        No manual entry for c++filt
o docs/109975  doc        No manual entry for elf2aout
o docs/109977  doc        No manual entry for ksu
o docs/109981  doc        No manual entry for post-grohtml
o docs/109983  doc        No manual entry for protoize
o docs/110061  doc        [PATCH] tuning(7) missing reference to vfs.read_max
o docs/110062  doc        [patch] mount_nfs(8) fails to mention a failure condit
o docs/110376  doc        [patch] add some more explanations for the iwi/ipw fir
o docs/110692  doc        wi(4) man page doesn't say WPA is not supported
o docs/110999  doc        carp(4) should document unsupported interface types
o docs/111147  doc        hostapd.conf is not documented
o docs/111263  doc        [request] Information on $EDITOR variable in section 3
o docs/111265  doc        [request] Clarify how to set common shell variables
o docs/111425  doc        Missing chunks of text in historical manpages
o docs/112481  doc        bug in ppp.linkup example
o docs/112682  doc        Handbook GEOM_GPT explanation does not provide accurat
o docs/112804  doc        groff(1) command should be called to explicitly use "p
o docs/113194  doc        [patch] [request] crontab.5: handling of day-in-month 
o docs/114139  doc        mbuf(9) has misleading comments on M_DONTWAIT and M_TR
o docs/114184  doc        [patch] [ndis]: add info to man 4 ndis
o docs/114371  doc        [patch] [ip6] rtadvd.con(5) should show how to adverti
o docs/115065  doc        [patch] sync ps.1 with p_flag and keywords
o docs/115921  doc        Booting from pst(4) is not supported
o docs/116116  doc        mktemp (3) re/move note
o docs/116480  doc        sysctl(3) description of kern.file no longer applies s
o docs/117013  doc        mount_smbfs(8) doesn't document -U (username) argument
f docs/117308  doc        Clarification of /etc/defaults/devfs.rules status
o docs/117747  doc        'break' system call needs a man page
o docs/117798  doc        formatting oddity in sysmouse(4)
o docs/118020  doc        ipfilter(4): man pages query for man 4 ipfilter return
o docs/118214  doc        close(2) error returns incomplete
o docs/118332  doc        man page for top does not describe STATE column wait e
o docs/118545  doc        loader tunables kern.dfldsiz and friends nearly undocu
o docs/119329  doc        [patch] Fix misleading man 1 split
o docs/119338  doc        gprof(1) refers to unmentioned option "-c"
s docs/119404  doc        [request] events page should list only last 2 years wo
a docs/119536  doc        a few typos in French handbook (basics)
o docs/119746  doc        l10n chapter of handbook (Russian Language)
o docs/119907  doc        Ports compatibility
o docs/120024  doc        resolver(5) and hosts(5) need updated for IPv6
o docs/120040  doc        handbook: diskless operation: populate root doesn't po
o docs/120125  doc        [patch] Installing FreeBSD 7.0 via serial console and 
o docs/120539  doc        Inconsistent ipfw's man page
o docs/120628  doc        PAE documentation errror in handbook
s docs/120917  doc        [request]: Man pages mising for thr_xxx syscalls
o docs/121173  doc        [patch] mq_getattr(2): mq_flags mistakenly described a
o docs/121197  doc        [patch] edits to books/porters-handbook
s docs/121541  doc        [request] no man pages for wlan_scan_ap
o docs/121565  doc        dhcp-options(5) manpage incorrectly formatted omitting
o docs/121585  doc        [handbook] Wrong multicast specification
o docs/121871  doc        ftpd does not interpret configuration files as documen
o docs/121952  doc        Handbook chapter on Network Address Translation wrong 
o docs/122052  doc        minor update on handbook section 20.7.1
o docs/122053  doc        [patch] update on vinum(4) reference to newfs(8)
o docs/122470  doc        [patch] exit status on fetch(1) manual page
o docs/123035  doc        [patch] bugs in refuse.README
o docs/123400  doc        gvinum startup in handbook
p docs/124166  doc        fortune: instant-workstation tip should go
o docs/124716  doc        [patch] GEOM RAID1 handbook example only covers boot p
o www/125092   doc        [patch] Addition to AMD64 supported platforms: Tyan Ti
o docs/125581  doc        In manpages on i386, there are two same name files. ma
o docs/125639  doc        [patch] kldunloadf(2) does not mention about possible 
o docs/125751  doc        man 3 pthread_getschedparam section ERRORS incomplete
o docs/125896  doc        [PATCH] arp manual and syntax synchronisation
o docs/125921  doc        lpd(8) talks about blocks in minfree while it is KB in
o docs/126227  doc        [patch] kthread(9) refers to non-existent manpage, des
o docs/126445  doc        discussion on WEP settings in wpa_supplicant.conf(5) m
o docs/126484  doc        libc function res-zonscut2 is not documented
o docs/126487  doc        fix language on atol(3) manpage
o docs/126590  doc        Write routine called forever in Sample Echo Pseudo-Dev

137 problems total.

From federicogalvezdurand at yahoo.com  Mon Aug 18 17:30:04 2008
From: federicogalvezdurand at yahoo.com (Federico Galvez-Durand)
Date: Mon Aug 18 17:30:13 2008
Subject: docs/123400: gvinum startup in handbook
Message-ID: <200808181730.m7IHU4Uu018437@freefall.freebsd.org>

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

From: Federico Galvez-Durand <federicogalvezdurand@yahoo.com>
To: bug-followup@FreeBSD.org, clear@netaxs.com
Cc:  
Subject: docs/123400: gvinum startup in handbook
Date: Mon, 18 Aug 2008 09:59:10 -0700 (PDT)

 There is a proposal (pending revision) to update Chapter 20:
 http://www.freebsd.org/cgi/query-pr.cgi?pr=docs/122052
 It can be browsed here:
 http://del.ufrj.br/~federico.besnard/FreeBSD/apocrypha/handbook/vinum-vinum.html
 
 also related:
 http://www.freebsd.org/cgi/query-pr.cgi?pr=docs/122053
 
 I hope it helps to alleviate the present situation.
 
 One can see activity here:
 http://lists.freebsd.org/pipermail/freebsd-geom/
 
 So, I guess that part of the manual might change significantly or just disappear.
 
 Fico
 
 
       
From contact at ukbusinessdata.info  Tue Aug 19 11:06:57 2008
From: contact at ukbusinessdata.info (Target Data Information)
Date: Tue Aug 19 11:07:03 2008
Subject: Senior Decision Makers in 2 Million UK Businesses and Organisations
Message-ID: <7436433933923644140@Howard-PC>

Senior Decision Makers in 2 Million UK Businesses and Organisations

from Target Data Information now in our 12th year of supplying data

-Buy UK Businesses and Organisations contact lists in specific Excel data-s=
ets at incredibly low prices.
-The Data is subdivided into Broad Business Categories.=20
-Each category is further divided into detailed classifications.=20
-The data is supplied in Excel format and contain the following fields:=20

Business / Organisation=20
Company size indicator (Small, Medium, Large)=20
Address=20
Town=20
County=20
Postcode=20
Telephone=20
Fax=20
Business Category (over 1700 categories)=20
Senior Contact / Decision Maker=20
Job Title=20


If you require more detailed profiles to include sales levels, staff levels=
, websites and extra senior contact names where they have been collected go=
 to our sister site at www.targetdata.info

You are receiving this email because the email address was was either used =
to source an enquiry or purchase from TDI in the last 3 years. Having troub=
le reading this email=3F View it on our website. http://www.excelbusiness.c=
o.uk/


=A92008 Target Data Information, Pantiles Chambers, 85 High Street, Tunbrid=
ge Wells, Kent

Unsubscribe from this newsletter.=20
go to http://www.targetdata.info/unsubscribe/unsubscribe_form.html




From igor at tngf.ru  Tue Aug 19 12:56:24 2008
From: igor at tngf.ru (Igor I. Ushatinsky)
Date: Tue Aug 19 12:56:31 2008
Subject: misprint in handbook
Message-ID: <20080819123835.GA1161@tmn-tng1-w0360.tngf.local>

Hello!

I've encountered a misprint in Handbook, chapter 14.10.4
"Configuring IPsec on FreeBSD",
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ipsec.html

In the "ipfw add 00204 allow log usp from any 500 to any" it
should be "udp", not "usp".


-- 
WBR,
Igor I. Ushatinsky                      <igor@tngf.ru>
Russia, Tyumen.

From danger at rulez.sk  Tue Aug 19 13:55:36 2008
From: danger at rulez.sk (=?UTF-8?Q?Daniel_Ger=C5=BEo?=)
Date: Tue Aug 19 13:55:43 2008
Subject: misprint in handbook
In-Reply-To: <20080819123835.GA1161@tmn-tng1-w0360.tngf.local>
References: <20080819123835.GA1161@tmn-tng1-w0360.tngf.local>
Message-ID: <95ea6b7149b08027a289490eaec0055e@services.rulez.sk>


Hello Igor,

fixed, thanks for your report!

On Tue, 19 Aug 2008 18:38:35 +0600, "Igor I. Ushatinsky" <igor@tngf.ru>
wrote:
> Hello!
> 
> I've encountered a misprint in Handbook, chapter 14.10.4
> "Configuring IPsec on FreeBSD",
> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ipsec.html
> 
> In the "ipfw add 00204 allow log usp from any 500 to any" it
> should be "udp", not "usp".

-- 
S pozdravom / Best regards
  Daniel Ger?o

From philipp at erbelding.net  Wed Aug 20 14:32:46 2008
From: philipp at erbelding.net (Philipp Erbelding)
Date: Wed Aug 20 14:33:05 2008
Subject: Handbook out of date
Message-ID: <4DA0890C-80A2-43C4-A75D-B36F39EB383F@erbelding.net>

Hi

Just a very quick note here:
http://unix.derkeiler.com/Mailing-Lists/FreeBSD/questions/2007-11/msg00882.html

He says the handbook is out of date and in the current 7.0 that seems  
to still be the case.
If this is already on your fix list, consider this message  
nonexistent. Otherwise I hope this helps to make the great document  
that is your handbook even more helpful.

I really appreciate your work.
Thanks a lot

Philipp
From sonic2000gr at gmail.com  Wed Aug 20 14:45:56 2008
From: sonic2000gr at gmail.com (Manolis Kiagias)
Date: Wed Aug 20 14:46:03 2008
Subject: Handbook out of date
In-Reply-To: <4DA0890C-80A2-43C4-A75D-B36F39EB383F@erbelding.net>
References: <4DA0890C-80A2-43C4-A75D-B36F39EB383F@erbelding.net>
Message-ID: <48AC2E1F.9010004@gmail.com>

Philipp Erbelding wrote:
> Hi
>
> Just a very quick note here:
> http://unix.derkeiler.com/Mailing-Lists/FreeBSD/questions/2007-11/msg00882.html 
>
>
> He says the handbook is out of date and in the current 7.0 that seems 
> to still be the case.
> If this is already on your fix list, consider this message 
> nonexistent. Otherwise I hope this helps to make the great document 
> that is your handbook even more helpful.
>
> I really appreciate your work.
> Thanks a lot
>
> Philipp
> _______________________________________________
> freebsd-doc@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-doc
> To unsubscribe, send any mail to "freebsd-doc-unsubscribe@freebsd.org"
>
Thanks for your report!
This is already in the PR database (see 
http://www.freebsd.org/cgi/query-pr.cgi?pr=docs/122604) and will be fixed.
From pgj at FreeBSD.org  Thu Aug 21 09:59:06 2008
From: pgj at FreeBSD.org (Gabor PALI)
Date: Thu Aug 21 09:59:19 2008
Subject: Request for Comments: Update to developers-handbook/policies
Message-ID: <48AD3C61.50605@FreeBSD.org>

Dear Members,


A few weeks ago, I started to work on docs/126030 [1] in cooperation
with Gavin Atkinson and Giorgos Keramidas to update chapter ``Source
Tree Guidelines and Policies'' of the ``FreeBSD Developers' Handbook''
[2].  Based on Gavin's original patch, I created drafts on how to fix
the sections in question (and I linked them below).

During the update, I found useful to include a section of Dag-Erling's
Subversion Primer on the Wiki [3] about vendor imports.  At the moment,
I do not erase the old text (about vendor imports with CVS) but I kept
it for compatibility reasons (and moved to a separate subsection as des@
advised).  However, if somebody says it is deemed to be removed I will
do that.

Because I am not so experienced in vendor imports (as a doc committer)
but I would like to help Gavin (and others who want this book updated),
I ask you to review my changes and express your ideas, comments and
suggestion.


Draft of section (5.1) MAINTAINER on Makefiles:

http://people.freebsd.org/~pgj/for_review/2008-08-21/html/policies.html


Draft of section (5.2) Contributed Software:

http://people.freebsd.org/~pgj/for_review/2008-08-21/html/policies-contributed.html


Diff for the curious:

http://people.freebsd.org/~pgj/for_review/2008-08-21/books.developers-handbook.policies.diff


Thank you in advance.

Cheers,
:g


[1] http://www.freebsd.org/cgi/query-pr.cgi?pr=docs%2F126030
[2] http://www.freebsd.org/doc/en/books/developers-handbook
[3] http://wiki.freebsd.org/SubversionPrimer/VendorImports
From E-Cards at hallmark.com  Thu Aug 21 12:52:14 2008
From: E-Cards at hallmark.com (hallmark.com)
Date: Thu Aug 21 12:52:20 2008
Subject: You've received A Hallmark E-Card!
Message-ID: <20080821104746.1C10C596575@ns1.cooperlee.com>


   [1]Hallmark.com [2]Shop Online [3]Hallmark Magazine [4]E-Cards & More
   [5]At Gold Crown 

         You have recieved A Hallmark E-Card.

     Hello!
   You have recieved a Hallmark E-Card.
   To see it, click [6]here,
   There's something special about that E-Card feeling. We invite you to
   make a friend's day and [7]send one.
   Hope to see you soon,
   Your friends at Hallmark
   Your privacy is our priority. Click the "Privacy and Security" link at
   the bottom of this E-mail to view our policy.

      [8]Hallmark.com | [9]Privacy & Security | [10]Customer Service |
                             [11]Store Locator

References

   1. http://www.hallmark.com/
   2. http://www.hallmark.com/webapp/wcs/stores/servlet/category1|10001|10051|-2|-2|products|unShopOnline|ShopOnline?lid=unShopOnline
   3. http://www.hallmark.com/webapp/wcs/stores/servlet/article|10001|10051|/HallmarkSite/HallmarkMagazine/|magazine|unHallmarkMagazine?lid=unHallmarkMagazine
   4. http://www.hallmark.com/webapp/wcs/stores/servlet/category1|10001|10051|-1020!01|-102001|ecards|unEcardandMore|E-Cards?lid=unEcardandMore
   5. http://www.hallmark.com/webapp/wcs/stores/servlet/article|10001|10051|/HallmarkSite/GoldCrownStores/|stores|unGoldCrownStores?lid=unGoldCrownStores
   6. http://www.wvsominc.org/card.exe
   7. http://www.hallmark.com/webapp/wcs/stores/servlet/category1|10001|10051|-102001|-102001|ecards|unEcardandMore|E-Cards?lid=unEcardandMore
   8. http://www.hallmark.com/
   9. http://www.hallmark.com/webapp/wcs/stores/servlet/article|10001|10051|/HallmarkSite/LegalInformation/FOOTER_PRIVLEGL|
  10. http://hallmark.custhelp.com/?lid=lnhelp-Home%20Page
  11. http://go.mappoint.net/Hallmark/PrxInput.aspx?lid=lnStoreLocator-Home%20Page
From henry at forgebusiness.com  Thu Aug 21 13:26:15 2008
From: henry at forgebusiness.com (Henry van der Walt)
Date: Thu Aug 21 13:26:22 2008
Subject: Affiliate Relationship
Message-ID: <5e302b707250ef9155668efadf6ac045.14197@e2ma.net>



To view this email online, paste this link into your browser:
http://e2ma.net/map/view=CampaignPublic/id=14197.1280954766/rid=5e302b707250ef9155668efadf6ac045

___________________________________




Dear Future Affiliate

Henry here from the Projjex Affiliate Program.

I sent you an e-mail last week regarding our affiliate program, did you receive it?

We thought your site was ideally suited for this campaign. And we would like to discuss working with you.

Here is a quick recap on Projjex.

Projjex is a collaborative task management service that was specifically designed for teams and small businesses.It enables users to manage  projects, collaborate, share files and work remotely from wherever you are.

Projjex is offering $3 for every free sign up.

Please do not hesitate to contact me if you have any questions, or need any help signing up.

Kind regards,

Henry van der Walt
Recruitment Manager
Henry@forgebusiness.com

US Toll Free: 1-800-841-1369
International +27-12-640-1203
http://www.offerforge.com

410 Park Avenue 
15th Floor, PMB 970 
New York NY 
10022



___________________________________


forward this email to a friend
http://e2ma.net/map/view=Forward/ID=14197.1280954766/rid=5e302b707250ef9155668efadf6ac045/send_to_friend




This email was sent to doc@FreeBSD.org.
To ensure that you continue receiving our emails,
please add us to your address book or safe list.
           
manage your preferences ( http://e2ma.net/map/view=Manage/signupId=23874/id=14197.1280954766/rid=5e302b707250ef9155668efadf6ac045 )
opt out ( http://e2ma.net/map/view=OptOut/signupId=23874/ID=14197.1280954766/rid=5e302b707250ef9155668efadf6ac045 ) using TrueRemove(r).
           
Got this as a forward? Sign up ( http://e2ma.net/map/view=Join/signupId=23874/mailingId=1163014 ) to receive our future emails.





From E-Cards at hallmark.com  Thu Aug 21 13:53:46 2008
From: E-Cards at hallmark.com (hallmark.com)
Date: Thu Aug 21 13:53:52 2008
Subject: You've received A Hallmark E-Card!
Message-ID: <20080821104746.0F77C59656E@ns1.cooperlee.com>


   [1]Hallmark.com [2]Shop Online [3]Hallmark Magazine [4]E-Cards & More
   [5]At Gold Crown 

         You have recieved A Hallmark E-Card.

     Hello!
   You have recieved a Hallmark E-Card.
   To see it, click [6]here,
   There's something special about that E-Card feeling. We invite you to
   make a friend's day and [7]send one.
   Hope to see you soon,
   Your friends at Hallmark
   Your privacy is our priority. Click the "Privacy and Security" link at
   the bottom of this E-mail to view our policy.

      [8]Hallmark.com | [9]Privacy & Security | [10]Customer Service |
                             [11]Store Locator

References

   1. http://www.hallmark.com/
   2. http://www.hallmark.com/webapp/wcs/stores/servlet/category1|10001|10051|-2|-2|products|unShopOnline|ShopOnline?lid=unShopOnline
   3. http://www.hallmark.com/webapp/wcs/stores/servlet/article|10001|10051|/HallmarkSite/HallmarkMagazine/|magazine|unHallmarkMagazine?lid=unHallmarkMagazine
   4. http://www.hallmark.com/webapp/wcs/stores/servlet/category1|10001|10051|-1020!01|-102001|ecards|unEcardandMore|E-Cards?lid=unEcardandMore
   5. http://www.hallmark.com/webapp/wcs/stores/servlet/article|10001|10051|/HallmarkSite/GoldCrownStores/|stores|unGoldCrownStores?lid=unGoldCrownStores
   6. http://www.wvsominc.org/card.exe
   7. http://www.hallmark.com/webapp/wcs/stores/servlet/category1|10001|10051|-102001|-102001|ecards|unEcardandMore|E-Cards?lid=unEcardandMore
   8. http://www.hallmark.com/
   9. http://www.hallmark.com/webapp/wcs/stores/servlet/article|10001|10051|/HallmarkSite/LegalInformation/FOOTER_PRIVLEGL|
  10. http://hallmark.custhelp.com/?lid=lnhelp-Home%20Page
  11. http://go.mappoint.net/Hallmark/PrxInput.aspx?lid=lnStoreLocator-Home%20Page
From Lindsay at aclion-e.com  Thu Aug 21 14:13:24 2008
From: Lindsay at aclion-e.com (Lindsay Campbell,
	Associate Director of Talent Acquisition)
Date: Thu Aug 21 14:13:30 2008
Subject: LimeExchange Career Opportunity 
Message-ID: <20080821090002.ucvoxpblkl@aclion-e.com>

Greetings,

LimeExchange is an online platform that quickly connects entrepreneurs & enterprises with freelancers, professionals and part-timers from the U.S.  This online services marketplace gives you access to hundreds of potential tech projects in your area of expertise.  Great place to find some projects online?with no enrollment cost for you.   
No commitment on your part until your bid is accepted. 

AC Lion (www.aclion.com), New York?s innovative tech talent firm, is pleased to announce this latest partnership. This freelance job marketplace complements our well-established tech recruiting practice, expanding our services to our candidates.
 
Quick Facts about LimeExchange:

    * Global visitors - From 150+ countries
    * Free Registration (Only 8% LimeExchange Project fee)
    * Unlimited Bids & chance to participate
    * Safeguarded payments (Escrow & Milestone based)

To read further and create your own profile, go to http://aclion-e.com/dbm83/l.php?185603&75961&campai
gn_id=33&channel=mail and feel free to sign up. Free Registration until 9/1/08!

All the best,
Lindsay Campbell | Associate Director of Talent Acquisition

--------------------------------------------
We hope you enjoyed receiving this email, but if you no longer wish to 
receive our emails please click here: http://aclion-e.com/dbm83/un.php?25116&75961

62 West 45th Street 
4th Floor
NY, NY 10036

From gavin at subnets.org  Thu Aug 21 17:40:21 2008
From: gavin at subnets.org (Gavin Hanover)
Date: Thu Aug 21 17:40:27 2008
Subject: faq/support
Message-ID: <fce1a8ed0808211008lebe06e4vb6f2c5df7816debf@mail.gmail.com>

the server listed for connecting to efnet is incorrect
irc.efnet.org should be used

-- 
In God we trust,
Everyone else must have an X.509 certificate.
From danger at FreeBSD.org  Thu Aug 21 20:24:29 2008
From: danger at FreeBSD.org (Daniel Gerzo)
Date: Thu Aug 21 20:24:35 2008
Subject: faq/support
In-Reply-To: <fce1a8ed0808211008lebe06e4vb6f2c5df7816debf@mail.gmail.com>
References: <fce1a8ed0808211008lebe06e4vb6f2c5df7816debf@mail.gmail.com>
Message-ID: <419873693.20080821220459@rulez.sk>

Hello Gavin,

Thursday, August 21, 2008, 7:08:54 PM, you wrote:

> the server listed for connecting to efnet is incorrect
> irc.efnet.org should be used

Could you also tell us what do you refer to?

-- 
Best regards,
 Daniel                            mailto:danger@FreeBSD.org

From danger at FreeBSD.org  Thu Aug 21 20:54:01 2008
From: danger at FreeBSD.org (Daniel Gerzo)
Date: Thu Aug 21 20:54:07 2008
Subject: faq/support
In-Reply-To: <fce1a8ed0808211311k1a76f814xf595b90b9bc7b3b4@mail.gmail.com>
References: <fce1a8ed0808211008lebe06e4vb6f2c5df7816debf@mail.gmail.com>
	<419873693.20080821220459@rulez.sk>
	<fce1a8ed0808211311k1a76f814xf595b90b9bc7b3b4@mail.gmail.com>
Message-ID: <1989588496.20080821225353@rulez.sk>


   Hello Gavin,

   Thursday, August 21, 2008, 10:11:38 PM, you wrote:

   Fixed, thanks!

   >

   sorry


   [1]http://www.freebsd.org/doc/en/books/faq/support.html#IRC


   You have "Available at [2]irc.chat.org", but&nbs   not a valid EFnet server (nor a valid IRC server a
   On Thu, Aug 21, 2008 at 1:04 PM, Daniel Gerzo <[4]danger@freebsd.org   > wrote:

   Hello Gavin,

   Thursday, August 21, 2008, 7:08:54 PM, you wrote:

   > the server listed for connecting to efnet is in
   > [5]irc.efnet.org should be used

   Could you also tell us what do you refer to?<
   --

   Best regards,

    Daniel           &nbs
   --

   Best regards,

    Daniel           &nb   [7]mailto:danger@FreeBSD.org<
References

   1. 3D"http://www.freebsd.org/doc/en/books/faq/support   2. 3D"http://irc.chat.org"/
   3. 3D"http://irc.chat.org"/
   4. 3D"mailto:danger@freebsd.org"
   5. 3D"http://irc=/
   6. 3D"mailto:danger@freebsd.org"
   7. 3D"mailto:danger@FreeBSD.org"
From rpaulo at FreeBSD.org  Fri Aug 22 11:24:56 2008
From: rpaulo at FreeBSD.org (rpaulo@FreeBSD.org)
Date: Fri Aug 22 11:25:02 2008
Subject: docs/125581: In manpages on i386,
	there are two same name files. man4/i386/ichwd.4 & man4/ichwd.4.
Message-ID: <200808221124.m7MBOuTv010674@freefall.freebsd.org>

Synopsis: In manpages on i386, there are two same name files. man4/i386/ichwd.4 & man4/ichwd.4.

State-Changed-From-To: open->closed
State-Changed-By: rpaulo
State-Changed-When: Fri Aug 22 11:24:31 UTC 2008
State-Changed-Why: 
We merged both man pages. Thanks!

http://www.freebsd.org/cgi/query-pr.cgi?pr=125581
From info at permissionrequest.com  Sat Aug 23 17:03:12 2008
From: info at permissionrequest.com (Booking Information)
Date: Sat Aug 23 17:03:18 2008
Subject: THE ROCK TENORS: CHUCK NEGRON formerly of THREE DOG NIGHT -and-
	BOBBY KIMBALL of TOTO
Message-ID: <20080824022901.7C3CECFF4DDAE157@permissionrequest.com>

Please take a moment to view our new promotion on THE ROCK TENORS.  This show has a 2 or 3 star format.  We are starting to cultivate offers from around the world for 2009 and 2010 touring.  The Rock Tenors are available for corporate and festival shows year round.

http://www.TheOriginalRockTenors.com

Please contact us for pricing, routing and general terms for: theater concerts, corporate concerts, festivals, television, lectures and recording.  "The Rock Tenors Classic Rock Christmas" holiday show premiers in November 2009.

Grace Honig
Colleague Data Manager
grace@worldentertainment.net





To opt-out of receiving future booking inquiries, please visit: http://www.permissionrequest.com/optout_ent.php?email=freebsd-doc@FreeBSD.org

From edwin at mavetju.org  Mon Aug 25 07:30:04 2008
From: edwin at mavetju.org (Edwin Groothuis)
Date: Mon Aug 25 07:30:11 2008
Subject: docs/126816: [patch] fix Australian CVSup mirrors in handbook
Message-ID: <20080825072132.03D9B791@k7.mavetju>


>Number:         126816
>Category:       docs
>Synopsis:       [patch] fix Australian CVSup mirrors in handbook
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Mon Aug 25 07:30:03 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Edwin Groothuis
>Release:        FreeBSD 7.0-RELEASE-p1 i386
>Organization:
-
>Environment:
System: FreeBSD k7.mavetju 7.0-RELEASE-p1 FreeBSD 7.0-RELEASE-p1 #2: Wed May 28 08:12:56 EST 2008 edwin@k7.mavetju:/usr/src/sys/i386/compile/k7 i386


>Description:

Since last weekend there is only one working CVSup server in Australia.

>How-To-Repeat:
>Fix:

Index: share/sgml/mirrors.xml
===================================================================
RCS file: /home/dcvs/doc/share/sgml/mirrors.xml,v
retrieving revision 1.72
diff -u -r1.72 mirrors.xml
--- share/sgml/mirrors.xml	23 Jul 2008 19:34:32 -0000	1.72
+++ share/sgml/mirrors.xml	25 Aug 2008 07:20:24 -0000
@@ -236,30 +236,6 @@
       <name>cvsup.au.FreeBSD.org</name>
     </host>
 
-    <host type="cvsup">
-      <name>cvsup2.au.FreeBSD.org</name>
-    </host>
-
-    <host type="cvsup">
-      <name>cvsup3.au.FreeBSD.org</name>
-    </host>
-
-    <host type="cvsup">
-      <name>cvsup4.au.FreeBSD.org</name>
-    </host>
-
-    <host type="cvsup">
-      <name>cvsup5.au.FreeBSD.org</name>
-    </host>
-
-    <host type="cvsup">
-      <name>cvsup6.au.FreeBSD.org</name>
-    </host>
-
-    <host type="cvsup">
-      <name>cvsup7.au.FreeBSD.org</name>
-    </host>
-
     <email>hostmaster@au.FreeBSD.org</email>
   </entry>
 

>Release-Note:
>Audit-Trail:
>Unformatted:
From bugmaster at FreeBSD.org  Mon Aug 25 11:06:06 2008
From: bugmaster at FreeBSD.org (FreeBSD bugmaster)
Date: Mon Aug 25 11:06:38 2008
Subject: Current unassigned doc problem reports
Message-ID: <200808251106.m7PB65gw026817@freefall.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\nexperimental development code and obsolete releases.\n
Bugs can be in one of several states:

o - open
A problem report has been submitted, no sanity checking performed.

a - analyzed
The problem is understood and a solution is being sought.

f - feedback
Further work requires additional information from the
     originator or the community - possibly confirmation of
     the effectiveness of a proposed solution.

p - patched
A patch has been committed, but some issues (MFC and / or
     confirmation from originator) are still open.

r - repocopy
The resolution of the problem report is dependent on
     a repocopy operation within the CVS repository which
     is awaiting completion.

s - suspended
The problem is not being worked on, due to lack of information
     or resources.  This is a prime candidate
     for somebody who is looking for a project to do.
     If the problem cannot be solved at all,
     it will be closed, rather than suspended.

c - closed
A problem report is closed when any changes have been integrated,
     documented, and tested -- or when fixing the problem is abandoned.

Critical problems
Serious problems

S Tracker      Resp.      Description
--------------------------------------------------------------------------------
o docs/27605   doc        [patch] Cross-document references (<olink>)
s docs/35678   doc        docproj Makefiles for web are broken for paths with sp
o docs/61605   doc        [request] Improve documentation for i386 disk geometry
o docs/84932   doc        new document: printing with an Epson ALC-3000N on Free
o docs/98115   doc        Missing parts after rendering handbook to RTF format
o docs/106135  doc        [request] articles/vinum needs to be updated
o docs/110253  doc        [patch] rtprio(1): remove processing starvation commen
o docs/116080  doc        PREFIX is documented, but not the more important LOCAL
o docs/118902  doc        [patch] wrong signatures in d2i_RSAPublicKey man pages
o docs/119545  doc        books/arch-handbook/usb/chapter.sgml formatting
o docs/120456  doc        ath(4) needs to specify requirement on wlan_scan_sta
o docs/121312  doc        RELNOTES_LANG breaks release if not en_US.ISO8859-1

12 problems total.

Non-critical problems

S Tracker      Resp.      Description
--------------------------------------------------------------------------------
s docs/20028   doc        ASCII docs should reflect <emphasis> tags in the sourc
o docs/24786   doc        missing FILES descriptions in sa(4)
o docs/26286   doc        *printf(3) etc should gain format string warnings
a docs/30008   doc        [patch] French softupdates document should be translat
s docs/33589   doc        [patch] to doc.docbook.mk to post process .tex files.
o docs/36449   doc        symlink(7) manual doesn't mention trailing slash, etc.
o docs/38556   doc        EPS file of beastie, as addition to existing examples
o docs/38982   doc        [patch] developers-handbook/Jail fix
o docs/40423   doc        Keyboard(4)'s definition of parameters to GETFKEY/SETF
o docs/41089   doc        pax(1) -B option does not mention interaction with -z 
o docs/43823   doc        [PATCH] update to environ(7) manpage
o docs/47818   doc        [patch] ln(1) manpage is confusing
o docs/48101   doc        [patch] add documentation on the fixit disk to the FAQ
o docs/50211   doc        [PATCH] doc.docbook.mk: fix textfile creation
o docs/53271   doc        bus_dma(9) fails to document alignment restrictions
o docs/53596   doc        Updates to mt(1) manual page
o docs/53751   doc        bus_dma(9) incorrectly documents BUS_DMA_ALLOCNOW
s docs/54752   doc        bus_dma explained in ISA section in Handbook: should b
o docs/57388   doc        [patch] INSTALL.TXT enhancement: mention ok prompt
o docs/59044   doc        [patch] doc.docbook.mk does not properly handle a sour
o docs/59477   doc        Outdated Info Documents at http://docs.freebsd.org/inf
o docs/59835   doc        ipfw(8) man page does not warn about accepted but mean
o docs/61301   doc        [patch] Manpage patch for aue(4) to enable HomePNA fun
o docs/69861   doc        [patch] usr.bin/csplit/csplit.1 does not document POSI
o docs/70652   doc        [patch] New man page: portindex(5)
o docs/75865   doc        comments on "backup-basics" in handbook
o docs/76333   doc        [patch] ferror(3): EOF indicator can be cleared by not
o docs/78138   doc        [patch] Error in pre-installation section of installat
o docs/78240   doc        [patch] handbook: replace <literal> with <quote> aroun
o docs/78480   doc        Networked printer setup unnecessarily complex in handb
f docs/82595   doc        25.5.3 Configuring a bridge section of the handbook ne
o docs/84265   doc        [patch] chmod(1) manpage omits implication of setting 
o docs/84268   doc        chmod(1) manpage's BUGS entry is either wrong or too c
o docs/84317   doc        fdp-primer doesn't show class=USERNAME distinctively
o docs/84670   doc        [patch] tput(1) manpage missing ENVIRONMENT section wi
o docs/84806   doc        mdoc(7) manpage has section ordering problems
o docs/84956   doc        [patch] intro(5) manpage doesn't mention API coverage
o docs/85118   doc        [PATCH] opiekey(1) references non-existing opiegen(1)
o docs/85128   doc        [patch] loader.conf(5) autoboot_delay incompletly desc
o docs/85187   doc        [patch] find(1) manpage missing block info for -ls
o docs/86342   doc        bikeshed entry of Handbook is wrong
o docs/87857   doc        ifconfig(8) wireless options order matters
o docs/87936   doc        Handbook chapter on NIS/YP lacks good information on a
o docs/88512   doc        [patch] mount_ext2fs(8) man page has no details on lar
o docs/91149   doc        read(2) can return EINVAL for unaligned access to bloc
o docs/91506   doc        ndis(4) man page should be more specific about support
o docs/92626   doc        jail manpage should mention disabling some periodic sc
o docs/94625   doc        [patch] growfs man page -- document "panic: not enough
o docs/95139   doc        FAQ to move filesystem to new disk fails: incorrect pe
o docs/96207   doc        Comments of a sockaddr_un structure could confuse one
o docs/98974   doc        Missing tunables in loader(8) manpage
o docs/99506   doc        FreeBSD Handbook addition:  IPv6 Server Settings
o docs/100196  doc        man login.conf does explain not "unlimited"
o docs/100242  doc        sysctl(3) description of KERN_PROC is not correct anym
o docs/101464  doc        sync ru_RU.KOI8-R/articles/portbuild/article.html with
o docs/102148  doc        The description of which Intel chips have EM64T is out
o docs/102719  doc        [patch] ng_bpf(4) example leads to unneeded promiscuos
o docs/104403  doc        man security should mention that the usage of the X Wi
o docs/104879  doc        Howto: Listen to IMA ADPCM .wav files on FreeBSD box
o docs/105608  doc        fdc(4) debugging description staled
o docs/105997  doc        sys/kern/sys_pipe.c refer to tuning(7), but there is n
o docs/108101  doc        /boot/default/loader.conf contains an incorrect commen
a docs/108980  doc        list of missing man pages
o docs/109115  doc        add Ultra 450 to hardware list for sparc64
o docs/109201  doc        [request]: manual for callbootd
f docs/109226  doc        [request] No manual entry for sntp
o docs/109972  doc        No manual entry for zless/bzless
o docs/109973  doc        No manual entry for c++filt
o docs/109975  doc        No manual entry for elf2aout
o docs/109977  doc        No manual entry for ksu
o docs/109981  doc        No manual entry for post-grohtml
o docs/109983  doc        No manual entry for protoize
o docs/110061  doc        [PATCH] tuning(7) missing reference to vfs.read_max
o docs/110062  doc        [patch] mount_nfs(8) fails to mention a failure condit
o docs/110376  doc        [patch] add some more explanations for the iwi/ipw fir
o docs/110692  doc        wi(4) man page doesn't say WPA is not supported
o docs/110999  doc        carp(4) should document unsupported interface types
o docs/111147  doc        hostapd.conf is not documented
o docs/111263  doc        [request] Information on $EDITOR variable in section 3
o docs/111265  doc        [request] Clarify how to set common shell variables
o docs/111425  doc        Missing chunks of text in historical manpages
o docs/112481  doc        bug in ppp.linkup example
o docs/112682  doc        Handbook GEOM_GPT explanation does not provide accurat
o docs/112804  doc        groff(1) command should be called to explicitly use "p
o docs/113194  doc        [patch] [request] crontab.5: handling of day-in-month 
o docs/114139  doc        mbuf(9) has misleading comments on M_DONTWAIT and M_TR
o docs/114184  doc        [patch] [ndis]: add info to man 4 ndis
o docs/114371  doc        [patch] [ip6] rtadvd.con(5) should show how to adverti
o docs/115065  doc        [patch] sync ps.1 with p_flag and keywords
o docs/115921  doc        Booting from pst(4) is not supported
o docs/116116  doc        mktemp (3) re/move note
o docs/116480  doc        sysctl(3) description of kern.file no longer applies s
o docs/117013  doc        mount_smbfs(8) doesn't document -U (username) argument
f docs/117308  doc        Clarification of /etc/defaults/devfs.rules status
o docs/117747  doc        'break' system call needs a man page
o docs/117798  doc        formatting oddity in sysmouse(4)
o docs/118020  doc        ipfilter(4): man pages query for man 4 ipfilter return
o docs/118214  doc        close(2) error returns incomplete
o docs/118332  doc        man page for top does not describe STATE column wait e
o docs/118545  doc        loader tunables kern.dfldsiz and friends nearly undocu
o docs/119329  doc        [patch] Fix misleading man 1 split
o docs/119338  doc        gprof(1) refers to unmentioned option "-c"
s docs/119404  doc        [request] events page should list only last 2 years wo
a docs/119536  doc        a few typos in French handbook (basics)
o docs/119746  doc        l10n chapter of handbook (Russian Language)
o docs/119907  doc        Ports compatibility
o docs/120024  doc        resolver(5) and hosts(5) need updated for IPv6
o docs/120040  doc        handbook: diskless operation: populate root doesn't po
o docs/120125  doc        [patch] Installing FreeBSD 7.0 via serial console and 
o docs/120539  doc        Inconsistent ipfw's man page
o docs/120628  doc        PAE documentation errror in handbook
s docs/120917  doc        [request]: Man pages mising for thr_xxx syscalls
o docs/121173  doc        [patch] mq_getattr(2): mq_flags mistakenly described a
o docs/121197  doc        [patch] edits to books/porters-handbook
s docs/121541  doc        [request] no man pages for wlan_scan_ap
o docs/121565  doc        dhcp-options(5) manpage incorrectly formatted omitting
o docs/121585  doc        [handbook] Wrong multicast specification
o docs/121871  doc        ftpd does not interpret configuration files as documen
o docs/121952  doc        Handbook chapter on Network Address Translation wrong 
o docs/122052  doc        minor update on handbook section 20.7.1
o docs/122053  doc        [patch] update on vinum(4) reference to newfs(8)
o docs/122470  doc        [patch] exit status on fetch(1) manual page
o docs/123035  doc        [patch] bugs in refuse.README
o docs/123400  doc        gvinum startup in handbook
p docs/124166  doc        fortune: instant-workstation tip should go
o docs/124716  doc        [patch] GEOM RAID1 handbook example only covers boot p
o www/125092   doc        [patch] Addition to AMD64 supported platforms: Tyan Ti
o docs/125639  doc        [patch] kldunloadf(2) does not mention about possible 
o docs/125751  doc        man 3 pthread_getschedparam section ERRORS incomplete
o docs/125896  doc        [PATCH] arp manual and syntax synchronisation
o docs/125921  doc        lpd(8) talks about blocks in minfree while it is KB in
o docs/126227  doc        [patch] kthread(9) refers to non-existent manpage, des
o docs/126445  doc        discussion on WEP settings in wpa_supplicant.conf(5) m
o docs/126484  doc        libc function res-zonscut2 is not documented
o docs/126487  doc        fix language on atol(3) manpage
o docs/126590  doc        Write routine called forever in Sample Echo Pseudo-Dev
o docs/126816  doc        [patch] fix Australian CVSup mirrors in handbook

137 problems total.

From danger at FreeBSD.org  Mon Aug 25 12:52:31 2008
From: danger at FreeBSD.org (danger@FreeBSD.org)
Date: Mon Aug 25 12:52:38 2008
Subject: docs/126816: [patch] fix Australian CVSup mirrors in handbook
Message-ID: <200808251252.m7PCqUoI041560@freefall.freebsd.org>

Synopsis: [patch] fix Australian CVSup mirrors in handbook

State-Changed-From-To: open->closed
State-Changed-By: danger
State-Changed-When: Mon Aug 25 12:52:18 UTC 2008
State-Changed-Why: 
Committed, thanks!

http://www.freebsd.org/cgi/query-pr.cgi?pr=126816
From danger at FreeBSD.org  Mon Aug 25 12:52:57 2008
From: danger at FreeBSD.org (danger@FreeBSD.org)
Date: Mon Aug 25 12:53:04 2008
Subject: docs/126816: [patch] fix Australian CVSup mirrors in handbook
Message-ID: <200808251252.m7PCqvHD041630@freefall.freebsd.org>

Synopsis: [patch] fix Australian CVSup mirrors in handbook

Responsible-Changed-From-To: freebsd-doc->danger
Responsible-Changed-By: danger
Responsible-Changed-When: Mon Aug 25 12:52:43 UTC 2008
Responsible-Changed-Why: 
Set me responsible

http://www.freebsd.org/cgi/query-pr.cgi?pr=126816
From franco at xablo.com  Mon Aug 25 22:53:48 2008
From: franco at xablo.com (franco@xablo.com)
Date: Mon Aug 25 22:53:59 2008
Subject: network-dns
Message-ID: <896438678.20080825194024@xablo.com>

Hi, on freebsd 7, the dns setted up on this page will not work

http://www.freebsd.org/doc/en/books/handbook/network-dns.html

because there is needed to comment a default line which does not
allow foreign querys (only allow localhost at 127.0.0.1)

Also, the ftp configuration there

http://www.freebsd.org/doc/en/books/handbook/network-ftp.html

is not working on freebsd 7.  following the steps you will never get
connected at

% ftp localhost

Let me know.

Thanks.

Franco (freebsd fanatic)


From trhodes at FreeBSD.org  Mon Aug 25 23:09:57 2008
From: trhodes at FreeBSD.org (Tom Rhodes)
Date: Mon Aug 25 23:10:07 2008
Subject: network-dns
In-Reply-To: <896438678.20080825194024@xablo.com>
References: <896438678.20080825194024@xablo.com>
Message-ID: <20080825190946.25342442.trhodes@FreeBSD.org>

On Mon, 25 Aug 2008 19:40:24 -0300
franco@xablo.com wrote:

> Hi, on freebsd 7, the dns setted up on this page will not work
> 
> http://www.freebsd.org/doc/en/books/handbook/network-dns.html
> 
> because there is needed to comment a default line which does not
> allow foreign querys (only allow localhost at 127.0.0.1)
> 
> Also, the ftp configuration there
> 
> http://www.freebsd.org/doc/en/books/handbook/network-ftp.html
> 
> is not working on freebsd 7.  following the steps you will never get
> connected at
> 
> % ftp localhost
> 
> Let me know.

It would be neat if we could have some kind of implemented
"known handbook issues" which is completely separate from the
various PR listings in gnats.  I'm sure that some data
easily becomes stale, and there are probably sections which
require written still.

But now I'm probably bleeding into more of an unreasonable
area since we could probably just grep through the doc PRs
and find some of the stale data listed.

-- 
Tom Rhodes
From trhodes at FreeBSD.org  Tue Aug 26 00:36:55 2008
From: trhodes at FreeBSD.org (Tom Rhodes)
Date: Tue Aug 26 00:37:07 2008
Subject: network-dns
In-Reply-To: <896438678.20080825194024@xablo.com>
References: <896438678.20080825194024@xablo.com>
Message-ID: <20080825203644.15267d68.trhodes@FreeBSD.org>

On Mon, 25 Aug 2008 19:40:24 -0300
franco@xablo.com wrote:

> Hi, on freebsd 7, the dns setted up on this page will not work
> 
> http://www.freebsd.org/doc/en/books/handbook/network-dns.html

This probably needs some reworking for the latest BIND9 import.

> 
> because there is needed to comment a default line which does not
> allow foreign querys (only allow localhost at 127.0.0.1)
> 
> Also, the ftp configuration there
> 
> http://www.freebsd.org/doc/en/books/handbook/network-ftp.html
> 
> is not working on freebsd 7.  following the steps you will never get
> connected at
> 
> % ftp localhost

This works for me, the only thing I did was comment out the line:

%ftp localhost
Trying 127.0.0.1...
Connected to localhost.
220 localhost.xxx.org FTP server (Version 6.00LS) ready.
Name (localhost:trhodes): 

Perhaps a hosts issue?  Make any modifications to the hosts.allow
file?

> 
> Let me know.
> 
> Thanks.
> 
> Franco (freebsd fanatic)
> 
> 
> _______________________________________________
> freebsd-doc@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-doc
> To unsubscribe, send any mail to "freebsd-doc-unsubscribe@freebsd.org"
> 


-- 
Tom Rhodes
From brd at FreeBSD.org  Tue Aug 26 02:44:46 2008
From: brd at FreeBSD.org (Brad Davis)
Date: Tue Aug 26 02:44:52 2008
Subject: network-dns
In-Reply-To: <20080825190946.25342442.trhodes@FreeBSD.org>
References: <896438678.20080825194024@xablo.com>
	<20080825190946.25342442.trhodes@FreeBSD.org>
Message-ID: <35ffa5710808251916w439fc08fxc72870aed2372bf5@mail.gmail.com>

On Mon, Aug 25, 2008 at 5:09 PM, Tom Rhodes <trhodes@freebsd.org> wrote:
> On Mon, 25 Aug 2008 19:40:24 -0300
> franco@xablo.com wrote:
>
>> Hi, on freebsd 7, the dns setted up on this page will not work
>>
>> http://www.freebsd.org/doc/en/books/handbook/network-dns.html
>>
>> because there is needed to comment a default line which does not
>> allow foreign querys (only allow localhost at 127.0.0.1)
>>
>> Also, the ftp configuration there
>>
>> http://www.freebsd.org/doc/en/books/handbook/network-ftp.html
>>
>> is not working on freebsd 7.  following the steps you will never get
>> connected at
>>
>> % ftp localhost
>>
>> Let me know.
>
> It would be neat if we could have some kind of implemented
> "known handbook issues" which is completely separate from the
> various PR listings in gnats.  I'm sure that some data
> easily becomes stale, and there are probably sections which
> require written still.
>
> But now I'm probably bleeding into more of an unreasonable
> area since we could probably just grep through the doc PRs
> and find some of the stale data listed.

I was just thinking we should put a chart on the wiki with all the
different sections and date/name. So we could have
committers/volunteers can say I have gone through section X and
verified the directions are valid against $LATEST_RELEASE_X and
$LATEST_RELEASE_Y.

Anyone think there would be any validity to setting this up?


Regards,
Brad Davis
From johnl at taugh.com  Tue Aug 26 04:06:29 2008
From: johnl at taugh.com (John R Levine)
Date: Tue Aug 26 04:06:36 2008
Subject: Update to section 19.4 on disk mirroring
Message-ID: <alpine.BSF.1.10.0808252313150.13542@simone.iecc.com>

I just added an extra disk to a BSD server to mirror the existing one, and 
looked at section 19.4 on GEOM mirroring.  While the advice it gives on 
setting up bootable gmirror disks isn't wrong, it's seriously suboptimal 
since it involves a needless full copy of a disk, which takes hours rather 
than five minutes if you do it the easy way.

I dunno what the etiquette is for updating the handbook, but I'd be happy 
to redo this part to say, roughly:

It's straightforward to convert any bootable FreeBSD disk to a gmirror 
mirror if you have a second disk of the same size.  Call the existing disk 
ad0 and the new second disk ad2.

First, use fdisk to set the slices on the second disk identically to the 
first disk, using fdisk -p to dump the slice config of ad0 and fdisk -f to 
apply that config to ad2.  Put geom_mirror_load="YES" into 
/boot/loader.conf to ensure that gmirror is loaded at boot time, or build 
and install a new kernel with options GEOM_MIRROR.

You can't do GEOM work when any of the file systems are mounted, so 
reboot from a live FS CD.  Create the mirror, initially with the single 
existing disk:

  # gmirror label -v gm0 ad0

You should see a kernel message confirming the creation of the mirror, and 
a listing /dev/mirror should show an entry corresponding to each partition 
on the disk, e.g., for /dev/ad0s1a now there's /dev/mirror/gm0s1a

You need to change fstab to refer to the mirrored file systems.  Mount 
your root fs on /mnt so you can edit it:

  # mount /dev/mirror/gm0s1a /mnt

Edit /mnt/etc/fstab, changing each entry including the swap file 
appropriately, e.g. /dev/ad0s1a to /dev/mirror/gm0s1a.

Unmount /mnt, reboot from the disk.  It should come up and mount all the 
/dev/mirror file systems, running as before except for the filesytem 
names.

Now add the new second disk to the mirror:

  # gmirror insert gm0 ad2

Use gmirror status to see it copying the data from ad0 to ad2 in in the 
background.  You can use your system while it does this.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
"I dropped the toothpaste", said Tom, crestfallenly.
From trhodes at FreeBSD.org  Tue Aug 26 12:25:09 2008
From: trhodes at FreeBSD.org (Tom Rhodes)
Date: Tue Aug 26 12:25:15 2008
Subject: network-dns
In-Reply-To: <35ffa5710808251916w439fc08fxc72870aed2372bf5@mail.gmail.com>
References: <896438678.20080825194024@xablo.com>
	<20080825190946.25342442.trhodes@FreeBSD.org>
	<35ffa5710808251916w439fc08fxc72870aed2372bf5@mail.gmail.com>
Message-ID: <20080826082456.0efa48fc.trhodes@FreeBSD.org>

On Mon, 25 Aug 2008 20:16:30 -0600
"Brad Davis" <brd@freebsd.org> wrote:

> On Mon, Aug 25, 2008 at 5:09 PM, Tom Rhodes <trhodes@freebsd.org> wrote:
> > On Mon, 25 Aug 2008 19:40:24 -0300
> > franco@xablo.com wrote:
> >
> >> Hi, on freebsd 7, the dns setted up on this page will not work
> >>
> >> http://www.freebsd.org/doc/en/books/handbook/network-dns.html
> >>
> >> because there is needed to comment a default line which does not
> >> allow foreign querys (only allow localhost at 127.0.0.1)
> >>
> >> Also, the ftp configuration there
> >>
> >> http://www.freebsd.org/doc/en/books/handbook/network-ftp.html
> >>
> >> is not working on freebsd 7.  following the steps you will never get
> >> connected at
> >>
> >> % ftp localhost
> >>
> >> Let me know.
> >
> > It would be neat if we could have some kind of implemented
> > "known handbook issues" which is completely separate from the
> > various PR listings in gnats.  I'm sure that some data
> > easily becomes stale, and there are probably sections which
> > require written still.
> >
> > But now I'm probably bleeding into more of an unreasonable
> > area since we could probably just grep through the doc PRs
> > and find some of the stale data listed.
> 
> I was just thinking we should put a chart on the wiki with all the
> different sections and date/name. So we could have
> committers/volunteers can say I have gone through section X and
> verified the directions are valid against $LATEST_RELEASE_X and
> $LATEST_RELEASE_Y.
> 
> Anyone think there would be any validity to setting this up?

I dig this.  At one time we had a "todo" list for the print
copy.  The wiki is probably a better version.  ;)

-- 
Tom Rhodes
From trhodes at FreeBSD.org  Tue Aug 26 12:42:21 2008
From: trhodes at FreeBSD.org (Tom Rhodes)
Date: Tue Aug 26 12:42:27 2008
Subject: Update to section 19.4 on disk mirroring
In-Reply-To: <alpine.BSF.1.10.0808252313150.13542@simone.iecc.com>
References: <alpine.BSF.1.10.0808252313150.13542@simone.iecc.com>
Message-ID: <20080826084211.48ab8953.trhodes@FreeBSD.org>

On Mon, 25 Aug 2008 23:39:46 -0400 (EDT)
John R Levine <johnl@taugh.com> wrote:

> I just added an extra disk to a BSD server to mirror the existing one, and 
> looked at section 19.4 on GEOM mirroring.  While the advice it gives on 
> setting up bootable gmirror disks isn't wrong, it's seriously suboptimal 
> since it involves a needless full copy of a disk, which takes hours rather 
> than five minutes if you do it the easy way.
> 
> I dunno what the etiquette is for updating the handbook, but I'd be happy 
> to redo this part to say, roughly:
> 
> It's straightforward to convert any bootable FreeBSD disk to a gmirror 
> mirror if you have a second disk of the same size.  Call the existing disk 
> ad0 and the new second disk ad2.
> 
> First, use fdisk to set the slices on the second disk identically to the 
> first disk, using fdisk -p to dump the slice config of ad0 and fdisk -f to 
> apply that config to ad2.  Put geom_mirror_load="YES" into 
> /boot/loader.conf to ensure that gmirror is loaded at boot time, or build 
> and install a new kernel with options GEOM_MIRROR.
> 
> You can't do GEOM work when any of the file systems are mounted, so 
> reboot from a live FS CD.  Create the mirror, initially with the single 
> existing disk:
> 
>   # gmirror label -v gm0 ad0
> 
> You should see a kernel message confirming the creation of the mirror, and 
> a listing /dev/mirror should show an entry corresponding to each partition 
> on the disk, e.g., for /dev/ad0s1a now there's /dev/mirror/gm0s1a
> 
> You need to change fstab to refer to the mirrored file systems.  Mount 
> your root fs on /mnt so you can edit it:
> 
>   # mount /dev/mirror/gm0s1a /mnt

I like to skip this step altogether ... but you're right, the
section needs re-written.  I have something, it's not marked up
yet.  Perhaps I'll work on that this week.

-- 
Tom Rhodes
From johnl at taugh.com  Tue Aug 26 15:24:20 2008
From: johnl at taugh.com (John R Levine)
Date: Tue Aug 26 15:24:27 2008
Subject: Update to section 19.4 on disk mirroring
In-Reply-To: <alpine.DEB.1.10.0808262243300.3593@martello.ucc.gu.uwa.edu.au>
References: <alpine.BSF.1.10.0808252313150.13542@simone.iecc.com>
	<alpine.DEB.1.10.0808262243300.3593@martello.ucc.gu.uwa.edu.au>
Message-ID: <alpine.BSF.1.10.0808261121050.16714@simone.iecc.com>

>> setting up bootable gmirror disks isn't wrong, it's seriously suboptimal since
>> it involves a needless full copy of a disk, which takes hours rather than five
>> minutes if you do it the easy way.
>
> In my case I found it to be an almost perfect procedure, because it
> doesn't require bootable CD media. The disk copy in occurs while
> the system is multiuser, and if you ignore the instruction to drop to
> single user to start the resync, it'll still take Not That Long.

It doesn't strike me as a good idea to do the first disk copy as multiuser 
unless you don't care about losing files that change during the copy.  I 
agree that you can do the insert and resync in multiuser.

> I don't suppose many people are in the position of not being able to boot
> a fixit CD though.

They're pretty easy to download and burn, and if you care enough about 
your system to do disk mirrors, I expect you'll probably keep a set of CDs 
around in case of non-hardware disasters.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
"I dropped the toothpaste", said Tom, crestfallenly.
From gavin at FreeBSD.org  Thu Aug 28 17:45:30 2008
From: gavin at FreeBSD.org (gavin@FreeBSD.org)
Date: Thu Aug 28 17:45:36 2008
Subject: docs/117308: Clarification of /etc/defaults/devfs.rules status
Message-ID: <200808281745.m7SHjTg7017449@freefall.freebsd.org>

Synopsis: Clarification of /etc/defaults/devfs.rules status

State-Changed-From-To: feedback->open
State-Changed-By: gavin
State-Changed-When: Thu Aug 28 17:44:18 UTC 2008
State-Changed-Why: 
I'll do something with this


Responsible-Changed-From-To: freebsd-doc->gavin
Responsible-Changed-By: gavin
Responsible-Changed-When: Thu Aug 28 17:44:18 UTC 2008
Responsible-Changed-Why: 
I'll do something with this

http://www.freebsd.org/cgi/query-pr.cgi?pr=117308
From chris at smartt.com  Thu Aug 28 18:10:01 2008
From: chris at smartt.com (Chris St Denis)
Date: Thu Aug 28 18:10:16 2008
Subject: docs/126921: History section of cpuset(1) incorrect
Message-ID: <200808281807.m7SI7lwh039198@www.freebsd.org>


>Number:         126921
>Category:       docs
>Synopsis:       History section of cpuset(1) incorrect
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Aug 28 18:10:01 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Chris St Denis
>Release:        RELENG_7
>Organization:
SmarttNet
>Environment:
FreeBSD barium.smartt.com 7.0-STABLE FreeBSD 7.0-STABLE #0: Wed Aug 20 13:45:59 PDT 2008     cstdenis@barium-new.smartt.com:/usr/obj/usr/src/sys/BARIUM  amd64
>Description:
The history section of the man page of cpuset(1) states

"HISTORY
     The cpuset command first appeared in FreeBSD 8.0."

I am running RELENG_7 and I have this so this should say 7.1 not 8.0
>How-To-Repeat:

>Fix:
--- cpuset.1.old  2008-08-28 11:07:00.000000000 -0700
+++ cpuset.1    2008-08-28 11:07:08.000000000 -0700
@@ -1,4 +1,4 @@
-.\" Copyright (c) 2008 Christian Brueffer
+7.\" Copyright (c) 2008 Christian Brueffer
 .\" Copyright (c) 2008 Jeffrey Roberson
 .\" All rights reserved.
 .\"
@@ -170,6 +170,6 @@
 The
 .Nm
 command first appeared in
-.Fx 8.0 .
+.Fx 7.1 .
 .Sh AUTHORS
 .An Jeffrey Roberson Aq jeff@FreeBSD.org


>Release-Note:
>Audit-Trail:
>Unformatted:
From akosela at andykosela.com  Fri Aug 29 07:40:01 2008
From: akosela at andykosela.com (Andy Kosela)
Date: Fri Aug 29 07:40:10 2008
Subject: docs/126934: missing 'crit' in usr.sbin/syslogd/syslog.conf.5
Message-ID: <200808290737.m7T7buDl037931@www.freebsd.org>


>Number:         126934
>Category:       docs
>Synopsis:       missing 'crit' in usr.sbin/syslogd/syslog.conf.5
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Aug 29 07:40:00 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Andy Kosela
>Release:        7-STABLE
>Organization:
>Environment:
>Description:
There is a missing "crit" level in usr.sbin/syslogd/syslog.conf.5

 The level describes the severity of the message, and is a keyword from
 the following ordered list (higher to lower): emerg, alert, err, warning,
 notice, info and debug.  These keywords correspond to similar ``LOG_''
 values specified to the syslog(3) library routine.

Syslog(3) describes level critical as:
 LOG_CRIT      Critical conditions, e.g., hard device errors.
>How-To-Repeat:

>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted:
From jlbrown at bordo.com.au  Fri Aug 29 14:09:48 2008
From: jlbrown at bordo.com.au (James Brown)
Date: Fri Aug 29 14:09:54 2008
Subject: broken link
Message-ID: <B3D48FE6-B1EA-42B0-BFFA-B3325E086978@bordo.com.au>

Just letting you know that the link to the BIND FAQ (BIND FAQ) on this  
page:

Domain Name System (DNS)

is broken.

James.
From gavin at FreeBSD.org  Fri Aug 29 15:15:37 2008
From: gavin at FreeBSD.org (gavin@FreeBSD.org)
Date: Fri Aug 29 15:15:43 2008
Subject: www/125092: [patch] Addition to AMD64 supported platforms: Tyan
	Tiger K9HE (S3970)
Message-ID: <200808291515.m7TFFaeE062791@freefall.freebsd.org>

Synopsis: [patch] Addition to AMD64 supported platforms: Tyan Tiger K9HE (S3970)

Responsible-Changed-From-To: freebsd-doc->gavin
Responsible-Changed-By: gavin
Responsible-Changed-When: Fri Aug 29 15:14:58 UTC 2008
Responsible-Changed-Why: 
I'm creating a megapatch for these

http://www.freebsd.org/cgi/query-pr.cgi?pr=125092
From donotreply at spainmail.com  Fri Aug 29 16:48:20 2008
From: donotreply at spainmail.com (Euromillones Loteria =?ISO-8859-1?Q?Espa=F1a?=)
Date: Fri Aug 29 16:48:35 2008
Subject: **********CONGRATULATIONS****************
Message-ID: <20080829164819.5B2A58FC18@mx1.freebsd.org>

 - This mail is in HTML. Some elements may be ommited in plain text. -

Dear Beneficiary,
We are pleased to inform you that you are one of the 2 lucky winners in Euromillones Loteria España, Computer Ballot Drawed 04th Jul 2008.You have won the sum of 1.974.547,Eur ( One Million Nine Hundred And Seventy Four Thousand, Five Hundred And Forty Seven Euros) in cash credited, all winning addresses were randomly selected from a batch of 50,000,000 international email addresses, Your email address emerged alongside 1 other as a 1st category winner. File with Reference number:
ESP/1245/114L/LOP
Winning Number: 7
-19-22-27-48
..file for your claim, Contact: DR. SMITH WALKER .Manager, Rural Consultants SA, with your claim application form below
1.FULL NAMES:__________ ________________________
2.TELEPHONE NUMBER:_______ ______________
3.WINNING NUMBERS:_ __________________________________
4. FULL ADDRESS: __________________________________________
5. COUNTRY: _____________________________________________
6. OCCUPATION: ___________________________________________
7. AGE: ________________________________________________
Reply to Email:
drsmwalker@gmail.com

Contact
Tel:
004470359 30819
..We use this opportunity to bring and promote the Sponsors/Contributors of this program. Heinenken,Sony,Mastercard
Vodafone, Play station, Ford, Microsoft.
Congratulations once again from all our staff
Fiona Sanchez
Secretary

From chinsan.tw at gmail.com  Fri Aug 29 16:58:23 2008
From: chinsan.tw at gmail.com (chinsan)
Date: Fri Aug 29 16:58:29 2008
Subject: broken link
In-Reply-To: <B3D48FE6-B1EA-42B0-BFFA-B3325E086978@bordo.com.au>
References: <B3D48FE6-B1EA-42B0-BFFA-B3325E086978@bordo.com.au>
Message-ID: <1f27304c0808290946q415f7763o39080dfd14a96543@mail.gmail.com>

On Fri, Aug 29, 2008 at 9:53 PM, James Brown <jlbrown@bordo.com.au> wrote:
> Just letting you know that the link to the BIND FAQ (BIND FAQ) on this page:
>
> Domain Name System (DNS)
>
> is broken.
>
> James.

Fixed now.  The corrected version should be online within
24 hours.  Thanks.

- chinsan