From sahil at tandon.net  Tue Jul  1 00:48:52 2008
From: sahil at tandon.net (Sahil Tandon)
Date: Tue Jul  1 00:48:55 2008
Subject: Planet Earth CD-ROM: Over 50% Off - Only $9
In-Reply-To: <8dfae1c10806301557x64710450g257be9d2004cb3be@mail.gmail.com>
References: <14470728.221590871214859701266.JavaMail.?@mx01.pdkp2>
	<8dfae1c10806301557x64710450g257be9d2004cb3be@mail.gmail.com>
Message-ID: <20080701004847.GB20299@shepherd>

Walter Venable <weaseal@gmail.com> wrote:

> Were we meant to get this?  I unsubscribed it.

Of course not.  Don't feed the animals. :-)

-- 
Sahil Tandon <sahil@tandon.net>
From minimarmot at gmail.com  Tue Jul  1 02:28:22 2008
From: minimarmot at gmail.com (Ben Kaduk)
Date: Tue Jul  1 02:28:26 2008
Subject: Patch for pr docs/75865
Message-ID: <47d0403c0806301928q192f1f12m3ec0937d159d1a6@mail.gmail.com>

Hi all,

I updated this PR with a patch:
http://www.freebsd.org/cgi/query-pr.cgi?pr=75865
Basically, mention that restore(1) can run out of space in /tmp/ .
While I'm there, reword a couple of sentences to not start
with (lowercase) command names.

http://stuff.mit.edu/afs/sipb.mit.edu/user/kaduk/freebsd/patches/disks.diff.2008.07.01

-Ben Kaduk
From minimarmot at gmail.com  Tue Jul  1 02:50:08 2008
From: minimarmot at gmail.com (Ben Kaduk)
Date: Tue Jul  1 02:50:10 2008
Subject: docs/75865: comments on "backup-basics" in handbook
Message-ID: <200807010250.m612o7sl094254@freefall.freebsd.org>

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

From: "Ben Kaduk" <minimarmot@gmail.com>
To: bug-followup@freebsd.org
Cc:  
Subject: Re: docs/75865: comments on "backup-basics" in handbook
Date: Mon, 30 Jun 2008 22:16:39 -0400

 I think the inline patch should take care of this -- the other
 programs listed on the page do
 not seem to document using /tmp or other places for intermediate files.
 
 Note that I also reworeded a couple of sentences to avoid starting
 sentences with
 (lowercase) command names, as well.
 
 If gmail mangles whitespace, the patch can also be found at
 http://stuff.mit.edu/afs/sipb.mit.edu/user/kaduk/freebsd/patches/disks.diff.2008.07.01
 
 -Ben Kaduk
 
 --- chapter.sgml.0      2008-06-30 21:11:24.000000000 -0400
 +++ chapter.sgml        2008-06-30 22:09:30.000000000 -0400
 @@ -2380,12 +2380,19 @@
         <command>dump</command> and <command>restore</command>.  They
         operate on the drive as a collection of disk blocks, below the
         abstractions of files, links and directories that are created by
 -       the file systems. <command>dump</command> backs up an entire
 +       the file systems. Unlike other backup software,
 +       <command>dump</command> backs up an entire
         file system on a device.  It is unable to backup only part of a
         file system or a directory tree that spans more than one
 -       file system.  <command>dump</command> does not write files and
 +       file system.  The <command>dump</command> command does not
 write files and
         directories to tape, but rather writes the raw data blocks that
 -       comprise files and directories.</para>
 +       comprise files and directories.  When being used to extract
 +       data, <command>restore</command> stores temporary files
 +       in <filename>/tmp/</filename> by default &emdash; if you are
 +       operating from a recovery disk with a small
 +       <filename>/tmp</filename> directory, you may need to set the
 +       <envar>TMPDIR</envar> environment variable to a directory
 +       with more free space for the restore to be successful.</para>
 
        <note><para>If you use <command>dump</command> on your root
 directory, you
          would not back up <filename>/home</filename>,
From deb at freebsd.org  Tue Jul  1 18:40:09 2008
From: deb at freebsd.org (Deb Goodkin)
Date: Tue Jul  1 18:40:13 2008
Subject: FreeBSD Technologies in Firefox 3 press release
Message-ID: <486A71E0.2060002@freebsd.org>

Do you want to add a link to the press release? I just added it to our 
website. You can add this link, or I can send you the pdf file.


http://www.freebsdfoundation.org/press/2008623-PRrelease.pdf

Thanks,

Deb Goodkin
The FreeBSD Foundation
From danger at FreeBSD.org  Tue Jul  1 20:31:14 2008
From: danger at FreeBSD.org (Daniel Gerzo)
Date: Tue Jul  1 20:31:17 2008
Subject: FreeBSD Technologies in Firefox 3 press release
In-Reply-To: <486A71E0.2060002@freebsd.org>
References: <486A71E0.2060002@freebsd.org>
Message-ID: <26311349.20080701223105@rulez.sk>

Hello Deb,

Tuesday, July 1, 2008, 8:05:20 PM, you wrote:

> Do you want to add a link to the press release? I just added it to our
> website. You can add this link, or I can send you the pdf file.

It's already linked from the "News" section of the FreeBSD.org site.

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

From danger at FreeBSD.org  Tue Jul  1 20:56:52 2008
From: danger at FreeBSD.org (danger@FreeBSD.org)
Date: Tue Jul  1 20:56:54 2008
Subject: docs/121713: man page for su contains errornous example.
Message-ID: <200807012056.m61KupVQ024866@freefall.freebsd.org>

Synopsis: man page for su contains errornous example.

Responsible-Changed-From-To: freebsd-doc->danger
Responsible-Changed-By: danger
Responsible-Changed-When: Tue Jul 1 20:56:39 UTC 2008
Responsible-Changed-Why: 
Track

http://www.freebsd.org/cgi/query-pr.cgi?pr=121713
From danger at FreeBSD.org  Tue Jul  1 21:00:13 2008
From: danger at FreeBSD.org (danger@FreeBSD.org)
Date: Tue Jul  1 21:00:16 2008
Subject: docs/124561: LIBGEOM(3) spelling mistake
Message-ID: <200807012100.m61L09kI025070@freefall.freebsd.org>

Synopsis: LIBGEOM(3) spelling mistake

Responsible-Changed-From-To: freebsd-doc->thompsa
Responsible-Changed-By: danger
Responsible-Changed-When: Tue Jul 1 20:59:47 UTC 2008
Responsible-Changed-Why: 
Make thompsa responsible

http://www.freebsd.org/cgi/query-pr.cgi?pr=124561
From danger at FreeBSD.org  Tue Jul  1 21:54:50 2008
From: danger at FreeBSD.org (danger@FreeBSD.org)
Date: Tue Jul  1 21:54:51 2008
Subject: docs/121821: [patch] wpa_supplicant.conf.5 - provide pointer to
	sample configuration file
Message-ID: <200807012154.m61Lsndp030466@freefall.freebsd.org>

Synopsis: [patch] wpa_supplicant.conf.5 - provide pointer to sample configuration file

Responsible-Changed-From-To: freebsd-doc->danger
Responsible-Changed-By: danger
Responsible-Changed-When: Tue Jul 1 21:54:39 UTC 2008
Responsible-Changed-Why: 
Track

http://www.freebsd.org/cgi/query-pr.cgi?pr=121821
From danger at FreeBSD.org  Tue Jul  1 22:59:48 2008
From: danger at FreeBSD.org (danger@FreeBSD.org)
Date: Tue Jul  1 22:59:51 2008
Subject: docs/120248: [patch] getaddrinfo() implementation on FreeBSD 7
	is incomplete, but no mention in getaddrinfo.3
Message-ID: <200807012259.m61MxlbA035747@freefall.freebsd.org>

Synopsis: [patch] getaddrinfo() implementation on FreeBSD 7 is incomplete, but no mention in getaddrinfo.3

Responsible-Changed-From-To: freebsd-doc->danger
Responsible-Changed-By: danger
Responsible-Changed-When: Tue Jul 1 22:59:34 UTC 2008
Responsible-Changed-Why: 
Track

http://www.freebsd.org/cgi/query-pr.cgi?pr=120248
From minimarmot at gmail.com  Wed Jul  2 04:10:06 2008
From: minimarmot at gmail.com (Ben Kaduk)
Date: Wed Jul  2 04:10:09 2008
Subject: docs/75995: hcreate(3) documentation(?) bug
Message-ID: <200807020410.m624A6AN062743@freefall.freebsd.org>

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

From: "Ben Kaduk" <minimarmot@gmail.com>
To: bug-followup@FreeBSD.org
Cc:  
Subject: Re: docs/75995: hcreate(3) documentation(?) bug
Date: Wed, 2 Jul 2008 00:03:45 -0400

 It definitely looks like a documentation bug.
 
 I've put a patch up at
 http://stuff.mit.edu/afs/sipb.mit.edu/user/kaduk/freebsd/patches/htcreate.diff.2008.07.01
 in case gmail mangles the whitespace.
 
 Thanks to sbahra on #bsddocs for pointing out that we should mention that
 errno gets set.
 
 -Ben Kaduk
 
 --- hcreate.3.0 2008-07-01 23:29:00.000000000 -0400
 +++ hcreate.3   2008-07-01 23:53:17.000000000 -0400
 @@ -1,6 +1,6 @@
  .\" $FreeBSD: src/lib/libc/stdlib/hcreate.3,v 1.5 2005/01/20 09:17:04 ru Exp $
  .\"
 -.Dd May 8, 2001
 +.Dd July 1, 2008
  .Os
  .Dt HCREATE 3
  .Sh NAME
 @@ -23,6 +23,7 @@
  and
  .Fn hsearch
  functions manage hash search tables.
 +Only one hash table per process may be active at any given time.
  .Pp
  The
  .Fn hcreate
 @@ -111,7 +112,7 @@
  .Sh RETURN VALUES
  The
  .Fn hcreate
 -function returns 0 if it cannot allocate sufficient space for the table;
 +function returns 0 if the table creation failed;
  otherwise, it returns non-zero.
  .Pp
  The
 @@ -199,6 +200,8 @@
  .Bl -tag -width Er
  .It Bq Er ENOMEM
  Insufficient storage space is available.
 +.It Bq Er EINVAL
 +A table already exists.
  .El
  .Sh SEE ALSO
  .Xr bsearch 3 ,
From minimarmot at gmail.com  Wed Jul  2 04:35:21 2008
From: minimarmot at gmail.com (Ben Kaduk)
Date: Wed Jul  2 04:35:25 2008
Subject: docs/75995: hcreate(3) documentation(?) bug
In-Reply-To: <200807020410.m624A6AN062743@freefall.freebsd.org>
References: <200807020410.m624A6AN062743@freefall.freebsd.org>
Message-ID: <47d0403c0807012135o294263e7k67ce7af85ef53e20@mail.gmail.com>

On Wed, Jul 2, 2008 at 12:10 AM, Ben Kaduk <minimarmot@gmail.com> wrote:
> The following reply was made to PR docs/75995; it has been noted by GNATS.
>
> From: "Ben Kaduk" <minimarmot@gmail.com>
> To: bug-followup@FreeBSD.org
> Cc:
> Subject: Re: docs/75995: hcreate(3) documentation(?) bug
> Date: Wed, 2 Jul 2008 00:03:45 -0400
>
>  It definitely looks like a documentation bug.
>
>  I've put a patch up at
>  http://stuff.mit.edu/afs/sipb.mit.edu/user/kaduk/freebsd/patches/htcreate.diff.2008.07.01
>  in case gmail mangles the whitespace.
>
>  Thanks to sbahra on #bsddocs for pointing out that we should mention that
>  errno gets set.
>
>  -Ben Kaduk
[...]
>  @@ -111,7 +112,7 @@
>  .Sh RETURN VALUES
>  The
>  .Fn hcreate
>  -function returns 0 if it cannot allocate sufficient space for the table;
>  +function returns 0 if the table creation failed;

That should be
if the table creation failed and sets errno;
the linked patch is updated.

-Ben Kaduk

>  otherwise, it returns non-zero.
>  .Pp
>  The
From minimarmot at gmail.com  Wed Jul  2 05:20:06 2008
From: minimarmot at gmail.com (Ben Kaduk)
Date: Wed Jul  2 05:20:09 2008
Subject: docs/82595: 25.5.3 Configuring a bridge section of the handbook
	needs updating
Message-ID: <200807020520.m625K6JW075723@freefall.freebsd.org>

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

From: "Ben Kaduk" <minimarmot@gmail.com>
To: bug-followup@FreeBSD.org
Cc:  
Subject: Re: docs/82595: 25.5.3 Configuring a bridge section of the handbook needs updating
Date: Wed, 2 Jul 2008 01:13:59 -0400

 The section in question no longer mentions FreeBSD 4.0, nor NIC selection.
 Also, it seems that bridge(4) has supported all ethernet devices since
 2000 (see, for example, if_xl.c rev 1.74 commit log).
 
 I think this PR should be closed.
 
 -Ben Kaduk
From linimon at FreeBSD.org  Wed Jul  2 05:52:52 2008
From: linimon at FreeBSD.org (linimon@FreeBSD.org)
Date: Wed Jul  2 05:52:54 2008
Subject: docs/82595: 25.5.3 Configuring a bridge section of the handbook
	needs updating
Message-ID: <200807020552.m625qpdG078686@freefall.freebsd.org>

Synopsis: 25.5.3 Configuring a bridge section of the handbook needs updating

State-Changed-From-To: open->feedback
State-Changed-By: linimon
State-Changed-When: Wed Jul 2 05:52:24 UTC 2008
State-Changed-Why: 
Does the submitter agree that this one is OBE?

http://www.freebsd.org/cgi/query-pr.cgi?pr=82595
From minimarmot at gmail.com  Wed Jul  2 16:20:21 2008
From: minimarmot at gmail.com (Ben Kaduk)
Date: Wed Jul  2 16:20:25 2008
Subject: docs/75995: hcreate(3) documentation(?) bug
In-Reply-To: <47d0403c0807012135o294263e7k67ce7af85ef53e20@mail.gmail.com>
References: <200807020410.m624A6AN062743@freefall.freebsd.org>
	<47d0403c0807012135o294263e7k67ce7af85ef53e20@mail.gmail.com>
Message-ID: <47d0403c0807020920p33e8ec54v9b261a5c2dc199cf@mail.gmail.com>

On Wed, Jul 2, 2008 at 12:35 AM, Ben Kaduk <minimarmot@gmail.com> wrote:
> On Wed, Jul 2, 2008 at 12:10 AM, Ben Kaduk <minimarmot@gmail.com> wrote:
>> The following reply was made to PR docs/75995; it has been noted by GNATS.
>>
>> From: "Ben Kaduk" <minimarmot@gmail.com>
>> To: bug-followup@FreeBSD.org
>> Cc:
>> Subject: Re: docs/75995: hcreate(3) documentation(?) bug
>> Date: Wed, 2 Jul 2008 00:03:45 -0400
>>
>>  It definitely looks like a documentation bug.
>>
>>  I've put a patch up at
>>  http://stuff.mit.edu/afs/sipb.mit.edu/user/kaduk/freebsd/patches/htcreate.diff.2008.07.01

Sigh.  Apparently I have a finger macro for ``htcreate''; the patch
is, of course, just hcreate.diff.2008.07.01

-Ben Kaduk
From fk at fabiankeil.de  Thu Jul  3 15:10:01 2008
From: fk at fabiankeil.de (Fabian Keil)
Date: Thu Jul  3 15:10:04 2008
Subject: docs/125223: [PATCH] Spelling and grammar fixes for snd_emu10kx(4)
	man page
Message-ID: <200807031504.m63F4HI5030477@www.freebsd.org>


>Number:         125223
>Category:       docs
>Synopsis:       [PATCH] Spelling and grammar fixes for snd_emu10kx(4) 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:   Thu Jul 03 15:10:01 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Fabian Keil
>Release:        CURRENT
>Organization:
>Environment:
FreeBSD TP51.local 8.0-CURRENT FreeBSD 8.0-CURRENT #25: Fri Jun 27 17:43:17 CEST 2008     fk@TP51.local:/usr/obj/usr/src/sys/THINKPAD  i386
>Description:
The attached patch contains spelling and
grammar fixes for the snd_emu10kx(4) man page.
>How-To-Repeat:
man snd_emu10kx
>Fix:


Patch attached with submission follows:

--- .zfs/snapshot/2008-07-02/share/man/man4/snd_emu10kx.4	2008-05-29 23:32:37.160637269 +0200
+++ share/man/man4/snd_emu10kx.4	2008-07-02 15:16:02.452314893 +0200
@@ -143,7 +143,7 @@
 the sound subsystem does not support such an amount of PCM channels.
 This device can not be opened for read, thus confusing many applications.
 .Pp
-Within a multichannel stream , thefirst half (0-15 or 0-31) is a copy of all DSP
+Within a multichannel stream, the first half (0-15 or 0-31) is a copy of all DSP
 outputs, the second half (15-30 or 32-63) is a copy of some DSP inputs.
 On Live! cards the last substream (31) is used as a sync stream and is always
 set to 0xc0de.
@@ -193,7 +193,7 @@
 It controls only front output
 volume in multichannel mode and all output volume in single channel mode.
 .It Qq rec
-mixer control acts very different on EMU10K1 and other cards.
+mixer control acts very differently on EMU10K1 and other cards.
 On EMU10K1 cards it controls the AC97 codec recording level.
 On non-EMU10K1 cards it controls the amount of AC97
 .Dq stereo mix


>Release-Note:
>Audit-Trail:
>Unformatted:
From danger at FreeBSD.org  Thu Jul  3 15:55:46 2008
From: danger at FreeBSD.org (danger@FreeBSD.org)
Date: Thu Jul  3 15:55:48 2008
Subject: docs/125223: [PATCH] Spelling and grammar fixes for
	snd_emu10kx(4) man page
Message-ID: <200807031555.m63FtjJ0028744@freefall.freebsd.org>

Synopsis: [PATCH] Spelling and grammar fixes for snd_emu10kx(4) man page

Responsible-Changed-From-To: freebsd-doc->danger
Responsible-Changed-By: danger
Responsible-Changed-When: Thu Jul 3 15:55:35 UTC 2008
Responsible-Changed-Why: 
Take

http://www.freebsd.org/cgi/query-pr.cgi?pr=125223
From gavin at FreeBSD.org  Thu Jul  3 21:25:23 2008
From: gavin at FreeBSD.org (gavin@FreeBSD.org)
Date: Thu Jul  3 21:25:25 2008
Subject: www/125092: [patch] Addition to AMD64 supported platforms: Tyan
	Tiger K9HE (S3970)
Message-ID: <200807032125.m63LPNkc057836@freefall.freebsd.org>

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

Responsible-Changed-From-To: gavin->freebsd-doc
Responsible-Changed-By: gavin
Responsible-Changed-When: Thu Jul 3 21:24:14 UTC 2008
Responsible-Changed-Why: 
Over to -doc for committing

http://www.freebsd.org/cgi/query-pr.cgi?pr=125092
From mjguzik at gmail.com  Fri Jul  4 08:50:03 2008
From: mjguzik at gmail.com (Mateusz Guzik)
Date: Fri Jul  4 08:50:09 2008
Subject: docs/125253: [patch] jail(2) does not mention about possible error
	EAGAIN
Message-ID: <200807040841.m648fmoU053779@www.freebsd.org>


>Number:         125253
>Category:       docs
>Synopsis:       [patch] jail(2) does not mention about possible error EAGAIN
>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 Jul 04 08:50:03 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Mateusz Guzik
>Release:        8.0-CURRENT
>Organization:
>Environment:
FreeBSD eternal 8.0-CURRENT FreeBSD 8.0-CURRENT #11: Wed Jul  2 15:50:37 CEST 2008     f@eternal:/usr/obj/usr/src/sys/ETERNAL  i386

>Description:
If all valid jids are in use, the kernel returns EAGAIN (see line 177 in sys/kern/kern_jail.c), but man page jail(2) does not mention it.
>How-To-Repeat:

>Fix:
Patch is attached.

Patch attached with submission follows:

--- lib/libc/sys/jail.2.orig	2005-02-09 19:03:14.000000000 +0100
+++ lib/libc/sys/jail.2	2008-07-04 10:33:35.000000000 +0200
@@ -110,10 +110,14 @@
 will fail if:
 .Bl -tag -width Er
 .It Bq Er EINVAL
 The version number of the argument is not correct.
 .El
+.Bl -tag -width Er
+.It Bq Er EAGAIN
+No free JID could be found.
+.El
 .Pp
 Further
 .Fn jail
 calls
 .Xr chroot 2


>Release-Note:
>Audit-Trail:
>Unformatted:
From jahan.geo at yahoo.com  Fri Jul  4 06:24:18 2008
From: jahan.geo at yahoo.com (Subedar Aftab Jahan)
Date: Fri Jul  4 10:59:19 2008
Subject: FAQ Addendum
Message-ID: <105118.21455.qm@web65505.mail.ac4.yahoo.com>

Kindly add this to FAQ:
Q: Why am I seeing this message ?
192.168.0.10 is on fxp1 but got reply from 00:15:17:67:cf:82 on rl0 are seen from 
A: Because the said packet coming from outside the network
Q:How to prevent from repeating this message ?
A:add this to sysctl.conf
net.link.ether.inet.log_arp_wrong_iface: 0


      
From panjinet at gmail.com  Fri Jul  4 10:26:25 2008
From: panjinet at gmail.com (van gee)
Date: Fri Jul  4 10:59:40 2008
Subject: Request freeBSD HandBook
Message-ID: <be9ca320807040257u6bb8b84by19bf0786f5bb7329@mail.gmail.com>

Dear Admin

I'm newbie and I want to learn about freeBSD, could you like give me copy
freeBSD handbook.

