aboutsummaryrefslogtreecommitdiff
path: root/en_US.ISO8859-1/books
diff options
context:
space:
mode:
Diffstat (limited to 'en_US.ISO8859-1/books')
-rw-r--r--en_US.ISO8859-1/books/arch-handbook/book.xml61
-rw-r--r--en_US.ISO8859-1/books/arch-handbook/boot/chapter.xml34
-rw-r--r--en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.xml31
-rw-r--r--en_US.ISO8859-1/books/arch-handbook/isa/chapter.xml63
-rw-r--r--en_US.ISO8859-1/books/arch-handbook/jail/chapter.xml25
-rw-r--r--en_US.ISO8859-1/books/arch-handbook/kobj/chapter.xml17
-rw-r--r--en_US.ISO8859-1/books/arch-handbook/locking/chapter.xml89
-rw-r--r--en_US.ISO8859-1/books/arch-handbook/mac/chapter.xml432
-rw-r--r--en_US.ISO8859-1/books/arch-handbook/newbus/chapter.xml39
-rw-r--r--en_US.ISO8859-1/books/arch-handbook/pccard/chapter.xml19
-rw-r--r--en_US.ISO8859-1/books/arch-handbook/pci/chapter.xml15
-rw-r--r--en_US.ISO8859-1/books/arch-handbook/scsi/chapter.xml55
-rw-r--r--en_US.ISO8859-1/books/arch-handbook/smp/chapter.xml119
-rw-r--r--en_US.ISO8859-1/books/arch-handbook/sound/chapter.xml134
-rw-r--r--en_US.ISO8859-1/books/arch-handbook/sysinit/chapter.xml9
-rw-r--r--en_US.ISO8859-1/books/arch-handbook/usb/chapter.xml54
-rw-r--r--en_US.ISO8859-1/books/arch-handbook/vm/chapter.xml31
-rw-r--r--en_US.ISO8859-1/books/design-44bsd/book.xml422
-rw-r--r--en_US.ISO8859-1/books/dev-model/book.xml340
-rw-r--r--en_US.ISO8859-1/books/developers-handbook/book.xml129
-rw-r--r--en_US.ISO8859-1/books/developers-handbook/introduction/chapter.xml121
-rw-r--r--en_US.ISO8859-1/books/developers-handbook/ipv6/chapter.xml72
-rw-r--r--en_US.ISO8859-1/books/developers-handbook/kernelbuild/chapter.xml23
-rw-r--r--en_US.ISO8859-1/books/developers-handbook/kerneldebug/chapter.xml62
-rw-r--r--en_US.ISO8859-1/books/developers-handbook/l10n/chapter.xml51
-rw-r--r--en_US.ISO8859-1/books/developers-handbook/policies/chapter.xml190
-rw-r--r--en_US.ISO8859-1/books/developers-handbook/secure/chapter.xml35
-rw-r--r--en_US.ISO8859-1/books/developers-handbook/sockets/chapter.xml83
-rw-r--r--en_US.ISO8859-1/books/developers-handbook/testing/chapter.xml37
-rw-r--r--en_US.ISO8859-1/books/developers-handbook/tools/chapter.xml127
-rw-r--r--en_US.ISO8859-1/books/developers-handbook/x86/chapter.xml195
-rw-r--r--en_US.ISO8859-1/books/faq/book.xml1587
-rw-r--r--en_US.ISO8859-1/books/fdp-primer/book.xml32
-rw-r--r--en_US.ISO8859-1/books/fdp-primer/doc-build/chapter.xml114
-rw-r--r--en_US.ISO8859-1/books/fdp-primer/docbook-markup/chapter.xml1316
-rw-r--r--en_US.ISO8859-1/books/fdp-primer/editor-config/chapter.xml29
-rw-r--r--en_US.ISO8859-1/books/fdp-primer/examples/appendix.xml174
-rw-r--r--en_US.ISO8859-1/books/fdp-primer/overview/chapter.xml30
-rw-r--r--en_US.ISO8859-1/books/fdp-primer/psgml-mode/chapter.xml7
-rw-r--r--en_US.ISO8859-1/books/fdp-primer/see-also/chapter.xml49
-rw-r--r--en_US.ISO8859-1/books/fdp-primer/sgml-markup/chapter.xml669
-rw-r--r--en_US.ISO8859-1/books/fdp-primer/sgml-primer/chapter.xml115
-rw-r--r--en_US.ISO8859-1/books/fdp-primer/structure/chapter.xml80
-rw-r--r--en_US.ISO8859-1/books/fdp-primer/stylesheets/chapter.xml5
-rw-r--r--en_US.ISO8859-1/books/fdp-primer/the-website/chapter.xml68
-rw-r--r--en_US.ISO8859-1/books/fdp-primer/tools/chapter.xml35
-rw-r--r--en_US.ISO8859-1/books/fdp-primer/translations/chapter.xml35
-rw-r--r--en_US.ISO8859-1/books/fdp-primer/working-copy/chapter.xml63
-rw-r--r--en_US.ISO8859-1/books/fdp-primer/writing-style/chapter.xml126
-rw-r--r--en_US.ISO8859-1/books/fdp-primer/xhtml-markup/chapter.xml352
-rw-r--r--en_US.ISO8859-1/books/fdp-primer/xml-primer/chapter.xml258
-rw-r--r--en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml974
-rw-r--r--en_US.ISO8859-1/books/handbook/audit/chapter.xml73
-rw-r--r--en_US.ISO8859-1/books/handbook/basics/chapter.xml469
-rw-r--r--en_US.ISO8859-1/books/handbook/bibliography/chapter.xml212
-rw-r--r--en_US.ISO8859-1/books/handbook/book.xml41
-rw-r--r--en_US.ISO8859-1/books/handbook/boot/chapter.xml152
-rw-r--r--en_US.ISO8859-1/books/handbook/bsdinstall/chapter.xml587
-rw-r--r--en_US.ISO8859-1/books/handbook/colophon.xml3
-rw-r--r--en_US.ISO8859-1/books/handbook/config/chapter.xml493
-rw-r--r--en_US.ISO8859-1/books/handbook/cutting-edge/chapter.xml640
-rw-r--r--en_US.ISO8859-1/books/handbook/desktop/chapter.xml165
-rw-r--r--en_US.ISO8859-1/books/handbook/disks/chapter.xml691
-rw-r--r--en_US.ISO8859-1/books/handbook/dtrace/chapter.xml55
-rw-r--r--en_US.ISO8859-1/books/handbook/eresources/chapter.xml136
-rw-r--r--en_US.ISO8859-1/books/handbook/filesystems/chapter.xml90
-rw-r--r--en_US.ISO8859-1/books/handbook/firewalls/chapter.xml280
-rw-r--r--en_US.ISO8859-1/books/handbook/geom/chapter.xml366
-rw-r--r--en_US.ISO8859-1/books/handbook/install/chapter.xml576
-rw-r--r--en_US.ISO8859-1/books/handbook/introduction/chapter.xml252
-rw-r--r--en_US.ISO8859-1/books/handbook/jails/chapter.xml155
-rw-r--r--en_US.ISO8859-1/books/handbook/kernelconfig/chapter.xml143
-rw-r--r--en_US.ISO8859-1/books/handbook/l10n/chapter.xml139
-rw-r--r--en_US.ISO8859-1/books/handbook/linuxemu/chapter.xml65
-rw-r--r--en_US.ISO8859-1/books/handbook/mac/chapter.xml137
-rw-r--r--en_US.ISO8859-1/books/handbook/mail/chapter.xml435
-rw-r--r--en_US.ISO8859-1/books/handbook/mirrors/chapter.xml243
-rw-r--r--en_US.ISO8859-1/books/handbook/multimedia/chapter.xml287
-rw-r--r--en_US.ISO8859-1/books/handbook/network-servers/chapter.xml634
-rw-r--r--en_US.ISO8859-1/books/handbook/pgpkeys/chapter.xml14
-rw-r--r--en_US.ISO8859-1/books/handbook/ports/chapter.xml341
-rw-r--r--en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.xml170
-rw-r--r--en_US.ISO8859-1/books/handbook/preface/preface.xml63
-rw-r--r--en_US.ISO8859-1/books/handbook/printing/chapter.xml772
-rw-r--r--en_US.ISO8859-1/books/handbook/security/chapter.xml607
-rw-r--r--en_US.ISO8859-1/books/handbook/serialcomms/chapter.xml262
-rw-r--r--en_US.ISO8859-1/books/handbook/users/chapter.xml127
-rw-r--r--en_US.ISO8859-1/books/handbook/vinum/chapter.xml327
-rw-r--r--en_US.ISO8859-1/books/handbook/virtualization/chapter.xml105
-rw-r--r--en_US.ISO8859-1/books/handbook/x11/chapter.xml115
-rw-r--r--en_US.ISO8859-1/books/pmake/answers/chapter.xml3
-rw-r--r--en_US.ISO8859-1/books/pmake/basics/chapter.xml108
-rw-r--r--en_US.ISO8859-1/books/pmake/book.xml18
-rw-r--r--en_US.ISO8859-1/books/pmake/glossary/glossary.xml17
-rw-r--r--en_US.ISO8859-1/books/pmake/gods/chapter.xml77
-rw-r--r--en_US.ISO8859-1/books/pmake/intro/chapter.xml3
-rw-r--r--en_US.ISO8859-1/books/pmake/legalnotice.xml3
-rw-r--r--en_US.ISO8859-1/books/pmake/shortcuts/chapter.xml130
-rw-r--r--en_US.ISO8859-1/books/porters-handbook/book.xml3642
99 files changed, 10531 insertions, 13124 deletions
diff --git a/en_US.ISO8859-1/books/arch-handbook/book.xml b/en_US.ISO8859-1/books/arch-handbook/book.xml
index 61509a2072..2853744df8 100644
--- a/en_US.ISO8859-1/books/arch-handbook/book.xml
+++ b/en_US.ISO8859-1/books/arch-handbook/book.xml
@@ -1,23 +1,21 @@
<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE book PUBLIC "-//FreeBSD//DTD DocBook XML V4.5-Based Extension//EN"
- "../../../share/xml/freebsd45.dtd" [
+<!DOCTYPE book PUBLIC "-//FreeBSD//DTD DocBook XML V5.0-Based Extension//EN"
+ "../../../share/xml/freebsd50.dtd" [
<!ENTITY % chapters SYSTEM "chapters.ent">
%chapters;
<!ENTITY % mac-entities SYSTEM "mac.ent">
%mac-entities;
]>
-
<!--
The FreeBSD Documentation Project
$FreeBSD$
-->
+<book xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:lang="en">
+ <info><title>&os; Architecture Handbook</title>
+
-<book lang='en'>
- <bookinfo>
- <title>&os; Architecture Handbook</title>
-
- <corpauthor>The FreeBSD Documentation Project</corpauthor>
+ <author><orgname>The FreeBSD Documentation Project</orgname></author>
<pubdate>$FreeBSD$</pubdate>
@@ -34,7 +32,7 @@
<holder>The FreeBSD Documentation Project</holder>
</copyright>
- <legalnotice id="trademarks" role="trademarks">
+ <legalnotice xml:id="trademarks" role="trademarks">
&tm-attrib.freebsd;
&tm-attrib.unix;
&tm-attrib.apple;
@@ -55,16 +53,14 @@
helping with this project, send email to the &a.doc;.</para>
<para>The latest version of this document is always available
- from the <ulink url="&url.base;/index.html">FreeBSD World
- Wide Web server</ulink>. It may also be downloaded in a
- variety of formats and compression options from the <ulink
- url="ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/">FreeBSD FTP server</ulink>
- or one of the numerous <ulink
- url="&url.books.handbook;/mirrors-ftp.html">mirror sites</ulink>.</para>
+ from the <link xlink:href="&url.base;/index.html">FreeBSD World
+ Wide Web server</link>. It may also be downloaded in a
+ variety of formats and compression options from the <link xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/">FreeBSD FTP server</link>
+ or one of the numerous <link xlink:href="&url.books.handbook;/mirrors-ftp.html">mirror sites</link>.</para>
</abstract>
- </bookinfo>
+ </info>
- <part id="kernel">
+ <part xml:id="kernel">
<title>Kernel</title>
&chap.boot;
@@ -78,7 +74,7 @@
</part>
- <part id="devicedrivers">
+ <part xml:id="devicedrivers">
<title>Device Drivers</title>
&chap.driverbasics;
@@ -135,32 +131,17 @@
</part>
-->
- <part id="appendices">
+ <part xml:id="appendices">
<title>Appendices</title>
<bibliography>
<biblioentry xreflabel="1">
<authorgroup>
- <author>
- <firstname>Marshall</firstname>
- <othername role="Middle">Kirk</othername>
- <surname>McKusick</surname>
- </author>
- <author>
- <firstname>Keith</firstname>
- <surname>Bostic</surname>
- </author>
- <author>
- <firstname>Michael</firstname>
- <othername role="MI">J</othername>
- <surname>Karels</surname>
- </author>
- <author>
- <firstname>John</firstname>
- <othername role="MI">S</othername>
- <surname>Quarterman</surname>
- </author>
+ <author><personname><firstname>Marshall</firstname><othername role="Middle">Kirk</othername><surname>McKusick</surname></personname></author>
+ <author><personname><firstname>Keith</firstname><surname>Bostic</surname></personname></author>
+ <author><personname><firstname>Michael</firstname><othername role="MI">J</othername><surname>Karels</surname></personname></author>
+ <author><personname><firstname>John</firstname><othername role="MI">S</othername><surname>Quarterman</surname></personname></author>
</authorgroup>
<copyright>
@@ -168,13 +149,13 @@
<holder>Addison-Wesley Publishing Company, Inc.</holder>
</copyright>
- <isbn>0-201-54979-4</isbn>
+ <biblioid class="isbn">0-201-54979-4</biblioid>
<publisher>
<publishername>Addison-Wesley Publishing Company, Inc.</publishername>
</publisher>
- <title>The Design and Implementation of the 4.4 BSD Operating System</title>
+ <citetitle>The Design and Implementation of the 4.4 BSD Operating System</citetitle>
<pagenums>1-2</pagenums>
</biblioentry>
diff --git a/en_US.ISO8859-1/books/arch-handbook/boot/chapter.xml b/en_US.ISO8859-1/books/arch-handbook/boot/chapter.xml
index 40b71de09c..2aff82083e 100644
--- a/en_US.ISO8859-1/books/arch-handbook/boot/chapter.xml
+++ b/en_US.ISO8859-1/books/arch-handbook/boot/chapter.xml
@@ -6,20 +6,15 @@ Copyright (c) 2002 Sergey Lyubka <devnull@uptsoft.com>
All rights reserved
$FreeBSD$
-->
-
-<chapter id="boot">
- <chapterinfo>
+<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:id="boot">
+ <info><title>Bootstrapping and Kernel Initialization</title>
<authorgroup>
- <author>
- <firstname>Sergey</firstname>
- <surname>Lyubka</surname>
- <contrib>Contributed by </contrib>
- </author> <!-- devnull@uptsoft.com 12 Jun 2002 -->
+ <author><personname><firstname>Sergey</firstname><surname>Lyubka</surname></personname><contrib>Contributed by </contrib></author> <!-- devnull@uptsoft.com 12 Jun 2002 -->
</authorgroup>
- </chapterinfo>
- <title>Bootstrapping and Kernel Initialization</title>
+ </info>
+
- <sect1 id="boot-synopsis">
+ <sect1 xml:id="boot-synopsis">
<title>Synopsis</title>
<indexterm><primary>BIOS</primary></indexterm>
@@ -35,7 +30,7 @@ $FreeBSD$
architecture is used as an example.</para>
</sect1>
- <sect1 id="boot-overview">
+ <sect1 xml:id="boot-overview">
<title>Overview</title>
<para>A computer running FreeBSD can boot by several methods,
@@ -117,7 +112,7 @@ Timecounter "i8254" frequency 1193182 Hz</screen></para></entry>
</informaltable>
</sect1>
- <sect1 id="boot-bios">
+ <sect1 xml:id="boot-bios">
<title>BIOS POST</title>
<para>When the PC powers on, the processor's registers are set
@@ -173,7 +168,7 @@ Timecounter "i8254" frequency 1193182 Hz</screen></para></entry>
sector.</para></footnote>.</para>
</sect1>
- <sect1 id="boot-boot0">
+ <sect1 xml:id="boot-boot0">
<title><literal>boot0</literal> Stage</title>
<indexterm><primary>MBR</primary></indexterm>
@@ -259,7 +254,7 @@ Timecounter "i8254" frequency 1193182 Hz</screen></para></entry>
<filename>boot2</filename>.</para>
</sect1>
- <sect1 id="boot-boot2">
+ <sect1 xml:id="boot-boot2">
<title><literal>boot2</literal> Stage</title>
<para>You might wonder, why <literal>boot2</literal> comes after
@@ -456,7 +451,7 @@ struct bootinfo {
0, 0, 0, VTOP(&amp;bootinfo));</programlisting>
</sect1>
- <sect1 id="boot-loader">
+ <sect1 xml:id="boot-loader">
<title><application>loader</application> Stage</title>
<para><application>loader</application> is a BTX client as well.
@@ -473,7 +468,7 @@ struct bootinfo {
module_formats[km-&gt;m_loader]-&gt;l_exec(km);</programlisting>
</sect1>
- <sect1 id="boot-kernel">
+ <sect1 xml:id="boot-kernel">
<title>Kernel Initialization</title>
<para>Let us take a look at the command that links the kernel.
@@ -840,9 +835,8 @@ struct gate_descriptor *idt = &amp;idt0[0]; /* interrupt descriptor table */
}</programlisting>
<para>Although the sysinit framework is described in the
- <ulink
- url="&url.doc.langbase;/books/developers-handbook">Developers'
- Handbook</ulink>, I will discuss the internals of it.</para>
+ <link xlink:href="&url.doc.langbase;/books/developers-handbook">Developers'
+ Handbook</link>, I will discuss the internals of it.</para>
<indexterm><primary>sysinit objects</primary></indexterm>
<para>Every system initialization object (sysinit object) is
diff --git a/en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.xml b/en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.xml
index 2815b30aa8..9105d11730 100644
--- a/en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.xml
+++ b/en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.xml
@@ -4,27 +4,18 @@
$FreeBSD$
-->
-
-<chapter id="driverbasics">
- <chapterinfo>
+<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:id="driverbasics">
+ <info><title>Writing FreeBSD Device Drivers</title>
<authorgroup>
- <author>
- <firstname>Murray</firstname>
- <surname>Stokely</surname>
- <contrib>Written by </contrib>
- </author>
+ <author><personname><firstname>Murray</firstname><surname>Stokely</surname></personname><contrib>Written by </contrib></author>
</authorgroup>
<authorgroup>
- <author>
- <firstname>J&ouml;rg</firstname>
- <surname>Wunsch</surname>
- <contrib>Based on intro(4) manual page by </contrib>
- </author>
+ <author><personname><firstname>J&ouml;rg</firstname><surname>Wunsch</surname></personname><contrib>Based on intro(4) manual page by </contrib></author>
</authorgroup>
- </chapterinfo>
- <title>Writing FreeBSD Device Drivers</title>
+ </info>
+
- <sect1 id="driverbasics-intro">
+ <sect1 xml:id="driverbasics-intro">
<title>Introduction</title>
<indexterm><primary>device driver</primary></indexterm>
@@ -54,7 +45,7 @@
</sect1>
- <sect1 id="driverbasics-kld">
+ <sect1 xml:id="driverbasics-kld">
<title>Dynamic Kernel Linker Facility - KLD</title>
<indexterm><primary>kernel linking</primary><secondary>dynamic</secondary></indexterm>
@@ -154,7 +145,7 @@ KMOD=skeleton
</sect2>
</sect1>
- <sect1 id="driverbasics-char">
+ <sect1 xml:id="driverbasics-char">
<title>Character Devices</title>
<indexterm><primary>character devices</primary></indexterm>
@@ -349,7 +340,7 @@ Closing device "echo".</screen>
<para>Real hardware devices are described in the next chapter.</para>
</sect1>
- <sect1 id="driverbasics-block">
+ <sect1 xml:id="driverbasics-block">
<title>Block Devices (Are Gone)</title>
<indexterm><primary>block devices</primary></indexterm>
@@ -377,7 +368,7 @@ Closing device "echo".</screen>
infrastructure.</para>
</sect1>
- <sect1 id="driverbasics-net">
+ <sect1 xml:id="driverbasics-net">
<title>Network Drivers</title>
<indexterm><primary>network devices</primary></indexterm>
diff --git a/en_US.ISO8859-1/books/arch-handbook/isa/chapter.xml b/en_US.ISO8859-1/books/arch-handbook/isa/chapter.xml
index f413a0dbb1..97bd2822c5 100644
--- a/en_US.ISO8859-1/books/arch-handbook/isa/chapter.xml
+++ b/en_US.ISO8859-1/books/arch-handbook/isa/chapter.xml
@@ -4,36 +4,21 @@
$FreeBSD$
-->
-
-<chapter id="isa-driver">
- <chapterinfo>
+<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:id="isa-driver">
+ <info><title>ISA Device Drivers</title>
<authorgroup>
- <author>
- <firstname>Sergey</firstname>
- <surname>Babkin</surname>
- <contrib>Written by </contrib>
- </author>
+ <author><personname><firstname>Sergey</firstname><surname>Babkin</surname></personname><contrib>Written by </contrib></author>
</authorgroup>
<authorgroup>
- <author>
- <firstname>Murray</firstname>
- <surname>Stokely</surname>
- <contrib>Modifications for Handbook made by </contrib>
- </author>
- <author>
- <firstname>Valentino</firstname>
- <surname>Vaschetto</surname>
- </author>
- <author>
- <firstname>Wylie</firstname>
- <surname>Stilwell</surname>
- </author>
+ <author><personname><firstname>Murray</firstname><surname>Stokely</surname></personname><contrib>Modifications for Handbook made by </contrib></author>
+ <author><personname><firstname>Valentino</firstname><surname>Vaschetto</surname></personname></author>
+ <author><personname><firstname>Wylie</firstname><surname>Stilwell</surname></personname></author>
</authorgroup>
- </chapterinfo>
+ </info>
- <title>ISA Device Drivers</title>
+
- <sect1 id="isa-driver-synopsis">
+ <sect1 xml:id="isa-driver-synopsis">
<title>Synopsis</title>
<indexterm><primary>ISA</primary></indexterm>
@@ -48,7 +33,7 @@
<literal>ep</literal> and <literal>aha</literal> are good sources of information.</para>
</sect1>
- <sect1 id="isa-driver-basics">
+ <sect1 xml:id="isa-driver-basics">
<title>Basic Information</title>
<para>A typical ISA driver would need the following include
@@ -163,7 +148,7 @@
<indexterm><primary>softc</primary></indexterm>
- <para>Here struct <structname>xxx_softc</structname> is a
+ <para>Here struct <varname remap="structname">xxx_softc</varname> is a
device-specific structure that contains private driver data
and descriptors for the driver's resources. The bus code
automatically allocates one softc descriptor per device as
@@ -207,10 +192,10 @@
</sect1>
- <sect1 id="isa-driver-device-t">
- <title><structname>device_t</structname> Pointer</title>
+ <sect1 xml:id="isa-driver-device-t">
+ <title><varname remap="structname">device_t</varname> Pointer</title>
- <para><structname>device_t</structname> is the pointer type for
+ <para><varname remap="structname">device_t</varname> is the pointer type for
the device structure. Here we consider only the methods
interesting from the device driver writer's standpoint. The
methods to manipulate values in the device structure
@@ -257,7 +242,7 @@
<listitem><para><function>void
*device_get_softc(dev)</function> Get pointer to the device
- descriptor (struct <structname>xxx_softc</structname>)
+ descriptor (struct <varname remap="structname">xxx_softc</varname>)
associated with this device.</para></listitem>
<listitem><para><function>u_int32_t
@@ -276,7 +261,7 @@
</sect1>
- <sect1 id="isa-driver-config">
+ <sect1 xml:id="isa-driver-config">
<title>Configuration File and the Order of Identifying and Probing
During Auto-Configuration</title>
@@ -417,7 +402,7 @@
</sect1>
- <sect1 id="isa-driver-resources">
+ <sect1 xml:id="isa-driver-resources">
<title>Resources</title>
<indexterm><primary>resources</primary></indexterm>
@@ -730,7 +715,7 @@
</sect1>
- <sect1 id="isa-driver-busmem">
+ <sect1 xml:id="isa-driver-busmem">
<title>Bus Memory Mapping</title>
<para>In many cases data is exchanged between the driver and the
@@ -1510,7 +1495,7 @@
<!--_________________________________________________________________________-->
<!--~~~~~~~~~~~~~~~~~~~~END OF SECTION~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~-->
- <sect1 id="isa-driver-dma">
+ <sect1 xml:id="isa-driver-dma">
<title>DMA</title>
<!-- Section Marked up by Wylie -->
@@ -1747,7 +1732,7 @@
</itemizedlist>
</sect1>
- <sect1 id="isa-driver-probe">
+ <sect1 xml:id="isa-driver-probe">
<title>xxx_isa_probe</title>
<!-- Section marked up by Wylie -->
@@ -2177,7 +2162,7 @@
</sect1>
- <sect1 id="isa-driver-attach">
+ <sect1 xml:id="isa-driver-attach">
<title>xxx_isa_attach</title>
<!-- Section Marked up by Wylie -->
@@ -2385,7 +2370,7 @@
</sect1>
- <sect1 id="isa-driver-detach">
+ <sect1 xml:id="isa-driver-detach">
<title>xxx_isa_detach</title>
<para>
@@ -2448,7 +2433,7 @@
</para>
</sect1>
- <sect1 id="isa-driver-shutdown">
+ <sect1 xml:id="isa-driver-shutdown">
<title>xxx_isa_shutdown</title>
<para>
@@ -2468,7 +2453,7 @@
</para>
</sect1>
- <sect1 id="isa-driver-intr">
+ <sect1 xml:id="isa-driver-intr">
<title>xxx_intr</title>
<indexterm><primary>interrupt handler</primary></indexterm>
diff --git a/en_US.ISO8859-1/books/arch-handbook/jail/chapter.xml b/en_US.ISO8859-1/books/arch-handbook/jail/chapter.xml
index f6d6e404da..7269fdefbe 100644
--- a/en_US.ISO8859-1/books/arch-handbook/jail/chapter.xml
+++ b/en_US.ISO8859-1/books/arch-handbook/jail/chapter.xml
@@ -4,22 +4,17 @@
$FreeBSD$
-->
-
-<chapter id="jail">
- <chapterinfo>
- <author>
- <firstname>Evan</firstname>
- <surname>Sarmiento</surname>
- <affiliation>
+<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:id="jail">
+ <info><title>The Jail Subsystem</title>
+ <author><personname><firstname>Evan</firstname><surname>Sarmiento</surname></personname><affiliation>
<address><email>evms@cs.bu.edu</email></address>
- </affiliation>
- </author>
+ </affiliation></author>
<copyright>
<year>2001</year>
<holder role="mailto:evms@cs.bu.edu">Evan Sarmiento</holder>
</copyright>
- </chapterinfo>
- <title>The Jail Subsystem</title>
+ </info>
+
<indexterm><primary>security</primary></indexterm>
<indexterm><primary>Jail</primary></indexterm>
@@ -46,10 +41,9 @@
gains <literal>root</literal> within the <application>jail</application>,
it is only an annoyance, and not a devastation. This article mainly
focuses on the internals (source code) of <application>jail</application>.
- For information on how to set up a jail see the <ulink
- url="&url.books.handbook;/jails.html">handbook entry on jails</ulink>.</para>
+ For information on how to set up a jail see the <link xlink:href="&url.books.handbook;/jails.html">handbook entry on jails</link>.</para>
- <sect1 id="jail-arch">
+ <sect1 xml:id="jail-arch">
<title>Architecture</title>
<para>
@@ -422,7 +416,7 @@ td2-&gt;td_ucred = crhold(p2-&gt;p_ucred);</programlisting>
</sect2>
</sect1>
- <sect1 id="jail-restrictions">
+ <sect1 xml:id="jail-restrictions">
<title>Restrictions</title>
<para>Throughout the kernel there are access restrictions relating
@@ -751,4 +745,3 @@ prison_priv_check(struct ucred *cred, int priv)
</sect1>
</chapter>
-
diff --git a/en_US.ISO8859-1/books/arch-handbook/kobj/chapter.xml b/en_US.ISO8859-1/books/arch-handbook/kobj/chapter.xml
index f08b847166..e52d1603d4 100644
--- a/en_US.ISO8859-1/books/arch-handbook/kobj/chapter.xml
+++ b/en_US.ISO8859-1/books/arch-handbook/kobj/chapter.xml
@@ -4,8 +4,7 @@
$FreeBSD$
-->
-
-<chapter id="kernel-objects">
+<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:id="kernel-objects">
<title>Kernel Objects</title>
<indexterm><primary>Kernel Objects</primary></indexterm>
@@ -18,7 +17,7 @@
interface at run time and without breaking binary
compatibility.</para>
- <sect1 id="kernel-objects-term">
+ <sect1 xml:id="kernel-objects-term">
<title>Terminology</title>
<indexterm><primary>object</primary></indexterm>
@@ -54,7 +53,7 @@
</variablelist>
</sect1>
- <sect1 id="kernel-objects-operation">
+ <sect1 xml:id="kernel-objects-operation">
<title>Kobj Operation</title>
<para>Kobj works by generating descriptions of methods. Each
@@ -86,7 +85,7 @@
</sect1>
- <sect1 id="kernel-objects-using">
+ <sect1 xml:id="kernel-objects-using">
<title>Using Kobj</title>
<sect2>
@@ -118,8 +117,8 @@ KOBJMETHOD(NAME, FUNC)</programlisting>
<sect2>
<title>Headers</title>
- <programlisting>&lt;sys/param.h>
-&lt;sys/kobj.h></programlisting>
+ <programlisting>&lt;sys/param.h&gt;
+&lt;sys/kobj.h&gt;</programlisting>
</sect2>
<sect2>
@@ -147,7 +146,7 @@ KOBJMETHOD(NAME, FUNC)</programlisting>
<para>For example:</para>
- <programlisting>#include &lt;sys/foo.h></programlisting>
+ <programlisting>#include &lt;sys/foo.h&gt;</programlisting>
<para>The <literal>INTERFACE</literal> keyword is used to define
the interface name. This name is concatenated with each method
@@ -242,7 +241,7 @@ kobj_method_t foomethods[] = {
the state of the system at the time that the class is to be
initialized a statically allocated cache, <quote>ops
table</quote> have to be used. This can be accomplished by
- declaring a <structname>struct kobj_ops</structname> and using
+ declaring a <varname remap="structname">struct kobj_ops</varname> and using
<function>kobj_class_compile_static();</function> otherwise,
<function>kobj_class_compile()</function> should be used.</para>
</sect2>
diff --git a/en_US.ISO8859-1/books/arch-handbook/locking/chapter.xml b/en_US.ISO8859-1/books/arch-handbook/locking/chapter.xml
index 4486cfb648..47ec5236ba 100644
--- a/en_US.ISO8859-1/books/arch-handbook/locking/chapter.xml
+++ b/en_US.ISO8859-1/books/arch-handbook/locking/chapter.xml
@@ -5,8 +5,7 @@
$FreeBSD$
-->
-
-<chapter id="locking">
+<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:id="locking">
<title>Locking Notes</title>
<indexterm><primary>SMP Next Generation Project</primary></indexterm>
@@ -25,7 +24,7 @@
are protected simply by always using atomic operations to access
them.</para>
- <sect1 id="locking-mutexes">
+ <sect1 xml:id="locking-mutexes">
<title>Mutexes</title>
<para>A mutex is simply a lock used to guarantee mutual exclusion.
@@ -99,7 +98,7 @@
<para>A list of data structures or data structure members
that this entry protects. For data structure members, the
name will be in the form of
- <structname>structure name</structname>.<structfield>member name</structfield>.</para>
+ <varname remap="structname">structure name</varname>.<varname remap="structfield">member name</varname>.</para>
</listitem>
</varlistentry>
@@ -152,38 +151,38 @@
<varname>cnt.v_swtch</varname>,
<varname>cp_time</varname>,
<varname>curpriority</varname>,
- <structname>mtx</structname>.<structfield>mtx_blocked</structfield>,
- <structname>mtx</structname>.<structfield>mtx_contested</structfield>,
- <structname>proc</structname>.<structfield>p_procq</structfield>,
- <structname>proc</structname>.<structfield>p_slpq</structfield>,
- <structname>proc</structname>.<structfield>p_sflag</structfield>,
- <structname>proc</structname>.<structfield>p_stat</structfield>,
- <structname>proc</structname>.<structfield>p_estcpu</structfield>,
- <structname>proc</structname>.<structfield>p_cpticks</structfield>
- <structname>proc</structname>.<structfield>p_pctcpu</structfield>,
- <structname>proc</structname>.<structfield>p_wchan</structfield>,
- <structname>proc</structname>.<structfield>p_wmesg</structfield>,
- <structname>proc</structname>.<structfield>p_swtime</structfield>,
- <structname>proc</structname>.<structfield>p_slptime</structfield>,
- <structname>proc</structname>.<structfield>p_runtime</structfield>,
- <structname>proc</structname>.<structfield>p_uu</structfield>,
- <structname>proc</structname>.<structfield>p_su</structfield>,
- <structname>proc</structname>.<structfield>p_iu</structfield>,
- <structname>proc</structname>.<structfield>p_uticks</structfield>,
- <structname>proc</structname>.<structfield>p_sticks</structfield>,
- <structname>proc</structname>.<structfield>p_iticks</structfield>,
- <structname>proc</structname>.<structfield>p_oncpu</structfield>,
- <structname>proc</structname>.<structfield>p_lastcpu</structfield>,
- <structname>proc</structname>.<structfield>p_rqindex</structfield>,
- <structname>proc</structname>.<structfield>p_heldmtx</structfield>,
- <structname>proc</structname>.<structfield>p_blocked</structfield>,
- <structname>proc</structname>.<structfield>p_mtxname</structfield>,
- <structname>proc</structname>.<structfield>p_contested</structfield>,
- <structname>proc</structname>.<structfield>p_priority</structfield>,
- <structname>proc</structname>.<structfield>p_usrpri</structfield>,
- <structname>proc</structname>.<structfield>p_nativepri</structfield>,
- <structname>proc</structname>.<structfield>p_nice</structfield>,
- <structname>proc</structname>.<structfield>p_rtprio</structfield>,
+ <varname remap="structname">mtx</varname>.<varname remap="structfield">mtx_blocked</varname>,
+ <varname remap="structname">mtx</varname>.<varname remap="structfield">mtx_contested</varname>,
+ <varname remap="structname">proc</varname>.<varname remap="structfield">p_procq</varname>,
+ <varname remap="structname">proc</varname>.<varname remap="structfield">p_slpq</varname>,
+ <varname remap="structname">proc</varname>.<varname remap="structfield">p_sflag</varname>,
+ <varname remap="structname">proc</varname>.<varname remap="structfield">p_stat</varname>,
+ <varname remap="structname">proc</varname>.<varname remap="structfield">p_estcpu</varname>,
+ <varname remap="structname">proc</varname>.<varname remap="structfield">p_cpticks</varname>
+ <varname remap="structname">proc</varname>.<varname remap="structfield">p_pctcpu</varname>,
+ <varname remap="structname">proc</varname>.<varname remap="structfield">p_wchan</varname>,
+ <varname remap="structname">proc</varname>.<varname remap="structfield">p_wmesg</varname>,
+ <varname remap="structname">proc</varname>.<varname remap="structfield">p_swtime</varname>,
+ <varname remap="structname">proc</varname>.<varname remap="structfield">p_slptime</varname>,
+ <varname remap="structname">proc</varname>.<varname remap="structfield">p_runtime</varname>,
+ <varname remap="structname">proc</varname>.<varname remap="structfield">p_uu</varname>,
+ <varname remap="structname">proc</varname>.<varname remap="structfield">p_su</varname>,
+ <varname remap="structname">proc</varname>.<varname remap="structfield">p_iu</varname>,
+ <varname remap="structname">proc</varname>.<varname remap="structfield">p_uticks</varname>,
+ <varname remap="structname">proc</varname>.<varname remap="structfield">p_sticks</varname>,
+ <varname remap="structname">proc</varname>.<varname remap="structfield">p_iticks</varname>,
+ <varname remap="structname">proc</varname>.<varname remap="structfield">p_oncpu</varname>,
+ <varname remap="structname">proc</varname>.<varname remap="structfield">p_lastcpu</varname>,
+ <varname remap="structname">proc</varname>.<varname remap="structfield">p_rqindex</varname>,
+ <varname remap="structname">proc</varname>.<varname remap="structfield">p_heldmtx</varname>,
+ <varname remap="structname">proc</varname>.<varname remap="structfield">p_blocked</varname>,
+ <varname remap="structname">proc</varname>.<varname remap="structfield">p_mtxname</varname>,
+ <varname remap="structname">proc</varname>.<varname remap="structfield">p_contested</varname>,
+ <varname remap="structname">proc</varname>.<varname remap="structfield">p_priority</varname>,
+ <varname remap="structname">proc</varname>.<varname remap="structfield">p_usrpri</varname>,
+ <varname remap="structname">proc</varname>.<varname remap="structfield">p_nativepri</varname>,
+ <varname remap="structname">proc</varname>.<varname remap="structfield">p_nice</varname>,
+ <varname remap="structname">proc</varname>.<varname remap="structfield">p_rtprio</varname>,
<varname>pscnt</varname>,
<varname>slpque</varname>,
<varname>itqueuebits</varname>,
@@ -258,8 +257,8 @@
<varname>callfree</varname>,
<varname>callwheel</varname>,
<varname>nextsoftcheck</varname>,
- <structname>proc</structname>.<structfield>p_itcallout</structfield>,
- <structname>proc</structname>.<structfield>p_slpcallout</structfield>,
+ <varname remap="structname">proc</varname>.<varname remap="structfield">p_itcallout</varname>,
+ <varname remap="structname">proc</varname>.<varname remap="structfield">p_slpcallout</varname>,
<varname>softticks</varname>,
<varname>ticks</varname>
</entry>
@@ -271,7 +270,7 @@
</table>
</sect1>
- <sect1 id="locking-sx">
+ <sect1 xml:id="locking-sx">
<title>Shared Exclusive Locks</title>
<para>These locks provide basic reader-writer type functionality
@@ -301,16 +300,16 @@
<varname>allproc</varname>
<varname>zombproc</varname>
<varname>pidhashtbl</varname>
- <structname>proc</structname>.<structfield>p_list</structfield>
- <structname>proc</structname>.<structfield>p_hash</structfield>
+ <varname remap="structname">proc</varname>.<varname remap="structfield">p_list</varname>
+ <varname remap="structname">proc</varname>.<varname remap="structfield">p_hash</varname>
<varname>nextpid</varname>
</entry>
</row>
<row>
<entry><varname>proctree_lock</varname></entry>
<entry>
- <structname>proc</structname>.<structfield>p_children</structfield>
- <structname>proc</structname>.<structfield>p_sibling</structfield>
+ <varname remap="structname">proc</varname>.<varname remap="structfield">p_children</varname>
+ <varname remap="structname">proc</varname>.<varname remap="structfield">p_sibling</varname>
</entry>
</row>
</tbody>
@@ -318,7 +317,7 @@
</table>
</sect1>
- <sect1 id="locking-atomic">
+ <sect1 xml:id="locking-atomic">
<title>Atomically Protected Variables</title>
<indexterm><primary>atomically protected variables</primary></indexterm>
@@ -333,7 +332,7 @@
<itemizedlist>
<listitem>
- <para><structname>mtx</structname>.<structfield>mtx_lock</structfield></para>
+ <para><varname remap="structname">mtx</varname>.<varname remap="structfield">mtx_lock</varname></para>
</listitem>
</itemizedlist>
</sect1>
diff --git a/en_US.ISO8859-1/books/arch-handbook/mac/chapter.xml b/en_US.ISO8859-1/books/arch-handbook/mac/chapter.xml
index 923dd53eb6..215b9557de 100644
--- a/en_US.ISO8859-1/books/arch-handbook/mac/chapter.xml
+++ b/en_US.ISO8859-1/books/arch-handbook/mac/chapter.xml
@@ -32,35 +32,24 @@
$FreeBSD$
-->
-
-<chapter id="mac">
- <chapterinfo>
+<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:id="mac">
+ <info><title>The TrustedBSD MAC Framework</title>
<authorgroup>
- <author>
- <firstname>Chris</firstname>
- <surname>Costello</surname>
-
- <affiliation>
+ <author><personname><firstname>Chris</firstname><surname>Costello</surname></personname><affiliation>
<orgname>TrustedBSD Project</orgname>
<address><email>chris@FreeBSD.org</email></address>
- </affiliation>
- </author>
-
- <author>
- <firstname>Robert</firstname>
- <surname>Watson</surname>
+ </affiliation></author>
- <affiliation>
+ <author><personname><firstname>Robert</firstname><surname>Watson</surname></personname><affiliation>
<orgname>TrustedBSD Project</orgname>
<address><email>rwatson@FreeBSD.org</email></address>
- </affiliation>
- </author>
+ </affiliation></author>
</authorgroup>
- </chapterinfo>
+ </info>
- <title>The TrustedBSD MAC Framework</title>
+
- <sect1 id="mac-copyright">
+ <sect1 xml:id="mac-copyright">
<title>MAC Documentation Copyright</title>
<para>This documentation was developed for the FreeBSD Project by
@@ -110,7 +99,7 @@
</important>
</sect1>
- <sect1 id="mac-synopsis">
+ <sect1 xml:id="mac-synopsis">
<title>Synopsis</title>
<para>FreeBSD includes experimental support for several
@@ -129,7 +118,7 @@
</sect1>
- <sect1 id="mac-introduction">
+ <sect1 xml:id="mac-introduction">
<title>Introduction</title>
<para>The TrustedBSD MAC framework provides a mechanism to allow
@@ -148,7 +137,7 @@
access control extension of the kernel.</para>
</sect1>
- <sect1 id="mac-background">
+ <sect1 xml:id="mac-background">
<title>Policy Background</title>
<para>Mandatory Access Control (MAC), refers to a set of
@@ -180,7 +169,7 @@
flexibility in how they authorize protections.</para>
</sect1>
- <sect1 id="mac-framework-kernel-arch">
+ <sect1 xml:id="mac-framework-kernel-arch">
<title>MAC Framework Kernel Architecture</title>
<para>The TrustedBSD MAC Framework permits kernel modules to
@@ -191,7 +180,7 @@
some definition of useful) compose the results of the
policies.</para>
- <sect2 id="mac-framework-kernel-arch-elements">
+ <sect2 xml:id="mac-framework-kernel-arch-elements">
<title>Kernel Elements</title>
<para>The MAC Framework contains a number of kernel elements:</para>
@@ -221,7 +210,7 @@
</itemizedlist>
</sect2>
- <sect2 id="mac-framework-kernel-arch-management">
+ <sect2 xml:id="mac-framework-kernel-arch-management">
<title>Framework Management Interfaces</title>
<para>The TrustedBSD MAC Framework may be directly managed using
@@ -247,7 +236,7 @@
events, including preventing undesired unloading of the policy.</para>
</sect2>
- <sect2 id="mac-framework-kernel-arch-synchronization">
+ <sect2 xml:id="mac-framework-kernel-arch-synchronization">
<title>Policy List Concurrency and Synchronization</title>
<para>As the set of active policies may change at run-time,
@@ -286,7 +275,7 @@
framework to become idle.</para>
</sect2>
- <sect2 id="mac-framework-kernel-arch-label-synchronization">
+ <sect2 xml:id="mac-framework-kernel-arch-label-synchronization">
<title>Label Synchronization</title>
<para>As kernel objects of interest may generally be accessed from
@@ -311,7 +300,7 @@
the label state attached to the credential.</para>
</sect2>
- <sect2 id="mac-framework-kernel-arch-policy-synchronization">
+ <sect2 xml:id="mac-framework-kernel-arch-policy-synchronization">
<title>Policy Synchronization and Concurrency</title>
<para>Policy modules must be written to assume that many
@@ -338,7 +327,7 @@
locks in the global lock order, helping to avoid deadlock.</para>
</sect2>
- <sect2 id="mac-framework-kernel-arch-registration">
+ <sect2 xml:id="mac-framework-kernel-arch-registration">
<title>Policy Registration</title>
<para>The MAC Framework maintains two lists of active
@@ -361,7 +350,7 @@
not unloadable.</para>
</sect2>
- <sect2 id="mac-framework-kernel-arch-entrypoints">
+ <sect2 xml:id="mac-framework-kernel-arch-entrypoints">
<title>Entry Points</title>
<para>Kernel services interact with the MAC Framework in two ways:
@@ -385,7 +374,7 @@
sockets and label transition at program execution.</para>
</sect2>
- <sect2 id="mac-framework-kernel-arch-composition">
+ <sect2 xml:id="mac-framework-kernel-arch-composition">
<title>Policy Composition</title>
<para>When more than one policy module is loaded into the kernel
@@ -406,7 +395,7 @@
composition.</para>
</sect2>
- <sect2 id="mac-framework-kernel-arch-labels">
+ <sect2 xml:id="mac-framework-kernel-arch-labels">
<title>Labeling Support</title>
<para>As many interesting access control extensions rely on
@@ -422,8 +411,8 @@
of string-based labels provides by user applications, and can
expose multiple label elements to applications if desired.</para>
- <para>In-memory labels are stored in slab-allocated <structname>struct
- label</structname>, which consists of a fixed-length array
+ <para>In-memory labels are stored in slab-allocated <varname remap="structname">struct
+ label</varname>, which consists of a fixed-length array
of unions, each holding a <literal>void *</literal> pointer
and a <literal>long</literal>. Policies registering for
label storage will be assigned a "slot" identifier, which
@@ -483,7 +472,7 @@
unload-reload operations for labeled policies.</para></note>
</sect2>
- <sect2 id="mac-framework-kernel-arch-syscalls">
+ <sect2 xml:id="mac-framework-kernel-arch-syscalls">
<title>System Calls</title>
<para>The MAC Framework implements a number of system calls:
@@ -492,7 +481,7 @@
applications.</para>
<para>The label management calls accept a label description
- structure, <structname>struct mac</structname>, which
+ structure, <varname remap="structname">struct mac</varname>, which
contains a series of MAC label elements. Each element
contains a character string name, and character string
value. Each policy will be given the chance to claim a
@@ -590,7 +579,7 @@
</sect2>
</sect1>
- <sect1 id="mac-policy-architecture">
+ <sect1 xml:id="mac-policy-architecture">
<title>MAC Policy Architecture</title>
<para>Security policies are either linked directly into the kernel,
@@ -618,7 +607,7 @@
points, and policy properties.</para></listitem>
</itemizedlist>
- <sect2 id="mac-policy-declaration">
+ <sect2 xml:id="mac-policy-declaration">
<title>Policy Declaration</title>
<para>Modules may be declared using the
@@ -670,7 +659,7 @@
processes.</para>
</sect2>
- <sect2 id="mac-policy-flags">
+ <sect2 xml:id="mac-policy-flags">
<title>Policy Flags</title>
<para>The policy declaration flags field permits the module to
@@ -737,7 +726,7 @@
to have label storage.</para></note>
</sect2>
- <sect2 id="mac-policy-entry-points">
+ <sect2 xml:id="mac-policy-entry-points">
<title>Policy Entry Points</title>
<para>Four classes of entry points are offered to policies
@@ -772,13 +761,13 @@
</sect2>
</sect1>
- <sect1 id="mac-entry-point-reference">
+ <sect1 xml:id="mac-entry-point-reference">
<title>MAC Policy Entry Point Reference</title>
- <sect2 id="mac-mpo-general">
+ <sect2 xml:id="mac-mpo-general">
<title>General-Purpose Module Entry Points</title>
- <sect3 id="mac-mpo-init">
+ <sect3 xml:id="mac-mpo-init">
<title><function>&mac.mpo;_init</function></title>
<funcsynopsis>
@@ -812,7 +801,7 @@
SYSINIT().</para>
</sect3>
- <sect3 id="mpo-destroy">
+ <sect3 xml:id="mpo-destroy">
<title><function>&mac.mpo;_destroy</function></title>
<funcsynopsis>
@@ -842,7 +831,7 @@
caution should be applied.</para>
</sect3>
- <sect3 id="mac-mpo-syscall">
+ <sect3 xml:id="mac-mpo-syscall">
<title><function>&mac.mpo;_syscall</function></title>
<funcsynopsis>
@@ -898,7 +887,7 @@
own.</para></note>
</sect3>
- <sect3 id="mac-mpo-thread-userret">
+ <sect3 xml:id="mac-mpo-thread-userret">
<title><function>&mac.mpo;_thread_userret</function></title>
<funcsynopsis>
@@ -948,10 +937,10 @@
</sect3>
</sect2>
- <sect2 id="mac-label-ops">
+ <sect2 xml:id="mac-label-ops">
<title>Label Operations</title>
- <sect3 id="mac-mpo-init-bpfdesc">
+ <sect3 xml:id="mac-mpo-init-bpfdesc">
<title><function>&mac.mpo;_init_bpfdesc_label</function></title>
<funcsynopsis>
@@ -981,7 +970,7 @@
descriptor). Sleeping is permitted.</para>
</sect3>
- <sect3 id="mac-mpo-init-cred-label">
+ <sect3 xml:id="mac-mpo-init-cred-label">
<title><function>&mac.mpo;_init_cred_label</function></title>
<funcsynopsis>
@@ -1011,7 +1000,7 @@
user credential. Sleeping is permitted.</para>
</sect3>
- <sect3 id="mac-mpo-init-devfsdirent">
+ <sect3 xml:id="mac-mpo-init-devfsdirent">
<title><function>&mac.mpo;_init_devfsdirent_label</function></title>
<funcsynopsis>
@@ -1041,7 +1030,7 @@
entry. Sleeping is permitted.</para>
</sect3>
- <sect3 id="mac-mpo-init-ifnet">
+ <sect3 xml:id="mac-mpo-init-ifnet">
<title><function>&mac.mpo;_init_ifnet_label</function></title>
<funcsynopsis>
@@ -1071,7 +1060,7 @@
interface. Sleeping is permitted.</para>
</sect3>
- <sect3 id="mac-mpo-init-ipq">
+ <sect3 xml:id="mac-mpo-init-ipq">
<title><function>&mac.mpo;_init_ipq_label</function></title>
<funcsynopsis>
@@ -1116,7 +1105,7 @@
the IP fragment reassembly queue.</para>
</sect3>
- <sect3 id="mac-mpo-init-mbuf">
+ <sect3 xml:id="mac-mpo-init-mbuf">
<title><function>&mac.mpo;_init_mbuf_label</function></title>
<funcsynopsis>
@@ -1162,7 +1151,7 @@
the mbuf header.</para>
</sect3>
- <sect3 id="mac-mpo-init-mount">
+ <sect3 xml:id="mac-mpo-init-mount">
<title><function>&mac.mpo;_init_mount_label</function></title>
<funcsynopsis>
@@ -1202,7 +1191,7 @@
point. Sleeping is permitted.</para>
</sect3>
- <sect3 id="mac-mpo-init-mount-fs-label">
+ <sect3 xml:id="mac-mpo-init-mount-fs-label">
<title><function>&mac.mpo;_init_mount_fs_label</function></title>
<funcsynopsis>
@@ -1232,7 +1221,7 @@
system. Sleeping is permitted</para>
</sect3>
- <sect3 id="mac-mpo-init-pipe-label">
+ <sect3 xml:id="mac-mpo-init-pipe-label">
<title><function>&mac.mpo;_init_pipe_label</function></title>
<funcsynopsis>
@@ -1262,7 +1251,7 @@
is permitted.</para>
</sect3>
- <sect3 id="mac-mpo-init-socket">
+ <sect3 xml:id="mac-mpo-init-socket">
<title><function>&mac.mpo;_init_socket_label</function></title>
<funcsynopsis>
@@ -1301,7 +1290,7 @@
during this initialization call.</para>
</sect3>
- <sect3 id="mac-mpo-init-socket-peer-label">
+ <sect3 xml:id="mac-mpo-init-socket-peer-label">
<title><function>&mac.mpo;_init_socket_peer_label</function></title>
<funcsynopsis>
@@ -1340,7 +1329,7 @@
during this initialization call.</para>
</sect3>
- <sect3 id="mac-mpo-init-proc-label">
+ <sect3 xml:id="mac-mpo-init-proc-label">
<title><function>&mac.mpo;_init_proc_label</function></title>
<funcsynopsis>
@@ -1371,7 +1360,7 @@
</sect3>
- <sect3 id="mac-mpo-init-vnode">
+ <sect3 xml:id="mac-mpo-init-vnode">
<title><function>&mac.mpo;_init_vnode_label</function></title>
<funcsynopsis>
@@ -1400,7 +1389,7 @@
<para>Initialize the label on a newly instantiated vnode. Sleeping
is permitted.</para>
</sect3>
- <sect3 id="mac-mpo-destroy-bpfdesc">
+ <sect3 xml:id="mac-mpo-destroy-bpfdesc">
<title><function>&mac.mpo;_destroy_bpfdesc_label</function></title>
<funcsynopsis>
@@ -1432,7 +1421,7 @@
destroyed.</para>
</sect3>
- <sect3 id="mac-mpo-destroy-cred">
+ <sect3 xml:id="mac-mpo-destroy-cred">
<title><function>&mac.mpo;_destroy_cred_label</function></title>
<funcsynopsis>
@@ -1465,7 +1454,7 @@
</sect3>
- <sect3 id="mac-mpo-destroy-devfsdirent">
+ <sect3 xml:id="mac-mpo-destroy-devfsdirent">
<title><function>&mac.mpo;_destroy_devfsdirent_label</function></title>
<funcsynopsis>
@@ -1497,7 +1486,7 @@
be destroyed.</para>
</sect3>
- <sect3 id="mac-mpo-destroy-ifnet-label">
+ <sect3 xml:id="mac-mpo-destroy-ifnet-label">
<title><function>&mac.mpo;_destroy_ifnet_label</function></title>
<funcsynopsis>
@@ -1529,7 +1518,7 @@
be destroyed.</para>
</sect3>
- <sect3 id="mac-mpo-destroy-ipq-label">
+ <sect3 xml:id="mac-mpo-destroy-ipq-label">
<title><function>&mac.mpo;_destroy_ipq_label</function></title>
<funcsynopsis>
@@ -1561,7 +1550,7 @@
it may be destroyed.</para>
</sect3>
- <sect3 id="mac-mpo-destroy-mbuf-label">
+ <sect3 xml:id="mac-mpo-destroy-mbuf-label">
<title><function>&mac.mpo;_destroy_mbuf_label</function></title>
<funcsynopsis>
@@ -1593,7 +1582,7 @@
be destroyed.</para>
</sect3>
- <sect3 id="mac-mpo-destroy-mount-label">
+ <sect3 xml:id="mac-mpo-destroy-mount-label">
<title><function>&mac.mpo;_destroy_mount_label</function></title>
<funcsynopsis>
@@ -1625,7 +1614,7 @@
may be destroyed.</para>
</sect3>
- <sect3 id="mac-mpo-destroy-mount">
+ <sect3 xml:id="mac-mpo-destroy-mount">
<title><function>&mac.mpo;_destroy_mount_label</function></title>
<funcsynopsis>
@@ -1652,7 +1641,7 @@
<row>
<entry><parameter>fslabel</parameter></entry>
- <entry>File system label being destroyed></entry>
+ <entry>File system label being destroyed&gt;</entry>
</row>
</tbody>
</tgroup>
@@ -1665,7 +1654,7 @@
destroyed.</para>
</sect3>
- <sect3 id="mac-mpo-destroy-socket">
+ <sect3 xml:id="mac-mpo-destroy-socket">
<title><function>&mac.mpo;_destroy_socket_label</function></title>
<funcsynopsis>
@@ -1699,7 +1688,7 @@
destroyed.</para>
</sect3>
- <sect3 id="mac-mpo-destroy-socket-peer-label">
+ <sect3 xml:id="mac-mpo-destroy-socket-peer-label">
<title><function>&mac.mpo;_destroy_socket_peer_label</function></title>
<funcsynopsis>
@@ -1731,7 +1720,7 @@
be destroyed.</para>
</sect3>
- <sect3 id="mac-mpo-destroy-pipe-label">
+ <sect3 xml:id="mac-mpo-destroy-pipe-label">
<title><function>&mac.mpo;_destroy_pipe_label</function></title>
<funcsynopsis>
@@ -1763,7 +1752,7 @@
destroyed.</para>
</sect3>
- <sect3 id="mac-mpo-destroy-proc-label">
+ <sect3 xml:id="mac-mpo-destroy-proc-label">
<title><function>&mac.mpo;_destroy_proc_label</function></title>
<funcsynopsis>
@@ -1794,7 +1783,7 @@
destroyed.</para>
</sect3>
- <sect3 id="mac-mpo-destroy-vnode-label">
+ <sect3 xml:id="mac-mpo-destroy-vnode-label">
<title><function>&mac.mpo;_destroy_vnode_label</function></title>
<funcsynopsis>
@@ -1825,7 +1814,7 @@
destroyed.</para>
</sect3>
- <sect3 id="mac-mpo-copy-mbuf-label">
+ <sect3 xml:id="mac-mpo-copy-mbuf-label">
<title><function>&mac.mpo;_copy_mbuf_label</function></title>
<funcsynopsis>
@@ -1863,7 +1852,7 @@
<parameter>dest</parameter>.</para>
</sect3>
- <sect3 id="mac-mpo-copy-pipe-label">
+ <sect3 xml:id="mac-mpo-copy-pipe-label">
<title><function>&mac.mpo;_copy_pipe_label</function></title>
<funcsynopsis>
@@ -1901,7 +1890,7 @@
<parameter>dest</parameter>.</para>
</sect3>
- <sect3 id="mac-mpo-copy-vnode-label">
+ <sect3 xml:id="mac-mpo-copy-vnode-label">
<title><function>&mac.mpo;_copy_vnode_label</function></title>
<funcsynopsis>
@@ -1939,7 +1928,7 @@
<parameter>dest</parameter>.</para>
</sect3>
- <sect3 id="mac-mpo-externalize-cred-label">
+ <sect3 xml:id="mac-mpo-externalize-cred-label">
<title><function>&mac.mpo;_externalize_cred_label</function></title>
<funcsynopsis>
@@ -1962,7 +1951,7 @@
&mac.externalize.para;
</sect3>
- <sect3 id="mac-mpo-externalize-ifnet-label">
+ <sect3 xml:id="mac-mpo-externalize-ifnet-label">
<title><function>&mac.mpo;_externalize_ifnet_label</function></title>
<funcsynopsis>
@@ -1985,7 +1974,7 @@
&mac.externalize.para;
</sect3>
- <sect3 id="mac-mpo-externalize-pipe-label">
+ <sect3 xml:id="mac-mpo-externalize-pipe-label">
<title><function>&mac.mpo;_externalize_pipe_label</function></title>
<funcsynopsis>
@@ -2008,7 +1997,7 @@
&mac.externalize.para;
</sect3>
- <sect3 id="mac-mpo-externalize-socket-label">
+ <sect3 xml:id="mac-mpo-externalize-socket-label">
<title><function>&mac.mpo;_externalize_socket_label</function></title>
<funcsynopsis>
@@ -2031,7 +2020,7 @@
&mac.externalize.para;
</sect3>
- <sect3 id="mac-mpo-externalize-socket-peer-label">
+ <sect3 xml:id="mac-mpo-externalize-socket-peer-label">
<title><function>&mac.mpo;_externalize_socket_peer_label</function></title>
<funcsynopsis>
@@ -2054,7 +2043,7 @@
&mac.externalize.para;
</sect3>
- <sect3 id="mac-mpo-externalize-vnode-label">
+ <sect3 xml:id="mac-mpo-externalize-vnode-label">
<title><function>&mac.mpo;_externalize_vnode_label</function></title>
<funcsynopsis>
@@ -2077,7 +2066,7 @@
&mac.externalize.para;
</sect3>
- <sect3 id="mac-mpo-internalize-cred-label">
+ <sect3 xml:id="mac-mpo-internalize-cred-label">
<title><function>&mac.mpo;_internalize_cred_label</function></title>
<funcsynopsis>
@@ -2100,7 +2089,7 @@
&mac.internalize.para;
</sect3>
- <sect3 id="mac-mpo-internalize-ifnet-label">
+ <sect3 xml:id="mac-mpo-internalize-ifnet-label">
<title><function>&mac.mpo;_internalize_ifnet_label</function></title>
<funcsynopsis>
@@ -2123,7 +2112,7 @@
&mac.internalize.para;
</sect3>
- <sect3 id="mac-mpo-internalize-pipe-label">
+ <sect3 xml:id="mac-mpo-internalize-pipe-label">
<title><function>&mac.mpo;_internalize_pipe_label</function></title>
<funcsynopsis>
@@ -2146,7 +2135,7 @@
&mac.internalize.para;
</sect3>
- <sect3 id="mac-mpo-internalize-socket-label">
+ <sect3 xml:id="mac-mpo-internalize-socket-label">
<title><function>&mac.mpo;_internalize_socket_label</function></title>
<funcsynopsis>
@@ -2169,7 +2158,7 @@
&mac.internalize.para;
</sect3>
- <sect3 id="mac-mpo-internalize-vnode-label">
+ <sect3 xml:id="mac-mpo-internalize-vnode-label">
<title><function>&mac.mpo;_internalize_vnode_label</function></title>
<funcsynopsis>
@@ -2193,7 +2182,7 @@
</sect3>
</sect2>
- <sect2 id="mac-label-events">
+ <sect2 xml:id="mac-label-events">
<title>Label Events</title>
<para>This class of entry points is used by the MAC framework to
@@ -2264,10 +2253,10 @@ Label destruction o</programlisting>
<symbol>MAC_INTERNALIZE</symbol>, which accepts a user label
to be converted to an in-kernel representation.</para>
- <sect3 id="mac-fs-label-event-ops">
+ <sect3 xml:id="mac-fs-label-event-ops">
<title>File System Object Labeling Event Operations</title>
- <sect4 id="mac-mpo-associate-vnode-devfs">
+ <sect4 xml:id="mac-mpo-associate-vnode-devfs">
<title><function>&mac.mpo;_associate_vnode_devfs</function></title>
<funcsynopsis>
@@ -2338,7 +2327,7 @@ Label destruction o</programlisting>
label.</para>
</sect4>
- <sect4 id="mac-mpo-associate-vnode-extattr">
+ <sect4 xml:id="mac-mpo-associate-vnode-extattr">
<title><function>&mac.mpo;_associate_vnode_extattr</function></title>
<funcsynopsis>
@@ -2397,7 +2386,7 @@ Label destruction o</programlisting>
be returned.</para>
</sect4>
- <sect4 id="mac-mpo-associate-vnode-singlelabel">
+ <sect4 xml:id="mac-mpo-associate-vnode-singlelabel">
<title><function>&mac.mpo;_associate_vnode_singlelabel</function></title>
<funcsynopsis>
@@ -2452,7 +2441,7 @@ Label destruction o</programlisting>
</sect4>
- <sect4 id="mac-mpo-create-devfs-device">
+ <sect4 xml:id="mac-mpo-create-devfs-device">
<title><function>&mac.mpo;_create_devfs_device</function></title>
<funcsynopsis>
@@ -2499,7 +2488,7 @@ Label destruction o</programlisting>
available.</para>
</sect4>
- <sect4 id="mac-mpo-create-devfs-directory">
+ <sect4 xml:id="mac-mpo-create-devfs-directory">
<title><function>&mac.mpo;_create_devfs_directory</function></title>
<funcsynopsis>
@@ -2548,7 +2537,7 @@ Label destruction o</programlisting>
available.</para>
</sect4>
- <sect4 id="mac-mpo-create-devfs-symlink">
+ <sect4 xml:id="mac-mpo-create-devfs-symlink">
<title><function>&mac.mpo;_create_devfs_symlink</function></title>
<funcsynopsis>
@@ -2615,7 +2604,7 @@ Label destruction o</programlisting>
a newly created &man.devfs.5; symbolic link entry.</para>
</sect4>
- <sect4 id="mac-mpo-create-vnode-extattr">
+ <sect4 xml:id="mac-mpo-create-vnode-extattr">
<title><function>&mac.mpo;_create_vnode_extattr</function></title>
<funcsynopsis>
@@ -2700,7 +2689,7 @@ Label destruction o</programlisting>
return an appropriate error.</para>
</sect4>
- <sect4 id="mac-mpo-create-mount">
+ <sect4 xml:id="mac-mpo-create-mount">
<title><function>&mac.mpo;_create_mount</function></title>
<funcsynopsis>
@@ -2754,7 +2743,7 @@ Label destruction o</programlisting>
a new file system is mounted.</para>
</sect4>
- <sect4 id="mac-mpo-create-root-mount">
+ <sect4 xml:id="mac-mpo-create-root-mount">
<title><function>&mac.mpo;_create_root_mount</function></title>
<funcsynopsis>
@@ -2779,8 +2768,7 @@ Label destruction o</programlisting>
<tbody>
<row>
- <entry namest="first" nameend="last">See <xref
- linkend="mac-mpo-create-mount"/>.</entry>
+ <entry namest="first" nameend="last">See <xref linkend="mac-mpo-create-mount"/>.</entry>
</row>
</tbody>
</tgroup>
@@ -2792,7 +2780,7 @@ Label destruction o</programlisting>
&mac.mpo;_create_mount;.</para>
</sect4>
- <sect4 id="mac-mpo-relabel-vnode">
+ <sect4 xml:id="mac-mpo-relabel-vnode">
<title><function>&mac.mpo;_relabel_vnode</function></title>
<funcsynopsis>
@@ -2845,7 +2833,7 @@ Label destruction o</programlisting>
update vnode label and the passed subject credential.</para>
</sect4>
- <sect4 id="mac-mpo-setlabel-vnode-extattr">
+ <sect4 xml:id="mac-mpo-setlabel-vnode-extattr">
<title><function>&mac.mpo;_setlabel_vnode_extattr</function></title>
<funcsynopsis>
@@ -2900,7 +2888,7 @@ Label destruction o</programlisting>
<function>vop_stdcreatevnode_ea</function>.</para>
</sect4>
- <sect4 id="mac-mpo-update-devfsdirent">
+ <sect4 xml:id="mac-mpo-update-devfsdirent">
<title><function>&mac.mpo;_update_devfsdirent</function></title>
<funcsynopsis>
<funcprototype>
@@ -2961,11 +2949,11 @@ Label destruction o</programlisting>
</sect4>
</sect3>
- <sect3 id="mac-ipc-label-ops">
+ <sect3 xml:id="mac-ipc-label-ops">
<title>IPC Object Labeling Event Operations</title>
- <sect4 id="mac-mpo-create-mbuf-from-socket">
+ <sect4 xml:id="mac-mpo-create-mbuf-from-socket">
<title><function>&mac.mpo;_create_mbuf_from_socket</function></title>
<funcsynopsis>
@@ -3020,7 +3008,7 @@ Label destruction o</programlisting>
passed mbuf.</para>
</sect4>
- <sect4 id="mac-mpo-create-pipe">
+ <sect4 xml:id="mac-mpo-create-pipe">
<title><function>&mac.mpo;_create_pipe</function></title>
<funcsynopsis>
@@ -3066,7 +3054,7 @@ Label destruction o</programlisting>
created.</para>
</sect4>
- <sect4 id="mac-mpo-create-socket">
+ <sect4 xml:id="mac-mpo-create-socket">
<title><function>&mac.mpo;_create_socket</function></title>
<funcsynopsis>
@@ -3113,7 +3101,7 @@ Label destruction o</programlisting>
created.</para>
</sect4>
- <sect4 id="mac-mpo-create-socket-from-socket">
+ <sect4 xml:id="mac-mpo-create-socket-from-socket">
<title><function>&mac.mpo;_create_socket_from_socket</function></title>
<funcsynopsis>
@@ -3167,7 +3155,7 @@ Label destruction o</programlisting>
socket, <parameter>oldsocket</parameter>.</para>
</sect4>
- <sect4 id="mac-mpo-relabel-pipe">
+ <sect4 xml:id="mac-mpo-relabel-pipe">
<title><function>&mac.mpo;_relabel_pipe</function></title>
<funcsynopsis>
@@ -3220,7 +3208,7 @@ Label destruction o</programlisting>
<parameter>pipe</parameter>.</para>
</sect4>
- <sect4 id="mac-mpo-relabel-socket">
+ <sect4 xml:id="mac-mpo-relabel-socket">
<title><function>&mac.mpo;_relabel_socket</function></title>
<funcsynopsis>
@@ -3274,7 +3262,7 @@ Label destruction o</programlisting>
label update.</para>
</sect4>
- <sect4 id="mpo-set-socket-peer-from-mbuf">
+ <sect4 xml:id="mpo-set-socket-peer-from-mbuf">
<title><function>&mac.mpo;_set_socket_peer_from_mbuf</function></title>
<funcsynopsis>
@@ -3328,7 +3316,7 @@ Label destruction o</programlisting>
domain sockets.</para>
</sect4>
- <sect4 id="mac-mpo-set-socket-peer-from-socket">
+ <sect4 xml:id="mac-mpo-set-socket-peer-from-socket">
<title><function>&mac.mpo;_set_socket_peer_from_socket</function></title>
<funcsynopsis>
@@ -3385,10 +3373,10 @@ Label destruction o</programlisting>
</sect4>
</sect3>
- <sect3 id="mac-net-labeling-event-ops">
+ <sect3 xml:id="mac-net-labeling-event-ops">
<title>Network Object Labeling Event Operations</title>
- <sect4 id="mac-mpo-create-bpfdesc">
+ <sect4 xml:id="mac-mpo-create-bpfdesc">
<title><function>&mac.mpo;_create_bpfdesc</function></title>
<funcsynopsis>
@@ -3436,7 +3424,7 @@ Label destruction o</programlisting>
subject credential.</para>
</sect4>
- <sect4 id="mac-mpo-create-ifnet">
+ <sect4 xml:id="mac-mpo-create-ifnet">
<title><function>&mac.mpo;_create_ifnet</function></title>
<funcsynopsis>
@@ -3476,7 +3464,7 @@ Label destruction o</programlisting>
during the boot or as a result of a user action.</para>
</sect4>
- <sect4 id="mac-mpo-create-ipq">
+ <sect4 xml:id="mac-mpo-create-ipq">
<title><function>&mac.mpo;_create_ipq</function></title>
<funcsynopsis>
@@ -3530,7 +3518,7 @@ Label destruction o</programlisting>
fragment.</para>
</sect4>
- <sect4 id="mac-mpo-create-datagram-from-ipq">
+ <sect4 xml:id="mac-mpo-create-datagram-from-ipq">
<title><function>&mac.mpo;_create_datagram_from_ipq</function></title>
<funcsynopsis>
@@ -3584,7 +3572,7 @@ Label destruction o</programlisting>
generated.</para>
</sect4>
- <sect4 id="mac-mpo-create-fragment">
+ <sect4 xml:id="mac-mpo-create-fragment">
<title><function>&mac.mpo;_create_fragment</function></title>
<funcsynopsis>
@@ -3638,7 +3626,7 @@ Label destruction o</programlisting>
it was generate from.</para>
</sect4>
- <sect4 id="mac-mpo-create-mbuf-from-mbuf">
+ <sect4 xml:id="mac-mpo-create-mbuf-from-mbuf">
<title><function>&mac.mpo;_create_mbuf_from_mbuf</function></title>
<funcsynopsis>
@@ -3693,7 +3681,7 @@ Label destruction o</programlisting>
an mbuf is re-allocated for alignment purposes.</para>
</sect4>
- <sect4 id="mac-mpo-create-mbuf-linklayer">
+ <sect4 xml:id="mac-mpo-create-mbuf-linklayer">
<title><function>&mac.mpo;_create_mbuf_linklayer</function></title>
<funcsynopsis>
@@ -3749,7 +3737,7 @@ Label destruction o</programlisting>
IPv4 and IPv6 stacks.</para>
</sect4>
- <sect4 id="mac-mpo-create-mbuf-from-bpfdesc">
+ <sect4 xml:id="mac-mpo-create-mbuf-from-bpfdesc">
<title><function>&mac.mpo;_create_mbuf_from_bpfdesc</function></title>
<funcsynopsis>
@@ -3804,7 +3792,7 @@ Label destruction o</programlisting>
associated with the passed BPF descriptor.</para>
</sect4>
- <sect4 id="mac-mpo-create-mbuf-from-ifnet">
+ <sect4 xml:id="mac-mpo-create-mbuf-from-ifnet">
<title><function>&mac.mpo;_create_mbuf_from_ifnet</function></title>
<funcsynopsis>
@@ -3857,7 +3845,7 @@ Label destruction o</programlisting>
datagram generated from the passed network interface.</para>
</sect4>
- <sect4 id="mac-mpo-create-mbuf-multicast-encap">
+ <sect4 xml:id="mac-mpo-create-mbuf-multicast-encap">
<title><function>&mac.mpo;_create_mbuf_multicast_encap</function></title>
<funcsynopsis>
@@ -3929,7 +3917,7 @@ Label destruction o</programlisting>
delivered using the virtual interface.</para>
</sect4>
- <sect4 id="mac-mpo-create-mbuf-netlayer">
+ <sect4 xml:id="mac-mpo-create-mbuf-netlayer">
<title><function>&mac.mpo;_create_mbuf_netlayer</function></title>
<funcsynopsis>
@@ -3985,7 +3973,7 @@ Label destruction o</programlisting>
when responding to ICMP request datagrams.</para>
</sect4>
- <sect4 id="mac-mpo-fragment-match">
+ <sect4 xml:id="mac-mpo-fragment-match">
<title><function>&mac.mpo;_fragment_match</function></title>
<funcsynopsis>
@@ -4049,7 +4037,7 @@ Label destruction o</programlisting>
label or other information.</para>
</sect4>
- <sect4 id="mac-mpo-ifnet-relabel">
+ <sect4 xml:id="mac-mpo-ifnet-relabel">
<title><function>&mac.mpo;_relabel_ifnet</function></title>
<funcsynopsis>
@@ -4104,7 +4092,7 @@ Label destruction o</programlisting>
subject credential, <parameter>cred</parameter>.</para>
</sect4>
- <sect4 id="mac-mpo-update-ipq">
+ <sect4 xml:id="mac-mpo-update-ipq">
<title><function>&mac.mpo;_update_ipq</function></title>
<funcsynopsis>
@@ -4160,10 +4148,10 @@ Label destruction o</programlisting>
</sect4>
</sect3>
- <sect3 id="mac-proc-labeling-event-ops">
+ <sect3 xml:id="mac-proc-labeling-event-ops">
<title>Process Labeling Event Operations</title>
- <sect4 id="mac-mpo-create-cred">
+ <sect4 xml:id="mac-mpo-create-cred">
<title><function>&mac.mpo;_create_cred</function></title>
<funcsynopsis>
@@ -4203,7 +4191,7 @@ Label destruction o</programlisting>
process forking or creation event.</para>
</sect4>
- <sect4 id="mac-mpo-execve-transition">
+ <sect4 xml:id="mac-mpo-execve-transition">
<title><function>&mac.mpo;_execve_transition</function></title>
<funcsynopsis>
@@ -4271,7 +4259,7 @@ Label destruction o</programlisting>
<function>mpo_execve_will_transition</function>.</para>
</sect4>
- <sect4 id="mac-mpo-execve-will-transition">
+ <sect4 xml:id="mac-mpo-execve-will-transition">
<title><function>&mac.mpo;_execve_will_transition</function></title>
<funcsynopsis>
@@ -4326,7 +4314,7 @@ Label destruction o</programlisting>
transition.</para>
</sect4>
- <sect4 id="mac-mpo-create-proc0">
+ <sect4 xml:id="mac-mpo-create-proc0">
<title><function>&mac.mpo;_create_proc0</function></title>
<funcsynopsis>
@@ -4356,7 +4344,7 @@ Label destruction o</programlisting>
of all kernel processes.</para>
</sect4>
- <sect4 id="mac-mpo-create-proc1">
+ <sect4 xml:id="mac-mpo-create-proc1">
<title><function>&mac.mpo;_create_proc1</function></title>
<funcsynopsis>
@@ -4386,7 +4374,7 @@ Label destruction o</programlisting>
of all user processes.</para>
</sect4>
- <sect4 id="mac-mpo-relabel-cred">
+ <sect4 xml:id="mac-mpo-relabel-cred">
<title><function>&mac.mpo;_relabel_cred</function></title>
<funcsynopsis>
@@ -4427,7 +4415,7 @@ Label destruction o</programlisting>
</sect3>
</sect2>
- <sect2 id="mac-access-control-checks">
+ <sect2 xml:id="mac-access-control-checks">
<title>Access Control Checks</title>
<para>Access control entry points permit policy modules to
@@ -4455,15 +4443,15 @@ Label destruction o</programlisting>
<entry><errorcode>EDEADLK</errorcode></entry></row>
<row>
- <entry></entry>
+ <entry/>
<entry><errorcode>EINVAL</errorcode></entry>
</row>
<row>
- <entry></entry>
+ <entry/>
<entry><errorcode>ESRCH</errorcode></entry>
</row>
<row>
- <entry></entry>
+ <entry/>
<entry>EACCES</entry>
</row>
<row>
@@ -4481,7 +4469,7 @@ Label destruction o</programlisting>
failures, invalid arguments, object not present, access not
permitted, other.</para>
- <sect3 id="mac-mpo-bpfdesc-check-receive-from-ifnet">
+ <sect3 xml:id="mac-mpo-bpfdesc-check-receive-from-ifnet">
<title><function>&mac.mpo;_check_bpfdesc_receive</function></title>
<funcsynopsis>
@@ -4539,7 +4527,7 @@ Label destruction o</programlisting>
<errorcode>EPERM</errorcode> for lack of privilege.</para>
</sect3>
- <sect3 id="mac-mpo-check-kenv-dump">
+ <sect3 xml:id="mac-mpo-check-kenv-dump">
<title><function>&mac.mpo;_check_kenv_dump</function></title>
<funcsynopsis>
@@ -4569,7 +4557,7 @@ Label destruction o</programlisting>
retrieve the kernel environment (see &man.kenv.2;).</para>
</sect3>
- <sect3 id="mac-mpo-check-kenv-get">
+ <sect3 xml:id="mac-mpo-check-kenv-get">
<title><function>&mac.mpo;_check_kenv_get</function></title>
<funcsynopsis>
@@ -4606,7 +4594,7 @@ Label destruction o</programlisting>
variable.</para>
</sect3>
- <sect3 id="mac-mpo-check-kenv-set">
+ <sect3 xml:id="mac-mpo-check-kenv-set">
<title><function>&mac.mpo;_check_kenv_set</function></title>
<funcsynopsis>
@@ -4642,7 +4630,7 @@ Label destruction o</programlisting>
the specified kernel environment variable.</para>
</sect3>
- <sect3 id="mac-mpo-check-kenv-unset">
+ <sect3 xml:id="mac-mpo-check-kenv-unset">
<title><function>&mac.mpo;_check_kenv_unset</function></title>
<funcsynopsis>
@@ -4678,7 +4666,7 @@ Label destruction o</programlisting>
the specified kernel environment variable.</para>
</sect3>
- <sect3 id="mac-mpo-check-kld-load">
+ <sect3 xml:id="mac-mpo-check-kld-load">
<title><function>&mac.mpo;_check_kld_load</function></title>
<funcsynopsis>
@@ -4723,7 +4711,7 @@ Label destruction o</programlisting>
the specified module file.</para>
</sect3>
- <sect3 id="mac-mpo-check-kld-stat">
+ <sect3 xml:id="mac-mpo-check-kld-stat">
<title><function>&mac.mpo;_check_kld_stat</function></title>
<funcsynopsis>
@@ -4754,7 +4742,7 @@ Label destruction o</programlisting>
statistics.</para>
</sect3>
- <sect3 id="mac-mpo-check-kld-unload">
+ <sect3 xml:id="mac-mpo-check-kld-unload">
<title><function>&mac.mpo;_check_kld_unload</function></title>
<funcsynopsis>
@@ -4784,7 +4772,7 @@ Label destruction o</programlisting>
unload a kernel module.</para>
</sect3>
- <sect3 id="mac-mpo-check-pipe-ioctl">
+ <sect3 xml:id="mac-mpo-check-pipe-ioctl">
<title><function>&mac.mpo;_check_pipe_ioctl</function></title>
<funcsynopsis>
@@ -4842,7 +4830,7 @@ Label destruction o</programlisting>
the specified &man.ioctl.2; call.</para>
</sect3>
- <sect3 id="mac-mpo-check-pipe-poll">
+ <sect3 xml:id="mac-mpo-check-pipe-poll">
<title><function>&mac.mpo;_check_pipe_poll</function></title>
<funcsynopsis>
@@ -4887,7 +4875,7 @@ Label destruction o</programlisting>
<parameter>pipe</parameter>.</para>
</sect3>
- <sect3 id="mac-mpo-check-pipe-read">
+ <sect3 xml:id="mac-mpo-check-pipe-read">
<title><function>&mac.mpo;_check_pipe_read</function></title>
<funcsynopsis>
@@ -4932,7 +4920,7 @@ Label destruction o</programlisting>
access to <parameter>pipe</parameter>.</para>
</sect3>
- <sect3 id="mac-mpo-check-pipe-relabel">
+ <sect3 xml:id="mac-mpo-check-pipe-relabel">
<title><function>&mac.mpo;_check_pipe_relabel</function></title>
<funcsynopsis>
@@ -4985,7 +4973,7 @@ Label destruction o</programlisting>
relabel <parameter>pipe</parameter>.</para>
</sect3>
- <sect3 id="mac-mpo-check-pipe-stat">
+ <sect3 xml:id="mac-mpo-check-pipe-stat">
<title><function>&mac.mpo;_check_pipe_stat</function></title>
<funcsynopsis>
@@ -5031,7 +5019,7 @@ Label destruction o</programlisting>
<parameter>pipe</parameter>.</para>
</sect3>
- <sect3 id="mac-mpo-check-pipe-write">
+ <sect3 xml:id="mac-mpo-check-pipe-write">
<title><function>&mac.mpo;_check_pipe_write</function></title>
<funcsynopsis>
@@ -5076,7 +5064,7 @@ Label destruction o</programlisting>
to <parameter>pipe</parameter>.</para>
</sect3>
- <sect3 id="mac-mpo-cred-check-socket-bind">
+ <sect3 xml:id="mac-mpo-cred-check-socket-bind">
<title><function>&mac.mpo;_check_socket_bind</function></title>
<funcsynopsis>
@@ -5128,7 +5116,7 @@ Label destruction o</programlisting>
</sect3>
- <sect3 id="mac-mpo-cred-check-socket-connect">
+ <sect3 xml:id="mac-mpo-cred-check-socket-connect">
<title><function>&mac.mpo;_check_socket_connect</function></title>
<funcsynopsis>
@@ -5187,7 +5175,7 @@ Label destruction o</programlisting>
<errorcode>EPERM</errorcode> for lack of privilege.</para>
</sect3>
- <sect3 id="mac-mpo-check-socket-receive">
+ <sect3 xml:id="mac-mpo-check-socket-receive">
<title><function>&mac.mpo;_check_socket_receive</function></title>
<funcsynopsis>
@@ -5233,7 +5221,7 @@ Label destruction o</programlisting>
<parameter>so</parameter>.</para>
</sect3>
- <sect3 id="mac-mpo-check-socket-send">
+ <sect3 xml:id="mac-mpo-check-socket-send">
<title><function>&mac.mpo;_check_socket_send</function></title>
<funcsynopsis>
@@ -5279,7 +5267,7 @@ Label destruction o</programlisting>
<parameter>so</parameter>.</para>
</sect3>
- <sect3 id="mac-mpo-check-cred-visible">
+ <sect3 xml:id="mac-mpo-check-cred-visible">
<title><function>&mac.mpo;_check_cred_visible</function></title>
<funcsynopsis>
@@ -5326,7 +5314,7 @@ Label destruction o</programlisting>
and in procfs lookups.</para>
</sect3>
- <sect3 id="mac-mpo-cred-check-socket-visible">
+ <sect3 xml:id="mac-mpo-cred-check-socket-visible">
<title><function>&mac.mpo;_check_socket_visible</function></title>
<funcsynopsis>
@@ -5369,7 +5357,7 @@ Label destruction o</programlisting>
</sect3>
- <sect3 id="mac-mpo-cred-check-ifnet-relabel">
+ <sect3 xml:id="mac-mpo-cred-check-ifnet-relabel">
<title><function>&mac.mpo;_check_ifnet_relabel</function></title>
<funcsynopsis>
@@ -5422,7 +5410,7 @@ Label destruction o</programlisting>
passed network interface to the passed label update.</para>
</sect3>
- <sect3 id="mac-mpo-cred-check-socket-relabel">
+ <sect3 xml:id="mac-mpo-cred-check-socket-relabel">
<title><function>&mac.mpo;_check_socket_relabel</function></title>
<funcsynopsis>
@@ -5475,7 +5463,7 @@ Label destruction o</programlisting>
passed socket to the passed label update.</para>
</sect3>
- <sect3 id="mac-mpo-cred-check-cred-relabel">
+ <sect3 xml:id="mac-mpo-cred-check-cred-relabel">
<title><function>&mac.mpo;_check_cred_relabel</function></title>
<funcsynopsis>
@@ -5514,7 +5502,7 @@ Label destruction o</programlisting>
</sect3>
- <sect3 id="mac-mpo-cred-check-vnode-relabel">
+ <sect3 xml:id="mac-mpo-cred-check-vnode-relabel">
<title><function>&mac.mpo;_check_vnode_relabel</function></title>
<funcsynopsis>
@@ -5569,7 +5557,7 @@ Label destruction o</programlisting>
passed vnode to the passed label update.</para>
</sect3>
- <sect3 id="mpo-cred-check-mount-stat">
+ <sect3 xml:id="mpo-cred-check-mount-stat">
<title><function>&mac.mpo;_check_mount_stat</function></title>
<funcsynopsis>
@@ -5622,7 +5610,7 @@ Label destruction o</programlisting>
systems, such as when &man.getfsstat.2; is invoked. </para>
</sect3>
- <sect3 id="mac-mpo-cred-check-proc-debug">
+ <sect3 xml:id="mac-mpo-cred-check-proc-debug">
<title><function>&mac.mpo;_check_proc_debug</function></title>
<funcsynopsis>
@@ -5668,7 +5656,7 @@ Label destruction o</programlisting>
operations.</para>
</sect3>
- <sect3 id="mac-mpo-cred-check-vnode-access">
+ <sect3 xml:id="mac-mpo-cred-check-vnode-access">
<title><function>&mac.mpo;_check_vnode_access</function></title>
<funcsynopsis>
@@ -5727,7 +5715,7 @@ Label destruction o</programlisting>
privilege.</para>
</sect3>
- <sect3 id="mac-mpo-cred-check-vnode-chdir">
+ <sect3 xml:id="mac-mpo-cred-check-vnode-chdir">
<title><function>&mac.mpo;_check_vnode_chdir</function></title>
<funcsynopsis>
@@ -5777,7 +5765,7 @@ Label destruction o</programlisting>
privilege.</para>
</sect3>
- <sect3 id="mac-mpo-check-vnode-chroot">
+ <sect3 xml:id="mac-mpo-check-vnode-chroot">
<title><function>&mac.mpo;_check_vnode_chroot</function></title>
<funcsynopsis>
@@ -5823,7 +5811,7 @@ Label destruction o</programlisting>
(<parameter>dvp</parameter>).</para>
</sect3>
- <sect3 id="mac-mpo-cred-check-vnode-create">
+ <sect3 xml:id="mac-mpo-cred-check-vnode-create">
<title><function>&mac.mpo;_check_vnode_create</function></title>
<funcsynopsis>
@@ -5892,7 +5880,7 @@ Label destruction o</programlisting>
others.</para>
</sect3>
- <sect3 id="mac-mpo-cred-check-vnode-delete">
+ <sect3 xml:id="mac-mpo-cred-check-vnode-delete">
<title><function>&mac.mpo;_check_vnode_delete</function></title>
<funcsynopsis>
@@ -5970,7 +5958,7 @@ Label destruction o</programlisting>
rename.</para>
</sect3>
- <sect3 id="mac-mpo-cred-check-vnode-deleteacl">
+ <sect3 xml:id="mac-mpo-cred-check-vnode-deleteacl">
<title><function>&mac.mpo;_check_vnode_deleteacl</function></title>
<funcsynopsis>
@@ -6025,7 +6013,7 @@ Label destruction o</programlisting>
privilege.</para>
</sect3>
- <sect3 id="mac-mpo-cred-check-vnode-exec">
+ <sect3 xml:id="mac-mpo-cred-check-vnode-exec">
<title><function>&mac.mpo;_check_vnode_exec</function></title>
<funcsynopsis>
@@ -6076,7 +6064,7 @@ Label destruction o</programlisting>
privilege.</para>
</sect3>
- <sect3 id="mpo-cred-check-vnode-getacl">
+ <sect3 xml:id="mpo-cred-check-vnode-getacl">
<title><function>&mac.mpo;_check_vnode_getacl</function></title>
<funcsynopsis>
@@ -6133,7 +6121,7 @@ Label destruction o</programlisting>
privilege.</para>
</sect3>
- <sect3 id="mac-mpo-cred-check-vnode-getextattr">
+ <sect3 xml:id="mac-mpo-cred-check-vnode-getextattr">
<title><function>&mac.mpo;_check_vnode_getextattr</function></title>
<funcsynopsis>
@@ -6207,7 +6195,7 @@ Label destruction o</programlisting>
privilege.</para>
</sect3>
- <sect3 id="mac-mpo-check-vnode-link">
+ <sect3 xml:id="mac-mpo-check-vnode-link">
<title><function>&mac.mpo;_check_vnode_link</function></title>
<funcsynopsis>
@@ -6275,7 +6263,7 @@ Label destruction o</programlisting>
the name specified by <parameter>cnp</parameter>.</para>
</sect3>
- <sect3 id="mac-mpo-check-vnode-mmap">
+ <sect3 xml:id="mac-mpo-check-vnode-mmap">
<title><function>&mac.mpo;_check_vnode_mmap</function></title>
<funcsynopsis>
@@ -6327,7 +6315,7 @@ Label destruction o</programlisting>
specified in <parameter>prot</parameter>.</para>
</sect3>
- <sect3 id="mac-mpo-check-vnode-mmap-downgrade">
+ <sect3 xml:id="mac-mpo-check-vnode-mmap-downgrade">
<title><function>&mac.mpo;_check_vnode_mmap_downgrade</function></title>
<funcsynopsis>
@@ -6376,7 +6364,7 @@ Label destruction o</programlisting>
object labels.</para>
</sect3>
- <sect3 id="mac-mpo-check-vnode-mprotect">
+ <sect3 xml:id="mac-mpo-check-vnode-mprotect">
<title><function>&mac.mpo;_check_vnode_mprotect</function></title>
<funcsynopsis>
@@ -6422,7 +6410,7 @@ Label destruction o</programlisting>
the vnode <parameter>vp</parameter>.</para>
</sect3>
- <sect3 id="mac-mpo-check-vnode-poll">
+ <sect3 xml:id="mac-mpo-check-vnode-poll">
<title><function>&mac.mpo;_check_vnode_poll</function></title>
<funcsynopsis>
@@ -6475,7 +6463,7 @@ Label destruction o</programlisting>
the vnode <parameter>vp</parameter>.</para>
</sect3>
- <sect3 id="mac-mpo-check-vnode-rename-from">
+ <sect3 xml:id="mac-mpo-check-vnode-rename-from">
<title><function>&mac.mpo;_check_vnode_rename_from</function></title>
<funcsynopsis>
@@ -6544,7 +6532,7 @@ Label destruction o</programlisting>
else.</para>
</sect3>
- <sect3 id="mac-mpo-check-vnode-rename-to">
+ <sect3 xml:id="mac-mpo-check-vnode-rename-to">
<title><function>&mac.mpo;_check_vnode_rename_to</function></title>
<funcsynopsis>
@@ -6622,7 +6610,7 @@ Label destruction o</programlisting>
<parameter>label</parameter> will be NULL.</para>
</sect3>
- <sect3 id="mac-mpo-cred-check-socket-listen">
+ <sect3 xml:id="mac-mpo-cred-check-socket-listen">
<title><function>&mac.mpo;_check_socket_listen</function></title>
<funcsynopsis>
@@ -6671,7 +6659,7 @@ Label destruction o</programlisting>
privilege.</para>
</sect3>
- <sect3 id="mac-mpo-cred-check-vnode-lookup">
+ <sect3 xml:id="mac-mpo-cred-check-vnode-lookup">
<title><function>&mac.mpo;_check_vnode_lookup</function></title>
<funcsynopsis>
@@ -6680,11 +6668,11 @@ Label destruction o</programlisting>
<function>&mac.mpo;_check_vnode_lookup</function></funcdef>
<paramdef>struct ucred
- *<parameter></parameter>cred</paramdef>
+ *<parameter/>cred</paramdef>
<paramdef>struct vnode
- *<parameter></parameter>dvp</paramdef>
+ *<parameter/>dvp</paramdef>
<paramdef>struct label
- *<parameter></parameter>dlabel</paramdef>
+ *<parameter/>dlabel</paramdef>
<paramdef>struct componentname
*<parameter>cnp</parameter></paramdef>
</funcprototype>
@@ -6728,7 +6716,7 @@ Label destruction o</programlisting>
privilege.</para>
</sect3>
- <sect3 id="mac-mpo-cred-check-vnode-open">
+ <sect3 xml:id="mac-mpo-cred-check-vnode-open">
<title><function>&mac.mpo;_check_vnode_open</function></title>
<funcsynopsis>
@@ -6784,7 +6772,7 @@ Label destruction o</programlisting>
<errorcode>EPERM</errorcode> for lack of privilege.</para>
</sect3>
- <sect3 id="mac-mpo-cred-check-vnode-readdir">
+ <sect3 xml:id="mac-mpo-cred-check-vnode-readdir">
<title><function>&mac.mpo;_check_vnode_readdir</function></title>
<funcsynopsis>
@@ -6793,11 +6781,11 @@ Label destruction o</programlisting>
<function>&mac.mpo;_check_vnode_readdir</function></funcdef>
<paramdef>struct ucred
- *<parameter></parameter>cred</paramdef>
+ *<parameter/>cred</paramdef>
<paramdef>struct vnode
- *<parameter></parameter>dvp</paramdef>
+ *<parameter/>dvp</paramdef>
<paramdef>struct label
- *<parameter></parameter>dlabel</paramdef>
+ *<parameter/>dlabel</paramdef>
</funcprototype>
</funcsynopsis>
@@ -6834,7 +6822,7 @@ Label destruction o</programlisting>
privilege.</para>
</sect3>
- <sect3 id="mac-mpo-cred-check-vnode-readlink">
+ <sect3 xml:id="mac-mpo-cred-check-vnode-readlink">
<title><function>&mac.mpo;_check_vnode_readlink</function></title>
<funcsynopsis>
@@ -6888,7 +6876,7 @@ Label destruction o</programlisting>
process.</para>
</sect3>
- <sect3 id="mac-mpo-cred-check-vnode-revoke">
+ <sect3 xml:id="mac-mpo-cred-check-vnode-revoke">
<title><function>&mac.mpo;_check_vnode_revoke</function></title>
<funcsynopsis>
@@ -6938,7 +6926,7 @@ Label destruction o</programlisting>
privilege.</para>
</sect3>
- <sect3 id="mac-mpo-cred-check-vnode-setacl">
+ <sect3 xml:id="mac-mpo-cred-check-vnode-setacl">
<title><function>&mac.mpo;_check_vnode_setacl</function></title>
<funcsynopsis>
@@ -7002,7 +6990,7 @@ Label destruction o</programlisting>
privilege.</para>
</sect3>
- <sect3 id="mac-mpo-cred-check-vnode-setextattr">
+ <sect3 xml:id="mac-mpo-cred-check-vnode-setextattr">
<title><function>&mac.mpo;_check_vnode_setextattr</function></title>
<funcsynopsis>
@@ -7080,7 +7068,7 @@ Label destruction o</programlisting>
privilege.</para>
</sect3>
- <sect3 id="mac-mpo-cred-check-vnode-setflags">
+ <sect3 xml:id="mac-mpo-cred-check-vnode-setflags">
<title><function>&mac.mpo;_check_vnode_setflags</function></title>
<funcsynopsis>
@@ -7136,7 +7124,7 @@ Label destruction o</programlisting>
privilege.</para>
</sect3>
- <sect3 id="mac-mpo-cred-check-vnode-setmode">
+ <sect3 xml:id="mac-mpo-cred-check-vnode-setmode">
<title><function>&mac.mpo;_check_vnode_setmode</function></title>
<funcsynopsis>
@@ -7191,7 +7179,7 @@ Label destruction o</programlisting>
privilege.</para>
</sect3>
- <sect3 id="mac-mpo-cred-check-vnode-setowner">
+ <sect3 xml:id="mac-mpo-cred-check-vnode-setowner">
<title><function>&mac.mpo;_check_vnode_setowner</function></title>
<funcsynopsis>
@@ -7253,7 +7241,7 @@ Label destruction o</programlisting>
of privilege.</para>
</sect3>
- <sect3 id="mac-mpo-cred-check-vnode-setutimes">
+ <sect3 xml:id="mac-mpo-cred-check-vnode-setutimes">
<title><function>&mac.mpo;_check_vnode_setutimes</function></title>
<funcsynopsis>
@@ -7262,15 +7250,15 @@ Label destruction o</programlisting>
<function>&mac.mpo;_check_vnode_setutimes</function></funcdef>
<paramdef>struct ucred
- *<parameter></parameter>cred</paramdef>
+ *<parameter/>cred</paramdef>
<paramdef>struct vnode
- *<parameter></parameter>vp</paramdef>
+ *<parameter/>vp</paramdef>
<paramdef>struct label
- *<parameter></parameter>label</paramdef>
+ *<parameter/>label</paramdef>
<paramdef>struct timespec
- <parameter></parameter>atime</paramdef>
+ <parameter/>atime</paramdef>
<paramdef>struct timespec
- <parameter></parameter>mtime</paramdef>
+ <parameter/>mtime</paramdef>
</funcprototype>
</funcsynopsis>
@@ -7317,7 +7305,7 @@ Label destruction o</programlisting>
privilege.</para>
</sect3>
- <sect3 id="mac-mpo-cred-check-proc-sched">
+ <sect3 xml:id="mac-mpo-cred-check-proc-sched">
<title><function>&mac.mpo;_check_proc_sched</function></title>
<funcsynopsis>
@@ -7361,7 +7349,7 @@ Label destruction o</programlisting>
<para>See &man.setpriority.2; for more information.</para>
</sect3>
- <sect3 id="mac-mpo-cred-check-proc-signal">
+ <sect3 xml:id="mac-mpo-cred-check-proc-signal">
<title><function>&mac.mpo;_check_proc_signal</function></title>
<funcsynopsis>
@@ -7409,7 +7397,7 @@ Label destruction o</programlisting>
<errorcode>ESRCH</errorcode> to limit visibility.</para>
</sect3>
- <sect3 id="mac-mpo-cred-check-vnode-stat">
+ <sect3 xml:id="mac-mpo-cred-check-vnode-stat">
<title><function>&mac.mpo;_check_vnode_stat</function></title>
<funcsynopsis>
@@ -7461,7 +7449,7 @@ Label destruction o</programlisting>
<para>See &man.stat.2; for more information.</para>
</sect3>
- <sect3 id="mac-mpo-cred-check-ifnet-transmit">
+ <sect3 xml:id="mac-mpo-cred-check-ifnet-transmit">
<title><function>&mac.mpo;_check_ifnet_transmit</function></title>
<funcsynopsis>
@@ -7525,7 +7513,7 @@ Label destruction o</programlisting>
privilege.</para>
</sect3>
- <sect3 id="mac-mpo-cred-check-socket-deliver">
+ <sect3 xml:id="mac-mpo-cred-check-socket-deliver">
<title><function>&mac.mpo;_check_socket_deliver</function></title>
<funcsynopsis>
@@ -7590,7 +7578,7 @@ Label destruction o</programlisting>
privilege.</para>
</sect3>
- <sect3 id="mac-mpo-check-socket-visible">
+ <sect3 xml:id="mac-mpo-check-socket-visible">
<title><function>&mac.mpo;_check_socket_visible</function></title>
<funcsynopsis>
@@ -7643,7 +7631,7 @@ Label destruction o</programlisting>
<errorcode>ESRCH</errorcode> to hide visibility.</para>
</sect3>
- <sect3 id="mac-mpo-check-system-acct">
+ <sect3 xml:id="mac-mpo-check-system-acct">
<title><function>&mac.mpo;_check_system_acct</function></title>
<funcsynopsis>
@@ -7689,7 +7677,7 @@ Label destruction o</programlisting>
accounting log file.</para>
</sect3>
- <sect3 id="mac-mpo-check-system-nfsd">
+ <sect3 xml:id="mac-mpo-check-system-nfsd">
<title><function>&mac.mpo;_check_system_nfsd</function></title>
<funcsynopsis>
@@ -7719,7 +7707,7 @@ Label destruction o</programlisting>
&man.nfssvc.2;.</para>
</sect3>
- <sect3 id="mac-mpo-check-system-reboot">
+ <sect3 xml:id="mac-mpo-check-system-reboot">
<title><function>&mac.mpo;_check_system_reboot</function></title>
<funcsynopsis>
@@ -7756,7 +7744,7 @@ Label destruction o</programlisting>
reboot the system in the specified manner.</para>
</sect3>
- <sect3 id="mac-mpo-check-system-settime">
+ <sect3 xml:id="mac-mpo-check-system-settime">
<title><function>&mac.mpo;_check_system_settime</function></title>
<funcsynopsis>
@@ -7786,7 +7774,7 @@ Label destruction o</programlisting>
system clock.</para>
</sect3>
- <sect3 id="mac-mpo-check-system-swapon">
+ <sect3 xml:id="mac-mpo-check-system-swapon">
<title><function>&mac.mpo;_check_system_swapon</function></title>
<funcsynopsis>
@@ -7831,7 +7819,7 @@ Label destruction o</programlisting>
<parameter>vp</parameter> as a swap device.</para>
</sect3>
- <sect3 id="mac-mpo-check-system-sysctl">
+ <sect3 xml:id="mac-mpo-check-system-sysctl">
<title><function>&mac.mpo;_check_system_sysctl</function></title>
<funcsynopsis>
@@ -7902,7 +7890,7 @@ Label destruction o</programlisting>
</sect3>
</sect2>
- <sect2 id="mac-label-management">
+ <sect2 xml:id="mac-label-management">
<title>Label Management Calls</title>
<para>Relabel events occur when a user process has requested
@@ -7919,7 +7907,7 @@ Label destruction o</programlisting>
</sect2>
</sect1>
- <sect1 id="mac-userland-arch">
+ <sect1 xml:id="mac-userland-arch">
<title>Userland Architecture</title>
<para>The TrustedBSD MAC Framework includes a number of
@@ -7931,7 +7919,7 @@ Label destruction o</programlisting>
interfaces. More details on the user architecture will
be added to this section in the near future.</para>
- <sect2 id="mac-userland-labels">
+ <sect2 xml:id="mac-userland-labels">
<title>APIs for Policy-Agnostic Label Management</title>
<para>The TrustedBSD MAC Framework provides a number of
@@ -7980,7 +7968,7 @@ Label destruction o</programlisting>
writers.</para></note>
</sect2>
- <sect2 id="mac-userland-credentials">
+ <sect2 xml:id="mac-userland-credentials">
<title>Binding of Labels to Users</title>
<para>The standard user context management interface,
@@ -8001,7 +7989,7 @@ Label destruction o</programlisting>
</sect2>
</sect1>
- <sect1 id="mac-conclusion">
+ <sect1 xml:id="mac-conclusion">
<title>Conclusion</title>
<para>The TrustedBSD MAC framework permits kernel modules to
diff --git a/en_US.ISO8859-1/books/arch-handbook/newbus/chapter.xml b/en_US.ISO8859-1/books/arch-handbook/newbus/chapter.xml
index 48df641aa6..e038e49f2f 100644
--- a/en_US.ISO8859-1/books/arch-handbook/newbus/chapter.xml
+++ b/en_US.ISO8859-1/books/arch-handbook/newbus/chapter.xml
@@ -22,27 +22,18 @@
Provided under the FreeBSD Documentation License.
-->
-<chapter id="newbus">
- <chapterinfo>
+<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:id="newbus">
+ <info><title>Newbus</title>
<authorgroup>
- <author>
- <firstname>Jeroen</firstname>
- <surname>Ruigrok van der Werven (asmodai)</surname>
- <affiliation>
+ <author><personname><firstname>Jeroen</firstname><surname>Ruigrok van der Werven (asmodai)</surname></personname><affiliation>
<address><email>asmodai@FreeBSD.org</email></address>
- </affiliation>
- <contrib>Written by </contrib>
- </author>
- <author>
- <firstname>Hiten</firstname>
- <surname>Pandya</surname>
- <affiliation>
+ </affiliation><contrib>Written by </contrib></author>
+ <author><personname><firstname>Hiten</firstname><surname>Pandya</surname></personname><affiliation>
<address><email>hiten@uk.FreeBSD.org</email></address>
- </affiliation>
- </author>
+ </affiliation></author>
</authorgroup>
- </chapterinfo>
- <title>Newbus</title>
+ </info>
+
<para><emphasis>Special thanks to Matthew N. Dodd, Warner Losh, Bill
Paul, Doug Rabson, Mike Smith, Peter Wemm and Scott
@@ -51,7 +42,7 @@
<para>This chapter explains the Newbus device framework in
detail.</para>
- <sect1 id="newbus-devdrivers">
+ <sect1 xml:id="newbus-devdrivers">
<title>Device Drivers</title>
<sect2>
@@ -106,7 +97,7 @@
</sect2>
</sect1>
- <sect1 id="newbus-overview">
+ <sect1 xml:id="newbus-overview">
<!--
Real title:
Newbus, Busspace and the Resource Manager, an Explanation of the Possibilities
@@ -161,9 +152,9 @@
device, which normally has one child for the attached bus. An
example of this is a <emphasis>PCI-to-PCI bridge</emphasis>
which is represented by a device
- <emphasis><devicename>pcibN</devicename></emphasis> on the
+ <emphasis><filename>pcibN</filename></emphasis> on the
parent PCI bus and has a child
- <emphasis><devicename>pciN</devicename></emphasis> for the
+ <emphasis><filename>pciN</filename></emphasis> for the
attached bus. This layout simplifies the implementation of the
PCI bus tree, allowing common code to be used for both top-level
and bridged busses.</para>
@@ -203,8 +194,8 @@
<para>This support is integrated into the resource allocation
mechanism. When a resource is allocated, a driver can retrieve
- the associated <structfield>bus_space_tag_t</structfield> and
- <structfield>bus_space_handle_t</structfield> from the
+ the associated <varname remap="structfield">bus_space_tag_t</varname> and
+ <varname remap="structfield">bus_space_handle_t</varname> from the
resource.</para>
<para>Newbus also allows for definitions of interface methods in
@@ -319,7 +310,7 @@
accessing the configuration registers of a PCI device.</para>
</sect1>
- <sect1 id="newbus-api">
+ <sect1 xml:id="newbus-api">
<title>Newbus API</title>
<para>As the Newbus API is huge, this section makes some effort at
diff --git a/en_US.ISO8859-1/books/arch-handbook/pccard/chapter.xml b/en_US.ISO8859-1/books/arch-handbook/pccard/chapter.xml
index b894c1e68e..a9a2753d9a 100644
--- a/en_US.ISO8859-1/books/arch-handbook/pccard/chapter.xml
+++ b/en_US.ISO8859-1/books/arch-handbook/pccard/chapter.xml
@@ -4,8 +4,7 @@
$FreeBSD$
-->
-
-<chapter id="pccard">
+<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:id="pccard">
<title>PC Card</title>
<indexterm><primary>PC Card</primary></indexterm>
@@ -16,14 +15,14 @@
at present it just documents how to add a new device to an
existing pccard driver.</para>
- <sect1 id="pccard-adddev">
+ <sect1 xml:id="pccard-adddev">
<title>Adding a Device</title>
<para>Device drivers know what devices they support. There is a
table of supported devices in the kernel that drivers use to
attach to a device.</para>
- <sect2 id="pccard-overview">
+ <sect2 xml:id="pccard-overview">
<title>Overview</title>
<indexterm><primary>CIS</primary></indexterm>
@@ -85,7 +84,7 @@
adding new devices, prefer using the numeric method.</para>
</sect2>
- <sect2 id="pccard-pccarddevs">
+ <sect2 xml:id="pccard-pccarddevs">
<title>Format of <filename>pccarddevs</filename></title>
<para>There are four sections in the
@@ -199,7 +198,7 @@ product ALLIEDTELESIS WR211PCM { "Allied&amp;spTelesis&amp;spK.K.", "WR211PCM",
available at this time.</para>
</sect2>
- <sect2 id="pccard-probe">
+ <sect2 xml:id="pccard-probe">
<title>Sample Probe Routine</title>
<indexterm>
@@ -248,11 +247,11 @@ wi_pccard_probe(dev)
the rest of the driver, so there may be some variance in the
table. The only requirement is that each row of the table
must have a <function>struct</function>
- <structname>pccard_product</structname> as the first
+ <varname remap="structname">pccard_product</varname> as the first
element.</para>
<para>Looking at the table
- <structname>wi_pccard_products</structname>, one notices that
+ <varname remap="structname">wi_pccard_products</varname>, one notices that
all the entries are of the form
<function>PCMCIA_CARD(<replaceable>foo</replaceable>,
<replaceable>bar</replaceable>,
@@ -273,7 +272,7 @@ wi_pccard_probe(dev)
description from pccarddevs</quote> flavors.</para>
</sect2>
- <sect2 id="pccard-add">
+ <sect2 xml:id="pccard-add">
<title>Putting it All Together</title>
<para>To add a new device, one must first obtain the
@@ -348,7 +347,7 @@ product BUFFALO WLI_CF_S11G 0x030b BUFFALO AirStation 11Mbps CF WLAN</programlis
Finally, commit the additions to the driver.</para>
</sect2>
- <sect2 id="pccard-pr">
+ <sect2 xml:id="pccard-pr">
<title>Submitting a New Device</title>
<para>Please do not send entries for new devices to the author
diff --git a/en_US.ISO8859-1/books/arch-handbook/pci/chapter.xml b/en_US.ISO8859-1/books/arch-handbook/pci/chapter.xml
index 15a70da312..592096c867 100644
--- a/en_US.ISO8859-1/books/arch-handbook/pci/chapter.xml
+++ b/en_US.ISO8859-1/books/arch-handbook/pci/chapter.xml
@@ -4,8 +4,7 @@
$FreeBSD$
-->
-
-<chapter id="pci">
+<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:id="pci">
<title>PCI Devices</title>
<indexterm><primary>PCI bus</primary></indexterm>
@@ -13,7 +12,7 @@
<para>This chapter will talk about the FreeBSD mechanisms for
writing a device driver for a device on a PCI bus.</para>
- <sect1 id="pci-probe">
+ <sect1 xml:id="pci-probe">
<title>Probe and Attach</title>
<para>Information here about how the PCI bus code iterates through
@@ -253,8 +252,8 @@ SRCS+= device_if.h bus_if.h pci_if.h
<sect2>
<title>Additional Resources</title>
<itemizedlist>
- <listitem><simpara><ulink url="http://www.pcisig.org/">PCI
- Special Interest Group</ulink></simpara></listitem>
+ <listitem><simpara><link xlink:href="http://www.pcisig.org/">PCI
+ Special Interest Group</link></simpara></listitem>
<listitem><simpara>PCI System Architecture, Fourth Edition by
Tom Shanley, et al.</simpara></listitem>
@@ -263,7 +262,7 @@ SRCS+= device_if.h bus_if.h pci_if.h
</sect2>
</sect1>
- <sect1 id="pci-bus">
+ <sect1 xml:id="pci-bus">
<title>Bus Resources</title>
<indexterm><primary>PCI bus</primary><secondary>resources</secondary></indexterm>
@@ -310,7 +309,7 @@ SRCS+= device_if.h bus_if.h pci_if.h
sc-&gt;bar1_bh = rman_get_bushandle(sc-&gt;bar1res);</programlisting>
<para>Handles for each base address register are kept in the
- <structname>softc</structname> structure so that they can be
+ <varname remap="structname">softc</varname> structure so that they can be
used to write to the device later.</para>
<para>These handles can then be used to read or write from the
@@ -346,7 +345,7 @@ board_write(struct ni_softc *sc, uint16_t address, uint16_t value)
<function>bus_*</function> functions take a <type>struct
resource *</type> pointer instead of a bus tag and handle.
Thus, you could drop the bus tag and bus handle members from
- the <structname>softc</structname> and rewrite the
+ the <varname remap="structname">softc</varname> and rewrite the
<function>board_read()</function> function as:</para>
<programlisting>uint16_t
diff --git a/en_US.ISO8859-1/books/arch-handbook/scsi/chapter.xml b/en_US.ISO8859-1/books/arch-handbook/scsi/chapter.xml
index 8e94b8904e..f29a4c88cd 100644
--- a/en_US.ISO8859-1/books/arch-handbook/scsi/chapter.xml
+++ b/en_US.ISO8859-1/books/arch-handbook/scsi/chapter.xml
@@ -4,28 +4,19 @@
$FreeBSD$
-->
-
-<chapter id="scsi">
- <chapterinfo>
+<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:id="scsi">
+ <info><title>Common Access Method SCSI Controllers</title>
<authorgroup>
- <author>
- <firstname>Sergey</firstname>
- <surname>Babkin</surname>
- <contrib>Written by </contrib>
- </author>
+ <author><personname><firstname>Sergey</firstname><surname>Babkin</surname></personname><contrib>Written by </contrib></author>
</authorgroup>
<authorgroup>
- <author>
- <firstname>Murray</firstname>
- <surname>Stokely</surname>
- <contrib>Modifications for Handbook made by </contrib>
- </author>
+ <author><personname><firstname>Murray</firstname><surname>Stokely</surname></personname><contrib>Modifications for Handbook made by </contrib></author>
</authorgroup>
- </chapterinfo>
+ </info>
- <title>Common Access Method SCSI Controllers</title>
+
- <sect1 id="scsi-synopsis">
+ <sect1 xml:id="scsi-synopsis">
<title>Synopsis</title>
<indexterm><primary>SCSI</primary></indexterm>
@@ -71,7 +62,7 @@
can be found in the real drivers.</para>
</sect1>
- <sect1 id="scsi-general">
+ <sect1 xml:id="scsi-general">
<title>General Architecture</title>
<indexterm>
@@ -163,17 +154,17 @@
}</programlisting>
<para>Note that if we are not able to create a SIM descriptor we
- free the <structname>devq</structname> also because we can do
+ free the <varname remap="structname">devq</varname> also because we can do
nothing else with it and we want to conserve memory.</para>
<para>If a SCSI card has multiple SCSI
buses<indexterm><primary>SCSI</primary><secondary>bus</secondary></indexterm>
on it then each bus requires its own
- <structname>cam_sim</structname> structure.</para>
+ <varname remap="structname">cam_sim</varname> structure.</para>
<para>An interesting question is what to do if a SCSI card has
more than one SCSI bus, do we need one
- <structname>devq</structname> structure per card or per SCSI
+ <varname remap="structname">devq</varname> structure per card or per SCSI
bus? The answer given in the comments to the CAM code is:
either way, as the driver's author prefers.</para>
@@ -218,7 +209,7 @@
</listitem>
<listitem>
- <para><structname>softc</structname> - pointer to the driver's
+ <para><varname remap="structname">softc</varname> - pointer to the driver's
internal descriptor for this SCSI card. This pointer will
be used by the driver in future to get private
data.</para>
@@ -262,7 +253,7 @@
error; /* some code to handle the error */
}</programlisting>
- <para>If there is one <structname>devq</structname> structure per
+ <para>If there is one <varname remap="structname">devq</varname> structure per
SCSI bus (i.e., we consider a card with multiple buses as
multiple cards with one bus each) then the bus number will
always be 0, otherwise each bus on the SCSI card should be get a
@@ -270,7 +261,7 @@
cam_sim.</para>
<para>After that our controller is completely hooked to the CAM
- system. The value of <structname>devq</structname> can be
+ system. The value of <varname remap="structname">devq</varname> can be
discarded now: sim will be passed as an argument in all further
calls from CAM and devq can be derived from it.</para>
@@ -339,7 +330,7 @@
bus.</para>
<para>And we save the path pointer in the
- <structname>softc</structname> structure for future use. After
+ <varname remap="structname">softc</varname> structure for future use. After
that we save the value of sim (or we can also discard it on the
exit from <function>xxx_probe()</function> if we wish).</para>
@@ -426,7 +417,7 @@
these functions.</para>
<para>The type of request is stored in
- <structfield>ccb-&gt;ccb_h.func_code</structfield>. So
+ <varname remap="structfield">ccb-&gt;ccb_h.func_code</varname>. So
generally <function>xxx_action()</function> consists of a big
switch:</para>
@@ -446,7 +437,7 @@
<para>As can be seen from the default case (if an unknown command
was received) the return code of the command is set into
- <structfield>ccb-&gt;ccb_h.status</structfield> and the
+ <varname remap="structfield">ccb-&gt;ccb_h.status</varname> and the
completed CCB is returned back to CAM by calling
<function>xpt_done(ccb)</function>.</para>
@@ -1626,7 +1617,7 @@
</itemizedlist>
</sect1>
- <sect1 id="scsi-polling">
+ <sect1 xml:id="scsi-polling">
<title>Polling</title>
<funcsynopsis>
@@ -1652,7 +1643,7 @@
<function>xxx_poll</function> routine gets the struct cam_sim
pointer as its argument when the PCI interrupt routine by common
convention gets pointer to the struct
- <structname>xxx_softc</structname> and the ISA interrupt routine
+ <varname remap="structname">xxx_softc</varname> and the ISA interrupt routine
gets just the device unit number. So the poll routine would
normally look as:</para>
@@ -1671,7 +1662,7 @@ xxx_poll(struct cam_sim *sim)
}</programlisting>
</sect1>
- <sect1 id="scsi-async">
+ <sect1 xml:id="scsi-async">
<title>Asynchronous Events</title>
<para>If an asynchronous event callback has been set up then the
@@ -1728,7 +1719,7 @@ ahc_async(void *callback_arg, u_int32_t code, struct cam_path *path, void *arg)<
}</programlisting>
</sect1>
- <sect1 id="scsi-interrupts">
+ <sect1 xml:id="scsi-interrupts">
<title>Interrupts</title>
<indexterm><primary>SCSI</primary><secondary>interrupts</secondary></indexterm>
@@ -2093,7 +2084,7 @@ ahc_async(void *callback_arg, u_int32_t code, struct cam_path *path, void *arg)<
specific controllers may require some additions.</para>
</sect1>
- <sect1 id="scsi-errors">
+ <sect1 xml:id="scsi-errors">
<title>Errors Summary</title>
<indexterm><primary>SCSI</primary><secondary>errors</secondary></indexterm>
@@ -2208,7 +2199,7 @@ ahc_async(void *callback_arg, u_int32_t code, struct cam_path *path, void *arg)<
</itemizedlist>
</sect1>
- <sect1 id="scsi-timeout">
+ <sect1 xml:id="scsi-timeout">
<title>Timeout Handling</title>
<para>When the timeout for an HCB expires that request should be
diff --git a/en_US.ISO8859-1/books/arch-handbook/smp/chapter.xml b/en_US.ISO8859-1/books/arch-handbook/smp/chapter.xml
index f6ab5e9985..6c1256b045 100644
--- a/en_US.ISO8859-1/books/arch-handbook/smp/chapter.xml
+++ b/en_US.ISO8859-1/books/arch-handbook/smp/chapter.xml
@@ -5,18 +5,11 @@
$FreeBSD$
-->
-<chapter id="smp">
- <chapterinfo>
+<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:id="smp">
+ <info><title>SMPng Design Document</title>
<authorgroup>
- <author>
- <firstname>John</firstname>
- <surname>Baldwin</surname>
- <contrib>Written by </contrib>
- </author>
- <author>
- <firstname>Robert</firstname>
- <surname>Watson</surname>
- </author>
+ <author><personname><firstname>John</firstname><surname>Baldwin</surname></personname><contrib>Written by </contrib></author>
+ <author><personname><firstname>Robert</firstname><surname>Watson</surname></personname></author>
</authorgroup>
<copyright>
@@ -26,11 +19,11 @@
<holder>John Baldwin</holder>
<holder>Robert Watson</holder>
</copyright>
- </chapterinfo>
+ </info>
- <title>SMPng Design Document</title>
+
- <sect1 id="smp-intro">
+ <sect1 xml:id="smp-intro">
<title>Introduction</title>
<indexterm><primary>SMP Next Generation</primary></indexterm>
@@ -64,7 +57,7 @@
the <xref linkend="smp-glossary"/> section of this article.</para>
</sect1>
- <sect1 id="smp-lock-fundamentals">
+ <sect1 xml:id="smp-lock-fundamentals">
<title>Basic Tools and Locking Fundamentals</title>
<sect2>
@@ -105,7 +98,7 @@
<function>atomic_cmpset</function> rather than an
<function>atomic_set</function> to turn on the
<constant>MTX_CONTESTED</constant> bit. The reason is that we
- read the value of <structfield>mtx_lock</structfield> into a
+ read the value of <varname remap="structfield">mtx_lock</varname> into a
variable and then make a decision based on that read.
However, the value we read may be stale, or it may change
while we are making our decision. Thus, when the
@@ -172,7 +165,7 @@
</sect2>
</sect1>
- <sect1 id="smp-design">
+ <sect1 xml:id="smp-design">
<title>General Architecture and Design</title>
<sect2>
@@ -498,7 +491,7 @@
</sect2>
</sect1>
- <sect1 id="smp-lock-strategies">
+ <sect1 xml:id="smp-lock-strategies">
<title>Specific Locking Strategies</title>
<sect2>
@@ -506,7 +499,7 @@
<indexterm><primary>credentials</primary></indexterm>
- <para><structname>struct ucred</structname> is the kernel's
+ <para><varname remap="structname">struct ucred</varname> is the kernel's
internal credential structure, and is generally used as the
basis for process-driven access control within the kernel.
BSD-derived systems use a <quote>copy-on-write</quote> model
@@ -524,35 +517,35 @@
<para>Credential structures with a single reference are
considered mutable; shared credential structures must not be
modified or a race condition is risked. A mutex,
- <structfield>cr_mtxp</structfield> protects the reference
- count of <structname>struct ucred</structname> so as to
+ <varname remap="structfield">cr_mtxp</varname> protects the reference
+ count of <varname remap="structname">struct ucred</varname> so as to
maintain consistency. Any use of the structure requires a
valid reference for the duration of the use, or the structure
may be released out from under the illegitimate
consumer.</para>
- <para>The <structname>struct ucred</structname> mutex is a leaf
+ <para>The <varname remap="structname">struct ucred</varname> mutex is a leaf
mutex and is implemented via a mutex pool for performance
reasons.</para>
<para>Usually, credentials are used in a read-only manner for access
control decisions, and in this case
- <structfield>td_ucred</structfield> is generally preferred
+ <varname remap="structfield">td_ucred</varname> is generally preferred
because it requires no locking. When a process' credential is
updated the <literal>proc</literal> lock must be held across
the check and update operations thus avoid races. The process
- credential <structfield>p_ucred</structfield> must be used for
+ credential <varname remap="structfield">p_ucred</varname> must be used for
check and update operations to prevent time-of-check,
time-of-use races.</para>
<para>If system call invocations will perform access control after
an update to the process credential, the value of
- <structfield>td_ucred</structfield> must also be refreshed to
+ <varname remap="structfield">td_ucred</varname> must also be refreshed to
the current process value. This will prevent use of a stale
credential following a change. The kernel automatically
- refreshes the <structfield>td_ucred</structfield> pointer in
+ refreshes the <varname remap="structfield">td_ucred</varname> pointer in
the thread structure from the process
- <structfield>p_ucred</structfield> whenever a process enters
+ <varname remap="structfield">p_ucred</varname> whenever a process enters
the kernel, permitting use of a fresh credential for kernel
access control.</para>
</sect2>
@@ -568,17 +561,17 @@
<indexterm><primary>Jail</primary></indexterm>
- <para><structname>struct prison</structname> stores
+ <para><varname remap="structname">struct prison</varname> stores
administrative details pertinent to the maintenance of jails
created using the &man.jail.2; API. This includes the
per-jail hostname, IP address, and related settings. This
structure is reference-counted since pointers to instances of
the structure are shared by many credential structures. A
- single mutex, <structfield>pr_mtx</structfield> protects read
+ single mutex, <varname remap="structfield">pr_mtx</varname> protects read
and write access to the reference count and all mutable
variables inside the struct jail. Some variables are set only
when the jail is created, and a valid reference to the
- <structname>struct prison</structname> is sufficient to read
+ <varname remap="structname">struct prison</varname> is sufficient to read
these values. The precise locking of each entry is documented
via comments in <filename>sys/jail.h</filename>.</para>
</sect2>
@@ -589,11 +582,11 @@
<indexterm><primary>MAC</primary></indexterm>
<para>The TrustedBSD MAC Framework maintains data in a variety
- of kernel objects, in the form of <structname>struct
- label</structname>. In general, labels in kernel objects
+ of kernel objects, in the form of <varname remap="structname">struct
+ label</varname>. In general, labels in kernel objects
are protected by the same lock as the remainder of the kernel
- object. For example, the <structfield>v_label</structfield>
- label in <structname>struct vnode</structname> is protected
+ object. For example, the <varname remap="structfield">v_label</varname>
+ label in <varname remap="structname">struct vnode</varname> is protected
by the vnode lock on the vnode.</para>
<para>In addition to labels maintained in standard kernel objects,
@@ -636,8 +629,8 @@
added to make access to the lock more easy. These macros can be
located in <filename>sys/module.h</filename> and are quite basic
in terms of usage. The main structures protected under this lock
- are the <structname>module_t</structname> structures (when shared)
- and the global <structname>modulelist_t</structname> structure,
+ are the <varname remap="structname">module_t</varname> structures (when shared)
+ and the global <varname remap="structname">modulelist_t</varname> structure,
modules. One should review the related source code in
<filename>kern/kern_module.c</filename> to further understand the
locking strategy.</para>
@@ -710,27 +703,27 @@
referred to as the owner. Each object supporting SIGIO
registration contains pointer field that is
<constant>NULL</constant> if the object is not registered, or
- points to a <structname>struct sigio</structname> describing
+ points to a <varname remap="structname">struct sigio</varname> describing
the registration. This field is protected by a global mutex,
<varname>sigio_lock</varname>. Callers to SIGIO maintenance
functions must pass in this field <quote>by reference</quote>
so that local register copies of the field are not made when
unprotected by the lock.</para>
- <para>One <structname>struct sigio</structname> is allocated for
+ <para>One <varname remap="structname">struct sigio</varname> is allocated for
each registered object associated with any process or process
group, and contains back-pointers to the object, owner, signal
information, a credential, and the general disposition of the
registration. Each process or progress group contains a list of
- registered <structname>struct sigio</structname> structures,
- <structfield>p_sigiolst</structfield> for processes, and
- <structfield>pg_sigiolst</structfield> for process groups.
+ registered <varname remap="structname">struct sigio</varname> structures,
+ <varname remap="structfield">p_sigiolst</varname> for processes, and
+ <varname remap="structfield">pg_sigiolst</varname> for process groups.
These lists are protected by the process or process group
- locks respectively. Most fields in each <structname>struct
- sigio</structname> are constant for the duration of the
+ locks respectively. Most fields in each <varname remap="structname">struct
+ sigio</varname> are constant for the duration of the
registration, with the exception of the
- <structfield>sio_pgsigio</structfield> field which links the
- <structname>struct sigio</structname> into the process or
+ <varname remap="structfield">sio_pgsigio</varname> field which links the
+ <varname remap="structname">struct sigio</varname> into the process or
process group list. Developers implementing new kernel
objects supporting SIGIO will, in general, want to avoid
holding structure locks while invoking SIGIO supporting
@@ -786,17 +779,17 @@
<varname>taskqueue_queues_mutex</varname> is meant to serve as a
lock to protect the <varname>taskqueue_queues</varname> TAILQ.
The other mutex lock associated with this system is the one in the
- <structname>struct taskqueue</structname> data structure. The
+ <varname remap="structname">struct taskqueue</varname> data structure. The
use of the synchronization primitive here is to protect the
- integrity of the data in the <structname>struct
- taskqueue</structname>. It should be noted that there are no
+ integrity of the data in the <varname remap="structname">struct
+ taskqueue</varname>. It should be noted that there are no
separate macros to assist the user in locking down his/her own work
since these locks are most likely not going to be used outside of
<filename>kern/subr_taskqueue.c</filename>.</para>
</sect2>
</sect1>
- <sect1 id="smp-implementation-notes">
+ <sect1 xml:id="smp-implementation-notes">
<title>Implementation Notes</title>
<sect2>
@@ -1004,7 +997,7 @@
</sect2>
</sect1>
- <sect1 id="smp-misc">
+ <sect1 xml:id="smp-misc">
<title>Miscellaneous Topics</title>
<sect2>
@@ -1027,10 +1020,10 @@
</sect2>
</sect1>
- <glossary id="smp-glossary">
+ <glossary xml:id="smp-glossary">
<title>Glossary</title>
- <glossentry id="smp-glossary-atomic">
+ <glossentry xml:id="smp-glossary-atomic">
<glossterm>atomic</glossterm>
<glossdef>
<para>An operation is atomic if all of its effects are visible
@@ -1046,7 +1039,7 @@
</glossdef>
</glossentry>
- <glossentry id="smp-glossary-block">
+ <glossentry xml:id="smp-glossary-block">
<glossterm>block</glossterm>
<glossdef>
<para>A thread is blocked when it is waiting on a lock,
@@ -1057,7 +1050,7 @@
</glossdef>
</glossentry>
- <glossentry id="smp-glossary-critical-section">
+ <glossentry xml:id="smp-glossary-critical-section">
<glossterm>critical section</glossterm>
<glossdef>
<para>A section of code that is not allowed to be preempted.
@@ -1066,7 +1059,7 @@
</glossdef>
</glossentry>
- <glossentry id="smp-glossary-MD">
+ <glossentry xml:id="smp-glossary-MD">
<glossterm>MD</glossterm>
<glossdef>
<para>Machine dependent.</para>
@@ -1075,7 +1068,7 @@
</glossdef>
</glossentry>
- <glossentry id="smp-glossary-memory-operation">
+ <glossentry xml:id="smp-glossary-memory-operation">
<glossterm>memory operation</glossterm>
<glossdef>
<para>A memory operation reads and/or writes to a memory
@@ -1083,7 +1076,7 @@
</glossdef>
</glossentry>
- <glossentry id="smp-glossary-MI">
+ <glossentry xml:id="smp-glossary-MI">
<glossterm>MI</glossterm>
<glossdef>
<para>Machine independent.</para>
@@ -1092,12 +1085,12 @@
</glossdef>
</glossentry>
- <glossentry id="smp-glossary-operation">
+ <glossentry xml:id="smp-glossary-operation">
<glossterm>operation</glossterm>
<glosssee>memory operation</glosssee>
</glossentry>
- <glossentry id="smp-glossary-primary-interrupt-context">
+ <glossentry xml:id="smp-glossary-primary-interrupt-context">
<glossterm>primary interrupt context</glossterm>
<glossdef>
<para>Primary interrupt context refers to the code that runs
@@ -1118,7 +1111,7 @@
</glossdef>
</glossentry>
- <glossentry id="smp-glossary-sleep">
+ <glossentry xml:id="smp-glossary-sleep">
<glossterm>sleep</glossterm>
<glossdef>
<para>A thread is asleep when it is blocked on a condition
@@ -1129,7 +1122,7 @@
</glossdef>
</glossentry>
- <glossentry id="smp-glossary-sleepable-lock">
+ <glossentry xml:id="smp-glossary-sleepable-lock">
<glossterm>sleepable lock</glossterm>
<glossdef>
<para>A sleepable lock is a lock that can be held by a thread
@@ -1142,7 +1135,7 @@
</glossdef>
</glossentry>
- <glossentry id="smp-glossary-thread">
+ <glossentry xml:id="smp-glossary-thread">
<glossterm>thread</glossterm>
<glossdef>
<para>A kernel thread represented by a struct thread. Threads own
@@ -1150,7 +1143,7 @@
</glossdef>
</glossentry>
- <glossentry id="smp-glossary-wait-channel">
+ <glossentry xml:id="smp-glossary-wait-channel">
<glossterm>wait channel</glossterm>
<glossdef>
<para>A kernel virtual address that threads may sleep on.</para>
diff --git a/en_US.ISO8859-1/books/arch-handbook/sound/chapter.xml b/en_US.ISO8859-1/books/arch-handbook/sound/chapter.xml
index aca69c4450..488e437f64 100644
--- a/en_US.ISO8859-1/books/arch-handbook/sound/chapter.xml
+++ b/en_US.ISO8859-1/books/arch-handbook/sound/chapter.xml
@@ -4,22 +4,17 @@
$FreeBSD$
-->
-
-<chapter id="oss">
- <chapterinfo>
+<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:id="oss">
+ <info><title>Sound Subsystem</title>
<authorgroup>
- <author>
- <firstname>Jean-Francois</firstname>
- <surname>Dockes</surname>
- <contrib>Contributed by </contrib>
- </author>
+ <author><personname><firstname>Jean-Francois</firstname><surname>Dockes</surname></personname><contrib>Contributed by </contrib></author>
</authorgroup>
- <!-- 23 November 2001 -->
- </chapterinfo>
+
+ </info>
- <title>Sound Subsystem</title>
+
- <sect1 id="oss-intro">
+ <sect1 xml:id="oss-intro">
<title>Introduction</title>
<indexterm><primary>sound subsystem</primary></indexterm>
@@ -62,10 +57,10 @@
<para>The support for specific sound cards is implemented by
hardware-specific drivers, which provide channel and mixer
- interfaces to plug into the generic <devicename>pcm</devicename>
+ interfaces to plug into the generic <filename>pcm</filename>
code.</para>
- <para>In this chapter, the term <devicename>pcm</devicename> will
+ <para>In this chapter, the term <filename>pcm</filename> will
refer to the central, common part of the sound driver, as
opposed to the hardware-specific modules.</para>
@@ -78,11 +73,11 @@
<para>As an alternative, or in addition to starting from a working
example, you can find a commented driver template at
- <ulink url="http://people.FreeBSD.org/~cg/template.c">
- http://people.FreeBSD.org/~cg/template.c</ulink></para>
+ <link xlink:href="http://people.FreeBSD.org/~cg/template.c">
+ http://people.FreeBSD.org/~cg/template.c</link></para>
</sect1>
- <sect1 id="oss-files">
+ <sect1 xml:id="oss-files">
<title>Files</title>
<para>All the relevant code lives in
@@ -97,22 +92,20 @@
for PCI and ISA boards, and for USB audio devices.</para>
</sect1>
- <sect1 id="pcm-probe-and-attach">
+ <sect1 xml:id="pcm-probe-and-attach">
<title>Probing, Attaching, etc.</title>
<para>Sound drivers probe and attach in almost the same way as any
- hardware driver module. You might want to look at the <link
- linkend="isa-driver"> ISA</link> or <link
- linkend="pci">PCI</link> specific sections of the handbook for
+ hardware driver module. You might want to look at the <link linkend="isa-driver"> ISA</link> or <link linkend="pci">PCI</link> specific sections of the handbook for
more information.</para>
<para>However, sound drivers differ in some ways:</para>
<itemizedlist>
<listitem>
- <para>They declare themselves as <devicename>pcm</devicename>
+ <para>They declare themselves as <filename>pcm</filename>
class devices, with a
- <structname>struct snddev_info</structname> device private
+ <varname remap="structname">struct snddev_info</varname> device private
structure:</para>
<programlisting> static driver_t xxx_driver = {
@@ -129,29 +122,28 @@
need to store additional private information about their
device. A private data structure is usually allocated in
the attach routine. Its address is passed to
- <devicename>pcm</devicename> by the calls to
+ <filename>pcm</filename> by the calls to
<function>pcm_register()</function> and
<function>mixer_init()</function>.
- <devicename>pcm</devicename> later passes back this address
+ <filename>pcm</filename> later passes back this address
as a parameter in calls to the sound driver
interfaces.</para>
</listitem>
<listitem>
<para>The sound driver attach routine should declare its MIXER
- or AC97 interface to <devicename>pcm</devicename> by calling
+ or AC97 interface to <filename>pcm</filename> by calling
<function>mixer_init()</function>. For a MIXER interface,
- this causes in turn a call to <link
- linkend="xxxmixer-init"><function>xxxmixer_init()</function></link>.</para>
+ this causes in turn a call to <link linkend="xxxmixer-init"><function>xxxmixer_init()</function></link>.</para>
</listitem>
<listitem>
<para>The sound driver attach routine declares its general
- CHANNEL configuration to <devicename>pcm</devicename> by
+ CHANNEL configuration to <filename>pcm</filename> by
calling <function>pcm_register(dev, sc, nplay,
nrec)</function>, where <varname>sc</varname> is the address
for the device data structure, used in further calls from
- <devicename>pcm</devicename>, and <varname>nplay</varname>
+ <filename>pcm</filename>, and <varname>nplay</varname>
and <varname>nrec</varname> are the number of play and
record channels.</para>
</listitem>
@@ -160,7 +152,7 @@
<para>The sound driver attach routine declares each of its
channel objects by calls to
<function>pcm_addchan()</function>. This sets up the
- channel glue in <devicename>pcm</devicename> and causes in
+ channel glue in <filename>pcm</filename> and causes in
turn a call to
<link linkend="xxxchannel-init">
<function>xxxchannel_init()</function></link>.</para>
@@ -193,19 +185,18 @@
</listitem>
</itemizedlist>
- <para><devicename>pcm</devicename> drivers should implement
+ <para><filename>pcm</filename> drivers should implement
<function>device_suspend</function>,
<function>device_resume</function> and
<function>device_shutdown</function> routines, so that power
management and module unloading function correctly.</para>
</sect1>
- <sect1 id="oss-interfaces">
+ <sect1 xml:id="oss-interfaces">
<title>Interfaces</title>
- <para>The interface between the <devicename>pcm</devicename> core
- and the sound drivers is defined in terms of <link
- linkend="kernel-objects">kernel objects</link>.</para>
+ <para>The interface between the <filename>pcm</filename> core
+ and the sound drivers is defined in terms of <link linkend="kernel-objects">kernel objects</link>.</para>
<para>There are two main interfaces that a sound driver will
usually provide: <emphasis>CHANNEL</emphasis> and either
@@ -215,7 +206,7 @@
hardware access (register read/write) interface, implemented by
drivers for hardware with an AC97 codec. In this case, the
actual MIXER interface is provided by the shared AC97 code in
- <devicename>pcm</devicename>.</para>
+ <filename>pcm</filename>.</para>
<sect2>
<title>The CHANNEL Interface</title>
@@ -235,19 +226,19 @@
<function>channel_init()</function> which has a pointer to
the private device structure (and returns the channel
pointer for further use by
- <devicename>pcm</devicename>).</para>
+ <filename>pcm</filename>).</para>
</sect3>
<sect3>
<title>Overview of Data Transfer Operations</title>
<para>For sound data transfers, the
- <devicename>pcm</devicename> core and the sound drivers
+ <filename>pcm</filename> core and the sound drivers
communicate through a shared memory area, described by a
- <structname>struct snd_dbuf</structname>.</para>
+ <varname remap="structname">struct snd_dbuf</varname>.</para>
- <para><structname>struct snd_dbuf</structname> is private to
- <devicename>pcm</devicename>, and sound drivers obtain
+ <para><varname remap="structname">struct snd_dbuf</varname> is private to
+ <filename>pcm</filename>, and sound drivers obtain
values of interest by calls to accessor functions
(<function>sndbuf_getxxx()</function>).</para>
@@ -261,9 +252,8 @@
<itemizedlist>
<listitem>
- <para><devicename>pcm</devicename> initially fills up the
- buffer, then calls the sound driver's <link
- linkend="channel-trigger">
+ <para><filename>pcm</filename> initially fills up the
+ buffer, then calls the sound driver's <link linkend="channel-trigger">
<function>xxxchannel_trigger()</function></link>
function with a parameter of PCMTRIG_START.</para>
</listitem>
@@ -275,7 +265,7 @@
<function>sndbuf_getsize()</function>) to the device, in
blocks of <function>sndbuf_getblksz()</function> bytes.
It calls back the <function>chn_intr()</function>
- <devicename>pcm</devicename> function for each
+ <filename>pcm</filename> function for each
transferred block (this will typically happen at
interrupt time).</para>
</listitem>
@@ -284,12 +274,12 @@
<para><function>chn_intr()</function> arranges to copy new
data to the area that was transferred to the device (now
free), and make appropriate updates to the
- <structname>snd_dbuf</structname> structure.</para>
+ <varname remap="structname">snd_dbuf</varname> structure.</para>
</listitem>
</itemizedlist>
</sect3>
- <sect3 id="xxxchannel-init">
+ <sect3 xml:id="xxxchannel-init">
<title>channel_init</title>
<para><function>xxxchannel_init()</function> is called to
@@ -300,28 +290,28 @@
<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 xml:id="co-chinit-params"/>
{
struct xxx_info *sc = data;
struct xxx_chinfo *ch;
...
- return ch;<co id="co-chinit-return"/>
+ return ch;<co xml:id="co-chinit-return"/>
}</programlisting>
<calloutlist>
<callout arearefs="co-chinit-params">
<para><varname>b</varname> is the address for the channel
- <structname>struct snd_dbuf</structname>. It should be
+ <varname remap="structname">struct snd_dbuf</varname>. It should be
initialized in the function by calling
<function>sndbuf_alloc()</function>. The buffer size to
use is normally a small multiple of the 'typical' unit
transfer size for your device.</para>
<para><varname>c</varname> is the
- <devicename>pcm</devicename> channel control structure
+ <filename>pcm</filename> channel control structure
pointer. This is an opaque object. The function should
store it in the local channel structure, to be used in
- later calls to <devicename>pcm</devicename> (ie:
+ later calls to <filename>pcm</filename> (ie:
<function>chn_intr(c)</function>).</para>
<para><varname>dir</varname> indicates the channel
@@ -345,7 +335,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 xml:id="co-chsetformat-params"/>
{
struct xxx_chinfo *ch = data;
...
@@ -382,11 +372,11 @@
<para><function>xxxchannel_setblocksize()</function> sets the
block size, which is the size of unit transactions between
- <devicename>pcm</devicename> and the sound driver, and
+ <filename>pcm</filename> and the sound driver, and
between the sound driver and the device. Typically, this
would be the number of bytes transferred before an interrupt
occurs. During a transfer, the sound driver should call
- <devicename>pcm</devicename>'s
+ <filename>pcm</filename>'s
<function>chn_intr()</function> every time this size has
been transferred.</para>
@@ -399,7 +389,7 @@
{
struct xxx_chinfo *ch = data;
...
- return blocksize;<co id="co-chsetblocksize-return"/>
+ return blocksize;<co xml:id="co-chsetblocksize-return"/>
}</programlisting>
<calloutlist>
@@ -412,15 +402,15 @@
</calloutlist>
</sect3>
- <sect3 id="channel-trigger">
+ <sect3 xml:id="channel-trigger">
<title>channel_trigger</title>
<para><function>xxxchannel_trigger()</function> is called by
- <devicename>pcm</devicename> to control data transfer
+ <filename>pcm</filename> to control data transfer
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 xml:id="co-chtrigger-params"/>
{
struct xxx_chinfo *ch = data;
...
@@ -473,7 +463,7 @@
<para><function>xxxchannel_getptr()</function> returns the
current offset in the transfer buffer. This will typically
be called by <function>chn_intr()</function>, and this is
- how <devicename>pcm</devicename> knows where it can transfer
+ how <filename>pcm</filename> knows where it can transfer
new data.</para>
</sect3>
@@ -494,7 +484,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 xml:id="co-chgetcaps-return"/>
}</programlisting>
<calloutlist>
@@ -502,7 +492,7 @@
<callout arearefs="co-chgetcaps-return">
<para>The routine returns a pointer to a (usually
statically-defined)
- <structname>pcmchan_caps</structname> structure (defined
+ <varname remap="structname">pcmchan_caps</varname> structure (defined
in <filename>sound/pcm/channel.h</filename>. The
structure holds the minimum and maximum sampling
frequencies, and the accepted sound formats. Look at
@@ -528,11 +518,11 @@
<sect2>
<title>The MIXER Interface</title>
- <sect3 id="xxxmixer-init">
+ <sect3 xml:id="xxxmixer-init">
<title>mixer_init</title>
<para><function>xxxmixer_init()</function> initializes the
- hardware and tells <devicename>pcm</devicename> what mixer
+ hardware and tells <filename>pcm</filename> what mixer
devices are available for playing and recording</para>
<programlisting> static int
@@ -543,7 +533,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 xml:id="co-mxini-sd"/>
mix_setdevs(m, v);
[Set appropriate bits in v for record mixers]
mix_setrecdevs(m, v)
@@ -556,7 +546,7 @@
<para>Set bits in an integer value and call
<function>mix_setdevs()</function> and
<function>mix_setrecdevs()</function> to tell
- <devicename>pcm</devicename> what devices exist.</para>
+ <filename>pcm</filename> what devices exist.</para>
</callout>
</calloutlist>
@@ -574,11 +564,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 xml: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 xml:id="co-mxset-return"/>
}</programlisting>
<calloutlist>
@@ -607,14 +597,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 xml: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 xml:id="co-mxsr-return"/>
}</programlisting>
<calloutlist>
@@ -668,7 +658,7 @@
</itemizedlist>
<para>The <emphasis>AC97</emphasis> interface is used by the
- AC97 code in <devicename>pcm</devicename> to perform higher
+ AC97 code in <filename>pcm</filename> to perform higher
level operations. Look at
<filename>sound/pci/maestro3.c</filename> or many others under
<filename>sound/pci/</filename> for an example.</para>
diff --git a/en_US.ISO8859-1/books/arch-handbook/sysinit/chapter.xml b/en_US.ISO8859-1/books/arch-handbook/sysinit/chapter.xml
index 7898ee7e2e..66a61dce18 100644
--- a/en_US.ISO8859-1/books/arch-handbook/sysinit/chapter.xml
+++ b/en_US.ISO8859-1/books/arch-handbook/sysinit/chapter.xml
@@ -4,8 +4,7 @@
$FreeBSD$
-->
-
-<chapter id="sysinit">
+<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:id="sysinit">
<title>The SYSINIT Framework</title>
<indexterm><primary>SYSINIT</primary></indexterm>
@@ -28,7 +27,7 @@
using the <quote>kernel linker</quote> and <quote>linker
sets</quote>.</para>
- <sect1 id="sysinit-term">
+ <sect1 xml:id="sysinit-term">
<title>Terminology</title>
<variablelist>
@@ -44,7 +43,7 @@
</variablelist>
</sect1>
- <sect1 id="sysinit-operation">
+ <sect1 xml:id="sysinit-operation">
<title>SYSINIT Operation</title>
<indexterm><primary>linker sets</primary></indexterm>
@@ -86,7 +85,7 @@
</sect1>
- <sect1 id="sysinit-using">
+ <sect1 xml:id="sysinit-using">
<title>Using SYSINIT</title>
<sect2>
diff --git a/en_US.ISO8859-1/books/arch-handbook/usb/chapter.xml b/en_US.ISO8859-1/books/arch-handbook/usb/chapter.xml
index 61c244bf8b..8cf67b0500 100644
--- a/en_US.ISO8859-1/books/arch-handbook/usb/chapter.xml
+++ b/en_US.ISO8859-1/books/arch-handbook/usb/chapter.xml
@@ -4,28 +4,19 @@
$FreeBSD$
-->
-
-<chapter id="usb">
- <chapterinfo>
+<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:id="usb">
+ <info><title>USB Devices</title>
<authorgroup>
- <author>
- <firstname>Nick</firstname>
- <surname>Hibma</surname>
- <contrib>Written by </contrib>
- </author>
+ <author><personname><firstname>Nick</firstname><surname>Hibma</surname></personname><contrib>Written by </contrib></author>
</authorgroup>
<authorgroup>
- <author>
- <firstname>Murray</firstname>
- <surname>Stokely</surname>
- <contrib>Modifications for Handbook made by </contrib>
- </author>
+ <author><personname><firstname>Murray</firstname><surname>Stokely</surname></personname><contrib>Modifications for Handbook made by </contrib></author>
</authorgroup>
- </chapterinfo>
+ </info>
- <title>USB Devices</title>
+
- <sect1 id="usb-intro">
+ <sect1 xml:id="usb-intro">
<title>Introduction</title>
<indexterm><primary>Universal Serial Bus (USB)</primary></indexterm>
@@ -123,7 +114,7 @@
</sect2>
</sect1>
- <sect1 id="usb-hc">
+ <sect1 xml:id="usb-hc">
<title>Host Controllers</title>
<indexterm><primary>USB</primary><secondary>host controllers</secondary></indexterm>
@@ -141,9 +132,8 @@
which the recipient of the data can return either ACK
(acknowledge reception), NAK (retry), STALL (error condition) or
nothing (garbled data stage, device not available or
- disconnected). Section 8.5 of the <ulink
- url="http://www.usb.org/developers/docs.html">USB
- specification</ulink> explains the details of packets in more
+ disconnected). Section 8.5 of the <link xlink:href="http://www.usb.org/developers/docs.html">USB
+ specification</link> explains the details of packets in more
detail. Four different types of transfers can occur on a USB
bus: control, bulk, interrupt and isochronous. The types of
transfers and their characteristics are described below (`Pipes'
@@ -170,11 +160,9 @@
to it. It returns the standard andhub class specific set of
descriptors. It should also provide an interrupt pipe that
reports changes happening at its ports. There are currently two
- specifications for host controllers available: <ulink
- url="http://developer.intel.com/design/USB/UHCI11D.htm">Universal
- Host Controller Interface</ulink> (UHCI; Intel) and <ulink
- url="http://www.compaq.com/productinfo/development/openhci.html">Open
- Host Controller Interface</ulink> (OHCI; Compaq, Microsoft,
+ specifications for host controllers available: <link xlink:href="http://developer.intel.com/design/USB/UHCI11D.htm">Universal
+ Host Controller Interface</link> (UHCI; Intel) and <link xlink:href="http://www.compaq.com/productinfo/development/openhci.html">Open
+ Host Controller Interface</link> (OHCI; Compaq, Microsoft,
National Semiconductor). The UHCI specification has been
designed to reduce hardware complexity by requiring the host
controller driver to supply a complete schedule of the transfers
@@ -232,9 +220,8 @@
service routine will locate all the finished transfers and
call their callbacks.</para>
- <para>See for a more elaborate description the <ulink
- url="http://developer.intel.com/design/USB/UHCI11D.htm">UHCI
- specification.</ulink></para>
+ <para>See for a more elaborate description the <link xlink:href="http://developer.intel.com/design/USB/UHCI11D.htm">UHCI
+ specification.</link></para>
</sect2>
@@ -276,9 +263,8 @@
transfer and reschedule interrupt and isochronous
endpoints.</para>
- <para>See for a more elaborate description the <ulink
- url="http://www.compaq.com/productinfo/development/openhci.html">
- OHCI specification</ulink>. Services layer The middle layer
+ <para>See for a more elaborate description the <link xlink:href="http://www.compaq.com/productinfo/development/openhci.html">
+ OHCI specification</link>. Services layer The middle layer
provides access to the device in a controlled way and
maintains resources in use by the different drivers and the
services layer. The layer takes care of the following
@@ -296,7 +282,7 @@
</sect2>
</sect1>
- <sect1 id="usb-dev">
+ <sect1 xml:id="usb-dev">
<title>USB Device Information</title>
<sect2>
@@ -465,7 +451,7 @@
</sect2>
</sect1>
- <sect1 id="usb-devprobe">
+ <sect1 xml:id="usb-devprobe">
<title>Device Probe and Attach</title>
<indexterm><primary>USB</primary><secondary>probe</secondary></indexterm>
@@ -536,7 +522,7 @@
</sect2>
</sect1>
- <sect1 id="usb-protocol">
+ <sect1 xml:id="usb-protocol">
<title>USB Drivers Protocol Information</title>
<para>The protocol used over pipes other than the default pipe is
diff --git a/en_US.ISO8859-1/books/arch-handbook/vm/chapter.xml b/en_US.ISO8859-1/books/arch-handbook/vm/chapter.xml
index 39ec4fba3c..52c44fca29 100644
--- a/en_US.ISO8859-1/books/arch-handbook/vm/chapter.xml
+++ b/en_US.ISO8859-1/books/arch-handbook/vm/chapter.xml
@@ -4,22 +4,17 @@
$FreeBSD$
-->
-
-<chapter id="vm">
- <chapterinfo>
+<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:id="vm">
+ <info><title>Virtual Memory System</title>
<authorgroup>
- <author>
- <firstname>Matthew</firstname>
- <surname>Dillon</surname>
- <contrib>Contributed by </contrib>
- </author>
+ <author><personname><firstname>Matthew</firstname><surname>Dillon</surname></personname><contrib>Contributed by </contrib></author>
</authorgroup>
- <!-- 6 Feb 1999 -->
- </chapterinfo>
+
+ </info>
- <title>Virtual Memory System</title>
+
- <sect1 id="vm-physmem">
+ <sect1 xml:id="vm-physmem">
<title>Management of Physical
Memory&mdash;<literal>vm_page_t</literal></title>
@@ -86,7 +81,7 @@
launder or swap-out a page.</para>
</sect1>
- <sect1 id="vm-cache">
+ <sect1 xml:id="vm-cache">
<title>The Unified Buffer
Cache&mdash;<literal>vm_object_t</literal></title>
@@ -113,7 +108,7 @@
instances.</para>
</sect1>
- <sect1 id="vm-fileio">
+ <sect1 xml:id="vm-fileio">
<title>Filesystem I/O&mdash;<literal>struct buf</literal></title>
<indexterm><primary>vnode</primary></indexterm>
@@ -149,7 +144,7 @@
problem.</para>
</sect1>
- <sect1 id="vm-pagetables">
+ <sect1 xml:id="vm-pagetables">
<title>Mapping Page Tables&mdash;<literal>vm_map_t, vm_entry_t</literal></title>
<indexterm><primary>page tables</primary></indexterm>
@@ -176,7 +171,7 @@
across the board.</para>
</sect1>
- <sect1 id="vm-kvm">
+ <sect1 xml:id="vm-kvm">
<title>KVM Memory Mapping</title>
<para>FreeBSD uses KVM to hold various kernel structures. The single
@@ -198,7 +193,7 @@
overview of current KVM utilization broken down by zone.</para>
</sect1>
- <sect1 id="vm-tuning">
+ <sect1 xml:id="vm-tuning">
<title>Tuning the FreeBSD VM System</title>
<para>A concerted effort has been made to make the FreeBSD kernel
@@ -206,7 +201,7 @@
anything beyond the <option>maxusers</option> and
<option>NMBCLUSTERS</option> kernel config options. That is, kernel
compilation options specified in (typically)
- <filename>/usr/src/sys/i386/conf/<replaceable>CONFIG_FILE</replaceable></filename>.
+ <filename>/usr/src/sys/i386/conf/CONFIG_FILE</filename>.
A description of all available kernel configuration options can be
found in <filename>/usr/src/sys/i386/conf/LINT</filename>.</para>
diff --git a/en_US.ISO8859-1/books/design-44bsd/book.xml b/en_US.ISO8859-1/books/design-44bsd/book.xml
index 04637580a8..7de5641d8e 100644
--- a/en_US.ISO8859-1/books/design-44bsd/book.xml
+++ b/en_US.ISO8859-1/books/design-44bsd/book.xml
@@ -1,37 +1,20 @@
<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE book PUBLIC "-//FreeBSD//DTD DocBook XML V4.5-Based Extension//EN"
- "../../../share/xml/freebsd45.dtd">
-
+<!DOCTYPE book PUBLIC "-//FreeBSD//DTD DocBook XML V5.0-Based Extension//EN"
+ "../../../share/xml/freebsd50.dtd">
<!-- $FreeBSD$ -->
<!-- FreeBSD Documentation Project -->
-
-<book lang='en'>
- <bookinfo>
- <title>The Design and Implementation of the 4.4BSD Operating System</title>
+<book xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:lang="en">
+ <info><title>The Design and Implementation of the 4.4BSD Operating System</title>
+
<authorgroup>
- <author>
- <firstname>Marshall</firstname>
- <othername>Kirk</othername>
- <surname>McKusick</surname>
- </author>
-
- <author>
- <firstname>Keith</firstname>
- <surname>Bostic</surname>
- </author>
-
- <author>
- <firstname>Michael</firstname>
- <othername>J.</othername>
- <surname>Karels</surname>
- </author>
-
- <author>
- <firstname>John</firstname>
- <othername>S.</othername>
- <surname>Quarterman</surname>
- </author>
+ <author><personname><firstname>Marshall</firstname><othername>Kirk</othername><surname>McKusick</surname></personname></author>
+
+ <author><personname><firstname>Keith</firstname><surname>Bostic</surname></personname></author>
+
+ <author><personname><firstname>Michael</firstname><othername>J.</othername><surname>Karels</surname></personname></author>
+
+ <author><personname><firstname>John</firstname><othername>S.</othername><surname>Quarterman</surname></personname></author>
</authorgroup>
<copyright>
@@ -39,34 +22,33 @@
<holder>Addison-Wesley Longman, Inc</holder>
</copyright>
-<!-- I seem to recall the editor wanting this notice to be bold. In html, I'd
- use the _strong_ tag. What should I use instead? -->
- <legalnotice id="legalnotice">
+
+ <legalnotice xml:id="legalnotice">
<para>The second chapter of the book, <citetitle>The Design and
Implementation of the 4.4BSD Operating System</citetitle> is
excerpted here with the permission of the publisher. No part of it
may be further reproduced or distributed without the publisher's
express written
- <ulink url="mailto:peter.gordon@awl.com">permission</ulink>. The
+ <link xlink:href="mailto:peter.gordon@awl.com">permission</link>. The
rest of
- <ulink url="http://cseng.aw.com/catalog/academic/product/0,1144,0201549794,00.html">the
- book</ulink> explores the concepts introduced in this chapter in
+ <link xlink:href="http://cseng.aw.com/catalog/academic/product/0,1144,0201549794,00.html">the
+ book</link> explores the concepts introduced in this chapter in
incredible detail and is an excellent reference for anyone with an
interest in BSD UNIX. More information about this book is available
from the publisher, with whom you can also sign up to receive news
- of <ulink url="mailto:curt.johnson@awl.com">related titles</ulink>.
- Information about <ulink url="http://www.mckusick.com/courses/">BSD
- courses</ulink> is available from Kirk McKusick.</para>
+ of <link xlink:href="mailto:curt.johnson@awl.com">related titles</link>.
+ Information about <link xlink:href="http://www.mckusick.com/courses/">BSD
+ courses</link> is available from Kirk McKusick.</para>
</legalnotice>
<releaseinfo>$FreeBSD$</releaseinfo>
- </bookinfo>
+ </info>
- <chapter id="overview" label="2">
+ <chapter xml:id="overview" label="2">
<title>Design Overview of 4.4BSD</title>
- <sect1 id="overview-facilities">
+ <sect1 xml:id="overview-facilities">
<title>4.4BSD Facilities and the Kernel</title>
<para>The 4.4BSD kernel provides four basic facilities:
@@ -223,7 +205,7 @@
</sect2>
</sect1>
- <sect1 id="overview-kernel-organization">
+ <sect1 xml:id="overview-kernel-organization">
<title>Kernel Organization</title>
<para>In this section, we view the organization of the 4.4BSD
@@ -288,7 +270,7 @@
</listitem>
</itemizedlist>
- <table frame="none" id="table-mach-indep">
+ <table frame="none" xml:id="table-mach-indep">
<title>Machine-independent software in the 4.4BSD kernel</title>
<tgroup cols="3">
<thead>
@@ -466,7 +448,7 @@
</listitem>
</itemizedlist>
- <table frame="none" id="table-mach-dep">
+ <table frame="none" xml:id="table-mach-dep">
<title>Machine-dependent software for the HP300 in the 4.4BSD
kernel</title>
@@ -568,7 +550,7 @@
in places logically associated with what is being initialized.</para>
</sect1>
- <sect1 id="overview-kernel-service">
+ <sect1 xml:id="overview-kernel-service">
<title>Kernel Services</title>
<para>The boundary between the kernel- and user-level code is enforced by
@@ -635,7 +617,7 @@
invisible to the processes involved.</para>
</sect1>
- <sect1 id="overview-process-management">
+ <sect1 xml:id="overview-process-management">
<title>Process Management</title>
<para>4.4BSD supports a multitasking environment.
@@ -672,7 +654,7 @@
Important components of the kernel state are described in
Chapter 4.</para>
- <figure id="fig-process-lifecycle">
+ <figure xml:id="fig-process-lifecycle">
<title>Process lifecycle</title>
<mediaobject>
@@ -682,13 +664,13 @@
<textobject>
<literallayout class="monospaced">+----------------+ wait +----------------+
-| parent process |--------------------------------->| parent process |--->
+| parent process |---------------------------------&gt;| parent process |---&gt;
+----------------+ +----------------+
| ^
| fork |
V |
+----------------+ execve +----------------+ wait +----------------+
-| child process |------->| child process |------->| zombie process |
+| child process |-------&gt;| child process |-------&gt;| zombie process |
+----------------+ +----------------+ +----------------+</literallayout>
</textobject>
@@ -899,7 +881,7 @@
</sect2>
</sect1>
- <sect1 id="overview-memory-management">
+ <sect1 xml:id="overview-memory-management">
<title>Memory Management</title>
<para>Each process has its own private address space.
@@ -1120,7 +1102,7 @@
</sect2>
</sect1>
- <sect1 id="overview-io-system">
+ <sect1 xml:id="overview-io-system">
<title>I/O System</title>
<para>The basic model of the UNIX
@@ -1633,7 +1615,7 @@
</sect2>
</sect1>
- <sect1 id="overview-filesystem">
+ <sect1 xml:id="overview-filesystem">
<title>Filesystems</title>
<para>A regular file is a linear array of bytes,
@@ -1658,7 +1640,7 @@
A hierarchy of directories and files is thus formed, and is called a
<emphasis>filesystem</emphasis>;</para>
- <figure id="fig-small-fs">
+ <figure xml:id="fig-small-fs">
<title>A small filesystem</title>
<mediaobject>
@@ -1979,7 +1961,7 @@
in addition to the natural desire of users
to give files long descriptive names,
a common way of forming filenames is as
- <filename><replaceable>basename</replaceable>.<replaceable>extension</replaceable></filename>,
+ <filename>basename.extension</filename>,
where the extension (indicating the kind of file, such as
<literal>.c</literal>
for C source or
@@ -2019,7 +2001,7 @@
first introduced in 4.2BSD practically eliminate it.</para>
</sect1>
- <sect1 id="overview-filestore">
+ <sect1 xml:id="overview-filestore">
<title>Filestores</title>
<para>The operations defined for local filesystems are divided into two parts.
@@ -2078,7 +2060,7 @@
the usage of virtual-memory resources.</para>
</sect1>
- <sect1 id="overview-nfs">
+ <sect1 xml:id="overview-nfs">
<title>Network Filesystem</title>
<para>Initially, networking was used
@@ -2136,7 +2118,7 @@
</para>
</sect1>
- <sect1 id="overview-terminal">
+ <sect1 xml:id="overview-terminal">
<title>Terminals</title>
<para>Terminals support the standard system I/O operations, as well
@@ -2221,7 +2203,7 @@
</sect1>
- <sect1 id="overview-ipc">
+ <sect1 xml:id="overview-ipc">
<title>Interprocess Communication</title>
<para>Interprocess communication in 4.4BSD is organized in
@@ -2315,7 +2297,7 @@
Microsoft's Winsock networking interface for Windows.</para>
</sect1>
- <sect1 id="overview-network-communication">
+ <sect1 xml:id="overview-network-communication">
<title>Network Communication</title>
<para>Some of the communication domains supported by the
@@ -2350,7 +2332,7 @@
running with a newer network protocol.</para>
</sect1>
- <sect1 id="overview-network-implementation">
+ <sect1 xml:id="overview-network-implementation">
<title>Network Implementation</title>
<para>The first protocol suite implemented in 4.2BSD was
@@ -2408,7 +2390,7 @@
network masks.</para>
</sect1>
- <sect1 id="overview-operation">
+ <sect1 xml:id="overview-operation">
<title>System Operation</title>
<para>Bootstrapping mechanisms are used to start the system running.
@@ -2435,163 +2417,112 @@
the user can run additional processes.</para>
</sect1>
- <bibliography id="references">
+ <bibliography xml:id="references">
<title>References</title>
- <biblioentry id="biblio-accetta">
+ <biblioentry xml:id="biblio-accetta">
<abbrev>Accetta et al, 1986</abbrev>
<biblioset relation="article">
- <title>Mach: A New Kernel Foundation for UNIX Development"</title>
+ <citetitle>Mach: A New Kernel Foundation for UNIX Development"</citetitle>
<authorgroup>
- <author>
- <firstname>M. </firstname>
- <surname>Accetta</surname>
- </author>
- <author>
- <firstname>R.</firstname>
- <surname>Baron</surname>
- </author>
- <author>
- <firstname>W.</firstname>
- <surname>Bolosky</surname>
- </author>
- <author>
- <firstname>D.</firstname>
- <surname>Golub</surname>
- </author>
- <author>
- <firstname>R.</firstname>
- <surname>Rashid</surname>
- </author>
- <author>
- <firstname>A.</firstname>
- <surname>Tevanian</surname>
- </author>
- <author>
- <firstname>M.</firstname>
- <surname>Young</surname>
- </author>
+ <author><personname><firstname>M. </firstname><surname>Accetta</surname></personname></author>
+ <author><personname><firstname>R.</firstname><surname>Baron</surname></personname></author>
+ <author><personname><firstname>W.</firstname><surname>Bolosky</surname></personname></author>
+ <author><personname><firstname>D.</firstname><surname>Golub</surname></personname></author>
+ <author><personname><firstname>R.</firstname><surname>Rashid</surname></personname></author>
+ <author><personname><firstname>A.</firstname><surname>Tevanian</surname></personname></author>
+ <author><personname><firstname>M.</firstname><surname>Young</surname></personname></author>
</authorgroup>
<pagenums>93-113</pagenums>
</biblioset>
<biblioset relation="journal">
- <title>USENIX Association Conference Proceedings</title>
+ <citetitle>USENIX Association Conference Proceedings</citetitle>
<publishername>USENIX Association</publishername>
<pubdate>June 1986</pubdate>
</biblioset>
</biblioentry>
- <biblioentry id="biblio-cheriton">
+ <biblioentry xml:id="biblio-cheriton">
<abbrev>Cheriton, 1988</abbrev>
<biblioset relation="article">
- <title>The V Distributed System</title>
+ <citetitle>The V Distributed System</citetitle>
- <author>
- <firstname>D. R.</firstname>
- <surname>Cheriton</surname>
- </author>
+ <author><personname><firstname>D. R.</firstname><surname>Cheriton</surname></personname></author>
<pagenums>314-333</pagenums>
</biblioset>
<biblioset relation="journal">
- <title>Comm ACM, 31, 3</title>
+ <citetitle>Comm ACM, 31, 3</citetitle>
<pubdate>March 1988</pubdate>
</biblioset>
</biblioentry>
- <biblioentry id="biblio-ewens">
+ <biblioentry xml:id="biblio-ewens">
<abbrev>Ewens et al, 1985</abbrev>
<biblioset relation="article">
- <title>Tunis: A Distributed Multiprocessor Operating System</title>
+ <citetitle>Tunis: A Distributed Multiprocessor Operating System</citetitle>
<authorgroup>
- <author>
- <firstname>P.</firstname>
- <surname>Ewens</surname>
- </author>
-
- <author>
- <firstname>D. R.</firstname>
- <surname>Blythe</surname>
- </author>
-
- <author>
- <firstname>M.</firstname>
- <surname>Funkenhauser</surname>
- </author>
-
- <author>
- <firstname>R. C.</firstname>
- <surname>Holt</surname>
- </author>
+ <author><personname><firstname>P.</firstname><surname>Ewens</surname></personname></author>
+
+ <author><personname><firstname>D. R.</firstname><surname>Blythe</surname></personname></author>
+
+ <author><personname><firstname>M.</firstname><surname>Funkenhauser</surname></personname></author>
+
+ <author><personname><firstname>R. C.</firstname><surname>Holt</surname></personname></author>
</authorgroup>
<pagenums>247-254</pagenums>
</biblioset>
<biblioset relation="journal">
- <title>USENIX Assocation Conference Proceedings</title>
+ <citetitle>USENIX Assocation Conference Proceedings</citetitle>
<publishername>USENIX Association</publishername>
<pubdate>June 1985</pubdate>
</biblioset>
</biblioentry>
- <biblioentry id="biblio-gingell">
+ <biblioentry xml:id="biblio-gingell">
<abbrev>Gingell et al, 1987</abbrev>
<biblioset relation="article">
- <title>Virtual Memory Architecture in SunOS</title>
+ <citetitle>Virtual Memory Architecture in SunOS</citetitle>
<authorgroup>
- <author>
- <firstname>R.</firstname>
- <surname>Gingell</surname>
- </author>
-
- <author>
- <firstname>J.</firstname>
- <surname>Moran</surname>
- </author>
-
- <author>
- <firstname>W.</firstname>
- <surname>Shannon</surname>
- </author>
+ <author><personname><firstname>R.</firstname><surname>Gingell</surname></personname></author>
+
+ <author><personname><firstname>J.</firstname><surname>Moran</surname></personname></author>
+
+ <author><personname><firstname>W.</firstname><surname>Shannon</surname></personname></author>
</authorgroup>
<pagenums>81-94</pagenums>
</biblioset>
<biblioset relation="journal">
- <title>USENIX Association Conference Proceedings</title>
+ <citetitle>USENIX Association Conference Proceedings</citetitle>
<publishername>USENIX Association</publishername>
<pubdate>June 1987</pubdate>
</biblioset>
</biblioentry>
- <biblioentry id="biblio-kernighan">
+ <biblioentry xml:id="biblio-kernighan">
<abbrev>Kernighan &amp; Pike, 1984</abbrev>
- <title>The UNIX Programming Environment</title>
+ <citetitle>The UNIX Programming Environment</citetitle>
<authorgroup>
- <author>
- <firstname>B. W.</firstname>
- <surname>Kernighan</surname>
- </author>
-
- <author>
- <firstname>R.</firstname>
- <surname>Pike</surname>
- </author>
+ <author><personname><firstname>B. W.</firstname><surname>Kernighan</surname></personname></author>
+
+ <author><personname><firstname>R.</firstname><surname>Pike</surname></personname></author>
</authorgroup>
<publisher>
@@ -2605,22 +2536,19 @@
<pubdate>1984</pubdate>
</biblioentry>
- <biblioentry id="biblio-macklem">
+ <biblioentry xml:id="biblio-macklem">
<abbrev>Macklem, 1994</abbrev>
<biblioset relation="chapter">
- <title>The 4.4BSD NFS Implementation</title>
+ <citetitle>The 4.4BSD NFS Implementation</citetitle>
- <author>
- <firstname>R.</firstname>
- <surname>Macklem</surname>
- </author>
+ <author><personname><firstname>R.</firstname><surname>Macklem</surname></personname></author>
<pagenums>6:1-14</pagenums>
</biblioset>
<biblioset relation="book">
- <title>4.4BSD System Manager's Manual</title>
+ <citetitle>4.4BSD System Manager's Manual</citetitle>
<publisher>
<publishername>O'Reilly &amp; Associates, Inc.</publishername>
@@ -2634,73 +2562,52 @@
</biblioset>
</biblioentry>
- <biblioentry id="biblio-mckusick-2">
+ <biblioentry xml:id="biblio-mckusick-2">
<abbrev>McKusick &amp; Karels, 1988</abbrev>
<biblioset relation="article">
- <title>Design of a General Purpose Memory Allocator for the 4.3BSD
- UNIX Kernel</title>
+ <citetitle>Design of a General Purpose Memory Allocator for the 4.3BSD
+ UNIX Kernel</citetitle>
<authorgroup>
- <author>
- <firstname>M. K.</firstname>
- <surname>McKusick</surname>
- </author>
-
- <author>
- <firstname>M. J.</firstname>
- <surname>Karels</surname>
- </author>
+ <author><personname><firstname>M. K.</firstname><surname>McKusick</surname></personname></author>
+
+ <author><personname><firstname>M. J.</firstname><surname>Karels</surname></personname></author>
</authorgroup>
<pagenums>295-304</pagenums>
</biblioset>
<biblioset relation="journal">
- <title>USENIX Assocation Conference Proceedings</title>
+ <citetitle>USENIX Assocation Conference Proceedings</citetitle>
<publishername>USENIX Assocation</publishername>
<pubdate>June 1998</pubdate>
</biblioset>
</biblioentry>
- <biblioentry id="biblio-mckusick-1">
+ <biblioentry xml:id="biblio-mckusick-1">
<abbrev>McKusick et al, 1994</abbrev>
<biblioset relation="manual">
- <title>Berkeley Software Architecture Manual, 4.4BSD Edition</title>
+ <citetitle>Berkeley Software Architecture Manual, 4.4BSD Edition</citetitle>
<authorgroup>
- <author>
- <firstname>M. K.</firstname>
- <surname>McKusick</surname>
- </author>
-
- <author>
- <firstname>M. J.</firstname>
- <surname>Karels</surname>
- </author>
-
- <author>
- <firstname>S. J.</firstname>
- <surname>Leffler</surname>
- </author>
-
- <author>
- <firstname>W. N.</firstname>
- <surname>Joy</surname>
- </author>
-
- <author>
- <firstname>R. S.</firstname>
- <surname>Faber</surname>
- </author>
+ <author><personname><firstname>M. K.</firstname><surname>McKusick</surname></personname></author>
+
+ <author><personname><firstname>M. J.</firstname><surname>Karels</surname></personname></author>
+
+ <author><personname><firstname>S. J.</firstname><surname>Leffler</surname></personname></author>
+
+ <author><personname><firstname>W. N.</firstname><surname>Joy</surname></personname></author>
+
+ <author><personname><firstname>R. S.</firstname><surname>Faber</surname></personname></author>
</authorgroup>
<pagenums>5:1-42</pagenums>
</biblioset>
<biblioset relation="book">
- <title>4.4BSD Programmer's Supplementary Documents</title>
+ <citetitle>4.4BSD Programmer's Supplementary Documents</citetitle>
<publisher>
<publishername>O'Reilly &amp; Associates, Inc.</publishername>
@@ -2714,133 +2621,88 @@
</biblioset>
</biblioentry>
- <biblioentry id="biblio-ritchie">
+ <biblioentry xml:id="biblio-ritchie">
<abbrev>Ritchie, 1988</abbrev>
- <title>Early Kernel Design</title>
+ <citetitle>Early Kernel Design</citetitle>
<subtitle>private communication</subtitle>
- <author>
- <firstname>D. M.</firstname>
- <surname>Ritchie</surname>
- </author>
+ <author><personname><firstname>D. M.</firstname><surname>Ritchie</surname></personname></author>
<pubdate>March 1988</pubdate>
</biblioentry>
- <biblioentry id="biblio-rosenblum">
+ <biblioentry xml:id="biblio-rosenblum">
<abbrev>Rosenblum &amp; Ousterhout, 1992</abbrev>
<biblioset relation="article">
- <title>The Design and Implementation of a Log-Structured File
- System</title>
+ <citetitle>The Design and Implementation of a Log-Structured File
+ System</citetitle>
<authorgroup>
- <author>
- <firstname>M.</firstname>
- <surname>Rosenblum</surname>
- </author>
-
- <author>
- <firstname>K.</firstname>
- <surname>Ousterhout</surname>
- </author>
+ <author><personname><firstname>M.</firstname><surname>Rosenblum</surname></personname></author>
+
+ <author><personname><firstname>K.</firstname><surname>Ousterhout</surname></personname></author>
</authorgroup>
<pagenums>26-52</pagenums>
</biblioset>
<biblioset relation="journal">
- <title>ACM Transactions on Computer Systems, 10, 1</title>
+ <citetitle>ACM Transactions on Computer Systems, 10, 1</citetitle>
<publishername>Association for Computing Machinery</publishername>
<pubdate>February 1992</pubdate>
</biblioset>
</biblioentry>
- <biblioentry id="biblio-rozier">
+ <biblioentry xml:id="biblio-rozier">
<abbrev>Rozier et al, 1988</abbrev>
<biblioset relation="article">
- <title>Chorus Distributed Operating Systems</title>
+ <citetitle>Chorus Distributed Operating Systems</citetitle>
<authorgroup>
- <author>
- <firstname>M.</firstname>
- <surname>Rozier</surname>
- </author>
-
- <author>
- <firstname>V.</firstname>
- <surname>Abrossimov</surname>
- </author>
-
- <author>
- <firstname>F.</firstname>
- <surname>Armand</surname>
- </author>
-
- <author>
- <firstname>I.</firstname>
- <surname>Boule</surname>
- </author>
-
- <author>
- <firstname>M.</firstname>
- <surname>Gien</surname>
- </author>
-
- <author>
- <firstname>M.</firstname>
- <surname>Guillemont</surname>
- </author>
-
- <author>
- <firstname>F.</firstname>
- <surname>Herrmann</surname>
- </author>
-
- <author>
- <firstname>C.</firstname>
- <surname>Kaiser</surname>
- </author>
-
- <author>
- <firstname>S.</firstname>
- <surname>Langlois</surname>
- </author>
-
- <author>
- <firstname>P.</firstname>
- <surname>Leonard</surname>
- </author>
-
- <author>
- <firstname>W.</firstname>
- <surname>Neuhauser</surname>
- </author>
+ <author><personname><firstname>M.</firstname><surname>Rozier</surname></personname></author>
+
+ <author><personname><firstname>V.</firstname><surname>Abrossimov</surname></personname></author>
+
+ <author><personname><firstname>F.</firstname><surname>Armand</surname></personname></author>
+
+ <author><personname><firstname>I.</firstname><surname>Boule</surname></personname></author>
+
+ <author><personname><firstname>M.</firstname><surname>Gien</surname></personname></author>
+
+ <author><personname><firstname>M.</firstname><surname>Guillemont</surname></personname></author>
+
+ <author><personname><firstname>F.</firstname><surname>Herrmann</surname></personname></author>
+
+ <author><personname><firstname>C.</firstname><surname>Kaiser</surname></personname></author>
+
+ <author><personname><firstname>S.</firstname><surname>Langlois</surname></personname></author>
+
+ <author><personname><firstname>P.</firstname><surname>Leonard</surname></personname></author>
+
+ <author><personname><firstname>W.</firstname><surname>Neuhauser</surname></personname></author>
</authorgroup>
<pagenums>305-370</pagenums>
</biblioset>
<biblioset relation="journal">
- <title>USENIX Computing Systems, 1, 4</title>
+ <citetitle>USENIX Computing Systems, 1, 4</citetitle>
<pubdate>Fall 1988</pubdate>
</biblioset>
</biblioentry>
- <biblioentry id="biblio-tevanian">
+ <biblioentry xml:id="biblio-tevanian">
<abbrev>Tevanian, 1987</abbrev>
- <title>Architecture-Independent Virtual Memory Management for Parallel
- and Distributed Environments: The Mach Approach</title>
+ <citetitle>Architecture-Independent Virtual Memory Management for Parallel
+ and Distributed Environments: The Mach Approach</citetitle>
<subtitle>Technical Report CMU-CS-88-106,</subtitle>
- <author>
- <firstname>A.</firstname>
- <surname>Tevanian</surname>
- </author>
+ <author><personname><firstname>A.</firstname><surname>Tevanian</surname></personname></author>
<publisher>
<publishername>Department of Computer Science, Carnegie-Mellon
diff --git a/en_US.ISO8859-1/books/dev-model/book.xml b/en_US.ISO8859-1/books/dev-model/book.xml
index 91f3e6b981..593b777d26 100644
--- a/en_US.ISO8859-1/books/dev-model/book.xml
+++ b/en_US.ISO8859-1/books/dev-model/book.xml
@@ -1,10 +1,9 @@
<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE book PUBLIC "-//FreeBSD//DTD DocBook XML V4.5-Based Extension//EN"
- "../../../share/xml/freebsd45.dtd" [
+<!DOCTYPE book PUBLIC "-//FreeBSD//DTD DocBook XML V5.0-Based Extension//EN"
+ "../../../share/xml/freebsd50.dtd" [
<!ENTITY % chapters SYSTEM "chapters.ent">
%chapters;
]>
-
<!--
- Copyright (c) 2002-2005 Niklas Saers
- All rights reserved.
@@ -32,14 +31,10 @@
-
- $FreeBSD$
-->
-
-<book lang='en'>
- <bookinfo>
- <title>A project model for the FreeBSD Project</title>
- <author>
- <firstname>Niklas</firstname>
- <surname>Saers</surname>
- </author>
+<book xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:lang="en">
+ <info><title>A project model for the FreeBSD Project</title>
+
+ <author><personname><firstname>Niklas</firstname><surname>Saers</surname></personname></author>
<copyright>
<year>2002-2005</year>
<holder>Niklas Saers</holder>
@@ -91,8 +86,8 @@
</revhistory>
<releaseinfo>$FreeBSD$</releaseinfo>
- </bookinfo>
- <preface id="foreword">
+ </info>
+ <preface xml:id="foreword">
<title>Foreword</title>
<para>
@@ -140,7 +135,7 @@
</preface>
- <chapter id="overview">
+ <chapter xml:id="overview">
<title>Overview</title>
@@ -193,8 +188,7 @@
</para>
<para>
- <citation><xref
- linkend="freebsd-developer-handbook"/>, Section 1.2 and 1.3</citation>
+ <citation><xref 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
@@ -205,10 +199,10 @@
</para>
</chapter>
- <chapter id="definitions">
+ <chapter xml:id="definitions">
<title>Definitions</title>
- <section id="ref-activity" xreflabel="">
+ <section xml:id="ref-activity" xreflabel="">
<title>Activity</title>
<para>
@@ -223,7 +217,7 @@
</section>
- <section id="def-process" xreflabel="">
+ <section xml:id="def-process" xreflabel="">
<title>Process</title>
<para>
@@ -235,7 +229,7 @@
</section>
- <section id="ref-hat" xreflabel="Hat">
+ <section xml:id="ref-hat" xreflabel="Hat">
<title>Hat</title>
<para>
@@ -248,7 +242,7 @@
</section>
- <section id="ref-outcome" xreflabel="Outcome">
+ <section xml:id="ref-outcome" xreflabel="Outcome">
<title>Outcome</title>
<para>
@@ -258,8 +252,7 @@
item that must be produced to complete a project or part of a
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>.
+ by the project sponsor or customer</quote> by <citation><xref linkend="ref-pmbok"/></citation>.
Examples of
outcomes are a piece of software, a decision made or a
report written.
@@ -268,7 +261,7 @@
</section>
- <section id="ref-freebsd" xreflabel="">
+ <section xml:id="ref-freebsd" xreflabel="">
<title>FreeBSD</title>
<para>
@@ -280,7 +273,7 @@
</section>
</chapter>
- <chapter id="model-orgstruct">
+ <chapter xml:id="model-orgstruct">
<title>Organisational structure</title>
<para>
@@ -292,7 +285,7 @@
<para>
<figure>
<title>The FreeBSD Project's structure</title>
- <graphic fileref="orghierarchy"/>
+ <mediaobject><imageobject><imagedata fileref="orghierarchy"/></imageobject></mediaobject>
</figure>
</para>
@@ -350,7 +343,7 @@
<para>
<figure>
<title>The FreeBSD Project's structure with committers in categories</title>
- <graphic fileref="orghierarchy2"/>
+ <mediaobject><imageobject><imagedata fileref="orghierarchy2"/></imageobject></mediaobject>
</figure>
</para>
<para>
@@ -430,10 +423,10 @@
</chapter>
- <chapter id="methodology-model">
+ <chapter xml:id="methodology-model">
<title>Methodology model</title>
- <section id="development-model"><title>Development model</title>
+ <section xml:id="development-model"><title>Development model</title>
<para>
There is no defined model for how people write code in
@@ -444,7 +437,7 @@
<para>
<figure>
<title>J&oslash;rgenssen's model for change integration</title>
- <graphic fileref="maintenance"/>
+ <mediaobject><imageobject><imagedata fileref="maintenance"/></imageobject></mediaobject>
</figure>
</para>
@@ -581,7 +574,7 @@
</section>
- <section id="release-branches">
+ <section xml:id="release-branches">
<title>Release branches</title>
<para>
@@ -609,7 +602,7 @@
<para>
<figure>
<title>The FreeBSD release tree</title>
- <graphic fileref="branches"/>
+ <mediaobject><imageobject><imagedata fileref="branches"/></imageobject></mediaobject>
</figure>
</para>
<para>
@@ -679,7 +672,7 @@
</section>
- <section id="model-summary">
+ <section xml:id="model-summary">
<title>Model summary</title>
<para>
@@ -690,7 +683,7 @@
<para>
<figure>
<title>The overall development model</title>
- <graphic fileref="freebsd-code-model"/>
+ <mediaobject><imageobject><imagedata fileref="freebsd-code-model"/></imageobject></mediaobject>
</figure>
</para>
<para>
@@ -719,7 +712,7 @@
</chapter>
- <chapter id="sect-hats">
+ <chapter xml:id="sect-hats">
<title>Hats</title>
<para>
@@ -747,10 +740,10 @@
</para>
- <section id="general-hats">
+ <section xml:id="general-hats">
<title>General Hats</title>
- <section id="role-contributor" xreflabel="Contributor">
+ <section xml:id="role-contributor" xreflabel="Contributor">
<title>Contributor</title>
<para>
A Contributor contributes to the FreeBSD project either as a
@@ -761,7 +754,7 @@
</para>
</section>
- <section id="role-committer" xreflabel="Committer">
+ <section xml:id="role-committer" xreflabel="Committer">
<title>Committer</title>
<para>
A person who has the required privileges to add his code or documentation to the
@@ -799,7 +792,7 @@
</para>
</section>
- <section id="role-core" xreflabel="Core team">
+ <section xml:id="role-core" xreflabel="Core team">
<title>Core Team</title>
@@ -816,7 +809,7 @@
</section>
- <section id="role-maintainer" xreflabel="Maintainership">
+ <section xml:id="role-maintainer" xreflabel="Maintainership">
<title>Maintainership</title>
<para>
@@ -856,7 +849,7 @@
</section>
- <section id="official-hats">
+ <section xml:id="official-hats">
<title>Official Hats</title>
<para>
@@ -870,7 +863,7 @@
<para>
<figure>
<title>Overview of official hats</title>
- <graphic fileref="hats-overview"/>
+ <mediaobject><imageobject><imagedata fileref="hats-overview"/></imageobject></mediaobject>
</figure>
</para>
@@ -883,8 +876,7 @@
- <section id="role-doc-manager" xreflabel="Documentation
- project architect">
+ <section xml:id="role-doc-manager" xreflabel="Documentation project architect">
<title>Documentation project manager</title>
<para>
<xref linkend="sub-project-documentation"/>
@@ -897,12 +889,12 @@
Hat held by:
The DocEng team <email>doceng@FreeBSD.org</email>.
The
- <ulink url="http://www.freebsd.org/internal/doceng.html">
- DocEng Charter</ulink>.
+ <link xlink:href="http://www.freebsd.org/internal/doceng.html">
+ DocEng Charter</link>.
</para>
</section>
- <section id="role-postmaster" xreflabel="Postmaster">
+ <section xml:id="role-postmaster" xreflabel="Postmaster">
<title>Postmaster</title>
<para>
The Postmaster is responsible for mail being correctly
@@ -917,7 +909,7 @@
</para>
</section>
- <section id="role-release-coordination" xreflabel="Release Coordination">
+ <section xml:id="role-release-coordination" xreflabel="Release Coordination">
<title>Release Coordination</title>
<para>
@@ -948,16 +940,16 @@
available in the <xref linkend="process-release-engineering"/> section.
</para>
- <para id="role-releng" xreflabel="Release Engineering Team">
+ <para xml:id="role-releng" xreflabel="Release Engineering Team">
Hat held by:
the Release Engineering team <email>re@FreeBSD.org</email>.
The
- <ulink url="http://www.freebsd.org/releng/charter.html">
- Release Engineering Charter</ulink>.
+ <link xlink:href="http://www.freebsd.org/releng/charter.html">
+ Release Engineering Charter</link>.
</para>
</section>
- <section id="role-pr-cr" xreflabel="Public Relations &amp; Corporate Liaison">
+ <section xml:id="role-pr-cr" xreflabel="Public Relations &amp; Corporate Liaison">
<title>Public Relations &amp; Corporate Liaison</title>
<para>
The Public Relations &amp; Corporate Liaison's
@@ -986,7 +978,7 @@
</para>
</section>
- <section id="role-security-officer" xreflabel="Security Officer">
+ <section xml:id="role-security-officer" xreflabel="Security Officer">
<title>Security Officer</title>
<para>
The Security Officer's main responsibility is to
@@ -1010,7 +1002,7 @@
</para>
</section>
- <section id="role-repo-manager" xreflabel="Source Repository Manager">
+ <section xml:id="role-repo-manager" xreflabel="Source Repository Manager">
<title>Source Repository Manager</title>
<para>
The Source Repository Manager is the only one who is allowed
@@ -1028,7 +1020,7 @@
</para>
</section>
- <section id="role-election-manager" xreflabel="Election Manager">
+ <section xml:id="role-election-manager" xreflabel="Election Manager">
<title>Election Manager</title>
<para>
The Election Manager is responsible for the
@@ -1043,7 +1035,7 @@
</para>
</section>
- <section id="role-webmaster" xreflabel="Web site Management">
+ <section xml:id="role-webmaster" xreflabel="Web site Management">
<title>Web site Management</title>
<para>
The Web site Management hat is responsible for coordinating
@@ -1061,7 +1053,7 @@
</para>
</section>
- <section id="role-ports-manager" xreflabel="Ports Manager">
+ <section xml:id="role-ports-manager" xreflabel="Ports Manager">
<title>Ports Manager</title>
<para>
The Ports Manager acts as a liaison between
@@ -1075,12 +1067,12 @@
Hat held by:
the Ports Management Team <email>portmgr@FreeBSD.org</email>.
The
- <ulink url="http://www.freebsd.org/portmgr/charter.html">
- Portmgr charter</ulink>.
+ <link xlink:href="http://www.freebsd.org/portmgr/charter.html">
+ Portmgr charter</link>.
</para>
</section>
- <section id="role-standards" xreflabel="Standards">
+ <section xml:id="role-standards" xreflabel="Standards">
<title>Standards</title>
<para>
The Standards hat is responsible for ensuring that FreeBSD
@@ -1098,7 +1090,7 @@
</para>
</section>
- <section id="role-core-secretary" xreflabel="Core Secretary">
+ <section xml:id="role-core-secretary" xreflabel="Core Secretary">
<title>Core Secretary</title>
<para>
The Core Secretary's main responsibility is to write drafts to
@@ -1111,7 +1103,7 @@
</para>
</section>
- <section id="role-gnats" xreflabel="GNATS Administrator">
+ <section xml:id="role-gnats" xreflabel="GNATS Administrator">
<title>GNATS Administrator</title>
<para>
The GNATS Administrator is responsible for ensuring that the
@@ -1124,7 +1116,7 @@
</para>
</section>
- <section id="role-bugmeister" xreflabel="Bugmeister">
+ <section xml:id="role-bugmeister" xreflabel="Bugmeister">
<title>Bugmeister</title>
<para>
The Bugmeister is the person in charge of the problem report
@@ -1137,7 +1129,7 @@
</para>
</section>
- <section id="role-donations" xreflabel="Donations Liaison Officer">
+ <section xml:id="role-donations" xreflabel="Donations Liaison Officer">
<title>Donations Liaison Officer</title>
<para>
The task of
@@ -1146,7 +1138,7 @@
organisations willing to make a
donation. The Donations Liaison Charter is
available
- <ulink url="http://www.freebsd.org/donations/">here</ulink>
+ <link xlink:href="http://www.freebsd.org/donations/">here</link>
</para>
<para>
Hat held by:
@@ -1154,7 +1146,7 @@
</para>
</section>
- <section id="role-admin" xreflabel="Admin">
+ <section xml:id="role-admin" xreflabel="Admin">
<title>Admin</title>
<para>
(Also called <quote>FreeBSD Cluster Admin</quote>)
@@ -1181,10 +1173,10 @@
</section>
- <section id="proc-depend-hats">
+ <section xml:id="proc-depend-hats">
<title>Process dependent hats</title>
- <section id="role-problem-originator" xreflabel="Report originator">
+ <section xml:id="role-problem-originator" xreflabel="Report originator">
<title>Report originator</title>
<para>
The person originally responsible for
@@ -1193,7 +1185,7 @@
</section>
- <section id="role-bugbuster" xreflabel="Bugbuster">
+ <section xml:id="role-bugbuster" xreflabel="Bugbuster">
<title>Bugbuster</title>
<para>
A person who will either find the right
@@ -1203,7 +1195,7 @@
</para>
</section>
- <section id="role-mentor" xreflabel="Mentor">
+ <section xml:id="role-mentor" xreflabel="Mentor">
<title>Mentor</title>
<para>
A mentor is a committer who takes it upon him/her to
@@ -1215,7 +1207,7 @@
behaviour.
</para>
</section>
- <section id="role-vendor" xreflabel="Vendor">
+ <section xml:id="role-vendor" xreflabel="Vendor">
<title>Vendor</title>
<para>
The person(s) or organisation whom
@@ -1223,7 +1215,7 @@
</para>
</section>
- <section id="role-reviewer" xreflabel="Reviewer">
+ <section xml:id="role-reviewer" xreflabel="Reviewer">
<title>Reviewers</title>
<para>
People on the mailing list where the request
@@ -1235,7 +1227,7 @@
</chapter>
- <chapter id="model-processes" xreflabel="processes">
+ <chapter xml:id="model-processes" xreflabel="processes">
<title>Processes</title>
<para>
@@ -1245,7 +1237,7 @@
similar cases.
</para>
- <section id="proc-addrem-committer">
+ <section xml:id="proc-addrem-committer">
<title>Adding new and removing old committers</title>
<para>
@@ -1289,8 +1281,7 @@
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
- new committer and sends them to <xref
- linkend="role-admin"/>. When the new account is created, the
+ new committer and sends them to <xref 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>
@@ -1298,7 +1289,7 @@
<para>
<figure>
<title>Process summary: adding a new committer</title>
- <graphic fileref="proc-add-committer"/>
+ <mediaobject><imageobject><imagedata fileref="proc-add-committer"/></imageobject></mediaobject>
</figure>
</para>
@@ -1330,7 +1321,7 @@
<para>
<figure>
<title>Process summary: removing a committer</title>
- <graphic fileref="proc-rm-committer"/>
+ <mediaobject><imageobject><imagedata fileref="proc-rm-committer"/></imageobject></mediaobject>
</figure>
</para>
@@ -1378,7 +1369,7 @@
</section>
- <section id="committing">
+ <section xml:id="committing">
<title>Committing code</title>
<para>
@@ -1441,7 +1432,7 @@
<para>
<figure>
<title>Process summary: A committer commits code</title>
- <graphic fileref="proc-commit"/>
+ <mediaobject><imageobject><imagedata fileref="proc-commit"/></imageobject></mediaobject>
</figure>
</para>
@@ -1465,7 +1456,7 @@
<para>
<figure>
<title>Process summary: A contributor commits code</title>
- <graphic fileref="proc-contrib"/>
+ <mediaobject><imageobject><imagedata fileref="proc-contrib"/></imageobject></mediaobject>
</figure>
</para>
@@ -1501,7 +1492,7 @@
</section>
- <section id="process-core-election" xreflabel="Core election">
+ <section xml:id="process-core-election" xreflabel="Core election">
<title>Core election</title>
<para>
@@ -1526,9 +1517,8 @@
to submit their candidacy at least one week before the
election starts, but can refine their statements until the
voting starts. They are
- presented in the <ulink
- url="http://election.uk.freebsd.org/candidates.html">candidates
- list</ulink>. When writing their election statements, the candidates
+ presented in the <link xlink:href="http://election.uk.freebsd.org/candidates.html">candidates
+ list</link>. When writing their election statements, the candidates
must answer a few standard questions submitted by the election manager.
</para>
@@ -1565,7 +1555,7 @@
<para>
<figure>
<title>Process summary: Core elections</title>
- <graphic fileref="proc-elections"/>
+ <mediaobject><imageobject><imagedata fileref="proc-elections"/></imageobject></mediaobject>
</figure>
</para>
@@ -1603,7 +1593,7 @@
</para>
</section>
- <section id="new-features">
+ <section xml:id="new-features">
<title>Development of new features</title>
<para>
@@ -1686,7 +1676,7 @@
</section>
- <section id="model-maintenance" xreflabel="maintenance">
+ <section xml:id="model-maintenance" xreflabel="maintenance">
<title>Maintenance</title>
<para>
@@ -1718,8 +1708,7 @@
<para>
The main bulk of work that is put into the FreeBSD project is
- maintenance. <citation><xref
- linkend="jorgensen2001"/></citation>
+ maintenance. <citation><xref linkend="jorgensen2001"/></citation>
has made a figure
showing the life cycle of changes.
</para>
@@ -1727,7 +1716,7 @@
<para>
<figure>
<title>J&oslash;rgenssen's model for change integration</title>
- <graphic fileref="maintenance"/>
+ <mediaobject><imageobject><imagedata fileref="maintenance"/></imageobject></mediaobject>
</figure>
</para>
@@ -1769,7 +1758,7 @@
</section>
- <section id="model-pr">
+ <section xml:id="model-pr">
<title>Problem reporting</title>
<para>
@@ -1807,7 +1796,7 @@
<para>
<figure>
<title>Process summary: problem reporting</title>
- <graphic fileref="proc-pr"/>
+ <mediaobject><imageobject><imagedata fileref="proc-pr"/></imageobject></mediaobject>
</figure>
</para>
@@ -1843,7 +1832,7 @@
</section>
- <section id="process-reactions" xreflabel="Reacting to misbehaviour">
+ <section xml:id="process-reactions" xreflabel="Reacting to misbehaviour">
<title>Reacting to misbehaviour</title>
<para>
@@ -1904,7 +1893,7 @@
</section>
- <section id="process-release-engineering" xreflabel="release engineering">
+ <section xml:id="process-release-engineering" xreflabel="release engineering">
<title>Release engineering</title>
<para>
@@ -2044,7 +2033,7 @@
<para>
<figure>
<title>Process summary: release engineering</title>
- <graphic fileref="proc-releng"/>
+ <mediaobject><imageobject><imagedata fileref="proc-releng"/></imageobject></mediaobject>
</figure>
</para>
@@ -2067,7 +2056,7 @@
- <chapter id="tools">
+ <chapter xml:id="tools">
<title>Tools</title>
<para>
@@ -2076,7 +2065,7 @@
developed tools and are commonly used in the open source world.
</para>
- <section id="tool-svn" xreflabel="SVN">
+ <section xml:id="tool-svn" xreflabel="SVN">
<title>Subversion (SVN)</title>
<para>Subversion (<quote>SVN</quote>)
is a system to handle multiple versions of text files and
@@ -2086,7 +2075,7 @@
</para>
</section>
- <section id="tool-gnats" xreflabel="GNATS">
+ <section xml:id="tool-gnats" xreflabel="GNATS">
<title>GNATS</title>
<para>
GNATS is a maintenance database consisting of a set of tools to track bugs at a
@@ -2100,7 +2089,7 @@
</para>
</section>
- <section id="model-mailman" xreflabel="[model, Mailman]">
+ <section xml:id="model-mailman" xreflabel="[model, Mailman]">
<title>Mailman</title>
<para>
Mailman is a program that automates the
@@ -2119,7 +2108,7 @@
</para>
</section>
- <section id="tool-perforce" xreflabel="Perforce">
+ <section xml:id="tool-perforce" xreflabel="Perforce">
<title>Perforce</title>
<para>
Perforce is a commercial software configuration management
@@ -2137,7 +2126,7 @@
</section>
- <section id="tool-pgp" xreflabel="PGP">
+ <section xml:id="tool-pgp" xreflabel="PGP">
<title>Pretty Good Privacy</title>
<para>
Pretty Good Privacy, better known as PGP, is a cryptosystem
@@ -2152,7 +2141,7 @@
</para>
</section>
- <section id="tool-ssh2" xreflabel="SSH 2">
+ <section xml:id="tool-ssh2" xreflabel="SSH 2">
<title>Secure Shell</title>
<para>
Secure Shell is a standard for securely logging into a remote system
@@ -2169,7 +2158,7 @@
</chapter>
- <chapter id="sub-projects">
+ <chapter xml:id="sub-projects">
<title>Sub-projects</title>
<para>
@@ -2182,7 +2171,7 @@
</para>
- <section id="sub-project-ports" xreflabel="The Ports Subproject">
+ <section xml:id="sub-project-ports" xreflabel="The Ports Subproject">
<title>The Ports Subproject</title>
<para>
@@ -2193,16 +2182,16 @@
</para>
<para>
- <figure id="fig-ports">
+ <figure xml:id="fig-ports">
<title>Number of ports added between 1996 and 2005</title>
- <graphic fileref="portsstatus"/>
+ <mediaobject><imageobject><imagedata fileref="portsstatus"/></imageobject></mediaobject>
</figure>
</para>
<para>
<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
+ <link xlink:href="http://www.freebsd.org/ports/growth/status.png">
+ the FreeBSD web site</link>. It shows the number of ports
available to FreeBSD in the period 1995 to 2005. It looks
like the curve has first grown exponentionally, and then
since the middle of 2001 grown linearly.
@@ -2252,8 +2241,7 @@
</section>
- <section id="sub-project-documentation" xreflabel="The FreeBSD
- Documentation Project">
+ <section xml:id="sub-project-documentation" xreflabel="The FreeBSD Documentation Project">
<title>The FreeBSD Documentation Project</title>
<para>
@@ -2303,57 +2291,57 @@
</chapter>
-<bibliography id="bibliography">
+<bibliography xml:id="bibliography">
<title>References</title>
- <biblioentry id="brooks" xreflabel="Brooks, 1995">
+ <biblioentry xml:id="brooks" xreflabel="Brooks, 1995">
<authorgroup>
- <author><firstname>Frederick P.</firstname><surname>Brooks</surname></author>
+ <author><personname><firstname>Frederick P.</firstname><surname>Brooks</surname></personname></author>
</authorgroup>
<copyright><year>1975</year><year>1995</year>
<holder>Pearson Education Limited</holder>
</copyright>
- <isbn>0201835959</isbn>
+ <biblioid class="isbn">0201835959</biblioid>
<publisher>
<publishername>Addison-Wesley Pub Co</publishername>
</publisher>
- <title>The Mythical Man-Month</title>
+ <citetitle>The Mythical Man-Month</citetitle>
<subtitle>Essays on Software Engineering, Anniversary Edition (2nd Edition)</subtitle>
</biblioentry>
- <biblioentry id="thesis" xreflabel="Saers, 2003">
+ <biblioentry xml:id="thesis" xreflabel="Saers, 2003">
<authorgroup>
- <author><firstname>Niklas</firstname><surname>Saers</surname></author>
+ <author><personname><firstname>Niklas</firstname><surname>Saers</surname></personname></author>
</authorgroup>
<copyright>
<year>2003</year>
</copyright>
- <title>A project model for the FreeBSD Project</title>
+ <citetitle>A project model for the FreeBSD Project</citetitle>
<subtitle>Candidatus Scientiarum thesis</subtitle>
- <bibliomisc role="url"><ulink url="http://niklas.saers.com/thesis"></ulink></bibliomisc>
+ <bibliomisc xlink:href="http://niklas.saers.com/thesis">http://niklas.saers.com/thesis</bibliomisc>
</biblioentry>
- <biblioentry id="jorgensen2001" xreflabel="J&oslash;rgensen, 2001">
+ <biblioentry xml:id="jorgensen2001" xreflabel="J&oslash;rgensen, 2001">
<authorgroup>
- <author><firstname>Niels</firstname><surname>J&oslash;rgensen</surname></author>
+ <author><personname><firstname>Niels</firstname><surname>J&oslash;rgensen</surname></personname></author>
</authorgroup>
<copyright>
<year>2001</year>
</copyright>
- <title>Putting it All in the Trunk</title>
+ <citetitle>Putting it All in the Trunk</citetitle>
<subtitle>Incremental Software Development in the FreeBSD Open Source Project</subtitle>
- <bibliomisc role="url"><ulink url="http://www.dat.ruc.dk/~nielsj/research/papers/freebsd.pdf"></ulink></bibliomisc>
+ <bibliomisc xlink:href="http://www.dat.ruc.dk/~nielsj/research/papers/freebsd.pdf">http://www.dat.ruc.dk/~nielsj/research/papers/freebsd.pdf</bibliomisc>
</biblioentry>
- <biblioentry id="ref-pmbok" xreflabel="PMI, 2000">
+ <biblioentry xml:id="ref-pmbok" xreflabel="PMI, 2000">
<authorgroup>
- <author><surname>Project Management Institute</surname></author>
+ <author><personname><surname>Project Management Institute</surname></personname></author>
</authorgroup>
<copyright><year>1996</year><year>2000</year>
<holder>Project Management Institute</holder>
</copyright>
- <isbn>1-880410-23-0</isbn>
+ <biblioid class="isbn">1-880410-23-0</biblioid>
<publisher>
<publishername>Project Management Institute</publishername>
<address>
@@ -2362,41 +2350,41 @@
<country>USA</country>
</address>
</publisher>
- <title>PMBOK Guide</title>
+ <citetitle>PMBOK Guide</citetitle>
<subtitle>A Guide to the Project Management Body of Knowledge,
2000 Edition</subtitle>
</biblioentry>
- <biblioentry id="freebsd-bylaws" xreflabel="FreeBSD, 2000A">
+ <biblioentry xml:id="freebsd-bylaws" xreflabel="FreeBSD, 2000A">
<copyright><year>2002</year>
<holder>The FreeBSD Project</holder>
</copyright>
- <title>Core Bylaws</title>
- <bibliomisc role="url"><ulink url="http://www.freebsd.org/internal/bylaws.html"></ulink></bibliomisc>
+ <citetitle>Core Bylaws</citetitle>
+ <bibliomisc xlink:href="http://www.freebsd.org/internal/bylaws.html">http://www.freebsd.org/internal/bylaws.html</bibliomisc>
</biblioentry>
- <biblioentry id="freebsd-developer-handbook" xreflabel="FreeBSD, 2002A">
+ <biblioentry xml:id="freebsd-developer-handbook" xreflabel="FreeBSD, 2002A">
<copyright><year>2002</year>
<holder>The FreeBSD Documentation Project</holder>
</copyright>
- <title>FreeBSD Developer's Handbook</title>
- <bibliomisc role="url"><ulink url="http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/"></ulink></bibliomisc>
+ <citetitle>FreeBSD Developer's Handbook</citetitle>
+ <bibliomisc xlink:href="http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/">http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/</bibliomisc>
</biblioentry>
- <biblioentry id="bsd-election2002" xreflabel="FreeBSD, 2002B">
+ <biblioentry xml:id="bsd-election2002" xreflabel="FreeBSD, 2002B">
<copyright><year>2002</year>
<holder>The FreeBSD Project</holder>
</copyright>
- <title>Core team election 2002</title>
- <bibliomisc role="url"><ulink url="http://election.uk.freebsd.org/candidates.html"></ulink></bibliomisc>
+ <citetitle>Core team election 2002</citetitle>
+ <bibliomisc xlink:href="http://election.uk.freebsd.org/candidates.html">http://election.uk.freebsd.org/candidates.html</bibliomisc>
</biblioentry>
- <biblioentry id="freebsd-handle-pr" xreflabel="FreeBSD, 2002C">
+ <biblioentry xml:id="freebsd-handle-pr" xreflabel="FreeBSD, 2002C">
<authorgroup>
- <author><firstname>Dag-Erling</firstname><surname>Sm&oslash;rgrav</surname></author>
- <author><firstname>Hiten</firstname><surname>Pandya</surname></author>
+ <author><personname><firstname>Dag-Erling</firstname><surname>Sm&oslash;rgrav</surname></personname></author>
+ <author><personname><firstname>Hiten</firstname><surname>Pandya</surname></personname></author>
</authorgroup>
<copyright><year>2002</year>
<holder>The FreeBSD Documentation Project</holder>
@@ -2404,13 +2392,13 @@
<publisher>
<publishername>The FreeBSD Documentation Project</publishername>
</publisher>
- <title>Problem Report Handling Guidelines</title>
- <bibliomisc role="url"><ulink url="http://www.freebsd.org/doc/en/articles/pr-guidelines/article.html"></ulink></bibliomisc>
+ <citetitle>Problem Report Handling Guidelines</citetitle>
+ <bibliomisc xlink:href="http://www.freebsd.org/doc/en/articles/pr-guidelines/article.html">http://www.freebsd.org/doc/en/articles/pr-guidelines/article.html</bibliomisc>
</biblioentry>
- <biblioentry id="freebsd-send-pr" xreflabel="FreeBSD, 2002D">
+ <biblioentry xml:id="freebsd-send-pr" xreflabel="FreeBSD, 2002D">
<authorgroup>
- <author><firstname>Dag-Erling</firstname><surname>Sm&oslash;rgrav</surname></author>
+ <author><personname><firstname>Dag-Erling</firstname><surname>Sm&oslash;rgrav</surname></personname></author>
</authorgroup>
<copyright><year>2002</year>
<holder>The FreeBSD Documentation Project</holder>
@@ -2418,11 +2406,11 @@
<publisher>
<publishername>The FreeBSD Documentation Project</publishername>
</publisher>
- <title>Writing FreeBSD Problem Reports</title>
- <bibliomisc role="url"><ulink url="http://www.freebsd.org/doc/en/articles/problem-reports/article.html"></ulink></bibliomisc>
+ <citetitle>Writing FreeBSD Problem Reports</citetitle>
+ <bibliomisc xlink:href="http://www.freebsd.org/doc/en/articles/problem-reports/article.html">http://www.freebsd.org/doc/en/articles/problem-reports/article.html</bibliomisc>
</biblioentry>
- <biblioentry id="freebsd-committer" xreflabel="FreeBSD, 2001">
+ <biblioentry xml:id="freebsd-committer" xreflabel="FreeBSD, 2001">
<copyright><year>2001</year>
<holder>The FreeBSD Documentation Project</holder>
</copyright>
@@ -2430,13 +2418,13 @@
<publishername>The FreeBSD Documentation Project</publishername>
</publisher>
<!-- Version 1.146 -->
- <title>Committers Guide</title>
- <bibliomisc role="url"><ulink url="http://www.freebsd.org/doc/en/articles/committers-guide/article.html"></ulink></bibliomisc>
+ <citetitle>Committers Guide</citetitle>
+ <bibliomisc xlink:href="http://www.freebsd.org/doc/en/articles/committers-guide/article.html">http://www.freebsd.org/doc/en/articles/committers-guide/article.html</bibliomisc>
</biblioentry>
- <biblioentry id="freebsd-releng" xreflabel="FreeBSD, 2002E">
+ <biblioentry xml:id="freebsd-releng" xreflabel="FreeBSD, 2002E">
<authorgroup>
- <author><firstname>Murray</firstname><surname>Stokely</surname></author>
+ <author><personname><firstname>Murray</firstname><surname>Stokely</surname></personname></author>
</authorgroup>
<copyright><year>2002</year>
<holder>The FreeBSD Documentation Project</holder>
@@ -2445,79 +2433,79 @@
<publisher>
<publishername>The FreeBSD Documentation Project</publishername>
</publisher>
- <title>FreeBSD Release Engineering</title>
- <bibliomisc role="url"><ulink url="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/releng/article.html"></ulink></bibliomisc>
+ <citetitle>FreeBSD Release Engineering</citetitle>
+ <bibliomisc xlink:href="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/releng/article.html">http://www.freebsd.org/doc/en_US.ISO8859-1/articles/releng/article.html</bibliomisc>
</biblioentry>
- <biblioentry id="ref-bsd-handbook" xreflabel="FreeBSD, 2003A">
+ <biblioentry xml:id="ref-bsd-handbook" xreflabel="FreeBSD, 2003A">
<authorgroup>
- <author><surname>The FreeBSD Documentation Project</surname></author>
+ <author><personname><surname>The FreeBSD Documentation Project</surname></personname></author>
</authorgroup>
- <title>FreeBSD Handbook</title>
- <bibliomisc role="url"><ulink url="http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook"></ulink></bibliomisc>
+ <citetitle>FreeBSD Handbook</citetitle>
+ <bibliomisc xlink:href="http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook">http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook</bibliomisc>
</biblioentry>
- <biblioentry id="freebsd-contributors" xreflabel="FreeBSD, 2002F">
+ <biblioentry xml:id="freebsd-contributors" xreflabel="FreeBSD, 2002F">
<copyright><year>2002</year>
<holder>The FreeBSD Documentation Project</holder>
</copyright>
<publisher>
<publishername>The FreeBSD Documentation Project</publishername>
</publisher>
- <title>Contributors to FreeBSD</title>
- <bibliomisc role="url"><ulink url="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributors/article.html"></ulink></bibliomisc>
+ <citetitle>Contributors to FreeBSD</citetitle>
+ <bibliomisc xlink:href="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributors/article.html">http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributors/article.html</bibliomisc>
</biblioentry>
- <biblioentry id="freebsd-election" xreflabel="FreeBSD, 2002G">
+ <biblioentry xml:id="freebsd-election" xreflabel="FreeBSD, 2002G">
<copyright><year>2002</year>
<holder>The FreeBSD Project</holder>
</copyright>
<publisher>
<publishername>The FreeBSD Project</publishername>
</publisher>
- <title>Core team elections 2002</title>
- <bibliomisc role="url"><ulink url="http://election.uk.freebsd.org"></ulink></bibliomisc>
+ <citetitle>Core team elections 2002</citetitle>
+ <bibliomisc xlink:href="http://election.uk.freebsd.org">http://election.uk.freebsd.org</bibliomisc>
</biblioentry>
- <biblioentry id="freebsd-expiration-policy" xreflabel="FreeBSD, 2002H">
+ <biblioentry xml:id="freebsd-expiration-policy" xreflabel="FreeBSD, 2002H">
<copyright><year>2002</year>
<holder>The FreeBSD Project</holder>
</copyright>
<publisher>
<publishername>The FreeBSD Project</publishername>
</publisher>
- <title>Commit Bit Expiration Policy</title>
+ <citetitle>Commit Bit Expiration Policy</citetitle>
<subtitle>2002/04/06 15:35:30</subtitle>
- <bibliomisc role="url"><ulink url="http://www.freebsd.org/internal/expire-bits.html"></ulink></bibliomisc>
+ <bibliomisc xlink:href="http://www.freebsd.org/internal/expire-bits.html">http://www.freebsd.org/internal/expire-bits.html</bibliomisc>
</biblioentry>
- <biblioentry id="freebsd-new-account" xreflabel="FreeBSD, 2002I">
+ <biblioentry xml:id="freebsd-new-account" xreflabel="FreeBSD, 2002I">
<copyright><year>2002</year>
<holder>The FreeBSD Project</holder>
</copyright>
<publisher>
<publishername>The FreeBSD Project</publishername>
</publisher>
- <title>New Account Creation Procedure</title>
+ <citetitle>New Account Creation Procedure</citetitle>
<subtitle>2002/08/19 17:11:27</subtitle>
- <bibliomisc role="url"><ulink url="http://www.freebsd.org/internal/new-account.html"></ulink></bibliomisc>
+ <bibliomisc xlink:href="http://www.freebsd.org/internal/new-account.html">http://www.freebsd.org/internal/new-account.html</bibliomisc>
</biblioentry>
- <biblioentry id="freebsd-doceng-charter" xreflabel="FreeBSD, 2003B">
+ <biblioentry xml:id="freebsd-doceng-charter" xreflabel="FreeBSD, 2003B">
<copyright><year>2002</year>
<holder>The FreeBSD Documentation Project</holder>
</copyright>
<publisher>
<publishername>The FreeBSD Documentation Project</publishername>
</publisher>
- <title>FreeBSD DocEng Team Charter</title>
+ <citetitle>FreeBSD DocEng Team Charter</citetitle>
<subtitle>2003/03/16 12:17</subtitle>
- <bibliomisc role="url"><ulink url="http://www.freebsd.org/internal/doceng.html"></ulink></bibliomisc>
+ <bibliomisc xlink:href="http://www.freebsd.org/internal/doceng.html">http://www.freebsd.org/internal/doceng.html</bibliomisc>
</biblioentry>
- <biblioentry id="ref-freebsd-trenches" xreflabel="Lehey, 2002">
+ <biblioentry xml:id="ref-freebsd-trenches" xreflabel="Lehey, 2002">
<authorgroup>
- <author><firstname>Greg</firstname><surname>Lehey</surname></author>
+ <author><personname><firstname>Greg</firstname><surname>Lehey</surname></personname></author>
</authorgroup>
<copyright><year>2002</year>
<holder>Greg Lehey</holder>
@@ -2525,9 +2513,9 @@
<publisher>
<publishername>Greg Lehey</publishername>
</publisher>
- <title>Two years in the trenches</title>
+ <citetitle>Two years in the trenches</citetitle>
<subtitle>The evolution of a software project</subtitle>
- <bibliomisc role="url"><ulink url="http://www.lemis.com/grog/In-the-trenches.pdf"></ulink></bibliomisc>
+ <bibliomisc xlink:href="http://www.lemis.com/grog/In-the-trenches.pdf">http://www.lemis.com/grog/In-the-trenches.pdf</bibliomisc>
</biblioentry>
</bibliography>
diff --git a/en_US.ISO8859-1/books/developers-handbook/book.xml b/en_US.ISO8859-1/books/developers-handbook/book.xml
index 622e745d64..941e222568 100644
--- a/en_US.ISO8859-1/books/developers-handbook/book.xml
+++ b/en_US.ISO8859-1/books/developers-handbook/book.xml
@@ -1,20 +1,18 @@
<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE book PUBLIC "-//FreeBSD//DTD DocBook XML V4.5-Based Extension//EN"
- "../../../share/xml/freebsd45.dtd" [
+<!DOCTYPE book PUBLIC "-//FreeBSD//DTD DocBook XML V5.0-Based Extension//EN"
+ "../../../share/xml/freebsd50.dtd" [
<!ENTITY % chapters SYSTEM "chapters.ent"> %chapters;
]>
-
<!--
The FreeBSD Documentation Project
$FreeBSD$
-->
+<book xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:lang="en">
+ <info><title>FreeBSD Developers' Handbook</title>
+
-<book lang='en'>
- <bookinfo>
- <title>FreeBSD Developers' Handbook</title>
-
- <corpauthor>The FreeBSD Documentation Project</corpauthor>
+ <author><orgname>The FreeBSD Documentation Project</orgname></author>
<pubdate>$FreeBSD$</pubdate>
@@ -38,7 +36,7 @@
&legalnotice;
- <legalnotice id="trademarks" role="trademarks">
+ <legalnotice xml:id="trademarks" role="trademarks">
&tm-attrib.freebsd;
&tm-attrib.apple;
&tm-attrib.ibm;
@@ -61,17 +59,15 @@
helping with this project, send email to the &a.doc;.</para>
<para>The latest version of this document is always available
- from the <ulink url="&url.base;/index.html">FreeBSD World
- Wide Web server</ulink>. It may also be downloaded in a
- variety of formats and compression options from the <ulink
- url="ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/">FreeBSD FTP
- server</ulink> or one of the numerous <ulink
- url="&url.books.handbook;/mirrors-ftp.html">mirror
- sites</ulink>.</para>
+ from the <link xlink:href="&url.base;/index.html">FreeBSD World
+ Wide Web server</link>. It may also be downloaded in a
+ variety of formats and compression options from the <link xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/">FreeBSD FTP
+ server</link> or one of the numerous <link xlink:href="&url.books.handbook;/mirrors-ftp.html">mirror
+ sites</link>.</para>
</abstract>
- </bookinfo>
+ </info>
- <part id="Basics">
+ <part xml:id="Basics">
<title>Basics</title>
&chap.introduction;
@@ -82,7 +78,7 @@
&chap.testing;
</part>
- <part id="ipc">
+ <part xml:id="ipc">
<title>Interprocess Communication</title>
&chap.sockets;
@@ -90,7 +86,7 @@
</part>
- <part id="kernel">
+ <part xml:id="kernel">
<title>Kernel</title>
&chap.kernelbuild;
@@ -98,123 +94,86 @@
</part>
- <part id="architectures">
+ <part xml:id="architectures">
<title>Architectures</title>
&chap.x86;
</part>
- <part id="appendices">
+ <part xml:id="appendices">
<title>Appendices</title>
<bibliography>
- <biblioentry id="COD" xreflabel="1">
+ <biblioentry xml:id="COD" xreflabel="1">
<authorgroup>
- <author>
- <firstname>Dave</firstname>
- <othername role="MI">A</othername>
- <surname>Patterson</surname>
- </author>
- <author>
- <firstname>John</firstname>
- <othername role="MI">L</othername>
- <surname>Hennessy</surname>
- </author>
+ <author><personname><firstname>Dave</firstname><othername role="MI">A</othername><surname>Patterson</surname></personname></author>
+ <author><personname><firstname>John</firstname><othername role="MI">L</othername><surname>Hennessy</surname></personname></author>
</authorgroup>
<copyright><year>1998</year><holder>Morgan Kaufmann Publishers,
Inc.</holder></copyright>
- <isbn>1-55860-428-6</isbn>
+ <biblioid class="isbn">1-55860-428-6</biblioid>
<publisher>
<publishername>Morgan Kaufmann Publishers, Inc.</publishername>
</publisher>
- <title>Computer Organization and Design</title>
+ <citetitle>Computer Organization and Design</citetitle>
<subtitle>The Hardware / Software Interface</subtitle>
<pagenums>1-2</pagenums>
</biblioentry>
<biblioentry xreflabel="2">
<authorgroup>
- <author>
- <firstname>W.</firstname>
- <othername role="Middle">Richard</othername>
- <surname>Stevens</surname>
- </author>
+ <author><personname><firstname>W.</firstname><othername role="Middle">Richard</othername><surname>Stevens</surname></personname></author>
</authorgroup>
<copyright><year>1993</year><holder>Addison Wesley Longman,
Inc.</holder></copyright>
- <isbn>0-201-56317-7</isbn>
+ <biblioid class="isbn">0-201-56317-7</biblioid>
<publisher>
<publishername>Addison Wesley Longman, Inc.</publishername>
</publisher>
- <title>Advanced Programming in the Unix Environment</title>
+ <citetitle>Advanced Programming in the Unix Environment</citetitle>
<pagenums>1-2</pagenums>
</biblioentry>
<biblioentry xreflabel="3">
<authorgroup>
- <author>
- <firstname>Marshall</firstname>
- <othername role="Middle">Kirk</othername>
- <surname>McKusick</surname>
- </author>
- <author>
- <firstname>George</firstname>
- <surname>Neville-Neil</surname>
- </author>
+ <author><personname><firstname>Marshall</firstname><othername role="Middle">Kirk</othername><surname>McKusick</surname></personname></author>
+ <author><personname><firstname>George</firstname><surname>Neville-Neil</surname></personname></author>
</authorgroup>
<copyright><year>2004</year><holder>Addison-Wesley</holder></copyright>
- <isbn>0-201-70245-2</isbn>
+ <biblioid class="isbn">0-201-70245-2</biblioid>
<publisher>
<publishername>Addison-Wesley</publishername>
</publisher>
- <title>The Design and Implementation of the FreeBSD Operating System</title>
+ <citetitle>The Design and Implementation of the FreeBSD Operating System</citetitle>
<pagenums>1-2</pagenums>
</biblioentry>
- <biblioentry id="Phrack" xreflabel="4">
+ <biblioentry xml:id="Phrack" xreflabel="4">
<authorgroup>
- <author>
- <firstname>Aleph</firstname>
- <surname>One</surname>
- </author>
+ <author><personname><firstname>Aleph</firstname><surname>One</surname></personname></author>
</authorgroup>
- <title>Phrack 49; "Smashing the Stack for Fun and Profit"</title>
+ <citetitle>Phrack 49; "Smashing the Stack for Fun and Profit"</citetitle>
</biblioentry>
- <biblioentry id="StackGuard" xreflabel="5">
+ <biblioentry xml:id="StackGuard" xreflabel="5">
<authorgroup>
- <author>
- <firstname>Chrispin</firstname>
- <surname>Cowan</surname>
- </author>
- <author>
- <firstname>Calton</firstname>
- <surname>Pu</surname>
- </author>
- <author>
- <firstname>Dave</firstname>
- <surname>Maier</surname>
- </author>
+ <author><personname><firstname>Chrispin</firstname><surname>Cowan</surname></personname></author>
+ <author><personname><firstname>Calton</firstname><surname>Pu</surname></personname></author>
+ <author><personname><firstname>Dave</firstname><surname>Maier</surname></personname></author>
</authorgroup>
- <title>StackGuard; Automatic Adaptive Detection and Prevention of
- Buffer-Overflow Attacks</title>
+ <citetitle>StackGuard; Automatic Adaptive Detection and Prevention of
+ Buffer-Overflow Attacks</citetitle>
</biblioentry>
- <biblioentry id="OpenBSD" xreflabel="6">
+ <biblioentry xml:id="OpenBSD" xreflabel="6">
<authorgroup>
- <author>
- <firstname>Todd</firstname>
- <surname>Miller</surname>
- </author>
- <author>
- <firstname>Theo</firstname>
- <surname>de Raadt</surname>
- </author>
+ <author><personname><firstname>Todd</firstname><surname>Miller</surname></personname></author>
+ <author><personname><firstname>Theo</firstname><surname>de Raadt</surname></personname></author>
</authorgroup>
- <title>strlcpy and strlcat -- consistent, safe string copy and
- concatenation.</title>
+ <citetitle>strlcpy and strlcat -- consistent, safe string copy and
+ concatenation.</citetitle>
</biblioentry>
</bibliography>
diff --git a/en_US.ISO8859-1/books/developers-handbook/introduction/chapter.xml b/en_US.ISO8859-1/books/developers-handbook/introduction/chapter.xml
index 0f7e8270b7..899c0bc0a3 100644
--- a/en_US.ISO8859-1/books/developers-handbook/introduction/chapter.xml
+++ b/en_US.ISO8859-1/books/developers-handbook/introduction/chapter.xml
@@ -4,24 +4,16 @@
$FreeBSD$
-->
-
-<chapter id="introduction">
- <chapterinfo>
+<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:id="introduction">
+ <info><title>Introduction</title>
<authorgroup>
- <author>
- <firstname>Murray</firstname>
- <surname>Stokely</surname>
- <contrib>Contributed by </contrib>
- </author>
- <author>
- <firstname>Jeroen</firstname>
- <surname>Ruigrok van der Werven</surname>
- </author>
+ <author><personname><firstname>Murray</firstname><surname>Stokely</surname></personname><contrib>Contributed by </contrib></author>
+ <author><personname><firstname>Jeroen</firstname><surname>Ruigrok van der Werven</surname></personname></author>
</authorgroup>
- </chapterinfo>
- <title>Introduction</title>
+ </info>
+
- <sect1 id="introduction-devel">
+ <sect1 xml:id="introduction-devel">
<title>Developing on FreeBSD</title>
<para>So here we are. System all installed and you are ready to
@@ -36,7 +28,7 @@
for the programmer unfamiliar with the &os; platform.</para>
</sect1>
- <sect1 id="introduction-bsdvision">
+ <sect1 xml:id="introduction-bsdvision">
<title>The BSD Vision</title>
<para>To produce the best &unix; like operating system package
@@ -45,7 +37,7 @@
stability.</para>
</sect1>
- <sect1 id="introduction-archguide">
+ <sect1 xml:id="introduction-archguide">
<title>Architectural Guidelines</title>
<para>Our ideology can be described by the following
@@ -94,13 +86,13 @@
<para>From Scheifler &amp; Gettys: "X Window System"</para>
</sect1>
- <sect1 id="introduction-layout">
+ <sect1 xml:id="introduction-layout">
<title>The Layout of
- <filename class="directory">/usr/src</filename></title>
+ <filename>/usr/src</filename></title>
<para>The complete source code to FreeBSD is available from our
public repository. The source code is normally installed in
- <filename class="directory">/usr/src</filename> which contains
+ <filename>/usr/src</filename> which contains
the following subdirectories:</para>
<para>
@@ -115,140 +107,111 @@
<tbody>
<row>
- <entry><filename
- class="directory">bin/</filename></entry>
+ <entry><filename>bin/</filename></entry>
<entry>Source for files in
<filename>/bin</filename></entry>
</row>
<row>
- <entry><filename
- class="directory">cddl/</filename></entry>
+ <entry><filename>cddl/</filename></entry>
<entry>Utilities covered by the Common Development and
Distribution License</entry>
</row>
<row>
- <entry><filename
- class="directory">contrib/</filename></entry>
+ <entry><filename>contrib/</filename></entry>
<entry>Source for files from contributed
software.</entry>
</row>
<row>
- <entry><filename
- class="directory">crypto/</filename></entry>
+ <entry><filename>crypto/</filename></entry>
<entry>Cryptographical sources</entry>
</row>
<row>
- <entry><filename
- class="directory">etc/</filename></entry>
- <entry>Source for files in <filename
- class="directory">/etc</filename></entry>
+ <entry><filename>etc/</filename></entry>
+ <entry>Source for files in <filename>/etc</filename></entry>
</row>
<row>
- <entry><filename
- class="directory">games/</filename></entry>
- <entry>Source for files in <filename
- class="directory">/usr/games</filename></entry>
+ <entry><filename>games/</filename></entry>
+ <entry>Source for files in <filename>/usr/games</filename></entry>
</row>
<row>
- <entry><filename
- class="directory">gnu/</filename></entry>
+ <entry><filename>gnu/</filename></entry>
<entry>Utilities covered by the GNU Public
License</entry>
</row>
<row>
- <entry><filename
- class="directory">include/</filename></entry>
- <entry>Source for files in <filename
- class="directory">/usr/include</filename></entry>
+ <entry><filename>include/</filename></entry>
+ <entry>Source for files in <filename>/usr/include</filename></entry>
</row>
<row>
- <entry><filename
- class="directory">kerberos5/</filename></entry>
+ <entry><filename>kerberos5/</filename></entry>
<entry>Source for Kerberos version 5</entry>
</row>
<row>
- <entry><filename
- class="directory">lib/</filename></entry>
- <entry>Source for files in <filename
- class="directory">/usr/lib</filename></entry>
+ <entry><filename>lib/</filename></entry>
+ <entry>Source for files in <filename>/usr/lib</filename></entry>
</row>
<row>
- <entry><filename
- class="directory">libexec/</filename></entry>
- <entry>Source for files in <filename
- class="directory">/usr/libexec</filename></entry>
+ <entry><filename>libexec/</filename></entry>
+ <entry>Source for files in <filename>/usr/libexec</filename></entry>
</row>
<row>
- <entry><filename
- class="directory">release/</filename></entry>
+ <entry><filename>release/</filename></entry>
<entry>Files required to produce a FreeBSD
release</entry>
</row>
<row>
- <entry><filename
- class="directory">rescue/</filename></entry>
+ <entry><filename>rescue/</filename></entry>
<entry>Build system for the
- <filename class="directory">/rescue</filename>
+ <filename>/rescue</filename>
utilities</entry>
</row>
<row>
- <entry><filename
- class="directory">sbin/</filename></entry>
- <entry>Source for files in <filename
- class="directory">/sbin</filename></entry>
+ <entry><filename>sbin/</filename></entry>
+ <entry>Source for files in <filename>/sbin</filename></entry>
</row>
<row>
- <entry><filename
- class="directory">secure/</filename></entry>
+ <entry><filename>secure/</filename></entry>
<entry>FreeSec sources</entry>
</row>
<row>
- <entry><filename
- class="directory">share/</filename></entry>
- <entry>Source for files in <filename
- class="directory">/usr/share</filename></entry>
+ <entry><filename>share/</filename></entry>
+ <entry>Source for files in <filename>/usr/share</filename></entry>
</row>
<row>
- <entry><filename
- class="directory">sys/</filename></entry>
+ <entry><filename>sys/</filename></entry>
<entry>Kernel source files</entry>
</row>
<row>
- <entry><filename
- class="directory">tools/</filename></entry>
+ <entry><filename>tools/</filename></entry>
<entry>Tools used for maintenance and testing of
FreeBSD</entry>
</row>
<row>
- <entry><filename
- class="directory">usr.bin/</filename></entry>
- <entry>Source for files in <filename
- class="directory">/usr/bin</filename></entry>
+ <entry><filename>usr.bin/</filename></entry>
+ <entry>Source for files in <filename>/usr/bin</filename></entry>
</row>
<row>
- <entry><filename
- class="directory">usr.sbin/</filename></entry>
- <entry>Source for files in <filename
- class="directory">/usr/sbin</filename></entry>
+ <entry><filename>usr.sbin/</filename></entry>
+ <entry>Source for files in <filename>/usr/sbin</filename></entry>
</row>
</tbody>
</tgroup>
diff --git a/en_US.ISO8859-1/books/developers-handbook/ipv6/chapter.xml b/en_US.ISO8859-1/books/developers-handbook/ipv6/chapter.xml
index 66c0ff75b9..1ec2147461 100644
--- a/en_US.ISO8859-1/books/developers-handbook/ipv6/chapter.xml
+++ b/en_US.ISO8859-1/books/developers-handbook/ipv6/chapter.xml
@@ -4,29 +4,23 @@
$FreeBSD$
-->
-
-<chapter id="ipv6">
+<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:id="ipv6">
<title>IPv6 Internals</title>
- <sect1 id="ipv6-implementation">
- <sect1info>
+ <sect1 xml:id="ipv6-implementation">
+ <info><title>IPv6/IPsec Implementation</title>
<authorgroup>
- <author>
- <firstname>Yoshinobu</firstname>
- <surname>Inoue</surname>
- <contrib>Contributed by </contrib>
- </author>
+ <author><personname><firstname>Yoshinobu</firstname><surname>Inoue</surname></personname><contrib>Contributed by </contrib></author>
</authorgroup>
- <!-- March 2000 -->
- </sect1info>
+
+ </info>
- <title>IPv6/IPsec Implementation</title>
+
<para>This section should explain IPv6 and IPsec related implementation
- internals. These functionalities are derived from <ulink
- url="http://www.kame.net/">KAME project</ulink></para>
+ internals. These functionalities are derived from <link xlink:href="http://www.kame.net/">KAME project</link></para>
- <sect2 id="ipv6details">
+ <sect2 xml:id="ipv6details">
<title>IPv6</title>
<sect3>
@@ -42,9 +36,9 @@
<para>Conformance tests have been performed on the KAME STABLE kit
at TAHI project. Results can be viewed at
- <ulink url="http://www.tahi.org/report/KAME/"></ulink>.
+ <uri xlink:href="http://www.tahi.org/report/KAME/">http://www.tahi.org/report/KAME/</uri>.
We also attended Univ. of New Hampshire IOL tests
- (<ulink url="http://www.iol.unh.edu/"></ulink>) in the
+ (<uri xlink:href="http://www.iol.unh.edu/">http://www.iol.unh.edu/</uri>) in the
past, with our past snapshots.</para>
<itemizedlist>
@@ -233,8 +227,7 @@
<itemizedlist>
<listitem>
<para>IPv4 mapped address (3.7) and special behavior of IPv6
- wildcard bind socket (3.8) are supported. See <link
- linkend="ipv6-wildcard-socket">23.5.1.12</link>
+ wildcard bind socket (3.8) are supported. See <link linkend="ipv6-wildcard-socket">23.5.1.12</link>
in this document for details.</para>
</listitem>
</itemizedlist>
@@ -308,7 +301,7 @@
</itemizedlist>
</sect3>
- <sect3 id="neighbor-discovery">
+ <sect3 xml:id="neighbor-discovery">
<title>Neighbor Discovery</title>
<para>Neighbor Discovery is fairly stable. Currently Address
@@ -367,7 +360,7 @@
we may provide sysctl knob for the variable.</para>
</sect3>
- <sect3 id="ipv6-scope-index">
+ <sect3 xml:id="ipv6-scope-index">
<title>Scope Index</title>
<para>IPv6 uses scoped addresses. Therefore, it is very important to
@@ -430,7 +423,7 @@
link and an interface, which is stronger than what specs say.</para>
</sect3>
- <sect3 id="ipv6-pnp">
+ <sect3 xml:id="ipv6-pnp">
<title>Plug and Play</title>
<para>Most of the IPv6 stateless address autoconfiguration is implemented
@@ -549,7 +542,7 @@ fe80:2::%ep0/64 link#2 UC ep0</screen>
</sect4>
</sect3>
- <sect3 id="gif">
+ <sect3 xml:id="gif">
<title>Generic tunnel interface</title>
<para>GIF (Generic InterFace) is a pseudo interface for configured
@@ -577,8 +570,7 @@ fe80:2::%ep0/64 link#2 UC ep0</screen>
routing tables to perform infinite level of tunneling.
<emphasis>Please be warned</emphasis>.</para>
- <para>gif can be configured to be ECN-friendly. See <link
- linkend="ipsec-ecn">23.5.4.5</link> for ECN-friendliness of
+ <para>gif can be configured to be ECN-friendly. See <link linkend="ipsec-ecn">23.5.4.5</link> for ECN-friendliness of
tunnels, and &man.gif.4; for how to configure.</para>
<para>If you would like to configure an IPv4-in-IPv6 tunnel with gif
@@ -587,7 +579,7 @@ fe80:2::%ep0/64 link#2 UC ep0</screen>
interface.</para>
</sect3>
- <sect3 id="ipv6-sas">
+ <sect3 xml:id="ipv6-sas">
<title>Source Address Selection</title>
<para>Current source selection rule is scope oriented (there are some
@@ -633,8 +625,7 @@ fe80:2::%ep0/64 link#2 UC ep0</screen>
<para>For instance, ::1 is selected for ff01::1,
fe80:1::200:f8ff:fe01:6317 for fe80:1::2a0:24ff:feab:839b (note
- that embedded interface index - described in <link
- linkend="ipv6-scope-index">23.5.1.3</link> - helps us
+ that embedded interface index - described in <link linkend="ipv6-scope-index">23.5.1.3</link> - helps us
choose the right source address. Those embedded indices will not
be on the wire). If the outgoing interface has multiple address for
the scope, a source is selected longest match basis (rule 3). Suppose
@@ -664,7 +655,7 @@ fe80:2::%ep0/64 link#2 UC ep0</screen>
address).</para>
</sect3>
- <sect3 id="ipv6-jumbo">
+ <sect3 xml:id="ipv6-jumbo">
<title>Jumbo Payload</title>
<para>The Jumbo Payload hop-by-hop option is implemented and can
@@ -782,7 +773,7 @@ fe80:2::%ep0/64 link#2 UC ep0</screen>
attack.)</para>
</sect3>
- <sect3 id="icmpv6">
+ <sect3 xml:id="icmpv6">
<title>ICMPv6</title>
<para>After RFC2463 was published, IETF ipngwg has decided to
@@ -853,7 +844,7 @@ fe80:2::%ep0/64 link#2 UC ep0</screen>
<para>Both IP and IP6 reassemble functions never call m_pullup().</para>
</sect3>
- <sect3 id="ipv6-wildcard-socket">
+ <sect3 xml:id="ipv6-wildcard-socket">
<title>IPv4 mapped address and IPv6 wildcard socket</title>
<para>RFC2553 describes IPv4 mapped address (3.7) and special behavior
@@ -1217,7 +1208,7 @@ FreeBSD 4.x configurable supported
</sect3>
</sect2>
- <sect2 id="ipsec-implementation">
+ <sect2 xml:id="ipsec-implementation">
<title>IPsec</title>
<para>IPsec is mainly organized by three components.</para>
@@ -1327,9 +1318,8 @@ FreeBSD 4.x configurable supported
<filename>rfc240[1-6].txt</filename>,
<filename>rfc241[01].txt</filename>, <filename>rfc2451.txt</filename>
and <filename>draft-mcdonald-simple-ipsec-api-01.txt</filename>
- (draft expired, but you can take from <ulink
- url="ftp://ftp.kame.net/pub/internet-drafts/">
- ftp://ftp.kame.net/pub/internet-drafts/</ulink>).
+ (draft expired, but you can take from <link xlink:href="ftp://ftp.kame.net/pub/internet-drafts/">
+ ftp://ftp.kame.net/pub/internet-drafts/</link>).
(NOTE: IKE specifications, <filename>rfc241[7-9].txt</filename> are
implemented in userland, as "racoon" IKE daemon)</para>
@@ -1475,7 +1465,7 @@ FreeBSD 4.x configurable supported
property issues only).</para>
</sect3>
- <sect3 id="ipsec-ecn">
+ <sect3 xml:id="ipsec-ecn">
<title>ECN consideration on IPsec tunnels</title>
<para>ECN-friendly IPsec tunnel is supported as described in
@@ -1489,9 +1479,8 @@ FreeBSD 4.x configurable supported
lost.</para>
<para>To make IPsec tunnel ECN-friendly, we should modify encapsulation
- and decapsulation procedure. This is described in <ulink
- url="http://www.aciri.org/floyd/papers/draft-ipsec-ecn-00.txt">
- http://www.aciri.org/floyd/papers/draft-ipsec-ecn-00.txt</ulink>,
+ and decapsulation procedure. This is described in <link xlink:href="http://www.aciri.org/floyd/papers/draft-ipsec-ecn-00.txt">
+ http://www.aciri.org/floyd/papers/draft-ipsec-ecn-00.txt</link>,
chapter 3.</para>
<para>IPsec tunnel implementation can give you three behaviors, by
@@ -1554,9 +1543,8 @@ ECN allowed copy TOS bits except for ECN use inner TOS bits with some
<para>For more information, please refer to:</para>
- <para><ulink
- url="http://www.aciri.org/floyd/papers/draft-ipsec-ecn-00.txt">
- http://www.aciri.org/floyd/papers/draft-ipsec-ecn-00.txt</ulink>,
+ <para><link xlink:href="http://www.aciri.org/floyd/papers/draft-ipsec-ecn-00.txt">
+ http://www.aciri.org/floyd/papers/draft-ipsec-ecn-00.txt</link>,
RFC2481 (Explicit Congestion Notification),
src/sys/netinet6/{ah,esp}_input.c</para>
diff --git a/en_US.ISO8859-1/books/developers-handbook/kernelbuild/chapter.xml b/en_US.ISO8859-1/books/developers-handbook/kernelbuild/chapter.xml
index 0c147b8eb6..9b3420b8ab 100644
--- a/en_US.ISO8859-1/books/developers-handbook/kernelbuild/chapter.xml
+++ b/en_US.ISO8859-1/books/developers-handbook/kernelbuild/chapter.xml
@@ -4,8 +4,7 @@
$FreeBSD$
-->
-
-<chapter id="kernelbuild">
+<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:id="kernelbuild">
<title>Building and Installing a &os; Kernel</title>
<para>Being a kernel developer requires understanding of the kernel
@@ -24,21 +23,20 @@
<note>
<para>It is supposed that the reader of this chapter is familiar
- with the information described in the <ulink
- url="../handbook/kernelconfig-building.html">Building and
- Installing a Custom Kernel</ulink> chapter of the &os;
+ with the information described in the <link xlink:href="../handbook/kernelconfig-building.html">Building and
+ Installing a Custom Kernel</link> chapter of the &os;
Handbook. If this is not the case, please read through the above
mentioned chapter to understand how the build process
works.</para>
</note>
- <sect1 id="kernelbuild-traditional">
+ <sect1 xml:id="kernelbuild-traditional">
<title>Building a Kernel the <quote>Traditional</quote> Way</title>
<para>Up to version 4.X of &os; this was the recommended way to
build a new kernel. It can still be used on newer versions
(instead of the <quote>buildkernel</quote> target of the toplevel
- <filename class="directory">/usr/src/</filename> makefiles).
+ <filename>/usr/src/</filename> makefiles).
Building the kernel this way may be useful when working on the
kernel code and it may actually be faster than the
<quote>New</quote> procedure when only a single option or two were
@@ -51,7 +49,7 @@
<para>Run &man.config.8; to generate the kernel source
code:</para>
- <screen>&prompt.root; <userinput>/usr/sbin/config <replaceable>MYKERNEL</replaceable></userinput></screen>
+ <screen>&prompt.root; <userinput>/usr/sbin/config MYKERNEL</userinput></screen>
</step>
<step>
@@ -59,7 +57,7 @@
print the name of this directory after being run as
above.</para>
- <screen>&prompt.root; <userinput>cd ../compile/<replaceable>MYKERNEL</replaceable></userinput></screen>
+ <screen>&prompt.root; <userinput>cd ../compile/MYKERNEL</userinput></screen>
</step>
<step>
@@ -77,13 +75,12 @@
</procedure>
</sect1>
- <sect1 id="kernelbuild-new">
+ <sect1 xml:id="kernelbuild-new">
<title>Building a Kernel the <quote>New</quote> Way</title>
<para>This procedure is well supported and recommended under the
- latest &os; releases and is documented in the <ulink
- url="../handbook/kernelconfig-building.html">Building and
- Installing a Custom Kernel</ulink> chapter of the &os;
+ latest &os; releases and is documented in the <link xlink:href="../handbook/kernelconfig-building.html">Building and
+ Installing a Custom Kernel</link> chapter of the &os;
Handbook.</para>
</sect1>
</chapter>
diff --git a/en_US.ISO8859-1/books/developers-handbook/kerneldebug/chapter.xml b/en_US.ISO8859-1/books/developers-handbook/kerneldebug/chapter.xml
index b901c833e4..cc5b911182 100644
--- a/en_US.ISO8859-1/books/developers-handbook/kerneldebug/chapter.xml
+++ b/en_US.ISO8859-1/books/developers-handbook/kerneldebug/chapter.xml
@@ -4,29 +4,18 @@
$FreeBSD$
-->
-
-<chapter id="kerneldebug">
- <chapterinfo>
+<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:id="kerneldebug">
+ <info><title>Kernel Debugging</title>
<authorgroup>
- <author>
- <firstname>Paul</firstname>
- <surname>Richards</surname>
- <contrib>Contributed by </contrib>
- </author>
- <author>
- <firstname>J&ouml;rg</firstname>
- <surname>Wunsch</surname>
- </author>
- <author>
- <firstname>Robert</firstname>
- <surname>Watson</surname>
- </author>
+ <author><personname><firstname>Paul</firstname><surname>Richards</surname></personname><contrib>Contributed by </contrib></author>
+ <author><personname><firstname>J&ouml;rg</firstname><surname>Wunsch</surname></personname></author>
+ <author><personname><firstname>Robert</firstname><surname>Watson</surname></personname></author>
</authorgroup>
- </chapterinfo>
+ </info>
- <title>Kernel Debugging</title>
+
- <sect1 id="kerneldebug-obtain">
+ <sect1 xml:id="kerneldebug-obtain">
<title>Obtaining a Kernel Crash Dump</title>
<para>When running a development kernel (e.g., &os.current;), such as a
@@ -64,7 +53,7 @@
memory dump, as most problems can be isolated only using kernel
state.</para>
- <sect2 id="config-dumpdev">
+ <sect2 xml:id="config-dumpdev">
<title>Configuring the Dump Device</title>
<para>Before the kernel will dump the contents of its physical
@@ -101,7 +90,7 @@
</important>
</sect2>
- <sect2 id="extract-dump">
+ <sect2 xml:id="extract-dump">
<title>Extracting a Kernel Dump</title>
<para>Once a dump has been written to a dump device, the dump
@@ -149,7 +138,7 @@
</sect2>
</sect1>
- <sect1 id="kerneldebug-gdb">
+ <sect1 xml:id="kerneldebug-gdb">
<title>Debugging a Kernel Crash Dump with <command>kgdb</command></title>
<note>
@@ -164,8 +153,8 @@
the crash dump, locate the debug version of your kernel
(normally called <filename>kernel.debug</filename>) and the path
to the source files used to build your kernel (normally
- <filename>/usr/obj/usr/src/sys/<replaceable>KERNCONF</replaceable></filename>,
- where <filename><replaceable>KERNCONF</replaceable></filename>
+ <filename>/usr/obj/usr/src/sys/KERNCONF</filename>,
+ where <filename>KERNCONF</filename>
is the <varname>ident</varname> specified in a kernel
&man.config.5;). With those two pieces of info, let the
debugging commence!</para>
@@ -173,7 +162,7 @@
<para>To enter into the debugger and begin getting information
from the dump, the following steps are required at a minimum:</para>
- <screen>&prompt.root; <userinput>cd /usr/obj/usr/src/sys/<replaceable>KERNCONF</replaceable></userinput>
+ <screen>&prompt.root; <userinput>cd /usr/obj/usr/src/sys/KERNCONF</userinput>
&prompt.root; <userinput>kgdb kernel.debug /var/crash/vmcore.0</userinput></screen>
<para>You can debug the crash dump using the kernel sources just like
@@ -191,7 +180,7 @@
your patch winds its way into the source tree via a problem
report, mailing lists, or by being able to commit it!</para>
- <screen> 1:&prompt.root; <userinput>cd /usr/obj/usr/src/sys/<replaceable>KERNCONF</replaceable></userinput>
+ <screen> 1:&prompt.root; <userinput>cd /usr/obj/usr/src/sys/KERNCONF</userinput>
2:&prompt.root; <userinput>kgdb kernel.debug /var/crash/vmcore.0</userinput>
3:GNU gdb 5.2.1 (FreeBSD)
4:Copyright 2002 Free Software Foundation, Inc.
@@ -432,12 +421,12 @@
considerable amount of disk space!</para></tip>
</sect1>
- <sect1 id="kerneldebug-ddd">
+ <sect1 xml:id="kerneldebug-ddd">
<title>Debugging a Crash Dump with DDD</title>
<para>Examining a kernel crash dump with a graphical debugger like
<command>ddd</command> is also possible (you will need to install
- the <filename role="package">devel/ddd</filename> port in order to use the
+ the <package>devel/ddd</package> port in order to use the
<command>ddd</command> debugger). Add the <option>-k</option>
option to the <command>ddd</command> command line you would use
normally. For example;</para>
@@ -448,7 +437,7 @@
<command>ddd</command>'s graphical interface.</para>
</sect1>
- <sect1 id="kerneldebug-online-ddb">
+ <sect1 xml:id="kerneldebug-online-ddb">
<title>On-Line Kernel Debugging Using DDB</title>
<para>While <command>kgdb</command> as an off-line debugger provides a very
@@ -468,8 +457,7 @@
<programlisting>options KDB</programlisting>
<programlisting>options DDB</programlisting>
- to your config file, and rebuild. (See <ulink
- url="&url.books.handbook;/index.html">The FreeBSD Handbook</ulink> for details on
+ to your config file, and rebuild. (See <link xlink:href="&url.books.handbook;/index.html">The FreeBSD Handbook</link> for details on
configuring the FreeBSD kernel).</para>
<note>
@@ -671,7 +659,7 @@
single-stepping the kernel.</para>
</sect1>
- <sect1 id="kerneldebug-online-gdb">
+ <sect1 xml:id="kerneldebug-online-gdb">
<title>On-Line Kernel Debugging Using Remote GDB</title>
<para>This feature has been supported since FreeBSD 2.2, and it is
@@ -741,7 +729,7 @@ Debugger (msg=0xf01b0383 "Boot flags requested debugger")
window), etc.</para>
</sect1>
- <sect1 id="kerneldebug-console">
+ <sect1 xml:id="kerneldebug-console">
<title>Debugging a Console Driver</title>
<para>Since you need a console driver to run DDB on, things are more
@@ -753,7 +741,7 @@ Debugger (msg=0xf01b0383 "Boot flags requested debugger")
console.</para>
</sect1>
- <sect1 id="kerneldebug-deadlocks">
+ <sect1 xml:id="kerneldebug-deadlocks">
<title>Debugging Deadlocks</title>
<para>You may experience so called deadlocks, the situation where
@@ -786,7 +774,7 @@ Debugger (msg=0xf01b0383 "Boot flags requested debugger")
stack, and do a backtrace with <command>where</command>.</para>
</sect1>
- <sect1 id="kerneldebug-dcons">
+ <sect1 xml:id="kerneldebug-dcons">
<title>Kernel debugging with Dcons</title>
<para>&man.dcons.4; is a very simple console driver that is
@@ -912,7 +900,7 @@ hw.firewire.dcons_crom.force_console=1</screen>
<para>Run &man.dconschat.8;, with:</para>
- <screen>&prompt.root; <userinput>dconschat -e \# -br -G 12345 -t <replaceable>00-11-22-33-44-55-66-77</replaceable></userinput></screen>
+ <screen>&prompt.root; <userinput>dconschat -e \# -br -G 12345 -t 00-11-22-33-44-55-66-77</userinput></screen>
<para>The following key combinations can be used once
&man.dconschat.8; is running:</para>
@@ -1034,7 +1022,7 @@ LANG=C ddd --debugger kgdb kernel /dev/fwmem0.2</screen>
</sect2>
</sect1>
- <sect1 id="kerneldebug-options">
+ <sect1 xml:id="kerneldebug-options">
<title>Glossary of Kernel Options for Debugging</title>
<para>This section provides a brief glossary of compile-time kernel
diff --git a/en_US.ISO8859-1/books/developers-handbook/l10n/chapter.xml b/en_US.ISO8859-1/books/developers-handbook/l10n/chapter.xml
index 1dbc259899..7a30e9b404 100644
--- a/en_US.ISO8859-1/books/developers-handbook/l10n/chapter.xml
+++ b/en_US.ISO8859-1/books/developers-handbook/l10n/chapter.xml
@@ -4,11 +4,10 @@
$FreeBSD$
-->
-
- <chapter id="l10n">
+<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:id="l10n">
<title>Localization and Internationalization - L10N and I18N</title>
- <sect1 id="l10n-programming">
+ <sect1 xml:id="l10n-programming">
<title>Programming I18N Compliant Applications</title>
<indexterm><primary>Qt</primary></indexterm>
<indexterm><primary>GTK</primary></indexterm>
@@ -60,18 +59,14 @@
</sect2>
</sect1>
- <sect1 id="posix-nls">
- <sect1info>
+ <sect1 xml:id="posix-nls">
+ <info><title>Localized Messages with POSIX.1 Native Language Support (NLS)</title>
<authorgroup>
- <author>
- <firstname>G&aacute;bor</firstname>
- <surname>K&ouml;vesd&aacute;n</surname>
- <contrib>Contributed by </contrib>
- </author>
+ <author><personname><firstname>G&aacute;bor</firstname><surname>K&ouml;vesd&aacute;n</surname></personname><contrib>Contributed by </contrib></author>
</authorgroup>
- </sect1info>
+ </info>
- <title>Localized Messages with POSIX.1 Native Language Support (NLS)</title>
+
<para>Beyond the basic I18N functions, like supporting various input
encodings or supporting national conventions, such as the different
@@ -80,7 +75,7 @@
this is using the POSIX.1 NLS functions, which are provided as a part
of the &os; base system.</para>
- <sect2 id="nls-catalogs">
+ <sect2 xml:id="nls-catalogs">
<title>Organizing Localized Messages into Catalog Files</title>
<para>POSIX.1 NLS is based on catalog files, which contain the
@@ -116,22 +111,19 @@
&man.gencat.1;.</para>
</sect2>
- <sect2 id="nls-using">
+ <sect2 xml:id="nls-using">
<title>Using the Catalog Files from the Source Code</title>
<para>Using the catalog files is simple. To use
- the related functions, <filename
- class="headerfile">nl_types.h</filename> must be included. Before
+ the related functions, <filename>nl_types.h</filename> must be included. Before
using a catalog, it has to be opened with &man.catopen.3;.
The function takes two arguments. The first parameter is the name of the
installed and compiled catalog. Usually, the name of the
program is used, such as <application>grep</application>.
This name will be used when looking for the compiled
catalog file. The &man.catopen.3; call looks for this file
- in <filename
- class="directory">/usr/share/nls/<replaceable>locale</replaceable>/<replaceable>catname</replaceable></filename>
- and in <filename
- class="directory">/usr/local/share/nls/<replaceable>locale</replaceable>/<replaceable>catname</replaceable></filename>,
+ in <filename>/usr/share/nls/locale/catname</filename>
+ and in <filename>/usr/local/share/nls/locale/catname</filename>,
where <literal>locale</literal> is the locale set and
<literal>catname</literal> is the catalog name being
discussed. The second parameter is a constant, which can have
@@ -165,7 +157,7 @@
&man.catclose.3;, which has one argument, the catalog id.</para>
</sect2>
- <sect2 id="nls-example">
+ <sect2 xml:id="nls-example">
<title>A Practical Example</title>
<para>The following example will demonstrate an easy solution on how to
@@ -262,8 +254,7 @@ if (!S_ISDIR(st.st_mode)) {
and users will see the usual <quote>Not a directory</quote>
error message when they encounter this error. This message
will probably seem more familiar to them. Please note that
- it was necessary to include <filename
- class="headerfile">errno.h</filename> in order to directly
+ it was necessary to include <filename>errno.h</filename> in order to directly
access <varname>errno</varname>.</para>
<para>It is worth to note that there are cases when
@@ -279,7 +270,7 @@ if ((p = malloc(size)) == NULL)
</sect3>
</sect2>
- <sect2 id="nls-mk">
+ <sect2 xml:id="nls-mk">
<title>Making use of <filename>bsd.nls.mk</filename></title>
<para>Using the catalog files requires few repeatable steps,
@@ -291,13 +282,13 @@ if ((p = malloc(size)) == NULL)
such as <filename>bsd.prog.mk</filename> or
<filename>bsd.lib.mk</filename>.</para>
- <para>Usually it is enough to define <makevar>NLSNAME</makevar>,
+ <para>Usually it is enough to define <varname>NLSNAME</varname>,
which should have the catalog name mentioned as the first
argument of &man.catopen.3; and list the catalog files in
- <makevar>NLS</makevar> without their <literal>.msg</literal>
+ <varname>NLS</varname> without their <literal>.msg</literal>
extension. Here is an example, which makes it possible to
to disable NLS when used with the code examples before.
- The <makevar>WITHOUT_NLS</makevar> &man.make.1; variable has
+ The <varname>WITHOUT_NLS</varname> &man.make.1; variable has
to be defined in order to build the program without NLS
support.</para>
@@ -311,13 +302,13 @@ CFLAGS+= -DWITHOUT_NLS
.endif</programlisting>
<para>Conventionally, the catalog files are placed under the
- <filename class="directory">nls</filename> subdirectory and
+ <filename>nls</filename> subdirectory and
this is the default behaviour of <filename>bsd.nls.mk</filename>.
It is possible, though to override the location of the
- catalogs with the <makevar>NLSSRCDIR</makevar> &man.make.1;
+ catalogs with the <varname>NLSSRCDIR</varname> &man.make.1;
variable. The default name of the precompiled catalog files
also follow the naming convention mentioned before. It can be
- overridden by setting the <makevar>NLSNAME</makevar> variable.
+ overridden by setting the <varname>NLSNAME</varname> variable.
There are other options to fine tune the processing of the catalog
files but usually it is not needed, thus they are not described
here. For further information on <filename>bsd.nls.mk</filename>,
diff --git a/en_US.ISO8859-1/books/developers-handbook/policies/chapter.xml b/en_US.ISO8859-1/books/developers-handbook/policies/chapter.xml
index 7da8cc7186..fc94e3ae5b 100644
--- a/en_US.ISO8859-1/books/developers-handbook/policies/chapter.xml
+++ b/en_US.ISO8859-1/books/developers-handbook/policies/chapter.xml
@@ -4,29 +4,21 @@
$FreeBSD$
-->
-
-<chapter id="policies">
- <chapterinfo>
+<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:id="policies">
+ <info><title>Source Tree Guidelines and Policies</title>
<authorgroup>
- <author>
- <firstname>Poul-Henning</firstname>
- <surname>Kamp</surname>
- <contrib>Contributed by </contrib>
- </author>
- <author>
- <firstname>Giorgos</firstname>
- <surname>Keramidas</surname>
- </author>
+ <author><personname><firstname>Poul-Henning</firstname><surname>Kamp</surname></personname><contrib>Contributed by </contrib></author>
+ <author><personname><firstname>Giorgos</firstname><surname>Keramidas</surname></personname></author>
</authorgroup>
- <!-- June 1996 -->
- </chapterinfo>
+
+ </info>
- <title>Source Tree Guidelines and Policies</title>
+
<para>This chapter documents various guidelines and policies in
force for the FreeBSD source tree.</para>
- <sect1 id="policies-style">
+ <sect1 xml:id="policies-style">
<title>Style Guidelines</title>
<indexterm><primary>style</primary></indexterm>
@@ -37,8 +29,8 @@
&man.style.Makefile.5;.</para>
</sect1>
- <sect1 id="policies-maintainer">
- <title><makevar>MAINTAINER</makevar> on Makefiles</title>
+ <sect1 xml:id="policies-maintainer">
+ <title><varname>MAINTAINER</varname> on Makefiles</title>
<indexterm><primary>ports maintainer</primary></indexterm>
@@ -48,10 +40,10 @@
entry in the <filename>src/MAINTAINERS</filename> file.
Maintainers of ports within the Ports Collection express their
maintainership to the world by adding a
- <makevar>MAINTAINER</makevar> line to the
+ <varname>MAINTAINER</varname> line to the
<filename>Makefile</filename> of the port in question:</para>
- <programlisting><makevar>MAINTAINER</makevar>= <replaceable>email-addresses</replaceable></programlisting>
+ <programlisting><varname>MAINTAINER</varname>= <replaceable>email-addresses</replaceable></programlisting>
<tip>
<para>For other parts of the repository, or for sections not
@@ -97,27 +89,17 @@
</itemizedlist>
</sect1>
- <sect1 id="policies-contributed">
- <sect1info>
+ <sect1 xml:id="policies-contributed">
+ <info><title>Contributed Software</title>
<authorgroup>
- <author>
- <firstname>Poul-Henning</firstname>
- <surname>Kamp</surname>
- <contrib>Contributed by </contrib>
- </author>
- <author>
- <firstname>David</firstname>
- <surname>O'Brien</surname>
- </author>
- <author>
- <firstname>Gavin</firstname>
- <surname>Atkinson</surname>
- </author>
+ <author><personname><firstname>Poul-Henning</firstname><surname>Kamp</surname></personname><contrib>Contributed by </contrib></author>
+ <author><personname><firstname>David</firstname><surname>O'Brien</surname></personname></author>
+ <author><personname><firstname>Gavin</firstname><surname>Atkinson</surname></personname></author>
</authorgroup>
- <!-- June 1996 -->
- </sect1info>
+
+ </info>
- <title>Contributed Software</title>
+
<indexterm><primary>contributed software</primary></indexterm>
@@ -161,17 +143,13 @@
still tracking the vendor branch.</para>
</note>
- <sect2 id="vendor-import-svn">
- <sect2info>
+ <sect2 xml:id="vendor-import-svn">
+ <info><title>Vendor Imports with SVN</title>
<authorgroup>
- <author>
- <firstname>Dag-Erling</firstname>
- <surname>Sm&oslash;rgrav</surname>
- <contrib>Contributed by </contrib>
- </author>
+ <author><personname><firstname>Dag-Erling</firstname><surname>Sm&oslash;rgrav</surname></personname><contrib>Contributed by </contrib></author>
</authorgroup>
- </sect2info>
- <title>Vendor Imports with SVN</title>
+ </info>
+
<para>This section describes the vendor import procedure with
<application>Subversion</application> in details.</para>
@@ -189,18 +167,18 @@
<acronym>SVN</acronym>, vendor branches were imported with
the same layout as the main tree. For example, the
<application>foo</application> vendor sources ended up in
- <filename>vendor/<replaceable>foo</replaceable>/dist/contrib/<replaceable>foo</replaceable></filename>,
+ <filename>vendor/foo/dist/contrib/foo</filename>,
but it is pointless and rather inconvenient. What we
really want is to have the vendor source directly in
- <filename>vendor/<replaceable>foo</replaceable>/dist</filename>,
+ <filename>vendor/foo/dist</filename>,
like this:</para>
- <screen>&prompt.user; <userinput><command>cd</command> <filename class="directory">vendor/<replaceable>foo</replaceable>/dist/contrib/<replaceable>foo</replaceable></filename></userinput>
-&prompt.user; <userinput><command>svn move</command> $(svn list) <filename>../..</filename></userinput>
-&prompt.user; <userinput><command>cd</command> <filename>../..</filename></userinput>
-&prompt.user; <userinput><command>svn remove</command> <filename>contrib</filename></userinput>
-&prompt.user; <userinput><command>svn propdel</command> <option>-R</option> svn:mergeinfo</userinput>
-&prompt.user; <userinput><command>svn commit</command></userinput></screen>
+ <screen>&prompt.user; <userinput>cd vendor/foo/dist/contrib/foo</userinput>
+&prompt.user; <userinput>svn move $(svn list) ../..</userinput>
+&prompt.user; <userinput>cd ../..</userinput>
+&prompt.user; <userinput>svn remove contrib</userinput>
+&prompt.user; <userinput>svn propdel -R svn:mergeinfo</userinput>
+&prompt.user; <userinput>svn commit</userinput></screen>
<para>Note that, the <literal>propdel</literal> bit is
necessary because starting with 1.5, Subversion will
@@ -221,17 +199,17 @@
unmodified vendor code. In some cases, it can be even be
harmful.</para>
- <screen>&prompt.user; <userinput><command>svn propdel</command> svn:keywords <option>-R</option> <filename>.</filename></userinput>
-&prompt.user; <userinput><command>svn commit</command></userinput></screen>
+ <screen>&prompt.user; <userinput>svn propdel svn:keywords -R .</userinput>
+&prompt.user; <userinput>svn commit</userinput></screen>
<para>Bootstrapping of <literal>svn:mergeinfo</literal> on
the target directory (in the main tree) to the revision
that corresponds to the last change was made to the vendor
tree prior to importing new sources is also needed:</para>
- <screen>&prompt.user; <userinput><command>cd</command> <filename>head/contrib/<replaceable>foo</replaceable></filename></userinput>
-&prompt.user; <userinput><command>svn merge</command> <option>--record-only</option> <replaceable>svn_base</replaceable>/vendor/<replaceable>foo</replaceable>/dist@<replaceable>12345678</replaceable> <filename>.</filename></userinput>
-&prompt.user; <userinput><command>svn commit</command></userinput></screen>
+ <screen>&prompt.user; <userinput>cd head/contrib/foo</userinput>
+&prompt.user; <userinput>svn merge --record-only svn_base/vendor/foo/dist@12345678 .</userinput>
+&prompt.user; <userinput>svn commit</userinput></screen>
<para>where <replaceable>svn_base</replaceable> is the base
directory of your <acronym>SVN</acronym> repository, e.g.
@@ -253,30 +231,30 @@
sorted lists of the contents of the vendor tree and of the
sources you are about to import:</para>
- <screen>&prompt.user; <userinput><command>cd</command> <filename>vendor/<replaceable>foo</replaceable>/dist</filename></userinput>
-&prompt.user; <userinput><command>svn list</command> <option>-R</option> | <command>grep</command> <option>-v</option> '/$' | <command>sort</command> > <filename>../<replaceable>old</replaceable></filename></userinput>
-&prompt.user; <userinput><command>cd</command> <filename>../<replaceable>foo-9.9</replaceable></filename></userinput>
-&prompt.user; <userinput><command>find</command> <filename>.</filename> <option>-type</option> f | <command>cut</command> <option>-c</option> 3- | <command>sort</command> > <filename>../<replaceable>new</replaceable></filename></userinput></screen>
+ <screen>&prompt.user; <userinput>cd vendor/foo/dist</userinput>
+&prompt.user; <userinput>svn list -R | grep -v '/$' | sort &gt; ../old</userinput>
+&prompt.user; <userinput>cd ../foo-9.9</userinput>
+&prompt.user; <userinput>find . -type f | cut -c 3- | sort &gt; ../new</userinput></screen>
<para>With these two files, the following command will list
list removed files (files only in
- <filename><replaceable>old</replaceable></filename>):</para>
+ <filename>old</filename>):</para>
- <screen>&prompt.user; <userinput><command>comm <option>-23</option> <filename>../<replaceable>old</replaceable></filename> <filename>../<replaceable>new</replaceable></filename></command></userinput></screen>
+ <screen>&prompt.user; <userinput>comm -23 ../old ../new</userinput></screen>
<para>While the command below will list added files (files
only in
- <filename><replaceable>new</replaceable></filename>):</para>
+ <filename>new</filename>):</para>
- <screen>&prompt.user; <userinput><command>comm <option>-13</option> <filename>../<replaceable>old</replaceable></filename> <filename>../<replaceable>new</replaceable></filename></command></userinput></screen>
+ <screen>&prompt.user; <userinput>comm -13 ../old ../new</userinput></screen>
<para>Let's put this together:</para>
- <screen>&prompt.user; <userinput><command>cd</command> <filename class="directory">vendor/<replaceable>foo</replaceable>/<replaceable>foo-9.9</replaceable></filename></userinput>
-&prompt.user; <userinput><command>tar</command> cf - <filename>.</filename> | <command>tar</command> xf - <option>-C</option> <filename>../dist</filename></userinput>
-&prompt.user; <userinput><command>cd</command> <filename class="directory">../dist</filename></userinput>
-&prompt.user; <userinput><command>comm</command> <option>-23</option> <filename>../<replaceable>old</replaceable></filename> <filename>../<replaceable>new</replaceable></filename> | <command>xargs</command> svn remove</userinput>
-&prompt.user; <userinput><command>comm</command> <option>-13</option> <filename>../<replaceable>old</replaceable></filename> <filename>../<replaceable>new</replaceable></filename> | <command>xargs</command> svn add</userinput></screen>
+ <screen>&prompt.user; <userinput>cd vendor/foo/foo-9.9</userinput>
+&prompt.user; <userinput>tar cf - . | tar xf - -C ../dist</userinput>
+&prompt.user; <userinput>cd ../dist</userinput>
+&prompt.user; <userinput>comm -23 ../old ../new | xargs svn remove</userinput>
+&prompt.user; <userinput>comm -13 ../old ../new | xargs svn add</userinput></screen>
<warning>
<para>If there are new directories in the new
@@ -325,11 +303,11 @@
should tag it for future reference. The best and quickest
way is to do it directly in the repository:</para>
- <screen>&prompt.user; <userinput><command>svn copy</command> <filename><replaceable>svn_base</replaceable>/vendor/<replaceable>foo</replaceable>/dist</filename> <filename><replaceable>svn_base</replaceable>/vendor/<replaceable>foo</replaceable>/<replaceable>9.9</replaceable></filename></userinput></screen>
+ <screen>&prompt.user; <userinput>svn copy svn_base/vendor/foo/dist svn_base/vendor/foo/9.9</userinput></screen>
<para>To get the new tag, you can update your working copy
of
- <filename>vendor/<replaceable>foo</replaceable></filename>.</para>
+ <filename>vendor/foo</filename>.</para>
<note>
<para>If you choose to do the copy in the checkout
@@ -347,9 +325,9 @@
<acronym>SVN</acronym> not to handle merge conflicts yet,
because they will be taken care of manually:</para>
- <screen>&prompt.user; <userinput><command>cd</command> <filename class="directory">head/contrib/<replaceable>foo</replaceable></filename></userinput>
-&prompt.user; <userinput><command>svn update</command></userinput>
-&prompt.user; <userinput><command>svn merge</command> <option>--accept=postpone</option> <filename><replaceable>svn_base</replaceable>/vendor/<replaceable>foo</replaceable>/dist</filename></userinput></screen>
+ <screen>&prompt.user; <userinput>cd head/contrib/foo</userinput>
+&prompt.user; <userinput>svn update</userinput>
+&prompt.user; <userinput>svn merge --accept=postpone svn_base/vendor/foo/dist</userinput></screen>
<para>Resolve any conflicts, and make sure that any files
that were added or removed in the vendor tree have been
@@ -357,7 +335,7 @@
a good idea to check differences against the vendor
branch:</para>
- <screen>&prompt.user; <userinput><command>svn diff</command> <option>--no-diff-deleted</option> <option>--old=</option><filename><replaceable>svn_base</replaceable>/vendor/<replaceable>foo</replaceable>/dist</filename> <option>--new=</option><filename>.</filename></userinput></screen>
+ <screen>&prompt.user; <userinput>svn diff --no-diff-deleted --old=svn_base/vendor/foo/dist --new=.</userinput></screen>
<para>The <option>--no-diff-deleted</option> option tells
<acronym>SVN</acronym> not to check files that are in the
@@ -392,7 +370,7 @@
</sect2>
</sect1>
- <sect1 id="policies-encumbered">
+ <sect1 xml:id="policies-encumbered">
<title>Encumbered Files</title>
<para>It might occasionally be necessary to include an encumbered
@@ -423,8 +401,8 @@
<listitem>
<para>Any encumbered file requires specific approval from the
- <ulink url="&url.base;/administration.html#t-core">Core
- Team</ulink> before it is added to the repository.</para>
+ <link xlink:href="&url.base;/administration.html#t-core">Core
+ Team</link> before it is added to the repository.</para>
</listitem>
<listitem>
@@ -440,7 +418,7 @@
<listitem>
<para>Object files are named
- <filename><replaceable>arch</replaceable>/<replaceable>filename</replaceable>.o.uu></filename>.</para>
+ <filename>arch/filename.o.uu&gt;</filename>.</para>
</listitem>
<listitem>
@@ -455,12 +433,10 @@
<listitem>
<para>Should always be in <filename>LINT</filename>, but
- the <ulink
- url="&url.base;/administration.html#t-core">Core
- Team</ulink> decides per case if it should be
- commented out or not. The <ulink
- url="&url.base;/administration.html#t-core">Core
- Team</ulink> can, of course, change their minds later
+ the <link xlink:href="&url.base;/administration.html#t-core">Core
+ Team</link> decides per case if it should be
+ commented out or not. The <link xlink:href="&url.base;/administration.html#t-core">Core
+ Team</link> can, of course, change their minds later
on.</para>
</listitem>
@@ -476,18 +452,16 @@
<orderedlist>
<listitem>
- <para>The <ulink
- url="&url.base;/administration.html#t-core">Core
- team</ulink><indexterm><primary>core
+ <para>The <link xlink:href="&url.base;/administration.html#t-core">Core
+ team</link><indexterm><primary>core
team</primary></indexterm> decides if
the code should be part of
<command>make world</command>.</para>
</listitem>
<listitem>
- <para>The <ulink
- url="&url.base;/administration.html#t-re">Release
- Engineering</ulink><indexterm><primary>release
+ <para>The <link xlink:href="&url.base;/administration.html#t-re">Release
+ Engineering</link><indexterm><primary>release
engineering</primary></indexterm>
decides if it goes into the release.</para>
</listitem>
@@ -496,27 +470,17 @@
</orderedlist>
</sect1>
- <sect1 id="policies-shlib">
- <sect1info>
+ <sect1 xml:id="policies-shlib">
+ <info><title>Shared Libraries</title>
<authorgroup>
- <author>
- <firstname>Satoshi</firstname>
- <surname>Asami</surname>
- <contrib>Contributed by </contrib>
- </author>
- <author>
- <firstname>Peter</firstname>
- <surname>Wemm</surname>
- </author>
- <author>
- <firstname>David</firstname>
- <surname>O'Brien</surname>
- </author>
+ <author><personname><firstname>Satoshi</firstname><surname>Asami</surname></personname><contrib>Contributed by </contrib></author>
+ <author><personname><firstname>Peter</firstname><surname>Wemm</surname></personname></author>
+ <author><personname><firstname>David</firstname><surname>O'Brien</surname></personname></author>
</authorgroup>
- <!-- 9 Dec 1996 -->
- </sect1info>
+
+ </info>
- <title>Shared Libraries</title>
+
<para>If you are adding shared library support to a port or other
piece of software that does not have one, the version numbers
diff --git a/en_US.ISO8859-1/books/developers-handbook/secure/chapter.xml b/en_US.ISO8859-1/books/developers-handbook/secure/chapter.xml
index 4a655c189c..eb5d53b7a2 100644
--- a/en_US.ISO8859-1/books/developers-handbook/secure/chapter.xml
+++ b/en_US.ISO8859-1/books/developers-handbook/secure/chapter.xml
@@ -4,21 +4,16 @@
$FreeBSD$
-->
-
- <chapter id="secure">
- <chapterinfo>
+<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:id="secure">
+ <info><title>Secure Programming</title>
<authorgroup>
- <author>
- <firstname>Murray</firstname>
- <surname>Stokely</surname>
- <contrib>Contributed by </contrib>
- </author>
+ <author><personname><firstname>Murray</firstname><surname>Stokely</surname></personname><contrib>Contributed by </contrib></author>
</authorgroup>
- </chapterinfo>
+ </info>
- <title>Secure Programming</title>
+
- <sect1 id="secure-synopsis"><title>Synopsis</title>
+ <sect1 xml:id="secure-synopsis"><title>Synopsis</title>
<para>This chapter describes some of the security issues that
have plagued &unix; programmers for decades and some of the new
@@ -26,7 +21,7 @@
code.</para>
</sect1>
- <sect1 id="secure-philosophy"><title>Secure Design
+ <sect1 xml:id="secure-philosophy"><title>Secure Design
Methodology</title>
<para>Writing secure applications takes a very scrutinous and
@@ -45,7 +40,7 @@
operations are rarely atomic.</para>
</sect1>
- <sect1 id="secure-bufferov"><title>Buffer Overflows</title>
+ <sect1 xml: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.
@@ -230,8 +225,7 @@ int main() {
<function>strlcpy</function> and <function>strlcat</function>
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
+ more information about these functions see <xref linkend="OpenBSD"/>. The OpenBSD <function>strlcpy</function> and
<function>strlcat</function> instructions have been in FreeBSD
since 3.3.</para>
@@ -317,7 +311,7 @@ int main() {
</sect2>
</sect1>
- <sect1 id="secure-setuid"><title>SetUID issues</title>
+ <sect1 xml:id="secure-setuid"><title>SetUID issues</title>
<indexterm><primary>seteuid</primary></indexterm>
@@ -350,7 +344,7 @@ int main() {
</sect1>
- <sect1 id="secure-chroot"><title>Limiting your program's environment</title>
+ <sect1 xml:id="secure-chroot"><title>Limiting your program's environment</title>
<indexterm><primary>chroot()</primary></indexterm>
@@ -438,8 +432,7 @@ int main() {
<para>&posix; has released a working draft that adds event
auditing, access control lists, fine grained privileges,
information labeling, and mandatory access control.</para>
- <para>This is a work in progress and is the focus of the <ulink
- url="http://www.trustedbsd.org/">TrustedBSD</ulink> project. Some
+ <para>This is a work in progress and is the focus of the <link xlink:href="http://www.trustedbsd.org/">TrustedBSD</link> project. Some
of the initial work has been committed to &os.current;
(cap_set_proc(3)).</para>
@@ -447,7 +440,7 @@ int main() {
</sect1>
- <sect1 id="secure-trust"><title>Trust</title>
+ <sect1 xml:id="secure-trust"><title>Trust</title>
<para>An application should never assume that anything about the
users environment is sane. This includes (but is certainly not
@@ -479,7 +472,7 @@ int main() {
</sect1>
- <sect1 id="secure-race-conditions">
+ <sect1 xml:id="secure-race-conditions">
<title>Race Conditions</title>
<para>A race condition is anomalous behavior caused by the
diff --git a/en_US.ISO8859-1/books/developers-handbook/sockets/chapter.xml b/en_US.ISO8859-1/books/developers-handbook/sockets/chapter.xml
index 7cb263be69..c6c76fcf24 100644
--- a/en_US.ISO8859-1/books/developers-handbook/sockets/chapter.xml
+++ b/en_US.ISO8859-1/books/developers-handbook/sockets/chapter.xml
@@ -4,21 +4,16 @@
$FreeBSD$
-->
-
-<chapter id="sockets">
- <chapterinfo>
+<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:id="sockets">
+ <info><title>Sockets</title>
<authorgroup>
- <author>
- <firstname>G. Adam</firstname>
- <surname>Stanislav</surname>
- <contrib>Contributed by </contrib>
- </author>
+ <author><personname><firstname>G. Adam</firstname><surname>Stanislav</surname></personname><contrib>Contributed by </contrib></author>
</authorgroup>
- </chapterinfo>
+ </info>
- <title>Sockets</title>
+
- <sect1 id="sockets-synopsis">
+ <sect1 xml:id="sockets-synopsis">
<title>Synopsis</title>
<para><acronym>BSD</acronym> sockets take interprocess
@@ -45,7 +40,7 @@
</sect1>
- <sect1 id="sockets-diversity">
+ <sect1 xml:id="sockets-diversity">
<title>Networking and Diversity</title>
<para>We have already hinted on the <emphasis>diversity</emphasis>
@@ -85,7 +80,7 @@
</para>
</sect1>
- <sect1 id="sockets-protocols">
+ <sect1 xml:id="sockets-protocols">
<title>Protocols</title>
<para>While various programming languages tend to have complex
@@ -324,7 +319,7 @@
</sect1>
- <sect1 id="sockets-model">
+ <sect1 xml:id="sockets-model">
<title>The Sockets Model</title>
<para><acronym>BSD</acronym> sockets are built on the basic &unix;
@@ -349,7 +344,7 @@
</sect1>
- <sect1 id="sockets-essential-functions">
+ <sect1 xml:id="sockets-essential-functions">
<title>Essential Socket Functions</title>
<para>While FreeBSD offers different functions to work with
@@ -357,17 +352,17 @@
<quote>open</quote> a socket. And in some cases we only need
two.</para>
- <sect2 id="sockets-client-server">
+ <sect2 xml:id="sockets-client-server">
<title>The Client-Server Difference</title>
<para>Typically, one of the ends of a socket-based data
communication is a <emphasis>server</emphasis>, the other is a
<emphasis>client</emphasis>.</para>
- <sect3 id="sockets-common-elements">
+ <sect3 xml:id="sockets-common-elements">
<title>The Common Elements</title>
- <sect4 id="sockets-socket">
+ <sect4 xml:id="sockets-socket">
<title><function>socket</function></title>
<para>The one function used by both, clients and servers, is
@@ -418,7 +413,7 @@ int socket(int domain, int type, int protocol);
meaningful. In that case, use <constant>0</constant> for
its value.</para>
- <note id="sockets-unconnected">
+ <note xml:id="sockets-unconnected">
<title>The Unconnected Socket</title>
<para>Nowhere, in the <function>socket</function> function
@@ -434,7 +429,7 @@ int socket(int domain, int type, int protocol);
</sect4>
- <sect4 id="sockets-sockaddr">
+ <sect4 xml:id="sockets-sockaddr">
<title><varname>sockaddr</varname></title>
<para>Various functions of the sockets family expect the
@@ -598,10 +593,8 @@ struct sockaddr_in {
<constant>AF_INET</constant> in the address family
field. <constant>AF_INET</constant> is defined as
<constant>2</constant>. Let us use the
- <acronym>IP</acronym> address of <hostid
- role="ipaddr">192.43.244.18</hostid>, which is the time
- server of US federal government (<hostid
- role="domainname">time.nist.gov</hostid>).</para>
+ <acronym>IP</acronym> address of <systemitem class="ipaddress">192.43.244.18</systemitem>, which is the time
+ server of US federal government (<systemitem class="fqdomainname">time.nist.gov</systemitem>).</para>
<mediaobject>
<imageobject>
@@ -643,7 +636,7 @@ struct in_addr {
<para>In addition, <varname>in_addr_t</varname> is a 32-bit
integer.</para>
- <para>The <hostid role="ipaddr">192.43.244.18</hostid> is
+ <para>The <systemitem class="ipaddress">192.43.244.18</systemitem> is
just a convenient notation of expressing a 32-bit integer
by listing all of its 8-bit bytes, starting with the
<emphasis>most significant</emphasis> one.</para>
@@ -905,7 +898,7 @@ struct in_addr {
</sect3>
- <sect3 id="sockets-client-functions">
+ <sect3 xml:id="sockets-client-functions">
<title>Client Functions</title>
<para>Typically, the client initiates the connection to the
@@ -917,7 +910,7 @@ struct in_addr {
asking for the person in charge of wingdings (the
<emphasis>port</emphasis>).</para>
- <sect4 id="sockets-connect">
+ <sect4 xml:id="sockets-connect">
<title><function>connect</function></title>
<para>Once a client has created a socket, it needs to
@@ -952,13 +945,12 @@ int connect(int s, const struct sockaddr *name, socklen_t namelen);
</sect4>
- <sect4 id="sockets-first-client">
+ <sect4 xml:id="sockets-first-client">
<title>Our First Client</title>
<para>We now know enough to write a very simple client, one
- that will get current time from <hostid
- role="ipaddr">192.43.244.18</hostid> and print it to
- <devicename>stdout</devicename>.</para>
+ that will get current time from <systemitem class="ipaddress">192.43.244.18</systemitem> and print it to
+ <filename>stdout</filename>.</para>
<programlisting>
/*
@@ -1020,7 +1012,7 @@ int main() {
</sect3>
- <sect3 id="sockets-server-functions">
+ <sect3 xml:id="sockets-server-functions">
<title>Server Functions</title>
<para>The typical server does not initiate the
@@ -1034,7 +1026,7 @@ int main() {
<para>The sockets interface offers three basic functions to
handle this.</para>
- <sect4 id="sockets-bind">
+ <sect4 xml:id="sockets-bind">
<title><function>bind</function></title>
<para>Ports are like extensions to a phone line: After you
@@ -1095,7 +1087,7 @@ int bind(int s, const struct sockaddr *addr, socklen_t addrlen);
</mediaobject>
</sect4>
- <sect4 id="sockets-listen">
+ <sect4 xml:id="sockets-listen">
<title><function>listen</function></title>
<para>To continue our office phone analogy, after you have
@@ -1120,7 +1112,7 @@ int listen(int s, int backlog);
</sect4>
- <sect4 id="sockets-accept">
+ <sect4 xml:id="sockets-accept">
<title><function>accept</function></title>
<para>After you hear the phone ringing, you accept the call
@@ -1157,7 +1149,7 @@ int accept(int s, struct sockaddr *addr, socklen_t *addrlen);
</sect4>
- <sect4 id="sockets-first-server">
+ <sect4 xml:id="sockets-first-server">
<title>Our First Server</title>
<para>Our first server will be somewhat more complex than
@@ -1514,19 +1506,19 @@ Connection closed by foreign host.
</sect1>
- <sect1 id="sockets-helper-functions">
+ <sect1 xml:id="sockets-helper-functions">
<title>Helper Functions</title>
<para>FreeBSD C library contains many helper functions for sockets
programming. For example, in our sample client we hard coded
- the <hostid role="domainname">time.nist.gov</hostid>
+ the <systemitem class="fqdomainname">time.nist.gov</systemitem>
<acronym>IP</acronym> address. But we do not always know the
<acronym>IP</acronym> address. Even if we do, our software is
more flexible if it allows the user to enter the
<acronym>IP</acronym> address, or even the domain name.
</para>
- <sect2 id="sockets-gethostbyname">
+ <sect2 xml:id="sockets-gethostbyname">
<title><function>gethostbyname</function></title>
<para>While there is no way to pass the domain name directly to
@@ -1608,18 +1600,15 @@ int main(int argc, char *argv[]) {
address, it works both ways) on the command line, and the
program will try to connect to its
<emphasis>daytime</emphasis> server. Otherwise, it will still
- default to <hostid
- role="domainname">time.nist.gov</hostid>. However, even in
+ default to <systemitem class="fqdomainname">time.nist.gov</systemitem>. However, even in
this case we will use <function>gethostbyname</function>
- rather than hard coding <hostid
- role="ipaddr">192.43.244.18</hostid>. That way, even if its
+ rather than hard coding <systemitem class="ipaddress">192.43.244.18</systemitem>. That way, even if its
<acronym>IP</acronym> address changes in the future, we will
still find it.</para>
<para>Since it takes virtually no time to get the time from your
local server, you could run <application>daytime</application>
- twice in a row: First to get the time from <hostid
- role="domainname">time.nist.gov</hostid>, the second time from
+ twice in a row: First to get the time from <systemitem class="fqdomainname">time.nist.gov</systemitem>, the second time from
your own system. You can then compare the results and see how
exact your system clock is:</para>
@@ -1635,7 +1624,7 @@ int main(int argc, char *argv[]) {
</sect2>
- <sect2 id="sockets-getservbyname">
+ <sect2 xml:id="sockets-getservbyname">
<title><function>getservbyname</function></title>
<para>Sometimes you may not be sure what port a certain service
@@ -1680,7 +1669,7 @@ struct servent * getservbyname(const char *name, const char *proto);
</sect1>
- <sect1 id="sockets-concurrent-servers">
+ <sect1 xml:id="sockets-concurrent-servers">
<title>Concurrent Servers</title>
<para>Unlike a sequential server, a <emphasis>concurrent
diff --git a/en_US.ISO8859-1/books/developers-handbook/testing/chapter.xml b/en_US.ISO8859-1/books/developers-handbook/testing/chapter.xml
index 1f0150ea6f..99c2148356 100644
--- a/en_US.ISO8859-1/books/developers-handbook/testing/chapter.xml
+++ b/en_US.ISO8859-1/books/developers-handbook/testing/chapter.xml
@@ -4,8 +4,7 @@
$FreeBSD$
-->
-
-<chapter id="testing">
+<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:id="testing">
<title>Regression and Performance Testing</title>
<para>Regression tests are used to exercise a particular bit of the
@@ -13,10 +12,9 @@
old bugs are not reintroduced.</para>
<para>The &os; regression testing tools can be found in the &os;
- source tree in the directory <filename
- class="directory">src/tools/regression</filename>.</para>
+ source tree in the directory <filename>src/tools/regression</filename>.</para>
- <section id="testing-micro-benchmark">
+ <section xml:id="testing-micro-benchmark">
<title>Micro Benchmark Checklist</title>
<para>This section contains hints for doing proper
@@ -61,8 +59,8 @@
</listitem>
<listitem>
- <para>Mount <filename class="directory">/</filename>,
- <filename class="directory">/usr</filename>, and any other
+ <para>Mount <filename>/</filename>,
+ <filename>/usr</filename>, and any other
file system as read-only if possible. This removes atime
updates to disk (etc.) from the I/O picture.</para>
</listitem>
@@ -73,12 +71,11 @@
&man.dump.8; file before every run. Unmount and mount it
before starting the test. This results in a consistent file
system layout. For a worldstone test this would apply to
- <filename class="directory">/usr/obj</filename> (just
+ <filename>/usr/obj</filename> (just
reinitialize with <command>newfs</command> and mount). To
get 100% reproducibility, populate the file system from a
&man.dd.1; file (i.e.: <command>dd
- if=<filename>myimage</filename> of=<filename
- class="devicefile">/dev/ad0s1h</filename>
+ if=myimage of=/dev/ad0s1h
bs=1m</command>)</para>
</listitem>
@@ -215,7 +212,7 @@
</itemizedlist>
</section>
- <section id="testing-tinderbox">
+ <section xml:id="testing-tinderbox">
<title>The &os; Source Tinderbox</title>
<para>The source Tinderbox consists of:</para>
@@ -250,8 +247,7 @@
<para>The scripts are maintained and were developed by &a.des.email;,
and are now written in Perl, a move on from their original
incarnation as shell scripts. All scripts and configuration
- files are kept in <ulink
- url="http://www.freebsd.org/cgi/cvsweb.cgi/projects/tinderbox/">/projects/tinderbox/</ulink>.</para>
+ files are kept in <link xlink:href="http://www.freebsd.org/cgi/cvsweb.cgi/projects/tinderbox/">/projects/tinderbox/</link>.</para>
<para>For more information about the tinderbox and tbmaster
scripts at this stage, see their respective man pages:
@@ -367,11 +363,11 @@
have rank 9999.</para>
</listitem>
<listitem>
- <para><literal>RELENG_<replaceable>x</replaceable></literal>
+ <para><literal>RELENG_x</literal>
has rank <replaceable>xx</replaceable>99.</para>
</listitem>
<listitem>
- <para><literal>RELENG_<replaceable>x</replaceable>_<replaceable>y</replaceable></literal>
+ <para><literal>RELENG_x_y</literal>
has rank <replaceable>xxyy</replaceable>.</para>
</listitem>
</itemizedlist>
@@ -416,11 +412,9 @@
<section>
<title>Official Build Servers</title>
- <para>The official Tinderbox build servers are hosted by <ulink
- url="http://www.sentex.ca">Sentex Data
- Communications</ulink>, who also host the <ulink
- url="http://www.freebsd.org/projects/netperf/cluster.html">&os;
- Netperf Cluster</ulink>.</para>
+ <para>The official Tinderbox build servers are hosted by <link xlink:href="http://www.sentex.ca">Sentex Data
+ Communications</link>, who also host the <link xlink:href="http://www.freebsd.org/projects/netperf/cluster.html">&os;
+ Netperf Cluster</link>.</para>
<para>Three build servers currently exist:</para>
@@ -468,8 +462,7 @@
<title>Official Summary Site</title>
<para>Summaries and logs from the official build servers are
- available online at <ulink
- url="http://tinderbox.FreeBSD.org">http://tinderbox.FreeBSD.org</ulink>,
+ available online at <link xlink:href="http://tinderbox.FreeBSD.org">http://tinderbox.FreeBSD.org</link>,
hosted by &a.des.email; and set up as follows:</para>
<itemizedlist>
diff --git a/en_US.ISO8859-1/books/developers-handbook/tools/chapter.xml b/en_US.ISO8859-1/books/developers-handbook/tools/chapter.xml
index 890979af7d..8f50cdf03f 100644
--- a/en_US.ISO8859-1/books/developers-handbook/tools/chapter.xml
+++ b/en_US.ISO8859-1/books/developers-handbook/tools/chapter.xml
@@ -4,24 +4,16 @@
$FreeBSD$
-->
-
-<chapter id="tools">
- <chapterinfo>
+<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:id="tools">
+ <info><title>Programming Tools</title>
<authorgroup>
- <author>
- <firstname>James</firstname>
- <surname>Raynard</surname>
- <contrib>Contributed by </contrib>
- </author>
- <author>
- <firstname>Murray</firstname>
- <surname>Stokely</surname>
- </author>
+ <author><personname><firstname>James</firstname><surname>Raynard</surname></personname><contrib>Contributed by </contrib></author>
+ <author><personname><firstname>Murray</firstname><surname>Stokely</surname></personname></author>
</authorgroup>
- </chapterinfo>
+ </info>
- <title>Programming Tools</title>
- <sect1 id="tools-synopsis"><title>Synopsis</title>
+
+ <sect1 xml:id="tools-synopsis"><title>Synopsis</title>
<para>This chapter is an introduction to using some of the
programming tools supplied with FreeBSD, although much of it
@@ -33,7 +25,7 @@
</sect1>
- <sect1 id="tools-intro"><title>Introduction</title>
+ <sect1 xml:id="tools-intro"><title>Introduction</title>
<para>FreeBSD offers an excellent development environment.
Compilers for C and C++ and an assembler come with the
@@ -62,7 +54,7 @@
</sect1>
- <sect1 id="tools-programming">
+ <sect1 xml:id="tools-programming">
<title>Introduction to Programming</title>
<para>A program is a set of instructions that tell the computer to
@@ -121,8 +113,8 @@
<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.</para>
+ <link xlink:href="&url.books.handbook;/ports-using.html">
+ Ports section</link> of the handbook.</para>
<variablelist>
<varlistentry>
@@ -139,10 +131,10 @@
<para>The Bywater Basic Interpreter can be found in the
Ports Collection as
- <filename role="package">lang/bwbasic</filename>
+ <package>lang/bwbasic</package>
and the Phil Cockroft's Basic Interpreter
(formerly Rabbit Basic) is available as
- <filename role="package">lang/pbasic</filename>.</para>
+ <package>lang/pbasic</package>.</para>
</listitem>
</varlistentry>
@@ -164,14 +156,14 @@
<para>Various implementations of Lisp that can run on &unix;
systems are available in the Ports Collection for &os;.
GNU Common Lisp can be found as
- <filename role="package">lang/gcl</filename>. CLISP
+ <package>lang/gcl</package>. CLISP
by Bruno Haible and Michael Stoll is available as
- <filename role="package">lang/clisp</filename>.
+ <package>lang/clisp</package>.
For CMUCL, which includes a highly-optimizing compiler too, or
simpler Lisp implementations like SLisp, which implements most
of the Common Lisp constructs in a few hundred lines of C code,
- <filename role="package">lang/cmucl</filename> and
- <filename role="package">lang/slisp</filename> are available
+ <package>lang/cmucl</package> and
+ <package>lang/slisp</package> are available
respectively.</para>
</listitem>
</varlistentry>
@@ -185,7 +177,7 @@
writing <acronym>CGI</acronym> scripts.</para>
<para>Perl is available in the Ports Collection as
- <filename role="package">lang/perl5.16</filename> for all
+ <package>lang/perl5.16</package> for all
&os; releases.</para>
</listitem>
</varlistentry>
@@ -201,12 +193,12 @@
abstraction to be used in research work.</para>
<para>Scheme is available from the Ports Collection as
- <filename role="package">lang/elk</filename> for the
+ <package>lang/elk</package> for the
Elk Scheme Interpreter. The MIT Scheme Interpreter
can be found in
- <filename role="package">lang/mit-scheme</filename>
+ <package>lang/mit-scheme</package>
and the SCM Scheme Interpreter in
- <filename role="package">lang/scm</filename>.</para>
+ <package>lang/scm</package>.</para>
</listitem>
</varlistentry>
@@ -218,7 +210,7 @@
facilities for processing strings and structures.
The version of Icon for &os; can be found in the
Ports Collection as
- <filename role="package">lang/icon</filename>.</para>
+ <package>lang/icon</package>.</para>
</listitem>
</varlistentry>
@@ -235,7 +227,7 @@
<para>The latest version of Logo for &os; is available from
the Ports Collection in
- <filename role="package">lang/logo</filename>.</para>
+ <package>lang/logo</package>.</para>
</listitem>
</varlistentry>
@@ -253,7 +245,7 @@
<para>The latest version of Python is available from the
Ports Collection in
- <filename role="package">lang/python</filename>.</para>
+ <package>lang/python</package>.</para>
</listitem>
</varlistentry>
@@ -268,7 +260,7 @@
programs.</para>
<para>Ruby is available from the Ports Collection as
- <filename role="package">lang/ruby18</filename>.</para>
+ <package>lang/ruby18</package>.</para>
</listitem>
</varlistentry>
@@ -285,7 +277,7 @@
<para>Various versions of Tcl are available as ports
for &os;. The latest version, Tcl 8.5, can be found in
- <filename role="package">lang/tcl85</filename>.</para>
+ <package>lang/tcl85</package>.</para>
</listitem>
</varlistentry>
</variablelist>
@@ -324,7 +316,7 @@
using separate programs, many commercial compiler makers have
produced Integrated Development Environments
(<acronym>IDE</acronym>s for short). FreeBSD does not include
- an IDE in the base system, but <filename role="package">devel/kdevelop</filename> is
+ an IDE in the base system, but <package>devel/kdevelop</package> is
available in the Ports Collection and many use
<application>Emacs</application> for this purpose. Using
<application>Emacs</application> as an IDE is discussed in
@@ -333,7 +325,7 @@
</sect1>
- <sect1 id="tools-compiling">
+ <sect1 xml:id="tools-compiling">
<title>Compiling with <command>cc</command></title>
<para>This section deals with the <application>gcc</application>
@@ -448,8 +440,8 @@
</footnote></para>
<informalexample>
- <screen>&prompt.user; <userinput>cc foobar.c</userinput> <lineannotation>executable is <filename>a.out</filename></lineannotation>
-&prompt.user; <userinput>cc -o foobar foobar.c</userinput> <lineannotation>executable is <filename>foobar</filename></lineannotation>
+ <screen>&prompt.user; <userinput>cc foobar.c</userinput> <lineannotation>executable is a.out</lineannotation>
+&prompt.user; <userinput>cc -o foobar foobar.c</userinput> <lineannotation>executable is foobar</lineannotation>
</screen>
</informalexample>
</listitem>
@@ -608,7 +600,7 @@
compiler to add it.</para>
<para>The rule is that if the library is called
- <filename>lib<replaceable>something</replaceable>.a</filename>,
+ <filename>libsomething.a</filename>,
you give <command>cc</command> the argument
<option>-l<replaceable>something</replaceable></option>.
For example, the math library is
@@ -1004,7 +996,7 @@ free(foo);
<para>to find out the process ID of your program, and
do</para>
- <screen>&prompt.user; <userinput>kill -ABRT <replaceable>pid</replaceable></userinput>
+ <screen>&prompt.user; <userinput>kill -ABRT pid</userinput>
</screen>
<para>where
@@ -1032,7 +1024,7 @@ free(foo);
</sect2>
</sect1>
- <sect1 id="tools-make">
+ <sect1 xml:id="tools-make">
<title>Make</title>
<sect2>
@@ -1155,22 +1147,22 @@ install:
<para>We can tell make which target we want to make by
typing:</para>
- <screen>&prompt.user; <userinput>make <replaceable>target</replaceable></userinput></screen>
+ <screen>&prompt.user; <userinput>make target</userinput></screen>
<para><command>make</command> will then only look at that target
and ignore any others. For example, if we type
<userinput>make foo</userinput> with the makefile above, make
- will ignore the <maketarget>install</maketarget> target.</para>
+ will ignore the <buildtarget>install</buildtarget> target.</para>
<para>If we just type <userinput>make</userinput> on its own,
make will always look at the first target and then stop
without looking at any others. So if we typed
<userinput>make</userinput> here, it will just go to the
- <maketarget>foo</maketarget> target, re-compile
+ <buildtarget>foo</buildtarget> target, re-compile
<filename>foo</filename> if necessary, and then stop without
- going on to the <maketarget>install</maketarget> target.</para>
+ going on to the <buildtarget>install</buildtarget> target.</para>
- <para>Notice that the <maketarget>install</maketarget> target does not
+ <para>Notice that the <buildtarget>install</buildtarget> target does not
actually depend on anything! This means that the command on
the following line is always executed when we try to make that
target by typing <userinput>make install</userinput>. In this
@@ -1374,7 +1366,7 @@ DISTFILES= scheme-microcode+dist-7.3-freebsd.tgz
</sect2>
</sect1>
- <sect1 id="debugging">
+ <sect1 xml:id="debugging">
<title>Debugging</title>
<sect2>
@@ -1384,12 +1376,12 @@ DISTFILES= scheme-microcode+dist-7.3-freebsd.tgz
<command>gdb</command> (<application>GNU
debugger</application>). You start it up by typing</para>
- <screen>&prompt.user; <userinput>gdb <replaceable>progname</replaceable></userinput></screen>
+ <screen>&prompt.user; <userinput>gdb progname</userinput></screen>
<para>although many people prefer to run it inside
<application>Emacs</application>. You can do this by:</para>
- <screen><userinput>M-x gdb RET <replaceable>progname</replaceable> RET</userinput></screen>
+ <screen><userinput>M-x gdb RET progname RET</userinput></screen>
<para>Using a debugger allows you to run the program under more
controlled circumstances. Typically, you can step through the
@@ -1407,7 +1399,7 @@ DISTFILES= scheme-microcode+dist-7.3-freebsd.tgz
<para>Finally, if you find its text-based command-prompt style
off-putting, there is a graphical front-end for it
- (<filename role="package">devel/xxgdb</filename>) in the Ports
+ (<package>devel/xxgdb</package>) in the Ports
Collection.</para>
<para>This section is intended to be an introduction to using
@@ -1491,15 +1483,15 @@ GDB is free software and you are welcome to distribute copies of it
There is absolutely no warranty for GDB; type "show warranty" for details.
GDB 4.13 (i386-unknown-freebsd), Copyright 1994 Free Software Foundation, Inc.
(gdb) <userinput>break main</userinput> <lineannotation>Skip the set-up code</lineannotation>
-Breakpoint 1 at 0x160f: file temp.c, line 9. <lineannotation><command>gdb</command> puts breakpoint at <function>main()</function></lineannotation>
-(gdb) <userinput>run</userinput> <lineannotation>Run as far as <function>main()</function></lineannotation>
+Breakpoint 1 at 0x160f: file temp.c, line 9. <lineannotation>gdb puts breakpoint at main()</lineannotation>
+(gdb) <userinput>run</userinput> <lineannotation>Run as far as main()</lineannotation>
Starting program: /home/james/tmp/temp <lineannotation>Program starts running</lineannotation>
-Breakpoint 1, main () at temp.c:9 <lineannotation><command>gdb</command> stops at <function>main()</function></lineannotation>
+Breakpoint 1, main () at temp.c:9 <lineannotation>gdb stops at main()</lineannotation>
(gdb) <userinput>n</userinput> <lineannotation>Go to next line</lineannotation>
This is my program <lineannotation>Program prints out</lineannotation>
-(gdb) <userinput>s</userinput> <lineannotation>step into <function>bazz()</function></lineannotation>
-bazz (anint=4231) at temp.c:17 <lineannotation><command>gdb</command> displays stack frame</lineannotation>
+(gdb) <userinput>s</userinput> <lineannotation>step into bazz()</lineannotation>
+bazz (anint=4231) at temp.c:17 <lineannotation>gdb displays stack frame</lineannotation>
(gdb)</screen>
<para>Hang on a minute! How did <symbol>anint</symbol> get to be
@@ -1508,9 +1500,9 @@ bazz (anint=4231) at temp.c:17 <lineannotation><command>gdb</command> displays
move up to <function>main()</function> and have a look.</para>
<screen>(gdb) <userinput>up</userinput> <lineannotation>Move up call stack</lineannotation>
-#1 0x1625 in main () at temp.c:11 <lineannotation><command>gdb</command> displays stack frame</lineannotation>
-(gdb) <userinput>p i</userinput> <lineannotation>Show us the value of <symbol>i</symbol></lineannotation>
-$1 = 4231 <lineannotation><command>gdb</command> displays <literal>4231</literal></lineannotation></screen>
+#1 0x1625 in main () at temp.c:11 <lineannotation>gdb displays stack frame</lineannotation>
+(gdb) <userinput>p i</userinput> <lineannotation>Show us the value of i</lineannotation>
+$1 = 4231 <lineannotation>gdb displays 4231</lineannotation></screen>
<para>Oh dear! Looking at the code, we forgot to initialize
<symbol>i</symbol>. We meant to put</para>
@@ -1551,7 +1543,7 @@ main() {
listings of core files and sweat over machine code manuals,
but now life is a bit easier. Incidentally, under FreeBSD and
other 4.4BSD systems, a core file is called
- <filename><replaceable>progname</replaceable>.core</filename> instead of just
+ <filename>progname.core</filename> instead of just
<filename>core</filename>, to make it clearer which program a
core file belongs to.</para>
@@ -1559,7 +1551,7 @@ main() {
the usual way. Instead of typing <command>break</command> or
<command>run</command>, type</para>
- <screen>(gdb) <userinput>core <replaceable>progname</replaceable>.core</userinput></screen>
+ <screen>(gdb) <userinput>core progname.core</userinput></screen>
<para>If you are not in the same directory as the core file,
you will have to do <userinput>dir
@@ -1617,7 +1609,7 @@ Cannot access memory at address 0x7020796d.
use <command>ps</command> to find the process ID for the
child, and do</para>
- <screen>(gdb) <userinput>attach <replaceable>pid</replaceable></userinput></screen>
+ <screen>(gdb) <userinput>attach pid</userinput></screen>
<para>in <command>gdb</command>, and then debug as usual.</para>
@@ -1645,7 +1637,7 @@ else if (pid == 0) { /* child */
</sect2>
</sect1>
- <sect1 id="emacs">
+ <sect1 xml:id="emacs">
<title>Using Emacs as a Development Environment</title>
<sect2>
@@ -1708,7 +1700,7 @@ else if (pid == 0) { /* child */
<para>And doubtless many more that have been overlooked.</para>
<para>Emacs can be installed on &os; using
- the <filename role="package">editors/emacs</filename>
+ the <package>editors/emacs</package>
port.</para>
<para>Once it is installed, start it up and do <userinput>C-h
@@ -1791,9 +1783,8 @@ else if (pid == 0) { /* child */
although it is considerably smaller (and thus easier to
master).</para>
- <para>The best way to learn Emacs Lisp is to download the <ulink
- url="ftp://ftp.gnu.org/old-gnu/emacs/elisp-manual-19-2.4.tar.gz">Emacs
- Tutorial</ulink></para>
+ <para>The best way to learn Emacs Lisp is to download the <link xlink:href="ftp://ftp.gnu.org/old-gnu/emacs/elisp-manual-19-2.4.tar.gz">Emacs
+ Tutorial</link></para>
<para>However, there is no need to actually know any Lisp to get
started with configuring Emacs, as I have included a sample
@@ -1860,7 +1851,7 @@ else if (pid == 0) { /* child */
if you are doing something outside Emacs and you want to
edit a file, you can just type in</para>
- <screen>&prompt.user; <userinput>emacsclient <replaceable>filename</replaceable></userinput>
+ <screen>&prompt.user; <userinput>emacsclient filename</userinput>
</screen>
<para>and then you can edit the file in your
@@ -2239,7 +2230,7 @@ else if (pid == 0) { /* child */
</sect2>
</sect1>
- <sect1 id="tools-reading">
+ <sect1 xml:id="tools-reading">
<title>Further Reading</title>
<para>For information about setting up a development environment
diff --git a/en_US.ISO8859-1/books/developers-handbook/x86/chapter.xml b/en_US.ISO8859-1/books/developers-handbook/x86/chapter.xml
index 5f682a8a16..e72bb99840 100644
--- a/en_US.ISO8859-1/books/developers-handbook/x86/chapter.xml
+++ b/en_US.ISO8859-1/books/developers-handbook/x86/chapter.xml
@@ -18,8 +18,7 @@
$FreeBSD$
-->
-
-<chapter id="x86">
+<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:id="x86">
<title>x86 Assembly Language Programming</title>
<para>
@@ -29,7 +28,7 @@ This chapter was written by &a.stanislav.email;.
-<sect1 id="x86-intro">
+<sect1 xml:id="x86-intro">
<title>Synopsis</title>
<para>
@@ -64,11 +63,11 @@ how you can use assembly language writing
This chapter does not explain the basics of assembly language.
There are enough resources about that (for a complete
online course in assembly language, see Randall Hyde's
-<ulink url="http://webster.cs.ucr.edu/">Art
-of Assembly Language</ulink>; or if you prefer
+<link xlink:href="http://webster.cs.ucr.edu/">Art
+of Assembly Language</link>; or if you prefer
a printed book, take a look at Jeff Duntemann's
-<ulink url="http://www.int80h.org/cgi-bin/isbn?isbn=0471375233">Assembly
-Language Step-by-Step</ulink>). However,
+<link xlink:href="http://www.int80h.org/cgi-bin/isbn?isbn=0471375233">Assembly
+Language Step-by-Step</link>). However,
once the chapter is finished, any assembly language programmer
will be able to write programs for FreeBSD
quickly and efficiently.
@@ -80,10 +79,10 @@ Copyright &copy; 2000-2001 G. Adam Stanislav. All rights reserved.
</sect1>
-<sect1 id="x86-the-tools">
+<sect1 xml:id="x86-the-tools">
<title>The Tools</title>
-<sect2 id="x86-the-assembler">
+<sect2 xml:id="x86-the-assembler">
<title>The Assembler</title>
<para>
@@ -116,7 +115,7 @@ quite frankly, that is what I am used to.
</sect2>
-<sect2 id="x86-the-linker">
+<sect2 xml:id="x86-the-linker">
<title>The Linker</title>
<para>
@@ -134,10 +133,10 @@ code assembled with either assembler.
</sect2>
</sect1>
-<sect1 id="x86-system-calls">
+<sect1 xml:id="x86-system-calls">
<title>System Calls</title>
-<sect2 id="x86-default-calling-convention">
+<sect2 xml:id="x86-default-calling-convention">
<title>Default Calling Convention</title>
<para>
@@ -208,7 +207,7 @@ the kernel function, in this case <function role="syscall">open</function>.
</para>
</sect2>
-<sect2 id="x86-alternate-calling-convention">
+<sect2 xml:id="x86-alternate-calling-convention">
<title>Alternate Calling Convention</title>
<para>
FreeBSD is an extremely flexible system. It offers other ways of
@@ -250,11 +249,11 @@ the system know about it. After your program is assembled and
linked, you need to brand the executable:
</para>
-<screen>&prompt.user; <userinput>brandelf -t Linux <replaceable>filename</replaceable></userinput></screen>
+<screen>&prompt.user; <userinput>brandelf -t Linux filename</userinput></screen>
</sect2>
-<sect2 id="x86-use-geneva">
+<sect2 xml:id="x86-use-geneva">
<title>Which Convention Should You Use?</title>
<para>
@@ -274,7 +273,7 @@ how you can accomplish that after I have explained the basics.
</sect2>
-<sect2 id="x86-call-numbers">
+<sect2 xml:id="x86-call-numbers">
<title>Call Numbers</title>
<para>
@@ -283,7 +282,7 @@ place its number in <varname role="register">EAX</varname>. Of course, you need
to know what the number is.
</para>
-<sect3 id="x86-the-syscalls-file">
+<sect3 xml:id="x86-the-syscalls-file">
<title>The <filename>syscalls</filename> File</title>
<para>
@@ -351,7 +350,7 @@ the <varname>path</varname> is stored.
</sect1>
-<sect1 id="x86-return-values">
+<sect1 xml:id="x86-return-values">
<title>Return Values</title>
<para>
@@ -367,7 +366,7 @@ occurs: A file does not exist, system resources are exhausted,
we passed an invalid parameter, etc.
</para>
-<sect2 id="x86-man-pages">
+<sect2 xml:id="x86-man-pages">
<title>Man Pages</title>
<para>
@@ -405,7 +404,7 @@ information.
</sect2>
-<sect2 id="x86-where-return-values">
+<sect2 xml:id="x86-where-return-values">
<title>Where Are the Return Values?</title>
<para>
@@ -437,7 +436,7 @@ interfaces with the kernel.
</tip>
</sect2>
-<sect2 id="x86-where-errno">
+<sect2 xml:id="x86-where-errno">
<title>Where Is <varname>errno</varname>?</title>
<para>
@@ -460,7 +459,7 @@ value. One register can contain either.
</sect2>
-<sect2 id="x86-how-to-know-error">
+<sect2 xml:id="x86-how-to-know-error">
<title>Determining an Error Occurred</title>
<para>
@@ -480,7 +479,7 @@ is negative, i.e., <varname>-errno</varname>.
</sect1>
-<sect1 id="x86-portable-code">
+<sect1 xml:id="x86-portable-code">
<title>Creating Portable Code</title>
<para>
@@ -504,7 +503,7 @@ programmer's perspective): The calling convention, the
function numbers, and the way of returning values.
</para>
-<sect2 id="x86-deal-with-function-numbers"><title>Dealing with Function Numbers</title>
+<sect2 xml:id="x86-deal-with-function-numbers"><title>Dealing with Function Numbers</title>
<para>
In many cases the function numbers are the same. However,
@@ -522,7 +521,7 @@ architecture:
%endif
</programlisting>
</sect2>
-<sect2 id="x86-deal-with-geneva"><title>Dealing with Conventions</title>
+<sect2 xml:id="x86-deal-with-geneva"><title>Dealing with Conventions</title>
<para>
Both, the calling convention, and the return value (the
<varname>errno</varname> problem) can be resolved with macros:
@@ -579,7 +578,7 @@ kernel:
</sect2>
-<sect2 id="x86-deal-with-other-portability"><title>Dealing with Other Portability Issues</title>
+<sect2 xml:id="x86-deal-with-other-portability"><title>Dealing with Other Portability Issues</title>
<para>
The above solutions can handle most cases of writing code
@@ -597,7 +596,7 @@ a few such conditional sections in your code.
</sect2>
-<sect2 id="x86-portable-library"><title>Using a Library</title>
+<sect2 xml:id="x86-portable-library"><title>Using a Library</title>
<para>
You can avoid portability issues in your main code altogether
@@ -676,7 +675,7 @@ main program.
</sect2>
-<sect2 id="x86-portable-include">
+<sect2 xml:id="x86-portable-include">
<title>Using an Include File</title>
<para>
@@ -784,7 +783,7 @@ discuss more syscalls.
</sect1>
-<sect1 id="x86-first-program">
+<sect1 xml:id="x86-first-program">
<title>Our First Program</title>
<para>
@@ -856,7 +855,7 @@ is for the system to figure out.
</para>
</note>
-<sect2 id="x86-assemble-1"><title>Assembling the Code</title>
+<sect2 xml:id="x86-assemble-1"><title>Assembling the Code</title>
<para>
Type the code (except the line numbers) in an editor, and save
@@ -864,14 +863,14 @@ it in a file named <filename>hello.asm</filename>. You need
<application>nasm</application> to assemble it.
</para>
-<sect3 id="x86-get-nasm"><title>Installing <application>nasm</application></title>
+<sect3 xml:id="x86-get-nasm"><title>Installing <application>nasm</application></title>
<para>
If you do not have <application>nasm</application>, type:
</para>
<screen>&prompt.user; <userinput>su</userinput>
-Password:<userinput><replaceable>your root password</replaceable></userinput>
+Password:<userinput>your root password</userinput>
&prompt.root; <userinput>cd /usr/ports/devel/nasm</userinput>
&prompt.root; <userinput>make install</userinput>
&prompt.root; <userinput>exit</userinput>
@@ -893,8 +892,8 @@ compile it, and install it on your system.
<para>
If your system is not FreeBSD, you need to get
<application>nasm</application> from its
-<ulink url="https://sourceforge.net/projects/nasm">home
-page</ulink>. You can still use it to assemble FreeBSD code.
+<link xlink:href="https://sourceforge.net/projects/nasm">home
+page</link>. You can still use it to assemble FreeBSD code.
</para>
</note>
@@ -914,7 +913,7 @@ Hello, World!
</sect1>
-<sect1 id="x86-unix-filters">
+<sect1 xml:id="x86-unix-filters">
<title>Writing &unix; Filters</title>
<para>
@@ -1151,7 +1150,7 @@ to read it, another time to write the output).
</sect1>
-<sect1 id="x86-buffered-io">
+<sect1 xml:id="x86-buffered-io">
<title>Buffered Input and Output</title>
<para>
@@ -1361,9 +1360,9 @@ _start:
.put:
call putchar
-> cmp al, 0Ah
-> jne .loop
-> call write
+&gt; cmp al, 0Ah
+&gt; jne .loop
+&gt; call write
jmp short .loop
align 4
@@ -1444,7 +1443,7 @@ fix&mdash;it later, when I talk about the
side of buffering</link>.</para>
</note>
-<sect2 id="x86-ungetc">
+<sect2 xml:id="x86-ungetc">
<title>How to Unread a Character</title>
<warning><para>
@@ -1605,7 +1604,7 @@ the buffer or within the "spare").
</sect1>
-<sect1 id="x86-command-line"><title>Command Line Arguments</title>
+<sect1 xml:id="x86-command-line"><title>Command Line Arguments</title>
<para>
Our <application>hex</application> program will be more useful if it can
@@ -1938,7 +1937,7 @@ You already know everything you need to know to implement them.
</sect1>
-<sect1 id="x86-environment">
+<sect1 xml:id="x86-environment">
<title>&unix; Environment</title>
<para>
@@ -1948,7 +1947,7 @@ by you, yet others by the <application>shell</application>, or any program
that loads another program.
</para>
-<sect2 id="x86-find-environment">
+<sect2 xml:id="x86-find-environment">
<title>How to Find Environment Variables</title>
<para>
@@ -1977,7 +1976,7 @@ may be missing. We need to account for that possibility.
</sect2>
-<sect2 id="x86-webvar">
+<sect2 xml:id="x86-webvar">
<title>webvars</title>
<para>
@@ -1987,13 +1986,13 @@ I thought it would be more interesting to write a simple
assembly language CGI utility.
</para>
-<sect3 id="x86-cgi">
+<sect3 xml:id="x86-cgi">
<title>CGI: A Quick Overview</title>
<para>
I have a
-<ulink url="http://www.whizkidtech.redprince.net/cgi-bin/tutorial">detailed
-<acronym>CGI</acronym> tutorial</ulink> on my web site,
+<link xlink:href="http://www.whizkidtech.redprince.net/cgi-bin/tutorial">detailed
+<acronym>CGI</acronym> tutorial</link> on my web site,
but here is a very quick overview of <acronym>CGI</acronym>:
</para>
@@ -2039,7 +2038,7 @@ quite a useful diagnostic tool.
</sect3>
-<sect3 id="x86-webvars-the-code">
+<sect3 xml:id="x86-webvars-the-code">
<title>The Code</title>
<para>
@@ -2262,10 +2261,10 @@ or perhaps rename it with a <filename>.cgi</filename> extension.
<para>
Then you need to use your browser to view its output.
To see its output on my web server, please go to
-<ulink url="http://www.int80h.org/webvars/"><filename>http://www.int80h.org/webvars/</filename></ulink>.
+<link xlink:href="http://www.int80h.org/webvars/"><filename>http://www.int80h.org/webvars/</filename></link>.
If curious about the additional environment variables
present in a password protected web directory, go to
-<ulink url="http://www.int80h.org/private/"><filename>http://www.int80h.org/private/</filename></ulink>,
+<link xlink:href="http://www.int80h.org/private/"><filename>http://www.int80h.org/private/</filename></link>,
using the name <userinput>asm</userinput> and password
<userinput>programmer</userinput>.
</para>
@@ -2276,7 +2275,7 @@ using the name <userinput>asm</userinput> and password
</sect1>
-<sect1 id="x86-files">
+<sect1 xml:id="x86-files">
<title>Working with Files</title>
<para>
@@ -2296,7 +2295,7 @@ supposed to do.
<para>
One of the first programs I wrote for &unix; was
-<ulink url="ftp://ftp.int80h.org/unix/tuc/"><application>tuc</application></ulink>,
+<link xlink:href="ftp://ftp.int80h.org/unix/tuc/"><application>tuc</application></link>,
a text-to-&unix; file converter. It converts a text
file from other operating systems to a &unix; text file.
In other words, it changes from different kind of line endings
@@ -2314,15 +2313,15 @@ to send the output to a different file. Most of the time,
I end up using it like this:
</para>
-<screen>&prompt.user; <userinput>tuc <replaceable>myfile tempfile</replaceable></userinput>
-&prompt.user; <userinput>mv <replaceable>tempfile myfile</replaceable></userinput></screen>
+<screen>&prompt.user; <userinput>tuc myfile tempfile</userinput>
+&prompt.user; <userinput>mv tempfile myfile</userinput></screen>
<para>
It would be nice to have a <application>ftuc</application>,
i.e., <emphasis>fast tuc</emphasis>, and use it like this:
</para>
-<screen>&prompt.user; <userinput>ftuc <replaceable>myfile</replaceable></userinput></screen>
+<screen>&prompt.user; <userinput>ftuc myfile</userinput></screen>
<para>
In this chapter, then, we will write
@@ -2389,7 +2388,7 @@ combination of the above (e.g., carriage return followed
by several line feeds).
</para>
-<sect2 id="x86-finite-state-machine">
+<sect2 xml:id="x86-finite-state-machine">
<title>Finite State Machine</title>
<para>
@@ -2545,7 +2544,7 @@ and leave the state unchanged.
</listitem>
</itemizedlist>
-<sect3 id="x86-final-state">
+<sect3 xml:id="x86-final-state">
<title>The Final State</title>
<para>
@@ -2576,7 +2575,7 @@ an assembly language program.
</sect3>
-<sect3 id="x86-tuc-counter">
+<sect3 xml:id="x86-tuc-counter">
<title>The Output Counter</title>
<para>
@@ -2592,7 +2591,7 @@ to set the file to.
</sect2>
-<sect2 id="x86-software-fsm">
+<sect2 xml:id="x86-software-fsm">
<title>Implementing FSM in Software</title>
<para>
@@ -2657,7 +2656,7 @@ microprocessors do, either way may be equally fast.
</sect2>
-<sect2 id="memory-mapped-files">
+<sect2 xml:id="memory-mapped-files">
<title>Memory Mapped Files</title>
<para>
@@ -2739,14 +2738,14 @@ we unmap it with the <function role="syscall">munmap</function> syscall:
<para>
For an in-depth treatment of <function role="syscall">mmap</function>, see
W. Richard Stevens'
-<ulink url="http://www.int80h.org/cgi-bin/isbn?isbn=0130810819">Unix
-Network Programming, Volume 2, Chapter 12</ulink>.
+<link xlink:href="http://www.int80h.org/cgi-bin/isbn?isbn=0130810819">Unix
+Network Programming, Volume 2, Chapter 12</link>.
</para>
</tip>
</sect2>
-<sect2 id="x86-file-size">
+<sect2 xml:id="x86-file-size">
<title>Determining File Size</title>
<para>
@@ -2775,14 +2774,14 @@ of <function role="syscall">fstat</function>, a traditional one
<para>
This is a very straightforward call: We pass to it the address
-of a <structname>stat</structname> structure and the descriptor
+of a <varname remap="structname">stat</varname> structure and the descriptor
of an open file. It will fill out the contents of the
-<structname>stat</structname> structure.
+<varname remap="structname">stat</varname> structure.
</para>
<para>
I do, however, have to say that I tried to declare the
-<structname>stat</structname> structure in the
+<varname remap="structname">stat</varname> structure in the
<varname>.bss</varname> section, and
<function role="syscall">fstat</function> did not like it: It set the carry
flag indicating an error. After I changed the code to allocate
@@ -2791,7 +2790,7 @@ the structure on the stack, everything was working fine.
</sect2>
-<sect2 id="x86-ftruncate">
+<sect2 xml:id="x86-ftruncate">
<title>Changing the File Size</title>
<para>
@@ -2826,7 +2825,7 @@ Please note that this one contains a <varname>int pad</varname> again.
</sect2>
-<sect2 id="x86-ftuc">
+<sect2 xml:id="x86-ftuc">
<title>ftuc</title>
<para>
@@ -3166,7 +3165,7 @@ its contents.
</sect1>
-<sect1 id="x86-one-pointed-mind">
+<sect1 xml:id="x86-one-pointed-mind">
<title>One-Pointed Mind</title>
<para>
@@ -3197,7 +3196,7 @@ write your own programs for that part of the problem
that you do not have an existing solution for.
</para>
-<sect2 id="x86-csv"><title>CSV</title>
+<sect2 xml:id="x86-csv"><title>CSV</title>
<para>
I will illustrate this principle with a specific real-life
@@ -3344,7 +3343,7 @@ specified.
To get the 11th field of each record, I can now do:
</para>
-<screen>&prompt.user; <userinput>csv '-t;' <replaceable>data.csv</replaceable> | awk '-F;' '{print $11}'</userinput></screen>
+<screen>&prompt.user; <userinput>csv '-t;' data.csv | awk '-F;' '{print $11}'</userinput></screen>
<para>
The code stores the options (except for the file descriptors)
@@ -3656,7 +3655,7 @@ keyboard, processes it, and sees its input buffer is empty. It
flushes its output and reads the next line.
</para>
-<sect3 id="x86-buffered-dark-side">
+<sect3 xml:id="x86-buffered-dark-side">
<title>The Dark Side of Buffering</title>
<para>
This change prevents a mysterious lockup
@@ -3794,7 +3793,7 @@ its output buffer <emphasis>before</emphasis> asking the
</sect1>
-<sect1 id="x86-fpu">
+<sect1 xml:id="x86-fpu">
<title>Using the <acronym>FPU</acronym></title>
<para>
Strangely enough, most of assembly language literature does not
@@ -3808,7 +3807,7 @@ Yet, never does assembly language shine more than when
we create highly optimized <acronym>FPU</acronym>
code by doing things that can be done <emphasis>only</emphasis> in assembly language.</para>
-<sect2 id="x86-fpu-organization"><title>Organization of the <acronym>FPU</acronym></title>
+<sect2 xml:id="x86-fpu-organization"><title>Organization of the <acronym>FPU</acronym></title>
<para>
The <acronym>FPU</acronym> consists of 8 80&ndash;bit floating&ndash;point registers.
These are organized in a stack fashion&mdash;you can
@@ -3910,7 +3909,7 @@ and the <acronym>TOS</acronym> is always
<varname role="register">st0</varname>, never just <function role="opcode">st</function>.
</para>
-<sect3 id="x86-fpu-packed-decimal">
+<sect3 xml:id="x86-fpu-packed-decimal">
<title>The Packed Decimal Format</title>
<para>
The <emphasis>packed decimal</emphasis> format
@@ -3977,8 +3976,8 @@ in desperation!
<note>
<para>
The book to read&mdash;if you can find it&mdash;is Richard Startz'
-<ulink url="http://www.int80h.org/cgi-bin/isbn?isbn=013246604X">8087/80287/80387
-for the IBM PC &amp; Compatibles</ulink>.
+<link xlink:href="http://www.int80h.org/cgi-bin/isbn?isbn=013246604X">8087/80287/80387
+for the IBM PC &amp; Compatibles</link>.
Though it does seem to take the fact about the
little&ndash;endian storage of the <emphasis>packed
decimal</emphasis> for granted. I kid you not about the
@@ -3993,7 +3992,7 @@ little&ndash;endian order even for this type of data.
</sect2>
-<sect2 id="x86-pinhole-photography">
+<sect2 xml:id="x86-pinhole-photography">
<title>Excursion to Pinhole Photography</title>
<para>
To write meaningful software, we must not only
@@ -4008,7 +4007,7 @@ so, we need some background in <emphasis>pinhole
photography</emphasis> before we can continue.
</para>
-<sect3 id="x86-camera">
+<sect3 xml:id="x86-camera">
<title>The Camera</title>
<para>
The easiest way to describe any camera ever built
@@ -4040,7 +4039,7 @@ a lens assembly, often called the <emphasis>objective</emphasis>.
</sect3>
-<sect3 id="x86-the-pinhole">
+<sect3 xml:id="x86-the-pinhole">
<title>The Pinhole</title>
<para>
But, strictly speaking, the lens is not necessary:
@@ -4059,7 +4058,7 @@ sharpness.</para>
</sect3>
-<sect3 id="x86-focal-length">
+<sect3 xml:id="x86-focal-length">
<title>Focal Length</title>
<para>
This ideal pinhole diameter is a function
@@ -4089,7 +4088,7 @@ experimentation.
</sect3>
-<sect3 id="x86-f-number">
+<sect3 xml:id="x86-f-number">
<title>The F&ndash;Number</title>
<para>
The f&ndash;number is a very useful measure of
@@ -4136,7 +4135,7 @@ at f&ndash;number <varname>B</varname> is:</para>
</programlisting>
</sect3>
-<sect3 id="x86-normalized-f-number">
+<sect3 xml:id="x86-normalized-f-number">
<title>Normalized F&ndash;Number</title>
<para>
While many modern cameras can change the diameter
@@ -4170,7 +4169,7 @@ be rounded somewhat.
</sect3>
-<sect3 id="x86-f-stop">
+<sect3 xml:id="x86-f-stop">
<title>The F&ndash;Stop</title>
<para>
A typical camera is designed in such a way that setting
@@ -4193,14 +4192,14 @@ quadruple the required exposure. Moving the dial by
</sect2>
-<sect2 id="x86-pinhole-software">
+<sect2 xml:id="x86-pinhole-software">
<title>Designing the Pinhole Software</title>
<para>
We are now ready to decide what exactly we want our
pinhole software to do.
</para>
-<sect3 id="xpinhole-processing-input">
+<sect3 xml:id="xpinhole-processing-input">
<title>Processing Program Input</title>
<para>
Since its main purpose is to help us design a working
@@ -4326,7 +4325,7 @@ of course.
</sect3>
-<sect3 id="x86-pinhole-options">
+<sect3 xml:id="x86-pinhole-options">
<title>Offering Options</title>
<para>
The most important thing we need to know when building
@@ -4501,7 +4500,7 @@ and <parameter>-c</parameter> as identical to <parameter>-p037</parameter>.
</sect3>
-<sect3 id="x86-pinhole-output">
+<sect3 xml:id="x86-pinhole-output">
<title>The Output</title>
<para>
We need to decide what we want our software to
@@ -5083,7 +5082,7 @@ anyway.</para>
</sect2>
-<sect2 id="x86-fpu-optimizations">
+<sect2 xml:id="x86-fpu-optimizations">
<title>FPU Optimizations</title>
<para>
In assembly language we can optimize the <acronym>FPU</acronym>
@@ -5249,7 +5248,7 @@ available about &postscript; than about the
</sect2>
-<sect2 id="x86-pinhole-the-code">
+<sect2 xml:id="x86-pinhole-the-code">
<title><application>pinhole</application>&mdash;The Code</title>
<programlisting>
;;;;;;; pinhole.asm ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
@@ -6110,7 +6109,7 @@ tiny detail, the code almost writes itself.
</sect2>
-<sect2 id="x86-pinhole-using">
+<sect2 xml:id="x86-pinhole-using">
<title>Using <application>pinhole</application></title>
<para>
Because we have decided to make the program
@@ -6168,7 +6167,7 @@ one half of a millimeter.
</sect2>
-<sect2 id="x86-pinhole-scripting">
+<sect2 xml:id="x86-pinhole-scripting">
<title>Scripting</title>
<para>
Because we have chosen the <constant>#</constant>
@@ -6306,7 +6305,7 @@ focal length in millimeters,pinhole diameter in microns,F-number,normalized F-nu
</sect1>
-<sect1 id="x86-caveats">
+<sect1 xml:id="x86-caveats">
<title>Caveats</title>
<para>
@@ -6335,7 +6334,7 @@ That is generally a <emphasis>very bad idea</emphasis>
in &unix; environment! Let me explain why.
</para>
-<sect2 id="x86-protected">
+<sect2 xml:id="x86-protected">
<title>&unix; Is Protected</title>
<para>
@@ -6350,7 +6349,7 @@ become a dinosaur overnight.
</sect2>
-<sect2 id="x86-abstraction">
+<sect2 xml:id="x86-abstraction">
<title>&unix; Is an Abstraction</title>
<para>
@@ -6451,7 +6450,7 @@ them and why.
</sect1>
-<sect1 id="x86-acknowledgements">
+<sect1 xml:id="x86-acknowledgements">
<title>Acknowledgements</title>
<para>
@@ -6465,8 +6464,8 @@ system programming in general and FreeBSD in particular.
<para>
Thomas M. Sommers opened the door for me. His
-<ulink url="http://www.codebreakers-journal.com/content/view/262/27/">How
-do I write "Hello, world" in FreeBSD assembler?</ulink>
+<link xlink:href="http://www.codebreakers-journal.com/content/view/262/27/">How
+do I write "Hello, world" in FreeBSD assembler?</link>
web page was my first encounter with an example of
assembly language programming under FreeBSD.
</para>
diff --git a/en_US.ISO8859-1/books/faq/book.xml b/en_US.ISO8859-1/books/faq/book.xml
index 886c6b2f43..49a32f3954 100644
--- a/en_US.ISO8859-1/books/faq/book.xml
+++ b/en_US.ISO8859-1/books/faq/book.xml
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE book PUBLIC "-//FreeBSD//DTD DocBook XML V4.5-Based Extension//EN"
- "../../../share/xml/freebsd45.dtd" [
+<!DOCTYPE book PUBLIC "-//FreeBSD//DTD DocBook XML V5.0-Based Extension//EN"
+ "../../../share/xml/freebsd50.dtd" [
<!ENTITY bibliography SYSTEM "../../../share/xml/bibliography.xml">
<!ENTITY rel.numbranch "3"> <!-- number of branches that follow in this list -->
<!ENTITY rel.head "<emphasis xmlns='http://docbook.org/ns/docbook'>10-CURRENT</emphasis>">
@@ -18,13 +18,12 @@
<!ENTITY rel2.relengdate "August 2009">
<!ENTITY rel2.packages "packages-8-stable">
]>
-
-<book lang='en'>
- <bookinfo>
- <title>Frequently Asked Questions for &os;
+<book xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:lang="en">
+ <info><title>Frequently Asked Questions for &os;
&rel2.relx;, and &rel.relx;</title>
+
- <corpauthor>The &os; Documentation Project</corpauthor>
+ <author><orgname>The &os; Documentation Project</orgname></author>
<copyright>
<year>1995</year>
@@ -51,7 +50,7 @@
&legalnotice;
- <legalnotice id="trademarks" role="trademarks">
+ <legalnotice xml:id="trademarks" role="trademarks">
&tm-attrib.freebsd;
&tm-attrib.adobe;
&tm-attrib.ibm;
@@ -76,30 +75,26 @@
&a.doc;.</para>
<para>The latest version of
- this document is always available from the <ulink
- url="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/faq/index.html">&os; website</ulink>.
- It may also be downloaded as one large <ulink
- url="book.html">HTML</ulink> file with HTTP or as a variety
- of other formats from the <ulink
- url="ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/">&os; FTP
- server</ulink>.</para>
+ this document is always available from the <link xlink:href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/faq/index.html">&os; website</link>.
+ It may also be downloaded as one large <link xlink:href="book.html">HTML</link> file with HTTP or as a variety
+ of other formats from the <link xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/">&os; FTP
+ server</link>.</para>
</abstract>
- </bookinfo>
+ </info>
- <chapter id="introduction">
+ <chapter xml:id="introduction">
<title>Introduction</title>
<qandaset>
<qandaentry>
- <question id="what-is-FreeBSD">
+ <question xml:id="what-is-FreeBSD">
<para>What is &os;?</para>
</question>
<answer>
<para>&os; is a modern operating system for desktops,
laptops, servers, and embedded systems with
- support for a large number of <ulink
- url="http://www.FreeBSD.org/platforms/">platforms</ulink>.</para>
+ support for a large number of <link xlink:href="http://www.FreeBSD.org/platforms/">platforms</link>.</para>
<para>It is based on U.C.
Berkeley's <quote>4.4BSD-Lite</quote> release, with some
@@ -115,13 +110,12 @@
recreation.</para>
<para>For more detailed information on &os;, please see the
- <ulink
- url="&url.books.handbook;/index.html">&os; Handbook</ulink>.</para>
+ <link xlink:href="&url.books.handbook;/index.html">&os; Handbook</link>.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="FreeBSD-goals">
+ <question xml:id="FreeBSD-goals">
<para>What is the goal of the &os; Project?</para>
</question>
@@ -135,15 +129,14 @@
</qandaentry>
<qandaentry>
- <question id="bsd-license-restrictions">
+ <question xml:id="bsd-license-restrictions">
<para>Does the &os; license have any restrictions?</para>
</question>
<answer>
<para>Yes. Those restrictions do not control how you use the
code, merely how you treat the &os; Project itself. If you
- have serious license concerns, read the actual <ulink
- url="http://www.FreeBSD.org/copyright/freebsd-license.html">license</ulink>.
+ have serious license concerns, read the actual <link xlink:href="http://www.FreeBSD.org/copyright/freebsd-license.html">license</link>.
For the simply curious, the license can be summarized like
this.</para>
@@ -176,23 +169,20 @@
support.</para>
<para>Code in our source tree which falls under the
- <ulink
- url="http://www.FreeBSD.org/copyright/COPYING">GNU General Public License (GPL)</ulink>
- or <ulink
- url="http://www.FreeBSD.org/copyright/COPYING.LIB">GNU Library General Public License (LGPL)</ulink>
+ <link xlink:href="http://www.FreeBSD.org/copyright/COPYING">GNU General Public License (GPL)</link>
+ or <link xlink:href="http://www.FreeBSD.org/copyright/COPYING.LIB">GNU Library General Public License (LGPL)</link>
comes with slightly more strings attached, though at least
on the side of enforced access rather than the usual
opposite. Due to the additional complexities that can
evolve in the commercial use of GPL software, we do,
however, endeavor to replace such software with submissions
- under the more relaxed <ulink
- url="http://www.FreeBSD.org/copyright/freebsd-license.html">&os; license</ulink>
+ under the more relaxed <link xlink:href="http://www.FreeBSD.org/copyright/freebsd-license.html">&os; license</link>
whenever possible.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="replace-current-OS">
+ <question xml:id="replace-current-OS">
<para>Can &os; replace my current operating system?</para>
</question>
@@ -208,8 +198,7 @@
readers, graphics programs, programming environments,
network servers, and just about everything else you might
want. Most of these applications can be managed through the
- <ulink
- url="http://www.FreeBSD.org/ports/">Ports Collection</ulink>.</para>
+ <link xlink:href="http://www.FreeBSD.org/ports/">Ports Collection</link>.</para>
<para>If you need to use an application that is only available
on one operating system, you simply cannot replace that
@@ -226,19 +215,17 @@
environment, you already know most of what you need to. If
your background is in graphic-driven operating systems such
as &windows; and &macos;, you may be interested in using
- <ulink
- url="http://www.pcbsd.org/">PC-BSD</ulink>, a &os; based
+ <link xlink:href="http://www.pcbsd.org/">PC-BSD</link>, a &os; based
distribution, instead. If you have not used &unix; before
expect to invest
additional time learning the &unix; way of doing things.
- This FAQ and the <ulink
- url="&url.books.handbook;/index.html">&os; Handbook</ulink>
+ This FAQ and the <link xlink:href="&url.books.handbook;/index.html">&os; Handbook</link>
are excellent places to start.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="why-called-FreeBSD">
+ <question xml:id="why-called-FreeBSD">
<para>Why is it called &os;?</para>
</question>
@@ -274,7 +261,7 @@
</qandaentry>
<qandaentry>
- <question id="differences-to-other-bsds">
+ <question xml:id="differences-to-other-bsds">
<para>What are the differences between &os; and NetBSD,
OpenBSD, and other open source BSD operating systems?</para>
</question>
@@ -282,8 +269,7 @@
<answer>
<para>James Howard wrote a good explanation of the history and
differences between the various projects,
- called <ulink
- url="http://www.freebsdworld.gr/freebsd/bsd-family-tree.html">The BSD Family Tree</ulink>
+ called <link xlink:href="http://www.freebsdworld.gr/freebsd/bsd-family-tree.html">The BSD Family Tree</link>
which goes a fair way to answering this question.
Some of the information is out of date, but the history
portion in particular remains accurate.</para>
@@ -319,7 +305,7 @@
</qandaentry>
<qandaentry>
- <question id="latest-version">
+ <question xml:id="latest-version">
<para>What is the latest version of &os;?</para>
</question>
@@ -341,12 +327,10 @@
<quote>legacy</quote> branch and most current work will only
become a part of &rel.stable; and &rel2.stable;.--></para>
- <para>Version <ulink
- url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/i386/&rel.current;-RELEASE/">&rel.current;</ulink>
+ <para>Version <link xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/i386/&rel.current;-RELEASE/">&rel.current;</link>
is the latest release from the &rel.stable;
branch; it was released in &rel.current.date;. Version
- <ulink
- url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel2.current;-RELEASE/">&rel2.current;</ulink>
+ <link xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel2.current;-RELEASE/">&rel2.current;</link>
is the latest release from the &rel2.stable;
branch; it was released in &rel2.current.date;.</para>
@@ -360,37 +344,30 @@
volatility (relative to <emphasis>-STABLE</emphasis>, that
is).</para>
- <para>Releases are made <link
- linkend="release-freq">every few months</link>. While
+ <para>Releases are made <link linkend="release-freq">every few months</link>. While
many people stay more up-to-date with the &os; sources (see
- the questions on <link
- linkend="current">&os.current;</link> and <link
- linkend="stable">&os.stable;</link>) than that, doing so
+ the questions on <link linkend="current">&os.current;</link> and <link linkend="stable">&os.stable;</link>) than that, doing so
is more of a commitment, as the sources are a moving
target.</para>
<para>More information on &os; releases can be found on the
- <ulink
- url="http://www.FreeBSD.org/releng/index.html#release-build">Release Engineering page</ulink>
+ <link xlink:href="http://www.FreeBSD.org/releng/index.html#release-build">Release Engineering page</link>
and in &man.release.7;.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="current">
+ <question xml:id="current">
<para>What is <emphasis>&os;-CURRENT</emphasis>?</para>
</question>
<answer>
- <para><ulink
- url="&url.books.handbook;/current-stable.html#current">&os.current;</ulink>
+ <para><link xlink:href="&url.books.handbook;/current-stable.html#current">&os.current;</link>
is the development version of the operating system, which
will in due course become the new &os.stable; branch. As
such, it is really only of interest to developers working on
- the system and die-hard hobbyists. See the <ulink
- url="&url.books.handbook;/current-stable.html#current">relevant section</ulink>
- in the <ulink
- url="&url.books.handbook;/index.html">Handbook</ulink> for
+ the system and die-hard hobbyists. See the <link xlink:href="&url.books.handbook;/current-stable.html#current">relevant section</link>
+ in the <link xlink:href="&url.books.handbook;/index.html">Handbook</link> for
details on running <emphasis>-CURRENT</emphasis>.</para>
<para>If you are not familiar with &os;
@@ -400,8 +377,7 @@
People that use &os.current; are expected to be able to
analyze, debug, and report problems.</para>
- <para>&os; <ulink
- url="&url.base;/snapshots/">snapshot</ulink>
+ <para>&os; <link xlink:href="&url.base;/snapshots/">snapshot</link>
releases are made based on the current state of the
<emphasis>-CURRENT</emphasis> and
<emphasis>-STABLE</emphasis> branches. The goals behind
@@ -442,8 +418,7 @@
to stick to full releases, or use the
<emphasis>-STABLE</emphasis> snapshots.</para>
- <para>Snapshot releases are directly available from <ulink
- url="&url.base;/snapshots/">snapshot</ulink>.</para>
+ <para>Snapshot releases are directly available from <link xlink:href="&url.base;/snapshots/">snapshot</link>.</para>
<para>Official snapshots are generated on a regular
basis for all actively developed branches.</para>
@@ -451,17 +426,15 @@
</qandaentry>
<qandaentry>
- <question id="stable">
+ <question xml:id="stable">
<para>What is the <emphasis>&os;-STABLE</emphasis>
concept?</para>
</question>
<answer>
<para>Back when &os;&nbsp;2.0.5 was released, &os; development
- branched in two. One branch was named <ulink
- url="&url.books.handbook;/current-stable.html#stable">-STABLE</ulink>,
- one <ulink
- url="&url.books.handbook;/current-stable.html#current">-CURRENT</ulink>.
+ branched in two. One branch was named <link xlink:href="&url.books.handbook;/current-stable.html#stable">-STABLE</link>,
+ one <link xlink:href="&url.books.handbook;/current-stable.html#current">-CURRENT</link>.
<emphasis>&os;-STABLE</emphasis> is intended for Internet
Service Providers and other commercial enterprises for whom
sudden shifts or experimental features are quite
@@ -470,11 +443,9 @@
<emphasis>&os;-CURRENT</emphasis>, on the other hand, has
been one unbroken line since 2.0 was released, leading
towards &rel.current;-RELEASE and beyond. For more detailed
- information on branches see <quote><ulink
- url="&url.articles.releng;/release-proc.html#rel-branch">&os; Release Engineering: Creating the Release Branch</ulink></quote>,
+ information on branches see <quote><link xlink:href="&url.articles.releng;/release-proc.html#rel-branch">&os; Release Engineering: Creating the Release Branch</link></quote>,
the status of the branches and the upcoming release schedule
- can be found on the <ulink
- url="http://www.FreeBSD.org/releng">Release Engineering Information</ulink> page.</para>
+ can be found on the <link xlink:href="http://www.FreeBSD.org/releng">Release Engineering Information</link> page.</para>
<para>&rel.current;-STABLE is the actively developed
<emphasis>-STABLE</emphasis> branch. The latest release on
@@ -483,14 +454,13 @@
<para>The &rel.head; branch is the actively developed
<emphasis>-CURRENT</emphasis> branch toward the next
- generation of &os;. See <link
- linkend="current">What is &os;-CURRENT?</link> for more
+ generation of &os;. See <link linkend="current">What is &os;-CURRENT?</link> for more
information on this branch.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="release-freq">
+ <question xml:id="release-freq">
<para>When are &os; releases made?</para>
</question>
@@ -509,8 +479,7 @@
<para>More information on the release engineering process
(including a schedule of upcoming releases) can be found on
- the <ulink
- url="http://www.FreeBSD.org/releng/index.html">release engineering</ulink>
+ the <link xlink:href="http://www.FreeBSD.org/releng/index.html">release engineering</link>
pages on the &os; Web site.</para>
<para>For people who need or want a little more excitement,
@@ -519,18 +488,16 @@
</qandaentry>
<qandaentry>
- <question id="responsible">
+ <question xml:id="responsible">
<para>Who is responsible for &os;?</para>
</question>
<answer>
<para>The key decisions concerning the &os; project, such as
the overall direction of the project and who is allowed to
- add code to the source tree, are made by a <ulink
- url="&url.base;/administration.html#t-core">core team</ulink> of
+ add code to the source tree, are made by a <link xlink:href="&url.base;/administration.html#t-core">core team</link> of
9 people. There is a much larger team of more than 350
- <ulink
- url="&url.articles.contributors;/article.html#staff-committers">committers</ulink>
+ <link xlink:href="&url.articles.contributors;/article.html#staff-committers">committers</link>
who are authorized to make changes directly to the &os;
source tree.</para>
@@ -542,92 +509,80 @@
</qandaentry>
<qandaentry>
- <question id="where-get">
+ <question xml:id="where-get">
<para>Where can I get &os;?</para>
</question>
<answer>
<para>Every significant release of &os; is available via
- anonymous FTP from the <ulink
- url="ftp://ftp.FreeBSD.org/pub/FreeBSD/"> &os; FTP site</ulink>:</para>
+ anonymous FTP from the <link xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/"> &os; FTP site</link>:</para>
<itemizedlist>
<listitem>
<para>The latest &rel.stable; release, &rel.current;-RELEASE
- can be found in the <ulink
- url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/i386/&rel.current;-RELEASE/">&rel.current;-RELEASE directory</ulink>.</para>
+ can be found in the <link xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/i386/&rel.current;-RELEASE/">&rel.current;-RELEASE directory</link>.</para>
</listitem>
<listitem>
- <para><ulink url="&url.base;/snapshots/"> Snapshot</ulink>
- releases are made monthly for the <link
- linkend="current">-CURRENT</link> and <link
- linkend="stable">-STABLE</link> branch, these being of
+ <para><link xlink:href="&url.base;/snapshots/"> Snapshot</link>
+ releases are made monthly for the <link linkend="current">-CURRENT</link> and <link linkend="stable">-STABLE</link> branch, these being of
service purely to bleeding-edge testers and
developers.</para>
</listitem>
<listitem>
<para>The latest &rel2.stable; release, &rel2.current;-RELEASE
- can be found in the <ulink
- url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel2.current;-RELEASE/">&rel2.current;-RELEASE directory</ulink>.</para>
+ can be found in the <link xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel2.current;-RELEASE/">&rel2.current;-RELEASE directory</link>.</para>
</listitem>
</itemizedlist>
<para>Information about obtaining &os; on CD, DVD, and other
- media can be found in <ulink
- url="&url.books.handbook;/mirrors.html">the Handbook</ulink>.</para>
+ media can be found in <link xlink:href="&url.books.handbook;/mirrors.html">the Handbook</link>.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="access-pr">
+ <question xml:id="access-pr">
<para>How do I access the Problem Report database?</para>
</question>
<answer>
<para>The Problem Report database of all user change requests
- may be queried by using our web-based PR <ulink
- url="http://www.FreeBSD.org/cgi/query-pr.cgi?query">query</ulink>
+ may be queried by using our web-based PR <link xlink:href="http://www.FreeBSD.org/cgi/query-pr.cgi?query">query</link>
interface.</para>
<para>The &man.send-pr.1; command can be used to submit
problem reports and change requests via electronic mail.
- Alternatively, the <ulink
- url="http://www.freebsd.org/send-pr.html">web-based problem report submission interface</ulink>
+ Alternatively, the <link xlink:href="http://www.freebsd.org/send-pr.html">web-based problem report submission interface</link>
can be used to submit problem reports through a web
browser.</para>
- <para>Before submitting a problem report, please read <ulink
- url="&url.articles.problem-reports;/article.html">Writing &os; Problem Reports</ulink>,
+ <para>Before submitting a problem report, please read <link xlink:href="&url.articles.problem-reports;/article.html">Writing &os; Problem Reports</link>,
an article on how to write good problem reports.</para>
</answer>
</qandaentry>
</qandaset>
</chapter>
- <chapter id="support">
+ <chapter xml:id="support">
<title>Documentation and Support</title>
<qandaset>
<qandaentry>
- <question id="books">
+ <question xml:id="books">
<para>What good books are there about &os;?</para>
</question>
<answer>
<para>The project produces a wide range of documentation,
- available online from this link: <ulink
- url="http://www.FreeBSD.org/docs.html"></ulink>. In addition, <link
- linkend="bibliography">the Bibliography</link> at the end of this
- FAQ, and <ulink
- url="&url.books.handbook;/bibliography.html">the one in the Handbook</ulink>
+ available online from this link: <uri xlink:href="http://www.FreeBSD.org/docs.html">http://www.FreeBSD.org/docs.html</uri>. In addition, <link linkend="bibliography">the Bibliography</link> at the end of this
+ FAQ, and <link xlink:href="&url.books.handbook;/bibliography.html">the one in the Handbook</link>
reference other recommended books.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="doc-formats">
+ <question xml:id="doc-formats">
<para>Is the documentation available in other formats, such as
plain text (ASCII), or &postscript;?</para>
</question>
@@ -635,8 +590,7 @@
<answer>
<para>Yes. The documentation is available in a number of
different formats and compression schemes on the &os; FTP
- site, in the <ulink
- url="ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/">/pub/FreeBSD/doc/</ulink>
+ site, in the <link xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/">/pub/FreeBSD/doc/</link>
directory.</para>
<para>The documentation is categorized in a number of
@@ -651,7 +605,7 @@
<listitem>
<para>The document's language and encoding. These are
based on the locale names you will find under
- <filename class="directory">/usr/share/locale</filename> on your &os;
+ <filename>/usr/share/locale</filename> on your &os;
system. The current languages and encodings that we
have for documentation are as follows:</para>
@@ -862,10 +816,8 @@
<note>
<para>Page numbers are not automatically updated when
- loading Rich Text Format into Word. Press <keycombo
- action="simul"><keycap>Ctrl</keycap><keycap>A</keycap></keycombo>,
- <keycombo
- action="simul"><keycap>Ctrl</keycap><keycap>End</keycap></keycombo>,
+ loading Rich Text Format into Word. Press <keycombo action="simul"><keycap>Ctrl</keycap><keycap>A</keycap></keycombo>,
+ <keycombo action="simul"><keycap>Ctrl</keycap><keycap>End</keycap></keycombo>,
<keycap>F9</keycap> after loading the document, to
update the page numbers.</para>
</note>
@@ -886,7 +838,7 @@
<listitem>
<para>All the other formats generate one file, called
- <filename><replaceable>type</replaceable>.<replaceable>format</replaceable></filename>
+ <filename>type.format</filename>
(i.e., <filename>article.pdf</filename>,
<filename>book.html</filename>, and so on).</para>
@@ -899,7 +851,7 @@
<para>So the &postscript; version of the Handbook,
compressed using <literal>bzip2</literal> will be stored in a file
called <filename>book.ps.bz2</filename> in the
- <filename class="directory">handbook/</filename> directory.</para>
+ <filename>handbook/</filename> directory.</para>
</listitem>
</orderedlist>
</listitem>
@@ -932,21 +884,19 @@
</qandaentry>
<qandaentry>
- <question id="mailing">
+ <question xml:id="mailing">
<para>Where do I find info on the &os; mailing lists?
What &os; news groups are available?</para>
</question>
<answer>
- <para>You can find full information in the <ulink
- url="&url.books.handbook;/eresources.html#eresources-mail">Handbook entry on mailing-lists</ulink>
- and the <ulink
- url="&url.books.handbook;/eresources-news.html">Handbook entry on newsgroups</ulink>.</para>
+ <para>You can find full information in the <link xlink:href="&url.books.handbook;/eresources.html#eresources-mail">Handbook entry on mailing-lists</link>
+ and the <link xlink:href="&url.books.handbook;/eresources-news.html">Handbook entry on newsgroups</link>.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="irc">
+ <question xml:id="irc">
<para>Are there &os; IRC (Internet Relay Chat)
channels?</para>
</question>
@@ -957,16 +907,14 @@
<itemizedlist>
<listitem>
- <para>Channel <literal>#FreeBSDhelp</literal> on <ulink
- url="http://www.efnet.org/index.php">EFNet</ulink> is
+ <para>Channel <literal>#FreeBSDhelp</literal> on <link xlink:href="http://www.efnet.org/index.php">EFNet</link> is
a channel dedicated to helping &os; users. They are
much more sympathetic to questions than
<literal>#FreeBSD</literal> is.</para>
</listitem>
<listitem>
- <para>Channel <literal>#FreeBSD</literal> on <ulink
- url="http://freenode.net/">Freenode</ulink> is a
+ <para>Channel <literal>#FreeBSD</literal> on <link xlink:href="http://freenode.net/">Freenode</link> is a
general help channel with many users at any time.
The conversations have been known to run off-topic for a
while, but priority is given to users with &os;
@@ -978,45 +926,41 @@
If you would like to speak in your native language, try
to ask the question in English and then relocate to
another channel
- <literal>##freebsd-<replaceable>lang</replaceable></literal>
+ <literal>##freebsd-lang</literal>
as appropriate.</para>
</listitem>
<listitem>
- <para>Channel <literal>#FreeBSD</literal> on <ulink
- url="http://www.dal.net/">DALNET</ulink> is available at
- <hostid>irc.dal.net</hostid> in the US and
- <hostid>irc.eu.dal.net</hostid> in Europe.</para>
+ <para>Channel <literal>#FreeBSD</literal> on <link xlink:href="http://www.dal.net/">DALNET</link> is available at
+ <systemitem>irc.dal.net</systemitem> in the US and
+ <systemitem>irc.eu.dal.net</systemitem> in Europe.</para>
</listitem>
<listitem>
- <para>Channel <literal>#FreeBSD</literal> on <ulink
- url="http://www.undernet.org/">UNDERNET</ulink> is
- available at <hostid>us.undernet.org</hostid> in the US
- and <hostid>eu.undernet.org</hostid> in Europe. Since
+ <para>Channel <literal>#FreeBSD</literal> on <link xlink:href="http://www.undernet.org/">UNDERNET</link> is
+ available at <systemitem>us.undernet.org</systemitem> in the US
+ and <systemitem>eu.undernet.org</systemitem> in Europe. Since
it is a help channel, be prepared to read the documents
you are referred to.</para>
</listitem>
<listitem>
<para>Channel <literal>#FreeBSD</literal> on
- <ulink url="http://www.rusnet.org.ru/">RUSNET</ulink>
+ <link xlink:href="http://www.rusnet.org.ru/">RUSNET</link>
is a russian-language oriented channel dedicated
to helping &os; users. This is also good place
for non-technical discussions.</para>
</listitem>
<listitem>
- <para>Channel <literal>#bsdchat</literal> on <ulink
- url="http://freenode.net/">Freenode</ulink> is a
+ <para>Channel <literal>#bsdchat</literal> on <link xlink:href="http://freenode.net/">Freenode</link> is a
Traditional-Chinese (UTF-8 encoding) language oriented
channel dedicated to helping &os; users. This is also
good place for non-technical discussions.</para>
</listitem>
</itemizedlist>
- <para>The &os; wiki has a <ulink
- url="http://wiki.freebsd.org/IrcChannels">good list</ulink>
+ <para>The &os; wiki has a <link xlink:href="http://wiki.freebsd.org/IrcChannels">good list</link>
of IRC channels.</para>
<para>Each of these channels are distinct and are not
@@ -1031,34 +975,29 @@
</qandaentry>
<qandaentry>
- <question id="forums">
+ <question xml:id="forums">
<para>Are there any web based forums to discuss &os;?</para>
</question>
<answer>
- <para>The official &os; forums are located at <ulink
- url="http://forums.FreeBSD.org/">http://forums.FreeBSD.org/</ulink>.</para>
+ <para>The official &os; forums are located at <link xlink:href="http://forums.FreeBSD.org/">http://forums.FreeBSD.org/</link>.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="training">
+ <question xml:id="training">
<para>Where can I get commercial &os; training and
support?</para>
</question>
<answer>
- <para><ulink
- url="http://www.ixsystems.com">iXsystems, Inc.</ulink>,
- parent company of the <ulink
- url="http://www.freebsdmall.com/">&os; Mall</ulink>,
- provides commercial &os; and PC-BSD software <ulink
- url="http://www.ixsystems.com/bsdsupport">support</ulink>,
+ <para><link xlink:href="http://www.ixsystems.com">iXsystems, Inc.</link>,
+ parent company of the <link xlink:href="http://www.freebsdmall.com/">&os; Mall</link>,
+ provides commercial &os; and PC-BSD software <link xlink:href="http://www.ixsystems.com/bsdsupport">support</link>,
in addition to &os; development and tuning solutions.</para>
<para>BSD Certification Group, Inc. provides system
administration certifications for DragonFly&nbsp;BSD, &os;, NetBSD,
- OpenBSD. If you are interested in them, visit <ulink
- url="http://www.BSDCertification.org">their site</ulink>.</para>
+ OpenBSD. If you are interested in them, visit <link xlink:href="http://www.BSDCertification.org">their site</link>.</para>
<para>Any other organizations providing training and support
should contact the Project to be listed here.</para>
@@ -1067,23 +1006,19 @@
</qandaset>
</chapter>
- <chapter id="install">
- <chapterinfo>
- <author>
- <firstname>Nik</firstname>
- <surname>Clayton</surname>
- <affiliation>
+ <chapter xml:id="install">
+ <info><title>Installation</title>
+ <author><personname><firstname>Nik</firstname><surname>Clayton</surname></personname><affiliation>
<address><email>nik@FreeBSD.org</email></address>
- </affiliation>
- </author>
- </chapterinfo>
+ </affiliation></author>
+ </info>
- <title>Installation</title>
+
<qandaset>
<qandaentry>
- <question id="which-architecture">
+ <question xml:id="which-architecture">
<para>Which platform should I download? I have a 64
bit capable &intel; CPU,
but I only see <literal>amd64</literal>.</para>
@@ -1102,13 +1037,13 @@
</qandaentry>
<qandaentry>
- <question id="floppy-download">
+ <question xml:id="floppy-download">
<para>Which file do I download to get &os;?</para>
</question>
<answer>
<para>On the
- <ulink url="http://www.freebsd.org/where.html">Getting &os;</ulink>
+ <link xlink:href="http://www.freebsd.org/where.html">Getting &os;</link>
page select <literal>[iso]</literal> next to the
architecture you want to use.</para>
@@ -1163,13 +1098,12 @@
<para>Full instructions on this procedure and a little bit
more about installation issues in general can be found in
- the <ulink
- url="&url.books.handbook;/install.html">Handbook entry on installing &os;</ulink>.</para>
+ the <link xlink:href="&url.books.handbook;/install.html">Handbook entry on installing &os;</link>.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="floppy-image-too-large">
+ <question xml:id="floppy-image-too-large">
<para>What do I do if the images do not fit on a
single disk?</para>
</question>
@@ -1212,29 +1146,26 @@
on the floppy as a regular file. You have to transfer
it to the floppy <quote>raw</quote>, using the low-level
tools (e.g., <command>fdimage</command> or
- <command>rawrite</command>) described in the <ulink
- url="&url.books.handbook;/install.html">installation guide to &os;</ulink>.</para>
+ <command>rawrite</command>) described in the <link xlink:href="&url.books.handbook;/install.html">installation guide to &os;</link>.</para>
</listitem>
</itemizedlist>
</answer>
</qandaentry>
<qandaentry>
- <question id="install-instructions-location">
+ <question xml:id="install-instructions-location">
<para>Where are the instructions for installing &os;?</para>
</question>
<answer>
<para>Installation instructions for versions since
- &os;&nbsp;9.0 can be found at <ulink
- url="&url.books.handbook;/bsdinstall.html">Handbook entry on installing &os;</ulink>.
- Older instructions can be found in the <ulink
- url="&url.books.handbook;/install.html">legacy entry on installing &os;</ulink>.</para>
+ &os;&nbsp;9.0 can be found at <link xlink:href="&url.books.handbook;/bsdinstall.html">Handbook entry on installing &os;</link>.
+ Older instructions can be found in the <link xlink:href="&url.books.handbook;/install.html">legacy entry on installing &os;</link>.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="need-to-run">
+ <question xml:id="need-to-run">
<para>What do I need to run &os;?</para>
</question>
@@ -1248,21 +1179,20 @@
</qandaentry>
<qandaentry>
- <question id="custom-boot-floppy">
+ <question xml:id="custom-boot-floppy">
<para>How can I make my own custom release or install disk?</para>
</question>
<answer>
<para>Customized &os; installation media can be created by
building a custom release. Follow the instructions in the
- <ulink
- url="&url.articles.releng;/article.html">Release Engineering</ulink>
+ <link xlink:href="&url.articles.releng;/article.html">Release Engineering</link>
article.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="windows-coexist">
+ <question xml:id="windows-coexist">
<para>Can &windows; co-exist with &os;?</para>
</question>
@@ -1277,7 +1207,7 @@
</qandaentry>
<qandaentry>
- <question id="bootmanager-restore">
+ <question xml:id="bootmanager-restore">
<para>Another operating system destroyed my Boot Manager. How
do I get it back?</para>
</question>
@@ -1301,7 +1231,7 @@
</qandaentry>
<qandaentry>
- <question id="no-install-cdrom">
+ <question xml:id="no-install-cdrom">
<para>I booted from my ATAPI CD-ROM, but the install program
says no CD-ROM is found. Where did it go?</para>
</question>
@@ -1325,15 +1255,14 @@
</qandaentry>
<qandaentry>
- <question id="need-complete-sources">
+ <question xml:id="need-complete-sources">
<para>Do I need to install the source?</para>
</question>
<answer>
<para>In general, no. There is nothing in the base
system which requires the presence of the source to
- operate. Some ports, like <filename
- role="package">sysutils/lsof</filename>, will not build
+ operate. Some ports, like <package>sysutils/lsof</package>, will not build
unless the source is installed. In particular, if the
port builds a kernel module or directly operates on kernel
structures, the source must be installed.</para>
@@ -1341,7 +1270,7 @@
</qandaentry>
<qandaentry>
- <question id="need-kernel">
+ <question xml:id="need-kernel">
<para>Do I need to build a kernel?</para>
</question>
@@ -1359,7 +1288,7 @@
</qandaentry>
<qandaentry>
- <question id="password-encryption">
+ <question xml:id="password-encryption">
<para>Should I use DES, Blowfish, or MD5 passwords and how do
I specify which form my users receive?</para>
</question>
@@ -1387,15 +1316,14 @@
</qandaentry>
<qandaentry>
- <question id="memory-limits">
+ <question xml:id="memory-limits">
<para>What are the limits for memory?</para>
</question>
<answer>
<para>Memory limits depend on the platform used. On a
standard &i386; install, the limit is 4&nbsp;GB but more
- memory can be supported through &man.pae.4;. See <link
- linkend="memory-i386-over-4gb">instructions for using 4&nbsp;GB or more memory on &i386;</link>.</para>
+ memory can be supported through &man.pae.4;. See <link linkend="memory-i386-over-4gb">instructions for using 4&nbsp;GB or more memory on &i386;</link>.</para>
<para>&os;/pc98 has a limit of 4&nbsp;GB memory, and PAE can
not be used with it. Other architectures supported by &os;
@@ -1405,7 +1333,7 @@
</qandaentry>
<qandaentry>
- <question id="ffs-limits">
+ <question xml:id="ffs-limits">
<para>What are the limits for FFS file systems?</para>
</question>
@@ -1500,7 +1428,7 @@
</qandaentry>
<qandaentry>
- <question id="archsw-readin-failed-error">
+ <question xml:id="archsw-readin-failed-error">
<para>Why do I get an error message,
<errorname>readin failed</errorname> after compiling
and booting a new kernel?</para>
@@ -1508,8 +1436,8 @@
<answer>
<para>Because your world and kernel are out of sync. This is
- not supported. Be sure you use <command>make <maketarget>buildworld</maketarget></command>
- and <command>make <maketarget>buildkernel</maketarget></command>
+ not supported. Be sure you use <command>make buildworld</command>
+ and <command>make buildkernel</command>
to update your kernel.</para>
<para>You can boot by specifying the kernel directly at the
@@ -1519,7 +1447,7 @@
</qandaentry>
<qandaentry>
- <question id="general-configuration-tool">
+ <question xml:id="general-configuration-tool">
<para>Is there a tool to perform post-installation
configuration tasks?</para>
</question>
@@ -1529,21 +1457,21 @@
<varname>WITH_BSDCONFIG</varname> in
<filename>/etc/src.conf</filename>. Users of &rel.relx;
and higher may also install
- <filename role="package">sysutils/bsdconfig</filename>.</para>
+ <package>sysutils/bsdconfig</package>.</para>
</answer>
</qandaentry>
</qandaset>
</chapter>
- <chapter id="hardware">
+ <chapter xml:id="hardware">
<title>Hardware Compatibility</title>
- <sect1 id="compatibility-general">
+ <sect1 xml:id="compatibility-general">
<title>General</title>
<qandaset>
<qandaentry>
- <question id="which-hardware-to-get">
+ <question xml:id="which-hardware-to-get">
<para>I want to get a piece of hardware for my &os; system.
Which model/brand/type is best?</para>
</question>
@@ -1553,12 +1481,9 @@
lists. Since hardware changes so quickly, however, we
expect this. We <emphasis>still</emphasis> strongly
recommend that you read through the Hardware&nbsp;Notes
- for &os; <ulink
- url="&rel.current.hardware;">&rel.current;</ulink> or
- <ulink
- url="&rel2.current.hardware;">&rel2.current;</ulink> and
- search the mailing list <ulink
- url="http://www.FreeBSD.org/search/#mailinglists">archives</ulink>
+ for &os; <link xlink:href="&rel.current.hardware;">&rel.current;</link> or
+ <link xlink:href="&rel2.current.hardware;">&rel2.current;</link> and
+ search the mailing list <link xlink:href="http://www.FreeBSD.org/search/#mailinglists">archives</link>
before asking about the latest and greatest hardware.
Chances are a discussion about the type of hardware you
are looking for took place just last week.</para>
@@ -1571,7 +1496,7 @@
</qandaentry>
<qandaentry>
- <question id="memory-upper-limitation">
+ <question xml:id="memory-upper-limitation">
<para>Does &os; support more than 4&nbsp;GB of memory (RAM)?
More than 16&nbsp;GB? More than 48&nbsp;GB?</para>
</question>
@@ -1590,7 +1515,7 @@
</qandaentry>
<qandaentry>
- <question id="memory-i386-over-4gb">
+ <question xml:id="memory-i386-over-4gb">
<para>Why does &os; report less than 4&nbsp;GB memory when
installed on an &i386; machine?</para>
</question>
@@ -1648,12 +1573,12 @@
</qandaset>
</sect1>
- <sect1 id="compatibility-processors">
+ <sect1 xml:id="compatibility-processors">
<title>Architectures and Processors</title>
<qandaset>
<qandaentry>
- <question id="architectures">
+ <question xml:id="architectures">
<para>Does &os; support architectures other than the
x86?</para>
</question>
@@ -1664,18 +1589,16 @@
fully supported. Tiers 2 and 3 are supported on an
if-possible basis. A full explanation of the tier
system is available in the
- <ulink
- url="&url.articles.committers-guide;/archs.html">Committer's Guide.</ulink></para>
+ <link xlink:href="&url.articles.committers-guide;/archs.html">Committer's Guide.</link></para>
<para>A complete list of supported architectures can be
found on the
- <ulink
- url="http://www.FreeBSD.org/platforms/">platforms page.</ulink></para>
+ <link xlink:href="http://www.FreeBSD.org/platforms/">platforms page.</link></para>
</answer>
</qandaentry>
<qandaentry>
- <question id="smp-support">
+ <question xml:id="smp-support">
<para>Does &os; support Symmetric Multiprocessing
(SMP)?</para>
</question>
@@ -1694,7 +1617,7 @@
</qandaentry>
<qandaentry>
- <question id="microcode">
+ <question xml:id="microcode">
<para>What is microcode?
How do I install &intel; CPU microcode updates?</para>
</question>
@@ -1704,7 +1627,7 @@
implementating hardware level instructions. This allows
for CPU bugs to be fixed without replacing the on board chip.</para>
- <para>Install <filename role="package">sysutils/devcpu-data</filename>,
+ <para>Install <package>sysutils/devcpu-data</package>,
then add:</para>
<programlisting>microcode_update_enable="YES"</programlisting>
@@ -1714,12 +1637,12 @@
</qandaset>
</sect1>
- <sect1 id="compatibility-drives">
+ <sect1 xml:id="compatibility-drives">
<title>Hard Drives, Tape Drives, and CD and DVD Drives</title>
<qandaset>
<qandaentry>
- <question id="supported-hard-drives">
+ <question xml:id="supported-hard-drives">
<para>What kind of hard drives does &os; support?</para>
</question>
@@ -1734,20 +1657,19 @@
</qandaentry>
<qandaentry>
- <question id="supported-scsi-controllers">
+ <question xml:id="supported-scsi-controllers">
<para>Which SCSI or SAS controllers are supported?</para>
</question>
<answer>
<para>See the complete list in the Hardware Notes for &os;
- <ulink url="&rel.current.hardware;">&rel.current;</ulink>
- or <ulink
- url="&rel2.current.hardware;">&rel2.current;</ulink>.</para>
+ <link xlink:href="&rel.current.hardware;">&rel.current;</link>
+ or <link xlink:href="&rel2.current.hardware;">&rel2.current;</link>.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="tape-support">
+ <question xml:id="tape-support">
<para>What types of tape drives are supported?</para>
</question>
@@ -1757,7 +1679,7 @@
</qandaentry>
<qandaentry>
- <question id="tape-changer-support">
+ <question xml:id="tape-changer-support">
<para>Does &os; support tape changers?</para>
</question>
@@ -1777,7 +1699,7 @@
</qandaentry>
<qandaentry>
- <question id="supported-cdrom-drives">
+ <question xml:id="supported-cdrom-drives">
<para>Which CD-ROM drives are supported by &os;?</para>
</question>
@@ -1789,7 +1711,7 @@
</qandaentry>
<qandaentry>
- <question id="supported-cdrw-drives">
+ <question xml:id="supported-cdrw-drives">
<para>Which CD-RW drives are supported by &os;?</para>
</question>
@@ -1800,19 +1722,19 @@
<para>&os; also supports any SCSI CD-R or CD-RW drives.
Install and use <command>cdrecord</command>
from the ports or packages system, and make sure that you
- have the <devicename>pass</devicename> device compiled in
+ have the <filename>pass</filename> device compiled in
your kernel.</para>
</answer>
</qandaentry>
</qandaset>
</sect1>
- <sect1 id="compatibility-kbd-mice">
+ <sect1 xml:id="compatibility-kbd-mice">
<title>Keyboards and Mice</title>
<qandaset>
<qandaentry>
- <question id="moused">
+ <question xml:id="moused">
<para>Is it possible to use a mouse in any way outside the X
Window system?</para>
</question>
@@ -1824,7 +1746,7 @@
&man.moused.8;, and turn on the mouse pointer in the
virtual console:</para>
- <screen>&prompt.root; <userinput>moused -p /dev/<replaceable>xxxx</replaceable> -t <replaceable>yyyy</replaceable></userinput>
+ <screen>&prompt.root; <userinput>moused -p /dev/xxxx -t yyyy</userinput>
&prompt.root; <userinput>vidcontrol -m on</userinput></screen>
<para>Where <replaceable>xxxx</replaceable> is the mouse
@@ -1848,14 +1770,13 @@
<para>When the mouse daemon is running, access to the mouse
must be coordinated between the mouse daemon and other
- programs such as X Windows. Refer to the FAQ <link
- linkend="x-and-moused">Why does my mouse not work with X?</link>
+ programs such as X Windows. Refer to the FAQ <link linkend="x-and-moused">Why does my mouse not work with X?</link>
for more details on this issue.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="text-mode-cut-paste">
+ <question xml:id="text-mode-cut-paste">
<para>How do I cut and paste text with a mouse in the text
console?</para>
</question>
@@ -1881,7 +1802,7 @@
</qandaentry>
<qandaentry>
- <question id="mouse-wheel-buttons">
+ <question xml:id="mouse-wheel-buttons">
<para>My mouse has a fancy wheel and buttons. Can I use
them in &os;?</para>
</question>
@@ -1895,13 +1816,12 @@
two, or three button mouse.</para>
<para>For the possible usage of wheels in the X Window
- environment, refer to <link
- linkend="x-and-wheel">that section</link>.</para>
+ environment, refer to <link linkend="x-and-wheel">that section</link>.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="keyboard-delete-key">
+ <question xml:id="keyboard-delete-key">
<para>How do I use my delete key in <command>sh</command>
and <command>csh</command>?</para>
</question>
@@ -1921,19 +1841,18 @@ bind ^[[3~ ed-delete-next-char # for xterm</programlisting>
<programlisting>bindkey ^? delete-char # for console
bindkey ^[[3~ delete-char # for xterm</programlisting>
- <para>For more information, see <ulink
- url="http://www.ibb.net/~anne/keyboard.html">this page</ulink>.</para>
+ <para>For more information, see <link xlink:href="http://www.ibb.net/~anne/keyboard.html">this page</link>.</para>
</answer>
</qandaentry>
</qandaset>
</sect1>
- <sect1 id="compatibility-other">
+ <sect1 xml:id="compatibility-other">
<title>Other Hardware</title>
<qandaset>
<qandaentry>
- <question id="es1370-silent-pcm">
+ <question xml:id="es1370-silent-pcm">
<para>Workarounds for no sound from my &man.pcm.4; sound
card?</para>
</question>
@@ -1948,7 +1867,7 @@ bindkey ^[[3~ delete-char # for xterm</programlisting>
</qandaentry>
<qandaentry>
- <question id="power-management-support">
+ <question xml:id="power-management-support">
<para>Does &os; support power management on my
laptop?</para>
</question>
@@ -1963,12 +1882,12 @@ bindkey ^[[3~ delete-char # for xterm</programlisting>
</sect1>
</chapter>
- <chapter id="troubleshoot">
+ <chapter xml:id="troubleshoot">
<title>Troubleshooting</title>
<qandaset>
<qandaentry>
- <question id="pae">
+ <question xml:id="pae">
<para>Why is &os; finding the wrong amount of memory on &i386;
hardware?</para>
</question>
@@ -1995,8 +1914,7 @@ bindkey ^[[3~ delete-char # for xterm</programlisting>
<para>On a 32-bit version of &os;, the memory appears
lost, since it will be remapped above 4&nbsp;GB, which a
32-bit kernel is unable to access. In this case, the
- solution is to build a PAE enabled kernel. See <link
- linkend="memory-limits">the entry on memory limits</link>
+ solution is to build a PAE enabled kernel. See <link linkend="memory-limits">the entry on memory limits</link>
and <link linkend="memory-upper-limitation">about different
memory limits on different platforms</link> for more
information.</para>
@@ -2012,7 +1930,7 @@ bindkey ^[[3~ delete-char # for xterm</programlisting>
</qandaentry>
<qandaentry>
- <question id="signal11">
+ <question xml:id="signal11">
<para>Why do my programs occasionally die with
<errorname>Signal 11</errorname> errors?</para>
</question>
@@ -2049,11 +1967,11 @@ bindkey ^[[3~ delete-char # for xterm</programlisting>
that the compiler is carrying out changes each time.</para>
<para>For example, suppose you are running
- <command>make <maketarget>buildworld</maketarget></command>,
+ <command>make buildworld</command>,
and the compile fails while trying to compile
<filename>ls.c</filename> into <filename>ls.o</filename>.
If you then run
- <command>make <maketarget>buildworld</maketarget></command>
+ <command>make buildworld</command>
again, and the compile fails in the same place then this is
a broken build &mdash; try updating your sources and try
again. If the compile fails elsewhere then this is almost
@@ -2134,13 +2052,12 @@ bindkey ^[[3~ delete-char # for xterm</programlisting>
you have just found a bug in &os;, and you should follow the
instructions to send a problem report.</para>
- <para>There is an extensive FAQ on this at <ulink
- url="http://www.bitwizard.nl/sig11/">the SIG11 problem FAQ</ulink>.</para>
+ <para>There is an extensive FAQ on this at <link xlink:href="http://www.bitwizard.nl/sig11/">the SIG11 problem FAQ</link>.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="trap-12-panic">
+ <question xml:id="trap-12-panic">
<para>My system crashes with either <errorname>Fatal trap 12:
page fault in kernel mode</errorname>, or
<errorname>panic:</errorname>, and spits out a bunch of
@@ -2151,8 +2068,7 @@ bindkey ^[[3~ delete-char # for xterm</programlisting>
<para>The &os; developers are very interested in these
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>,
+ FAQ section on <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>
@@ -2160,7 +2076,7 @@ bindkey ^[[3~ delete-char # for xterm</programlisting>
</qandaentry>
<qandaentry>
- <question id="proc-table-full">
+ <question xml:id="proc-table-full">
<para>Why do I get the error <errorname>maxproc limit
exceeded by uid %i, please see tuning(7) and
login.conf(5)</errorname>?</para>
@@ -2178,8 +2094,7 @@ bindkey ^[[3~ delete-char # for xterm</programlisting>
maximum number of processes.</para>
<para>To adjust your <varname>kern.maxusers</varname> value,
- see the <ulink
- url="&url.books.handbook;/configtuning-kernel-limits.html#kern-maxfiles">File/Process Limits</ulink>
+ see the <link xlink:href="&url.books.handbook;/configtuning-kernel-limits.html#kern-maxfiles">File/Process Limits</link>
section of the Handbook. (While that section refers to open
files, the same limits apply to processes.)</para>
@@ -2200,7 +2115,7 @@ bindkey ^[[3~ delete-char # for xterm</programlisting>
</qandaentry>
<qandaentry>
- <question id="mail-loopback">
+ <question xml:id="mail-loopback">
<para>Why does <application>sendmail</application> give me an
error reading <errorname>mail loops back to
myself</errorname>?</para>
@@ -2208,13 +2123,12 @@ bindkey ^[[3~ delete-char # for xterm</programlisting>
<answer>
<para>You can find a detailed answer for this question in the
- <ulink
- url="&url.books.handbook;/mail-trouble.html#q26.5.2.">Handbook</ulink>.</para>
+ <link xlink:href="&url.books.handbook;/mail-trouble.html#q26.5.2.">Handbook</link>.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="remote-fullscreen">
+ <question xml:id="remote-fullscreen">
<para>Why do full screen applications on remote machines
misbehave?</para>
</question>
@@ -2269,7 +2183,7 @@ bindkey ^[[3~ delete-char # for xterm</programlisting>
</qandaentry>
<qandaentry>
- <question id="connection-delay">
+ <question xml:id="connection-delay">
<para>Why does it take so long to connect to my computer via
<command>ssh</command> or <command>telnet</command>?</para>
</question>
@@ -2309,7 +2223,7 @@ bindkey ^[[3~ delete-char # for xterm</programlisting>
for more information. If this is on the global Internet,
the problem may be that your server's resolver is not
functioning correctly. To check, try to look up another
- host &mdash; say, <hostid>www.yahoo.com</hostid>. If it
+ host &mdash; say, <systemitem>www.yahoo.com</systemitem>. If it
does not work, that is your problem.</para>
<para>Following a fresh install of &os;, it is also possible
@@ -2329,7 +2243,7 @@ bindkey ^[[3~ delete-char # for xterm</programlisting>
</qandaentry>
<qandaentry>
- <question id="file-table-full">
+ <question xml:id="file-table-full">
<para>Why does <errorname>file: table is full</errorname> show
up repeatedly in &man.dmesg.8;?</para>
</question>
@@ -2337,17 +2251,15 @@ bindkey ^[[3~ delete-char # for xterm</programlisting>
<answer>
<para>This error message indicates you have exhausted the
number of available file descriptors on your system. Please
- see the <ulink
- url="&url.books.handbook;/configtuning-kernel-limits.html#kern-maxfiles">kern.maxfiles</ulink>
- section of the <ulink
- url="&url.books.handbook;/configtuning-kernel-limits.html">Tuning Kernel Limits</ulink>
+ see the <link xlink:href="&url.books.handbook;/configtuning-kernel-limits.html#kern-maxfiles">kern.maxfiles</link>
+ section of the <link xlink:href="&url.books.handbook;/configtuning-kernel-limits.html">Tuning Kernel Limits</link>
section of the Handbook for a discussion and
solution.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="computer-clock-skew">
+ <question xml:id="computer-clock-skew">
<para>Why does the clock on my computer keep incorrect time?</para>
</question>
@@ -2403,7 +2315,7 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
</qandaentry>
<qandaentry>
- <question id="indefinite-wait-buffer">
+ <question xml:id="indefinite-wait-buffer">
<para>What does the error <errorname>swap_pager: indefinite
wait buffer:</errorname> mean?</para>
</question>
@@ -2422,7 +2334,7 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
</qandaentry>
<qandaentry>
- <question id="lock-order-reversal">
+ <question xml:id="lock-order-reversal">
<para>What is a <errorname>lock order
reversal</errorname>?</para>
</question>
@@ -2464,7 +2376,7 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
</qandaentry>
<qandaentry>
- <question id="called-with-non-sleepable-locks-held">
+ <question xml:id="called-with-non-sleepable-locks-held">
<para>What does <errorname>Called ... with the following
non-sleepable locks held</errorname> mean?</para>
</question>
@@ -2500,9 +2412,9 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
</qandaentry>
<qandaentry>
- <question id="touch-not-found">
+ <question xml:id="touch-not-found">
<para>Why does
- <maketarget>buildworld</maketarget>/<maketarget>installworld</maketarget>
+ <buildtarget>buildworld</buildtarget>/<buildtarget>installworld</buildtarget>
die with the message <errorname>touch: not
found</errorname>?</para>
</question>
@@ -2519,18 +2431,17 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
</qandaset>
</chapter>
- <chapter id="applications">
+ <chapter xml:id="applications">
<title>User Applications</title>
<qandaset>
<qandaentry>
- <question id="user-apps">
+ <question xml:id="user-apps">
<para>So, where are all the user applications?</para>
</question>
<answer>
- <para>Please take a look at <ulink
- url="&url.base;/ports/index.html">the ports page</ulink>
+ <para>Please take a look at <link xlink:href="&url.base;/ports/index.html">the ports page</link>
for info on software packages ported to &os;. The list
currently tops &os.numports; and is growing daily, so come
back to check often or subscribe to the &a.announce; for
@@ -2540,7 +2451,7 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
&rel2.relx;, and &rel.relx; branches.
Each time a &os;
release is made, a snapshot of the ports tree at the time of
- release in also included in the <filename class="directory">ports/</filename>
+ release in also included in the <filename>ports/</filename>
directory.</para>
<para>We also support the concept of a <quote>package</quote>,
@@ -2555,7 +2466,7 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
you are interested in installing. Package files can usually
be identified by their <filename>.tbz</filename> suffix and
CD-ROM distribution people will have a
- <filename class="directory">packages/All</filename> directory on their CD
+ <filename>packages/All</filename> directory on their CD
which contains such files. They can also be downloaded over
the net for various versions of &os; at the following
locations:</para>
@@ -2565,8 +2476,7 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
<term>for &rel2.relx;&nbsp;-RELEASE/&rel2.stable;</term>
<listitem>
- <para><ulink
- url="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/&rel2.packages;/">ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/&rel2.packages;</ulink></para>
+ <para><link xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/&rel2.packages;/">ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/&rel2.packages;</link></para>
</listitem>
</varlistentry>
@@ -2574,8 +2484,7 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
<term>for &rel.relx;&nbsp;-RELEASE/&rel.stable;</term>
<listitem>
- <para><ulink
- url="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/&rel.packages;/">ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/&rel.packages;</ulink></para>
+ <para><link xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/&rel.packages;/">ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/&rel.packages;</link></para>
</listitem>
</varlistentry>
</variablelist>
@@ -2585,14 +2494,13 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
<para>Note that all ports may not be available as packages
since new ones are constantly being added. It is always a
good idea to check back periodically to see which packages
- are available at the <ulink
- url="ftp://ftp.FreeBSD.org/pub/FreeBSD/">ftp.FreeBSD.org</ulink>
+ are available at the <link xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/">ftp.FreeBSD.org</link>
master site.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="how-do-download-ports-tree">
+ <question xml:id="how-do-download-ports-tree">
<para>How do I download the Ports tree? Should I be using
SVN?</para>
</question>
@@ -2621,18 +2529,17 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
</qandaentry>
<qandaentry>
- <question id="java">
+ <question xml:id="java">
<para>Does &os; support &java;?</para>
</question>
<answer>
- <para>Yes. Please see <ulink
- url="&url.base;/java/index.html">http://www.FreeBSD.org/java/</ulink>.</para>
+ <para>Yes. Please see <link xlink:href="&url.base;/java/index.html">http://www.FreeBSD.org/java/</link>.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="ports-4x">
+ <question xml:id="ports-4x">
<para>Why can I not build this port on my
&rel2.relx;&nbsp;-, or
&rel.relx;&nbsp;-STABLE machine?</para>
@@ -2642,8 +2549,7 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
<para>If you are running a &os; version that lags
significantly behind <emphasis>-CURRENT</emphasis> or
<emphasis>-STABLE</emphasis>, you may need to update your
- Ports Collection; see the <ulink
- url="&url.books.porters-handbook;/keeping-up.html">Keeping Up</ulink>
+ Ports Collection; see the <link xlink:href="&url.books.porters-handbook;/keeping-up.html">Keeping Up</link>
section of the Porter's Handbook for further information on
how to do this. If you are up to date, then someone might
have committed a change to the port which works for
@@ -2657,9 +2563,9 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
</qandaentry>
<qandaentry>
- <question id="make-index">
+ <question xml:id="make-index">
<para>I just tried to build <filename>INDEX</filename> using
- <command>make <maketarget>index</maketarget></command>, and
+ <command>make index</command>, and
it failed. Why?</para>
</question>
@@ -2672,8 +2578,8 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
<para>There are rare cases where <filename>INDEX</filename>
will not build due to odd cases involving
- <makevar>WITH_<replaceable>*</replaceable></makevar> or
- <makevar>WITHOUT_<replaceable>*</replaceable></makevar>
+ <varname>WITH_<replaceable>*</replaceable></varname> or
+ <varname>WITHOUT_<replaceable>*</replaceable></varname>
variables being set in <filename>make.conf</filename>. If
you suspect that this is the case, please try to make
<filename>INDEX</filename> with those make variables turned
@@ -2682,7 +2588,7 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
</qandaentry>
<qandaentry>
- <question id="ports-update">
+ <question xml:id="ports-update">
<para>I updated the sources, now how do I update my installed
ports?</para>
</question>
@@ -2691,14 +2597,13 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
<para>&os; does not include a port upgrading tool, but it does
have some tools to make the upgrade process somewhat easier.
You can also install additional tools to simplify port
- handling, see the <ulink
- url="&url.books.handbook;/ports-using.html">Upgrading Ports</ulink>
+ handling, see the <link xlink:href="&url.books.handbook;/ports-using.html">Upgrading Ports</link>
section in the &os; Handbook.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="ports-major-upgrade">
+ <question xml:id="ports-major-upgrade">
<para>Do I need to recompile every port each time I perform a
major version update?</para>
</question>
@@ -2716,14 +2621,13 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
the older versions may fail to start or, in other cases,
fail to function properly.</para>
- <para>For more information, see <ulink
- url="&url.books.handbook;/updating-upgrading-freebsdupdate.html#freebsdupdate-upgrade">the section on upgrades</ulink>
+ <para>For more information, see <link xlink:href="&url.books.handbook;/updating-upgrading-freebsdupdate.html#freebsdupdate-upgrade">the section on upgrades</link>
in the &os; Handbook.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="ports-minor-upgrade">
+ <question xml:id="ports-minor-upgrade">
<para>Do I need to recompile every port each time I perform a
minor version update?</para>
</question>
@@ -2738,7 +2642,7 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
</qandaentry>
<qandaentry>
- <question id="minimal-sh">
+ <question xml:id="minimal-sh">
<para>Why is <command>/bin/sh</command> so minimal? Why
does &os; not use <command>bash</command> or another
shell?</para>
@@ -2770,43 +2674,39 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
compare for yourself the memory utilization of all these
shells by looking at the <quote>VSZ</quote> and
<quote>RSS</quote> columns in a <command>ps
- <option>-u</option></command> listing.)</para>
+ -u</command> listing.)</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="midi-sound-files">
+ <question xml:id="midi-sound-files">
<para>How do I create audio CDs from my MIDI files?</para>
</question>
<answer>
<para>To create audio CDs from MIDI files, first install
- <filename role="package">audio/timidity++</filename> from
+ <package>audio/timidity++</package> from
ports then install manually the GUS patches set by Eric A.
- Welsh, available at <ulink
- url="http://alleg.sourceforge.net/digmid.html"></ulink>.
+ Welsh, available at <uri xlink:href="http://alleg.sourceforge.net/digmid.html">http://alleg.sourceforge.net/digmid.html</uri>.
After <application>TiMidity++</application> has been installed
properly, MIDI files may be converted to WAV files with the
following command line:</para>
- <screen>&prompt.user; <userinput>timidity -Ow -s 44100 -o <replaceable>/tmp/juke/01.wav</replaceable> <replaceable>01.mid</replaceable></userinput></screen>
+ <screen>&prompt.user; <userinput>timidity -Ow -s 44100 -o /tmp/juke/01.wav 01.mid</userinput></screen>
<para>The WAV files can then be converted to other formats or
- burned onto audio CDs, as described in the <ulink
- url="&url.books.handbook;/creating-cds.html">&os; Handbook</ulink>.</para>
+ burned onto audio CDs, as described in the <link xlink:href="&url.books.handbook;/creating-cds.html">&os; Handbook</link>.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="officesuite">
+ <question xml:id="officesuite">
<para>Where can I get an Office Suite for &os;?</para>
</question>
<answer>
- <para>The open-source <application><ulink
- url="http://www.openoffice.org">Apache OpenOffice</ulink></application>
- and <application><ulink
- url="http://www.libreoffice.org">LibreOffice</ulink></application>
+ <para>The open-source <application>Apache OpenOffice</application>
+ and <application>LibreOffice</application>
office suites work natively on &os;.</para>
<para>&os; also includes a variety of text editors,
@@ -2816,7 +2716,7 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
</qandaentry>
<qandaentry>
- <question id="convert-back-from-pkgng">
+ <question xml:id="convert-back-from-pkgng">
<para>How can I convert from pkgng to the old package
tools?</para>
</question>
@@ -2837,25 +2737,24 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
</qandaset>
</chapter>
- <chapter id="kernelconfig">
+ <chapter xml:id="kernelconfig">
<title>Kernel Configuration</title>
<qandaset>
<qandaentry>
- <question id="make-kernel">
+ <question xml:id="make-kernel">
<para>I would like to customize my kernel. Is it
difficult?</para>
</question>
<answer>
- <para>Not at all! Check out the <ulink
- url="&url.books.handbook;/kernelconfig.html">kernel config section of the Handbook</ulink>.</para>
+ <para>Not at all! Check out the <link xlink:href="&url.books.handbook;/kernelconfig.html">kernel config section of the Handbook</link>.</para>
<note>
<para>The new <filename>kernel</filename> will be installed
- to the <filename class="directory">/boot/kernel</filename> directory along
+ to the <filename>/boot/kernel</filename> directory along
with its modules, while the old kernel and its modules
- will be moved to the <filename class="directory">/boot/kernel.old</filename>
+ will be moved to the <filename>/boot/kernel.old</filename>
directory, so if you make a mistake the next time you play
with your configuration you can boot the previous version
of your kernel.</para>
@@ -2864,7 +2763,7 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
</qandaentry>
<qandaentry>
- <question id="why-kernel-big">
+ <question xml:id="why-kernel-big">
<para>Why is my kernel so big?</para>
</question>
@@ -2874,14 +2773,13 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
Kernels built in debug mode
contain many symbols in separate files that are used for
debugging, thus greatly increasing the size of
- <filename class="directory">/boot/kernel/</filename>.
+ <filename>/boot/kernel/</filename>.
Note that there will be little or no performance loss
from running a debug kernel, and it is useful to keep one
around in case of a system panic.</para>
<para>However, if you are running low on disk space, there
- are different options to reduce the size of <filename
- class="directory">/boot/kernel/</filename>.</para>
+ are different options to reduce the size of <filename>/boot/kernel/</filename>.</para>
<para>If you do not want the symbol files to be installed,
make sure you have the following line present in
@@ -2930,7 +2828,7 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
<xref linkend="make-kernel"/> for more information.</para>
<para>To put any of these options into effect you will have
- to <ulink url="&url.books.handbook;/kernelconfig-building.html">build and install</ulink>
+ to <link xlink:href="&url.books.handbook;/kernelconfig-building.html">build and install</link>
your new kernel.</para>
<para>Most kernels (<filename>/boot/kernel/kernel</filename>)
@@ -2939,7 +2837,7 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
</qandaentry>
<qandaentry>
- <question id="generic-kernel-build-failure">
+ <question xml:id="generic-kernel-build-failure">
<para>Why does every kernel I try to build fail to compile,
even <filename>GENERIC</filename>?</para>
</question>
@@ -2951,8 +2849,8 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
<itemizedlist>
<listitem>
<para>You are not using the
- <command>make <maketarget>buildkernel</maketarget></command> and
- <command>make <maketarget>installkernel</maketarget></command>
+ <command>make buildkernel</command> and
+ <command>make installkernel</command>
targets, and your source tree is different from the one
used to build the currently running system (e.g., you
are compiling &rel.current;-RELEASE on a
@@ -2965,21 +2863,20 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
<listitem>
<para>You are using the
- <command>make <maketarget>buildkernel</maketarget></command>
+ <command>make buildkernel</command>
and
- <command>make <maketarget>installkernel</maketarget></command>
+ <command>make installkernel</command>
targets, but you failed to assert the completion of the
- <command>make <maketarget>buildworld</maketarget></command>
+ <command>make buildworld</command>
target. The
- <command>make <maketarget>buildkernel</maketarget></command>
+ <command>make buildkernel</command>
target relies on files generated by the
- <command>make <maketarget>buildworld</maketarget></command>
+ <command>make buildworld</command>
target to complete its job correctly.</para>
</listitem>
<listitem>
- <para>Even if you are trying to build <link
- linkend="stable">&os;-STABLE</link>, it is possible that
+ <para>Even if you are trying to build <link linkend="stable">&os;-STABLE</link>, it is possible that
you fetched the source tree at a time when it was either
being modified, or broken for other reasons; only
releases are absolutely guaranteed to be buildable,
@@ -2994,7 +2891,7 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
</qandaentry>
<qandaentry>
- <question id="scheduler-in-use">
+ <question xml:id="scheduler-in-use">
<para>How can I verify which scheduler is in use on a running
system?</para>
</question>
@@ -3010,7 +2907,7 @@ kern.sched.name: ULE</screen>
</qandaentry>
<qandaentry>
- <question id="scheduler-kern-quantum">
+ <question xml:id="scheduler-kern-quantum">
<para>What is <varname>kern.sched.quantum</varname>?</para>
</question>
@@ -3023,24 +2920,23 @@ kern.sched.name: ULE</screen>
</qandaset>
</chapter>
- <chapter id="disks">
+ <chapter xml:id="disks">
<title>Disks, File Systems, and Boot Loaders</title>
<qandaset>
<qandaentry>
- <question id="adding-disks">
+ <question xml:id="adding-disks">
<para>How can I add my new hard disk to my &os; system?</para>
</question>
<answer>
- <para>See the <ulink
- url="&url.books.handbook;/disks-adding.html">Adding Disks</ulink>
+ <para>See the <link xlink:href="&url.books.handbook;/disks-adding.html">Adding Disks</link>
section in the &os; Handbook.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="new-huge-disk">
+ <question xml:id="new-huge-disk">
<para>How do I move my system over to my huge new disk?</para>
</question>
@@ -3064,7 +2960,7 @@ kern.sched.name: ULE</screen>
<para>Now you have the new disk set up, and are ready to move
the data. Unfortunately, you cannot just blindly copy the
data. Things like device files (in
- <filename class="directory">/dev</filename>), flags, and links tend to screw
+ <filename>/dev</filename>), flags, and links tend to screw
that up. You need to use tools that understand these
things, which means &man.dump.8;. Although it is suggested
that you move the data in single user mode, it is not
@@ -3099,41 +2995,41 @@ kern.sched.name: ULE</screen>
</procedure>
<para>For example, if you are going to move root to
- <devicename>/dev/<replaceable>ada1s1a</replaceable></devicename>,
- with <filename class="directory"><replaceable>/mnt</replaceable></filename> as
+ <filename>/dev/ada1s1a</filename>,
+ with <filename>/mnt</filename> as
the temporary mount point, it is:</para>
- <screen>&prompt.root; <userinput>newfs /dev/<replaceable>ada1s1a</replaceable></userinput>
-&prompt.root; <userinput>mount /dev/<replaceable>ada1s1a</replaceable> <replaceable>/mnt</replaceable></userinput>
-&prompt.root; <userinput>cd <replaceable>/mnt</replaceable></userinput>
+ <screen>&prompt.root; <userinput>newfs /dev/ada1s1a</userinput>
+&prompt.root; <userinput>mount /dev/ada1s1a /mnt</userinput>
+&prompt.root; <userinput>cd /mnt</userinput>
&prompt.root; <userinput>dump 0af - / | restore rf -</userinput></screen>
<para>Rearranging your partitions with <command>dump</command>
takes a bit more work. To merge a partition like
- <filename class="directory">/var</filename> into its parent, create the new
+ <filename>/var</filename> into its parent, create the new
partition large enough for both, move the parent partition
as described above, then move the child partition into the
empty directory that the first move created:</para>
- <screen>&prompt.root; <userinput>newfs /dev/<replaceable>ada1s1a</replaceable></userinput>
-&prompt.root; <userinput>mount /dev/<replaceable>ada1s1a</replaceable> <replaceable>/mnt</replaceable></userinput>
-&prompt.root; <userinput>cd <replaceable>/mnt</replaceable></userinput>
+ <screen>&prompt.root; <userinput>newfs /dev/ada1s1a</userinput>
+&prompt.root; <userinput>mount /dev/ada1s1a /mnt</userinput>
+&prompt.root; <userinput>cd /mnt</userinput>
&prompt.root; <userinput>dump 0af - / | restore rf -</userinput>
&prompt.root; <userinput>cd var</userinput>
&prompt.root; <userinput>dump 0af - /var | restore rf -</userinput></screen>
<para>To split a directory from its parent, say putting
- <filename class="directory">/var</filename> on its own partition when it was
+ <filename>/var</filename> on its own partition when it was
not before, create both partitions, then mount the child
partition on the appropriate directory in the temporary
mount point, then move the old single partition:</para>
- <screen>&prompt.root; <userinput>newfs /dev/<replaceable>ada1s1a</replaceable></userinput>
-&prompt.root; <userinput>newfs /dev/<replaceable>ada1s1d</replaceable></userinput>
-&prompt.root; <userinput>mount /dev/<replaceable>ada1s1a</replaceable> <replaceable>/mnt</replaceable></userinput>
-&prompt.root; <userinput>mkdir <replaceable>/mnt</replaceable>/var</userinput>
-&prompt.root; <userinput>mount /dev/<replaceable>ada1s1d</replaceable> <replaceable>/mnt</replaceable>/var</userinput>
-&prompt.root; <userinput>cd <replaceable>/mnt</replaceable></userinput>
+ <screen>&prompt.root; <userinput>newfs /dev/ada1s1a</userinput>
+&prompt.root; <userinput>newfs /dev/ada1s1d</userinput>
+&prompt.root; <userinput>mount /dev/ada1s1a /mnt</userinput>
+&prompt.root; <userinput>mkdir /mnt/var</userinput>
+&prompt.root; <userinput>mount /dev/ada1s1d /mnt/var</userinput>
+&prompt.root; <userinput>cd /mnt</userinput>
&prompt.root; <userinput>dump 0af - / | restore rf -</userinput></screen>
<para>You might prefer &man.cpio.1;, &man.pax.1;, &man.tar.1;
@@ -3144,9 +3040,9 @@ kern.sched.name: ULE</screen>
</qandaentry>
<qandaentry>
- <question id="safe-softupdates">
+ <question xml:id="safe-softupdates">
<para>Which partitions can safely use Soft Updates? I have
- heard that Soft Updates on <filename class="directory">/</filename> can cause
+ heard that Soft Updates on <filename>/</filename> can cause
problems. What about Journaled Soft Updates?</para>
</question>
@@ -3196,13 +3092,13 @@ kern.sched.name: ULE</screen>
tolerate this much risk, do not use Soft Updates on the root
file system!</para>
- <para><filename class="directory">/</filename> is traditionally one of the
+ <para><filename>/</filename> is traditionally one of the
smallest partitions. If you put the
- <filename class="directory">/tmp</filename> directory on
- <filename class="directory">/</filename> and you have a busy
- <filename class="directory">/tmp</filename>, you might see intermittent space
- problems. Symlinking <filename class="directory">/tmp</filename> to
- <filename class="directory">/var/tmp</filename> will solve this
+ <filename>/tmp</filename> directory on
+ <filename>/</filename> and you have a busy
+ <filename>/tmp</filename>, you might see intermittent space
+ problems. Symlinking <filename>/tmp</filename> to
+ <filename>/var/tmp</filename> will solve this
problem.</para>
<para>Finally, &man.dump.8; does not work in live mode (-L)
@@ -3212,7 +3108,7 @@ kern.sched.name: ULE</screen>
</qandaentry>
<qandaentry>
- <question id="mount-foreign-fs">
+ <question xml:id="mount-foreign-fs">
<para>Can I mount other foreign file systems under
&os;?</para>
</question>
@@ -3248,9 +3144,8 @@ kern.sched.name: ULE</screen>
<listitem>
<para>FUSE based NTFS support is available as a port
- (<filename role="package">sysutils/fusefs-ntfs</filename>).
- For more information see <ulink
- url="http://www.tuxera.com/community/ntfs-3g-manual/"><application>ntfs-3g</application></ulink>.</para>
+ (<package>sysutils/fusefs-ntfs</package>).
+ For more information see <link xlink:href="http://www.tuxera.com/community/ntfs-3g-manual/"><application>ntfs-3g</application></link>.</para>
</listitem>
</varlistentry>
@@ -3278,14 +3173,13 @@ kern.sched.name: ULE</screen>
<para>&os; also supports network file systems such as NFS (see
&man.mount.nfs.8;), NetWare (see &man.mount.nwfs.8;), and
Microsoft-style SMB file systems (see &man.mount.smbfs.8;).
- You can find ports based on FUSE (<filename
- role="package">sysutils/fusefs-kmod</filename>) for many
+ You can find ports based on FUSE (<package>sysutils/fusefs-kmod</package>) for many
other file systems.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="mount-dos">
+ <question xml:id="mount-dos">
<para>How do I mount a secondary DOS partition?</para>
</question>
@@ -3295,27 +3189,26 @@ kern.sched.name: ULE</screen>
example, if you have an <quote>E</quote> partition as the
second DOS partition on the second SCSI drive, there will be
a device file for <quote>slice 5</quote> in
- <filename class="directory">/dev</filename>, so simply mount it:</para>
+ <filename>/dev</filename>, so simply mount it:</para>
<screen>&prompt.root; <userinput>mount -t msdosfs /dev/da1s5 /dos/e</userinput></screen>
</answer>
</qandaentry>
<qandaentry>
- <question id="crypto-file-system">
+ <question xml:id="crypto-file-system">
<para>Is there a cryptographic file system for &os;?</para>
</question>
<answer>
<para>Yes. You can use either &man.gbde.8; or &man.geli.8;,
- see the <ulink
- url="&url.books.handbook;/disks-encrypting.html">Encrypting Disk Partitions</ulink>
+ see the <link xlink:href="&url.books.handbook;/disks-encrypting.html">Encrypting Disk Partitions</link>
section of the &os; Handbook.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="nt-bootloader">
+ <question xml:id="nt-bootloader">
<para>How can I use the &windowsnt; loader to boot
&os;?</para>
</question>
@@ -3372,7 +3265,7 @@ C:\="DOS"</programlisting>
</qandaentry>
<qandaentry>
- <question id="lilo-bootloader">
+ <question xml:id="lilo-bootloader">
<para>How do I boot &os; and &linux; from LILO?</para>
</question>
@@ -3390,9 +3283,9 @@ C:\="DOS"</programlisting>
label=&os;</programlisting>
<para>(the above assumes that your &os; slice is known to
- &linux; as <devicename>/dev/hda2</devicename>; tailor to
+ &linux; as <filename>/dev/hda2</filename>; tailor to
suit your setup). Then, run <command>lilo</command> as
- <username>root</username> and you should be done.</para>
+ <systemitem class="username">root</systemitem> and you should be done.</para>
<para>If &os; resides on another disk, you need to add
<literal>loader=/boot/chain.b</literal> to the LILO entry.
@@ -3414,15 +3307,14 @@ C:\="DOS"</programlisting>
<para>You can configure &man.boot.8; to automatically do this
for you at boot time.</para>
- <para>The <ulink
- url="http://tldp.org/HOWTO/Linux+FreeBSD.html">&linux;+&os; mini-HOWTO</ulink>
+ <para>The <link xlink:href="http://tldp.org/HOWTO/Linux+FreeBSD.html">&linux;+&os; mini-HOWTO</link>
is a good reference for &os; and &linux; interoperability
issues.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="grub-loader">
+ <question xml:id="grub-loader">
<para>How do I boot &os; and &linux; using GRUB?</para>
</question>
@@ -3447,7 +3339,7 @@ C:\="DOS"</programlisting>
</qandaentry>
<qandaentry>
- <question id="booteasy-loader">
+ <question xml:id="booteasy-loader">
<para>How do I boot &os; and &linux; using
<application>BootEasy?</application></para>
</question>
@@ -3466,7 +3358,7 @@ C:\="DOS"</programlisting>
</qandaentry>
<qandaentry>
- <question id="changing-bootprompt">
+ <question xml:id="changing-bootprompt">
<para>How do I change the boot prompt from
<literal>???</literal> to something more meaningful?</para>
</question>
@@ -3474,13 +3366,13 @@ C:\="DOS"</programlisting>
<answer>
<para>You can not do that with the standard boot manager
without rewriting it. There are a number of other boot
- managers in the <filename class="directory">sysutils</filename> ports category
+ managers in the <filename>sysutils</filename> ports category
that provide this functionality.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="removable-drives">
+ <question xml:id="removable-drives">
<para>I have a new removable drive, how do I use it?</para>
</question>
@@ -3521,22 +3413,20 @@ C:\="DOS"</programlisting>
</qandaentry>
<qandaentry>
- <question id="mount-cd-superblock">
+ <question xml:id="mount-cd-superblock">
<para>Why do I get <errorname>Incorrect super
block</errorname> when mounting a CD-ROM?</para>
</question>
<answer>
<para>You have to tell &man.mount.8; the type of the device
- that you want to mount. This is described in the <ulink
- url="&url.books.handbook;/creating-cds.html"> Handbook section on optical media</ulink>,
- specifically the section <ulink
- url="&url.books.handbook;/creating-cds.html#mounting-cd">Using Data CDs</ulink>.</para>
+ that you want to mount. This is described in the <link xlink:href="&url.books.handbook;/creating-cds.html"> Handbook section on optical media</link>,
+ specifically the section <link xlink:href="&url.books.handbook;/creating-cds.html#mounting-cd">Using Data CDs</link>.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="cdrom-not-configured">
+ <question xml:id="cdrom-not-configured">
<para>Why do I get <errorname>Device not
configured</errorname> when mounting a CD-ROM?</para>
</question>
@@ -3544,15 +3434,14 @@ C:\="DOS"</programlisting>
<answer>
<para>This generally means that there is no CD-ROM in the
CD-ROM drive, or the drive is not visible on the bus.
- Please see the <ulink
- url="&url.books.handbook;/creating-cds.html#mounting-cd">Using Data CDs</ulink>
+ Please see the <link xlink:href="&url.books.handbook;/creating-cds.html#mounting-cd">Using Data CDs</link>
section of the Handbook for a detailed discussion of this
issue.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="cdrom-unicode-filenames">
+ <question xml:id="cdrom-unicode-filenames">
<para>Why do all non-English characters in filenames show up
as <quote>?</quote> on my CDs when mounted in &os;?</para>
</question>
@@ -3561,15 +3450,13 @@ C:\="DOS"</programlisting>
<para>Your CD-ROM probably uses the <quote>Joliet</quote>
extension for storing information about files and
directories. This is discussed in the Handbook chapter on
- <ulink
- url="&url.books.handbook;/creating-cds.html">creating and using CD-ROMs</ulink>,
- specifically the section on <ulink
- url="&url.books.handbook;/creating-cds.html#mounting-cd">Using Data CD-ROMs</ulink>.</para>
+ <link xlink:href="&url.books.handbook;/creating-cds.html">creating and using CD-ROMs</link>,
+ specifically the section on <link xlink:href="&url.books.handbook;/creating-cds.html#mounting-cd">Using Data CD-ROMs</link>.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="burncd-isofs">
+ <question xml:id="burncd-isofs">
<para>I burned a CD under &os; and now I can not read it under
any other operating system. Why?</para>
</question>
@@ -3577,29 +3464,25 @@ C:\="DOS"</programlisting>
<answer>
<para>You most likely burned a raw file to your CD, rather
than creating an ISO&nbsp;9660 file system. Take a look at
- the <ulink
- url="&url.books.handbook;/creating-cds.html">Handbook chapter on creating CD-ROMs</ulink>,
- particularly the section on <ulink
- url="&url.books.handbook;/creating-cds.html#rawdata-cd">burning raw data CDs</ulink>.</para>
+ the <link xlink:href="&url.books.handbook;/creating-cds.html">Handbook chapter on creating CD-ROMs</link>,
+ particularly the section on <link xlink:href="&url.books.handbook;/creating-cds.html#rawdata-cd">burning raw data CDs</link>.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="copy-cd">
+ <question xml:id="copy-cd">
<para>How can I create an image of a data CD?</para>
</question>
<answer>
- <para>This is discussed in the Handbook section on <ulink
- url="&url.books.handbook;/creating-cds.html#imaging-cd">duplicating data CDs</ulink>.
- For more on working with CD-ROMs, see the <ulink
- url="&url.books.handbook;/creating-cds.html">Creating CDs Section</ulink>
+ <para>This is discussed in the Handbook section on <link xlink:href="&url.books.handbook;/creating-cds.html#imaging-cd">duplicating data CDs</link>.
+ For more on working with CD-ROMs, see the <link xlink:href="&url.books.handbook;/creating-cds.html">Creating CDs Section</link>
in the Storage chapter in the Handbook.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="mount-audio-CD">
+ <question xml:id="mount-audio-CD">
<para>Why can I not <command>mount</command> an audio
CD?</para>
</question>
@@ -3610,13 +3493,12 @@ C:\="DOS"</programlisting>
argument</errorname>. This is because
<command>mount</command> only works on file systems. Audio
CDs do not have file systems; they just have data. You need
- a program that reads audio CDs, such as the <filename
- role="package">audio/xmcd</filename> port.</para>
+ a program that reads audio CDs, such as the <package>audio/xmcd</package> port.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="multi-session-CD">
+ <question xml:id="multi-session-CD">
<para>How do I <command>mount</command> a multi-session
CD?</para>
</question>
@@ -3631,20 +3513,20 @@ C:\="DOS"</programlisting>
</qandaentry>
<qandaentry>
- <question id="user-floppymount">
+ <question xml:id="user-floppymount">
<para>How do I let ordinary users mount CD-ROMs, DVDs,
USB drives, and other removable media?</para>
</question>
<answer>
- <para>As <username>root</username> set the sysctl variable
+ <para>As <systemitem class="username">root</systemitem> set the sysctl variable
<varname>vfs.usermount</varname> to
<literal>1</literal>.</para>
<screen>&prompt.root; <userinput>sysctl vfs.usermount=1</userinput></screen>
<para>To make this persist across reboots, add the line
- <literal><varname>vfs.usermount</varname>=1</literal> to
+ <literal>vfs.usermount=1</literal> to
<filename>/etc/sysctl.conf</filename> so that
it is reset at system boot time.</para>
@@ -3663,17 +3545,16 @@ C:\="DOS"</programlisting>
<para>All users can now mount devices they could read
onto a directory that they own:</para>
- <screen>&prompt.user; <userinput>mkdir <replaceable>~/my-mount-point</replaceable></userinput>
-&prompt.user; <userinput>mount -t msdosfs /dev/da0<replaceable>~/my-mount-point</replaceable></userinput></screen>
+ <screen>&prompt.user; <userinput>mkdir ~/my-mount-point</userinput>
+&prompt.user; <userinput>mount -t msdosfs /dev/da0~/my-mount-point</userinput></screen>
<para>Unmounting the device is simple:</para>
- <screen>&prompt.user; <userinput>umount <replaceable>~/my-mount-point</replaceable></userinput></screen>
+ <screen>&prompt.user; <userinput>umount ~/my-mount-point</userinput></screen>
<para>Enabling <varname>vfs.usermount</varname>, however, has
negative security implications. A better way to access
- &ms-dos; formatted media is to use the <filename
- role="package">emulators/mtools</filename> package in the
+ &ms-dos; formatted media is to use the <package>emulators/mtools</package> package in the
Ports Collection.</para>
<note>
@@ -3684,7 +3565,7 @@ C:\="DOS"</programlisting>
</qandaentry>
<qandaentry>
- <question id="du-vs-df">
+ <question xml:id="du-vs-df">
<para>The <command>du</command> and <command>df</command>
commands show different amounts of disk space available.
What is going on?</para>
@@ -3724,7 +3605,7 @@ C:\="DOS"</programlisting>
<para>This situation is common on web servers. Many people
set up a &os; web server and forget to rotate the log files.
- The access log fills up <filename class="directory">/var</filename>. The new
+ The access log fills up <filename>/var</filename>. The new
administrator deletes the file, but the system still
complains that the partition is full. Stopping and
restarting the web server program would free the file,
@@ -3738,21 +3619,19 @@ C:\="DOS"</programlisting>
</qandaentry>
<qandaentry>
- <question id="add-swap-space">
+ <question xml:id="add-swap-space">
<para>How can I add more swap space?</para>
</question>
<answer>
- <para>In the <ulink
- url="&url.books.handbook;/config-tuning.html">Configuration and Tuning</ulink>
- section of the Handbook, you will find a <ulink
- url="&url.books.handbook;/adding-swap-space.html">section</ulink>
+ <para>In the <link xlink:href="&url.books.handbook;/config-tuning.html">Configuration and Tuning</link>
+ section of the Handbook, you will find a <link xlink:href="&url.books.handbook;/adding-swap-space.html">section</link>
describing how to do this.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="manufacturer-disk-size">
+ <question xml:id="manufacturer-disk-size">
<para>Why does &os; see my disk as smaller than the
manufacturer says it is?</para>
</question>
@@ -3764,14 +3643,13 @@ C:\="DOS"</programlisting>
example, &os;'s boot messages will report a disk that
supposedly has 80&nbsp;GB as holding 76,319&nbsp;MB.</para>
- <para>Also note that &os; will (by default) <link
- linkend="disk-more-than-full">reserve</link> 8% of the disk
+ <para>Also note that &os; will (by default) <link linkend="disk-more-than-full">reserve</link> 8% of the disk
space.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="disk-more-than-full">
+ <question xml:id="disk-more-than-full">
<para>How is it possible for a partition to be more than 100%
full?</para>
</question>
@@ -3779,7 +3657,7 @@ C:\="DOS"</programlisting>
<answer>
<para>A portion of each UFS partition (8%, by default) is
reserved for use by the operating system and the
- <username>root</username> user. &man.df.1; does not count
+ <systemitem class="username">root</systemitem> user. &man.df.1; does not count
that space when calculating the <literal>Capacity</literal>
column, so it can exceed 100%. Also, you will notice that
the <literal>Blocks</literal> column is always greater than
@@ -3793,12 +3671,12 @@ C:\="DOS"</programlisting>
</qandaentry>
</qandaset>
- <sect1 id="all-about-zfs">
+ <sect1 xml:id="all-about-zfs">
<title>ZFS</title>
<qandaset>
<qandaentry>
- <question id="how-much-ram-for-zfs">
+ <question xml:id="how-much-ram-for-zfs">
<para>What is the minimum amount of RAM one should have to
run ZFS?</para>
</question>
@@ -3810,7 +3688,7 @@ C:\="DOS"</programlisting>
</qandaentry>
<qandaentry>
- <question id="what-is-zil">
+ <question xml:id="what-is-zil">
<para>What is the ZIL and when does it get used?</para>
</question>
@@ -3832,7 +3710,7 @@ C:\="DOS"</programlisting>
</qandaentry>
<qandaentry>
- <question id="need-ssd-for-zil">
+ <question xml:id="need-ssd-for-zil">
<para>Do I need a SSD for ZIL?</para>
</question>
@@ -3847,7 +3725,7 @@ C:\="DOS"</programlisting>
</qandaentry>
<qandaentry>
- <question id="what-is-l2arc">
+ <question xml:id="what-is-l2arc">
<para>What is the L2ARC?</para>
</question>
@@ -3869,7 +3747,7 @@ C:\="DOS"</programlisting>
</qandaentry>
<qandaentry>
- <question id="should-enable-dedup">
+ <question xml:id="should-enable-dedup">
<para>Is enabling deduplication advisable?</para>
</question>
@@ -3894,7 +3772,7 @@ C:\="DOS"</programlisting>
</qandaentry>
<qandaentry>
- <question id="zpool-fully-full">
+ <question xml:id="zpool-fully-full">
<para>I can not delete or create files on my ZFS pool.
How can I fix this?</para>
</question>
@@ -3906,7 +3784,7 @@ C:\="DOS"</programlisting>
to a usable state, truncate a file you want to
delete.</para>
- <screen>&prompt.user; <userinput>truncate -s 0 <replaceable>unimportant-file</replaceable></userinput></screen>
+ <screen>&prompt.user; <userinput>truncate -s 0 unimportant-file</userinput></screen>
<para>File truncation works because a new transaction is
not started, new spare blocks are created instead.</para>
@@ -3920,13 +3798,13 @@ C:\="DOS"</programlisting>
</qandaentry>
<qandaentry>
- <question id="zfs-ssd-trim">
+ <question xml:id="zfs-ssd-trim">
<para>Does ZFS support TRIM for Solid State Drives?</para>
</question>
<answer>
<para>ZFS TRIM support was added to &os;&nbsp;10-CURRENT
- with revision r<svnref>240868</svnref>. ZFS TRIM
+ with revision r<revnumber>240868</revnumber>. ZFS TRIM
support is not yet available on the -STABLE
branches.</para>
@@ -3947,12 +3825,12 @@ C:\="DOS"</programlisting>
</sect1>
</chapter>
- <chapter id="admin">
+ <chapter xml:id="admin">
<title>System Administration</title>
<qandaset>
<qandaentry>
- <question id="startup-config-files">
+ <question xml:id="startup-config-files">
<para>Where are the system start-up configuration
files?</para>
</question>
@@ -3961,8 +3839,8 @@ C:\="DOS"</programlisting>
<para>The primary configuration file is
<filename>/etc/defaults/rc.conf</filename> (see
&man.rc.conf.5;). System startup scripts such as
- <filename class="directory">/etc/rc</filename> and
- <filename class="directory">/etc/rc.d</filename> (see &man.rc.8;) just include
+ <filename>/etc/rc</filename> and
+ <filename>/etc/rc.d</filename> (see &man.rc.8;) just include
this file. <emphasis>Do not edit this file!</emphasis>
Instead, if there is any entry in
<filename>/etc/defaults/rc.conf</filename> that you want to
@@ -3976,14 +3854,14 @@ C:\="DOS"</programlisting>
<screen>&prompt.root; <userinput>echo 'named_enable="YES"' &gt;&gt; /etc/rc.conf</userinput></screen>
<para>To start up local services, place shell scripts in the
- <filename class="directory">/usr/local/etc/rc.d</filename> directory. These
+ <filename>/usr/local/etc/rc.d</filename> directory. These
shell scripts should be set executable, the default file
mode is <literal>555</literal>.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="adding-users">
+ <question xml:id="adding-users">
<para>How do I add a user easily?</para>
</question>
@@ -3997,7 +3875,7 @@ C:\="DOS"</programlisting>
</qandaentry>
<qandaentry>
- <question id="root-not-found-cron-errors">
+ <question xml:id="root-not-found-cron-errors">
<para>Why do I keep getting messages like <errorname>root: not
found</errorname> after editing
<filename>/etc/crontab</filename></para>
@@ -4028,7 +3906,7 @@ C:\="DOS"</programlisting>
<para>If you want something to be run once per day, week, or
month, it is probably better to add shell scripts
- <filename class="directory">/usr/local/etc/periodic</filename>, and let the
+ <filename>/usr/local/etc/periodic</filename>, and let the
&man.periodic.8; command run from the system
<command>cron</command> schedule it with the other periodic
system tasks.</para>
@@ -4036,8 +3914,8 @@ C:\="DOS"</programlisting>
<para>The actual reason for the error is that the system
crontab has an extra field, specifying which user to run the
command as. In the default system crontab provided with
- &os;, this is <username>root</username> for all entries.
- When this crontab is used as the <username>root</username>
+ &os;, this is <systemitem class="username">root</systemitem> for all entries.
+ When this crontab is used as the <systemitem class="username">root</systemitem>
user's crontab (which is <emphasis>not</emphasis> the same
as the system crontab), &man.cron.8; assumes the string
<literal>root</literal> is the first word of the command to
@@ -4046,39 +3924,39 @@ C:\="DOS"</programlisting>
</qandaentry>
<qandaentry>
- <question id="su-wheel-group">
+ <question xml:id="su-wheel-group">
<para>Why do I get the error, <errorname>you are not in the
correct group to su root</errorname> when I try to
- <command>su</command> to <username>root</username>?</para>
+ <command>su</command> to <systemitem class="username">root</systemitem>?</para>
</question>
<answer>
<para>This is a security feature. To
- <command>su</command> to <username>root</username> (or any
+ <command>su</command> to <systemitem class="username">root</systemitem> (or any
other account with superuser privileges), you must be in the
- <groupname>wheel</groupname> group. If this feature were
+ <systemitem class="groupname">wheel</systemitem> group. If this feature were
not there, anybody with an account on a system who also
- found out <username>root</username>'s password would be able
+ found out <systemitem class="username">root</systemitem>'s password would be able
to gain superuser level access to the system. With this
feature, this is not strictly true; &man.su.1; will prevent
them from even trying to enter the password if they are not
- in <groupname>wheel</groupname>.</para>
+ in <systemitem class="groupname">wheel</systemitem>.</para>
<para>To allow someone to <command>su</command> to
- <username>root</username>, simply put them in the
- <groupname>wheel</groupname> group. Use &man.pw.8;
+ <systemitem class="username">root</systemitem>, simply put them in the
+ <systemitem class="groupname">wheel</systemitem> group. Use &man.pw.8;
for this purpose.</para>
- <screen>&prompt.root; <userinput>pw groupmod wheel -m <replaceable>lisa</replaceable></userinput></screen>
+ <screen>&prompt.root; <userinput>pw groupmod wheel -m lisa</userinput></screen>
<para>The above example will add user
- <username>lisa</username> to the group
- <groupname>wheel</groupname>.</para>
+ <systemitem class="username">lisa</systemitem> to the group
+ <systemitem class="groupname">wheel</systemitem>.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="rcconf-readonly">
+ <question xml:id="rcconf-readonly">
<para>I made a mistake in <filename>rc.conf</filename>, or
another startup file, and now I cannot edit it because the
file system is read-only. What should I do?</para>
@@ -4115,13 +3993,12 @@ C:\="DOS"</programlisting>
</qandaentry>
<qandaentry>
- <question id="printer-setup">
+ <question xml:id="printer-setup">
<para>Why am I having trouble setting up my printer?</para>
</question>
<answer>
- <para>See the <ulink
- url="&url.books.handbook;/printing.html">Handbook entry on printing</ulink>.
+ <para>See the <link xlink:href="&url.books.handbook;/printing.html">Handbook entry on printing</link>.
It should cover most of your problem.</para>
<para>Some printers require a host-based driver to do any kind
@@ -4129,27 +4006,25 @@ C:\="DOS"</programlisting>
not natively supported by &os;. If your printer does not
work in DOS or &windows;, it is probably a WinPrinter. Your
only hope of getting one of these to work is to check if the
- <filename role="package">print/pnm2ppa</filename> port
+ <package>print/pnm2ppa</package> port
supports it.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="keyboard-mappings">
+ <question xml:id="keyboard-mappings">
<para>How can I correct the keyboard mappings for my
system?</para>
</question>
<answer>
- <para>Please see the Handbook section on <ulink
- url="&url.books.handbook;/using-localization.html">using localization</ulink>,
- specifically the section on <ulink
- url="&url.books.handbook;/using-localization.html#setting-console">console setup</ulink>.</para>
+ <para>Please see the Handbook section on <link xlink:href="&url.books.handbook;/using-localization.html">using localization</link>,
+ specifically the section on <link xlink:href="&url.books.handbook;/using-localization.html#setting-console">console setup</link>.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="user-quotas">
+ <question xml:id="user-quotas">
<para>Why can I not get user quotas to work properly?</para>
</question>
@@ -4163,14 +4038,13 @@ C:\="DOS"</programlisting>
<programlisting>options QUOTA</programlisting>
- <para>Please read the <ulink
- url="&url.books.handbook;/quotas.html">Handbook entry on quotas</ulink>
+ <para>Please read the <link xlink:href="&url.books.handbook;/quotas.html">Handbook entry on quotas</link>
for full details.</para>
</listitem>
<listitem>
<para>Do not turn on quotas on
- <filename class="directory">/</filename>.</para>
+ <filename>/</filename>.</para>
</listitem>
<listitem>
@@ -4189,13 +4063,13 @@ C:\="DOS"</programlisting>
<tbody>
<row>
- <entry><filename class="directory">/usr</filename></entry>
+ <entry><filename>/usr</filename></entry>
<entry><filename>/usr/admin/quotas</filename></entry>
</row>
<row>
- <entry><filename class="directory">/home</filename></entry>
+ <entry><filename>/home</filename></entry>
<entry><filename>/home/admin/quotas</filename></entry>
</row>
@@ -4214,7 +4088,7 @@ C:\="DOS"</programlisting>
</qandaentry>
<qandaentry>
- <question id="sysv-ipc">
+ <question xml:id="sysv-ipc">
<para>Does &os; support System V IPC primitives?</para>
</question>
@@ -4237,23 +4111,20 @@ options SYSVMSG # enable for messaging</programlisting>
</qandaentry>
<qandaentry>
- <question id="sendmail-alternative">
+ <question xml:id="sendmail-alternative">
<para>What other mail-server software can I use instead of
<application>sendmail</application>?</para>
</question>
<answer>
- <para>The <ulink
- url="http://www.sendmail.org/"><application>sendmail</application></ulink>
+ <para>The <link xlink:href="http://www.sendmail.org/"><application>sendmail</application></link>
server is the default mail-server software for &os;, but you
can easily replace it with one of the other MTA (for
instance, an MTA installed from the ports).</para>
<para>There are various alternative MTAs in the ports tree
- already, with <filename role="package">mail/exim</filename>,
- <filename role="package">mail/postfix</filename>, <filename
- role="package">mail/qmail</filename>, and <filename
- role="package">mail/zmailer</filename> being some of the
+ already, with <package>mail/exim</package>,
+ <package>mail/postfix</package>, <package>mail/qmail</package>, and <package>mail/zmailer</package> being some of the
most popular choices.</para>
<para>Diversity is nice, and the fact that you have many
@@ -4269,8 +4140,8 @@ options SYSVMSG # enable for messaging</programlisting>
</qandaentry>
<qandaentry>
- <question id="forgot-root-pw">
- <para>I have forgotten the <username>root</username> password!
+ <question xml:id="forgot-root-pw">
+ <para>I have forgotten the <systemitem class="username">root</systemitem> password!
What do I do?</para>
</question>
@@ -4284,12 +4155,12 @@ options SYSVMSG # enable for messaging</programlisting>
to remount your root file system read/write, then run
<command>mount -a</command> to remount all the file systems.
Run <command>passwd root</command> to change the
- <username>root</username> password then run &man.exit.1; to
+ <systemitem class="username">root</systemitem> password then run &man.exit.1; to
continue booting.</para>
<note>
<para>If you are still prompted to give the
- <username>root</username> password when entering the
+ <systemitem class="username">root</systemitem> password when entering the
Single User mode, it means that the console has been
marked as <literal>insecure</literal> in
<filename>/etc/ttys</filename>. In this case it will be
@@ -4309,16 +4180,14 @@ options SYSVMSG # enable for messaging</programlisting>
encrypted and it is impossible to mount them without the
access keys. Your chances depend on the chosen
implementation. For more information see the section
- about encrypted disks in the &os; <ulink
- url="&url.books.handbook;/disks-encrypting.html">Handbook</ulink>.</para>
+ about encrypted disks in the &os; <link xlink:href="&url.books.handbook;/disks-encrypting.html">Handbook</link>.</para>
</note>
</answer>
</qandaentry>
<qandaentry>
- <question id="CAD-reboot">
- <para>How do I keep <keycombo
- action="simul"><keycap>Control</keycap><keycap>Alt</keycap><keycap>Delete</keycap></keycombo>
+ <question xml:id="CAD-reboot">
+ <para>How do I keep <keycombo action="simul"><keycap>Control</keycap><keycap>Alt</keycap><keycap>Delete</keycap></keycombo>
from rebooting the system?</para>
</question>
@@ -4344,14 +4213,14 @@ options SYSVMSG # enable for messaging</programlisting>
</qandaentry>
<qandaentry>
- <question id="dos-to-unix-txt">
+ <question xml:id="dos-to-unix-txt">
<para>How do I reformat DOS text files to &unix; ones?</para>
</question>
<answer>
<para>Use this &man.perl.1; command:</para>
- <screen>&prompt.user; <userinput>perl -i.bak -npe 's/\r\n/\n/g' <replaceable>file(s)</replaceable></userinput></screen>
+ <screen>&prompt.user; <userinput>perl -i.bak -npe 's/\r\n/\n/g' file(s)</userinput></screen>
<para>where <replaceable>file(s)</replaceable> is one or more
files to process. The modification is done in-place, with the
@@ -4360,7 +4229,7 @@ options SYSVMSG # enable for messaging</programlisting>
<para>Alternatively you can use the &man.tr.1; command:</para>
- <screen>&prompt.user; <userinput>tr -d '\r' &lt; <replaceable>dos-text-file</replaceable> &gt; <replaceable>unix-file</replaceable></userinput></screen>
+ <screen>&prompt.user; <userinput>tr -d '\r' &lt; dos-text-file &gt; unix-file</userinput></screen>
<para><replaceable>dos-text-file</replaceable> is the file
containing DOS text while
@@ -4369,14 +4238,14 @@ options SYSVMSG # enable for messaging</programlisting>
<command>perl</command>.</para>
<para>Yet another way to reformat DOS text files is to use the
- <filename role="package">converters/dosunix</filename> port
+ <package>converters/dosunix</package> port
from the Ports Collection. Consult its documentation about
the details.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="kill-by-name">
+ <question xml:id="kill-by-name">
<para>How do I kill processes by name?</para>
</question>
@@ -4386,7 +4255,7 @@ options SYSVMSG # enable for messaging</programlisting>
</qandaentry>
<qandaentry>
- <question id="reread-rc">
+ <question xml:id="reread-rc">
<para>How do I re-read <filename>/etc/rc.conf</filename> and
re-start <filename>/etc/rc</filename> without a
reboot?</para>
@@ -4407,7 +4276,7 @@ options SYSVMSG # enable for messaging</programlisting>
</qandaentry>
<qandaentry>
- <question id="release-candidate">
+ <question xml:id="release-candidate">
<para>I tried to update my system to the latest
<emphasis>-STABLE</emphasis>, but got
<emphasis>-BETA<replaceable>x</replaceable></emphasis>,
@@ -4427,8 +4296,7 @@ options SYSVMSG # enable for messaging</programlisting>
<para>Long answer: &os; derives its releases from one of two
places. Major, dot-zero, releases, such as 9.0-RELEASE
are branched from the head of the development
- stream, commonly referred to as <link
- linkend="current">-CURRENT</link>. Minor releases, such as
+ stream, commonly referred to as <link linkend="current">-CURRENT</link>. Minor releases, such as
6.3-RELEASE or 5.2-RELEASE, have been snapshots of the
active <link linkend="stable">-STABLE</link> branch.
Starting with 4.3-RELEASE, each release also now has its own
@@ -4454,14 +4322,13 @@ options SYSVMSG # enable for messaging</programlisting>
6.3-STABLE.</para>
<para>For more information on version numbers and the various
- Subversion branches, refer to the <ulink
- url="&url.articles.releng;/article.html">Release Engineering</ulink>
+ Subversion branches, refer to the <link xlink:href="&url.articles.releng;/article.html">Release Engineering</link>
article.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="kernel-chflag-failure">
+ <question xml:id="kernel-chflag-failure">
<para>I tried to install a new kernel, and the &man.chflags.1;
failed. How do I get around this?</para>
</question>
@@ -4489,7 +4356,7 @@ options SYSVMSG # enable for messaging</programlisting>
</qandaentry>
<qandaentry>
- <question id="kernel-securelevel-time">
+ <question xml:id="kernel-securelevel-time">
<para>I cannot change the time on my system by more than one
second! How do I get around this?</para>
</question>
@@ -4517,7 +4384,7 @@ options SYSVMSG # enable for messaging</programlisting>
</qandaentry>
<qandaentry>
- <question id="statd-mem-leak">
+ <question xml:id="statd-mem-leak">
<para>Why is <command>rpc.statd</command> using 256&nbsp;MB of
memory?</para>
</question>
@@ -4531,7 +4398,7 @@ options SYSVMSG # enable for messaging</programlisting>
off things like &man.top.1; and &man.ps.1;.</para>
<para>&man.rpc.statd.8; maps its status file (resident on
- <filename class="directory">/var</filename>) into its address space; to save
+ <filename>/var</filename>) into its address space; to save
worrying about remapping it later when it needs to grow, it
maps it with a generous size. This is very evident from the
source code, where one can see that the length argument to
@@ -4542,7 +4409,7 @@ options SYSVMSG # enable for messaging</programlisting>
</qandaentry>
<qandaentry>
- <question id="unsetting-schg">
+ <question xml:id="unsetting-schg">
<para>Why can I not unset the <literal>schg</literal> file
flag?</para>
</question>
@@ -4557,7 +4424,7 @@ options SYSVMSG # enable for messaging</programlisting>
</qandaentry>
<qandaentry>
- <question id="ssh-shosts">
+ <question xml:id="ssh-shosts">
<para>Why does <application>SSH</application> authentication
through <filename>.shosts</filename> not work by default in
recent versions of &os;?</para>
@@ -4567,14 +4434,14 @@ options SYSVMSG # enable for messaging</programlisting>
<para>The reason why <filename>.shosts</filename>
authentication does not work by default in more recent
versions of &os; is because &man.ssh.1; is not installed
- suid <username>root</username> by default. To
+ suid <systemitem class="username">root</systemitem> by default. To
<quote>fix</quote> this, you can do one of the
following:</para>
<itemizedlist>
<listitem>
<para>As a permanent fix, set
- <makevar>ENABLE_SUID_SSH</makevar> to
+ <varname>ENABLE_SUID_SSH</varname> to
<literal>true</literal> in
<filename>/etc/make.conf</filename> then rebuild and
reinstall &man.ssh.1;.</para>
@@ -4585,14 +4452,14 @@ options SYSVMSG # enable for messaging</programlisting>
<filename>/usr/bin/ssh</filename> to
<literal>4555</literal> by running
<command>chmod 4555 /usr/bin/ssh</command> as
- <username>root</username>.</para>
+ <systemitem class="username">root</systemitem>.</para>
</listitem>
</itemizedlist>
</answer>
</qandaentry>
<qandaentry>
- <question id="vnlru">
+ <question xml:id="vnlru">
<para>What is <literal>vnlru</literal>?</para>
</question>
@@ -4606,7 +4473,7 @@ options SYSVMSG # enable for messaging</programlisting>
</qandaentry>
<qandaentry>
- <question id="top-memory-states">
+ <question xml:id="top-memory-states">
<para>What do the various memory states displayed by
<command>top</command> mean?</para>
</question>
@@ -4674,7 +4541,7 @@ options SYSVMSG # enable for messaging</programlisting>
</qandaentry>
<qandaentry>
- <question id="free-memory-amount">
+ <question xml:id="free-memory-amount">
<para>How much free memory is available?</para>
</question>
@@ -4697,16 +4564,16 @@ options SYSVMSG # enable for messaging</programlisting>
</qandaentry>
<qandaentry>
- <question id="var-empty">
- <para>What is <filename class="directory">/var/empty</filename>? I can not
+ <question xml:id="var-empty">
+ <para>What is <filename>/var/empty</filename>? I can not
delete it!</para>
</question>
<answer>
- <para><filename class="directory">/var/empty</filename> is a directory that the
+ <para><filename>/var/empty</filename> is a directory that the
&man.sshd.8; program uses when performing privilege separation.
- The <filename class="directory">/var/empty</filename> directory is empty, owned by
- <username>root</username> and has the <literal>schg</literal>
+ The <filename>/var/empty</filename> directory is empty, owned by
+ <systemitem class="username">root</systemitem> and has the <literal>schg</literal>
flag set.</para>
<para>Although it is not recommended to delete this directory, to
@@ -4718,7 +4585,7 @@ options SYSVMSG # enable for messaging</programlisting>
</qandaentry>
<qandaentry>
- <question id="newsyslog-expectations">
+ <question xml:id="newsyslog-expectations">
<para>I just changed
<filename>/etc/newsyslog.conf</filename>. How can I check
if it does what I expect?</para>
@@ -4733,7 +4600,7 @@ options SYSVMSG # enable for messaging</programlisting>
</qandaentry>
<qandaentry>
- <question id="timezone">
+ <question xml:id="timezone">
<para>My time is wrong, how can I change the
timezone?</para>
</question>
@@ -4745,12 +4612,12 @@ options SYSVMSG # enable for messaging</programlisting>
</qandaset>
</chapter>
- <chapter id="x">
+ <chapter xml:id="x">
<title>The X Window System and Virtual Consoles</title>
<qandaset>
<qandaentry>
- <question id="whatis-X">
+ <question xml:id="whatis-X">
<para>What is the X Window System?</para>
</question>
@@ -4758,9 +4625,8 @@ options SYSVMSG # enable for messaging</programlisting>
<para>The X Window System (commonly <literal>X11</literal>) is
the most widely available windowing system capable of running
on &unix; or &unix;&nbsp;like systems, including &os;.
- <ulink url= "http://www.x.org/wiki/">The X.Org Foundation</ulink>
- administers the <ulink
- url="http://en.wikipedia.org/wiki/X_Window_System_core_protocol">X protocol standards</ulink>,
+ <link xlink:href="http://www.x.org/wiki/">The X.Org Foundation</link>
+ administers the <link xlink:href="http://en.wikipedia.org/wiki/X_Window_System_core_protocol">X protocol standards</link>,
with the current reference implementation, version 11
release &xorg.version;, so you will often see references
shortened to <literal>X11</literal>.</para>
@@ -4773,19 +4639,18 @@ options SYSVMSG # enable for messaging</programlisting>
</qandaentry>
<qandaentry>
- <question id="running-X">
+ <question xml:id="running-X">
<para>I want to run &xorg;, how do I go about it?</para>
</question>
<answer>
<para>To install &xorg; do one of the following:</para>
- <para>Use the <filename role="package">x11/xorg</filename>
+ <para>Use the <package>x11/xorg</package>
meta-port, which builds and installs every &xorg;
component.</para>
- <para>Use <filename
- role="package">x11/xorg-minimal</filename>, which builds
+ <para>Use <package>x11/xorg-minimal</package>, which builds
and installs only the necessary &xorg; components.</para>
<para>Install &xorg; from &os; packages:</para>
@@ -4797,14 +4662,13 @@ options SYSVMSG # enable for messaging</programlisting>
<screen><userinput>&prompt.root; pkg install xorg</userinput></screen>
<para>After the installation of &xorg;, follow
- the instructions from the <ulink
- url="&url.books.handbook;/x-config.html">X11 Configuration</ulink> section of
+ the instructions from the <link xlink:href="&url.books.handbook;/x-config.html">X11 Configuration</link> section of
the &os; Handbook.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="running-X-securelevels">
+ <question xml:id="running-X-securelevels">
<para>I <emphasis>tried</emphasis> to run X, but I get a
<errorname>No devices detected.</errorname> error when I
type
@@ -4832,7 +4696,7 @@ options SYSVMSG # enable for messaging</programlisting>
</qandaentry>
<qandaentry>
- <question id="x-and-moused">
+ <question xml:id="x-and-moused">
<para>Why does my mouse not work with X?</para>
</question>
@@ -4841,12 +4705,11 @@ options SYSVMSG # enable for messaging</programlisting>
driver), you can configure &os; to support a mouse pointer on
each virtual screen. To avoid conflicting with X,
&man.syscons.4; supports a virtual device called
- <devicename>/dev/sysmouse</devicename>. All mouse events
+ <filename>/dev/sysmouse</filename>. All mouse events
received from the real mouse device are written to the
&man.sysmouse.4; device via &man.moused.8;. 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
+ <emphasis>and</emphasis> use X, see <xref linkend="moused" remap="another section"/> and set up
&man.moused.8;.</para>
<para>Then edit <filename>/etc/X11/xorg.conf</filename> and
@@ -4867,9 +4730,9 @@ options SYSVMSG # enable for messaging</programlisting>
<programlisting>Option "AutoAddDevices" "false"</programlisting>
<para>Some people prefer to use
- <devicename>/dev/mouse</devicename> under X. To make this
- work, <devicename>/dev/mouse</devicename> should be linked
- to <devicename>/dev/sysmouse</devicename> (see
+ <filename>/dev/mouse</filename> under X. To make this
+ work, <filename>/dev/mouse</filename> should be linked
+ to <filename>/dev/sysmouse</filename> (see
&man.sysmouse.4;) by adding the following line to
<filename>/etc/devfs.conf</filename> (see
&man.devfs.conf.5;):</para>
@@ -4878,14 +4741,14 @@ options SYSVMSG # enable for messaging</programlisting>
<para>This link can be created by restarting &man.devfs.5;
with the following command (as
- <username>root</username>):</para>
+ <systemitem class="username">root</systemitem>):</para>
<screen>&prompt.root; <userinput>service devfs restart</userinput></screen>
</answer>
</qandaentry>
<qandaentry>
- <question id="x-and-wheel">
+ <question xml:id="x-and-wheel">
<para>My mouse has a fancy wheel. Can I use it in X?</para>
</question>
@@ -4926,7 +4789,7 @@ EndSection</programlisting>
</qandaentry>
<qandaentry>
- <question id="x-and-synaptic">
+ <question xml:id="x-and-synaptic">
<para>My laptop has a Synaptics touchpad. Can I use
it in X?</para>
</question>
@@ -4965,7 +4828,7 @@ EndSection</programlisting>
</qandaentry>
<qandaentry>
- <question id="no-remote-x11">
+ <question xml:id="no-remote-x11">
<para>How do I use remote X displays?</para>
</question>
@@ -4982,7 +4845,7 @@ EndSection</programlisting>
</qandaentry>
<qandaentry>
- <question id="virtual-console">
+ <question xml:id="virtual-console">
<para>What is a virtual console and how do I make more?</para>
</question>
@@ -5000,28 +4863,23 @@ EndSection</programlisting>
<para>At some point, you will probably wish to start another
session, perhaps to look at documentation for a program you
are running or to read your mail while waiting for an FTP
- transfer to finish. Just do <keycombo
- action="simul"><keycap>Alt</keycap><keycap>F2</keycap></keycombo>
+ transfer to finish. Just do <keycombo action="simul"><keycap>Alt</keycap><keycap>F2</keycap></keycombo>
(hold down <keycap>Alt</keycap> and press
<keycap>F2</keycap>), and you will find a login prompt
waiting for you on the second <quote>virtual
console</quote>! When you want to go back to the original
- session, do <keycombo
- action="simul"><keycap>Alt</keycap><keycap>F1</keycap></keycombo>.</para>
+ session, do <keycombo action="simul"><keycap>Alt</keycap><keycap>F1</keycap></keycombo>.</para>
<para>The default &os; installation has eight virtual consoles
- enabled. <keycombo
- action="simul"><keycap>Alt</keycap><keycap>F1</keycap></keycombo>,
- <keycombo
- action="simul"><keycap>Alt</keycap><keycap>F2</keycap></keycombo>,
- <keycombo
- action="simul"><keycap>Alt</keycap><keycap>F3</keycap></keycombo>,
+ enabled. <keycombo action="simul"><keycap>Alt</keycap><keycap>F1</keycap></keycombo>,
+ <keycombo action="simul"><keycap>Alt</keycap><keycap>F2</keycap></keycombo>,
+ <keycombo action="simul"><keycap>Alt</keycap><keycap>F3</keycap></keycombo>,
and so on will switch between these virtual consoles.</para>
<para>To enable more of them, edit
<filename>/etc/ttys</filename> (see &man.ttys.5;) and add
- entries for <devicename>ttyv8</devicename> to
- <devicename>ttyvc</devicename> after the comment on
+ entries for <filename>ttyv8</filename> to
+ <filename>ttyvc</filename> after the comment on
<quote>Virtual terminals</quote>:</para>
<programlisting># Edit the existing entry for ttyv8 in /etc/ttys and change
@@ -5078,7 +4936,7 @@ ttyvb "/usr/libexec/getty Pc" xterm off secure</programlisting>
<para>Next, the easiest (and cleanest) way to activate the
virtual consoles is to reboot. However, if you really do
not want to reboot, you can just shut down the X Window
- system and execute (as <username>root</username>):</para>
+ system and execute (as <systemitem class="username">root</systemitem>):</para>
<screen>&prompt.root; <userinput>kill -HUP 1</userinput></screen>
@@ -5090,20 +4948,17 @@ ttyvb "/usr/libexec/getty Pc" xterm off secure</programlisting>
</qandaentry>
<qandaentry>
- <question id="vty-from-x">
+ <question xml:id="vty-from-x">
<para>How do I access the virtual consoles from X?</para>
</question>
<answer>
- <para>Use <keycombo
- action="simul"><keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>F<replaceable>n</replaceable></keycap></keycombo>
- to switch back to a virtual console. <keycombo
- action="simul"><keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>F1</keycap></keycombo>
+ <para>Use <keycombo action="simul"><keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>F<replaceable>n</replaceable></keycap></keycombo>
+ to switch back to a virtual console. <keycombo action="simul"><keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>F1</keycap></keycombo>
would return you to the first virtual console.</para>
<para>Once you are back to a text console, you can then use
- <keycombo
- action="simul"><keycap>Alt</keycap><keycap>F<replaceable>n</replaceable></keycap></keycombo>
+ <keycombo action="simul"><keycap>Alt</keycap><keycap>F<replaceable>n</replaceable></keycap></keycombo>
as normal to move between them.</para>
<para>To return to the X session, you must switch to the
@@ -5112,14 +4967,13 @@ ttyvb "/usr/libexec/getty Pc" xterm off secure</programlisting>
the X session will attach to the next unused virtual
console, not the text console from which it was invoked. If
you have eight active virtual terminals then X will be
- running on the ninth, and you would use <keycombo
- action="simul"><keycap>Alt</keycap><keycap>F9</keycap></keycombo>
+ running on the ninth, and you would use <keycombo action="simul"><keycap>Alt</keycap><keycap>F9</keycap></keycombo>
to return.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="xdm-boot">
+ <question xml:id="xdm-boot">
<para>How do I start <application>XDM</application> on
boot?</para>
</question>
@@ -5132,7 +4986,7 @@ ttyvb "/usr/libexec/getty Pc" xterm off secure</programlisting>
<command>xdm</command> from
<filename>rc.local</filename> (see &man.rc.8;) or from an
<filename>X</filename> script in
- <filename class="directory">/usr/local/etc/rc.d</filename>. Both are equally
+ <filename>/usr/local/etc/rc.d</filename>. Both are equally
valid, and one may work in situations where the other does
not. In both cases the result is the same: X will pop up a
graphical login prompt.</para>
@@ -5163,14 +5017,14 @@ ttyvb "/usr/libexec/getty Pc" xterm off secure</programlisting>
<programlisting>:0 local /usr/local/bin/X vt4</programlisting>
<para>The above example will direct the X server to run in
- <devicename>/dev/ttyv3</devicename>. Note the number is
+ <filename>/dev/ttyv3</filename>. Note the number is
offset by one. The X server counts the vty from one,
whereas the &os; kernel numbers the vty from zero.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="xconsole-failure">
+ <question xml:id="xconsole-failure">
<para>Why do I get <errorname>Couldn't open
console</errorname> when I run
<command>xconsole</command>?</para>
@@ -5179,7 +5033,7 @@ ttyvb "/usr/libexec/getty Pc" xterm off secure</programlisting>
<answer>
<para>If you start <application>X</application> with
<command>startx</command>, the permissions on
- <devicename>/dev/console</devicename> will
+ <filename>/dev/console</filename> will
<emphasis>not</emphasis> get changed, resulting in things
like <command>xterm -C</command> and
<command>xconsole</command> not working.</para>
@@ -5198,13 +5052,13 @@ ttyvb "/usr/libexec/getty Pc" xterm off secure</programlisting>
<programlisting>/dev/ttyv0 0600 /dev/console</programlisting>
<para>It will ensure that whomever logs in on
- <devicename>/dev/ttyv0</devicename> will own the
+ <filename>/dev/ttyv0</filename> will own the
console.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="ps2-x">
+ <question xml:id="ps2-x">
<para>Why does my PS/2 mouse misbehave under X?</para>
</question>
@@ -5234,7 +5088,7 @@ ttyvb "/usr/libexec/getty Pc" xterm off secure</programlisting>
</qandaentry>
<qandaentry>
- <question id="mouse-button-reverse">
+ <question xml:id="mouse-button-reverse">
<para>How do I reverse the mouse buttons?</para>
</question>
@@ -5249,21 +5103,20 @@ ttyvb "/usr/libexec/getty Pc" xterm off secure</programlisting>
</qandaentry>
<qandaentry>
- <question id="install-splash">
+ <question xml:id="install-splash">
<para>How do I install a splash screen and where do I find
them?</para>
</question>
<answer>
<para>The detailed answer for this question can be found in
- the <ulink
- url="&url.books.handbook;/boot-blocks.html#boot-splash">Boot Time Splash Screens</ulink>
+ the <link xlink:href="&url.books.handbook;/boot-blocks.html#boot-splash">Boot Time Splash Screens</link>
section of the &os; Handbook.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="windows-keys">
+ <question xml:id="windows-keys">
<para>Can I use the <keycap>Windows</keycap> keys on my
keyboard in X?</para>
</question>
@@ -5325,8 +5178,7 @@ ttyvb "/usr/libexec/getty Pc" xterm off secure</programlisting>
keycode 116 = F14
keycode 117 = F15</programlisting>
- <para>If you use the <filename
- role="package">x11-wm/fvwm2</filename> port, for example,
+ <para>If you use the <package>x11-wm/fvwm2</package> port, for example,
you could map the keys so that <keycap>F13</keycap>
iconifies (or de-iconifies) the window the cursor is in,
<keycap>F14</keycap> brings the window the cursor is in to
@@ -5347,7 +5199,7 @@ Key F15 A A Menu Workplace Nop</programlisting>
</qandaentry>
<qandaentry>
- <question id="x-3d-acceleration">
+ <question xml:id="x-3d-acceleration">
<para>How can I get 3D hardware acceleration for
&opengl;?</para>
</question>
@@ -5362,34 +5214,31 @@ Key F15 A A Menu Workplace Nop</programlisting>
<itemizedlist>
<listitem>
<para>The latest versions of nVidia cards are supported by
- the <filename role="package">x11/nvidia-driver</filename>
+ the <package>x11/nvidia-driver</package>
port.</para>
</listitem>
<listitem>
<para>nVidia cards like the GeForce2&nbsp;MX/3/4 series
are supported by the 96XX series of drivers, available
- in the <filename
- role="package">x11/nvidia-driver-96xx</filename>
+ in the <package>x11/nvidia-driver-96xx</package>
port.</para>
</listitem>
<listitem>
<para>Even older cards, like GeForce and RIVA&nbsp;TNT are
supported by the 71XX series of drivers, available in
- the <filename
- role="package">x11/nvidia-driver-71xx</filename>
+ the <package>x11/nvidia-driver-71xx</package>
port.</para>
</listitem>
</itemizedlist>
<para>nVidia provides detailed information on which
card is supported by which driver
- on their web site: <ulink
- url="http://www.nvidia.com/object/IO_32667.html"></ulink>.</para>
+ on their web site: <uri xlink:href="http://www.nvidia.com/object/IO_32667.html">http://www.nvidia.com/object/IO_32667.html</uri>.</para>
<para>For Matrox&nbsp;G200/G400, check the
- <filename role="package">x11-servers/mga_hal</filename>
+ <package>x11-servers/mga_hal</package>
port.</para>
<para>For ATI&nbsp;Rage&nbsp;128 and Radeon see
@@ -5399,12 +5248,12 @@ Key F15 A A Menu Workplace Nop</programlisting>
</qandaset>
</chapter>
- <chapter id="networking">
+ <chapter xml:id="networking">
<title>Networking</title>
<qandaset>
<qandaentry>
- <question id="diskless-booting">
+ <question xml:id="diskless-booting">
<para>Where can I get information on <quote>diskless
booting</quote>?</para>
</question>
@@ -5413,27 +5262,24 @@ Key F15 A A Menu Workplace Nop</programlisting>
<para><quote>Diskless booting</quote> means that the &os;
box is booted over a network, and reads the necessary
files from a server instead of its hard disk. For full
- details, please read <ulink
- url="&url.books.handbook;/network-diskless.html">the Handbook entry on diskless booting</ulink>.</para>
+ details, please read <link xlink:href="&url.books.handbook;/network-diskless.html">the Handbook entry on diskless booting</link>.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="router">
+ <question xml:id="router">
<para>Can a &os; box be used as a dedicated network
router?</para>
</question>
<answer>
- <para>Yes. Please see the Handbook entry on <ulink
- url="&url.books.handbook;/advanced-networking.html">advanced networking</ulink>,
- specifically the section on <ulink
- url="&url.books.handbook;/network-routing.html">routing and gateways</ulink>.</para>
+ <para>Yes. Please see the Handbook entry on <link xlink:href="&url.books.handbook;/advanced-networking.html">advanced networking</link>,
+ specifically the section on <link xlink:href="&url.books.handbook;/network-routing.html">routing and gateways</link>.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="win95-connection">
+ <question xml:id="win95-connection">
<para>Can I connect my &windows; box to the Internet via
&os;?</para>
</question>
@@ -5454,19 +5300,17 @@ Key F15 A A Menu Workplace Nop</programlisting>
<filename>/etc/rc.conf</filename>.
For
more information, please see the &man.ppp.8; manual page or
- the <ulink
- url="&url.books.handbook;/userppp.html">Handbook entry on user PPP</ulink>.</para>
+ the <link xlink:href="&url.books.handbook;/userppp.html">Handbook entry on user PPP</link>.</para>
<para>If you are using kernel-mode PPP or have an Ethernet
connection to the Internet, you need to use &man.natd.8;.
- Please look at the <ulink
- url="&url.books.handbook;/network-natd.html">natd</ulink>
+ Please look at the <link xlink:href="&url.books.handbook;/network-natd.html">natd</link>
section of the Handbook for a tutorial.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="slip-ppp-support">
+ <question xml:id="slip-ppp-support">
<para>Does &os; support PPP?</para>
</question>
@@ -5475,29 +5319,26 @@ Key F15 A A Menu Workplace Nop</programlisting>
incoming and outgoing connections.</para>
<para>For more information on how to use this, please see the
- <ulink
- url="&url.books.handbook;/ppp-and-slip.html">Handbook chapter on PPP</ulink>.</para>
+ <link xlink:href="&url.books.handbook;/ppp-and-slip.html">Handbook chapter on PPP</link>.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="natd">
+ <question xml:id="natd">
<para>Does &os; support NAT or Masquerading?</para>
</question>
<answer>
<para>Yes. If you want to use NAT over a user PPP connection,
- please see the <ulink
- url="&url.books.handbook;/userppp.html">Handbook entry on user PPP</ulink>.
+ please see the <link xlink:href="&url.books.handbook;/userppp.html">Handbook entry on user PPP</link>.
If you want to use NAT over some other sort of network
- connection, please look at the <ulink
- url="&url.books.handbook;/network-natd.html">natd</ulink>
+ connection, please look at the <link xlink:href="&url.books.handbook;/network-natd.html">natd</link>
section of the Handbook.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="ethernet-aliases">
+ <question xml:id="ethernet-aliases">
<para>How can I set up Ethernet aliases?</para>
</question>
@@ -5507,20 +5348,19 @@ Key F15 A A Menu Workplace Nop</programlisting>
0xffffffff</literal> to your &man.ifconfig.8; command-line,
as in the following:</para>
- <screen>&prompt.root; <userinput>ifconfig <replaceable>ed0</replaceable> alias <replaceable>192.0.2.2</replaceable> netmask 0xffffffff</userinput></screen>
+ <screen>&prompt.root; <userinput>ifconfig ed0 alias 192.0.2.2 netmask 0xffffffff</userinput></screen>
<para>Otherwise, just specify the network address and netmask
as usual:</para>
- <screen>&prompt.root; <userinput>ifconfig <replaceable>ed0</replaceable> alias <replaceable>172.16.141.5</replaceable> netmask 0xffffff00</userinput></screen>
+ <screen>&prompt.root; <userinput>ifconfig ed0 alias 172.16.141.5 netmask 0xffffff00</userinput></screen>
- <para>You can read more about this in the &os; <ulink
- url="&url.books.handbook;/configtuning-virtual-hosts.html">Handbook</ulink>.</para>
+ <para>You can read more about this in the &os; <link xlink:href="&url.books.handbook;/configtuning-virtual-hosts.html">Handbook</link>.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="nfs-linux">
+ <question xml:id="nfs-linux">
<para>Why can I not NFS-mount from a &linux; box?</para>
</question>
@@ -5529,12 +5369,12 @@ Key F15 A A Menu Workplace Nop</programlisting>
requests from a privileged port; try to issue the following
command:</para>
- <screen>&prompt.root; <userinput>mount -o -P <replaceable>linuxbox:/blah</replaceable> <replaceable>/mnt</replaceable></userinput></screen>
+ <screen>&prompt.root; <userinput>mount -o -P linuxbox:/blah /mnt</userinput></screen>
</answer>
</qandaentry>
<qandaentry>
- <question id="exports-errors">
+ <question xml:id="exports-errors">
<para>Why does <command>mountd</command> keep telling me it
<errorname>can't change attributes</errorname> and that I
have a <errorname>bad exports list</errorname> on my &os;
@@ -5544,15 +5384,13 @@ Key F15 A A Menu Workplace Nop</programlisting>
<answer>
<para>The most frequent problem is not understanding the
correct format of <filename>/etc/exports</filename>. Please
- review &man.exports.5; and the <ulink
- url="&url.books.handbook;/network-nfs.html">NFS</ulink>
- entry in the Handbook, especially the section on <ulink
- url="&url.books.handbook;/network-nfs.html#configuring-nfs">configuring NFS</ulink>.</para>
+ review &man.exports.5; and the <link xlink:href="&url.books.handbook;/network-nfs.html">NFS</link>
+ entry in the Handbook, especially the section on <link xlink:href="&url.books.handbook;/network-nfs.html#configuring-nfs">configuring NFS</link>.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="ip-multicast">
+ <question xml:id="ip-multicast">
<para>How do I enable IP multicast support?</para>
</question>
@@ -5571,25 +5409,24 @@ Key F15 A A Menu Workplace Nop</programlisting>
routing daemon, the &man.map-mbone.8; and &man.mrinfo.8;
utilities have been removed from the base system. These
programs are now available in the &os; Ports Collection as
- <filename role="package">net/mrouted</filename>.</para>
+ <package>net/mrouted</package>.</para>
</note>
</answer>
</qandaentry>
<qandaentry>
- <question id="fqdn-hosts">
+ <question xml:id="fqdn-hosts">
<para>Why do I have to use the FQDN for hosts on my
site?</para>
</question>
<answer>
- <para>See the answer in the &os; <ulink
- url="&url.books.handbook;/mail-trouble.html">Handbook</ulink>.</para>
+ <para>See the answer in the &os; <link xlink:href="&url.books.handbook;/mail-trouble.html">Handbook</link>.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="network-permission-denied">
+ <question xml:id="network-permission-denied">
<para>Why do I get an error, <errorname>Permission
denied</errorname>, for all networking operations?</para>
</question>
@@ -5603,7 +5440,7 @@ Key F15 A A Menu Workplace Nop</programlisting>
<para>If you had unintentionally misconfigured your system for
firewalling, you can restore network operability by typing
the following while logged in as
- <username>root</username>:</para>
+ <systemitem class="username">root</systemitem>:</para>
<screen>&prompt.root; <userinput>ipfw add 65534 allow all from any to any</userinput></screen>
@@ -5611,13 +5448,12 @@ Key F15 A A Menu Workplace Nop</programlisting>
in <filename>/etc/rc.conf</filename>.</para>
<para>For further information on configuring a &os; firewall,
- see the <ulink
- url="&url.books.handbook;/firewalls.html">Handbook chapter</ulink>.</para>
+ see the <link xlink:href="&url.books.handbook;/firewalls.html">Handbook chapter</link>.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="ipfw-fwd">
+ <question xml:id="ipfw-fwd">
<para>Why is my <command>ipfw</command> <quote>fwd</quote>
rule to redirect a service to another machine not
working?</para>
@@ -5645,24 +5481,22 @@ Key F15 A A Menu Workplace Nop</programlisting>
<quote>fwd</quote> rule does not often work the way the user
expects. This behavior is a feature and not a bug.</para>
- <para>See the <link
- linkend="service-redirect">FAQ about redirecting services</link>,
+ <para>See the <link linkend="service-redirect">FAQ about redirecting services</link>,
the &man.natd.8; manual, or one of the several port
- redirecting utilities in the <ulink
- url="&url.base;/ports/index.html">Ports Collection</ulink>
+ redirecting utilities in the <link xlink:href="&url.base;/ports/index.html">Ports Collection</link>
for a correct way to do this.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="service-redirect">
+ <question xml:id="service-redirect">
<para>How can I redirect service requests from one machine to
another?</para>
</question>
<answer>
<para>You can redirect FTP (and other service) request with
- the <filename role="package">sysutils/socket</filename>
+ the <package>sysutils/socket</package>
port. Simply replace the service's command line to call
<command>socket</command> instead, like so:</para>
@@ -5675,24 +5509,22 @@ Key F15 A A Menu Workplace Nop</programlisting>
</qandaentry>
<qandaentry>
- <question id="bandwidth-mgr-tool">
+ <question xml:id="bandwidth-mgr-tool">
<para>Where can I get a bandwidth management tool?</para>
</question>
<answer>
<para>There are three bandwidth management tools available for
&os;. &man.dummynet.4; is integrated into &os; as part of
- &man.ipfw.4;. <ulink
- url="http://www.sonycsl.co.jp/person/kjc/programs.html">ALTQ</ulink>
+ &man.ipfw.4;. <link xlink:href="http://www.sonycsl.co.jp/person/kjc/programs.html">ALTQ</link>
has been integrated into &os; as part of &man.pf.4;.
- Bandwidth Manager from <ulink
- url="http://www.etinc.com/">Emerging Technologies</ulink>
+ Bandwidth Manager from <link xlink:href="http://www.etinc.com/">Emerging Technologies</link>
is a commercial product.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="bpf-not-configured">
+ <question xml:id="bpf-not-configured">
<para>Why do I get <errorname>/dev/bpf0: device not
configured</errorname>?</para>
</question>
@@ -5708,7 +5540,7 @@ Key F15 A A Menu Workplace Nop</programlisting>
</qandaentry>
<qandaentry>
- <question id="mount-smb-share">
+ <question xml:id="mount-smb-share">
<para>How do I mount a disk from a &windows; machine that is
on my network, like smbmount in &linux;?</para>
</question>
@@ -5722,7 +5554,7 @@ Key F15 A A Menu Workplace Nop</programlisting>
</qandaentry>
<qandaentry>
- <question id="icmp-response-bw-limit">
+ <question xml:id="icmp-response-bw-limit">
<para>What are these messages about: <errorname>Limiting
icmp/open port/closed port response</errorname> in my log
files?</para>
@@ -5779,7 +5611,7 @@ Key F15 A A Menu Workplace Nop</programlisting>
</qandaentry>
<qandaentry>
- <question id="unknown-hw-addr-format">
+ <question xml:id="unknown-hw-addr-format">
<para>What are these <errorname>arp: unknown hardware address
format</errorname> error messages?</para>
</question>
@@ -5796,7 +5628,7 @@ Key F15 A A Menu Workplace Nop</programlisting>
</qandaentry>
<qandaentry>
- <question id="arp-wrong-iface">
+ <question xml:id="arp-wrong-iface">
<para>Why do I keep seeing messages like: <errorname>192.168.0.10 is on
fxp1 but got reply from 00:15:17:67:cf:82 on rl0</errorname>, and how do I
disable it?</para>
@@ -5812,12 +5644,12 @@ Key F15 A A Menu Workplace Nop</programlisting>
</qandaset>
</chapter>
- <chapter id="security">
+ <chapter xml:id="security">
<title>Security</title>
<qandaset>
<qandaentry>
- <question id="sandbox">
+ <question xml:id="sandbox">
<para>What is a sandbox?</para>
</question>
<answer>
@@ -5844,9 +5676,9 @@ Key F15 A A Menu Workplace Nop</programlisting>
<para>Take the <literal>ntalk</literal> service, for
example (see &man.inetd.8;). This service used to run
- as user&nbsp;ID <username>root</username>. Now it runs
- as user&nbsp;ID <username>tty</username>. The
- <username>tty</username> user is a sandbox designed to
+ as user&nbsp;ID <systemitem class="username">root</systemitem>. Now it runs
+ as user&nbsp;ID <systemitem class="username">tty</systemitem>. The
+ <systemitem class="username">tty</systemitem> user is a sandbox designed to
make it more difficult for someone who has successfully
hacked into the system via <literal>ntalk</literal> from
being able to hack beyond that user&nbsp;ID.</para>
@@ -5862,10 +5694,8 @@ Key F15 A A Menu Workplace Nop</programlisting>
<para>The most common way to accomplish this is to build a
simulated environment in a subdirectory and then run the
- processes in that directory chrooted (i.e., <filename
- class="directory">/</filename> for that process is this
- directory, not the real <filename
- class="directory">/</filename> of the system).</para>
+ processes in that directory chrooted (i.e., <filename>/</filename> for that process is this
+ directory, not the real <filename>/</filename> of the system).</para>
<para>Another common use is to mount an underlying file
system read-only and then create a file system layer on
@@ -5889,7 +5719,7 @@ Key F15 A A Menu Workplace Nop</programlisting>
address space of another.</para>
<para>A &unix; process is owned by a particular userid. If
- the user&nbsp;ID is not the <username>root</username> user,
+ the user&nbsp;ID is not the <systemitem class="username">root</systemitem> user,
it serves to firewall the process off from processes owned
by other users. The user&nbsp;ID is also used to firewall
off on-disk data.</para>
@@ -5897,7 +5727,7 @@ Key F15 A A Menu Workplace Nop</programlisting>
</qandaentry>
<qandaentry>
- <question id="securelevel">
+ <question xml:id="securelevel">
<para>What is securelevel?</para>
</question>
@@ -5906,7 +5736,7 @@ Key F15 A A Menu Workplace Nop</programlisting>
mechanism implemented in the kernel. When the securelevel
is positive, the
kernel restricts certain tasks; not even the superuser
- (i.e., <username>root</username>) is allowed to do them.
+ (i.e., <systemitem class="username">root</systemitem>) is allowed to do them.
The securelevel mechanism limits the ability to:</para>
<itemizedlist>
@@ -5918,8 +5748,8 @@ Key F15 A A Menu Workplace Nop</programlisting>
<listitem>
<para>Write to kernel memory via
- <devicename>/dev/mem</devicename> and
- <devicename>/dev/kmem</devicename>.</para>
+ <filename>/dev/mem</filename> and
+ <filename>/dev/kmem</filename>.</para>
</listitem>
<listitem>
@@ -5944,7 +5774,7 @@ Key F15 A A Menu Workplace Nop</programlisting>
<para>The securelevel of a running system can not be
lowered as this would defeat its purpose. If you need
to do a task that requires that the securelevel be
- non-positive (e.g., an <maketarget>installworld</maketarget>
+ non-positive (e.g., an <buildtarget>installworld</buildtarget>
or changing the date), you will have to change the
securelevel setting in <filename>/etc/rc.conf</filename>
(you want to look for the
@@ -5977,8 +5807,7 @@ Key F15 A A Menu Workplace Nop</programlisting>
<para>This point and others are often discussed on the
mailing lists, particularly the &a.security;. Please
- search the archives <ulink
- url="&url.base;/search/index.html">here</ulink> for an
+ search the archives <link xlink:href="&url.base;/search/index.html">here</link> for an
extensive discussion. A more fine-grained mechanism
is preferred.</para>
</warning>
@@ -5986,7 +5815,7 @@ Key F15 A A Menu Workplace Nop</programlisting>
</qandaentry>
<qandaentry>
- <question id="extra-named-port">
+ <question xml:id="extra-named-port">
<para>BIND (<command>named</command>) is listening on
some high-numbered ports. What is going on?</para>
</question>
@@ -6019,7 +5848,7 @@ Key F15 A A Menu Workplace Nop</programlisting>
</qandaentry>
<qandaentry>
- <question id="sendmail-port-587">
+ <question xml:id="sendmail-port-587">
<para>The <application>sendmail</application> daemon is
listening on port 587 as well as the standard port 25! What
is going on?</para>
@@ -6034,59 +5863,58 @@ Key F15 A A Menu Workplace Nop</programlisting>
</qandaentry>
<qandaentry>
- <question id="toor-account">
- <para>What is this UID 0 <username>toor</username> account?
+ <question xml:id="toor-account">
+ <para>What is this UID 0 <systemitem class="username">toor</systemitem> account?
Have I been compromised?</para>
</question>
<answer>
- <para>Do not worry. <username>toor</username> is an
+ <para>Do not worry. <systemitem class="username">toor</systemitem> is an
<quote>alternative</quote> superuser account (toor is root
spelt backwards). Previously it was created when the
&man.bash.1; shell was installed but now it is created by
default. It is intended to be used with a non-standard
shell so you do not have to change
- <username>root</username>'s default shell. This is
+ <systemitem class="username">root</systemitem>'s default shell. This is
important as shells which are not part of the base
distribution (for example a shell installed from ports or
packages) are likely to be installed in
- <filename class="directory">/usr/local/bin</filename> which, by default,
+ <filename>/usr/local/bin</filename> which, by default,
resides on a different file system. If
- <username>root</username>'s shell is located in
- <filename class="directory">/usr/local/bin</filename> and
- <filename class="directory">/usr</filename> (or whatever file system contains
- <filename class="directory">/usr/local/bin</filename>) is not mounted for some
- reason, <username>root</username> will not be able to log in
+ <systemitem class="username">root</systemitem>'s shell is located in
+ <filename>/usr/local/bin</filename> and
+ <filename>/usr</filename> (or whatever file system contains
+ <filename>/usr/local/bin</filename>) is not mounted for some
+ reason, <systemitem class="username">root</systemitem> will not be able to log in
to fix a problem (although if you reboot into single user
mode you will be prompted for the path to a shell).</para>
- <para>Some people use <username>toor</username> for day-to-day
- <username>root</username> tasks with a non-standard shell,
- leaving <username>root</username>, with a standard shell,
+ <para>Some people use <systemitem class="username">toor</systemitem> for day-to-day
+ <systemitem class="username">root</systemitem> tasks with a non-standard shell,
+ leaving <systemitem class="username">root</systemitem>, with a standard shell,
for single user mode or emergencies. By default you cannot
- log in using <username>toor</username> as it does not have a
- password, so log in as <username>root</username> and set a
- password for <username>toor</username> if you want to use
+ log in using <systemitem class="username">toor</systemitem> as it does not have a
+ password, so log in as <systemitem class="username">root</systemitem> and set a
+ password for <systemitem class="username">toor</systemitem> if you want to use
it.</para>
</answer>
</qandaentry>
</qandaset>
</chapter>
- <chapter id="ppp">
+ <chapter xml:id="ppp">
<title>PPP</title>
<qandaset>
<qandaentry>
- <question id="userppp">
+ <question xml:id="userppp">
<para>I cannot make &man.ppp.8; work. What am I doing
wrong?</para>
</question>
<answer>
<para>You should first read the &man.ppp.8; manual page and
- the <ulink
- url="&url.books.handbook;/ppp-and-slip.html#userppp">PPP section of the handbook</ulink>.
+ the <link xlink:href="&url.books.handbook;/ppp-and-slip.html#userppp">PPP section of the handbook</link>.
Enable logging with the following command:</para>
<programlisting>set log Phase Chat Connect Carrier lcp ipcp ccp command</programlisting>
@@ -6111,7 +5939,7 @@ Key F15 A A Menu Workplace Nop</programlisting>
</qandaentry>
<qandaentry>
- <question id="ppp-hangs">
+ <question xml:id="ppp-hangs">
<para>Why does &man.ppp.8; hang when I run it?</para>
</question>
@@ -6124,7 +5952,7 @@ Key F15 A A Menu Workplace Nop</programlisting>
<literal>hosts</literal> line first. Then, simply put an
entry in <filename>/etc/hosts</filename> for your local
machine. If you have no local network, change your
- <hostid>localhost</hostid> line:</para>
+ <systemitem>localhost</systemitem> line:</para>
<programlisting>127.0.0.1 foo.example.com foo localhost</programlisting>
@@ -6138,7 +5966,7 @@ Key F15 A A Menu Workplace Nop</programlisting>
</qandaentry>
<qandaentry>
- <question id="ppp-nodial-auto">
+ <question xml:id="ppp-nodial-auto">
<para>Why will &man.ppp.8; not dial in
<literal>-auto</literal> mode?</para>
</question>
@@ -6168,14 +5996,13 @@ default 10.0.0.2 UGSc 0 0 tun0
<programlisting>delete ALL</programlisting>
- <para>If this is the case, go back to the <ulink
- url="&url.books.handbook;/userppp.html#userppp-final">Final System Configuration</ulink>
+ <para>If this is the case, go back to the <link xlink:href="&url.books.handbook;/userppp.html#userppp-final">Final System Configuration</link>
section of the handbook.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="no-route-to-host">
+ <question xml:id="no-route-to-host">
<para>What does <errorname>No route to host</errorname>
mean?</para>
</question>
@@ -6198,14 +6025,13 @@ default 10.0.0.2 UGSc 0 0 tun0
<programlisting>delete ALL
add 0 0 HISADDR</programlisting>
- <para>Refer to the <ulink
- url="&url.books.handbook;/userppp.html#userppp-dynamicip">PPP and Dynamic IP addresses</ulink>
+ <para>Refer to the <link xlink:href="&url.books.handbook;/userppp.html#userppp-dynamicip">PPP and Dynamic IP addresses</link>
section of the handbook for further details.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="connection-threeminutedrop">
+ <question xml:id="connection-threeminutedrop">
<para>Why does my connection drop after about 3
minutes?</para>
</question>
@@ -6230,7 +6056,7 @@ add 0 0 HISADDR</programlisting>
</qandaentry>
<qandaentry>
- <question id="ppp-drop-heavy-load">
+ <question xml:id="ppp-drop-heavy-load">
<para>Why does my connection drop under heavy load?</para>
</question>
@@ -6247,7 +6073,7 @@ add 0 0 HISADDR</programlisting>
</qandaentry>
<qandaentry>
- <question id="ppp-drop-random">
+ <question xml:id="ppp-drop-random">
<para>Why does my connection drop after a random amount of
time?</para>
</question>
@@ -6264,7 +6090,7 @@ add 0 0 HISADDR</programlisting>
</qandaentry>
<qandaentry>
- <question id="ppp-hangs-random">
+ <question xml:id="ppp-hangs-random">
<para>Why does my connection hang after a random amount of
time?</para>
</question>
@@ -6299,20 +6125,18 @@ add 0 0 HISADDR</programlisting>
<itemizedlist>
<listitem>
- <para>If the problem is remote, read on entry <xref
- linkend="ppp-remote-not-responding"/>.</para>
+ <para>If the problem is remote, read on entry <xref linkend="ppp-remote-not-responding"/>.</para>
</listitem>
<listitem>
- <para>If the problem is local, read on entry <xref
- linkend="ppp-hung"/>.</para>
+ <para>If the problem is local, read on entry <xref linkend="ppp-hung"/>.</para>
</listitem>
</itemizedlist>
</answer>
</qandaentry>
<qandaentry>
- <question id="ppp-remote-not-responding">
+ <question xml:id="ppp-remote-not-responding">
<para>The remote end is not responding. What can I do?</para>
</question>
@@ -6354,7 +6178,7 @@ deny pred1 deflate deflate24 protocomp acfcomp shortseq vj</programlisting>
</qandaentry>
<qandaentry>
- <question id="ppp-hung">
+ <question xml:id="ppp-hung">
<para>&man.ppp.8; has hung. What can I do?</para>
</question>
@@ -6388,7 +6212,7 @@ deny pred1 deflate deflate24 protocomp acfcomp shortseq vj</programlisting>
</qandaentry>
<qandaentry>
- <question id="ppp-same-magic">
+ <question xml:id="ppp-same-magic">
<para>I keep seeing errors about magic being the same. What
does it mean?</para>
</question>
@@ -6455,7 +6279,7 @@ deny pred1 deflate deflate24 protocomp acfcomp shortseq vj</programlisting>
</qandaentry>
<qandaentry>
- <question id="ppp-lcp-constant">
+ <question xml:id="ppp-lcp-constant">
<para>LCP negotiations continue until the connection is
closed. What is wrong?</para>
</question>
@@ -6468,32 +6292,32 @@ deny pred1 deflate deflate24 protocomp acfcomp shortseq vj</programlisting>
other side, the other side will send two additional LCP
configuration requests. This is fatal.</para>
- <para>Consider two implementations, <hostid>A</hostid> and
- <hostid>B</hostid>. <hostid>A</hostid> starts sending LCP
- requests immediately after connecting and <hostid>B</hostid>
- takes 7 seconds to start. When <hostid>B</hostid> starts,
- <hostid>A</hostid> has sent 3 LCP REQs. We are assuming the
+ <para>Consider two implementations, <systemitem>A</systemitem> and
+ <systemitem>B</systemitem>. <systemitem>A</systemitem> starts sending LCP
+ requests immediately after connecting and <systemitem>B</systemitem>
+ takes 7 seconds to start. When <systemitem>B</systemitem> starts,
+ <systemitem>A</systemitem> has sent 3 LCP REQs. We are assuming the
line has ECHO switched off, otherwise we would see magic
number problems as described in the previous section.
- <hostid>B</hostid> sends a REQ, then an ACK to the first of
- <hostid>A</hostid>'s REQs. This results in
- <hostid>A</hostid> entering the <acronym>OPENED</acronym>
+ <systemitem>B</systemitem> sends a REQ, then an ACK to the first of
+ <systemitem>A</systemitem>'s REQs. This results in
+ <systemitem>A</systemitem> entering the <acronym>OPENED</acronym>
state and sending and ACK (the first) back to
- <hostid>B</hostid>. In the meantime, <hostid>B</hostid>
+ <systemitem>B</systemitem>. In the meantime, <systemitem>B</systemitem>
sends back two more ACKs in response to the two additional
- REQs sent by <hostid>A</hostid> before <hostid>B</hostid>
- started up. <hostid>B</hostid> then receives the first ACK
- from <hostid>A</hostid> and enters the
- <acronym>OPENED</acronym> state. <hostid>A</hostid>
- receives the second ACK from <hostid>B</hostid> and goes
+ REQs sent by <systemitem>A</systemitem> before <systemitem>B</systemitem>
+ started up. <systemitem>B</systemitem> then receives the first ACK
+ from <systemitem>A</systemitem> and enters the
+ <acronym>OPENED</acronym> state. <systemitem>A</systemitem>
+ receives the second ACK from <systemitem>B</systemitem> and goes
back to the <acronym>REQ-SENT</acronym> state, sending
another (forth) REQ as per the RFC. It then receives the
third ACK and enters the <acronym>OPENED</acronym> state.
- In the meantime, <hostid>B</hostid> receives the forth REQ
- from <hostid>A</hostid>, resulting in it reverting to the
+ In the meantime, <systemitem>B</systemitem> receives the forth REQ
+ from <systemitem>A</systemitem>, resulting in it reverting to the
<acronym>ACK-SENT</acronym> state and sending another
(second) REQ and (forth) ACK as per the RFC.
- <hostid>A</hostid> gets the REQ, goes into
+ <systemitem>A</systemitem> gets the REQ, goes into
<acronym>REQ-SENT</acronym> and sends another REQ. It
immediately receives the following ACK and enters
<acronym>OPENED</acronym>.</para>
@@ -6525,7 +6349,7 @@ deny pred1 deflate deflate24 protocomp acfcomp shortseq vj</programlisting>
</qandaentry>
<qandaentry>
- <question id="ppp-shell-test-lockup">
+ <question xml:id="ppp-shell-test-lockup">
<para>Why does &man.ppp.8; lock up when I shell out to test
it?</para>
</question>
@@ -6549,7 +6373,7 @@ deny pred1 deflate deflate24 protocomp acfcomp shortseq vj</programlisting>
</qandaentry>
<qandaentry>
- <question id="ppp-null-modem">
+ <question xml:id="ppp-null-modem">
<para>Why does &man.ppp.8; over a null-modem cable never
exit?</para>
</question>
@@ -6569,7 +6393,7 @@ deny pred1 deflate deflate24 protocomp acfcomp shortseq vj</programlisting>
</qandaentry>
<qandaentry>
- <question id="ppp-auto-noreasondial">
+ <question xml:id="ppp-auto-noreasondial">
<para>Why does &man.ppp.8; dial for no reason in
<option>-auto</option> mode?</para>
</question>
@@ -6608,8 +6432,7 @@ set dfilter 3 permit 0/0 0/0</programlisting>
&man.sendmail.8; is the culprit. You should make sure that
you tell <application>sendmail</application> not to do any
DNS lookups in its configuration file. See the section on
- <ulink
- url="&url.books.handbook;/smtp-dialup.html">using email with a dialup connection</ulink>
+ <link xlink:href="&url.books.handbook;/smtp-dialup.html">using email with a dialup connection</link>
in the &os; Handbook for details on how to create your own
configuration file and what should go into it. You may also
want to add the following line to
@@ -6621,13 +6444,13 @@ set dfilter 3 permit 0/0 0/0</programlisting>
everything until the queue is run (usually, sendmail is
run with <option>-bd -q30m</option>, telling it to run
the queue every 30 minutes) or until a <command>sendmail
- <option>-q</option></command> is done (perhaps from your
+ -q</command> is done (perhaps from your
<filename>ppp.linkup</filename>).</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="ccp-errors">
+ <question xml:id="ccp-errors">
<para>What do these CCP errors mean?</para>
</question>
@@ -6649,7 +6472,7 @@ CCP: Received Terminate Ack (1) state = Req-Sent (6)</programlisting>
</qandaentry>
<qandaentry>
- <question id="ppp-connectionspeed">
+ <question xml:id="ppp-connectionspeed">
<para>Why does &man.ppp.8; not log my connection speed?</para>
</question>
@@ -6681,7 +6504,7 @@ CCP: Received Terminate Ack (1) state = Req-Sent (6)</programlisting>
</qandaentry>
<qandaentry>
- <question id="ppp-ignores-backslash">
+ <question xml:id="ppp-ignores-backslash">
<para>Why does &man.ppp.8; ignore the <literal>\</literal>
character in my chat script?</para>
</question>
@@ -6729,7 +6552,7 @@ ATDT1234567</programlisting>
</qandaentry>
<qandaentry>
- <question id="ppp-segfault-nocore">
+ <question xml:id="ppp-segfault-nocore">
<para>Why does &man.ppp.8; get a <errorname>Segmentation
fault</errorname>, but I see no
<filename>ppp.core</filename></para>
@@ -6748,13 +6571,13 @@ ATDT1234567</programlisting>
section), then you should install the system sources and do
the following:</para>
- <screen>&prompt.root; <userinput><command>cd</command> <filename class="directory">/usr/src/usr.sbin/ppp</filename></userinput>
-&prompt.root; <userinput><command>echo</command> <makevar>STRIP</makevar>= &gt;&gt; <filename>/etc/make.conf</filename></userinput>
-&prompt.root; <userinput><command>echo</command> <makevar>CFLAGS</makevar>+=<option>-g</option> &gt;&gt; <filename>/etc/make.conf</filename></userinput>
-&prompt.root; <userinput><command>make</command> <maketarget>install</maketarget> <maketarget>clean</maketarget></userinput></screen>
+ <screen>&prompt.root; <userinput>cd /usr/src/usr.sbin/ppp</userinput>
+&prompt.root; <userinput>echo STRIP= &gt;&gt; /etc/make.conf</userinput>
+&prompt.root; <userinput>echo CFLAGS+=-g &gt;&gt; /etc/make.conf</userinput>
+&prompt.root; <userinput>make install clean</userinput></screen>
<para>You will now have a debuggable version of &man.ppp.8;
- installed. You will have to be <username>root</username> to
+ installed. You will have to be <systemitem class="username">root</systemitem> to
run &man.ppp.8; as all of its privileges have been revoked.
When you start &man.ppp.8;, take a careful note of what your
current directory was at the time.</para>
@@ -6786,7 +6609,7 @@ ATDT1234567</programlisting>
</qandaentry>
<qandaentry>
- <question id="ppp-autodialprocess-noconnect">
+ <question xml:id="ppp-autodialprocess-noconnect">
<para>Why does the process that forces a dial in
<option>-auto</option> mode never connect?</para>
</question>
@@ -6839,12 +6662,11 @@ ATDT1234567</programlisting>
<para>Yet another possibility is to allow an interface to be
brought up without an IP number. Outgoing packets would be
- given an IP number of <hostid
- role="ipaddr">255.255.255.255</hostid> up until the first
+ given an IP number of <systemitem class="ipaddress">255.255.255.255</systemitem> up until the first
<literal>SIOCAIFADDR</literal> &man.ioctl.2; is done. This
would result in fully binding the socket. It would be up to
&man.ppp.8; to change the source IP number, but only if it
- is set to <hostid role="ipaddr">255.255.255.255</hostid>,
+ is set to <systemitem class="ipaddress">255.255.255.255</systemitem>,
and only the IP number and IP checksum would need to change.
This, however is a bit of a hack as the kernel would be
sending bad packets to an improperly configured interface,
@@ -6854,7 +6676,7 @@ ATDT1234567</programlisting>
</qandaentry>
<qandaentry>
- <question id="ppp-nat-games">
+ <question xml:id="ppp-nat-games">
<para>Why do most games not work with the
<option>-nat</option> switch?</para>
</question>
@@ -6939,7 +6761,7 @@ ATDT1234567</programlisting>
</qandaentry>
<qandaentry>
- <question id="fcs-errors">
+ <question xml:id="fcs-errors">
<para>What are FCS errors?</para>
</question>
@@ -6988,7 +6810,7 @@ ATDT1234567</programlisting>
</qandaentry>
<qandaentry>
- <question id="desperation">
+ <question xml:id="desperation">
<para>None of this helps &mdash; I am desperate! What can I
do?</para>
</question>
@@ -7006,23 +6828,21 @@ ATDT1234567</programlisting>
</qandaset>
</chapter>
- <chapter id="serial">
+ <chapter xml:id="serial">
<title>Serial Communications</title>
<para>This section answers common questions about serial
- communications with &os;. PPP is covered in the <link
- linkend="networking">Networking</link> section.</para>
+ communications with &os;. PPP is covered in the <link linkend="networking">Networking</link> section.</para>
<qandaset>
<qandaentry>
- <question id="multiport-serial-support">
+ <question xml:id="multiport-serial-support">
<para>Which multi-port serial cards are supported by
&os;?</para>
</question>
<answer>
- <para>There is a list of these in the <ulink
- url="&url.books.handbook;/serial.html">Serial Communications</ulink>
+ <para>There is a list of these in the <link xlink:href="&url.books.handbook;/serial.html">Serial Communications</link>
chapter of the handbook.</para>
<para>Most multi-port PCI cards that are based on 16550 or
@@ -7037,19 +6857,18 @@ ATDT1234567</programlisting>
</qandaentry>
<qandaentry>
- <question id="serial-console-prompt">
+ <question xml:id="serial-console-prompt">
<para>How do I get the boot: prompt to show on the serial
console?</para>
</question>
<answer>
- <para>See <ulink
- url="&url.books.handbook;/serialconsole-setup.html">this section of the handbook</ulink>.</para>
+ <para>See <link xlink:href="&url.books.handbook;/serialconsole-setup.html">this section of the handbook</link>.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="found-serial">
+ <question xml:id="found-serial">
<para>How do I tell if &os; found my serial ports or modem
cards?</para>
</question>
@@ -7084,42 +6903,41 @@ sio1: type 16550A</programlisting>
settings in the above example. If these settings are not
right for your system, or if you have added modem cards or
have more serial ports than your kernel is configured for,
- just reconfigure your kernel. See section <link
- linkend="make-kernel">about building a kernel</link> for
+ just reconfigure your kernel. See section <link linkend="make-kernel">about building a kernel</link> for
more details.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="access-serial-ports">
+ <question xml:id="access-serial-ports">
<para>How do I access the serial ports on &os;?</para>
</question>
<answer>
- <para>The third serial port, <devicename>sio2</devicename>
- (see &man.sio.4;, known as <devicename>COM3</devicename> in
- DOS), is on <devicename>/dev/cuad2</devicename> for dial-out
- devices, and on <devicename>/dev/ttyd2</devicename> for
+ <para>The third serial port, <filename>sio2</filename>
+ (see &man.sio.4;, known as <filename>COM3</filename> in
+ DOS), is on <filename>/dev/cuad2</filename> for dial-out
+ devices, and on <filename>/dev/ttyd2</filename> for
dial-in devices. What is the difference between these two
classes of devices?</para>
<para>You use
- <devicename>ttyd<replaceable>X</replaceable></devicename>
+ <filename>ttydX</filename>
for dial-ins. When opening
- <devicename>/dev/ttyd<replaceable>X</replaceable></devicename>
+ <filename>/dev/ttydX</filename>
in blocking mode, a process will wait for the corresponding
- <devicename>cuad<replaceable>X</replaceable></devicename>
+ <filename>cuadX</filename>
device to become inactive, and then wait for the carrier
detect line to go active. When you open the
- <devicename>cuad<replaceable>X</replaceable></devicename>
+ <filename>cuadX</filename>
device, it makes sure the serial port is not already in use
by the
- <devicename>ttyd<replaceable>X</replaceable></devicename>
+ <filename>ttydX</filename>
device. If the port is available, it <quote>steals</quote>
it from the
- <devicename>ttyd<replaceable>X</replaceable></devicename>
+ <filename>ttydX</filename>
device. Also, the
- <devicename>cuad<replaceable>X</replaceable></devicename>
+ <filename>cuadX</filename>
device does not care about carrier detect. With this scheme
and an auto-answer modem, you can have remote users log in
and you can still dial out with the same modem and the
@@ -7128,7 +6946,7 @@ sio1: type 16550A</programlisting>
</qandaentry>
<qandaentry>
- <question id="enable-multiport-serial">
+ <question xml:id="enable-multiport-serial">
<para>How do I enable support for a multiport serial
card?</para>
</question>
@@ -7170,56 +6988,53 @@ hint.sio.7.irq="12"</programlisting>
</qandaentry>
<qandaentry>
- <question id="default-serial-params">
+ <question xml:id="default-serial-params">
<para>Can I set the default serial parameters for a
port?</para>
</question>
<answer>
- <para>See the <ulink
- url="&url.books.handbook;/serial.html#serial-hw-config">Serial Communications</ulink>
+ <para>See the <link xlink:href="&url.books.handbook;/serial.html#serial-hw-config">Serial Communications</link>
section in the &os; Handbook.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="enable-dialup">
+ <question xml:id="enable-dialup">
<para>How can I enable dialup logins on my modem?</para>
</question>
<answer>
- <para>Please read the section about <ulink
- url="&url.books.handbook;/dialup.html">Dial-in Services</ulink>
+ <para>Please read the section about <link xlink:href="&url.books.handbook;/dialup.html">Dial-in Services</link>
in the &os; Handbook.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="dumb-terminal">
+ <question xml:id="dumb-terminal">
<para>How can I connect a dumb terminal to my &os; box?</para>
</question>
<answer>
- <para>You can find this information in the <ulink
- url="&url.books.handbook;/term.html">Terminals</ulink>
+ <para>You can find this information in the <link xlink:href="&url.books.handbook;/term.html">Terminals</link>
section of the &os; Handbook.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="cannot-tip">
+ <question xml:id="cannot-tip">
<para>Why can I not run <command>tip</command> or
<command>cu</command>?</para>
</question>
<answer>
<para>On your system, the programs &man.tip.1; and &man.cu.1;
- can only access the <filename class="directory">/var/spool/lock</filename>
- directory via user <username>uucp</username> and group
- <groupname>dialer</groupname>. You can use the group
- <groupname>dialer</groupname> to control who has access to
+ can only access the <filename>/var/spool/lock</filename>
+ directory via user <systemitem class="username">uucp</systemitem> and group
+ <systemitem class="groupname">dialer</systemitem>. You can use the group
+ <systemitem class="groupname">dialer</systemitem> to control who has access to
your modem or remote systems. Just add yourself to group
- <groupname>dialer</groupname>.</para>
+ <systemitem class="groupname">dialer</systemitem>.</para>
<para>Alternatively, you can let everyone on your system run
&man.tip.1; and &man.cu.1; by typing:</para>
@@ -7231,12 +7046,12 @@ hint.sio.7.irq="12"</programlisting>
</qandaset>
</chapter>
- <chapter id="misc">
+ <chapter xml:id="misc">
<title>Miscellaneous Questions</title>
<qandaset>
<qandaentry>
- <question id="more-swap">
+ <question xml:id="more-swap">
<para>&os; uses a lot of swap space even when the computer has
free memory left. Why?</para>
</question>
@@ -7257,7 +7072,7 @@ hint.sio.7.irq="12"</programlisting>
</qandaentry>
<qandaentry>
- <question id="top-freemem">
+ <question xml:id="top-freemem">
<para>Why does <command>top</command> show very little free
memory even when I have very few programs running?</para>
</question>
@@ -7278,7 +7093,7 @@ hint.sio.7.irq="12"</programlisting>
</qandaentry>
<qandaentry>
- <question id="chmod-symlinks">
+ <question xml:id="chmod-symlinks">
<para>Why will <command>chmod</command> not change the
permissions on symlinks?</para>
</question>
@@ -7310,11 +7125,11 @@ hint.sio.7.irq="12"</programlisting>
&man.chmod.1;. If you want to change the permissions of a
directory referenced by a symlink, use &man.chmod.1;
without any options and follow the symlink with a trailing
- slash (<filename class="directory">/</filename>). For example, if
+ slash (<filename>/</filename>). For example, if
<filename>foo</filename> is a symlink to directory
- <filename class="directory">bar</filename>, and you want to change the
+ <filename>bar</filename>, and you want to change the
permissions of <filename>foo</filename> (actually
- <filename class="directory">bar</filename>), you would do something
+ <filename>bar</filename>), you would do something
like:</para>
<screen>&prompt.user; <userinput>chmod 555 foo/</userinput></screen>
@@ -7322,30 +7137,27 @@ hint.sio.7.irq="12"</programlisting>
<para>With the trailing slash, &man.chmod.1; will follow the
symlink, <filename>foo</filename>, to change the
permissions of the directory,
- <filename class="directory">bar</filename>.</para>
+ <filename>bar</filename>.</para>
</warning>
</answer>
</qandaentry>
<qandaentry>
- <question id="dos-binaries">
+ <question xml:id="dos-binaries">
<para>Can I run DOS binaries under &os;?</para>
</question>
<answer>
- <para>Yes, you can use <filename
- role="package">emulators/doscmd</filename>, a DOS
+ <para>Yes, you can use <package>emulators/doscmd</package>, a DOS
emulation program, available in the &os; Ports
Collection.</para>
<para>If <application>doscmd</application> will not suffice,
- the add-on utility <filename
- role="package">emulators/pcemu</filename> emulates an 8088
+ the add-on utility <package>emulators/pcemu</package> emulates an 8088
and enough BIOS services to run many DOS text mode
applications. It requires the X Window System.</para>
- <para>You may also try <filename
- role="package">emulators/dosbox</filename> from the &os;
+ <para>You may also try <package>emulators/dosbox</package> from the &os;
Ports Collection. The main focus of this application is
emulating old DOS games using the local file system for
files.</para>
@@ -7353,26 +7165,24 @@ hint.sio.7.irq="12"</programlisting>
</qandaentry>
<qandaentry>
- <question id="translation">
+ <question xml:id="translation">
<para>What do I need to do to translate a &os; document into
my native language?</para>
</question>
<answer>
- <para>See the <ulink
- url="&url.books.fdp-primer;/translations.html">Translation FAQ</ulink>
+ <para>See the <link xlink:href="&url.books.fdp-primer;/translations.html">Translation FAQ</link>
in the &os; Documentation Project Primer.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="freebsd-mail-bounces">
- <para>Why does my email to any address at <hostid
- role="domainname">FreeBSD.org</hostid> bounce?</para>
+ <question xml:id="freebsd-mail-bounces">
+ <para>Why does my email to any address at <systemitem class="fqdomainname">FreeBSD.org</systemitem> bounce?</para>
</question>
<answer>
- <para>The <hostid role="domainname">FreeBSD.org</hostid> mail
+ <para>The <systemitem class="fqdomainname">FreeBSD.org</systemitem> mail
system implements some
<application>Postfix</application> checks on incoming mail
and rejects mail that is either from misconfigured relays or
@@ -7411,7 +7221,7 @@ hint.sio.7.irq="12"</programlisting>
</itemizedlist>
<para>If you still have trouble with email infrastructure at
- <hostid role="domainname">FreeBSD.org</hostid> send a note
+ <systemitem class="fqdomainname">FreeBSD.org</systemitem> send a note
with the details to
<email>postmaster@freebsd.org</email>; Include a
date/time interval so that logs may be reviewed &mdash;
@@ -7422,7 +7232,7 @@ hint.sio.7.irq="12"</programlisting>
</qandaentry>
<qandaentry>
- <question id="free-account">
+ <question xml:id="free-account">
<para>Where can I find a free &os; account?</para>
</question>
@@ -7431,8 +7241,7 @@ hint.sio.7.irq="12"</programlisting>
servers, others do provide open access &unix; systems. The
charge varies and limited services may be available.</para>
- <para><ulink
- url="http://www.arbornet.org/">Arbornet, Inc</ulink>,
+ <para><link xlink:href="http://www.arbornet.org/">Arbornet, Inc</link>,
also known as <emphasis>M-Net</emphasis>, has been providing
open access to &unix; systems since 1983. Starting on an
Altos running System III, the site switched to BSD/OS in
@@ -7449,7 +7258,7 @@ hint.sio.7.irq="12"</programlisting>
</qandaentry>
<qandaentry>
- <question id="daemon-name">
+ <question xml:id="daemon-name">
<para>What is the cute little red guy's name?</para>
</question>
@@ -7459,57 +7268,53 @@ hint.sio.7.irq="12"</programlisting>
<quote>beastie</quote>. Note that <quote>beastie</quote> is
pronounced <quote>BSD</quote>.</para>
- <para>You can learn more about the BSD daemon on his <ulink
- url="http://www.mckusick.com/beastie/index.html">home page</ulink>.</para>
+ <para>You can learn more about the BSD daemon on his <link xlink:href="http://www.mckusick.com/beastie/index.html">home page</link>.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="use-beastie">
+ <question xml:id="use-beastie">
<para>Can I use the BSD daemon image?</para>
</question>
<answer>
<para>Perhaps. The BSD daemon is copyrighted by Marshall Kirk
- McKusick. You will want to check his <ulink
- url="http://www.mckusick.com/beastie/mainpage/copyright.html">Statement on the Use of the BSD Daemon Figure</ulink>
+ McKusick. You will want to check his <link xlink:href="http://www.mckusick.com/beastie/mainpage/copyright.html">Statement on the Use of the BSD Daemon Figure</link>
for detailed usage terms.</para>
<para>In summary, you are free to use the image in a tasteful
manner, for personal use, so long as appropriate credit is
given. If you want to use him commercially, you must
contact &a.mckusick.email;. More details are available on the
- <ulink
- url="http://www.mckusick.com/beastie/index.html">BSD Daemon's home page</ulink>.</para>
+ <link xlink:href="http://www.mckusick.com/beastie/index.html">BSD Daemon's home page</link>.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="daemon-images">
+ <question xml:id="daemon-images">
<para>Do you have any BSD daemon images I could use?</para>
</question>
<answer>
<para>You will find eps and Xfig drawings under
- <filename class="directory">/usr/share/examples/BSD_daemon/</filename>.</para>
+ <filename>/usr/share/examples/BSD_daemon/</filename>.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="glossary">
+ <question xml:id="glossary">
<para>I have seen an acronym or other term on the mailing
lists and I do not understand what it means. Where should I
look?</para>
</question>
<answer>
- <para>Please see the <ulink
- url="&url.books.handbook;/freebsd-glossary.html">&os; Glossary</ulink>.</para>
+ <para>Please see the <link xlink:href="&url.books.handbook;/freebsd-glossary.html">&os; Glossary</link>.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="bikeshed-painting">
+ <question xml:id="bikeshed-painting">
<para>Why should I care what color the bikeshed is?</para>
</question>
@@ -7528,8 +7333,7 @@ hint.sio.7.irq="12"</programlisting>
<para>The longer and more complete answer is that after a very
long argument about whether &man.sleep.1; should take
fractional second arguments, &a.phk.email; posted a long message
- entitled <quote><ulink
- url="http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=506636+517178+/usr/local/www/db/text/1999/freebsd-hackers/19991003.freebsd-hackers">A bike shed (any color will do) on greener grass...</ulink></quote>.
+ entitled <quote><link xlink:href="http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=506636+517178+/usr/local/www/db/text/1999/freebsd-hackers/19991003.freebsd-hackers">A bike shed (any color will do) on greener grass...</link></quote>.
The appropriate portions of that message are quoted
below.</para>
@@ -7588,12 +7392,12 @@ hint.sio.7.irq="12"</programlisting>
</qandaset>
</chapter>
- <chapter id="funnies">
+ <chapter xml:id="funnies">
<title>The &os; Funnies</title>
<qandaset>
<qandaentry>
- <question id="very-very-cool">
+ <question xml:id="very-very-cool">
<para>How cool is &os;?</para>
</question>
@@ -7628,7 +7432,7 @@ hint.sio.7.irq="12"</programlisting>
</qandaentry>
<qandaentry>
- <question id="letmeoutofhere">
+ <question xml:id="letmeoutofhere">
<para>Who is scratching in my memory banks??</para>
</question>
@@ -7665,7 +7469,7 @@ hint.sio.7.irq="12"</programlisting>
</qandaentry>
<qandaentry>
- <question id="changing-lightbulbs">
+ <question xml:id="changing-lightbulbs">
<para>How many &os; hackers does it take to change a
lightbulb?</para>
</question>
@@ -7782,7 +7586,7 @@ hint.sio.7.irq="12"</programlisting>
</qandaentry>
<qandaentry>
- <question id="dev-null">
+ <question xml:id="dev-null">
<para>Where does data written to
<filename>/dev/null</filename> go?</para>
</question>
@@ -7802,7 +7606,7 @@ hint.sio.7.irq="12"</programlisting>
CPU by reading data out of <filename>/dev/random</filename>
and sending it off somewhere; however you run the risk of
overheating your network connection and
- <filename class="directory">/</filename> or angering your ISP, as most of the
+ <filename>/</filename> or angering your ISP, as most of the
data will end up getting converted to heat by their
equipment, but they generally have good cooling, so if you
do not overdo it you should be OK.</para>
@@ -7839,13 +7643,13 @@ hint.sio.7.irq="12"</programlisting>
</qandaentry>
<qandaentry>
- <question id="punk-my-friend">
+ <question xml:id="punk-my-friend">
<para>My colleague sits at the computer too much, how
can I prank her?</para>
</question>
<answer>
- <para>Install <filename role="port">games/sl</filename> and wait
+ <para>Install <package role="port">games/sl</package> and wait
for her to mistype <userinput>sl</userinput> for
<command>ls</command>.</para>
</answer>
@@ -7853,19 +7657,18 @@ hint.sio.7.irq="12"</programlisting>
</qandaset>
</chapter>
- <chapter id="advanced">
+ <chapter xml:id="advanced">
<title>Advanced Topics</title>
<qandaset>
<qandaentry>
- <question id="learn-advanced">
+ <question xml:id="learn-advanced">
<para>How can I learn more about &os;'s internals?</para>
</question>
<answer>
<para>See the
- <ulink
- url="&url.books.arch-handbook;">&os; Architecture Handbook</ulink>.</para>
+ <link xlink:href="&url.books.arch-handbook;">&os; Architecture Handbook</link>.</para>
<para>Additionally, much general &unix; knowledge is directly
applicable to &os;.</para>
@@ -7873,27 +7676,25 @@ hint.sio.7.irq="12"</programlisting>
</qandaentry>
<qandaentry>
- <question id="how-to-contribute">
+ <question xml:id="how-to-contribute">
<para>How can I contribute to &os;?</para>
</question>
<answer>
- <para>Please see the article on <ulink
- url="&url.articles.contributing;/article.html">Contributing to &os;</ulink>
+ <para>Please see the article on <link xlink:href="&url.articles.contributing;/article.html">Contributing to &os;</link>
for specific advice on how to do this. Assistance is more
than welcome!</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="define-snap-release">
+ <question xml:id="define-snap-release">
<para>What are snapshots and releases?</para>
</question>
<answer>
<para>There are currently &rel.numbranch; active/semi-active branches in
- the &os; <ulink
- url="http://svnweb.FreeBSD.org/base/">Subversion Repository</ulink>.
+ the &os; <link xlink:href="http://svnweb.FreeBSD.org/base/">Subversion Repository</link>.
(Earlier branches are only changed very rarely, which is why
there are only &rel.numbranch; active branches of development):</para>
@@ -7933,27 +7734,25 @@ hint.sio.7.irq="12"</programlisting>
</qandaentry>
<qandaentry>
- <question id="ctm">
+ <question xml:id="ctm">
<para>Can I follow <emphasis>-CURRENT</emphasis> with limited
Internet access?</para>
</question>
<answer>
<para>Yes, you can do this <emphasis>without</emphasis>
- downloading the whole source tree by using the <ulink
- url="&url.books.handbook;/synching.html#ctm">CTM facility</ulink>.</para>
+ downloading the whole source tree by using the <link xlink:href="&url.books.handbook;/synching.html#ctm">CTM facility</link>.</para>
</answer>
</qandaentry>
<qandaentry>
- <question id="submitting-kernel-extensions">
+ <question xml:id="submitting-kernel-extensions">
<para>I have written a kernel extension, who do I send it
to?</para>
</question>
<answer>
- <para>Please take a look at the article on <ulink
- url="&url.articles.contributing;/article.html">Contributing to &os;</ulink>
+ <para>Please take a look at the article on <link xlink:href="&url.articles.contributing;/article.html">Contributing to &os;</link>
to learn how to submit code.</para>
<para>And thanks for the thought!</para>
@@ -7961,7 +7760,7 @@ hint.sio.7.irq="12"</programlisting>
</qandaentry>
<qandaentry>
- <question id="kernel-panic-troubleshooting">
+ <question xml:id="kernel-panic-troubleshooting">
<para>How can I make the most of the data I see when my kernel
panics?</para>
</question>
@@ -8009,7 +7808,7 @@ panic: page fault</programlisting>
<step>
<para>When the system reboots, do the following:</para>
- <screen>&prompt.user; <userinput><command>nm</command> <option>-n</option> <replaceable>kernel.that.caused.the.panic</replaceable> | <command>grep</command> f0xxxxxx</userinput></screen>
+ <screen>&prompt.user; <userinput>nm -n kernel.that.caused.the.panic | grep f0xxxxxx</userinput></screen>
<para>where <literal>f0xxxxxx</literal> is the
instruction pointer value. The odds are you will not
@@ -8020,7 +7819,7 @@ panic: page fault</programlisting>
get an exact match, omit the last digit from the
instruction pointer value and try again, i.e.:</para>
- <screen>&prompt.user; <userinput><command>nm</command> <option>-n</option> <replaceable>kernel.that.caused.the.panic</replaceable> | <command>grep</command> f0xxxxx</userinput></screen>
+ <screen>&prompt.user; <userinput>nm -n kernel.that.caused.the.panic | grep f0xxxxx</userinput></screen>
<para>If that does not yield any results, chop off another
digit. Repeat until you get some sort of output. The
@@ -8041,23 +7840,22 @@ panic: page fault</programlisting>
<step>
<para>Make sure that the following line is included in
your kernel configuration file
- (<filename>/usr/src/sys/<replaceable>arch</replaceable>/conf/<replaceable>MYKERNEL</replaceable></filename>):</para>
+ (<filename>/usr/src/sys/arch/conf/MYKERNEL</filename>):</para>
<programlisting>makeoptions DEBUG=-g # Build kernel with gdb(1) debug symbols</programlisting>
</step>
<step>
- <para>Change to the <filename
- class="directory">/usr/src</filename>
+ <para>Change to the <filename>/usr/src</filename>
directory:</para>
- <screen>&prompt.root; <userinput><command>cd</command> <filename class="directory">/usr/src</filename></userinput></screen>
+ <screen>&prompt.root; <userinput>cd /usr/src</userinput></screen>
</step>
<step>
<para>Compile the kernel:</para>
- <screen>&prompt.root; <userinput><command>make</command> <maketarget>buildkernel</maketarget> <makevar>KERNCONF</makevar>=<replaceable>MYKERNEL</replaceable></userinput></screen>
+ <screen>&prompt.root; <userinput>make buildkernel KERNCONF=MYKERNEL</userinput></screen>
</step>
<step>
@@ -8065,7 +7863,7 @@ panic: page fault</programlisting>
</step>
<step>
- <screen>&prompt.root; <userinput><command>make</command> <maketarget>installkernel</maketarget> <makevar>KERNCONF</makevar>=<replaceable>MYKERNEL</replaceable></userinput></screen>
+ <screen>&prompt.root; <userinput>make installkernel KERNCONF=MYKERNEL</userinput></screen>
</step>
<step>
@@ -8074,15 +7872,15 @@ panic: page fault</programlisting>
</procedure>
<note>
- <para>If you do not use the <makevar>KERNCONF</makevar>
+ <para>If you do not use the <varname>KERNCONF</varname>
make variable a <filename>GENERIC</filename> kernel will
be built and installed.</para>
</note>
<para>The &man.make.1; process will have built two kernels.
- <filename>/usr/obj/usr/src/sys/<replaceable>MYKERNEL</replaceable>/kernel</filename>
+ <filename>/usr/obj/usr/src/sys/MYKERNEL/kernel</filename>
and
- <filename>/usr/obj/usr/src/sys/<replaceable>MYKERNEL</replaceable>/kernel.debug</filename>.
+ <filename>/usr/obj/usr/src/sys/MYKERNEL/kernel.debug</filename>.
<filename>kernel</filename> was installed as
<filename>/boot/kernel/kernel</filename>, while
<filename>kernel.debug</filename> can be used as the source
@@ -8098,19 +7896,19 @@ panic: page fault</programlisting>
using &man.savecore.8;; if <literal>dumpdev</literal> is set
in <filename>/etc/rc.conf</filename>, the &man.rc.8; scripts
will run &man.savecore.8; automatically and put the crash
- dump in <filename class="directory">/var/crash</filename>.</para>
+ dump in <filename>/var/crash</filename>.</para>
<note>
<para>&os; crash dumps are usually the same size as the
physical RAM size of your machine. That is, if you have
512&nbsp;MB of RAM, you will get a 512&nbsp;MB crash dump.
Therefore you must make sure there is enough space in
- <filename class="directory">/var/crash</filename> to hold the dump.
+ <filename>/var/crash</filename> to hold the dump.
Alternatively, you run &man.savecore.8; manually and have
it recover the crash dump to another directory where you
have more room. It is possible to limit the size of the
crash dump by using <literal>options
- MAXMEM=<replaceable>N</replaceable></literal> where
+ MAXMEM=N</literal> where
<replaceable>N</replaceable> is the size of kernel's
memory usage in KBs. For example, if you have 1&nbsp;GB
of RAM, you can limit the kernel's memory usage to
@@ -8121,7 +7919,7 @@ panic: page fault</programlisting>
<para>Once you have recovered the crash dump, you can get a
stack trace with &man.kgdb.1; as follows:</para>
- <screen>&prompt.user; <userinput><command>kgdb</command> <filename>/usr/obj/usr/src/sys/<replaceable>MYKERNEL</replaceable>/kernel.debug</filename> <filename class="directory">/var/crash/<replaceable>vmcore.0</replaceable></filename></userinput>
+ <screen>&prompt.user; <userinput>kgdb /usr/obj/usr/src/sys/MYKERNEL/kernel.debug /var/crash/vmcore.0</userinput>
<prompt>(kgdb)</prompt> <userinput>backtrace</userinput></screen>
<para>Note that there may be several screens worth of
@@ -8157,7 +7955,7 @@ panic: page fault</programlisting>
</qandaentry>
<qandaentry>
- <question id="dlsym-failure">
+ <question xml:id="dlsym-failure">
<para>Why has <function>dlsym()</function> stopped working for
ELF executables?</para>
</question>
@@ -8178,7 +7976,7 @@ panic: page fault</programlisting>
</qandaentry>
<qandaentry>
- <question id="change-kernel-address-space">
+ <question xml:id="change-kernel-address-space">
<para>How can I increase or reduce the kernel address space on
i386?</para>
</question>
@@ -8204,7 +8002,7 @@ panic: page fault</programlisting>
</qandaset>
</chapter>
- <chapter id="acknowledgments">
+ <chapter xml:id="acknowledgments">
<title>Acknowledgments</title>
<para>This innocent little Frequently Asked Questions document has
@@ -8215,8 +8013,7 @@ panic: page fault</programlisting>
Repeatedly.</para>
<para>We wish to thank every one of the people responsible, and we
- encourage you to <ulink
- url="&url.articles.contributing;/article.html">join them</ulink>
+ encourage you to <link xlink:href="&url.articles.contributing;/article.html">join them</link>
in making this FAQ even better.</para>
</chapter>
diff --git a/en_US.ISO8859-1/books/fdp-primer/book.xml b/en_US.ISO8859-1/books/fdp-primer/book.xml
index 7daf24e427..31c9c556f3 100644
--- a/en_US.ISO8859-1/books/fdp-primer/book.xml
+++ b/en_US.ISO8859-1/books/fdp-primer/book.xml
@@ -1,10 +1,9 @@
<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE book PUBLIC "-//FreeBSD//DTD DocBook XML V4.5-Based Extension//EN"
- "../../../share/xml/freebsd45.dtd" [
+<!DOCTYPE book PUBLIC "-//FreeBSD//DTD DocBook XML V5.0-Based Extension//EN"
+ "../../../share/xml/freebsd50.dtd" [
<!ENTITY % chapters SYSTEM "chapters.ent"> %chapters;
<!-- ENTITY index SYSTEM "index.xml" -->
]>
-
<!-- Copyright (c) 1998, 1999 Nik Clayton, All rights reserved.
Redistribution and use in source (SGML DocBook) and 'compiled' forms
@@ -36,13 +35,12 @@
$FreeBSD$
-->
-
-<book lang='en'>
- <bookinfo>
- <title>FreeBSD Documentation Project Primer for New
+<book xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:lang="en">
+ <info><title>FreeBSD Documentation Project Primer for New
Contributors</title>
+
- <corpauthor>The FreeBSD Documentation Project</corpauthor>
+ <author><orgname>The FreeBSD Documentation Project</orgname></author>
<copyright>
<year>1998</year>
@@ -84,12 +82,12 @@
<para>This is a work in progress. Corrections and
additions are always welcome.</para>
</abstract>
- </bookinfo>
+ </info>
- <preface id="preface">
+ <preface xml:id="preface">
<title>Preface</title>
- <sect1 id="preface-prompts">
+ <sect1 xml:id="preface-prompts">
<title>Shell Prompts</title>
<para>This table shows the default system prompt and
@@ -112,7 +110,7 @@
</row>
<row>
- <entry><username>root</username></entry>
+ <entry><systemitem class="username">root</systemitem></entry>
<entry>&prompt.root;</entry>
</row>
</tbody>
@@ -120,7 +118,7 @@
</informaltable>
</sect1>
- <sect1 id="preface-conventions">
+ <sect1 xml:id="preface-conventions">
<title>Typographic Conventions</title>
<para>This table describes the typographic conventions
@@ -167,7 +165,7 @@ The time is 09:18</screen></entry>
<row>
<entry>User and group names.</entry>
- <entry>Only <username>root</username> can do
+ <entry>Only <systemitem class="username">root</systemitem> can do
this.</entry>
</row>
@@ -183,7 +181,7 @@ The time is 09:18</screen></entry>
<entry>To search for a keyword in the manual pages, type
<command>man -k
- <replaceable>keyword</replaceable></command></entry>
+ keyword</command></entry>
</row>
<row>
@@ -196,7 +194,7 @@ The time is 09:18</screen></entry>
</informaltable>
</sect1>
- <sect1 id="preface-notes">
+ <sect1 xml:id="preface-notes">
<title>Notes, Tips, Important Information, Warnings, and
Examples</title>
@@ -238,7 +236,7 @@ The time is 09:18</screen></entry>
</example>
</sect1>
- <sect1 id="preface-acknowledgements">
+ <sect1 xml:id="preface-acknowledgements">
<title>Acknowledgments</title>
<para>My thanks to Sue Blake, Patrick Durusau, Jon Hamilton,
diff --git a/en_US.ISO8859-1/books/fdp-primer/doc-build/chapter.xml b/en_US.ISO8859-1/books/fdp-primer/doc-build/chapter.xml
index 95ab3e73a0..1f95722816 100644
--- a/en_US.ISO8859-1/books/fdp-primer/doc-build/chapter.xml
+++ b/en_US.ISO8859-1/books/fdp-primer/doc-build/chapter.xml
@@ -30,14 +30,13 @@
$FreeBSD$
-->
-
-<chapter id="doc-build">
+<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:id="doc-build">
<title>The Documentation Build Process</title>
<para>This chapter covers organization of the documentation build
process and how &man.make.1; is used to control it.</para>
- <sect1 id="doc-build-toolset">
+ <sect1 xml:id="doc-build-toolset">
<title>The &os; Documentation Build Toolset</title>
<para>These are the tools used to build and install the
@@ -67,7 +66,7 @@
</itemizedlist>
</sect1>
- <sect1 id="doc-build-makefiles">
+ <sect1 xml:id="doc-build-makefiles">
<title>Understanding <filename>Makefile</filename>s in the
Documentation Tree</title>
@@ -90,15 +89,14 @@
</listitem>
<listitem>
- <para><link
- linkend="make-includes"><application>Make</application>
+ <para><link linkend="make-includes"><application>Make</application>
includes</link> are the glue that perform the document
production, and are usually of the form
- <filename>doc.<replaceable>xxx</replaceable>.mk</filename>.</para>
+ <filename>doc.xxx.mk</filename>.</para>
</listitem>
</itemizedlist>
- <sect2 id="sub-make">
+ <sect2 xml:id="sub-make">
<title>Subdirectory <filename>Makefile</filename>s</title>
<para>These <filename>Makefile</filename>s usually take the form
@@ -113,40 +111,40 @@ DOC_PREFIX?= ${.CURDIR}/..
.include "${DOC_PREFIX}/share/mk/doc.project.mk"</programlisting>
<para>The first four non-empty lines define the &man.make.1;
- variables <makevar>SUBDIR</makevar>,
- <makevar>COMPAT_SYMLINK</makevar>, and
- <makevar>DOC_PREFIX</makevar>.</para>
+ variables <varname>SUBDIR</varname>,
+ <varname>COMPAT_SYMLINK</varname>, and
+ <varname>DOC_PREFIX</varname>.</para>
- <para>The <makevar>SUBDIR</makevar> statement and
- <makevar>COMPAT_SYMLINK</makevar> statement show how to
+ <para>The <varname>SUBDIR</varname> statement and
+ <varname>COMPAT_SYMLINK</varname> statement show how to
assign a value to a variable, overriding any previous
value.</para>
- <para>The second <makevar>SUBDIR</makevar> statement shows how a
+ <para>The second <varname>SUBDIR</varname> statement shows how a
value is appended to the current value of a variable. The
- <makevar>SUBDIR</makevar> variable is now <literal>articles
+ <varname>SUBDIR</varname> variable is now <literal>articles
books</literal>.</para>
- <para>The <makevar>DOC_PREFIX</makevar> assignment shows how a
+ <para>The <varname>DOC_PREFIX</varname> assignment shows how a
value is assigned to the variable, but only if it is not
already defined. This is useful if
- <makevar>DOC_PREFIX</makevar> is not where this
+ <varname>DOC_PREFIX</varname> is not where this
<filename>Makefile</filename> thinks it is - the user can
override this and provide the correct value.</para>
- <para>What does it all mean? <makevar>SUBDIR</makevar>
+ <para>What does it all mean? <varname>SUBDIR</varname>
mentions which subdirectories below this one the build process
should pass any work on to.</para>
- <para><makevar>COMPAT_SYMLINK</makevar> is specific to
+ <para><varname>COMPAT_SYMLINK</varname> is specific to
compatibility symlinks (amazingly enough) for languages to
their official encoding (<filename>doc/en</filename> would
point to <filename>en_US.ISO-8859-1</filename>).</para>
- <para><makevar>DOC_PREFIX</makevar> is the path to the root of
+ <para><varname>DOC_PREFIX</varname> is the path to the root of
the &os; Document Project tree. This is not always that easy
to find, and is also easily overridden, to allow for
- flexibility. <makevar>.CURDIR</makevar> is a &man.make.1;
+ flexibility. <varname>.CURDIR</varname> is a &man.make.1;
builtin variable with the path to the current
directory.</para>
@@ -156,7 +154,7 @@ DOC_PREFIX?= ${.CURDIR}/..
converts these variables into build instructions.</para>
</sect2>
- <sect2 id="doc-make">
+ <sect2 xml:id="doc-make">
<title>Documentation <filename>Makefile</filename>s</title>
<para>These <filename>Makefile</filename>s set &man.make.1;
@@ -181,32 +179,32 @@ DOC_PREFIX?= ${.CURDIR}/../../..
.include "$(DOC_PREFIX)/share/mk/docproj.docbook.mk"</programlisting>
- <para>The <makevar>MAINTAINER</makevar> variable allows
+ <para>The <varname>MAINTAINER</varname> variable allows
committers to claim ownership of a document in the &os;
Documentation Project, and take responsibility for maintaining
it.</para>
- <para><makevar>DOC</makevar> is the name (sans the
+ <para><varname>DOC</varname> is the name (sans the
<filename>.xml</filename> extension) of the main document
- created by this directory. <makevar>SRCS</makevar> lists all
+ created by this directory. <varname>SRCS</varname> lists all
the individual files that make up the document. This should
also include important files in which a change should result
in a rebuild.</para>
- <para><makevar>FORMATS</makevar> indicates the default formats
+ <para><varname>FORMATS</varname> indicates the default formats
that should be built for this document.
- <makevar>INSTALL_COMPRESSED</makevar> is the default list of
+ <varname>INSTALL_COMPRESSED</varname> is the default list of
compression techniques that should be used in the document
- build. <makevar>INSTALL_ONLY_COMPRESS</makevar>, empty by
+ build. <varname>INSTALL_ONLY_COMPRESS</varname>, empty by
default, should be non-empty if only compressed documents are
desired in the build.</para>
- <para>The <makevar>DOC_PREFIX</makevar> and include statements
+ <para>The <varname>DOC_PREFIX</varname> and include statements
should be familiar already.</para>
</sect2>
</sect1>
- <sect1 id="make-includes">
+ <sect1 xml:id="make-includes">
<title>&os; Documentation Project
<application>Make</application> Includes</title>
@@ -233,8 +231,8 @@ DOC_PREFIX?= ${.CURDIR}/../../..
<listitem>
<para><filename>doc.docbook.mk</filename> is included if
- <makevar>DOCFORMAT</makevar> is <literal>docbook</literal>
- and <makevar>DOC</makevar> is set.</para>
+ <varname>DOCFORMAT</varname> is <literal>docbook</literal>
+ and <varname>DOC</varname> is set.</para>
</listitem>
</itemizedlist>
@@ -262,22 +260,22 @@ PRI_LANG?= en_US.ISO8859-1
<title>Variables</title>
- <para><makevar>DOCFORMAT</makevar> and
- <makevar>MAINTAINER</makevar> are assigned default values,
+ <para><varname>DOCFORMAT</varname> and
+ <varname>MAINTAINER</varname> are assigned default values,
if these are not set by the document make file.</para>
- <para><makevar>PREFIX</makevar> is the prefix under which the
+ <para><varname>PREFIX</varname> is the prefix under which the
<link linkend="tools">documentation building tools</link>
are installed. For normal package and port installation,
this is <filename>/usr/local</filename>.</para>
- <para><makevar>PRI_LANG</makevar> should be set to whatever
+ <para><varname>PRI_LANG</varname> should be set to whatever
language and encoding is natural amongst users these
documents are being built for. US English is the
default.</para>
<note>
- <para><makevar>PRI_LANG</makevar> does not affect which
+ <para><varname>PRI_LANG</varname> does not affect which
documents can, or even will, be built. Its main use is
creating links to commonly referenced documents into the
&os; documentation install root.</para>
@@ -294,7 +292,7 @@ PRI_LANG?= en_US.ISO8859-1
returns whether the variable given is defined or not.</para>
<para><literal>.if ${DOCFORMAT} == "docbook"</literal>, next,
- tests whether the <makevar>DOCFORMAT</makevar> variable is
+ tests whether the <varname>DOCFORMAT</varname> variable is
<literal>"docbook"</literal>, and in this case, includes
<filename>doc.docbook.mk</filename>.</para>
@@ -314,21 +312,21 @@ PRI_LANG?= en_US.ISO8859-1
<itemizedlist>
<listitem>
- <para><makevar>SUBDIR</makevar> is a list of
+ <para><varname>SUBDIR</varname> is a list of
subdirectories that the build process should go further
down into.</para>
</listitem>
<listitem>
- <para><makevar>ROOT_SYMLINKS</makevar> is the name of
+ <para><varname>ROOT_SYMLINKS</varname> is the name of
directories that should be linked to the document
install root from their actual locations, if the current
language is the primary language (specified by
- <makevar>PRI_LANG</makevar>).</para>
+ <varname>PRI_LANG</varname>).</para>
</listitem>
<listitem>
- <para><makevar>COMPAT_SYMLINK</makevar> is described in
+ <para><varname>COMPAT_SYMLINK</varname> is described in
the
<link linkend="sub-make">Subdirectory Makefile</link>
section.</para>
@@ -340,9 +338,9 @@ PRI_LANG?= en_US.ISO8859-1
<title>Targets and Macros</title>
<para>Dependencies are described by
- <literal><replaceable>target</replaceable>:
- <replaceable>dependency1 dependency2
- ...</replaceable></literal> tuples, where to build
+ <literal>target:
+ dependency1 dependency2
+ ...</literal> tuples, where to build
<literal>target</literal>, the given
dependencies must be built first.</para>
@@ -362,7 +360,7 @@ PRI_LANG?= en_US.ISO8859-1
${MAKE} ${.TARGET:S/realpackage/package/:S/realinstall/install/} DIRPRFX=${DIRPRFX}${entry}/ )
.endfor</programlisting>
- <para>In the above, <maketarget>_SUBDIRUSE</maketarget> is now
+ <para>In the above, <buildtarget>_SUBDIRUSE</buildtarget> is now
a macro which will execute the given commands when it is
listed as a dependency.</para>
@@ -370,18 +368,18 @@ PRI_LANG?= en_US.ISO8859-1
Basically, it is executed <emphasis>after</emphasis> the
instructions given in the build procedure it is listed as a
dependency to, and it does not adjust
- <makevar>.TARGET</makevar>, which is the variable which
+ <varname>.TARGET</varname>, which is the variable which
contains the name of the target currently being
built.</para>
<programlisting>clean: _SUBDIRUSE
rm -f ${CLEANFILES}</programlisting>
- <para>In the above, <maketarget>clean</maketarget> will use
- the <maketarget>_SUBDIRUSE</maketarget> macro after it has
+ <para>In the above, <buildtarget>clean</buildtarget> will use
+ the <buildtarget>_SUBDIRUSE</buildtarget> macro after it has
executed the instruction
<command>rm -f ${CLEANFILES}</command>. In effect, this
- causes <maketarget>clean</maketarget> to go further and
+ causes <buildtarget>clean</buildtarget> to go further and
further down the directory tree, deleting built files as it
goes <emphasis>down</emphasis>, not on the way back
up.</para>
@@ -391,20 +389,20 @@ PRI_LANG?= en_US.ISO8859-1
<itemizedlist>
<listitem>
- <para><maketarget>install</maketarget> and
- <maketarget>package</maketarget> both go down the
+ <para><buildtarget>install</buildtarget> and
+ <buildtarget>package</buildtarget> both go down the
directory tree calling the real versions of themselves
in the subdirectories
- (<maketarget>realinstall</maketarget> and
- <maketarget>realpackage</maketarget>
+ (<buildtarget>realinstall</buildtarget> and
+ <buildtarget>realpackage</buildtarget>
respectively).</para>
</listitem>
<listitem>
- <para><maketarget>clean</maketarget> removes files
+ <para><buildtarget>clean</buildtarget> removes files
created by the build process (and goes down the
directory tree too).
- <maketarget>cleandir</maketarget> does the same, and
+ <buildtarget>cleandir</buildtarget> does the same, and
also removes the object directory, if any.</para>
</listitem>
</itemizedlist>
@@ -449,11 +447,11 @@ PRI_LANG?= en_US.ISO8859-1
${MAKE} ${.TARGET:S/realpackage/package/:S/realinstall/install/} DIRPRFX=${DIRPRFX}${entry}/ )
.endfor</programlisting>
- <para>In the above, if <makevar>SUBDIR</makevar> is empty, no
+ <para>In the above, if <varname>SUBDIR</varname> is empty, no
action is taken; if it has one or more elements, the
instructions between <literal>.for</literal> and
<literal>.endfor</literal> would repeat for every element,
- with <makevar>entry</makevar> being replaced with the value
+ with <varname>entry</varname> being replaced with the value
of the current element.</para>
</sect3>
</sect2>
diff --git a/en_US.ISO8859-1/books/fdp-primer/docbook-markup/chapter.xml b/en_US.ISO8859-1/books/fdp-primer/docbook-markup/chapter.xml
index dd987da928..46f1573f99 100644
--- a/en_US.ISO8859-1/books/fdp-primer/docbook-markup/chapter.xml
+++ b/en_US.ISO8859-1/books/fdp-primer/docbook-markup/chapter.xml
@@ -30,11 +30,10 @@
$FreeBSD$
-->
-
-<chapter id="docbook-markup">
+<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:id="docbook-markup">
<title>DocBook Markup</title>
- <sect1 id="docbook-markup-introduction">
+ <sect1 xml:id="docbook-markup-introduction">
<title>Introduction</title>
<para>This chapter is an introduction to DocBook as it is used for
@@ -49,12 +48,10 @@
O'Reilly &amp; Associates to be a Document Type Definition
(<acronym>DTD</acronym>) for writing technical documentation
<footnote><para>A short history
- can be found under <ulink
- url="http://www.oasis-open.org/docbook/intro.shtml#d0e41">
- http://www.oasis-open.org/docbook/intro.shtml#d0e41</ulink>.</para></footnote>.
- Since 1998 it is maintained by the <ulink
- url="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=docbook">
- DocBook Technical Committee</ulink>. As such, and unlike
+ can be found under <link xlink:href="http://www.oasis-open.org/docbook/intro.shtml#d0e41">
+ http://www.oasis-open.org/docbook/intro.shtml#d0e41</link>.</para></footnote>.
+ Since 1998 it is maintained by the <link xlink:href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=docbook">
+ DocBook Technical Committee</link>. As such, and unlike
LinuxDoc and <acronym>XHTML</acronym>, DocBook is very heavily
oriented towards markup that describes <emphasis>what</emphasis>
something is, rather than describing <emphasis>how</emphasis> it
@@ -62,9 +59,9 @@
<para>The DocBook <acronym>DTD</acronym> is available from the
Ports Collection in the
- <filename role="package">textproc/docbook-xml-450</filename>
+ <package>textproc/docbook-xml-450</package>
port. It is automatically installed as part of the
- <filename role="package">textproc/docproj</filename>
+ <package>textproc/docproj</package>
port.</para>
<note>
@@ -89,7 +86,7 @@
</note>
</sect1>
- <sect1 id="docbook-markup-freebsd-extensions">
+ <sect1 xml:id="docbook-markup-freebsd-extensions">
<title>&os; Extensions</title>
<para>The &os; Documentation Project has extended the
@@ -111,25 +108,24 @@
&a.doceng;.</para>
</note>
- <sect2 id="docbook-markup-freebsd-extensions-elements">
+ <sect2 xml:id="docbook-markup-freebsd-extensions-elements">
<title>&os; Elements</title>
<para>The additional &