freebsd-doc Digest, Vol 368, Issue 1
freebsd-d...@freebsd.org
freeb...@freebsd.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.freebsd.org/mailman/listinfo/freebsd-doc
or, via email, send a message with subject or body 'help' to
freebsd-d...@freebsd.org
You can reach the person managing the list at
freebsd-...@freebsd.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of freebsd-doc digest..."
Today's Topics:
1. FreeBSD web build failed on www.freebsd.org (World Wide Web Owner)
2. FreeBSD web build failed on www.freebsd.org (World Wide Web Owner)
3. FreeBSD pxe installation server howto (Egoitz Aurrekoetxea Aurre)
4. Re: FreeBSD PXE installation howto (Egoitz Aurrekoetxea Aurre)
5. docs/145631: References to ttyd0 serial devices in handbook
need to be updated for FreeBSD 8.0 (Conall O'Brien)
6. Re: FreeBSD PXE installation howto (Egoitz Aurrekoetxea Aurre)
7. docs/145644: Add artical about creating manpage from scratch
(Joe Barbish)
8. Current unassigned doc problem reports (FreeBSD bugmaster)
----------------------------------------------------------------------
Message: 1
Date: Sun, 11 Apr 2010 12:53:13 GMT
From: World Wide Web Owner <w...@FreeBSD.org>
Subject: FreeBSD web build failed on www.freebsd.org
To: freeb...@FreeBSD.org
Message-ID: <201004111253....@www.freebsd.org>
------------------------------
Message: 2
Date: Sun, 11 Apr 2010 13:08:15 GMT
From: World Wide Web Owner <w...@FreeBSD.org>
Subject: FreeBSD web build failed on www.freebsd.org
To: freeb...@FreeBSD.org
Message-ID: <201004111308....@www.freebsd.org>
------------------------------
Message: 3
Date: Sun, 11 Apr 2010 18:24:53 +0200
From: Egoitz Aurrekoetxea Aurre <ego...@ramattack.net>
Subject: FreeBSD pxe installation server howto
To: freeb...@freebsd.org
Message-ID: <4DFBF8DF-3236-420C...@ramattack.net>
Content-Type: text/plain; charset=us-ascii
Hi,
I'm working on a project for setting up a freebsd installation server with pxe. When I started I see the doc was a bit old-fashioned... so I started looking at some blogs... freebsd doc that could help me understanding the whole process and so on... finally I have ended looking at source code of some involved parts like sysintall, boot stages and so on.... for understanding all properly for setting up this service. I have written a documentation that if you see it to be ok... (it seems to be working fine) perhaps, would be nice to appear in handbook or in some official documentation site... So if you see something that should be done in another way... or some point wich you consider it's wrong... please make me know and I'll correct it. The url in wich you could fetch the pdf file is :http://postfixquotareject.ramattack.net/freebsdpxehowto.pdf
Thank you very much.
Bye!!
------------------------------
Message: 4
Date: Sun, 11 Apr 2010 20:15:42 +0200
From: Egoitz Aurrekoetxea Aurre <ego...@ramattack.net>
Subject: Re: FreeBSD PXE installation howto
To: freeb...@freebsd.org
Message-ID: <82A8CE62-656D-4365...@ramattack.net>
Content-Type: text/plain; charset=iso-8859-1
Hi Erik,
I see.... you know like the first place you look is at handbook... yep I have read too you're guide sometime... seems another way of doing the same...
One suggest only... this is not correct...
# cd /usr/src/sys/boot
# make -DLOADER_TFTP_SUPPORT=YES
has no effect... in the Makefiles you will see it's checking a variable independently of the value the variable contains... and in a make line setting a define AFAIK has not much sense...
Make will do all with the default nfs support.
Bye!!
El 11/04/2010, a las 18:56, Erik Norgaard escribió:
> On 11/04/10 18:21, Egoitz Aurrekoetxea Aurre wrote:
>
>> I'm working on a project for setting up a freebsd installation server with pxe. When I started I see the doc was a bit old-fashioned... so I started looking at some blogs... freebsd doc that could help me understanding the whole process and so on... finally I have ended looking at source code of some involved parts like sysintall, boot stages and so on.... for understanding all properly for setting up this service. I have written a documentation that if you see it to be ok... (it seems to be working fine) perhaps, would be nice to appear in handbook or in some official documentation site... So if you see something that should be done in another way... or some point wich you consider it's wrong... please make me know and I'll correct it. The url in wich you could fetch the pdf file is : http://postfixquotareject.ramattack.net/freebsdpxehowto.pdf
>
> I don't know which docs you have seen, I recently updated my guide to FBSD8, www.locolomo.org/howto/pxeboot/
>
> BR, Erik
>
> --
> Erik Nørgaard
> Ph: +34.666334818/+34.915211157 http://www.locolomo.org
------------------------------
Message: 5
Date: Sun, 11 Apr 2010 20:31:30 +0100 (IST)
From: "Conall O'Brien" <con...@conall.net>
Subject: docs/145631: References to ttyd0 serial devices in handbook
need to be updated for FreeBSD 8.0
To: FreeBSD-gn...@FreeBSD.org
Message-ID: <201004111931...@daedalus.asclepian.ie>
>Number: 145631
>Category: docs
>Synopsis: References to ttyd0 serial devices in handbook need to be updated for FreeBSD 8.0
>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: Sun Apr 11 19:40:00 UTC 2010
>Closed-Date:
>Last-Modified:
>Originator: Conall O'Brien
>Release: FreeBSD 7.2-STABLE amd64
>Organization:
>Environment:
System: FreeBSD daedalus.asclepian.ie 7.2-STABLE FreeBSD 7.2-STABLE #9: Sat Jun 27 00:05:26 IST 2009 ro...@daedalus.asclepian.ie:/usr/src/obj/usr/src/sys/DAEDALUS amd64
>Description:
Handbook's handbook/serialconsole-setup.html page refers to ttyd0 as
the default serial console of a system. As of FreeBSD 8.0, ttyu0 is the
default port, so the docs need to be updated to handle both devices.
>How-To-Repeat:
Read serialconsole-setup.html while configuring a fresh install of
FreeBSD 8.0
>Fix:
grep through the handbook and other docs for references to ttyd0 and
update to refer to ttyd0 or ttyu0 (FreeBSD 8.0 and higher)
>Release-Note:
>Audit-Trail:
>Unformatted:
------------------------------
Message: 6
Date: Mon, 12 Apr 2010 07:03:27 +0200
From: Egoitz Aurrekoetxea Aurre <ego...@ramattack.net>
Subject: Re: FreeBSD PXE installation howto
To: freeb...@freebsd.org
Message-ID: <BDC6BAA3-190B-42B5...@ramattack.net>
Content-Type: text/plain; charset=iso-8859-1
Hi all,
Erik when you specify there -DLOADER_TFTP_SUPPORT=YES this is a directive for the preprocessor in the time it is looking wich source code to compile... but it should be entered in cc line... not in make... just do one check.... save the output of that make to a file and you will see that nfs support is going to be used... check too the makefiles... you will see that makefiles to enter the -DLOADER_TFTP_SUPPORT they are checking if make variable LOADER_TFTP_SUPPORT is initialized to something... you could perhaps do...
export CPPFLAGS="-DLOADER_TFTP_SUPPORT=YES"
make
but not the way you said... and I won't do things this way too... just use makefile for this kind of flags... as I say basically...
make LOADER_TFTP_SUPPORT=YES
try this and the way you set and you will see different output of make.
The suggested parts to correct corrected...
tftpd run from inetd is the same as base system really... so this is done....
Fbsd1 I'll try to improve this aspects of the doc... yep perhaps I have explained a little for me :)...
Well if any developer could check too this howto, will be just fine :)
Thankss a lot :) to all.
bye!!!
El 12/04/2010, a las 06:33, Fbsd1 escribió:
> Egoitz Aurrekoetxea Aurre wrote:
> > Hi,
> >
> > I'm working on a project for setting up a freebsd installation server > with pxe.
> > When I started I see the doc was a bit old-fashioned. so I started
> > looking at some blogs. freebsd doc that could help me understanding
> > the whole process and so on. Finally I have ended looking at source
> > code of some involved parts like sysintall, boot stages and so on for
> > understanding all properly for setting up this service.
> > I have written a documentation that if you see it to be ok. (it seems
> > to be working fine) perhaps, would be nice to appear in handbook or
> > in some official documentation site. So if you see something that
> > should be done in another way, or some point which you consider is
> > wrong, please make me know and I'll correct it.
> >
> > The url in which you could fetch the pdf file is :
> >
> > http://postfixquotareject.ramattack.net/freebsdpxehowto.pdf
> >
> > Thank you very much.
> >
> >
> >
>
>
> Thank you Egoitz for volunteering to write documentation for the handbook. The following criticism is not meant in a negative way.
>
> I can not evaluate the correctness of the technical procedure you write about, but I am going to talk about your style of written documentation.
>
> What you have written is what I would call a personal short cut outline of the steps you did. So next time you need to do the same thing again you have something to follow and remind youself of what you did. This only has value to you because you have in your head all the understanding and background information of why you are doing these steps.
>
> When writhing documentation for the handbook you must keep in mind that the reader has no idea what you are talking about. So your document has to contain right at the beginning an explanation of what PBX is, how you are using it, what other programs you are using and why. The general rule is MORE details is better then LESS details. Explain what and why for each step.
>
> Know that the reader will execute every command just as you wrote them, so test the sequence of commands to verify it's correct. This is a very important step in writing documentation. It has to produce the exact results you say it will.
>
> Adding or replacing a section in the handbook takes a long time. Maybe 1 or 2 RELEASE versions before it gets added. The documentation department moves slowly. The technical stuff in the document is reviewed by some of the developers for accuracy.
>
> I know what I am talking about because I am the author of the handbook Firewall section. I am willing to help and guide you through this process. I suggest you put your document in Microsoft Word, add the background information and step details talked about above, and then attach it to an email for my review.
>
> Let me know if you choose to proceed.
>
> Joe
>
>
>
>
>
>
>
>
>
------------------------------
Message: 7
Date: Mon, 12 Apr 2010 09:30:18 GMT
From: Joe Barbish <fb...@a1poweruser.com>
Subject: docs/145644: Add artical about creating manpage from scratch
To: freebsd-gn...@FreeBSD.org
Message-ID: <201004120930....@www.freebsd.org>
>Number: 145644
>Category: docs
>Synopsis: Add artical about creating manpage from scratch
>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 Apr 12 09:40:01 UTC 2010
>Closed-Date:
>Last-Modified:
>Originator: Joe Barbish
>Release: 8.0 release
>Organization:
none
>Environment:
>Description:
The FreeBSD documentation environment is lacking instructions on how to
create “man page” manuals. I have written a ‘How To’ document titled;
Creating a manpage from scratch. It’s too big for the FAQ list,
but fits nicely into the article size.
You can read it online at
http://www.daemonforums.org/showthread.php?t=4602
I am donating it to the FreeBSD document team with the hopes you will take
the text file I have attached and convert it to SGML and add it as an article.
>How-To-Repeat:
>Fix:
Patch attached with submission follows:
Creating a manpage from scratch.
What is a manpage?
The FreeBSD documentation manuals system is comprised on many manuals that
are intended to by displayed on-line from the command line using the
“man” command. Every Base RELEASE command has it’s own manual as well as
the commands introduced by the ports system. The layout of the manual is
standardized by the use of groff_mdoc(7) documentation macro markup
language. The files containing the source for each manual are located in
the /usr/share/man/manX/ directory tree, where the X of manX is one of
the following sections.
Under FreeBSD 8.0, the following sections are defined:
1 FreeBSD General Commands Manual
2 FreeBSD System Calls Manual
3 FreeBSD Library Functions Manual
4 FreeBSD Kernel Interfaces Manual
5 FreeBSD File Formats Manual
6 FreeBSD Games Manual
7 FreeBSD Miscellaneous Information Manual
8 FreeBSD System Manager's Manual
9 FreeBSD Kernel Developer's Manual
So you would see this
/usr/share/man/man1/
/usr/share/man/man2/
/usr/share/man/man3/
/usr/share/man/man4/
/usr/share/man/man5/
/usr/share/man/man6/
/usr/share/man/man7/
/usr/share/man/man8/
/usr/share/man/man9/
Manual File Naming Standard.
There is a standardized naming convention in place for manpage files:
name.X.gz
Where name = the name of the command being documented.
X = the manual section its in from the above path list.
gz = means the file has been compress with gzip(1) command.
The file itself is a text file with the documentation being prefixed and
sometimes enclosed with formatting macros from groff_mdoc(7) markup language.
Take note; The macro text file should contain no blank lines in it.
Creating The Manual Source File.
The best way to get started is to just copy a man page from the base system
and edit it to taste. As the system administrator I always login as user
root so the following command examples and manual sample are developed in /root.
The manual for the jail(8) command will be used as the template for my new manual ezjail.
cd /root
cp /usr/share/man/man8/jail.8.gz /root/ # get my own copy of file.
mv jail.8.gz ezjail.8.gz # rename the file.
gunzip ezjail.8.gz # unzip the file.
ee ezjail.8 # edit the text file.
The start of the text file has the standard FreeBSD copyright comments. Delete all
these comments. All groff_mdoc(7) documentation line macros begin with an period “.”
Then an uppercase letter followed by a lowercase letter. The following discussion
has comments to the right and these comments are not part of the macro command syntax,
but put here to explain what’s happening. So starting the new ezjail manpage text file is;
# Setup the manual format section
.Dd July 22, 2010 # Date displayed on center of last line.
.Dt EZJAIL 8 # Name and section of this manpage,
# has to be in uppercase letters,
# displays left & right corners of top line.
.Os # Displays RELEASE version in left & right
# corners of last line.
# This is how the man command displays the first and last lines
EZJAIL(8) FreeBSD System Manager's Manual EZJAIL(8)
FreeBSD 8.0 July 22, 2010 FreeBSD 8.0
# Setup the highlighted first two lines you see.
.Sh NAME # Section header name in uppercase letters.
.Nm ezjail # Name to display.
.Nd “description” # short description of command.
# This is what is displayed by the man command
NAME
ezjail -- description
# Setup the command syntax section
.Sh SYNOPSIS # Section header name in uppercase letters.
.Nm # Display saved name.
# The following macros format the flags in bold and/or with brackets
# and with white background / black letters.
.Op Fl dhi
.Op Fl J Ar jid_file
.Op Fl l u Ar username | Fl U Ar username
.Op Fl c | m
.Br
.Nm
.Op Fl hi
.Op Fl n Ar jailname
.Op Fl J Ar jid_file
.Op Fl s Ar securelevel
.Op Fl l u Ar username | Fl U Ar username
.Op Ar path hostname [ip[,..]] command ...
# This is what is displayed by the man command
SYNOPSIS
jail [-dhi] [-J jid_file] [-l -u username | -U username] [-c | -m]
jail [-hi] [-n jailname] [-J jid_file] [-s securelevel]
[-l -u username | -U username] [path hostname [ip[,..]]
# This is a real pain to play with. So I used the short method like this.
It displays the text just as written with no bold and no white boxes.
This method is simpler and makes the manpage easier to read without all
those white-boxed words. The layout will be the same as what is shown above.
.Sh SYNOPSIS
.Nm
[-dhi] [-J jid_file] [-l -u username | -U username] [-c | -m]
.Nm
[-hi] [-n jailname] [-J jid_file] [-s securelevel]
.Br # this means next line
[-l -u username | -U username] [path hostname [ip[,..]]
# The description section with the meaning of the flags comes next.
.Sh DESCRIPTION
The jail utility creates a new jail or modifies an existing jail,
imprisoning the current process (and future descendants) inside it.
.Pp # blank line position holder.
The options are as follows:
.Bl -tag -width indent # indent everything that follows.
.It Fl d # adds the dash and bolds them both.
Allow making changes to a dying jail.
.It Fl h # adds the dash and bolds them both.
Resolve the host.hostname parameter (or hostname) and add
all IP addresses returned by the resolver to the list of
ip addresses for this jail.
.El # end the indented section.
# This is what is displayed by the man command
DESCRIPTION
The jail utility creates a new jail or modifies an existing jail,
optionally imprisoning the current process (and future
descendants) inside it.
The options are as follows:
-d Allow making changes to a dying jail.
-h Resolve the host.hostname parameter (or hostname) and add
all IP addresses returned by the resolver to the list of
ip addresses for this jail.
# The short method I used like this.
.Sh DESCRIPTION
The jail utility creates a new jail or modifies an existing jail,
imprisoning the current process (and future descendants) inside it.
.Pp # blank line position holder
The options are as follows:
.Bl -tag -width indent # indent everything that follows
.It \fB-d\fR # adds the bold
Allow making changes to a dying jail.
.It \fB-h\fR # adds the bold
Resolve the host.hostname parameter (or hostname) and add
all IP addresses returned by the resolver to the list of
ip addresses for this jail
.El # End the indented section.
# This is an example of the special enclosure macro that bolds any word
or words its wrapped around. \fB 10.0.10.2 \fR will display as 10.0.10.2
General format notes.
The manual standards specify the following sections as mandatory.
.Sh NAME
.Sh SYNOPSIS
.Sh DESCRIPTION
Which have been covered all ready. At the end of the manpage there are a
few more mandatory sections required in all manpages.
.Sh FILES # Section header name in uppercase letters.
/usr/local/etc/ezjail.conf
.br
/usr/local/bin/ezjail
.Sh SEE ALSO # Section header name in uppercase letters.
.Xr killall 1 ,
.Xr lsvfs 1 ,
.Xr newaliases 1 ,
# or you could just say
killall(1), lsvfs(1), newaliases(1)
.Sh AUTHORS # Section header name in uppercase letters.
.An Tom Jones
.Aq tjo...@home.com
# or you could just use
Tom Jones tjo...@home.com
Now in between the Description section and the FILES section you can make
as many sections as you want by using the .Sh macro. Example
.Sh USAGE EXAMPLES
.Sh HISTORY
.Sh BACKGROUND
Testing method.
I have found it convenient to use 2 sessions for testing.
In the F1 session I cycle through these commands
gunzip ezjail.8.gz
ee ezjail.8
gzip ezjail.8
cp ezjail.8.gz /usr/local/man/man8/
And then from the F2 session I issue
man 8 ezjail
I can then read my new manpage looking for format, word spacing, sentence
wrapping, and verifying that all special bolding is working.
Swapping between the edit of the manpage text source on the F1 session
and the view of the displayed manpage on the F2 session making any changes
to the source as necessary. Then ending the edit, gziping the file and
coping it to it’s running location. Where in the F2 session I enter ctlr-c
to close the old manpage view and then man 8 ezjail again to view the
just update version.
I have found that sometimes it’s convenient to render the groff source as
pure ascii text. Groff will complain if the raw macro source has blank
lines in it and gives you the line number of macros with syntax errors.
groff -mdoc -Tascii ezjail.8 | more
groff -mdoc -Tascii ezjail.8 > ezjail.raw.text
gzcat ezjail.8.gz | groff -mdoc -Tascii | less
>Release-Note:
>Audit-Trail:
>Unformatted:
------------------------------
Message: 8
Date: Mon, 12 Apr 2010 11:06:07 GMT
From: FreeBSD bugmaster <bugm...@FreeBSD.org>
Subject: Current unassigned doc problem reports
To: FreeBSD doc list <freeb...@FreeBSD.org>
Message-ID: <201004121106....@freefall.freebsd.org>
(Note: an HTML version of this report is available at
http://www.freebsd.org/cgi/query-pr-summary.cgi?category=doc .)
The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.
S Tracker Resp. Description
--------------------------------------------------------------------------------
o docs/145644 doc Add artical about creating manpage from scratch
o docs/145631 doc [handbook] References to ttyd0 serial devices in handb
o docs/145362 doc [patch] articles/version-guide: russian translation ne
o docs/145361 doc [patch] articles/solid-state: russian translation need
o docs/145360 doc [patch] articles/releng: russian translation needs to
o docs/145359 doc [patch] articles/relaydelay: russian translation needs
o docs/145358 doc [patch] articles/problem-reports: russian translation
o docs/145357 doc [patch] articles/pr-guidelines: russian translation ne
o docs/145356 doc [patch] articles/ipsec-must: russian translation needs
o docs/145355 doc [patch] articles/fbsd-from-scratch: russian translatio
o docs/145354 doc [patch] articles/checkpoint: russian translation needs
o docs/145353 doc [patch] articles/5-roadmap: russian translation needs
o docs/145251 doc [patch] iscsi_initiator.4 man page formatting and synt
o docs/145227 doc [patch] freebsd-update(8): Update to more recent relea
o docs/145069 doc Dialup firewalling with FreeBSD article out dated.
o docs/145067 doc FAQ remove all reference to floppy installs
o docs/145066 doc FAQ update for new uart dev names for serial port.
o docs/145059 doc [patch] 7.3 relnotes erroneously describes new ps -p o
o docs/145051 doc [patch] missing closing parenthesis in 7.3 relnotes ar
o docs/145037 doc [geom] [request] the geom manual sections are sorted i
p docs/145031 doc [patch] setkey.8 typo
p docs/145030 doc [patch] whitespace fix for sysinstall.8
o docs/145028 doc Handbook Section 2.10.1 Network Device Configuration i
o docs/145027 doc Remove all sysinstall references to floppy and slip &
o docs/145025 doc Handbook Figure 2-27. Choose Installation Media is out
o docs/145023 doc handbook section 2.4 Starting the Installation is outd
o docs/145021 doc handbook section 2.3 Pre-installation Tasks is outdate
o docs/144986 doc [pf] pf.conf example should show allowing icmp through
o docs/144893 doc [handbook] handbook section 18.16.1 Disk Encryption wi
o docs/144881 doc [patch][handbook] Reference to incorrect manual page
o docs/144880 doc [patch] ipmon(8): Missing BUGS section header
o docs/144818 doc all mailinglist archives dated 19970101 contain traili
o docs/144630 doc domainname(1) manpage contains old information
o docs/144614 doc [patch] [mfi] add IBM ServeRAID M5015 SAS/SATA to list
o docs/144543 doc [handbook] IPFW doc change
o docs/144537 doc Missing _mdconfig_list and _mdconfig2_list explanation
o docs/144534 doc [patch] fdescfs(5) and devfs(5) both provide /dev/fd/{
o docs/144516 doc Remove obsolete sections from handbook
o docs/144515 doc [handbook] Expand handbook Table of contents
o docs/144498 doc boot(8) should reference uart(4) instead of sio(4)
o docs/144488 doc share/examples/etc/make.conf: contains dangerous examp
o docs/144408 doc [patch] update makefs(8) (remove device option)
p docs/144407 doc Duplicate argument entry in mtree(8)
o docs/143944 doc strtod(3) mentions "bug noted below" with no such note
o docs/143926 doc FAQ entry 16.3 out of date
o docs/143850 doc procfs(5) manpage for status > controlling terminal is
o docs/143694 doc man8/uathload: the switch -d is mandatory, [] around i
o docs/143603 doc error in nanobsd article
o docs/143472 doc gethostname(3) references undefined value: HOST_NAME_M
o docs/143454 doc [patch] mtree.8 man page errors
o docs/143416 doc [handbook] IPFW handbook page issues
o docs/143408 doc man filedesc(9) is missing
o docs/143342 doc Developer's handbook contains stale information.
o docs/143330 doc [patch] strtonum(3) does undocumented clobbering of er
o docs/143094 doc [patch] handbook/filesystems: russian translation is m
o docs/143041 doc [patch] doc/en__US.ISO8859-1 refers to slip, slirp, sl
o docs/142917 doc top(1) man page does not include information about VCS
o docs/142437 doc [request] Errata Notices Index missing
o docs/142418 doc [PATCH] newfs_msdos(8) doc fix
a docs/142341 doc jail(8): Jail escape when cwd is moved from the host s
o docs/142243 doc Netcat (nc(1)) manual mistake
o docs/142168 doc ld(1): ldd(1) not mentioned in ld(1) manpage
o docs/141316 doc ntpd(8): ntpd does not honor -d flag
o docs/140918 doc [handbook] update 8.0 handbook about serial port /dev
s docs/140847 doc [request] add documentation on ECMP and new route args
o docs/140814 doc [handbook][patch] Chapter 15 - Jails: add section on c
o docs/140703 doc [patch] add xorg-minimal as alternative for X11 Distri
o docs/140495 doc [patch] /etc/rc.conf.d is not documented in rc.conf(5)
o docs/140474 doc signal(3) missing reference to NSIG
o docs/140458 doc [patch] Grammar fix for to{upper,lower}(3)
o docs/140457 doc [patch] Grammar fix for isspace(3)
o docs/140444 doc [patch] New Traditional Chinese translation of custom-
o docs/140435 doc ls(1), section STANDARD: the -A is exception from POSI
o docs/140375 doc [UPDATE] Updated zh_TW.Big5/articles/nanobsd
o docs/140369 doc [patch] src/contrib/pf/man/pf.4
o docs/140075 doc release notes: missing word "NOT", which changes all t
o docs/139682 doc [PATCH] dialog(1) man page does not mention radiolist
o docs/139336 doc [request] ZFS documentation suggestion
o docs/139165 doc gssapi.3 man page out of sync with between crypto and
o docs/139153 doc [patch] the hier(7) man page needs to be updated
o docs/139018 doc translation of submitting.sgml from docproj/submitting
o docs/138887 doc manpage ports(7) incorrect
o docs/138845 doc Exceeding kern.ipc.maxpipekva refers to tuning(7) whic
o docs/138663 doc system(3) man page confuses users about "return value
o docs/138485 doc bpf(4) and ip(4) man pages missing important corner ca
o docs/138206 doc [patch] ntp(1): not enabled function, and false manual
o docs/137762 doc [handbook] proposed: mention "make delete-old" in sec
o docs/136712 doc [handbook] [patch] draft new section on gmirror per pa
o docs/136666 doc [handbook] Configure serial port for remote kernel deb
o docs/136035 doc ftpchroot(5) omits an important option
p docs/136029 doc MALLOC_PRODUCTION knob should be mentioned somewhere,
o docs/135999 doc Netgear GS105v3 should be added to list of switches th
o docs/135676 doc FAQ About The FreeBSD Mailing Lists doesn't mention ma
o docs/135516 doc pax(1) manual not mentioning chflags unawareness
o docs/135475 doc [patch] jot(1) manpage and behaviour differ
o docs/135165 doc [patch] make(1) fixes: punctuation, typos, tweaks
o docs/134376 doc pthread(3): pthread manpages don't mention that PTHREA
o docs/134226 doc /usr/share/examples/ftpd/ftpd.conf does not exist.
o docs/134222 doc installation failure of japanese docs
o docs/134123 doc The RUNQUEUE(9) man page is out of date
o docs/133567 doc [patch] doc/Makefile switch to csup
o docs/133245 doc french handbook 27.3.5 amd.map amd.conf
o docs/133118 doc [patch] Error in getopt (1) manual EXAMPLES section
o docs/132884 doc [request] No manpage for SYSINIT and SYSUNINIT
o docs/132839 doc [patch] Fix example script in ldap-auth article
o docs/132718 doc [handbook] Information about adding a new mirror is ou
o docs/132311 doc [patch] man5/nsmb.conf.5
o docs/132260 doc dhcpd(8) pid not stored in documented location
o docs/132190 doc EPERM explanation for send(2), sendto(2), and sendmsg(
o docs/132113 doc [handbook] Update handbook jails creation
o docs/131918 doc [patch] Fixes for the BPF(4) man page
o docs/131684 doc [patch] articles/linux-comparison: replace Addenda by
o docs/131590 doc [patch] whitespace-only change of developers-handbook/
o docs/130364 doc Man page for top needs explanation of CPU states
o docs/130238 doc nfs.lockd man page doesn't mention NFSLOCKD option or
o docs/129671 doc New TCP chapter for Developer's Handbook (from rwatson
o docs/129464 doc using packages system
o docs/129095 doc ipfw(8): Can not check that packet originating/destine
o docs/128524 doc No geom documentation for loading gjournal(8)
s docs/128356 doc [request] add Firefox plugin for FreeBSD manual pages
o docs/127908 doc [patch] readdir(3) error documentation
s docs/127844 doc Example code skeleton_capture_n.c in meteor(4) manpage
o docs/127253 doc Error in Handbook: http://www.freebsd.org/doc/en/books
o docs/126590 doc [patch] Write routine called forever in Sample Echo Ps
o docs/126484 doc libc function res-zonscut2 is not documented
o docs/125921 doc lpd(8) talks about blocks in minfree while it is KB in
o docs/125751 doc man 3 pthread_getschedparam section ERRORS incomplete
f docs/122052 doc minor update on handbook section 20.7.1
o docs/121952 doc Handbook chapter on Network Address Translation wrong
o docs/121871 doc ftpd does not interpret configuration files as documen
o docs/121585 doc [handbook] Wrong multicast specification
o docs/121565 doc dhcp-options(5) manpage incorrectly formatted omitting
s docs/121541 doc [request] no man pages for wlan_scan_ap
o docs/121312 doc RELNOTES_LANG breaks release if not en_US.ISO8859-1
o docs/121173 doc [patch] mq_getattr(2): mq_flags mistakenly described a
s docs/120917 doc [request]: Man pages mising for thr_xxx syscalls
o docs/120539 doc Inconsistent ipfw's man page
o docs/120456 doc ath(4) needs to specify requirement on wlan_scan_sta
o docs/120125 doc [patch] Installing FreeBSD 7.0 via serial console and
o docs/120024 doc resolver(5) and hosts(5) need updated for IPv6
o docs/119545 doc books/arch-handbook/usb/chapter.sgml formatting
a docs/119536 doc a few typos in French handbook (basics)
o docs/118902 doc [patch] wrong signatures in d2i_RSAPublicKey man pages
o docs/118332 doc man page for top does not describe STATE column wait e
o docs/118214 doc close(2) error returns incomplete
o docs/118020 doc ipfilter(4): man pages query for man 4 ipfilter return
o docs/117747 doc 'break' system call needs a man page
o docs/116480 doc sysctl(3) description of kern.file no longer applies s
o docs/116116 doc mktemp (3) re/move note
o docs/116080 doc PREFIX is documented, but not the more important LOCAL
o docs/115065 doc [patch] sync ps.1 with p_flag and keywords
o docs/114371 doc [patch] [ip6] rtadvd.con(5) should show how to adverti
o docs/114139 doc mbuf(9) has misleading comments on M_DONTWAIT and M_TR
o docs/113194 doc [patch] [request] crontab.5: handling of day-in-month
o docs/112804 doc groff(1) command should be called to explicitly use "p
o docs/112682 doc Handbook GEOM_GPT explanation does not provide accurat
o docs/111425 doc Missing chunks of text in historical manpages
o docs/111265 doc [request] Clarify how to set common shell variables
o docs/111147 doc hostapd.conf is not documented
o docs/110999 doc carp(4) should document unsupported interface types
o docs/110692 doc wi(4) man page doesn't say WPA is not supported
o docs/110376 doc [patch] add some more explanations for the iwi/ipw fir
o docs/110253 doc [patch] rtprio(1): remove processing starvation commen
o docs/110062 doc [patch] mount_nfs(8) fails to mention a failure condit
o docs/110061 doc [patch] tuning(7) missing reference to vfs.read_max
o docs/109981 doc No manual entry for post-grohtml
o docs/109977 doc No manual entry for ksu
o docs/109973 doc No manual entry for c++filt
o docs/109972 doc No manual entry for zless/bzless
f docs/109226 doc [request] No manual entry for sntp
o docs/109201 doc [request]: manual for callbootd
a docs/108980 doc list of missing man pages
o docs/108101 doc /boot/default/loader.conf contains an incorrect commen
o docs/107924 doc [usb67] usbd(8) does not call detach
o docs/106135 doc [request] articles/vinum needs to be updated
o docs/105608 doc fdc(4) debugging description staled
o docs/104879 doc Howto: Listen to IMA ADPCM .wav files on FreeBSD box
o docs/102719 doc [patch] ng_bpf(4) example leads to unneeded promiscuos
o docs/101464 doc sync ru_RU.KOI8-R/articles/portbuild/article.html with
o docs/100196 doc man login.conf does explain not "unlimited"
o docs/99506 doc FreeBSD Handbook addition: IPv6 Server Settings
o docs/98974 doc Missing tunables in loader(8) manpage
o docs/98115 doc Missing parts after rendering handbook to RTF format
o docs/96207 doc Comments of a sockaddr_un structure could confuse one
o docs/94625 doc [patch] growfs man page -- document "panic: not enough
o docs/92626 doc jail manpage should mention disabling some periodic sc
o docs/91506 doc ndis(4) man page should be more specific about support
o docs/91174 doc [REQUEST] Handbook: Addition of Oracle 9i installation
o docs/91149 doc read(2) can return EINVAL for unaligned access to bloc
o docs/88512 doc [patch] mount_ext2fs(8) man page has no details on lar
o docs/87936 doc Handbook chapter on NIS/YP lacks good information on a
o docs/87857 doc ifconfig(8) wireless options order matters
o docs/86342 doc bikeshed entry of Handbook is wrong
o docs/85128 doc [patch] loader.conf(5) autoboot_delay incompletly desc
o docs/84956 doc [patch] intro(5) manpage doesn't mention API coverage
o docs/84932 doc new document: printing with an Epson ALC-3000N on Free
o docs/84670 doc [patch] tput(1) manpage missing ENVIRONMENT section wi
o docs/84317 doc fdp-primer doesn't show class=USERNAME distinctively
o docs/84271 doc [patch] compress(1) doesn't warn about nasty link hand
o docs/83820 doc getino(3) manpage not installed
o docs/78480 doc Networked printer setup unnecessarily complex in handb
o docs/63570 doc [patch] Language cleanup for the Handbook's DNS sectio
o docs/61605 doc [request] Improve documentation for i386 disk geometry
o docs/61301 doc [patch] Manpage patch for aue(4) to enable HomePNA fun
o docs/59835 doc ipfw(8) man page does not warn about accepted but mean
o docs/59477 doc Outdated Info Documents at http://docs.freebsd.org/inf
o docs/59044 doc [patch] doc.docbook.mk does not properly handle a sour
s docs/54752 doc bus_dma explained in ISA section in Handbook: should b
o docs/53751 doc bus_dma(9) incorrectly documents BUS_DMA_ALLOCNOW
o docs/53596 doc Updates to mt(1) manual page
o docs/53271 doc bus_dma(9) fails to document alignment restrictions
o docs/50211 doc [patch] doc.docbook.mk: fix textfile creation
o docs/48101 doc [patch] add documentation on the fixit disk to the FAQ
o docs/43823 doc [patch] update to environ(7) manpage
o docs/41089 doc pax(1) -B option does not mention interaction with -z
o docs/40423 doc Keyboard(4)'s definition of parameters to GETFKEY/SETF
o docs/38982 doc [patch] developers-handbook/Jail fix
o docs/38556 doc EPS file of beastie, as addition to existing examples
s docs/35678 doc docproj Makefiles for web are broken for paths with sp
s docs/33589 doc [patch] to doc.docbook.mk to post process .tex files.
a docs/30008 doc [patch] French softupdates document should be translat
o docs/27605 doc [patch] Cross-document references (<olink>)
o docs/26286 doc *printf(3) etc should gain format string warnings
o docs/24786 doc missing FILES descriptions in sa(4)
s docs/20028 doc ASCII docs should reflect <emphasis> tags in the sourc
225 problems total.
------------------------------
End of freebsd-doc Digest, Vol 368, Issue 1
*******************************************