os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

- XMLify English books

Browse source 
Approved by:	doceng (implicit)
This commit is contained in:
Gabor Kovesdan 2012-06-21 16:04:40 +00:00
parent e6b69c3357
commit 3cdf4e4922
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/projects/sgml2xml/; revision=39087
105 changed files with 1876 additions and 1550 deletions
en_US.ISO8859-1/books
arch-handbook
book.sgml
boot
chapter.sgml
chapters.ent
driverbasics
chapter.sgml
isa
chapter.sgml
jail
chapter.sgml
kobj
chapter.sgml
locking
chapter.sgml
mac.ent
mac
chapter.sgml
newbus
chapter.sgml
pccard
chapter.sgml
pci
chapter.sgml
scsi
chapter.sgml
smp
chapter.sgml
sound
chapter.sgml
sysinit
chapter.sgml
usb
chapter.sgml
vm
chapter.sgml
bibliography
book.sgml
corp-net-guide
book.sgml
design-44bsd
book.sgml
dev-model
book.sgmlchapters.ent
developers-handbook
book.sgmlchapters.ent
introduction
chapter.sgml
ipv6
chapter.sgml
kernelbuild
chapter.sgml
kerneldebug
chapter.sgml
l10n
chapter.sgml
policies
chapter.sgml
secure
chapter.sgml
sockets
chapter.sgml
testing
chapter.sgml
tools
chapter.sgml
x86
chapter.sgml
faq
book.sgml
fdp-primer
book.sgmlchapters.ent
doc-build
chapter.sgml
examples
appendix.sgml
overview
chapter.sgml
psgml-mode
chapter.sgml
see-also
chapter.sgml
sgml-markup
chapter.sgml
sgml-primer
chapter.sgml
structure
chapter.sgml
stylesheets
chapter.sgml
the-website
chapter.sgml
tools
chapter.sgml
translations
chapter.sgml
writing-style
chapter.sgml
handbook
Makefile
advanced-networking
chapter.sgml
audit
chapter.sgml
basics
chapter.sgml
bibliography
chapter.sgml
book.sgml
boot
chapter.sgml
bsdinstall
chapter.sgml
chapters.entcolophon.sgml
config
chapter.sgml
cutting-edge
chapter.sgml
desktop
chapter.sgml
disks
chapter.sgml
dtrace
chapter.sgml
eresources
chapter.sgml
filesystems
chapter.sgml
firewalls
chapter.sgml
geom
chapter.sgml
install
chapter.sgml
introduction
chapter.sgml
jails
chapter.sgml
kernelconfig
chapter.sgml
l10n
chapter.sgml
linuxemu
chapter.sgml
mac
chapter.sgml
mail
chapter.sgml
mirrors
chapter.sgml
multimedia
chapter.sgml
network-servers
chapter.sgml
pgpkeys
chapter.sgml
ports
chapter.sgml
ppp-and-slip
chapter.sgml
preface
preface.sgml
printing
chapter.sgml
security
chapter.sgml
serialcomms
chapter.sgml
txtfiles.ent
users
chapter.sgml
vinum
chapter.sgml
virtualization
chapter.sgml
x11
chapter.sgml
pmake
answers
chapter.sgml
basics
chapter.sgml
book.sgmlchapters.ent
glossary
glossary.sgml
Show more

32
en_US.ISO8859-1/books/arch-handbook/book.sgml
View file

@ -1,21 +1,21 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!DOCTYPE book PUBLIC "-//FreeBSD//DTD DocBook XML V4.2-Based Extension//EN"
"../../../share/sgml/freebsd42.dtd" [
<!ENTITY % entities PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Entity Set//EN" "../../share/sgml/entities.ent">
%entities;
<!ENTITY % chapters SYSTEM "chapters.ent">
%chapters;
<!ENTITY % mac-entities SYSTEM "mac.ent">
%mac-entities;
]>
<!--
The FreeBSD Documentation Project
$FreeBSD$
-->
<!DOCTYPE BOOK PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
<!ENTITY % books.ent PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Books Entity Set//EN">
%books.ent;
<!ENTITY % chapters SYSTEM "chapters.ent">
%chapters;
<!ENTITY % mac-entities SYSTEM "mac.ent">
%mac-entities;
<!ENTITY % chap.index "IGNORE">
]>
<book>
<book lang='en'>
<bookinfo>
<title>&os; Architecture Handbook</title>
@ -34,8 +34,10 @@
<holder>The FreeBSD Documentation Project</holder>
</copyright>
&bookinfo.trademarks;
&bookinfo.legalnotice;
&trademarks;
&legalnotice;
<releaseinfo>$FreeBSD$</releaseinfo>
<abstract>
<para>Welcome to the &os; Architecture Handbook. This manual is a
@ -173,6 +175,6 @@
</bibliography>
</part>
<![ %chap.index; [ &chap.index; ]]>
&chap.index;
</book>

1
en_US.ISO8859-1/books/arch-handbook/boot/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!--
The FreeBSD Documentation Project

8
en_US.ISO8859-1/books/arch-handbook/chapters.ent
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="iso-8859-1"?>
<!--
Creates entities for each chapter in the FreeBSD Architecture
Handbook. Each entity is named chap.foo, where foo is the value
@ -9,6 +10,8 @@
$FreeBSD$
-->
<!ENTITY % chap.index "IGNORE">
<!-- Part one - Kernel -->
<!ENTITY chap.boot SYSTEM "boot/chapter.sgml">
<!ENTITY chap.kobj SYSTEM "kobj/chapter.sgml">
@ -30,4 +33,7 @@
<!ENTITY chap.pccard SYSTEM "pccard/chapter.sgml">
<!-- Part three - Appendices -->
<!ENTITY chap.index SYSTEM "index.sgml">
<![%chap.index[
<!ENTITY chap.index SYSTEM "index.sgml">
]]>
<!ENTITY chap.index "">

1
en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!--
The FreeBSD Documentation Project

1
en_US.ISO8859-1/books/arch-handbook/isa/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!--
The FreeBSD Documentation Project

1
en_US.ISO8859-1/books/arch-handbook/jail/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!--
The FreeBSD Documentation Project

1
en_US.ISO8859-1/books/arch-handbook/kobj/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!--
The FreeBSD Documentation Project

1
en_US.ISO8859-1/books/arch-handbook/locking/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!--
The FreeBSD Documentation Project
The FreeBSD SMP Next Generation Project

11
en_US.ISO8859-1/books/arch-handbook/mac.ent
View file

@ -1,10 +1,11 @@
<?xml version="1.0" encoding="iso-8859-1"?>
<!-- $FreeBSD$ -->
<!ENTITY mac.mpo "mpo">
<!ENTITY mac.thead '
<colspec colname="first" colwidth="0">
<colspec colwidth="0">
<colspec colname="last" colwidth="0">
<colspec colname="first" colwidth="0"/>
<colspec colwidth="0"/>
<colspec colname="last" colwidth="0"/>
<thead>
<row>
@ -30,12 +31,12 @@
</row>
<row>
<entry><parameter>element_name</parameter>
<entry><parameter>element_name</parameter></entry>
<entry>Name of the policy whose label should be externalized</entry>
</row>
<row>
<entry><parameter>sb</parameter>
<entry><parameter>sb</parameter></entry>
<entry>String buffer to be filled with a text representation of
label</entry>
</row>

8
en_US.ISO8859-1/books/arch-handbook/mac/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!--
Copyright (c) 2002-2005 Networks Associates Technology, Inc.
All rights reserved.
@ -335,6 +336,7 @@
order to avoid violating the kernel lock order or risking
lock recursion. This will maintain policy locks as leaf
locks in the global lock order, helping to avoid deadlock.</para>
</sect2>
<sect2 id="mac-framework-kernel-arch-registration">
<title>Policy Registration</title>
@ -584,7 +586,7 @@
<para>In addition to these system calls, the
<literal>SIOCSIGMAC</literal> and <literal>SIOCSIFMAC</literal>
network interface ioctls permit the labels on network interfaces to
be retrieved and set.<para>
be retrieved and set.</para>
</sect2>
</sect1>
@ -2778,7 +2780,7 @@ Label destruction o</programlisting>
<tbody>
<row>
<entry namest="first" nameend="last">See <xref
linkend="mac-mpo-create-mount">.</entry>
linkend="mac-mpo-create-mount"/>.</entry>
</row>
</tbody>
</tgroup>
@ -6351,7 +6353,7 @@ Label destruction o</programlisting>
<row>
<entry><parameter>cred</parameter></entry>
<entry morerows="2">See
<xref linkend="mac-mpo-check-vnode-mmap">.</entry>
<xref linkend="mac-mpo-check-vnode-mmap"/>.</entry>
</row>
<row>

1
en_US.ISO8859-1/books/arch-handbook/newbus/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!--
The FreeBSD Documentation Project
$FreeBSD$

1
en_US.ISO8859-1/books/arch-handbook/pccard/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!--
The FreeBSD Documentation Project

1
en_US.ISO8859-1/books/arch-handbook/pci/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!--
The FreeBSD Documentation Project

9
en_US.ISO8859-1/books/arch-handbook/scsi/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!--
The FreeBSD Documentation Project
@ -1224,9 +1225,9 @@ of the union ccb:</para>
<function>xxx_attach()</function>) the current negotiation
values must be initialized to narrow asynchronous mode, the goal
and current values must be initialized to the maximal values
supported by controller.</para></listitem>
supported by controller.</para>
<listitem><para><emphasis>XPT_GET_TRAN_SETTINGS</emphasis> - get values of
<para><emphasis>XPT_GET_TRAN_SETTINGS</emphasis> - get values of
SCSI transfer settings</para>
<para>This operations is the reverse of
@ -1234,11 +1235,11 @@ of the union ccb:</para>
ccb_trans_setting cts</quote> with data as requested by the flags
CCB_TRANS_CURRENT_SETTINGS or CCB_TRANS_USER_SETTINGS (if both
are set then the existing drivers return the current
settings). Set all the bits in the valid field.</para></listitem>
settings). Set all the bits in the valid field.</para>
<indexterm><primary>BIOS</primary></indexterm>
<listitem><para><emphasis>XPT_CALC_GEOMETRY</emphasis> - calculate logical
<para><emphasis>XPT_CALC_GEOMETRY</emphasis> - calculate logical
(BIOS) geometry of the disk</para>
<para>The arguments are transferred in the instance <quote>struct

3
en_US.ISO8859-1/books/arch-handbook/smp/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!--
The FreeBSD Documentation Project
The FreeBSD SMP Next Generation Project
@ -60,7 +61,7 @@
to make other programs multi-threaded. These include mutexes,
shared/exclusive locks, semaphores, and condition variables. For
the definitions of these and other SMP-related terms, please see
the <xref linkend="smp-glossary"> section of this article.</para>
the <xref linkend="smp-glossary"/> section of this article.</para>
</sect1>
<sect1 id="smp-lock-fundamentals">

23
en_US.ISO8859-1/books/arch-handbook/sound/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!--
The FreeBSD Documentation Project
@ -296,12 +297,12 @@
<programlisting> static void *
xxxchannel_init(kobj_t obj, void *data,
struct snd_dbuf *b, struct pcm_channel *c, int dir)<co id="co-chinit-params">
struct snd_dbuf *b, struct pcm_channel *c, int dir)<co id="co-chinit-params"/>
{
struct xxx_info *sc = data;
struct xxx_chinfo *ch;
...
return ch;<co id="co-chinit-return">
return ch;<co id="co-chinit-return"/>
}</programlisting>
<calloutlist>
@ -344,7 +345,7 @@
sound format.</para>
<programlisting> static int
xxxchannel_setformat(kobj_t obj, void *data, u_int32_t format)<co id="co-chsetformat-params">
xxxchannel_setformat(kobj_t obj, void *data, u_int32_t format)<co id="co-chsetformat-params"/>
{
struct xxx_chinfo *ch = data;
...
@ -400,7 +401,7 @@
{
struct xxx_chinfo *ch = data;
...
return blocksize;<co id="co-chsetblocksize-return">
return blocksize;<co id="co-chsetblocksize-return"/>
}</programlisting>
<calloutlist>
@ -423,7 +424,7 @@
operations in the driver.</para>
<programlisting> static int
xxxchannel_trigger(kobj_t obj, void *data, int go)<co id="co-chtrigger-params">
xxxchannel_trigger(kobj_t obj, void *data, int go)<co id="co-chtrigger-params"/>
{
struct xxx_chinfo *ch = data;
...
@ -500,7 +501,7 @@
<programlisting> struct pcmchan_caps *
xxxchannel_getcaps(kobj_t obj, void *data)
{
return &amp;xxx_caps;<co id="co-chgetcaps-return">
return &amp;xxx_caps;<co id="co-chgetcaps-return"/>
}</programlisting>
<calloutlist>
@ -551,7 +552,7 @@
[Initialize hardware]
[Set appropriate bits in v for play mixers]<co id="co-mxini-sd">
[Set appropriate bits in v for play mixers]<co id="co-mxini-sd"/>
mix_setdevs(m, v);
[Set appropriate bits in v for record mixers]
mix_setrecdevs(m, v)
@ -583,11 +584,11 @@
<programlisting> static int
xxxmixer_set(struct snd_mixer *m, unsigned dev,
unsigned left, unsigned right)<co id="co-mxset-params">
unsigned left, unsigned right)<co id="co-mxset-params"/>
{
struct sc_info *sc = mix_getdevinfo(m);
[set volume level]
return left | (right &lt;&lt; 8);<co id="co-mxset-return">
return left | (right &lt;&lt; 8);<co id="co-mxset-return"/>
}</programlisting>
<calloutlist>
@ -615,14 +616,14 @@
recording source device.</para>
<programlisting> static int
xxxmixer_setrecsrc(struct snd_mixer *m, u_int32_t src)<co id="co-mxsr-params">
xxxmixer_setrecsrc(struct snd_mixer *m, u_int32_t src)<co id="co-mxsr-params"/>
{
struct xxx_info *sc = mix_getdevinfo(m);
[look for non zero bit(s) in src, set up hardware]
[update src to reflect actual action]
return src;<co id="co-mxsr-return">
return src;<co id="co-mxsr-return"/>
}</programlisting>
<calloutlist>

1
en_US.ISO8859-1/books/arch-handbook/sysinit/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!--
The FreeBSD Documentation Project

1
en_US.ISO8859-1/books/arch-handbook/usb/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!--
The FreeBSD Documentation Project

1
en_US.ISO8859-1/books/arch-handbook/vm/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!--
The FreeBSD Documentation Project

18
en_US.ISO8859-1/books/bibliography/book.sgml
View file

@ -1,17 +1,18 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!DOCTYPE book PUBLIC "-//FreeBSD//DTD DocBook XML V4.2-Based Extension//EN"
"../../../share/sgml/freebsd42.dtd" [
<!ENTITY % entities PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Entity Set//EN" "../../share/sgml/entities.ent">
%entities;
<!ENTITY bibliography SYSTEM "../../../share/sgml/bibliography.sgml">
]>
<!--
The FreeBSD Documentation Project
$FreeBSD$
-->
<!DOCTYPE BOOK PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
<!ENTITY % books.ent PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Books Entity Set//EN">
%books.ent;
<!ENTITY bibliography SYSTEM "../../../share/sgml/bibliography.sgml">
]>
<book>
<book lang='en'>
<bookinfo>
<title>FreeBSD Bibliography</title>
@ -24,6 +25,7 @@
<holder>The FreeBSD Documentation Project</holder>
</copyright>
<releaseinfo>$FreeBSD$</releaseinfo>
</bookinfo>
&bibliography;

28
en_US.ISO8859-1/books/corp-net-guide/book.sgml
View file

@ -1,12 +1,14 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!DOCTYPE book PUBLIC "-//FreeBSD//DTD DocBook XML V4.2-Based Extension//EN"
"../../../share/sgml/freebsd42.dtd" [
<!ENTITY % entities PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Entity Set//EN" "../../share/sgml/entities.ent">
%entities;
]>
<!-- $FreeBSD$ -->
<!-- FreeBSD Documentation Project -->
<!DOCTYPE book PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
<!ENTITY % books.ent PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Books Entity Set//EN">
%books.ent;
]>
<book>
<book lang='en'>
<bookinfo>
<title>The FreeBSD Corporate Networker's Guide</title>
@ -46,6 +48,8 @@
and a Q&amp;A forum, and is available at
<ulink url="http://www.freebsd-corp-net-guide.com/"></ulink>.</para>
</legalnotice>
<releaseinfo>$FreeBSD$</releaseinfo>
</bookinfo>
<chapter id="printserving" label="8">
@ -279,7 +283,7 @@
<mediaobject>
<imageobject>
<imagedata fileref="08-01" format="EPS">
<imagedata fileref="08-01" format="EPS"/>
</imageobject>
<textobject>
@ -319,7 +323,7 @@
<mediaobject>
<imageobject>
<imagedata fileref="08-02" format="EPS">
<imagedata fileref="08-02" format="EPS"/>
</imageobject>
<textobject>
@ -367,7 +371,7 @@
<mediaobject>
<imageobject>
<imagedata fileref="08-03" format="EPS">
<imagedata fileref="08-03" format="EPS"/>
</imageobject>
<textobject>
@ -409,7 +413,7 @@
<mediaobject>
<imageobject>
<imagedata fileref="08-04" format="EPS">
<imagedata fileref="08-04" format="EPS"/>
</imageobject>
<textobject>
@ -507,7 +511,7 @@
<mediaobject>
<imageobject>
<imagedata fileref="08-05" format="EPS">
<imagedata fileref="08-05" format="EPS"/>
</imageobject>
<textobject>
@ -2512,7 +2516,7 @@ lpnobanner|local line printer, PostScript, no banner:\
<mediaobject>
<imageobject>
<imagedata fileref="08-06" format="EPS">
<imagedata fileref="08-06" format="EPS"/>
</imageobject>
<textobject>

58
en_US.ISO8859-1/books/design-44bsd/book.sgml
View file

@ -1,12 +1,14 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!DOCTYPE book PUBLIC "-//FreeBSD//DTD DocBook XML V4.2-Based Extension//EN"
"../../../share/sgml/freebsd42.dtd" [
<!ENTITY % entities PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Entity Set//EN" "../../share/sgml/entities.ent">
%entities;
]>
<!-- $FreeBSD$ -->
<!-- FreeBSD Documentation Project -->
<!DOCTYPE book PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
<!ENTITY % books.ent PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Books Entity Set//EN">
%books.ent;
]>
<book>
<book lang='en'>
<bookinfo>
<title>The Design and Implementation of the 4.4BSD Operating System</title>
@ -60,6 +62,8 @@
Information about <ulink url="http://www.mckusick.com/courses/">BSD
courses</ulink> is available from Kirk McKusick.</para>
</legalnotice>
<releaseinfo>$FreeBSD$</releaseinfo>
</bookinfo>
<chapter id="overview" label="2">
@ -176,14 +180,14 @@
additional operating-system services.
In contemporary research operating systems -- such as
Chorus
<xref linkend="biblio-rozier">,
<xref linkend="biblio-rozier"/>,
Mach
<xref linkend="biblio-accetta">,
<xref linkend="biblio-accetta"/>,
Tunis
<xref linkend="biblio-ewens">,
<xref linkend="biblio-ewens"/>,
and the
V Kernel
<xref linkend="biblio-cheriton"> --
<xref linkend="biblio-cheriton"/> --
this division of functionality is more than just a logical one.
Services such as filesystems and networking protocols are
implemented as client application processes of the nucleus or kernel.</para>
@ -195,7 +199,7 @@
Ken Thompson had no memory mapping,
and thus made no hardware-enforced distinction
between user and kernel space
<xref linkend="biblio-ritchie">.
<xref linkend="biblio-ritchie"/>.
A message-passing system could have been implemented as readily
as the actually implemented model of kernel and user processes.
The monolithic kernel was chosen for simplicity and performance.
@ -532,7 +536,7 @@
</tgroup>
</table>
<para><xref linkend="table-mach-indep"> summarizes the machine-independent software that constitutes the
<para><xref linkend="table-mach-indep"/> summarizes the machine-independent software that constitutes the
4.4BSD kernel for the HP300.
The numbers in column 2 are for lines of C source code,
header files, and assembly language.
@ -540,7 +544,7 @@
programming language;
less than 2 percent is written in
assembly language.
As the statistics in <xref linkend="table-mach-dep"> show,
As the statistics in <xref linkend="table-mach-dep"/> show,
the machine-dependent software, excluding
HP/UX
and device support,
@ -676,7 +680,7 @@
<mediaobject>
<imageobject>
<imagedata fileref="fig1" format="EPS">
<imagedata fileref="fig1" format="EPS"/>
</imageobject>
<textobject>
@ -697,7 +701,7 @@
</mediaobject>
</figure>
<para>The process lifecycle is depicted in <xref linkend="fig-process-lifecycle">.
<para>The process lifecycle is depicted in <xref linkend="fig-process-lifecycle"/>.
A process may create a new process that is a copy of the original
by using the
<emphasis>fork</emphasis>
@ -968,9 +972,9 @@
Over 40 companies and research groups participated
in the discussions leading to the revised architecture
that was described in the Berkeley Software Architecture Manual
<xref linkend="biblio-mckusick-1">.
<xref linkend="biblio-mckusick-1"/>.
Several of the companies have implemented the revised interface
<xref linkend="biblio-gingell">.</para>
<xref linkend="biblio-gingell"/>.</para>
<para>Once again, time pressure prevented 4.3BSD from providing an
implementation of the interface.
@ -1004,7 +1008,7 @@
Consequently, the virtual-memory system was completely replaced in 4.4BSD.
The 4.4BSD virtual-memory system
is based on the Mach 2.0 VM system
<xref linkend="biblio-tevanian">.
<xref linkend="biblio-tevanian"/>.
with updates from Mach 2.5 and Mach 3.0.
It features
efficient support for sharing,
@ -1107,7 +1111,7 @@
and
<emphasis>free</emphasis>
that provide memory allocation to application programs
<xref linkend="biblio-mckusick-2">.
<xref linkend="biblio-mckusick-2"/>.
Like the C library interface,
the allocation routine takes a parameter specifying the
size of memory that is needed.
@ -1146,7 +1150,7 @@
<emphasis>I/O stream</emphasis>.
It is this single common data form that makes the
characteristic UNIX tool-based approach work
<xref linkend="biblio-kernighan">.
<xref linkend="biblio-kernighan"/>.
An I/O stream from one program can be fed as input
to almost any other program.
(This kind of traditional UNIX
@ -1662,7 +1666,7 @@
<mediaobject>
<imageobject>
<imagedata fileref="fig2" format="EPS">
<imagedata fileref="fig2" format="EPS"/>
</imageobject>
<textobject>
@ -1696,7 +1700,7 @@
</mediaobject>
</figure>
<para>a small one is shown in <xref linkend="fig-small-fs">.
<para>a small one is shown in <xref linkend="fig-small-fs"/>.
Directories may contain subdirectories, and there is no inherent
limitation to the depth with which directory nesting may occur.
To protect the consistency of the filesystem, the kernel
@ -2040,7 +2044,7 @@
<listitem>
<para>The log-structured filesystem,
based on the Sprite operating-system design
<xref linkend="biblio-rosenblum"></para>
<xref linkend="biblio-rosenblum"/></para>
</listitem>
<listitem>
<para>A memory-based filesystem</para>
@ -2127,7 +2131,7 @@
NFS
protocol, although the implementation was done independently
from the protocol specification
<xref linkend="biblio-macklem">.
<xref linkend="biblio-macklem"/>.
The
NFS
protocol is described in
@ -2577,7 +2581,7 @@
</biblioentry>
<biblioentry id="biblio-kernighan">
<abbrev>Kernighan & Pike, 1984</abbrev>
<abbrev>Kernighan &amp; Pike, 1984</abbrev>
<title>The UNIX Programming Environment</title>
@ -2634,7 +2638,7 @@
</biblioentry>
<biblioentry id="biblio-mckusick-2">
<abbrev>McKusick & Karels, 1988</abbrev>
<abbrev>McKusick &amp; Karels, 1988</abbrev>
<biblioset relation="article">
<title>Design of a General Purpose Memory Allocator for the 4.3BSD
@ -2728,7 +2732,7 @@
</biblioentry>
<biblioentry id="biblio-rosenblum">
<abbrev>Rosenblum & Ousterhout, 1992</abbrev>
<abbrev>Rosenblum &amp; Ousterhout, 1992</abbrev>
<biblioset relation="article">
<title>The Design and Implementation of a Log-Structured File

223
en_US.ISO8859-1/books/dev-model/book.sgml
View file

@ -1,3 +1,12 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!DOCTYPE book PUBLIC "-//FreeBSD//DTD DocBook XML V4.2-Based Extension//EN"
"../../../share/sgml/freebsd42.dtd" [
<!ENTITY % entities PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Entity Set//EN" "../../share/sgml/entities.ent">
%entities;
<!ENTITY % chapters SYSTEM "chapters.ent">
%chapters;
]>
<!--
- Copyright (c) 2002-2005 Niklas Saers
- All rights reserved.
@ -26,15 +35,7 @@
- $FreeBSD$
-->
<!DOCTYPE book PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
<!ENTITY % books.ent PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Books Entity Set//EN">
%books.ent;
<!ENTITY % chapters SYSTEM "chapters.ent">
%chapters;
<!ENTITY % chap.index "IGNORE">
]>
<book>
<book lang='en'>
<bookinfo>
<title>A project model for the FreeBSD Project</title>
<author>
@ -78,6 +79,8 @@
<revremark>Initial review by interviewees</revremark>
</revision>
</revhistory>
<releaseinfo>$FreeBSD$</releaseinfo>
</bookinfo>
<preface id="foreword">
@ -91,7 +94,7 @@
<para>
This goes hand-in-hand with Brooks' law that <quote>adding
another person to a late project will make it later</quote>
since it will increase the communication needs <xref linkend="brooks">.
since it will increase the communication needs <xref linkend="brooks"/>.
A project model
is a tool to reduce the communication needs.
</para>
@ -100,7 +103,7 @@
will provide such a project model and is donated to the
FreeBSD Documentation project where it can evolve together with
the project so that it can at any point in time reflect the way
the project works. It is based on <citation><xref linkend="thesis"></citation>.
the project works. It is based on <citation><xref linkend="thesis"/></citation>.
</para>
<para>
@ -133,7 +136,7 @@
<para>
A project model is a means to reduce the communications overhead in
a project. As shown by <citation><xref linkend="brooks"></citation>, increasing the
a project. As shown by <citation><xref linkend="brooks"/></citation>, increasing the
number of project participants increases the communication in the
project exponentionally. FreeBSD has during the past few years
increased both its mass of active users and committers, and the
@ -148,7 +151,7 @@
lawyer-tendencies, and is counter to the technocentricity that
the project so badly needs.</quote>
<citation><xref linkend="bsd-election2002"></citation>.
<citation><xref linkend="bsd-election2002"/></citation>.
This project model is not meant to be a tool to
justify creating impositions for developers, but as a tool to
facilitate coordination.
@ -163,7 +166,7 @@
<para>
The FreeBSD project model will be described as of
July 1st, 2004. It is based on the Niels J&oslash;rgensen's paper
<citation><xref linkend="jorgensen2001"></citation>,
<citation><xref linkend="jorgensen2001"/></citation>,
FreeBSD's official documents,
discussions on FreeBSD mailing lists and interviews with
developers.
@ -181,7 +184,7 @@
<para>
<citation><xref
linkend="freebsd-developer-handbook">, Section 1.2 and 1.3</citation>
linkend="freebsd-developer-handbook"/>, Section 1.2 and 1.3</citation>
give the vision and the architectural guidelines for the
project. The vision is <quote>To produce the best UNIX-like
operating system package possible, with due respect to the
@ -200,7 +203,7 @@
<para>
An <quote>activity</quote> is an element of work performed
during the course of a project <citation><xref linkend="ref-pmbok"></citation>.
during the course of a project <citation><xref linkend="ref-pmbok"/></citation>.
It has an output and
leads towards an outcome.
Such an output can either be an input to another
@ -246,7 +249,7 @@
project. Often used more narrowly in reference to an external
deliverable, which is a deliverable that is subject to approval
by the project sponsor or customer</quote> by <citation><xref
linkend="ref-pmbok"></citation>.
linkend="ref-pmbok"/></citation>.
Examples of
outcomes are a piece of software, a decision made or a
report written.
@ -279,7 +282,7 @@
<para>
<figure>
<title>The FreeBSD Project's structure</title>
<graphic fileref="orghierarchy.png" format="PNG">
<graphic fileref="orghierarchy.png" format="PNG"/>
</figure>
</para>
@ -337,7 +340,7 @@
<para>
<figure>
<title>The FreeBSD Project's structure with committers in categories</title>
<graphic fileref="orghierarchy2.png" format="PNG">
<graphic fileref="orghierarchy2.png" format="PNG"/>
</figure>
</para>
<para>
@ -380,11 +383,11 @@
development and maintenance, many being maintainers for
their own part of the code.
Maintainership will
be discussed in the <xref linkend="role-maintainer"> section.
be discussed in the <xref linkend="role-maintainer"/> section.
</para>
<para>
Documentation is handled by <xref linkend="sub-project-documentation">
Documentation is handled by <xref linkend="sub-project-documentation"/>
and includes all documents surrounding the
FreeBSD project, including the web pages. There were during 2004 101
people making commits to the FreeBSD Documentation Project.
@ -411,7 +414,7 @@
application types that are in use on modern computers.
Ports will be discussed further in the section
<xref linkend="sub-project-ports">.
<xref linkend="sub-project-ports"/>.
</para>
@ -431,7 +434,7 @@
<para>
<figure>
<title>J&oslash;rgenssen's model for change integration</title>
<graphic fileref="maintenance.png" format="PNG">
<graphic fileref="maintenance.png" format="PNG"/>
</figure>
</para>
@ -439,7 +442,7 @@
The <quote>development release</quote> is the FreeBSD-CURRENT
("-CURRENT") branch and the <quote>production release</quote>
is the FreeBSD-STABLE branch ("-STABLE")
<citation><xref linkend="jorgensen2001"></citation>.
<citation><xref linkend="jorgensen2001"/></citation>.
</para>
<para>
@ -596,7 +599,7 @@
<para>
<figure>
<title>The FreeBSD release tree</title>
<graphic fileref="branches.png" format="PNG">
<graphic fileref="branches.png" format="PNG"/>
</figure>
</para>
<para>
@ -605,7 +608,7 @@
release is always referred to as -STABLE. In this figure,
-STABLE refers to 4-STABLE while -CURRENT refers to
5.0-CURRENT following 5.0-RELEASE.
<citation><xref linkend="freebsd-releng"></citation>
<citation><xref linkend="freebsd-releng"/></citation>
</para>
<para>
@ -677,7 +680,7 @@
<para>
<figure>
<title>The overall development model</title>
<graphic fileref="freebsd-code-model.png" format="PNG">
<graphic fileref="freebsd-code-model.png" format="PNG"/>
</figure>
</para>
<para>
@ -712,7 +715,7 @@
<para>
Many committers have a special area of responsibility. These
roles are called hats
<citation><xref linkend="bsd-hats"></citation>.
<citation><xref linkend="bsd-hats"/></citation>.
These hats can
be either project roles, such as public relations officer, or
maintainer for a certain area of the
@ -745,7 +748,7 @@
developer, as an author, by sending problem reports, or in
other ways contributing to the progress of the project. A
contributor has no special privileges in the FreeBSD project.
<citation><xref linkend="freebsd-contributors"></citation>
<citation><xref linkend="freebsd-contributors"/></citation>
</para>
</section>
@ -760,7 +763,7 @@
twelve months. These are not referred to as committers. -->
A committer has made a commit within the past 12 months.
<citation><xref linkend="freebsd-bylaws"></citation>
<citation><xref linkend="freebsd-bylaws"/></citation>
An active committer is a committer
who has made an average of one commit per month during that time.
</para>
@ -777,7 +780,7 @@
changes in the code should be made
<!--
Also, since
<xref linkend="sub-project-ports"> is allowed to give commit
<xref linkend="sub-project-ports"/> is allowed to give commit
privileges without approval from core, a committer who has
gained his privileges through contributing to the ports
sub-project should be careful and
@ -858,7 +861,7 @@
<para>
<figure>
<title>Overview of official hats</title>
<graphic fileref="hats-overview.png" format="PNG">
<graphic fileref="hats-overview.png" format="PNG"/>
</figure>
</para>
@ -875,7 +878,7 @@
project architect">
<title>Documentation project manager</title>
<para>
<xref linkend="sub-project-documentation">
<xref linkend="sub-project-documentation"/>
architect is responsible for
defining and following up documentation goals for the
committers in the Documentation project.
@ -896,7 +899,7 @@
<title>CVSup Mirror Site Coordinator</title>
<para>
The CVSup Mirror Site Coordinator coordinates all the
<xref linkend="role-cvsup-sitemaint">s to ensure that they
<xref linkend="role-cvsup-sitemaint"/>s to ensure that they
are distributing current versions of the software, that they
have the capacity to update themselves when major updates
are in progress, and making it easy for the general public
@ -914,7 +917,7 @@
The Internationalisation hat is responsible for coordinating
the localisation efforts of the FreeBSD kernel and userland
utilities. The translation effort are coordinated by
<xref linkend="sub-project-documentation">. The
<xref linkend="sub-project-documentation"/>. The
Internationalisation hat should suggest and promote standards
and guidelines for writing and maintaining the software in a
fashion that makes it easier to translate.
@ -987,7 +990,7 @@
</itemizedlist>
Further information about the development process is
available in the <xref linkend="process-release-engineering"> section.
available in the <xref linkend="process-release-engineering"/> section.
</para>
<para id="role-releng" xreflabel="Release Engineering Team">
@ -1046,7 +1049,7 @@
vulnerabilities may leak out to people with malicious
intent before a patch is available, only the Security
Officer, consisting of an officer, a deputy and two
<xref linkend="role-core"> members, receive sensitive
<xref linkend="role-core"/> members, receive sensitive
information about security issues. However, to create or
implement a patch, the Security Officer has the Security
Officer Team <email>security-team@FreeBSD.org</email> to
@ -1069,7 +1072,7 @@
<para>
The Source Repository Manager is the only one who is allowed
to directly modify the repository without using the
<xref linkend="tool-cvs"> tool.
<xref linkend="tool-cvs"/> tool.
It is his/her
responsibility to ensure that technical problems that arise in the
repository are resolved quickly. The source repository
@ -1087,11 +1090,11 @@
<title>Election Manager</title>
<para>
The Election Manager is responsible for the
<xref linkend="process-core-election"> process. The manager
<xref linkend="process-core-election"/> process. The manager
is responsible for running and maintaining the election
system, and is the final authority should minor unforeseen
events happen in the election process. Major unforeseen
events have to be discussed with the <xref linkend="role-core">
events have to be discussed with the <xref linkend="role-core"/>
</para>
<para>
Hat held only during elections.
@ -1106,7 +1109,7 @@
for the overall structure of the primary web site and the
system it is running upon. The management needs to
coordinate the content with
<xref linkend="sub-project-documentation"> and acts as
<xref linkend="sub-project-documentation"/> and acts as
maintainer for the <quote>www</quote> tree.
</para>
@ -1120,7 +1123,7 @@
<title>Ports Manager</title>
<para>
The Ports Manager acts as a liaison between
<xref linkend="sub-project-ports">
<xref linkend="sub-project-ports"/>
and the core project, and
all requests from the project should go to the ports manager.
@ -1140,7 +1143,7 @@
<para>
The Standards hat is responsible for ensuring that FreeBSD
complies with the standards it is committed to <!-- (covered in
<xref linkend="standardsguidelines">) -->, keeping up to date
<xref linkend="standardsguidelines"/>) -->, keeping up to date
on the development of these standards and notifying
FreeBSD developers of important changes that allows them to take a
proactive role and decrease the time between a standards
@ -1296,7 +1299,7 @@
<para>
A CVSup Mirror Site Admin has accesses to a server that he/she
uses to mirror the CVS repository. The admin works with the
<xref linkend="role-cvsup-coordinator"> to ensure the site
<xref linkend="role-cvsup-coordinator"/> to ensure the site
remains up-to-date and is following the general policy of
official mirror sites.
</para>
@ -1356,14 +1359,14 @@
</para>
<para>
When a contributor is given his commit bit, a <xref linkend="tool-pgp">-signed email is sent
from either <xref linkend="role-core-secretary">,
<xref linkend="role-ports-manager"> or nik@freebsd.org to both
When a contributor is given his commit bit, a <xref linkend="tool-pgp"/>-signed email is sent
from either <xref linkend="role-core-secretary"/>,
<xref linkend="role-ports-manager"/> or nik@freebsd.org to both
admins@freebsd.org, the assigned mentor, the new committer and
core confirming the approval of a new account. The mentor then
gathers a password line, <xref linkend="tool-ssh2"> public key and PGP key from the
gathers a password line, <xref linkend="tool-ssh2"/> public key and PGP key from the
new committer and sends them to <xref
linkend="role-admin">. When the new account is created, the
linkend="role-admin"/>. When the new account is created, the
mentor activates the commit bit and guides the new committer
through the rest of the initial process.
</para>
@ -1371,7 +1374,7 @@
<para>
<figure>
<title>Process summary: adding a new committer</title>
<graphic fileref="proc-add-committer.png" format="PNG">
<graphic fileref="proc-add-committer.png" format="PNG"/>
</figure>
</para>
@ -1393,7 +1396,7 @@
months. However, it is not until after 18 months of inactivity
have passed
that commit privileges are eligible to be revoked.
<citation><xref linkend="freebsd-expiration-policy"></citation>
<citation><xref linkend="freebsd-expiration-policy"/></citation>
There are, however, no
automatic procedures for doing this.
For reactions concerning commit privileges not triggered by
@ -1403,7 +1406,7 @@
<para>
<figure>
<title>Process summary: removing a committer</title>
<graphic fileref="proc-rm-committer.png" format="PNG">
<graphic fileref="proc-rm-committer.png" format="PNG"/>
</figure>
</para>
@ -1426,27 +1429,27 @@
<orderedlist>
<listitem><para>
<xref linkend="role-core">
<xref linkend="role-core"/>
</para></listitem>
<listitem><para>
<xref linkend="role-contributor">
<xref linkend="role-contributor"/>
</para></listitem>
<listitem><para>
<xref linkend="role-committer">
<xref linkend="role-committer"/>
</para></listitem>
<listitem><para>
<xref linkend="role-maintainer">
<xref linkend="role-maintainer"/>
</para></listitem>
<listitem><para>
<xref linkend="role-mentor">
<xref linkend="role-mentor"/>
</para></listitem>
</orderedlist>
</para>
<para>
<citation><xref linkend="freebsd-bylaws"></citation>
<citation><xref linkend="freebsd-expiration-policy"></citation>
<citation><xref linkend="freebsd-new-account"></citation>
<citation><xref linkend="freebsd-bylaws"/></citation>
<citation><xref linkend="freebsd-expiration-policy"/></citation>
<citation><xref linkend="freebsd-new-account"/></citation>
</para>
</section>
@ -1456,7 +1459,7 @@
<title>Adding/Removing an official CVSup Mirror</title>
<para>
A <xref linkend="tool-cvsup"> mirror is a replica of the
A <xref linkend="tool-cvsup"/> mirror is a replica of the
official CVSup master that contains all the up-to-date source
code for all the branches in the FreeBSD project, ports and
documentation.
@ -1464,7 +1467,7 @@
<para>
Adding an official CVSup mirror starts with the potential
<xref linkend="role-cvsup-sitemaint"> installing the
<xref linkend="role-cvsup-sitemaint"/> installing the
<quote>cvsup-mirror</quote> package. Having done this and
updated the source code with a mirror site, he now runs a
fairly recent unofficial CVSup mirror.
@ -1474,12 +1477,12 @@
Deciding he has a stable environment, the processing
power, the network capacity and the
storage capacity to run an official mirror, he mails the
<xref linkend="role-cvsup-coordinator"> who decides whether
<xref linkend="role-cvsup-coordinator"/> who decides whether
the mirror should become an official mirror or not.
</para>
<para>
In making this decision, the <xref linkend="role-cvsup-coordinator">
In making this decision, the <xref linkend="role-cvsup-coordinator"/>
has to determine whether that geographical area needs
another mirror site, if the mirror administrator has the
skills to run it reliably, if the network bandwidth is
@ -1488,7 +1491,7 @@
</para>
<para>
If <xref linkend="role-cvsup-coordinator"> decides that the
If <xref linkend="role-cvsup-coordinator"/> decides that the
mirror should become an official mirror, he obtains an
authentication key from the mirror admin that he installs so
the mirror admin can update the mirror from the master server.
@ -1497,7 +1500,7 @@
<para>
<figure>
<title>Process summary: adding a CVSup mirror</title>
<graphic fileref="proc-add-cvsup.png" format="PNG">
<graphic fileref="proc-add-cvsup.png" format="PNG"/>
</figure>
</para>
@ -1516,10 +1519,10 @@
Tools used in this process:
<itemizedlist>
<listitem><para>
<xref linkend="tool-cvsup">
<xref linkend="tool-cvsup"/>
</para></listitem>
<listitem><para>
<xref linkend="tool-ssh2">
<xref linkend="tool-ssh2"/>
</para></listitem>
</itemizedlist>
</para>
@ -1528,10 +1531,10 @@
Hats involved in this process:
<itemizedlist>
<listitem><para>
<xref linkend="role-cvsup-coordinator">
<xref linkend="role-cvsup-coordinator"/>
</para></listitem>
<listitem><para>
<xref linkend="role-cvsup-sitemaint">
<xref linkend="role-cvsup-sitemaint"/>
</para></listitem>
</itemizedlist>
</para>
@ -1565,7 +1568,7 @@
<para>
When a change is committed to a part of the source that
has been contributed from an outside
<xref linkend="role-vendor">,
<xref linkend="role-vendor"/>,
the maintainer should
ensure that the patch is contributed back to the
vendor. This is in line with the open source
@ -1601,7 +1604,7 @@
<para>
<figure>
<title>Process summary: A committer commits code</title>
<graphic fileref="proc-commit.png" format="PNG">
<graphic fileref="proc-commit.png" format="PNG"/>
</figure>
</para>
@ -1625,7 +1628,7 @@
<para>
<figure>
<title>Process summary: A contributor commits code</title>
<graphic fileref="proc-contrib.png" format="PNG">
<graphic fileref="proc-contrib.png" format="PNG"/>
</figure>
</para>
@ -1640,23 +1643,23 @@
Hats included in this process are:
<orderedlist>
<listitem><para>
<xref linkend="role-committer">
<xref linkend="role-committer"/>
</para></listitem>
<listitem><para>
<xref linkend="role-contributor">
<xref linkend="role-contributor"/>
</para></listitem>
<listitem><para>
<xref linkend="role-vendor">
<xref linkend="role-vendor"/>
</para></listitem>
<listitem><para>
<xref linkend="role-reviewer">
<xref linkend="role-reviewer"/>
</para></listitem>
</orderedlist>
</para>
<para>
<citation><xref linkend="freebsd-committer"></citation>
<citation><xref linkend="jorgensen2001"></citation>
<citation><xref linkend="freebsd-committer"/></citation>
<citation><xref linkend="jorgensen2001"/></citation>
</para>
</section>
@ -1725,7 +1728,7 @@
<para>
<figure>
<title>Process summary: Core elections</title>
<graphic fileref="proc-elections.png" format="PNG">
<graphic fileref="proc-elections.png" format="PNG"/>
</figure>
</para>
@ -1742,13 +1745,13 @@
Hats in core elections are:
<itemizedlist>
<listitem><para>
<xref linkend="role-core">
<xref linkend="role-core"/>
</para></listitem>
<listitem><para>
<xref linkend="role-committer">
<xref linkend="role-committer"/>
</para></listitem>
<listitem><para>
<xref linkend="role-election-manager">
<xref linkend="role-election-manager"/>
</para></listitem>
</itemizedlist>
@ -1757,9 +1760,9 @@
<para>
<citation><xref linkend="freebsd-bylaws"></citation>
<citation><xref linkend="bsd-election2002"></citation>
<citation><xref linkend="freebsd-election"></citation>
<citation><xref linkend="freebsd-bylaws"/></citation>
<citation><xref linkend="bsd-election2002"/></citation>
<citation><xref linkend="freebsd-election"/></citation>
</para>
</section>
@ -1769,7 +1772,7 @@
<para>
Within the project there are sub-projects that are working on
new features. These projects are generally done by one person
<citation><xref linkend="jorgensen2001"></citation>.
<citation><xref linkend="jorgensen2001"/></citation>.
Every project is free to
organise development as it sees fit. However, when the project
is merged to the -CURRENT branch it must follow the project
@ -1790,7 +1793,7 @@
someone's responsibility are collected on TODO-lists unless someone
volunteers to take the responsibility. All
requests, their distribution and follow-up are
handled by the <xref linkend="tool-gnats"> tool.
handled by the <xref linkend="tool-gnats"/> tool.
</para>
<para>
@ -1879,7 +1882,7 @@
<para>
The main bulk of work that is put into the FreeBSD project is
maintenance. <citation><xref
linkend="jorgensen2001"></citation>
linkend="jorgensen2001"/></citation>
has made a figure
showing the life cycle of changes.
</para>
@ -1887,7 +1890,7 @@
<para>
<figure>
<title>J&oslash;rgenssen's model for change integration</title>
<graphic fileref="maintenance.png" format="PNG">
<graphic fileref="maintenance.png" format="PNG"/>
</figure>
</para>
@ -1945,7 +1948,7 @@
<para>
Problem reports are sent to an email address where it
is inserted into the GNATS maintenance database. A
<xref linkend="role-bugbuster">
<xref linkend="role-bugbuster"/>
classifies the problem and sends it to the
correct group or maintainer within the project. After someone
has taken responsibility for the report, the report is being
@ -1956,7 +1959,7 @@
originator may be asked to try it out. Finally, the working patch
is integrated into the project, and documented if
applicable. It there goes through the regular maintenance
cycle as described in section <xref linkend="model-maintenance">.
cycle as described in section <xref linkend="model-maintenance"/>.
These are the states a problem report can be in:
open, analyzed, feedback, patched, suspended and closed. The
suspended state is for when further progress is not possible
@ -1967,7 +1970,7 @@
<para>
<figure>
<title>Process summary: problem reporting</title>
<graphic fileref="proc-pr.png" format="PNG">
<graphic fileref="proc-pr.png" format="PNG"/>
</figure>
</para>
@ -1985,20 +1988,20 @@
The roles included in this process are:
<orderedlist>
<listitem><para>
<xref linkend="role-problem-originator">
<xref linkend="role-problem-originator"/>
</para></listitem>
<listitem><para>
<xref linkend="role-maintainer">
<xref linkend="role-maintainer"/>
</para></listitem>
<listitem><para>
<xref linkend="role-bugbuster">
<xref linkend="role-bugbuster"/>
</para></listitem>
</orderedlist>
</para>
<para>
<citation><xref linkend="freebsd-handle-pr"></citation>.
<citation><xref linkend="freebsd-send-pr"></citation>
<citation><xref linkend="freebsd-handle-pr"/></citation>.
<citation><xref linkend="freebsd-send-pr"/></citation>
</para>
</section>
@ -2007,7 +2010,7 @@
<title>Reacting to misbehaviour</title>
<para>
<citation><xref linkend="freebsd-committer"></citation> has a
<citation><xref linkend="freebsd-committer"/></citation> has a
number of rules that committers should follow. However, it
happens that these rules are broken. The following rules exist
in order to be able to react to misbehaviour. They specify what
@ -2030,7 +2033,7 @@
</para></listitem>
</itemizedlist>
<citation><xref linkend="ref-freebsd-trenches"></citation>
<citation><xref linkend="ref-freebsd-trenches"/></citation>
</para>
<para>
@ -2054,10 +2057,10 @@
Hats involved in this process:
<itemizedlist>
<listitem><para>
<xref linkend="role-core">
<xref linkend="role-core"/>
</para></listitem>
<listitem><para>
<xref linkend="role-committer">
<xref linkend="role-committer"/>
</para></listitem>
</itemizedlist>
</para>
@ -2141,7 +2144,7 @@
release process, a release is created with the new version
number, including binary distributions on web sites and the
creation of a CD-ROM images. However, the release is not
considered "really released" until a <xref linkend="tool-pgp">-signed message stating
considered "really released" until a <xref linkend="tool-pgp"/>-signed message stating
exactly that, is sent to the mailing list freebsd-announce; anything
labelled as a "release" before that may well be in-process and
subject to change before the PGP-signed message is sent.
@ -2204,7 +2207,7 @@
<para>
<figure>
<title>Process summary: release engineering</title>
<graphic fileref="proc-releng.png" format="PNG">
<graphic fileref="proc-releng.png" format="PNG"/>
</figure>
</para>
@ -2216,7 +2219,7 @@
<para>
<citation><xref linkend="freebsd-releng"></citation>
<citation><xref linkend="freebsd-releng"/></citation>
</para>
</section>
@ -2290,7 +2293,7 @@
are for internal communication not intended for the general
public. The majority of all the communication in the project goes
through these 85 lists
<citation><xref linkend="ref-bsd-handbook">, Appendix C</citation>.
<citation><xref linkend="ref-bsd-handbook"/>, Appendix C</citation>.
</para>
</section>
@ -2371,12 +2374,12 @@
<para>
<figure id="fig-ports">
<title>Number of ports added between 1996 and 2005</title>
<graphic fileref="portsstatus.png" format="PNG">
<graphic fileref="portsstatus.png" format="PNG"/>
</figure>
</para>
<para>
<xref linkend="fig-ports"> is taken from
<xref linkend="fig-ports"/> is taken from
<ulink url="http://www.freebsd.org/ports/growth/status.png">
the FreeBSD web site</ulink>. It shows the number of ports
available to FreeBSD in the period 1995 to 2005. It looks
@ -2395,7 +2398,7 @@
<para>
Ports has its own core team with the
<xref linkend="role-ports-manager"> as its leader, and this
<xref linkend="role-ports-manager"/> as its leader, and this
team can appoint committers without FreeBSD Core's
approval. Unlike in the FreeBSD Project, where a lot of maintenance
frequently is rewarded with a commit bit, the ports sub-project
@ -2465,7 +2468,7 @@
<para>
Like the ports sub-project, the Documentation project can
appoint documentation committers without FreeBSD Core's approval.
<citation><xref linkend="freebsd-doceng-charter"></citation>.
<citation><xref linkend="freebsd-doceng-charter"/></citation>.
</para>
<para>

1
en_US.ISO8859-1/books/dev-model/chapters.ent
View file

@ -1,2 +1,3 @@
<?xml version="1.0" encoding="iso-8859-1"?>
<!-- $FreeBSD$ -->
<!--!ENTITY chap.references SYSTEM "references.sgml"-->

23
en_US.ISO8859-1/books/developers-handbook/book.sgml
View file

@ -1,17 +1,18 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!DOCTYPE book PUBLIC "-//FreeBSD//DTD DocBook XML V4.2-Based Extension//EN"
"../../../share/sgml/freebsd42.dtd" [
<!ENTITY % entities PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Entity Set//EN" "../../share/sgml/entities.ent">
%entities;
<!ENTITY % chapters SYSTEM "chapters.ent"> %chapters;
]>
<!--
The FreeBSD Documentation Project
$FreeBSD$
-->
<!DOCTYPE BOOK PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
<!ENTITY % books.ent PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Books Entity Set//EN">
%books.ent;
<!ENTITY % chapters SYSTEM "chapters.ent"> %chapters;
<!ENTITY % chap.index "IGNORE">
]>
<book>
<book lang='en'>
<bookinfo>
<title>FreeBSD Developers' Handbook</title>
@ -34,7 +35,7 @@
<holder>The FreeBSD Documentation Project</holder>
</copyright>
&bookinfo.legalnotice;
&legalnotice;
<legalnotice id="trademarks" role="trademarks">
&tm-attrib.freebsd;
@ -48,6 +49,8 @@
&tm-attrib.sun;
&tm-attrib.general;
</legalnotice>
<releaseinfo>$FreeBSD$</releaseinfo>
<abstract>
<para>Welcome to the Developers' Handbook. This manual is a
@ -217,6 +220,6 @@
</part>
<![ %chap.index; [ &chap.index; ]]>
&chap.index;
</book>

8
en_US.ISO8859-1/books/developers-handbook/chapters.ent
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="iso-8859-1"?>
<!--
Creates entities for each chapter in the FreeBSD Developer's
Handbook. Each entity is named chap.foo, where foo is the value
@ -9,6 +10,8 @@
$FreeBSD$
-->
<!ENTITY % chap.index "IGNORE">
<!-- Part one -->
<!ENTITY chap.introduction SYSTEM "introduction/chapter.sgml">
<!ENTITY chap.tools SYSTEM "tools/chapter.sgml">
@ -29,4 +32,7 @@
<!ENTITY chap.x86 SYSTEM "x86/chapter.sgml">
<!-- Part six - Appendices -->
<!ENTITY chap.index SYSTEM "index.sgml">
<![%chap.index;[
<!ENTITY chap.index SYSTEM "index.sgml">
]]>
<!ENTITY chap.index "">

3
en_US.ISO8859-1/books/developers-handbook/introduction/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!--
The FreeBSD Documentation Project
@ -90,7 +91,7 @@
</listitem>
</itemizedlist>
<para>From Scheifler & Gettys: "X Window System"</para>
<para>From Scheifler &amp; Gettys: "X Window System"</para>
</sect1>
<sect1 id="introduction-layout">

1
en_US.ISO8859-1/books/developers-handbook/ipv6/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!--
The FreeBSD Documentation Project

1
en_US.ISO8859-1/books/developers-handbook/kernelbuild/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!--
The FreeBSD Documentation Project

1
en_US.ISO8859-1/books/developers-handbook/kerneldebug/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!--
The FreeBSD Documentation Project

2
en_US.ISO8859-1/books/developers-handbook/l10n/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!--
The FreeBSD Documentation Project
@ -146,6 +147,7 @@
<para><literal>0</literal>, which means that
<envar>LANG</envar> has to be used to open
the proper catalog.</para>
</listitem>
</itemizedlist>
<para>The &man.catopen.3; call returns a catalog identifier of

3
en_US.ISO8859-1/books/developers-handbook/policies/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!--
The FreeBSD Documentation Project
@ -426,7 +427,7 @@ ru@FreeBSD.org - 20 October 2005</programlisting>
<listitem>
<para>All text files
should have <literal>svn:eol-style</literal> set to
<literal>native</literal>.
<literal>native</literal>.</para>
</listitem>
<listitem>

9
en_US.ISO8859-1/books/developers-handbook/secure/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!--
The FreeBSD Documentation Project
@ -47,7 +48,7 @@
<sect1 id="secure-bufferov"><title>Buffer Overflows</title>
<para>Buffer Overflows have been around since the very
beginnings of the Von-Neuman <xref linkend="COD"> architecture.
beginnings of the Von-Neuman <xref linkend="COD"/> architecture.
<indexterm><primary>buffer overflow</primary></indexterm>
<indexterm><primary>Von-Neuman</primary></indexterm>
@ -87,7 +88,7 @@
stack, many implementations also provide a "frame pointer" that
is located near the beginning of a stack frame so that local
variables can more easily be addressed relative to this
value. <xref linkend="COD"> The return address for function
value. <xref linkend="COD"/> The return address for function
<indexterm><primary>frame pointer</primary></indexterm>
<indexterm>
@ -156,7 +157,7 @@
<para>The following example code contains a buffer overflow
designed to overwrite the return address and skip the
instruction immediately following the function call. (Inspired
by <xref linkend="Phrack">)</para>
by <xref linkend="Phrack"/>)</para>
<programlisting>#include &lt;stdio.h&gt;
@ -230,7 +231,7 @@ int main() {
functions guarantee that they will always null terminate the
destination string when given a non-zero length argument. For
more information about these functions see <xref
linkend="OpenBSD">. The OpenBSD <function>strlcpy</function> and
linkend="OpenBSD"/>. The OpenBSD <function>strlcpy</function> and
<function>strlcat</function> instructions have been in FreeBSD
since 3.3.</para>

23
en_US.ISO8859-1/books/developers-handbook/sockets/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!--
The FreeBSD Documentation Project
@ -110,7 +111,7 @@
<mediaobject>
<imageobject>
<imagedata fileref="sockets/layers">
<imagedata fileref="sockets/layers"/>
</imageobject>
<textobject>
@ -287,7 +288,7 @@
<mediaobject>
<imageobject>
<imagedata fileref="sockets/slayers">
<imagedata fileref="sockets/slayers"/>
</imageobject>
<textobject>
@ -560,7 +561,7 @@ struct sockaddr_in {
<mediaobject>
<imageobject>
<imagedata fileref="sockets/sain">
<imagedata fileref="sockets/sain"/>
</imageobject>
<textobject>
@ -604,7 +605,7 @@ struct sockaddr_in {
<mediaobject>
<imageobject>
<imagedata fileref="sockets/sainfill">
<imagedata fileref="sockets/sainfill"/>
</imageobject>
<textobject>
@ -668,7 +669,7 @@ struct in_addr {
<mediaobject>
<imageobject>
<imagedata fileref="sockets/sainlsb">
<imagedata fileref="sockets/sainlsb"/>
</imageobject>
<textobject>
@ -694,7 +695,7 @@ struct in_addr {
<mediaobject>
<imageobject>
<imagedata fileref="sockets/sainmsb">
<imagedata fileref="sockets/sainmsb"/>
</imageobject>
<textobject>
@ -788,7 +789,7 @@ struct in_addr {
<mediaobject>
<imageobject>
<imagedata fileref="sockets/sainlsb">
<imagedata fileref="sockets/sainlsb"/>
</imageobject>
<textobject>
@ -815,7 +816,7 @@ struct in_addr {
<mediaobject>
<imageobject>
<imagedata fileref="sockets/sainmsb">
<imagedata fileref="sockets/sainmsb"/>
</imageobject>
<textobject>
@ -1072,7 +1073,7 @@ int bind(int s, const struct sockaddr *addr, socklen_t addrlen);
<mediaobject>
<imageobject>
<imagedata fileref="sockets/sainserv">
<imagedata fileref="sockets/sainserv"/>
</imageobject>
<textobject>
@ -1335,7 +1336,7 @@ int main() {
<mediaobject>
<imageobject>
<imagedata fileref="sockets/serv">
<imagedata fileref="sockets/serv"/>
</imageobject>
<textobject>
@ -1692,7 +1693,7 @@ struct servent * getservbyname(const char *name, const char *proto);
<mediaobject>
<imageobject>
<imagedata fileref="sockets/serv2">
<imagedata fileref="sockets/serv2"/>
</imageobject>
<textobject>

1
en_US.ISO8859-1/books/developers-handbook/testing/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!--
The FreeBSD Documentation Project

7
en_US.ISO8859-1/books/developers-handbook/tools/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!--
The FreeBSD Documentation Project
@ -121,7 +122,7 @@
<para>Instructions on how to get and install applications
from the Ports Collection can be found in the
<ulink url="&url.books.handbook;/ports-using.html">
Ports section</ulink> of the handbook.
Ports section</ulink> of the handbook.</para>
<variablelist>
<varlistentry>
@ -338,7 +339,7 @@
available in the Ports Collection and many use
<application>Emacs</application> for this purpose. Using
<application>Emacs</application> as an IDE is discussed in
<xref linkend="emacs">.</para>
<xref linkend="emacs"/>.</para>
</sect2>
@ -899,7 +900,7 @@ int main() {
<answer>
<para>Use <command>gdb</command> to analyze the core (see
<xref linkend="debugging">).</para>
<xref linkend="debugging"/>).</para>
</answer>
</qandaentry>

1
en_US.ISO8859-1/books/developers-handbook/x86/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!--
The FreeBSD Documentation Project

46
en_US.ISO8859-1/books/faq/book.sgml
View file

@ -1,6 +1,8 @@
<!DOCTYPE book PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
<!ENTITY % books.ent PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Books Entity Set//EN">
%books.ent;
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!DOCTYPE book PUBLIC "-//FreeBSD//DTD DocBook XML V4.2-Based Extension//EN"
"../../../share/sgml/freebsd42.dtd" [
<!ENTITY % entities PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Entity Set//EN" "../../share/sgml/entities.ent">
%entities;
<!ENTITY bibliography SYSTEM "../../../share/sgml/bibliography.sgml">
<!ENTITY rel.head "<emphasis>10-CURRENT</emphasis>">
<!ENTITY rel.head.relx "10.<replaceable>X</replaceable>">
@ -24,15 +26,13 @@
<!ENTITY rel3.packages "packages-7-stable">
]>
<book>
<book lang='en'>
<bookinfo>
<title>Frequently Asked Questions for &os;
&rel3.relx;, &rel2.relx;, and &rel.relx;</title>
<corpauthor>The &os; Documentation Project</corpauthor>
<pubdate>$FreeBSD$</pubdate>
<copyright>
<year>1995</year>
<year>1996</year>
@ -55,7 +55,7 @@
<holder>The &os; Documentation Project</holder>
</copyright>
&bookinfo.legalnotice;
&legalnotice;
<legalnotice id="trademarks" role="trademarks">
&tm-attrib.freebsd;
@ -80,6 +80,8 @@
&tm-attrib.general;
</legalnotice>
<releaseinfo>$FreeBSD$</releaseinfo>
<abstract>
<para>This is the FAQ for &os; versions
&rel3.relx;, &rel2.relx; and &rel.relx;.
@ -1293,7 +1295,7 @@
card but to run &xorg;, a VGA or better video card is
needed.</para>
<para>See also <xref linkend="hardware">.</para>
<para>See also <xref linkend="hardware"/>.</para>
</answer>
</qandaentry>
@ -2883,7 +2885,7 @@ bindkey ^[[3~ delete-char # for xterm</programlisting>
as if &os; is detecting more memory than the system really
has, due to the described remapping. This is normal and the
available memory will be corrected as the boot process
completes.<para>
completes.</para>
</answer>
</qandaentry>
@ -3165,7 +3167,7 @@ quit</programlisting>
errors, but need some more information than just the error
you see. Copy your full crash message. Then consult the
FAQ section on <link
linkend="KERNEL-PANIC-TROUBLESHOOTING">kernel panics</link>,
linkend="kernel-panic-troubleshooting">kernel panics</link>,
build a debugging kernel, and get a backtrace. This might
sound difficult, but you do not need any programming skills;
you just have to follow the instructions.</para>
@ -3523,7 +3525,7 @@ Checking for Plug-n-Play devices...
Card assigned CSN #1
Vendor ID PMC2430 (0x3024a341), Serial Number 0xffffffff
PnP Version 1.0, Vendor Version 0
Device Description: Pace 56 Voice Internal Plug & Play Modem
Device Description: Pace 56 Voice Internal Plug &amp; Play Modem
Logical Device ID: PMC2430 0x3024a341 #0
Device supports I/O Range Check
@ -4109,7 +4111,7 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
be used in closed-source software. Contact <link
linkend="apps2go">Apps2go</link> for the least expensive ELF
<application>&motif;&nbsp;2.1.20</application> distribution
for &os; (&i386;).<anchor id="apps2go"></para>
for &os; (&i386;).<anchor id="apps2go"/></para>
<para>There are two distributions, the <quote>development
edition</quote> and the <quote>runtime edition</quote> (for
@ -4965,7 +4967,7 @@ kern.sched.name: 4BSD</screen>
</question>
<answer>
<para><anchor id="dedicate">The installation procedure allows
<para><anchor id="dedicate"/>The installation procedure allows
you to chose two different methods in partitioning your hard
disk(s). The default way makes it compatible with other
operating systems on the same machine, by using
@ -6788,7 +6790,7 @@ options SYSVMSG # enable for messaging</programlisting>
at boot time (before the <literal>securelevel</literal> is
raised).</para>
<para>See <xref linkend="xdm-boot"> for more information about
<para>See <xref linkend="xdm-boot"/> for more information about
running &man.xdm.1; at boot time.</para>
</answer>
</qandaentry>
@ -6808,7 +6810,7 @@ options SYSVMSG # enable for messaging</programlisting>
&man.sysmouse.4; device via &man.moused.8;. If you wish to
use your mouse on one or more virtual consoles,
<emphasis>and</emphasis> use X, see <xref
linkend="moused" remap="another section"> and set up
linkend="moused" remap="another section"/> and set up
&man.moused.8;.</para>
<para>Then edit <filename>/etc/X11/xorg.conf</filename> and
@ -7698,7 +7700,7 @@ Key F15 A A Menu Workplace Nop</programlisting>
<table>
<title>Network Cards Based on the DEC PCI Chipset</title>
<tgroup cols=2>
<tgroup cols="2">
<thead>
<row>
<entry>Vendor</entry>
@ -8572,12 +8574,12 @@ add 0 0 HISADDR</programlisting>
<itemizedlist>
<listitem>
<para>If the problem is remote, read on entry <xref
linkend="ppp-remote-not-responding">.</para>
linkend="ppp-remote-not-responding"/>.</para>
</listitem>
<listitem>
<para>If the problem is local, read on entry <xref
linkend="ppp-hung">.</para>
linkend="ppp-hung"/>.</para>
</listitem>
</itemizedlist>
</answer>
@ -9376,7 +9378,7 @@ ATDT1234567</programlisting>
</answer>
</qandaentry>
<qandaentry id=PPPoEwithNAT>
<qandaentry id="PPPoEwithNAT">
<question id="macos-win98-pppoe-freeze">
<para>Why do &macos; and &windows;&nbsp;98 connections freeze
when running PPPoE on the gateway?</para>
@ -9421,7 +9423,7 @@ ATDT1234567</programlisting>
<para>Refer to the Microsoft Knowledge Base documents <ulink
url="http://support.microsoft.com/support/kb/articles/Q158/4/74.asp">Q158474 - Windows TCPIP Registry Entries</ulink>
and <ulink
url="http://support.microsoft.com/support/kb/articles/Q120/6/42.asp">Q120642 - TCPIP & NBT Configuration Parameters for &windowsnt;</ulink>
url="http://support.microsoft.com/support/kb/articles/Q120/6/42.asp">Q120642 - TCPIP &amp; NBT Configuration Parameters for &windowsnt;</ulink>
for more information on changing &windows; MTU to work with
a NAT router.</para>
@ -9493,9 +9495,9 @@ ATDT1234567</programlisting>
<para>Here is some example output from the above
command:</para>
<programlisting>sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
<programlisting>sio0: &lt;16550A-compatible COM port&gt; port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
sio0: type 16550A
sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0
sio1: &lt;16550A-compatible COM port&gt; port 0x2f8-0x2ff irq 3 on acpi0
sio1: type 16550A</programlisting>
<para>This shows two serial ports. The first is on

21
en_US.ISO8859-1/books/fdp-primer/book.sgml
View file

@ -1,3 +1,12 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!DOCTYPE book PUBLIC "-//FreeBSD//DTD DocBook XML V4.2-Based Extension//EN"
"../../../share/sgml/freebsd42.dtd" [
<!ENTITY % entities PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Entity Set//EN" "../../share/sgml/entities.ent">
%entities;
<!ENTITY % chapters SYSTEM "chapters.ent"> %chapters;
<!-- ENTITY index SYSTEM "index.sgml" -->
]>
<!-- Copyright (c) 1998, 1999 Nik Clayton, All rights reserved.
Redistribution and use in source (SGML DocBook) and 'compiled' forms
@ -30,15 +39,7 @@
$FreeBSD$
-->
<!DOCTYPE book PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
<!ENTITY % books.ent PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Books Entity Set//EN">
%books.ent;
<!ENTITY % chapters SYSTEM "chapters.ent"> %chapters;
<!ENTITY % not.published "INCLUDE">
<!-- ENTITY index SYSTEM "index.sgml" -->
]>
<book>
<book lang='en'>
<bookinfo>
<title>FreeBSD Documentation Project Primer for New
Contributors</title>
@ -65,7 +66,7 @@
<releaseinfo>$FreeBSD$</releaseinfo>
&bookinfo.legalnotice;
&legalnotice;
<abstract>
<para>Thank you for becoming a part of the FreeBSD Documentation

1
en_US.ISO8859-1/books/fdp-primer/chapters.ent
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="iso-8859-1"?>
<!--
Creates entities for each chapter in the Documentation Project Primer.
Each entity is named chap.foo, where foo is the value of the id

1
en_US.ISO8859-1/books/fdp-primer/doc-build/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!-- Copyright (c) 1999 Neil Blakey-Milner, All rights reserved.
Redistribution and use in source (SGML DocBook) and 'compiled' forms

33
en_US.ISO8859-1/books/fdp-primer/examples/appendix.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!-- Copyright (c) 2000 Nik Clayton, All rights reserved.
Redistribution and use in source (SGML DocBook) and 'compiled' forms
@ -59,9 +60,9 @@
<example>
<title>DocBook <sgmltag>book</sgmltag></title>
<programlisting><![ CDATA [<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook V4.1//EN">
<programlisting><![CDATA[<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook V4.1//EN">
<book>
<book lang='en'>
<bookinfo>
<title>An Example Book</title>
@ -111,9 +112,9 @@
<example>
<title>DocBook <sgmltag>article</sgmltag></title>
<programlisting><![ CDATA [<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.1//EN">
<programlisting><![CDATA[<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.1//EN">
<article>
<article lang='en'>
<articleinfo>
<title>An Example Article</title>
@ -168,12 +169,12 @@
<example>
<title>Converting DocBook to HTML (One Large File)</title>
<screen>&prompt.user; <userinput>jade -V nochunks \ <co id="examples-co-jade-1-nochunks">
-c /usr/local/share/sgml/docbook/dsssl/modular/catalog \ <co id="examples-co-jade-1-catalog">
<screen>&prompt.user; <userinput>jade -V nochunks \ <co id="examples-co-jade-1-nochunks"/>
-c /usr/local/share/sgml/docbook/dsssl/modular/catalog \ <co id="examples-co-jade-1-catalog"/>
-c /usr/local/share/sgml/docbook/catalog \
-c /usr/local/share/sgml/jade/catalog \
-d /usr/local/share/sgml/docbook/dsssl/modular/html/docbook.dsl \<co id="examples-co-jade-1-dsssl">
-t sgml <co id="examples-co-jade-1-transform"> <replaceable>file</replaceable>.sgml &gt; <replaceable>file</replaceable>.html <co id="examples-co-jade-1-filename"></userinput></screen>
-d /usr/local/share/sgml/docbook/dsssl/modular/html/docbook.dsl \<co id="examples-co-jade-1-dsssl"/>
-t sgml <co id="examples-co-jade-1-transform"/> <replaceable>file</replaceable>.sgml &gt; <replaceable>file</replaceable>.html <co id="examples-co-jade-1-filename"/></userinput></screen>
<calloutlist>
<callout arearefs="examples-co-jade-1-nochunks">
@ -220,11 +221,11 @@
Files)</title>
<screen>&prompt.user; <userinput>jade \
-c /usr/local/share/sgml/docbook/dsssl/modular/catalog \ <co id="examples-co-jade-2-catalog">
-c /usr/local/share/sgml/docbook/dsssl/modular/catalog \ <co id="examples-co-jade-2-catalog"/>
-c /usr/local/share/sgml/docbook/catalog \
-c /usr/local/share/sgml/jade/catalog \
-d /usr/local/share/sgml/docbook/dsssl/modular/html/docbook.dsl \<co id="examples-co-jade-2-dsssl">
-t sgml <co id="examples-co-jade-2-transform"> <replaceable>file</replaceable>.sgml <co id="examples-co-jade-2-filename"></userinput></screen>
-d /usr/local/share/sgml/docbook/dsssl/modular/html/docbook.dsl \<co id="examples-co-jade-2-dsssl"/>
-t sgml <co id="examples-co-jade-2-transform"/> <replaceable>file</replaceable>.sgml <co id="examples-co-jade-2-filename"/></userinput></screen>
<calloutlist>
<callout arearefs="examples-co-jade-2-catalog">
@ -271,12 +272,12 @@
<para>The source SGML file must be converted to a &tex;
file.</para>
<screen>&prompt.user; <userinput>jade -V tex-backend \ <co id="examples-co-jade-3-tex-backend">
-c /usr/local/share/sgml/docbook/dsssl/modular/catalog \ <co id="examples-co-jade-3-catalog">
<screen>&prompt.user; <userinput>jade -V tex-backend \ <co id="examples-co-jade-3-tex-backend"/>
-c /usr/local/share/sgml/docbook/dsssl/modular/catalog \ <co id="examples-co-jade-3-catalog"/>
-c /usr/local/share/sgml/docbook/catalog \
-c /usr/local/share/sgml/jade/catalog \
-d /usr/local/share/sgml/docbook/dsssl/modular/print/docbook.dsl \<co id="examples-co-jade-3-dsssl">
-t tex <co id="examples-co-jade-3-tex"> <replaceable>file</replaceable>.sgml</userinput></screen>
-d /usr/local/share/sgml/docbook/dsssl/modular/print/docbook.dsl \<co id="examples-co-jade-3-dsssl"/>
-t tex <co id="examples-co-jade-3-tex"/> <replaceable>file</replaceable>.sgml</userinput></screen>
<calloutlist>
<callout arearefs="examples-co-jade-3-tex-backend">
@ -345,7 +346,7 @@
<para>The first part of this process is identical to that when
converting DocBook to Postscript, using the same
<command>jade</command> command line (<xref
linkend="examples-docbook-postscript">).</para>
linkend="examples-docbook-postscript"/>).</para>
<para>When the <filename>.tex</filename> file has been
generated you run <application>pdfTeX</application>.

1
en_US.ISO8859-1/books/fdp-primer/overview/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!-- Copyright (c) 1998, 1999 Nik Clayton, All rights reserved.
Redistribution and use in source (SGML DocBook) and 'compiled' forms

1
en_US.ISO8859-1/books/fdp-primer/psgml-mode/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!-- Copyright (c) 1998, 1999 Nik Clayton, All rights reserved.
Redistribution and use in source (SGML DocBook) and 'compiled' forms

1
en_US.ISO8859-1/books/fdp-primer/see-also/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!-- Copyright (c) 1998, 1999 Nik Clayton, All rights reserved.
Redistribution and use in source (SGML DocBook) and 'compiled' forms

127
en_US.ISO8859-1/books/fdp-primer/sgml-markup/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!-- Copyright (c) 1998, 1999 Nik Clayton, All rights reserved.
Redistribution and use in source (SGML DocBook) and 'compiled' forms
@ -151,7 +152,7 @@
<para>Use:</para>
<programlisting><![ CDATA [<h1>First section</h1>
<programlisting><![CDATA[<h1>First section</h1>
<!-- Document introduction goes here -->
@ -184,7 +185,7 @@
<para>Use:</para>
<programlisting><![ CDATA [<h1>First section</h1>
<programlisting><![CDATA[<h1>First section</h1>
<!-- Document introduction -->
@ -205,7 +206,7 @@
<para>Use:</para>
<programlisting><![ CDATA [<p>This is a paragraph. It can contain just about any
<programlisting><![CDATA[<p>This is a paragraph. It can contain just about any
other element.</p>]]></programlisting>
</example>
</sect3>
@ -222,7 +223,7 @@
<para>Use:</para>
<programlisting><![ CDATA [<p>A small excerpt from the US Constitution:</p>
<programlisting><![CDATA[<p>A small excerpt from the US Constitution:</p>
<blockquote>We the People of the United States, in Order to form
a more perfect Union, establish Justice, insure domestic
@ -268,7 +269,7 @@
<para>Use:</para>
<programlisting><![ CDATA [<p>An unordered list. Listitems will probably be
<programlisting><![CDATA[<p>An unordered list. Listitems will probably be
preceded by bullets.</p>
<ul>
@ -300,7 +301,7 @@
<para>Use:</para>
<programlisting><![ CDATA [<dl>
<programlisting><![CDATA[<dl>
<dt>Term 1</dt>
<dd><p>Paragraph 1 of definition 1.</p>
@ -336,7 +337,7 @@
<para>You could use <sgmltag>pre</sgmltag> to mark up an
email message:</para>
<programlisting><![ CDATA [<pre> From: nik@FreeBSD.org
<programlisting><![CDATA[<pre> From: nik@FreeBSD.org
To: freebsd-doc@FreeBSD.org
Subject: New documentation available
@ -387,7 +388,7 @@
<para>Use:</para>
<programlisting><![ CDATA [<p>This is a simple 2x2 table.</p>
<programlisting><![CDATA[<p>This is a simple 2x2 table.</p>
<table>
<tr>
@ -414,7 +415,7 @@
<para>Use:</para>
<programlisting><![ CDATA [<p>One tall thin cell on the left, two short cells next to
<programlisting><![CDATA[<p>One tall thin cell on the left, two short cells next to
it on the right.</p>
<table>
@ -435,7 +436,7 @@
<para>Use:</para>
<programlisting><![ CDATA [<p>One long cell on top, two short cells below it.</p>
<programlisting><![CDATA[<p>One long cell on top, two short cells below it.</p>
<table>
<tr>
@ -456,7 +457,7 @@
<para>Use:</para>
<programlisting><![ CDATA [<p>On a 3x3 grid, the top left block is a 2x2 set of
<programlisting><![CDATA[<p>On a 3x3 grid, the top left block is a 2x2 set of
cells merged into one. The other cells are normal.</p>
<table>
@ -509,7 +510,7 @@
<para>Use:</para>
<programlisting><![ CDATA [<p><em>This</em> has been emphasized, while
<programlisting><![CDATA[<p><em>This</em> has been emphasized, while
<strong>this</strong> has been strongly emphasized.</p>]]></programlisting>
</example>
</sect3>
@ -525,7 +526,7 @@
<example>
<title><sgmltag>b</sgmltag> and <sgmltag>i</sgmltag></title>
<programlisting><![ CDATA [<p><b>This</b> is in bold, while <i>this</i> is
<programlisting><![CDATA[<p><b>This</b> is in bold, while <i>this</i> is
in italics.</p>]]></programlisting>
</example>
</sect3>
@ -542,7 +543,7 @@
<para>Use:</para>
<programlisting><![ CDATA [<p>This document was originally written by
<programlisting><![CDATA[<p>This document was originally written by
Nik Clayton, who can be reached by email as
<tt>nik@FreeBSD.org</tt>.</p>]]></programlisting>
</example>
@ -589,7 +590,7 @@
<para>The following fragments all do the same thing.</para>
<programlisting><![ CDATA [<p>This text is <small>slightly smaller</small>. But
<programlisting><![CDATA[<p>This text is <small>slightly smaller</small>. But
this text is <big>slightly bigger</big>.</p>
<p>This text is <font size="-1">slightly smaller</font>. But
@ -627,7 +628,7 @@
<para>Use:</para>
<programlisting><![ CDATA [<p>More information is available at the
<programlisting><![CDATA[<p>More information is available at the
<a href="http://www.FreeBSD.org/">FreeBSD web site</a>.</p>]]></programlisting>
</example>
@ -651,7 +652,7 @@
<para>Use:</para>
<programlisting><![ CDATA [<p><a name="para1">This</a> paragraph can be referenced
<programlisting><![CDATA[<p><a name="para1">This</a> paragraph can be referenced
in other links with the name <tt>para1</tt>.</p>]]></programlisting>
</example>
@ -666,7 +667,7 @@
resides in a document called
<filename>foo.html</filename>.</para>
<programlisting><![ CDATA [<p>More information can be found in the
<programlisting><![CDATA[<p>More information can be found in the
<a href="foo.html#para1">first paragraph</a> of
<tt>foo.html</tt>.</p>]]></programlisting>
</example>
@ -682,7 +683,7 @@
<para>Assume that the <literal>para1</literal> example
resides in this document:</para>
<programlisting><![ CDATA [<p>More information can be found in the
<programlisting><![CDATA[<p>More information can be found in the
<a href="#para1">first paragraph</a> of this
document.</p>]]></programlisting>
</example>
@ -919,7 +920,7 @@
<example>
<title>A Simple Chapter</title>
<programlisting><![ CDATA [<chapter>
<programlisting><![CDATA[<chapter>
<title>The Chapter's Title</title>
...
@ -934,7 +935,7 @@
<example>
<title>Empty Chapters</title>
<programlisting><![ CDATA [<chapter>
<programlisting><![CDATA[<chapter>
<title>This is An Empty Chapter</title>
<para></para>
@ -963,7 +964,7 @@
<example>
<title>Sections in Chapters</title>
<programlisting><![ RCDATA [<chapter>
<programlisting><![CDATA[<chapter>
<title>A Sample Chapter</title>
<para>Some text in the chapter.</para>
@ -1014,7 +1015,7 @@
one or more <sgmltag>part</sgmltag>s. This cannot be done
in an <sgmltag>article</sgmltag>.</para>
<programlisting><![ CDATA [<part>
<programlisting><![CDATA[<part>
<title>Introduction</title>
<chapter>
@ -1060,7 +1061,7 @@
<para>Use:</para>
<programlisting><![ CDATA [<para>This is a paragraph. It can contain just about any
<programlisting><![CDATA[<para>This is a paragraph. It can contain just about any
other element.</para> ]]></programlisting>
<para>Appearance:</para>
@ -1087,7 +1088,7 @@
<para>Use:</para>
<programlisting><![ CDATA [<para>A small excerpt from the US Constitution:</para>
<programlisting><![CDATA[<para>A small excerpt from the US Constitution:</para>
<blockquote>
<title>Preamble to the Constitution of the United States</title>
@ -1169,7 +1170,7 @@
<para>Use:</para>
<programlisting><![ CDATA [<warning>
<programlisting><![CDATA[<warning>
<para>Installing FreeBSD may make you want to delete Windows from your
hard disk.</para>
</warning>]]></programlisting>
@ -1221,7 +1222,7 @@
<para>Use:</para>
<programlisting><![ CDATA [<itemizedlist>
<programlisting><![CDATA[<itemizedlist>
<listitem>
<para>This is the first itemized item.</para>
</listitem>
@ -1315,7 +1316,7 @@
<para>Use:</para>
<programlisting><![ CDATA[<para>When you have finished, your program should look like
<programlisting><![CDATA[<para>When you have finished, your program should look like
this:</para>
<programlisting>#include &lt;stdio.h&gt;
@ -1365,15 +1366,15 @@ main(void)
<title><sgmltag>co</sgmltag> and
<sgmltag>calloutlist</sgmltag></title>
<programlisting><![ CDATA[<para>When you have finished, your program should look like
<programlisting><![CDATA[<para>When you have finished, your program should look like
this:</para>
<programlisting>#include &lt;stdio.h&gt; <co id="co-ex-include">
<programlisting>#include &lt;stdio.h&gt; <co id="co-ex-include"/>
int <co id="co-ex-return">
int <co id="co-ex-return"/>
main(void)
{
printf("hello, world\n"); <co id="co-ex-printf">
printf("hello, world\n"); <co id="co-ex-printf"/>
}</programlisting>
<calloutlist>
@ -1397,12 +1398,12 @@ main(void)
<para>When you have finished, your program should look like
this:</para>
<programlisting>#include &lt;stdio.h&gt; <co id="co-ex-include">
<programlisting>#include &lt;stdio.h&gt; <co id="co-ex-include"/>
int <co id="co-ex-return">
int <co id="co-ex-return"/>
main(void)
{
printf("hello, world\n"); <co id="co-ex-printf">
printf("hello, world\n"); <co id="co-ex-printf"/>
}</programlisting>
<calloutlist>
@ -1453,7 +1454,7 @@ main(void)
<para>Use:</para>
<programlisting><![ CDATA [<informaltable pgwide="1">
<programlisting><![CDATA[<informaltable pgwide="1">
<tgroup cols="2">
<thead>
<row>
@ -1617,7 +1618,7 @@ main(void)
<para>Use:</para>
<programlisting><![ CDATA [<screen>&prompt.user; <userinput>ls -1</userinput>
<programlisting><![CDATA[<screen>&prompt.user; <userinput>ls -1</userinput>
foo1
foo2
foo3
@ -1675,7 +1676,7 @@ This is the file called 'foo2'</screen>
<para>Use:</para>
<programlisting><![ CDATA [<para>FreeBSD is without doubt <emphasis>the</emphasis>
<programlisting><![CDATA[<para>FreeBSD is without doubt <emphasis>the</emphasis>
premiere Unix like operating system for the Intel architecture.</para>]]></programlisting>
<para>Appearance:</para>
@ -1700,7 +1701,7 @@ This is the file called 'foo2'</screen>
<para>Use:</para>
<programlisting><![ CDATA [<para>However, make sure that the search does not go beyond the
<programlisting><![CDATA[<para>However, make sure that the search does not go beyond the
<quote>boundary between local and public administration</quote>,
as RFC 1535 calls it.</para>]]></programlisting>
@ -1738,7 +1739,7 @@ This is the file called 'foo2'</screen>
<para>Use:</para>
<programlisting><![ CDATA [<para>To switch to the second virtual terminal, press
<programlisting><![CDATA[<para>To switch to the second virtual terminal, press
<keycombo action="simul"><keycap>Alt</keycap>
<keycap>F1</keycap></keycombo>.</para>
@ -1850,7 +1851,7 @@ This is the file called 'foo2'</screen>
<para>Use:</para>
<programlisting><![ CDATA [<para><application>Sendmail</application> is the most
<programlisting><![CDATA[<para><application>Sendmail</application> is the most
widely used Unix mail application.</para>
<para><application>Sendmail</application> includes the
@ -1908,7 +1909,7 @@ This is the file called 'foo2'</screen>
<para>Use:</para>
<programlisting><![ CDATA [<para>The SGML source for the Handbook in English can be
<programlisting><![CDATA[<para>The SGML source for the Handbook in English can be
found in <filename class="directory">/usr/doc/en_US.ISO8859-1/books/handbook/</filename>. The first
file is called <filename>book.sgml</filename> in that
directory. You should also see a <filename>Makefile</filename>
@ -1952,7 +1953,7 @@ This is the file called 'foo2'</screen>
<para>Use:</para>
<programlisting><![ CDATA [<para>Install the <filename role="package">net/ethereal</filename> port to view network traffic.</para>]]></programlisting>
<programlisting><![CDATA[<para>Install the <filename role="package">net/ethereal</filename> port to view network traffic.</para>]]></programlisting>
<para>Appearance:</para>
@ -1989,7 +1990,7 @@ This is the file called 'foo2'</screen>
<para>Use:</para>
<programlisting><![ CDATA [<para><devicename>sio</devicename> is used for serial
<programlisting><![CDATA[<para><devicename>sio</devicename> is used for serial
communication in FreeBSD. <devicename>sio</devicename> manifests
through a number of entries in <filename>/dev</filename>, including
<filename>/dev/ttyd0</filename> and <filename>/dev/cuaa0</filename>.</para>
@ -2117,7 +2118,7 @@ This is the file called 'foo2'</screen>
<para>Use:</para>
<programlisting><![ CDATA [<para>The local machine can always be referred to by the
<programlisting><![CDATA[<para>The local machine can always be referred to by the
name <hostid>localhost</hostid>, which will have the IP address
<hostid role="ipaddr">127.0.0.1</hostid>.</para>
@ -2180,7 +2181,7 @@ This is the file called 'foo2'</screen>
<para>Use:</para>
<programlisting><![ CDATA [<para>To carry out most system administration functions you
<programlisting><![CDATA[<para>To carry out most system administration functions you
will need to be <username>root</username>.</para>]]></programlisting>
<para>Appearance:</para>
@ -2220,7 +2221,7 @@ This is the file called 'foo2'</screen>
<para>Use:</para>
<programlisting><![ CDATA [<para>Two common targets in a <filename>Makefile</filename>
<programlisting><![CDATA[<para>Two common targets in a <filename>Makefile</filename>
are <maketarget>all</maketarget> and <maketarget>clean</maketarget>.</para>
<para>Typically, invoking <maketarget>all</maketarget> will rebuild the
@ -2273,7 +2274,7 @@ This is the file called 'foo2'</screen>
<para>Use:</para>
<programlisting><![ CDATA [<para>The <literal>maxusers 10</literal> line in the kernel
<programlisting><![CDATA[<para>The <literal>maxusers 10</literal> line in the kernel
configuration file determines the size of many system tables, and is
a rough guide to how many simultaneous logins the system will
support.</para>]]></programlisting>
@ -2307,7 +2308,7 @@ This is the file called 'foo2'</screen>
<para>Use:</para>
<programlisting><![ CDATA [<screen>&prompt.user; <userinput>man <replaceable>command</replaceable></userinput></screen>]]></programlisting>
<programlisting><![CDATA[<screen>&prompt.user; <userinput>man <replaceable>command</replaceable></userinput></screen>]]></programlisting>
<para>Appearance:</para>
@ -2325,7 +2326,7 @@ This is the file called 'foo2'</screen>
<para>Use:</para>
<programlisting><![ CDATA [<para>The <literal>maxusers <replaceable>n</replaceable></literal>
<programlisting><![CDATA[<para>The <literal>maxusers <replaceable>n</replaceable></literal>
line in the kernel configuration file determines the size of many system
tables, and is a rough guide to how many simultaneous logins the system will
support.</para>
@ -2358,7 +2359,7 @@ This is the file called 'foo2'</screen>
<para>Use:</para>
<programlisting><![ CDATA [
<programlisting><![CDATA[
<screen><errorname>Panic: cannot mount root</errorname></screen> ]]>
</programlisting>
@ -2480,17 +2481,17 @@ This is the file called 'foo2'</screen>
<programlisting>&lt;mediaobject>
&lt;imageobject>
&lt;imagedata fileref="fig1"> <co id="co-image-ext">
&lt;imagedata fileref="fig1"> <co id="co-image-ext"/>
&lt;/imageobject>
&lt;textobject>
&lt;literallayout class="monospaced">+---------------+ <co id="co-image-literal">
&lt;literallayout class="monospaced">+---------------+ <co id="co-image-literal"/>
| A |
+---------------+&lt;/literallayout>
&lt;/textobject>
&lt;textobject>
&lt;phrase>A picture&lt;/phrase> <co id="co-image-phrase">
&lt;phrase>A picture&lt;/phrase> <co id="co-image-phrase"/>
&lt;/textobject>
&lt;/mediaobject></programlisting>
@ -2567,7 +2568,7 @@ IMAGES+= fig3.png
<para>You must be careful when you separate your documentation
into smaller files (see
<xref linkend="sgml-primer-include-using-gen-entities">) in
<xref linkend="sgml-primer-include-using-gen-entities"/>) in
different directories.</para>
<para>Suppose you have a book with three chapters, and the
@ -2595,7 +2596,7 @@ IMAGES+= fig3.png
<programlisting>&lt;mediaobject>
&lt;imageobject>
&lt;imagedata fileref="chapter1/fig1"> <co id="co-image-dir">
&lt;imagedata fileref="chapter1/fig1"> <co id="co-image-dir"/>
&lt;/imageobject>
&hellip;
@ -2649,7 +2650,7 @@ IMAGES= chapter1/fig1.png
<title>Attribute <literal>id</literal> on Chapters and
Sections</title>
<programlisting><![ CDATA [<chapter id="chapter1">
<programlisting><![CDATA[<chapter id="chapter1">
<title>Introduction</title>
<para>This is the introduction. It contains a subsection,
@ -2680,7 +2681,7 @@ IMAGES= chapter1/fig1.png
<example>
<title><sgmltag>anchor</sgmltag></title>
<programlisting><![ CDATA [<para>This paragraph has an embedded
<programlisting><![CDATA[<para>This paragraph has an embedded
<anchor id="para1">link target in it. It will not show up in
the document.</para>]]></programlisting>
</example>
@ -2709,11 +2710,11 @@ IMAGES= chapter1/fig1.png
document that includes the <literal>id</literal>
example:</para>
<programlisting><![ CDATA [<para>More information can be found
in <xref linkend="chapter1">.</para>
<programlisting><![CDATA[<para>More information can be found
in <xref linkend="chapter1"/>.</para>
<para>More specific information can be found
in <xref linkend="chapter1-sect1">.</para>]]></programlisting>
in <xref linkend="chapter1-sect1"/>.</para>]]></programlisting>
<para>The text of the link will be generated automatically,
and will look like (<emphasis>emphasized</emphasis> text
@ -2753,7 +2754,7 @@ IMAGES= chapter1/fig1.png
document that includes the <literal>id</literal>
example.</para>
<programlisting><![ CDATA [<para>More information can be found in
<programlisting><![CDATA[<para>More information can be found in
<link linkend="chapter1">the first chapter</link>.</para>
<para>More specific information can be found in
@ -2804,7 +2805,7 @@ IMAGES= chapter1/fig1.png
<para>Use:</para>
<programlisting><![ CDATA [<para>Of course, you could stop reading this document and
<programlisting><![CDATA[<para>Of course, you could stop reading this document and
go to the <ulink url="&url.base;/index.html">FreeBSD
home page</ulink> instead.</para>]]></programlisting>

59
en_US.ISO8859-1/books/fdp-primer/sgml-primer/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!-- Copyright (c) 1998, 1999 Nik Clayton, All rights reserved.
Redistribution and use in source (SGML DocBook) and 'compiled' forms
@ -105,7 +106,7 @@
<para>The previous example is actually represented in this
document like this:</para>
<programlisting><![ CDATA [
<programlisting><![CDATA[
<para>To remove <filename>/tmp/foo</filename> use &man.rm.1;.</para>
<screen>&prompt.user; <userinput>rm /tmp/foo</userinput></screen>]]></programlisting>
@ -233,7 +234,7 @@
<sgmltag>p</sgmltag>. This element has both start and end
tags.</para>
<programlisting><![ CDATA [<p>This is a paragraph. It starts with the start tag for
<programlisting><![CDATA[<p>This is a paragraph. It starts with the start tag for
the 'p' element, and it will end with the end tag for the 'p'
element.</p>
@ -253,7 +254,7 @@
called <sgmltag>hr</sgmltag>. This element does not wrap
content, so only has a start tag.</para>
<programlisting><![ CDATA [<p>This is a paragraph.</p>
<programlisting><![CDATA[<p>This is a paragraph.</p>
<hr>
@ -269,7 +270,7 @@
<example>
<title>Elements within Elements; <sgmltag>em</sgmltag></title>
<programlisting><![ CDATA [<p>This is a simple <em>paragraph</em> where some
<programlisting><![CDATA[<p>This is a simple <em>paragraph</em> where some
of the <em>words</em> have been <em>emphasized</em>.</p>]]></programlisting>
</example>
@ -324,7 +325,7 @@
<example>
<title>Using An Element with An Attribute</title>
<programlisting><![ CDATA [<p align="left">The inclusion of the align attribute
<programlisting><![CDATA[<p align="left">The inclusion of the align attribute
on this paragraph was superfluous, since the default is left.</p>
<p align="center">This may appear in the center.</p>]]></programlisting>
@ -339,7 +340,7 @@
<example>
<title>Single Quotes Around Attributes</title>
<programlisting><![ CDATA [<p align='right'>I am on the right!</p>]]></programlisting>
<programlisting><![CDATA[<p align='right'>I am on the right!</p>]]></programlisting>
</example>
<para>Sometimes you do not need to use quotes around attribute
@ -417,7 +418,7 @@ setenv SGML_CATALOG_FILES /usr/doc/en_US.ISO8859-1/share/sgml/catalog:$SGML_CATA
<para>Create <filename>example.sgml</filename>, and enter
the following text:</para>
<programlisting><![ CDATA [<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<programlisting><![CDATA[<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
@ -578,7 +579,7 @@ onsgmls:example.sgml:6:8:E: end tag for "HEAD" which is not finished</screen>
<para>A typical declaration for a document written to conform with
version 4.0 of the HTML DTD looks like this:</para>
<programlisting><![ CDATA [<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0//EN">]]></programlisting>
<programlisting><![CDATA[<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0//EN">]]></programlisting>
<para>That line contains a number of different components.</para>
@ -818,7 +819,7 @@ onsgmls:example.sgml:6:8:E: end tag for "HEAD" which is not finished</screen>
<para>The syntax for this is slightly different:</para>
<programlisting><![ CDATA [<!DOCTYPE html SYSTEM "/path/to/file.dtd">]]></programlisting>
<programlisting><![CDATA[<!DOCTYPE html SYSTEM "/path/to/file.dtd">]]></programlisting>
<para>The <literal>SYSTEM</literal> keyword indicates that the
SGML processor should locate the DTD in a system specific
@ -864,7 +865,7 @@ onsgmls:example.sgml:6:8:E: end tag for "HEAD" which is not finished</screen>
<para>Comments are an SGML construction, and are normally only
valid inside a DTD. However, as
<xref linkend="sgml-primer-sgml-escape"> shows, it is possible
<xref linkend="sgml-primer-sgml-escape"/> shows, it is possible
to use SGML syntax within your document.</para>
<para>The delimiter for SGML comments is the string
@ -876,7 +877,7 @@ onsgmls:example.sgml:6:8:E: end tag for "HEAD" which is not finished</screen>
<programlisting>&lt;!-- test comment --></programlisting>
<programlisting><![ CDATA [
<programlisting><![CDATA[
<!-- This is inside the comment -->
<!-- This is another comment -->
@ -924,7 +925,7 @@ onsgmls:example.sgml:6:8:E: end tag for "HEAD" which is not finished</screen>
<example>
<title>Erroneous SGML Comments</title>
<programlisting><![ CDATA [
<programlisting><![CDATA[
<!-- This is in the comment --
THIS IS OUTSIDE THE COMMENT!
@ -939,12 +940,12 @@ onsgmls:example.sgml:6:8:E: end tag for "HEAD" which is not finished</screen>
<para>This is not valid SGML, and may give confusing error
messages.</para>
<programlisting><![ CDATA [<!--------------- This is a very bad idea --------------->]]></programlisting>
<programlisting><![CDATA[<!--------------- This is a very bad idea --------------->]]></programlisting>
<para>As the example suggests, <emphasis>do not</emphasis> write
comments like that.</para>
<programlisting><![ CDATA [<!--===================================================-->]]></programlisting>
<programlisting><![CDATA[<!--===================================================-->]]></programlisting>
<para>That is a (slightly) better approach, but it still
potentially confusing to people new to SGML.</para>
@ -1005,7 +1006,7 @@ onsgmls:example.sgml:6:8:E: end tag for "HEAD" which is not finished</screen>
current version number of your product. You could
write:</para>
<programlisting><![ CDATA [<para>The current version of our product is
<programlisting><![CDATA[<para>The current version of our product is
&current.version;.</para>]]></programlisting>
<para>When the version number changes you can simply change the
@ -1032,7 +1033,7 @@ onsgmls:example.sgml:6:8:E: end tag for "HEAD" which is not finished</screen>
<example>
<title>Defining General Entities</title>
<programlisting><![ CDATA [<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0//EN" [
<programlisting><![CDATA[<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0//EN" [
<!ENTITY current.version "3.0-RELEASE">
<!ENTITY last.version "2.2.7-RELEASE">
]>]]></programlisting>
@ -1074,7 +1075,7 @@ onsgmls:example.sgml:6:8:E: end tag for "HEAD" which is not finished</screen>
<example>
<title>Defining Parameter Entities</title>
<programlisting><![ CDATA [<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0//EN" [
<programlisting><![CDATA[<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0//EN" [
<!ENTITY % param.some "some">
<!ENTITY % param.text "text">
<!ENTITY % param.new "%param.some more %param.text">
@ -1094,7 +1095,7 @@ onsgmls:example.sgml:6:8:E: end tag for "HEAD" which is not finished</screen>
<para>Add a general entity to
<filename>example.sgml</filename>.</para>
<programlisting><![ CDATA [<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" [
<programlisting><![CDATA[<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" [
<!ENTITY version "1.1">
]>
@ -1199,7 +1200,7 @@ onsgmls:example.sgml:6:8:E: end tag for "HEAD" which is not finished</screen>
<example>
<title>Using General Entities to Include Files</title>
<programlisting><![ CDATA [<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0//EN" [
<programlisting><![CDATA[<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0//EN" [
<!ENTITY chapter.1 SYSTEM "chapter1.sgml">
<!ENTITY chapter.2 SYSTEM "chapter2.sgml">
<!ENTITY chapter.3 SYSTEM "chapter3.sgml">
@ -1253,7 +1254,7 @@ onsgmls:example.sgml:6:8:E: end tag for "HEAD" which is not finished</screen>
called <filename>chapters.ent</filename>. This file
contains the following:</para>
<programlisting><![ CDATA [<!ENTITY chapter.1 SYSTEM "chapter1.sgml">
<programlisting><![CDATA[<!ENTITY chapter.1 SYSTEM "chapter1.sgml">
<!ENTITY chapter.2 SYSTEM "chapter2.sgml">
<!ENTITY chapter.3 SYSTEM "chapter3.sgml">]]></programlisting>
@ -1263,7 +1264,7 @@ onsgmls:example.sgml:6:8:E: end tag for "HEAD" which is not finished</screen>
entities available for use. Then use the general entities
as before:</para>
<programlisting><![ CDATA [<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0//EN" [
<programlisting><![CDATA[<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0//EN" [
<!-- Define a parameter entity to load in the chapter general entities -->
<!ENTITY % chapters SYSTEM "chapters.ent">
@ -1294,14 +1295,14 @@ onsgmls:example.sgml:6:8:E: end tag for "HEAD" which is not finished</screen>
<para>Put content similar to the following in each
file:</para>
<programlisting><![ CDATA [<p>This is the first paragraph.</p>]]></programlisting>
<programlisting><![CDATA[<p>This is the first paragraph.</p>]]></programlisting>
</step>
<step>
<para>Edit <filename>example.sgml</filename> so that it
looks like this:</para>
<programlisting><![ CDATA [<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0//EN" [
<programlisting><![CDATA[<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0//EN" [
<!ENTITY version "1.1">
<!ENTITY para1 SYSTEM "para1.sgml">
<!ENTITY para2 SYSTEM "para2.sgml">
@ -1352,7 +1353,7 @@ onsgmls:example.sgml:6:8:E: end tag for "HEAD" which is not finished</screen>
<para>Edit <filename>example.sgml</filename> so that it
looks like this:</para>
<programlisting><![ CDATA [<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0//EN" [
<programlisting><![CDATA[<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0//EN" [
<!ENTITY % entities SYSTEM "entities.sgml"> %entities;
]>
@ -1376,7 +1377,7 @@ onsgmls:example.sgml:6:8:E: end tag for "HEAD" which is not finished</screen>
<filename>entities.sgml</filename>, with this
content:</para>
<programlisting><![ CDATA [<!ENTITY version "1.1">
<programlisting><![CDATA[<!ENTITY version "1.1">
<!ENTITY para1 SYSTEM "para1.sgml">
<!ENTITY para2 SYSTEM "para2.sgml">
<!ENTITY para3 SYSTEM "para3.sgml">]]></programlisting>
@ -1505,7 +1506,7 @@ onsgmls:example.sgml:6:8:E: end tag for "HEAD" which is not finished</screen>
&lt;programlisting>) are from DocBook.&lt;/para>
&lt;programlisting>
&lt;![ CDATA [ <![ CDATA [
&lt;![CDATA[ <![ CDATA [
<p>This is a sample that shows you some of the elements within
HTML. Since the angle brackets are used so many times, it is
simpler to say the whole example is a CDATA marked section
@ -1621,16 +1622,16 @@ onsgmls:example.sgml:6:8:E: end tag for "HEAD" which is not finished</screen>
&lt;/head>
&lt;body>
&lt;p>This paragraph &lt;![ CDATA [contains many &lt;
&lt;p>This paragraph &lt;![CDATA[contains many &lt;
characters (&lt; &lt; &lt; &lt; &lt;) so it is easier
to wrap it in a CDATA marked section.]]&gt;&lt;/p>
&lt;![ IGNORE [
&lt;![IGNORE[
&lt;p>This paragraph will definitely not be included in the
output.&lt;/p>
]]&gt;
&lt;![ <![ CDATA [%text.output]]> [
&lt;![ <![CDATA[%text.output]]> [
&lt;p>This paragraph might appear in the output, or it
might not.&lt;/p>

3
en_US.ISO8859-1/books/fdp-primer/structure/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!-- Copyright (c) 1998, 1999 Nik Clayton, All rights reserved.
Redistribution and use in source (SGML DocBook) and 'compiled' forms
@ -234,7 +235,7 @@
<para>For example, if one of the chapter files
contains:</para>
<programlisting><![ CDATA [
<programlisting><![CDATA[
<chapter id="kernelconfig">
...
</chapter>]]></programlisting>

1
en_US.ISO8859-1/books/fdp-primer/stylesheets/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!-- Copyright (c) 1998, 1999 Nik Clayton, All rights reserved.
Redistribution and use in source (SGML DocBook) and 'compiled' forms

1
en_US.ISO8859-1/books/fdp-primer/the-website/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!-- Copyright (c) 1998, 1999 Nik Clayton, All rights reserved.
Redistribution and use in source (SGML DocBook) and 'compiled' forms

1
en_US.ISO8859-1/books/fdp-primer/tools/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!-- Copyright (c) 1998, 1999 Nik Clayton, All rights reserved.
Redistribution and use in source (SGML DocBook) and 'compiled' forms

1
en_US.ISO8859-1/books/fdp-primer/translations/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!-- Copyright (c) 1999 Nik Clayton, All rights reserved.
Redistribution and use in source (SGML DocBook) and 'compiled' forms

11
en_US.ISO8859-1/books/fdp-primer/writing-style/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!-- Copyright (c) 1998 Nik Clayton, All rights reserved.
Redistribution and use in source (SGML DocBook) and 'compiled' forms
@ -229,7 +230,7 @@
<para>For example, the source for this section looks something
like:</para>
<programlisting><![ CDATA [+--- This is column 0
<programlisting><![CDATA[+--- This is column 0
V
<chapter>
<title>...</title>
@ -280,7 +281,7 @@ augroup END</programlisting>
at the same indent as a previous tag should not:</para>
<informalexample>
<programlisting><![ CDATA [<article>
<programlisting><![CDATA[<article lang='en'>
<articleinfo>
<title>NIS</title>
@ -379,12 +380,12 @@ GB. Hardware compression &hellip;</literallayout>
<itemizedlist>
<listitem>
<para>between numbers and units:</para>
<programlisting><![ CDATA [57600&nbsp;bps]]></programlisting>
<programlisting><![CDATA[57600&nbsp;bps]]></programlisting>
</listitem>
<listitem>
<para>between program names and version numbers:</para>
<programlisting><![ CDATA [FreeBSD&nbsp;4.7]]></programlisting>
<programlisting><![CDATA[FreeBSD&nbsp;4.7]]></programlisting>
</listitem>
<listitem>
@ -392,7 +393,7 @@ GB. Hardware compression &hellip;</literallayout>
applying this to more than 3-4 word names like
<quote>The FreeBSD Brazilian Portuguese Documentation
Project</quote>):</para>
<programlisting><![ CDATA [Sun&nbsp;Microsystems]]></programlisting>
<programlisting><![CDATA[Sun&nbsp;Microsystems]]></programlisting>
</listitem>
</itemizedlist>
</sect2>

23
en_US.ISO8859-1/books/handbook/Makefile
View file

@ -253,7 +253,6 @@ SRCS+= book.sgml
SRCS+= bsdinstall/chapter.sgml
SRCS+= colophon.sgml
SRCS+= dtrace/chapter.sgml
SRCS+= freebsd-glossary.sgml
SRCS+= advanced-networking/chapter.sgml
SRCS+= basics/chapter.sgml
SRCS+= bibliography/chapter.sgml
@ -316,9 +315,9 @@ DOC_PREFIX?= ${.CURDIR}/../../..
#
# rules generating lists of mirror site from XML database.
#
XMLDOCS= mirrors-ftp:::mirrors.sgml.ftp.inc.tmp \
mirrors-cvsup:::mirrors.sgml.cvsup.inc.tmp \
eresources:::eresources.sgml.www.inc.tmp
XMLDOCS= mirrors-ftp:::mirrors.sgml.ftp.inc \
mirrors-cvsup:::mirrors.sgml.cvsup.inc \
eresources:::eresources.sgml.www.inc
DEPENDSET.DEFAULT= transtable mirror
XSLT.DEFAULT= ${XSL_MIRRORS}
XML.DEFAULT= ${XML_MIRRORS}
@ -338,18 +337,8 @@ SRCS+= mirrors.sgml.ftp.inc \
mirrors.sgml.cvsup.inc \
eresources.sgml.www.inc
CLEANFILES+= mirrors.sgml.ftp.inc mirrors.sgml.ftp.inc.tmp \
mirrors.sgml.cvsup.inc mirrors.sgml.cvsup.inc.tmp \
eresources.sgml.www.inc eresources.sgml.www.inc.tmp
CLEANFILES+= mirrors.sgml.ftp.inc \
mirrors.sgml.cvsup.inc \
eresources.sgml.www.inc
.include "${DOC_PREFIX}/share/mk/doc.project.mk"
.for p in ftp cvsup
mirrors.sgml.${p}.inc: mirrors.sgml.${p}.inc.tmp
${SED} -e 's,<\([^ >]*\)\([^>]*\)/>,<\1\2></\1>,;s,</anchor>,,'\
< $@.tmp > $@ || (${RM} -f $@ && false)
.endfor
eresources.sgml.www.inc: eresources.sgml.www.inc.tmp
${SED} -e 's,<\([^ >]*\)\([^>]*\)/>,<\1\2></\1>,;s,</anchor>,,'\
< $@.tmp > $@ || (${RM} -f $@ && false)

173
en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!--
The FreeBSD Documentation Project
@ -75,12 +76,12 @@
<listitem>
<para>Know how to configure and install a new FreeBSD kernel
(<xref linkend="kernelconfig">).</para>
(<xref linkend="kernelconfig"/>).</para>
</listitem>
<listitem>
<para>Know how to install additional third-party
software (<xref linkend="ports">).</para>
software (<xref linkend="ports"/>).</para>
</listitem>
</itemizedlist>
@ -219,8 +220,8 @@ host2.example.com link#1 UC 0 0
<informaltable frame="none" pgwide="1">
<tgroup cols="2">
<colspec colwidth="1*">
<colspec colwidth="4*">
<colspec colwidth="1*"/>
<colspec colwidth="4*"/>
<tbody>
<row>
@ -301,7 +302,7 @@ host2.example.com link#1 UC 0 0
<mediaobject>
<imageobject>
<imagedata fileref="advanced-networking/net-routing">
<imagedata fileref="advanced-networking/net-routing"/>
</imageobject>
<textobject>
@ -493,7 +494,7 @@ host2.example.com link#1 UC 0 0
<mediaobject>
<imageobject>
<imagedata fileref="advanced-networking/static-routes">
<imagedata fileref="advanced-networking/static-routes"/>
</imageobject>
<textobject>
@ -1185,7 +1186,7 @@ ifconfig_wlan0="authmode shared wepmode on weptxkey <replaceable>1</replaceable>
compatibility with legacy devices) it is better to use
WEP with <literal>open</literal> authentication. More
information regarding WEP can be found in the
<xref linkend="network-wireless-wep">.</para>
<xref linkend="network-wireless-wep"/>.</para>
</note>
</sect5>
@ -1443,15 +1444,15 @@ wlan0: flags=8843&lt;UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST&gt; mtu 1500
<filename>/etc/wpa_supplicant.conf</filename>:</para>
<programlisting>network={
ssid="freebsdap" <co id="co-tls-ssid">
proto=RSN <co id="co-tls-proto">
key_mgmt=WPA-EAP <co id="co-tls-kmgmt">
eap=TLS <co id="co-tls-eap">
identity="loader" <co id="co-tls-id">
ca_cert="/etc/certs/cacert.pem" <co id="co-tls-cacert">
client_cert="/etc/certs/clientcert.pem" <co id="co-tls-clientcert">
private_key="/etc/certs/clientkey.pem" <co id="co-tls-pkey">
private_key_passwd="freebsdmallclient" <co id="co-tls-pwd">
ssid="freebsdap" <co id="co-tls-ssid"/>
proto=RSN <co id="co-tls-proto"/>
key_mgmt=WPA-EAP <co id="co-tls-kmgmt"/>
eap=TLS <co id="co-tls-eap"/>
identity="loader" <co id="co-tls-id"/>
ca_cert="/etc/certs/cacert.pem" <co id="co-tls-cacert"/>
client_cert="/etc/certs/clientcert.pem" <co id="co-tls-clientcert"/>
private_key="/etc/certs/clientkey.pem" <co id="co-tls-pkey"/>
private_key_passwd="freebsdmallclient" <co id="co-tls-pwd"/>
}</programlisting>
<calloutlist>
@ -1560,11 +1561,11 @@ wlan0: flags=8843&lt;UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST&gt; mtu 1500
ssid="freebsdap"
proto=RSN
key_mgmt=WPA-EAP
eap=TTLS <co id="co-ttls-eap">
identity="test" <co id="co-ttls-id">
password="test" <co id="co-ttls-passwd">
ca_cert="/etc/certs/cacert.pem" <co id="co-ttls-cacert">
phase2="auth=MD5" <co id="co-ttls-pha2">
eap=TTLS <co id="co-ttls-eap"/>
identity="test" <co id="co-ttls-id"/>
password="test" <co id="co-ttls-passwd"/>
ca_cert="/etc/certs/cacert.pem" <co id="co-ttls-cacert"/>
phase2="auth=MD5" <co id="co-ttls-pha2"/>
}</programlisting>
<calloutlist>
@ -1660,12 +1661,12 @@ wlan0: flags=8843&lt;UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST&gt; mtu 1500
ssid="freebsdap"
proto=RSN
key_mgmt=WPA-EAP
eap=PEAP <co id="co-peap-eap">
identity="test" <co id="co-peap-id">
password="test" <co id="co-peap-passwd">
ca_cert="/etc/certs/cacert.pem" <co id="co-peap-cacert">
phase1="peaplabel=0" <co id="co-peap-pha1">
phase2="auth=MSCHAPV2" <co id="co-peap-pha2">
eap=PEAP <co id="co-peap-eap"/>
identity="test" <co id="co-peap-id"/>
password="test" <co id="co-peap-passwd"/>
ca_cert="/etc/certs/cacert.pem" <co id="co-peap-cacert"/>
phase1="peaplabel=0" <co id="co-peap-pha1"/>
phase2="auth=MSCHAPV2" <co id="co-peap-pha2"/>
}</programlisting>
<calloutlist>
@ -1877,7 +1878,7 @@ Associated with 00:13:46:49:41:76</screen>
networking support for your wireless card. You also have to
add support for the security protocols you intend to
use. For more details, see
<xref linkend="network-wireless-basic">.</para>
<xref linkend="network-wireless-basic"/>.</para>
<note>
<para>The use of the NDIS driver wrapper and the &windows;
@ -1979,7 +1980,7 @@ freebsdap 00:11:95:c3:0d:ac 1 54M -66:-96 100 ES WME</screen>
<para>This section will focus on setting up &os; Access Point
using the WPA security protocol. More details regarding WPA
and the configuration of WPA-based wireless clients can be
found in the <xref linkend="network-wireless-wpa">.</para>
found in the <xref linkend="network-wireless-wpa"/>.</para>
<para>The <application>hostapd</application> daemon is used to
deal with client authentication and keys management on the
@ -1996,7 +1997,7 @@ freebsdap 00:11:95:c3:0d:ac 1 54M -66:-96 100 ES WME</screen>
<para>Before trying to configure
<application>hostapd</application>, be sure you have done
the basic settings introduced in the
<xref linkend="network-wireless-ap-basic">.</para>
<xref linkend="network-wireless-ap-basic"/>.</para>
<sect4>
<title>WPA-PSK</title>
@ -2008,15 +2009,15 @@ freebsdap 00:11:95:c3:0d:ac 1 54M -66:-96 100 ES WME</screen>
<para>The configuration is done in the
<filename>/etc/hostapd.conf</filename> file:</para>
<programlisting>interface=wlan0 <co id="co-ap-wpapsk-iface">
debug=1 <co id="co-ap-wpapsk-dbug">
ctrl_interface=/var/run/hostapd <co id="co-ap-wpapsk-ciface">
ctrl_interface_group=wheel <co id="co-ap-wpapsk-cifacegrp">
ssid=freebsdap <co id="co-ap-wpapsk-ssid">
wpa=1 <co id="co-ap-wpapsk-wpa">
wpa_passphrase=freebsdmall <co id="co-ap-wpapsk-pass">
wpa_key_mgmt=WPA-PSK <co id="co-ap-wpapsk-kmgmt">
wpa_pairwise=CCMP TKIP <co id="co-ap-wpapsk-pwise"></programlisting>
<programlisting>interface=wlan0 <co id="co-ap-wpapsk-iface"/>
debug=1 <co id="co-ap-wpapsk-dbug"/>
ctrl_interface=/var/run/hostapd <co id="co-ap-wpapsk-ciface"/>
ctrl_interface_group=wheel <co id="co-ap-wpapsk-cifacegrp"/>
ssid=freebsdap <co id="co-ap-wpapsk-ssid"/>
wpa=1 <co id="co-ap-wpapsk-wpa"/>
wpa_passphrase=freebsdmall <co id="co-ap-wpapsk-pass"/>
wpa_key_mgmt=WPA-PSK <co id="co-ap-wpapsk-kmgmt"/>
wpa_pairwise=CCMP TKIP <co id="co-ap-wpapsk-pwise"/></programlisting>
<calloutlist>
<callout arearefs="co-ap-wpapsk-iface">
@ -2090,7 +2091,7 @@ wpa_pairwise=CCMP TKIP <co id="co-ap-wpapsk-pwise"></programlisting>
<para>The next step is to start
<application>hostapd</application>:</para>
<screen>&prompt.root <userinput>/etc/rc.d/hostapd forcestart</userinput></screen>
<screen>&prompt.root; <userinput>/etc/rc.d/hostapd forcestart</userinput></screen>
<screen>&prompt.root; <userinput>ifconfig <replaceable>wlan0</replaceable></userinput>
wlan0: flags=8843&lt;UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST&gt; mtu 2290
@ -2104,7 +2105,7 @@ wpa_pairwise=CCMP TKIP <co id="co-ap-wpapsk-pwise"></programlisting>
<para>The Access Point is running, the clients can now be
associated with it, see
<xref linkend="network-wireless-wpa"> for more details.
<xref linkend="network-wireless-wpa"/> for more details.
It is possible to see the stations associated with the AP
using the <command>ifconfig
<replaceable>wlan0</replaceable> list sta</command>
@ -2171,7 +2172,7 @@ freebsdap 00:11:95:c3:0d:ac 1 54M 22:1 100 EPS</screen>
<para>The client machine found the Access Point and can be
associated with it using the correct parameters (key, etc.),
see <xref linkend="network-wireless-wep"> for more
see <xref linkend="network-wireless-wep"/> for more
details.</para>
</sect3>
</sect2>
@ -2193,9 +2194,9 @@ freebsdap 00:11:95:c3:0d:ac 1 54M 22:1 100 EPS</screen>
changes.</para>
<para>We will cover link aggregation and failover in
<xref linkend="network-aggregation"> where an example for
<xref linkend="network-aggregation"/> where an example for
using both wired and wireless connection is also provided at
<xref linkend="networking-lagg-wired-and-wireless">.</para>
<xref linkend="networking-lagg-wired-and-wireless"/>.</para>
</sect2>
<sect2>
@ -2350,9 +2351,9 @@ Max. SCO packet size: 64 bytes
Number of SCO packets: 8</screen>
</sect2>
<indexterm><primary>HCI</primary></indexterm>
<sect2>
<title>Host Controller Interface (HCI)</title>
<indexterm><primary>HCI</primary></indexterm>
<para>Host Controller Interface (HCI) provides a command
interface to the baseband controller and link manager, and
@ -2438,11 +2439,12 @@ Reason: Connection terminated by local host [0x16]</screen>
do not require superuser privileges.</para>
</sect2>
<indexterm><primary>L2CAP</primary></indexterm>
<sect2>
<title>Logical Link Control and Adaptation Protocol
(L2CAP)</title>
<indexterm><primary>L2CAP</primary></indexterm>
<para>Logical Link Control and Adaptation Protocol (L2CAP)
provides connection-oriented and connectionless data services
to upper layer protocols with protocol multiplexing capability
@ -2511,7 +2513,6 @@ PCB Recv-Q Send-Q Local address Foreign address Chan DLCI State
c2e8bc80 0 250 00:02:72:00:d4:1a 00:07:e0:00:0b:ca 3 6 OPEN</screen>
</sect2>
<indexterm><primary>RFCOMM</primary></indexterm>
<sect2>
<title>RFCOMM Protocol</title>
@ -2542,7 +2543,6 @@ c2e8bc80 0 250 00:02:72:00:d4:1a 00:07:e0:00:0b:ca 3 6 OPEN</scree
Bluetooth sockets layer.</para>
</sect2>
<indexterm><primary>pairing</primary></indexterm>
<sect2>
<title>Pairing of Devices</title>
@ -2606,11 +2606,11 @@ hcsecd[16484]: Found matching entry, remote bdaddr 0:80:37:29:19:a4, name 'Pav's
hcsecd[16484]: Sending PIN_Code_Reply to 'ubt0hci' for remote bdaddr 0:80:37:29:19:a4</programlisting>
</sect2>
<indexterm><primary>SDP</primary></indexterm>
<sect2>
<title>Service Discovery Protocol (SDP)</title>
<indexterm><primary>SDP</primary></indexterm>
<para>The Service Discovery Protocol (SDP) provides the means
for client applications to discover the existence of services
provided by server applications as well as the attributes of
@ -2772,12 +2772,11 @@ Bluetooth Profile Descriptor List:
<screen>&prompt.root; <userinput>rfcomm_pppd -s -C 7 -l rfcomm-server</userinput></screen>
</sect2>
<indexterm><primary>OBEX</primary></indexterm>
<sect2>
<title>OBEX Object Push (OPUSH) Profile</title>
<para>OBEX is a widely used protocol for simple file transfers
<indexterm><primary>OBEX</primary></indexterm>
<para>OBEX is a widely used protocol for simple file transfers between
between mobile devices. Its main use is in infrared
communication, where it is used for generic file transfers
between notebooks or PDAs, and for sending business cards or
@ -3211,7 +3210,7 @@ bridge0: flags=8843&lt;UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST&gt; metric 0 mtu 1
combine the bridge with VLANs to create a router where
customer networks are isolated without wasting IP address
space. Consider that
<hostid role="Hostname">CustomerA</hostid> is on
<hostid role="hostname">CustomerA</hostid> is on
<literal>vlan100</literal> and
<hostid role="hostname">CustomerB</hostid> is on
<literal>vlan101</literal>. The bridge has the address
@ -3247,7 +3246,7 @@ bridge0: flags=8843&lt;UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST&gt; metric 0 mtu 1
<para>The following example sets the maximum number of
Ethernet devices for
<hostid role="Hostname">CustomerA</hostid> on
<hostid role="hostname">CustomerA</hostid> on
<literal>vlan100</literal> to 10.</para>
<screen>&prompt.root; <userinput>ifconfig bridge0 ifmaxaddr vlan100 10</userinput></screen>
@ -3940,16 +3939,16 @@ option domain-name-servers 192.168.4.1;
option routers 192.168.4.1;
subnet 192.168.4.0 netmask 255.255.255.0 {
use-host-decl-names on; <co id="co-dhcp-host-name">
use-host-decl-names on; <co id="co-dhcp-host-name"/>
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.4.255;
host margaux {
hardware ethernet 01:23:45:67:89:ab;
fixed-address margaux.example.com;
next-server 192.168.4.4; <co id="co-dhcp-next-server">
filename "/data/misc/kernel.diskless"; <co id="co-dhcp-filename">
option root-path "192.168.4.4:/data/misc/diskless"; <co id="co-dhcp-root-path">
next-server 192.168.4.4; <co id="co-dhcp-next-server"/>
filename "/data/misc/kernel.diskless"; <co id="co-dhcp-filename"/>
option root-path "192.168.4.4:/data/misc/diskless"; <co id="co-dhcp-root-path"/>
}
host corbieres {
hardware ethernet 00:02:b3:27:62:df;
@ -4241,7 +4240,7 @@ options BOOTP_NFSROOT # NFS mount root file system using BOOTP info</progra
also possible to force strict BOOTP or
<acronym>DHCP</acronym> use).</para>
<para>Build the kernel (see <xref linkend="kernelconfig">),
<para>Build the kernel (see <xref linkend="kernelconfig"/>),
and copy it to the place specified in
<filename>dhcpd.conf</filename>.</para>
@ -4409,7 +4408,7 @@ cd /usr/src/etc; make distribution</programlisting>
process is <filename>/boot/pxeboot</filename>. After
<filename>/boot/pxeboot</filename> executes, the &os; kernel is
loaded, and the rest of the &os; bootup sequence proceeds.
Refer to <xref linkend="boot"> for more information about the
Refer to <xref linkend="boot"/> for more information about the
&os; booting process.</para>
<sect2>
@ -4430,7 +4429,7 @@ cd /usr/src/etc; make distribution</programlisting>
<step>
<para>Enable the NFS server by following the instructions
in <xref linkend="network-configuring-nfs">.</para>
in <xref linkend="network-configuring-nfs"/>.</para>
</step>
<step>
@ -4448,7 +4447,7 @@ cd /usr/src/etc; make distribution</programlisting>
<step>
<para>Enable &man.inetd.8; by following the steps outlined
in <xref linkend="network-inetd-settings">.</para>
in <xref linkend="network-inetd-settings"/>.</para>
</step>
<step>
@ -4581,7 +4580,7 @@ myhost.example.com:/b/tftpboot/FreeBSD/install / nfs ro
<step>
<para>Install the <acronym>DHCP</acronym> server by
following the instructions documented at
<xref linkend="network-dhcp-server">. Make sure that
<xref linkend="network-dhcp-server"/>. Make sure that
<filename>/etc/rc.conf</filename> and
<filename>/usr/local/etc/dhcpd.conf</filename> are
correctly configured.</para>
@ -4641,7 +4640,7 @@ myhost.example.com:/b/tftpboot/FreeBSD/install / nfs ro
debug the network traffic involved during the
<acronym>PXE</acronym> booting process, which is
illustrated in the diagram below. In
<xref linkend="network-pxe-setting-up-dhcp">, an example
<xref linkend="network-pxe-setting-up-dhcp"/>, an example
configuration is shown where the <acronym>DHCP</acronym>,
<acronym>TFTP</acronym>, and <acronym>NFS</acronym>
servers are actually on the same machine. However, these
@ -4653,14 +4652,14 @@ myhost.example.com:/b/tftpboot/FreeBSD/install / nfs ro
<mediaobjectco>
<imageobjectco>
<areaspec units="calspair">
<area id="co-pxenfs1" coords="2873,8133 3313,7266">
<area id="co-pxenfs2" coords="3519,6333 3885,5500">
<area id="co-pxenfs3" coords="4780,5866 5102,5200">
<area id="co-pxenfs4" coords="4794,4333 5102,3600">
<area id="co-pxenfs5" coords="3108,2666 3519,1800">
<area id="co-pxenfs1" coords="2873,8133 3313,7266"/>
<area id="co-pxenfs2" coords="3519,6333 3885,5500"/>
<area id="co-pxenfs3" coords="4780,5866 5102,5200"/>
<area id="co-pxenfs4" coords="4794,4333 5102,3600"/>
<area id="co-pxenfs5" coords="3108,2666 3519,1800"/>
</areaspec>
<imageobject>
<imagedata fileref="advanced-networking/pxe-nfs">
<imagedata fileref="advanced-networking/pxe-nfs"/>
</imageobject>
<calloutlist>
<callout arearefs="co-pxenfs1">
@ -4982,7 +4981,7 @@ Received 264951 bytes in 0.1 seconds</screen>
<mediaobject>
<imageobject>
<imagedata fileref="advanced-networking/isdn-bus">
<imagedata fileref="advanced-networking/isdn-bus"/>
</imageobject>
<textobject>
@ -5017,7 +5016,7 @@ ISDN BRI line</literallayout>
<mediaobject>
<imageobject>
<imagedata
fileref="advanced-networking/isdn-twisted-pair">
fileref="advanced-networking/isdn-twisted-pair"/>
</imageobject>
<textobject>
@ -5131,7 +5130,7 @@ ISDN BRI line</literallayout>
<mediaobject>
<imageobject>
<imagedata fileref="advanced-networking/natd">
<imagedata fileref="advanced-networking/natd"/>
</imageobject>
<textobject>
@ -5159,13 +5158,13 @@ ISDN BRI line</literallayout>
</sect2>
<sect2 id="network-natdloaderconfiguration">
<title>Boot Loader Configuration</title>
<indexterm>
<primary>boot loader</primary>
<secondary>configuration</secondary>
</indexterm>
<title>Boot Loader Configuration</title>
<para>The kernel features for network address translation with
&man.natd.8; are not enabled in the
<filename>GENERIC</filename> kernel, but they can be preloaded
@ -5220,12 +5219,12 @@ options IPFIREWALL_VERBOSE</programlisting>
<para>To enable firewall and NAT support at boot time, the
following must be in <filename>/etc/rc.conf</filename>:</para>
<programlisting>gateway_enable="YES" <co id="co-natd-gateway-enable">
firewall_enable="YES" <co id="co-natd-firewall-enable">
firewall_type="OPEN" <co id="co-natd-firewall-type">
<programlisting>gateway_enable="YES" <co id="co-natd-gateway-enable"/>
firewall_enable="YES" <co id="co-natd-firewall-enable"/>
firewall_type="OPEN" <co id="co-natd-firewall-type"/>
natd_enable="YES"
natd_interface="<replaceable>fxp0</replaceable>" <co id="co-natd-natd-interface">
natd_flags="" <co id="co-natd-natd-flags"></programlisting>
natd_interface="<replaceable>fxp0</replaceable>" <co id="co-natd-natd-interface"/>
natd_flags="" <co id="co-natd-natd-flags"/></programlisting>
<calloutlist>
<callout arearefs="co-natd-gateway-enable">
@ -6112,8 +6111,8 @@ round-trip min/avg/max/stddev = 2.530/2.643/2.774/0.103 ms</screen>
<informaltable frame="none" pgwide="1">
<tgroup cols="2">
<colspec colwidth="1*">
<colspec colwidth="1*">
<colspec colwidth="1*"/>
<colspec colwidth="1*"/>
<thead>
<row>
<entry>Host</entry>
@ -6154,8 +6153,8 @@ round-trip min/avg/max/stddev = 2.530/2.643/2.774/0.103 ms</screen>
<informaltable frame="none" pgwide="1">
<tgroup cols="2">
<colspec colwidth="1*">
<colspec colwidth="1*">
<colspec colwidth="1*"/>
<colspec colwidth="1*"/>
<thead>
<row>
<entry>Machines</entry>
@ -6294,7 +6293,7 @@ route_hostD="192.168.173.4 hatm0 0 102 llc/snap ubr"</programlisting>
<para>To enable support for <acronym>CARP</acronym>, the &os;
kernel must be rebuilt as described in
<xref linkend="kernelconfig"> with the following option:</para>
<xref linkend="kernelconfig"/> with the following option:</para>
<programlisting>device carp</programlisting>
@ -6451,7 +6450,7 @@ ifconfig_carp1="vhid 2 advskew 100 pass testpass 192.168.1.51/24"</programlistin
should be issued on
<hostid>provider.example.org</hostid>:</para>
<screen>&prompt.root; <userinput>ifconfig carp0 down && ifconfig carp0 up</userinput></screen>
<screen>&prompt.root; <userinput>ifconfig carp0 down &amp;&amp; ifconfig carp0 up</userinput></screen>
<para>This should be done on the <devicename>carp</devicename>
interface which corresponds to the correct host.</para>

9
en_US.ISO8859-1/books/handbook/audit/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!--
The FreeBSD Documentation Project
$FreeBSD$
@ -73,18 +74,18 @@ requirements. -->
<itemizedlist>
<listitem>
<para>Understand &unix; and &os; basics
(<xref linkend="basics">).</para>
(<xref linkend="basics"/>).</para>
</listitem>
<listitem>
<para>Be familiar with the basics of kernel
configuration/compilation
(<xref linkend="kernelconfig">).</para>
(<xref linkend="kernelconfig"/>).</para>
</listitem>
<listitem>
<para>Have some familiarity with security and how it
pertains to &os; (<xref linkend="security">).</para>
pertains to &os; (<xref linkend="security"/>).</para>
</listitem>
</itemizedlist>
@ -196,7 +197,7 @@ requirements. -->
<para>Rebuild and reinstall
the kernel via the normal process explained in
<xref linkend="kernelconfig">.</para>
<xref linkend="kernelconfig"/>.</para>
<para>Once an audit-enabled kernel is built, installed, and the system
has been rebooted, enable the audit daemon by adding the following line

41
en_US.ISO8859-1/books/handbook/basics/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!--
The FreeBSD Documentation Project
@ -262,7 +263,7 @@ ttyv8 "/usr/X11R6/bin/xdm -nodaemon" xterm off secure</programlisting>
<title>Single User Mode Console</title>
<para>A detailed description of what <quote>single user mode</quote> is
can be found in <xref linkend="boot-singleuser">. It is worth noting
can be found in <xref linkend="boot-singleuser"/>. It is worth noting
that there is only one console when you are running FreeBSD in single
user mode. There are no virtual consoles available. The settings of
the single user mode console can also be found in the
@ -810,7 +811,7 @@ root 5211 0.0 0.2 3620 1724 2 I+ 2:09AM 0:00.01 passwd</screen>
<para>A mount point is a directory where additional file systems can
be grafted onto a parent file system (usually the root file system).
This is further described in <xref linkend="disk-organization">.
This is further described in <xref linkend="disk-organization"/>.
Standard mount points include
<filename>/usr</filename>, <filename>/var</filename>, <filename>/tmp</filename>,
<filename>/mnt</filename>, and <filename>/cdrom</filename>. These
@ -820,7 +821,7 @@ root 5211 0.0 0.2 3620 1724 2 I+ 2:09AM 0:00.01 passwd</screen>
system. Most of the file systems in <filename>/etc/fstab</filename>
are mounted automatically at boot time from the script &man.rc.8;
unless they contain the <option>noauto</option> option.
Details can be found in <xref linkend="disks-fstab">.</para>
Details can be found in <xref linkend="disks-fstab"/>.</para>
<para>A complete description of the file system hierarchy is
available in &man.hier.7;. For now, a brief overview of the
@ -1030,7 +1031,7 @@ root 5211 0.0 0.2 3620 1724 2 I+ 2:09AM 0:00.01 passwd</screen>
A memory-based file system is sometimes mounted at
<filename class="directory">/var</filename>.
This can be automated using the varmfs-related variables of
&man.rc.conf.5 (or with an entry in
&man.rc.conf.5; (or with an entry in
<filename>/etc/fstab</filename>; see &man.mdmfs.8;).</entry>
</row>
@ -1131,7 +1132,7 @@ root 5211 0.0 0.2 3620 1724 2 I+ 2:09AM 0:00.01 passwd</screen>
<mediaobject>
<imageobject>
<imagedata fileref="install/example-dir1" format="EPS">
<imagedata fileref="install/example-dir1" format="EPS"/>
</imageobject>
<textobject>
@ -1151,7 +1152,7 @@ root 5211 0.0 0.2 3620 1724 2 I+ 2:09AM 0:00.01 passwd</screen>
<mediaobject>
<imageobject>
<imagedata fileref="install/example-dir2" format="EPS">
<imagedata fileref="install/example-dir2" format="EPS"/>
</imageobject>
<textobject>
@ -1179,7 +1180,7 @@ root 5211 0.0 0.2 3620 1724 2 I+ 2:09AM 0:00.01 passwd</screen>
<mediaobject>
<imageobject>
<imagedata fileref="install/example-dir3" format="EPS">
<imagedata fileref="install/example-dir3" format="EPS"/>
</imageobject>
<textobject>
@ -1205,7 +1206,7 @@ root 5211 0.0 0.2 3620 1724 2 I+ 2:09AM 0:00.01 passwd</screen>
<mediaobject>
<imageobject>
<imagedata fileref="install/example-dir4" format="EPS">
<imagedata fileref="install/example-dir4" format="EPS"/>
</imageobject>
<textobject>
@ -1231,7 +1232,7 @@ root 5211 0.0 0.2 3620 1724 2 I+ 2:09AM 0:00.01 passwd</screen>
<mediaobject>
<imageobject>
<imagedata fileref="install/example-dir5" format="EPS">
<imagedata fileref="install/example-dir5" format="EPS"/>
</imageobject>
<textobject>
@ -1337,8 +1338,8 @@ root 5211 0.0 0.2 3620 1724 2 I+ 2:09AM 0:00.01 passwd</screen>
<informaltable frame="none" pgwide="1">
<tgroup cols="2">
<colspec colwidth="1*">
<colspec colwidth="5*">
<colspec colwidth="1*"/>
<colspec colwidth="5*"/>
<thead>
<row>
@ -1417,7 +1418,7 @@ root 5211 0.0 0.2 3620 1724 2 I+ 2:09AM 0:00.01 passwd</screen>
starts with a code that indicates the type of disk, and then a number,
indicating which disk it is. Unlike slices, disk numbering starts at
0. Common codes that you will see are listed in
<xref linkend="basics-dev-codes">.</para>
<xref linkend="basics-dev-codes"/>.</para>
<para>When referring to a partition FreeBSD requires that you also name
the slice and disk that contains the partition, and when referring to
@ -1425,9 +1426,9 @@ root 5211 0.0 0.2 3620 1724 2 I+ 2:09AM 0:00.01 passwd</screen>
Thus, you refer to a partition by listing
the disk name, <literal>s</literal>, the slice number, and then the
partition letter. Examples are shown in
<xref linkend="basics-disk-slice-part">.</para>
<xref linkend="basics-disk-slice-part"/>.</para>
<para><xref linkend="basics-concept-disk-model"> shows a conceptual
<para><xref linkend="basics-concept-disk-model"/> shows a conceptual
model of the disk layout that should help make things clearer.</para>
<para>In order to install FreeBSD you must first configure the disk
@ -1439,8 +1440,8 @@ root 5211 0.0 0.2 3620 1724 2 I+ 2:09AM 0:00.01 passwd</screen>
<title>Disk Device Codes</title>
<tgroup cols="2">
<colspec colwidth="1*">
<colspec colwidth="5*">
<colspec colwidth="1*"/>
<colspec colwidth="5*"/>
<thead>
<row>
@ -1489,8 +1490,8 @@ root 5211 0.0 0.2 3620 1724 2 I+ 2:09AM 0:00.01 passwd</screen>
<informaltable frame="none" pgwide="1">
<tgroup cols="2">
<colspec colwidth="1*">
<colspec colwidth="5*">
<colspec colwidth="1*"/>
<colspec colwidth="5*"/>
<thead>
<row>
@ -1539,7 +1540,7 @@ root 5211 0.0 0.2 3620 1724 2 I+ 2:09AM 0:00.01 passwd</screen>
<mediaobject>
<imageobject>
<imagedata fileref="install/disk-layout" format="EPS">
<imagedata fileref="install/disk-layout" format="EPS"/>
</imageobject>
<textobject>
@ -1624,7 +1625,7 @@ root 5211 0.0 0.2 3620 1724 2 I+ 2:09AM 0:00.01 passwd</screen>
<term><literal>device</literal></term>
<listitem>
<para>A device name (which should exist), as explained in
<xref linkend="disks-naming">.</para>
<xref linkend="disks-naming"/>.</para>
</listitem>
</varlistentry>

1
en_US.ISO8859-1/books/handbook/bibliography/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!--
The FreeBSD Documentation Project

135
en_US.ISO8859-1/books/handbook/book.sgml
View file

@ -1,61 +1,22 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!DOCTYPE book PUBLIC "-//FreeBSD//DTD DocBook XML V4.2-Based Extension//EN"
"../../../share/sgml/freebsd42.dtd" [
<!ENTITY % entities PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Entity Set//EN" "../../share/sgml/entities.ent">
%entities;
<!--
The FreeBSD Documentation Project
$FreeBSD$
-->
<!DOCTYPE BOOK PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
<!ENTITY % books.ent PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Books Entity Set//EN">
%books.ent;
<!ENTITY % chapters SYSTEM "chapters.ent">
%chapters;
<!ENTITY % txtfiles SYSTEM "txtfiles.ent">
%txtfiles;
<!ENTITY % not.published "INCLUDE">
<!ENTITY % chap.introduction "IGNORE">
<!ENTITY % chap.install "IGNORE">
<!ENTITY % chap.bsdinstall "IGNORE">
<!ENTITY % chap.basics "IGNORE">
<!ENTITY % chap.ports "IGNORE">
<!ENTITY % chap.config "IGNORE">
<!ENTITY % chap.boot "IGNORE">
<!ENTITY % chap.users "IGNORE">
<!ENTITY % chap.kernelconfig "IGNORE">
<!ENTITY % chap.security "IGNORE">
<!ENTITY % chap.jails "IGNORE">
<!ENTITY % chap.printing "IGNORE">
<!ENTITY % chap.disks "IGNORE">
<!ENTITY % chap.geom "IGNORE">
<!ENTITY % chap.vinum "IGNORE">
<!ENTITY % chap.x11 "IGNORE">
<!ENTITY % chap.l10n "IGNORE">
<!ENTITY % chap.multimedia "IGNORE">
<!ENTITY % chap.desktop "IGNORE">
<!ENTITY % chap.serialcomms "IGNORE">
<!ENTITY % chap.ppp-and-slip "IGNORE">
<!ENTITY % chap.advanced-networking "IGNORE">
<!ENTITY % chap.firewalls "IGNORE">
<!ENTITY % chap.network-servers "IGNORE">
<!ENTITY % chap.mail "IGNORE">
<!ENTITY % chap.cutting-edge "IGNORE">
<!ENTITY % chap.linuxemu "IGNORE">
<!ENTITY % chap.mirrors "IGNORE">
<!ENTITY % chap.bibliography "IGNORE">
<!ENTITY % chap.eresources "IGNORE">
<!ENTITY % chap.pgpkeys "IGNORE">
<!ENTITY % chap.index "IGNORE">
<!ENTITY % chap.freebsd-glossary "IGNORE">
<!ENTITY % chap.mac "IGNORE">
<!ENTITY % chap.audit "IGNORE">
<!ENTITY % chap.filesystems "IGNORE">
<!ENTITY % chap.dtrace "IGNORE">
<!ENTITY % pgpkeys SYSTEM "../../../share/pgpkeys/pgpkeys.ent"> %pgpkeys;
]>
<book>
<book lang='en'>
<bookinfo>
<title>FreeBSD Handbook</title>
@ -63,6 +24,8 @@
<pubdate>February 1999</pubdate>
<releaseinfo>$FreeBSD$</releaseinfo>
<copyright>
<year>1995</year>
<year>1996</year>
@ -85,7 +48,7 @@
<holder>The FreeBSD Documentation Project</holder>
</copyright>
&bookinfo.legalnotice;
&legalnotice;
<legalnotice id="trademarks" role="trademarks">
&tm-attrib.freebsd;
@ -196,12 +159,12 @@
required.</para>
</partintro>
<![ %chap.introduction; [ &chap.introduction; ]]>
<![ %chap.install; [ &chap.install; ]]>
<![ %chap.bsdinstall; [ &chap.bsdinstall; ]]>
<![ %chap.basics; [ &chap.basics; ]]>
<![ %chap.ports; [ &chap.ports; ]]>
<![ %chap.x11; [ &chap.x11; ]]>
&chap.introduction;
&chap.install;
&chap.bsdinstall;
&chap.basics;
&chap.ports;
&chap.x11;
</part>
<part id="common-tasks">
@ -246,11 +209,11 @@
each chapter.</para>
</partintro>
<![ %chap.desktop; [ &chap.desktop; ]]>
<![ %chap.multimedia; [ &chap.multimedia; ]]>
<![ %chap.kernelconfig; [ &chap.kernelconfig; ]]>
<![ %chap.printing; [ &chap.printing; ]]>
<![ %chap.linuxemu; [ &chap.linuxemu; ]]>
&chap.desktop;
&chap.multimedia;
&chap.kernelconfig;
&chap.printing;
&chap.linuxemu;
</part>
<part id="system-administration">
@ -269,21 +232,21 @@
you can begin using FreeBSD.</para>
</partintro>
<![ %chap.config; [ &chap.config; ]]>
<![ %chap.boot; [ &chap.boot; ]]>
<![ %chap.users; [ &chap.users; ]]>
<![ %chap.security; [ &chap.security; ]]>
<![ %chap.jails; [ &chap.jails; ]]>
<![ %chap.mac; [ &chap.mac; ]]>
<![ %chap.audit; [ &chap.audit; ]]>
<![ %chap.disks; [ &chap.disks; ]]>
<![ %chap.geom; [ &chap.geom; ]]>
<![ %chap.filesystems; [ &chap.filesystems; ]]>
<![ %chap.vinum; [ &chap.vinum; ]]>
<![ %chap.virtualization; [ &chap.virtualization; ]]>
<![ %chap.l10n; [ &chap.l10n; ]]>
<![ %chap.cutting-edge; [ &chap.cutting-edge; ]]>
<![ %chap.dtrace; [ &chap.dtrace; ]]>
&chap.config;
&chap.boot;
&chap.users;
&chap.security;
&chap.jails;
&chap.mac;
&chap.audit;
&chap.disks;
&chap.geom;
&chap.filesystems;
&chap.vinum;
&chap.virtualization;
&chap.l10n;
&chap.cutting-edge;
&chap.dtrace;
</part>
<part id="network-communication">
@ -326,25 +289,25 @@
you can begin using FreeBSD in a network environment.</para>
</partintro>
<![ %chap.serialcomms; [ &chap.serialcomms; ]]>
<![ %chap.ppp-and-slip; [ &chap.ppp-and-slip; ]]>
<![ %chap.mail; [ &chap.mail; ]]>
<![ %chap.network-servers; [ &chap.network-servers; ]]>
<![ %chap.firewalls; [ &chap.firewalls; ]]>
<![ %chap.advanced-networking; [ &chap.advanced-networking; ]]>
&chap.serialcomms;
&chap.ppp-and-slip;
&chap.mail;
&chap.network-servers;
&chap.firewalls;
&chap.advanced-networking;
</part>
<part id="appendices">
<title>Appendices</title>
<![ %chap.mirrors; [ &chap.mirrors; ]]>
<![ %chap.bibliography; [ &chap.bibliography; ]]>
<![ %chap.eresources; [ &chap.eresources; ]]>
<![ %chap.pgpkeys; [ &chap.pgpkeys; ]]>
&chap.mirrors;
&chap.bibliography;
&chap.eresources;
&chap.pgpkeys;
</part>
<![ %chap.freebsd-glossary; [ &bookinfo.freebsd-glossary; ]]>
<![ %chap.index; [ &chap.index; ]]>
&freebsd-glossary;
&chap.index;
&chap.colophon;
</book>

17
en_US.ISO8859-1/books/handbook/boot/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!--
The FreeBSD Documentation Project
@ -614,7 +615,7 @@ boot:</screen>
the <acronym>VESA</acronym> module during system boot, or
adding a <literal>VESA</literal> kernel configuration
option and building a custom kernel (see <xref
linkend="kernelconfig">). The <acronym>VESA</acronym>
linkend="kernelconfig"/>). The <acronym>VESA</acronym>
support gives users the ability to display a splash screen
image that fills the whole display screen.</para>
@ -756,11 +757,12 @@ bitmap_name="<replaceable>/boot/splash.bin</replaceable>"</programlisting>
necessary.</para>
<sect2 id="boot-kernel-bootflags">
<title>Kernel Boot Flags</title>
<indexterm>
<primary>kernel</primary>
<secondary>bootflags</secondary>
</indexterm>
<title>Kernel Boot Flags</title>
<para>Here are the more common boot flags:</para>
@ -832,10 +834,12 @@ bitmap_name="<replaceable>/boot/splash.bin</replaceable>"</programlisting>
</authorgroup>
<!-- 18 OCT 2002 -->
</sect1info>
<title>Device Hints</title>
<indexterm>
<primary>device.hints</primary>
</indexterm>
<title>Device Hints</title>
<para>During initial system startup, the boot &man.loader.8; will
read the &man.device.hints.5; file. This file stores kernel
@ -916,10 +920,11 @@ bitmap_name="<replaceable>/boot/splash.bin</replaceable>"</programlisting>
</sect1>
<sect1 id="boot-init">
<title>Init: Process Control Initialization</title>
<indexterm>
<primary><command>init</command></primary>
</indexterm>
<title>Init: Process Control Initialization</title>
<para>Once the kernel has finished booting, it passes control to
the user process &man.init.8;, which is located at
@ -995,9 +1000,10 @@ console none unknown off insecure</programlisting>
resource configuration of the system.</para>
<sect3 id="boot-rc">
<indexterm><primary>rc files</primary></indexterm>
<title>Resource Configuration (rc)</title>
<indexterm><primary>rc files</primary></indexterm>
<para>The resource configuration system reads in
configuration defaults from
<filename>/etc/defaults/rc.conf</filename>, and
@ -1018,6 +1024,7 @@ console none unknown off insecure</programlisting>
<sect1 id="boot-shutdown">
<title>Shutdown Sequence</title>
<indexterm>
<primary><command>shutdown</command></primary>
</indexterm>

136
en_US.ISO8859-1/books/handbook/bsdinstall/chapter.sgml
View file

@ -52,7 +52,7 @@
chapter describes the use of
<application>bsdinstall</application>. The use of
<application>sysinstall</application> is covered in <xref
linkend="install">.</para>
linkend="install"/>.</para>
<para>After reading this chapter, you will know:</para>
@ -111,7 +111,7 @@
sections. Depending on the method you choose to install &os;,
you may also need a supported CDROM drive, and in some cases a
network adapter. This will be covered by <xref
linkend="bsdinstall-installation-media">.</para>
linkend="bsdinstall-installation-media"/>.</para>
<sect3>
<title>&os;/&arch.i386;</title>
@ -254,7 +254,7 @@
<para>&os;'s standard boot loader requires either a primary or
<acronym>GPT</acronym> partition. (See <xref
linkend="boot"> for more information about the &os;
linkend="boot"/> for more information about the &os;
booting process.) If all of the primary or
<acronym>GPT</acronym> partitions are already in use, one
must be freed for &os;.</para>
@ -335,7 +335,7 @@
make it possible to run any one of those operating systems
at a time. An alternative method that allows running
multiple operating systems at the same time is covered in
<xref linkend="virtualization">.</para>
<xref linkend="virtualization"/>.</para>
</sect3>
</sect2>
@ -454,7 +454,7 @@
<para>A different directory path is used for
&os;&nbsp;8.<replaceable>X</replaceable> and earlier versions. Details of
download and installation of &os;&nbsp;8.<replaceable>X</replaceable> and
earlier is covered in <xref linkend="install">.</para>
earlier is covered in <xref linkend="install"/>.</para>
</tip>
<para>The memory stick image has a <filename>.img</filename>
@ -580,7 +580,7 @@ commit your changes?</literallayout>
<step>
<para>If you prepared a <quote>bootable</quote> USB stick,
as described in
<xref linkend="bsdinstall-installation-media">, then
<xref linkend="bsdinstall-installation-media"/>, then
plug in your USB stick before turning on the
computer.</para>
@ -665,7 +665,7 @@ Loading /boot/defaults/loader.conf
<imageobject>
<imagedata
fileref="bsdinstall/bsdinstall-boot-loader-menu"
format="PNG">
format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -738,8 +738,8 @@ Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4.</screen>
<screenco>
<areaspec>
<area id="bsdinstall-prompt-single" coords="1 5">
<area id="bsdinstall-prompt-smp" coords="2 5">
<area id="bsdinstall-prompt-single" coords="1 5"/>
<area id="bsdinstall-prompt-smp" coords="2 5"/>
</areaspec>
<screen><prompt>ok </prompt>
@ -781,7 +781,7 @@ Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4.</screen>
<para>Do this now, to review the text that scrolled off the
screen when the kernel was carrying out the device probes.
You will see text similar to <xref
linkend="bsdinstall-dev-probe">, although the precise text
linkend="bsdinstall-dev-probe"/>, although the precise text
will differ depending on the devices that you have in your
computer.</para>
@ -945,7 +945,7 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
<filename>GENERIC</filename> kernel.</para>
<para>After the procedure of device probing, you will see
<xref linkend="bsdinstall-choose-mode">. The install media
<xref linkend="bsdinstall-choose-mode"/>. The install media
can be used in three ways: to install &os;, as a "live CD", or
to simply access a &os; shell. Use the arrow keys to choose
an option, and <keycap>Enter</keycap> to select.</para>
@ -955,7 +955,7 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
<mediaobject>
<imageobject>
<imagedata fileref="bsdinstall/bsdinstall-choose-mode"
format="PNG">
format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -1000,7 +1000,7 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
<imageobject>
<imagedata
fileref="bsdinstall/bsdinstall-keymap-select-default"
format="PNG">
format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -1015,7 +1015,7 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
<mediaobject>
<imageobject>
<imagedata fileref="bsdinstall/bsdinstall-config-keymap"
format="PNG">
format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -1044,7 +1044,7 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
<mediaobject>
<imageobject>
<imagedata fileref="bsdinstall/bsdinstall-config-hostname"
format="PNG">
format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -1066,7 +1066,7 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
<imageobject>
<imagedata
fileref="bsdinstall/bsdinstall-config-components"
format="PNG">
format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -1110,7 +1110,7 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
the source code necessary to compile the software.
Instead, it is a collection of files which automates the
downloading, compiling and installation of third-party
software packages. <xref linkend="ports"> discusses how
software packages. <xref linkend="ports"/> discusses how
to use the ports collection.</para>
<warning>
@ -1155,13 +1155,13 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
<mediaobject>
<imageobject>
<imagedata fileref="bsdinstall/bsdinstall-netinstall-files"
format="PNG">
format="PNG"/>
</imageobject>
</mediaobject>
</figure>
<para>After the network connection has been configured as shown in
<xref linkend="bsdinstall-config-network-dev">, a mirror site is
<xref linkend="bsdinstall-config-network-dev"/>, a mirror site is
selected. Mirror sites cache copies of the &os; files. Choose
a mirror site located in the same region of the world as the
computer on which &os; is being installed. Files can be
@ -1175,7 +1175,7 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
<imageobject>
<imagedata
fileref="bsdinstall/bsdinstall-netinstall-mirrorselect"
format="PNG">
format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -1203,7 +1203,7 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
<imageobject>
<imagedata
fileref="bsdinstall/bsdinstall-part-guided-manual"
format="PNG">
format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -1220,7 +1220,7 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
<imageobject>
<imagedata
fileref="bsdinstall/bsdinstall-part-guided-disk"
format="PNG">
format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -1240,7 +1240,7 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
<imageobject>
<imagedata
fileref="bsdinstall/bsdinstall-part-entire-part"
format="PNG">
format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -1260,7 +1260,7 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
<mediaobject>
<imageobject>
<imagedata fileref="bsdinstall/bsdinstall-part-review"
format="PNG">
format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -1279,7 +1279,7 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
<imageobject>
<imagedata
fileref="bsdinstall/bsdinstall-part-manual-create"
format="PNG">
format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -1297,7 +1297,7 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
<imageobject>
<imagedata
fileref="bsdinstall/bsdinstall-part-manual-partscheme"
format="PNG">
format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -1378,7 +1378,7 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
<imageobject>
<imagedata
fileref="bsdinstall/bsdinstall-part-manual-addpart"
format="PNG">
format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -1410,7 +1410,7 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
partitions for the <filename>/</filename>,
<filename>/var</filename>, <filename>/tmp</filename>, and <filename>/usr</filename>
filesystems. See <xref
linkend="bsdinstall-part-manual-splitfs"> for an
linkend="bsdinstall-part-manual-splitfs"/> for an
example.</para>
<para>See &man.gpart.8; for a complete list of available
@ -1554,7 +1554,7 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
<imageobject>
<imagedata
fileref="bsdinstall/bsdinstall-final-confirmation"
format="PNG">
format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -1587,7 +1587,7 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
<mediaobject>
<imageobject>
<imagedata fileref="bsdinstall/bsdinstall-distfile-fetching"
format="PNG">
format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -1603,7 +1603,7 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
<imageobject>
<imagedata
fileref="bsdinstall/bsdinstall-distfile-verifying"
format="PNG">
format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -1618,7 +1618,7 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
<imageobject>
<imagedata
fileref="bsdinstall/bsdinstall-distfile-extracting"
format="PNG">
format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -1626,7 +1626,7 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
<para>Once all requested distribution files have been extracted,
<application>bsdinstall</application> will then drop straight
into the post-installation configuration tasks (see
<xref linkend="bsdinstall-post">).</para>
<xref linkend="bsdinstall-post"/>).</para>
</sect1>
<sect1 id="bsdinstall-post">
@ -1653,7 +1653,7 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
<imageobject>
<imagedata
fileref="bsdinstall/bsdinstall-post-root-passwd"
format="PNG">
format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -1681,7 +1681,7 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
<imageobject>
<imagedata
fileref="bsdinstall/bsdinstall-configure-network-interface"
format="PNG">
format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -1716,7 +1716,7 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
<imageobject>
<imagedata
fileref="bsdinstall/bsdinstall-configure-wireless-scan"
format="PNG">
format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -1739,7 +1739,7 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
<imageobject>
<imagedata
fileref="bsdinstall/bsdinstall-configure-wireless-accesspoints"
format="PNG">
format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -1759,7 +1759,7 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
<imageobject>
<imagedata
fileref="bsdinstall/bsdinstall-configure-wireless-wpa2setup"
format="PNG">
format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -1782,7 +1782,7 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
<imageobject>
<imagedata
fileref="bsdinstall/bsdinstall-configure-network-interface-ipv4"
format="PNG">
format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -1798,7 +1798,7 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
<note>
<para>Do not enter random network information, as it will
not work. Obtain the information shown in
<xref linkend="bsdinstall-collect-network-information">
<xref linkend="bsdinstall-collect-network-information"/>
from the network administrator or service provider.</para>
</note>
@ -1816,7 +1816,7 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
<imageobject>
<imagedata
fileref="bsdinstall/bsdinstall-configure-network-interface-ipv4-dhcp"
format="PNG">
format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -1835,7 +1835,7 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
<imageobject>
<imagedata
fileref="bsdinstall/bsdinstall-configure-network-interface-ipv4-static"
format="PNG">
format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -1882,7 +1882,7 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
<imageobject>
<imagedata
fileref="bsdinstall/bsdinstall-configure-network-interface-ipv6"
format="PNG">
format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -1911,7 +1911,7 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
<imageobject>
<imagedata
fileref="bsdinstall/bsdinstall-configure-network-interface-slaac"
format="PNG">
format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -1930,7 +1930,7 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
<imageobject>
<imagedata
fileref="bsdinstall/bsdinstall-configure-network-interface-ipv6-static"
format="PNG">
format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -1980,7 +1980,7 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
<imageobject>
<imagedata
fileref="bsdinstall/bsdinstall-configure-network-ipv4-dns"
format="PNG">
format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -2005,7 +2005,7 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
<imageobject>
<imagedata
fileref="bsdinstall/bsdinstall-set-clock-local-utc"
format="PNG">
format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -2024,7 +2024,7 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
<mediaobject>
<imageobject>
<imagedata fileref="bsdinstall/bsdinstall-timezone-region"
format="PNG">
format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -2039,7 +2039,7 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
<imageobject>
<imagedata
fileref="bsdinstall/bsdinstall-timezone-country"
format="PNG">
format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -2053,7 +2053,7 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
<mediaobject>
<imageobject>
<imagedata fileref="bsdinstall/bsdinstall-timezone-zone"
format="PNG">
format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -2068,7 +2068,7 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
<imageobject>
<imagedata
fileref="bsdinstall/bsdinstall-timezone-confirm"
format="PNG">
format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -2090,7 +2090,7 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
<mediaobject>
<imageobject>
<imagedata fileref="bsdinstall/bsdinstall-config-services"
format="PNG">
format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -2140,7 +2140,7 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
<imageobject>
<imagedata
fileref="bsdinstall/bsdinstall-config-crashdump"
format="PNG">
format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -2165,7 +2165,7 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
<mediaobject>
<imageobject>
<imagedata fileref="bsdinstall/bsdinstall-adduser1"
format="PNG">
format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -2178,7 +2178,7 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
<mediaobject>
<imageobject>
<imagedata fileref="bsdinstall/bsdinstall-adduser2"
format="PNG">
format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -2279,7 +2279,7 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
<mediaobject>
<imageobject>
<imagedata fileref="bsdinstall/bsdinstall-adduser3"
format="PNG">
format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -2290,7 +2290,7 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
installation.</para>
<para>For more information on adding users and user management,
see <xref linkend="users">.</para>
see <xref linkend="users"/>.</para>
</sect2>
<sect2 id="bsdinstall-final-conf">
@ -2306,7 +2306,7 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
<imageobject>
<imagedata
fileref="bsdinstall/bsdinstall-finalconfiguration"
format="PNG">
format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -2319,32 +2319,32 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
<listitem>
<para><literal>Add User</literal> - Described in
<xref linkend="bsdinstall-addusers">.</para>
<xref linkend="bsdinstall-addusers"/>.</para>
</listitem>
<listitem>
<para><literal>Root Password</literal> - Described in
<xref linkend="bsdinstall-post-root">.</para>
<xref linkend="bsdinstall-post-root"/>.</para>
</listitem>
<listitem>
<para><literal>Hostname</literal> - Described in
<xref linkend="bsdinstall-hostname">.</para>
<xref linkend="bsdinstall-hostname"/>.</para>
</listitem>
<listitem>
<para><literal>Network</literal> - Described in
<xref linkend="bsdinstall-config-network-dev">.</para>
<xref linkend="bsdinstall-config-network-dev"/>.</para>
</listitem>
<listitem>
<para><literal>Services</literal> - Described in
<xref linkend="bsdinstall-sysconf">.</para>
<xref linkend="bsdinstall-sysconf"/>.</para>
</listitem>
<listitem>
<para><literal>Time Zone</literal> - Described in
<xref linkend="bsdinstall-timezone">.</para>
<xref linkend="bsdinstall-timezone"/>.</para>
</listitem>
<listitem>
@ -2363,7 +2363,7 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
<imageobject>
<imagedata
fileref="bsdinstall/bsdinstall-final-modification-shell"
format="PNG">
format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -2382,7 +2382,7 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
<mediaobject>
<imageobject>
<imagedata fileref="bsdinstall/bsdinstall-mainexit"
format="PNG">
format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -2599,7 +2599,7 @@ login:</screen>
automatically. Subsequent boots will be faster.</para>
<para>&os; does not install graphical environments by default,
but many are available. See <xref linkend="x11"> for more
but many are available. See <xref linkend="x11"/> for more
information.</para>
</sect3>
</sect2>
@ -2713,7 +2713,7 @@ login:</screen>
file
<filename>/boot/loader.conf</filename>. More
information about the boot loader can be found
in <xref linkend="boot-synopsis">.</para>
in <xref linkend="boot-synopsis"/>.</para>
</answer>
</qandaentry>
</qandaset>

272
en_US.ISO8859-1/books/handbook/chapters.ent
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="iso-8859-1"?>
<!--
Creates entities for each chapter in the FreeBSD Handbook. Each entity
is named chap.foo, where foo is the value of the id attribute on that
@ -9,56 +10,235 @@
$FreeBSD$
-->
<!ENTITY % not.published "INCLUDE">
<!ENTITY % chap.introduction "IGNORE">
<!ENTITY % chap.install "IGNORE">
<!ENTITY % chap.bsdinstall "IGNORE">
<!ENTITY % chap.basics "IGNORE">
<!ENTITY % chap.ports "IGNORE">
<!ENTITY % chap.config "IGNORE">
<!ENTITY % chap.boot "IGNORE">
<!ENTITY % chap.users "IGNORE">
<!ENTITY % chap.kernelconfig "IGNORE">
<!ENTITY % chap.security "IGNORE">
<!ENTITY % chap.jails "IGNORE">
<!ENTITY % chap.printing "IGNORE">
<!ENTITY % chap.disks "IGNORE">
<!ENTITY % chap.geom "IGNORE">
<!ENTITY % chap.vinum "IGNORE">
<!ENTITY % chap.x11 "IGNORE">
<!ENTITY % chap.l10n "IGNORE">
<!ENTITY % chap.multimedia "IGNORE">
<!ENTITY % chap.desktop "IGNORE">
<!ENTITY % chap.serialcomms "IGNORE">
<!ENTITY % chap.ppp-and-slip "IGNORE">
<!ENTITY % chap.advanced-networking "IGNORE">
<!ENTITY % chap.firewalls "IGNORE">
<!ENTITY % chap.network-servers "IGNORE">
<!ENTITY % chap.mail "IGNORE">
<!ENTITY % chap.cutting-edge "IGNORE">
<!ENTITY % chap.linuxemu "IGNORE">
<!ENTITY % chap.mirrors "IGNORE">
<!ENTITY % chap.mirrors.ftp.inc "INCLUDE">
<!ENTITY % chap.mirrors.cvsup.inc "INCLUDE">
<!ENTITY % chap.bibliography "IGNORE">
<!ENTITY % chap.eresources "IGNORE">
<!ENTITY % chap.eresources.www.inc "INCLUDE">
<!ENTITY % chap.pgpkeys "IGNORE">
<!ENTITY % chap.index "IGNORE">
<!ENTITY % chap.freebsd-glossary "IGNORE">
<!ENTITY % chap.mac "IGNORE">
<!ENTITY % chap.audit "IGNORE">
<!ENTITY % chap.filesystems "IGNORE">
<!ENTITY % chap.dtrace "IGNORE">
<!ENTITY chap.preface SYSTEM "preface/preface.sgml">
<!ENTITY % pgpkeys SYSTEM "../../../share/pgpkeys/pgpkeys.ent"> %pgpkeys;
<!-- Part one -->
<!ENTITY chap.introduction SYSTEM "introduction/chapter.sgml">
<!ENTITY chap.install SYSTEM "install/chapter.sgml">
<!ENTITY chap.bsdinstall SYSTEM "bsdinstall/chapter.sgml">
<!ENTITY chap.basics SYSTEM "basics/chapter.sgml">
<!ENTITY chap.ports SYSTEM "ports/chapter.sgml">
<!ENTITY chap.x11 SYSTEM "x11/chapter.sgml">
<!-- Part One -->
<![%chap.introduction;[
<!ENTITY chap.introduction SYSTEM "introduction/chapter.sgml">
]]>
<![%chap.install;[
<!ENTITY chap.install SYSTEM "install/chapter.sgml">
]]>
<![%chap.bsdinstall;[
<!ENTITY chap.bsdinstall SYSTEM "bsdinstall/chapter.sgml">
]]>
<![%chap.basics;[
<!ENTITY chap.basics SYSTEM "basics/chapter.sgml">
]]>
<![%chap.ports;[
<!ENTITY chap.ports SYSTEM "ports/chapter.sgml">
]]>
<![%chap.x11;[
<!ENTITY chap.x11 SYSTEM "x11/chapter.sgml">
]]>
<!-- Part two -->
<!ENTITY chap.desktop SYSTEM "desktop/chapter.sgml">
<!ENTITY chap.multimedia SYSTEM "multimedia/chapter.sgml">
<!ENTITY chap.kernelconfig SYSTEM "kernelconfig/chapter.sgml">
<!ENTITY chap.printing SYSTEM "printing/chapter.sgml">
<!ENTITY chap.linuxemu SYSTEM "linuxemu/chapter.sgml">
<!-- Part Two -->
<![%chap.desktop;[
<!ENTITY chap.desktop SYSTEM "desktop/chapter.sgml">
]]>
<![%chap.multimedia;[
<!ENTITY chap.multimedia SYSTEM "multimedia/chapter.sgml">
]]>
<![%chap.kernelconfig;[
<!ENTITY chap.kernelconfig SYSTEM "kernelconfig/chapter.sgml">
]]>
<![%chap.printing;[
<!ENTITY chap.printing SYSTEM "printing/chapter.sgml">
]]>
<![%chap.linuxemu;[
<!ENTITY chap.linuxemu SYSTEM "linuxemu/chapter.sgml">
]]>
<!-- Part three -->
<!ENTITY chap.config SYSTEM "config/chapter.sgml">
<!ENTITY chap.boot SYSTEM "boot/chapter.sgml">
<!ENTITY chap.users SYSTEM "users/chapter.sgml">
<!ENTITY chap.security SYSTEM "security/chapter.sgml">
<!ENTITY chap.jails SYSTEM "jails/chapter.sgml">
<!ENTITY chap.mac SYSTEM "mac/chapter.sgml">
<!ENTITY chap.audit SYSTEM "audit/chapter.sgml">
<!ENTITY chap.disks SYSTEM "disks/chapter.sgml">
<!ENTITY chap.geom SYSTEM "geom/chapter.sgml">
<!ENTITY chap.filesystems SYSTEM "filesystems/chapter.sgml">
<!ENTITY chap.vinum SYSTEM "vinum/chapter.sgml">
<!ENTITY chap.virtualization SYSTEM "virtualization/chapter.sgml">
<!ENTITY chap.l10n SYSTEM "l10n/chapter.sgml">
<!ENTITY chap.cutting-edge SYSTEM "cutting-edge/chapter.sgml">
<!ENTITY chap.dtrace SYSTEM "dtrace/chapter.sgml">
<!-- Part Three -->
<![%chap.config;[
<!ENTITY chap.config SYSTEM "config/chapter.sgml">
]]>
<![%chap.boot;[
<!ENTITY chap.boot SYSTEM "boot/chapter.sgml">
]]>
<![%chap.users;[
<!ENTITY chap.users SYSTEM "users/chapter.sgml">
]]>
<![%chap.security;[
<!ENTITY chap.security SYSTEM "security/chapter.sgml">
]]>
<![%chap.jails;[
<!ENTITY chap.jails SYSTEM "jails/chapter.sgml">
]]>
<![%chap.mac;[
<!ENTITY chap.mac SYSTEM "mac/chapter.sgml">
]]>
<![%chap.audit;[
<!ENTITY chap.audit SYSTEM "audit/chapter.sgml">
]]>
<![%chap.disks;[
<!ENTITY chap.disks SYSTEM "disks/chapter.sgml">
]]>
<![%chap.geom;[
<!ENTITY chap.geom SYSTEM "geom/chapter.sgml">
]]>
<![%chap.filesystems;[
<!ENTITY chap.filesystems SYSTEM "filesystems/chapter.sgml">
]]>
<![%chap.vinum;[
<!ENTITY chap.vinum SYSTEM "vinum/chapter.sgml">
]]>
<![%chap.virtualization;[
<!ENTITY chap.virtualization SYSTEM "virtualization/chapter.sgml">
]]>
<![%chap.l10n;[
<!ENTITY chap.l10n SYSTEM "l10n/chapter.sgml">
]]>
<![%chap.cutting-edge;[
<!ENTITY chap.cutting-edge SYSTEM "cutting-edge/chapter.sgml">
]]>
<![%chap.dtrace;[
<!ENTITY chap.dtrace SYSTEM "dtrace/chapter.sgml">
]]>
<!-- Part four -->
<!ENTITY chap.serialcomms SYSTEM "serialcomms/chapter.sgml">
<!ENTITY chap.ppp-and-slip SYSTEM "ppp-and-slip/chapter.sgml">
<!ENTITY chap.mail SYSTEM "mail/chapter.sgml">
<!ENTITY chap.network-servers SYSTEM "network-servers/chapter.sgml">
<!ENTITY chap.firewalls SYSTEM "firewalls/chapter.sgml">
<!ENTITY chap.advanced-networking SYSTEM "advanced-networking/chapter.sgml">
<!-- Part Four -->
<![%chap.serialcomms;[
<!ENTITY chap.serialcomms SYSTEM "serialcomms/chapter.sgml">
]]>
<![%chap.ppp-and-slip;[
<!ENTITY chap.ppp-and-slip SYSTEM "ppp-and-slip/chapter.sgml">
]]>
<![%chap.mail;[
<!ENTITY chap.mail SYSTEM "mail/chapter.sgml">
]]>
<![%chap.network-servers;[
<!ENTITY chap.network-servers SYSTEM "network-servers/chapter.sgml">
]]>
<![%chap.firewalls;[
<!ENTITY chap.firewalls SYSTEM "firewalls/chapter.sgml">
]]>
<![%chap.advanced-networking;[
<!ENTITY chap.advanced-networking SYSTEM "advanced-networking/chapter.sgml">
]]>
<!-- Part five (appendices) -->
<!ENTITY chap.mirrors SYSTEM "mirrors/chapter.sgml">
<!ENTITY chap.mirrors.ftp.inc SYSTEM "mirrors.sgml.ftp.inc">
<!ENTITY chap.mirrors.cvsup.inc SYSTEM "mirrors.sgml.cvsup.inc">
<!-- Part Five (appendices) -->
<![%chap.mirrors;[
<!ENTITY chap.mirrors SYSTEM "mirrors/chapter.sgml">
]]>
<![%chap.mirrors.ftp.inc;[
<!ENTITY chap.mirrors.ftp.inc SYSTEM "mirrors.sgml.ftp.inc">
]]>
<![%chap.mirrors.cvsup.inc;[
<!ENTITY chap.mirrors.cvsup.inc SYSTEM "mirrors.sgml.cvsup.inc">
]]>
<![%chap.bibliography;[
<!ENTITY chap.bibliography SYSTEM "bibliography/chapter.sgml">
]]>
<![%chap.eresources;[
<!ENTITY chap.eresources SYSTEM "eresources/chapter.sgml">
]]>
<![%chap.eresources.www.inc;[
<!ENTITY chap.eresources.www.inc SYSTEM "eresources.sgml.www.inc">
]]>
<![%chap.pgpkeys;[
<!ENTITY chap.pgpkeys SYSTEM "pgpkeys/chapter.sgml">
]]>
<![%chap.freebsd-glossary;[
<!ENTITY chap.freebsd-glossary "&freebsd-glossary;">
]]>
<![%chap.index;[
<!ENTITY chap.index SYSTEM "index.sgml">
]]>
<!ENTITY chap.bibliography SYSTEM "bibliography/chapter.sgml">
<!ENTITY chap.eresources SYSTEM "eresources/chapter.sgml">
<!ENTITY chap.eresources.www.inc SYSTEM "eresources.sgml.www.inc">
<!ENTITY chap.pgpkeys SYSTEM "pgpkeys/chapter.sgml">
<!ENTITY chap.index SYSTEM "index.sgml">
<!ENTITY chap.colophon SYSTEM "colophon.sgml">
<!ENTITY chap.colophon SYSTEM "colophon.sgml">
<!-- IGNORE cases -->
<!-- Part One -->
<!ENTITY chap.introduction "">
<!ENTITY chap.install "">
<!ENTITY chap.basics "">
<!ENTITY chap.ports "">
<!ENTITY chap.x11 "">
<!-- Part Two -->
<!ENTITY chap.desktop "">
<!ENTITY chap.multimedia "">
<!ENTITY chap.kernelconfig "">
<!ENTITY chap.printing "">
<!ENTITY chap.linuxemu "">
<!-- Part Three -->
<!ENTITY chap.config "">
<!ENTITY chap.boot "">
<!ENTITY chap.users "">
<!ENTITY chap.security "">
<!ENTITY chap.jails "">
<!ENTITY chap.mac "">
<!ENTITY chap.audit "">
<!ENTITY chap.disks "">
<!ENTITY chap.geom "">
<!ENTITY chap.filesystems "">
<!ENTITY chap.vinum "">
<!ENTITY chap.virtualization "">
<!ENTITY chap.l10n "">
<!ENTITY chap.cutting-edge "">
<!ENTITY chap.dtrace "">
<!-- Part Four -->
<!ENTITY chap.serialcomms "">
<!ENTITY chap.ppp-and-slip "">
<!ENTITY chap.mail "">
<!ENTITY chap.network-servers "">
<!ENTITY chap.firewalls "">
<!ENTITY chap.advanced-networking "">
<!-- Part Five (appendices) -->
<!ENTITY chap.mirrors "">
<!ENTITY chap.mirrors.ftp.inc "">
<!ENTITY chap.mirrors.cvsup.inc "">
<!ENTITY chap.bibliography "">
<!ENTITY chap.eresources "">
<!ENTITY chap.eresources.www.inc "">
<!ENTITY chap.pgpkeys "">
<!ENTITY chap.freebsd-glossary "">
<!ENTITY chap.index "">

1
en_US.ISO8859-1/books/handbook/colophon.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!--
The FreeBSD Documentation Project

55
en_US.ISO8859-1/books/handbook/config/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!--
The FreeBSD Documentation Project
@ -88,13 +89,13 @@
<itemizedlist>
<listitem>
<para>Understand &unix; and &os; basics (<xref
linkend="basics">).</para>
linkend="basics"/>).</para>
</listitem>
<listitem>
<para>Be familiar with the basics of kernel
configuration/compilation
(<xref linkend="kernelconfig">).</para>
(<xref linkend="kernelconfig"/>).</para>
</listitem>
</itemizedlist>
</sect1>
@ -526,17 +527,17 @@ run_rc_command "$1"</programlisting>
<programlisting># /etc/crontab - root's crontab for &os;
#
# &dollar;&os;: src/etc/crontab,v 1.32 2002/11/22 16:13:39 tom Exp &dollar;
# <co id="co-comments">
# <co id="co-comments"/>
#
SHELL=/bin/sh
PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin <co id="co-env">
PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin <co id="co-env"/>
HOME=/var/log
#
#
#minute hour mday month wday who command <co id="co-field-descr">
#minute hour mday month wday who command <co id="co-field-descr"/>
#
#
*/5 * * * * root /usr/libexec/atrun <co id="co-main"></programlisting>
*/5 * * * * root /usr/libexec/atrun <co id="co-main"/></programlisting>
<calloutlist>
<callout arearefs="co-comments">
@ -906,7 +907,7 @@ dc1: [ITHREAD]</screen>
and the manual page of the driver to know what to add in
your kernel configuration file. For more information
about recompiling your kernel, please see
<xref linkend="kernelconfig">. If your card was detected
<xref linkend="kernelconfig"/>. If your card was detected
at boot by your kernel (<filename>GENERIC</filename>) you
do not have to build a new kernel.</para>
</listitem>
@ -1324,14 +1325,14 @@ round-trip min/avg/max/stddev = 0.700/0.729/0.766/0.025 ms</screen>
<command>netstat -rn</command> and make sure there is a
valid route to the host you are trying to reach. If there
is not, read on to
<xref linkend="advanced-networking">.</para>
<xref linkend="advanced-networking"/>.</para>
<para><errorname>ping: sendto: Permission denied</errorname>
error messages are often caused by a misconfigured firewall.
If <command>ipfw</command> is enabled in the kernel but no
rules have been defined, then the default policy is to deny
all traffic, even ping requests! Read on to
<xref linkend="firewalls"> for more information.</para>
<xref linkend="firewalls"/> for more information.</para>
<para>Sometimes performance of the card is poor, or below
average. In these cases it is best to set the media
@ -1446,7 +1447,7 @@ ifconfig_fxp0_alias7="inet 202.0.75.20 netmask 255.255.255.255"</programlisting>
and log management using &man.newsyslog.8;. Focus
will be on setting up and using <command>syslogd</command> on
a local machine. For more advanced setups using a separate
loghost, see <xref linkend="network-syslogd">.</para>
loghost, see <xref linkend="network-syslogd"/>.</para>
<sect2>
<title>Using <application>syslogd</application></title>
@ -1460,8 +1461,8 @@ ifconfig_fxp0_alias7="inet 202.0.75.20 netmask 255.255.255.255"</programlisting>
<literal>syslogd_flags</literal> in
<filename>/etc/rc.conf</filename>. Refer to &man.syslogd.8;
for more information on the arguments, and &man.rc.conf.5;,
<xref linkend="configtuning-core-configuration"> and <xref
linkend="configtuning-rcd"> for more information about
<xref linkend="configtuning-core-configuration"/> and <xref
linkend="configtuning-rcd"/> for more information about
<filename>/etc/rc.conf</filename> and the &man.rc.8;
subsystem.</para>
</sect2>
@ -1510,15 +1511,15 @@ ifconfig_fxp0_alias7="inet 202.0.75.20 netmask 255.255.255.255"</programlisting>
# separators. If you are sharing this file between systems, you
# may want to use only tabs as field separators here.
# Consult the &man.syslog.conf.5; manpage.
*.err;kern.warning;auth.notice;mail.crit /dev/console <co id="co-syslog-many-match">
*.err;kern.warning;auth.notice;mail.crit /dev/console <co id="co-syslog-many-match"/>
*.notice;authpriv.none;kern.debug;lpr.info;mail.crit;news.err /var/log/messages
security.* /var/log/security
auth.info;authpriv.info /var/log/auth.log
mail.info /var/log/maillog <co id="co-syslog-one-match">
mail.info /var/log/maillog <co id="co-syslog-one-match"/>
lpr.info /var/log/lpd-errs
ftp.info /var/log/xferlog
cron.* /var/log/cron
*.=debug /var/log/debug.log <co id="co-syslog-comparison">
*.=debug /var/log/debug.log <co id="co-syslog-comparison"/>
*.emerg *
# uncomment this to log all writes to /dev/console to /var/log/console.log
#console.info /var/log/console.log
@ -1531,7 +1532,7 @@ cron.* /var/log/cron
# news.crit /var/log/news/news.crit
# news.err /var/log/news/news.err
# news.notice /var/log/news/news.notice
!ppp <co id="co-syslog-prog-spec">
!ppp <co id="co-syslog-prog-spec"/>
*.* /var/log/ppp.log
!*</programlisting>
@ -1602,7 +1603,7 @@ cron.* /var/log/cron
For more information about <filename>syslog.conf</filename>,
its syntax, and more advanced usage examples, see
&man.syslog.conf.5; and <xref
linkend="network-syslogd">.</para>
linkend="network-syslogd"/>.</para>
</sect2>
<sect2>
@ -1724,8 +1725,8 @@ cron.* /var/log/cron
<informaltable frame="none" pgwide="1">
<tgroup cols="2">
<colspec colwidth="1*">
<colspec colwidth="2*">
<colspec colwidth="1*"/>
<colspec colwidth="2*"/>
<tbody>
<row>
@ -1812,8 +1813,8 @@ cron.* /var/log/cron
<informaltable frame="none" pgwide="1">
<tgroup cols="2">
<colspec colwidth="1*">
<colspec colwidth="2*">
<colspec colwidth="1*"/>
<colspec colwidth="2*"/>
<tbody>
<row>
@ -1986,7 +1987,7 @@ kern.maxfiles: 2088 -&gt; 5000</screen>
the machine boots, add them to the
<filename>/etc/sysctl.conf</filename> file. For more
information see the &man.sysctl.conf.5; manual page and the
<xref linkend="configtuning-sysctlconf">.</para>
<xref linkend="configtuning-sysctlconf"/>.</para>
<sect2 id="sysctl-readonly">
<sect2info>
@ -2678,7 +2679,7 @@ kern.maxvnodes: 100000</screen>
<para>For information on how to encrypt swap space, what options
for this task exist and why it should be done, please refer to
<xref linkend="swap-encrypting"> of the Handbook.</para>
<xref linkend="swap-encrypting"/> of the Handbook.</para>
<sect2 id="new-drive-swap">
<title>Swap on a New or Existing Hard Drive</title>
@ -2686,8 +2687,8 @@ kern.maxvnodes: 100000</screen>
<para>Adding a new hard drive for swap gives better performance
than adding a partition on an existing drive. Setting up
partitions and hard drives is explained in
<xref linkend="disks-adding">.
<xref linkend="configtuning-initial"> discusses partition
<xref linkend="disks-adding"/>.
<xref linkend="configtuning-initial"/> discusses partition
layouts and swap partition size considerations.</para>
<para>Use &man.swapon.8; to add a swap partition to the system.
@ -2747,7 +2748,7 @@ kern.maxvnodes: 100000</screen>
<programlisting>device md</programlisting>
<para>For information on building your own kernel, please
refer to <xref linkend="kernelconfig">.</para>
refer to <xref linkend="kernelconfig"/>.</para>
</listitem>
<listitem>
@ -3271,7 +3272,7 @@ hw.acpi.s4bios: 0</screen>
isolate the steps to reproduce the panic (if possible) and
get a backtrace. Follow the advice for enabling
<literal>options DDB</literal> and setting up a serial
console (see <xref linkend="serialconsole-ddb">) or setting
console (see <xref linkend="serialconsole-ddb"/>) or setting
up a &man.dump.8; partition. You can get a backtrace in
<acronym>DDB</acronym> with <literal>tr</literal>. If you
have to handwrite the backtrace, be sure to at least get the

52
en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!--
The FreeBSD Documentation Project
@ -100,12 +101,12 @@
<itemizedlist>
<listitem>
<para>Properly set up your network connection (<xref
linkend="advanced-networking">).</para>
linkend="advanced-networking"/>).</para>
</listitem>
<listitem>
<para>Know how to install additional third-party
software (<xref linkend="ports">).</para>
software (<xref linkend="ports"/>).</para>
</listitem>
</itemizedlist>
@ -236,7 +237,7 @@ MergeChanges /etc/ /var/named/etc/</programlisting>
are either accepted, open an editor, or
<command>freebsd-update</command> will abort. When in doubt,
backup <filename class="directory">/etc</filename> and just
accept the merges. See <xref linkend="mergemaster"> for more
accept the merges. See <xref linkend="mergemaster"/> for more
information about the <command>mergemaster</command>
command.</para>
@ -317,7 +318,7 @@ MergeChanges /etc/ /var/named/etc/</programlisting>
class="directory">/boot/GENERIC</filename>. It will be helpful
in diagnosing a variety of problems, and in performing version
upgrades using <command>freebsd-update</command> as described in
<xref linkend="freebsdupdate-upgrade">.</para>
<xref linkend="freebsdupdate-upgrade"/>.</para>
</note>
<para>Unless the default configuration in
@ -742,7 +743,7 @@ Fetching 133 new ports or files... done.</screen>
<para>The sources and the installed copy of the &os; documentation
can be updated with <application>CVSup</application>, using a
mechanism similar to the one employed for the base system
sources (c.f. <xref linkend="makeworld">). This section
sources (c.f. <xref linkend="makeworld"/>). This section
describes:</para>
<itemizedlist>
@ -825,7 +826,7 @@ Fetching 133 new ports or files... done.</screen>
<para>Change <replaceable>cvsup.FreeBSD.org</replaceable> to the
nearest <application>CVSup</application> server. See <xref
linkend="cvsup-mirrors"> for a complete listing of mirror
linkend="cvsup-mirrors"/> for a complete listing of mirror
sites.</para>
<para>The initial download of the documentation sources may take a
@ -1462,11 +1463,12 @@ DOCSUPFILE?= /usr/share/examples/cvsup/doc-supfile</programlisting>
</note>
</listitem>
<indexterm>
<primary>-CURRENT</primary>
<secondary>Syncing with CTM</secondary>
</indexterm>
<listitem>
<indexterm>
<primary>-CURRENT</primary>
<secondary>Syncing with CTM</secondary>
</indexterm>
<para>Use the <application><link
linkend="ctm">CTM</link></application> facility. If you
have very bad connectivity (high price connections or
@ -1634,6 +1636,7 @@ DOCSUPFILE?= /usr/share/examples/cvsup/doc-supfile</programlisting>
<primary>-STABLE</primary>
<secondary>syncing with <application>CVSup</application></secondary>
</indexterm>
<listitem>
<para>Use the <link linkend="cvsup">cvsup</link> program
with the <filename>supfile</filename> named
@ -1649,11 +1652,12 @@ DOCSUPFILE?= /usr/share/examples/cvsup/doc-supfile</programlisting>
environment.</para>
</listitem>
<indexterm>
<primary>-STABLE</primary>
<secondary>syncing with CTM</secondary>
</indexterm>
<listitem>
<indexterm>
<primary>-STABLE</primary>
<secondary>syncing with CTM</secondary>
</indexterm>
<para>Use the <application><link
linkend="ctm">CTM</link></application> facility. If
you do not have a fast and inexpensive connection to
@ -1670,11 +1674,12 @@ DOCSUPFILE?= /usr/share/examples/cvsup/doc-supfile</programlisting>
Otherwise, use <application>CTM</application>.</para>
</listitem>
<indexterm>
<primary>-STABLE</primary>
<secondary>compiling</secondary>
</indexterm>
<listitem>
<indexterm>
<primary>-STABLE</primary>
<secondary>compiling</secondary>
</indexterm>
<para>Before compiling &os.stable;, read the
<filename>Makefile</filename> in <filename>/usr/src</filename>
carefully. You should at least <link
@ -1842,7 +1847,7 @@ DOCSUPFILE?= /usr/share/examples/cvsup/doc-supfile</programlisting>
<para>We also assume that you have already obtained the sources to a
newer system. If the sources available on the particular system are
old too, see <xref linkend="synching"> for detailed help about
old too, see <xref linkend="synching"/> for detailed help about
synchronizing them to a newer version.</para>
<para>Updating the system from sources is a bit more subtle than it
@ -2428,7 +2433,7 @@ Script done, &hellip;</screen>
<para>You should reboot into single user mode to test the new kernel
works. Do this by following the instructions in
<xref linkend="makeworld-singleuser">.</para>
<xref linkend="makeworld-singleuser"/>.</para>
</sect2>
<sect2 id="make-installworld">
@ -2787,10 +2792,11 @@ Script done, &hellip;</screen>
<qandaentry>
<question>
<indexterm><primary>signal 11</primary></indexterm>
<para>My compile failed with lots of signal 11 (or other signal
number) errors. What has happened?</para>
</question>
<indexterm><primary>signal 11</primary></indexterm>
<answer>
<para>This is normally indicative of hardware problems.
@ -3047,7 +3053,7 @@ Building everything..
system upgrade process.</para>
<para>We assume you are following the steps outlined in <xref
linkend="canonical-build">. After the <command>make
linkend="canonical-build"/>. After the <command>make
<maketarget>installworld</maketarget></command> and the subsequent
<command>mergemaster</command> commands have finished successfully, you
should check for obsolete files and libraries as follows:</para>
@ -3189,7 +3195,7 @@ Building everything..
<para>Now that all that is done, you are ready to build
everything. Build the kernel and world as described in <xref
linkend="make-buildworld"> on the build machine,
linkend="make-buildworld"/> on the build machine,
but do not install anything. After the build has finished, go
to the test machine, and install the kernel you just
built. If this machine mounts <filename>/usr/src</filename>

13
en_US.ISO8859-1/books/handbook/desktop/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!--
The FreeBSD Documentation Project
$FreeBSD$
@ -37,7 +38,7 @@
<para>As FreeBSD features Linux binary compatibility, many
applications originally developed for Linux are available for
your desktop. It is strongly recommended that you read
<xref linkend="linuxemu"> before installing any of the Linux
<xref linkend="linuxemu"/> before installing any of the Linux
applications. Many of the ports using the Linux binary
compatibility start with <quote>linux-</quote>. Remember this
when you search for a particular port, for instance with
@ -84,18 +85,18 @@
<itemizedlist>
<listitem>
<para>Know how to install additional third-party software
(<xref linkend="ports">).</para>
(<xref linkend="ports"/>).</para>
</listitem>
<listitem>
<para>Know how to install additional Linux software
(<xref linkend="linuxemu">).</para>
(<xref linkend="linuxemu"/>).</para>
</listitem>
</itemizedlist>
<para>For information on how to get a multimedia environment, read
<xref linkend="multimedia">. If you want to set up and use
electronic mail, please refer to <xref linkend="mail">.</para>
<xref linkend="multimedia"/>. If you want to set up and use
electronic mail, please refer to <xref linkend="mail"/>.</para>
</sect1>
<sect1 id="desktop-browsers">
@ -116,7 +117,7 @@
<para><application>KDE</application> and
<application>GNOME</application> already provide HTML browsers.
Please refer to <xref linkend="x11-wm"> for more information on
Please refer to <xref linkend="x11-wm"/> for more information on
how to set up these complete desktops.</para>
<para>If you are looking for light-weight browsers, you should

78
en_US.ISO8859-1/books/handbook/disks/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!--
The FreeBSD Documentation Project
@ -74,7 +75,7 @@
<itemizedlist>
<listitem>
<para>Know how to configure and install a new FreeBSD kernel
(<xref linkend="kernelconfig">).</para>
(<xref linkend="kernelconfig"/>).</para>
</listitem>
</itemizedlist>
</sect1>
@ -413,11 +414,11 @@
</authorgroup>
</sect3info>
<title>Concatenated Disk Driver (CCD) Configuration</title>
<indexterm><primary>RAID</primary><secondary>software</secondary></indexterm>
<indexterm><primary>RAID</primary><secondary>CCD</secondary></indexterm>
<title>Concatenated Disk Driver (CCD) Configuration</title>
<para>When choosing a mass storage solution the most important
factors to consider are speed, reliability, and cost. It is
rare to have all three in balance; normally a fast, reliable
@ -467,7 +468,7 @@ ad3: 29333MB &lt;WDC WD307AA&gt; [59598/16/63] at ata1-slave UDMA33</programlist
<para>Next, consider how to attach them as part of the file
system. You should research both &man.vinum.4; (<xref
linkend="vinum-vinum">) and &man.ccd.4;. In this
linkend="vinum-vinum"/>) and &man.ccd.4;. In this
particular configuration, &man.ccd.4; was chosen.</para>
</sect4>
@ -537,7 +538,7 @@ bsdlabel -e ad3</programlisting>
build the &man.ccd.4;. To do that, use &man.ccdconfig.8;,
with options similar to the following:</para>
<programlisting>ccdconfig ccd0<co id="co-ccd-dev"> 32<co id="co-ccd-interleave"> 0<co id="co-ccd-flags"> /dev/ad1e<co id="co-ccd-devs"> /dev/ad2e /dev/ad3e</programlisting>
<programlisting>ccdconfig ccd0<co id="co-ccd-dev"/> 32<co id="co-ccd-interleave"/> 0<co id="co-ccd-flags"/> /dev/ad1e<co id="co-ccd-devs"/> /dev/ad2e /dev/ad3e</programlisting>
<para>The use and meaning of each option is shown
below:</para>
@ -630,7 +631,7 @@ bsdlabel -e ad3</programlisting>
storage. &man.vinum.4; implements the RAID-0, RAID-1 and
RAID-5 models, both individually and in combination.</para>
<para>See <xref linkend="vinum-vinum"> for more
<para>See <xref linkend="vinum-vinum"/> for more
information about &man.vinum.4;.</para>
</sect3>
</sect2>
@ -847,7 +848,7 @@ da0: 126MB (258048 512 byte sectors: 64H 32S/T 126C)</screen>
&lt;Generic Traveling Disk 1.11&gt; at scbus0 target 0 lun 0 (da0,pass0)</screen>
<para>If the drive comes with a file system, you should be able
to mount it. The <xref linkend="disks-adding"> will help you
to mount it. The <xref linkend="disks-adding"/> will help you
to format and create partitions on the USB drive if
needed.</para>
@ -1234,7 +1235,7 @@ scsibus1:
<para>Make sure that <replaceable>2,0</replaceable> is set
appropriately, as described in
<xref linkend="cdrecord">.</para>
<xref linkend="cdrecord"/>.</para>
</step>
</procedure>
@ -1414,11 +1415,12 @@ scsibus1:
</authorgroup>
</sect2info>
<title>Using the ATAPI/CAM Driver</title>
<indexterm>
<primary>CD burner</primary>
<secondary>ATAPI/CAM driver</secondary>
</indexterm>
<title>Using the ATAPI/CAM Driver</title>
<para>This driver allows ATAPI devices (CD-ROM, CD-RW, DVD
drives etc...) to be accessed through the SCSI subsystem, and
@ -1540,7 +1542,7 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c
removable hard drive. However, this media is not
compatible with most DVD-ROM drives and DVD-Video players;
only a few DVD writers support the DVD-RAM format. Read
the <xref linkend="creating-dvd-ram"> for more information
the <xref linkend="creating-dvd-ram"/> for more information
on DVD-RAM use.</para>
</listitem>
@ -1587,7 +1589,7 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c
devices, therefore the <link linkend="atapicam">ATAPI/CAM
support</link> must be added to your kernel. If your burner
uses the USB interface this addition is useless, and you
should read the <xref linkend="usb-disks"> for more details on
should read the <xref linkend="usb-disks"/> for more details on
USB devices configuration.</para>
<para>You also have to enable DMA access for ATAPI devices, this
@ -1687,14 +1689,14 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c
</note>
</sect2>
<indexterm>
<primary>DVD</primary>
<secondary>DVD-Video</secondary>
</indexterm>
<sect2>
<title>Burning a DVD-Video</title>
<indexterm>
<primary>DVD</primary>
<secondary>DVD-Video</secondary>
</indexterm>
<para>A DVD-Video is a specific file layout based on ISO 9660
and the micro-UDF (M-UDF) specifications. The DVD-Video also
presents a specific data structure hierarchy, it is the reason
@ -1718,14 +1720,14 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c
<option>-dvd-compat</option> &man.growisofs.1; option.</para>
</sect2>
<indexterm>
<primary>DVD</primary>
<secondary>DVD+RW</secondary>
</indexterm>
<sect2>
<title>Using a DVD+RW</title>
<indexterm>
<primary>DVD</primary>
<secondary>DVD+RW</secondary>
</indexterm>
<para>Unlike CD-RW, a virgin DVD+RW needs to be formatted before
first use. The &man.growisofs.1; program will take care of it
automatically whenever appropriate, which is the
@ -1774,14 +1776,14 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c
<screen>&prompt.root; <userinput>growisofs -Z <replaceable>/dev/cd0</replaceable>=<replaceable>/dev/zero</replaceable></userinput></screen>
</sect2>
<indexterm>
<primary>DVD</primary>
<secondary>DVD-RW</secondary>
</indexterm>
<sect2>
<title>Using a DVD-RW</title>
<indexterm>
<primary>DVD</primary>
<secondary>DVD-RW</secondary>
</indexterm>
<para>A DVD-RW accepts two disc formats: the incremental
sequential one and the restricted overwrite. By default
DVD-RW discs are in sequential format.</para>
@ -1902,6 +1904,7 @@ cd0: Attempt to query device size failed: NOT READY, Medium not present - tray c
<sect2 id="creating-dvd-ram">
<title>Using a DVD-RAM</title>
<indexterm>
<primary>DVD</primary>
<secondary>DVD-RAM</secondary>
@ -2900,7 +2903,7 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
distress later.</para>
</sect3>
<![ %not.published; [
<![%not.published;[
<sect3>
<title>* I Did Not Prepare for the Disaster, What Now?</title>
@ -2908,7 +2911,6 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
<para></para>
</sect3>
]]>
</sect2>
</sect1>
@ -3253,7 +3255,7 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
<para>The stock <filename>GENERIC</filename> kernel does not
have this enabled by default, so you will have to configure,
build and install a custom kernel in order to use disk quotas.
Please refer to <xref linkend="kernelconfig"> for more
Please refer to <xref linkend="kernelconfig"/> for more
information on kernel configuration.</para>
<para>Next you will need to enable disk quotas in
@ -3508,7 +3510,7 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
<para>FreeBSD offers excellent online protections against
unauthorized data access. File permissions and Mandatory Access
Control (MAC) (see <xref linkend="mac">) help prevent
Control (MAC) (see <xref linkend="mac"/>) help prevent
unauthorized third-parties from accessing data while the
operating system is active and the computer is powered up.
However, the permissions enforced by the operating system are
@ -3553,7 +3555,7 @@ Password:</screen>
<para><literal>options GEOM_BDE</literal></para>
<para>Rebuild the kernel as described in <xref
linkend="kernelconfig">.</para>
linkend="kernelconfig"/>.</para>
<para>Reboot into the new kernel.</para>
</step>
@ -3584,7 +3586,7 @@ Password:</screen>
<title>Add the New Hard Drive</title>
<para>Install the new drive to the system as explained in
<xref linkend="disks-adding">. For the purposes of this
<xref linkend="disks-adding"/>. For the purposes of this
example, a new hard drive partition has been added as
<filename>/dev/ad4s1c</filename>. The
<filename>/dev/ad0s1<replaceable>*</replaceable></filename>
@ -3932,7 +3934,7 @@ gbde_lockdir="/etc/gbde"</programlisting>
device crypto</programlisting>
<para>Rebuild the kernel as described in <xref
linkend="kernelconfig">.</para>
linkend="kernelconfig"/>.</para>
<para>Alternatively, the <command>geli</command> module can
be loaded at boot time. Add the following line to the
@ -4269,18 +4271,18 @@ Device 1K-blocks Used Avail Capacity
<itemizedlist>
<listitem>
<para>Understand &unix; and &os; basics
(<xref linkend="basics">).</para>
(<xref linkend="basics"/>).</para>
</listitem>
<listitem>
<para>Know how to configure network interfaces and other
core &os; subsystems
(<xref linkend="config-tuning">).</para>
(<xref linkend="config-tuning"/>).</para>
</listitem>
<listitem>
<para>Have a good understanding of &os; networking
(<xref linkend="network-communication">).</para>
(<xref linkend="network-communication"/>).</para>
</listitem>
<listitem>
@ -4563,7 +4565,7 @@ Device 1K-blocks Used Avail Capacity
other, and both are configured as primary nodes, the
condition is called <literal>split-brain</literal>. To
troubleshoot this situation, follow the steps described in
<xref linkend="disks-hast-sb">.</para>
<xref linkend="disks-hast-sb"/>.</para>
</caution>
<para>Verify the result with the
@ -4619,7 +4621,7 @@ Device 1K-blocks Used Avail Capacity
same network segment to share an IP address. Set up
<acronym>CARP</acronym> on both nodes of the cluster
according to the documentation available in
<xref linkend="carp">. After setup, each node will have its
<xref linkend="carp"/>. After setup, each node will have its
own <devicename>carp0</devicename> interface with a shared
IP address <replaceable>172.16.0.254</replaceable>. The
primary <acronym>HAST</acronym> node of the cluster must be

9
en_US.ISO8859-1/books/handbook/dtrace/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!--
Recently I suggested to myself that this should become a profiling
and debugging chapter, which covers things like ktrace(1) and
@ -68,23 +69,23 @@ that might make this chapter too large.
<itemizedlist>
<listitem>
<para>Understand &unix; and &os; basics
(<xref linkend="basics">).</para>
(<xref linkend="basics"/>).</para>
</listitem>
<listitem>
<para>Be familiar with
the basics of kernel configuration/compilation
(<xref linkend="kernelconfig">).</para>
(<xref linkend="kernelconfig"/>).</para>
</listitem>
<listitem>
<para>Have some familiarity with security and how it
pertains to &os; (<xref linkend="security">).</para>
pertains to &os; (<xref linkend="security"/>).</para>
</listitem>
<listitem>
<para>Understand how to obtain and rebuild the &os; sources
(<xref linkend="updating-upgrading">).</para>
(<xref linkend="updating-upgrading"/>).</para>
</listitem>
</itemizedlist>

1
en_US.ISO8859-1/books/handbook/eresources/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!--
The FreeBSD Documentation Project

11
en_US.ISO8859-1/books/handbook/filesystems/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!--
The FreeBSD Documentation Project
$FreeBSD$
@ -74,23 +75,23 @@
<itemizedlist>
<listitem>
<para>Understand &unix; and &os; basics
(<xref linkend="basics">).</para>
(<xref linkend="basics"/>).</para>
</listitem>
<listitem>
<para>Be familiar with
the basics of kernel configuration/compilation
(<xref linkend="kernelconfig">).</para>
(<xref linkend="kernelconfig"/>).</para>
</listitem>
<listitem>
<para>Feel comfortable installing third party software
in &os; (<xref linkend="ports">).</para>
in &os; (<xref linkend="ports"/>).</para>
</listitem>
<listitem>
<para>Have some familiarity with disks, storage and
device names in &os; (<xref linkend="disks">).</para>
device names in &os; (<xref linkend="disks"/>).</para>
</listitem>
</itemizedlist>
</sect1>
@ -220,7 +221,7 @@ example 17547136 0 17547136 0% /example</screen>
and users are able to browse it as in the
following example:</para>
<screen>&prompt.root <userinput>cd /example</userinput>
<screen>&prompt.root; <userinput>cd /example</userinput>
&prompt.root; <userinput>ls</userinput>
&prompt.root; <userinput>touch testfile</userinput>
&prompt.root; <userinput>ls -al</userinput>

15
en_US.ISO8859-1/books/handbook/firewalls/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!--
The FreeBSD Documentation Project
@ -310,7 +311,7 @@
paired with &man.carp.4; to create failover firewalls using
<acronym>PF</acronym>. More information on
<acronym>CARP</acronym> can be found in
<xref linkend="carp"> of the Handbook.</para>
<xref linkend="carp"/> of the Handbook.</para>
<para>The <acronym>PF</acronym> kernel options can be found in
<filename>/usr/src/sys/conf/NOTES</filename> and are reproduced
@ -681,7 +682,7 @@ ipnat_rules="/etc/ipnat.rules" # rules definition file for ipnat</programlist
<para>There is a way to build IPF rules that utilizes the power
of script symbolic substitution. For more information, see
<xref linkend="firewalls-ipf-rules-script">.</para>
<xref linkend="firewalls-ipf-rules-script"/>.</para>
</sect2>
<sect2>
@ -1743,11 +1744,11 @@ block in log first quick on dc0 all
<informaltable frame="none" pgwide="1">
<tgroup cols="2">
<colspec colwidth="1*">
<colspec colwidth="1*"/>
<colspec colwidth="1*">
<colspec colwidth="1*"/>
<colspec colwidth="1*">
<colspec colwidth="1*"/>
<tbody>
<row>
@ -2318,7 +2319,7 @@ ipfw add deny out</programlisting>
<varname>firewall_logging</varname> variable will do is
setting the <varname>net.inet.ip.fw.verbose</varname> sysctl
variable to the value of <literal>1</literal> (see <xref
linkend="firewalls-ipfw-enable">). There is no
linkend="firewalls-ipfw-enable"/>). There is no
<filename>rc.conf</filename> variable to set log limitations,
but it can be set via sysctl variable, manually or from the
<filename>/etc/sysctl.conf</filename> file:</para>
@ -2328,7 +2329,7 @@ ipfw add deny out</programlisting>
<para>If your machine is acting as a gateway, i.e., providing
Network Address Translation (NAT) via &man.natd.8;, please
refer to <xref linkend="network-natd"> for information
refer to <xref linkend="network-natd"/> for information
regarding the required <filename>/etc/rc.conf</filename>
options.</para>
</sect2>

13
en_US.ISO8859-1/books/handbook/geom/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!--
The FreeBSD Documentation Project
$FreeBSD$
@ -70,12 +71,12 @@
<itemizedlist>
<listitem>
<para>Understand how &os; treats disk devices
(<xref linkend="disks">).</para>
(<xref linkend="disks"/>).</para>
</listitem>
<listitem>
<para>Know how to configure and install a new &os; kernel
(<xref linkend="kernelconfig">).</para>
(<xref linkend="kernelconfig"/>).</para>
</listitem>
</itemizedlist>
</sect1>
@ -136,7 +137,7 @@
<mediaobject>
<imageobject>
<imagedata fileref="geom/striping" align="center">
<imagedata fileref="geom/striping" align="center"/>
</imageobject>
<textobject>
@ -466,6 +467,9 @@ OK? <userinput>boot</userinput></screen>
</authorgroup>
</sect1info>
<title><acronym>RAID</acronym>3 - Byte-level Striping with Dedicated
Parity</title>
<indexterm>
<primary>GEOM</primary>
</indexterm>
@ -473,9 +477,6 @@ OK? <userinput>boot</userinput></screen>
<primary>RAID3</primary>
</indexterm>
<title><acronym>RAID</acronym>3 - Byte-level Striping with Dedicated
Parity</title>
<para><acronym>RAID</acronym>3 is a method used to combine several
disk drives into a single volume with a dedicated parity
disk. In a <acronym>RAID</acronym>3 system, data is split up

232
en_US.ISO8859-1/books/handbook/install/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!--
The FreeBSD Documentation Project
@ -39,7 +40,7 @@
to 9.0-RELEASE using <application>sysinstall</application> for
installation. This chapter describes the use of <application>sysinstall</application>
to install &os;. The use of <application>bsdinstall</application>
is covered in <xref linkend="bsdinstall">.</para>
is covered in <xref linkend="bsdinstall"/>.</para>
<para>After reading this chapter, you will know:</para>
@ -98,7 +99,7 @@
Depending on the method you choose to install &os;, you may
also need a floppy drive, a supported CDROM drive, and in some
case a network adapter. This will be covered by the <xref
linkend="install-boot-media">.</para>
linkend="install-boot-media"/>.</para>
<sect3>
<title>&os;/&arch.i386; and &os;/&arch.pc98;</title>
@ -144,7 +145,7 @@
<para>To install &os;/&arch.sparc64;, you will need a supported
platform (see <xref
linkend="install-hardware-supported">).</para>
linkend="install-hardware-supported"/>).</para>
<para>You will need a dedicated disk for &os;/&arch.sparc64;. It
is not possible to share a disk with another operating
@ -200,10 +201,10 @@
<title>Sample Device Inventory</title>
<tgroup cols="4">
<colspec colwidth="2*">
<colspec colwidth="1*">
<colspec colwidth="1*">
<colspec colwidth="4*">
<colspec colwidth="2*"/>
<colspec colwidth="1*"/>
<colspec colwidth="1*"/>
<colspec colwidth="4*"/>
<thead>
<row>
<entry>Device Name</entry>
@ -574,13 +575,13 @@
<para>If you have purchased FreeBSD on CD or DVD then you already have
everything you need, and should proceed to the next section
(<xref linkend="install-boot-media">).</para>
(<xref linkend="install-boot-media"/>).</para>
<para>If you have not obtained the FreeBSD installation files you should
skip ahead to <xref linkend="install-diff-media"> which explains how
skip ahead to <xref linkend="install-diff-media"/> which explains how
to prepare to install FreeBSD from any of the above. After reading
that section, you should come back here, and read on to
<xref linkend="install-boot-media">.</para>
<xref linkend="install-boot-media"/>.</para>
</sect2>
<sect2 id="install-boot-media">
@ -627,7 +628,7 @@
<para>A different directory path is used for
&os;&nbsp;9.0-RELEASE and later versions. Details of
download and installation of &os;&nbsp;9.0-RELEASE and
later is covered in <xref linkend="bsdinstall">.</para>
later is covered in <xref linkend="bsdinstall"/>.</para>
</tip>
<para>The memory stick image has a <filename>.img</filename>
@ -904,7 +905,7 @@ We can take no responsibility for lost disk contents!</literallayout>
<step>
<para>If you prepared a <quote>bootable</quote> USB stick, as described in
<xref linkend="install-boot-media">, then plug in your USB
<xref linkend="install-boot-media"/>, then plug in your USB
stick before turning on the computer.</para>
<para>If you are booting from CDROM, then you will need to turn on
@ -914,7 +915,7 @@ We can take no responsibility for lost disk contents!</literallayout>
<note>
<para>For &os;&nbsp;7.<replaceable>X</replaceable>, installation
boot floppies are available and can be prepared as
described in <xref linkend="install-boot-media">. One of
described in <xref linkend="install-boot-media"/>. One of
them will be the first boot disc:
<filename>boot.flp</filename>. Put this disc in your
floppy drive and boot the computer.</para>
@ -1005,7 +1006,7 @@ Insert disk labelled "Kernel floppy 1" and press any key...</screen>
<mediaobject>
<imageobject>
<imagedata fileref="install/boot-loader-menu" format="PNG">
<imagedata fileref="install/boot-loader-menu" format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -1045,8 +1046,8 @@ Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4.</screen>
<screenco>
<areaspec>
<area id="prompt-single" coords="1 5">
<area id="prompt-smp" coords="2 5">
<area id="prompt-single" coords="1 5"/>
<area id="prompt-smp" coords="2 5"/>
</areaspec>
<screen><prompt>ok </prompt>
@ -1086,7 +1087,7 @@ Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4.</screen>
<para>Do this now, to review the text that scrolled off the screen when
the kernel was carrying out the device probes. You will see text
similar to <xref linkend="install-dev-probe">, although the precise
similar to <xref linkend="install-dev-probe"/>, although the precise
text will differ depending on the devices that you have in your
computer.</para>
@ -1163,7 +1164,7 @@ Mounting root from ufs:/dev/md0c
<filename>GENERIC</filename> kernel, such as sound cards.</para>
<para>After the procedure of device
probing, you will see <xref linkend="config-country">. Use the
probing, you will see <xref linkend="config-country"/>. Use the
arrow key to choose a country, region, or group. Then press
<keycap>Enter</keycap>, it will set your country
easily.</para>
@ -1173,7 +1174,7 @@ Mounting root from ufs:/dev/md0c
<mediaobject>
<imageobject>
<imagedata fileref="install/config-country" format="PNG">
<imagedata fileref="install/config-country" format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -1189,7 +1190,7 @@ Mounting root from ufs:/dev/md0c
<mediaobject>
<imageobject>
<imagedata fileref="install/config-keymap" format="PNG">
<imagedata fileref="install/config-keymap" format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -1217,7 +1218,7 @@ Mounting root from ufs:/dev/md0c
<para>To review this information, ensure that the
<guimenuitem>Usage</guimenuitem> entry is highlighted and that the
<guibutton>[Select]</guibutton> button is selected, as shown in <xref
linkend="sysinstall-main3">, then press <keycap>Enter</keycap>.</para>
linkend="sysinstall-main3"/>, then press <keycap>Enter</keycap>.</para>
<para>The instructions for using the menu system will be displayed. After
reviewing them, press <keycap>Enter</keycap> to return to the Main
@ -1228,7 +1229,7 @@ Mounting root from ufs:/dev/md0c
<mediaobject>
<imageobject>
<imagedata fileref="install/main1" format="PNG">
<imagedata fileref="install/main1" format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -1245,7 +1246,7 @@ Mounting root from ufs:/dev/md0c
<mediaobject>
<imageobject>
<imagedata fileref="install/main-doc" format="PNG">
<imagedata fileref="install/main-doc" format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -1257,7 +1258,7 @@ Mounting root from ufs:/dev/md0c
<mediaobject>
<imageobject>
<imagedata fileref="install/docmenu1" format="PNG">
<imagedata fileref="install/docmenu1" format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -1287,7 +1288,7 @@ Mounting root from ufs:/dev/md0c
<mediaobject>
<imageobject>
<imagedata fileref="install/main-keymap" format="PNG">
<imagedata fileref="install/main-keymap" format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -1307,7 +1308,7 @@ Mounting root from ufs:/dev/md0c
<mediaobject>
<imageobject>
<imagedata fileref="install/keymap" format="PNG">
<imagedata fileref="install/keymap" format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -1325,7 +1326,7 @@ Mounting root from ufs:/dev/md0c
<mediaobject>
<imageobject>
<imagedata fileref="install/main-options" format="PNG">
<imagedata fileref="install/main-options" format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -1335,7 +1336,7 @@ Mounting root from ufs:/dev/md0c
<mediaobject>
<imageobject>
<imagedata fileref="install/options" format="PNG">
<imagedata fileref="install/options" format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -1369,7 +1370,7 @@ Mounting root from ufs:/dev/md0c
<mediaobject>
<imageobject>
<imagedata fileref="install/main-std" format="PNG">
<imagedata fileref="install/main-std" format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -1525,7 +1526,7 @@ Mounting root from ufs:/dev/md0c
<para>Press <keycap>Enter</keycap> as instructed. You will then be
shown a list of all the hard drives that the kernel found when it
carried out the device probes.
<xref linkend="sysinstall-fdisk-drive1"> shows an example from a
<xref linkend="sysinstall-fdisk-drive1"/> shows an example from a
system with two IDE disks. They have been called
<devicename>ad0</devicename> and <devicename>ad2</devicename>.</para>
@ -1534,7 +1535,7 @@ Mounting root from ufs:/dev/md0c
<mediaobject>
<imageobject>
<imagedata fileref="install/fdisk-drive1" format="PNG">
<imagedata fileref="install/fdisk-drive1" format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -1574,7 +1575,7 @@ Mounting root from ufs:/dev/md0c
<para>You should select the disk on which you want to install FreeBSD,
and then press &gui.ok;.
<application>FDisk</application> will start, with a display similar to
that shown in <xref linkend="sysinstall-fdisk1">.</para>
that shown in <xref linkend="sysinstall-fdisk1"/>.</para>
<para>The <application>FDisk</application> display is broken into three
sections.</para>
@ -1600,7 +1601,7 @@ Mounting root from ufs:/dev/md0c
<mediaobject>
<imageobject>
<imagedata fileref="install/fdisk-edit1" format="PNG">
<imagedata fileref="install/fdisk-edit1" format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -1619,7 +1620,7 @@ Mounting root from ufs:/dev/md0c
you should select the newly created FreeBSD slice using the arrow
keys, and press <keycap>S</keycap> to mark the slice as being
bootable. The screen will then look very similar to
<xref linkend="sysinstall-fdisk2">. Note the
<xref linkend="sysinstall-fdisk2"/>. Note the
<literal>A</literal> in the <literal>Flags</literal> column, which
indicates that this slice is <emphasis>active</emphasis>, and will be
booted from.</para>
@ -1643,7 +1644,7 @@ Mounting root from ufs:/dev/md0c
<mediaobject>
<imageobject>
<imagedata fileref="install/fdisk-edit2" format="PNG">
<imagedata fileref="install/fdisk-edit2" format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -1685,7 +1686,7 @@ Mounting root from ufs:/dev/md0c
<mediaobject>
<imageobject>
<imagedata fileref="install/boot-mgr" format="PNG">
<imagedata fileref="install/boot-mgr" format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -1715,7 +1716,7 @@ Mounting root from ufs:/dev/md0c
<mediaobject>
<imageobject>
<imagedata fileref="install/fdisk-drive2" format="PNG">
<imagedata fileref="install/fdisk-drive2" format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -1756,10 +1757,10 @@ Mounting root from ufs:/dev/md0c
<title>Partition Layout for First Disk</title>
<tgroup cols="4">
<colspec colwidth="1*">
<colspec colwidth="1*">
<colspec colwidth="1*">
<colspec colwidth="4*">
<colspec colwidth="1*"/>
<colspec colwidth="1*"/>
<colspec colwidth="1*"/>
<colspec colwidth="4*"/>
<thead>
<row>
@ -1864,10 +1865,10 @@ Mounting root from ufs:/dev/md0c
<title>Partition Layout for Subsequent Disks</title>
<tgroup cols="4">
<colspec colwidth="1*">
<colspec colwidth="1*">
<colspec colwidth="2*">
<colspec colwidth="3*">
<colspec colwidth="1*"/>
<colspec colwidth="1*"/>
<colspec colwidth="2*"/>
<colspec colwidth="3*"/>
<thead>
<row>
@ -1939,7 +1940,7 @@ Mounting root from ufs:/dev/md0c
<para>Press <keycap>Enter</keycap> to start the FreeBSD partition
editor, called <application>Disklabel</application>.</para>
<para><xref linkend="sysinstall-label"> shows the display when you first
<para><xref linkend="sysinstall-label"/> shows the display when you first
start <application>Disklabel</application>. The display is divided in
to three sections.</para>
@ -1964,7 +1965,7 @@ Mounting root from ufs:/dev/md0c
<mediaobject>
<imageobject>
<imagedata fileref="install/disklabel-ed1" format="PNG">
<imagedata fileref="install/disklabel-ed1" format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -1974,7 +1975,7 @@ Mounting root from ufs:/dev/md0c
are calculated with the help of an internal partition sizing algorithm
based on the disk size. Try this now, by
Pressing <keycap>A</keycap>. You will see a display similar to that
shown in <xref linkend="sysinstall-label2">. Depending on the size of
shown in <xref linkend="sysinstall-label2"/>. Depending on the size of
the disk you are using, the defaults may or may not be appropriate.
This does not matter, as you do not have to accept the
defaults.</para>
@ -1992,7 +1993,7 @@ Mounting root from ufs:/dev/md0c
<mediaobject>
<imageobject>
<imagedata fileref="install/disklabel-auto" format="PNG">
<imagedata fileref="install/disklabel-auto" format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -2008,7 +2009,7 @@ Mounting root from ufs:/dev/md0c
at the top of
the screen is selected and press <keycap>C</keycap>. A dialog box
will appear prompting you for the size of the new partition (as shown
in <xref linkend="sysinstall-label-add">). You can enter the size as
in <xref linkend="sysinstall-label-add"/>). You can enter the size as
the number of disk blocks you want to use, or as a
number followed by either <literal>M</literal> for megabytes,
<literal>G</literal> for gigabytes, or <literal>C</literal> for
@ -2019,7 +2020,7 @@ Mounting root from ufs:/dev/md0c
<mediaobject>
<imageobject>
<imagedata fileref="install/disklabel-root1" format="PNG">
<imagedata fileref="install/disklabel-root1" format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -2029,7 +2030,7 @@ Mounting root from ufs:/dev/md0c
in the earlier example, then delete the existing figure using
<keycap>Backspace</keycap>, and then type in
<userinput>512M</userinput>, as shown in
<xref linkend="sysinstall-label-add2">. Then press
<xref linkend="sysinstall-label-add2"/>. Then press
&gui.ok;.</para>
<figure id="sysinstall-label-add2">
@ -2037,14 +2038,14 @@ Mounting root from ufs:/dev/md0c
<mediaobject>
<imageobject>
<imagedata fileref="install/disklabel-root2" format="PNG">
<imagedata fileref="install/disklabel-root2" format="PNG"/>
</imageobject>
</mediaobject>
</figure>
<para>Having chosen the partition's size you will then be asked whether
this partition will contain a filesystem or swap space. The dialog
box is shown in <xref linkend="sysinstall-label-type">. This first
box is shown in <xref linkend="sysinstall-label-type"/>. This first
partition will contain a filesystem, so check that
<guimenuitem>FS</guimenuitem> is selected and press
<keycap>Enter</keycap>.</para>
@ -2054,7 +2055,7 @@ Mounting root from ufs:/dev/md0c
<mediaobject>
<imageobject>
<imagedata fileref="install/disklabel-fs" format="PNG">
<imagedata fileref="install/disklabel-fs" format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -2062,7 +2063,7 @@ Mounting root from ufs:/dev/md0c
<para>Finally, because you are creating a filesystem, you must tell
<application>Disklabel</application> where the filesystem is to be
mounted. The dialog box is shown in
<xref linkend="sysinstall-label-mount">. The root filesystem's mount
<xref linkend="sysinstall-label-mount"/>. The root filesystem's mount
point is <filename>/</filename>, so type <userinput>/</userinput>, and
then press <keycap>Enter</keycap>.</para>
@ -2071,7 +2072,7 @@ Mounting root from ufs:/dev/md0c
<mediaobject>
<imageobject>
<imagedata fileref="install/disklabel-root3" format="PNG">
<imagedata fileref="install/disklabel-root3" format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -2085,7 +2086,7 @@ Mounting root from ufs:/dev/md0c
use the rest of the slice.</para>
<para>Your final FreeBSD DiskLabel Editor screen will appear similar to
<xref linkend="sysinstall-label4">, although your values chosen may
<xref linkend="sysinstall-label4"/>, although your values chosen may
be different. Press <keycap>Q</keycap> to finish.</para>
<figure id="sysinstall-label4">
@ -2093,7 +2094,7 @@ Mounting root from ufs:/dev/md0c
<mediaobject>
<imageobject>
<imagedata fileref="install/disklabel-ed2" format="PNG">
<imagedata fileref="install/disklabel-ed2" format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -2123,17 +2124,17 @@ Mounting root from ufs:/dev/md0c
configuration of the X server and selection of a default
desktop must be done after the installation of &os;. More
information regarding the installation and configuration of a
X server can be found in <xref linkend="x11">.</para>
X server can be found in <xref linkend="x11"/>.</para>
<para>If compiling a custom kernel is anticipated, select an option
which includes the source code. For more information on why a
custom kernel should be built or how to build a custom kernel, see
<xref linkend="kernelconfig">.</para>
<xref linkend="kernelconfig"/>.</para>
<para>Obviously, the most versatile system is one that includes
everything. If there is adequate disk space, select
<guimenuitem>All</guimenuitem> as shown in
<xref linkend="distribution-set1"> by using the arrow keys and
<xref linkend="distribution-set1"/> by using the arrow keys and
press <keycap>Enter</keycap>. If there is a concern about disk
space consider using an option that is more suitable for the
situation.
@ -2145,7 +2146,7 @@ Mounting root from ufs:/dev/md0c
<mediaobject>
<imageobject>
<imagedata fileref="install/dist-set" format="PNG">
<imagedata fileref="install/dist-set" format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -2161,7 +2162,7 @@ Mounting root from ufs:/dev/md0c
to compile the software. Instead, it is a collection of files which
automates the downloading, compiling and installation
of third-party software packages.
<xref linkend="ports"> discusses how to use the ports
<xref linkend="ports"/> discusses how to use the ports
collection.</para>
<para>The installation program does not check to see if you have
@ -2200,7 +2201,7 @@ Mounting root from ufs:/dev/md0c
<mediaobject>
<imageobject>
<imagedata fileref="install/dist-set2" format="PNG">
<imagedata fileref="install/dist-set2" format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -2233,7 +2234,7 @@ Mounting root from ufs:/dev/md0c
<mediaobject>
<imageobject>
<imagedata fileref="install/media" format="PNG">
<imagedata fileref="install/media" format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -2430,7 +2431,7 @@ installation menus to retry whichever operations have failed.
<mediaobject>
<imageobject>
<imagedata fileref="install/ed0-conf" format="PNG">
<imagedata fileref="install/ed0-conf" format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -2465,7 +2466,7 @@ installation menus to retry whichever operations have failed.
<para>Selecting &gui.yes; will execute
<application>dhclient</application>, and if successful, will fill
in the network configuration information automatically. Refer to
<xref linkend="network-dhcp"> for more information.</para>
<xref linkend="network-dhcp"/> for more information.</para>
<para>The following Network Configuration screen shows the
configuration of the Ethernet device for a system that will act
@ -2476,7 +2477,7 @@ installation menus to retry whichever operations have failed.
<mediaobject>
<imageobject>
<imagedata fileref="install/ed0-conf2" format="PNG">
<imagedata fileref="install/ed0-conf2" format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -2611,7 +2612,7 @@ Do you want to configure inetd and the network services that it provides?
<para>These services can be enabled after installation by editing
<filename>/etc/inetd.conf</filename> with your favorite text editor.
See <xref linkend="network-inetd-overview"> for more information.</para>
See <xref linkend="network-inetd-overview"/> for more information.</para>
<para>Select &gui.yes; if you wish to
configure these services during install. An additional
@ -2651,7 +2652,7 @@ use the current settings.
<mediaobject>
<imageobject>
<imagedata fileref="install/edit-inetd-conf" format="PNG">
<imagedata fileref="install/edit-inetd-conf" format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -2678,7 +2679,7 @@ use the current settings.
program for <application>OpenSSH</application>. This will
allow secure remote access to your machine. For more
information about <application>OpenSSH</application> see <xref
linkend="openssh">.</para>
linkend="openssh"/>.</para>
</sect2>
<sect2 id="ftpanon">
@ -2708,7 +2709,7 @@ use the current settings.
<para>Anyone can access your machine if you elect to allow
anonymous FTP connections. The security implications should be
considered before enabling this option. For more information
about security see <xref linkend="security">.</para>
about security see <xref linkend="security"/>.</para>
<para>To allow anonymous FTP, use the arrow keys to select
&gui.yes; and press <keycap>Enter</keycap>.
@ -2735,7 +2736,7 @@ use the current settings.
<para>This message informs you that the FTP service will also
have to be enabled in <filename>/etc/inetd.conf</filename>
if you want to allow anonymous FTP connections, see <xref
linkend="inetd-services">. Select &gui.yes; and press
linkend="inetd-services"/>. Select &gui.yes; and press
<keycap>Enter</keycap> to continue; the following screen
will display:</para>
@ -2744,7 +2745,7 @@ use the current settings.
<mediaobject>
<imageobject>
<imagedata fileref="install/ftp-anon1" format="PNG">
<imagedata fileref="install/ftp-anon1" format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -2823,7 +2824,7 @@ use the current settings.
<mediaobject>
<imageobject>
<imagedata fileref="install/ftp-anon2" format="PNG">
<imagedata fileref="install/ftp-anon2" format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -2846,7 +2847,7 @@ use the current settings.
<para>Network File System (NFS) allows sharing of files across a
network. A machine can be configured as a server, a client, or
both. Refer to <xref linkend="network-nfs"> for a more information.</para>
both. Refer to <xref linkend="network-nfs"/> for a more information.</para>
<sect3 id="nsf-server-options">
<title>NFS Server</title>
@ -2880,7 +2881,7 @@ Press [Enter] now to invoke an editor on /etc/exports
<mediaobject>
<imageobject>
<imagedata fileref="install/nfs-server-edit" format="PNG">
<imagedata fileref="install/nfs-server-edit" format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -2930,7 +2931,7 @@ Press [Enter] now to invoke an editor on /etc/exports
<mediaobject>
<imageobject>
<imagedata fileref="install/console-saver1" format="PNG">
<imagedata fileref="install/console-saver1" format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -2944,7 +2945,7 @@ Press [Enter] now to invoke an editor on /etc/exports
<mediaobject>
<imageobject>
<imagedata fileref="install/console-saver2" format="PNG">
<imagedata fileref="install/console-saver2" format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -2964,7 +2965,7 @@ Press [Enter] now to invoke an editor on /etc/exports
<mediaobject>
<imageobject>
<imagedata fileref="install/console-saver3" format="PNG">
<imagedata fileref="install/console-saver3" format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -2978,7 +2979,7 @@ Press [Enter] now to invoke an editor on /etc/exports
<mediaobject>
<imageobject>
<imagedata fileref="install/console-saver4" format="PNG">
<imagedata fileref="install/console-saver4" format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -3022,7 +3023,7 @@ Press [Enter] now to invoke an editor on /etc/exports
<mediaobject>
<imageobject>
<imagedata fileref="install/timezone1" format="PNG">
<imagedata fileref="install/timezone1" format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -3035,7 +3036,7 @@ Press [Enter] now to invoke an editor on /etc/exports
<mediaobject>
<imageobject>
<imagedata fileref="install/timezone2" format="PNG">
<imagedata fileref="install/timezone2" format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -3048,7 +3049,7 @@ Press [Enter] now to invoke an editor on /etc/exports
<mediaobject>
<imageobject>
<imagedata fileref="install/timezone3" format="PNG">
<imagedata fileref="install/timezone3" format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -3114,7 +3115,7 @@ Press [Enter] now to invoke an editor on /etc/exports
<mediaobject>
<imageobject>
<imagedata fileref="install/mouse1" format="PNG">
<imagedata fileref="install/mouse1" format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -3127,7 +3128,7 @@ Press [Enter] now to invoke an editor on /etc/exports
<mediaobject>
<imageobject>
<imagedata fileref="install/mouse2" format="PNG">
<imagedata fileref="install/mouse2" format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -3142,7 +3143,7 @@ Press [Enter] now to invoke an editor on /etc/exports
<mediaobject>
<imageobject>
<imagedata fileref="install/mouse3" format="PNG">
<imagedata fileref="install/mouse3" format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -3155,7 +3156,7 @@ Press [Enter] now to invoke an editor on /etc/exports
<mediaobject>
<imageobject>
<imagedata fileref="install/mouse4" format="PNG">
<imagedata fileref="install/mouse4" format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -3169,7 +3170,7 @@ Press [Enter] now to invoke an editor on /etc/exports
<mediaobject>
<imageobject>
<imagedata fileref="install/mouse5" format="PNG">
<imagedata fileref="install/mouse5" format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -3185,7 +3186,7 @@ Press [Enter] now to invoke an editor on /etc/exports
<mediaobject>
<imageobject>
<imagedata fileref="install/mouse6" format="PNG">
<imagedata fileref="install/mouse6" format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -3230,7 +3231,7 @@ Press [Enter] now to invoke an editor on /etc/exports
<mediaobject>
<imageobject>
<imagedata fileref="install/pkg-cat" format="PNG">
<imagedata fileref="install/pkg-cat" format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -3251,7 +3252,7 @@ Press [Enter] now to invoke an editor on /etc/exports
<mediaobject>
<imageobject>
<imagedata fileref="install/pkg-sel" format="PNG">
<imagedata fileref="install/pkg-sel" format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -3278,7 +3279,7 @@ Press [Enter] now to invoke an editor on /etc/exports
<mediaobject>
<imageobject>
<imagedata fileref="install/pkg-install" format="PNG">
<imagedata fileref="install/pkg-install" format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -3292,7 +3293,7 @@ Press [Enter] now to invoke an editor on /etc/exports
<mediaobject>
<imageobject>
<imagedata fileref="install/pkg-confirm" format="PNG">
<imagedata fileref="install/pkg-confirm" format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -3332,7 +3333,7 @@ Press [Enter] now to invoke an editor on /etc/exports
<mediaobject>
<imageobject>
<imagedata fileref="install/adduser1" format="PNG">
<imagedata fileref="install/adduser1" format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -3345,7 +3346,7 @@ Press [Enter] now to invoke an editor on /etc/exports
<mediaobject>
<imageobject>
<imagedata fileref="install/adduser2" format="PNG">
<imagedata fileref="install/adduser2" format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -3445,7 +3446,7 @@ Press [Enter] now to invoke an editor on /etc/exports
<mediaobject>
<imageobject>
<imagedata fileref="install/adduser3" format="PNG">
<imagedata fileref="install/adduser3" format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -3510,7 +3511,7 @@ Retype new password :</screen>
<mediaobject>
<imageobject>
<imagedata fileref="install/mainexit" format="PNG">
<imagedata fileref="install/mainexit" format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -3539,7 +3540,7 @@ Retype new password :</screen>
be removed from drive (quickly). Press &gui.ok; to reboot.</para>
<para>The system will reboot so watch for any error messages that
may appear, see <xref linkend="freebsdboot"> for more
may appear, see <xref linkend="freebsdboot"/> for more
details.</para>
</sect2>
@ -3585,13 +3586,13 @@ Retype new password :</screen>
<mediaobject>
<imageobject>
<imagedata fileref="install/net-config-menu1" format="PNG">
<imagedata fileref="install/net-config-menu1" format="PNG"/>
</imageobject>
</mediaobject>
</figure>
<para>The first option, <guimenuitem>Interfaces</guimenuitem>, was
previously covered during the <xref linkend="inst-network-dev">,
previously covered during the <xref linkend="inst-network-dev"/>,
thus this option can safely be ignored.</para>
<para>Selecting the <guimenuitem>AMD</guimenuitem> option adds
@ -3652,7 +3653,7 @@ Retype new password :</screen>
<mediaobject>
<imageobject>
<imagedata fileref="install/mta-main" format="PNG">
<imagedata fileref="install/mta-main" format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -3687,7 +3688,7 @@ Retype new password :</screen>
network via the <acronym>NFS</acronym> protocol. If this is
a stand-alone machine, this option can remain unselected.
The system may require more configuration later; see
<xref linkend="network-nfs"> for more
<xref linkend="network-nfs"/> for more
information about client and server configuration.</para>
<para>Below that option is the <guimenuitem>NFS server</guimenuitem>
@ -3706,7 +3707,7 @@ Retype new password :</screen>
<mediaobject>
<imageobject>
<imagedata fileref="install/ntp-config" format="PNG">
<imagedata fileref="install/ntp-config" format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -3732,7 +3733,7 @@ Retype new password :</screen>
<mediaobject>
<imageobject>
<imagedata fileref="install/net-config-menu2" format="PNG">
<imagedata fileref="install/net-config-menu2" format="PNG"/>
</imageobject>
</mediaobject>
</figure>
@ -4134,7 +4135,7 @@ Please press any key to reboot.</screen>
file
<filename>/boot/loader.conf</filename>. More
information about the boot loader can be found
in <xref linkend="boot-synopsis">.</para>
in <xref linkend="boot-synopsis"/>.</para>
</answer>
</qandaentry>
<qandaentry>
@ -4278,11 +4279,11 @@ Please press any key to reboot.</screen>
<qandaentry>
<question>
<indexterm>
<primary>color</primary>
<secondary>contrast</secondary>
</indexterm>
<question>
<para>When <application>sysinstall</application> is used
in an X11 terminal, the yellow font is difficult to read
against the light gray background. Is there a way to
@ -4344,10 +4345,9 @@ Please press any key to reboot.</screen>
machine to act as the main display and keyboard for a
system. To do this, just follow the steps to create
an installation USB memstick, explained in <xref
linkend="install-boot-media"> or download the correct
linkend="install-boot-media"/> or download the correct
installation ISO image, see <xref
linkend="install-cdrom">.</para>
linkend="install-cdrom"/>.</para>
<para>To modify these media to boot into a serial console, follow
these steps (If you want to use a CDROM you can skip the first
@ -4400,7 +4400,7 @@ Please press any key to reboot.</screen>
</indexterm>
<para>If you were to boot into the CD that you just
made from the installation ISO image (see <xref
linkend="install-cdrom">), &os; would boot into its
linkend="install-cdrom"/>), &os; would boot into its
normal install mode. We want &os; to boot into a serial
console for our install. To do this, you have to
extract, modify and regenerate the ISO image before
@ -4657,7 +4657,7 @@ Please press any key to reboot.</screen>
access is cheap for you. It will let you install &os;, and
you can then install third-party
packages by downloading them using the ports/packages system (see
<xref linkend="ports">) as
<xref linkend="ports"/>) as
necessary.</para>
<para>Use the image of <literal>dvd1</literal> if you want to
@ -4674,9 +4674,9 @@ Please press any key to reboot.</screen>
<para>You must then write the CD images to disc. If you will be
doing this on another FreeBSD system then see
<xref linkend="creating-cds"> for more information (in
particular, <xref linkend="burncd"> and
<xref linkend="cdrecord">).</para>
<xref linkend="creating-cds"/> for more information (in
particular, <xref linkend="burncd"/> and
<xref linkend="cdrecord"/>).</para>
<para>If you will be doing this on another platform then you will
need to use whatever utilities exist to control your CD writer on

185
en_US.ISO8859-1/books/handbook/introduction/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!--
The FreeBSD Documentation Project
@ -72,16 +73,18 @@
are:</para>
<itemizedlist>
<indexterm><primary>preemptive multitasking</primary></indexterm>
<listitem>
<indexterm><primary>preemptive multitasking</primary></indexterm>
<para><emphasis>Preemptive multitasking</emphasis> with
dynamic priority adjustment to ensure smooth and fair
sharing of the computer between applications and users, even
under the heaviest of loads.</para>
</listitem>
<indexterm><primary>multi-user facilities</primary></indexterm>
<listitem>
<indexterm><primary>multi-user facilities</primary></indexterm>
<para><emphasis>Multi-user facilities</emphasis> which allow many
people to use a &os; system simultaneously for a variety
of things. This means, for example, that system peripherals
@ -90,9 +93,9 @@
resource limits can be placed on users or groups of users,
protecting critical system resources from over-use.</para>
</listitem>
<indexterm><primary>TCP/IP networking</primary></indexterm>
<listitem>
<indexterm><primary>TCP/IP networking</primary></indexterm>
<para>Strong <emphasis>TCP/IP networking</emphasis> with
support for industry standards such as SCTP, DHCP, NFS,
NIS, PPP, SLIP, IPsec, and IPv6. This means that your &os;
@ -103,8 +106,9 @@
firewall (security) services.</para>
</listitem>
<indexterm><primary>memory protection</primary></indexterm>
<listitem>
<indexterm><primary>memory protection</primary></indexterm>
<para><emphasis>Memory protection</emphasis> ensures that
applications (or users) cannot interfere with each other. One
application crashing will not affect others in any way.</para>
@ -117,17 +121,18 @@
up.</para>
</listitem>
<indexterm>
<primary>X Window System</primary>
</indexterm>
<listitem>
<indexterm>
<primary>X Window System</primary>
</indexterm>
<para>The industry standard <emphasis>X Window System</emphasis>
(X11R7) provides a graphical user interface (GUI) for the cost
of a common VGA card and monitor and comes with full
sources.</para>
</listitem>
<listitem>
<indexterm>
<primary>binary compatibility</primary>
<secondary>Linux</secondary>
@ -148,7 +153,7 @@
<primary>binary compatibility</primary>
<secondary>NetBSD</secondary>
</indexterm>
<listitem>
<para><emphasis>Binary compatibility</emphasis> with many
programs built for Linux, SCO, SVR4, BSDI and NetBSD.</para>
</listitem>
@ -168,32 +173,34 @@
popular commercial &unix; systems and thus most applications
require few, if any, changes to compile.</para>
</listitem>
<indexterm><primary>virtual memory</primary></indexterm>
<listitem>
<indexterm><primary>virtual memory</primary></indexterm>
<para>Demand paged <emphasis>virtual memory</emphasis> and
<quote>merged VM/buffer cache</quote> design efficiently
satisfies applications with large appetites for memory while
still maintaining interactive response to other users.</para>
</listitem>
<indexterm>
<primary>Symmetric Multi-Processing (SMP)</primary>
</indexterm>
<listitem>
<indexterm>
<primary>Symmetric Multi-Processing (SMP)</primary>
</indexterm>
<para><emphasis>SMP</emphasis> support for machines with
multiple CPUs.</para>
</listitem>
<indexterm>
<primary>compilers</primary>
<secondary>C</secondary>
</indexterm>
<indexterm>
<primary>compilers</primary>
<secondary>C++</secondary>
</indexterm>
<listitem>
<indexterm>
<primary>compilers</primary>
<secondary>C</secondary>
</indexterm>
<indexterm>
<primary>compilers</primary>
<secondary>C++</secondary>
</indexterm>
<para>A full complement of <emphasis>C</emphasis>
and <emphasis>C++</emphasis>
development tools.
@ -202,8 +209,9 @@
collection.</para>
</listitem>
<indexterm><primary>source code</primary></indexterm>
<listitem>
<indexterm><primary>source code</primary></indexterm>
<para><emphasis>Source code</emphasis> for the entire system
means you have the greatest degree of control over your
environment. Why be locked into a proprietary solution
@ -262,13 +270,15 @@
variety of Internet services such as:</para>
<itemizedlist>
<indexterm><primary>FTP servers</primary></indexterm>
<listitem>
<indexterm><primary>FTP servers</primary></indexterm>
<para>FTP servers</para>
</listitem>
<indexterm><primary>web servers</primary></indexterm>
<listitem>
<indexterm><primary>web servers</primary></indexterm>
<para>World Wide Web servers (standard or secure
[SSL])</para>
</listitem>
@ -277,13 +287,16 @@
<para>IPv4 and IPv6 routing</para>
</listitem>
<indexterm><primary>firewall</primary></indexterm>
<indexterm><primary>NAT</primary></indexterm>
<listitem>
<indexterm><primary>firewall</primary></indexterm>
<indexterm><primary>NAT</primary></indexterm>
<para>Firewalls and NAT (<quote>IP masquerading</quote>)
gateways</para>
</listitem>
<listitem>
<indexterm>
<primary>electronic mail</primary>
<see>email</see>
@ -291,12 +304,13 @@
<indexterm>
<primary>email</primary>
</indexterm>
<listitem>
<para>Electronic Mail servers</para>
</listitem>
<indexterm><primary>USENET</primary></indexterm>
<listitem>
<indexterm><primary>USENET</primary></indexterm>
<para>USENET News or Bulletin Board Systems</para>
</listitem>
@ -334,9 +348,11 @@
in open forums.</para>
</listitem>
<indexterm><primary>router</primary></indexterm>
<indexterm><primary>DNS Server</primary></indexterm>
<listitem>
<indexterm><primary>router</primary></indexterm>
<indexterm><primary>DNS Server</primary></indexterm>
<para><emphasis>Networking:</emphasis> Need a new router? A
name server (DNS)? A firewall to keep people out of your
internal network? &os; can easily turn that unused 386 or
@ -344,6 +360,7 @@
sophisticated packet-filtering capabilities.</para>
</listitem>
<listitem>
<indexterm>
<primary>X Window System</primary>
</indexterm>
@ -351,7 +368,7 @@
<primary>X Window System</primary>
<secondary>Accelerated-X</secondary>
</indexterm>
<listitem>
<para><emphasis>X Window workstation:</emphasis> &os; is a
fine choice for an inexpensive X terminal solution,
using the freely available X11 server.
@ -362,8 +379,9 @@
administer.</para>
</listitem>
<indexterm><primary>GNU Compiler Collection</primary></indexterm>
<listitem>
<indexterm><primary>GNU Compiler Collection</primary></indexterm>
<para><emphasis>Software Development:</emphasis> The basic
&os; system comes with a full complement of development
tools including the renowned GNU C/C++ compiler and
@ -372,7 +390,7 @@
</itemizedlist>
<para>&os; is available in both source and binary form on CD-ROM,
DVD, and via anonymous FTP. Please see <xref linkend="mirrors">
DVD, and via anonymous FTP. Please see <xref linkend="mirrors"/>
for more information about obtaining &os;.</para>
</sect2>
@ -388,23 +406,22 @@
many of the world's largest IT companies, including:</para>
<itemizedlist>
<indexterm><primary>Apple</primary></indexterm>
<listitem>
<indexterm><primary>Apple</primary></indexterm>
<para><ulink url="http://www.apple.com/">Apple</ulink></para>
</listitem>
<indexterm><primary>Cisco</primary></indexterm>
<listitem>
<indexterm><primary>Cisco</primary></indexterm>
<para><ulink url="http://www.cisco.com/">Cisco</ulink></para>
</listitem>
<indexterm><primary>Juniper</primary></indexterm>
<listitem>
<para><ulink url="http://www.juniper.net/">Juniper</ulink></para>
</listitem>
<indexterm><primary>NetApp</primary></indexterm>
<listitem>
<indexterm><primary>NetApp</primary></indexterm>
<para><ulink url="http://www.netapp.com/">NetApp</ulink></para>
</listitem>
</itemizedlist>
@ -413,68 +430,74 @@
Internet, including:</para>
<itemizedlist>
<indexterm><primary>Yahoo!</primary></indexterm>
<listitem>
<indexterm><primary>Yahoo!</primary></indexterm>
<para><ulink url="http://www.yahoo.com/">Yahoo!</ulink></para>
</listitem>
<indexterm><primary>Yandex</primary></indexterm>
<listitem>
<indexterm><primary>Yandex</primary></indexterm>
<para><ulink url="http://www.yandex.ru/">Yandex</ulink></para>
</listitem>
<indexterm><primary>Apache</primary></indexterm>
<listitem>
<indexterm><primary>Apache</primary></indexterm>
<para><ulink url="http://www.apache.org/">Apache</ulink></para>
</listitem>
<indexterm><primary>Rambler</primary></indexterm>
<listitem>
<indexterm><primary>Rambler</primary></indexterm>
<para><ulink url="http://www.rambler.ru/">Rambler</ulink></para>
</listitem>
<indexterm><primary>Sina</primary></indexterm>
<listitem>
<indexterm><primary>Sina</primary></indexterm>
<para><ulink url="http://www.sina.com/">Sina</ulink></para>
</listitem>
<indexterm><primary>Pair Networks</primary></indexterm>
<listitem>
<indexterm><primary>Pair Networks</primary></indexterm>
<para><ulink url="http://www.pair.com/">Pair Networks</ulink></para>
</listitem>
<indexterm><primary>Sony Japan</primary></indexterm>
<listitem>
<indexterm><primary>Sony Japan</primary></indexterm>
<para><ulink url="http://www.sony.co.jp/">Sony Japan</ulink></para>
</listitem>
<indexterm><primary>Netcraft</primary></indexterm>
<listitem>
<indexterm><primary>Netcraft</primary></indexterm>
<para><ulink url="http://www.netcraft.com/">Netcraft</ulink></para>
</listitem>
<indexterm><primary>NetEase</primary></indexterm>
<listitem>
<indexterm><primary>NetEase</primary></indexterm>
<para><ulink url="http://www.163.com/">NetEase</ulink></para>
</listitem>
<indexterm><primary>Weathernews</primary></indexterm>
<listitem>
<indexterm><primary>Weathernews</primary></indexterm>
<para><ulink url="http://www.wni.com/">Weathernews</ulink></para>
</listitem>
<indexterm><primary>TELEHOUSE America</primary></indexterm>
<listitem>
<indexterm><primary>TELEHOUSE America</primary></indexterm>
<para><ulink url="http://www.telehouse.com/">TELEHOUSE
America</ulink></para>
</listitem>
<indexterm><primary>Experts Exchange</primary></indexterm>
<listitem>
<indexterm><primary>Experts Exchange</primary></indexterm>
<para><ulink url="http://www.experts-exchange.com/">Experts
Exchange</ulink></para>
</listitem>
</itemizedlist>
<para>and many more.</para>
@ -756,25 +779,28 @@
<variablelist>
<varlistentry>
<term>The SVN and CVS repositories<anchor
id="development-cvs-repository"></term>
<indexterm>
<primary>CVS</primary>
<secondary>repository</secondary>
</indexterm>
<indexterm>
<primary>Concurrent Versions System</primary>
<see>CVS</see>
</indexterm>
<indexterm>
<primary>SVN</primary>
<secondary>repository</secondary>
</indexterm>
<indexterm>
<primary>Subversion</primary>
<see>SVN</see>
</indexterm>
id="development-cvs-repository"/></term>
<listitem>
<indexterm>
<primary>CVS</primary>
<secondary>repository</secondary>
</indexterm>
<indexterm>
<primary>Concurrent Versions System</primary>
<see>CVS</see>
</indexterm>
<indexterm>
<primary>SVN</primary>
<secondary>repository</secondary>
</indexterm>
<indexterm>
<primary>Subversion</primary>
<see>SVN</see>
</indexterm>
<para>For several years, the central source tree for &os;
was maintained by
<ulink url="http://www.nongnu.org/cvs/">CVS</ulink>
@ -818,10 +844,11 @@
<varlistentry>
<term>The committers list<anchor
id="development-committers"></term>
id="development-committers"/></term>
<indexterm><primary>committers</primary></indexterm>
<listitem>
<indexterm><primary>committers</primary></indexterm>
<para>The <firstterm>committers</firstterm>
are the people who have <emphasis>write</emphasis> access to
the CVS tree, and are authorized to make modifications
@ -837,10 +864,11 @@
</varlistentry>
<varlistentry>
<term>The FreeBSD core team<anchor id="development-core"></term>
<term>The FreeBSD core team<anchor id="development-core"/></term>
<indexterm><primary>core team</primary></indexterm>
<listitem>
<indexterm><primary>core team</primary></indexterm>
<para>The <firstterm>&os; core team</firstterm>
would be equivalent to the board of directors if the
&os;&nbsp;Project were a company. The primary task of the core
@ -878,14 +906,15 @@
<varlistentry>
<term>Outside contributors</term>
<indexterm><primary>contributors</primary></indexterm>
<listitem>
<indexterm><primary>contributors</primary></indexterm>
<para>Last, but definitely not least, the largest group of
developers are the users themselves who provide feedback and
bug fixes to us on an almost constant basis. The primary
way of keeping in touch with &os;'s more non-centralized
development is to subscribe to the &a.hackers; where such
things are discussed. See <xref linkend="eresources"> for
things are discussed. See <xref linkend="eresources"/> for
more information about the various &os; mailing lists.</para>
<para><citetitle><ulink
@ -975,7 +1004,7 @@
<quote>package</quote>, which can be installed with a simple
command (<command>pkg_add</command>) by those who do not wish
to compile their own ports from source. More information on
packages and ports can be found in <xref linkend="ports">.</para>
packages and ports can be found in <xref linkend="ports"/>.</para>
<para>All recent &os; versions provide an option in the installer
(either &man.sysinstall.8; or &man.bsdinstall.8;) to install
@ -983,7 +1012,7 @@
class="directory">/usr/local/share/doc/freebsd</filename> during
the initial system setup. Documentation may also be installed at
any later time using packages as described in <xref
linkend="doc-ports-install-package">.
linkend="doc-ports-install-package"/>.
You may view the locally installed
manuals with any HTML capable browser using the following
URLs:</para>

18
en_US.ISO8859-1/books/handbook/jails/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!--
The FreeBSD Documentation Project
@ -179,7 +180,7 @@
kernel and a few other things. A more complete set of
fine-grained controls available for tuning the access of a
jailed environment is described in <xref
linkend="jails-tuning">.</para>
linkend="jails-tuning"/>.</para>
<para>A jail is characterized by four elements:</para>
@ -224,7 +225,7 @@
the associated &man.jail.8; environment. More information
about capabilities and restrictions of the
<username>root</username> user will be discussed in <xref
linkend="jails-tuning"> below.</para>
linkend="jails-tuning"/> below.</para>
</sect2>
</sect1>
@ -240,12 +241,12 @@
the procedure for building a jail:</para>
<screen>&prompt.root; <userinput>setenv D <replaceable>/here/is/the/jail</replaceable></userinput>
&prompt.root; <userinput>mkdir -p $D</userinput> <co id="jailpath">
&prompt.root; <userinput>mkdir -p $D</userinput> <co id="jailpath"/>
&prompt.root; <userinput>cd /usr/src</userinput>
&prompt.root; <userinput>make buildworld</userinput> <co id="jailbuildworld">
&prompt.root; <userinput>make installworld DESTDIR=$D</userinput> <co id="jailinstallworld">
&prompt.root; <userinput>make distribution DESTDIR=$D</userinput> <co id="jaildistrib">
&prompt.root; <userinput>mount -t devfs devfs $D/dev</userinput> <co id="jaildevfs"></screen>
&prompt.root; <userinput>make buildworld</userinput> <co id="jailbuildworld"/>
&prompt.root; <userinput>make installworld DESTDIR=$D</userinput> <co id="jailinstallworld"/>
&prompt.root; <userinput>make distribution DESTDIR=$D</userinput> <co id="jaildistrib"/>
&prompt.root; <userinput>mount -t devfs devfs $D/dev</userinput> <co id="jaildevfs"/></screen>
<calloutlist>
<callout arearefs="jailpath">
@ -300,7 +301,7 @@
<para>Once a jail is installed, it can be started by using the
&man.jail.8; utility. The &man.jail.8; utility takes four
mandatory arguments which are described in the <xref
linkend="jails-what">. Other arguments may be
linkend="jails-what"/>. Other arguments may be
specified too, e.g., to run the jailed process with the credentials of a specific
user. The <option><replaceable>command</replaceable></option> argument depends on
the type of the jail; for a <emphasis>virtual system</emphasis>,
@ -391,6 +392,7 @@ jail_<replaceable>www</replaceable>_devfs_ruleset="<replaceable>www_ruleset</rep
<para>Some of the high-level applications for jail management,
which are available through the &os; Ports Collection, and can
be used to implement overall jail-based solutions.</para>
</listitem>
</itemizedlist>
<sect2 id="jails-tuning-utilities">

13
en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!--
The FreeBSD Documentation Project
@ -301,7 +302,7 @@ following line in &man.loader.conf.5;:
exist on your system (or if it is empty), then the sources have
not been installed. The easiest way to install the full source
is to use &man.csup.1; as described in <xref
linkend="synching">. You should also create a symlink to
linkend="synching"/>. You should also create a symlink to
<filename class="directory">/usr/src/sys/</filename>:</para>
<screen>&prompt.root; <userinput>ln -s /usr/src/sys /sys</userinput></screen>
@ -483,7 +484,7 @@ following line in &man.loader.conf.5;:
ignored. The following sections describe each keyword, in
the order they are listed in <filename>GENERIC</filename>.
<anchor
id="kernelconfig-options"> For an exhaustive list of architecture
id="kernelconfig-options"/> For an exhaustive list of architecture
dependent options and devices, see the <filename>NOTES</filename>
file in the same directory as the <filename>GENERIC</filename> file. For
architecture independent options, see
@ -647,7 +648,7 @@ cpu I686_CPU</programlisting>
<para>This option enables kernel support
for access control lists. This relies on the use of extended
attributes and <acronym>UFS2</acronym>, and the feature is described
in detail in <xref linkend="fs-acl">. <acronym>ACL</acronym>s are
in detail in <xref linkend="fs-acl"/>. <acronym>ACL</acronym>s are
enabled by default and should not be
disabled in the kernel if they have been used previously on a file
system, as this will remove the access control lists, changing the
@ -880,7 +881,7 @@ device ata</programlisting>
<para>This is needed along with <literal>device ata</literal> for ATA
RAID drives.</para>
<programlisting><anchor id="kernelconfig-atapi">
<programlisting><anchor id="kernelconfig-atapi"/>
device atapicd # ATAPI CDROM drives</programlisting>
<para>This is needed along with <literal>device ata</literal> for
@ -1271,7 +1272,7 @@ device loop # Network loopback</programlisting>
the <link linkend="userppp">PPP</link> section of this book for more
information.</para>
<programlisting><anchor id="kernelconfig-ptys">
<programlisting><anchor id="kernelconfig-ptys"/>
device pty # Pseudo-ttys (telnet etc)</programlisting>
<para>This is a <quote>pseudo-terminal</quote> or simulated login port.
@ -1480,7 +1481,7 @@ device fwe # Ethernet over FireWire (non-standard!)</programl
<varlistentry>
<term>The kernel does not boot:<anchor
id="kernelconfig-noboot"></term>
id="kernelconfig-noboot"/></term>
<listitem>
<para>If your new kernel does not boot, or fails to

12
en_US.ISO8859-1/books/handbook/l10n/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!--
The FreeBSD Documentation Project
@ -54,7 +55,7 @@
<itemizedlist>
<listitem><para>Know how to install additional third-party
applications (<xref linkend="ports">).</para></listitem>
applications (<xref linkend="ports"/>).</para></listitem>
</itemizedlist>
</sect1>
@ -233,8 +234,9 @@
functions</para>
</listitem>
<indexterm><primary>MIME</primary></indexterm>
<listitem>
<indexterm><primary>MIME</primary></indexterm>
<para><envar>MM_CHARSET</envar> for applications' MIME character
set</para>
</listitem>
@ -332,7 +334,7 @@ me:\
<para>to make new configuration in
<filename>/etc/login.conf</filename> visible to the system.</para>
<bridgehead renderas=sect4>Changing Login Classes with &man.vipw.8;</bridgehead>
<bridgehead renderas="sect4">Changing Login Classes with &man.vipw.8;</bridgehead>
<indexterm>
<primary><command>vipw</command></primary>
@ -342,7 +344,7 @@ me:\
<programlisting>user:password:1111:11:<replaceable>language</replaceable>:0:0:User Name:/home/user:/bin/sh</programlisting>
<bridgehead renderas=sect4>Changing Login Classes with &man.adduser.8;</bridgehead>
<bridgehead renderas="sect4">Changing Login Classes with &man.adduser.8;</bridgehead>
<indexterm>
<primary><command>adduser</command></primary>
@ -376,7 +378,7 @@ me:\
</listitem>
</itemizedlist>
<bridgehead renderas=sect4>Changing Login Classes with &man.pw.8;</bridgehead>
<bridgehead renderas="sect4">Changing Login Classes with &man.pw.8;</bridgehead>
<indexterm>
<primary><command>pw</command></primary>
</indexterm>

17
en_US.ISO8859-1/books/handbook/linuxemu/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!--
The FreeBSD Documentation Project
@ -94,7 +95,7 @@
<itemizedlist>
<listitem>
<para>Know how to install additional third-party
software (<xref linkend="ports">).</para>
software (<xref linkend="ports"/>).</para>
</listitem>
</itemizedlist>
@ -135,7 +136,7 @@ Id Refs Address Size Name
then you may statically link Linux binary compatibility into the kernel
by adding <literal>options COMPAT_LINUX</literal> to your kernel
configuration file. Then install your new kernel as described in
<xref linkend="kernelconfig">.</para>
<xref linkend="kernelconfig"/>.</para>
<sect2>
<title>Installing Linux Runtime Libraries</title>
@ -636,14 +637,14 @@ LOG=/var/log/lmgrd.log
case "$1" in
start)
lmgrd -c ${LICENSE_FILE} 2&gt;&gt; ${LOG} 1&gt;&2
lmgrd -c ${LICENSE_FILE} 2&gt;&gt; ${LOG} 1&gt;&amp;2
echo -n " lmgrd"
;;
stop)
lmgrd -c ${LICENSE_FILE} -x lmdown 2&gt;&gt; ${LOG} 1&gt;&2
lmgrd -c ${LICENSE_FILE} -x lmdown 2&gt;&gt; ${LOG} 1&gt;&amp;2
;;
*)
echo "Usage: `basename $0` {start|stop}" 1&gt;&2
echo "Usage: `basename $0` {start|stop}" 1&gt;&amp;2
exit 64
;;
esac
@ -718,7 +719,7 @@ FEATURE Maple maplelmg 2000.0831 permanent 1 XXXXXXXXXXXX \
version of <application>&matlab; version 6.5</application> onto
a &os; system. It works quite well, with the exception of the
<application>&java.virtual.machine;</application> (see
<xref linkend="matlab-jre">).</para>
<xref linkend="matlab-jre"/>).</para>
<para>The Linux version of <application>&matlab;</application> can be
ordered directly from The MathWorks at <ulink
@ -1043,8 +1044,8 @@ options SYSVMSG #SysV interprocess communication</programlisting>
<informaltable frame="none" pgwide="1">
<tgroup cols="2">
<colspec colwidth="1*">
<colspec colwidth="2*">
<colspec colwidth="1*"/>
<colspec colwidth="2*"/>
<thead>
<row>
<entry>Variable</entry>

9
en_US.ISO8859-1/books/handbook/mac/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!--
The FreeBSD Documentation Project
$FreeBSD$
@ -87,18 +88,18 @@
<itemizedlist>
<listitem>
<para>Understand &unix; and &os; basics
(<xref linkend="basics">).</para>
(<xref linkend="basics"/>).</para>
</listitem>
<listitem>
<para>Be familiar with
the basics of kernel configuration/compilation
(<xref linkend="kernelconfig">).</para>
(<xref linkend="kernelconfig"/>).</para>
</listitem>
<listitem>
<para>Have some familiarity with security and how it
pertains to &os; (<xref linkend="security">).</para>
pertains to &os; (<xref linkend="security"/>).</para>
</listitem>
</itemizedlist>
@ -757,7 +758,7 @@ test: biba/high</screen>
<para>Some users have experienced problems with setting the
<option>multilabel</option> flag on the root partition.
If this is the case, please review the
<xref linkend="mac-troubleshoot"> of this chapter.</para>
<xref linkend="mac-troubleshoot"/> of this chapter.</para>
</note>
</sect2>
</sect1>

48
en_US.ISO8859-1/books/handbook/mail/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!--
The FreeBSD Documentation Project
@ -36,7 +37,7 @@
it is not a complete reference and in fact many important
considerations are omitted. For more complete coverage of the
subject, the reader is referred to the many excellent books listed
in <xref linkend="bibliography">.</para>
in <xref linkend="bibliography"/>.</para>
<para>After reading this chapter, you will know:</para>
@ -108,17 +109,17 @@
<itemizedlist>
<listitem>
<para>Properly set up your network connection
(<xref linkend="advanced-networking">).</para>
(<xref linkend="advanced-networking"/>).</para>
</listitem>
<listitem>
<para>Properly set up the DNS information for your mail host
(<xref linkend="network-servers">).</para>
(<xref linkend="network-servers"/>).</para>
</listitem>
<listitem>
<para>Know how to install additional third-party software
(<xref linkend="ports">).</para></listitem>
(<xref linkend="ports"/>).</para></listitem>
</itemizedlist>
</sect1>
@ -350,8 +351,8 @@ FreeBSD.org mail is handled (pri=10) by mx1.FreeBSD.org</screen>
that if you wish to secure the transmission of information
across these protocols, you should consider tunneling
sessions over &man.ssh.1; or using SSL. Tunneling sessions is
described in <xref linkend="security-ssh-tunneling"> and SSL is
described in <xref linkend="openssl">.</para>
described in <xref linkend="security-ssh-tunneling"/> and SSL is
described in <xref linkend="openssl"/>.</para>
</warning>
</sect3>
@ -880,12 +881,11 @@ purgestat /usr/local/supermailer/bin/purgestat-compat</programlisting>
</answer>
</qandaentry>
<indexterm>
<primary>MX record</primary>
</indexterm>
<qandaentry>
<question>
<indexterm>
<primary>MX record</primary>
</indexterm>
<para><application>sendmail</application> says <errorname>mail
loops back to myself</errorname></para>
</question>
@ -916,9 +916,9 @@ to /etc/mail/sendmail.cf.</programlisting>
</answer>
</qandaentry>
<indexterm><primary>PPP</primary></indexterm>
<qandaentry>
<question>
<indexterm><primary>PPP</primary></indexterm>
<para>How can I run a mail server on a dial-up PPP host?</para>
</question>
@ -1439,7 +1439,7 @@ hostname=_HOSTNAME_</programlisting>
<para>Make sure you disable <application>sendmail</application>,
including the outgoing mail service. See
<xref linkend="mail-disable-sendmail"> for details.</para>
<xref linkend="mail-disable-sendmail"/> for details.</para>
<para><filename role="package">mail/ssmtp</filename> has some
other options available. See the example configuration file in
@ -1623,11 +1623,11 @@ SENDMAIL_LDADD=-lsasl2</programlisting>
<para>Recompile <application>sendmail</application> by executing the following commands:</para>
<screen>&prompt.root; <userinput>cd /usr/src/lib/libsmutil</userinput>
&prompt.root; <userinput>make cleandir && make obj && make</userinput>
&prompt.root; <userinput>make cleandir &amp;&amp; make obj &amp;&amp; make</userinput>
&prompt.root; <userinput>cd /usr/src/lib/libsm</userinput>
&prompt.root; <userinput>make cleandir && make obj && make</userinput>
&prompt.root; <userinput>make cleandir &amp;&amp; make obj &amp;&amp; make</userinput>
&prompt.root; <userinput>cd /usr/src/usr.sbin/sendmail</userinput>
&prompt.root; <userinput>make cleandir && make obj && make && make install</userinput></screen>
&prompt.root; <userinput>make cleandir &amp;&amp; make obj &amp;&amp; make &amp;&amp; make install</userinput></screen>
<para>The compile of <application>sendmail</application> should not have any problems
if <filename>/usr/src</filename> has not been changed extensively
@ -1725,7 +1725,7 @@ define(`confAUTH_MECHANISMS', `GSSAPI DIGEST-MD5 CRAM-MD5 LOGIN')dnl</programlis
downloaded to a local <filename>mbox</filename> file using an
application such as <application>fetchmail</application>, which
will be discussed later in this chapter (<xref
linkend="mail-fetchmail">).</para>
linkend="mail-fetchmail"/>).</para>
<para>In order to send and receive email, run
<command>mail</command>:</para>
@ -1879,7 +1879,7 @@ EOT</screen>
<mediaobject>
<imageobject>
<imagedata fileref="mail/mutt1" format="PNG">
<imagedata fileref="mail/mutt1" format="PNG"/>
</imageobject>
</mediaobject>
@ -1890,7 +1890,7 @@ EOT</screen>
<mediaobject>
<imageobject>
<imagedata fileref="mail/mutt2" format="PNG">
<imagedata fileref="mail/mutt2" format="PNG"/>
</imageobject>
</mediaobject>
@ -1926,7 +1926,7 @@ EOT</screen>
<mediaobject>
<imageobject>
<imagedata fileref="mail/mutt3" format="PNG">
<imagedata fileref="mail/mutt3" format="PNG"/>
</imageobject>
</mediaobject>
@ -1975,7 +1975,7 @@ EOT</screen>
<mediaobject>
<imageobject>
<imagedata fileref="mail/pine1" format="PNG">
<imagedata fileref="mail/pine1" format="PNG"/>
</imageobject>
</mediaobject>
@ -1993,7 +1993,7 @@ EOT</screen>
<mediaobject>
<imageobject>
<imagedata fileref="mail/pine2" format="PNG">
<imagedata fileref="mail/pine2" format="PNG"/>
</imageobject>
</mediaobject>
@ -2004,7 +2004,7 @@ EOT</screen>
<mediaobject>
<imageobject>
<imagedata fileref="mail/pine3" format="PNG">
<imagedata fileref="mail/pine3" format="PNG"/>
</imageobject>
</mediaobject>
@ -2017,7 +2017,7 @@ EOT</screen>
<mediaobject>
<imageobject>
<imagedata fileref="mail/pine4" format="PNG">
<imagedata fileref="mail/pine4" format="PNG"/>
</imageobject>
</mediaobject>
@ -2034,7 +2034,7 @@ EOT</screen>
<mediaobject>
<imageobject>
<imagedata fileref="mail/pine5" format="PNG">
<imagedata fileref="mail/pine5" format="PNG"/>
</imageobject>
</mediaobject>

21
en_US.ISO8859-1/books/handbook/mirrors/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!--
The FreeBSD Documentation Project
@ -266,14 +267,14 @@
<para>After downloading the ISO image with BitTorrent, you may
burn it to CD or DVD media as described in <xref
linkend="burncd">, burncd.</para>
linkend="burncd"/>, burncd.</para>
</sect1>
<sect1 id="anoncvs">
<title>Anonymous CVS</title>
<sect2>
<title><anchor id="anoncvs-intro">Introduction</title>
<title><anchor id="anoncvs-intro"/>Introduction</title>
<indexterm>
<primary>CVS</primary>
@ -330,7 +331,7 @@
</sect2>
<sect2>
<title><anchor id="anoncvs-usage">Using Anonymous CVS</title>
<title><anchor id="anoncvs-usage"/>Using Anonymous CVS</title>
<para>Configuring &man.cvs.1; to use an Anonymous CVS repository
is a simple matter of setting the <envar>CVSROOT</envar>
@ -392,7 +393,7 @@ SSH2 HostKey: 1024 e8:3b:29:7b:ca:9f:ac:e9:45:cb:c8:17:ae:9b:eb:55 /etc/ssh/ssh_
specific revision, it may mean something different tomorrow than
it means today.</para>
<para><xref linkend="cvs-tags"> contains revision tags that users
<para><xref linkend="cvs-tags"/> contains revision tags that users
might be interested
in. Again, none of these are valid for the Ports Collection
since the Ports Collection does not have multiple
@ -1000,7 +1001,7 @@ Warning: Permanently added 'anoncvs1.freebsd.org' (DSA) to the list of known hos
<itemizedlist>
<listitem>
<para><anchor id="cvsup-config-files">Which files do you want
<para><anchor id="cvsup-config-files"/>Which files do you want
to receive?</para>
<para>The files available via <application>CVSup</application>
@ -1021,7 +1022,7 @@ Warning: Permanently added 'anoncvs1.freebsd.org' (DSA) to the list of known hos
</listitem>
<listitem>
<para><anchor id="cvsup-config-vers">Which version(s) of them
<para><anchor id="cvsup-config-vers"/>Which version(s) of them
do you want?</para>
<para>With <application>CVSup</application>, you can receive
@ -1054,7 +1055,7 @@ Warning: Permanently added 'anoncvs1.freebsd.org' (DSA) to the list of known hos
mean something different tomorrow than it means
today.</para>
<para><xref linkend="cvs-tags"> contains branch tags that
<para><xref linkend="cvs-tags"/> contains branch tags that
users might be interested in. When specifying a tag in
<application>CVSup</application>'s configuration file, it
must be preceded with <literal>tag=</literal>
@ -1100,7 +1101,7 @@ Warning: Permanently added 'anoncvs1.freebsd.org' (DSA) to the list of known hos
</listitem>
<listitem>
<para><anchor id="cvsup-config-where">Where do you want to get
<para><anchor id="cvsup-config-where"/>Where do you want to get
them from?</para>
<para>We use the <literal>host=</literal> field to tell
@ -1122,7 +1123,7 @@ Warning: Permanently added 'anoncvs1.freebsd.org' (DSA) to the list of known hos
</listitem>
<listitem>
<para><anchor id="cvsup-config-dest">Where do you want to put
<para><anchor id="cvsup-config-dest"/>Where do you want to put
them on your own machine?</para>
<para>The <literal>prefix=</literal> field tells
@ -1137,7 +1138,7 @@ Warning: Permanently added 'anoncvs1.freebsd.org' (DSA) to the list of known hos
</listitem>
<listitem>
<para><anchor id="cvsup-config-status">Where should
<para><anchor id="cvsup-config-status"/>Where should
<command>cvsup</command> maintain its status files?</para>
<para>The <application>CVSup</application> client maintains

19
en_US.ISO8859-1/books/handbook/multimedia/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!--
The FreeBSD Documentation Project
@ -39,7 +40,7 @@
<para>This chapter will describe the necessary steps to configure
your sound card. The configuration and installation of X11
(<xref linkend="x11">) has already taken care of the
(<xref linkend="x11"/>) has already taken care of the
hardware issues for your video card, though there may be some
tweaks to apply for better playback.</para>
@ -93,7 +94,7 @@
<itemizedlist>
<listitem><para>Know how to configure and install a new kernel (<xref
linkend="kernelconfig">).</para></listitem>
linkend="kernelconfig"/>).</para></listitem>
</itemizedlist>
<warning>
@ -184,7 +185,7 @@
section below provides the information you need to add support
for your hardware in this manner. For more information about
recompiling your kernel, please see <xref
linkend="kernelconfig">.</para>
linkend="kernelconfig"/>.</para>
<sect3>
<title>Configuring a Custom Kernel with Sound Support</title>
@ -273,7 +274,7 @@ kld snd_ich (1p/2r/0v channels duplex default)</screen>
what was done earlier. Go through your kernel
configuration file again and make sure the correct
device driver was chosen. Common problems are listed in <xref
linkend="troubleshooting">.</para>
linkend="troubleshooting"/>.</para>
<para>If all goes well, you should now have a functioning sound
card. If your CD-ROM or DVD-ROM drive's audio-out pins are properly connected to
@ -587,7 +588,7 @@ MPEG 1.0 layer III, 128 kbit/s, 44100 Hz joint-stereo
<screen>&prompt.root; <userinput>cdda2wav -D <replaceable>0,1,0</replaceable> -t 1+7</userinput></screen>
<para>The utility &man.dd.1; can also be used to extract audio tracks
on ATAPI drives, read <xref linkend="duplicating-audiocds">
on ATAPI drives, read <xref linkend="duplicating-audiocds"/>
for more information on that possibility.</para>
</sect2>
@ -707,7 +708,7 @@ MPEG 1.0 layer III, 128 kbit/s, 44100 Hz joint-stereo
<screen>&prompt.user; <userinput>sox -t wav -r 44100 -s -w -c 2 <replaceable>track.wav track.raw</replaceable></userinput></screen>
<para>Read <xref linkend="creating-cds"> for more information on using a
<para>Read <xref linkend="creating-cds"/> for more information on using a
CD burner in FreeBSD.</para>
</sect2>
</sect1>
@ -903,7 +904,7 @@ no adaptors present</screen>
video card and processor, though, you might still be able to
have a satisfying experience. You should probably read about
ways of improving performance in the advanced reading <xref
linkend="video-further-reading">.</para>
linkend="video-further-reading"/>.</para>
</sect3>
@ -1771,7 +1772,7 @@ found SCSI scanner "AGFA SNAPSCAN 600 1.10" at /dev/pass3</screen>
device `snapscan:/dev/pass3' is a AGFA SNAPSCAN 600 flatbed scanner</screen>
<para>Or, for example with the USB scanner used in the <xref
linkend="scanners-kernel-usb">:</para>
linkend="scanners-kernel-usb"/>:</para>
<screen>&prompt.root; <userinput>scanimage -L</userinput>
device 'epson2:libusb:/dev/usb:/dev/ugen0.2' is a Epson GT-8200 flatbed scanner</screen>
@ -1794,7 +1795,7 @@ device 'epson2:libusb:/dev/usb:/dev/ugen0.2' is a Epson GT-8200 flatbed scanner<
scanners.</para>
<para>For example, with the USB scanner used in the <xref
linkend="scanners-kernel-usb">, under &os;&nbsp;8.X the
linkend="scanners-kernel-usb"/>, under &os;&nbsp;8.X the
scanner is perfectly detected and working but under prior
versions of &os; (where &man.uscanner.4; driver is used)
<command>sane-find-scanner</command> gives us the following

98
en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!--
The FreeBSD Documentation Project
@ -96,7 +97,7 @@
<listitem>
<para>Know how to install additional third-party
software (<xref linkend="ports">).</para>
software (<xref linkend="ports"/>).</para>
</listitem>
</itemizedlist>
@ -618,8 +619,8 @@ server-program-arguments</programlisting>
<informaltable frame="none" pgwide="1">
<tgroup cols="2">
<colspec colwidth="1*">
<colspec colwidth="3*">
<colspec colwidth="1*"/>
<colspec colwidth="3*"/>
<thead>
<row>
@ -798,7 +799,7 @@ mountd_flags="-r"</programlisting>
<screen>&prompt.root; <userinput>/etc/rc.d/mountd onereload</userinput></screen>
<para>Please refer to <xref linkend="configtuning-rcd"> for more
<para>Please refer to <xref linkend="configtuning-rcd"/> for more
information about using rc scripts.</para>
<para>Alternatively, a reboot will make FreeBSD set everything
@ -1217,8 +1218,8 @@ Exports list on foobar:
<informaltable frame="none" pgwide="1">
<tgroup cols="2">
<colspec colwidth="1*">
<colspec colwidth="3*">
<colspec colwidth="1*"/>
<colspec colwidth="3*"/>
<thead>
<row>
@ -1331,11 +1332,13 @@ Exports list on foobar:
assumes a relatively small-scale NIS
environment.</para></note>
</listitem>
<indexterm>
<primary>NIS</primary>
<secondary>slave server</secondary>
</indexterm>
<listitem>
<indexterm>
<primary>NIS</primary>
<secondary>slave server</secondary>
</indexterm>
<para><emphasis>NIS slave servers</emphasis>. Similar to
the &windowsnt; backup domain controllers, NIS slave
servers maintain copies of the NIS master's data files.
@ -1345,11 +1348,13 @@ Exports list on foobar:
always attach to the NIS server whose response they get
first, and this includes slave-server-replies.</para>
</listitem>
<indexterm>
<primary>NIS</primary>
<secondary>client</secondary>
</indexterm>
<listitem>
<indexterm>
<primary>NIS</primary>
<secondary>client</secondary>
</indexterm>
<para><emphasis>NIS clients</emphasis>. NIS clients, like
most &windowsnt; workstations, authenticate against the
NIS server (or the &windowsnt; domain controller in the
@ -1968,7 +1973,7 @@ basie&prompt.root; <userinput>cat /etc/master.passwd</userinput>
root:[password]:0:0::0:0:The super-user:/root:/bin/csh
toor:[password]:0:0::0:0:The other super-user:/root:/bin/sh
daemon:*:1:1::0:0:Owner of many system processes:/root:/sbin/nologin
operator:*:2:5::0:0:System &:/:/sbin/nologin
operator:*:2:5::0:0:System &amp;:/:/sbin/nologin
bin:*:3:7::0:0:Binaries Commands and Source,,,:/:/sbin/nologin
tty:*:4:65533::0:0:Tty Sandbox:/:/sbin/nologin
kmem:*:5:65533::0:0:KMem Sandbox:/:/sbin/nologin
@ -2663,7 +2668,7 @@ nis_client_flags="-S <replaceable>NIS domain</replaceable>,<replaceable>server</
<literal>device bpf</literal> to your kernel
configuration file, and rebuild the kernel. For more
information about building kernels, see <xref
linkend="kernelconfig">.</para> <para>The
linkend="kernelconfig"/>.</para> <para>The
<devicename>bpf</devicename> device is already part of
the <filename>GENERIC</filename> kernel that is supplied
with FreeBSD, so if you do not have a custom kernel, you
@ -2715,7 +2720,7 @@ nis_client_flags="-S <replaceable>NIS domain</replaceable>,<replaceable>server</
<para>Replace the <replaceable>fxp0</replaceable> shown
in these examples with the name of the interface to be
dynamically configured, as described in
<xref linkend="config-network-setup">.</para>
<xref linkend="config-network-setup"/>.</para>
</note>
<para>If you are using a different location for
@ -2805,7 +2810,7 @@ dhclient_flags=""</programlisting>
<para>The server is not provided as part of FreeBSD, and so
you will need to install the <filename
role="package">net/isc-dhcp42-server</filename> port to
provide this service. See <xref linkend="ports"> for
provide this service. See <xref linkend="ports"/> for
more information on using the Ports Collection.</para>
</sect3>
@ -2821,7 +2826,7 @@ dhclient_flags=""</programlisting>
<literal>device bpf</literal> to your kernel
configuration file, and rebuild the kernel. For more
information about building kernels, see <xref
linkend="kernelconfig">.</para>
linkend="kernelconfig"/>.</para>
<para>The <devicename>bpf</devicename> device is already
part of the <filename>GENERIC</filename> kernel that is
@ -2862,22 +2867,22 @@ dhclient_flags=""</programlisting>
declarations regarding subnets and hosts, and is perhaps
most easily explained using an example :</para>
<programlisting>option domain-name "example.com";<co id="domain-name">
option domain-name-servers 192.168.4.100;<co id="domain-name-servers">
option subnet-mask 255.255.255.0;<co id="subnet-mask">
<programlisting>option domain-name "example.com";<co id="domain-name"/>
option domain-name-servers 192.168.4.100;<co id="domain-name-servers"/>
option subnet-mask 255.255.255.0;<co id="subnet-mask"/>
default-lease-time 3600;<co id="default-lease-time">
max-lease-time 86400;<co id="max-lease-time">
ddns-update-style none;<co id="ddns-update-style">
default-lease-time 3600;<co id="default-lease-time"/>
max-lease-time 86400;<co id="max-lease-time"/>
ddns-update-style none;<co id="ddns-update-style"/>
subnet 192.168.4.0 netmask 255.255.255.0 {
range 192.168.4.129 192.168.4.254;<co id="range">
option routers 192.168.4.1;<co id="routers">
range 192.168.4.129 192.168.4.254;<co id="range"/>
option routers 192.168.4.1;<co id="routers"/>
}
host mailhost {
hardware ethernet 02:03:04:05:06:07;<co id="hardware">
fixed-address mailhost.example.com;<co id="fixed-address">
hardware ethernet 02:03:04:05:06:07;<co id="hardware"/>
fixed-address mailhost.example.com;<co id="fixed-address"/>
}</programlisting>
<calloutlist>
@ -3104,8 +3109,8 @@ dhcpd_ifaces="dc0"</programlisting>
<informaltable frame="none" pgwide="1">
<tgroup cols="2">
<colspec colwidth="1*">
<colspec colwidth="3*">
<colspec colwidth="1*"/>
<colspec colwidth="3*"/>
<thead>
<row>
@ -3347,7 +3352,7 @@ dhcpd_ifaces="dc0"</programlisting>
<literal>named_<replaceable>*</replaceable></literal> flags in
<filename>/etc/defaults/rc.conf</filename> and consult the
&man.rc.conf.5; manual page. The <xref
linkend="configtuning-rcd"> section is also a good
linkend="configtuning-rcd"/> section is also a good
read.</para>
</sect2>
@ -3997,7 +4002,7 @@ mail IN A 192.168.1.5</programlisting>
Internet in general. For more in-depth details of how
<acronym>DNSSEC</acronym> works, the relevant
<acronym>RFC</acronym>s are a good place to start. See the
list in <xref linkend="dns-read">.</para>
list in <xref linkend="dns-read"/>.</para>
<para>The following sections will demonstrate how to enable
<acronym>DNSSEC</acronym> for an authoritative
@ -4066,7 +4071,7 @@ mail IN A 192.168.1.5</programlisting>
Signing Key (<acronym
role="Zone Signing Key">ZSK</acronym>). More on the
different key types later in <xref
linkend="dns-dnssec-auth">.</para>
linkend="dns-dnssec-auth"/>.</para>
<para>Now the key must be verified and formatted so that
<acronym>BIND</acronym> can use it. To verify the key,
@ -4324,14 +4329,14 @@ $include Kexample.com.+005+nnnnn.ZSK.key ; ZSK</programlisting>
};</programlisting>
<para>After making these changes, generate keys for the zone
as explained in <xref linkend="dns-dnssec-auth">, put those
as explained in <xref linkend="dns-dnssec-auth"/>, put those
keys in the key repository given as the argument to the
<literal>key-directory</literal> in the zone configuration
and the zone will be signed automatically. Updates to a
zone configured this way must be done using
<application>nsupdate</application>, which will take care of
re-signing the zone with the new data added. For further
details, see <xref linkend="dns-read"> and the
details, see <xref linkend="dns-read"/> and the
<acronym>BIND</acronym> documentation.</para>
</sect3>
</sect2>
@ -5022,10 +5027,10 @@ DocumentRoot /www/someotherdomain.tld
<programlisting>ftp stream tcp nowait root /usr/libexec/ftpd ftpd -l</programlisting>
<para>As explained in <xref linkend="network-inetd-reread">,
<para>As explained in <xref linkend="network-inetd-reread"/>,
the <application>inetd</application> configuration must be
reloaded after this configuration file is changed. Please
refer to <xref linkend="network-inetd-settings"> for details
refer to <xref linkend="network-inetd-settings"/> for details
on enabling <application>inetd</application> on your
system.</para>
@ -5156,7 +5161,7 @@ DocumentRoot /www/someotherdomain.tld
<application>Samba</application>:</para>
<programlisting>swat stream tcp nowait/400 root /usr/local/sbin/swat swat</programlisting>
<para>As explained in <xref linkend="network-inetd-reread">,
<para>As explained in <xref linkend="network-inetd-reread"/>,
the <application>inetd</application> configuration must be
reloaded after this configuration file is changed.</para>
@ -5199,7 +5204,6 @@ DocumentRoot /www/someotherdomain.tld
<varlistentry>
<term><literal>netbios name</literal></term>
<indexterm><primary>NetBIOS</primary></indexterm>
<listitem>
<para>This sets the NetBIOS name by which a
@ -5256,11 +5260,11 @@ DocumentRoot /www/someotherdomain.tld
<varlistentry>
<term><literal>passdb backend</literal></term>
<indexterm><primary>NIS+</primary></indexterm>
<indexterm><primary>LDAP</primary></indexterm>
<indexterm><primary>SQL database</primary></indexterm>
<listitem>
<indexterm><primary>NIS+</primary></indexterm>
<indexterm><primary>LDAP</primary></indexterm>
<indexterm><primary>SQL database</primary></indexterm>
<para><application>Samba</application> has several
different backend authentication models. You can
authenticate clients with LDAP, NIS+, a SQL database,
@ -5330,7 +5334,7 @@ Starting SAMBA: removing stale tdbs :
Starting nmbd.
Starting smbd.</screen>
<para>Please refer to <xref linkend="configtuning-rcd"> for more
<para>Please refer to <xref linkend="configtuning-rcd"/> for more
information about using rc scripts.</para>
<para><application>Samba</application> actually consists of
@ -5459,13 +5463,13 @@ Starting smbd.</screen>
</sect3>
<sect3>
<title>General Configuration</title>
<indexterm>
<primary>NTP</primary>
<secondary>ntp.conf</secondary>
</indexterm>
<title>General Configuration</title>
<para>NTP is configured by the
<filename>/etc/ntp.conf</filename> file in the format
described in &man.ntp.conf.5;. Here is a simple

1
en_US.ISO8859-1/books/handbook/pgpkeys/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!--
The FreeBSD Documentation Project

15
en_US.ISO8859-1/books/handbook/ports/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!--
The FreeBSD Documentation Project
@ -262,9 +263,9 @@
all the applications available in a category.</para>
</listitem>
<indexterm><primary>FreshPorts</primary></indexterm>
<listitem>
<indexterm><primary>FreshPorts</primary></indexterm>
<para>Dan Langille maintains FreshPorts, at <ulink
url="http://www.FreshPorts.org/"></ulink>. FreshPorts
tracks changes to the applications in the ports tree as they
@ -272,9 +273,9 @@
ports, and can send you email when they are updated.</para>
</listitem>
<indexterm><primary>FreshMeat</primary></indexterm>
<listitem>
<indexterm><primary>FreshMeat</primary></indexterm>
<para>If you do not know the name of the application you want,
try using a site like FreshMeat (<ulink
url="http://www.freshmeat.net/"></ulink>) to find an
@ -377,7 +378,7 @@ R-deps: </screen>
<listitem><para>The <command>sysinstall</command> utility can be invoked on a
running system to install, delete, and list available and
installed packages. For more information, see <xref
linkend="packages">.</para></listitem>
linkend="packages"/>.</para></listitem>
<listitem><para>The package management command line tools, which are
the subject of the rest of this section.</para></listitem>
</itemizedlist>
@ -660,7 +661,7 @@ docbook =
<replaceable>cvsup.FreeBSD.org</replaceable> to a
<application>CVSup</application> server near you. See
<link linkend="cvsup-mirrors">CVSup Mirrors</link> (<xref
linkend="cvsup-mirrors">) for a complete listing of mirror
linkend="cvsup-mirrors"/>) for a complete listing of mirror
sites.</para>
<note>
@ -687,7 +688,7 @@ docbook =
<replaceable>CHANGE_THIS.FreeBSD.org</replaceable>
to a <application>CVSup</application> server near
you. See <link linkend="cvsup-mirrors">CVSup
Mirrors</link> (<xref linkend="cvsup-mirrors">) for
Mirrors</link> (<xref linkend="cvsup-mirrors"/>) for
a complete listing of mirror sites.</para>
</step>

95
en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!--
The FreeBSD Documentation Project
@ -177,31 +178,32 @@
<para>The dial-up number(s) of your ISP.</para>
</listitem>
<indexterm id="ppp-pap">
<primary>PAP</primary>
</indexterm>
<indexterm id="ppp-chap">
<primary>CHAP</primary>
</indexterm>
<indexterm id="ppp-unix">
<primary>UNIX</primary>
</indexterm>
<indexterm id="ppp-login">
<primary>login name</primary>
</indexterm>
<indexterm id="ppp-password">
<primary>password</primary>
</indexterm>
<listitem>
<indexterm id="ppp-pap">
<primary>PAP</primary>
</indexterm>
<indexterm id="ppp-chap">
<primary>CHAP</primary>
</indexterm>
<indexterm id="ppp-unix">
<primary>UNIX</primary>
</indexterm>
<indexterm id="ppp-login">
<primary>login name</primary>
</indexterm>
<indexterm id="ppp-password">
<primary>password</primary>
</indexterm>
<para>Your login name and password. (Either a
regular &unix; style login and password pair, or a PAP or CHAP
login and password pair).</para>
</listitem>
<indexterm id="ppp-nameserver">
<primary>nameserver</primary>
</indexterm>
<listitem>
<indexterm id="ppp-nameserver">
<primary>nameserver</primary>
</indexterm>
<para>The IP address of one or more name servers.
Normally, you will be given two IP addresses by your ISP to
use for this. If they have not given you at least one, then
@ -235,10 +237,11 @@
role="netmask">255.255.255.255</hostid>.</para>
</listitem>
<indexterm id="ppp-static-ip">
<primary>static IP address</primary>
</indexterm>
<listitem>
<indexterm id="ppp-static-ip">
<primary>static IP address</primary>
</indexterm>
<para>If your ISP provides you with a static IP address and
hostname, you can enter it. Otherwise, we simply let the
peer assign whatever IP address it sees fit.</para>
@ -380,12 +383,12 @@
<varlistentry>
<term>Line 6 &amp; 7:</term>
<indexterm>
<primary>PPP</primary>
<secondary>user PPP</secondary>
</indexterm>
<listitem>
<indexterm>
<primary>PPP</primary>
<secondary>user PPP</secondary>
</indexterm>
<para>The dial string. User PPP uses an expect-send
syntax similar to the &man.chat.8; program. Refer to
the manual page for information on the features of this
@ -504,8 +507,9 @@ protocol: ppp</screen>
<varlistentry>
<term>Line 16:</term>
<indexterm><primary>timeout</primary></indexterm>
<listitem>
<indexterm><primary>timeout</primary></indexterm>
<para>Sets the default idle timeout (in seconds) for the
connection. Here, the connection will be closed
automatically after 300 seconds of inactivity. If you
@ -516,8 +520,9 @@ protocol: ppp</screen>
<varlistentry>
<term>Line 17:</term>
<indexterm><primary>ISP</primary></indexterm>
<listitem>
<indexterm><primary>ISP</primary></indexterm>
<para>Sets the interface addresses. The string
<replaceable>x.x.x.x</replaceable> should be
replaced by the IP address that your provider has
@ -1038,8 +1043,9 @@ set nbns 203.14.100.5</programlisting>
<varlistentry>
<term>Line 14:</term>
<indexterm><primary>password</primary></indexterm>
<listitem>
<indexterm><primary>password</primary></indexterm>
<para>This line specifies your PAP/CHAP password. You
will need to insert the correct value for
<replaceable>MyPassword</replaceable>. You may want to
@ -1364,12 +1370,12 @@ ifconfig_tun0=</programlisting>
modem line.</para>
</listitem>
<indexterm>
<primary>PPP</primary>
<secondary>server</secondary>
</indexterm>
<listitem>
<indexterm>
<primary>PPP</primary>
<secondary>server</secondary>
</indexterm>
<para>As a <quote>server</quote> &mdash; your machine is located on
the network, and is used to connect other computers using
PPP.</para>
@ -2355,9 +2361,9 @@ ppp_profile="adsl"</programlisting>
adsl:
new -i ng0 adsl adsl
set bundle authname <replaceable>username</replaceable> <co
id="co-mpd-ex-user">
id="co-mpd-ex-user"/>
set bundle password <replaceable>password</replaceable> <co
id="co-mpd-ex-pass">
id="co-mpd-ex-pass"/>
set bundle disable multilink
set link no pap acfcomp protocomp
@ -2394,9 +2400,9 @@ adsl:
set pptp mode active
set pptp enable originate outcall
set pptp self <replaceable>10.0.0.1</replaceable> <co
id="co-mpd-ex-self">
id="co-mpd-ex-self"/>
set pptp peer <replaceable>10.0.0.138</replaceable> <co
id="co-mpd-ex-peer"></programlisting>
id="co-mpd-ex-peer"/></programlisting>
<calloutlist>
<callout arearefs="co-mpd-ex-self">
@ -2447,8 +2453,8 @@ ng0: flags=88d1&lt;UP,POINTOPOINT,RUNNING,NOARP,SIMPLEX,MULTICAST&gt; mtu 1500
set log phase chat lcp ipcp ccp tun command
set timeout 0
enable dns
set authname <replaceable>username</replaceable> <co id="co-pptp-ex-user">
set authkey <replaceable>password</replaceable> <co id="co-pptp-ex-pass">
set authname <replaceable>username</replaceable> <co id="co-pptp-ex-user"/>
set authkey <replaceable>password</replaceable> <co id="co-pptp-ex-pass"/>
set ifaddr 0 0
add default HISADDR</programlisting>
@ -2618,8 +2624,9 @@ tun0: flags=8051&lt;UP,POINTOPOINT,RUNNING,MULTICAST&gt; mtu 1500
placed here.</para>
</listitem>
<indexterm><primary>default route</primary></indexterm>
<listitem>
<indexterm><primary>default route</primary></indexterm>
<para>Designate the default router by changing the
line:</para>
@ -2844,7 +2851,7 @@ water.CS.Example localhost.Example. UGH 34 47641234 lo0 - 0.438
modem(s) and configured the appropriate system files to allow
logins through your modems. If you have not prepared your
system for this yet, please see <xref
linkend="dialup"> for details on dialup services
linkend="dialup"/> for details on dialup services
configuration.
You may also want to check the manual pages for &man.sio.4; for
information on the serial port device driver and &man.ttys.5;,
@ -2948,7 +2955,7 @@ water.CS.Example localhost.Example. UGH 34 47641234 lo0 - 0.438
<screen>&prompt.root; /etc/rc.d/routing start</screen>
<para>Please refer to <xref linkend="kernelconfig"> on
<para>Please refer to <xref linkend="kernelconfig"/> on
Configuring the FreeBSD Kernel for help in
reconfiguring your kernel.</para>
</sect3>
@ -3045,7 +3052,7 @@ Shelmerg dc-slip sl-helmerg 0xfffffc00 autocomp</programlisting
that is the terminology used in this section to describe it).
If you are not sure which method to select or how to assign IP
addresses, please refer to the TCP/IP books referenced in
the SLIP Prerequisites (<xref linkend="slips-prereqs">)
the SLIP Prerequisites (<xref linkend="slips-prereqs"/>)
and/or consult your IP network manager.</para>
<para>If you are going to use a separate subnet for your SLIP

151
en_US.ISO8859-1/books/handbook/preface/preface.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!--
$FreeBSD$
-->
@ -5,7 +6,7 @@
<preface id="book-preface">
<title>Preface</title>
<bridgehead id="preface-audience" renderas=sect1>Intended
<bridgehead id="preface-audience" renderas="sect1">Intended
Audience</bridgehead>
<para>The &os; newcomer will find that the first section of this
@ -23,9 +24,9 @@
chapter.</para>
<para>For a list of additional sources of information, please see <xref
linkend="bibliography">.</para>
linkend="bibliography"/>.</para>
<bridgehead id="preface-changes-from3" renderas=sect1>Changes from the
<bridgehead id="preface-changes-from3" renderas="sect1">Changes from the
Third Edition</bridgehead>
<para>The current online version of the Handbook represents the
@ -35,31 +36,31 @@
<itemizedlist>
<listitem>
<para><xref linkend="dtrace">, &dtrace;, has been added with
<para><xref linkend="dtrace"/>, &dtrace;, has been added with
information about the powerful &dtrace; performance analysis
tool.</para>
</listitem>
<listitem>
<para><xref linkend="filesystems">, File Systems Support, has
<para><xref linkend="filesystems"/>, File Systems Support, has
been added with information about non-native file systems in
&os;, such as ZFS from &sun;.</para>
</listitem>
<listitem>
<para><xref linkend="audit">, Security Event Auditing, has
<para><xref linkend="audit"/>, Security Event Auditing, has
been added to cover the new auditing capabilities in &os;
and explain its use.</para>
</listitem>
<listitem>
<para><xref linkend="virtualization">, Virtualization, has
<para><xref linkend="virtualization"/>, Virtualization, has
been added with information about installing &os; on
virtualization software.</para>
</listitem>
<listitem>
<para><xref linkend="bsdinstall">, Installing
<para><xref linkend="bsdinstall"/>, Installing
&os;&nbsp;9.<replaceable>x</replaceable> and Later, has been
added to cover installation of &os; using the new
installation utility,
@ -67,7 +68,7 @@
</listitem>
</itemizedlist>
<bridgehead id="preface-changes-from2" renderas=sect1>Changes from the
<bridgehead id="preface-changes-from2" renderas="sect1">Changes from the
Second Edition (2004)</bridgehead>
<para>The third edition was the culmination of over two years of
@ -78,35 +79,35 @@
<itemizedlist>
<listitem>
<para><xref linkend="config-tuning">, Configuration and
<para><xref linkend="config-tuning"/>, Configuration and
Tuning, has been expanded with new information about the
ACPI power and resource management, the <command>cron</command> system utility,
and more kernel tuning options.</para>
</listitem>
<listitem>
<para><xref linkend="security">, Security, has been expanded with
<para><xref linkend="security"/>, Security, has been expanded with
new information about virtual private networks (VPNs), file
system access control lists (ACLs), and security
advisories.</para>
</listitem>
<listitem>
<para><xref linkend="mac">, Mandatory Access Control (MAC), is
<para><xref linkend="mac"/>, Mandatory Access Control (MAC), is
a new chapter with this edition. It explains what MAC is
and how this mechanism can be used to secure a &os;
system.</para>
</listitem>
<listitem>
<para><xref linkend="disks">, Storage, has been expanded with
<para><xref linkend="disks"/>, Storage, has been expanded with
new information about USB storage devices, file system
snapshots, file system quotas, file and network backed
filesystems, and encrypted disk partitions.</para>
</listitem>
<listitem>
<para><xref linkend="vinum-vinum">, Vinum, is a new chapter
<para><xref linkend="vinum-vinum"/>, Vinum, is a new chapter
with this edition. It describes how to use Vinum, a logical
volume manager which provides device-independent logical
disks, and software RAID-0, RAID-1 and RAID-5.</para>
@ -114,28 +115,28 @@
<listitem>
<para>A troubleshooting section has been added to <xref
linkend="ppp-and-slip">, PPP and SLIP.</para>
linkend="ppp-and-slip"/>, PPP and SLIP.</para>
</listitem>
<listitem>
<para><xref linkend="mail">, Electronic Mail, has been
<para><xref linkend="mail"/>, Electronic Mail, has been
expanded with new information about using alternative
transport agents, SMTP authentication, UUCP, <application>fetchmail</application>,
<application>procmail</application>, and other advanced topics.</para>
</listitem>
<listitem>
<para><xref linkend="network-servers">, Network Servers, is
<para><xref linkend="network-servers"/>, Network Servers, is
all new with this edition. This chapter includes
information about setting up the <application>Apache HTTP Server</application>, <application>ftpd</application>,
and setting up a server for &microsoft; &windows; clients with
<application>Samba</application>. Some sections from <xref
linkend="advanced-networking">, Advanced Networking, were
linkend="advanced-networking"/>, Advanced Networking, were
moved here to improve the presentation.</para>
</listitem>
<listitem>
<para><xref linkend="advanced-networking">, Advanced
<para><xref linkend="advanced-networking"/>, Advanced
Networking, has been expanded with new information about
using &bluetooth; devices with &os;, setting up wireless
networks, and Asynchronous Transfer Mode (ATM)
@ -154,7 +155,7 @@
</listitem>
</itemizedlist>
<bridgehead id="preface-changes" renderas=sect1>Changes from the
<bridgehead id="preface-changes" renderas="sect1">Changes from the
First Edition (2001)</bridgehead>
<para>The second edition was the culmination of over two years of
@ -182,55 +183,55 @@
<quote>Appendices</quote>.</para>
</listitem>
<listitem>
<para><xref linkend="install"> (<quote>Installing &os;</quote>) was completely
<para><xref linkend="install"/> (<quote>Installing &os;</quote>) was completely
rewritten with many screenshots to make it much easier for new
users to grasp the text.</para>
</listitem>
<listitem>
<para><xref linkend="basics"> (<quote>&unix; Basics</quote>) has been expanded to contain
<para><xref linkend="basics"/> (<quote>&unix; Basics</quote>) has been expanded to contain
additional information about processes, daemons, and
signals.</para>
</listitem>
<listitem>
<para><xref linkend="ports"> (<quote>Installing Applications</quote>) has been expanded
<para><xref linkend="ports"/> (<quote>Installing Applications</quote>) has been expanded
to contain additional information about binary package
management.</para>
</listitem>
<listitem>
<para><xref linkend="x11"> (<quote>The X Window System</quote>) has been completely
<para><xref linkend="x11"/> (<quote>The X Window System</quote>) has been completely
rewritten with an emphasis on using modern desktop
technologies such as <application>KDE</application> and <application>GNOME</application> on &xfree86; 4.X.</para>
</listitem>
<listitem>
<para><xref linkend="boot"> (<quote>The &os; Booting Process</quote>) has been
<para><xref linkend="boot"/> (<quote>The &os; Booting Process</quote>) has been
expanded.</para>
</listitem>
<listitem>
<para><xref linkend="disks"> (<quote>Storage</quote>) has been written from what used
<para><xref linkend="disks"/> (<quote>Storage</quote>) has been written from what used
to be two separate chapters on <quote>Disks</quote> and <quote>Backups</quote>. We feel
that the topics are easier to comprehend when presented as a
single chapter. A section on RAID (both hardware and
software) has also been added.</para>
</listitem>
<listitem>
<para><xref linkend="serialcomms"> (<quote>Serial Communications</quote>) has been completely
<para><xref linkend="serialcomms"/> (<quote>Serial Communications</quote>) has been completely
reorganized and updated for &os; 4.X/5.X.</para>
</listitem>
<listitem>
<para><xref linkend="ppp-and-slip"> (<quote>PPP and SLIP</quote>) has been substantially
<para><xref linkend="ppp-and-slip"/> (<quote>PPP and SLIP</quote>) has been substantially
updated.</para>
</listitem>
<listitem>
<para>Many new sections have been added to <xref linkend="advanced-networking">
<para>Many new sections have been added to <xref linkend="advanced-networking"/>
(<quote>Advanced Networking</quote>).</para>
</listitem>
<listitem>
<para><xref linkend="mail"> (<quote>Electronic Mail</quote>) has been expanded to
<para><xref linkend="mail"/> (<quote>Electronic Mail</quote>) has been expanded to
include more information about configuring
<application>sendmail</application>.</para>
</listitem>
<listitem>
<para><xref linkend="linuxemu"> (<quote>&linux; Compatibility</quote>) has been expanded to
<para><xref linkend="linuxemu"/> (<quote>&linux; Compatibility</quote>) has been expanded to
include information about installing
<application>&oracle;</application> and
<application>&sap.r3;</application>.</para>
@ -240,16 +241,16 @@
edition:</para>
<itemizedlist>
<listitem>
<para>Configuration and Tuning (<xref linkend="config-tuning">).</para>
<para>Configuration and Tuning (<xref linkend="config-tuning"/>).</para>
</listitem>
<listitem>
<para>Multimedia (<xref linkend="multimedia">)</para>
<para>Multimedia (<xref linkend="multimedia"/>)</para>
</listitem>
</itemizedlist>
</listitem>
</itemizedlist>
<bridgehead id="preface-overview" renderas=sect1>Organization of This
<bridgehead id="preface-overview" renderas="sect1">Organization of This
Book</bridgehead>
<para>This book is split into five logically distinct sections.
@ -275,14 +276,14 @@
<!-- Part I - Introduction -->
<varlistentry>
<term><emphasis><xref linkend="introduction">, Introduction</emphasis></term>
<term><emphasis><xref linkend="introduction"/>, Introduction</emphasis></term>
<listitem>
<para>Introduces &os; to a new user. It describes the
history of the &os; Project, its goals and development model.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><emphasis><xref linkend="install">, Installation of
<term><emphasis><xref linkend="install"/>, Installation of
&os;&nbsp;8.<replaceable>x</replaceable> and Earlier</emphasis></term>
<listitem>
<para>Walks a user through the entire installation process of
@ -293,7 +294,7 @@
</listitem>
</varlistentry>
<varlistentry>
<term><emphasis><xref linkend="bsdinstall">, Installation of
<term><emphasis><xref linkend="bsdinstall"/>, Installation of
&os;&nbsp;9.<replaceable>x</replaceable> and Later</emphasis></term>
<listitem>
<para>Walks a user through the entire installation process of
@ -302,7 +303,7 @@
</listitem>
</varlistentry>
<varlistentry>
<term><emphasis><xref linkend="basics">, &unix; Basics</emphasis></term>
<term><emphasis><xref linkend="basics"/>, &unix; Basics</emphasis></term>
<listitem>
<para>Covers the basic commands and functionality of the
&os; operating system. If you are familiar with &linux; or
@ -311,7 +312,7 @@
</listitem>
</varlistentry>
<varlistentry>
<term><emphasis><xref linkend="ports">, Installing Applications</emphasis></term>
<term><emphasis><xref linkend="ports"/>, Installing Applications</emphasis></term>
<listitem>
<para>Covers the installation of third-party software with
both &os;'s innovative <quote>Ports Collection</quote> and standard
@ -319,7 +320,7 @@
</listitem>
</varlistentry>
<varlistentry>
<term><emphasis><xref linkend="x11">, The X Window System</emphasis></term>
<term><emphasis><xref linkend="x11"/>, The X Window System</emphasis></term>
<listitem>
<para>Describes the X Window System in general and using
X11 on &os; in particular. Also describes common
@ -330,7 +331,7 @@
<!-- Part II Common Tasks -->
<varlistentry>
<term><emphasis><xref linkend="desktop">, Desktop Applications</emphasis></term>
<term><emphasis><xref linkend="desktop"/>, Desktop Applications</emphasis></term>
<listitem>
<para>Lists some common desktop applications, such as web browsers
and productivity suites, and describes how to install them on
@ -338,14 +339,14 @@
</listitem>
</varlistentry>
<varlistentry>
<term><emphasis><xref linkend="multimedia">, Multimedia</emphasis></term>
<term><emphasis><xref linkend="multimedia"/>, Multimedia</emphasis></term>
<listitem>
<para>Shows how to set up sound and video playback support for your
system. Also describes some sample audio and video applications.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><emphasis><xref linkend="kernelconfig">, Configuring the &os;
<term><emphasis><xref linkend="kernelconfig"/>, Configuring the &os;
Kernel</emphasis></term>
<listitem>
<para>Explains why you might need to configure a new kernel
@ -354,7 +355,7 @@
</listitem>
</varlistentry>
<varlistentry>
<term><emphasis><xref linkend="printing">, Printing</emphasis></term>
<term><emphasis><xref linkend="printing"/>, Printing</emphasis></term>
<listitem>
<para>Describes managing printers on &os;, including
information about banner pages, printer accounting, and
@ -362,7 +363,7 @@
</listitem>
</varlistentry>
<varlistentry>
<term><emphasis><xref linkend="linuxemu">, &linux; Binary Compatibility</emphasis></term>
<term><emphasis><xref linkend="linuxemu"/>, &linux; Binary Compatibility</emphasis></term>
<listitem>
<para>Describes the &linux; compatibility features of &os;.
Also provides detailed installation instructions for many
@ -374,7 +375,7 @@
<!-- Part III - System Administration -->
<varlistentry>
<term><emphasis><xref linkend="config-tuning">, Configuration and Tuning</emphasis></term>
<term><emphasis><xref linkend="config-tuning"/>, Configuration and Tuning</emphasis></term>
<listitem>
<para>Describes the parameters available for system
administrators to tune a &os; system for optimum
@ -383,14 +384,14 @@
</listitem>
</varlistentry>
<varlistentry>
<term><emphasis><xref linkend="boot">, Booting Process</emphasis></term>
<term><emphasis><xref linkend="boot"/>, Booting Process</emphasis></term>
<listitem>
<para>Describes the &os; boot process and explains
how to control this process with configuration options.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><emphasis><xref linkend="users">, Users and Basic Account
<term><emphasis><xref linkend="users"/>, Users and Basic Account
Management</emphasis></term>
<listitem>
<para>Describes the creation and manipulation of user
@ -399,28 +400,28 @@
</listitem>
</varlistentry>
<varlistentry>
<term><emphasis><xref linkend="security">, Security</emphasis></term>
<term><emphasis><xref linkend="security"/>, Security</emphasis></term>
<listitem>
<para>Describes many different tools available to help keep your
&os; system secure, including Kerberos, IPsec and OpenSSH.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><emphasis><xref linkend="jails">, Jails</emphasis></term>
<term><emphasis><xref linkend="jails"/>, Jails</emphasis></term>
<listitem>
<para>Describes the jails framework, and the improvements of jails
over the traditional chroot support of &os;.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><emphasis><xref linkend="mac">, Mandatory Access Control</emphasis></term>
<term><emphasis><xref linkend="mac"/>, Mandatory Access Control</emphasis></term>
<listitem>
<para>Explains what Mandatory Access Control (MAC) is and how this
mechanism can be used to secure a &os; system.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><emphasis><xref linkend="audit">, Security Event Auditing</emphasis></term>
<term><emphasis><xref linkend="audit"/>, Security Event Auditing</emphasis></term>
<listitem>
<para>Describes what &os; Event Auditing is, how it can be installed,
configured, and how audit trails can be inspected or monitored.</para>
@ -428,7 +429,7 @@
</varlistentry>
<varlistentry>
<term><emphasis><xref linkend="disks">, Storage</emphasis></term>
<term><emphasis><xref linkend="disks"/>, Storage</emphasis></term>
<listitem>
<para>Describes how to manage storage media and filesystems
with &os;. This includes physical disks, RAID arrays,
@ -437,21 +438,21 @@
</listitem>
</varlistentry>
<varlistentry>
<term><emphasis><xref linkend="geom">, GEOM</emphasis></term>
<term><emphasis><xref linkend="GEOM-synopsis"/>, GEOM</emphasis></term>
<listitem>
<para>Describes what the GEOM framework in &os; is and how
to configure various supported RAID levels.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><emphasis><xref linkend="filesystems">, File Systems Support</emphasis></term>
<term><emphasis><xref linkend="filesystems"/>, File Systems Support</emphasis></term>
<listitem>
<para>Examines support of non-native file systems in &os;, like the Z
File System from &sun;.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><emphasis><xref linkend="vinum-vinum">, Vinum</emphasis></term>
<term><emphasis><xref linkend="vinum-vinum"/>, Vinum</emphasis></term>
<listitem>
<para>Describes how to use Vinum, a logical volume manager
which provides device-independent logical disks, and
@ -459,14 +460,14 @@
</listitem>
</varlistentry>
<varlistentry>
<term><emphasis><xref linkend="virtualization">, Virtualization</emphasis></term>
<term><emphasis><xref linkend="virtualization"/>, Virtualization</emphasis></term>
<listitem>
<para>Describes what virtualization systems offer, and how they
can be used with &os;.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><emphasis><xref linkend="l10n">, Localization</emphasis></term>
<term><emphasis><xref linkend="l10n"/>, Localization</emphasis></term>
<listitem>
<para>Describes how to use &os; in languages other than
English. Covers both system and application level
@ -474,7 +475,7 @@
</listitem>
</varlistentry>
<varlistentry>
<term><emphasis><xref linkend="updating-upgrading">, Updating and Upgrading &os;</emphasis></term>
<term><emphasis><xref linkend="updating-upgrading"/>, Updating and Upgrading &os;</emphasis></term>
<listitem>
<para>Explains the differences between &os;-STABLE,
&os;-CURRENT, and &os; releases. Describes which users
@ -484,7 +485,7 @@
</listitem>
</varlistentry>
<varlistentry>
<term><emphasis><xref linkend="dtrace">, &dtrace;</emphasis></term>
<term><emphasis><xref linkend="dtrace"/>, &dtrace;</emphasis></term>
<listitem>
<para>Describes how to configure and use the &dtrace; tool from &sun;
in &os;. Dynamic tracing can help locate performance issues, by
@ -495,21 +496,21 @@
<!-- Part IV - Network Communications -->
<varlistentry>
<term><emphasis><xref linkend="serialcomms">, Serial Communications</emphasis></term>
<term><emphasis><xref linkend="serialcomms"/>, Serial Communications</emphasis></term>
<listitem>
<para>Explains how to connect terminals and modems to your
&os; system for both dial in and dial out connections.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><emphasis><xref linkend="ppp-and-slip">, PPP and SLIP</emphasis></term>
<term><emphasis><xref linkend="ppp-and-slip"/>, PPP and SLIP</emphasis></term>
<listitem>
<para>Describes how to use PPP, SLIP, or PPP over Ethernet to
connect to remote systems with &os;.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><emphasis><xref linkend="mail">, Electronic Mail</emphasis></term>
<term><emphasis><xref linkend="mail"/>, Electronic Mail</emphasis></term>
<listitem>
<para>Explains the different components of an email server and
dives into simple configuration topics for the most popular
@ -518,7 +519,7 @@
</listitem>
</varlistentry>
<varlistentry>
<term><emphasis><xref linkend="network-servers">, Network Servers</emphasis></term>
<term><emphasis><xref linkend="network-servers"/>, Network Servers</emphasis></term>
<listitem>
<para>Provides detailed instructions and example configuration
files to set up your &os; machine as a network filesystem
@ -527,7 +528,7 @@
</listitem>
</varlistentry>
<varlistentry>
<term><emphasis><xref linkend="firewalls">, Firewalls</emphasis></term>
<term><emphasis><xref linkend="firewalls"/>, Firewalls</emphasis></term>
<listitem>
<para>Explains the philosophy behind software-based firewalls and
provides detailed information about the configuration of the
@ -535,7 +536,7 @@
</listitem>
</varlistentry>
<varlistentry>
<term><emphasis><xref linkend="advanced-networking">, Advanced Networking</emphasis></term>
<term><emphasis><xref linkend="advanced-networking"/>, Advanced Networking</emphasis></term>
<listitem>
<para>Describes many networking topics, including sharing an
Internet connection with other computers on your LAN, advanced
@ -547,7 +548,7 @@
<!-- Part V - Appendices -->
<varlistentry>
<term><emphasis><xref linkend="mirrors">, Obtaining &os; </emphasis></term>
<term><emphasis><xref linkend="mirrors"/>, Obtaining &os; </emphasis></term>
<listitem>
<para>Lists different sources for obtaining &os; media on CDROM
or DVD as well as different sites on the Internet that allow
@ -555,7 +556,7 @@
</listitem>
</varlistentry>
<varlistentry>
<term><emphasis><xref linkend="bibliography">, Bibliography </emphasis></term>
<term><emphasis><xref linkend="bibliography"/>, Bibliography </emphasis></term>
<listitem>
<para>This book touches on many different subjects that may
leave you hungry for a more detailed explanation. The
@ -564,7 +565,7 @@
</listitem>
</varlistentry>
<varlistentry>
<term><emphasis><xref linkend="eresources">, Resources on the Internet</emphasis></term>
<term><emphasis><xref linkend="eresources"/>, Resources on the Internet</emphasis></term>
<listitem>
<para>Describes the many forums available for &os; users to
post questions and engage in technical conversations about
@ -572,20 +573,20 @@
</listitem>
</varlistentry>
<varlistentry>
<term><emphasis><xref linkend="pgpkeys">, PGP Keys</emphasis></term>
<term><emphasis><xref linkend="pgpkeys"/>, PGP Keys</emphasis></term>
<listitem>
<para>Lists the PGP fingerprints of several &os; Developers.</para>
</listitem>
</varlistentry>
</variablelist>
<bridgehead id="preface-conv" renderas=sect1>Conventions used
<bridgehead id="preface-conv" renderas="sect1">Conventions used
in this book</bridgehead>
<para>To provide a consistent and easy to read text, several
conventions are followed throughout the book.</para>
<bridgehead id="preface-conv-typographic" renderas=sect2>Typographic
<bridgehead id="preface-conv-typographic" renderas="sect2">Typographic
Conventions</bridgehead>
<variablelist>
@ -616,7 +617,7 @@
<!-- Var list -->
<bridgehead id="preface-conv-commands"
renderas=sect2>User Input</bridgehead>
renderas="sect2">User Input</bridgehead>
<para>Keys are shown in <keycap>bold</keycap> to stand out from
other text. Key combinations that are meant to be typed
@ -656,7 +657,7 @@
<!-- How to type in key stokes, etc.. -->
<bridgehead id="preface-conv-examples"
renderas=sect2>Examples</bridgehead>
renderas="sect2">Examples</bridgehead>
<para>Examples starting with <devicename>E:\&gt;</devicename>
indicate a &ms-dos; command. Unless otherwise noted, these commands
@ -681,7 +682,7 @@
<screen>&prompt.user; <userinput>top</userinput></screen>
<bridgehead id="preface-acknowledgements"
renderas=sect1>Acknowledgments</bridgehead>
renderas="sect1">Acknowledgments</bridgehead>
<para>The book you are holding represents the efforts of many hundreds of
people around the world. Whether they sent in fixes for typos, or

60
en_US.ISO8859-1/books/handbook/printing/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!--
The FreeBSD Documentation Project
@ -90,7 +91,7 @@
<itemizedlist>
<listitem>
<para>Know how to configure and install a new kernel
(<xref linkend="kernelconfig">).</para>
(<xref linkend="kernelconfig"/>).</para>
</listitem>
</itemizedlist>
</sect1>
@ -120,8 +121,9 @@
attached to other hosts on the network.</para>
</listitem>
<indexterm><primary>print jobs</primary></indexterm>
<listitem>
<indexterm><primary>print jobs</primary></indexterm>
<para>It enables users to submit files to be printed; these
submissions are known as <emphasis>jobs</emphasis>.</para>
</listitem>
@ -181,8 +183,9 @@
printer.</para>
</listitem>
<indexterm><primary>&tex;</primary></indexterm>
<listitem>
<indexterm><primary>&tex;</primary></indexterm>
<para><application>LPD</application> can conveniently run a job
to be printed through filters to add date/time headers or convert
a special file format (such as a &tex; DVI file) into a format
@ -288,11 +291,12 @@
with one or more of the following three interfaces:</para>
<itemizedlist>
<indexterm>
<primary>printers</primary>
<secondary>serial</secondary>
</indexterm>
<listitem>
<indexterm>
<primary>printers</primary>
<secondary>serial</secondary>
</indexterm>
<para><emphasis>Serial</emphasis> interfaces, also known
as RS-232 or COM ports, use a serial port
on your computer to send data to the printer. Serial
@ -305,11 +309,12 @@
large graphic print jobs with them impractical.</para>
</listitem>
<indexterm>
<primary>printers</primary>
<secondary>parallel</secondary>
</indexterm>
<listitem>
<indexterm>
<primary>printers</primary>
<secondary>parallel</secondary>
</indexterm>
<para><emphasis>Parallel</emphasis> interfaces use a
parallel port on your computer to send data to the
printer. Parallel interfaces are common in the PC market
@ -328,11 +333,12 @@
connector type on the printer.</para>
</listitem>
<indexterm>
<primary>printers</primary>
<secondary>USB</secondary>
</indexterm>
<listitem>
<indexterm>
<primary>printers</primary>
<secondary>USB</secondary>
</indexterm>
<para>USB interfaces, named for the Universal Serial
Bus, can run at even faster speeds than parallel or
RS-232 serial interfaces. Cables are simple and cheap.
@ -413,8 +419,9 @@
<quote>DTE-to-DCE</quote> cable.</para>
</listitem>
<indexterm><primary>null-modem cable</primary></indexterm>
<listitem>
<indexterm><primary>null-modem cable</primary></indexterm>
<para>A <emphasis>null-modem</emphasis> cable connects some
pins straight through, swaps others (send data to receive
data, for example), and shorts some internally in each
@ -896,8 +903,9 @@ showpage</programlisting>
section for more information on naming.</para>
</step>
<indexterm><primary>header pages</primary></indexterm>
<step>
<indexterm><primary>header pages</primary></indexterm>
<para>Turn off header pages (which are on by default) by
inserting the <literal>sh</literal> capability; see the
<link linkend="printing-no-header-pages">Suppressing Header
@ -1662,11 +1670,12 @@ $%&amp;'()*+,-./01234567
</variablelist>
</listitem>
<indexterm>
<primary>printing</primary>
<secondary>filters</secondary>
</indexterm>
<listitem>
<indexterm>
<primary>printing</primary>
<secondary>filters</secondary>
</indexterm>
<para>A <emphasis>conversion filter</emphasis> converts a specific
file format into one the printer can render onto paper. For
example, ditroff typesetting data cannot be directly printed,
@ -4537,8 +4546,9 @@ cfA013rose dequeued
<varlistentry>
<term>LPRng</term>
<indexterm><primary>LPRng</primary></indexterm>
<listitem>
<indexterm><primary>LPRng</primary></indexterm>
<para><application>LPRng</application>, which purportedly means
<quote>LPR: the Next Generation</quote> is a complete rewrite of
PLP. Patrick Powell and Justin Mason (the principal maintainer
@ -4551,8 +4561,9 @@ cfA013rose dequeued
<varlistentry>
<term>CUPS</term>
<indexterm><primary>CUPS</primary></indexterm>
<listitem>
<indexterm><primary>CUPS</primary></indexterm>
<para><application>CUPS</application>, the Common UNIX Printing
System, provides a portable printing layer for &unix;-based
operating systems. It has been developed by Easy Software
@ -4577,8 +4588,9 @@ cfA013rose dequeued
<varlistentry>
<term>HPLIP</term>
<indexterm><primary>HPLIP</primary></indexterm>
<listitem>
<indexterm><primary>HPLIP</primary></indexterm>
<para><application>HPLIP</application>, the HP &linux; Imaging and
Printing system, is an HP-developed suite of programs that
supports printing, scanning and fax facilities for HP appliances.

77
en_US.ISO8859-1/books/handbook/security/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!--
The FreeBSD Documentation Project
@ -108,8 +109,8 @@
<para>Additional security topics are covered throughout this book.
For example, Mandatory Access Control is discussed in <xref
linkend="mac"> and Internet Firewalls are discussed in <xref
linkend="firewalls">.</para>
linkend="mac"/> and Internet Firewalls are discussed in <xref
linkend="firewalls"/>.</para>
</sect1>
<sect1 id="security-intro">
@ -1383,10 +1384,10 @@ Enter secret pass phrase: <userinput>&lt;secret password&gt;</userinput>
</authorgroup>
</sect1info>
<indexterm><primary>TCP Wrappers</primary></indexterm>
<title>TCP Wrappers</title>
<indexterm><primary>TCP Wrappers</primary></indexterm>
<para>Anyone familiar with &man.inetd.8; has probably heard of
<acronym>TCP</acronym> Wrappers at some point. But few
individuals seem to fully comprehend its usefulness in a network
@ -2097,12 +2098,12 @@ jdoe@example.org</screen>
<title><application>Kerberos</application> Tips, Tricks, and
Troubleshooting</title>
<indexterm>
<primary>Kerberos5</primary>
<secondary>troubleshooting</secondary>
</indexterm>
<itemizedlist>
<indexterm>
<primary>Kerberos5</primary>
<secondary>troubleshooting</secondary>
</indexterm>
<listitem>
<para>When using either the Heimdal or
<acronym>MIT</acronym>
@ -2115,7 +2116,7 @@ jdoe@example.org</screen>
<listitem>
<para>Do all the computers in your realm have synchronized
time settings? If not, authentication may fail.
<xref linkend="network-ntp"> describes how to synchronize
<xref linkend="network-ntp"/> describes how to synchronize
clocks using <acronym>NTP</acronym>.</para>
</listitem>
@ -2675,12 +2676,12 @@ Connection closed by foreign host.</screen>
</authorgroup>
</sect1info>
<title>VPN over IPsec</title>
<indexterm>
<primary>IPsec</primary>
</indexterm>
<title>VPN over IPsec</title>
<para>Creating a VPN between two networks, separated by the
Internet, using FreeBSD gateways.</para>
@ -2703,7 +2704,7 @@ Connection closed by foreign host.</screen>
<para>This section will guide you through the process of
setting up IPsec. In order to set up IPsec, it is necessary
that you are familiar with the concepts of building a custom
kernel (see <xref linkend="kernelconfig">).</para>
kernel (see <xref linkend="kernelconfig"/>).</para>
<para><emphasis>IPsec</emphasis> is a protocol which sits on
top of the Internet Protocol (IP) layer. It allows two or
@ -3349,7 +3350,7 @@ bb:48:db:f2:93:57:80:b6:aa:bc:f5:d5:ba:8f:79:17 user@host.example.com</screen>
will be prompted for a password each time in order to use
the private key. &man.ssh-agent.1; can alleviate the strain
of repeatedly entering long passphrases, and is explored in
the <xref linkend="security-ssh-agent"> section
the <xref linkend="security-ssh-agent"/> section
below.</para>
<warning>
@ -3627,12 +3628,12 @@ user@unfirewalled-system.example.org's password: <userinput>*******</userinput><
</authorgroup>
</sect1info>
<title>File System Access Control Lists</title>
<indexterm>
<primary>ACL</primary>
</indexterm>
<title>File System Access Control Lists</title>
<para>In conjunction with file system enhancements like
snapshots, FreeBSD offers the security of File System Access
Control Lists (<acronym>ACL</acronym>s).</para>
@ -3786,12 +3787,12 @@ drwxr-xr-x 2 robert robert 512 Nov 10 11:54 public_html</programlisting>
</authorgroup>
</sect1info>
<title>Monitoring Third Party Security Issues</title>
<indexterm>
<primary>Portaudit</primary>
</indexterm>
<title>Monitoring Third Party Security Issues</title>
<para>In recent years, the security world has made many
improvements to how vulnerability assessment is handled. The
threat of system intrusion increases as third party utilities
@ -3877,12 +3878,13 @@ You are advised to update or deinstall the affected package(s) immediately.</pro
</author>
</authorgroup>
</sect1info>
<title>&os; Security Advisories</title>
<indexterm>
<primary>FreeBSD Security Advisories</primary>
</indexterm>
<title>&os; Security Advisories</title>
<para>Like many production quality operating systems, &os;
publishes <quote>Security Advisories</quote>. These
advisories are usually mailed to the security lists and noted
@ -3902,13 +3904,13 @@ You are advised to update or deinstall the affected package(s) immediately.</pro
FreeBSD-SA-XX:XX.UTIL Security Advisory
The FreeBSD Project
Topic: denial of service due to some problem <co id="co-topic">
Topic: denial of service due to some problem <co id="co-topic"/>
Category: core <co id="co-category">
Module: sys <co id="co-module">
Announced: 2003-09-23 <co id="co-announce">
Credits: Person <co id="co-credit">
Affects: All releases of &os; <co id="co-affects">
Category: core <co id="co-category"/>
Module: sys <co id="co-module"/>
Announced: 2003-09-23 <co id="co-announce"/>
Credits: Person <co id="co-credit"/>
Affects: All releases of &os; <co id="co-affects"/>
&os; 4-STABLE prior to the correction date
Corrected: 2003-09-23 16:42:59 UTC (RELENG_4, 4.9-PRERELEASE)
2003-09-23 20:08:42 UTC (RELENG_5_1, 5.1-RELEASE-p6)
@ -3918,33 +3920,33 @@ Corrected: 2003-09-23 16:42:59 UTC (RELENG_4, 4.9-PRERELEASE)
2003-09-23 16:49:46 UTC (RELENG_4_6, 4.6-RELEASE-p21)
2003-09-23 16:51:24 UTC (RELENG_4_5, 4.5-RELEASE-p33)
2003-09-23 16:52:45 UTC (RELENG_4_4, 4.4-RELEASE-p43)
2003-09-23 16:54:39 UTC (RELENG_4_3, 4.3-RELEASE-p39) <co id="co-corrected">
<acronym>CVE</acronym> Name: CVE-XXXX-XXXX <co id="co-cve">
2003-09-23 16:54:39 UTC (RELENG_4_3, 4.3-RELEASE-p39) <co id="co-corrected"/>
<acronym>CVE</acronym> Name: CVE-XXXX-XXXX <co id="co-cve"/>
For general information regarding FreeBSD Security Advisories,
including descriptions of the fields above, security branches, and the
following sections, please visit
http://www.FreeBSD.org/security/.
I. Background <co id="co-backround">
I. Background <co id="co-backround"/>
II. Problem Description <co id="co-descript">
II. Problem Description <co id="co-descript"/>
III. Impact <co id="co-impact">
III. Impact <co id="co-impact"/>
IV. Workaround <co id="co-workaround">
IV. Workaround <co id="co-workaround"/>
V. Solution <co id="co-solution">
V. Solution <co id="co-solution"/>
VI. Correction details <co id="co-details">
VI. Correction details <co id="co-details"/>
VII. References <co id="co-ref"></programlisting>
VII. References <co id="co-ref"/></programlisting>
<calloutlist>
<callout arearefs="co-topic">
@ -4088,12 +4090,13 @@ VII. References <co id="co-ref"></programlisting>
</author>
</authorgroup>
</sect1info>
<title>Process Accounting</title>
<indexterm>
<primary>Process Accounting</primary>
</indexterm>
<title>Process Accounting</title>
<para>Process accounting is a security method in which an
administrator may keep track of system resources used,
their allocation among users, provide for system monitoring,

43
en_US.ISO8859-1/books/handbook/serialcomms/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!--
The FreeBSD Documentation Project
@ -44,11 +45,11 @@
<itemizedlist>
<listitem>
<para>Know how to configure and install a new kernel (<xref
linkend="kernelconfig">).</para>
linkend="kernelconfig"/>).</para>
</listitem>
<listitem>
<para>Understand &unix; permissions and processes (<xref
linkend="basics">).</para>
linkend="basics"/>).</para>
</listitem>
<listitem>
<para>Have access to the technical manual for the serial hardware
@ -89,8 +90,9 @@
<varlistentry>
<term>DTE</term>
<indexterm><primary>DTE</primary></indexterm>
<listitem>
<indexterm><primary>DTE</primary></indexterm>
<para>Data Terminal Equipment &mdash; for example, your
computer</para>
</listitem>
@ -98,16 +100,19 @@
<varlistentry>
<term>DCE</term>
<indexterm><primary>DCE</primary></indexterm>
<listitem>
<indexterm><primary>DCE</primary></indexterm>
<para>Data Communications Equipment &mdash; your modem</para>
</listitem>
</varlistentry>
<varlistentry>
<term>RS-232</term>
<indexterm><primary>RS-232C cables</primary></indexterm>
<listitem>
<indexterm><primary>RS-232C cables</primary></indexterm>
<para>EIA standard for hardware serial communications</para>
</listitem>
</varlistentry>
@ -836,7 +841,7 @@ sio3: type 16550A</screen>
already configured your kernel to support the serial port to which the
terminal is connected&mdash;and that you have connected it.</para>
<para>Recall from <xref linkend="boot"> that the
<para>Recall from <xref linkend="boot"/> that the
<command>init</command> process is responsible for all process
control and initialization at system startup. One of the
tasks performed by <command>init</command> is to read the
@ -923,11 +928,11 @@ sio3: type 16550A</screen>
look like this:</para>
<programlisting>ttyu1<co
id="co-ttys-line1col1"> "/usr/libexec/getty std.38400"<co
id="co-ttys-line1col2"> wy50<co
id="co-ttys-line1col3"> on<co
id="co-ttys-line1col4"> insecure<co
id="co-ttys-line1col5">
id="co-ttys-line1col1"/> "/usr/libexec/getty std.38400"<co
id="co-ttys-line1col2"/> wy50<co
id="co-ttys-line1col3"/> on<co
id="co-ttys-line1col4"/> insecure<co
id="co-ttys-line1col5"/>
ttyu5 "/usr/libexec/getty std.19200" vt100 on insecure
</programlisting>
@ -1477,7 +1482,7 @@ vq|VH57600|Very High Speed Modem at 57600,8-bit:\
</indexterm>
<para>Configuration of the <filename>/etc/ttys</filename> file
was covered in <xref linkend="ex-etc-ttys">.
was covered in <xref linkend="ex-etc-ttys"/>.
Configuration for modems is similar but we must pass a
different argument to <command>getty</command> and specify a
different terminal type. The general format for both
@ -2169,7 +2174,7 @@ raisechar=^^</programlisting>
attached, and developers who want to debug the kernel or device
drivers.</para>
<para>As described in <xref linkend="boot">, FreeBSD employs a three
<para>As described in <xref linkend="boot"/>, FreeBSD employs a three
stage bootstrap. The first two stages are in the boot block code which
is stored at the beginning of the FreeBSD slice on the boot disk. The
boot block will then load and run the boot loader
@ -2217,7 +2222,7 @@ raisechar=^^</programlisting>
<para>If a different configuration is required, a more in depth
configuration explanation exists in
<xref linkend="serialconsole-howto">.</para>
<xref linkend="serialconsole-howto"/>.</para>
</sect2>
<sect2 id="serialconsole-howto">
@ -2229,7 +2234,7 @@ raisechar=^^</programlisting>
<indexterm><primary>null-modem cable</primary></indexterm>
<para>You will need either a null-modem cable or a standard serial
cable and a null-modem adapter. See <xref linkend="serial-cables-ports"> for
cable and a null-modem adapter. See <xref linkend="serial-cables-ports"/> for
a discussion on serial cables.</para>
</step>
@ -2539,7 +2544,7 @@ boot:</screen>
<para>After the boot loader is loaded and you are in the third stage of
the boot process you can still switch between the internal console and
the serial console by setting appropriate environment variables in the
boot loader. See <xref linkend="serialconsole-loader">.</para>
boot loader. See <xref linkend="serialconsole-loader"/>.</para>
</sect2>
<sect2 id="serialconsole-summary">
@ -2690,7 +2695,7 @@ boot:</screen>
<listitem>
<para>Recompile the boot blocks
with <makevar>BOOT_COMCONSOLE_SPEED</makevar> set to the new
console speed. See <xref linkend="serialconsole-com2"> for
console speed. See <xref linkend="serialconsole-com2"/> for
detailed instructions about building and installing new boot
blocks.</para>
@ -2744,7 +2749,7 @@ console="comconsole,vidconsole"</programlisting>
<procedure>
<step>
<para>Get the kernel source. (See <xref
linkend="updating-upgrading">)</para>
linkend="updating-upgrading"/>)</para>
</step>
<step>
@ -2895,7 +2900,7 @@ ttyu3 "/usr/libexec/getty std.9600" unknown off secure</programlisting>
<para>You need to recompile the boot loader to use a serial port other
than <devicename>sio0</devicename> for the serial console. Follow the
procedure described in <xref linkend="serialconsole-com2">.</para>
procedure described in <xref linkend="serialconsole-com2"/>.</para>
</sect3>
</sect2>

1
en_US.ISO8859-1/books/handbook/txtfiles.ent
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="iso-8859-1"?>
<!--
Creates entities for each .txt screenshot that is included in the
Handbook.

15
en_US.ISO8859-1/books/handbook/users/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!--
The FreeBSD Documentation Project
@ -26,7 +27,7 @@
keyboard at any one time
<footnote>
<para>Well, unless you hook up multiple terminals, but we will
save that for <xref linkend="serialcomms">.</para>
save that for <xref linkend="serialcomms"/>.</para>
</footnote>, but any number of users can log in through the
network to get their work done. To use the system every user must have
an account.</para>
@ -68,7 +69,7 @@
<itemizedlist>
<listitem>
<para>Understand the basics of &unix; and FreeBSD (<xref
linkend="basics">).</para>
linkend="basics"/>).</para>
</listitem>
</itemizedlist>
</sect1>
@ -133,7 +134,7 @@
<term>Group ID (GID)</term>
<listitem>
<para>The GID is a number, traditionally from 0 to 65535<footnoteref linkend="users-largeuidgid">, used to uniquely identify
<para>The GID is a number, traditionally from 0 to 65535<footnoteref linkend="users-largeuidgid"/>, used to uniquely identify
the primary group that the user belongs to. Groups are a
mechanism for controlling access to resources based on a user's
GID rather than their UID. This can significantly reduce the size
@ -331,8 +332,8 @@
<informaltable frame="none" pgwide="1">
<tgroup cols="2">
<colspec colwidth="1*">
<colspec colwidth="2*">
<colspec colwidth="1*"/>
<colspec colwidth="2*"/>
<thead>
<row>
@ -579,7 +580,7 @@ Other information:</screen>
&man.ypchsh.1;. NIS support is automatic, so
specifying the <literal>yp</literal> before the command is
not necessary. If this is confusing to you, do not worry, NIS will
be covered in <xref linkend="network-servers">.</para>
be covered in <xref linkend="network-servers"/>.</para>
</note>
</sect2>
<sect2 id="users-passwd">
@ -672,7 +673,7 @@ passwd: done</screen>
they
provide a way to quickly check that usage without
calculating it every time. Quotas are discussed in <xref
linkend="quotas">.</para>
linkend="quotas"/>.</para>
<para>The other resource limits include ways to limit the amount of
CPU, memory, and other resources a user may consume. These are

45
en_US.ISO8859-1/books/handbook/vinum/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!--
The Vinum Volume Manager
By Greg Lehey (grog at lemis dot com)
@ -61,7 +62,7 @@
<note>
<para>Starting with &os;&nbsp;5, Vinum has been rewritten in order
to fit into the GEOM architecture (<xref linkend="GEOM">),
to fit into the GEOM architecture (<xref linkend="GEOM"/>),
retaining the original ideas, terminology, and on-disk
metadata. This rewrite is called <emphasis>gvinum</emphasis>
(for <emphasis> GEOM vinum</emphasis>). The following text
@ -120,7 +121,7 @@
to be atomic: it does not make any sense to interrupt
them.</para>
<para><anchor id="vinum-latency"> Consider a typical transfer of
<para><anchor id="vinum-latency"/> Consider a typical transfer of
about 10&nbsp;kB: the current generation of high-performance
disks can position the heads in an average of 3.5&nbsp;ms. The
fastest drives spin at 15,000&nbsp;rpm, so the average
@ -167,14 +168,14 @@
relationships. It works well when the access to the virtual
disk is spread evenly about its address space. When access is
concentrated on a smaller area, the improvement is less marked.
<xref linkend="vinum-concat"> illustrates the sequence in which
<xref linkend="vinum-concat"/> illustrates the sequence in which
storage units are allocated in a concatenated
organization.</para>
<para>
<figure id="vinum-concat">
<title>Concatenated Organization</title>
<graphic fileref="vinum/vinum-concat">
<graphic fileref="vinum/vinum-concat"/>
</figure>
</para>
@ -206,14 +207,14 @@
Striping requires somewhat more effort to locate the data, and it
can cause additional I/O load where a transfer is spread over
multiple disks, but it can also provide a more constant load
across the disks. <xref linkend="vinum-striped"> illustrates the
across the disks. <xref linkend="vinum-striped"/> illustrates the
sequence in which storage units are allocated in a striped
organization.</para>
<para>
<figure id="vinum-striped">
<title>Striped Organization</title>
<graphic fileref="vinum/vinum-striped">
<graphic fileref="vinum/vinum-striped"/>
</figure>
</para>
</sect1>
@ -283,7 +284,7 @@
<para>
<figure id="vinum-raid5-org">
<title>RAID-5 Organization</title>
<graphic fileref="vinum/vinum-raid5-org">
<graphic fileref="vinum/vinum-raid5-org"/>
</figure>
</para>
@ -426,7 +427,7 @@
</listitem>
</itemizedlist>
<para><xref linkend="vinum-comparison"> summarizes the advantages
<para><xref linkend="vinum-comparison"/> summarizes the advantages
and disadvantages of each plex organization.</para>
<table id="vinum-comparison" frame="none">
@ -554,12 +555,12 @@
S myvol.p0.s0 State: up PO: 0 B Size: 512 MB</programlisting>
<para>This output shows the brief listing format of &man.gvinum.8;. It
is represented graphically in <xref linkend="vinum-simple-vol">.</para>
is represented graphically in <xref linkend="vinum-simple-vol"/>.</para>
<para>
<figure id="vinum-simple-vol">
<title>A Simple Vinum Volume</title>
<graphic fileref="vinum/vinum-simple-vol">
<graphic fileref="vinum/vinum-simple-vol"/>
</figure>
</para>
@ -621,13 +622,13 @@
S mirror.p0.s0 State: up PO: 0 B Size: 512 MB
S mirror.p1.s0 State: empty PO: 0 B Size: 512 MB</programlisting>
<para><xref linkend="vinum-mirrored-vol"> shows the structure
<para><xref linkend="vinum-mirrored-vol"/> shows the structure
graphically.</para>
<para>
<figure id="vinum-mirrored-vol">
<title>A Mirrored Vinum Volume</title>
<graphic fileref="vinum/vinum-mirrored-vol">
<graphic fileref="vinum/vinum-mirrored-vol"/>
</figure>
</para>
@ -694,12 +695,12 @@
<para>
<figure id="vinum-striped-vol">
<title>A Striped Vinum Volume</title>
<graphic fileref="vinum/vinum-striped-vol">
<graphic fileref="vinum/vinum-striped-vol"/>
</figure>
</para>
<para>This volume is represented in
<xref linkend="vinum-striped-vol">. The darkness of the stripes
<xref linkend="vinum-striped-vol"/>. The darkness of the stripes
indicates the position within the plex address space: the lightest stripes
come first, the darkest last.</para>
</sect2>
@ -707,7 +708,7 @@
<sect2>
<title>Resilience and Performance</title>
<para><anchor id="vinum-resilience">With sufficient hardware, it
<para><anchor id="vinum-resilience"/>With sufficient hardware, it
is possible to build volumes which show both increased
resilience and increased performance compared to standard
&unix; partitions. A typical configuration file might
@ -732,13 +733,13 @@
of the first plex: this helps ensure that writes do not go to the same
subdisks even if a transfer goes over two drives.</para>
<para><xref linkend="vinum-raid10-vol"> represents the structure
<para><xref linkend="vinum-raid10-vol"/> represents the structure
of this volume.</para>
<para>
<figure id="vinum-raid10-vol">
<title>A Mirrored, Striped Vinum Volume</title>
<graphic fileref="vinum/vinum-raid10-vol">
<graphic fileref="vinum/vinum-raid10-vol"/>
</figure>
</para>
</sect2>
@ -974,7 +975,7 @@ sd name bigraid.p0.s4 drive e plex bigraid.p0 state initializing len 4194304b dr
<listitem>
<para>Vinum must be available in the kernel at boot-time.
Thus, the method to start Vinum automatically described in
<xref linkend="vinum-rc-startup"> is not applicable to
<xref linkend="vinum-rc-startup"/> is not applicable to
accomplish this task, and the
<literal>start_vinum</literal> parameter must actually
<emphasis>not</emphasis> be set when the following setup
@ -983,7 +984,7 @@ sd name bigraid.p0.s4 drive e plex bigraid.p0 state initializing len 4194304b dr
the time, but this is usually not desirable. There is
another option as well, to have
<filename>/boot/loader</filename> (<xref
linkend="boot-loader">) load the vinum kernel module
linkend="boot-loader"/>) load the vinum kernel module
early, before starting the kernel. This can be
accomplished by putting the line:</para>
@ -1185,7 +1186,7 @@ Subdisk root.p1.s0:
within the Vinum partition <literal>"h"</literal>, and the
offset of this partition within the device (or slice). This
is a typical setup that is necessary to avoid the problem
described in <xref linkend="vinum-root-panic">. It can also
described in <xref linkend="vinum-root-panic"/>. It can also
be seen that the entire <literal>"a"</literal> partition is
completely within the <literal>"h"</literal> partition
containing all the Vinum data for this device.</para>
@ -1255,7 +1256,7 @@ Subdisk root.p1.s0:
process starts), an attempt can be made to interrupt the
primary bootstrap at this point, using the
<keycap>space</keycap> key. This will make the bootstrap
stop in stage two, see <xref linkend="boot-boot1">. An
stop in stage two, see <xref linkend="boot-boot1"/>. An
attempt can be made here to boot off an alternate partition,
like the partition containing the previous root filesystem
that has been moved away from <literal>"a"</literal>
@ -1280,7 +1281,7 @@ Subdisk root.p1.s0:
for example by booting from a <quote>Fixit</quote> medium,
and the bootstrap has been re-installed using
<command>bsdlabel -B</command> as described in <xref
linkend="boot-boot1">, the bootstrap will trash the Vinum
linkend="boot-boot1"/>, the bootstrap will trash the Vinum
header, and Vinum will no longer find its disk(s). Though
no actual Vinum configuration data or data in Vinum volumes
will be trashed by this, and it would be possible to recover

97
en_US.ISO8859-1/books/handbook/virtualization/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!--
The FreeBSD Documentation Project
@ -66,22 +67,22 @@
<itemizedlist>
<listitem>
<para>Understand the basics of &unix; and &os; (<xref
linkend="basics">).</para>
linkend="basics"/>).</para>
</listitem>
<listitem>
<para>Know how to install &os; (<xref
linkend="install">).</para>
linkend="install"/>).</para>
</listitem>
<listitem>
<para>Know how to set up your network connection (<xref
linkend="advanced-networking">).</para>
linkend="advanced-networking"/>).</para>
</listitem>
<listitem>
<para>Know how to install additional third-party
software (<xref linkend="ports">).</para>
software (<xref linkend="ports"/>).</para>
</listitem>
</itemizedlist>
</sect1>
@ -111,7 +112,7 @@
<mediaobject>
<imageobject>
<imagedata fileref="virtualization/parallels-freebsd1">
<imagedata fileref="virtualization/parallels-freebsd1"/>
</imageobject>
</mediaobject>
@ -122,25 +123,25 @@
<mediaobject>
<imageobject>
<imagedata fileref="virtualization/parallels-freebsd2">
<imagedata fileref="virtualization/parallels-freebsd2"/>
</imageobject>
</mediaobject>
<mediaobject>
<imageobject>
<imagedata fileref="virtualization/parallels-freebsd3">
<imagedata fileref="virtualization/parallels-freebsd3"/>
</imageobject>
</mediaobject>
<mediaobject>
<imageobject>
<imagedata fileref="virtualization/parallels-freebsd4">
<imagedata fileref="virtualization/parallels-freebsd4"/>
</imageobject>
</mediaobject>
<mediaobject>
<imageobject>
<imagedata fileref="virtualization/parallels-freebsd5">
<imagedata fileref="virtualization/parallels-freebsd5"/>
</imageobject>
</mediaobject>
@ -149,13 +150,13 @@
<mediaobject>
<imageobject>
<imagedata fileref="virtualization/parallels-freebsd6">
<imagedata fileref="virtualization/parallels-freebsd6"/>
</imageobject>
</mediaobject>
<mediaobject>
<imageobject>
<imagedata fileref="virtualization/parallels-freebsd7">
<imagedata fileref="virtualization/parallels-freebsd7"/>
</imageobject>
</mediaobject>
@ -163,13 +164,13 @@
<mediaobject>
<imageobject>
<imagedata fileref="virtualization/parallels-freebsd8">
<imagedata fileref="virtualization/parallels-freebsd8"/>
</imageobject>
</mediaobject>
<mediaobject>
<imageobject>
<imagedata fileref="virtualization/parallels-freebsd9">
<imagedata fileref="virtualization/parallels-freebsd9"/>
</imageobject>
</mediaobject>
@ -186,7 +187,7 @@
<mediaobject>
<imageobject>
<imagedata fileref="virtualization/parallels-freebsd11">
<imagedata fileref="virtualization/parallels-freebsd11"/>
</imageobject>
</mediaobject>
@ -199,19 +200,19 @@
<mediaobject>
<imageobject>
<imagedata fileref="virtualization/parallels-freebsd10">
<imagedata fileref="virtualization/parallels-freebsd10"/>
</imageobject>
</mediaobject>
<para>In this case it will find the &os; installation media
and begin a normal <application>sysinstall</application>
based installation as described in <xref
linkend="install">. You may install, but do not attempt
linkend="install"/>. You may install, but do not attempt
to configure X11 at this time.</para>
<mediaobject>
<imageobject>
<imagedata fileref="virtualization/parallels-freebsd12">
<imagedata fileref="virtualization/parallels-freebsd12"/>
</imageobject>
</mediaobject>
@ -220,7 +221,7 @@
<mediaobject>
<imageobject>
<imagedata fileref="virtualization/parallels-freebsd13">
<imagedata fileref="virtualization/parallels-freebsd13"/>
</imageobject>
</mediaobject>
</sect3>
@ -275,7 +276,7 @@
<literal>ifconfig_ed0="DHCP"</literal> to
<filename>/etc/rc.conf</filename>. More advanced
networking setups are described in
<xref linkend="advanced-networking">.</para>
<xref linkend="advanced-networking"/>.</para>
</step>
</procedure>
</sect3>
@ -614,13 +615,13 @@ xenbr1 8000.feffffffffff no vif0.1
<mediaobject>
<imageobject>
<imagedata fileref="virtualization/virtualpc-freebsd1">
<imagedata fileref="virtualization/virtualpc-freebsd1"/>
</imageobject>
</mediaobject>
<mediaobject>
<imageobject>
<imagedata fileref="virtualization/virtualpc-freebsd2">
<imagedata fileref="virtualization/virtualpc-freebsd2"/>
</imageobject>
</mediaobject>
@ -630,7 +631,7 @@ xenbr1 8000.feffffffffff no vif0.1
<mediaobject>
<imageobject>
<imagedata fileref="virtualization/virtualpc-freebsd3">
<imagedata fileref="virtualization/virtualpc-freebsd3"/>
</imageobject>
</mediaobject>
@ -642,13 +643,13 @@ xenbr1 8000.feffffffffff no vif0.1
<mediaobject>
<imageobject>
<imagedata fileref="virtualization/virtualpc-freebsd4">
<imagedata fileref="virtualization/virtualpc-freebsd4"/>
</imageobject>
</mediaobject>
<mediaobject>
<imageobject>
<imagedata fileref="virtualization/virtualpc-freebsd5">
<imagedata fileref="virtualization/virtualpc-freebsd5"/>
</imageobject>
</mediaobject>
@ -656,7 +657,7 @@ xenbr1 8000.feffffffffff no vif0.1
<mediaobject>
<imageobject>
<imagedata fileref="virtualization/virtualpc-freebsd6">
<imagedata fileref="virtualization/virtualpc-freebsd6"/>
</imageobject>
</mediaobject>
@ -666,13 +667,13 @@ xenbr1 8000.feffffffffff no vif0.1
<mediaobject>
<imageobject>
<imagedata fileref="virtualization/virtualpc-freebsd7">
<imagedata fileref="virtualization/virtualpc-freebsd7"/>
</imageobject>
</mediaobject>
<mediaobject>
<imageobject>
<imagedata fileref="virtualization/virtualpc-freebsd8">
<imagedata fileref="virtualization/virtualpc-freebsd8"/>
</imageobject>
</mediaobject>
@ -691,13 +692,13 @@ xenbr1 8000.feffffffffff no vif0.1
<mediaobject>
<imageobject>
<imagedata fileref="virtualization/virtualpc-freebsd9">
<imagedata fileref="virtualization/virtualpc-freebsd9"/>
</imageobject>
</mediaobject>
<mediaobject>
<imageobject>
<imagedata fileref="virtualization/virtualpc-freebsd10">
<imagedata fileref="virtualization/virtualpc-freebsd10"/>
</imageobject>
</mediaobject>
@ -711,19 +712,19 @@ xenbr1 8000.feffffffffff no vif0.1
<mediaobject>
<imageobject>
<imagedata fileref="virtualization/virtualpc-freebsd11">
<imagedata fileref="virtualization/virtualpc-freebsd11"/>
</imageobject>
</mediaobject>
<para>In this case it will find the &os; installation media
and begin a normal <application>sysinstall</application>
based installation as described in <xref linkend="install">.
based installation as described in <xref linkend="install"/>.
You may install, but do not attempt to configure X11 at this
time.</para>
<mediaobject>
<imageobject>
<imagedata fileref="virtualization/virtualpc-freebsd12">
<imagedata fileref="virtualization/virtualpc-freebsd12"/>
</imageobject>
</mediaobject>
@ -733,7 +734,7 @@ xenbr1 8000.feffffffffff no vif0.1
<mediaobject>
<imageobject>
<imagedata fileref="virtualization/virtualpc-freebsd13">
<imagedata fileref="virtualization/virtualpc-freebsd13"/>
</imageobject>
</mediaobject>
</sect3>
@ -789,7 +790,7 @@ xenbr1 8000.feffffffffff no vif0.1
<literal>ifconfig_de0="DHCP"</literal> to
<filename>/etc/rc.conf</filename>. More advanced
networking setups are described in
<xref linkend="advanced-networking">.</para>
<xref linkend="advanced-networking"/>.</para>
</step>
</procedure>
</sect3>
@ -816,7 +817,7 @@ xenbr1 8000.feffffffffff no vif0.1
<mediaobject>
<imageobject>
<imagedata fileref="virtualization/vmware-freebsd01">
<imagedata fileref="virtualization/vmware-freebsd01"/>
</imageobject>
</mediaobject>
@ -825,7 +826,7 @@ xenbr1 8000.feffffffffff no vif0.1
<mediaobject>
<imageobject>
<imagedata fileref="virtualization/vmware-freebsd02">
<imagedata fileref="virtualization/vmware-freebsd02"/>
</imageobject>
</mediaobject>
@ -838,7 +839,7 @@ xenbr1 8000.feffffffffff no vif0.1
<mediaobject>
<imageobject>
<imagedata fileref="virtualization/vmware-freebsd03">
<imagedata fileref="virtualization/vmware-freebsd03"/>
</imageobject>
</mediaobject>
@ -847,7 +848,7 @@ xenbr1 8000.feffffffffff no vif0.1
<mediaobject>
<imageobject>
<imagedata fileref="virtualization/vmware-freebsd04">
<imagedata fileref="virtualization/vmware-freebsd04"/>
</imageobject>
</mediaobject>
@ -856,7 +857,7 @@ xenbr1 8000.feffffffffff no vif0.1
<mediaobject>
<imageobject>
<imagedata fileref="virtualization/vmware-freebsd05">
<imagedata fileref="virtualization/vmware-freebsd05"/>
</imageobject>
</mediaobject>
@ -865,7 +866,7 @@ xenbr1 8000.feffffffffff no vif0.1
<mediaobject>
<imageobject>
<imagedata fileref="virtualization/vmware-freebsd06">
<imagedata fileref="virtualization/vmware-freebsd06"/>
</imageobject>
</mediaobject>
@ -873,16 +874,16 @@ xenbr1 8000.feffffffffff no vif0.1
<mediaobject>
<imageobject>
<imagedata fileref="virtualization/vmware-freebsd07">
<imagedata fileref="virtualization/vmware-freebsd07"/>
</imageobject>
</mediaobject>
<para>Install &os; like you normally would, or by following
the directions in <xref linkend="install">:</para>
the directions in <xref linkend="install"/>:</para>
<mediaobject>
<imageobject>
<imagedata fileref="virtualization/vmware-freebsd08">
<imagedata fileref="virtualization/vmware-freebsd08"/>
</imageobject>
</mediaobject>
@ -896,7 +897,7 @@ xenbr1 8000.feffffffffff no vif0.1
<mediaobject>
<imageobject>
<imagedata fileref="virtualization/vmware-freebsd09">
<imagedata fileref="virtualization/vmware-freebsd09"/>
</imageobject>
</mediaobject>
@ -904,7 +905,7 @@ xenbr1 8000.feffffffffff no vif0.1
<mediaobject>
<imageobject>
<imagedata fileref="virtualization/vmware-freebsd10">
<imagedata fileref="virtualization/vmware-freebsd10"/>
</imageobject>
</mediaobject>
@ -914,7 +915,7 @@ xenbr1 8000.feffffffffff no vif0.1
<mediaobject>
<imageobject>
<imagedata fileref="virtualization/vmware-freebsd11">
<imagedata fileref="virtualization/vmware-freebsd11"/>
</imageobject>
</mediaobject>
@ -929,7 +930,7 @@ xenbr1 8000.feffffffffff no vif0.1
<mediaobject>
<imageobject>
<imagedata fileref="virtualization/vmware-freebsd12">
<imagedata fileref="virtualization/vmware-freebsd12"/>
</imageobject>
</mediaobject>
@ -985,7 +986,7 @@ xenbr1 8000.feffffffffff no vif0.1
<literal>ifconfig_em0="DHCP"</literal> to
<filename>/etc/rc.conf</filename>. More advanced
networking setups are described in
<xref linkend="advanced-networking">.</para>
<xref linkend="advanced-networking"/>.</para>
</step>
</procedure>
</sect3>

13
en_US.ISO8859-1/books/handbook/x11/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!--
The FreeBSD Documentation Project
@ -71,7 +72,7 @@
<itemizedlist>
<listitem>
<para>Know how to install additional third-party
software (<xref linkend="ports">).</para>
software (<xref linkend="ports"/>).</para>
</listitem>
</itemizedlist>
</sect1>
@ -300,7 +301,7 @@
implementation for &os;. <application>&xorg;</application> is
the X server of the open source X Window System implementation released by the X.Org
Foundation. <application>&xorg;</application> is based on the code of
<application>&xfree86&nbsp;4.4RC2</application> and X11R6.6.
<application>&xfree86;&nbsp;4.4RC2</application> and X11R6.6.
The version of <application>&xorg;</application> currently
available in the &os; Ports Collection is &xorg.version;.</para>
@ -518,7 +519,7 @@ dbus_enable="YES"</programlisting>
</note>
<para>If the mouse does not work, you will need to first
configure it before proceeding. See <xref linkend="mouse">
configure it before proceeding. See <xref linkend="mouse"/>
in the &os; install chapter. In recent
<application>Xorg</application> versions,
the <literal>InputDevice</literal> sections in
@ -1110,7 +1111,7 @@ EndSection</programlisting>
<para>Think of <application>XDM</application> as
providing the same functionality to the user as the
&man.getty.8; utility (see <xref linkend="term-config"> for
&man.getty.8; utility (see <xref linkend="term-config"/> for
details). That is, it performs system logins to the display
being connected to and then runs a session manager on behalf of
the user (usually an X window
@ -1136,7 +1137,7 @@ EndSection</programlisting>
time the machine boots up, a convenient way to do this is by
adding an entry to <filename>/etc/ttys</filename>. For more
information about the format and usage of this file, see <xref
linkend="term-etcttys">. There is a line in the default
linkend="term-etcttys"/>. There is a line in the default
<filename>/etc/ttys</filename> file for running the
<application>XDM</application> daemon on a virtual terminal:</para>
@ -1145,7 +1146,7 @@ EndSection</programlisting>
<para>By default this entry is disabled; in order to enable it
change field 5 from <literal>off</literal> to
<literal>on</literal> and restart &man.init.8; using the
directions in <xref linkend="term-hup">. The first field, the
directions in <xref linkend="term-hup"/>. The first field, the
name of the terminal this program will manage, is
<literal>ttyv8</literal>. This means that
<application>XDM</application> will start running on the 9th

1
en_US.ISO8859-1/books/pmake/answers/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!--
$FreeBSD$
-->

23
en_US.ISO8859-1/books/pmake/basics/chapter.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!--
$FreeBSD$
-->
@ -116,7 +117,7 @@
it will be re-created. This operator also does
something else to the targets, but I will go into that
in the next section
(see <xref linkend="shellcmds">).</entry>
(see <xref linkend="shellcmds"/>).</entry>
</row>
</tbody>
</tgroup>
@ -356,13 +357,13 @@ Linking index</screen>
input, something they probably will not find to their liking.
A simple way around this is to give a command like this:</para>
<screen><command>ci $(SRCS) < <devicename>/dev/tty</devicename></command></screen>
<screen><command>ci $(SRCS) &lt; <devicename>/dev/tty</devicename></command></screen>
<para>This would force the program's input to come from the
terminal. If you cannot do this for some reason, your only
other alternative is to use <application>PMake</application> in
its fullest compatibility mode.
See <quote>Compatibility</quote> in <xref linkend="gods">.</para>
See <quote>Compatibility</quote> in <xref linkend="gods"/>.</para>
</section>
@ -648,7 +649,7 @@ Linking index</screen>
<para>Two other variables, <makevar>.INCLUDES</makevar> and
<makevar>.LIBS,</makevar> are covered in the section on
special targets in <xref linkend="shortcuts">.</para>
special targets in <xref linkend="shortcuts"/>.</para>
<para>Global variables may be deleted using lines of the
form:</para>
@ -754,7 +755,7 @@ c.o : c.c
because of its sequential, depth-first way of examining them.
While I do not want to go into depth on how
<application>PMake</application> works (look in <xref
linkend="gods"> if you are interested), I will warn you that
linkend="gods"/> if you are interested), I will warn you that
files in two different levels of the dependency tree may be
examined in a different order in
<application>PMake</application> than they were in
@ -865,7 +866,7 @@ output.o : output.c
program you want it to without unnecessary compilations or
excessive typing on your part. There are two things wrong with
it, however (aside from it being altogether too long, something
I will address in <xref linkend="shortcuts">):</para>
I will address in <xref linkend="shortcuts"/>):</para>
<orderedlist>
<listitem>
@ -912,7 +913,7 @@ output.o : output.c
$(OBJS) : defs.h</programlisting>
<para>Alternatively, if you like the idea of dynamic sources
mentioned in <xref linkend="localvariables">, you could write it
mentioned in <xref linkend="localvariables"/>, you could write it
like this:</para>
<programlisting>OBJS = main.o parse.o output.o
@ -1065,7 +1066,7 @@ d : a</programlisting>
<entry><literal>s</literal></entry>
<entry>The application of suffix-transformation
rules. (See <xref linkend="shortcuts">.)</entry>
rules. (See <xref linkend="shortcuts"/>.)</entry>
</row>
<row valign="top">
@ -1228,7 +1229,7 @@ d : a</programlisting>
<para>When <application>PMake</application> starts up, it reads a
default makefile that tells it what sort of system it is on and
gives it some idea of what to do if you do not tell it anything.
I will tell you about it in <xref linkend="shortcuts">.
I will tell you about it in <xref linkend="shortcuts"/>.
If you give this flag, <application>PMake</application> will not
read the default makefile.</para>
</listitem>
@ -1339,7 +1340,7 @@ d : a</programlisting>
its value. The variable is a global variable, not a command-line
variable. This is useful mostly for people who are used to the C
compiler arguments and those using conditionals, which I will get
into in <xref linkend="condition">.</para>
into in <xref linkend="condition"/>.</para>
</listitem>
</varlistentry>
@ -1349,7 +1350,7 @@ d : a</programlisting>
<listitem>
<para>Tells <application>PMake</application> another place to search
for included makefiles. Yet another thing to be explained in
<xref linkend="shortcuts"> (<xref linkend="including">, to be
<xref linkend="shortcuts"/> (<xref linkend="including"/>, to be
precise).</para>
</listitem>
</varlistentry>

14
en_US.ISO8859-1/books/pmake/book.sgml
View file

@ -1,11 +1,13 @@
<!DOCTYPE BOOK PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
<!ENTITY % books.ent PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Books Entity Set//EN">
%books.ent;
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!DOCTYPE book PUBLIC "-//FreeBSD//DTD DocBook XML V4.2-Based Extension//EN"
"../../../share/sgml/freebsd42.dtd" [
<!ENTITY % entities PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Entity Set//EN" "../../share/sgml/entities.ent">
%entities;
<!ENTITY % chapters.ent SYSTEM "chapters.ent">
%chapters.ent;
]>
<book>
<book lang='en'>
<bookinfo>
<title>PMake &mdash; A Tutorial</title>
@ -14,9 +16,9 @@
<surname>de Boor</surname>
</author>
<pubdate>$FreeBSD$</pubdate>
&legalnotice;
<releaseinfo>$FreeBSD$</releaseinfo>
</bookinfo>
&chap.intro;

1
en_US.ISO8859-1/books/pmake/chapters.ent
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="iso-8859-1"?>
<!--
Creates entities for each chapter in the PMake Tutorial.

1
en_US.ISO8859-1/books/pmake/glossary/glossary.sgml
View file

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="ISO8859-1" standalone="no"?>
<!--
$FreeBSD$
-->

Some files were not shown because too many files have changed in this diff Show more