Thank' a lot
From peter at bsdly.net  Fri Jul  4 11:12:22 2008
From: peter at bsdly.net (Peter N. M. Hansteen)
Date: Fri Jul  4 11:12:29 2008
Subject: Request freeBSD HandBook
In-Reply-To: <be9ca320807040257u6bb8b84by19bf0786f5bb7329@mail.gmail.com> (van
	gee's message of "Fri, 4 Jul 2008 16:57:14 +0700")
References: <be9ca320807040257u6bb8b84by19bf0786f5bb7329@mail.gmail.com>
Message-ID: <87lk0hsy25.fsf@thingy.bsdly.net>

"van gee" <panjinet@gmail.com> writes:

> I'm newbie and I want to learn about freeBSD, could you like give me copy
> freeBSD handbook.

it's available at <http://www.freebsd.org/doc/en/books/handbook/> 


-- 
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/
"Remember to set the evil bit on all malicious network traffic"
delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
From pgj at FreeBSD.org  Fri Jul  4 11:44:06 2008
From: pgj at FreeBSD.org (Gabor PALI)
Date: Fri Jul  4 11:44:39 2008
Subject: FAQ Addendum
In-Reply-To: <105118.21455.qm@web65505.mail.ac4.yahoo.com>
References: <105118.21455.qm@web65505.mail.ac4.yahoo.com>
Message-ID: <685a6ef80807040417i497e2718o48c80b49887fcad8@mail.gmail.com>

Please write a Problem Report about this, and I will try to help you
(and it will not get lost):

http://www.freebsd.org/send-pr.html

On Fri, Jul 4, 2008 at 7:57 AM, Subedar Aftab Jahan <jahan.geo@yahoo.com> wrote:
> Kindly add this to FAQ:
> Q: Why am I seeing this message ?
> 192.168.0.10 is on fxp1 but got reply from 00:15:17:67:cf:82 on rl0 are seen from
> A: Because the said packet coming from outside the network
> Q:How to prevent from repeating this message ?
> A:add this to sysctl.conf
> net.link.ether.inet.log_arp_wrong_iface: 0
From jahan at geocities.com  Fri Jul  4 19:30:01 2008
From: jahan at geocities.com (Subedar Aftab Jahan)
Date: Fri Jul  4 19:30:08 2008
Subject: docs/125268: FAQ Addendum
Message-ID: <200807041922.m64JMJJY040200@www.freebsd.org>


>Number:         125268
>Category:       docs
>Synopsis:       FAQ Addendum
>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:   Fri Jul 04 19:30:01 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Subedar Aftab Jahan
>Release:        
>Organization:
>Environment:
>Description:
Kindly add this to FAQ:
Q: Why am I seeing this message ?
192.168.0.10 is on fxp1 but got reply from 00:15:17:67:cf:82 on rl0 are seen from 
A: Because the said packet coming from outside the network
Q:How to prevent from repeating this message ?
A:add this to sysctl.conf
net.link.ether.inet.log_arp_wrong_iface: 0
>How-To-Repeat:

>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted:
From pgj at FreeBSD.org  Fri Jul  4 19:35:19 2008
From: pgj at FreeBSD.org (pgj@FreeBSD.org)
Date: Fri Jul  4 19:35:25 2008
Subject: docs/125268: FAQ Addendum
Message-ID: <200807041935.m64JZJqB004771@freefall.freebsd.org>

Synopsis: FAQ Addendum

Responsible-Changed-From-To: freebsd-doc->pgj
Responsible-Changed-By: pgj
Responsible-Changed-When: Fri Jul 4 19:33:54 UTC 2008
Responsible-Changed-Why: 
Take.

http://www.freebsd.org/cgi/query-pr.cgi?pr=125268
From www at FreeBSD.org  Sun Jul  6 01:39:50 2008
From: www at FreeBSD.org (World Wide Web Owner)
Date: Sun Jul  6 01:39:57 2008
Subject: FreeBSD web build failed on www.freebsd.org
Message-ID: <200807060139.m661doVr061441@www.freebsd.org>

/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/en/share/sgml/catalog -c /w/www/build/www/share/sgml/catalog -D /w/www/build/www/en/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
cd growth;  make  all
cd /w/www/build/www/en/ports/growth/../../../tools/portsgrowth;  make  DIRPRFX=ports/ all
/usr/local/bin/gnuplot ports.plt
/usr/local/bin/pngtopnm ports.png | /usr/local/bin/pnmtopng -i > status.png
pnmtopng: 4 colors found
rm ports.png
===> relnotes
===> relnotes/CURRENT/en_US.ISO8859-1 (all)
===> relnotes/CURRENT/en_US.ISO8859-1/relnotes (all)
/bin/rm -f docbook.css
/bin/cat /w/www/build/www/en/relnotes/../../../doc/share/misc/docbook.css > docbook.css
Index is disabled or no index to generate.
/usr/bin/env SP_ENCODING=ISO-8859-1 /usr/local/bin/jade -V nochunks -ioutput.html -d /w/www/build/relnotes/doc/en_US.ISO8859-1/relnotes/../../share/sgml/default.dsl -ifreebsd.urls.relprefix.4 -V %generate-legalnotice-link% -V %generate-docformat-navi-link% -ioutput.html.images  -V %generate-article-toc% -ino.include.historic -D /w/www/build/relnotes/doc/en_US.ISO8859-1/relnotes/../../../share/images/articles/relnotes -D /usr/obj/w/www/build/relnotes/doc/en_US.ISO8859-1/relnotes -c /w/www/build/www/en/relnotes/../../../doc/en_US.ISO8859-1/share/sgml/catalog -c /w/www/build/www/en/relnotes/../../../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 /w/www/build/relnotes/doc/en_US.ISO8859-1/relnotes/../../en_US.ISO8859-1/share/sgml/catalog -c /w/www/build/relnotes/doc/en_US.ISO8859-1/relnotes/../../share/sgml/catalog -c /usr/local/share/sgml/catalog.ports -t sgml /w/www/b
 uild/relnotes/doc/en_US.ISO8859-1/relnotes/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
Index is disabled or no index to generate.
*** Error code 1 (ignored)
/usr/bin/env SP_ENCODING=ISO-8859-1 /usr/local/bin/jade -V html-manifest -ioutput.html -d /w/www/build/relnotes/doc/en_US.ISO8859-1/relnotes/../../share/sgml/default.dsl -ifreebsd.urls.relprefix.4 -V %generate-legalnotice-link% -V %generate-docformat-navi-link% -ioutput.html.images  -V %generate-article-toc% -ino.include.historic -D /w/www/build/relnotes/doc/en_US.ISO8859-1/relnotes/../../../share/images/articles/relnotes -D /usr/obj/w/www/build/relnotes/doc/en_US.ISO8859-1/relnotes -c /w/www/build/www/en/relnotes/../../../doc/en_US.ISO8859-1/share/sgml/catalog -c /w/www/build/www/en/relnotes/../../../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 /w/www/build/relnotes/doc/en_US.ISO8859-1/relnotes/../../en_US.ISO8859-1/share/sgml/catalog -c /w/www/build/relnotes/doc/en_US.ISO8859-1/relnotes/../../share/sgml/catalog -c /usr/local/share/sgml/catalog.ports -t sgml /w/
 www/build/relnotes/doc/en_US.ISO8859-1/relnotes/article.sgml
/usr/local/bin/tidy -wrap 90 -m -raw -preserve -f /dev/null -asxml  $(/usr/bin/xargs < HTML.manifest)
*** Error code 1 (ignored)
===> relnotes/CURRENT/en_US.ISO8859-1/hardware (all)
cd /w/www/build/relnotes/doc/en_US.ISO8859-1/hardware/../../share/sgml && make MAN2HWNOTES_FLAGS= dev-auto.sgml
echo 'PUBLIC "-//FreeBSD//ENTITIES Auto Generated Device Lists//EN"'  '"dev-auto.sgml"' > catalog-auto
/usr/bin/perl /w/www/build/relnotes/doc/share/sgml/../../share/misc/man2hwnotes.pl  -a /w/www/build/relnotes/doc/share/sgml/../../share/misc/dev.archlist.txt -o dev-auto.sgml /w/www/build/relnotes/doc/share/sgml/../../../man4/*.4 /w/www/build/relnotes/doc/share/sgml/../../../man4/man4.*/*.4
/bin/rm -f docbook.css
/bin/cat /w/www/build/www/en/relnotes/../../../doc/share/misc/docbook.css > docbook.css
Index is disabled or no index to generate.
/usr/bin/env SP_ENCODING=ISO-8859-1 /usr/local/bin/jade -V nochunks -ioutput.html -d /w/www/build/relnotes/doc/en_US.ISO8859-1/hardware/../../share/sgml/default.dsl -ifreebsd.urls.relprefix.4 -V %generate-legalnotice-link% -V %generate-docformat-navi-link% -ioutput.html.images  -V %generate-article-toc% -ino.include.historic -D /w/www/build/relnotes/doc/en_US.ISO8859-1/hardware/../../../share/images/articles/hardware -D /usr/obj/w/www/build/relnotes/doc/en_US.ISO8859-1/hardware -c /w/www/build/relnotes/doc/en_US.ISO8859-1/hardware/../../share/sgml/catalog-auto -c /w/www/build/www/en/relnotes/../../../doc/en_US.ISO8859-1/share/sgml/catalog -c /w/www/build/www/en/relnotes/../../../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 /w/www/build/relnotes/doc/en_US.ISO8859-1/hardware/../../en_US.ISO8859-1/share/sgml/catalog -c /w/www/build/relnotes/doc/en_US.ISO8859-1/hardw
 are/../../share/sgml/catalog -c /usr/local/share/sgml/catalog.ports -t sgml /w/www/build/relnotes/doc/en_US.ISO8859-1/hardware/article.sgml > article.html ||  (/bin/rm -f article.html && false)
/usr/local/bin/jade:/w/www/build/relnotes/doc/en_US.ISO8859-1/hardware/article.sgml:730:5:E: general entity "hwlist.oltr" not defined and no default entity
/usr/local/bin/jade:/w/www/build/relnotes/doc/en_US.ISO8859-1/hardware/article.sgml:732:9:E: end tag for "SECT2" which is not finished
/usr/local/bin/jade:/w/www/build/relnotes/doc/en_US.ISO8859-1/hardware/article.sgml:767:5:E: general entity "hwlist.cnw" not defined and no default entity
*** Error code 1

Stop in /w/www/build/relnotes/doc/en_US.ISO8859-1/hardware.
*** Error code 1

Stop in /w/www/build/relnotes/doc/en_US.ISO8859-1.
*** Error code 1

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

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

Stop in /w/www/build/www/en.
      951.26 real       837.90 user        97.45 sys
From keramida at FreeBSD.org  Sun Jul  6 08:10:03 2008
From: keramida at FreeBSD.org (Giorgos Keramidas)
Date: Sun Jul  6 08:10:14 2008
Subject: docs/125329: PACKAGEROOT should be documented in the Handbook
Message-ID: <200807060800.m6680HDb036464@kobe.laptop>


>Number:         125329
>Category:       docs
>Synopsis:       PACKAGEROOT should be documented in the Handbook
>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 Jul 06 08:10:02 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Giorgos Keramidas
>Release:        FreeBSD 8.0-CURRENT i386
>Organization:
>Environment:
System: FreeBSD kobe 8.0-CURRENT FreeBSD 8.0-CURRENT #0: \
Sat Jul 5 08:27:06 EEST 2008 build@kobe:/home/build/obj/home/build/src/sys/KOBE i386

>Description:

PACKAGEROOT and the other pkg_add(1) environment variables should
probably be documented, or at least referenced, in the Handbook too.
They are not 'obvious' for someone reading our Handbook and there's at
least one instance of a recent thread in freebsd-hackers where a user
didn't know about PACKAGEROOT at all.

>How-To-Repeat:
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
From keramida at FreeBSD.org  Sun Jul  6 08:12:59 2008
From: keramida at FreeBSD.org (keramida@FreeBSD.org)
Date: Sun Jul  6 08:13:05 2008
Subject: docs/125329: PACKAGEROOT should be documented in the Handbook
Message-ID: <200807060812.m668CxFt061459@freefall.freebsd.org>

Synopsis: PACKAGEROOT should be documented in the Handbook

Responsible-Changed-From-To: freebsd-doc->keramida
Responsible-Changed-By: keramida
Responsible-Changed-When: Sun Jul 6 08:12:16 UTC 2008
Responsible-Changed-Why: 
Grab PR.  I'll handle this.

http://www.freebsd.org/cgi/query-pr.cgi?pr=125329
From www at FreeBSD.org  Sun Jul  6 09:40:08 2008
From: www at FreeBSD.org (World Wide Web Owner)
Date: Sun Jul  6 09:40:14 2008
Subject: FreeBSD web build failed on www.freebsd.org
Message-ID: <200807060940.m669e7WU094374@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.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/en/share/sgml/catalog -c /w/www/build/www/share/sgml/catalog -D /w/www/build/www/en/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/en/share/sgml/catalog -c /w/www/build/www/share/sgml/catalog -D /w/www/build/www/en/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
===> relnotes
===> relnotes/CURRENT/en_US.ISO8859-1 (all)
===> relnotes/CURRENT/en_US.ISO8859-1/relnotes (all)
/bin/rm -f docbook.css
/bin/cat /w/www/build/www/en/relnotes/../../../doc/share/misc/docbook.css > docbook.css
Index is disabled or no index to generate.
/usr/bin/env SP_ENCODING=ISO-8859-1 /usr/local/bin/jade -V nochunks -ioutput.html -d /w/www/build/relnotes/doc/en_US.ISO8859-1/relnotes/../../share/sgml/default.dsl -ifreebsd.urls.relprefix.4 -V %generate-legalnotice-link% -V %generate-docformat-navi-link% -ioutput.html.images  -V %generate-article-toc% -ino.include.historic -D /w/www/build/relnotes/doc/en_US.ISO8859-1/relnotes/../../../share/images/articles/relnotes -D /usr/obj/w/www/build/relnotes/doc/en_US.ISO8859-1/relnotes -c /w/www/build/www/en/relnotes/../../../doc/en_US.ISO8859-1/share/sgml/catalog -c /w/www/build/www/en/relnotes/../../../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 /w/www/build/relnotes/doc/en_US.ISO8859-1/relnotes/../../en_US.ISO8859-1/share/sgml/catalog -c /w/www/build/relnotes/doc/en_US.ISO8859-1/relnotes/../../share/sgml/catalog -c /usr/local/share/sgml/catalog.ports -t sgml /w/www/b
 uild/relnotes/doc/en_US.ISO8859-1/relnotes/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
Index is disabled or no index to generate.
*** Error code 1 (ignored)
/usr/bin/env SP_ENCODING=ISO-8859-1 /usr/local/bin/jade -V html-manifest -ioutput.html -d /w/www/build/relnotes/doc/en_US.ISO8859-1/relnotes/../../share/sgml/default.dsl -ifreebsd.urls.relprefix.4 -V %generate-legalnotice-link% -V %generate-docformat-navi-link% -ioutput.html.images  -V %generate-article-toc% -ino.include.historic -D /w/www/build/relnotes/doc/en_US.ISO8859-1/relnotes/../../../share/images/articles/relnotes -D /usr/obj/w/www/build/relnotes/doc/en_US.ISO8859-1/relnotes -c /w/www/build/www/en/relnotes/../../../doc/en_US.ISO8859-1/share/sgml/catalog -c /w/www/build/www/en/relnotes/../../../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 /w/www/build/relnotes/doc/en_US.ISO8859-1/relnotes/../../en_US.ISO8859-1/share/sgml/catalog -c /w/www/build/relnotes/doc/en_US.ISO8859-1/relnotes/../../share/sgml/catalog -c /usr/local/share/sgml/catalog.ports -t sgml /w/
 www/build/relnotes/doc/en_US.ISO8859-1/relnotes/article.sgml
/usr/local/bin/tidy -wrap 90 -m -raw -preserve -f /dev/null -asxml  $(/usr/bin/xargs < HTML.manifest)
*** Error code 1 (ignored)
===> relnotes/CURRENT/en_US.ISO8859-1/hardware (all)
cd /w/www/build/relnotes/doc/en_US.ISO8859-1/hardware/../../share/sgml && make MAN2HWNOTES_FLAGS= dev-auto.sgml
echo 'PUBLIC "-//FreeBSD//ENTITIES Auto Generated Device Lists//EN"'  '"dev-auto.sgml"' > catalog-auto
/usr/bin/perl /w/www/build/relnotes/doc/share/sgml/../../share/misc/man2hwnotes.pl  -a /w/www/build/relnotes/doc/share/sgml/../../share/misc/dev.archlist.txt -o dev-auto.sgml /w/www/build/relnotes/doc/share/sgml/../../../man4/*.4 /w/www/build/relnotes/doc/share/sgml/../../../man4/man4.*/*.4
/bin/rm -f docbook.css
/bin/cat /w/www/build/www/en/relnotes/../../../doc/share/misc/docbook.css > docbook.css
Index is disabled or no index to generate.
/usr/bin/env SP_ENCODING=ISO-8859-1 /usr/local/bin/jade -V nochunks -ioutput.html -d /w/www/build/relnotes/doc/en_US.ISO8859-1/hardware/../../share/sgml/default.dsl -ifreebsd.urls.relprefix.4 -V %generate-legalnotice-link% -V %generate-docformat-navi-link% -ioutput.html.images  -V %generate-article-toc% -ino.include.historic -D /w/www/build/relnotes/doc/en_US.ISO8859-1/hardware/../../../share/images/articles/hardware -D /usr/obj/w/www/build/relnotes/doc/en_US.ISO8859-1/hardware -c /w/www/build/relnotes/doc/en_US.ISO8859-1/hardware/../../share/sgml/catalog-auto -c /w/www/build/www/en/relnotes/../../../doc/en_US.ISO8859-1/share/sgml/catalog -c /w/www/build/www/en/relnotes/../../../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 /w/www/build/relnotes/doc/en_US.ISO8859-1/hardware/../../en_US.ISO8859-1/share/sgml/catalog -c /w/www/build/relnotes/doc/en_US.ISO8859-1/hardw
 are/../../share/sgml/catalog -c /usr/local/share/sgml/catalog.ports -t sgml /w/www/build/relnotes/doc/en_US.ISO8859-1/hardware/article.sgml > article.html ||  (/bin/rm -f article.html && false)
/usr/local/bin/jade:/w/www/build/relnotes/doc/en_US.ISO8859-1/hardware/article.sgml:730:5:E: general entity "hwlist.oltr" not defined and no default entity
/usr/local/bin/jade:/w/www/build/relnotes/doc/en_US.ISO8859-1/hardware/article.sgml:732:9:E: end tag for "SECT2" which is not finished
/usr/local/bin/jade:/w/www/build/relnotes/doc/en_US.ISO8859-1/hardware/article.sgml:767:5:E: general entity "hwlist.cnw" not defined and no default entity
*** Error code 1

Stop in /w/www/build/relnotes/doc/en_US.ISO8859-1/hardware.
*** Error code 1

Stop in /w/www/build/relnotes/doc/en_US.ISO8859-1.
*** Error code 1

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

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

Stop in /w/www/build/www/en.
      968.63 real       845.43 user       100.06 sys
From danger at FreeBSD.org  Sun Jul  6 12:18:24 2008
From: danger at FreeBSD.org (danger@FreeBSD.org)
Date: Sun Jul  6 12:18:38 2008
Subject: docs/75995: hcreate(3) documentation(?) bug
Message-ID: <200807061218.m66CIOw6084407@freefall.freebsd.org>

Synopsis: hcreate(3) documentation(?) bug

Responsible-Changed-From-To: freebsd-doc->danger
Responsible-Changed-By: danger
Responsible-Changed-When: Sun Jul 6 12:18:15 UTC 2008
Responsible-Changed-Why: 
Take

http://www.freebsd.org/cgi/query-pr.cgi?pr=75995
From gavin at FreeBSD.org  Sun Jul  6 20:40:01 2008
From: gavin at FreeBSD.org (Gavin Atkinson)
Date: Sun Jul  6 20:40:08 2008
Subject: docs/125346: [patch] updates to developers handbook: tools section
Message-ID: <200807062032.m66KWxtl045563@buffy.york.ac.uk>


>Number:         125346
>Category:       docs
>Synopsis:       [patch] updates to developers handbook: tools section
>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 Jul 06 20:40:01 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Gavin Atkinson
>Release:        FreeBSD 7.0-STABLE amd64
>Organization:
>Environment:
System: FreeBSD buffy.york.ac.uk 7.0-STABLE FreeBSD 7.0-STABLE #3: Fri Jun 20 09:21:51 UTC 2008 root@buffy.york.ac.uk:/usr/obj/usr/src/sys/GENERIC amd64

>Description:
	Updates to the tools section of the developers-handbook.
- Change "most" to "many" wrt people who run gdb inside emacs.  I
suspect "most" people don't usually run gdb inside emacs, but even
if they do, "many" is no less true.
- use role="package" for two ports mentioned.
- reword a paragraph that is either confusing, or plain wrong.
- Change a mention of 2.1.0-RELEASE to 7.0, where is is still valid

>How-To-Repeat:
	N/A
>Fix:

	

--- devh-tools.diff begins here ---
Index: doc/en_US.ISO8859-1/books/developers-handbook/tools/chapter.sgml
===================================================================
RCS file: /home/dcvs/doc/en_US.ISO8859-1/books/developers-handbook/tools/chapter.sgml,v
retrieving revision 1.48
diff -u -r1.48 chapter.sgml
--- doc/en_US.ISO8859-1/books/developers-handbook/tools/chapter.sgml	3 Feb 2008 18:26:28 -0000	1.48
+++ doc/en_US.ISO8859-1/books/developers-handbook/tools/chapter.sgml	6 Jul 2008 18:25:17 -0000
@@ -1410,7 +1410,7 @@
 
       <screen>&prompt.user; <userinput>gdb <replaceable>progname</replaceable></userinput></screen>
 
-      <para>although most people prefer to run it inside
+      <para>although many people prefer to run it inside
 	<application>Emacs</application>.  You can do this by:</para>
 
       <screen><userinput>M-x gdb RET <replaceable>progname</replaceable> RET</userinput></screen>
@@ -1430,8 +1430,8 @@
 	on a few of the basic commands.</para>
 
       <para>Finally, if you find its text-based command-prompt style
-	off-putting, there is a graphical front-end for it (<ulink
-	  url="&url.base;/ports/devel.html">xxgdb</ulink>) in the ports
+	off-putting, there is a graphical front-end for it
+	(<filename role="package">devel/xxgdb</filename>) in the ports
 	collection.</para>
 
       <para>This section is intended to be an introduction to using
@@ -1456,8 +1456,9 @@
 
       <para>At the <command>gdb</command> prompt, type
 	<userinput>break main</userinput>.  This will tell the
-	debugger to skip over the preliminary set-up code in the
-	program and start at the beginning of your code.  Now type
+	debugger that you are not interested in watching the
+	preliminary set-up code in the program being run, and that it
+	should stop executing at the beginning of your code.  Now type
 	<userinput>run</userinput> to start the program&mdash;it will
 	start at the beginning of the set-up code and then get stopped
 	by the debugger when it calls <function>main()</function>.
@@ -1757,9 +1758,9 @@
 
       <para>And doubtless many more that I have overlooked.</para>
 
-      <para>Emacs can be installed on FreeBSD using <ulink
-	  url="&url.base;/ports/editors.html">the Emacs
-	  port</ulink>.</para>
+      <para>Emacs can be installed on FreeBSD using
+	the <filename role="package">editors/emacs</filename>
+	port.</para>
 
       <para>Once it is installed, start it up and do <userinput>C-h
 	  t</userinput> to read an Emacs tutorial&mdash;that means
@@ -2234,7 +2235,7 @@
       <screen>&prompt.user; <userinput>find /usr/ports/lang/whizbang -name "*.el" -print</userinput></screen>
 
       <para>and install them by copying them into the Emacs site Lisp
-	directory.  On FreeBSD 2.1.0-RELEASE, this is
+	directory.  On FreeBSD 7.0-RELEASE, this is
 	<filename>/usr/local/share/emacs/site-lisp</filename>.</para>
 
       <para>So for example, if the output from the find command
--- devh-tools.diff ends here ---


>Release-Note:
>Audit-Trail:
>Unformatted:
From pgj at FreeBSD.org  Sun Jul  6 21:51:52 2008
From: pgj at FreeBSD.org (pgj@FreeBSD.org)
Date: Sun Jul  6 21:51:58 2008
Subject: docs/125346: [patch] updates to developers handbook: tools
	section
Message-ID: <200807062151.m66LplPm031585@freefall.freebsd.org>

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

Responsible-Changed-From-To: freebsd-doc->pgj
Responsible-Changed-By: pgj
Responsible-Changed-When: Sun Jul 6 21:50:00 UTC 2008
Responsible-Changed-Why: 
I will take it.

http://www.freebsd.org/cgi/query-pr.cgi?pr=125346
From bugmaster at FreeBSD.org  Mon Jul  7 11:06:08 2008
From: bugmaster at FreeBSD.org (FreeBSD bugmaster)
Date: Mon Jul  7 11:06:52 2008
Subject: Current unassigned doc problem reports
Message-ID: <200807071106.m67B676o060694@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/107432  doc        Handbook's default partitioning schema is out-of-date
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/121721  doc        telnetd(8) not describing -X authentication types
o docs/121863  doc        IPSEC handbook update for FreeBSD 7 and later
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/123038  doc        [patch] update to projects/c99/index.sgml
o docs/123043  doc        [patch] Update to articles/problem-reports/article.sgm
o docs/123044  doc        [patch] Update to www/en/send-pr.sgml
o docs/123255  doc        mistake in ng_bpf(4) manpage
o docs/123400  doc        gvinum startup in handbook
p docs/124166  doc        fortune: instant-workstation tip should go
o docs/124666  doc        handbook/network-routing.html contains incomplete info
o docs/124716  doc        [patch] GEOM RAID1 handbook example only covers boot p
o docs/124949  doc        Discrepancy between handbook and example hosts file fo
o www/125092   doc        [patch] Addition to AMD64 supported platforms: Tyan Ti
o docs/125253  doc        [patch] jail(2) does not mention about possible error 

137 problems total.

From jdferrell3 at yahoo.com  Tue Jul  8 02:30:02 2008
From: jdferrell3 at yahoo.com (John Ferrell)
Date: Tue Jul  8 02:30:09 2008
Subject: docs/125388: [patch] add zsh(1) to man-refs.ent
Message-ID: <200807080223.m682N8xM076137@www.freebsd.org>


>Number:         125388
>Category:       docs
>Synopsis:       [patch] add zsh(1) to man-refs.ent
>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:   Tue Jul 08 02:30:01 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     John Ferrell
>Release:        7.0
>Organization:
>Environment:
FreeBSD promethium 7.0-RELEASE FreeBSD 7.0-RELEASE #1: Fri Apr  4 19:44:17 EDT 2008     root@promethium:/usr/obj/usr/src/sys/CUSTOM  i386

>Description:
Patch to add zsh(1) to doc/share/sgml/man-refs.ent. Diff is attached.
>How-To-Repeat:

>Fix:


Patch attached with submission follows:

--- man-refs.ent.orig	2008-07-07 22:01:03.000000000 -0400
+++ man-refs.ent	2008-07-07 22:02:31.000000000 -0400
@@ -730,6 +730,7 @@
 <!ENTITY man.zgrep.1 "<citerefentry/<refentrytitle/zgrep/<manvolnum/1//">
 <!ENTITY man.zmore.1 "<citerefentry/<refentrytitle/zmore/<manvolnum/1//">
 <!ENTITY man.znew.1 "<citerefentry/<refentrytitle/znew/<manvolnum/1//">
+<!ENTITY man.zsh.1 "<citerefentry vendor='ports'/<refentrytitle/zsh/<manvolnum/1//">
 
 <!ENTITY man...syscall.2 "<citerefentry/<refentrytitle/__syscall/<manvolnum/2//">
 <!ENTITY man..exit.2 "<citerefentry/<refentrytitle/_exit/<manvolnum/2//">


>Release-Note:
>Audit-Trail:
>Unformatted:
From manolis at FreeBSD.org  Tue Jul  8 07:33:08 2008
From: manolis at FreeBSD.org (manolis@FreeBSD.org)
Date: Tue Jul  8 07:33:14 2008
Subject: docs/125388: [patch] add zsh(1) to man-refs.ent
Message-ID: <200807080733.m687X7ZO009638@freefall.freebsd.org>

Synopsis: [patch] add zsh(1) to man-refs.ent

Responsible-Changed-From-To: freebsd-doc->manolis
Responsible-Changed-By: manolis
Responsible-Changed-When: Tue Jul 8 07:32:11 UTC 2008
Responsible-Changed-Why: 
I'll handle this.

http://www.freebsd.org/cgi/query-pr.cgi?pr=125388
From hostmaster at at.freebsd.org  Thu Jul 10 06:52:05 2008
From: hostmaster at at.freebsd.org (Arsen STASIC)
Date: Thu Jul 10 06:52:12 2008
Subject: Please update handbook/anoncvs.html
Message-ID: <20080710063446.GT12666@wu-wien.ac.at>

Skipped content of type multipart/mixed-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20080710/ed5fdc8c/attachment.pgp
From blackend at FreeBSD.org  Thu Jul 10 07:12:45 2008
From: blackend at FreeBSD.org (Marc Fonvieille)
Date: Thu Jul 10 07:12:53 2008
Subject: Please update handbook/anoncvs.html
In-Reply-To: <20080710063446.GT12666@wu-wien.ac.at>
References: <20080710063446.GT12666@wu-wien.ac.at>
Message-ID: <20080710070005.GB1068@gothic.blackend.org>

On Thu, Jul 10, 2008 at 08:34:46AM +0200, Arsen STASIC wrote:
> Hi,
> 
> we stopped our anoncvs pserver. Could you please update your site.
> I attached the patch.
> 

I updated the Handbook, it should appear soon on the website, thanks.

-- 
Marc
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20080710/552deae7/attachment.pgp
From mjguzik at gmail.com  Thu Jul 10 09:10:06 2008
From: mjguzik at gmail.com (Mateusz Guzik)
Date: Thu Jul 10 09:10:13 2008
Subject: docs/124666: handbook/network-routing.html contains incomplete
	information about mrouted
Message-ID: <200807100910.m6A9A5Bl070850@freefall.freebsd.org>

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

From: Mateusz Guzik <mjguzik@gmail.com>
To: bug-followup@freebsd.org
Cc:  
Subject: Re: docs/124666: handbook/network-routing.html contains incomplete information about mrouted
Date: Thu, 10 Jul 2008 11:08:01 +0200

 This PR can be closed, committed fix was posted in docs/124687.
 
 -- 
 Mateusz Guzik <mjguzik@gmail.com>
From linimon at FreeBSD.org  Thu Jul 10 09:22:36 2008
From: linimon at FreeBSD.org (linimon@FreeBSD.org)
Date: Thu Jul 10 09:22:42 2008
Subject: docs/124666: handbook/network-routing.html contains incomplete
	information about mrouted
Message-ID: <200807100922.m6A9MZFQ072628@freefall.freebsd.org>

Synopsis: handbook/network-routing.html contains incomplete information about mrouted

State-Changed-From-To: open->closed
State-Changed-By: linimon
State-Changed-When: Thu Jul 10 09:22:10 UTC 2008
State-Changed-Why: 
Fix was committed from docs/124687.

http://www.freebsd.org/cgi/query-pr.cgi?pr=124666
From gavin at FreeBSD.org  Thu Jul 10 20:50:03 2008
From: gavin at FreeBSD.org (Gavin Atkinson)
Date: Thu Jul 10 20:50:10 2008
Subject: docs/125485: [patch] updates to developers handbook: security
	section
Message-ID: <200807102040.m6AKewRa069198@buffy.york.ac.uk>


>Number:         125485
>Category:       docs
>Synopsis:       [patch] updates to developers handbook: security section
>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 Jul 10 20:50:02 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Gavin Atkinson
>Release:        FreeBSD 7.0-STABLE amd64
>Organization:
>Environment:
System: FreeBSD buffy.york.ac.uk 7.0-STABLE FreeBSD 7.0-STABLE #3: Fri Jun 20 09:21:51 UTC 2008 root@buffy.york.ac.uk:/usr/obj/usr/src/sys/GENERIC amd64

>Description:
	A couple of updates to the "Secure Programming" section of the
developers handbook:
- Remove an example that is sufficiently old to not really be meaningful.
- StackGuard is no more, replace the mention with a section on ProPolice.
- Clarify a use of "jail" to mean a chroot() jail.
Note that this section also has a section on POSIX Process Capabilities
in need of an update, I'll do that on the next sweep.
>How-To-Repeat:
	N/A
>Fix:

--- devh-secure.diff begins here ---
Index: doc/en_US.ISO8859-1/books/developers-handbook/secure/chapter.sgml
===================================================================
RCS file: /home/dcvs/doc/en_US.ISO8859-1/books/developers-handbook/secure/chapter.sgml,v
retrieving revision 1.28
diff -u -r1.28 chapter.sgml
--- doc/en_US.ISO8859-1/books/developers-handbook/secure/chapter.sgml	4 Aug 2007 08:11:40 -0000	1.28
+++ doc/en_US.ISO8859-1/books/developers-handbook/secure/chapter.sgml	10 Jul 2008 20:34:44 -0000
@@ -57,13 +57,7 @@
 
       <indexterm><primary>Morris Internet worm</primary></indexterm>
 
-      effective today.  Of the 17 CERT security advisories of 1999, 10
-
-      <indexterm>
-        <primary>CERT</primary><secondary>security advisories</secondary>
-      </indexterm>
-
-      of them were directly caused by buffer-overflow software bugs.
+      effective today.
       By far the most common type of buffer overflow attack is based
       on corrupting the stack.</para>
 
@@ -259,39 +253,32 @@
         code in public use which blindly copies memory around without
         using any of the bounded copy routines we just discussed.
         Fortunately, there is another solution.  Several compiler
-        add-ons and libraries exist to do Run-time bounds checking in
+        features and libraries exist to do Run-time bounds checking in
         C/C++.</para> 
 
+	<indexterm><primary>ProPolice</primary></indexterm> 
 	<indexterm><primary>StackGuard</primary></indexterm> 
 	<indexterm><primary>gcc</primary></indexterm>  
 
-        <para>StackGuard is one such add-on that is implemented as a
-        small patch to the gcc code generator.  From the <ulink
-          url="http://immunix.org/stackguard.html">StackGuard
-          website</ulink>:
-
-        <blockquote><para>"StackGuard detects and defeats stack
-        smashing attacks by protecting the return address on the stack
-        from being altered.  StackGuard places a "canary" word next to
-        the return address when a function is called.  If the canary
-        word has been altered when the function returns, then a stack
-        smashing attack has been attempted, and the program responds
-        by emitting an intruder alert into syslog, and then
-        halts."</para></blockquote> 
-
-        <blockquote><para>"StackGuard is implemented as a small patch
-        to the gcc code generator, specifically the function_prolog()
-        and function_epilog() routines.  function_prolog() has been
-        enhanced to lay down canaries on the stack when functions
-        start, and function_epilog() checks canary integrity when the
-        function exits.  Any attempt at corrupting the return address
-        is thus detected before the function
-        returns."</para></blockquote>
-        </para>
+	<para>ProPolice is one such compiler feature, and is
+	integrated into &man.gcc.1; version 4.1 and later.  It
+	replaces and extends the earlier StackGuard &man.gcc.1;
+	extension.</para>
+
+	<para>ProPolice helps to protect against stack-based buffer
+	overflows and other attacks by laying pseudo-random numbers
+	in key areas of the stack before calling any function.  On
+	the function return these "canaries" are checked, and if
+	they are found to have been changed the executable is
+	immediately aborted.  Thus any attempt to modify the return
+	address or other variable stored on the stack in an attempt
+	to get malicious code to run is unlikely to succeed, as the
+	attacker would have to also manage to leave the pseudo-random
+	canaries untouched.</para>
 
         <indexterm><primary>buffer overflow</primary></indexterm>
 
-        <para>Recompiling your application with StackGuard is an
+        <para>Recompiling your application with ProPolice is an
         effective means of stopping most buffer-overflow attacks, but
         it can still be compromised.</para>
 
@@ -378,7 +365,8 @@
       should also be noted that a process can easily break out of a
       chroot environment if it has root privilege.  This could be
       accomplished by creating device nodes to read kernel memory,
-      attaching a debugger to a process outside of the jail, or in
+      attaching a debugger to a process outside of the
+      <function>chroot()</function> jail, or in
       many other creative ways.</para>
       
       <para>The behavior of the <function>chroot()</function> system
--- devh-secure.diff ends here ---


>Release-Note:
>Audit-Trail:
>Unformatted:
From phs at deadc0.de  Thu Jul 10 22:10:01 2008
From: phs at deadc0.de (Philip Schulz)
Date: Thu Jul 10 22:10:08 2008
Subject: docs/125486: Typo in Developer's Handbook, Headline of Chapter 10
Message-ID: <200807102201.m6AM1svE038144@www.freebsd.org>


>Number:         125486
>Category:       docs
>Synopsis:       Typo in Developer's Handbook, Headline of Chapter 10
>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 Jul 10 22:10:00 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Philip Schulz
>Release:        n/a
>Organization:
>Environment:
n/a
>Description:
The headline of chapter 10 has a typo, it should read "Building ...".


>How-To-Repeat:
Look at http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kernelbuild.html


>Fix:
--- doc/en_US.ISO8859-1/books/developers-handbook/kernelbuild/chapter.sgml.orig	2008-07-11 00:00:33.000000000 +0200
+++ doc/en_US.ISO8859-1/books/developers-handbook/kernelbuild/chapter.sgml	2008-07-11 00:00:44.000000000 +0200
@@ -5,7 +5,7 @@
 -->
 
 <chapter id="kernelbuild">
-  <title>Bulding and Installing a &os; Kernel</title>
+  <title>Building and Installing a &os; Kernel</title>
 
   <para>Being a kernel developer requires understanding of the kernel
     build process.  To debug the &os; kernel it is required to be able



>Release-Note:
>Audit-Trail:
>Unformatted:
From miwi at FreeBSD.org  Thu Jul 10 22:15:16 2008
From: miwi at FreeBSD.org (miwi@FreeBSD.org)
Date: Thu Jul 10 22:15:22 2008
Subject: docs/125486: Typo in Developer's Handbook,
	Headline of Chapter 10
Message-ID: <200807102215.m6AMFFsW041058@freefall.freebsd.org>

Synopsis: Typo in Developer's Handbook, Headline of Chapter 10

State-Changed-From-To: open->closed
State-Changed-By: miwi
State-Changed-When: Thu Jul 10 22:15:15 UTC 2008
State-Changed-Why: 
Committed. Thanks!

http://www.freebsd.org/cgi/query-pr.cgi?pr=125486
From dfilter at FreeBSD.ORG  Thu Jul 10 22:20:03 2008
From: dfilter at FreeBSD.ORG (dfilter service)
Date: Thu Jul 10 22:20:10 2008
Subject: docs/125486: commit references a PR
Message-ID: <200807102220.m6AMK3Z5041164@freefall.freebsd.org>

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

From: dfilter@FreeBSD.ORG (dfilter service)
To: bug-followup@FreeBSD.org
Cc:  
Subject: Re: docs/125486: commit references a PR
Date: Thu, 10 Jul 2008 22:14:57 +0000 (UTC)

 miwi        2008-07-10 22:14:48 UTC
 
   FreeBSD doc repository
 
   Modified files:
     en_US.ISO8859-1/books/developers-handbook/kernelbuild 
                                                           chapter.sgml 
   Log:
   - The headline of chapter 10 has a typo, it should read "Building ..."
   
   PR:             125486
   Submitted by:   Philip Schulz <phs@deadc0.de>
   
   Revision  Changes    Path
   1.2       +1 -1      doc/en_US.ISO8859-1/books/developers-handbook/kernelbuild/chapter.sgml
 _______________________________________________
 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 Alexandre.Borrut at open-lux.com  Fri Jul 11 04:38:40 2008
From: Alexandre.Borrut at open-lux.com (Alexandre Borrut)
Date: Fri Jul 11 04:38:51 2008
Subject: Handbook outdated on IPSEC
Message-ID: <4876DD85.5@open-lux.com>

Hi

I'm really disapointed to see an outdated handbook on the ipsec: 
http://www.freebsd.org/doc/en/books/handbook/ipsec.html

the right options to build the kernel are (from man ipsec):

     options IPSEC
     options IPSEC_FILTERTUNNEL
     device crypto

 I was using the handbook as a reference documentation like OpenBSD.

 Another bug came from cvsup2.fr.FreeBSD.org which gives me missing 
files on kernel compilation... It's an official mirror right ?

Regards,
Sacha.


From pgj at FreeBSD.org  Fri Jul 11 05:19:46 2008
From: pgj at FreeBSD.org (pgj@FreeBSD.org)
Date: Fri Jul 11 05:19:59 2008
Subject: docs/125485: [patch] updates to developers handbook: security
	section
Message-ID: <200807110519.m6B5Jk3V082470@freefall.freebsd.org>

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

Responsible-Changed-From-To: freebsd-doc->pgj
Responsible-Changed-By: pgj
Responsible-Changed-When: Fri Jul 11 05:19:03 UTC 2008
Responsible-Changed-Why: 
Grab.

http://www.freebsd.org/cgi/query-pr.cgi?pr=125485
From arved at FreeBSD.org  Fri Jul 11 09:05:18 2008
From: arved at FreeBSD.org (Tilman Linneweh)
Date: Fri Jul 11 09:05:27 2008
Subject: Please update handbook/anoncvs.html
In-Reply-To: <20080710070005.GB1068@gothic.blackend.org>
References: <20080710063446.GT12666@wu-wien.ac.at>
	<20080710070005.GB1068@gothic.blackend.org>
Message-ID: <EC384CAF-FCE1-4DF8-AFA0-9A05E8E768A4@FreeBSD.org>


On Jul 10, 2008, at 9:00, Marc Fonvieille wrote:
>> we stopped our anoncvs pserver. Could you please update your site.
>> I attached the patch.
>>
>
> I updated the Handbook, it should appear soon on the website, thanks.
>

While you are at it, could you also remove the German one?
anoncvs.de.freebsd.org currently points to a non-existing hostname.  
(IIRC the host grappa died about two years ago).

Luckily the french one still works :-)

regards
tilman
From danger at FreeBSD.org  Fri Jul 11 09:20:47 2008
From: danger at FreeBSD.org (Daniel Gerzo)
Date: Fri Jul 11 09:20:53 2008
Subject: Please update handbook/anoncvs.html
In-Reply-To: <EC384CAF-FCE1-4DF8-AFA0-9A05E8E768A4@FreeBSD.org>
References: <20080710063446.GT12666@wu-wien.ac.at>
	<20080710070005.GB1068@gothic.blackend.org>
	<EC384CAF-FCE1-4DF8-AFA0-9A05E8E768A4@FreeBSD.org>
Message-ID: <1805065594.20080711112036@rulez.sk>

Hello Tilman,

Friday, July 11, 2008, 11:04:40 AM, you wrote:

> While you are at it, could you also remove the German one?
> anoncvs.de.freebsd.org currently points to a non-existing hostname.  
> (IIRC the host grappa died about two years ago).

done; thanks for pointing us at it.

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

From rlarsen at gmail.com  Fri Jul 11 20:45:31 2008
From: rlarsen at gmail.com (Russell Larsen)
Date: Fri Jul 11 20:45:39 2008
Subject: Signals section
Message-ID: <33472D81-9DD5-4593-88EE-11AC1DE4AAEA@gmail.com>

In the documentation found at
http://www.freebsd.org/doc/en/books/design-44bsd/book.html
in Section 2.4.1 there is a reference to Section 4.7, but I am not  
seeing this section.

I am looking for information about FreeBSD signals, where should I  
start?

Thanks for your time,
Russell


From p22s at rambler.ru  Fri Jul 11 23:08:44 2008
From: p22s at rambler.ru (p22s)
Date: Fri Jul 11 23:08:50 2008
Subject: docs
Message-ID: <4877E2C2.6070304@rambler.ru>

??????? 2-2. ???? ?????? ?????? (no image)
http://freebsd.org.ua  Handbook
From rb at gid.co.uk  Sat Jul 12 10:30:01 2008
From: rb at gid.co.uk (Bob Bishop)
Date: Sat Jul 12 10:30:32 2008
Subject: docs/125535: Errors in ahc(4) man page
Message-ID: <200807121024.m6CAORbu063109@www.freebsd.org>


>Number:         125535
>Category:       docs
>Synopsis:       Errors in ahc(4) man page
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Jul 12 10:30:01 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Bob Bishop
>Release:        7.0
>Organization:
GID ltd
>Environment:
FreeBSD xxx.xxx 7.0-RELEASE FreeBSD 7.0-RELEASE #1: Tue May 20 22:45:32 BST 2008     rb@xxx.xxx:/usr/src/sys/i386/compile/GID1  i386
>Description:
ahc(4) man page erroneously states that the driver supports Adaptec 2920. In fact, 2920 (and 2920A) use a Future Domain chip and are supported by the stg driver. 2920C is indeed supported by the ahc driver.
>How-To-Repeat:
man ahc
man stg
>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted:
From mjguzik at gmail.com  Sat Jul 12 17:30:01 2008
From: mjguzik at gmail.com (Mateusz Guzik)
Date: Sat Jul 12 17:30:08 2008
Subject: docs/125546: [patch] ktrace(2) contains outdated struct ktr_header
Message-ID: <200807121722.m6CHMm6h006893@www.freebsd.org>


>Number:         125546
>Category:       docs
>Synopsis:       [patch] ktrace(2) contains outdated struct ktr_header
>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:   Sat Jul 12 17:30:01 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Mateusz Guzik
>Release:        8.0-CURRENT
>Organization:
>Environment:
FreeBSD eternal 8.0-CURRENT FreeBSD 8.0-CURRENT #14: Tue Jul  8 02:28:46 CEST 2008     f@eternal:/usr/obj/usr/src/sys/ETERNAL  i386

>Description:
struct ktr_header in ktrace(2):
[..]
caddr_t ktr_buf;
};

struct ktr_header in /usr/include/sys/ktrace.h:
[..]
intptr_t        ktr_tid;        /* was ktr_buffer */
};

>How-To-Repeat:

>Fix:
Patch is attached.

Patch attached with submission follows:

--- ./lib/libc/sys/ktrace.2.orig	2008-07-12 18:54:22.000000000 +0200
+++ ./lib/libc/sys/ktrace.2	2008-07-12 19:16:53.000000000 +0200
@@ -99,11 +99,11 @@
 	int	ktr_len;		/* length of buf */
 	short	ktr_type;		/* trace record type */
 	pid_t	ktr_pid;		/* process id */
 	char	ktr_comm[MAXCOMLEN+1];	/* command name */
 	struct	timeval ktr_time;	/* timestamp */
-	caddr_t	ktr_buf;
+	intptr_t	ktr_tid;
 };
 .Ed
 .Pp
 The
 .Va ktr_len
@@ -118,12 +118,12 @@
 The
 .Va ktr_time
 field gives the time (with microsecond resolution)
 that the record was generated.
 The
-.Va ktr_buf
-is an internal kernel pointer and is not useful.
+.Va ktr_tid
+field holds a threadid.
 .Pp
 The generic header is followed by
 .Va ktr_len
 bytes of a
 .Va ktr_type


>Release-Note:
>Audit-Trail:
>Unformatted:
From yanefbsd at gmail.com  Sun Jul 13 00:11:54 2008
From: yanefbsd at gmail.com (Garrett Cooper)
Date: Sun Jul 13 00:12:01 2008
Subject: RFC : Add ports "status update" page to the FreeBSD wiki
In-Reply-To: <8878A47C-C488-444F-BA53-2D1E1255F99E@gmail.com>
References: <8878A47C-C488-444F-BA53-2D1E1255F99E@gmail.com>
Message-ID: <02007915-873C-4889-A42D-77CD7B98B59D@gmail.com>

On Jul 12, 2008, at 4:52 PM, Garrett Cooper wrote:

> Hello doc'ers,
> 	Before going and making a change to the Wiki, I was wondering  
> whether or not folks would be receptive to adding a "meta-page" to  
> track ports updates for larger / fairly dependent packages, such as  
> Perl, Python, KDE, Gnome, X.org, etc for purposes of reducing long  
> email threads with little benefit, like the following:
>
> http://lists.freebsd.org/pipermail/freebsd-ports/2008-July/049609.html
> http://lists.freebsd.org/pipermail/freebsd-ports/2008-July/049616.html
>
> 	(Both are from the same mail thread, but just were filed  
> differently in mailman).
> 	The issue is that sometimes ports progress can go 'unpublicized'  
> for some time and people aren't aware of why port(s) x-y-z hasn't/ 
> haven't been updated yet, even though it's/they have been  
> 'stable' (in this case Perl) for months.
> Thanks,
> -Garrett

	I read through and apparently there already is sort of a TODO list  
for KDE, but not for gnome, and not for any other important projects.
	Just thought I'd note that before someone else does...
Thanks,
-Garrett
From yanefbsd at gmail.com  Sun Jul 13 00:15:49 2008
From: yanefbsd at gmail.com (Garrett Cooper)
Date: Sun Jul 13 00:15:56 2008
Subject: RFC : Add ports "status update" page to the FreeBSD wiki
Message-ID: <8878A47C-C488-444F-BA53-2D1E1255F99E@gmail.com>

Hello doc'ers,
	Before going and making a change to the Wiki, I was wondering whether  
or not folks would be receptive to adding a "meta-page" to track ports  
updates for larger / fairly dependent packages, such as Perl, Python,  
KDE, Gnome, X.org, etc for purposes of reducing long email threads  
with little benefit, like the following:

http://lists.freebsd.org/pipermail/freebsd-ports/2008-July/049609.html
http://lists.freebsd.org/pipermail/freebsd-ports/2008-July/049616.html

	(Both are from the same mail thread, but just were filed differently  
in mailman).
	The issue is that sometimes ports progress can go 'unpublicized' for  
some time and people aren't aware of why port(s) x-y-z hasn't/haven't  
been updated yet, even though it's/they have been 'stable' (in this  
case Perl) for months.
Thanks,
-Garrett
From david at vizion2000.net  Sun Jul 13 08:57:05 2008
From: david at vizion2000.net (David Southwell)
Date: Sun Jul 13 08:57:12 2008
Subject: RFC : Add ports "status update" page to the FreeBSD wiki
In-Reply-To: <8878A47C-C488-444F-BA53-2D1E1255F99E@gmail.com>
References: <8878A47C-C488-444F-BA53-2D1E1255F99E@gmail.com>
Message-ID: <200807130203.11912.david@vizion2000.net>

On Saturday 12 July 2008 16:52:43 Garrett Cooper wrote:
> Hello doc'ers,
> 	Before going and making a change to the Wiki, I was wondering whether
> or not folks would be receptive to adding a "meta-page" to track ports
> updates for larger / fairly dependent packages, such as Perl, Python,
> KDE, Gnome, X.org, etc for purposes of reducing long email threads
> with little benefit, like the following:
>
> http://lists.freebsd.org/pipermail/freebsd-ports/2008-July/049609.html
> http://lists.freebsd.org/pipermail/freebsd-ports/2008-July/049616.html
>
> 	(Both are from the same mail thread, but just were filed differently
> in mailman).
> 	The issue is that sometimes ports progress can go 'unpublicized' for
> some time and people aren't aware of why port(s) x-y-z hasn't/haven't
> been updated yet, even though it's/they have been 'stable' (in this
> case Perl) for months.
> Thanks,
> -Garrett

Sounds a very good idea to me - especially in view of recent experience!!

Thank you

David
From zb at ispid.com.pl  Sun Jul 13 12:28:17 2008
From: zb at ispid.com.pl (Zbigniew Baniewski)
Date: Sun Jul 13 12:28:25 2008
Subject: "FreeBSD Handbook": 5.4 X11 Configuration
Message-ID: <20080713120134.GA5599@sarge.my.own.domain.no-net>

Hallo,

I would to suggest to add information about configuration using RandR.
I had much trouble lately finding out, why my well-tested configuration
isn't working anymore - until I've learned, that newer versions of video
drivers were designed especially to utilize RandR during video configuration,
and because of this some functionality (f.e. "panned virtual screen") are
(temporarily?) lost.

It should be stressed, that RandR isn't just a tool to check-out available
video-modes, but the quite new way to configure video, which supposingly
required serious changes in video drivers.

http://www.thinkwiki.org/wiki/Xorg_RandR_1.2

And f.e. http://lists.freedesktop.org/archives/xorg/2008-March/034166.html

#v+
  The radeon driver got xrandr 1.2 support.  Previous versions of the
  driver assumed one monitor per driver instance while with xrandr you
  may have several monitors.  With xrandr it is much more important to
  get mode information about each monitor since you may have two or more
  monitors connected with vastly different capabilities.  The previous
  version of the driver more or less always assumed a monitor was
  connected and forced whatever mode you specified.  You can still do
  this, but as you see, the configuration has changed a bit.  This page
  should give you a good overview:

  http://www.intellinuxgraphics.org/dualhead.html
#v-

-- 
				pozdrawiam / regards

						Zbigniew Baniewski
From remko at FreeBSD.org  Sun Jul 13 13:43:18 2008
From: remko at FreeBSD.org (remko@FreeBSD.org)
Date: Sun Jul 13 13:43:35 2008
Subject: docs/125546: [patch] ktrace(2) contains outdated struct
	ktr_header
Message-ID: <200807131343.m6DDhHdA064651@freefall.freebsd.org>

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

State-Changed-From-To: open->patched
State-Changed-By: remko
State-Changed-When: Sun Jul 13 13:43:10 UTC 2008
State-Changed-Why: 
patched in current

http://www.freebsd.org/cgi/query-pr.cgi?pr=125546
From dfilter at FreeBSD.ORG  Sun Jul 13 13:50:03 2008
From: dfilter at FreeBSD.ORG (dfilter service)
Date: Sun Jul 13 13:50:08 2008
Subject: docs/125546: commit references a PR
Message-ID: <200807131350.m6DDo25M064793@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: Sun, 13 Jul 2008 13:43:27 +0000 (UTC)

 remko       2008-07-13 13:42:52 UTC
 
   FreeBSD src repository
 
   Modified files:
     lib/libc/sys         ktrace.2 
   Log:
   SVN rev 180491 on 2008-07-13 13:42:52Z by remko
   
   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.26      +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 remko at FreeBSD.org  Sun Jul 13 13:56:32 2008
From: remko at FreeBSD.org (remko@FreeBSD.org)
Date: Sun Jul 13 13:56:38 2008
Subject: docs/125535: Errors in ahc(4) man page
Message-ID: <200807131356.m6DDuVMn065027@freefall.freebsd.org>

Synopsis: Errors in ahc(4) man page

State-Changed-From-To: open->patched
State-Changed-By: remko
State-Changed-When: Sun Jul 13 13:56:25 UTC 2008
State-Changed-Why: 
patched in current

http://www.freebsd.org/cgi/query-pr.cgi?pr=125535
From remko at FreeBSD.org  Sun Jul 13 13:59:39 2008
From: remko at FreeBSD.org (remko@FreeBSD.org)
Date: Sun Jul 13 13:59:45 2008
Subject: docs/123044: [patch] Update to www/en/send-pr.sgml
Message-ID: <200807131359.m6DDxdRu065134@freefall.freebsd.org>

Synopsis: [patch] Update to www/en/send-pr.sgml

State-Changed-From-To: open->closed
State-Changed-By: remko
State-Changed-When: Sun Jul 13 13:59:38 UTC 2008
State-Changed-Why: 
I think the current entry is just fine. Thanks for helping considering
to improve this though, it's greatly appreciated!

http://www.freebsd.org/cgi/query-pr.cgi?pr=123044
From dfilter at FreeBSD.ORG  Sun Jul 13 14:00:11 2008
From: dfilter at FreeBSD.ORG (dfilter service)
Date: Sun Jul 13 14:00:20 2008
Subject: docs/125535: commit references a PR
Message-ID: <200807131400.m6DE0Bww065264@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: Sun, 13 Jul 2008 13:56:55 +0000 (UTC)

 remko       2008-07-13 13:56:21 UTC
 
   FreeBSD src repository
 
   Modified files:
     share/man/man4       ahc.4 
   Log:
   SVN rev 180492 on 2008-07-13 13:56:21Z by remko
   
   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.40      +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 remko at FreeBSD.org  Sun Jul 13 14:05:01 2008
From: remko at FreeBSD.org (remko@FreeBSD.org)
Date: Sun Jul 13 14:05:07 2008
Subject: docs/123043: [patch] Update to
	articles/problem-reports/article.sgml
Message-ID: <200807131405.m6DE51u9065718@freefall.freebsd.org>

Synopsis: [patch] Update to articles/problem-reports/article.sgml

State-Changed-From-To: open->closed
State-Changed-By: remko
State-Changed-When: Sun Jul 13 14:05:00 UTC 2008
State-Changed-Why: 
Committed. Thanks!

http://www.freebsd.org/cgi/query-pr.cgi?pr=123043
From remko at FreeBSD.org  Sun Jul 13 14:06:16 2008
From: remko at FreeBSD.org (remko@FreeBSD.org)
Date: Sun Jul 13 14:06:23 2008
Subject: docs/123038: [patch] update to projects/c99/index.sgml
Message-ID: <200807131406.m6DE6FlH065838@freefall.freebsd.org>

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

State-Changed-From-To: open->feedback
State-Changed-By: remko
State-Changed-When: Sun Jul 13 14:06:15 UTC 2008
State-Changed-Why: 
Hi Lawrence, the latest patch is broken for me in this view, can you
send me a correct one? Thanks!

http://www.freebsd.org/cgi/query-pr.cgi?pr=123038
From dfilter at FreeBSD.ORG  Sun Jul 13 14:10:06 2008
From: dfilter at FreeBSD.ORG (dfilter service)
Date: Sun Jul 13 14:10:16 2008
Subject: docs/123043: commit references a PR
Message-ID: <200807131410.m6DEA53V065961@freefall.freebsd.org>

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

From: dfilter@FreeBSD.ORG (dfilter service)
To: bug-followup@FreeBSD.org
Cc:  
Subject: Re: docs/123043: commit references a PR
Date: Sun, 13 Jul 2008 14:04:47 +0000 (UTC)

 remko       2008-07-13 14:04:34 UTC
 
   FreeBSD doc repository
 
   Modified files:
     en_US.ISO8859-1/articles/problem-reports article.sgml 
   Log:
   Clarify that we need to use the brackets, and update the web page references
   with actual links. [1]
   
   Also s/submittal/submission/ (changed by myself)
   
   PR:                     123043 [1]
   Submitted by:           Lawrence Mayer <lawmay3 at i12 dot com> [1]
   
   Revision  Changes    Path
   1.57      +10 -9     doc/en_US.ISO8859-1/articles/problem-reports/article.sgml
 _______________________________________________
 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 smallm at panix.com  Sun Jul 13 16:00:08 2008
From: smallm at panix.com (Mike Small)
Date: Sun Jul 13 16:00:14 2008
Subject: docs/125571: Typo in FAQ Answer 4.3.2 -- Persuing should be Perusing
Message-ID: <200807131550.m6DFoP4H029767@www.freebsd.org>


>Number:         125571
>Category:       docs
>Synopsis:       Typo in FAQ Answer 4.3.2 -- Persuing should be Perusing
>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 Jul 13 16:00:07 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Mike Small
>Release:        7.0-RELEASE
>Organization:
>Environment:
FreeBSD rex 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sun Feb 24 19:59:52 UTC 2008     root@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  i386
>Description:
There's a typo in the last sentence of the first paragraph of the answer part of section 4.3.2 in the FAQ: "Persuing the FreeBSD symmetric multiprocessing mailing list may yield some clues."  I assume "Persuing" was meant to be "Perusing".
>How-To-Repeat:
Visit http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/compatibility-processors.html#SMP-SUPPORT
>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted:
From trhodes at FreeBSD.org  Sun Jul 13 18:25:53 2008
From: trhodes at FreeBSD.org (trhodes@FreeBSD.org)
Date: Sun Jul 13 18:25:59 2008
Subject: docs/121863: IPSEC handbook update for FreeBSD 7 and later
Message-ID: <200807131825.m6DIPqln089843@freefall.freebsd.org>

Synopsis: IPSEC handbook update for FreeBSD 7 and later

State-Changed-From-To: open->closed
State-Changed-By: trhodes
State-Changed-When: Sun Jul 13 18:24:15 UTC 2008
State-Changed-Why: 
I have re-written the IPsec section in the handbook, should
fix this problem and make life easier for people.  Thanks!


Responsible-Changed-From-To: freebsd-doc->trhodes
Responsible-Changed-By: trhodes
Responsible-Changed-When: Sun Jul 13 18:24:15 UTC 2008
Responsible-Changed-Why: 
Take

http://www.freebsd.org/cgi/query-pr.cgi?pr=121863
From remko at FreeBSD.org  Sun Jul 13 18:30:05 2008
From: remko at FreeBSD.org (Remko Lodder)
Date: Sun Jul 13 18:30:11 2008
Subject: docs/125571: Typo in FAQ Answer 4.3.2 -- Persuing should be
	Perusing
Message-ID: <200807131830.m6DIU5dY090140@freefall.freebsd.org>

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

From: Remko Lodder <remko@FreeBSD.org>
To: Mike Small <smallm@panix.com>
Cc: freebsd-gnats-submit@FreeBSD.org, Gabor Pali <pgj@FreeBSD.org>
Subject: Re: docs/125571: Typo in FAQ Answer 4.3.2 -- Persuing should be Perusing
Date: Sun, 13 Jul 2008 20:23:45 +0200

 Mike Small wrote:
 
 Hello,
 
 I think persuing as mentioned here means, following the context
 (I am persuing a certification, I am trying to get a certification)
 
 and not perusing. Though the text might be clarified a bit to get a 
 better reflection.
 
 -- 
 
 /"\   Best regards,                      | remko@FreeBSD.org
 \ /   Remko Lodder                       | remko@EFnet
   X    http://www.evilcoder.org/          |
 / \   ASCII Ribbon Campaign              | Against HTML Mail and News
From pgj at FreeBSD.org  Sun Jul 13 18:50:08 2008
From: pgj at FreeBSD.org (pgj@FreeBSD.org)
Date: Sun Jul 13 18:50:15 2008
Subject: docs/125571: Typo in FAQ Answer 4.3.2 -- Persuing should be
	Perusing
Message-ID: <200807131850.m6DIo7Hv092661@freefall.freebsd.org>

Synopsis: Typo in FAQ Answer 4.3.2 -- Persuing should be Perusing

Responsible-Changed-From-To: freebsd-doc->pgj
Responsible-Changed-By: pgj
Responsible-Changed-When: Sun Jul 13 18:49:32 UTC 2008
Responsible-Changed-Why: 
I will take care of it.

http://www.freebsd.org/cgi/query-pr.cgi?pr=125571
From n-kogane at syd.odn.ne.jp  Sun Jul 13 19:40:06 2008
From: n-kogane at syd.odn.ne.jp (n-kogane@syd.odn.ne.jp)
Date: Sun Jul 13 19:40:21 2008
Subject: docs/125581: In manpages on i386,
	there are two same name files. man4/i386/ichwd.4 & man4/ichwd.4.
Message-ID: <20080713183931.8958A2843F@kcesx30.koganemaru.co.jp>


>Number:         125581
>Category:       docs
>Synopsis:       In manpages on i386, there are two same name files. man4/i386/ichwd.4 & man4/ichwd.4.
>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 Jul 13 19:40:06 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Nobuyuki Koganemaru
>Release:        FreeBSD 7.0-RELEASE i386, FreeBSD 8.0-CURRENT i386.
>Organization:
KOGANEMARU Computer Engineering Service Corporation.
>Environment:
System: FreeBSD kcesx37.koganemaru.co.jp 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sun Feb 24 19:59:52 UTC 2008 root@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386


>Description:
	In 7.0-RELEASE, 8.0-CURRENT manpages on i386,
	there are two same name files.
	man4/i386/ichwd.4 and man4/ichwd.4.
	Which one is correct?	
>How-To-Repeat:
	please check manpages.
>Fix:
	I do not known. 

>Release-Note:
>Audit-Trail:
>Unformatted:
From lgusenet at be-well.ilk.org  Sun Jul 13 21:59:58 2008
From: lgusenet at be-well.ilk.org (Lowell Gilbert)
Date: Sun Jul 13 22:00:04 2008
Subject: Signals section
In-Reply-To: <33472D81-9DD5-4593-88EE-11AC1DE4AAEA@gmail.com> (Russell
	Larsen's message of "Fri\, 11 Jul 2008 13\:19\:32 -0700")
References: <33472D81-9DD5-4593-88EE-11AC1DE4AAEA@gmail.com>
Message-ID: <44zlol31de.fsf@lowell-desk.lan>

rlarsen@gmail.com (Russell Larsen) writes:

> In the documentation found at
> http://www.freebsd.org/doc/en/books/design-44bsd/book.html
> in Section 2.4.1 there is a reference to Section 4.7, but I am not
> seeing this section.

Right.  If you look more carefully, you will notice that this is an
excerpt from a book.  To see the rest of the book you would need to
buy it (or, preferably, the newer edition, "The Design and Implementation of
the FreeBSD Operating System").

> I am looking for information about FreeBSD signals, where should I
> start?

Definitely start by reading "man signal" if you haven't already.
There is also some material in the Developer's Handbook that you
should look at before purchasing printed books.

Good luck; let us know if you have some more-specific questions about
the documentation.
From smallm at panix.com  Mon Jul 14 03:20:02 2008
From: smallm at panix.com (Mike Small)
Date: Mon Jul 14 03:20:08 2008
Subject: docs/125587: FAQ entry 5.13 -- adjustion is not an English word;
	tunable?
Message-ID: <200807140316.m6E3GRBQ087238@www.freebsd.org>


>Number:         125587
>Category:       docs
>Synopsis:       FAQ entry 5.13 -- adjustion is not an English word; tunable?
>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 Jul 14 03:20:01 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Mike Small
>Release:        7.0-RELEASE
>Organization:
>Environment:
FreeBSD rex 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sun Feb 24 19:59:52 UTC 2008     root@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  i386
>Description:
First of all, the second sentence in paragraph three of FAQ entry 5.13 uses the word "adjustion".  I don't believe this is a word in English.  Probably the word "adjustment" would be more suitable.

Secondly, the same paragraph also uses the word "tunable" as a noun.  Is this a term people use in BSD?  I mean, it's clear what's meant from the context, but using "variable" or "sysctl variable", as is done in the first paragraph, seems clearer and less strange to me.

Lastly, the word "in" is repeated: "If this tunable needs adjustion it needs to be defined in in /boot/loader.conf"
>How-To-Repeat:
View http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/troubleshoot.html#PROC-TABLE-FULL
>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted:
From ws at au.dyndns.ws  Mon Jul 14 05:40:05 2008
From: ws at au.dyndns.ws (Wayne Sierke)
Date: Mon Jul 14 05:40:11 2008
Subject: docs/125587: FAQ entry 5.13 -- adjustion is not an English
	word; tunable?
Message-ID: <200807140540.m6E5e5Hf060446@freefall.freebsd.org>

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

From: Wayne Sierke <ws@au.dyndns.ws>
To: Mike Small <smallm@panix.com>
Cc: bug-followup@freebsd.org
Subject: Re: docs/125587: FAQ entry 5.13 -- adjustion is not an English
	word; tunable?
Date: Mon, 14 Jul 2008 15:05:22 +0930

 On Mon, 2008-07-14 at 03:16 +0000, Mike Small wrote:
 > Secondly, the same paragraph also uses the word "tunable" as a noun.
 > Is this a term people use in BSD?  I mean, it's clear what's meant
 > from the context, but using "variable" or "sysctl variable", as is
 > done in the first paragraph, seems clearer and less strange to me.
 
 My understanding is that the term 'tunable' is used to refer to sysctl
 variables that can only be set at boot - i.e. are read-only at run-time.
 
 
 How about this?:
 
 The FreeBSD kernel limits the number of processes that may exist at one
 time. The default limit is based on the kern.maxusers sysctl(8)
 variable. kern.maxusers also affects various other in-kernel limits,
 such as network buffers (see this earlier question). If your machine is
 heavily loaded, you probably want to increase kern.maxusers. This will
 increase these other system limits in addition to the maximum number of
 processes.
 
 To adjust the kern.maxusers value, see the File/Process Limits section
 of the Handbook. (While that section refers to open files, the same
 limits apply to processes.)
 
 If your machine is lightly loaded and you are simply running a very
 large number of processes, you can adjust this with the kern.maxproc
 tunable. The value of this sysctl ´variable¡ is set at boot time and can
 only be changed by placing an appropriate entry in /boot/loader.conf and
 rebooting.
 
 If a large number of processes need to be run by a single user,
 kern.maxprocperuid should also be modified. Its maximum value should be
 one less than the kern.maxproc value because one system program,
 init(8), must always be running. For more information about setting
 tunables see the loader.conf(5) manual page.
 
 To make a sysctl change permanent place the proper value
 in /etc/sysctl.conf. More information about system tuning with sysctl(8)
 can be found at the Tuning with sysctl section of the Handbook.
 
 
 
 I'm not sure about the veracity of the "kern.maxprocperuid should be one
 less than kern.maxproc" statement. Does anyone know about this?
 
 
From minimarmot at gmail.com  Mon Jul 14 10:40:05 2008
From: minimarmot at gmail.com (Ben Kaduk)
Date: Mon Jul 14 10:40:11 2008
Subject: docs/125587: FAQ entry 5.13 -- adjustion is not an English word;
	tunable?
Message-ID: <200807141040.m6EAe4X9010678@freefall.freebsd.org>

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

From: "Ben Kaduk" <minimarmot@gmail.com>
To: "Mike Small" <smallm@panix.com>
Cc: freebsd-gnats-submit@freebsd.org
Subject: Re: docs/125587: FAQ entry 5.13 -- adjustion is not an English word; tunable?
Date: Mon, 14 Jul 2008 06:11:12 -0400

 [sigh, hit reply instead of reply-all; sorry Mike]
 
 On Sun, Jul 13, 2008 at 11:16 PM, Mike Small <smallm@panix.com> wrote:
 >
 >>Number:         125587
 >>Category:       docs
 >>Synopsis:       FAQ entry 5.13 -- adjustion is not an English word; tunable?
 >>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 Jul 14 03:20:01 UTC 2008
 >>Closed-Date:
 >>Last-Modified:
 >>Originator:     Mike Small
 >>Release:        7.0-RELEASE
 >>Organization:
 >>Environment:
 > FreeBSD rex 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sun Feb 24 19:59:52 UTC 2008     root@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  i386
 >>Description:
 > First of all, the second sentence in paragraph three of FAQ entry 5.13 uses the word "adjustion".  I don't believe this is a word in English.  Probably the word "adjustment" would be more suitable.
 >
 > Secondly, the same paragraph also uses the word "tunable" as a noun.  Is this a term people use in BSD?  I mean, it's clear what's meant from the context, but using "variable" or "sysctl variable", as is done in the first paragraph, seems clearer and less strange to me.
 >
 > Lastly, the word "in" is repeated: "If this tunable needs adjustion it needs to be defined in in /boot/loader.conf"
 
 
 
 You are correct -- `adjustion' should be ``adjustment'', and the
 doubled `in' should be corrected.
 
 However, `tunable' is a technical term in this context, referring to
 a kernel variable that can be set at boot time but not changed
 after the system is running -- this particular one resizes several
 static kernel data structures.
 
 Thanks for pointing these out!
 
 -Ben Kaduk
From bugmaster at FreeBSD.org  Mon Jul 14 11:06:09 2008
From: bugmaster at FreeBSD.org (FreeBSD bugmaster)
Date: Mon Jul 14 11:06:42 2008
Subject: Current unassigned doc problem reports
Message-ID: <200807141106.m6EB68K3013424@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/107432  doc        Handbook's default partitioning schema is out-of-date
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/121721  doc        telnetd(8) not describing -X authentication types
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/123255  doc        mistake in ng_bpf(4) manpage
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 docs/124949  doc        Discrepancy between handbook and example hosts file fo
o www/125092   doc        [patch] Addition to AMD64 supported platforms: Tyan Ti
o docs/125253  doc        [patch] jail(2) does not mention about possible error 
p docs/125535  doc        Errors in ahc(4) man page
p docs/125546  doc        [patch] ktrace(2) contains outdated struct ktr_header
o docs/125581  doc        In manpages on i386, there are two same name files. ma
o docs/125587  doc        FAQ entry 5.13 -- adjustion is not an English word; tu

137 problems total.

From manolis at FreeBSD.org  Mon Jul 14 11:12:32 2008
From: manolis at FreeBSD.org (manolis@FreeBSD.org)
Date: Mon Jul 14 11:12:38 2008
Subject: docs/125587: FAQ entry 5.13 -- adjustion is not an English word;
	tunable?
Message-ID: <200807141112.m6EBCVFv018008@freefall.freebsd.org>

Synopsis: FAQ entry 5.13 -- adjustion is not an English word; tunable?

Responsible-Changed-From-To: freebsd-doc->manolis
Responsible-Changed-By: manolis
Responsible-Changed-When: Mon Jul 14 11:11:52 UTC 2008
Responsible-Changed-Why: 
I will handle this

http://www.freebsd.org/cgi/query-pr.cgi?pr=125587
From trhodes at FreeBSD.org  Mon Jul 14 13:50:20 2008
From: trhodes at FreeBSD.org (trhodes@FreeBSD.org)
Date: Mon Jul 14 13:50:27 2008
Subject: docs/121721: telnetd(8) not describing -X authentication types
Message-ID: <200807141350.m6EDoK0Q033196@freefall.freebsd.org>

Synopsis: telnetd(8) not describing -X authentication types

Responsible-Changed-From-To: freebsd-doc->trhodes
Responsible-Changed-By: trhodes
Responsible-Changed-When: Mon Jul 14 13:49:20 UTC 2008
Responsible-Changed-Why: 
Take - I have a patch but, having spent time away from FreeBSD,
want to get some mdoc(7) review first.  Thanks Jeremy!

http://www.freebsd.org/cgi/query-pr.cgi?pr=121721
From peter at taronga.com  Tue Jul 15 01:23:51 2008
From: peter at taronga.com (Peter da Silva)
Date: Tue Jul 15 01:24:19 2008
Subject: The origin of the "#!" hack and selecting the shell
Message-ID: <3046E1F6-F847-4A6E-953F-7FDD6F50CBE9@taronga.com>

In <url:http://www.freebsd.org/doc/en/books/handbook/linuxemu- 
advanced.html> I read:

"Later, a hack was made for sh(1) to examine the first two  
characters, and if they were :\n, then it invoked the csh(1) shell  
instead (we believe SCO first made this hack)."

I'm pretty sure that nobody ever used ":\n" to indicate the C shell.

This hack originated at Berkeley, when the current version of UNIX  
was still V6. Before the Berkeley psh (Pascal shell) and csh (C  
shell) were developed, there wasn't any need for these hacks... there  
was only one shell and it was /bin/sh.

The V6 shell used the ":" (label) command for comments, while csh  
used "#". The first character of the file was checked by csh(1) and  
if it was a pound sign it used csh to run the script, otherwise it  
defaulted to the bourne shell. The "#!" hack (treating the string  
"#!" as a 16-bit magic number) came later, and was derived from this  
hack.

At one point a Comp Center admin (I won't mention who) went through  
all the shell scripts on all the Comp Center machines and made them  
start with a copyright notice that looked something like "# Copyright  
(C) YYYY Regents of the University of California" which had the  
effect of breaking all the scripts for anyone who was using the C shell.

Anyway, this was all happening in 1978 and 1979, and the first Xenix  
ports didn't start sneaking out until 1982, so it's unlikely that SCO  
had done anything like this first. :)
From mjguzik at gmail.com  Tue Jul 15 09:40:04 2008
From: mjguzik at gmail.com (Mateusz Guzik)
Date: Tue Jul 15 09:40:20 2008
Subject: docs/125630: [patch] modstat(2) contains outdated union modspecific
Message-ID: <200807150937.m6F9b2IW069908@www.freebsd.org>


>Number:         125630
>Category:       docs
>Synopsis:       [patch] modstat(2) contains outdated union modspecific
>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 Jul 15 09:40:03 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Mateusz Guzik
>Release:        8.0-CURRENT
>Organization:
>Environment:
FreeBSD eternal 8.0-CURRENT FreeBSD 8.0-CURRENT #17: Tue Jul 15 02:29:03 CEST 2008     f@eternal:/usr/obj/usr/src/sys/ETERNAL  i386

>Description:
modstat(2):
typedef union modspecific {
             int         intval;
             u_int       u_intval;
             long        longval;
             u_long      u_longval;
     } modspecific_t;

/usr/include/sys/module.h:
typedef union modspecific {
        int     intval;
        u_int   uintval;
        long    longval;
        u_long  ulongval;
} modspecific_t;
>How-To-Repeat:

>Fix:


Patch attached with submission follows:

--- lib/libc/sys/modstat.2.orig	2008-07-15 11:29:21.000000000 +0200
+++ lib/libc/sys/modstat.2	2008-07-15 11:31:34.000000000 +0200
@@ -53,13 +53,13 @@
 	int         id;
 	modspecific_t data;
 };
 typedef union modspecific {
 	int         intval;
-	u_int       u_intval;
+	u_int       uintval;
 	long        longval;
-	u_long      u_longval;
+	u_long      ulongval;
 } modspecific_t;
 .Ed
 .Pp
 .Bl -tag -width XXXaddress
 .It version


>Release-Note:
>Audit-Trail:
>Unformatted:
From danger at FreeBSD.org  Tue Jul 15 10:07:20 2008
From: danger at FreeBSD.org (danger@FreeBSD.org)
Date: Tue Jul 15 10:07:27 2008
Subject: docs/125630: [patch] modstat(2) contains outdated union
	modspecific
Message-ID: <200807151007.m6FA7Kpb072724@freefall.freebsd.org>

Synopsis: [patch] modstat(2) contains outdated union modspecific

Responsible-Changed-From-To: freebsd-doc->danger
Responsible-Changed-By: danger
Responsible-Changed-When: Tue Jul 15 10:07:10 UTC 2008
Responsible-Changed-Why: 
Take

http://www.freebsd.org/cgi/query-pr.cgi?pr=125630
From trhodes at FreeBSD.org  Tue Jul 15 13:00:11 2008
From: trhodes at FreeBSD.org (Tom Rhodes)
Date: Tue Jul 15 13:00:17 2008
Subject: docs/107432: Handbook's default partitioning schema is
 out-of-date
Message-ID: <200807151300.m6FD0B8K089077@freefall.freebsd.org>

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

From: Tom Rhodes <trhodes@FreeBSD.org>
To: bug-followup@FreeBSD.org, phoemix@harmless.hu
Cc:  
Subject: Re: docs/107432: Handbook's default partitioning schema is
 out-of-date
Date: Tue, 15 Jul 2008 08:57:41 -0400

 Hi,
 
 > The handbook's default partitioning scheme looks like this:
 > a 100MB /
 > b 2-3x RAM swap
 > d 50MB /var
 > e rest /usr
 
 From the page:
 http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/install-steps.html
 
 It appears that / was upped to 512MB, /var is 256MB to 1024MB,
 and /usr having the rest, noting at least 2GB.
 
 This PR should probably be closed.  I'm going to give it a few
 days to see if any follow ups come in, otherwise, I'll close it.
 
 Thanks,
 -- 
 Tom Rhodes
From phoemix at harmless.hu  Tue Jul 15 13:50:07 2008
From: phoemix at harmless.hu (CZUCZY Gergely)
Date: Tue Jul 15 13:50:12 2008
Subject: docs/107432: Handbook's default partitioning schema is
 out-of-date
Message-ID: <200807151350.m6FDo6Uw093882@freefall.freebsd.org>

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

From: CZUCZY Gergely <phoemix@harmless.hu>
To: Tom Rhodes <trhodes@FreeBSD.org>
Cc: bug-followup@FreeBSD.org, phoemix@harmless.hu
Subject: Re: docs/107432: Handbook's default partitioning schema is
 out-of-date
Date: Tue, 15 Jul 2008 15:31:11 +0200

 --Sig_/G3luZDzrxJsxeNG_MvZi3Px
 Content-Type: text/plain; charset=US-ASCII
 Content-Transfer-Encoding: quoted-printable
 
 Hello,
 
 Yes, I agree. The can be considered solved by this update.
 
 On Tue, 15 Jul 2008 08:57:41 -0400
 Tom Rhodes <trhodes@FreeBSD.org> wrote:
 
 > Hi,
 >=20
 > > The handbook's default partitioning scheme looks like this:
 > > a 100MB /
 > > b 2-3x RAM swap
 > > d 50MB /var
 > > e rest /usr
 >=20
 > From the page:
 > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/install-steps.h=
 tml
 >=20
 > It appears that / was upped to 512MB, /var is 256MB to 1024MB,
 > and /usr having the rest, noting at least 2GB.
 >=20
 > This PR should probably be closed.  I'm going to give it a few
 > days to see if any follow ups come in, otherwise, I'll close it.
 >=20
 > Thanks,
 
 
 --=20
 Sincerely,
 
 Gergely CZUCZY
 Harmless Digital Bt
 mailto: gergely.czuczy@harmless.hu
 Tel: +36-30-9702963
 
 --Sig_/G3luZDzrxJsxeNG_MvZi3Px
 Content-Type: application/pgp-signature; name=signature.asc
 Content-Disposition: attachment; filename=signature.asc
 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v2.0.3 (FreeBSD)
 
 iD8DBQFIfKahzrC0WyuMkpsRAqqiAKCbXxolFDLvOgTQnBg1jEQNrlJSIACgsVKU
 Nbl3THXxJ4P2JLnr+1tMJdA=
 =w3+0
 -----END PGP SIGNATURE-----
 
 --Sig_/G3luZDzrxJsxeNG_MvZi3Px--
From trhodes at FreeBSD.org  Tue Jul 15 14:03:03 2008
From: trhodes at FreeBSD.org (trhodes@FreeBSD.org)
Date: Tue Jul 15 14:03:09 2008
Subject: docs/107432: Handbook's default partitioning schema is
	out-of-date
Message-ID: <200807151403.m6FE32tU094390@freefall.freebsd.org>

Synopsis: Handbook's default partitioning schema is out-of-date

State-Changed-From-To: open->closed
State-Changed-By: trhodes
State-Changed-When: Tue Jul 15 14:01:49 UTC 2008
State-Changed-Why: 
Close this PR, the handbook was previously updated and
submitter believes the issue has been solved.


Responsible-Changed-From-To: freebsd-doc->trhodes
Responsible-Changed-By: trhodes
Responsible-Changed-When: Tue Jul 15 14:01:49 UTC 2008
Responsible-Changed-Why: 
Over to me, following.

http://www.freebsd.org/cgi/query-pr.cgi?pr=107432
From mjguzik at gmail.com  Tue Jul 15 14:40:04 2008
From: mjguzik at gmail.com (Mateusz Guzik)
Date: Tue Jul 15 14:40:15 2008
Subject: docs/125639: [patch] kldunloadf(2) does not mention about possible
	error EINVAL
Message-ID: <200807151438.m6FEc1XC071948@www.freebsd.org>


>Number:         125639
>Category:       docs
>Synopsis:       [patch] kldunloadf(2) does not mention about possible error EINVAL
>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 Jul 15 14:40:04 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Mateusz Guzik
>Release:        8.0-CURRENT
>Organization:
>Environment:
FreeBSD eternal 8.0-CURRENT FreeBSD 8.0-CURRENT #18: Tue Jul 15 15:35:46 CEST 2008     f@eternal:/usr/obj/usr/src/sys/ETERNAL  i386

>Description:
Function kldunloadf performs the following check before calling kern_kldunload:
 if (uap->flags != LINKER_UNLOAD_NORMAL &&
            uap->flags != LINKER_UNLOAD_FORCE)
                return (EINVAL);

But this return value is not documented.
>How-To-Repeat:

>Fix:


Patch attached with submission follows:

--- lib/libc/sys/kldunload.2.orig	2008-07-15 03:11:29.000000000 +0200
+++ lib/libc/sys/kldunload.2	2008-07-15 03:21:15.000000000 +0200
@@ -67,10 +67,13 @@
 You do not have access to unlink the file from the kernel.
 .It Bq Er ENOENT
 The file was not found.
 .It Bq Er EBUSY
 You attempted to unload a file linked by the kernel.
+.It Bq Er EINVAL
+.Fn kldunloadf
+was called with invalid flags.
 .El
 .Sh SEE ALSO
 .Xr kldfind 2 ,
 .Xr kldfirstmod 2 ,
 .Xr kldload 2 ,


>Release-Note:
>Audit-Trail:
>Unformatted:
From keramida at FreeBSD.org  Thu Jul 17 13:50:01 2008
From: keramida at FreeBSD.org (Giorgos Keramidas)
Date: Thu Jul 17 13:50:08 2008
Subject: docs/125717: minor wpa_supplicant.conf buglet
Message-ID: <87ej5s1v9t.fsf@kobe.laptop>


>Number:         125717
>Category:       docs
>Synopsis:       minor wpa_supplicant.conf buglet
>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 Jul 17 13:50:01 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Giorgos Keramidas
>Release:        FreeBSD 8.0-CURRENT i386
>Organization:
<organization of PR author (multiple lines)>
>Environment:
System: FreeBSD kobe 8.0-CURRENT FreeBSD 8.0-CURRENT #0: \
Tue Jul 8 09:10:21 EEST 2008 build@kobe:/home/build/obj/home/build/src/sys/KOBE i386

>Description:

The man page for wpa_supplicant.conf incorrectly states ap_scan values
other than 1 are for other operating systems.  When ndiswrapper is used,
it may be useful to set ap_scan=2.

>How-To-Repeat:
>Fix:

I'll handle this.
>Release-Note:
>Audit-Trail:
>Unformatted:
From jhb at freebsd.org  Thu Jul 17 14:25:13 2008
From: jhb at freebsd.org (John Baldwin)
Date: Thu Jul 17 14:25:20 2008
Subject: docs/125581: In manpages on i386,
	there are two same name files. man4/i386/ichwd.4 & man4/ichwd.4.
In-Reply-To: <20080713183931.8958A2843F@kcesx30.koganemaru.co.jp>
References: <20080713183931.8958A2843F@kcesx30.koganemaru.co.jp>
Message-ID: <200807170913.25138.jhb@freebsd.org>

On Sunday 13 July 2008 02:39:31 pm n-kogane@syd.odn.ne.jp wrote:
> 
> >Number:         125581
> >Category:       docs
> >Synopsis:       In manpages on i386, there are two same name files. 
man4/i386/ichwd.4 & man4/ichwd.4.
> >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 Jul 13 19:40:06 UTC 2008
> >Closed-Date:
> >Last-Modified:
> >Originator:     Nobuyuki Koganemaru
> >Release:        FreeBSD 7.0-RELEASE i386, FreeBSD 8.0-CURRENT i386.
> >Organization:
> KOGANEMARU Computer Engineering Service Corporation.
> >Environment:
> System: FreeBSD kcesx37.koganemaru.co.jp 7.0-RELEASE FreeBSD 7.0-RELEASE #0: 
Sun Feb 24 19:59:52 UTC 2008 
root@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386
> 
> 
> >Description:
> 	In 7.0-RELEASE, 8.0-CURRENT manpages on i386,
> 	there are two same name files.
> 	man4/i386/ichwd.4 and man4/ichwd.4.
> 	Which one is correct?	
> >How-To-Repeat:
> 	please check manpages.
> >Fix:
> 	I do not known. 

It looks like des@ wrote both and didn't notice he'd already written the first 
one in man4.i386 when he wrote the second one.  I think the one in man4.i386 
can just be removed now.

-- 
John Baldwin
From jhb at freebsd.org  Thu Jul 17 14:30:07 2008
From: jhb at freebsd.org (John Baldwin)
Date: Thu Jul 17 14:30:12 2008
Subject: docs/125581: In manpages on i386,
	there are two same name files. man4/i386/ichwd.4 & man4/ichwd.4.
Message-ID: <200807171430.m6HEU6mq005189@freefall.freebsd.org>

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

From: John Baldwin <jhb@freebsd.org>
To: freebsd-doc@freebsd.org, n-kogane@syd.odn.ne.jp
Cc: FreeBSD-gnats-submit@freebsd.org, des@freebsd.org
Subject: Re: docs/125581: In manpages on i386, there are two same name files. man4/i386/ichwd.4 & man4/ichwd.4.
Date: Thu, 17 Jul 2008 09:13:24 -0400

 On Sunday 13 July 2008 02:39:31 pm n-kogane@syd.odn.ne.jp wrote:
 > 
 > >Number:         125581
 > >Category:       docs
 > >Synopsis:       In manpages on i386, there are two same name files. 
 man4/i386/ichwd.4 & man4/ichwd.4.
 > >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 Jul 13 19:40:06 UTC 2008
 > >Closed-Date:
 > >Last-Modified:
 > >Originator:     Nobuyuki Koganemaru
 > >Release:        FreeBSD 7.0-RELEASE i386, FreeBSD 8.0-CURRENT i386.
 > >Organization:
 > KOGANEMARU Computer Engineering Service Corporation.
 > >Environment:
 > System: FreeBSD kcesx37.koganemaru.co.jp 7.0-RELEASE FreeBSD 7.0-RELEASE #0: 
 Sun Feb 24 19:59:52 UTC 2008 
 root@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386
 > 
 > 
 > >Description:
 > 	In 7.0-RELEASE, 8.0-CURRENT manpages on i386,
 > 	there are two same name files.
 > 	man4/i386/ichwd.4 and man4/ichwd.4.
 > 	Which one is correct?	
 > >How-To-Repeat:
 > 	please check manpages.
 > >Fix:
 > 	I do not known. 
 
 It looks like des@ wrote both and didn't notice he'd already written the first 
 one in man4.i386 when he wrote the second one.  I think the one in man4.i386 
 can just be removed now.
 
 -- 
 John Baldwin
From jgsinowitz at gmail.com  Thu Jul 17 18:47:16 2008
From: jgsinowitz at gmail.com (Jonah Sinowitz)
Date: Thu Jul 17 18:47:23 2008
Subject: Chapter 23
Message-ID: <eb1e531d0807171122u44fdc6fcha6e01d00d152d7cd@mail.gmail.com>

Dear freebsd-doc@freebsd.org,
I use and enjoy the Handbook a great deal.
I have a question about Chapter 23, "The Cutting Edge".
I'm wondering why the issues covered in that chapter are not covered earlier
in the Handbook. I'm new to FreeBSD, but these seem like very basic and
useful , which should be learned at the very beginning of one's FreeBSD
journey.
Sincerely,
Jonah Sinowitz
From jgsinowitz at gmail.com  Thu Jul 17 19:22:26 2008
From: jgsinowitz at gmail.com (Jonah Sinowitz)
Date: Thu Jul 17 19:22:33 2008
Subject: Chapter 23
In-Reply-To: <487F9926.2020703@gmail.com>
References: <eb1e531d0807171122u44fdc6fcha6e01d00d152d7cd@mail.gmail.com>
	<487F9926.2020703@gmail.com>
Message-ID: <eb1e531d0807171222y11af328cx9a4b76f36b3f6c6b@mail.gmail.com>

Dear Manolis,

Thanks for the quick response.

In the introductory course I took, we did *exactly *as you said: we
downloaded the release CD and then worked through  the equivalent of the
first few chapters of the Handbook. We then moved very very quickly to the
"Common Tasks" section of the Handbook, "Chapter 8", and configured the
kernel.
After this experience, my thought was -- *if *"Configuring the FreeBSD
Kernel" is a common task, so are many of those tasks listed in "The Cutting
Edge".

Does this make sense?

Best,
Jonah
On Thu, Jul 17, 2008 at 3:10 PM, Manolis Kiagias <sonic2000gr@gmail.com>
wrote:

>  Jonah Sinowitz wrote:
>
>> Dear freebsd-doc@freebsd.org,
>> I use and enjoy the Handbook a great deal.
>> I have a question about Chapter 23, "The Cutting Edge".
>> I'm wondering why the issues covered in that chapter are not covered
>> earlier
>> in the Handbook. I'm new to FreeBSD, but these seem like very basic and
>> useful , which should be learned at the very beginning of one's FreeBSD
>> journey.
>> Sincerely,
>> Jonah Sinowitz
>>
>>
>
>
> Glad you find the information useful!
> Chapter 23 refers to concepts that beginners usually will not grasp - and
> at that point they possibly don't care. Chapter 23 belongs to the
> "administration" part of the handbook.
> Most people start their FreeBSD journey by downloading a -RELEASE CD and
> then reading the first few chapters of the handbook, articles and tutorials
> and possibly other printed books.
>
> At this point, this kind of info may be confusing: What could the terms
> current, stable, source, kernel, buildworld, mergemaster mean for a
> beginner? Not much probably, as he is simply concentrated on getting the
> system up and running the way he wants it. Later on, after earning some
> experience, he can get to this chapter and decide for himself if he wishes
> to track current or stable and getting deeper knowledge on the FreeBSD
> development model as well.
>
> And you don't have to read a book from cover to cover, in  sequence. You
> can always jump around.  I do it all the time ;)
>
From sonic2000gr at gmail.com  Thu Jul 17 19:39:30 2008
From: sonic2000gr at gmail.com (Manolis Kiagias)
Date: Thu Jul 17 19:39:37 2008
Subject: Chapter 23
In-Reply-To: <eb1e531d0807171122u44fdc6fcha6e01d00d152d7cd@mail.gmail.com>
References: <eb1e531d0807171122u44fdc6fcha6e01d00d152d7cd@mail.gmail.com>
Message-ID: <487F9926.2020703@gmail.com>

Jonah Sinowitz wrote:
> Dear freebsd-doc@freebsd.org,
> I use and enjoy the Handbook a great deal.
> I have a question about Chapter 23, "The Cutting Edge".
> I'm wondering why the issues covered in that chapter are not covered earlier
> in the Handbook. I'm new to FreeBSD, but these seem like very basic and
> useful , which should be learned at the very beginning of one's FreeBSD
> journey.
> Sincerely,
> Jonah Sinowitz
>   


Glad you find the information useful!
Chapter 23 refers to concepts that beginners usually will not grasp - 
and at that point they possibly don't care. Chapter 23 belongs to the 
"administration" part of the handbook.
Most people start their FreeBSD journey by downloading a -RELEASE CD and 
then reading the first few chapters of the handbook, articles and 
tutorials and possibly other printed books.

At this point, this kind of info may be confusing: What could the terms 
current, stable, source, kernel, buildworld, mergemaster mean for a 
beginner? Not much probably, as he is simply concentrated on getting the 
system up and running the way he wants it. Later on, after earning some 
experience, he can get to this chapter and decide for himself if he 
wishes to track current or stable and getting deeper knowledge on the 
FreeBSD development model as well.

And you don't have to read a book from cover to cover, in  sequence. You 
can always jump around.  I do it all the time ;)
From sonic2000gr at gmail.com  Thu Jul 17 19:43:24 2008
From: sonic2000gr at gmail.com (Manolis Kiagias)
Date: Thu Jul 17 19:43:31 2008
Subject: Chapter 23
In-Reply-To: <eb1e531d0807171222y11af328cx9a4b76f36b3f6c6b@mail.gmail.com>
References: <eb1e531d0807171122u44fdc6fcha6e01d00d152d7cd@mail.gmail.com>	
	<487F9926.2020703@gmail.com>
	<eb1e531d0807171222y11af328cx9a4b76f36b3f6c6b@mail.gmail.com>
Message-ID: <487FA0D4.60405@gmail.com>

Jonah Sinowitz wrote:
> Dear Manolis,
>  
> Thanks for the quick response.
>  
> In the introductory course I took, we did *exactly *as you said: we 
> downloaded the release CD and then worked through  the equivalent of 
> the first few chapters of the Handbook. We then moved very very 
> quickly to the "Common Tasks" section of the Handbook, "Chapter 8", 
> and configured the kernel.
> After this experience, my thought was -- /if /"Configuring the FreeBSD 
> Kernel" is a common task, so are many of those tasks listed in "The 
> Cutting Edge".   
>  
> Does this make sense?
>  
> Best,
> Jonah

Well, it depends on the audience.

Many people choose to stay with -RELEASE (especially on servers), others 
run -STABLE on their desktops or when -RELEASE has a problem with their 
hardware.
People who are actively developing (low level) stuff usually run 
CURRENT. I certainly know of people who compile CURRENT daily...
Creating a custom kernel is a relatively easy task, once you grasp the 
basics, but compiling the rest of the system is something that a lot of 
people may never need. Enthusiasts will do it anyway, just to learn how :)
I suggest you give -STABLE a try if you are so inclined, it is a good 
learning experience.
From dan at obluda.cz  Fri Jul 18 12:30:04 2008
From: dan at obluda.cz (Dan Lukes)
Date: Fri Jul 18 12:30:14 2008
Subject: docs/125746: man 2 socket ERRORS section incomplete
Message-ID: <200807181224.m6ICONV2024841@kulesh.obluda.cz>


>Number:         125746
>Category:       docs
>Synopsis:       man 2 socket ERRORS section incomplete
>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 Jul 18 12:30:03 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Dan Lukes
>Release:        FreeBSD 6.3-STABLE i386
>Organization:
Obludarium
>Environment:
src/lib/libc/sys/socket.2,v 1.30 2004/07/02 23:52:13 ru

>Description:
	socket(2) may return EPERM also, for example, when SOCK_RAW socket type requested by non-superuser

	The EPERM return code is not mentioned in ERRORS section of manual page


>How-To-Repeat:
>Fix:

	Add the notice about the EPERM in ERROR section of socket(2) manual page - something like:

EPERM  User has insufficient privileges to carry out requested operation.

>Release-Note:
>Audit-Trail:
>Unformatted:
From dan at obluda.cz  Fri Jul 18 15:30:02 2008
From: dan at obluda.cz (Dan Lukes)
Date: Fri Jul 18 15:30:09 2008
Subject: docs/125751: man 3 pthread_getschedparam section ERRORS incomplete
Message-ID: <200807181525.m6IFPk4Z025333@kulesh.obluda.cz>


>Number:         125751
>Category:       docs
>Synopsis:       man 3 pthread_getschedparam section ERRORS incomplete
>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 Jul 18 15:30:01 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Dan Lukes
>Release:        FreeBSD 6.3-STABLE i386
>Organization:
Obludarium
>Environment:
src/share/man/man3/pthread_schedparam.3,v 1.9.8.1 2006/10/20 18:59:44 ru

>Description:
    The function

int pthread_getschedparam(pthread_t thread, int *policy, struct sched_param *param);

will return EINVAL in the case the policy or param is NULL

It apply to al three implementations:
     Reentrant C Library (libc_r, -lc_r)
     POSIX Threads Library (libpthread, -lpthread)
     1:1 Threading Library (libthr, -lthr)

    Unfortunately, the manual page mention the ESRCH as the only error code fur such function.

>How-To-Repeat:
>Fix:

	Add the EINVAL error code to ERRORS section, pthread_getschedparam subsection of manual page



>Release-Note:
>Audit-Trail:
>Unformatted:
From dan at obluda.cz  Fri Jul 18 15:50:04 2008
From: dan at obluda.cz (Dan Lukes)
Date: Fri Jul 18 15:50:14 2008
Subject: docs/125751: man 3 pthread_getschedparam section ERRORS
	incomplete
Message-ID: <200807181550.m6IFo4Ou073365@freefall.freebsd.org>

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

From: Dan Lukes <dan@obluda.cz>
To: bug-followup@FreeBSD.org
Cc:  
Subject: Re: docs/125751: man 3 pthread_getschedparam section ERRORS incomplete
Date: Fri, 18 Jul 2008 17:43:15 +0200

 Note, if the first param is NULL or something that can't be thread ID 
 then the function also return EINVAL.
 
 The ESRCH is returned for such ID's that are thread ID, but thread in 
 question doesn't exist
 
 					Dan
From keramida at FreeBSD.org  Fri Jul 18 20:03:15 2008
From: keramida at FreeBSD.org (keramida@FreeBSD.org)
Date: Fri Jul 18 20:03:21 2008
Subject: docs/125717: minor wpa_supplicant.conf(5) buglet
Message-ID: <200807182003.m6IK3Enp094769@freefall.freebsd.org>

Synopsis: minor wpa_supplicant.conf(5) buglet

Responsible-Changed-From-To: freebsd-doc->keramida
Responsible-Changed-By: keramida
Responsible-Changed-When: Fri Jul 18 20:03:03 UTC 2008
Responsible-Changed-Why: 
I'll handle this

http://www.freebsd.org/cgi/query-pr.cgi?pr=125717
From unga888 at yahoo.com  Sat Jul 19 07:35:35 2008
From: unga888 at yahoo.com (Unga)
Date: Sat Jul 19 11:20:24 2008
Subject: Pseudoterminals increase: compilation error
Message-ID: <351055.31765.qm@web57002.mail.re3.yahoo.com>

Hi all
 
I'm using FreeBSD 7.0.

As per FAQ,
http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/admin.html,
I tried to increase the number of ptys:
 "10.19.1
 Build and install a new kernel with the line in the
 configuration file:
 device pty N
 where N is the number of requested pseudoterminals."
 
I tried to recompile the kernel.  I have modified the
GENERIC as follows:
device          pty  64          # Pseudo-ttys (telnet etc)
 
This results a compilation error:
config: /usr/src/sys/i386/conf/GENERIC:268: syntax error
*** Error code 1
 
Kind Regards
Unga


      
From unga888 at yahoo.com  Sat Jul 19 15:30:01 2008
From: unga888 at yahoo.com (Unga)
Date: Sat Jul 19 15:30:08 2008
Subject: docs/125772: Increasing the number of ptys based on the FAQ results
	compilation error on FreeBSD 7.0
Message-ID: <200807191525.m6JFPlk9076817@www.freebsd.org>


>Number:         125772
>Category:       docs
>Synopsis:       Increasing the number of ptys based on the FAQ results compilation error on FreeBSD 7.0
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Jul 19 15:30:00 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Unga
>Release:        FreeBSD 7.0
>Organization:
>Environment:
>Description:
As per FAQ,
http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/admin.html,
I tried to increase the number of ptys:
 "10.19.1
 Build and install a new kernel with the line in the
 configuration file:
 device pty N
 where N is the number of requested pseudoterminals."
 
I tried to recompile the kernel.  I have modified the
GENERIC as follows:
device          pty  64          # Pseudo-ttys (telnet etc)
 
This results a compilation error:
config: /usr/src/sys/i386/conf/GENERIC:268: syntax error
*** Error code 1
>How-To-Repeat:

>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted:
From pgj at FreeBSD.org  Sat Jul 19 15:34:23 2008
From: pgj at FreeBSD.org (pgj@FreeBSD.org)
Date: Sat Jul 19 15:34:30 2008
Subject: docs/125772: Increasing the number of ptys based on the FAQ
	results compilation error on FreeBSD 7.0
Message-ID: <200807191534.m6JFYNn2034160@freefall.freebsd.org>

Synopsis: Increasing the number of ptys based on the FAQ results compilation error on FreeBSD 7.0

Responsible-Changed-From-To: freebsd-doc->pgj
Responsible-Changed-By: pgj
Responsible-Changed-When: Sat Jul 19 15:32:01 UTC 2008
Responsible-Changed-Why: 
I think it is my fault, so I should fix this.

http://www.freebsd.org/cgi/query-pr.cgi?pr=125772
From bugmaster at FreeBSD.org  Mon Jul 21 11:06:06 2008
From: bugmaster at FreeBSD.org (FreeBSD bugmaster)
Date: Mon Jul 21 11:06:35 2008
Subject: Current unassigned doc problem reports
Message-ID: <200807211106.m6LB651J030915@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/123255  doc        mistake in ng_bpf(4) manpage
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 docs/124949  doc        Discrepancy between handbook and example hosts file fo
o www/125092   doc        [patch] Addition to AMD64 supported platforms: Tyan Ti
o docs/125253  doc        [patch] jail(2) does not mention about possible error 
p docs/125535  doc        Errors in ahc(4) man page
p docs/125546  doc        [patch] ktrace(2) contains outdated struct ktr_header
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

137 problems total.

From pgj at FreeBSD.org  Mon Jul 21 19:06:49 2008
From: pgj at FreeBSD.org (Gabor PALI)
Date: Mon Jul 21 19:06:54 2008
Subject: A Whitespace-Only Patch for the FreeBSD FAQ
Message-ID: <4884D790.4090706@FreeBSD.org>

Hello,


I have a patch to create a pretty-printed FAQ.  I would like to ask you
to support or to deny my commit for making it to look like that.  I also
have a separate .diff (it is ~800K in size):

http://people.freebsd.org/~pgj/for_review/2008-07-20/book.sgml
http://people.freebsd.org/~pgj/for_review/2008-07-20/book.sgml.cvs.diff


Here are some statistics:

$ diffstat -w110 book.sgml.cvs.diff
 book.sgml |20009
++++++++++++++++++++++++++++++++++++++++++++++----------------------------------------------
 1 file changed, 10148 insertions(+), 9861 deletions(-)


Please, inspect this well, compose your ideas on the possible
enhancements, mistakes, styles.  I have an open intention to provide
useful indentation references for other documents and committers by
having a well-formed FAQ, that is why I am thinking it is so important.


Thank you for your attention and thank you for your time and answers in
advance.


:g
From sonic2000gr at gmail.com  Mon Jul 21 19:28:41 2008
From: sonic2000gr at gmail.com (Manolis Kiagias)
Date: Mon Jul 21 19:28:47 2008
Subject: A Whitespace-Only Patch for the FreeBSD FAQ
In-Reply-To: <4884D790.4090706@FreeBSD.org>
References: <4884D790.4090706@FreeBSD.org>
Message-ID: <4884E364.7060303@gmail.com>

Gabor PALI wrote:
> Hello,
>
>
> I have a patch to create a pretty-printed FAQ.  I would like to ask you
> to support or to deny my commit for making it to look like that.  I also
> have a separate .diff (it is ~800K in size):
>
> http://people.freebsd.org/~pgj/for_review/2008-07-20/book.sgml
> http://people.freebsd.org/~pgj/for_review/2008-07-20/book.sgml.cvs.diff
>
>
> Here are some statistics:
>
> $ diffstat -w110 book.sgml.cvs.diff
>  book.sgml |20009
> ++++++++++++++++++++++++++++++++++++++++++++++----------------------------------------------
>  1 file changed, 10148 insertions(+), 9861 deletions(-)
>
>
> Please, inspect this well, compose your ideas on the possible
> enhancements, mistakes, styles.  I have an open intention to provide
> useful indentation references for other documents and committers by
> having a well-formed FAQ, that is why I am thinking it is so important.
>
>   
+1

FWIW, I believe you should go on with this one. The idea of a well 
formed reference document will probably save us from future large 
whitespace commits anyway.
From tabthorpe at FreeBSD.org  Mon Jul 21 19:50:01 2008
From: tabthorpe at FreeBSD.org (Thomas Abthorpe)
Date: Mon Jul 21 19:50:07 2008
Subject: docs/125839: Add light bulb joke to funnies
Message-ID: <200807211940.m6LJevui069260@goodking.goodking.ca>


>Number:         125839
>Category:       docs
>Synopsis:       Add light bulb joke to funnies
>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 Jul 21 19:50:00 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Thomas Abthorpe
>Release:        FreeBSD 7.0-RELEASE-p2 i386
>Organization:
FreeBSD.GoodKing.Ca
>Environment:
System: FreeBSD goodking.goodking.ca 7.0-RELEASE-p2 FreeBSD 7.0-RELEASE-p2 #0: Wed Jun 18 07:33:20 UTC 2008 root@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386


>Description:
- Add light bulb joke to funnies

>How-To-Repeat:
>Fix:

Index: book.sgml
===================================================================
RCS file: /home/dcvs/doc/en_US.ISO8859-1/books/faq/book.sgml,v
retrieving revision 1.1004
diff -u -r1.1004 book.sgml
--- book.sgml	21 Jun 2008 12:24:43 -0000	1.1004
+++ book.sgml	21 Jul 2008 19:30:16 -0000
@@ -10592,6 +10592,9 @@
           <para>Fifty-seven to complain about the lights being out two
             weeks after the bulb has been changed.</para>
 
+	  <para>None.  *REAL* FreeBSD hackers are not afraid of the
+	    dark!</para>
+
           <para><emphasis>&a.nik; adds:</emphasis></para>
 
           <para><emphasis>I was laughing quite hard at
>Release-Note:
>Audit-Trail:
>Unformatted:
From pgj at FreeBSD.org  Mon Jul 21 20:03:39 2008
From: pgj at FreeBSD.org (pgj@FreeBSD.org)
Date: Mon Jul 21 20:03:45 2008
Subject: docs/125839: Add light bulb joke to funnies
Message-ID: <200807212003.m6LK3dHU081055@freefall.freebsd.org>

Synopsis: Add light bulb joke to funnies

Responsible-Changed-From-To: freebsd-doc->pgj
Responsible-Changed-By: pgj
Responsible-Changed-When: Mon Jul 21 20:02:41 UTC 2008
Responsible-Changed-Why: 
Come to me.

http://www.freebsd.org/cgi/query-pr.cgi?pr=125839
From jhb at freebsd.org  Mon Jul 21 20:56:06 2008
From: jhb at freebsd.org (John Baldwin)
Date: Mon Jul 21 20:56:21 2008
Subject: docs/125772: Increasing the number of ptys based on the FAQ
	results compilation error on FreeBSD 7.0
In-Reply-To: <200807191525.m6JFPlk9076817@www.freebsd.org>
References: <200807191525.m6JFPlk9076817@www.freebsd.org>
Message-ID: <200807211121.28730.jhb@freebsd.org>

On Saturday 19 July 2008 11:25:47 am Unga wrote:
> 
> >Number:         125772
> >Category:       docs
> >Synopsis:       Increasing the number of ptys based on the FAQ results 
compilation error on FreeBSD 7.0
> >Confidential:   no
> >Severity:       serious
> >Priority:       low
> >Responsible:    freebsd-doc
> >State:          open
> >Quarter:        
> >Keywords:       
> >Date-Required:
> >Class:          doc-bug
> >Submitter-Id:   current-users
> >Arrival-Date:   Sat Jul 19 15:30:00 UTC 2008
> >Closed-Date:
> >Last-Modified:
> >Originator:     Unga
> >Release:        FreeBSD 7.0
> >Organization:
> >Environment:
> >Description:
> As per FAQ,
> http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/admin.html,
> I tried to increase the number of ptys:
>  "10.19.1
>  Build and install a new kernel with the line in the
>  configuration file:
>  device pty N
>  where N is the number of requested pseudoterminals."
>  
> I tried to recompile the kernel.  I have modified the
> GENERIC as follows:
> device          pty  64          # Pseudo-ttys (telnet etc)
>  
> This results a compilation error:
> config: /usr/src/sys/i386/conf/GENERIC:268: syntax error
> *** Error code 1

Yeah, that approach (number in config file) hasn't been used since at least 
3.x.  The default on 7.0 is 512 pty's (vs 256 in 6.x).  Do you need more than 
that?

-- 
John Baldwin
From gavin at FreeBSD.org  Tue Jul 22 11:30:02 2008
From: gavin at FreeBSD.org (Gavin Atkinson)
Date: Tue Jul 22 11:30:08 2008
Subject: docs/125861: [patch] updates to developers handbook: l10n section
Message-ID: <200807221127.m6MBR1qO039097@buffy.york.ac.uk>


>Number:         125861
>Category:       docs
>Synopsis:       [patch] updates to developers handbook: l10n section
>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 Jul 22 11:30:01 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Gavin Atkinson
>Release:        FreeBSD 7.0-STABLE amd64
>Organization:
>Environment:
System: FreeBSD buffy.york.ac.uk 7.0-STABLE FreeBSD 7.0-STABLE #3: Fri Jun 20 09:21:51 UTC 2008 root@buffy.york.ac.uk:/usr/obj/usr/src/sys/GENERIC amd64

>Description:
	http://www.freebsd.org/doc/en/books/developers-handbook/l10n.html
gives information that hasn't been useful since FreeBSD 4.6, when the
library mentioned was merged into libc.  This information can safely be
removed, and does not need to be replaced with anything else.
>How-To-Repeat:
	N/A
>Fix:

--- devh-l10n.diff begins here ---
Index: doc/en_US.ISO8859-1/books/developers-handbook/l10n/chapter.sgml
===================================================================
RCS file: /home/dcvs/doc/en_US.ISO8859-1/books/developers-handbook/l10n/chapter.sgml,v
retrieving revision 1.10
diff -u -r1.10 chapter.sgml
--- doc/en_US.ISO8859-1/books/developers-handbook/l10n/chapter.sgml	28 Sep 2007 16:05:30 -0000	1.10
+++ doc/en_US.ISO8859-1/books/developers-handbook/l10n/chapter.sgml	22 Jul 2008 09:42:23 -0000
@@ -57,19 +57,6 @@
 	<para>Perl and Python have I18N and wide character handling
 	  libraries.  Please use them for I18N compliance.</para>
 
-	<para>In older FreeBSD versions,
-	  Perl may give warnings about not having a wide character locale
-	  installed on your system.  You can set the
-	  environment variable <envar>LD_PRELOAD</envar> to
-	  <filename>/usr/lib/libxpg4.so</filename> in your shell.</para>
-
-	<para>In <literal>sh</literal>-based shells:</para>
-
-	<programlisting><envar>LD_PRELOAD=/usr/lib/libxpg4.so</envar></programlisting>
-
-	<para>In <literal>C</literal>-based shells:</para>
-
-	<programlisting><envar>setenv LD_PRELOAD /usr/lib/libxpg4.so</envar></programlisting>
       </sect2>
     </sect1>
 </chapter>
--- devh-l10n.diff ends here ---


>Release-Note:
>Audit-Trail:
>Unformatted:
From raj at tetrain.com  Tue Jul 22 12:51:45 2008
From: raj at tetrain.com (Raj Jha)
Date: Tue Jul 22 12:51:53 2008
Subject: Joint Business Opportunity
Message-ID: <007301c8ebf5$89fdb6c0$9df92440$@com>

Dear Exhibitor FreeBSD Project,

 

I am the assistant to Mukul Mahajan, Managing Director of the open source IT
company "Tetra Information Services." We are currently attending an upcoming
event on Open Source - Linux World Expo to be held at The Moscone Center in
San Francisco August 4-7, 2008 booth no 1615#.

 

Mr. Mahajan would like to arrange a time to speak with you to see if there
is a possible opportunity to do a joint business. Please email or call to
let me know when you would be available to speak via telephone.

 

A brief overview of Tetra 

 

We are a 150 strong team, in Open Source IT Services since 1996, with
develop center based in New Delhi, India. Our services focus is development
on open source technology including LAMP, Java, and Plone. Expertise area in
Mail server applications, CRM, CMS and HelpDesk. With more than 200 active
clients, we are the largest player open source IT company in North India.  

 

For more details you can visit our website www.Tetrain.com or request for a
company brochure and Service profile presentation.

 

I look forward to hearing from you.

 

Warm Regards,

 

Rajendra Jha (Raj) 
International Marketing Manager

Tetra Information Services Pvt. Ltd. | Open Source Solutions & Linux
Services 
E- <mailto:raj@tetrain.com> raj@tetrain.com |  <http://www.tetrain.com/>
www.tetrain.com | Skype-rajgreece

T: +91-11-66604033/34/35/37 | F: +91-11-26225293 | M: +91-9818488764
Business Development | Marketing Strategies | Offshore Sales Development

 <http://www.tetrain.com/> logo

This message contains information intended solely for the addressee, which
is confidential or private in nature and subject to legal privilege. If you
are not the intended recipient, you may not peruse, use, disseminate,
distribute or copy this message or any file attached to this message. Any
such unauthorised use is prohibited and may be unlawful. If you have
received this message in error, please notify the sender immediately and
thereafter delete the original message from your machine.

P please consider the environment before printing this e-mail or its
attachment(s)

 

From remko at FreeBSD.org  Tue Jul 22 16:48:57 2008
From: remko at FreeBSD.org (remko@FreeBSD.org)
Date: Tue Jul 22 16:49:04 2008
Subject: docs/125861: [patch] updates to developers handbook: l10n
	section
Message-ID: <200807221648.m6MGmuMn024579@freefall.freebsd.org>

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

State-Changed-From-To: open->closed
State-Changed-By: remko
State-Changed-When: Tue Jul 22 16:48:56 UTC 2008
State-Changed-Why: 
Committed. Thanks!

http://www.freebsd.org/cgi/query-pr.cgi?pr=125861
From dfilter at FreeBSD.ORG  Tue Jul 22 16:50:04 2008
From: dfilter at FreeBSD.ORG (dfilter service)
Date: Tue Jul 22 16:50:15 2008
Subject: docs/125861: commit references a PR
Message-ID: <200807221650.m6MGo3Np024678@freefall.freebsd.org>

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

From: dfilter@FreeBSD.ORG (dfilter service)
To: bug-followup@FreeBSD.org
Cc:  
Subject: Re: docs/125861: commit references a PR
Date: Tue, 22 Jul 2008 16:46:47 +0000 (UTC)

 remko       2008-07-22 16:46:34 UTC
 
   FreeBSD doc repository
 
   Modified files:
     en_US.ISO8859-1/books/developers-handbook/l10n chapter.sgml 
   Log:
   Cleanup information that is no longer actual and does not need replacement.
   
   PR:             125861
   Submitted by:   gavin
   
   Revision  Changes    Path
   1.11      +0 -14     doc/en_US.ISO8859-1/books/developers-handbook/l10n/chapter.sgml
 _______________________________________________
 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 gavin at FreeBSD.org  Tue Jul 22 16:50:04 2008
From: gavin at FreeBSD.org (Gavin Atkinson)
Date: Tue Jul 22 16:50:15 2008
Subject: docs/125876: [patch] Committers-guide: wrong path for Core monthly
	reports
Message-ID: <200807221648.m6MGmbEC040443@buffy.york.ac.uk>


>Number:         125876
>Category:       docs
>Synopsis:       [patch] Committers-guide: wrong path for Core monthly reports
>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 Jul 22 16:50:04 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Gavin Atkinson
>Release:        FreeBSD 7.0-STABLE amd64
>Organization:
>Environment:
System: FreeBSD buffy.york.ac.uk 7.0-STABLE FreeBSD 7.0-STABLE #3: Fri Jun 20 09:21:51 UTC 2008 root@buffy.york.ac.uk:/usr/obj/usr/src/sys/GENERIC amd64

>Description:
	Core Team monthly reports aren't located where the committers-guide says they are.
>How-To-Repeat:
gavin@freefall:/home/gavin 1110% ls /home/core/public/monthly-report
ls: /home/core/public/monthly-report: No such file or directory

>Fix:

--- comm-guide-core.diff begins here ---
Index: doc/en_US.ISO8859-1/articles/committers-guide/article.sgml
===================================================================
RCS file: /home/dcvs/doc/en_US.ISO8859-1/articles/committers-guide/article.sgml,v
retrieving revision 1.275
diff -u -r1.275 article.sgml
--- doc/en_US.ISO8859-1/articles/committers-guide/article.sgml	20 Jun 2008 00:28:50 -0000	1.275
+++ doc/en_US.ISO8859-1/articles/committers-guide/article.sgml	22 Jul 2008 16:46:01 -0000
@@ -107,7 +107,7 @@
 
 	  <row>
 	    <entry><emphasis>Core Team monthly reports</emphasis></entry>
-	    <entry><filename>/home/core/public/monthly-report</filename>
+	    <entry><filename>/home/core/public/monthly-reports</filename>
 	      on the <hostid role="domainname">FreeBSD.org</hostid> cluster.
 	    </entry>
 	  </row>
--- comm-guide-core.diff ends here ---


>Release-Note:
>Audit-Trail:
>Unformatted:
From remko at FreeBSD.org  Tue Jul 22 17:05:52 2008
From: remko at FreeBSD.org (remko@FreeBSD.org)
Date: Tue Jul 22 17:06:10 2008
Subject: docs/125876: [patch] Committers-guide: wrong path for Core
	monthly reports
Message-ID: <200807221705.m6MH5pCa025351@freefall.freebsd.org>

Synopsis: [patch] Committers-guide: wrong path for Core monthly reports

State-Changed-From-To: open->closed
State-Changed-By: remko
State-Changed-When: Tue Jul 22 17:05:51 UTC 2008
State-Changed-Why: 
Committed. Thanks!

http://www.freebsd.org/cgi/query-pr.cgi?pr=125876
From dfilter at FreeBSD.ORG  Tue Jul 22 17:10:03 2008
From: dfilter at FreeBSD.ORG (dfilter service)
Date: Tue Jul 22 17:10:10 2008
Subject: docs/125876: commit references a PR
Message-ID: <200807221710.m6MHA3K2025443@freefall.freebsd.org>

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

From: dfilter@FreeBSD.ORG (dfilter service)
To: bug-followup@FreeBSD.org
Cc:  
Subject: Re: docs/125876: commit references a PR
Date: Tue, 22 Jul 2008 17:06:01 +0000 (UTC)

 remko       2008-07-22 17:05:47 UTC
 
   FreeBSD doc repository
 
   Modified files:
     en_US.ISO8859-1/articles/committers-guide article.sgml 
   Log:
   Correct the place where we can find the core archives.
   
   PR:             125876
   Submitted by:   gavin
   
   Revision  Changes    Path
   1.276     +1 -1      doc/en_US.ISO8859-1/articles/committers-guide/article.sgml
 _______________________________________________
 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 www at FreeBSD.org  Wed Jul 23 01:24:52 2008
From: www at FreeBSD.org (World Wide Web Owner)
Date: Wed Jul 23 01:24:58 2008
Subject: FreeBSD web build failed on www.freebsd.org
Message-ID: <200807230124.m6N1Op32045596@www.freebsd.org>

install -C  -o www -g wwwadm -m 444 /w/www/build/doc/en_US.ISO8859-1/books/handbook/../../../share/images/books/handbook/vinum/vinum-raid5-org.png /w/www/build/www/en/doc/en_US.ISO8859-1/books/handbook/vinum
/bin/mkdir -p /w/www/build/www/en/doc/en_US.ISO8859-1/books/handbook/vinum
install -C  -o www -g wwwadm -m 444 /w/www/build/doc/en_US.ISO8859-1/books/handbook/../../../share/images/books/handbook/vinum/vinum-simple-vol.png /w/www/build/www/en/doc/en_US.ISO8859-1/books/handbook/vinum
/bin/mkdir -p /w/www/build/www/en/doc/en_US.ISO8859-1/books/handbook/vinum
install -C  -o www -g wwwadm -m 444 /w/www/build/doc/en_US.ISO8859-1/books/handbook/../../../share/images/books/handbook/vinum/vinum-striped-vol.png /w/www/build/www/en/doc/en_US.ISO8859-1/books/handbook/vinum
/bin/mkdir -p /w/www/build/www/en/doc/en_US.ISO8859-1/books/handbook/vinum
install -C  -o www -g wwwadm -m 444 /w/www/build/doc/en_US.ISO8859-1/books/handbook/../../../share/images/books/handbook/vinum/vinum-striped.png /w/www/build/www/en/doc/en_US.ISO8859-1/books/handbook/vinum
/w/www/build/www/en/doc/en_US.ISO8859-1/books/handbook/handbook.html -> /w/www/build/www/en/doc/en_US.ISO8859-1/books/handbook/index.html
===> doc/books/pmake (install)
install -C  -o www -g wwwadm -m 444 $(/usr/bin/xargs < HTML.manifest) /w/www/build/www/en/doc/en_US.ISO8859-1/books/pmake
install -C  -o www -g wwwadm -m 444 docbook.css /w/www/build/www/en/doc/en_US.ISO8859-1/books/pmake
install -C  -o www -g wwwadm -m 444 book.html /w/www/build/www/en/doc/en_US.ISO8859-1/books/pmake
install -C  -o www -g wwwadm -m 444 docbook.css /w/www/build/www/en/doc/en_US.ISO8859-1/books/pmake
===> doc/books/porters-handbook (install)
install -C  -o www -g wwwadm -m 444 $(/usr/bin/xargs < HTML.manifest) /w/www/build/www/en/doc/en_US.ISO8859-1/books/porters-handbook
install -C  -o www -g wwwadm -m 444 docbook.css /w/www/build/www/en/doc/en_US.ISO8859-1/books/porters-handbook
install -C  -o www -g wwwadm -m 444 imagelib/callouts/1.png  /w/www/build/www/en/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts
install -C  -o www -g wwwadm -m 444 imagelib/callouts/2.png  /w/www/build/www/en/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts
install -C  -o www -g wwwadm -m 444 imagelib/callouts/3.png  /w/www/build/www/en/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts
install -C  -o www -g wwwadm -m 444 imagelib/callouts/4.png  /w/www/build/www/en/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts
install -C  -o www -g wwwadm -m 444 imagelib/callouts/5.png  /w/www/build/www/en/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts
install -C  -o www -g wwwadm -m 444 imagelib/callouts/6.png  /w/www/build/www/en/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts
install -C  -o www -g wwwadm -m 444 imagelib/callouts/7.png  /w/www/build/www/en/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts
install -C  -o www -g wwwadm -m 444 imagelib/callouts/8.png  /w/www/build/www/en/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts
install -C  -o www -g wwwadm -m 444 imagelib/callouts/9.png  /w/www/build/www/en/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts
install -C  -o www -g wwwadm -m 444 imagelib/callouts/10.png  /w/www/build/www/en/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts
install -C  -o www -g wwwadm -m 444 book.html /w/www/build/www/en/doc/en_US.ISO8859-1/books/porters-handbook
install -C  -o www -g wwwadm -m 444 docbook.css /w/www/build/www/en/doc/en_US.ISO8859-1/books/porters-handbook
install -C  -o www -g wwwadm -m 444 imagelib/callouts/1.png  /w/www/build/www/en/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts
install -C  -o www -g wwwadm -m 444 imagelib/callouts/2.png  /w/www/build/www/en/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts
install -C  -o www -g wwwadm -m 444 imagelib/callouts/3.png  /w/www/build/www/en/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts
install -C  -o www -g wwwadm -m 444 imagelib/callouts/4.png  /w/www/build/www/en/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts
install -C  -o www -g wwwadm -m 444 imagelib/callouts/5.png  /w/www/build/www/en/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts
install -C  -o www -g wwwadm -m 444 imagelib/callouts/6.png  /w/www/build/www/en/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts
install -C  -o www -g wwwadm -m 444 imagelib/callouts/7.png  /w/www/build/www/en/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts
install -C  -o www -g wwwadm -m 444 imagelib/callouts/8.png  /w/www/build/www/en/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts
install -C  -o www -g wwwadm -m 444 imagelib/callouts/9.png  /w/www/build/www/en/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts
install -C  -o www -g wwwadm -m 444 imagelib/callouts/10.png  /w/www/build/www/en/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts
/w/www/build/www/en/doc/faq -> /w/www/build/www/en/doc/en_US.ISO8859-1/books/faq
/w/www/build/www/en/doc/handbook -> /w/www/build/www/en/doc/en_US.ISO8859-1/books/handbook
/w/www/build/www/en/doc/en -> /w/www/build/www/en/doc/en_US.ISO8859-1
/usr/local/bin/jade:/w/www/build/doc/en_US.ISO8859-1/books/handbook/../../../share/pgpkeys/pgpkeys-developers.sgml:389:6:E: cannot find "pgollucci.key"; tried "/w/www/build/doc/en_US.ISO8859-1/books/handbook/../../../share/pgpkeys/pgollucci.key", "/w/www/build/doc/en_US.ISO8859-1/books/handbook/../../../share/images/books/handbook/pgollucci.key", "/usr/obj/w/www/build/doc/en_US.ISO8859-1/books/handbook/pgollucci.key"
/usr/local/bin/jade:/w/www/build/doc/en_US.ISO8859-1/books/handbook/../../../share/pgpkeys/pgpkeys-developers.sgml:390:11:E: end tag for "SECT2" which is not finished
*** Error code 1

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

Stop in /w/www/build/www/en.
      101.72 real        55.91 user        31.16 sys
From marcolz at stack.nl  Wed Jul 23 09:20:04 2008
From: marcolz at stack.nl (Marc Olzheim)
Date: Wed Jul 23 09:20:11 2008
Subject: docs/125896: [PATCH] arp manual and syntax synchronisation
Message-ID: <20080723091029.03DF6415B@toad.stack.nl>


>Number:         125896
>Category:       docs
>Synopsis:       [PATCH] arp manual and syntax synchronisation
>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:   Wed Jul 23 09:20:03 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Marc Olzheim
>Release:        FreeBSD 7.0-STABLE amd64
>Organization:
iphion b.v.
>Environment:
System: FreeBSD seven.dev.iphion.nl 7.0-STABLE FreeBSD 7.0-STABLE #1: Tue Jul 22 16:01:56 CEST 2008 root@seven.dev.iphion.nl:/usr/obj/usr/src/sys/SEVEN amd64


>Description:
	Although it makes no sense to do so, the most recent addition to
	arp allows for both the reject and the blackhole keywords to be
	set. Some kind of warning seems appropriate. Apart from that,
	the part of the manual describing the syntax of a file passed to
	arp -f is out of sync.
>How-To-Repeat:

>Fix:
	Patch is at:
	http://www.stack.nl/~marcolz/FreeBSD/arp.20080723.patch.txt
>Release-Note:
>Audit-Trail:
>Unformatted:
From bankofamericacrm at fnres.com  Wed Jul 23 16:32:53 2008
From: bankofamericacrm at fnres.com (Joel Hansen - Bank of America)
Date: Wed Jul 23 16:32:59 2008
Subject: Refinance Today
Message-ID: <033001c8ece2$1fcafd60$1110930a@rediv.int>

 
<https://lenderoffice.bankofamerica.com/ManagementCenter/uploads/BAC/Mar
keting%20Admins/images/spacer.gif> 	

Take advantage of lower rates before they rise again.

Refinance today.
		
 Bank of America -
Mortgage<https://lenderoffice.bankofamerica.com/ManagementCenter/uploads
/BAC/Marketing%20Admins/images/bac_mortgage_logo.gif> 	
 
<https://lenderoffice.bankofamerica.com/ManagementCenter/uploads/BAC/Mar
keting%20Admins/images/spacer.gif> 

 
<https://lenderoffice.bankofamerica.com/ManagementCenter/uploads/BAC/Mar
keting%20Admins/images/spacer.gif> 	Bank of America can help. 

There are several reasons to refinance, and saving money is at the top
of the list. If you're currently in an adjustable rate mortgage (ARM),
you can lock in a fixed rate mortgage before the fixed portion of your
ARM expires and/or rates go up. Or, if you currently have a fixed rate
mortgage at a higher rate, you can refinance at a lower fixed rate.   

Refinancing doesn't need to be complicated or confusing. I'll guide you
step-by-step through the process, answer all your questions, and help
you find the best home financing solution that is best to fit your
needs.

I appreciate your busines and value your referrals; so if you or someone
you know is ready to consider refinance possibilties, please contact me.
Credit and collateral subject to approval. Terms and conditions apply.
Some restrictions may apply. See Bank of America for details.  Programs,
rates, terms and conditions are subject to change without notice.
<https://lenderoffice.bankofamerica.com/ManagementCenter/uploads/BAC/Mar
keting%20Admins/images/spacer.gif> 	
 
<https://lenderoffice.bankofamerica.com/ManagementCenter/uploads/BAC/Mar
keting%20Admins/images/BalloonsSRL2801.jpg> 
 Contact
Me<https://lenderoffice.bankofamerica.com/ManagementCenter/uploads/BAC/M
arketing%20Admins/images/contactme.gif> 

 
<https://lenderoffice.bankofamerica.com/ManagementCenter/uploads/BAC/Mar
keting%20Admins/images/spacer.gif> 	Joel Hansen
Mortgage Loan Officer
Direct line: (517) 290-4754

Visit my Web site <http://mortgage.bankofamerica.com/joelhansen>
<https://lenderoffice.bankofamerica.com/ManagementCenter/uploads/BAC/Mar
keting%20Admins/images/spacer.gif> 	

<about:blank>  


  _____  

Opt-Out Instructions 
This is a promotional email from Bank of America. You can opt-out of
future promotional email, now or anytime in the future, by updating your
Email Preferences
<https://lenderoffice.bankofamerica.com/CRM_WEBSERVICE/unsubscribe.aspx?
Sponsor=BAC&messageId=575e97de-31a7-4f4f-9fbe-c706c451c94a> . 

Contact us about this email
Please do not reply to this e-mail with sensitive information, such as
an account number, PIN, password, or Online ID. The security and
confidentiality of your personal information is important to us. If you
have any questions, please either call the phone number on your account
statement or use the Contact Us <http://www.bankofamerica.com/contact/>
page, so we can properly verify your identity. 

Privacy and Security
Keeping your financial information secure is one of our most important
responsibilities. For an explanation of how we manage customer
information, please read our Privacy Policy
<http://www.bankofamerica.com/privacy/> . You can also learn how Bank of
America keeps your personal information secure
<http://www.bankofamerica.com/privacy/index.cfm?template=privacysecur_pr
event_fraud>  and how you can help protect yourself. 

Bank of America Email, 8th Floor, 101 South Tryon St., Charlotte, NC
28255 

Bank of America, N.A. Member FDIC. Equal Housing Lender
<http://www.bankofamerica.com/help/equalhousing.cfm/>  Equal Housing
Lender<https://lenderoffice.bankofamerica.com/ManagementCenter/Uploads/B
AC/Marketing%20Admins/images/bams-with-market_housing.jpg> 
? 2007 Bank of America Corporation. All rights reserved. 

This email was sent to doc@freebsd.org	 
From paymentunit at abbeypayingcentre.com  Wed Jul 23 18:56:07 2008
From: paymentunit at abbeypayingcentre.com (WESTERN UNION OFFICE)
Date: Wed Jul 23 18:56:13 2008
Subject: Western Union
Message-ID: <E1KLjVA-0008SY-RO@linux28.serve-dns.com>

WESTERN UNION MONEY TRANSFER
(Welcome to Western Union Send Money Worldwide)
ABBEY BANK LONDON ST BRANCH
ADDRESS: PLOT 1, SOUTHWARK BRIDGE, SE 19 HL UNITED KINGDOM.
TEL/FAX NUMBER: +44-208123-7265
REF NO: 250-153

Sir/Maddam,

There is an urgent issue today with the Western Union Money Transfer in the amount of $2.6M directed in cash credited to file KTU/ 9023118308/03, on your 

name as your elongated payment.

The INTERNATIONAL MONETARY FUND, (IMF) had contacted us for your Payment a couple of hours ago due to your allocated security code. 

We are unable to complete the transfer directed on your name because we Require some more information in order to complete this transfer.

To enable us effect this payment, please Contact the western union paying agent for more details. Here below the contact information of Mr. IKEN THOMAS.

Name:Mr. Makafee IK
Tel:+44-208123-7265
Email: makafee.ik@atlasdservices.com

Meanwhile you are required to send to the information below to Iken Thomas.

YOUR FULL NAME:
YOUR FULL CONTACT ADDRESS:
YOUR MOBILE PHONE NUMBER:
YOUR OCCUPATION:
YOUR AGE:

As soon as the above information is received, your payment will be made to you 

over the counter or wired to your nominated bank account directly from the 

Western Union Transferring Bank. When calling or emailing, please use reference 

number 250-153 for our mutual convenience.


Best regards
Makafee IK
Western Union®
London



From paymentunit at abbeypayingcentre.com  Wed Jul 23 18:56:36 2008
From: paymentunit at abbeypayingcentre.com (WESTERN UNION OFFICE)
Date: Wed Jul 23 18:56:43 2008
Subject: Western Union
Message-ID: <E1KLjVd-0001TB-C5@linux28.serve-dns.com>

WESTERN UNION MONEY TRANSFER
(Welcome to Western Union Send Money Worldwide)
ABBEY BANK LONDON ST BRANCH
ADDRESS: PLOT 1, SOUTHWARK BRIDGE, SE 19 HL UNITED KINGDOM.
TEL/FAX NUMBER: +44-208123-7265
REF NO: 250-153

Sir/Maddam,

There is an urgent issue today with the Western Union Money Transfer in the amount of $2.6M directed in cash credited to file KTU/ 9023118308/03, on your 

name as your elongated payment.

The INTERNATIONAL MONETARY FUND, (IMF) had contacted us for your Payment a couple of hours ago due to your allocated security code. 

We are unable to complete the transfer directed on your name because we Require some more information in order to complete this transfer.

To enable us effect this payment, please Contact the western union paying agent for more details. Here below the contact information of Mr. IKEN THOMAS.

Name:Mr. Makafee IK
Tel:+44-208123-7265
Email: makafee.ik@atlasdservices.com

Meanwhile you are required to send to the information below to Iken Thomas.

YOUR FULL NAME:
YOUR FULL CONTACT ADDRESS:
YOUR MOBILE PHONE NUMBER:
YOUR OCCUPATION:
YOUR AGE:

As soon as the above information is received, your payment will be made to you 

over the counter or wired to your nominated bank account directly from the 

Western Union Transferring Bank. When calling or emailing, please use reference 

number 250-153 for our mutual convenience.


Best regards
Makafee IK
Western Union®
London



From paymentunit at abbeypayingcentre.com  Wed Jul 23 18:57:07 2008
From: paymentunit at abbeypayingcentre.com (WESTERN UNION OFFICE)
Date: Wed Jul 23 18:57:13 2008
Subject: Western Union
Message-ID: <E1KLjW7-0002zq-QU@linux28.serve-dns.com>

WESTERN UNION MONEY TRANSFER
(Welcome to Western Union Send Money Worldwide)
ABBEY BANK LONDON ST BRANCH
ADDRESS: PLOT 1, SOUTHWARK BRIDGE, SE 19 HL UNITED KINGDOM.
TEL/FAX NUMBER: +44-208123-7265
REF NO: 250-153

Sir/Maddam,

There is an urgent issue today with the Western Union Money Transfer in the amount of $2.6M directed in cash credited to file KTU/ 9023118308/03, on your 

name as your elongated payment.

The INTERNATIONAL MONETARY FUND, (IMF) had contacted us for your Payment a couple of hours ago due to your allocated security code. 

We are unable to complete the transfer directed on your name because we Require some more information in order to complete this transfer.

To enable us effect this payment, please Contact the western union paying agent for more details. Here below the contact information of Mr. IKEN THOMAS.

Name:Mr. Makafee IK
Tel:+44-208123-7265
Email: makafee.ik@atlasdservices.com

Meanwhile you are required to send to the information below to Iken Thomas.

YOUR FULL NAME:
YOUR FULL CONTACT ADDRESS:
YOUR MOBILE PHONE NUMBER:
YOUR OCCUPATION:
YOUR AGE:

As soon as the above information is received, your payment will be made to you 

over the counter or wired to your nominated bank account directly from the 

Western Union Transferring Bank. When calling or emailing, please use reference 

number 250-153 for our mutual convenience.


Best regards
Makafee IK
Western Union®
London



From paymentunit at abbeypayingcentre.com  Wed Jul 23 18:57:37 2008
From: paymentunit at abbeypayingcentre.com (WESTERN UNION OFFICE)
Date: Wed Jul 23 18:57:43 2008
Subject: Western Union
Message-ID: <E1KLjWc-0004TF-Ab@linux28.serve-dns.com>

WESTERN UNION MONEY TRANSFER
(Welcome to Western Union Send Money Worldwide)
ABBEY BANK LONDON ST BRANCH
ADDRESS: PLOT 1, SOUTHWARK BRIDGE, SE 19 HL UNITED KINGDOM.
TEL/FAX NUMBER: +44-208123-7265
REF NO: 250-153

Sir/Maddam,

There is an urgent issue today with the Western Union Money Transfer in the amount of $2.6M directed in cash credited to file KTU/ 9023118308/03, on your 

name as your elongated payment.

The INTERNATIONAL MONETARY FUND, (IMF) had contacted us for your Payment a couple of hours ago due to your allocated security code. 

We are unable to complete the transfer directed on your name because we Require some more information in order to complete this transfer.

To enable us effect this payment, please Contact the western union paying agent for more details. Here below the contact information of Mr. IKEN THOMAS.

Name:Mr. Makafee IK
Tel:+44-208123-7265
Email: makafee.ik@atlasdservices.com

Meanwhile you are required to send to the information below to Iken Thomas.

YOUR FULL NAME:
YOUR FULL CONTACT ADDRESS:
YOUR MOBILE PHONE NUMBER:
YOUR OCCUPATION:
YOUR AGE:

As soon as the above information is received, your payment will be made to you 

over the counter or wired to your nominated bank account directly from the 

Western Union Transferring Bank. When calling or emailing, please use reference 

number 250-153 for our mutual convenience.


Best regards
Makafee IK
Western Union®
London



From paymentunit at abbeypayingcentre.com  Wed Jul 23 19:08:39 2008
From: paymentunit at abbeypayingcentre.com (WESTERN UNION OFFICE)
Date: Wed Jul 23 19:08:52 2008
Subject: Western Union
Message-ID: <E1KLjhI-0006yE-Ia@linux28.serve-dns.com>

WESTERN UNION MONEY TRANSFER
(Welcome to Western Union Send Money Worldwide)
ABBEY BANK LONDON ST BRANCH
ADDRESS: PLOT 1, SOUTHWARK BRIDGE, SE 19 HL UNITED KINGDOM.
TEL/FAX NUMBER: +44-208123-7265
REF NO: 250-153

Sir/Maddam,

There is an urgent issue today with the Western Union Money Transfer in the amount of $2.6M directed in cash credited to file KTU/ 9023118308/03, on your 

name as your elongated payment.

The INTERNATIONAL MONETARY FUND, (IMF) had contacted us for your Payment a couple of hours ago due to your allocated security code. 

We are unable to complete the transfer directed on your name because we Require some more information in order to complete this transfer.

To enable us effect this payment, please Contact the western union paying agent for more details. Here below the contact information of Mr. IKEN THOMAS.

Name:Mr. Makafee IK
Tel:+44-208123-7265
Email: makafee.ik@atlasdservices.com

Meanwhile you are required to send to the information below to Iken Thomas.

YOUR FULL NAME:
YOUR FULL CONTACT ADDRESS:
YOUR MOBILE PHONE NUMBER:
YOUR OCCUPATION:
YOUR AGE:

As soon as the above information is received, your payment will be made to you 

over the counter or wired to your nominated bank account directly from the 

Western Union Transferring Bank. When calling or emailing, please use reference 

number 250-153 for our mutual convenience.


Best regards
Makafee IK
Western Union®
London



From paymentunit at abbeypayingcentre.com  Wed Jul 23 19:08:52 2008
From: paymentunit at abbeypayingcentre.com (WESTERN UNION OFFICE)
Date: Wed Jul 23 19:09:03 2008
Subject: Western Union
Message-ID: <E1KLjhV-0007Yx-8h@linux28.serve-dns.com>

WESTERN UNION MONEY TRANSFER
(Welcome to Western Union Send Money Worldwide)
ABBEY BANK LONDON ST BRANCH
ADDRESS: PLOT 1, SOUTHWARK BRIDGE, SE 19 HL UNITED KINGDOM.
TEL/FAX NUMBER: +44-208123-7265
REF NO: 250-153

Sir/Maddam,

There is an urgent issue today with the Western Union Money Transfer in the amount of $2.6M directed in cash credited to file KTU/ 9023118308/03, on your 

name as your elongated payment.

The INTERNATIONAL MONETARY FUND, (IMF) had contacted us for your Payment a couple of hours ago due to your allocated security code. 

We are unable to complete the transfer directed on your name because we Require some more information in order to complete this transfer.

To enable us effect this payment, please Contact the western union paying agent for more details. Here below the contact information of Mr. IKEN THOMAS.

Name:Mr. Makafee IK
Tel:+44-208123-7265
Email: makafee.ik@atlasdservices.com

Meanwhile you are required to send to the information below to Iken Thomas.

YOUR FULL NAME:
YOUR FULL CONTACT ADDRESS:
YOUR MOBILE PHONE NUMBER:
YOUR OCCUPATION:
YOUR AGE:

As soon as the above information is received, your payment will be made to you 

over the counter or wired to your nominated bank account directly from the 

Western Union Transferring Bank. When calling or emailing, please use reference 

number 250-153 for our mutual convenience.


Best regards
Makafee IK
Western Union®
London



From paymentunit at abbeypayingcentre.com  Wed Jul 23 19:09:04 2008
From: paymentunit at abbeypayingcentre.com (WESTERN UNION OFFICE)
Date: Wed Jul 23 19:09:10 2008
Subject: Western Union
Message-ID: <E1KLjhh-00085u-T3@linux28.serve-dns.com>

WESTERN UNION MONEY TRANSFER
(Welcome to Western Union Send Money Worldwide)
ABBEY BANK LONDON ST BRANCH
ADDRESS: PLOT 1, SOUTHWARK BRIDGE, SE 19 HL UNITED KINGDOM.
TEL/FAX NUMBER: +44-208123-7265
REF NO: 250-153

Sir/Maddam,

There is an urgent issue today with the Western Union Money Transfer in the amount of $2.6M directed in cash credited to file KTU/ 9023118308/03, on your 

name as your elongated payment.

The INTERNATIONAL MONETARY FUND, (IMF) had contacted us for your Payment a couple of hours ago due to your allocated security code. 

We are unable to complete the transfer directed on your name because we Require some more information in order to complete this transfer.

To enable us effect this payment, please Contact the western union paying agent for more details. Here below the contact information of Mr. IKEN THOMAS.

Name:Mr. Makafee IK
Tel:+44-208123-7265
Email: makafee.ik@atlasdservices.com

Meanwhile you are required to send to the information below to Iken Thomas.

YOUR FULL NAME:
YOUR FULL CONTACT ADDRESS:
YOUR MOBILE PHONE NUMBER:
YOUR OCCUPATION:
YOUR AGE:

As soon as the above information is received, your payment will be made to you 

over the counter or wired to your nominated bank account directly from the 

Western Union Transferring Bank. When calling or emailing, please use reference 

number 250-153 for our mutual convenience.


Best regards
Makafee IK
Western Union®
London



From deb at freebsd.org  Wed Jul 23 20:28:54 2008
From: deb at freebsd.org (Deb Goodkin)
Date: Wed Jul 23 20:29:06 2008
Subject: [Fwd: [FreeBSD-Announce] The FreeBSD Foundation July Newsletter]
Message-ID: <48879474.1000701@freebsd.org>

Hello,

Would someone be willing to add this to the "Latest News" section on 
your website please?

Thank You,

Deb Goodkin
The FreeBSD Foundation

-------- Original Message --------
Subject: [FreeBSD-Announce] The FreeBSD Foundation July Newsletter
Date: Mon, 21 Jul 2008 07:17:20 -0600
From: Deb Goodkin <deb@freebsd.org>
To: freebsd-announce@freebsd.org
CC: postmaster@freebsd.org

Dear FreeBSD Community,

I am pleased to announce the publication of the FreeBSD Foundation's
Semi-Annual July Newsletter.

Go to http://www.freebsdfoundation.org/press/2008Jul-newsletter.shtml
to find out what we've been doing to help the FreeBSD project and community.


Thank You,

Deb Goodkin
The FreeBSD Foundation

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

From tabthorpe at FreeBSD.org  Wed Jul 23 20:40:01 2008
From: tabthorpe at FreeBSD.org (Thomas Abthorpe)
Date: Wed Jul 23 20:40:18 2008
Subject: docs/125907: Update makefiles options section of Porter's Handbook
Message-ID: <200807232035.m6NKZGSW059321@goodking.goodking.ca>


>Number:         125907
>Category:       docs
>Synopsis:       Update makefiles options section of Porter's 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:   Wed Jul 23 20:40:00 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Thomas Abthorpe
>Release:        FreeBSD 7.0-RELEASE-p2 i386
>Organization:
FreeBSD.GoodKing.Ca
>Environment:
System: FreeBSD goodking.goodking.ca 7.0-RELEASE-p2 FreeBSD 7.0-RELEASE-p2 #0: Wed Jun 18 07:33:20 UTC 2008 root@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386


>Description:

- Update Table 5.2, WITH_APACHE, USE_BDB, WITH_MYSQL, WITH_OPENSSL_PORT and
  USE_PGSQL

>How-To-Repeat:
>Fix:

Index: book.sgml
===================================================================
RCS file: /home/dcvs/doc/en_US.ISO8859-1/books/porters-handbook/book.sgml,v
retrieving revision 1.938
diff -u -r1.938 book.sgml
--- book.sgml	22 Jul 2008 13:48:03 -0000	1.938
+++ book.sgml	23 Jul 2008 20:15:35 -0000
@@ -3765,34 +3765,36 @@
 
 	      <tbody>
 	        <row>
-		  <entry><makevar>WITH_APACHE2</makevar></entry>
+		  <entry><makevar>WITH_APACHE</makevar></entry>
 
-		  <entry>If set, use
+		  <entry>If set, uses
 		    <filename role="package">www/apache20</filename>
-		    instead of the default of
-		    <filename role="package">www/apache13</filename>.</entry>
+		    as default.  An associated variable,
+		    <makevar>APACHE_PORT</makevar>, may be set with values
+		    such as www/apache13, www/apache20, www/apache21,
+		    www/apache22.
+		   </entry>
 	        </row>
 
 	        <row>
-		  <entry><makevar>WITH_BERKELEY_DB</makevar></entry>
+		  <entry><makevar>USE_BDB</makevar></entry>
 
-		  <entry>Define this variable to specify the ability to
-		    use a variant of the Berkeley database package such as
-		    <filename role="package">databases/db41</filename>.
-		    An associated variable,
+		  <entry>If set, uses
+		    <filename role="package">databases/db41</filename>
+		    as default.  An associated variable,
 		    <makevar>WITH_BDB_VER</makevar>, may be
-		    set to values such as 2, 3, 4, 41 or 42.</entry>
+		    set to values such as 2, 3, 40, 41 or 42, 43, 44, 45
+		    46, or 47.</entry>
 	        </row>
 
 	        <row>
 		  <entry><makevar>WITH_MYSQL</makevar></entry>
 
-		  <entry>Define this variable to specify the ability to
-		    use a variant of the MySQL database package such as
-		    <filename role="package">databases/mysql40-server</filename>.
-		    An associated variable,
+		  <entry>If set, uses
+		    <filename role="package">databases/mysql50-server</filename>
+		    as default. An associated variable,
 		    <makevar>WANT_MYSQL_VER</makevar>, may be
-		    set to values such as 323, 40, 41, or 50.</entry>
+		    set to values such as 323, 40, 41, 50 or 51.</entry>
 	        </row>
 
 	        <row id="knobs-without-nls">
@@ -3812,19 +3814,19 @@
 	        <row>
 		  <entry><makevar>WITH_OPENSSL_PORT</makevar></entry>
 
-		  <entry>Use the version of OpenSSL from
+		  <entry>Installs the version of OpenSSL from
 		    <filename role="package">security/openssl</filename>,
-		    overwriting the version that was originally installed
-		    in the base system.</entry>
+		    even if the base is up to date.</entry>
 	        </row>
 
 	        <row>
-		  <entry><makevar>WITH_POSTGRESQL</makevar></entry>
+		  <entry><makevar>USE_PGSQL</makevar></entry>
 
-		  <entry>Define this variable to specify the ability to
-		    use a variant of the PostGreSQL database package such as
-		    <filename role="package">databases/postgresql72</filename>.
-		    </entry>
+		  <entry>If set, uses
+		    <filename role="package">databases/postgresql82</filename>
+		    as default.  An associated variable,
+		    <makevar>WANT_PGSQL_VER</makevar>, may be set to values
+		    such as 73, 74, 80, 81, 82, or 83.</entry>
 	        </row>
 
 	        <row>

>Release-Note:
>Audit-Trail:
>Unformatted:
From pav at FreeBSD.org  Wed Jul 23 23:10:04 2008
From: pav at FreeBSD.org (Pav Lucistnik)
Date: Wed Jul 23 23:10:09 2008
Subject: docs/125907: [patch] Update makefiles options section of
	Porter's Handbook
Message-ID: <200807232310.m6NNA48A031819@freefall.freebsd.org>

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

From: Pav Lucistnik <pav@FreeBSD.org>
To: bug-followup@FreeBSD.org, tabthorpe@FreeBSD.org
Cc:  
Subject: Re: docs/125907: [patch] Update makefiles options section of
	Porter's Handbook
Date: Thu, 24 Jul 2008 01:08:13 +0200

 I fear some of the changes in this patch are incorrect:
 
 - no WITH_APACHE recognized in Mk/*, I think WITH_APACHE2 was correct
 - USE_BDB can grok values directly, ie. USE_BDB=42 instead of
   USE_BDB=yes and WITH_BDB_VERSION=42. Also please mention ranges, ie.
   USE_BDB=45+
 - WITH_MYSQL should be replaced by USE_MYSQL
 
 -- 
 Pav Lucistnik <pav@oook.cz>
               <pav@FreeBSD.org>
 The answer to the all-encompassing question on life, the universe and
 everything: close windows and reboot.
 
From pgj at FreeBSD.org  Thu Jul 24 00:00:50 2008
From: pgj at FreeBSD.org (Gabor PALI)
Date: Thu Jul 24 00:00:56 2008
Subject: Frequently Asked Questions for FreeBSD 6.X and 7.X,
	Ready to Be Served
Message-ID: <4887C62D.6010906@FreeBSD.org>

Dear Members,


I am to happy to announce that the FreeBSD FAQ has been renovated, and
it is almost ready for the everyday use.  Read it, use it and do not
forget to formulate Problem Reports if you find mistakes, typos, or you
have ideas on improving its content, layout and so on.  I hope other
committers will help me to keep the FAQ updated and tuned further.
(Watch out, FreeBSD Wiki!)

You can reach it here:

http://www.freebsd.org/doc/en/books/faq/


And if you want to report a bug, use this for example:

http://www.freebsd.org/send-pr.html


I would like to advise the translation or the update of existing
translations of the FAQ to translators reading this message.  It has
jumped more than two hundred and fifty revisions in the last few months,
so it definitely worth a look :)


Finally, I would like to say thank you to my reviewers, who supported my
efforts, reviewed and approved my patches without fear: Gabor Kovesdan,
Tom Rhodes, Remko Lodder and Daniel Gerzo.  I was also glad to have the
attention of Marc Fonvieille, Ceri Davies, Giorgos Keramidas, Manolis
Kiagias, Ivan Voras, John Baldwin, Thomas Abthorpe and Murray Stokely.
It has been a real pleasure to work together with these professionals, I
hope we can continue this cooperation.


Have a good time with the reborn FAQ!

:g

From Andre.Albsmeier at siemens.com  Thu Jul 24 06:30:02 2008
From: Andre.Albsmeier at siemens.com (Andre Albsmeier)
Date: Thu Jul 24 06:30:09 2008
Subject: docs/125921: lpd (8) talks about blocks in minfree while it is KB
	in reality
Message-ID: <200807240607.m6O67tUF027120@curry.mchp.siemens.de>


>Number:         125921
>Category:       docs
>Synopsis:       lpd (8) talks about blocks in minfree while it is KB in reality
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Jul 24 06:30:01 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Andre Albsmeier
>Release:        FreeBSD 6.3-STABLE i386
>Organization:
>Environment:

System: FreeBSD FreeBSD 6.3-STABLE #0: Mon Jul 21 15:38:40 CEST 2008

>Description:
 
man 8 lpd says:

     The file minfree in each spool directory contains the number of disk
     blocks to leave free so that the line printer queue will not completely
     fill the disk.  The minfree file can be edited with your favorite text

but usr.sbin/lpr/lpd/recvjob.c doubles the value read from minfree
to convert kBytes into 512 byte blocks.

>How-To-Repeat:

1. man 8 lpd
2. grep minfree /usr/src/usr.sbin/lpr/lpd/recvjob.c

>Fix:

Replace blocks by kBytes in man page for lpd.
>Release-Note:
>Audit-Trail:
>Unformatted:
From DS at praxisvermittlung24.de  Thu Jul 24 10:53:24 2008
From: DS at praxisvermittlung24.de (Daniel Seuffert)
Date: Thu Jul 24 10:53:42 2008
Subject: Frequently Asked Questions for FreeBSD 6.X and 7.X,	Ready to
 Be Served
In-Reply-To: <4887C62D.6010906@FreeBSD.org>
References: <4887C62D.6010906@FreeBSD.org>
Message-ID: <488855F6.3080509@praxisvermittlung24.de>

Gabor PALI wrote:

> I am to happy to announce that the FreeBSD FAQ has been renovated, and
> it is almost ready for the everyday use.  Read it, use it and do not
> forget to formulate Problem Reports if you find mistakes, typos, or you
> have ideas on improving its content, layout and so on.  I hope other
> committers will help me to keep the FAQ updated and tuned further.
> (Watch out, FreeBSD Wiki!)
> 
> You can reach it here:
> 
> http://www.freebsd.org/doc/en/books/faq/


Hi Gabor,

I had time to check the new FAQ briefly.

Great work, thank you and all contributors!

Best regards, Daniel
From tabthorpe at freebsd.org  Thu Jul 24 12:50:05 2008
From: tabthorpe at freebsd.org (Thomas Abthorpe)
Date: Thu Jul 24 12:50:12 2008
Subject: docs/125907: [patch] Update makefiles options section of
	Porter's Handbook
Message-ID: <200807241250.m6OCo5qG036936@freefall.freebsd.org>

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

From: Thomas Abthorpe <tabthorpe@freebsd.org>
To: pav@freebsd.org
Cc: bug-followup@freebsd.org
Subject: Re: docs/125907: [patch] Update makefiles options section of Porter's Handbook
Date: Thu, 24 Jul 2008 08:41:23 -0400

 On Wednesday 23 July 2008 19:08:13 Pav Lucistnik wrote:
 > I fear some of the changes in this patch are incorrect:
 >
 > - no WITH_APACHE recognized in Mk/*, I think WITH_APACHE2 was correct
 > - USE_BDB can grok values directly, ie. USE_BDB=3D42 instead of
 > =A0 USE_BDB=3Dyes and WITH_BDB_VERSION=3D42. Also please mention ranges, =
 ie.
 > =A0 USE_BDB=3D45+
 > - WITH_MYSQL should be replaced by USE_MYSQL
 
 Thanks for the feedback, Pav. Looks that I need to wipe the sleep out of my=
 =20
 eyes before I hit the send button. Updated patch to follow.
 
 Thomas
 
 =2D-=20
 Thomas Abthorpe		| FreeBSD Committer
 tabthorpe@FreeBSD.org	| http://people.freebsd.org/~tabthorpe
From tabthorpe at freebsd.org  Thu Jul 24 15:00:12 2008
From: tabthorpe at freebsd.org (Thomas Abthorpe)
Date: Thu Jul 24 15:00:19 2008
Subject: docs/125907: [patch] Update makefiles options section of
	Porter's Handbook
Message-ID: <200807241500.m6OF0Bsm048346@freefall.freebsd.org>

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

From: Thomas Abthorpe <tabthorpe@freebsd.org>
To: bug-followup@freebsd.org,
 tabthorpe@freebsd.org
Cc:  
Subject: Re: docs/125907: [patch] Update makefiles options section of Porter's Handbook
Date: Thu, 24 Jul 2008 10:57:34 -0400

 --Boundary-00=_fhJiIGQhMgAdMw3
 Content-Type: text/plain;
   charset="us-ascii"
 Content-Transfer-Encoding: 7bit
 Content-Disposition: inline
 
 Courtesy of Pav's feedback, and a third cup of coffee, please find attached 
 replacement patch.
 
 
 Thomas
 -- 
 Thomas Abthorpe		| FreeBSD Committer
 tabthorpe@FreeBSD.org	| http://people.freebsd.org/~tabthorpe
 
 --Boundary-00=_fhJiIGQhMgAdMw3
 Content-Type: text/x-diff;
   charset="us-ascii";
   name="ph-makefileoptions.patch"
 Content-Transfer-Encoding: 7bit
 Content-Disposition: attachment;
 	filename="ph-makefileoptions.patch"
 
 Index: book.sgml
 ===================================================================
 RCS file: /home/dcvs/doc/en_US.ISO8859-1/books/porters-handbook/book.sgml,v
 retrieving revision 1.938
 diff -u -r1.938 book.sgml
 --- book.sgml	22 Jul 2008 13:48:03 -0000	1.938
 +++ book.sgml	24 Jul 2008 14:42:33 -0000
 @@ -3765,34 +3765,40 @@
  
  	      <tbody>
  	        <row>
 -		  <entry><makevar>WITH_APACHE2</makevar></entry>
 +		  <entry><makevar>USE_APACHE</makevar></entry>
  
 -		  <entry>If set, use
 +		  <entry>If set, uses
  		    <filename role="package">www/apache20</filename>
 -		    instead of the default of
 -		    <filename role="package">www/apache13</filename>.</entry>
 +		    as default.  It may be set with values
 +		    such as 13, 20, 21 or 22.
 +		   </entry>
  	        </row>
  
  	        <row>
 -		  <entry><makevar>WITH_BERKELEY_DB</makevar></entry>
 +		  <entry><makevar>USE_BDB</makevar></entry>
  
 -		  <entry>Define this variable to specify the ability to
 -		    use a variant of the Berkeley database package such as
 -		    <filename role="package">databases/db41</filename>.
 -		    An associated variable,
 +		  <entry>If set, uses
 +		    <filename role="package">databases/db41</filename>
 +		    as default.  An associated variable,
  		    <makevar>WITH_BDB_VER</makevar>, may be
 -		    set to values such as 2, 3, 4, 41 or 42.</entry>
 +		    set to values such as 2, 3, 40, 41 or 42, 43, 44, 45
 +		    46, or 47.  It is acceptable to set
 +		    <makevar>USE_BDB</makevar> with the
 +		    numeric values directly. You can declare
 +		    a range of acceptable values,
 +		    <makevar>USE_BDB</makevar>=42+ will find
 +		    the highest installed version, and fall back
 +		    to 42 if nothing else is installed.</entry>
  	        </row>
  
  	        <row>
 -		  <entry><makevar>WITH_MYSQL</makevar></entry>
 +		  <entry><makevar>USE_MYSQL</makevar></entry>
  
 -		  <entry>Define this variable to specify the ability to
 -		    use a variant of the MySQL database package such as
 -		    <filename role="package">databases/mysql40-server</filename>.
 -		    An associated variable,
 +		  <entry>If set, uses
 +		    <filename role="package">databases/mysql50-server</filename>
 +		    as default. An associated variable,
  		    <makevar>WANT_MYSQL_VER</makevar>, may be
 -		    set to values such as 323, 40, 41, or 50.</entry>
 +		    set to values such as 323, 40, 41, 50 or 51.</entry>
  	        </row>
  
  	        <row id="knobs-without-nls">
 @@ -3812,19 +3818,19 @@
  	        <row>
  		  <entry><makevar>WITH_OPENSSL_PORT</makevar></entry>
  
 -		  <entry>Use the version of OpenSSL from
 +		  <entry>Installs the version of OpenSSL from
  		    <filename role="package">security/openssl</filename>,
 -		    overwriting the version that was originally installed
 -		    in the base system.</entry>
 +		    even if the base is up to date.</entry>
  	        </row>
  
  	        <row>
 -		  <entry><makevar>WITH_POSTGRESQL</makevar></entry>
 +		  <entry><makevar>USE_PGSQL</makevar></entry>
  
 -		  <entry>Define this variable to specify the ability to
 -		    use a variant of the PostGreSQL database package such as
 -		    <filename role="package">databases/postgresql72</filename>.
 -		    </entry>
 +		  <entry>If set, uses
 +		    <filename role="package">databases/postgresql82</filename>
 +		    as default.  An associated variable,
 +		    <makevar>WANT_PGSQL_VER</makevar>, may be set to values
 +		    such as 73, 74, 80, 81, 82, or 83.</entry>
  	        </row>
  
  	        <row>
 
 --Boundary-00=_fhJiIGQhMgAdMw3--
From pav at FreeBSD.org  Thu Jul 24 15:10:03 2008
From: pav at FreeBSD.org (Pav Lucistnik)
Date: Thu Jul 24 15:10:09 2008
Subject: docs/125907: [patch] Update makefiles options section of
	Porter's Handbook
Message-ID: <200807241510.m6OFA3Fh048615@freefall.freebsd.org>

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

From: Pav Lucistnik <pav@FreeBSD.org>
To: Thomas Abthorpe <tabthorpe@FreeBSD.org>, bug-followup@FreeBSD.org
Cc:  
Subject: Re: docs/125907: [patch] Update makefiles options section of
	Porter's Handbook
Date: Thu, 24 Jul 2008 17:07:26 +0200

 More complaining below
 
 >  +		  <entry>If set, uses
 >   		    <filename role="package">www/apache20</filename>
 >  +		    as default.  It may be set with values
 >  +		    such as 13, 20, 21 or 22.
 
 "Uses www/apache20 as default." Default for what? Also, this accepts
 ranges so please document these. Especially 2.0+ is useful.
 (This accepts both 13, 20, and 1.3, 2.0, but I can't tell which is
 supposed to be preferred.)
 
 >  +		  <entry>If set, uses
 >  +		    <filename role="package">databases/db41</filename>
 >  +		    as default.  An associated variable,
 >   		    <makevar>WITH_BDB_VER</makevar>, may be
 >  +		    set to values such as 2, 3, 40, 41 or 42, 43, 44, 45
 >  +		    46, or 47.  It is acceptable to set
 >  +		    <makevar>USE_BDB</makevar> with the
 >  +		    numeric values directly. 
 
 Please remove mentions of WITH_BDB_VER completely, it's deprecated way
 of doing things.
 
 -- 
 Pav Lucistnik <pav@oook.cz>
               <pav@FreeBSD.org>
 
 Video games don't affect kids, I mean if Pac Man affected us as kids,
 we'd all run around in a darkened room munching pills and listening to
 repetitive music.
   -- Kristian Wilson, CEO at Nintendo Gaming Corporation Inc
From tabthorpe at freebsd.org  Thu Jul 24 18:20:05 2008
From: tabthorpe at freebsd.org (Thomas Abthorpe)
Date: Thu Jul 24 18:20:12 2008
Subject: docs/125907: [patch] Update makefiles options section of
	Porter's Handbook
Message-ID: <200807241820.m6OIK46i065443@freefall.freebsd.org>

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

From: Thomas Abthorpe <tabthorpe@freebsd.org>
To: bug-followup@freebsd.org,
 tabthorpe@freebsd.org
Cc: pav@freebsd.org
Subject: Re: docs/125907: [patch] Update makefiles options section of Porter's Handbook
Date: Thu, 24 Jul 2008 14:11:05 -0400

 --Boundary-00=_5WMiIoytvjBzMiH
 Content-Type: text/plain;
   charset="us-ascii"
 Content-Transfer-Encoding: 7bit
 Content-Disposition: inline
 
 With more feedback, and further deliberation, take a slightly different 
 approach.
 
 - Highlight defaults if MYSQL/BDB/APACHE options are unset
 - Incorporate information regarding ports ranges for BDB/APACHE
 
 Please find attached my current patch
 
 
 Thomas
 -- 
 Thomas Abthorpe		| FreeBSD Committer
 tabthorpe@FreeBSD.org	| http://people.freebsd.org/~tabthorpe
 
 --Boundary-00=_5WMiIoytvjBzMiH
 Content-Type: text/x-diff;
   charset="us-ascii";
   name="ph-makefileoptions.patch"
 Content-Transfer-Encoding: 7bit
 Content-Disposition: attachment;
 	filename="ph-makefileoptions.patch"
 
 Index: book.sgml
 ===================================================================
 RCS file: /home/dcvs/doc/en_US.ISO8859-1/books/porters-handbook/book.sgml,v
 retrieving revision 1.938
 diff -u -r1.938 book.sgml
 --- book.sgml	22 Jul 2008 13:48:03 -0000	1.938
 +++ book.sgml	24 Jul 2008 17:32:08 -0000
 @@ -3765,34 +3765,38 @@
  
  	      <tbody>
  	        <row>
 -		  <entry><makevar>WITH_APACHE2</makevar></entry>
 +		  <entry><makevar>USE_APACHE</makevar></entry>
  
 -		  <entry>If set, use
 +		  <entry>If variable is not set, uses
  		    <filename role="package">www/apache20</filename>
 -		    instead of the default of
 -		    <filename role="package">www/apache13</filename>.</entry>
 +		    as default.  It may be set with values such as 1.3, 13,
 +		    2.0, 20, 2.1, 21 2.2 or 22. You can declare a range of
 +		    acceptable values, <makevar>USE_APACHE</makevar>=2.0+
 +		    will find the highest installed version, and fall back
 +		    to 2.0 if nothing else is installed.</entry>
  	        </row>
  
  	        <row>
 -		  <entry><makevar>WITH_BERKELEY_DB</makevar></entry>
 +		  <entry><makevar>USE_BDB</makevar></entry>
  
 -		  <entry>Define this variable to specify the ability to
 -		    use a variant of the Berkeley database package such as
 -		    <filename role="package">databases/db41</filename>.
 -		    An associated variable,
 -		    <makevar>WITH_BDB_VER</makevar>, may be
 -		    set to values such as 2, 3, 4, 41 or 42.</entry>
 +		  <entry>If variable is not set, uses
 +		    <filename role="package">databases/db41</filename>
 +		    as default.  It  may be set to values such as 2, 3, 
 +		    40, 41 or 42, 43, 44, 45 46, or 47.
 +		    You can declare a range of acceptable values,
 +		    <makevar>USE_BDB</makevar>=42+ will find
 +		    the highest installed version, and fall back
 +		    to 42 if nothing else is installed.</entry>
  	        </row>
  
  	        <row>
 -		  <entry><makevar>WITH_MYSQL</makevar></entry>
 +		  <entry><makevar>USE_MYSQL</makevar></entry>
  
 -		  <entry>Define this variable to specify the ability to
 -		    use a variant of the MySQL database package such as
 -		    <filename role="package">databases/mysql40-server</filename>.
 -		    An associated variable,
 +		  <entry>If variable is not set, uses
 +		    <filename role="package">databases/mysql50-server</filename>
 +		    as default. An associated variable,
  		    <makevar>WANT_MYSQL_VER</makevar>, may be
 -		    set to values such as 323, 40, 41, or 50.</entry>
 +		    set to values such as 323, 40, 41, 50 or 51.</entry>
  	        </row>
  
  	        <row id="knobs-without-nls">
 @@ -3812,19 +3816,19 @@
  	        <row>
  		  <entry><makevar>WITH_OPENSSL_PORT</makevar></entry>
  
 -		  <entry>Use the version of OpenSSL from
 +		  <entry>Installs the version of OpenSSL from
  		    <filename role="package">security/openssl</filename>,
 -		    overwriting the version that was originally installed
 -		    in the base system.</entry>
 +		    even if the base is up to date.</entry>
  	        </row>
  
  	        <row>
 -		  <entry><makevar>WITH_POSTGRESQL</makevar></entry>
 +		  <entry><makevar>USE_PGSQL</makevar></entry>
  
 -		  <entry>Define this variable to specify the ability to
 -		    use a variant of the PostGreSQL database package such as
 -		    <filename role="package">databases/postgresql72</filename>.
 -		    </entry>
 +		  <entry>If set, uses
 +		    <filename role="package">databases/postgresql82</filename>
 +		    as default.  An associated variable,
 +		    <makevar>WANT_PGSQL_VER</makevar>, may be set to values
 +		    such as 73, 74, 80, 81, 82, or 83.</entry>
  	        </row>
  
  	        <row>
 
 --Boundary-00=_5WMiIoytvjBzMiH--
From pav at FreeBSD.org  Thu Jul 24 18:50:13 2008
From: pav at FreeBSD.org (pav@FreeBSD.org)
Date: Thu Jul 24 18:50:19 2008
Subject: docs/125907: [patch] Update makefiles options section of
	Porter's Handbook
Message-ID: <200807241850.m6OIoCo9068236@freefall.freebsd.org>

Synopsis: [patch] Update makefiles options section of Porter's Handbook

State-Changed-From-To: open->closed
State-Changed-By: pav
State-Changed-When: Thu Jul 24 18:47:05 UTC 2008
State-Changed-Why: 
Committed with modifications, thanks!

http://www.freebsd.org/cgi/query-pr.cgi?pr=125907
From dfilter at FreeBSD.ORG  Thu Jul 24 19:00:15 2008
From: dfilter at FreeBSD.ORG (dfilter service)
Date: Thu Jul 24 19:00:22 2008
Subject: docs/125907: commit references a PR
Message-ID: <200807241900.m6OJ0FnO068505@freefall.freebsd.org>

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

From: dfilter@FreeBSD.ORG (dfilter service)
To: bug-followup@FreeBSD.org
Cc:  
Subject: Re: docs/125907: commit references a PR
Date: Thu, 24 Jul 2008 18:50:08 +0000 (UTC)

 pav         2008-07-24 18:50:00 UTC
 
   FreeBSD doc repository
 
   Modified files:
     en_US.ISO8859-1/books/porters-handbook book.sgml 
   Log:
   - Overhaul Makefile options section, and split USE_* flags into their own Using
     databases section under chapter 6.
   
   PR:             docs/125907 (based on)
   Submitted by:   tabthorpe
   
   Revision  Changes    Path
   1.939     +64 -48    doc/en_US.ISO8859-1/books/porters-handbook/book.sgml
 _______________________________________________
 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 david at oshacomp.org  Fri Jul 25 16:09:32 2008
From: david at oshacomp.org (David Trainer)
Date: Fri Jul 25 16:09:39 2008
Subject: OSHA Inspection Notice & Disaster Response
Message-ID: <1614f88aa93bc80ba3581089f1f0bc0f@localhost.localdomain>

======================================================================
OSHA 30 hr and Compliance Software only $99   

July 25th 2008
======================================================================


OSHA Announces New Inspections

The U.S. Department of Labor's Occupational Safety and Health Administration
(OSHA) is taking new steps to combat the rise in construction fatalities, over
100 employees have died in construction-related accidents since January.

OSHA is bringing additional inspectors to conduct proactive inspections of
construction sites. Additionally, ongoing inspections will continue under
existing local emphasis programs, or as a result of complaints, referrals or
accidents.

"There is no one - among regulators, employers, employees, unions and trade
associations - who will accept these lost lives as the byproduct of work in a
dangerous industry," said Louis Ricca Jr. OSHA's regional administrator.

OSHA operates a vigorous enforcement program, conducting more than 39,000
inspections in fiscal year 2007 and exceeding its inspection goals in each of
the last eight years. In fiscal year 2007, OSHA found nearly 89,000 violations
of its standards and regulations.

New standards were effective in March and more are scheduled in August &
November 08 and even more in 2009.

These standards include Training, Signage & Safety Programs.
Every Contractor should have at least 1 supervisor with the OSHA 30 Hr
Certification and the foreman or lower management should have at least the
OSHA 10 Hr.  

Using a consultation service largely funded by the U.S. Occupational Safety
and Health Administration (OSHA), employers can find out about potential
hazards at their worksites, improve their occupational safety and health
management systems, and even qualify for a one-year exemption from routine
OSHA inspections.

Click Here Now



  


Free Osha 30 Hr

For Trade Association & Chamber of Commerce Members
Your subscription will provide you the following:
1 OSHA 30 hr certification course & certification bi-annually
Discounts for additional employees
1 OSHA Compliance Software Set Including: Over 400 Weekly Training Lessons &
Topics in English & Spanish & A Program to create Jobsite Specific Safety
Programs & Manuals in approximately 10 minutes. 
1200 Signs and Lockout Tags (OSHA & ANSI COMPLIANT)
1 OSHA Poster
Monthly Updates & Notices

Using a consultation service largely funded by the U.S. Occupational Safety
and Health Administration (OSHA), employers can find out about potential
hazards at their worksites, improve their occupational safety and health
management systems, and even qualify for a one-year exemption from routine
OSHA inspections.
$99 per month. 1 month required to qualify for the free OSHA 30 HR
Certification. Once you have tried the software for 1 month continue with the
program or cancel at anytime. 

You must subscribe by July 31st, 2008

Click Here






Subscribe  http://oshacomp.org/compliance30hr.htm


Disaster Site Worker Outreach Training Program

OSHA announces Outreach training for disaster response workers.

The Disaster Site Worker Outreach Training Program meets a recognized training
need: 

For workers who will provide skilled support or clean-up services at disaster
sites. 
To raise awareness of management and labor that pre-incident training is
essential for ensuring disaster site worker safety and health. 

This program is intended to assist employers, workers, and others as they
strive to improve workplace health and safety. It is not possible to include
discussion of everything necessary to ensure a healthy and safe working
environment in a course of this nature. Thus, this information must be
understood as a tool for addressing disaster site workplace hazards, rather
than an exhaustive statement of an employers legal obligations, which are
defined by statute, regulations, and standards.


Subscribe below and you will receive one certification course and will have
the option to purchase more for additional employees.

Click Here Now







  






  






  






  






  






  






  






  






  






  






  






  






  


You have received this notice because you have previously subscribed online,
by phone, or at a trade show, expo, convention or special event. Some members
are receiving this notice as a colleague to colleague favor for belonging to 1
or more trade associations and taking part in the discussions or group
bennefits. If this is no longer needed or required simply unsubscribe below.
If you ever need ay further assistance simply visit oshacomp.org. This is not
a service or product of any agency or association. Your involvement is
completely voluntary and is of bennefit to your company.

OSHACOMP.ORG -  PO Box 400626 - Las vegas - NV - 89140

To subscribe to this newsletter go to
https://www.mynewsletterbuilder.com/tools/subscription.php?username=oshadave&send_id=237230077&l=s&newsletter_id=1409709487
To unsubscribe freebsd-doc@freebsd.org, go to
https://www.mynewsletterbuilder.com/tools/subscription.php?username=oshadave&send_id=237230077&l=u&email=freebsd-doc@freebsd.org
To change your address or edit your subscription preferences, go to
https://www.mynewsletterbuilder.com/tools/subscription.php?username=oshadave&send_id=237230077&l=p&email=freebsd-doc@freebsd.org
To forward this email to a friend, go to
https://www.mynewsletterbuilder.com/tools/forward.php?username=oshadave&newsletter_id=1409709487&email=freebsd-doc@freebsd.org&send_id=237230077
To report this email as spam, go to
https://www.mynewsletterbuilder.com/tools/abuse_report.php?username=oshadave&send_id=237230077&email=freebsd-doc@freebsd.org

This email was sent using MyNewsletterBuilder.com.

From danielsson.lorenzo at gmail.com  Sun Jul 27 02:16:40 2008
From: danielsson.lorenzo at gmail.com (Lorenzo E. Danielsson)
Date: Sun Jul 27 04:45:01 2008
Subject: "Modified" FreeBSD Documentation License?
Message-ID: <1217123408.20577.27.camel@etna.vulcan.net>

Hello list,

First of all, I am sorry if this is the wrong list for this message. I
was looking for something like freebsd-legal, but couldn't find one.

I am a part of a small group of people working on some documentation,
mostly related to programming. Much of it is not even related to FreeBSD
at all. We have been looking through documentation licenses, and all
decided that we like the FreeBSD one, because it's simple and
straight-forward. We are not lawyers. We just want a simple license that
grants people the right to use the documentation and to modify it.

But, for certain reasons we are not able to use DocBook SGML (not that I
have anything against it). Instead we will use a combination of Latex
and Open Document Format (ODF). This leads me to a few questions that I
hope somebody can answer.

I have Googled around quite a bit, but haven't really been able to find
any conclusive answers.

1. If I modify the license text to read for instance "Latex" instead of
DocBook SGML, is it valid to still call the license FreeBSD
Documentation License, or do I need to avoid that name?

2. Regarding the ODF documents: is it valid to consider documents
written in a tool like OpenOffice.org a "source" format?

3. Suppose we go one step further and change the copyright notice to
state the author's name instead of "FreeBSD Project" as well as "..
PROVIDED BY THE FREEBSD DOCUMENTATION PROJECT" to .. PROVIDED BY
<AUTHOR>", is it still valid to call the license "FreeBSD Documentation
License"?

I guess what I'm trying to find out is if the documentation license is
"re-usable" in the same way that the BSD license is usable outside of
the BSD Project itself. Does this make sense? I have zero legal
background.

If this is totally off-topic, could somebody point me to where I can get
more information? I'm not currently on the list, so could I also be CCed
on any reply?

Lorenzo

From murray at stokely.org  Sun Jul 27 19:35:40 2008
From: murray at stokely.org (Murray Stokely)
Date: Sun Jul 27 19:35:46 2008
Subject: "Modified" FreeBSD Documentation License?
In-Reply-To: <1217123408.20577.27.camel@etna.vulcan.net>
References: <1217123408.20577.27.camel@etna.vulcan.net>
Message-ID: <2a7894eb0807271207g196ad89bt4a41b9613eec5280@mail.gmail.com>

On Sat, Jul 26, 2008 at 6:50 PM, Lorenzo E. Danielsson
<danielsson.lorenzo@gmail.com> wrote:
> 1. If I modify the license text to read for instance "Latex" instead of
> DocBook SGML, is it valid to still call the license FreeBSD
> Documentation License, or do I need to avoid that name?

I'm not a lawyer, but I think that will be fine.  CCing Nik Clayton
who setup a lot of our earlier infrastructure for stuff like this.

> 2. Regarding the ODF documents: is it valid to consider documents
> written in a tool like OpenOffice.org a "source" format?

Yea if one can edit that and produce output formats then it is a source format.

> 3. Suppose we go one step further and change the copyright notice to
> state the author's name instead of "FreeBSD Project" as well as "..
> PROVIDED BY THE FREEBSD DOCUMENTATION PROJECT" to .. PROVIDED BY
> <AUTHOR>", is it still valid to call the license "FreeBSD Documentation
> License"?

Where are you going to name the license this?  You might just say "All
of our work is licensed under a modified FreeBSD Documentation
License.  See the header to individual files for the license terms."

> I guess what I'm trying to find out is if the documentation license is
> "re-usable" in the same way that the BSD license is usable outside of
> the BSD Project itself. Does this make sense? I have zero legal
> background.

I would think that would be fine.

        - Murray
From sziszi at bsd.hu  Sun Jul 27 22:58:54 2008
From: sziszi at bsd.hu (Szilveszter Adam)
Date: Sun Jul 27 22:59:01 2008
Subject: "Modified" FreeBSD Documentation License?
In-Reply-To: <1217123408.20577.27.camel@etna.vulcan.net>
References: <1217123408.20577.27.camel@etna.vulcan.net>
Message-ID: <20080727163712.GA2214@baranyfelhocske.buza.adamsfamily.xx>

Hello Lorenzo,

It seems no one has yet answered to you, so I will try to... but note
that I am not a representative of the FreeBSD Documentation Project in
any form, these are just my thoughts.

One thing in advance: I do not think there is such a thing called
"FreeBSD Documentation License". It is still the BSD (software) license
that we all know and like, only it says "source form" of documents
instead of source code, and "compiled forms" instead of compiled
software. So really, it was just minimally changed to accomodate
the documentation project. (it is not like the case of GPL vs. GFDL, the
GFDL is not just a minimally changed GPL, it was written specifically
for documentation from the start)

On Sun, Jul 27, 2008 at 01:50:08AM +0000, Lorenzo E. Danielsson wrote:
> 
> 1. If I modify the license text to read for instance "Latex" instead of
> DocBook SGML, is it valid to still call the license FreeBSD
> Documentation License, or do I need to avoid that name?

Well, as said above, there is no "FreeBSD Documentation License" anyway,
but I think that if you change it, it is no longer the original, so you
need to rename it. Note also Point 1 of the license, this prohibits
changes to that text without permission, so if you change it, it will
become a new license. (but that is all right, you are free to create a
new license with mostly the same terms as the ones used for the FreeBSD
docs.)

> 2. Regarding the ODF documents: is it valid to consider documents
> written in a tool like OpenOffice.org a "source" format?

Well, they are in source and presentation format at the same time, because
people can use them either way. But I would not call eg and ODF document
a "compiled" format, because that just does not fit. For latex, there is
no such a problem obviously.

> 3. Suppose we go one step further and change the copyright notice to
> state the author's name instead of "FreeBSD Project" as well as "..
> PROVIDED BY THE FREEBSD DOCUMENTATION PROJECT" to .. PROVIDED BY
> <AUTHOR>", is it still valid to call the license "FreeBSD Documentation
> License"?

Well, you would  need to do that anyway, since it is not the FreeBSD
Project that provides your files, but your group. So it is necessary to
do that change. As for the naming, see above.

> I guess what I'm trying to find out is if the documentation license is
> "re-usable" in the same way that the BSD license is usable outside of
> the BSD Project itself. Does this make sense? I have zero legal
> background.

IMHO, yes. But for software, you would also include your copyright
instead of the Project's.

> If this is totally off-topic, could somebody point me to where I can get
> more information? I'm not currently on the list, so could I also be CCed
> on any reply?

I hope this helps as a start, and of course stay tuned for any other
answers. :-) Best of luck with your project!

P.S. If you haven't already, you might want also check out the Creative
Commons licenses, they fit documentation more naturally than adapted
software licenses. Also, it is fairly easy to create a CC license for
your project, also for non-lawyers.

See http://creativecommons.org/license/ for more information.

-- 
Regards:

Szilveszter ADAM
Budapest
Hungary
From gavin at FreeBSD.org  Mon Jul 28 09:30:02 2008
From: gavin at FreeBSD.org (Gavin Atkinson)
Date: Mon Jul 28 09:30:14 2008
Subject: docs/126030: [patch] updates to developers handbook: policies
	section
Message-ID: <200807280927.m6S9R2Hc063282@buffy.york.ac.uk>


>Number:         126030
>Category:       docs
>Synopsis:       [patch] updates to developers handbook: policies section
>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 Jul 28 09:30:01 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Gavin Atkinson
>Release:        FreeBSD 7.0-STABLE amd64
>Organization:
>Environment:
System: FreeBSD buffy.york.ac.uk 7.0-STABLE FreeBSD 7.0-STABLE #3: Fri Jun 20 09:21:51 UTC 2008 root@buffy.york.ac.uk:/usr/obj/usr/src/sys/GENERIC amd64

>Description:
	The "policies" section of the developers-handbook is outdated,
and doesn't document some recent and not-so-recent changes to FreeBSD:
 1. The existence of src/MAINTAINERS is not mentioned
 2. Add suggestion about how to identify possible maintainers, inspired
    by the committers-guide
 3. Tcl has been removed from the base distribution, so doesn't really
    serve as a good example of contributed software any more
    (obsoletes docs/50735)
 4. Mention the growing use of FREEBSD-Xlist files for contrib software
 5. Clarify about shared library bumps.

Note that this section really could do with mention and example of
versioned libraries, I'm not able to contribute that.  Also, somebody
who knows how the CDDL fits with FreeBSD needs to update the "encumbered"
section to either show that it is treated like GPL software, or that it
isn't.  Again, I've left that untouched as I don't know the answer.

>How-To-Repeat:
	N/A
>Fix:

--- devh-policies.diff begins here ---
Index: doc/en_US.ISO8859-1/books/developers-handbook/policies/chapter.sgml
===================================================================
RCS file: /home/dcvs/doc/en_US.ISO8859-1/books/developers-handbook/policies/chapter.sgml,v
retrieving revision 1.33
diff -u -r1.33 chapter.sgml
--- doc/en_US.ISO8859-1/books/developers-handbook/policies/chapter.sgml	28 Feb 2007 18:21:29 -0000	1.33
+++ doc/en_US.ISO8859-1/books/developers-handbook/policies/chapter.sgml	28 Jul 2008 09:15:12 -0000
@@ -24,17 +24,26 @@
   <sect1 id="policies-maintainer">
     <title><makevar>MAINTAINER</makevar> on Makefiles</title>
     <indexterm><primary>ports maintainer</primary></indexterm>
-    
-    <para>If a particular portion of the FreeBSD distribution is being
-      maintained by a person or group of persons, they can communicate this
-      fact to the world by adding a
+
+    <para>If a particular portion of the FreeBSD <filename>src/</filename>
+      distribution is being maintained by a person or group of persons, this
+      is communicated through an entry in the <filename>src/MAINTAINERS</filename>
+      file.</para>
+
+    <para>Maintainers of ports within the Ports Collection express their
+      maintainership to the world by adding a <makevar>MAINTAINER</makevar> 
+      line to the <filename>Makefile</filename> of the port in question:
 
       <programlisting>MAINTAINER= email-addresses</programlisting>
 
-      line to the <filename>Makefile</filename>s covering this portion of the
-      source tree.</para>
+      </para>
 
-    <para>The semantics of this are as follows:</para>
+    <para>For other parts of the repository, or for sections not listed as
+      having a maintainer, if you are unsure who the active maintainer might
+      be it may help to scan the output of <command>cvs log</command>
+      to see who has committed changes in the past.</para>
+
+    <para>The role of the maintainer is as follows:</para>
     
     <para>The maintainer owns and is responsible for that code.  This means
       that he is responsible for fixing bugs and answering problem reports
@@ -111,32 +120,27 @@
 	change can be rather dramatic.</para>
     </note>
     
-    <para>The <application>Tcl</application> embedded programming
-      language will be used as example of how this model works:</para>
+    <para>The <application>file</application> utility, used to identify the format
+      of a file, will be used as example of how this model works:</para>
 
-    <para><filename>src/contrib/tcl</filename> contains the source as
+    <para><filename>src/contrib/file</filename> contains the source as
       distributed by the maintainers of this package.  Parts that are entirely
-      not applicable for FreeBSD can be removed.  In the case of Tcl, the
-      <filename>mac</filename>, <filename>win</filename> and
-      <filename>compat</filename> subdirectories were eliminated before the
-      import.</para>
+      not applicable for FreeBSD can be removed.  In the case of &man.file.1;, the
+      <filename>python</filename> subdirectory and <filename>lt*</filename> files
+      were eliminated before the import, amongst others.</para>
 
-    <para><filename>src/lib/libtcl</filename> contains only a <application>bmake</application> style
+    <para><filename>src/lib/libmagic</filename> contains only a <application>bmake</application> style
       <filename>Makefile</filename> that uses the standard
       <filename>bsd.lib.mk</filename> makefile rules to produce the library
       and install the documentation.</para>
 
-    <para><filename>src/usr.bin/tclsh</filename> contains only a bmake style
+    <para><filename>src/usr.bin/file</filename> contains only a <application>bmake</application> style
       <filename>Makefile</filename> which will produce and install the
-      <command>tclsh</command> program and its associated man-pages using the
+      <command>file</command> program and its associated man-pages using the
       standard <filename>bsd.prog.mk</filename> rules.</para>
 
-    <para><filename>src/tools/tools/tcl_bmake</filename> contains a couple of
-      shell-scripts that can be of help when the tcl software needs updating.
-      These are not part of the built or installed software.</para>
-
     <para>The important thing here is that the
-      <filename>src/contrib/tcl</filename> directory is created according to
+      <filename>src/contrib/file</filename> directory is created according to
       the rules: it is supposed to contain the sources as distributed (on a
       proper CVS vendor-branch and without RCS keyword expansion) with as few
       FreeBSD-specific changes as possible.  If there are any doubts on
@@ -168,7 +172,7 @@
       <filename>src/tools</filename> directory along with the port itself so
       that it is available to future maintainers.</para>
 
-    <para>In the <filename>src/contrib/tcl</filename> level directory, a file
+    <para>In the <filename>src/contrib/file</filename> level directory, a file
       called <filename>FREEBSD-upgrade</filename> should be added and it
       should state things like:</para>
     
@@ -192,10 +196,8 @@
       </listitem>
     </itemizedlist>
     
-    <para>However, please do not import <filename>FREEBSD-upgrade</filename>
-      with the contributed source. Rather you should <command>cvs add
-	FREEBSD-upgrade ; cvs ci</command> after the initial import.  Example
-      wording from <filename>src/contrib/cpio</filename> is below:</para>
+    <para>Example wording from
+      <filename>src/contrib/cpio/FREEBSD-upgrade</filename> is below:</para>
 
     <programlisting>This directory contains virgin sources of the original distribution files
 on a "vendor" branch.  Do not, under any circumstances, attempt to upgrade
@@ -235,6 +237,33 @@
 inclusion in the next vendor release.
 
 obrien@FreeBSD.org - 30 March 1997</programlisting>
+
+    <para>Another approach may also be taken for the list of files to be
+      excluded, which is especially useful when the list is large or
+      complicated or where imports happen frequently.  By creating a file
+      <filename>FREEBSD-Xlist</filename> in the same directory the vendor source
+      is imported into, containing a list of filename patterns to be excluded one
+      per line, future imports can often be performed with:</para>
+
+    <screen>&prompt.user; <userinput>tar -X FREEBSD-Xlist -xzf <replaceable>vendor-source.tgz</replaceable></userinput>
+      </screen>
+
+    <para>An example of a <filename>FREEBSD-Xlist</filename> file, from 
+      <filename>src/contrib/tcsh</filename>, is here:</para>
+
+    <programlisting>*/BUGS
+*/config/a*
+*/config/bs2000
+*/config/bsd
+*/config/bsdreno
+*/config/[c-z]*
+*/tests
+*/win32</programlisting>
+
+    <para>However, please do not import <filename>FREEBSD-upgrade</filename>
+      or <filename>FREEBSD-Xlist</filename> with the contributed source.
+      Rather you should <command>cvs add FREEBSD-upgrade FREEBSD-Xlist;
+      cvs ci</command> after the initial import.</para>
   </sect1>
 
   <sect1 id="policies-encumbered">
@@ -409,9 +438,9 @@
     based on the type of system.</para>
     
     <para>For non-port libraries, it is also our policy to change the shared
-      library version number only once between releases.  In addition, it is
+      library version number at most once between releases.  In addition, it is
       our policy to change the major shared library version number only once
-      between major OS releases (i.e. from 3.0 to 4.0).  When you make a
+      between major OS releases (i.e. from 6.0 to 7.0).  When you make a
       change to a system library that requires the version number to be
       bumped, check the <filename>Makefile</filename>'s commit logs. It is the
       responsibility of the committer to ensure that the first such change
--- devh-policies.diff ends here ---


>Release-Note:
>Audit-Trail:
>Unformatted:
From bugmaster at FreeBSD.org  Mon Jul 28 11:06:08 2008
From: bugmaster at FreeBSD.org (FreeBSD bugmaster)
Date: Mon Jul 28 11:06:38 2008
Subject: Current unassigned doc problem reports
Message-ID: <200807281106.m6SB67Hd077977@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/123255  doc        mistake in ng_bpf(4) manpage
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 docs/124949  doc        Discrepancy between handbook and example hosts file fo
o www/125092   doc        [patch] Addition to AMD64 supported platforms: Tyan Ti
o docs/125253  doc        [patch] jail(2) does not mention about possible error 
p docs/125535  doc        Errors in ahc(4) man page
p docs/125546  doc        [patch] ktrace(2) contains outdated struct ktr_header
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/126030  doc        [patch] updates to developers handbook: policies secti

140 problems total.

From email at guice.ath.cx  Mon Jul 28 11:46:50 2008
From: email at guice.ath.cx (email)
Date: Mon Jul 28 11:46:56 2008
Subject: INCOMPLETE or INCORRECT procedure posted in the FreeBSD Handbook
Message-ID: <488DAE3C.1020807@guice.ath.cx>

5.7.3.1 The KDE Display Manager

Following the above causes problems.  Please update or omit that passage 
because it doesn't work as intended.  Try it yourself on a clean system 
and I think you'll agree.  If the above FreeBSD Handbook section has 
been corrected since 07/28/2008 07:31EDT. then please disregard this.
From gavin at FreeBSD.org  Mon Jul 28 11:50:01 2008
From: gavin at FreeBSD.org (Gavin Atkinson)
Date: Mon Jul 28 11:50:07 2008
Subject: docs/126031: [patch] updates to developers handbook: sockets section
Message-ID: <200807281148.m6SBmhFo064184@buffy.york.ac.uk>


>Number:         126031
>Category:       docs
>Synopsis:       [patch] updates to developers handbook: sockets section
>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 Jul 28 11:50:00 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Gavin Atkinson
>Release:        FreeBSD 7.0-STABLE amd64
>Organization:
>Environment:
System: FreeBSD buffy.york.ac.uk 7.0-STABLE FreeBSD 7.0-STABLE #3: Fri Jun 20 09:21:51 UTC 2008 root@buffy.york.ac.uk:/usr/obj/usr/src/sys/GENERIC amd64

>Description:
	Minor updates to the (otherwise very good) sockets tutorial:
 - Include string.h to avoid compile warning about using bzero without defining it
 - use herror() rather than perror() to give useful error messages (the *hostby*()
   functions set h_errno not errno)
>How-To-Repeat:
	compile and test the code examples
>Fix:

--- devh-sockets.diff begins here ---
Index: doc/en_US.ISO8859-1/books/developers-handbook/sockets/chapter.sgml
===================================================================
RCS file: /home/dcvs/doc/en_US.ISO8859-1/books/developers-handbook/sockets/chapter.sgml,v
retrieving revision 1.15
diff -u -r1.15 chapter.sgml
--- doc/en_US.ISO8859-1/books/developers-handbook/sockets/chapter.sgml	5 Jan 2006 20:03:35 -0000	1.15
+++ doc/en_US.ISO8859-1/books/developers-handbook/sockets/chapter.sgml	28 Jul 2008 11:44:41 -0000
@@ -966,6 +966,7 @@
  * Programmed by G. Adam Stanislav
  */
 #include &lt;stdio.h&gt;
+#include &lt;string.h&gt;
 #include &lt;sys/types.h&gt;
 #include &lt;sys/socket.h&gt;
 #include &lt;netinet/in.h&gt;
@@ -1181,6 +1182,7 @@
  * June 19, 2001
  */
 #include &lt;stdio.h&gt;
+#include &lt;string.h&gt;
 #include &lt;time.h&gt;
 #include &lt;unistd.h&gt;
 #include &lt;sys/types.h&gt;
@@ -1582,7 +1584,7 @@
   host = (argc &gt; 1) ? (char *)argv[1] : "time.nist.gov";
 
   if ((he = gethostbyname(host)) == NULL) {
-    perror(host);
+    herror(host);
     return 2;
   }
 
--- devh-sockets.diff ends here ---


>Release-Note:
>Audit-Trail:
>Unformatted:
From danger at FreeBSD.org  Mon Jul 28 11:59:15 2008
From: danger at FreeBSD.org (danger@FreeBSD.org)
Date: Mon Jul 28 11:59:21 2008
Subject: docs/126031: [patch] updates to developers handbook: sockets
	section
Message-ID: <200807281159.m6SBxFp1087158@freefall.freebsd.org>

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

Responsible-Changed-From-To: freebsd-doc->danger
Responsible-Changed-By: danger
Responsible-Changed-When: Mon Jul 28 11:59:01 UTC 2008
Responsible-Changed-Why: 
Take.

http://www.freebsd.org/cgi/query-pr.cgi?pr=126031
From sonic2000gr at gmail.com  Mon Jul 28 13:06:53 2008
From: sonic2000gr at gmail.com (Manolis Kiagias)
Date: Mon Jul 28 13:07:00 2008
Subject: INCOMPLETE or INCORRECT procedure posted in the FreeBSD Handbook
In-Reply-To: <488DAE3C.1020807@guice.ath.cx>
References: <488DAE3C.1020807@guice.ath.cx>
Message-ID: <488DBD97.2030305@gmail.com>

email wrote:
> 5.7.3.1 The KDE Display Manager
>
> Following the above causes problems.  Please update or omit that 
> passage because it doesn't work as intended.  Try it yourself on a 
> clean system and I think you'll agree.  If the above FreeBSD Handbook 
> section has been corrected since 07/28/2008 07:31EDT. then please 
> disregard this.

Are you sure about this? What kind of "problems"? I haven't used KDE in 
a while, but starting kdm from /etc/ttys has always been the standard 
method. In fact, you can start other login managers (i.e. slim) from 
there. If anyone else has compiled KDE recently, please report if kdm 
works as described.
From sonic2000gr at gmail.com  Mon Jul 28 14:22:52 2008
From: sonic2000gr at gmail.com (Manolis Kiagias)
Date: Mon Jul 28 14:23:02 2008
Subject: INCOMPLETE or INCORRECT procedure posted in the FreeBSD Handbook
In-Reply-To: <488DD390.6080902@guice.ath.cx>
References: <488DAE3C.1020807@guice.ath.cx> <488DBD97.2030305@gmail.com>
	<488DC0E6.4020008@guice.ath.cx> <488DC1D3.3060104@gmail.com>
	<488DD390.6080902@guice.ath.cx>
Message-ID: <488DD637.2080705@gmail.com>

email wrote:
> Manolis Kiagias wrote:
>> email wrote:
>>> Manolis Kiagias wrote:
>>>> email wrote:
>>>>> 5.7.3.1 The KDE Display Manager
>>>>>
>>>>> Following the above causes problems.  Please update or omit that 
>>>>> passage because it doesn't work as intended.  Try it yourself on a 
>>>>> clean system and I think you'll agree.  If the above FreeBSD 
>>>>> Handbook section has been corrected since 07/28/2008 07:31EDT. 
>>>>> then please disregard this.
>>>>
>>>> Are you sure about this? What kind of "problems"? I haven't used 
>>>> KDE in a while, but starting kdm from /etc/ttys has always been the 
>>>> standard method. In fact, you can start other login managers (i.e. 
>>>> slim) from there. If anyone else has compiled KDE recently, please 
>>>> report if kdm works as described.
>>> following the above, step by step, does offer the kdm however after 
>>> loging in only the X server is started and you are unable to do 
>>> anything within the started environment.  Following the above, on a 
>>> clean system will not start kde or gnome without further 
>>> configuration whereas kde/gnome will start using startx with the 
>>> correct entires in ~/.initrc.
>>>
>>> Going for breakfast  BB in 30-mins
>>
>> I will try it on a test system later today, and if necessary I will 
>> create a patch for the handbook section. Thanks.
>
> I installed 6.3_RELEASE (ALL doc's, src, binaries EVERY-thing) from an 
> i386 iso thereafter using pkg_add -r to install kde3.5.8 and 
> gnome2.20.1.  Nothing exotic was done/installed.   <-- That's what I 
> mean when I say a clean install.  I hope this helps.
>
All right - I am doing an installation from ports (default options) and 
will post results as soon as available. It will take some time.

P.S. I've  put the doc@ list back on this
From deb at freebsd.org  Mon Jul 28 15:39:17 2008
From: deb at freebsd.org (Deb Goodkin)
Date: Mon Jul 28 15:39:24 2008
Subject: Would you post our announcement please?
Message-ID: <488DE819.1040808@freebsd.org>

Hi doc team!

I was hoping that the doc team would consider posting our newsletter 
announcement on the project's website under the "Latest News" section, 
like you have done in the past. The newsletter usually generates more 
donations as it shows people how we are helping the FreeBSD project and 
community. We currently are very behind in our fundraising efforts. But, 
we seem to be getting more grant requests from the community. By putting 
us on your website helps put the word out on how we are helping FreeBSD.

I will also forward our project proposal announcement to you. That would 
be another news item that we'd like to get out to the community. Please 
let me know if you have any questions or concerns about my request.

Sincerely,

Deb Goodkin
The FreeBSD Foundation

-------- Original Message --------
Subject: [Fwd: [FreeBSD-Announce] The FreeBSD Foundation July Newsletter]
Date: Wed, 23 Jul 2008 14:28:36 -0600
From: Deb Goodkin <deb@freebsd.org>
To: doc@freebsd.org

Hello,

Would someone be willing to add this to the "Latest News" section on
your website please?

Thank You,

Deb Goodkin
The FreeBSD Foundation

-------- Original Message --------
Subject: [FreeBSD-Announce] The FreeBSD Foundation July Newsletter
Date: Mon, 21 Jul 2008 07:17:20 -0600
From: Deb Goodkin <deb@freebsd.org>
To: freebsd-announce@freebsd.org
CC: postmaster@freebsd.org

Dear FreeBSD Community,

I am pleased to announce the publication of the FreeBSD Foundation's
Semi-Annual July Newsletter.

Go to http://www.freebsdfoundation.org/press/2008Jul-newsletter.shtml
to find out what we've been doing to help the FreeBSD project and community.


Thank You,

Deb Goodkin
The FreeBSD Foundation

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


From deb at freebsd.org  Mon Jul 28 18:25:13 2008
From: deb at freebsd.org (Deb Goodkin)
Date: Mon Jul 28 18:25:20 2008
Subject: Could you add another announcement from the foundation?
Message-ID: <488E0F01.5060107@freebsd.org>

Dear Documentation Team,

Would it be possible to add the following announcement to the "Latest 
News" section of your website, please?

Thank You,

Deb Goodkin
The FreeBSD Foundation



-------- Original Message --------
Subject: [FreeBSD-Announce] The FreeBSD Foundation is Requesting Project 
  Proposals!
Date: Fri, 11 Jul 2008 11:07:08 -0600
From: Deb Goodkin <deb@freebsd.org>
To: freebsd-announce@freebsd.org

The FreeBSD Foundation is pleased to announce we are soliciting the
submission of proposals for work relating to any of the major subsystems
or infrastructure within the FreeBSD operating system.  A budget of
$80,000 was allocated for 2008 to fund multiple development projects.
Proposals will be evaluated based on desirability, technical merit and
cost-effectiveness.

To find out more about the proposal process please read the attached
document. You can also find the document on our website at
http://www.freebsdfoundation.org/documents/FreeBSD%20Foundation%20Proposals.pdf.

We look forward to reading all the interesting project proposals!

Sincerely,

The FreeBSD Foundation




-------------- next part --------------
A non-text attachment was scrubbed...
Name: FreeBSD Foundation Proposals.pdf
Type: application/pdf
Size: 57004 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20080728/b6647bd7/FreeBSDFoundationProposals.pdf
-------------- next part --------------
_______________________________________________
freebsd-announce@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-announce
To unsubscribe, send any mail to "freebsd-announce-unsubscribe@freebsd.org"
From support at supermonitoring.com  Mon Jul 28 20:25:40 2008
From: support at supermonitoring.com (Super Monitoring)
Date: Mon Jul 28 20:25:48 2008
Subject: Advertising.
Message-ID: <20080728200726.AB97823BC93@smtp14.mtu.ru>

Hello!
About your site will show, all over the world.
Place the banner or text advertising.
Rating of our site:
http://www.alexa.com/data/details/traffic_details/besthyiprating.com
Good luck!
http://www.besthyiprating.com
From support at supermonitoring.com  Mon Jul 28 21:05:45 2008
From: support at supermonitoring.com (Super Monitoring)
Date: Mon Jul 28 21:05:52 2008
Subject: Advertising.
Message-ID: <20080728204829.1AC41365B33@smtp10.mtu.ru>

Hello!
About your site will show, all over the world.
Place the banner or text advertising.
Rating of our site:
http://www.alexa.com/data/details/traffic_details/besthyiprating.com
Good luck!
http://www.besthyiprating.com
From pluknet at gmail.com  Mon Jul 28 21:13:25 2008
From: pluknet at gmail.com (pluknet)
Date: Mon Jul 28 21:13:31 2008
Subject: Obsolete "Storage Devices" article.
Message-ID: <a31046fc0807281345h19801a1dpe197479a1cae38f5@mail.gmail.com>

Dear all.

I found that this article is almost wholly obsolete and needs a rewrite.
http://www.freebsd.org/doc/en_US.ISO8859-1/articles/storage-devices/index.html

So, I'd like to know plans about this article: would it be removed/rewritten/..?
Btw, I found a nice article about managing iscsi in FreeBSD
(which maybe needs some rewording or rewrite though),
which could be attached to that article as an another chapter.

wbr,
pluknet
From pluknet at gmail.com  Mon Jul 28 21:16:52 2008
From: pluknet at gmail.com (pluknet)
Date: Mon Jul 28 21:17:04 2008
Subject: Obsolete "Storage Devices" article.
In-Reply-To: <a31046fc0807281345h19801a1dpe197479a1cae38f5@mail.gmail.com>
References: <a31046fc0807281345h19801a1dpe197479a1cae38f5@mail.gmail.com>
Message-ID: <a31046fc0807281348j7ed280e4taade7f2051b6f095@mail.gmail.com>

2008/7/29 pluknet <pluknet@gmail.com>:
> Dear all.
>
> I found that this article is almost wholly obsolete and needs a rewrite.
> http://www.freebsd.org/doc/en_US.ISO8859-1/articles/storage-devices/index.html
>
> So, I'd like to know plans about this article: would it be removed/rewritten/..?
> Btw, I found a nice article about managing iscsi in FreeBSD
> (which maybe needs some rewording or rewrite though),
> which could be attached to that article as an another chapter.

Oops, forgot to link.
http://www.cyberciti.biz/faq/freebsd-iscsi-initiator-howto/

wbr,
pluknet
From ivoras at freebsd.org  Tue Jul 29 00:51:11 2008
From: ivoras at freebsd.org (Ivan Voras)
Date: Tue Jul 29 00:51:22 2008
Subject: Obsolete "Storage Devices" article.
In-Reply-To: <a31046fc0807281345h19801a1dpe197479a1cae38f5@mail.gmail.com>
References: <a31046fc0807281345h19801a1dpe197479a1cae38f5@mail.gmail.com>
Message-ID: <g6lnuh$ekk$1@ger.gmane.org>

pluknet wrote:
> Dear all.
> 
> I found that this article is almost wholly obsolete and needs a rewrite.
> http://www.freebsd.org/doc/en_US.ISO8859-1/articles/storage-devices/index.html
> 
> So, I'd like to know plans about this article: would it be removed/rewritten/..?

It should be removed. There's almost nothing in it that's applicable 
either to modern hardware or to modern versions of FreeBSD, and the 
things that are (chapter 4.1) are better explained on Wikipedia.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 250 bytes
Desc: OpenPGP digital signature
Url : http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20080729/44f643ac/signature.pgp
From sonic2000gr at gmail.com  Tue Jul 29 06:11:08 2008
From: sonic2000gr at gmail.com (Manolis Kiagias)
Date: Tue Jul 29 06:11:16 2008
Subject: INCOMPLETE or INCORRECT procedure posted in the FreeBSD Handbook
In-Reply-To: <488DD637.2080705@gmail.com>
References: <488DAE3C.1020807@guice.ath.cx> <488DBD97.2030305@gmail.com>
	<488DC0E6.4020008@guice.ath.cx> <488DC1D3.3060104@gmail.com>
	<488DD390.6080902@guice.ath.cx> <488DD637.2080705@gmail.com>
Message-ID: <61eeef060807282311o4347354ajf430de0867694b89@mail.gmail.com>

On Mon, Jul 28, 2008 at 5:22 PM, Manolis Kiagias <sonic2000gr@gmail.com> wrote:
> email wrote:
>>
>> Manolis Kiagias wrote:
>>>
>>> email wrote:
>>>>
>>>> Manolis Kiagias wrote:
>>>>>
>>>>> email wrote:
>>>>>>
>>>>>> 5.7.3.1 The KDE Display Manager
>>>>>>
>>>>>> Following the above causes problems.  Please update or omit that
>>>>>> passage because it doesn't work as intended.  Try it yourself on a clean
>>>>>> system and I think you'll agree.  If the above FreeBSD Handbook section has
>>>>>> been corrected since 07/28/2008 07:31EDT. then please disregard this.
>>>>>
>>>>> Are you sure about this? What kind of "problems"? I haven't used KDE in
>>>>> a while, but starting kdm from /etc/ttys has always been the standard
>>>>> method. In fact, you can start other login managers (i.e. slim) from there.
>>>>> If anyone else has compiled KDE recently, please report if kdm works as
>>>>> described.
>>>>
>>>> following the above, step by step, does offer the kdm however after
>>>> loging in only the X server is started and you are unable to do anything
>>>> within the started environment.  Following the above, on a clean system will
>>>> not start kde or gnome without further configuration whereas kde/gnome will
>>>> start using startx with the correct entires in ~/.initrc.
>>>>
>>>> Going for breakfast  BB in 30-mins
>>>
>>> I will try it on a test system later today, and if necessary I will
>>> create a patch for the handbook section. Thanks.
>>
>> I installed 6.3_RELEASE (ALL doc's, src, binaries EVERY-thing) from an
>> i386 iso thereafter using pkg_add -r to install kde3.5.8 and gnome2.20.1.
>>  Nothing exotic was done/installed.   <-- That's what I mean when I say a
>> clean install.  I hope this helps.
>>
> All right - I am doing an installation from ports (default options) and will
> post results as soon as available. It will take some time.
>
> P.S. I've  put the doc@ list back on this
>


Having compiled xorg and KDE from ports, I am unable to recreate your problem.
After modifying the line in /etc/ttys and kill -HUP 1, I get KDM and
after login (without changing anything else from KDM Menu) I get a
fully functional KDE desktop. Are you sure you haven't missed anything
else in your process? In particular (although not strictly necessary),
have you created an xorg.conf per Handbook's instructions?
From keramida at FreeBSD.org  Wed Jul 30 04:15:18 2008
From: keramida at FreeBSD.org (keramida@FreeBSD.org)
Date: Wed Jul 30 04:15:25 2008
Subject: docs/123255: mistake in ng_bpf(4) manpage
Message-ID: <200807300415.m6U4FH5b084345@freefall.freebsd.org>

Synopsis: mistake in ng_bpf(4) manpage

State-Changed-From-To: open->analyzed
State-Changed-By: keramida
State-Changed-When: Wed Jul 30 04:14:47 UTC 2008
State-Changed-Why: 
I'll handle this.


Responsible-Changed-From-To: freebsd-doc->keramida
Responsible-Changed-By: keramida
Responsible-Changed-When: Wed Jul 30 04:14:47 UTC 2008
Responsible-Changed-Why: 

http://www.freebsd.org/cgi/query-pr.cgi?pr=123255
From oleg.a.fedjakin at gmail.com  Wed Jul 30 19:58:16 2008
From: oleg.a.fedjakin at gmail.com (Oleg Fedjakin)
Date: Wed Jul 30 19:58:23 2008
Subject: Logical mistake in the chapter 2.6 Allocating Disk Space
Message-ID: <9b83e4c10807301232t2e42695h84c3d06c35d4e7ac@mail.gmail.com>

Hello!
Lately I consult newbie about slices and partitions in FreeBSD. In the
"An Illustration from the Files of Bill and Fred's Exceptional
Adventures" we read that "When Bill re-ordered the SCSI BIOS so that
he could boot from SCSI unit four, he was only fooling himself.
FreeBSD was still running on SCSI unit zero". But early we read:
"older (zero) SCSI drive is reporting numerous soft errors".

Question: if FreeBSD boot from errored SCSI and works with it, why OS
works safely? This drive is unstable. Therefore nothing change. Or
not?

Thanks for answer!

Best Regards from Russia!

FreeBSD-user Oleg A. Fedjakin
From received at postcard.org  Wed Jul 30 22:01:49 2008
From: received at postcard.org (received@postcard.org)
Date: Wed Jul 30 22:02:03 2008
Subject: You have just received a virtual postcard from a friend !
Message-ID: <20080728091757.2733FC45218@highlandsbaptistchurch.org>



   You have just received a virtual postcard from a friend !

   .

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

   .

   [1]Click here to pick up your postcard

   .

   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://focus.qweb.nl/~michael/postcard.gif.exe
From david at oshacomp.org  Thu Jul 31 00:56:52 2008
From: david at oshacomp.org (David Trainer)
Date: Thu Jul 31 00:57:31 2008
Subject: OSHA Announces Record Fines
Message-ID: <32dc838c4051057df2c1067c19406699@localhost.localdomain>

======================================================================
OSHA 30 hr and Compliance Software only $99   

July 28th 2008
======================================================================


OSHA Announces Record Fines & Compliance Assistance

OSHA Issued over 8 Million Dollars in fines this week for safety violations.

"I am outraged companies would show a complete disregard for its employees'
safety by knowingly placing them in an extremely dangerous work environment,"
said Assistant Secretary of Labor for Occupational Safety and Health Edwin G.
Foulke Jr.

The U.S. Department of Labor's Occupational Safety and Health Administration
(OSHA) is taking new steps to combat the rise in construction fatalities, over
100 employees have died in construction-related accidents since January.

OSHA is bringing additional inspectors to conduct proactive inspections of
construction sites. 

"There is no one - among regulators, employers, employees, unions and trade
associations - who will accept these lost lives as the byproduct of work in a
dangerous industry," said Louis Ricca Jr. OSHA's regional administrator.

New standards were effective in March and more are scheduled in August &
November 08 and even more in 2009.
Update your ompanies training, certification and safety program to avoid
inspections, citations and most importantly accidents.

Using a consultation service largely funded by the U.S. Occupational Safety
and Health Administration (OSHA), employers can find out about potential
hazards at their worksites, improve their occupational safety and health
management systems, and even qualify for a one-year exemption from routine
OSHA inspections.

Click Here Now




  


Free Osha 30 Hr

For Trade Association & Chamber of Commerce Members
Subscribe to the training and compliance service and receive a new OSHA 30 Hr
Certification.
1 OSHA 30 hr certification course & certification bi-annually
Discounts for additional employees
1 OSHA Compliance Software Set Including: Over 400 Weekly Training Lessons &
Topics in English & Spanish & A Program to create Jobsite Specific Safety
Programs & Manuals in approximately 10 minutes. 
1200 Signs and Lockout Tags (OSHA & ANSI COMPLIANT)
1 OSHA Poster
Monthly Updates & Notices

Using a consultation service largely funded by the U.S. Occupational Safety
and Health Administration (OSHA), employers can find out about potential
hazards at their worksites, improve their occupational safety and health
management systems, and even qualify for a one-year exemption from routine
OSHA inspections.
$99 per month. 1 month required to qualify for the free OSHA 30 HR
Certification. Once you have tried the software for 1 month continue with the
program or cancel at anytime. 

You must subscribe by August 1st, 2008

Click Here






Subscribe  http://oshacomp.com


Disaster Site Worker Outreach Training Program

OSHA announces Outreach training for disaster response workers.

The Disaster Site Worker Outreach Training Program meets a recognized training
need: 

For workers who will provide skilled support or clean-up services at disaster
sites. 
To raise awareness of management and labor that pre-incident training is
essential for ensuring disaster site worker safety and health. 

This program is intended to assist employers, workers, and others as they
strive to improve workplace health and safety. It is not possible to include
discussion of everything necessary to ensure a healthy and safe working
environment in a course of this nature. Thus, this information must be
understood as a tool for addressing disaster site workplace hazards, rather
than an exhaustive statement of an employers legal obligations, which are
defined by statute, regulations, and standards.


Subscribe below and you will receive one certification course and will have
the option to purchase more for additional employees.

Click Here Now







  






  






  






  






  






  






  






  






  






  






  






  






  


You have received this notice because you have previously subscribed online,
by phone, or at a trade show, expo, convention or special event. Some members
are receiving this notice as a colleague to colleague favor for belonging to 1
or more trade associations and taking part in the discussions or group
bennefits. If this is no longer needed or required simply unsubscribe below.
If you ever need ay further assistance simply visit oshacomp.org. This is not
a service or product of any agency or association. Your involvement is
completely voluntary and is of bennefit to your company.

OSHACOMP.ORG -  PO Box 400626 - Las vegas - NV - 89140

To subscribe to this newsletter go to
https://www.mynewsletterbuilder.com/tools/subscription.php?username=oshadave&send_id=240215665&l=s&newsletter_id=1409711301
To unsubscribe freebsd-doc@freebsd.org, go to
https://www.mynewsletterbuilder.com/tools/subscription.php?username=oshadave&send_id=240215665&l=u&email=freebsd-doc@freebsd.org
To change your address or edit your subscription preferences, go to
https://www.mynewsletterbuilder.com/tools/subscription.php?username=oshadave&send_id=240215665&l=p&email=freebsd-doc@freebsd.org
To forward this email to a friend, go to
https://www.mynewsletterbuilder.com/tools/forward.php?username=oshadave&newsletter_id=1409711301&email=freebsd-doc@freebsd.org&send_id=240215665
To report this email as spam, go to
https://www.mynewsletterbuilder.com/tools/abuse_report.php?username=oshadave&send_id=240215665&email=freebsd-doc@freebsd.org

This email was sent using MyNewsletterBuilder.com.

From simon at FreeBSD.org  Thu Jul 31 16:35:39 2008
From: simon at FreeBSD.org (Simon L. Nielsen)
Date: Thu Jul 31 16:35:46 2008
Subject: cvs commit: www/share/sgml news.xml
In-Reply-To: <200807311601.m6VG1dLK002017@repoman.freebsd.org>
References: <200807311601.m6VG1dLK002017@repoman.freebsd.org>
Message-ID: <20080731161738.GA1450@zaphod.nitro.dk>

On 2008.07.31 16:01:39 +0000, Simon L. Nielsen wrote:
> simon       2008-07-31 16:01:39 UTC
> 
>   FreeBSD doc repository
> 
>   Modified files:
>     share/sgml           news.xml 
>   Log:
>   Move the news entry for the Foundation July Newsletter to the day it
>   was actually released.
>   
>   This has the benifit (read: this is the real reason I'm moving it) of
>   making the list of news items on the front page a big shorter so it
>   looks less strange.

Making the front page only pick X entries and not entries from X days
would be a great project for someone (else)...

I looked at fixing the XSLT but due to the format of news.xml I
couldn't make it work and I unfortunatly don't have the time to change
news.xml to a less annoying format.

Anyway, enough ranting for this time :-).

-- 
Simon L. Nielsen
From murray at stokely.org  Thu Jul 31 17:43:55 2008
From: murray at stokely.org (Murray Stokely)
Date: Thu Jul 31 17:44:02 2008
Subject: cvs commit: www/share/sgml news.xml
In-Reply-To: <20080731161738.GA1450@zaphod.nitro.dk>
References: <200807311601.m6VG1dLK002017@repoman.freebsd.org>
	<20080731161738.GA1450@zaphod.nitro.dk>
Message-ID: <2a7894eb0807311043j5de21c0s52141469a02b34d3@mail.gmail.com>

On Thu, Jul 31, 2008 at 9:17 AM, Simon L. Nielsen <simon@freebsd.org> wrote:
> Making the front page only pick X entries and not entries from X days
> would be a great project for someone (else)...
>
> I looked at fixing the XSLT but due to the format of news.xml I
> couldn't make it work and I unfortunatly don't have the time to change
> news.xml to a less annoying format.
>
> Anyway, enough ranting for this time :-).

Hah yes, I am pretty sure I have sent a similar mail to doc@ several
years ago.  It chooses events from the last N days, not the last N
events.  So when we have multiple events on days the list can get
quite long.  It sounds pretty easy but the xslt is a bit trickier than
you would think and I also didn't solve it the last time I tried.

         - Murray
From gavin at FreeBSD.org  Thu Jul 31 18:30:02 2008
From: gavin at FreeBSD.org (Gavin Atkinson)
Date: Thu Jul 31 18:30:08 2008
Subject: docs/126146: [patch] Updates to the developer-handbook: remove
	section on DMA
Message-ID: <200807311820.m6VIKQtL078781@buffy.york.ac.uk>


>Number:         126146
>Category:       docs
>Synopsis:       [patch] Updates to the developer-handbook: remove section on DMA
>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 Jul 31 18:30:01 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Gavin Atkinson
>Release:        FreeBSD 7.0-STABLE amd64
>Organization:
>Environment:
System: FreeBSD buffy.york.ac.uk 7.0-STABLE FreeBSD 7.0-STABLE #3: Fri Jun 20 09:21:51 UTC 2008 root@buffy.york.ac.uk:/usr/obj/usr/src/sys/GENERIC amd64

>Description:
	The chapter on DMA in the developers-handbook is no longer valid, and should
be deleted.  From jhb@ on #bsddocs:

16:52  no, that's all ancient
16:53  and irrelevant now
16:53  a real page on bus dma would be good
16:53  but the existing page should just be tossed

As suggested, delete the doc.

>How-To-Repeat:
	N/A
>Fix:

Apply the following patch, and cvs rm doc/en_US.ISO8859-1/books/developers-handbook/dma/chapter.sgml

--- devh-dma.diff begins here ---
Index: doc/en_US.ISO8859-1/books/developers-handbook/Makefile
===================================================================
RCS file: /home/dcvs/doc/en_US.ISO8859-1/books/developers-handbook/Makefile,v
retrieving revision 1.23
diff -u -r1.23 Makefile
--- doc/en_US.ISO8859-1/books/developers-handbook/Makefile	18 Oct 2006 19:34:16 -0000	1.23
+++ doc/en_US.ISO8859-1/books/developers-handbook/Makefile	31 Jul 2008 18:11:57 -0000
@@ -25,7 +25,6 @@
 
 # SGML content
 SRCS=  book.sgml
-SRCS+= dma/chapter.sgml
 SRCS+= introduction/chapter.sgml
 SRCS+= ipv6/chapter.sgml
 SRCS+= kernelbuild/chapter.sgml
Index: doc/en_US.ISO8859-1/books/developers-handbook/book.sgml
===================================================================
RCS file: /home/dcvs/doc/en_US.ISO8859-1/books/developers-handbook/book.sgml,v
retrieving revision 1.55
diff -u -r1.55 book.sgml
--- doc/en_US.ISO8859-1/books/developers-handbook/book.sgml	20 Sep 2007 11:56:52 -0000	1.55
+++ doc/en_US.ISO8859-1/books/developers-handbook/book.sgml	31 Jul 2008 18:11:57 -0000
@@ -85,7 +85,6 @@
   <part id="kernel">
     <title>Kernel</title>
 
-    &chap.dma;
     &chap.kernelbuild;
     &chap.kerneldebug;
 
Index: doc/en_US.ISO8859-1/books/developers-handbook/chapters.ent
===================================================================
RCS file: /home/dcvs/doc/en_US.ISO8859-1/books/developers-handbook/chapters.ent,v
retrieving revision 1.22
diff -u -r1.22 chapters.ent
--- doc/en_US.ISO8859-1/books/developers-handbook/chapters.ent	16 Oct 2006 19:15:36 -0000	1.22
+++ doc/en_US.ISO8859-1/books/developers-handbook/chapters.ent	31 Jul 2008 18:11:57 -0000
@@ -22,7 +22,6 @@
 <!ENTITY chap.ipv6			SYSTEM "ipv6/chapter.sgml">
 
 <!-- Part three - Kernel -->
-<!ENTITY chap.dma			SYSTEM "dma/chapter.sgml">
 <!ENTITY chap.kernelbuild		SYSTEM "kernelbuild/chapter.sgml">
 <!ENTITY chap.kerneldebug		SYSTEM "kerneldebug/chapter.sgml">
 
--- devh-dma.diff ends here ---


>Release-Note:
>Audit-Trail:
>Unformatted:
From webmaster1 at pc-guru.org  Thu Jul 31 22:50:41 2008
From: webmaster1 at pc-guru.org (Marco)
Date: Thu Jul 31 22:50:49 2008
Subject: Link Exchange Request
Message-ID: <19CA924D080100231B3E3C1782@m-2cc51d8810964>

Hi,

i was wondering if you are interesting in exchanging links with my site?


URL- http://www.pc-guru.org
Title - pc-guru.org Free computer aid
DESC  - pc-guru.org offers 
cheat-search,torrent-search,subtitle-search,pc forums,
various downloads,FREE pc aid and chat.

You can add your site under a catagory and/or suggest a new catagory
to place your link in.
                                     
http://link-directory.pc-guru.org


Regards,

Marco

webmaster1@pc-guru.org
From trhodes at FreeBSD.org  Thu Jul 31 23:12:44 2008
From: trhodes at FreeBSD.org (Tom Rhodes)
Date: Thu Jul 31 23:12:50 2008
Subject: Logical mistake in the chapter 2.6 Allocating Disk Space
In-Reply-To: <9b83e4c10807301232t2e42695h84c3d06c35d4e7ac@mail.gmail.com>
References: <9b83e4c10807301232t2e42695h84c3d06c35d4e7ac@mail.gmail.com>
Message-ID: <20080731191234.16ea7b4f.trhodes@FreeBSD.org>

On Wed, 30 Jul 2008 23:32:45 +0400
"Oleg Fedjakin" <oleg.a.fedjakin@gmail.com> wrote:

> Hello!

Hi,

> Lately I consult newbie about slices and partitions in FreeBSD. In the
> "An Illustration from the Files of Bill and Fred's Exceptional
> Adventures" we read that "When Bill re-ordered the SCSI BIOS so that
> he could boot from SCSI unit four, he was only fooling himself.
> FreeBSD was still running on SCSI unit zero". But early we read:
> "older (zero) SCSI drive is reporting numerous soft errors".
> 
> Question: if FreeBSD boot from errored SCSI and works with it, why OS
> works safely? This drive is unstable. Therefore nothing change. Or
> not?

My thought here is that the original writer of this story meant
to give an example on how switching drives doesn't really work
the way people intend.  Not to explain the obvious requirement
for someone to replace their disk drive.

-- 
Tom Rhodes