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

- MFH

Browse source
This commit is contained in:
Gabor Kovesdan 2013-03-20 21:05:33 +00:00
commit b1f6349527
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/projects/xml-tools/; revision=41274
199 changed files with 9371 additions and 9832 deletions
de_DE.ISO8859-1
books/handbook/geom
chapter.xml
htdocs
index.xslwhere.xml
share/xml
header.l10n.entnavibar.l10n.entnews.xmlpress.xml
el_GR.ISO8859-7/articles
bsdl-gpl
article.xml
compiz-fusion
article.xml
en_US.ISO8859-1
articles
bsdl-gpl
article.xml
casestudy-argentina.com
article.xml
committers-guide
article.xml
compiz-fusion
article.xml
contributors
article.xmlcontrib.additional.xmlcontrib.committers.xmlcontrib.develalumni.xmlcontrib.portmgralumni.xml
freebsd-update-server
article.xml
geom-class
article.xml
hubs
article.xml
p4-primer
article.xml
portbuild
article.xml
pr-guidelines
article.xml
releng
article.xml
wp-toolbox
article.xml
books
arch-handbook
book.xml
driverbasics
chapter.xml
developers-handbook/l10n
chapter.xml
faq
book.xml
fdp-primer
overview
chapter.xml
the-website
chapter.xml
translations
chapter.xml
handbook
advanced-networking
chapter.xml
audit
chapter.xml
basics
chapter.xml
config
chapter.xml
cutting-edge
chapter.xml
desktop
chapter.xml
disks
chapter.xml
eresources
chapter.xml
firewalls
chapter.xml
install
chapter.xml
introduction
chapter.xml
kernelconfig
chapter.xml
linuxemu
chapter.xml
mirrors
chapter.xml
multimedia
chapter.xml
ports
chapter.xml
ppp-and-slip
chapter.xml
printing
chapter.xml
security
chapter.xml
serialcomms
chapter.xml
users
chapter.xml
vinum
chapter.xml
virtualization
chapter.xml
x11
chapter.xml
porters-handbook
Makefilebook.xmluses.xml
htdocs
Makefileabout.xmladministration.xml
advocacy
index.xml
availability.xml
cgi
query-pr.cgi
developers
cvs.xml
docs
books.xml
features.xml
gnome
index.xsl
index.xsl
internal
MakefileREADME.mirrorabout.xmlfortunes.xmlmirror.xmlnew-account.xmlproposing-committers.xml
layout/css
layout.css
news
2012-compromise.xml
status
MakefileREADMEreport-2012-04-2012-06.xmlreport-2012-07-2012-09.xmlreport-2012-10-2012-12.xmlstatus.xml
platforms
amd64.xml
projects
newbies.xmlprojects.xml
releases
8.4R
Makefiledocbook.cssschedule.xml
Makefileindex.xml
releng
index.xml
search
sitemap.xml
security
security.xml
tutorials
index.xml
vendors.htmlwhere.xml
Show more

6
de_DE.ISO8859-1/books/handbook/geom/chapter.xml
View file

@ -4,8 +4,8 @@
The FreeBSD German Documentation Project
$FreeBSD$
$FreeBSDde: de-docproj/books/handbook/geom/chapter.xml,v 1.20 2011/12/19 15:25:08 bcr Exp $
basiert auf: 1.51
$FreeBSDde$
basiert auf: r39631
-->
<chapter id="GEOM">
@ -831,7 +831,7 @@ ufsid/486b6fc16926168e N/A ad4s1f</screen>
über alle Dateisystemtransaktionen angelegt, inklusive
aller Veränderungen, aus denen ein kompletter
Schreibvorgang besteht, bevor diese Änderungen (Metadaten
sowie tatsächliche Schreibvorgänge) physikalisch auf
sowie tatsächliche Schreibvorgänge) physisch auf
der Festplatte ausgeführt werden. Dieses Protokoll kann
später erneut aufgerufen werden, um diese Vorgänge
zu wiederholen (beispielsweise um Systeminkonsistenzen zu

22
de_DE.ISO8859-1/htdocs/index.xsl
View file

@ -5,8 +5,8 @@
]>
<!--
$FreeBSD$
$FreeBSDde: de-www/index.xsl,v 1.94 2012/02/23 17:35:11 jkois Exp $
basiert auf: 1.178
$FreeBSDde$
basiert auf: 41116
-->
<xsl:stylesheet version="1.0"
@ -56,7 +56,7 @@
Sicherheitsfunktionen und eine exzellente
Performance und wird deswegen beispielsweise von
einigen der größten <a
href="&enbase;/doc/&url.doc.langcode;/books/handbook/nutshell.html#INTRODUCTION-NUTSHELL-USERS">
href="&enbase;/doc/&url.doc.langcode;/books/handbook/nutshell.html#introduction-nutshell-users">
Internet-Seiten</a> und von zahlreichen Anbietern
eingebetteter Netzwerk- und Speichergeräte
eingesetzt.</p>
@ -81,11 +81,10 @@
<h2><a href="&base;/releases/">AKTUELLE VERSIONEN</a></h2>
<ul id="frontreleaseslist">
<li>
Produktion:&nbsp;<a href="&u.rel.announce;">&rel.current;</a>,&nbsp;
<a href="&u.rel2.announce;">&nbsp;&rel2.current;</a>
Produktion:&nbsp;<a href="&u.rel.announce;">&rel.current;</a>
</li>
<li>
Produktion (alt):&nbsp;<a href="&u.rel3.announce;">&rel3.current;</a>
Produktion (alt):&nbsp;<a href="&u.rel2.announce;">&rel2.current;</a>
</li>
<xsl:if test="'&beta.testing;' != 'IGNORE'">
<li>
@ -318,4 +317,15 @@
</div> <!-- FRONTMAIN -->
</div> <!-- FRONTCONTAINER -->
</xsl:template>
<xsl:template name="process.footer">
&copyright;
Die Marke FreeBSD ist eine eingetragene Marke der FreeBSD
Foundation und wird vom FreeBSD Project mit freundlicher Genehmigung
der <a
href="http://www.freebsdfoundation.org/documents/Guidelines.shtml">
FreeBSD Foundation</a> verwendet.
<a href="&base;/mailto.html" title="&header2.word.contact;">&header2.word.contact;</a>
</xsl:template>
</xsl:stylesheet>

12
de_DE.ISO8859-1/htdocs/where.xml
View file

@ -2,7 +2,7 @@
<!DOCTYPE html PUBLIC "-//FreeBSD//DTD XHTML 1.0 Transitional-Based Extension//EN"
"http://www.FreeBSD.org/XML/doc/share/xml/xhtml10-freebsd.dtd" [
<!ENTITY dedate "$FreeBSDde$">
<!ENTITY reference "basiert auf: r40536">
<!ENTITY reference "basiert auf: r41232">
<!ENTITY title "FreeBSD Bezugsquellen">
<!ENTITY url.rel "ftp://ftp.FreeBSD.org/pub/FreeBSD/releases">
]>
@ -146,6 +146,7 @@
<td><a href="&url.rel;/sparc64/&rel2.current;-RELEASE">[Distribution]</a></td>
<td><a href="&url.rel;/sparc64/ISO-IMAGES/&rel2.current;/">[ISO]</a></td>
</tr>
<!--
<tr>
<td colspan="2">FreeBSD &rel3.current;-RELEASE</td>
<td colspan="2"></td>
@ -157,27 +158,28 @@
<tr>
<td></td>
<td>amd64</td>
<!--<td><a href="&url.rel;/amd64/&rel3.current;-RELEASE">[Distribution]</a></td>-->
<td><a href="&url.rel;/amd64/&rel3.current;-RELEASE">[Distribution]</a></td>
<td colspan="2" align="right"><a href="&url.rel;/amd64/ISO-IMAGES/&rel3.current;/">[ISO]</a></td>
</tr>
<tr>
<td></td>
<td>i386</td>
<!--<td><a href="&url.rel;/i386/&rel3.current;-RELEASE">[Distribution]</a></td>-->
<td><a href="&url.rel;/i386/&rel3.current;-RELEASE">[Distribution]</a></td>
<td colspan="2" align="right"><a href="&url.rel;/i386/ISO-IMAGES/&rel3.current;/">[ISO]</a></td>
</tr>
<tr>
<td></td>
<td>pc98</td>
<!--<td><a href="&url.rel;/pc98/&rel3.current;-RELEASE">[Distribution]</a></td>-->
<td><a href="&url.rel;/pc98/&rel3.current;-RELEASE">[Distribution]</a></td>
<td colspan="2" align="right"><a href="&url.rel;/pc98/ISO-IMAGES/&rel3.current;/">[ISO]</a></td>
</tr>
<tr>
<td></td>
<td>sparc64</td>
<!--<td><<a href="&url.rel;/sparc64/&rel3.current;-RELEASE">[Distribution]</a></td>-->
<td><<a href="&url.rel;/sparc64/&rel3.current;-RELEASE">[Distribution]</a></td>
<td colspan="2" align="right"><a href="&url.rel;/sparc64/ISO-IMAGES/&rel3.current;/">[ISO]</a></td>
</tr>
-->
</tbody>
</table>

19
de_DE.ISO8859-1/share/xml/header.l10n.ent
View file

@ -1,13 +1,13 @@
<?xml version="1.0" encoding="iso-8859-1"?>
<!-- $FreeBSD$
$FreeBSDde$
basiert auf: r39675
basiert auf: r40575
-->
<!-- Components making up the standard headers and footers. -->
<!-- Override in the prolog <em>before</em> including this -->
<!-- file if necessary.-->
<!ENTITY copyright '<span xmlns="http://www.w3.org/1999/xhtml"><a href="&enbase;/search/index-site.html">Sitemap</a> | <a href="&enbase;/copyright/">Legal Notices</a> | &copy; 1995&ndash;2012 The FreeBSD Project. Alle Rechte vorbehalten.</span>'>
<!ENTITY copyright '<span xmlns="http://www.w3.org/1999/xhtml"><a href="&enbase;/search/index-site.html">Sitemap</a> | <a href="&enbase;/copyright/">Legal Notices</a> | &copy; 1995&ndash;2013 The FreeBSD Project. Alle Rechte vorbehalten.</span>'>
<!ENTITY author '<a href="&base;/index.html">Startseite</a> &nbsp; | &nbsp;
<a href="&base;/mailto.html">Ansprechpartner</a> &nbsp; | &nbsp;
<a href="&enbase;/copyright/index.html">Legal</a> &nbsp; | &nbsp;
@ -31,6 +31,7 @@
<li><a href="&base;/features.html">Eigenschaften</a></li>
<li><a href="&enbase;/advocacy/">Advocacy</a></li>
<li><a href="&enbase;/marketing/">Marketing</a></li>
<li><a href="&enbase;/privacy.html">Privacy Policy</a></li>
</ul>
</li>
</ul>
@ -68,7 +69,6 @@
<ul>
<li><a href="http://wiki.FreeBSD.org/IdeasPage">Projektideen</a></li>
<li><a href="http://svnweb.FreeBSD.org">SVN-Repository</a></li>
<li><a href="http://cvsweb.FreeBSD.org">CVS-Repository</a></li>
<li><a href="http://p4web.FreeBSD.org">Perforce-Repository</a></li>
</ul>
</li>
@ -87,7 +87,8 @@
<ul>
<li><a href="http://www.freebsdfoundation.org/">Foundation</a>
<ul>
<li><a href="http://www.freebsdfoundation.org/donate/">Spenden</a></li>
<li><a href="http://www.freebsdfoundation.org/donate/">Geldspende</a></li>
<li><a href="&enbase;/donations/">Hardwarespende</a></li>
</ul>
</li>
</ul>
@ -108,15 +109,17 @@
<div id="headerlogoright">
<h2 class="blockhide">Externe Links</h2>
<div id="SEARCHNAV">
<ul id="SEARCHNAVLIST">
<div id="searchnav">
<ul id="searchnavlist">
<!--
<li><a href="&enbase;/donations/" title="&header2.word.donate;">&header2.word.donate;</a></li>
<li class="last-child"><a href="&base;/mailto.html" title="&header2.word.contact;">&header2.word.contact;</a></li>
-->
</ul>
</div> <!-- SEARCHNAV -->
<div id="SEARCH">
<div id="search">
<form action="&cgibase;/search.cgi" method="get">
<div>
<h2 class="blockhide"><label for="WORDS">&header2.word.search;</label></h2>
@ -135,4 +138,4 @@
<!-- macro for webbuild paper -->
<!ENTITY webbuild '
<p xmlns="http://www.w3.org/1999/xhtml">Dieses Dokument beschreibt, wie man die FreeBSD Webseiten von Hand
mittels des CVS Repository aktualisiert und übersetzt.</p>'>
aus dem Subversion-Repository aktualisiert und übersetzt.</p>'>

11
de_DE.ISO8859-1/share/xml/navibar.l10n.ent
View file

@ -1,8 +1,8 @@
<?xml version="1.0" encoding="iso-8859-1"?>
<!--
$FreeBSD$
$FreeBSDde: de-www/share/xml/navibar.l10n.ent,v 1.33 2012/01/14 10:37:19 jkois Exp $
basiert auf: 1.37
$FreeBSDde$
basiert auf: r41115
-->
<!ENTITY nav.about '
@ -101,10 +101,11 @@
<li><a href="&base;/where.html">FreeBSD Bezugsquellen</a></li>
<li><a href="&base;/releases/">Release Informationen</a>
<ul>
<li>Produktivversion: <a href="&u.rel.announce;">&rel.current;</a>
<li>Produktivversion:<br />
<a href="&u.rel.announce;">&rel.current;</a></li>
<li>Alte Produktivversion:<br/>
<a href="&u.rel2.announce;">&rel2.current;</a></li>
<li>Alte Produktivversion:<br/> <a href="&u.rel3.announce;">&rel3.current;</a></li>
<li><a href="&base;/snapshots/">Snapshots</a></li>
<!-- <li><a href="&base;/snapshots/">Snapshots</a></li>-->
&beta.listitem;
&beta2.listitem;
</ul>

86
de_DE.ISO8859-1/share/xml/news.xml
View file

@ -4,7 +4,7 @@
<!--
$FreeBSD$
$FreeBSDde$
basiert auf: r40903
basiert auf: r41225
-->
<!-- Simple schema for FreeBSD Project news.
@ -38,6 +38,81 @@
<year>
<name>2013</name>
<month>
<name>3</name>
<day>
<name>14</name>
<event>
<title>Neuer technischer Mitarbeiter für die &os; Foundation:
Konstantin Belousov</title>
<p>Die &os;&nbsp;Foundation freut sich, bekanntgeben zu dürfen,
dass Konstantin Belousov als erster technischer Mitarbeiter
in Vollzeit für die Foundation tätig sein wird. Dies ist
ein wichtiger Meilenstein auf unserem Weg, FreeBSD auch 2013
zu unterstützen.</p>
<p>Weitere Informationen hierzu finden Sie <a
href="http://freebsdfoundation.blogspot.com/2013/03/foundation-announces-new-technical.html">hier</a>.</p>
</event>
</day>
<day>
<name>12</name>
<event>
<p>Neues Mitglied im Ports Management Team: <a
href="mailto:bdrewery@FreeBSD.org">Bryan Drewery</a></p>
</event>
</day>
<day>
<name>3</name>
<event>
<title>Statusreport Oktober-Dezember 2012</title>
<p>Der Statusreport für die Monate Oktober bis Dezember 2012
mit 27 Einträgen ist <a
href="&enbase;/news/status/report-2012-10-2012-12.html">
verfügbar</a>.</p>
</event>
<event>
<title>Statusreport Juli-September 2012</title>
<p>Der Statusreport für die Monate Juli bis September 2012
mit 12 Einträgen ist <a
href="&enbase;/news/status/report-2012-07-2012-09.html">
verfügbar</a>.</p>
</event>
</day>
</month>
<month>
<name>2</name>
<day>
<name>10</name>
<event>
<p>Neuer Committer: <a
href="mailto:pclin@FreeBSD.org">Po-Chien Lin</a> (ports)</p>
</event>
</day>
<day>
<name>1</name>
<event>
<p>Neuer Committer: <a
href="mailto:tmseck@FreeBSD.org">Thomas-Martin Seck</a> (ports)</p>
</event>
</day>
</month>
<month>
<name>1</name>
@ -221,8 +296,13 @@
<p>Das PC-BSD Team hat PC-BSD&nbsp;9.1 <a
href="http://blog.pcbsd.org/2012/12/pc-bsd-9-1-now-available/">veröffentlicht</a>.</p>
</event>
</day>
<event>
<p>Neuer Committer: <a
href="mailto:smh@FreeBSD.org">Steven Hartland</a> (src)</p>
</event>
</day>
<day>
<name>17</name>

17
de_DE.ISO8859-1/share/xml/press.xml
View file

@ -7,7 +7,7 @@
"freefall:/c/www/bsddoc/press/".
$FreeBSD$
$FreeBSDde$
basiert auf: r40864
basiert auf: r41004
-->
<press>
@ -17,6 +17,21 @@
<year>
<name>2013</name>
<month>
<name>2</name>
<story>
<name>2012 - A BSD Year in Retrospective</name>
<url>http://www.osnews.com/story/26787/2012_a_BSD_year_in_retrospective</url>
<site-name>OSnews</site-name>
<site-url>http://www.osnews.com/</site-url>
<date>14. Februar 2013</date>
<author>Julian Djamil</author>
<p>Ein Rückblick auf die aufregenden Entwicklungen, die 2012 in der
BSD-Betriebssystemfamilie stattgefunden haben. Näher eingegangen
wird dabei auf FreeBSD, NetBSD, OpenBSD sowie DragonflyBSD.</p>
</story>
</month>
<month>
<name>1</name>

32
el_GR.ISO8859-7/articles/bsdl-gpl/article.xml
View file

@ -13,24 +13,24 @@
<article lang="el">
<title>Γιατί να χρησιμοποιήσετε την άδεια BSD για το λογισμικό σας</title>
<articleinfo>
<articleinfo>
<authorgroup>
<author>
<firstname>Bruce</firstname>
<!-- middle initial: R. -->
<surname>Montague</surname>
<affiliation>
<address><email>brucem@alumni.cse.ucsc.edu</email></address>
</affiliation>
<firstname>Bruce</firstname>
<!-- middle initial: R. -->
<surname>Montague</surname>
<affiliation>
<address><email>brucem@alumni.cse.ucsc.edu</email></address>
</affiliation>
<contrib>Αρχικός συγγραφέας</contrib>
</author>
<author>
<firstname>Ãéþñãïò</firstname>
<surname>Êåñáìßäáò</surname>
<affiliation>
<address><email>keramida@FreeBSD.org</email></address>
</affiliation>
<firstname>Ãéþñãïò</firstname>
<surname>Êåñáìßäáò</surname>
<affiliation>
<address><email>keramida@FreeBSD.org</email></address>
</affiliation>
<contrib>Μετάφραση</contrib>
</author>
</authorgroup>
@ -114,7 +114,7 @@
Οι βασικοί λόγοι για τη δημοτικότητα του Unix ήταν ότι έτρεχε σε PDP-11,
ένα πολύ φτηνό υπολογιστή 16-bit, και ότι ήταν γραμμένο σε μια γλώσσα
υψηλού επιπέδου, η οποία ήταν εμφανώς καλή για προγραμματισμό
óõóôçìÜôùí. Ïé õðïëïãéóôÝò PDP-11 ôçò DEC åß÷áí, ïõóéáóôéêÜ, Ýíá áíïé÷ôü
óõóôçìÜôùí. Ïé õðïëïãéóôÝò PDP-11 ôçò DEC åß÷áí, ïõóéáóôéêÜ, Ýíá áíïé÷ôü
interface υλικού, σχεδιασμένο ακριβώς για να μπορούν οι
πελάτες να γράψουν το δικό τους λειτουργικό σύστημα. Πολλοί λοιπόν
έκαναν ακριβώς αυτό. Όπως έχει πει ο Ken Olsen, ιδρυτής της
@ -231,8 +231,7 @@
<para>
<quote>Αυτή η Γενική Δημόσια Άδεια δεν επιτρέπει την ενσωμάτωση του
ðñïãñÜììáôüò óáò óå åìðïñéêÜ ðñïãñÜììáôá.</quote>[1]
</para>
ðñïãñÜììáôüò óáò óå åìðïñéêÜ ðñïãñÜììáôá.</quote>[1]</para>
<para>Η
άδεια <ulink url="http://www.opensource.org/licenses/gpl-license.php">GPL</ulink>
@ -691,8 +690,7 @@
<sect1 id="addenda">
<title>Αναφορές</title>
<programlisting>
[1] http://www.gnu.org/licenses/gpl.html
<programlisting>[1] http://www.gnu.org/licenses/gpl.html
[2] http://archives.cnn.com/2000/TECH/computing/03/28/cyberpatrol.mirrors/

36
el_GR.ISO8859-7/articles/compiz-fusion/article.xml
View file

@ -1,6 +1,8 @@
<?xml version="1.0" encoding="iso-8859-7"?>
<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V4.5-Based Extension//EN"
"../../../share/xml/freebsd45.dtd">
"../../../share/xml/freebsd45.dtd" [
<!ENTITY nvidia "nVidia">
]>
<!--
@ -54,7 +56,7 @@
έχετε τα πλέον πρόσφατα τρισδιάστατα εφέ που προσφέρει το
<application>Compiz&nbsp;Fusion</application> χρησιμοποιώντας (αν
χρειάζεται) και την κατάλληλη έκδοση των προγραμμάτων οδήγησης
γραφικών της nVidia.</para>
γραφικών της &nvidia;.</para>
</abstract>
</articleinfo>
@ -66,7 +68,7 @@
Χρειάζονται, όμως, και κάποιες επιπλέον ρυθμίσεις, οι οποίες δεν
περιγράφονται στην τεκμηρίωση του port. Το άρθρο αυτό θα σας βοηθήσει
να ρυθμίσετε τον <application>&xorg;</application> server για
τρισδιάστατη λειτουργία, να ρυθμίσετε την nVidia κάρτα γραφικών σας,
τρισδιάστατη λειτουργία, να ρυθμίσετε την &nvidia; κάρτα γραφικών σας,
και τελικά να εγκαταστήσετε και να εκτελέσετε την εφαρμογή
<command>compiz</command>.</para>
@ -74,7 +76,7 @@
<itemizedlist>
<listitem>
<para>Πως να ρυθμίσετε το πιο πρόσφατο πρόγραμμα οδήγησης της nVidia
<para>Πως να ρυθμίσετε το πιο πρόσφατο πρόγραμμα οδήγησης της &nvidia;
(αν απαιτείται) για το σύστημα σας.</para>
</listitem>
@ -97,11 +99,11 @@
</sect1>
<sect1 id="nvidia-setup">
<title>Ρύθμιση των προγραμμάτων οδήγησης της nVidia για το &os;</title>
<title>Ρύθμιση των Προγραμμάτων Οδήγησης της &nvidia; Για Το &os;</title>
<para>Τα τρισδιάστατα εφέ απαιτούν αρκετή ισχύ επεξεργασίας από την
κάρτα γραφικών σας. Αν χρησιμοποιείτε κάποια κάρτα γραφικών που
βασίζεται σε κυκλώματα της nVidia, θα πρέπει να εγκαταστήσετε και να
βασίζεται σε κυκλώματα της &nvidia;, θα πρέπει να εγκαταστήσετε και να
ρυθμίσετε το πρόγραμμα οδήγησης που παρέχεται από την εταιρία για το
&os;, χρησιμοποιώντας την έκδοση που είναι κατάλληλη για το σύστημα
σας. Αν χρησιμοποιείτε κάποια άλλη κάρτα, που όμως γνωρίζετε ότι μπορεί
@ -112,18 +114,18 @@
<sect2 id="determine-driver">
<title>Προσδιορίστε το σωστό πρόγραμμα οδήγησης</title>
<para>Υπάρχουν διάφορες εκδόσεις των προγραμμάτων οδήγησης της nVidia
<para>Υπάρχουν διάφορες εκδόσεις των προγραμμάτων οδήγησης της &nvidia;
στη συλλογή των ports. Η επιλογή του σωστού προγράμματος για το
σύστημα σας, εξαρτάται από το μοντέλο (και την παλαιότητα) της κάρτας
γραφικών σας:</para>
<itemizedlist>
<listitem>
<para>Οι τελευταίες εκδόσεις των καρτών nVidia, υποστηρίζονται από
<para>Οι τελευταίες εκδόσεις των καρτών &nvidia;, υποστηρίζονται από
το port <filename role="package">x11/nvidia-driver</filename>.</para>
</listitem>
<listitem>
<para>Κάρτες της nVidia που ανήκουν στις σειρές GeForce 2MX/3/4
<para>Κάρτες της &nvidia; που ανήκουν στις σειρές GeForce 2MX/3/4
υποστηρίζονται από τα προγράμματα οδήγησης της σειράς 96 τα οποία
διατίθενται μέσω του port
<filename role="package">x11/nvidia-driver-96xx</filename>.</para>
@ -136,14 +138,14 @@
</listitem>
</itemizedlist>
<para>Στην πραγματικότητα, η nVidia παρέχει λεπτομερείς πληροφορίες
<para>Στην πραγματικότητα, η &nvidia; παρέχει λεπτομερείς πληροφορίες
σχετικά με το ποια κάρτα υποστηρίζεται από ποιο πρόγραμμα οδήγησης.
Οι πληροφορίες αυτές διατίθενται απευθείας από το δικτυακό τους τόπο:
<ulink url="http://www.nvidia.com/object/IO_32667.html"></ulink>.</para>
</sect2>
<sect2 id="install-driver">
<title>Εγκατάσταση του προγράμματος οδήγησης της nVidia</title>
<title>Εγκατάσταση του προγράμματος οδήγησης της &nvidia;</title>
<para>Αφού καθορίσετε το σωστό πρόγραμμα οδήγησης για την κάρτα σας,
η εγκατάσταση είναι το ίδιο απλή με οποιοδήποτε άλλη εφαρμογή της
@ -197,7 +199,7 @@
<programlisting>Driver "nvidia"</programlisting>
<para>Όταν ξεκινήσετε το γραφικό περιβάλλον με το συνήθη τρόπο, θα δείτε
την οθόνη χαιρετισμού της nVidia. Όλα θα πρέπει να λειτουργούν
την οθόνη χαιρετισμού της &nvidia;. Όλα θα πρέπει να λειτουργούν
κανονικά. Σημειώστε ωστόσο, ότι στο σημείο αυτό δεν έχει ακόμα
ρυθμιστεί το <application>&xorg;</application> για τρισδιάστατα εφέ.
Η ρύθμιση αυτή περιγράφεται παρακάτω.</para>
@ -217,7 +219,7 @@
</sect1>
<sect1 id="xorg-configuration">
<title>Ρύθμιση του xorg.conf για τρισδιάστατα εφέ</title>
<title>Ρύθμιση του <filename>xorg.conf</filename> για Τρισδιάστατα Εφέ</title>
<para>Πριν εγκαταστήσετε και εκτελέσετε το
<application>Compiz&nbsp;Fusion</application>, θα πρέπει να προσθέσετε
@ -280,13 +282,13 @@ Load "glx"
μπορείτε να κάνετε τις περισσότερες από τις παραπάνω ρυθμίσεις
δίνοντας τις ακόλουθες εντολές (ως root):</para>
<screen>&prompt.root; <userinput>nvidia-xconfig --add-argb-glx-visuals</userinput>
<screen>&prompt.root; <userinput>nvidia-xconfig --add-argb-glx-visuals</userinput>
&prompt.root; <userinput>nvidia-xconfig --composite</userinput>
&prompt.root; <userinput>nvidia-xconfig --depth=24</userinput></screen>
<para>Αν θέλετε να δείτε όλες τις δυνατότητες του παραπάνω
προγράμματος, δώστε την εντολή
<command>nvidia-xconfig -A | more</command>.</para>
<para>Αν θέλετε να δείτε όλες τις δυνατότητες του παραπάνω
προγράμματος, δώστε την εντολή
<command>nvidia-xconfig -A | more</command>.</para>
</note>
</sect1>

1
en_US.ISO8859-1/articles/bsdl-gpl/article.xml
View file

@ -20,7 +20,6 @@
<legalnotice id="trademarks" role="trademarks">
&tm-attrib.freebsd;
&tm-attrib.cvsup;
&tm-attrib.intel;
&tm-attrib.general;
</legalnotice>

1
en_US.ISO8859-1/articles/casestudy-argentina.com/article.xml
View file

@ -19,7 +19,6 @@
<legalnotice id="trademarks" role="trademarks">
&tm-attrib.freebsd;
&tm-attrib.cvsup;
&tm-attrib.intel;
&tm-attrib.xfree86;
&tm-attrib.general;

69
en_US.ISO8859-1/articles/committers-guide/article.xml
View file

@ -30,7 +30,6 @@
<legalnotice id="trademarks" role="trademarks">
&tm-attrib.freebsd;
&tm-attrib.coverity;
&tm-attrib.cvsup;
&tm-attrib.ibm;
&tm-attrib.intel;
&tm-attrib.sparc;
@ -313,9 +312,16 @@
<emphasis>r300894</emphasis>.</para>
<para>There are mechanisms in place to automatically merge
changes back from the Subversion repository to the
<acronym>CVS</acronym> one, so regular users should not notice
a difference, however developers most certainly will.</para>
changes back from the Subversion <literal>src</literal>
repository to the <acronym>CVS</acronym> repository for
some &os; branches (<literal>releng/6</literal> through
<literal>releng/9</literal>), however this is purely to
support pre-existing end-user installs and should not be
relied upon, recommended or advertised. Future branches
will not be exported to CVS at all. The
<literal>ports</literal> repository was exported to CVS
for a period of time to aid end user migration, but as of
28th February 2013 is no longer exported.</para>
<para>Subversion is not that different from
<acronym>CVS</acronym> when it comes to daily use, but there
@ -441,11 +447,11 @@
<sect3>
<title>Checkout from a Mirror</title>
<para>You can check out a working copy from a mirror by simply
<para>Check out a working copy from a mirror by
substituting the mirror's <acronym>URL</acronym> for
<literal>svn+ssh://svn.freebsd.org/base</literal>. This can
be an official mirror or a mirror you maintain yourself
using <command>svnsync</command> or similar.</para>
be an official mirror or a mirror maintained by
using <command>svnsync</command>.</para>
<para>There is a serious disadvantage to this method: every
time something is to be committed, a <command>svn switch
@ -456,8 +462,8 @@
the same UUID, some hacking of the local repository's UUID
has to occur before it is possible to start using it.</para>
<para>Unlike with <acronym>CVS</acronym> and
<acronym>csup</acronym>, the hassle of a local
<para>Unlike with <acronym>CVS</acronym>,
the hassle of a local
<command>svnsync</command> mirror probably is not worth it
unless the network connectivity situation or other factors
demand it. If it is needed, see the end of this chapter for
@ -478,9 +484,15 @@
<para>For the base repository, HEAD refers to the -CURRENT
tree. For example, <filename>head/bin/ls</filename> is what
would go into <filename>/usr/src/bin/ls</filename> in a
release. Some other key locations are:</para>
release. Some key locations are:</para>
<itemizedlist>
<listitem>
<para><emphasis>/head/</emphasis>
which corresponds to <literal>HEAD</literal>, also known as
<literal>-CURRENT</literal>.
</para>
</listitem>
<listitem>
<para><emphasis>/stable/<replaceable>n</replaceable></emphasis>
which corresponds to
@ -675,10 +687,14 @@
<para>It is possible to anonymously check out the &os;
repository with Subversion. This will give access to a
read-only tree that can be updated, but not committed
to. To do this, use one of the following commands:</para>
to. To do this, use the following command:</para>
<screen>&prompt.user; <userinput>svn co svn://svn.freebsd.org/base/head /usr/src</userinput>
&prompt.user; <userinput>svn co http://svn.freebsd.org/base/head /usr/src</userinput></screen>
<screen>&prompt.user; <userinput>svn co <replaceable>https://svn0.us-west.FreeBSD.org</replaceable>/base/head /usr/src</userinput></screen>
<para>Select the closest mirror and verify the mirror server
certificate from the list of <ulink
url="&url.books.handbook;/svn-mirrors.html">Subversion
mirror sites</ulink>.</para>
</sect3>
<sect3>
@ -2297,32 +2313,19 @@ ControlPersist yes</screen>
</itemizedlist>
<para>You can run a local copy of GNATS, and then integrate the FreeBSD
GNATS tree in to it using CVSup. Then you can run GNATS commands
locally.
This lets you query the PR database without needing to be connected to
the Internet.</para>
GNATS tree by creating an <application>rsync</application> mirror.
Then you can run GNATS commands locally, allowing you to query the PR
database without an Internet connection.</para>
<sect2>
<title>Mirroring the GNATS Tree</title>
<para>It is possible to mirror the GNATS database by adding this line
to your <filename>supfile</filename>. Note that since
GNATS is not under CVS control it has no tag, so if you are adding
it to your existing <filename>supfile</filename> it should appear
before any <quote>tag=</quote> entry as these remain active once set.</para>
<para>It is possible to mirror the GNATS database by installing
<filename role="package">net/rsync</filename>, and
executing:</para>
<programlisting>gnats release=current prefix=/usr</programlisting>
<screen>&prompt.user; <userinput>rsync -va rsync://bit0.us-west.freebsd.org/FreeBSD-bit/gnats .</userinput></screen>
<para>This will place the FreeBSD GNATS tree in
<filename>/usr/gnats</filename>. You can use a
<emphasis>refuse</emphasis> file to control which categories to
receive. For example, to only receive <literal>docs</literal> PRs,
put this line in
<filename>/usr/local/etc/cvsup/sup/refuse</filename><footnote>
<para>The precise path depends on the <literal>*default
base</literal> setting in your
<filename>supfile</filename>.</para>
</footnote>.</para>
</sect2>
<sect2 id="gnatstools">

4
en_US.ISO8859-1/articles/compiz-fusion/article.xml
View file

@ -135,9 +135,7 @@
<note>
<para>Make sure to update your ports tree using your favorite method
(like <application>csup</application>,
<application>CVSup</application> or
<application>portsnap</application>) before you install any
(e.g., <application>portsnap</application>) before you install any
application from the ports system. Graphics drivers and the
desktop effects programs are under heavy development, and are
updated regularly.</para>

1
en_US.ISO8859-1/articles/contributors/article.xml
View file

@ -12,7 +12,6 @@
<legalnotice id="trademarks" role="trademarks">
&tm-attrib.freebsd;
&tm-attrib.cvsup;
&tm-attrib.sun;
&tm-attrib.general;
</legalnotice>

35
en_US.ISO8859-1/articles/contributors/contrib.additional.xml
View file

@ -4407,6 +4407,11 @@
<email>doogie@forbidden-donut.anet-stl.com</email></para>
</listitem>
<listitem>
<para>Javad Kouhi
<email>javad.kouhi@gmail.com</email></para>
</listitem>
<listitem>
<para>Javier Martin Rueda
<email>jmrueda@diatel.upm.es</email></para>
@ -4912,6 +4917,11 @@
<email>jgm@berkeley.edu</email></para>
</listitem>
<listitem>
<para>John Mehr
<email>jcm@visi.com</email></para>
</listitem>
<listitem>
<para>John Merryweather Cooper
<email>jmcoopr@webmail.bmi.net</email></para>
@ -5331,6 +5341,11 @@
<email>vode@snakemail.hut.fi</email></para>
</listitem>
<listitem>
<para>Kai Wang
<email>kaiwang27@gmail.com</email></para>
</listitem>
<listitem>
<para>Kaleb S. Keithley
<email>kaleb@ics.com</email></para>
@ -7338,6 +7353,11 @@
<email>root@cooltrainer.org</email></para>
</listitem>
<listitem>
<para>Nikolai Lifanov
<email>lifanov@mail.lifanov.com</email></para>
</listitem>
<listitem>
<para>Nikos Kokkalis
<email>nickkokkalis@gmail.com</email></para>
@ -10077,11 +10097,6 @@
<email>thomas.vogt@bsdunix.ch</email></para>
</listitem>
<listitem>
<para>Thomas-Martin Seck
<email>tmseck@netcologne.de</email></para>
</listitem>
<listitem>
<para>Thorsten Greiner
<email>thorsten@tgreiner.net</email></para>
@ -10247,6 +10262,11 @@
<email>tomasv@megalogika.lt</email></para>
</listitem>
<listitem>
<para>Tomasz Walaszek
<email>tmwalaszek@gmail.com</email></para>
</listitem>
<listitem>
<para>Tomaz<!-- &zcaron; not rendered?--> Muraus
<email>kami@k5-storitve.net</email></para>
@ -10688,6 +10708,11 @@
<email>rstevens@noao.edu</email></para>
</listitem>
<listitem>
<para>Waitman Gobble
<email>waitman@waitman.net</email></para>
</listitem>
<listitem>
<para>Walt Howard
<email>howard@ee.utah.edu</email></para>

28
en_US.ISO8859-1/articles/contributors/contrib.committers.xml
View file

@ -187,10 +187,6 @@
<para>&a.acm;</para>
</listitem>
<listitem>
<para>&a.carvay;</para>
</listitem>
<listitem>
<para>&a.gahr;</para>
</listitem>
@ -435,10 +431,6 @@
<para>&a.decke;</para>
</listitem>
<listitem>
<para>&a.shige;</para>
</listitem>
<listitem>
<para>&a.gallatin;</para>
</listitem>
@ -519,10 +511,6 @@
<para>&a.jhale;</para>
</listitem>
<listitem>
<para>&a.randi;</para>
</listitem>
<listitem>
<para>&a.smh;</para>
</listitem>
@ -547,10 +535,6 @@
<para>&a.ghelmer;</para>
</listitem>
<listitem>
<para>&a.mux;</para>
</listitem>
<listitem>
<para>&a.wen;</para>
</listitem>
@ -695,10 +679,6 @@
<para>&a.jkim;</para>
</listitem>
<listitem>
<para>&a.zack;</para>
</listitem>
<listitem>
<para>&a.jceel;</para>
</listitem>
@ -1303,6 +1283,10 @@
<para>&a.matthew;</para>
</listitem>
<listitem>
<para>&a.tmseck;</para>
</listitem>
<listitem>
<para>&a.stas;</para>
</listitem>
@ -1635,10 +1619,6 @@
<para>&a.wollman;</para>
</listitem>
<listitem>
<para>&a.keichii;</para>
</listitem>
<listitem>
<para>&a.joerg;</para>
</listitem>

85
en_US.ISO8859-1/articles/contributors/contrib.develalumni.xml
View file

@ -2,6 +2,35 @@
<!-- $FreeBSD$ -->
<itemizedlist>
<listitem>
<para>&a.randi; (2010 - 2012)</para>
</listitem>
<listitem>
<para>&a.zack; (2010 - 2012)</para>
</listitem>
<listitem>
<para>&a.erik; (2008 - 2012)</para>
</listitem>
<listitem>
<para>&a.carvay; (2008 - 2012)</para>
</listitem>
<listitem>
<para>&a.lulf; (2007 - 2012)</para>
</listitem>
<listitem>
<para>&a.mnag; (2005 - 2012)</para>
</listitem>
<listitem>
<para>&a.ceri; (2002 - 2012)</para>
</listitem>
<listitem>
<para>Doug Barton (2000 - 2012)</para>
</listitem>
@ -18,26 +47,6 @@
<para>&a.steve; (1996 - 2012)</para>
</listitem>
<listitem>
<para>&a.erik; (2008 - 2012)</para>
</listitem>
<listitem>
<para>&a.ceri; (2002 - 2012)</para>
</listitem>
<listitem>
<para>&a.mnag; (2005 - 2012)</para>
</listitem>
<listitem>
<para>&a.lulf; (2007 - 2012)</para>
</listitem>
<listitem>
<para>&a.niels; (2004 - 2011)</para>
</listitem>
<listitem>
<para>&a.jacula; (2010 - 2011)</para>
</listitem>
@ -62,6 +71,10 @@
<para>&a.anray; (2005 - 2011)</para>
</listitem>
<listitem>
<para>&a.niels; (2004 - 2011)</para>
</listitem>
<listitem>
<para>&a.sergei; (2003 - 2011)</para>
</listitem>
@ -70,6 +83,10 @@
<para>&a.krion; (2003 - 2011)</para>
</listitem>
<listitem>
<para>&a.mux; (2002 - 2011)</para>
</listitem>
<listitem>
<para>&a.hm; (1998 - 2011)</para>
</listitem>
@ -86,6 +103,10 @@
<para>&a.snb; (2009 - 2010)</para>
</listitem>
<listitem>
<para>&a.cbzimmer; (2009 - 2010)</para>
</listitem>
<listitem>
<para>&a.bushman; (2007 - 2010)</para>
</listitem>
@ -206,6 +227,10 @@
<para>&a.tg; (1995 - 2009)</para>
</listitem>
<listitem>
<para>&a.kishore; (2007 - 2008)</para>
</listitem>
<listitem>
<para>&a.twinterg; (2006 - 2008)</para>
</listitem>
@ -258,6 +283,10 @@
<para>&a.dhartmei; (2004 - 2008)</para>
</listitem>
<listitem>
<para>&a.sah; (2004 - 2008)</para>
</listitem>
<listitem>
<para>&a.rsm; (2003 - 2008)</para>
</listitem>
@ -270,6 +299,10 @@
<para>&a.eik; (2003 - 2008)</para>
</listitem>
<listitem>
<para>&a.matk; (2003 - 2008)</para>
</listitem>
<listitem>
<para>&a.seanc; (2002 - 2008)</para>
</listitem>
@ -338,6 +371,10 @@
<para>&a.andy; (1999 - 2008)</para>
</listitem>
<listitem>
<para>&a.shige; (1999 - 2008)</para>
</listitem>
<listitem>
<para>&a.hosokawa; (1998 - 2008)</para>
</listitem>
@ -478,6 +515,10 @@
<para>&a.arun; (2003 - 2006)</para>
</listitem>
<listitem>
<para>&a.am; (2003 - 2006)</para>
</listitem>
<listitem>
<para>&a.scop; (2002 - 2006)</para>
</listitem>
@ -498,6 +539,10 @@
<para>&a.znerd; (2001 - 2006)</para>
</listitem>
<listitem>
<para>&a.keichii; (2001 - 2006)</para>
</listitem>
<listitem>
<para>&a.ue; (2001 - 2006)</para>
</listitem>

8
en_US.ISO8859-1/articles/contributors/contrib.portmgralumni.xml
View file

@ -2,6 +2,14 @@
<!-- $FreeBSD$ -->
<itemizedlist>
<listitem>
<para>&a.beat; (2011 - 2013)</para>
</listitem>
<listitem>
<para>&a.linimon; (2004 - 2013)</para>
</listitem>
<listitem>
<para>&a.pav; (2006 - 2012)</para>
</listitem>

42
en_US.ISO8859-1/articles/freebsd-update-server/article.xml
View file

@ -20,6 +20,7 @@
<year>2009</year>
<year>2010</year>
<year>2011</year>
<year>2013</year>
<holder role="mailto:jgh@FreeBSD.org">Jason Helfman</holder>
</copyright>
@ -38,8 +39,8 @@
<abstract>
<para>This article describes building an internal &fbus.ap;.
The <ulink
url="&url.base;/cgi/cvsweb.cgi/projects/freebsd-update-server/">freebsd-update-server</ulink> software
is written by &a.cperciva;, current Security Officer of &os;.
url="http://svnweb.freebsd.org/base/user/cperciva/freebsd-update-build/">freebsd-update-server</ulink>
software is written by &a.cperciva;, Security Officer Emeritus of &os;.
For users that think it is convenient to update their systems
against an official update server, building their own &fbus.ap; may
help to extend its functionality by supporting manually-tweaked
@ -116,11 +117,11 @@
<title>Configuration: Installation &amp; Setup</title>
<para>Download the <ulink
url="&url.base;/cgi/cvsweb.cgi/projects/freebsd-update-server/">freebsd-update-server</ulink>
software as a <ulink
url="&url.base;/cgi/cvsweb.cgi/projects/freebsd-update-server/freebsd-update-server.tar.gz?tarball=1">tar archive</ulink>,
or use &man.csup.1; and the <literal>projects-all</literal>
collection.</para>
url="http://svnweb.freebsd.org/base/user/cperciva/freebsd-update-build/">
freebsd-update-server</ulink> software by installing <filename
role="package">devel/subversion </filename>, and execute:</para>
<screen>&prompt.user; <userinput>svn co http://svn.freebsd.org/base/user/cperciva/freebsd-update-build freebsd-update-server</userinput></screen>
<para>Update <filename>scripts/build.conf</filename> appropriately.
It is sourced during all build operations.</para>
@ -351,9 +352,9 @@ world|base|/usr/lib/libalias_ftp.a
<warning>
<para>During this second build cycle, the network time protocol
daemon, &man.ntpd.8;, is turned off. Per &a.cperciva;, current
Security Officer of &os;, "the <ulink
url="&url.base;/cgi/cvsweb.cgi/projects/freebsd-update-server/">freebsd-update-server</ulink>
daemon, &man.ntpd.8;, is turned off. Per &a.cperciva;,
Security Officer Emeritus of &os;, "the <ulink
url="http://svnweb.freebsd.org/base/user/cperciva/freebsd-update-build/">freebsd-update-server</ulink>
build code needs to identify timestamps which are stored in files so
that they can be ignored when comparing builds to determine which
files need to be updated. This timestamp-finding works by doing two
@ -776,7 +777,6 @@ the new builds.</screen>
}
</screen>
</listitem>
<!-- this tip will speed up your build process, however it is not necessary -->
<listitem>
<para>Adding <option>-j <replaceable>NUMBER</replaceable></option>
flags to <maketarget>buildworld</maketarget> and
@ -799,28 +799,12 @@ the new builds.</screen>
</listitem>
<listitem>
<!-- Parse error. I don't understand what this paragraph suggests or
recommends. Also, why do we need to block RSTs? I don't really
like gratuitous blocking of RST, ICMP or other packets. Our
kernel can rate-limit most of the "strange" packets alredy. -->
<!-- there is a bug in earlier versions of the software that get the updates, and not blocking them will result in failure to update systems -->
<para>Create a <ulink
url="&url.books.handbook;/firewalls.html">firewall</ulink>
rule to block outgoing RST packets. Due to a bug noted <ulink
url="http://lists.freebsd.org/pipermail/freebsd-stable/2009-April/049578.html">in a posting</ulink>
on the &a.stable; in April 2009, there may be
time-outs and failures when updating a system.</para>
</listitem>
<!-- this tip is not necessary, however if you wish to retain mirrors and redundancy, this tip will help you. -->
<listitem>
<para>Create an appropriate <ulink
url="&url.books.handbook;/network-dns.html">DNS</ulink>
SRV record for the update server, and put others behind it with
variable weights. Using this facility will provide update
mirrors.</para>
mirrors, however this tip is not necessary unless you wish to
provide a redundant service.</para>
<screen> _http._tcp.update.myserver.com. IN SRV 0 2 80 host1.myserver.com.
SRV 0 1 80 host2.myserver.com.

1
en_US.ISO8859-1/articles/geom-class/article.xml
View file

@ -19,7 +19,6 @@
<legalnotice id="trademarks" role="trademarks">
&tm-attrib.freebsd;
&tm-attrib.cvsup;
&tm-attrib.intel;
&tm-attrib.general;
</legalnotice>

7
en_US.ISO8859-1/articles/hubs/article.xml
View file

@ -775,13 +775,6 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f -l -R -T /anoncvstmp --all
applies. This means:
</para>
<procedure>
<step>
<para>
Look at available mirrors in your country.
The <ulink url="http://mirrorlist.FreeBSD.org/">FreeBSD
Mirror Database</ulink> can help you with this.
</para>
</step>
<step>
<para>
Check for those which provide fastest access

23
en_US.ISO8859-1/articles/p4-primer/article.xml
View file

@ -34,7 +34,7 @@
<para>The &os; project uses the <application>Perforce</application>
version control system to manage experimental projects that are
not ready for the main CVS repository.</para>
not ready for the main Subversion repository.</para>
<sect2 id="resources">
<title>Availability, Documentation, and Resources</title>
@ -65,9 +65,9 @@
<para>The &os; <application>Perforce</application> server is
hosted on <hostid role="fqdn">perforce.freebsd.org</hostid>,
port <literal>1666</literal>. The repository is browsable
online at <ulink url="http://perforce.freebsd.org"></ulink>.
online at <ulink url="http://p4web.freebsd.org"></ulink>.
Some portions of the repository are also automatically exported
to a number of <application>CVSup</application> servers.</para>
to a number of legacy <application>CVSup</application> servers.</para>
</sect2>
</sect1>
@ -331,7 +331,8 @@
with &os;. Frequent submits of changes to the server are also
encouraged.</para>
<para>The <application>Perforce</application> repository (the
<para>sSimilar to <application>Subversion</application>, the
<application>Perforce</application> repository (the
<quote>depot</quote>) is a single flat tree. Every file, whether
a unique creation or a derivative from a branch, is accessible via
a simple path under the server <filename
@ -803,12 +804,12 @@
</sect1>
<sect1 id="freebsd-cvs-and-p4">
<title>Interactions between &os; CVS and Perforce</title>
<title>Interactions between &os; Subversion and Perforce</title>
<para>The &os; <application>Perforce</application> and CVS
repositories are completely separate. However, changes to CVS are
<para>The &os; <application>Perforce</application> and <application>Subversion</application>
repositories are completely separate. However, changes to Subversion are
tracked at near-real-time in <application>Perforce</application>.
Every 2 minutes, the CVS server is polled for updates in the HEAD
Every 2 minutes, the Subversion server is polled for updates in the HEAD
branch, and those updates are committed to
<application>Perforce</application> in the <filename
class="directory">//depot/vendor/freebsd/...</filename> tree. This
@ -819,10 +820,10 @@
should be done so that your tree stays up to date and avoids
conflicts with mainline development.</para>
<para>The bridge between CVS and <application>Perforce</application>
is one-way; changes to CVS will be reflected in
<para>The bridge between Subversion and <application>Perforce</application>
is one-way; changes to Subversion will be reflected in
<application>Perforce</application>, but changes in Perforce will
not be reflected in CVS. On request, some parts of the
not be reflected in Subversion. On request, some parts of the
<application>Perforce</application> repo can be exported to
<application>CVSup</application> and made available for
distribution that way. Contact the &os;

130
en_US.ISO8859-1/articles/portbuild/article.xml
View file

@ -1498,6 +1498,14 @@ umount: Cleanup of /x/tmp/8-exp/chroot/53837/compat/linux/proc failed!
command is no longer used.</para>
</note>
</step>
<step>
<para>Decide if you will be using a local
<application>squid</application> cache on the client,
instead of the server. It is more efficient to run it
on the server. If you are doing that, skip the "squid"
steps below.)</para>
</step>
</procedure>
</sect2>
@ -1624,12 +1632,21 @@ options NFSSERVER # Network Filesystem Server</programlist
</listitem>
<listitem>
<para>Also add the following users:</para>
<para>If you are using <application>ganglia</application>
for monitoring, add the following user:</para>
<programlisting>squid:*:100:100::0:0:User &amp;:/usr/local/squid:/bin/sh
ganglia:*:102:102::0:0:User &amp;:/usr/local/ganglia:/bin/sh</programlisting>
<programlisting>ganglia:*:102:102::0:0:User &amp;:/usr/local/ganglia:/bin/sh</programlisting>
<para>Add them to <filename>etc/group</filename> as well.</para>
<para>Add it to <filename>etc/group</filename> as well.</para>
</listitem>
<listitem>
<para>If you are using a local <application>squid</application>
cache on the client, add the following user:</para>
<programlisting>squid:*:100:100::0:0:User &amp;:/usr/local/squid:/bin/sh</programlisting>
<para>Add it to <filename>etc/group</filename> as well.</para>
</listitem>
<listitem>
@ -1679,13 +1696,19 @@ nfs_client_enable="YES"
ntpd_enable="YES"
sendmail_enable="NONE"
sshd_enable="YES"
sshd_program="/usr/local/sbin/sshd"
sshd_program="/usr/local/sbin/sshd"</programlisting>
gmond_enable="YES"
squid_enable="YES"
<para>If you are using <application>ganglia</application>
for monitoring, add the following</para>
<programlisting>gmond_enable="YES"</programlisting>
<para>If you are using a local <application>squid</application>
cache on the client, add the following</para>
<programlisting>squid_enable="YES"
squid_chdir="<filename>/<replaceable>usr2</replaceable>/squid/logs</filename>"
squid_pidfile="<filename>/<replaceable>usr2</replaceable>/squid/logs/squid.pid</filename>"</programlisting>
<para>Required entries for VMWare-based nodes:</para>
<programlisting>vmware_guest_vmmemctl_enable="YES"
@ -1771,13 +1794,21 @@ squid_pidfile="<filename>/<replaceable>usr2</replaceable>/squid/logs/squid.pid</
<para>Install the following ports:</para>
<programlisting>net/rsync
security/openssh-portable (with HPN on)
security/sudo
sysutils/ganglia-monitor-core (with GMETAD off)
www/squid (with SQUID_AUFS on)</programlisting>
security/sudo</programlisting>
<para>There is a WIP to create a meta-port, but it is not yet
complete.</para>
<para>You may also wish to install:</para>
<programlisting>security/openssh-portable (with HPN on)</programlisting>
<para>If you are using <application>ganglia</application>
for monitoring, install the following:</para>
<programlisting>sysutils/ganglia-monitor-core (with GMETAD off)</programlisting>
<para>If you are using a local <application>squid</application>
cache on the client, install the following</para>
<programlisting>www/squid (with SQUID_AUFS on)</programlisting>
</step>
<step>
@ -1798,7 +1829,8 @@ www/squid (with SQUID_AUFS on)</programlisting>
<itemizedlist>
<listitem>
<para>Modify
<para>If you are using <application>ganglia</application>,
modify
<filename>usr/local/etc/gmond.conf</filename>:</para>
<screen>21,22c21,22
@ -1846,7 +1878,8 @@ touch /tmp/.boot_finished</programlisting>
</listitem>
<listitem>
<para>Modify
<para>If you are using a local <application>squid</application>
cache, modify,
<filename>usr/local/etc/squid/squid.conf</filename>:</para>
<screen>288,290c288,290
@ -1921,8 +1954,12 @@ portbuild ALL=(ALL) NOPASSWD: ALL</programlisting>
<screen>&prompt.root; <userinput>mkdir portbuild</userinput>
&prompt.root; <userinput>chown portbuild:portbuild portbuild</userinput>
&prompt.root; <userinput>mkdir pkgbuild</userinput>
&prompt.root; <userinput>chown portbuild:portbuild pkgbuild</userinput>
&prompt.root; <userinput>mkdir squid</userinput>
&prompt.root; <userinput>chown portbuild:portbuild pkgbuild</userinput></screen>
<para>If you are using a local <application>squid</application>
cache:</para>
<screen>&prompt.root; <userinput>mkdir squid</userinput>
&prompt.root; <userinput>mkdir squid/cache</userinput>
&prompt.root; <userinput>mkdir squid/logs</userinput>
&prompt.root; <userinput>chown -R squid:squid squid</userinput></screen>
@ -1943,7 +1980,8 @@ portbuild ALL=(ALL) NOPASSWD: ALL</programlisting>
</step>
<step>
<para>As root, initialize the <command>squid</command>
<para>If you are using a local <application>squid</application>
cache, as root, initialize the <command>squid</command>
directories:</para>
<screen><userinput>squid -z</userinput></screen>
@ -2030,8 +2068,6 @@ MASTER_SITE_OVERRIDE= \
<para>Suggested values:</para>
<programlisting>disconnected=1
http_proxy="http://localhost:3128/"
squid_dir=<filename>/<replaceable>usr2</replaceable>/squid</filename>
scratchdir=<filename>/<replaceable>usr2</replaceable>/pkgbuild</filename>
client_user=portbuild
sudo_cmd="sudo -H"
@ -2040,6 +2076,18 @@ rsync_gzip=-z
infoseek_host=localhost
infoseek_port=<replaceable>${tunelled-tcp-port}</replaceable></programlisting>
<para>If you will be using <application>squid</application>
on the client:</para>
<programlisting>http_proxy="http://localhost:3128/"
squid_dir=<filename>/<replaceable>usr2</replaceable>/squid</filename></programlisting>
<para>If, instead, you will be using <application>squid</application>
on the server:</para>
<programlisting>
http_proxy="http://<replaceable>servername</replaceable>:3128/"</programlisting>
<para>Possible other values:</para>
<programlisting>use_md_swap=1
@ -2061,7 +2109,8 @@ ssh_cmd="/usr/local/bin/ssh"</programlisting>
</step>
<step>
<para>Add an appropriate <literal>data_source</literal> entry to
<para>If you are using <application>ganglia</application>,
add an appropriate <literal>data_source</literal> entry to
<filename>/usr/local/etc/gmetad.conf</filename>:</para>
<programlisting>data_source "<replaceable>arch</replaceable>/<replaceable>location</replaceable> Package Build Cluster" 30 <replaceable>hostname</replaceable></programlisting>
@ -2107,7 +2156,7 @@ ssh_cmd="/usr/local/bin/ssh"</programlisting>
</procedure>
<para>This step needs to be taken by a <literal>portmgr</literal>
acting as <literal>root</literal>:</para>
acting as <literal>portbuild</literal>:</para>
<procedure>
<step>
@ -2348,7 +2397,7 @@ zfs destroy -r a/snap/src-<replaceable>old-branch</replaceable></screen>
<listitem>
<para>As the <literal>portbuild</literal> user, run</para>
<screen>&prompt.user; /a/portbuild/admin/tools/addarch <replaceable>arch</replaceable></screen>
<screen>&prompt.user; /a/portbuild/tools/addarch <replaceable>arch</replaceable></screen>
</listitem>
</itemizedlist>
@ -2477,9 +2526,6 @@ zfs destroy -r a/snap/src-<replaceable>old-branch</replaceable></screen>
<sect1 id="new-head-node">
<title>How to configure a new head node (pointyhat instance)</title>
<para>Please talk to Mark Linimon before making any changes
to this section.</para>
<sect2 id="pointyhat-basics">
<title>Basic installation</title>
@ -2534,8 +2580,6 @@ fsck_y_enable="YES"
apache22_enable="YES"
apache_flags=""
apache_pidfile="/var/run/httpd.pid"
gmetad_enable="YES"
gmond_enable="YES"
inetd_enable="YES"
inetd_flags="-l -w"
mountd_enable="YES"
@ -2548,6 +2592,17 @@ rpc_lockd_enable="NO"
rpc_statd_enable="YES"
sendmail_enable="NONE"
smartd_enable="YES"</programlisting>
<para>If you are using <application>ganglia</application>,
add:</para>
<programlisting>gmetad_enable="YES"
gmond_enable="YES"</programlisting>
<para>If you will be using a <application>squid</application>
cache on the server, rather than the clients:</para>
<programlisting>squid_enable="YES"</programlisting>
</step>
<step>
@ -2600,8 +2655,6 @@ devel/py-setuptools
devel/subversion
net/nc
net/rsync
sysutils/ganglia-monitor-core (with GMETAD off)
sysutils/ganglia-webfrontend (compile with -DWITHOUT_X11)
www/apache22 (with EXT_FILTER)</programlisting>
<para>Expect those to bring in, among others:</para>
@ -2610,6 +2663,17 @@ www/apache22 (with EXT_FILTER)</programlisting>
lang/perl-5.14 (or successor)
lang/python27 (or sucessor)</programlisting>
<para>If you are using <application>ganglia</application>,
add:</para>
<programlisting>sysutils/ganglia-monitor-core (with GMETAD off)
sysutils/ganglia-webfrontend (compile with -DWITHOUT_X11)</programlisting>
<para>If you will be using a <application>squid</application>
cache on the server, rather than the clients:</para>
<programlisting>www/squid (with SQUID_AUFS on)</programlisting>
<para>The following ports (or their latest successors) are strongly suggested:</para>
<programlisting>devel/ccache
@ -2732,7 +2796,7 @@ sh -x ./tmp/mkportbuild
<step>
<para>Select an <application>svn</application> repository
and export it. See the
<ulink url="&url.books.handbook;/mirrors-svn.html">&os; Handbook</ulink>
<ulink url="&url.books.handbook;/svn-mirrors.html">&os; Handbook</ulink>
for the currently supported list.</para>
<screen>&prompt.root; export VCS_REPOSITORY=<replaceable>svn://svn0.us-east.FreeBSD.org</replaceable></screen>
@ -3015,7 +3079,7 @@ qmanager</programlisting>
</step>
<step>
<para>Install <filename>/a/srcbuild/admin/crontabs/portbuild</filename> as
<para>Install <filename>/a/portbuild/admin/crontabs/srcbuild</filename> as
the <username>srcbuild</username> crontab via
<command>crontab -u srcbuild -e</command>.</para>
</step>

2
en_US.ISO8859-1/articles/pr-guidelines/article.xml
View file

@ -900,7 +900,7 @@
<listitem>
<para>When completing the &man.send-pr.1; template, the submitter
set Confidential to <literal>yes</literal>. (Since we allow
anyone to mirror GNATS via <application>cvsup</application>,
anyone to mirror GNATS via <application>rsync</application>,
our PRs are public information. Security alerts should
therefore not be sent via GNATS but instead via email to
the Security Team.)</para>

429
en_US.ISO8859-1/articles/releng/article.xml
View file

@ -9,7 +9,9 @@
<articleinfo>
<!-- This paper was presented at BSDCon Europe in Brighton, UK on
November 11, 2001 -->
November 11, 2001. -->
<!-- The content in this paper was updated in March 2013 to
reflect the current FreeBSD Release process. -->
<confgroup>
<confdates>November 2001</confdates>
<conftitle>BSDCon Europe</conftitle>
@ -45,6 +47,16 @@
<releaseinfo>$FreeBSD$</releaseinfo>
<abstract>
<para>
<warning>
<para>2013/02/26: This document is outdated and does not
accurately describe the current release procedures of the
&os; Release Engineering team. The &os; Release
Engineering team is currently reviewing this document and
will publish updated content soon.
</para>
</warning>
</para>
<para>This paper describes the approach used by the &os;
release engineering team to make production quality releases
of the &os; Operating System. It details the methodology
@ -62,8 +74,14 @@
<para>The development of &os; is a very open process. &os; is
comprised of contributions from thousands of people around the
world. The &os; Project provides anonymous
<acronym>CVS</acronym>[1] access to the general public so that
world. The &os; Project provides
Subversion
<footnote>
<simpara>
Subversion, <ulink url="http://subversion.apache.org"></ulink>
</simpara>
</footnote>
access to the general public so that
others can have access to log messages, diffs (patches) between
development branches, and other productivity enhancements that
formal source code management provides. This has been a huge help
@ -71,9 +89,20 @@
think everyone would agree that chaos would soon manifest if write
access was opened up to everyone on the Internet. Therefore only
a <quote>select</quote> group of nearly 300 people are given write
access to the <acronym>CVS</acronym> repository. These
<emphasis>committers[5]</emphasis> are responsible for the bulk of
&os; development. An elected <emphasis>core-team[6]</emphasis>
access to the Subversion repository. These
<ulink url="&url.articles.contributors;/article.html#staff-committers">committers</ulink>
<footnote>
<simpara>
<ulink url="&url.articles.contributors;/article.html#staff-committers">FreeBSD committers</ulink>
</simpara>
</footnote>
are responsible for the bulk of &os; development. An elected
<ulink url="&url.base;/administration.html#t-core">Core Team</ulink>
<footnote>
<simpara>
<ulink url="&url.base;/administration.html#t-core">&os; Core Team</ulink>
</simpara>
</footnote>
of very senior developers provides some level of direction over
the project.</para>
@ -82,16 +111,15 @@
for polishing the development system into a production quality
release. To solve this dilemma, development continues on two
parallel tracks. The main development branch is the
<emphasis>HEAD</emphasis> or <emphasis>trunk</emphasis> of our CVS
<emphasis>HEAD</emphasis> or <emphasis>trunk</emphasis> of our Subversion
tree, known as <quote>&os;-CURRENT</quote> or
<quote>-CURRENT</quote> for short.</para>
<para>A more stable branch is maintained, known as
<quote>&os;-STABLE</quote> or <quote>-STABLE</quote> for short.
Both branches live in a master CVS repository in California and
are replicated via <application
class="software">CVSup</application>[2] to mirrors all over the
world. &os;-CURRENT[7] is the <quote>bleeding-edge</quote> of
Both branches live in a master Subversion repository on a machine
maintained by the &os; Project.
&os;-CURRENT is the <quote>bleeding-edge</quote> of
&os; development where all new changes first enter the system.
&os;-STABLE is the development branch from which major releases
are made. Changes go into this branch at a different pace, and
@ -105,52 +133,64 @@
class="resource">ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/</systemitem>.
The widespread availability of binary release snapshots, and the
tendency of our user community to keep up with -STABLE development
with CVSup and <quote><command>make</command>
<maketarget>world</maketarget></quote>[7] helps to keep
with Subversion and <quote><command>make</command>
<maketarget>buildworld</maketarget></quote>
<footnote>
<simpara>
<ulink url="&url.books.handbook;/makeworld.html">Rebuilding "world"</ulink>
</simpara>
</footnote>
helps to keep
&os;-STABLE in a very reliable condition even before the
quality assurance activities ramp up pending a major
release.</para>
<para>Bug reports and feature requests are continuously submitted by
users throughout the release cycle. Problems reports are entered into our
<application class="software">GNATS</application>[8] database
<application class="software">GNATS</application> database
<footnote>
<simpara>
GNATS: The GNU Bug Tracking System
<ulink url="http://www.gnu.org/software/gnats"></ulink>
</simpara>
</footnote>
through email, the &man.send-pr.1; application, or via the web
interface provided at <ulink
url="http://www.FreeBSD.org/send-pr.html"></ulink>.</para>
<para>To service our most conservative users, individual release
branches were introduced with &os;&nbsp;4.3.
These release branches are created shortly before a final release
is made. After the release goes out, only the most critical
security fixes and additions are merged onto the release branch.
In addition to source updates via CVS, binary patchkits are
In addition to source updates via Subversion, binary patchkits are
available to keep systems on the
<emphasis>RELENG_<replaceable>X</replaceable>_<replaceable>Y</replaceable></emphasis>
branches updated.</para>
<sect2>
<title>What this article describes</title>
<para>The following sections of this article describe:</para>
<variablelist>
<varlistentry>
<term><xref linkend="release-proc"/></term>
<listitem>
<para>The different phases of the release engineering process
leading up to the actual system build.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><xref linkend="release-build"/></term>
<listitem>
<para>The actual build process.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><xref linkend="extensibility"/></term>
@ -158,7 +198,7 @@
<para>How the base release may be extended by third parties.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><xref linkend="lessons-learned"/></term>
@ -252,41 +292,37 @@
<sect3 id="rel-branch">
<title>Creating the Release Branch</title>
<para>As described in the introduction, the
<literal>RELENG_<replaceable>X</replaceable>_<replaceable>Y</replaceable></literal>
release branch is a relatively new addition to our release
engineering
methodology. The first step in creating this branch is to
ensure that you are working with the newest version of the
<literal>RELENG_<replaceable>X</replaceable></literal> sources
that you want to branch <emphasis>from</emphasis>.</para>
<screen>/usr/src&prompt.root; <userinput>cvs update -rRELENG_4 -P -d</userinput></screen>
<para>The next step is to create a branch point
<emphasis>tag</emphasis>, so that diffs against the start of
the branch are easier with CVS:</para>
<screen>/usr/src&prompt.root; <userinput>cvs rtag -rRELENG_4 RELENG_4_8_BP src</userinput></screen>
<para>And then a new branch tag is created with:</para>
<screen>/usr/src&prompt.root; <userinput>cvs rtag -b -rRELENG_4_8_BP RELENG_4_8 src</userinput></screen>
<note>
<para><emphasis>The
<literal>RELENG_<replaceable>*</replaceable></literal> tags
are restricted for use by the CVS-meisters and release
engineers.</emphasis></para>
<para>In all examples below, <literal>&dollar;FSVN</literal>
refers to the location of the &os; Subversion repository,
<literal>svn+ssh://svn.freebsd.org/base/</literal>.</para>
</note>
<sidebar>
<para>A <quote><emphasis>tag</emphasis></quote> is CVS
vernacular for a label that identifies the source at a specific point
in time. By tagging the tree, we ensure that future release builders
will always be able to use the same source we used to create the
official &os; Project releases.</para>
</sidebar>
<para>The layout of &os; branches in Subversion is
described in the <ulink url="&url.articles.committers-guide;/subversion-primer.html#subversion-primer-base-layout">Committer's Guide</ulink>.
The first step in creating a branch is to
identify the revision of the
<literal>stable/<replaceable>X</replaceable></literal> sources
that you want to branch <emphasis>from</emphasis>.</para>
<screen>&prompt.root; <userinput>svn log -v $FSVN/stable/9</userinput></screen>
<para>The next step is to create the <emphasis>release branch</emphasis>
</para>
<screen>&prompt.root; <userinput>svn cp $FSVN/stable/9@REVISION $FSVN/releng/9.2</userinput></screen>
<para>This branch can be checked out:</para>
<screen>&prompt.root; <userinput>svn co $FSVN/releng/9.2 src</userinput></screen>
<note>
<para>Creating <literal>releng</literal> branch and <literal>release</literal>
tags are restricted to
<ulink url="&url.base;/administration.html#t-subversion">Subversion administrators</ulink>
and the <ulink url="&url.base;/administration.html#t-re">Release Engineering Team</ulink>.
</para>
</note>
<mediaobject>
<imageobject>
@ -467,7 +503,14 @@
<para><application>Sysinstall</application> should be updated to note
the number of available ports and the amount of disk space required
for the Ports Collection[4]. This information is currently kept in
for the Ports Collection.
<footnote>
<simpara>
&os; Ports Collection
<ulink url="http://www.FreeBSD.org/ports"></ulink>
</simpara>
</footnote>
This information is currently kept in
<filename>src/usr.sbin/sysinstall/dist.c</filename>.</para>
<para>After the release has been built, a number of file should
@ -514,47 +557,29 @@
</sect3>
<sect3 id="versionbump-major">
<title>Preparing a new major release branch
(RELENG_<replaceable>X</replaceable>)</title>
<para>When a new major release branch, such as
<literal>RELENG_6</literal> is branched from HEAD, some
additional files must be updated before releases can be made
from this new branch.</para>
<itemizedlist>
<listitem>
<para><filename>src/share/examples/cvsup/stable-supfile</filename>
- must be updated to point to the new -STABLE branch, when
applicable.</para>
</listitem>
</itemizedlist>
</sect3>
<sect3>
<title>Creating Release Tags</title>
<title>Creating the Release Tag</title>
<para>When the final release is ready, the following command
will create the <literal>RELENG_4_8_0_RELEASE</literal>
will create the <literal>release/9.2.0</literal>
tag.</para>
<screen>/usr/src&prompt.root; <userinput>cvs rtag -rRELENG_4_8 RELENG_4_8_0_RELEASE src</userinput></screen>
<screen>&prompt.root; <userinput>svn cp $FSVN/releng/9.2 $FSVN/release/9.2.0</userinput></screen>
<para>The Documentation and Ports managers are responsible for
tagging the respective trees with the <literal>RELEASE_4_8_0</literal>
tagging their respective trees with the <literal>tags/RELEASE_9_2_0</literal>
tag.</para>
<para>Occasionally, a last minute fix may be required
<emphasis>after</emphasis> the final tags have been created.
In practice this is not a problem, since <acronym>CVS</acronym>
allows tags to be manipulated with <command>cvs
tag -d <replaceable>tagname filename</replaceable></command>.
It is very important that any last minute changes be tagged
appropriately as part of the release. &os; releases must
always be reproducible. Local hacks in the release
engineer's environment are not acceptable.</para>
<sidebar>
<para>When the Subversion <command>svn cp</command> command
is used to create a <emphasis>release tag</emphasis>,
this identifies the source at a specific point in time.
By creating tags, we ensure that future release builders
will always be able to use the exact same source we used to create the
official &os; Project releases.</para>
</sidebar>
</sect3>
</sect2>
</sect1>
@ -565,79 +590,38 @@ applicable.</para>
<para>&os; <quote>releases</quote> can be built by anyone with a
fast machine and access to a source repository. (That should be
everyone, since we offer anonymous CVS! See The Handbook for
everyone, since we offer Subversion access !
See the
<ulink url="&url.books.handbook;/svn.html">Subversion section
in the Handbook</ulink> for
details.) The <emphasis>only</emphasis> special requirement is
that the &man.md.4; device must be available. If the
device is not loaded into your kernel, then the kernel module
should be automatically loaded when &man.mdconfig.8; is executed
during the boot media creation phase. All of the tools necessary
to build a release are available from the CVS repository in
to build a release are available from the Subversion repository in
<filename>src/release</filename>. These tools aim to provide a
consistent way to build &os; releases. A complete release can
actually be built with only a single command, including the
creation of <acronym>ISO</acronym> images suitable for burning to
CDROM, installation floppies, and an FTP install directory. This
command is aptly named <command>make
release</command>.</para>
CDROM or DVD, and an FTP install directory. &man.release.7; fully
documents the <command>src/release/generate-release.sh</command>
script which is used to build a release. <command>generate-release.sh</command>
is a wrapper around the Makefile target: <command>make release</command>.</para>
<sect2>
<title><command>make release</command></title>
<title>Building a Release</title>
<para>To successfully build a release, you must first populate
<filename>/usr/obj</filename> by running <command>make
world</command> or simply
<command>make
buildworld</command>. The release
target requires several variables be set properly to build a
release:</para>
<para>&man.release.7; documents the exact commands required to
build a &os; release. The following sequences of commands can build
an 9.2.0 release:</para>
<itemizedlist>
<listitem>
<para><makevar>CHROOTDIR</makevar> - The directory to be used as the
chroot environment for the entire release build.</para>
</listitem>
<screen>&prompt.root; <userinput>cd /usr/src/release</userinput></screen>
<screen>&prompt.root; <userinput>sh generate-release.sh release/9.2.0 /local3/release</userinput></screen>
<listitem>
<para><makevar>BUILDNAME</makevar> - The name of the release to be
built.</para>
</listitem>
<listitem>
<para><makevar>CVSROOT</makevar> - The location of a CVS Repository.
</para>
</listitem>
<listitem>
<para><makevar>RELEASETAG</makevar> - The CVS tag corresponding to the
release you would like to build.</para>
</listitem>
</itemizedlist>
<para>If you do not already have access to a local CVS
repository, then you may mirror one with <ulink
url="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/synching.html#CVSUP">CVSup</ulink>.
The supplied supfile,
<filename>/usr/share/examples/cvsup/cvs-supfile</filename>, is
a useful starting point for mirroring the CVS
repository.</para>
<para>If <makevar>RELEASETAG</makevar> is omitted, then the
release will be built from the <literal>HEAD</literal> (aka -CURRENT) branch.
Releases built from this branch are normally referred to as
<quote>-CURRENT snapshots</quote>.</para>
<para>There are many other variables available to customize the
release build. Most of these variables are documented at the
top of <filename>src/release/Makefile</filename>. The exact
command used to build the official &os;&nbsp;4.7 (x86) release
was:</para>
<screen><command>make <literal>release CHROOTDIR=/local3/release \
BUILDNAME=4.7-RELEASE \
CVSROOT=/host/cvs/usr/home/ncvs \
RELEASETAG=RELENG_4_7_0_RELEASE</literal>
</command>
</screen>
<para>After running these commands, all prepared release
files are available in <filename>/local3/release/R</filename>
directory.</para>
<para>The release <filename>Makefile</filename> can be broken down into several distinct
steps.</para>
@ -651,7 +635,7 @@ applicable.</para>
</listitem>
<listitem>
<para>Checkout from CVS of a clean version of the system source,
<para>Checkout from Subversion of a clean version of the system source,
documentation, and ports into the release build hierarchy.</para>
</listitem>
@ -696,20 +680,11 @@ applicable.</para>
and so on.)</para>
</listitem>
<listitem>
<para>Build of the <quote>crunched</quote> binaries used for
installation floppies.</para>
</listitem>
<listitem>
<para>Package up distribution tarballs of the binaries and sources.
</para>
</listitem>
<listitem>
<para>Create the boot media and a <quote>fixit</quote> floppy.</para>
</listitem>
<listitem>
<para>Create FTP installation hierarchy.</para>
</listitem>
@ -939,64 +914,20 @@ applicable.</para>
installation and administration tools, for example, but we cannot
be expected to answer questions about it.</para>
<sect2>
<title>Creating Customized Boot floppies</title>
<para>Many sites have complex requirements that may require
additional kernel modules or userland tools be added to the
installation floppies. The <quote>quick and dirty</quote> way
to accomplish this would be to modify the staging directory of
an existing <command>make release</command> build hierarchy:</para>
<itemizedlist>
<listitem>
<para>Apply patches or add additional files inside the chroot
release build directory.</para>
</listitem>
<listitem>
<para><command>rm
${CHROOTDIR}/usr/obj/usr/src/release/release.[59]</command></para>
</listitem>
<listitem>
<para>rebuild &man.sysinstall.8;, the kernel, or whatever
parts of the system your change affected.</para>
</listitem>
<listitem>
<para><command>chroot ${CHROOTDIR} ./mk floppies
</command></para>
</listitem>
</itemizedlist>
<para>New release floppies will be located in
<filename>${CHROOTDIR}/R/stage/floppies</filename>.</para>
<para>Alternatively, the
<filename>boot.flp</filename> make
target can be called, or the filesystem
creating script,
<filename>src/release/scripts/doFS.sh</filename>, may be invoked
directly.</para>
<para>Local patches may also be supplied to the release build by
defining the <makevar>LOCAL_PATCH</makevar> variable in <command>make
release</command>.
</para>
</sect2>
<sect2>
<title>Scripting <command>sysinstall</command></title>
<para>The &os; system installation and configuration tool,
&man.sysinstall.8;, can be scripted to provide automated installs
for large sites. This functionality can be used in conjunction
with &intel; PXE[12] to bootstrap systems from the network, or
via custom boot floppies with a sysinstall script. An example
sysinstall script is available in the CVS tree as
<filename>src/usr.sbin/sysinstall/install.cfg</filename>.</para>
with &intel; PXE
<footnote>
<simpara>
<ulink url="&url.books.handbook;/network-pxe-nfs.html"></ulink>
</simpara>
</footnote>
to bootstrap systems from the network.
</para>
</sect2>
</sect1>
@ -1088,59 +1019,31 @@ applicable.</para>
community. I would also like to thank &a.rgrimes;, &a.phk;, and others
who worked on the release engineering tools in the very early days
of &os;. This article was influenced by release engineering
documents from the CSRG[13], the NetBSD Project[10], and John
Baldwin's proposed release engineering process notes[11].</para>
</sect1>
<!-- Reference / Biblio Section -->
<sect1 id="biblio">
<title>References</title>
<para>[1] CVS - Concurrent Versions System
<ulink url="http://www.cvshome.org"></ulink></para>
<para>[2] CVSup - The CVS-Optimized General Purpose Network File Distribution
System <ulink url="http://www.polstra.com/projects/freeware/CVSup"></ulink>
</para>
<para>[3] <ulink url="http://pointyhat.FreeBSD.org"></ulink></para>
<para>[4] &os; Ports Collection
<ulink url="http://www.FreeBSD.org/ports"></ulink></para>
<para>[5] &os; Committers <ulink
url="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributors/staff-committers.html"></ulink>
</para>
<para>[6] &os; Core Team
<ulink url="&url.base;/administration.html#t-core"></ulink></para>
<para>[7] &os; Handbook
<ulink url="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook"></ulink>
</para>
<para>[8] GNATS: The GNU Bug Tracking System
<ulink url="http://www.gnu.org/software/gnats"></ulink>
</para>
<para>[9] &os; PR Statistics
<ulink url="http://www.FreeBSD.org/prstats/index.html"></ulink></para>
<para>[10] NetBSD Developer Documentation: Release Engineering
<ulink url="http://www.NetBSD.org/developers/releng/index.html"></ulink>
</para>
<para>[11] John Baldwin's &os; Release Engineering Proposal
<ulink url="http://people.FreeBSD.org/~jhb/docs/releng.txt"></ulink>
</para>
<para>[12] PXE Jumpstart Guide
<ulink
url="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/pxe/index.html"></ulink>
</para>
<para>[13] Marshall Kirk McKusick, Michael J. Karels, and Keith Bostic:
<ulink url="http://docs.FreeBSD.org/44doc/papers/releng.html">
<emphasis>The Release Engineering of 4.3BSD</emphasis></ulink>
documents from the CSRG
<footnote>
<simpara>
Marshall Kirk McKusick, Michael J. Karels, and Keith Bostic:
<ulink url="http://docs.FreeBSD.org/44doc/papers/releng.html">
<emphasis>The Release Engineering of 4.3BSD</emphasis></ulink>
</simpara>
</footnote>
,
the NetBSD Project ,
<footnote>
<simpara>
NetBSD Developer Documentation: Release Engineering
<ulink url="http://www.NetBSD.org/developers/releng/index.html"></ulink>
</simpara>
</footnote>
, and John
Baldwin's proposed release engineering process notes.
<footnote>
<simpara>
John Baldwin's &os; Release Engineering Proposal
<ulink url="http://people.FreeBSD.org/~jhb/docs/releng.txt"></ulink>
</simpara>
</footnote>
</para>
</sect1>
</article>

1
en_US.ISO8859-1/articles/wp-toolbox/article.xml
View file

@ -24,7 +24,6 @@
<legalnotice id="trademarks" role="trademarks">
&tm-attrib.freebsd;
&tm-attrib.cvsup;
&tm-attrib.intel;
&tm-attrib.microsoft;
&tm-attrib.symantec;

100
en_US.ISO8859-1/books/arch-handbook/book.xml
View file

@ -40,20 +40,20 @@
<releaseinfo>$FreeBSD$</releaseinfo>
<abstract>
<para>Welcome to the &os; Architecture Handbook. This manual is a
<para>Welcome to the &os; Architecture Handbook. This manual is
a
<emphasis>work in progress</emphasis> and is the work of many
individuals. Many sections do not yet exist and some of those
that do exist need to be updated. If you are interested in
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 <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>
</abstract>
</bookinfo>
@ -94,14 +94,7 @@
<title>* I386</title>
<para>Talk about <literal>i386</literal> specific &os;
architecture.</para>
</chapter>
<chapter id="alpha">
<title>* Alpha</title>
<para>Talk about the architectural specifics of
FreeBSD/alpha.</para>
architecture.</para>
</chapter>
<chapter id="ia64">
@ -116,21 +109,21 @@
<title>* SPARC64</title>
<para>Talk about <literal>SPARC64</literal> specific &os;
architecture.</para>
architecture.</para>
</chapter>
<chapter id="amd64">
<title>* AMD64</title>
<para>Talk about <literal>AMD64</literal> specific &os;
architecture.</para>
architecture.</para>
</chapter>
<chapter id="powerpc">
<title>* PowerPC</title>
<para>Talk about <literal>PowerPC</literal> specific &os;
architecture.</para>
architecture.</para>
</chapter>
</part>
-->
@ -138,41 +131,48 @@
<part id="appendices">
<title>Appendices</title>
<bibliography>
<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>
</authorgroup>
<copyright><year>1996</year><holder>Addison-Wesley Publishing Company,
Inc.</holder></copyright>
<isbn>0-201-54979-4</isbn>
<publisher>
<publishername>Addison-Wesley Publishing Company, Inc.</publishername>
</publisher>
<title>The Design and Implementation of the 4.4 BSD Operating System</title>
<pagenums>1-2</pagenums>
<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>
</authorgroup>
<copyright>
<year>1996</year>
<holder>Addison-Wesley Publishing Company, Inc.</holder>
</copyright>
<isbn>0-201-54979-4</isbn>
<publisher>
<publishername>Addison-Wesley Publishing Company, Inc.</publishername>
</publisher>
<title>The Design and Implementation of the 4.4 BSD Operating System</title>
<pagenums>1-2</pagenums>
</biblioentry>
</bibliography>
</bibliography>
</part>
&chap.index;

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

@ -188,7 +188,7 @@ KMOD=skeleton
#include &lt;sys/uio.h&gt; /* uio struct */
#include &lt;sys/malloc.h&gt;
#define BUFFERSIZE 256
#define BUFFERSIZE 255
/* Function prototypes */
static d_open_t echo_open;
@ -207,7 +207,7 @@ static struct cdevsw echo_cdevsw = {
};
struct s_echo {
char msg[BUFFERSIZE];
char msg[BUFFERSIZE + 1];
int len;
};
@ -222,7 +222,6 @@ MALLOC_DEFINE(M_ECHOBUF, "echobuffer", "buffer for echo module");
* This function is called by the kld[un]load(2) system calls to
* determine what actions to take when a module is loaded or unloaded.
*/
static int
echo_loader(struct module *m __unused, int what, void *arg __unused)
{
@ -241,8 +240,8 @@ echo_loader(struct module *m __unused, int what, void *arg __unused)
if (error != 0)
break;
/* kmalloc memory for use by this driver */
echomsg = malloc(sizeof(*echomsg), M_ECHOBUF, M_WAITOK);
echomsg = malloc(sizeof(*echomsg), M_ECHOBUF, M_WAITOK |
M_ZERO);
printf("Echo device loaded.\n");
break;
case MOD_UNLOAD:
@ -258,7 +257,8 @@ echo_loader(struct module *m __unused, int what, void *arg __unused)
}
static int
echo_open(struct cdev *dev __unused, int oflags __unused, int devtype __unused, struct thread *p __unused)
echo_open(struct cdev *dev __unused, int oflags __unused, int devtype __unused,
struct thread *td __unused)
{
int error = 0;
@ -267,7 +267,8 @@ echo_open(struct cdev *dev __unused, int oflags __unused, int devtype __unused,
}
static int
echo_close(struct cdev *dev __unused, int fflag __unused, int devtype __unused, struct thread *p __unused)
echo_close(struct cdev *dev __unused, int fflag __unused, int devtype __unused,
struct thread *td __unused)
{
uprintf("Closing device \"echo\".\n");
@ -279,19 +280,20 @@ echo_close(struct cdev *dev __unused, int fflag __unused, int devtype __unused,
* echo_write() and returns it to userland for accessing.
* uio(9)
*/
static int
echo_read(struct cdev *dev __unused, struct uio *uio, int ioflag __unused)
{
int error, amt;
size_t amt;
int error;
/*
* How big is this read operation? Either as big as the user wants,
* or as big as the remaining data
* or as big as the remaining data. Note that the 'len' does not
* include the trailing null character.
*/
amt = MIN(uio-&gt;uio_resid, uio-&gt;uio_offset &gt;= echomsg-&gt;len + 1 ? 0 :
echomsg-&gt;len + 1 - uio-&gt;uio_offset);
amt = MIN(uio-&gt;uio_resid, echomsg-&gt;len - uio-&gt;uio_offset);
uio-&gt;uio_offset += amt;
if ((error = uiomove(echomsg-&gt;msg, amt, uio)) != 0)
uprintf("uiomove failed!\n");
@ -302,13 +304,11 @@ echo_read(struct cdev *dev __unused, struct uio *uio, int ioflag __unused)
* echo_write takes in a character string and saves it
* to buf for later accessing.
*/
static int
echo_write(struct cdev *dev __unused, struct uio *uio, int ioflag __unused)
{
int error, amt;
/* Copy the string in from user memory to kernel memory */
size_t amt;
int error;
/*
* We either write from the beginning or are appending -- do
@ -317,32 +317,25 @@ echo_write(struct cdev *dev __unused, struct uio *uio, int ioflag __unused)
if (uio-&gt;uio_offset != 0 &amp;&amp; (uio-&gt;uio_offset != echomsg-&gt;len))
return (EINVAL);
/*
* This is new message, reset length
*/
/* This is a new message, reset length */
if (uio-&gt;uio_offset == 0)
echomsg-&gt;len = 0;
/* NULL character should be overridden */
if (echomsg-&gt;len != 0)
echomsg-&gt;len--;
/* Copy the string in from user memory to kernel memory */
amt = MIN(uio-&gt;uio_resid, (BUFFERSIZE - echomsg-&gt;len));
error = uiomove(echomsg-&gt;msg + uio-&gt;uio_offset, amt, uio);
/* Now we need to null terminate, then record the length */
echomsg-&gt;len += amt + 1;
uio-&gt;uio_offset += amt + 1;
echomsg-&gt;msg[echomsg-&gt;len - 1] = 0;
/* Now we need to null terminate and record the length */
echomsg-&gt;len = uio-&gt;uio_offset;
echomsg-&gt;msg[echomsg-&gt;len] = 0;
if (error != 0)
uprintf("Write failed: bad address!\n");
return (error);
}
DEV_MODULE(echo,echo_loader,NULL);</programlisting>
DEV_MODULE(echo, echo_loader, NULL);</programlisting>
</example>
<para>With this driver loaded try:</para>

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

@ -240,7 +240,7 @@ printf(getstr(1));
#include &lt;err.h&gt;
...
if (!S_ISDIR(st.st_mode))
err(1, "argument is not a directory");
errx(1, "argument is not a directory");
</programlisting>
<para>This can be transformed to print an error message by

342
en_US.ISO8859-1/books/faq/book.xml
View file

@ -16,18 +16,12 @@
<!ENTITY rel2.releng "<symbol>RELENG_8</symbol>">
<!ENTITY rel2.relengdate "August 2009">
<!ENTITY rel2.packages "packages-8-stable">
<!ENTITY rel3.current "7.4">
<!ENTITY rel3.relx "7.<replaceable>X</replaceable>">
<!ENTITY rel3.stable "<emphasis>7-STABLE</emphasis>">
<!ENTITY rel3.releng "<symbol>RELENG_7</symbol>">
<!ENTITY rel3.relengdate "October 2007">
<!ENTITY rel3.packages "packages-7-stable">
]>
<book lang='en'>
<bookinfo>
<title>Frequently Asked Questions for &os;
&rel3.relx;, &rel2.relx;, and &rel.relx;</title>
&rel2.relx;, and &rel.relx;</title>
<corpauthor>The &os; Documentation Project</corpauthor>
@ -64,11 +58,9 @@
&tm-attrib.intel;
&tm-attrib.linux;
&tm-attrib.microsoft;
&tm-attrib.mips;
&tm-attrib.netbsd;
&tm-attrib.opengroup;
&tm-attrib.oracle;
&tm-attrib.sgi;
&tm-attrib.sparc;
&tm-attrib.sun;
&tm-attrib.general;
</legalnotice>
@ -76,41 +68,26 @@
<releaseinfo>$FreeBSD$</releaseinfo>
<abstract>
<para>This is the FAQ for &os; versions
&rel3.relx;, &rel2.relx; and &rel.relx;.
All entries are assumed to be
relevant to &os; &rel3.relx; and later,
unless otherwise noted. If you are interested in helping with
this project, send email to the &a.doc;. The latest version of
<para>This is the FAQ for &os; versions &rel2.relx; and
&rel.relx;. Every effort has been made to make this FAQ as
informative as possible; if you have any suggestions as to how
it may be improved, please feel free to mail them to the
&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>. You may also want to <ulink
url="&url.base;/search/index.html">Search the FAQ</ulink>.</para>
server</ulink>.</para>
</abstract>
</bookinfo>
<chapter id="introduction">
<title>Introduction</title>
<para>Welcome to the &os;
&rel3.relx;&nbsp;-, &rel2.relx;&nbsp;- and &rel.relx;&nbsp;-
FAQ!</para>
<para>As is usual with Usenet FAQs, this document aims to cover the
most frequently asked questions concerning the &os; operating
system (and of course answer them!). Although originally intended
to reduce bandwidth and avoid the same old questions being asked
over and over again, FAQs have become recognized as valuable
information resources.</para>
<para>Every effort has been made to make this FAQ as informative as
possible; if you have any suggestions as to how it may be
improved, please feel free to mail them to the &a.doc;.</para>
<qandaset>
<qandaentry>
<question id="what-is-FreeBSD">
@ -331,7 +308,7 @@
</listitem>
<listitem>
<para>DragonFlyBSD is a fork of &os;&nbsp;4.8 that has
<para>DragonFly&nbsp;BSD is a fork of &os;&nbsp;4.8 that has
since developed many interesting features of its own,
including the HAMMER file system and support for
user-mode <quote>vkernels</quote>.</para>
@ -351,14 +328,15 @@
made from the &rel.stable; branch, and &rel2.relx;
releases are made from the &rel2.stable; branch.</para>
<para>Up until the release of 8.0, the
&rel3.relx; series was the one known as
<emphasis>-STABLE</emphasis>. However, as of 8.0, the
&rel3.relx; branch will be designated for
<para>Up until the release of 9.0, the
&rel2.relx; series was the one known as
<emphasis>-STABLE</emphasis>. However, as of
&rel.head.relx;, the
&rel2.relx;. branch will be designated for
an <quote>extended support</quote> status and receive only
fixes for major problems, such as security-related fixes.
There will be no more releases made from the
&rel3.stable; branch, and it is considered a
&rel2.stable; branch, and it is considered a
<quote>legacy</quote> branch and most current work will only
become a part of &rel.stable; and &rel2.stable;.</para>
@ -977,18 +955,6 @@
channel:</para>
<itemizedlist>
<listitem>
<para>Channel <literal>#FreeBSD</literal> on <ulink
url="http://www.efnet.org/index.php">EFNet</ulink> is
a &os; forum, but do not go there for tech support or
try to get folks there to help you avoid the pain of
reading manual pages or doing your own research. It is
a chat channel, first and foremost, and topics there are
just as likely to involve sex, sports or nuclear weapons
as they are &os;. You Have Been Warned! Available at
server <hostid>irc.efnet.org</hostid>.</para>
</listitem>
<listitem>
<para>Channel <literal>#FreeBSDhelp</literal> on <ulink
url="http://www.efnet.org/index.php">EFNet</ulink> is
@ -1124,7 +1090,8 @@
<answer>
<para>&arch.amd64; is the term &os; uses for 64-bit
compatible x86 architectures. Most modern computers
compatible x86 architectures (also known as "x86-64"
or "x64"). Most modern computers
should use &arch.amd64;. Older hardware should use
&arch.i386;. If you are installing on a
non-x86-compatible architecture select the platform
@ -1170,7 +1137,7 @@
<row>
<entry><filename>memstick.img</filename></entry>
<entry>A bootable image sufficient for copying to a
<entry>A bootable image sufficient for writing to a
USB stick.</entry>
</row>
@ -1190,7 +1157,7 @@
<filename>floppies/kern2.flp</filename>, and
<filename>floppies/mfsroot1.flp</filename>. These images
need
to be copied onto floppies by tools like
to be written onto floppies by tools like
&man.dd.1;.</para>
<para>Full instructions on this procedure and a little bit
@ -1693,7 +1660,7 @@
<answer>
<para>Yes. &os; divides support into multiple tiers.
Tier 1 architectures, such as i386 or amd64; are
fully supported. Tiers 2 and 3 are supported on a
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
@ -1719,7 +1686,8 @@
<para>&os; will take advantage of HyperThreading (HTT)
support on &intel; CPUs that support this feature. A kernel
with the <literal>options SMP</literal> feature enabled
with the <literal>options SMP</literal> option, enabled
by default,
will automatically detect the additional logical
processors.</para>
@ -1967,26 +1935,8 @@ bindkey ^[[3~ delete-char # for xterm</programlisting>
</qandaset>
</sect1>
<sect1 id="compatibility-networking">
<title>Networking</title>
<qandaset>
<qandaentry>
<question id="support-broadcom">
<para>Is there a native driver for the Broadcom 43xx
cards?</para>
</question>
<answer>
<para>Yes, many Broadcom 43xx cards are supported by the
&man.bwn.4; and &man.bwi.4; drivers.</para>
</answer>
</qandaentry>
</qandaset>
</sect1>
<sect1 id="compatibility-sound">
<title>Sound Devices</title>
<sect1 id="compatibility-other">
<title>Other Hardware</title>
<qandaset>
<qandaentry>
@ -2003,13 +1953,7 @@ bindkey ^[[3~ delete-char # for xterm</programlisting>
<screen>&prompt.root; <userinput>mixer pcm 100 vol 100 cd 100</userinput></screen>
</answer>
</qandaentry>
</qandaset>
</sect1>
<sect1 id="compatibility-other">
<title>Other Hardware</title>
<qandaset>
<qandaentry>
<question id="power-management-support">
<para>Does &os; support power management on my
@ -2491,9 +2435,38 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
</question>
<answer>
<para>An answer for this question can be found in the &os;
Glossary, see <ulink
url="&url.books.handbook;/freebsd-glossary.html#lor-glossary">LOR</ulink>.</para>
<para>The &os; kernel uses a number of resource locks to
arbitrate contention for certain resources. When multiple
kernel threads try to obtain multiple resource locks,
there's always the potential for a deadlock,
where two threads have each obtained one of the locks and
blocks forever waiting for the other thread to release one
of the other locks. This sort of locking problem can be
avoided if all threads obtain the locks in the same
order.</para>
<para>A run-time lock diagnostic system called &man.witness.4;,
enabled in &os.current; and disabled by default for stable
branches and releases, detects the potential for deadlocks due to
locking errors, including errors caused by obtaining multiple
resource locks with a different order from different parts of the
kernel. The &man.witness.4; framework tries to detect this
problem as it happens, and reports it by printing a message to the
system console about a <errorname>lock order reversal</errorname>
(often referred to also as <acronym>LOR</acronym>).</para>
<para>It is possible to get false positives, as &man.witness.4;
is conservative. A true positive report <emphasis>does
not</emphasis> mean that a system is dead-locked; instead
it should be understood as a warning of the form <quote>if
you were unlucky, a deadlock would have happened
here</quote>.</para>
<note>
<para>Problematic <acronym>LOR</acronym>s tend to get fixed
quickly, so check &a.current.url; before posting to the
mailing lists.</para>
</note>
</answer>
</qandaentry>
@ -2571,7 +2544,7 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
periodic updates on new entries.</para>
<para>Most ports should work on the
&rel3.relx;, &rel2.relx;, and &rel.relx; branches.
&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>
@ -2595,15 +2568,6 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
locations:</para>
<variablelist>
<varlistentry>
<term>for &rel3.relx;&nbsp;-RELEASE/&rel3.stable;</term>
<listitem>
<para><ulink
url="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/&rel3.packages;/">ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/&rel3.packages;</ulink></para>
</listitem>
</varlistentry>
<varlistentry>
<term>for &rel2.relx;&nbsp;-RELEASE/&rel2.stable;</term>
@ -2677,7 +2641,7 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
<qandaentry>
<question id="ports-4x">
<para>Why can I not build this port on my
&rel3.relx;&nbsp;-, &rel2.relx;&nbsp;-, or
&rel2.relx;&nbsp;-, or
&rel.relx;&nbsp;-STABLE machine?</para>
</question>
@ -3270,55 +3234,6 @@ kern.sched.name: ULE</screen>
</answer>
</qandaentry>
<qandaentry>
<question id="inappropriate-ccd">
<para>What is inappropriate about my &man.ccd.4;?</para>
</question>
<answer>
<para>The symptom of this is:</para>
<screen>&prompt.root; <userinput>ccdconfig -C</userinput>
ccdconfig: ioctl (CCDIOCSET): /dev/<replaceable>ccd0c</replaceable>: Inappropriate file type or format</screen>
<para>This usually happens when you are trying to concatenate
the <literal>c</literal> partitions, which default to type
<literal>unused</literal>. The &man.ccd.4; driver requires
the underlying partition type to be
<literal>FS_BSDFFS</literal>. Edit the disk label of the
disks you are trying to concatenate and change the types of
partitions to <literal>4.2BSD</literal>.</para>
</answer>
</qandaentry>
<qandaentry>
<question id="ccd-disk-label">
<para>Why can I not edit the disk label on my
&man.ccd.4;?</para>
</question>
<answer>
<para>The symptom of this is:</para>
<screen>&prompt.root; <userinput>disklabel <replaceable>ccd0</replaceable></userinput>
(it prints something sensible here, so let us try to edit it)
&prompt.root; <userinput>disklabel -e <replaceable>ccd0</replaceable></userinput>
(edit, save, quit)
disklabel: ioctl DIOCWDINFO: No disk label on disk;
use "disklabel -r" to install initial label</screen>
<para>This is because the disk label returned by &man.ccd.4;
is actually a <quote>fake</quote> one that is not really on
the disk. You can solve this problem by writing it back
explicitly, as in:</para>
<screen>&prompt.root; <userinput>disklabel <replaceable>ccd0</replaceable> &gt; <replaceable>/tmp/disklabel.tmp</replaceable></userinput>
&prompt.root; <userinput>disklabel -Rr <replaceable>ccd0</replaceable> <replaceable>/tmp/disklabel.tmp</replaceable></userinput>
&prompt.root; <userinput>disklabel -e <replaceable>ccd0</replaceable></userinput>
(this will work now)</screen>
</answer>
</qandaentry>
<qandaentry>
<question id="mount-foreign-fs">
<para>Can I mount other foreign file systems under
@ -3830,10 +3745,6 @@ C:\="DOS"</programlisting>
<command>more</command> session, <command>du</command> and
<command>df</command> will agree.</para>
<para>Note that Soft Updates can delay the freeing of disk
space; you might need to wait up to 30 seconds for the
change to be visible!</para>
<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
@ -3842,6 +3753,10 @@ C:\="DOS"</programlisting>
restarting the web server program would free the file,
allowing the system to release the disk space. To prevent
this from happening, set up &man.newsyslog.8;.</para>
<para>Note that Soft Updates can delay the freeing of disk
space; you might need to wait up to 30 seconds for the
change to be visible!</para>
</answer>
</qandaentry>
@ -4208,7 +4123,9 @@ C:\="DOS"</programlisting>
<para>If you intend to use a full screen editor such as
&man.vi.1; or &man.emacs.1;, you may also need to run
<command>export TERM=cons25</command> so that these editors
<command>export TERM=xterm</command> on &os; 9.0+, or
<command>export TERM=cons25</command> on &os; 8.X
so that these editors
can load the correct data from the &man.termcap.5;
database.</para>
@ -4327,9 +4244,12 @@ C:\="DOS"</programlisting>
<answer>
<para>Yes, &os; supports System V-style IPC, including shared
memory, messages and semaphores, in the
<filename>GENERIC</filename> kernel. In a custom kernel,
enable this support by adding the following lines to your
kernel config.</para>
<filename>GENERIC</filename> kernel. With a custom kernel,
support may be loaded with the <filename>sysvshm.ko</filename>,
<filename>sysvsem.ko</filename> and <filename>
sysvmsg.ko</filename> kernel modules, or
enabled in the custom kernel by adding the following lines to your
kernel config:</para>
<programlisting>options SYSVSHM # enable shared memory
options SYSVSEM # enable for semaphores
@ -4488,42 +4408,6 @@ options SYSVMSG # enable for messaging</programlisting>
</answer>
</qandaentry>
<qandaentry>
<question id="uninstall-kerberos">
<para>How do I uninstall
<application>Kerberos</application>?</para>
</question>
<answer>
<para>To remove <application>Kerberos</application> from the
system, reinstall the <literal>base</literal> distribution
for the release you are running. If you have the CD-ROM,
you can mount it (we will assume on <filename
class="directory">/cdrom</filename>) and run the commands
below:</para>
<screen>&prompt.root; <userinput>cd /cdrom/base</userinput>
&prompt.root; <userinput>./install.sh</userinput></screen>
<para>Alternately, you can include the
<makevar>NO_KERBEROS</makevar> option in your
<filename>/etc/make.conf</filename> and rebuild
world.</para>
</answer>
</qandaentry>
<qandaentry>
<question id="add-pty">
<para>How do I add pseudoterminals to the system?</para>
</question>
<answer>
<para>If you have a lot of <command>telnet</command>,
<command>ssh</command>, X, or <command>screen</command>
users, you might run out of pseudoterminals. By default,
&os; supports 512 pseudoterminals.</para>
</answer>
</qandaentry>
<qandaentry>
<question id="reread-rc">
<para>How do I re-read <filename>/etc/rc.conf</filename> and
@ -4564,8 +4448,8 @@ options SYSVMSG # enable for messaging</programlisting>
the same way as <emphasis>-PRERELEASE</emphasis>.)</para>
<para>Long answer: &os; derives its releases from one of two
places. Major, dot-zero, releases, such as 7.0-RELEASE and
8.0-RELEASE, are branched from the head of the development
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
6.3-RELEASE or 5.2-RELEASE, have been snapshots of the
@ -5165,10 +5049,10 @@ EndSection</programlisting>
<programlisting># Edit the existing entry for ttyv8 in /etc/ttys and change
# "off" to "on".
ttyv8 "/usr/libexec/getty Pc" cons25 on secure
ttyv9 "/usr/libexec/getty Pc" cons25 on secure
ttyva "/usr/libexec/getty Pc" cons25 on secure
ttyvb "/usr/libexec/getty Pc" cons25 on secure</programlisting>
ttyv8 "/usr/libexec/getty Pc" xterm on secure
ttyv9 "/usr/libexec/getty Pc" xterm on secure
ttyva "/usr/libexec/getty Pc" xterm on secure
ttyvb "/usr/libexec/getty Pc" xterm on secure</programlisting>
<para>Use as many or as few as you want. The more virtual
terminals you have, the more resources that are used; this
@ -5176,6 +5060,14 @@ ttyvb "/usr/libexec/getty Pc" cons25 on secure</programlisting>
also want to change the <literal>secure</literal> to
<literal>insecure</literal>.</para>
<note>
<para>Versions of &os; prior to 9.0 used the <quote>
cons25</quote> terminal type, and not <quote>
xterm</quote>. Existing entries in
<filename>/etc/ttys</filename> can be used on which to
base new additions.</para>
</note>
<important>
<para>If you want to run an X server you
<emphasis>must</emphasis> leave at least one virtual
@ -5191,18 +5083,18 @@ ttyvb "/usr/libexec/getty Pc" cons25 on secure</programlisting>
allocation mentioned above and you wanted to run X, you
would change settings for virtual terminal 12 from:</para>
<programlisting>ttyvb "/usr/libexec/getty Pc" cons25 on secure</programlisting>
<programlisting>ttyvb "/usr/libexec/getty Pc" xterm on secure</programlisting>
<para>to:</para>
<programlisting>ttyvb "/usr/libexec/getty Pc" cons25 off secure</programlisting>
<programlisting>ttyvb "/usr/libexec/getty Pc" xterm off secure</programlisting>
<para>If your keyboard has only ten function keys, you would
end up with:</para>
<programlisting>ttyv9 "/usr/libexec/getty Pc" cons25 off secure
ttyva "/usr/libexec/getty Pc" cons25 off secure
ttyvb "/usr/libexec/getty Pc" cons25 off secure</programlisting>
<programlisting>ttyv9 "/usr/libexec/getty Pc" xterm off secure
ttyva "/usr/libexec/getty Pc" xterm off secure
ttyvb "/usr/libexec/getty Pc" xterm off secure</programlisting>
<para>(You could also just delete these lines.)</para>
@ -5354,17 +5246,9 @@ ttyvb "/usr/libexec/getty Pc" cons25 off secure</programlisting>
<para>If this happens, disable the synchronization check code
by setting the driver flags for the PS/2 mouse driver to
<literal>0x100</literal>. Enter
<emphasis>UserConfig</emphasis> by giving the
<option>-c</option> option at the boot prompt:</para>
<screen>boot: <userinput>-c</userinput></screen>
<para>Then, in the <emphasis>UserConfig</emphasis> command
line, type:</para>
<screen>UserConfig&gt; <userinput>flags psm0 0x100</userinput>
UserConfig&gt; <userinput>quit</userinput></screen>
<literal>0x100</literal>. This can be easiest achieved
by adding <screen>hint.psm.0.flags="0x100"</screen> to
<filename>/boot/loader.conf</filename> and rebooting.</para>
</answer>
</qandaentry>
@ -5651,24 +5535,6 @@ Key F15 A A Menu Workplace Nop</programlisting>
</answer>
</qandaentry>
<qandaentry>
<question id="port-3c503">
<para>How do I get my 3C503 to use the other network
port?</para>
</question>
<answer>
<para>If you want to use the other ports, you will have to
specify an additional parameter on the &man.ifconfig.8;
command line. The default port is <literal>link0</literal>.
To use the AUI port instead of the BNC one, use
<literal>link2</literal>. These flags should be specified
using the ifconfig_* variables in
<filename>/etc/rc.conf</filename> (see
&man.rc.conf.5;).</para>
</answer>
</qandaentry>
<qandaentry>
<question id="nfs-linux">
<para>Why can I not NFS-mount from a &linux; box?</para>
@ -5723,13 +5589,6 @@ Key F15 A A Menu Workplace Nop</programlisting>
programs are now available in the &os; Ports Collection as
<filename role="package">net/mrouted</filename>.</para>
</note>
<para>MBONE tools are available in their own ports category,
<ulink
url="http://www.FreeBSD.org/ports/mbone.html">mbone</ulink>.
If you are looking for the conference tools
<command>vic</command> and <command>vat</command>, look
there!</para>
</answer>
</qandaentry>
@ -6043,9 +5902,7 @@ Key F15 A A Menu Workplace Nop</programlisting>
<para>Every &unix; process is completely firewalled off from
every other &unix; process. One process cannot modify the
address space of another. This is unlike &windows; where a
process can easily overwrite the address space of any other,
leading to a crash.</para>
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,
@ -6139,7 +5996,7 @@ Key F15 A A Menu Workplace Nop</programlisting>
search the archives <ulink
url="&url.base;/search/index.html">here</ulink> for an
extensive discussion. A more fine-grained mechanism
is preffered.</para>
is preferred.</para>
</warning>
</answer>
</qandaentry>
@ -8057,11 +7914,6 @@ hint.sio.7.irq="12"</programlisting>
there are only four active branches of development):</para>
<itemizedlist>
<listitem>
<para>&rel3.releng; AKA
&rel3.stable;</para>
</listitem>
<listitem>
<para>&rel2.releng; AKA
&rel2.stable;</para>

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

@ -137,11 +137,11 @@
<para>The documentation for the web site, &os; Handbook, and FAQ
are available in the <literal>doc/</literal> Subversion
repository, which is located at
<literal>svn://svn.FreeBSD.org/doc/</literal>.</para>
<literal>https://svn.FreeBSD.org/doc/</literal>.</para>
<para>Manual pages are available in the <literal>src/</literal>
Subversion repository, which is available at
<literal>svn://svn.FreeBSD.org/base/</literal>.</para>
<literal>https://svn.FreeBSD.org/base/</literal>.</para>
<para>This means that the logs of changes to these
files are visible to anyone, and anyone can use
@ -205,13 +205,23 @@
<screen>&prompt.user; <userinput>mkdir -p head/share</userinput>
&prompt.user; <userinput>mkdir -p head/en_US.ISO8859-1/share</userinput>
&prompt.user; <userinput>svn checkout svn://svn.FreeBSD.org/doc/head/share head/share</userinput>
&prompt.user; <userinput>svn checkout svn://svn.FreeBSD.org/doc/head/en_US.ISO8859-1/share head/en_US.ISO8859-1/share</userinput></screen>
&prompt.user; <userinput>svn checkout <replaceable>https://svn0.us-east.FreeBSD.org</replaceable>/doc/head/share head/share</userinput>
&prompt.user; <userinput>svn checkout <replaceable>https://svn0.us-east.FreeBSD.org</replaceable>/doc/head/en_US.ISO8859-1/share head/en_US.ISO8859-1/share</userinput></screen>
<para>If you have plenty of disk space then you could check
out everything.</para>
<screen>&prompt.user; <userinput>svn checkout svn://svn.FreeBSD.org/doc/head head</userinput></screen>
<screen>&prompt.user; <userinput>svn checkout <replaceable>https://svn0.us-east.FreeBSD.org</replaceable>/doc/head head</userinput></screen>
<note>
<para><ulink
url="https://svn0.us-east.FreeBSD.org/">svn0.us-east.FreeBSD.org</ulink>
is a public <literal>SVN</literal> server.
Select the closest mirror and verify the mirror server
certificate from the list of <ulink
url="&url.books.handbook;/svn-mirrors.html">Subversion
mirror sites</ulink>.</para>
</note>
</step>
<step>
@ -229,7 +239,7 @@
<para>Check out the <filename>articles</filename>
directory.</para>
<screen>&prompt.user; <userinput>svn checkout svn://svn.FreeBSD.org/doc/head/en_US.ISO8859-1/articles</userinput></screen>
<screen>&prompt.user; <userinput>svn checkout <replaceable>https://svn0.us-east.FreeBSD.org</replaceable>/doc/head/en_US.ISO8859-1/articles</userinput></screen>
</step>
<step>
@ -248,7 +258,7 @@
<filename>head/en_US.ISO8859-1/books/faq</filename> you
would check it out of the repository like this.</para>
<screen>&prompt.user; <userinput>svn checkout svn://svn.FreeBSD.org/doc/head/en_US.ISO8859-1/books/faq</userinput></screen>
<screen>&prompt.user; <userinput>svn checkout <replaceable>https://svn0.us-east.FreeBSD.org</replaceable>/doc/head/en_US.ISO8859-1/books/faq</userinput></screen>
</step>
<step>

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

@ -68,7 +68,15 @@
<para>To check out the full source files for the &os; website,
run:</para>
<screen>&prompt.root; <userinput><command>svn checkout svn://svn.FreeBSD.org/doc/head/ <replaceable>/usr/build</replaceable></command></userinput></screen>
<screen>&prompt.root; <userinput><command>svn checkout <replaceable>https://svn0.us-east.FreeBSD.org</replaceable>/doc/head/ <replaceable>/usr/build</replaceable></command></userinput></screen>
<para><ulink
url="https://svn0.us-east.FreeBSD.org/">svn0.us-east.FreeBSD.org</ulink>
is a public <literal>SVN</literal> server.
Select the closest mirror and verify the mirror server
certificate from the list of <ulink
url="&url.books.handbook;/svn-mirrors.html">Subversion
mirror sites</ulink>.</para>
<tip>
<para>If <command>svn</command> is not run as

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

@ -137,7 +137,15 @@
copy of the FreeBSD Subversion repository (at least the
documentation part). This can be done by running:</para>
<screen>&prompt.user; <userinput><command>svn</command> checkout svn://svn.FreeBSD.org/doc/head/ head</userinput></screen>
<screen>&prompt.user; <userinput><command>svn</command> checkout <replaceable>https://svn0.us-east.FreeBSD.org</replaceable>/doc/head/ head</userinput></screen>
<para><ulink
url="https://svn0.us-east.FreeBSD.org/">svn0.us-east.FreeBSD.org</ulink>
is a public <literal>SVN</literal> server.
Select the closest mirror and verify the mirror server
certificate from the list of <ulink
url="&url.books.handbook;/svn-mirrors.html">Subversion
mirror sites</ulink>.</para>
<note>
<para>This will require the <filename

96
en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml
View file

@ -867,22 +867,6 @@ route_net2="-net 192.168.1.0/24 192.168.1.1"</programlisting>
wrapper.</para>
</note>
<para>Under &os;&nbsp;7.X, with a device driver you need to
also bring in the 802.11 networking support required by the
driver. For the &man.ath.4; driver these are at least the
&man.wlan.4;, <literal>wlan_scan_ap</literal> and
<literal>wlan_scan_sta</literal> modules; the &man.wlan.4;
module is automatically loaded with the wireless device
driver, the remaining modules must be loaded at boot time
in <filename>/boot/loader.conf</filename>:</para>
<programlisting>wlan_scan_ap_load="YES"
wlan_scan_sta_load="YES"</programlisting>
<para>Since &os;&nbsp;8.0, these modules are part of the
base &man.wlan.4; driver which is dynamically loaded with
the adapter driver.</para>
<para>With that, you will need the modules that implement
cryptographic support for the security protocols you intend
to use. These are intended to be dynamically loaded on
@ -922,13 +906,6 @@ device ath_hal # pci/cardbus chip support
options AH_SUPPORT_AR5416 # enable AR5416 tx/rx descriptors
device ath_rate_sample # SampleRate tx rate control for ath</programlisting>
<para>Both following lines are also required by
&os;&nbsp;7.X, other &os; versions do not need
them:</para>
<programlisting>device wlan_scan_ap # 802.11 AP mode scanning
device wlan_scan_sta # 802.11 STA mode scanning</programlisting>
<para>With this information in the kernel configuration
file, recompile the kernel and reboot your &os;
machine.</para>
@ -979,21 +956,6 @@ freebsdap 00:11:95:c3:0d:ac 1 54M -83:96 100 EPS WPA</screen>
require you to mark the interface up again.</para>
</note>
<note>
<para>Under &os;&nbsp;7.X, the adapter device, for example
<devicename><replaceable>ath0</replaceable></devicename>,
is used directly instead of the
<devicename>wlan<replaceable>0</replaceable></devicename>
device. This requires you to replace the both previous
lines with:</para>
<screen>&prompt.root; <userinput>ifconfig <replaceable>ath0</replaceable> up scan</userinput></screen>
<para>In the rest of this document, &os;&nbsp;7.X users
will need to change the command and configuration lines
according to that scheme.</para>
</note>
<para>The output of a scan request lists each BSS/IBSS
network found. Beside the name of the network,
<literal>SSID</literal>, we find the
@ -1096,13 +1058,6 @@ freebsdap 00:11:95:c3:0d:ac 1 54M -83:96 100 EPS WPA</screen>
<programlisting>wlans_ath0="wlan0"
ifconfig_wlan0="DHCP"</programlisting>
<note>
<para>As previously mentioned, &os;&nbsp;7.X will only
require a line related to the adapter device:</para>
<programlisting>ifconfig_ath0="DHCP"</programlisting>
</note>
<para>If there are multiple access points and you want to
select a specific one, you can select it by its
SSID:</para>
@ -1319,7 +1274,7 @@ ifconfig_wlan0="WPA DHCP"</programlisting>
<para>Then we can bring up the interface:</para>
<screen>&prompt.root; <userinput><filename>service netif</filename> start</userinput>
<screen>&prompt.root; <userinput>service netif start</userinput>
Starting wpa_supplicant.
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
@ -2234,8 +2189,8 @@ freebsdap 00:11:95:c3:0d:ac 1 54M 22:1 100 EPS</screen>
can enable debugging messages in the 802.11 protocol
support layer using the <command>wlandebug</command>
program found in
<filename>/usr/src/tools/tools/net80211</filename>. For
example:</para>
<filename class="directory">/usr/src/tools/tools/net80211</filename>.
For example:</para>
<screen>&prompt.root; <userinput>wlandebug -i <replaceable>ath0</replaceable> +scan+auth+debug+assoc</userinput>
net.wlan.0.debug: 0 =&gt; 0xc80000&lt;assoc,auth,scan&gt;</screen>
@ -2805,7 +2760,8 @@ Success, response: OK, Success (0x20)</screen>
<para>In order to provide OBEX Object Push service, &man.sdpd.8;
server must be running. A root folder, where all incoming
objects will be stored, must be created. The default path to
the root folder is <filename>/var/spool/obex</filename>.
the root folder
is <filename class="directory">/var/spool/obex</filename>.
Finally, start OBEX server on valid RFCOMM channel number.
The OBEX server will automatically register OBEX Object Push
service with the local SDP daemon. The example below shows
@ -3734,9 +3690,9 @@ ifconfig_<literal>lagg<replaceable>0</replaceable></literal>="laggproto failover
</listitem>
<listitem>
<para>Standard system startup files exist in
<filename>/etc</filename> to detect and support a diskless
system startup.</para>
<para>Standard system startup files exist
in <filename class="directory">/etc</filename>
to detect and support a diskless system startup.</para>
</listitem>
<listitem>
@ -3755,8 +3711,9 @@ ifconfig_<literal>lagg<replaceable>0</replaceable></literal>="laggproto failover
<itemizedlist>
<listitem>
<para>The diskless workstations use a shared read-only
<filename>/</filename> file system, and a shared
read-only <filename>/usr</filename>.</para>
<filename class="directory">/</filename> file system,
and a shared read-only
<filename class="directory">/usr</filename>.</para>
<para>The root file system is a copy of a standard FreeBSD
root (typically the server's), with some configuration files
@ -4079,8 +4036,9 @@ margaux:ha=0123456789ab:tc=.def100</programlisting>
<para>To make a boot floppy, insert a floppy in the drive on
the machine where you installed
<application>Etherboot</application>, then change your
current directory to the <filename>src</filename> directory
in the <application>Etherboot</application> tree and
current directory to
the <filename class="directory">src</filename>
directory in the <application>Etherboot</application> tree and
type:</para>
<screen>&prompt.root; <userinput>gmake bin32/<replaceable>devicetype</replaceable>.fd0</userinput></screen>
@ -4138,7 +4096,7 @@ margaux:ha=0123456789ab:tc=.def100</programlisting>
<step>
<para>Create a directory from which
<application>tftpd</application> will serve the files,
e.g., <filename>/tftpboot</filename>.</para>
e.g., <filename class="directory">/tftpboot</filename>.</para>
</step>
<step>
@ -4168,7 +4126,8 @@ margaux:ha=0123456789ab:tc=.def100</programlisting>
</step>
</procedure>
<para>You can place the <filename>tftpboot</filename>
<para>You can place
the <filename class="directory">tftpboot</filename>
directory anywhere on the server. Make sure that the
location is set in both <filename>inetd.conf</filename> and
<filename>dhcpd.conf</filename>.</para>
@ -4331,7 +4290,7 @@ cd /usr/src/etc; make distribution</programlisting>
<sect4>
<title>Running with a Read-only
<filename>/usr</filename></title>
<filename class="directory">/usr</filename></title>
<indexterm>
<primary>diskless operation</primary>
@ -4341,7 +4300,8 @@ cd /usr/src/etc; make distribution</programlisting>
<para>If the diskless workstation is configured to run X,
you will have to adjust the
<application>XDM</application> configuration file, which
puts the error log on <filename>/usr</filename> by
puts the error log
on <filename class="directory">/usr</filename> by
default.</para>
</sect4>
@ -4355,7 +4315,8 @@ cd /usr/src/etc; make distribution</programlisting>
<command>cpio</command>.</para>
<para>In this situation, there are sometimes problems with
the special files in <filename>/dev</filename>, due to
the special files
in <filename class="directory">/dev</filename>, due to
differing major/minor integer sizes. A solution to this
problem is to export a directory from the non-FreeBSD
server, mount this directory onto a FreeBSD machine, and
@ -4415,7 +4376,7 @@ cd /usr/src/etc; make distribution</programlisting>
<para>Choose a directory which will have a &os;
installation which will be NFS mountable. For example, a
directory such as
<filename>/b/tftpboot/FreeBSD/install</filename> can be
<filename class="directory">/b/tftpboot/FreeBSD/install</filename> can be
used.</para>
<screen>&prompt.root; <userinput>export NFSROOTDIR=/b/tftpboot/FreeBSD/install</userinput>
@ -4545,8 +4506,10 @@ myhost.example.com:/b/tftpboot/FreeBSD/install / nfs ro
<filename>/etc/rc</filename> detects that you booted over NFS
and runs the <filename>/etc/rc.initdiskless</filename> script.
Read the comments in this script to understand what is going
on. We need to make <filename>/etc</filename> and
<filename>/var</filename> memory backed file systems because
on. We need to
make <filename class="directory">/etc</filename>
and <filename class="directory">/var</filename>
memory backed file systems because
these directories need to be writable, but the NFS root
directory is read-only.</para>
@ -4555,8 +4518,9 @@ myhost.example.com:/b/tftpboot/FreeBSD/install / nfs ro
&prompt.root; <userinput>tar -c -v -f conf/base/etc.cpio.gz --format cpio --gzip etc</userinput>
&prompt.root; <userinput>tar -c -v -f conf/base/var.cpio.gz --format cpio --gzip var</userinput></screen>
<para>When the system boots, memory file systems for
<filename>/etc</filename> and <filename>/var</filename> will
<para>When the system boots, memory file systems
for <filename class="directory">/etc</filename>
and <filename class="directory">/var</filename> will
be created and mounted, and the contents of the
<filename>cpio.gz</filename> files will be copied into
them.</para>

4
en_US.ISO8859-1/books/handbook/audit/chapter.xml
View file

@ -104,7 +104,7 @@ requirements. -->
Administrators should take into account disk space
requirements associated with high volume audit configurations.
For example, it may be desirable to dedicate a file system to
the <filename>/var/audit</filename> tree so that other file
the <filename class="directory">/var/audit</filename> tree so that other file
systems are not affected if the audit file system becomes
full.</para>
</warning>
@ -630,7 +630,7 @@ trailer,133</programlisting>
<para>Members of the <groupname>audit</groupname> group are
given permission to read audit trails in
<filename>/var/audit</filename>; by default, this group is
<filename class="directory">/var/audit</filename>; by default, this group is
empty, so only the <username>root</username> user may read
audit trails. Users may be added to the
<groupname>audit</groupname> group in order to delegate audit

55
en_US.ISO8859-1/books/handbook/basics/chapter.xml
View file

@ -961,21 +961,25 @@ root 5211 0.0 0.2 3620 1724 2 I+ 2:09AM 0:00.01 passwd</screen>
class="directory">/usr/local/</filename></entry>
<entry>Local executables and libraries. Also used as
the default destination for the &os; ports
framework. Within <filename>/usr/local</filename>,
the general layout sketched out by &man.hier.7; for
<filename>/usr</filename> should be used. Exceptions
are the man directory, which is directly under
<filename>/usr/local</filename> rather than under
<filename>/usr/local/share</filename>, and the ports
documentation is in
<filename>share/doc/<replaceable>port</replaceable></filename>.</entry>
framework. Within
<filename class="directory">/usr/local</filename>, the
general layout sketched out by &man.hier.7; for
<filename class="directory">/usr</filename> should be
used. Exceptions are the man directory, which is
directly under
<filename class="directory">/usr/local</filename>
rather than under
<filename class="directory">/usr/local/share</filename>,
and the ports documentation is in
<filename class="directory">share/doc/<replaceable>port</replaceable></filename>.</entry>
</row>
<row>
<entry><filename
class="directory">/usr/obj/</filename></entry>
<entry>Architecture-specific target tree produced by
building the <filename>/usr/src</filename>
building the
<filename class="directory">/usr/src</filename>
tree.</entry>
</row>
@ -1075,9 +1079,9 @@ root 5211 0.0 0.2 3620 1724 2 I+ 2:09AM 0:00.01 passwd</screen>
directory name, followed by a forward slash,
<literal>/</literal>, followed by any other directory names that
are necessary. For example, if the directory
<filename>foo</filename> contains a directory
<filename>bar</filename> which contains the file
<filename>readme.txt</filename>, the full name, or
<filename class="directory">foo</filename> contains a directory
<filename class="directory">bar</filename> which contains the
file <filename>readme.txt</filename>, the full name, or
<firstterm>path</firstterm>, to the file is
<filename>foo/bar/readme.txt</filename>. Note that this is
different from &windows; which uses
@ -1152,11 +1156,13 @@ root 5211 0.0 0.2 3620 1724 2 I+ 2:09AM 0:00.01 passwd</screen>
<para>Any files that are in the <literal>B1</literal> or
<literal>B2</literal> directories can be reached with the path
<filename>/A1/B1</filename> or <filename>/A1/B2</filename> as
necessary. Any files that were in <filename>/A1</filename> have
<filename class="directory">/A1/B1</filename> or
<filename class="directory">/A1/B2</filename> as
necessary. Any files that were in
<filename class="directory">/A1</filename> have
been temporarily hidden. They will reappear if
<literal>B</literal> is <firstterm>unmounted</firstterm> from
A.</para>
<literal>A</literal>.</para>
<para>If <literal>B</literal> had been mounted on
<literal>A2</literal> then the diagram would look like
@ -1180,8 +1186,10 @@ root 5211 0.0 0.2 3620 1724 2 I+ 2:09AM 0:00.01 passwd</screen>
</textobject>
</mediaobject>
<para>and the paths would be <filename>/A2/B1</filename> and
<filename>/A2/B2</filename> respectively.</para>
<para>and the paths would be
<filename class="directory">/A2/B1</filename> and
<filename class="directory">/A2/B2</filename>
respectively.</para>
<para>File systems can be mounted on top of one another.
Continuing the last example, the <literal>C</literal> file
@ -1257,9 +1265,9 @@ root 5211 0.0 0.2 3620 1724 2 I+ 2:09AM 0:00.01 passwd</screen>
file system can be mounted read-only, making it impossible
for users to inadvertently delete or edit a critical file.
Separating user-writable file systems, such as
<filename>/home</filename>, from other file systems allows
them to be mounted <firstterm>nosuid</firstterm>. This
option prevents the
<filename class="directory">/home</filename>, from other
file systems allows them to be mounted
<firstterm>nosuid</firstterm>. This option prevents the
<firstterm>suid</firstterm>/<firstterm>guid</firstterm> bits
on executables stored on the file system from taking effect,
possibly improving security.</para>
@ -2153,8 +2161,6 @@ Swap: 256M Total, 38M Used, 217M Free, 15% Inuse
configuration. Here is a list of common environment variables
and their meanings:</para>
<indexterm><primary>environment variables</primary></indexterm>
<informaltable frame="none" pgwide="1">
<tgroup cols="2">
<thead>
@ -2389,7 +2395,7 @@ Swap: 256M Total, 38M Used, 217M Free, 15% Inuse
<para>Most devices in a &os; must be accessed through special
files called device nodes, which are located in
<filename>/dev</filename>.</para>
<filename class="directory">/dev</filename>.</para>
<sect2>
<title>Creating Device Nodes</title>
@ -2637,7 +2643,8 @@ Swap: 256M Total, 38M Used, 217M Free, 15% Inuse
equivalent to using &man.apropos.1;.</para>
<para>To determine what the commands in
<filename>/usr/bin</filename> do, type:</para>
<filename class="directory">/usr/bin</filename> do,
type:</para>
<screen>&prompt.user; <userinput>cd /usr/bin</userinput>
&prompt.user; <userinput>man -f *</userinput></screen>

10
en_US.ISO8859-1/books/handbook/config/chapter.xml
View file

@ -711,7 +711,7 @@ $sshd_enable=YES</screen>
<username>root</username> console.</para>
</note>
<para>To determine if a service is running, use
<para>To determine whether or not a service is running, use
<option>status</option>. For instance, to verify that
<command>sshd</command> is running:</para>
@ -1111,8 +1111,8 @@ lo0: flags=8049&lt;UP,LOOPBACK,RUNNING,MULTICAST&gt; metric 0 mtu 16384
<listitem>
<para>The status of the link (<literal>status</literal>) is
<literal>active</literal>, indicating that the carrier is
detected. For <devicename>dc1</devicename>, the
<literal>active</literal>, indicating that the carrier
signal is detected. For <devicename>dc1</devicename>, the
<literal>status: no carrier</literal> status is normal
when an Ethernet cable is not plugged into the
card.</para>
@ -1133,8 +1133,8 @@ lo0: flags=8049&lt;UP,LOOPBACK,RUNNING,MULTICAST&gt; metric 0 mtu 16384
<para>To configure the card, you will need
<username>root</username> privileges. The network card
configuration can be performed from the command line with
&man.ifconfig.8; but will not persist after a reboot.
Instead, add the network card's configuration to
&man.ifconfig.8; but will not persist after a reboot unless
the network card's configuration is also added to
<filename>/etc/rc.conf</filename> using an editor. Add a
line for each network card present on the system, as seen in
this example:</para>

27
en_US.ISO8859-1/books/handbook/cutting-edge/chapter.xml
View file

@ -378,7 +378,7 @@ MergeChanges /etc/ /var/named/etc/</programlisting>
on the version of &os;.</para>
<sect4 id="freebsd-update-custom-kernel-8x">
<title>Custom Kernels with &os;&nbsp;8.X and Earlier</title>
<title>Custom Kernels with &os;&nbsp;8.X</title>
<para>A copy of the <filename>GENERIC</filename> kernel is
needed, and should be placed in <filename
@ -1738,8 +1738,8 @@ Fetching 133 new ports or files... done.</screen>
up-to-date, refer to <xref linkend="synching"/> for detailed
help about synchronizing to a newer version.</para>
<para>Updating the system from source is a more subtle than
it might initially seem to be, and the &os; developers have
<para>Updating the system from source is a more subtle process
than it might initially seem to be, and the &os; developers have
found it necessary over the years to change the recommended
approach fairly dramatically as new kinds of unavoidable
dependencies come to light. The rest of this section
@ -1783,7 +1783,7 @@ Fetching 133 new ports or files... done.</screen>
</listitem>
<listitem>
<para>Some configuration changes must be done before the new
<para>Some configuration changes must be made before the new
world is installed, but others might break the old world.
Hence, two different configuration upgrade steps are
generally needed.</para>
@ -1871,7 +1871,7 @@ Fetching 133 new ports or files... done.</screen>
<para><command>mergemaster</command></para>
<para>Repeated to update the remaining configuration files,
not that the new world is on disk.</para>
now that the new world is on disk.</para>
</listitem>
<listitem>
@ -2142,7 +2142,7 @@ Script done, &hellip;</screen>
<para><emphasis>Do not</emphasis> save the output in <filename
class="directory">/tmp</filename> as this directory may be
cleared at next reboot. A better place to save the file is
<filename class="directory">/var/tmp</filename>or in
<filename class="directory">/var/tmp</filename> or in
<username>root</username>'s home directory.</para>
</sect3>
@ -2159,8 +2159,7 @@ Script done, &hellip;</screen>
<para>To rebuild the world, use &man.make.1;. This command
reads instructions from the <filename>Makefile</filename>,
which describes how the programs that comprise &os; should
be rebuilt and the order in which they should be
built.</para>
be built and the order in which they should be built.</para>
<para>The general format of the command is as follows:</para>
@ -2467,7 +2466,7 @@ Script done, &hellip;</screen>
<sect3>
<title>Manual Update</title>
<para>To instead perform the update manually, do not just copy
<para>To perform the update manually instead, do not just copy
over the files from
<filename class="directory">/usr/src/etc</filename> to
<filename class="directory">/etc</filename> and expect it to
@ -2503,11 +2502,9 @@ Script done, &hellip;</screen>
files.</para>
</warning>
<para>Next, build a dummy set of directories to install the
new <filename class="directory">/etc</filename> and other
files into. <filename
class="directory">/var/tmp/root</filename> is a reasonable
choice:</para>
<para>Build a temporary set of directories into which the new
<filename class="directory">/etc</filename> and other files
can be installed:</para>
<screen>&prompt.root; <userinput>mkdir /var/tmp/root</userinput>
&prompt.root; <userinput>cd /usr/src/etc</userinput>
@ -2823,7 +2820,7 @@ Building everything..
<listitem>
<para>Turn off profiling by setting
<quote>NO_PROFILE=true</quote> in
<filename>/etc/make.conf</filename>).</para>
<filename>/etc/make.conf</filename>.</para>
</listitem>
<listitem>

19
en_US.ISO8859-1/books/handbook/desktop/chapter.xml
View file

@ -176,6 +176,7 @@
</row>
<row>
<entry>Finance</entry>
<entry><application>KMyMoney</application></entry>
<entry><literal>kmymoney-kde4</literal></entry>
<entry><filename
@ -251,8 +252,7 @@
<entry><application>Firefox</application></entry>
<entry>medium</entry>
<entry>heavy</entry>
<entry><application>&os; and &linux; versions are
available</application></entry>
<entry>&os; and &linux; versions are available</entry>
</row>
<row>
@ -266,7 +266,7 @@
<entry><application>Konqueror</application></entry>
<entry>medium</entry>
<entry>heavy</entry>
<entry><application>Requires KDE</application>
<entry>Requires <application>KDE</application>
libraries</entry>
</row>
@ -274,7 +274,7 @@
<entry><application>Chromium</application></entry>
<entry>medium</entry>
<entry>heavy</entry>
<entry><application>Requires Gtk+</application></entry>
<entry>Requires <application>Gtk+</application></entry>
</row>
</tbody>
</tgroup>
@ -403,9 +403,10 @@
<screen>&prompt.user; <userinput>nspluginwrapper -v -a -u</userinput></screen>
<para>Start the browser, enter <literal>about:plugins</literal>
in the location bar and press <keycap>Enter</keycap>. A list
should appear with all the currently available plugins.</para>
<para>Start the browser, enter
<literal>about:plugins</literal> in the location bar and
press <keycap>Enter</keycap>. A list should appear with
all the currently available plugins.</para>
</step>
</procedure>
@ -613,8 +614,8 @@
of the installed desktop environment.</para>
<para>This section demonstrates how to install the following
popular web browsers and indicates if the application is
resource-heavy, takes time to compile from ports, or has any
popular productivity software and indicates if the application
is resource-heavy, takes time to compile from ports, or has any
major dependencies.</para>
<informaltable frame="none" pgwide="1">

12
en_US.ISO8859-1/books/handbook/disks/chapter.xml
View file

@ -3040,13 +3040,7 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
kernel configuration.</para>
<para>Next, enable disk quotas in
<filename>/etc/rc.conf</filename>. On &os;&nbsp;7.X and
earlier, this is done by adding the line:</para>
<programlisting>enable_quotas="YES"</programlisting>
<para>On &os;&nbsp;8.0-RELEASE and later, add the following
line instead:</para>
<filename>/etc/rc.conf</filename>:</para>
<programlisting>quota_enable="YES"</programlisting>
@ -4028,10 +4022,6 @@ Device 1K-blocks Used Avail Capacity
linkend="network-communication">&os;
networking</link>.</para>
</listitem>
<listitem>
<para>Use &os;&nbsp;8.1-RELEASE or newer.</para>
</listitem>
</itemizedlist>
<para>The <acronym>HAST</acronym> project was sponsored by The

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

@ -94,7 +94,7 @@
<row>
<entry>&a.announce.name;</entry>
<entry>Important events and project milestones</entry>
<entry>Important events and project milestones (moderated)</entry>
</row>
<row>
@ -150,7 +150,7 @@
<row>
<entry>&a.security-notifications.name;</entry>
<entry>Security notifications</entry>
<entry>Security notifications (moderated)</entry>
</row>
<row>
@ -202,7 +202,7 @@
<row>
<entry>&a.amd64.name;</entry>
<entry>Porting FreeBSD to AMD64 systems</entry>
<entry>Porting FreeBSD to AMD64 systems (moderated)</entry>
</row>
<row>
@ -458,7 +458,7 @@
<row>
<entry>&a.ports-announce.name;</entry>
<entry>Important news and instructions about the Ports
Collection</entry>
Collection (moderated)</entry>
</row>
<row>
@ -634,11 +634,6 @@
<entry>User group coordination</entry>
</row>
<row>
<entry>&a.vendors.name;</entry>
<entry>Vendors pre-release coordination</entry>
</row>
<row>
<entry>&a.wip-status.name;</entry>
<entry>FreeBSD Work-In-Progress Status</entry>
@ -649,13 +644,6 @@
<entry>Discussions of 802.11 stack, tools, device driver
development</entry>
</row>
<row>
<entry>&a.www.name;</entry>
<entry>Maintainers of
<ulink
url="&url.base;/index.html">www.FreeBSD.org</ulink></entry>
</row>
</tbody>
</tgroup>
</informaltable>
@ -1518,7 +1506,7 @@
changes and issues related to the FreeBSD.org project
infrastructure.</para>
<para>This list is strictly for announcements: no replies,
<para>This moderated list is strictly for announcements: no replies,
requests, discussions, or opinions.</para>
</listitem>
</varlistentry>
@ -1858,18 +1846,6 @@
</listitem>
</varlistentry>
<varlistentry>
<term>&a.vendors.name;</term>
<listitem>
<para><emphasis>Vendors</emphasis></para>
<para>Coordination discussions between The FreeBSD
Project and Vendors of software and hardware for
FreeBSD.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>&a.virtualization.name;</term>

4
en_US.ISO8859-1/books/handbook/firewalls/chapter.xml
View file

@ -350,8 +350,8 @@ pflog_flags="" # additional flags for pflogd startup</programli
url="http://www.openbsd.org/faq/pf/">PF FAQ</ulink>,
keep in mind that different versions of &os; contain
different versions of PF. Currently,
&os;&nbsp;8.<replaceable>X</replaceable> and prior is using
the same version of <acronym>PF</acronym> as
&os;&nbsp;8.<replaceable>X</replaceable> is using the
same version of <acronym>PF</acronym> as
OpenBSD&nbsp;4.1. &os;&nbsp;9.<replaceable>X</replaceable>
and later is using the same version of <acronym>PF</acronym>
as OpenBSD&nbsp;4.5.</para>

389
en_US.ISO8859-1/books/handbook/install/chapter.xml
View file

@ -176,14 +176,14 @@
<sect2 id="install-inventory">
<title>Inventory Your Computer</title>
<para>Before installing FreeBSD you should attempt to inventory the
components in your computer. The FreeBSD installation routines will
<para>Before installing &os; you should attempt to inventory the
components in your computer. The &os; installation routines will
show you the components (hard disks, network cards, CDROM drives, and
so forth) with their model number and manufacturer. FreeBSD will also
so forth) with their model number and manufacturer. &os; will also
attempt to determine the correct configuration for these devices,
which includes information about IRQ and IO port usage. Due to the
vagaries of PC hardware this process is not always completely
successful, and you may need to correct FreeBSD's determination of
successful, and you may need to correct &os;'s determination of
your configuration.</para>
<para>If you already have another operating system installed, such as
@ -195,7 +195,7 @@
hexadecimal numbers, such as 0x330.</para>
<para>We recommend you print or write down this information before
installing FreeBSD. It may help to use a table, like this:</para>
installing &os;. It may help to use a table, like this:</para>
<table pgwide="1" frame="none">
<title>Sample Device Inventory</title>
@ -293,22 +293,22 @@
<sect2>
<title>Backup Your Data</title>
<para>If the computer you will be installing FreeBSD on contains
<para>If the computer you will be installing &os; on contains
valuable data, then ensure you have it backed up, and that you have
tested the backups before installing FreeBSD. The FreeBSD
tested the backups before installing &os;. The &os;
installation routine will prompt you before writing any
data to your disk, but once that process has started it cannot be
undone.</para>
</sect2>
<sect2 id="install-where">
<title>Decide Where to Install FreeBSD</title>
<title>Decide Where to Install &os;</title>
<para>If you want FreeBSD to use your entire hard disk, then there is nothing
<para>If you want &os; to use your entire hard disk, then there is nothing
more to concern yourself with at this point &mdash; you can skip this
section.</para>
<para>However, if you need FreeBSD to co-exist with other operating
<para>However, if you need &os; to co-exist with other operating
systems then you need to have a rough understanding of how data is
laid out on the disk, and how this affects you.</para>
@ -320,7 +320,7 @@
&os; internally also has partitions, the naming
can become confusing very quickly, therefore these
disk chunks are referred to as disk slices or simply slices
in &os; itself. For example, the FreeBSD utility
in &os; itself. For example, the &os; utility
<command>fdisk</command> which operates on the PC disk partitions,
refers to slices instead of partitions. By design, the PC only
supports four partitions per disk. These partitions are called
@ -332,7 +332,7 @@
extended partition.</para>
<para>Each partition has a <firstterm>partition ID</firstterm>, which is
a number used to identify the type of data on the partition. FreeBSD
a number used to identify the type of data on the partition. &os;
partitions have the partition ID of <literal>165</literal>.</para>
<para>In general, each operating system that you use will identify
@ -341,16 +341,16 @@
<firstterm>drive letter</firstterm>, starting with
<devicename>C:</devicename>.</para>
<para>FreeBSD must be installed into a primary partition. FreeBSD can
<para>&os; must be installed into a primary partition. &os; can
keep all its data, including any files that you create, on this one
partition. However, if you have multiple disks, then you can create a
FreeBSD partition on all, or some, of them. When you install FreeBSD,
&os; partition on all, or some, of them. When you install &os;,
you must have one partition available. This might be a blank
partition that you have prepared, or it might be an existing partition
that contains data that you no longer care about.</para>
<para>If you are already using all the partitions on all your disks, then
you will have to free one of them for FreeBSD using the tools
you will have to free one of them for &os; using the tools
provided by the other operating systems you use (e.g.,
<command>fdisk</command> on &ms-dos; or &windows;).</para>
@ -358,7 +358,7 @@
may need to shrink one or more of your existing partitions
first.</para>
<para>A minimal installation of FreeBSD takes as little as 100&nbsp;MB
<para>A minimal installation of &os; takes as little as 100&nbsp;MB
of disk
space. However, that is a <emphasis>very</emphasis> minimal install,
leaving almost no space for your own files. A more realistic minimum
@ -404,7 +404,7 @@
<para>This means that your disk has two partitions on it, one per
drive letter. You can copy all your existing data from
<devicename>D:</devicename> to <devicename>C:</devicename>, which
will free up the second partition, ready for FreeBSD.</para>
will free up the second partition, ready for &os;.</para>
</example>
<example>
@ -414,10 +414,10 @@
that already has a version of &windows; installed. When you installed
&windows; you created one large partition, giving you a
<devicename>C:</devicename> drive that is 4&nbsp;GB in size. You are
currently using 1.5&nbsp;GB of space, and want FreeBSD to have 2&nbsp;GB
currently using 1.5&nbsp;GB of space, and want &os; to have 2&nbsp;GB
of space.</para>
<para>In order to install FreeBSD you will need to either:</para>
<para>In order to install &os; you will need to either:</para>
<orderedlist>
<listitem>
@ -439,12 +439,12 @@
<sect2>
<title>Collect Your Network Configuration Details</title>
<para>If you intend to connect to a network as part of your FreeBSD
<para>If you intend to connect to a network as part of your &os;
installation (for example, if you will be installing from an FTP
site or an
NFS server), then you need to know your network configuration. You
will be prompted for this information during the installation so that
FreeBSD can connect to the network to complete the install.</para>
&os; can connect to the network to complete the install.</para>
<sect3>
<title>Connecting to an Ethernet Network or Cable/DSL Modem</title>
@ -485,7 +485,7 @@
<title>Connecting Using a Modem</title>
<para>If you dial up to an ISP using a regular modem then you can
still install FreeBSD over the Internet, it will just take a very
still install &os; over the Internet, it will just take a very
long time.</para>
<para>You will need to know:</para>
@ -506,14 +506,14 @@
</sect3>
</sect2>
<sect2>
<title>Check for FreeBSD Errata</title>
<title>Check for &os; Errata</title>
<para>Although the FreeBSD project strives to ensure that each release
of FreeBSD is as stable as possible, bugs do occasionally creep into
<para>Although the &os; project strives to ensure that each release
of &os; is as stable as possible, bugs do occasionally creep into
the process. On very rare occasions those bugs affect the
installation process. As these problems are discovered and fixed, they
are noted in the <ulink url="http://www.FreeBSD.org/releases/&rel.current;R/errata.html">FreeBSD Errata</ulink>,
which is found on the FreeBSD web site. You
are noted in the <ulink url="http://www.FreeBSD.org/releases/&rel.current;R/errata.html">&os; Errata</ulink>,
which is found on the &os; web site. You
should check the errata before installing to make sure that there are
no late-breaking problems which you should be aware of.</para>
@ -523,13 +523,13 @@
url="&url.base;/releases/index.html">release
information</ulink> section of the
<ulink
url="&url.base;/index.html">FreeBSD web site</ulink>.</para>
url="&url.base;/index.html">&os; web site</ulink>.</para>
</sect2>
<sect2>
<title>Obtain the FreeBSD Installation Files</title>
<title>Obtain the &os; Installation Files</title>
<para>The FreeBSD installation process can install FreeBSD from files
<para>The &os; installation process can install &os; from files
located in any of the following places:</para>
<itemizedlist>
@ -573,13 +573,13 @@
</listitem>
</itemizedlist>
<para>If you have purchased FreeBSD on CD or DVD then you already have
<para>If you have purchased &os; on CD or DVD then you already have
everything you need, and should proceed to the next section
(<xref linkend="install-boot-media"/>).</para>
<para>If you have not obtained the FreeBSD installation files you should
<para>If you have not obtained the &os; installation files you should
skip ahead to <xref linkend="install-diff-media"/> which explains how
to prepare to install FreeBSD from any of the above. After reading
to prepare to install &os; from any of the above. After reading
that section, you should come back here, and read on to
<xref linkend="install-boot-media"/>.</para>
</sect2>
@ -587,21 +587,20 @@
<sect2 id="install-boot-media">
<title>Prepare the Boot Media</title>
<para>The FreeBSD installation process is started by booting your
computer into the FreeBSD installer&mdash;it is not a program you run
within another operating system. Your computer normally boots using
the operating system installed on your hard disk, but it can also be
configured to use a <quote>bootable</quote> floppy disk.
Most modern computers can also
boot from a CDROM in the CDROM drive or from a USB disk.</para>
<para>The &os; installation process is started by booting the
computer into the &os; installer&mdash;it is not a program you run
within another operating system. The computer normally boots
using the operating system installed on the hard disk, but it
can also be configured to boot from a CDROM or from a USB
disk.</para>
<tip>
<para>If you have FreeBSD on CDROM or DVD (either one you purchased
<para>If you have &os; on CDROM or DVD (either one you purchased
or you prepared yourself), and your computer allows you to boot from
the CDROM or DVD (typically a BIOS option called <quote>Boot
Order</quote> or similar), then you can skip this section. The
FreeBSD CDROM and DVD images are bootable and can be used to install
FreeBSD without any other special preparation.</para>
&os; CDROM and DVD images are bootable and can be used to install
&os; without any other special preparation.</para>
</tip>
<para>To create a bootable memory stick, follow these
@ -650,7 +649,7 @@
<title>Write The Image File to the Memory Stick</title>
<procedure>
<title>Using FreeBSD To Write the Image</title>
<title>Using &os; To Write the Image</title>
<warning>
<para>The example below
@ -718,43 +717,27 @@
</step>
</procedure>
<para>To create boot floppy images, follow these steps:</para>
<para>To create the boot floppy images for a &os;/&arch.pc98;
installation, follow these steps:</para>
<procedure>
<step>
<title>Acquire the Boot Floppy Images</title>
<important>
<para>Please note, as of &os;&nbsp;8.<replaceable>X</replaceable>, floppy disk images are
no longer available. Please see above for instructions
on how to install &os; using a USB memory stick or just
use a CDROM or a DVD.</para>
</important>
<para>The &os;/&arch.pc98; boot disks
can be downloaded from the floppies directory,
<literal>ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/pc98/<replaceable>version</replaceable>-RELEASE/floppies/</literal>.
Replace <replaceable>version</replaceable> with the
version number to install.</para>
<para>The boot disks are available on your installation media
in the <filename>floppies/</filename> directory, and
can also be downloaded from the floppies directory,
<literal>ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/<replaceable>arch</replaceable>/<replaceable>version</replaceable>-RELEASE/floppies/</literal>.
Replace <replaceable>arch</replaceable> and
<replaceable>version</replaceable>
with the architecture and the version number
which you want to install, respectively.
For example, the boot floppy images for
&os;/&arch.i386;&nbsp;&rel2.current;-RELEASE are available
from <ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel2.current;-RELEASE/floppies/"></ulink>.</para>
<para>The floppy images have a <filename>.flp</filename> extension.
The <filename>floppies/</filename> directory contains a number of
different images, and the ones you will need to use depends on the
version of FreeBSD you are installing, and in some cases, the
hardware you are installing to.
In most cases you will need four
floppies, <filename>boot.flp</filename>,
<filename>kern1.flp</filename>,
<filename>kern2.flp</filename>, and
<filename>kern3.flp</filename>. Check
<filename>README.TXT</filename> in the same directory for the
most up to date information about these floppy images.</para>
<para>The floppy images have a <filename>.flp</filename>
extension. <filename
class="directory">floppies/</filename> contains a number
of different images. Download
<filename>boot.flp</filename> as well as the number of
files associated with the type of installation, such as
<literal>kern.small*</literal> or
<literal>kern*</literal>.</para>
<important>
<para>Your FTP program must use <emphasis>binary mode</emphasis>
@ -768,7 +751,7 @@
<step>
<title>Prepare the Floppy Disks</title>
<para>You must prepare one floppy disk per image file you had to
<para>Prepare one floppy disk per image file you had to
download. It is imperative that these disks are free from
defects. The easiest way to test this is to format the disks
for yourself. Do not trust pre-formatted floppies. The format
@ -778,9 +761,9 @@
floppies if choosing this installation route.</para>
<important>
<para>If you try to install FreeBSD and the installation
<para>If you try to install &os; and the installation
program crashes, freezes, or otherwise misbehaves, one of
the first things to suspect is the floppies. Try writing
the first things to suspect is the floppies. Write
the floppy image files to new disks and try
again.</para>
</important>
@ -816,16 +799,16 @@
the CDROM, then <command>fdimage</command> can be downloaded from
the <ulink
url="ftp://ftp.FreeBSD.org/pub/FreeBSD/tools/"><filename class="directory">tools</filename>
directory</ulink> on the FreeBSD FTP site.</para>
directory</ulink> on the &os; FTP site.</para>
<para>If you are writing the floppies on a &unix; system (such as
another FreeBSD system) you can use the &man.dd.1; command to
write the image files directly to disk. On FreeBSD, you would
another &os; system) you can use the &man.dd.1; command to
write the image files directly to disk. On &os;, you would
run:</para>
<screen>&prompt.root; <userinput>dd if=boot.flp of=/dev/fd0</userinput></screen>
<para>On FreeBSD, <filename>/dev/fd0</filename> refers to the
<para>On &os;, <filename>/dev/fd0</filename> refers to the
first floppy disk (the <devicename>A:</devicename> drive).
<filename>/dev/fd1</filename> would be the
<devicename>B:</devicename> drive, and so on. Other &unix;
@ -835,7 +818,7 @@
</step>
</procedure>
<para>You are now ready to start installing FreeBSD.</para>
<para>You are now ready to start installing &os;.</para>
</sect2>
</sect1>
@ -913,12 +896,12 @@ We can take no responsibility for lost disk contents!</literallayout>
opportunity.</para>
<note>
<para>For &os;&nbsp;7.<replaceable>X</replaceable>, installation
boot floppies are available and can be prepared as
described in <xref linkend="install-boot-media"/>. One of
them will be the first boot disc:
<filename>boot.flp</filename>. Put this disc in your
floppy drive and boot the computer.</para>
<para>For &os;/&arch.pc98;, installation boot floppies are
available and can be prepared as described in <xref
linkend="install-boot-media"/>. The first floppy
disc will contain <filename>boot.flp</filename>. Put
this floppy in the floppy drive to boot into the
installer.</para>
</note>
<para>If your computer starts up as normal and loads your existing
@ -944,7 +927,7 @@ We can take no responsibility for lost disk contents!</literallayout>
</step>
<step>
<para>FreeBSD will start to boot. If you are booting from CDROM you
<para>&os; will start to boot. If you are booting from CDROM you
will see a display similar to this (version information
omitted):</para>
@ -1150,7 +1133,7 @@ Mounting root from ufs:/dev/md0c
/stand/sysinstall running as init on vty0</screen>
</figure>
<para>Check the probe results carefully to make sure that FreeBSD found
<para>Check the probe results carefully to make sure that &os; found
all the devices you expected. If a device was not found, then it will
not be listed. A <link linkend="kernelconfig">custom kernel</link>
allows you to add in support for devices which are not in the
@ -1197,7 +1180,7 @@ Mounting root from ufs:/dev/md0c
<title>Introducing Sysinstall</title>
<para>The <application>sysinstall</application> utility is the installation
application provided by the FreeBSD Project. It is console based and is
application provided by the &os; Project. It is console based and is
divided into a number of menus and screens that you can use to
configure and control the installation process.</para>
@ -1354,7 +1337,7 @@ Mounting root from ufs:/dev/md0c
<title>Begin a Standard Installation</title>
<para>The <guimenuitem>Standard</guimenuitem> installation is the
option recommended for those new to &unix; or FreeBSD. Use the arrow
option recommended for those new to &unix; or &os;. Use the arrow
keys to select <guimenuitem>Standard</guimenuitem> and
then press <keycap>Enter</keycap> to start the installation.</para>
@ -1373,15 +1356,15 @@ Mounting root from ufs:/dev/md0c
<sect1 id="install-steps">
<title>Allocating Disk Space</title>
<para>Your first task is to allocate disk space for FreeBSD, and label
<para>Your first task is to allocate disk space for &os;, and label
that space so that <application>sysinstall</application> can prepare
it. In order to do this you need to know how FreeBSD expects to find
it. In order to do this you need to know how &os; expects to find
information on the disk.</para>
<sect2 id="install-drive-bios-numbering">
<title>BIOS Drive Numbering</title>
<para>Before you install and configure FreeBSD on your system, there is an
<para>Before you install and configure &os; on your system, there is an
important subject that you should be aware of, especially if you have
multiple hard drives.</para>
@ -1410,14 +1393,14 @@ Mounting root from ufs:/dev/md0c
fashion for up to seven drives.</para>
<para>A user who is accustomed to taking advantage of these features may
become surprised when the results with FreeBSD are not as expected.
FreeBSD does not use the BIOS, and does not know the <quote>logical BIOS
become surprised when the results with &os; are not as expected.
&os; does not use the BIOS, and does not know the <quote>logical BIOS
drive mapping</quote>. This can lead to very perplexing situations,
especially when drives are physically identical in geometry, and have
also been made as data clones of one another.</para>
<para>When using FreeBSD, always restore the BIOS to natural drive
numbering before installing FreeBSD, and then leave it that way. If you
<para>When using &os;, always restore the BIOS to natural drive
numbering before installing &os;, and then leave it that way. If you
need to switch drives around, then do so, but do it the hard way, and
open the case and move the jumpers and cables.</para>
@ -1425,9 +1408,9 @@ Mounting root from ufs:/dev/md0c
<title>An Illustration from the Files of Bill and Fred's Exceptional
Adventures:</title>
<para>Bill breaks-down an older Wintel box to make another FreeBSD box
<para>Bill breaks-down an older Wintel box to make another &os; box
for Fred. Bill installs a single SCSI drive as SCSI unit zero and
installs FreeBSD on it.</para>
installs &os; on it.</para>
<para>Fred begins using the system, but after several days notices that
the older SCSI drive is reporting numerous soft errors and reports
@ -1442,21 +1425,21 @@ Mounting root from ufs:/dev/md0c
that the new drive is installed and functioning nicely, Bill decides
that it is a good idea to start using it, so he uses features in the
SCSI BIOS to re-order the disk drives so that the system boots from
SCSI unit four. FreeBSD boots and runs just fine.</para>
SCSI unit four. &os; boots and runs just fine.</para>
<para>Fred continues his work for several days, and soon Bill and Fred
decide that it is time for a new adventure &mdash; time to upgrade
to a
newer version of FreeBSD. Bill removes SCSI unit zero because it was
newer version of &os;. Bill removes SCSI unit zero because it was
a bit flaky and replaces it with another identical disk drive from
the <quote>archive</quote>. Bill then installs the new version of
FreeBSD onto the new SCSI unit zero using Fred's magic Internet FTP
&os; onto the new SCSI unit zero using Fred's magic Internet FTP
floppies. The installation goes well.</para>
<para>Fred uses the new version of FreeBSD for a few days, and certifies
<para>Fred uses the new version of &os; for a few days, and certifies
that it is good enough for use in the engineering department. It is
time to copy all of his work from the old version. So Fred mounts
SCSI unit four (the latest copy of the older FreeBSD version). Fred
SCSI unit four (the latest copy of the older &os; version). Fred
is dismayed to find that none of his precious work is present on SCSI
unit four.</para>
@ -1466,11 +1449,11 @@ Mounting root from ufs:/dev/md0c
SCSI unit four, unit four became the <quote>new clone</quote>.
When Bill re-ordered the SCSI BIOS so that he could boot from
SCSI unit four, he was only fooling himself.
FreeBSD was still running on SCSI unit zero.
&os; was still running on SCSI unit zero.
Making this kind of BIOS change will cause some or all of the Boot and
Loader code to be fetched from the selected BIOS drive, but when the
FreeBSD kernel drivers take-over, the BIOS drive numbering will be
ignored, and FreeBSD will transition back to normal drive numbering.
&os; kernel drivers take-over, the BIOS drive numbering will be
ignored, and &os; will transition back to normal drive numbering.
In the illustration at hand, the system continued to operate on the
original SCSI unit zero, and all of Fred's data was there, not on SCSI
unit four. The fact that the system appeared to be running on SCSI
@ -1538,7 +1521,7 @@ Mounting root from ufs:/dev/md0c
<para>Consider what would happen if you had two IDE hard disks, one
as the master on the first IDE controller, and one as the master on
the second IDE controller. If FreeBSD numbered these as it found
the second IDE controller. If &os; numbered these as it found
them, as <devicename>ad0</devicename> and
<devicename>ad1</devicename> then everything would work.</para>
@ -1548,7 +1531,7 @@ Mounting root from ufs:/dev/md0c
<devicename>ad2</devicename>. Because device names (such as
<devicename>ad1s1a</devicename>) are used to find filesystems, you
may suddenly discover that some of your filesystems no longer
appear correctly, and you would need to change your FreeBSD
appear correctly, and you would need to change your &os;
configuration.</para>
<para>To work around this, the kernel can be configured to name IDE
@ -1559,13 +1542,13 @@ Mounting root from ufs:/dev/md0c
<devicename>ad0</devicename> or <devicename>ad1</devicename>
devices.</para>
<para>This configuration is the default for the FreeBSD kernel, which
<para>This configuration is the default for the &os; kernel, which
is why this display shows <devicename>ad0</devicename> and
<devicename>ad2</devicename>. The machine on which this screenshot
was taken had IDE disks on both master channels of the IDE
controllers, and no disks on the slave channels.</para>
<para>You should select the disk on which you want to install FreeBSD,
<para>You should select the disk on which you want to install &os;,
and then press &gui.ok;.
<application>FDisk</application> will start, with a display similar to
that shown in <xref linkend="sysinstall-fdisk1"/>.</para>
@ -1574,11 +1557,11 @@ Mounting root from ufs:/dev/md0c
sections.</para>
<para>The first section, covering the first two lines of the display,
shows details about the currently selected disk, including its FreeBSD
shows details about the currently selected disk, including its &os;
name, the disk geometry, and the total size of the disk.</para>
<para>The second section shows the slices that are currently on the
disk, where they start and end, how large they are, the name FreeBSD
disk, where they start and end, how large they are, the name &os;
gives them, and their description and sub-type. This example shows two
small unused slices, which are artifacts of disk layout schemes on the
PC. It also shows one large <acronym>FAT</acronym> slice, which
@ -1602,15 +1585,15 @@ Mounting root from ufs:/dev/md0c
<para>What you do now will depend on how you want to slice up your
disk.</para>
<para>If you want to use FreeBSD for the entire disk (which will delete
<para>If you want to use &os; for the entire disk (which will delete
all the other data on this disk when you confirm that you want
<application>sysinstall</application> to continue later in the
installation process) then you can press <keycap>A</keycap>, which
corresponds to the <guimenuitem>Use Entire Disk</guimenuitem> option.
The existing slices will be removed, and replaced with a small area
flagged as <literal>unused</literal> (again, an artifact of PC disk
layout), and then one large slice for FreeBSD. If you do this, then
you should select the newly created FreeBSD slice using the arrow
layout), and then one large slice for &os;. If you do this, then
you should select the newly created &os; slice using the arrow
keys, and press <keycap>S</keycap> to mark the slice as being
bootable. The screen will then look very similar to
<xref linkend="sysinstall-fdisk2"/>. Note the
@ -1619,7 +1602,7 @@ Mounting root from ufs:/dev/md0c
booted from.</para>
<para>If you will be deleting an existing slice to make space for
FreeBSD then you should select the slice using the arrow keys, and
&os; then you should select the slice using the arrow keys, and
then press <keycap>D</keycap>. You can then press <keycap>C</keycap>,
and be prompted for size of slice you want to create. Enter the
appropriate figure and press <keycap>Enter</keycap>. The default
@ -1627,7 +1610,7 @@ Mounting root from ufs:/dev/md0c
make, which could be the largest contiguous block of unallocated
space or the size of the entire hard disk.</para>
<para>If you have already made space for FreeBSD (perhaps by using a
<para>If you have already made space for &os; (perhaps by using a
tool such as <application>&partitionmagic;</application>) then you can
press <keycap>C</keycap> to create a new slice. Again, you will be
prompted for the size of slice you would like to create.</para>
@ -1651,26 +1634,26 @@ Mounting root from ufs:/dev/md0c
<title>Install a Boot Manager</title>
<para>You now have the option to install a boot manager. In general,
you should choose to install the FreeBSD boot manager if:</para>
you should choose to install the &os; boot manager if:</para>
<itemizedlist>
<listitem>
<para>You have more than one drive, and have installed FreeBSD onto
<para>You have more than one drive, and have installed &os; onto
a drive other than the first one.</para>
</listitem>
<listitem>
<para>You have installed FreeBSD alongside another operating system
on the same disk, and you want to choose whether to start FreeBSD
<para>You have installed &os; alongside another operating system
on the same disk, and you want to choose whether to start &os;
or the other operating system when you start the computer.</para>
</listitem>
</itemizedlist>
<para>If FreeBSD is going to be the only operating system on
<para>If &os; is going to be the only operating system on
this machine, installed on the first hard disk, then the
<guimenuitem>Standard</guimenuitem> boot manager will suffice.
Choose <guimenuitem>None</guimenuitem> if you are using a
third-party boot manager capable of booting FreeBSD.</para>
third-party boot manager capable of booting &os;.</para>
<para>Make your choice and press <keycap>Enter</keycap>.</para>
@ -1694,13 +1677,13 @@ Mounting root from ufs:/dev/md0c
<para>If there is more than one drive, it will return to the
Select Drives screen after the boot manager selection. If you wish to
install FreeBSD on to more than one disk, then you can select another
install &os; on to more than one disk, then you can select another
disk here and repeat the slice process using
<application>FDisk</application>.</para>
<important>
<para>If you are installing FreeBSD on a drive other than your
first, then the FreeBSD boot manager needs to be installed on
<para>If you are installing &os; on a drive other than your
first, then the &os; boot manager needs to be installed on
both drives.</para>
</important>
@ -1737,10 +1720,10 @@ Mounting root from ufs:/dev/md0c
<para>Certain applications can benefit from particular partition
schemes, especially if you are laying out partitions across more than
one disk. However, for this, your first FreeBSD installation, you do
one disk. However, for this, your first &os; installation, you do
not need to give too much thought to how you partition the disk. It
is more important that you install FreeBSD and start learning how to
use it. You can always re-install FreeBSD to change your partition
is more important that you install &os; and start learning how to
use it. You can always re-install &os; to change your partition
scheme when you are more familiar with the operating system.</para>
<para>This scheme features four partitions&mdash;one for swap space, and
@ -1778,11 +1761,11 @@ Mounting root from ufs:/dev/md0c
<entry>This is the root filesystem. Every other filesystem
will be mounted somewhere under this one. 1&nbsp;GB is a
reasonable size for this filesystem. You will not be storing
too much data on it, as a regular FreeBSD install will put
too much data on it, as a regular &os; install will put
about 128&nbsp;MB of data here. The remaining space is for
temporary data, and also leaves expansion space if future
versions of
FreeBSD need more space in <filename>/</filename>.</entry>
&os; need more space in <filename>/</filename>.</entry>
</row>
<row>
@ -1802,7 +1785,7 @@ Mounting root from ufs:/dev/md0c
the swap amount to 64&nbsp;MB.</para><para>
If you have more than one disk then you can put swap
space on each disk. FreeBSD will then use each disk for
space on each disk. &os; will then use each disk for
swap, which effectively speeds up the act of swapping. In
this case, calculate the total amount of swap you need
(e.g., 128&nbsp;MB), and then divide this by the number of
@ -1822,8 +1805,8 @@ Mounting root from ufs:/dev/md0c
files that are constantly varying;
log files, and other administrative files. Many
of these files are read-from or written-to extensively during
FreeBSD's day-to-day running. Putting these files on another
filesystem allows FreeBSD to optimize the access of these
&os;'s day-to-day running. Putting these files on another
filesystem allows &os; to optimize the access of these
files without affecting other files in other directories that
do not have the same access pattern.</entry>
</row>
@ -1849,7 +1832,7 @@ Mounting root from ufs:/dev/md0c
Defaults</literal> by the &os; partition editor.</para>
</warning>
<para>If you will be installing FreeBSD on to more than one disk then
<para>If you will be installing &os; on to more than one disk then
you must also create partitions in the other slices that you
configured. The easiest way to do this is to create two partitions on
each disk, one for the swap space, and one for a filesystem.</para>
@ -2078,7 +2061,7 @@ Mounting root from ufs:/dev/md0c
<filename>/usr</filename>, you can leave the suggested size as is, to
use the rest of the slice.</para>
<para>Your final FreeBSD DiskLabel Editor screen will appear similar to
<para>Your final &os; DiskLabel Editor screen will appear similar to
<xref linkend="sysinstall-label4"/>, although your values chosen may
be different. Press <keycap>Q</keycap> to finish.</para>
@ -2104,7 +2087,7 @@ Mounting root from ufs:/dev/md0c
on the intended use of the system and the amount of disk space
available. The predefined options range from installing the
smallest possible configuration to everything. Those who are
new to &unix; and/or FreeBSD should almost certainly select one
new to &unix; and/or &os; should almost certainly select one
of these canned options. Customizing a distribution set is
typically for the more experienced user.</para>
@ -2149,7 +2132,7 @@ Mounting root from ufs:/dev/md0c
<title>Installing the Ports Collection</title>
<para>After selecting the desired distribution, an opportunity to
install the FreeBSD Ports Collection is presented. The ports
install the &os; Ports Collection is presented. The ports
collection is an easy and convenient way to install software.
The Ports Collection does not contain the source code necessary
to compile the software. Instead, it is a collection of files which
@ -2160,10 +2143,10 @@ Mounting root from ufs:/dev/md0c
<para>The installation program does not check to see if you have
adequate space. Select this option only if you have
adequate hard disk space. As of FreeBSD &rel.current;, the FreeBSD
adequate hard disk space. As of &os; &rel.current;, the &os;
Ports Collection takes up about &ports.size; of disk space.
You can safely assume a larger value for more recent versions
of FreeBSD.</para>
of &os;.</para>
<screen> User Confirmation Requested
Would you like to install the FreeBSD ports collection?
@ -2392,7 +2375,7 @@ installation menus to retry whichever operations have failed.
<para>Configuration of various options follows the successful
installation. An option can be configured by re-entering the
configuration options before booting the new FreeBSD
configuration options before booting the new &os;
system or after installation using
<command>sysinstall</command>
and selecting
@ -2406,7 +2389,7 @@ installation menus to retry whichever operations have failed.
above.</para>
<para>For detailed information on Local Area Networks and
configuring FreeBSD as a gateway/router refer to the
configuring &os; as a gateway/router refer to the
<link linkend="advanced-networking">Advanced Networking</link>
chapter.</para>
@ -3060,31 +3043,6 @@ Press [Enter] now to invoke an editor on /etc/exports
the post-installation configuration.</para>
</sect2>
<sect2 id="linuxcomp">
<title>Linux Compatibility</title>
<note>
<para>This part only applies to &os;&nbsp;7.<replaceable>X</replaceable>
installation, if you install &os;&nbsp;8.<replaceable>X</replaceable>
this screen will not be proposed.</para>
</note>
<screen> User Confirmation Requested
Would you like to enable Linux binary compatibility?
[ Yes ] No</screen>
<para>Selecting &gui.yes; and pressing
<keycap>Enter</keycap> will allow
running Linux software on FreeBSD. The install will add
the appropriate packages for Linux compatibility.</para>
<para>If installing by FTP, the machine will need to be connected to
the Internet. Sometimes a remote ftp site will not have all the
distributions like the Linux binary compatibility. This can
be installed later if necessary.</para>
</sect2>
<sect2 id="mouse">
<title>Mouse Settings</title>
@ -3961,7 +3919,7 @@ Password:</screen>
</sect2>
<sect2 id="shutdown">
<title>FreeBSD Shutdown</title>
<title>&os; Shutdown</title>
<para>It is important to properly shutdown the operating
system. Do not just turn off power. First, become a superuser by
@ -4001,7 +3959,7 @@ Please press any key to reboot.</screen>
</indexterm>
<para>The following section covers basic installation troubleshooting,
such as common problems people have reported. There are also a few
questions and answers for people wishing to dual-boot FreeBSD with
questions and answers for people wishing to dual-boot &os; with
&ms-dos; or &windows;.</para>
<sect2>
@ -4318,11 +4276,11 @@ Please press any key to reboot.</screen>
<title>Advanced Installation Guide</title>
<para>This section describes how to install FreeBSD in exceptional
<para>This section describes how to install &os; in exceptional
cases.</para>
<sect2 id="headless-install">
<title>Installing FreeBSD on a System without a Monitor or
<title>Installing &os; on a System without a Monitor or
Keyboard</title>
<indexterm>
@ -4332,7 +4290,7 @@ Please press any key to reboot.</screen>
<indexterm><primary>serial console</primary></indexterm>
<para>This type of installation is called a <quote>headless
install</quote>, because the machine that you are trying to install
FreeBSD on either does not have a monitor attached to it, or does not
&os; on either does not have a monitor attached to it, or does not
even have a VGA output. How is this possible you ask? Using a
serial console. A serial console is basically using another
machine to act as the main display and keyboard for a
@ -4355,8 +4313,8 @@ Please press any key to reboot.</screen>
<primary><command>mount</command></primary>
</indexterm>
<para>If you were to boot into the USB stick that you just
made, FreeBSD would boot into its normal install mode. We
want FreeBSD to boot into a serial console for our
made, &os; would boot into its normal install mode. We
want &os; to boot into a serial console for our
install. To do this, you have to mount the
USB disk onto your &os;
system using the &man.mount.8; command.</para>
@ -4466,11 +4424,6 @@ Please press any key to reboot.</screen>
<screen>&prompt.root; <userinput>cu -l /dev/cuau0</userinput></screen>
<para>On &os;&nbsp;7.<replaceable>X</replaceable> use the following command
instead:</para>
<screen>&prompt.root; <userinput>cu -l /dev/cuad0</userinput></screen>
</step>
</procedure>
@ -4478,7 +4431,7 @@ Please press any key to reboot.</screen>
through your <command>cu</command> session. It will load the kernel
and then it will come up
with a selection of what kind of terminal to use. Select the
FreeBSD color console and proceed with your install!</para>
&os; color console and proceed with your install!</para>
</sect2>
</sect1>
@ -4487,13 +4440,13 @@ Please press any key to reboot.</screen>
<title>Preparing Your Own Installation Media</title>
<note>
<para>To prevent repetition, <quote>FreeBSD disc</quote> in this context
means a FreeBSD CDROM or DVD that you have purchased or produced
<para>To prevent repetition, <quote>&os; disc</quote> in this context
means a &os; CDROM or DVD that you have purchased or produced
yourself.</para>
</note>
<para>There may be some situations in which you need to create your own
FreeBSD installation media and/or source. This might be physical media,
&os; installation media and/or source. This might be physical media,
such as a tape, or a source that <application>sysinstall</application>
can use to retrieve the files, such as a local FTP site, or an &ms-dos;
partition.</para>
@ -4503,16 +4456,16 @@ Please press any key to reboot.</screen>
<itemizedlist>
<listitem>
<para>You have many machines connected to your local network, and one
FreeBSD disc. You want to create a local FTP site using the
contents of the FreeBSD disc, and then have your machines use this
&os; disc. You want to create a local FTP site using the
contents of the &os; disc, and then have your machines use this
local FTP site instead of needing to connect to the Internet.</para>
</listitem>
<listitem>
<para>You have a FreeBSD disc, and FreeBSD does not recognize your
<para>You have a &os; disc, and &os; does not recognize your
CD/DVD drive, but &ms-dos; / &windows; does. You want to copy the
FreeBSD installation files to a &ms-dos; partition on the same
computer, and then install FreeBSD using those files.</para>
&os; installation files to a &ms-dos; partition on the same
computer, and then install &os; using those files.</para>
</listitem>
<listitem>
@ -4524,19 +4477,19 @@ Please press any key to reboot.</screen>
<listitem>
<para>You want to create a tape that can be used to install
FreeBSD.</para>
&os;.</para>
</listitem>
</itemizedlist>
<sect2 id="install-cdrom">
<title>Creating an Installation CDROM</title>
<para>As part of each release, the FreeBSD project makes available at
<para>As part of each release, the &os; project makes available at
least two CDROM images (<quote>ISO images</quote>) per supported
architecture. These images can be written
(<quote>burned</quote>) to CDs if you have a CD writer, and then used
to install FreeBSD. If you have a CD writer, and bandwidth is cheap,
then this is the easiest way to install FreeBSD.</para>
to install &os;. If you have a CD writer, and bandwidth is cheap,
then this is the easiest way to install &os;.</para>
<procedure>
<step>
@ -4549,7 +4502,7 @@ Please press any key to reboot.</screen>
<para>That directory will normally contain the following images:</para>
<table frame="none">
<title>FreeBSD 7.<replaceable>X</replaceable> and 8.<replaceable>X</replaceable>
<title>&os; 8.<replaceable>X</replaceable>
ISO Image Names and Meanings</title>
<tgroup cols="2">
@ -4576,7 +4529,7 @@ Please press any key to reboot.</screen>
<entry><filename>&os;-<replaceable>version</replaceable>-RELEASE-<replaceable>arch</replaceable>-dvd1.iso.gz</filename></entry>
<entry>This DVD image contains everything necessary to
install the base FreeBSD operating system, a
install the base &os; operating system, a
collection of pre-built packages, and the
documentation. It also supports booting into a
<quote>livefs</quote> based rescue mode.</entry>
@ -4590,7 +4543,7 @@ Please press any key to reboot.</screen>
off USB drives. It also supports booting into a
<quote>livefs</quote> based rescue mode. The
documentation packages are provided but no other
packages. This image is not available for &os;&nbsp;7.<replaceable>X</replaceable>.</entry>
packages.</entry>
</row>
<row>
@ -4635,14 +4588,6 @@ Please press any key to reboot.</screen>
</tgroup>
</table>
<note>
<para>&os;&nbsp;7.<replaceable>X</replaceable> releases before
&os;&nbsp;7.3 and &os;&nbsp;8.0 used a
different naming convention. The names of their ISO
images are not prefixed with
<literal>&os;-</literal>.</para>
</note>
<para>You <emphasis>must</emphasis> download one of either
the <literal>bootonly</literal> ISO image,
or the image of <literal>disc1</literal>. Do not download
@ -4670,7 +4615,7 @@ Please press any key to reboot.</screen>
<title>Write the CDs</title>
<para>You must then write the CD images to disc. If you will be
doing this on another FreeBSD system then see
doing this on another &os; system then see
<xref linkend="creating-cds"/> for more information (in
particular, <xref linkend="burncd"/> and
<xref linkend="cdrecord"/>).</para>
@ -4683,14 +4628,14 @@ Please press any key to reboot.</screen>
</procedure>
<note><para>If you are interested in building a customized
release of FreeBSD, please see the <ulink
release of &os;, please see the <ulink
url="&url.articles.releng;">Release Engineering
Article</ulink>.</para></note>
</sect2>
<sect2 id="install-ftp">
<title>Creating a Local FTP Site with a FreeBSD Disc</title>
<title>Creating a Local FTP Site with a &os; Disc</title>
<indexterm>
<primary>installation</primary>
@ -4698,13 +4643,13 @@ Please press any key to reboot.</screen>
<tertiary>FTP</tertiary>
</indexterm>
<para>FreeBSD discs are laid out in the same way as the FTP site. This
<para>&os; discs are laid out in the same way as the FTP site. This
makes it very easy for you to create a local FTP site that can be used
by other machines on your network when installing FreeBSD.</para>
by other machines on your network when installing &os;.</para>
<procedure>
<step>
<para>On the FreeBSD computer that will host the FTP site, ensure
<para>On the &os; computer that will host the FTP site, ensure
that the CDROM is in the drive, and mounted on
<filename>/cdrom</filename>.</para>
@ -4782,7 +4727,7 @@ Please press any key to reboot.</screen>
the use of improperly formatted media, which is why we are
making a point of it now.</para>
<para>If you are creating the floppies on another FreeBSD machine,
<para>If you are creating the floppies on another &os; machine,
a format is still not a bad idea, though you do not need to put
a &ms-dos; filesystem on each floppy. You can use the
<command>bsdlabel</command> and <command>newfs</command>
@ -4835,7 +4780,7 @@ Please press any key to reboot.</screen>
reproduced within this directory, so we suggest using the &ms-dos;
<command>xcopy</command> command if you are copying it from a CD.
For example, to prepare for a minimal installation of
FreeBSD:</para>
&os;:</para>
<screen><prompt>C:\&gt;</prompt> <userinput>md c:\freebsd</userinput>
<prompt>C:\&gt;</prompt> <userinput>xcopy e:\bin c:\freebsd\bin\ /s</userinput>
@ -4914,12 +4859,12 @@ Please press any key to reboot.</screen>
Parallel port (PLIP (laplink cable)).</para>
<para>For the fastest possible network installation, an
Ethernet adapter is always a good choice! FreeBSD supports most
Ethernet adapter is always a good choice! &os; supports most
common PC Ethernet cards; a table of supported cards (and their
required settings) is provided in the Hardware Notes for each
release of FreeBSD. If you are using one of the supported PCMCIA
release of &os;. If you are using one of the supported PCMCIA
Ethernet cards, also be sure that it is plugged in
<emphasis>before</emphasis> the laptop is powered on! FreeBSD does
<emphasis>before</emphasis> the laptop is powered on! &os; does
not, unfortunately, currently support hot insertion of PCMCIA cards
during installation.</para>
@ -4957,7 +4902,7 @@ Please press any key to reboot.</screen>
If you have problems, logging can be directed to the screen using
the command <command>set log local ...</command>.</para>
<para>If a hard-wired connection to another FreeBSD
<para>If a hard-wired connection to another &os;
machine is available, you might also consider installing
over a <quote>laplink</quote> parallel port cable. The data rate
over the parallel port is much higher than what is typically
@ -4973,7 +4918,7 @@ Please press any key to reboot.</screen>
<tertiary>NFS</tertiary>
</indexterm>
<para>The NFS installation is fairly straight-forward. Simply
copy the FreeBSD distribution files you want onto an NFS server
copy the &os; distribution files you want onto an NFS server
and then point the NFS media selection at it.</para>
<para>If this server supports only <quote>privileged port</quote>
@ -4988,14 +4933,14 @@ Please press any key to reboot.</screen>
<para>In order for NFS installation to work, the server must
support subdir mounts, for example, if your
FreeBSD&nbsp;&rel.current; distribution directory lives on:
&os;&nbsp;&rel.current; distribution directory lives on:
<filename>ziggy:/usr/archive/stuff/FreeBSD</filename>, then
<hostid>ziggy</hostid> will have to allow the direct mounting
of <filename>/usr/archive/stuff/FreeBSD</filename>, not just
<filename>/usr</filename> or
<filename>/usr/archive/stuff</filename>.</para>
<para>In FreeBSD's <filename>/etc/exports</filename> file, this
<para>In &os;'s <filename>/etc/exports</filename> file, this
is controlled by the <option>-alldirs</option> options. Other NFS
servers may have different conventions. If you are getting
<errorname>permission denied</errorname> messages from the

34
en_US.ISO8859-1/books/handbook/introduction/chapter.xml
View file

@ -818,7 +818,7 @@
<variablelist>
<varlistentry>
<term>The SVN and CVS repositories<anchor
<term>The SVN repositories<anchor
id="development-cvs-repository"/></term>
<listitem>
<indexterm>
@ -862,35 +862,13 @@
Project and Ports Collection repositories also moved
from <application>CVS</application> to
<application>SVN</application> in May 2012 and July
2012, respectively.</para>
<para>While the <literal>src/</literal> and
<literal>ports/</literal> repositories now use
<application>SVN</application>, client side tools like
<application>csup</application> that depend on the older
<application>CVS</application> infrastructure, continue
to work normally &mdash; changes in the
<application>SVN</application> repository are backported
to <application>CVS</application> for this purpose.
Unlike <literal>src/</literal> and
<literal>ports/</literal>,
the documentation <application>SVN</application>
repository is not backported to
<application>CVS</application>.</para>
<para>The primary <application>CVS</application>
<ulink
url="http://www.FreeBSD.org/cgi/cvsweb.cgi">repository</ulink>
resides on a machine in Santa Clara CA, USA
from where it is replicated to numerous mirror machines
throughout the world. The
<application>SVN</application> tree, which contains the
<link linkend="current">-CURRENT</link> and <link
linkend="stable">-STABLE</link> trees, can all be
easily replicated to your own machine as well. Please
2012, respectively. Please
refer to the <link linkend="synching">Synchronizing
your source tree</link> section for more information on
doing this.</para>
obtaining the &os; <literal>src/</literal> repository
and <link linkend="ports-using">Using the Ports
Collection</link> for details on obtaining the &os;
Ports Collection.</para>
</listitem>
</varlistentry>

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

@ -603,7 +603,7 @@ cpu I686_CPU</programlisting>
<para>This option enables Soft Updates in the kernel which helps
to speed up write access on the disks. Even when this
functionality is provided by the kernel, it must be turned on
for specific disks. Review the output so &man.mount.8; to
for specific disks. Review the output of &man.mount.8; to
determine if Soft Updates is enabled. If the
<literal>soft-updates</literal> option is not in the output, it
can be activated using &man.tunefs.8; for existing file systems
@ -1019,17 +1019,6 @@ device sc</programlisting>
enable support for AGP and AGP GART for boards which have these
features.</para>
<indexterm>
<primary>APM</primary>
</indexterm>
<programlisting># Power management support (see NOTES for more options)
#device apm</programlisting>
<para>Advanced Power Management (<acronym>APM</acronym> support.
Useful for laptops, although this is disabled in
<filename>GENERIC</filename> by default.</para>
<programlisting># Add suspend/resume support for the i8254.
device pmtimer</programlisting>

1027
en_US.ISO8859-1/books/handbook/linuxemu/chapter.xml
View file

File diff suppressed because it is too large Load diff

710
en_US.ISO8859-1/books/handbook/mirrors/chapter.xml
View file

@ -151,7 +151,8 @@
<warning>
<para>CVS has been deprecated by the project, and its use is
not recommended. <application>Subversion</application>
not recommended.
<ulink url="&url.books.handbook;/svn.html">Subversion</ulink>
should be used instead.</para>
</warning>
</sect2>
@ -236,7 +237,7 @@
<application>CTM</application> distribution lists.
&a.ctm-cvs-cur.name; supports the entire CVS tree.
&a.ctm-src-cur.name; supports the head of the development
branch. &a.ctm-src-7.name; supports the 7.X release branch,
branch. &a.ctm-src-9.name; supports the 9.X release branch,
etc.. (If you do not know how to subscribe yourself to a
list, click on the list name above or go to
&a.mailman.lists.link; and click on the list that you wish to
@ -854,17 +855,6 @@ Certificate information:
<command>cvsupd</command> which runs at each of the &os;
mirror sites.</para>
<para>As you read the &os; documentation and mailing lists, you
may see references to <application>sup</application>.
<application>Sup</application> was the predecessor of
<application>CVSup</application>, and it served a similar
purpose. <application>CVSup</application> is used much in the
same way as sup and, in fact, uses configuration files which
are backward-compatible with <command>sup</command>'s.
<application>Sup</application> is no longer used in the &os;
project, because <application>CVSup</application> is both
faster and more flexible.</para>
<note>
<para>The <application>csup</application> utility is a rewrite
of the <application>CVSup</application> software in C. Its
@ -1219,23 +1209,10 @@ src-all</programlisting>
In the default configuration, the
<application>CVSup</application> client will take every file
associated with the collection and tag you chose in the
configuration file. However, this is not always what you
want, especially if you are synching the
<filename>doc</filename>, <filename>ports</filename>, or
<filename>www</filename> trees &mdash; most people cannot
read four or five languages, and therefore they do not need
to download the language-specific files. If you are
<application>CVSup</application>ing the Ports Collection,
you can get around this by specifying each collection
individually (e.g., <emphasis>ports-astrology</emphasis>,
<emphasis>ports-biology</emphasis>, etc instead of simply
saying <emphasis>ports-all</emphasis>). However, since the
<filename>doc</filename> and <filename>www</filename> trees
do not have language-specific collections, you must use one
of <application>CVSup</application>'s many nifty features:
the <filename>refuse</filename> file.</para>
configuration file. In order to download a partial tree,
use the <filename>refuse</filename> file.</para>
<para>The <filename>refuse</filename> file essentially tells
<para>The <filename>refuse</filename> file tells
<application>CVSup</application> that it should not take
every single file from a collection; in other words, it
tells the client to <emphasis>refuse</emphasis> certain
@ -1252,39 +1229,14 @@ src-all</programlisting>
<para>The <filename>refuse</filename> file has a very simple
format; it simply contains the names of files or directories
that you do not wish to download. For example, if you
cannot speak any languages other than English and some
German, and you do not feel the need to read the German
translation of documentation, you can put the following in
your <filename>refuse</filename> file:</para>
that you do not wish to download. For example:</para>
<programlisting>doc/bn_*
doc/da_*
doc/de_*
doc/el_*
doc/es_*
doc/fr_*
doc/hu_*
doc/it_*
doc/ja_*
doc/mn_*
doc/nl_*
doc/no_*
doc/pl_*
doc/pt_*
doc/ru_*
doc/sr_*
doc/tr_*
doc/zh_*</programlisting>
<programlisting>bin/
usr.bin/</programlisting>
<para>and so forth for the other languages (you can find the
full list by browsing the
<ulink url="http://www.FreeBSD.org/cgi/cvsweb.cgi/">&os; CVS
repository</ulink>).</para>
<para>With this very useful feature, those users who are on
<para>Users who are on
slow links or pay by the minute for their Internet
connection will be able to save valuable time as they will
connection will be able to save time as they will
no longer need to download files that they will never use.
For more information on <filename>refuse</filename> files
and other neat features of <application>CVSup</application>,
@ -1376,11 +1328,8 @@ doc/zh_*</programlisting>
hierarchical relationships among collections are reflected by
the use of indentation in the list below.</para>
<para>The most commonly used collections are
<literal>src-all</literal>, and
<literal>ports-all</literal>. The other collections are used
only by small groups of people for specialized purposes, and
some mirror sites may not carry all of them.</para>
<para>The most commonly used collection is
<literal>src-all</literal>. </para>
<variablelist>
<varlistentry>
@ -1400,630 +1349,6 @@ doc/zh_*</programlisting>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>ports-all release=cvs</literal></term>
<listitem>
<para>The &os; Ports Collection.</para>
<important id="cvsup-collec-pbase-warn">
<para>If you do not want to update the whole of
<literal>ports-all</literal> (the whole ports
tree), but use one of the subcollections listed
below, make sure that you
<emphasis>always</emphasis> update the
<literal>ports-base</literal> subcollection!
Whenever something changes in the ports build
infrastructure represented by
<literal>ports-base</literal>, it is virtually
certain that those changes will be used by
<quote>real</quote> ports real soon. Thus, if
you only update the <quote>real</quote> ports
and they use some of the new features, there is
a very high chance that their build will fail
with some mysterious error message. The
<emphasis>very first</emphasis> thing to do in
this case is to make sure that your
<literal>ports-base</literal> subcollection is
up to date.</para>
</important>
<important id="cvsup-collec-index-warn">
<para>If you are going to be building your own
local copy of <filename>ports/INDEX</filename>,
you <emphasis>must</emphasis> accept
<literal>ports-all</literal> (the whole ports
tree). Building
<filename>ports/INDEX</filename> with a partial
tree is not supported. See the <ulink
url="&url.books.faq;/applications.html#MAKE-INDEX">
FAQ</ulink>.</para>
</important>
<variablelist>
<varlistentry>
<term><literal>ports-accessibility
release=cvs</literal></term>
<listitem>
<para>Software to help disabled users.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>ports-arabic
release=cvs</literal></term>
<listitem>
<para>Arabic language support.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>ports-archivers
release=cvs</literal></term>
<listitem>
<para>Archiving tools.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>ports-astro
release=cvs</literal></term>
<listitem>
<para>Astronomical ports.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>ports-audio
release=cvs</literal></term>
<listitem>
<para>Sound support.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>ports-base
release=cvs</literal></term>
<listitem>
<para>The Ports Collection build
infrastructure - various files located in
the <filename>Mk/</filename> and
<filename>Tools/</filename> subdirectories
of <filename>/usr/ports</filename>.</para>
<note>
<para>Please see the <link
linkend="cvsup-collec-pbase-warn">important
warning above</link>: you should
<emphasis>always</emphasis> update this
subcollection, whenever you update any
part of the &os; Ports Collection!</para>
</note>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>ports-benchmarks
release=cvs</literal></term>
<listitem>
<para>Benchmarks.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>ports-biology
release=cvs</literal></term>
<listitem>
<para>Biology.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>ports-cad
release=cvs</literal></term>
<listitem>
<para>Computer aided design tools.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>ports-chinese
release=cvs</literal></term>
<listitem>
<para>Chinese language support.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>ports-comms
release=cvs</literal></term>
<listitem>
<para>Communication software.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>ports-converters
release=cvs</literal></term>
<listitem>
<para>character code converters.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>ports-databases
release=cvs</literal></term>
<listitem>
<para>Databases.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>ports-deskutils
release=cvs</literal></term>
<listitem>
<para>Things that used to be on the desktop
before computers were invented.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>ports-devel
release=cvs</literal></term>
<listitem>
<para>Development utilities.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>ports-dns
release=cvs</literal></term>
<listitem>
<para>DNS related software.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>ports-editors
release=cvs</literal></term>
<listitem>
<para>Editors.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>ports-emulators
release=cvs</literal></term>
<listitem>
<para>Emulators for other operating
systems.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>ports-finance
release=cvs</literal></term>
<listitem>
<para>Monetary, financial and related
applications.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>ports-ftp
release=cvs</literal></term>
<listitem>
<para>FTP client and server utilities.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>ports-games
release=cvs</literal></term>
<listitem>
<para>Games.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>ports-german
release=cvs</literal></term>
<listitem>
<para>German language support.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>ports-graphics
release=cvs</literal></term>
<listitem>
<para>Graphics utilities.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>ports-hebrew
release=cvs</literal></term>
<listitem>
<para>Hebrew language support.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>ports-hungarian
release=cvs</literal></term>
<listitem>
<para>Hungarian language support.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>ports-irc
release=cvs</literal></term>
<listitem>
<para>Internet Relay Chat utilities.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>ports-japanese
release=cvs</literal></term>
<listitem>
<para>Japanese language support.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>ports-java
release=cvs</literal></term>
<listitem>
<para>&java; utilities.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>ports-korean
release=cvs</literal></term>
<listitem>
<para>Korean language support.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>ports-lang
release=cvs</literal></term>
<listitem>
<para>Programming languages.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>ports-mail
release=cvs</literal></term>
<listitem>
<para>Mail software.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>ports-math
release=cvs</literal></term>
<listitem>
<para>Numerical computation software.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>ports-misc
release=cvs</literal></term>
<listitem>
<para>Miscellaneous utilities.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>ports-multimedia
release=cvs</literal></term>
<listitem>
<para>Multimedia software.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>ports-net
release=cvs</literal></term>
<listitem>
<para>Networking software.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>ports-net-im
release=cvs</literal></term>
<listitem>
<para>Instant messaging software.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>ports-net-mgmt
release=cvs</literal></term>
<listitem>
<para>Network management software.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>ports-net-p2p
release=cvs</literal></term>
<listitem>
<para>Peer to peer networking.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>ports-news
release=cvs</literal></term>
<listitem>
<para>USENET news software.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>ports-palm
release=cvs</literal></term>
<listitem>
<para>Software support for
<trademark class="trade">Palm</trademark>
series.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>ports-polish
release=cvs</literal></term>
<listitem>
<para>Polish language support.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>ports-ports-mgmt
release=cvs</literal></term>
<listitem>
<para>Utilities to manage ports and
packages.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>ports-portuguese
release=cvs</literal></term>
<listitem>
<para>Portuguese language support.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>ports-print
release=cvs</literal></term>
<listitem>
<para>Printing software.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>ports-russian
release=cvs</literal></term>
<listitem>
<para>Russian language support.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>ports-science
release=cvs</literal></term>
<listitem>
<para>Science.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>ports-security
release=cvs</literal></term>
<listitem>
<para>Security utilities.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>ports-shells
release=cvs</literal></term>
<listitem>
<para>Command line shells.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>ports-sysutils
release=cvs</literal></term>
<listitem>
<para>System utilities.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>ports-textproc
release=cvs</literal></term>
<listitem>
<para>text processing utilities (does not
include desktop publishing).</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>ports-ukrainian
release=cvs</literal></term>
<listitem>
<para>Ukrainian language support.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>ports-vietnamese
release=cvs</literal></term>
<listitem>
<para>Vietnamese language support.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>ports-www
release=cvs</literal></term>
<listitem>
<para>Software related to the World Wide
Web.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>ports-x11
release=cvs</literal></term>
<listitem>
<para>Ports to support the X window
system.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>ports-x11-clocks
release=cvs</literal></term>
<listitem>
<para>X11 clocks.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>ports-x11-drivers
release=cvs</literal></term>
<listitem>
<para>X11 drivers.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>ports-x11-fm
release=cvs</literal></term>
<listitem>
<para>X11 file managers.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>ports-x11-fonts
release=cvs</literal></term>
<listitem>
<para>X11 fonts and font utilities.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>ports-x11-toolkits
release=cvs</literal></term>
<listitem>
<para>X11 toolkits.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>ports-x11-servers
release=cvs</literal></term>
<listitem>
<para>X11 servers.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>ports-x11-themes
release=cvs</literal></term>
<listitem>
<para>X11 themes.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>ports-x11-wm
release=cvs</literal></term>
<listitem>
<para>X11 window managers.</para>
</listitem>
</varlistentry>
</variablelist>
</listitem>
</varlistentry>
<varlistentry>
<term>
<literal>projects-all release=cvs</literal>
@ -2330,15 +1655,6 @@ doc/zh_*</programlisting>
<para>&os; mailing list archive.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>www release=current</literal></term>
<listitem>
<para>The pre-processed &os; WWW site files (not the
source files). Used by WWW mirror sites.</para>
</listitem>
</varlistentry>
</variablelist>
</sect2>

40
en_US.ISO8859-1/books/handbook/multimedia/chapter.xml
View file

@ -1677,10 +1677,7 @@ bktr0: Pinnacle/Miro TV, Philips SECAM tuner.</programlisting>
<application>SANE</application> has a <ulink
url="http://www.sane-project.org/sane-supported-devices.html">supported
devices</ulink> list that can provide you with information
about the support for a scanner and its status. On systems
prior to &os;&nbsp;8.X the
&man.uscanner.4; manual page also provides a list of supported
USB scanners.</para>
about the support for a scanner and its status.</para>
</sect2>
<sect2>
@ -1704,16 +1701,6 @@ device uhci
device ohci
device ehci</programlisting>
<para>On systems prior to &os;&nbsp;8.X, the following line is
also needed:</para>
<programlisting>device uscanner</programlisting>
<para>On these versions of &os;, the &man.uscanner.4; device
driver provides support for the USB scanners. Since
&os;&nbsp;8.0, this support is directly provided by
the &man.libusb.3; library.</para>
<para>After rebooting with the correct kernel,
plug in your USB scanner. A
line showing the detection of your
@ -1722,14 +1709,9 @@ device ehci</programlisting>
<screen>ugen0.2: &lt;EPSON&gt; at usbus0</screen>
<para>or on a &os;&nbsp;7.X system:</para>
<screen>uscanner0: EPSON EPSON Scanner, rev 1.10/3.02, addr 2</screen>
<para>These messages show that our scanner is using
either <filename>/dev/ugen0.2</filename> or
<filename>/dev/uscanner0</filename> as device node according
to the &os; version we run. For this example, a
either <filename>/dev/ugen0.2</filename>
as device node. For this example, a
&epson.perfection;&nbsp;1650 USB scanner was used.</para>
</sect3>
@ -1973,22 +1955,6 @@ device `epson:/dev/uscanner0' is a Epson GT-8200 flatbed scanner</screen>
add path ugen0.2 mode 0660 group usb
add path usb/0.2.0 mode 0666 group usb</programlisting>
<para>&os;&nbsp;7.X users will probably need the following
lines with the correct device node
<filename>/dev/uscanner0</filename>:</para>
<programlisting>[system=5]
add path uscanner0 mode 660 group usb</programlisting>
<para>Then add the following to
<filename>/etc/rc.conf</filename> and reboot the
machine:</para>
<programlisting>devfs_system_ruleset="system"</programlisting>
<para>More information regarding these lines can be found in the
&man.devfs.8; manual page.</para>
<para>Now, one will just have to add users to the
<groupname><replaceable>usb</replaceable></groupname> group to
allow the access to the scanner:</para>

22
en_US.ISO8859-1/books/handbook/ports/chapter.xml
View file

@ -119,7 +119,7 @@
<emphasis>dependencies</emphasis>. If &man.pkg.add.1; or the
Ports Collection is used to install an application and a
dependent library is not already installed, the library will
automatically be installaed first.</para>
automatically be installed first.</para>
<para>While the two technologies are quite similar, packages and
ports each have their own strengths. Select the technology that
@ -259,7 +259,7 @@
<screen>&prompt.root; <userinput>whereis lsof</userinput>
lsof: /usr/ports/sysutils/lsof</screen>
<para>Alternately, a &man.echo.1; statement can be
<para>Alternately, an &man.echo.1; statement can be
used:</para>
<screen>&prompt.root; <userinput>echo /usr/ports/*/*lsof*</userinput>
@ -627,13 +627,6 @@ docbook =
<screen>&prompt.root; <userinput>pkg_add -r pkg</userinput></screen>
<note>
<para>The <application>pkgng</application> package management
utility is not supported on
&os;&nbsp;7.<replaceable>X</replaceable> or
&os;&nbsp;8.0.</para>
</note>
<para>Existing &os; installations require conversion of the
<application>pkg_install</application> package database to the
new format. To convert the package database, run:</para>
@ -1024,14 +1017,17 @@ Deinstalling ca_root_nss-3.13.5... done</screen>
<filename class="directory">/usr/ports</filename>:</para>
<screen>&prompt.root; <userinput>portsnap extract</userinput></screen>
</step>
<step>
<para>After the first use of
<application>Portsnap</application> has been completed as
shown above,
<filename class="directory">/usr/ports</filename> can be
updated with:</para>
<screen>&prompt.root; <userinput>portsnap update</userinput></screen>
<screen>&prompt.root; <userinput>portsnap fetch</userinput>
&prompt.root; <userinput>portsnap update</userinput></screen>
</step>
</procedure>
@ -1072,16 +1068,16 @@ Deinstalling ca_root_nss-3.13.5... done</screen>
<step>
<para>Check out a copy of the ports tree. Use a specific
<ulink
url="&url.books.handbook;/mirrors-svn.html">Subversion
url="&url.books.handbook;/svn-mirrors.html">Subversion
mirror</ulink> close to your geographic location instead
of <replaceable>svn.FreeBSD.org</replaceable> in the
of <replaceable>svn0.us-east.FreeBSD.org</replaceable> in the
command below for better performance. Committers should
read the <ulink
url="&url.articles.committers-guide;/subversion-primer.html">Subversion
Primer</ulink> first to be sure the correct protocol is
chosen.</para>
<screen>&prompt.root; <userinput>svn checkout svn://<replaceable>svn.FreeBSD.org</replaceable>/ports/head /usr/ports</userinput></screen>
<screen>&prompt.root; <userinput>svn checkout https://<replaceable>svn0.us-east.FreeBSD.org</replaceable>/ports/head /usr/ports</userinput></screen>
</step>
<step>

25
en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.xml
View file

@ -139,18 +139,6 @@
<title>Using User PPP</title>
<warning>
<para>As of &os; 8.0, device nodes for serial ports have been
renamed from
<filename>/dev/cuad<replaceable>N</replaceable></filename> to
<filename>/dev/cuau<replaceable>N</replaceable></filename> and
from
<filename>/dev/ttyd<replaceable>N</replaceable></filename> to
<filename>/dev/ttyu<replaceable>N</replaceable></filename>.
&os;&nbsp;7.X users will have to adapt the following
documentation according to these changes.</para>
</warning>
<sect2>
<title>User PPP</title>
@ -1881,19 +1869,6 @@ exit 1
<secondary>troubleshooting</secondary>
</indexterm>
<warning>
<para>As of &os; 8.0, the &man.uart.4; driver replaces the
&man.sio.4; driver. Device nodes for serial ports have been
renamed from
<filename>/dev/cuad<replaceable>N</replaceable></filename> to
<filename>/dev/cuau<replaceable>N</replaceable></filename> and
from
<filename>/dev/ttyd<replaceable>N</replaceable></filename> to
<filename>/dev/ttyu<replaceable>N</replaceable></filename>.
&os;&nbsp;7.X users will have to adapt the following
documentation according to these changes.</para>
</warning>
<para>This section covers a few issues which may arise when
using PPP over a modem connection. For instance, perhaps you
need to know exactly what prompts the system you are dialing

20
en_US.ISO8859-1/books/handbook/printing/chapter.xml
View file

@ -179,7 +179,7 @@
<title>Why You Should Use the Spooler</title>
<para>The spooler still provides benefit on a single-user system
and should be used because:</para>
and should be used because:</para>
<itemizedlist>
<listitem>
@ -212,15 +212,6 @@
<sect1 id="printing-intro-setup">
<title>Basic Setup</title>
<warning>
<para>As of &os; 8.0, device nodes for serial ports have been
renamed from
<filename>/dev/ttyd<replaceable>N</replaceable></filename> to
<filename>/dev/ttyu<replaceable>N</replaceable></filename>.
&os;&nbsp;7.X users will have to adapt the following
documentation according to these changes.</para>
</warning>
<para>To use printers with the <application>LPD</application>
spooling system, you will need to set up both your printer
hardware and the <application>LPD</application> software. This
@ -1465,15 +1456,6 @@ $%&amp;'()*+,-./01234567
<sect1 id="printing-advanced">
<title>Advanced Printer Setup</title>
<warning>
<para>As of &os; 8.0, device nodes for serial ports have been
renamed from
<filename>/dev/ttyd<replaceable>N</replaceable></filename> to
<filename>/dev/ttyu<replaceable>N</replaceable></filename>.
&os;&nbsp;7.X users will have to adapt the following
documentation according to these changes.</para>
</warning>
<para>This section describes filters for printing specially
formatted files, header pages, printing across networks, and
restricting and accounting for printer usage.</para>

3
en_US.ISO8859-1/books/handbook/security/chapter.xml
View file

@ -645,8 +645,7 @@
turned off, and access to raw devices will be denied. Higher
levels restrict even more operations. For a full description
of the effect of various secure levels, please read the
&man.security.7; manual page (or the manual page of
&man.init.8; in releases older than &os; 7.0).</para>
&man.security.7; manual page.</para>
<note>
<para>Bumping the secure level to 1 or higher may cause a few

1898
en_US.ISO8859-1/books/handbook/serialcomms/chapter.xml
View file

File diff suppressed because it is too large Load diff

738
en_US.ISO8859-1/books/handbook/users/chapter.xml
View file

File diff suppressed because it is too large Load diff

1004
en_US.ISO8859-1/books/handbook/vinum/chapter.xml
View file

File diff suppressed because it is too large Load diff

484
en_US.ISO8859-1/books/handbook/virtualization/chapter.xml
View file

@ -66,23 +66,23 @@
<itemizedlist>
<listitem>
<para>Understand the basics of &unix; and &os; (<xref
linkend="basics"/>).</para>
<para>Understand the <link linkend="basics">basics of &unix;
and &os;</link>.</para>
</listitem>
<listitem>
<para>Know how to install &os; (<xref
linkend="install"/>).</para>
<para>Know how to <link linkend="install">install
&os;</link>.</para>
</listitem>
<listitem>
<para>Know how to set up your network connection (<xref
linkend="advanced-networking"/>).</para>
<para>Know how to <link linkend="advanced-networking">set up a
network connection</link>.</para>
</listitem>
<listitem>
<para>Know how to install additional third-party
software (<xref linkend="ports"/>).</para>
<para>Know how to <link linkend="ports">install additional
third-party software</link>.</para>
</listitem>
</itemizedlist>
</sect1>
@ -91,7 +91,7 @@
<title>&os; as a Guest OS</title>
<sect2 id="virtualization-guest-parallels">
<title>Parallels on MacOS</title>
<title><application>Parallels</application> on &macos; X</title>
<para><application>Parallels Desktop</application> for &mac; is
a commercial software product available for &intel; based
@ -104,8 +104,8 @@
<sect3 id="virtualization-guest-parallels-install">
<title>Installing &os; on Parallels/&macos; X</title>
<para>The first step in installing &os; on &macos;
X/<application>Parallels</application> is to create a new
<para>The first step in installing &os; on
<application>Parallels</application> is to create a new
virtual machine for installing &os;. Select
<guimenuitem>&os;</guimenuitem> as the <guimenu>Guest OS
Type</guimenu> when prompted:</para>
@ -116,8 +116,8 @@
</imageobject>
</mediaobject>
<para>And choose a reasonable amount of disk and memory
depending on your plans for this virtual &os; instance.
<para>Choose a reasonable amount of disk and memory
depending on the plans for this virtual &os; instance.
4GB of disk space and 512MB of RAM work well for most uses
of &os; under <application>Parallels</application>:</para>
@ -174,16 +174,16 @@
</imageobject>
</mediaobject>
<para>After your &os; virtual machine has been created, you
will need to install &os; on it. This is best done with an
official &os; CDROM or with an ISO image downloaded from an
official FTP site. When you have the appropriate ISO image
on your local &mac; filesystem or a CDROM in your &mac;'s CD
drive, click on the disc icon in the bottom right corner of
your &os; <application>Parallels</application> window. This
will bring up a window that allows you to associate the
CDROM drive in your virtual machine with an ISO file on disk
or with your real CDROM drive.</para>
<para>After the &os; virtual machine has been created, &os;
can be installed on it. This is best done with an
official &os; CD/DVD or with an ISO image downloaded from an
official FTP site. Copy the appropriate ISO image to the
local &mac; filesystem or insert a CD/DVD in the &mac;'s CD
drive. Click on the disc icon in the bottom right corner of
the &os; <application>Parallels</application> window. This
will bring up a window that can be used to associate the
CDROM drive in the virtual machine with the ISO file on disk
or with the real CDROM drive.</para>
<mediaobject>
<imageobject>
@ -191,12 +191,10 @@
</imageobject>
</mediaobject>
<para>Once you have made this association with your CDROM
source, reboot your &os; virtual machine as normal by
clicking the reboot icon.
<application>Parallels</application> will reboot with a
special BIOS that first checks if you have a CDROM just as a
normal BIOS would do.</para>
<para>Once this association with the CDROM source has been
made, reboot the &os; virtual machine by clicking the reboot
icon. <application>Parallels</application> will reboot with
a special BIOS that first checks if there is a CDROM.</para>
<mediaobject>
<imageobject>
@ -205,10 +203,9 @@
</mediaobject>
<para>In this case it will find the &os; installation media
and begin a normal <application>sysinstall</application>
based installation as described in <xref
linkend="install"/>. You may install, but do not attempt
to configure X11 at this time.</para>
and begin a normal &os; installation. Perform the
installation, but do not attempt to configure
<application>&xorg;</application> at this time.</para>
<mediaobject>
<imageobject>
@ -216,8 +213,8 @@
</imageobject>
</mediaobject>
<para>When you have finished the installation, reboot into
your newly installed &os; virtual machine.</para>
<para>When the installation is finished, reboot into the
newly installed &os; virtual machine.</para>
<mediaobject>
<imageobject>
@ -227,7 +224,8 @@
</sect3>
<sect3 id="virtualization-guest-parallels-configure">
<title>Configuring &os; on &macos; X/Parallels</title>
<title>Configuring &os; on
<application>Parallels</application> </title>
<para>After &os; has been successfully installed on &macos;
X with <application>Parallels</application>, there are a
@ -248,35 +246,32 @@
<programlisting>kern.hz=100</programlisting>
<para>Without this setting, an idle &os;
<application>Parallels</application> guest
OS will use roughly 15% of the CPU of a single
processor &imac;. After this change the usage will be
closer to a mere 5%.</para>
<application>Parallels</application> guest will use
roughly 15% of the CPU of a single processor &imac;.
After this change the usage will be closer to 5%.</para>
</step>
<step>
<title>Create a New Kernel Configuration File</title>
<para>You can remove all of the SCSI, FireWire, and USB
device drivers. <application>Parallels</application>
provides a virtual network
adapter used by the &man.ed.4; driver, so
all other network devices except for
&man.ed.4; and &man.miibus.4; can be
removed from the kernel.</para>
<para>All of the SCSI, FireWire, and USB device drivers
can be removed from a custom kernel configuration file.
<application>Parallels</application> provides a virtual
network adapter used by the &man.ed.4; driver, so all
network devices except for &man.ed.4; and &man.miibus.4;
can be removed from the kernel.</para>
</step>
<step>
<title>Configure Networking</title>
<para>The most basic networking setup involves simply
using DHCP to connect your virtual machine to the same
local area network as your host &mac;. This can be
accomplished by adding
<para>The most basic networking setup uses DHCP to connect
the virtual machine to the same local area network as
the host &mac;. This can be accomplished by adding
<literal>ifconfig_ed0="DHCP"</literal> to
<filename>/etc/rc.conf</filename>. More advanced
networking setups are described in
<xref linkend="advanced-networking"/>.</para>
networking setups are described in <link
linkend="advanced-networking"></link>.</para>
</step>
</procedure>
</sect3>
@ -592,26 +587,27 @@ xenbr1 8000.feffffffffff no vif0.1
</sect2>
-->
<sect2 id="virtualization-guest-virtualpc">
<title>Virtual PC on &windows;</title>
<title><application>Virtual PC</application> on
&windows;</title>
<para><application>Virtual PC</application> for &windows; is a
&microsoft; software product available for free download.
See <ulink
See this website for the <ulink
url="http://www.microsoft.com/windows/downloads/virtualpc/sysreq.mspx">
system requirements</ulink>. Once <application> Virtual PC
</application> has been installed on &microsoft.windows;,
the user must configure a virtual machine and then install
the user can configure a virtual machine and then install
the desired guest operating system.</para>
<sect3 id="virtualization-guest-virtualpc-install">
<title>Installing &os; on Virtual
PC/&microsoft.windows;</title>
<title>Installing &os; on <application>Virtual
PC</application></title>
<para>The first step in installing &os; on
&microsoft.windows; /<application>Virtual PC
</application> is to create a new virtual machine for
installing &os;. Select <guimenuitem>Create a virtual
machine</guimenuitem> when prompted:</para>
<application>Virtual PC </application> is to create a new
virtual machine for installing &os;. Select
<guimenuitem>Create a virtual machine</guimenuitem> when
prompted:</para>
<mediaobject>
<imageobject>
@ -625,7 +621,7 @@ xenbr1 8000.feffffffffff no vif0.1
</imageobject>
</mediaobject>
<para>And select <guimenuitem>Other</guimenuitem> as the
<para>Select <guimenuitem>Other</guimenuitem> as the
<guimenuitem>Operating system</guimenuitem> when
prompted:</para>
@ -636,10 +632,9 @@ xenbr1 8000.feffffffffff no vif0.1
</mediaobject>
<para>Then, choose a reasonable amount of disk and memory
depending on your plans for this virtual &os;
instance. 4GB of disk space and 512MB of RAM work well
for most uses of &os; under
<application>Virtual PC</application>:</para>
depending on the plans for this virtual &os; instance.
4GB of disk space and 512MB of RAM work well for most uses
of &os; under <application>Virtual PC</application>:</para>
<mediaobject>
<imageobject>
@ -661,7 +656,7 @@ xenbr1 8000.feffffffffff no vif0.1
</imageobject>
</mediaobject>
<para>Select your &os; virtual machine and click
<para>Select the &os; virtual machine and click
<guimenu>Settings</guimenu>, then set the type of networking
and a network interface:</para>
@ -677,18 +672,18 @@ xenbr1 8000.feffffffffff no vif0.1
</imageobject>
</mediaobject>
<para>After your &os; virtual machine has been created, you
will need to install &os; on it. This is best done with an
official &os; CDROM or with an ISO image downloaded from an
official FTP site. When you have the appropriate ISO image
on your local &windows; filesystem or a CDROM in your CD
drive, double click on your &os; virtual machine to boot.
Then, click <guimenu>CD</guimenu> and choose
<guimenu>Capture ISO Image...</guimenu> on
<para>After the &os; virtual machine has been created, &os;
can be installed on it. This is best done with an
official &os; CD/DVD or with an ISO image downloaded from an
official FTP site. Copy the appropriate ISO image to the
local &windows; filesystem or insert a CD/DVD in the CD
drive, then double click on the &os; virtual machine to
boot. Then, click <guimenu>CD</guimenu> and choose
<guimenu>Capture ISO Image...</guimenu> on the
<application>Virtual PC</application> window. This will
bring up a window that allows you to associate the CDROM
drive in your virtual machine with an ISO file on disk or
with your real CDROM drive.</para>
bring up a window where the CDROM drive in the virtual
machine can be associated with an ISO file on disk or
with the real CDROM drive.</para>
<mediaobject>
<imageobject>
@ -702,13 +697,11 @@ xenbr1 8000.feffffffffff no vif0.1
</imageobject>
</mediaobject>
<para>Once you have made this association with your CDROM
source, reboot your &os; virtual machine as normal by
clicking the <guimenu>Action</guimenu> and
<guimenu>Reset</guimenu>.
<para>Once this association with the CDROM source has been
made, reboot the &os; virtual machine by clicking
<guimenu>Action</guimenu> and <guimenu>Reset</guimenu>.
<application>Virtual PC</application> will reboot with a
special BIOS that first checks if you have a CDROM just as a
normal BIOS would do.</para>
special BIOS that first checks for a CDROM.</para>
<mediaobject>
<imageobject>
@ -717,10 +710,9 @@ xenbr1 8000.feffffffffff no vif0.1
</mediaobject>
<para>In this case it will find the &os; installation media
and begin a normal <application>sysinstall</application>
based installation as described in
<xref linkend="install"/>. You may install, but do not
attempt to configure X11 at this time.</para>
and begin a normal &os; installation. Continue with the
installation, but do not attempt to configure
<application>&xorg;</application> at this time.</para>
<mediaobject>
<imageobject>
@ -728,9 +720,9 @@ xenbr1 8000.feffffffffff no vif0.1
</imageobject>
</mediaobject>
<para>When you have finished the installation, remember to
eject CDROM or release ISO image. Finally, reboot into your
newly installed &os; virtual machine.</para>
<para>When the installation is finished, remember to eject
the CD/DVD or release the ISO image. Finally, reboot into
the newly installed &os; virtual machine.</para>
<mediaobject>
<imageobject>
@ -740,8 +732,8 @@ xenbr1 8000.feffffffffff no vif0.1
</sect3>
<sect3 id="virtualization-guest-virtualpc-configure">
<title>Configuring &os; on &microsoft.windows;/Virtual
PC</title>
<title>Configuring &os; on <application>Virtual
PC</application></title>
<para>After &os; has been successfully installed on
&microsoft.windows; with <application>Virtual PC
@ -755,9 +747,9 @@ xenbr1 8000.feffffffffff no vif0.1
<para>The most important step is to reduce the
<option>kern.hz</option> tunable to reduce the CPU
utilization of &os; under the
<application>Virtual PC</application> environment.
This is accomplished by adding the following line to
utilization of &os; under the <application>Virtual
PC</application> environment. This is accomplished
by adding the following line to
<filename> /boot/loader.conf</filename>:</para>
<programlisting>kern.hz=100</programlisting>
@ -765,55 +757,57 @@ xenbr1 8000.feffffffffff no vif0.1
<para>Without this setting, an idle &os;
<application>Virtual PC</application> guest OS will
use roughly 40% of the CPU of a single processor
computer. After this change the usage will be
closer to a mere 3%.</para>
computer. After this change, the usage will be
closer to 3%.</para>
</step>
<step>
<title>Create a New Kernel Configuration File</title>
<para>You can remove all of the SCSI, FireWire, and USB
device drivers. <application>Virtual PC</application>
provides a virtual network adapter used by the
&man.de.4; driver, so all other network devices except
for &man.de.4; and &man.miibus.4; can be removed from
the kernel.</para>
<para>All of the SCSI, FireWire, and USB device drivers
can be removed from a custom kernel configuration file.
<application>Virtual PC</application> provides a virtual
network adapter used by the &man.de.4; driver, so all
network devices except for &man.de.4; and &man.miibus.4;
can be removed from the kernel.</para>
</step>
<step>
<title>Configure Networking</title>
<para>The most basic networking setup involves simply
using DHCP to connect your virtual machine to the same
local area network as your host &microsoft.windows;.
This can be accomplished by adding
<literal>ifconfig_de0="DHCP"</literal> to
<para>The most basic networking setup uses DHCP to connect
the virtual machine to the same local area network as
the &microsoft.windows; host. This can be accomplished
by adding <literal>ifconfig_de0="DHCP"</literal> to
<filename>/etc/rc.conf</filename>. More advanced
networking setups are described in
<xref linkend="advanced-networking"/>.</para>
networking setups are described in <link
linkend="advanced-networking"></link>.</para>
</step>
</procedure>
</sect3>
</sect2>
<sect2 id="virtualization-guest-vmware">
<title>VMware on MacOS</title>
<title><application>VMware Fusion</application> on
&macos;</title>
<para><application>VMware Fusion</application> for &mac; is a
commercial software product available for &intel; based
&apple; &mac; computers running &macos; 10.4.9 or higher.
&os; is a fully supported guest operating system. Once
<application>VMware Fusion</application> has been
installed on &macos; X, the user must configure a virtual
installed on &macos; X, the user can configure a virtual
machine and then install the desired guest operating
system.</para>
<sect3 id="virtualization-guest-vmware-install">
<title>Installing &os; on VMware/&macos; X</title>
<title>Installing &os; on <application>VMware
Fusion</application></title>
<para>The first step is to start VMware Fusion, the Virtual
Machine Library will load. Click "New" to create the
VM:</para>
<para>The first step is to start <application>VMware
Fusion</application> which will load the Virtual
Machine Library. Click <guimenuitem>New</guimenuitem> to
create the virtual machine:</para>
<mediaobject>
<imageobject>
@ -821,8 +815,8 @@ xenbr1 8000.feffffffffff no vif0.1
</imageobject>
</mediaobject>
<para>This will load the New Virtual Machine Assistant to help
you create the VM, click Continue to proceed:</para>
<para>This will load the New Virtual Machine Assistant. Click
<guimenuitem>Continue</guimenuitem> to proceed:</para>
<mediaobject>
<imageobject>
@ -831,11 +825,10 @@ xenbr1 8000.feffffffffff no vif0.1
</mediaobject>
<para>Select <guimenuitem>Other</guimenuitem> as the
<guimenuitem>Operating System</guimenuitem> and
<guimenuitem>Operating System</guimenuitem> and either
<guimenuitem>&os;</guimenuitem> or
<guimenuitem>&os; 64-bit</guimenuitem>, depending on if
you want 64-bit support, as the <guimenu>Version</guimenu>
when prompted:</para>
<guimenuitem>&os; 64-bit</guimenuitem>, as the
<guimenu>Version</guimenu> when prompted:</para>
<mediaobject>
<imageobject>
@ -843,8 +836,8 @@ xenbr1 8000.feffffffffff no vif0.1
</imageobject>
</mediaobject>
<para>Choose the Name of the VM Image and the Directory where
you would like it saved:</para>
<para>Choose the name of the virtual machine and the directory
where it should be saved:</para>
<mediaobject>
<imageobject>
@ -852,8 +845,8 @@ xenbr1 8000.feffffffffff no vif0.1
</imageobject>
</mediaobject>
<para>Choose the size of the Virtual Hard Disk for the
VM:</para>
<para>Choose the size of the Virtual Hard Disk for the virtual
machine:</para>
<mediaobject>
<imageobject>
@ -861,8 +854,8 @@ xenbr1 8000.feffffffffff no vif0.1
</imageobject>
</mediaobject>
<para>Choose the method you would like to install the VM,
either from an ISO image or from a CD:</para>
<para>Choose the method to install the virtual machine,
either from an ISO image or from a CD/DVD:</para>
<mediaobject>
<imageobject>
@ -870,7 +863,8 @@ xenbr1 8000.feffffffffff no vif0.1
</imageobject>
</mediaobject>
<para>Once you click Finish, the VM will boot:</para>
<para>Click <guimenuitem>Finish</guimenuitem> and the virtual
machine will boot:</para>
<mediaobject>
<imageobject>
@ -878,8 +872,7 @@ xenbr1 8000.feffffffffff no vif0.1
</imageobject>
</mediaobject>
<para>Install &os; like you normally would, or by following
the directions in <xref linkend="install"/>:</para>
<para>Install &os; as usual:</para>
<mediaobject>
<imageobject>
@ -887,12 +880,14 @@ xenbr1 8000.feffffffffff no vif0.1
</imageobject>
</mediaobject>
<para>Once the install is complete you can modify the settings
of the VM, such as Memory Usage:</para>
<para>Once the install is complete, the settings
of the virtual machine can be modified, such as memory
usage:</para>
<note>
<para>The System Hardware settings of the VM cannot be
modified while the VM is running.</para>
<para>The System Hardware settings of the virtual machine
cannot be modified while the virtual machine is
running.</para>
</note>
<mediaobject>
@ -901,7 +896,8 @@ xenbr1 8000.feffffffffff no vif0.1
</imageobject>
</mediaobject>
<para>The number of CPUs the VM will have access to:</para>
<para>The number of CPUs the virtual machine will have access
to:</para>
<mediaobject>
<imageobject>
@ -909,9 +905,9 @@ xenbr1 8000.feffffffffff no vif0.1
</imageobject>
</mediaobject>
<para>The status of the CD-Rom Device. Normally you can
disconnect the CD-Rom/ISO from the VM if you will not be
needing it anymore.</para>
<para>The status of the CDROM device. Normally the
CD/DVD/ISO is disconnected from the virtual machine when it
is no longer needed.</para>
<mediaobject>
<imageobject>
@ -919,14 +915,15 @@ xenbr1 8000.feffffffffff no vif0.1
</imageobject>
</mediaobject>
<para>The last thing to change is how the VM will connect to
the Network. If you want to allow connections to the VM
from other machines besides the Host, make sure you choose
the <guimenuitem>Connect directly to the physical network
(Bridged)</guimenuitem>. Otherwise <guimenuitem>Share the
<para>The last thing to change is how the virtual machine will
connect to the network. To allow connections to the virtual
machine from other machines besides the host, choose
<guimenuitem>Connect directly to the physical network
(Bridged)</guimenuitem>. Otherwise, <guimenuitem>Share the
host's internet connection (NAT)</guimenuitem> is
preferred so that the VM can have access to the Internet,
but the network cannot access the VM.</para>
preferred so that the virtual machine can have access to the
Internet, but the network cannot access the virtual
machine.</para>
<mediaobject>
<imageobject>
@ -934,17 +931,18 @@ xenbr1 8000.feffffffffff no vif0.1
</imageobject>
</mediaobject>
<para>After you have finished modifying the settings, boot the
newly installed &os; virtual machine.</para>
<para>After modifying the settings, boot the newly installed
&os; virtual machine.</para>
</sect3>
<sect3 id="virtualization-guest-vmware-configure">
<title>Configuring &os; on &macos; X/VMware</title>
<title>Configuring &os; on <application>VMware
Fusion</application></title>
<para>After &os; has been successfully installed on &macos; X
with <application>VMware</application>, there are a number
of configuration steps that can be taken to optimize the
system for virtualized operation.</para>
with <application>VMware Fusion</application>, there are a
number of configuration steps that can be taken to optimize
the system for virtualized operation.</para>
<procedure>
<step>
@ -953,40 +951,40 @@ xenbr1 8000.feffffffffff no vif0.1
<para>The most important step is to reduce the
<option>kern.hz</option> tunable to reduce the CPU
utilization of &os; under the
<application>VMware</application> environment. This is
accomplished by adding the following line to
<application>VMware Fusion</application> environment.
This is accomplished by adding the following line to
<filename>/boot/loader.conf</filename>:</para>
<programlisting>kern.hz=100</programlisting>
<para>Without this setting, an idle &os;
<application>VMware</application> guest
OS will use roughly 15% of the CPU of a single
processor &imac;. After this change the usage will be
closer to a mere 5%.</para>
<application>VMware Fusion</application> guest will use
roughly 15% of the CPU of a single processor &imac;.
After this change, the usage will be closer to
5%.</para>
</step>
<step>
<title>Create a New Kernel Configuration File</title>
<para>You can remove all of the FireWire, and USB device
drivers. <application>VMware</application> provides a
<para>All of the FireWire, and USB device drivers can be
removed from a custom kernel configuration file.
<application>VMware Fusion</application> provides a
virtual network adapter used by the &man.em.4; driver,
so all other network devices except for &man.em.4; can
be removed from the kernel.</para>
so all network devices except for &man.em.4; can be
removed from the kernel.</para>
</step>
<step>
<title>Configure Networking</title>
<para>The most basic networking setup involves simply
using DHCP to connect your virtual machine to the
same local area network as your host &mac;. This
can be accomplished by adding
<para>The most basic networking setup uses DHCP to connect
the virtual machine to the same local area network as
the host &mac;. This can be accomplished by adding
<literal>ifconfig_em0="DHCP"</literal> to
<filename>/etc/rc.conf</filename>. More advanced
networking setups are described in
<xref linkend="advanced-networking"/>.</para>
networking setups are described in <link
linkend="advanced-networking"></link>.</para>
</step>
</procedure>
</sect3>
@ -1000,23 +998,23 @@ xenbr1 8000.feffffffffff no vif0.1
<itemizedlist>
<listitem>
<para>Clipboard sharing</para>
<para>Clipboard sharing.</para>
</listitem>
<listitem>
<para>Mouse pointer integration</para>
<para>Mouse pointer integration.</para>
</listitem>
<listitem>
<para>Host time synchronization</para>
<para>Host time synchronization.</para>
</listitem>
<listitem>
<para>Window scaling</para>
<para>Window scaling.</para>
</listitem>
<listitem>
<para>Seamless mode</para>
<para>Seamless mode.</para>
</listitem>
</itemizedlist>
@ -1026,7 +1024,8 @@ xenbr1 8000.feffffffffff no vif0.1
<para>First, install the <filename
role="package">emulators/virtualbox-ose-additions</filename>
package in the &os; guest.</para>
package or port in the &os; guest. This will install
the port:</para>
<screen>&prompt.root; <userinput>cd /usr/ports/emulators/virtualbox-ose-additions &amp;&amp; make install clean</userinput></screen>
@ -1036,14 +1035,15 @@ xenbr1 8000.feffffffffff no vif0.1
<programlisting>vboxguest_enable="YES"
vboxservice_enable="YES"</programlisting>
<para>If &man.ntpd.8; or &man.ntpdate.8; will be used, host time
<para>If &man.ntpd.8; or &man.ntpdate.8; is used, host time
synchronization should be disabled:</para>
<programlisting>vboxservice_flags="--disable-timesync"</programlisting>
<para>The <literal>vboxvideo_drv</literal> should be recognized
by <command>Xorg -configure</command>. If not, modify
<filename>xorg.conf</filename> for the
<para>The <literal>vboxvideo</literal> driver should be
automatically recognized by <command>Xorg
-configure</command>. If not, modify
<filename>/etc/X11/xorg.conf</filename> for the
<application>&virtualbox;</application> video card:</para>
<programlisting>Section "Device"
@ -1058,15 +1058,16 @@ vboxservice_enable="YES"</programlisting>
BusID "PCI:0:2:0"
EndSection</programlisting>
<para>To use <literal>vboxmouse_drv</literal>, adjust the mouse
section in your <filename>xorg.conf</filename>:</para>
<para>To use the <literal>vboxmouse</literal> driver, adjust the
mouse section in
<filename>/etc/X11/xorg.conf</filename>:</para>
<programlisting>Section "InputDevice"
Identifier "Mouse0"
Driver "vboxmouse"
EndSection</programlisting>
<para><acronym>HAL</acronym> users should create this file at
<para><acronym>HAL</acronym> users should create the following
<filename>/usr/local/etc/hal/fdi/policy/90-vboxguest.fdi</filename>
or copy it from
<filename>/usr/local/share/hal/fdi/policy/10osvendor/90-vboxguest.fdi</filename>:</para>
@ -1107,45 +1108,33 @@ EndSection</programlisting>
</sect1>
<sect1 id="virtualization-host">
<title>&os; as a Host OS</title>
<para>For a number of years, &os; was not officially supported as
a host OS by any of the available virtualization solutions.
Some people were using older and mostly obsolete versions of
<application>VMware</application> (like
<filename role="package">emulators/vmware3</filename>), which
utilized the &linux; binary compatibility layer. Shortly after
the release of &os;&nbsp;7.2, Sun's
<application>&virtualbox;</application> appeared in the
Ports&nbsp;Collection as a native &os; program.</para>
<title>&os; as a Host</title>
<para><application>&virtualbox;</application> is an actively
developed, complete virtualization package, that is available
for most operating systems including &windows;, &macos;, &linux;
and &os;. It is equally capable at running &windows; or &unix;
like guests. It is released as open source software, but with
closed-source components available in a separate extension pack.
These components include support for USB 2.0 devices, among
others. More information may be found on the
<quote>Downloads</quote> page of the
<application>&virtualbox;</application> wiki, at <ulink
url="http://www.virtualbox.org/wiki/Downloads"></ulink>.
and &os;. It is equally capable of running &windows; or
&unix;-like guests. It is released as open source software, but
with closed-source components available in a separate extension
pack. These components include support for USB 2.0 devices.
More information may be found on the <ulink
url="http://www.virtualbox.org/wiki/Downloads">
<quote>Downloads</quote> page of the
<application>&virtualbox;</application> wiki</ulink>.
Currently, these extensions are not available for &os;.</para>
<sect2 id="virtualization-virtualbox-install">
<title>Installing &virtualbox;</title>
<para><application>&virtualbox;</application> is available as a
&os; port in
<filename role="package">emulators/virtualbox-ose</filename>.
As &virtualbox; is very actively developed, make sure your
ports tree is up to date before installing. Install using
these commands:</para>
&os; package or port in <filename
role="package">emulators/virtualbox-ose</filename>. The
port can be installed using these commands:</para>
<screen>&prompt.root; <userinput>cd /usr/ports/emulators/virtualbox-ose</userinput>
&prompt.root; <userinput>make install clean</userinput></screen>
<para>One useful option in the configuration dialog is the
<para>One useful option in the port's configuration menu is the
<literal>GuestAdditions</literal> suite of programs. These
provide a number of useful features in guest operating
systems, like mouse pointer integration (allowing the mouse to
@ -1153,8 +1142,7 @@ EndSection</programlisting>
special keyboard shortcut to switch) and faster video
rendering, especially in &windows; guests. The guest
additions are available in the <guimenu>Devices</guimenu>
menu, after the installation of the guest OS is
finished.</para>
menu, after the installation of the guest is finished.</para>
<para>A few configuration changes are needed before
<application>&virtualbox;</application> is started for the
@ -1181,59 +1169,51 @@ EndSection</programlisting>
during installation of
<application>&virtualbox;</application>. All users that need
access to <application>&virtualbox;</application> will have to
be added as members of this group. The <command>pw</command>
command may be used to add new members:</para>
be added as members of this group. <command>pw</command>
can be used to add new members:</para>
<screen>&prompt.root; <userinput>pw groupmod vboxusers -m <replaceable>yourusername</replaceable></userinput></screen>
<para>The default permissions for
<filename class="devicefile">/dev/vboxnetctl</filename> are
<para>The default permissions for <filename
class="devicefile">/dev/vboxnetctl</filename> are
restrictive and need to be changed for bridged
networking.</para>
<para>To test it temporarily:</para>
networking:</para>
<screen>&prompt.root; <userinput>chown root:vboxusers /dev/vboxnetctl</userinput>
&prompt.root; <userinput>chmod 0660 /dev/vboxnetctl</userinput></screen>
<para>To make the permissions change permanent, add these
<para>To make this permissions change permanent, add these
lines to <filename>/etc/devfs.conf</filename>:</para>
<programlisting>own vboxnetctl root:vboxusers
perm vboxnetctl 0660</programlisting>
<para>To launch <application>&virtualbox;</application>, either
select the <guimenuitem>Sun VirtualBox</guimenuitem> item from
the graphic environment's menu, or type the following in a
terminal:</para>
<para>To launch <application>&virtualbox;</application>,
type from a <application>&xorg;</application> session:</para>
<screen>&prompt.user; <userinput>VirtualBox</userinput></screen>
<para>For more information on configuring and using
<application>&virtualbox;</application>, please visit the
official website at
<ulink url="http://www.virtualbox.org"></ulink>. As the &os;
port is very recent, it is under heavy development. For the
latest information and troubleshooting instructions, please
visit the relevant page in the &os; wiki, at <ulink
url="http://wiki.FreeBSD.org/VirtualBox"></ulink>.</para>
<application>&virtualbox;</application>, refer to the
<ulink url="http://www.virtualbox.org">official
website</ulink>. For &os;-specific information and
troubleshooting instructions, refer to the <ulink
url="http://wiki.FreeBSD.org/VirtualBox">relevant page in
the &os; wiki</ulink>.</para>
</sect2>
<sect2 id="virtualization-virtualbox-usb-support">
<title>&virtualbox; USB Support</title>
<note>
<para>These steps require VirtualBox 4.0.0 or later.</para>
</note>
<para>In order to be able to read and write to USB devices,
users need to be members of the operator group:</para>
users need to be members of
<groupname>operator</groupname>:</para>
<screen>&prompt.root; <userinput>pw groupmod operator -m <replaceable>jerry</replaceable></userinput></screen>
<para>Then, add the following to
<filename>/etc/devfs.rules</filename> (create it if it does
not exist yet):</para>
<filename>/etc/devfs.rules</filename>, or create this file if
it does not exist yet:</para>
<programlisting>[system=10]
add path 'usb/*' mode 0660 group operator</programlisting>
@ -1256,20 +1236,20 @@ add path 'usb/*' mode 0660 group operator</programlisting>
<title>&virtualbox; Host DVD/CD Access</title>
<para>Access to the host DVD/CD drives from guests is achieved
through the sharing of the physical drives. In GUI this is
set up from the Storage window in the Settings of the virtual
machine. Create an empty IDE CD/DVD device first.
Then choose the Host Drive from the popup menu for the virtual
CD/DVD drive selection. A checkbox labeled
<literal>Passthrough</literal> check box will appear.
This allows the virtual machine to use the hardware directly.
For example, audio CDs or the burner only function if
this option is selected.</para>
through the sharing of the physical drives. Within
&virtualbox;, this is set up from the Storage window in the
Settings of the virtual machine. If needed, create an empty
IDE CD/DVD device first. Then choose the Host Drive from the
popup menu for the virtual CD/DVD drive selection. A checkbox
labeled <literal>Passthrough</literal> will appear. This
allows the virtual machine to use the hardware directly. For
example, audio CDs or the burner will only function if this
option is selected.</para>
<para><acronym>HAL</acronym> needs to run for
<application>&virtualbox;</application> DVD/CD functions to
work, so enable it in <filename>/etc/rc.conf</filename> and
start it (if it is not already running):</para>
start it if it is not already running:</para>
<programlisting>hald_enable="YES"</programlisting>
@ -1277,16 +1257,14 @@ add path 'usb/*' mode 0660 group operator</programlisting>
<para>In order for users to be able to use
<application>&virtualbox;</application> DVD/CD functions, they
need access to
<filename class="devicefile">/dev/xpt0</filename>, <filename
need access to <filename
class="devicefile">/dev/xpt0</filename>, <filename
class="devicefile">/dev/cd<replaceable>N</replaceable></filename>,
and <filename
class="devicefile">/dev/pass<replaceable>N</replaceable></filename>.
This is usually achieved by making the user of
<application>&virtualbox;</application>
a member of the operator group, which is also the default
group of the above mentioned devices. Permissions of these
devices have to be corrected by adding the following lines to
This is usually achieved by making the user a member of
<groupname>operator</groupname>. Permissions to these devices
have to be corrected by adding the following lines to
<filename>/etc/devfs.conf</filename>:</para>
<programlisting>perm cd* 0600

36
en_US.ISO8859-1/books/handbook/x11/chapter.xml
View file

@ -33,8 +33,7 @@
default and official flavor of X11 in &os; is
<application>&xorg;</application>, the X11 server developed by
the X.Org Foundation under a license very similar to the one
used by &os;. Commercial X servers for &os; are also
available.</para>
used by &os;.</para>
<para>For more information on the video hardware that X11
supports, check the <ulink
@ -119,8 +118,8 @@
other input or output devices (i.e., a <quote>tablet</quote>
can be used as an input device, and a video projector
may be an alternative output device). Each X application
(such as <application>XTerm</application>, or
<application>&netscape;</application>) is a
(such as <application>XTerm</application> or
<application>Firefox</application>) is a
<quote>client</quote>. A client sends messages to the server
such as <quote>Please draw a window at these
coordinates</quote>, and the server sends back messages such
@ -176,22 +175,16 @@
<para>Instead, X delegates this responsibility to an
application called a <quote>Window Manager</quote>. There
are dozens of window managers available for X:
<application>AfterStep</application>,
<application>Blackbox</application>,
<application>ctwm</application>,
<application>Enlightenment</application>,
<application>fvwm</application>,
<application>Sawfish</application>,
<application>twm</application>,
<application>Window Maker</application>, and more. Each of
are <ulink
url="http://xwinman.org/">dozens of window managers</ulink>
available for X. Each of
these window managers provides a different look and feel;
some of them support <quote>virtual desktops</quote>; some
of them allow customized keystrokes to manage the desktop;
some have a <quote>Start</quote> button or similar device;
some are <quote>themeable</quote>, allowing a complete change
of look-and-feel by applying a new theme. These window
managers, and many more, are available in the
of look-and-feel by applying a new theme. Window managers
are available in the
<filename>x11-wm</filename> category of the Ports
Collection.</para>
@ -300,15 +293,8 @@
<para>As a result, do not expect X applications to have a
common look and feel. There are several popular widget sets
and variations, including the original Athena widget set from
MIT, <application>&motif;</application> (on which the widget
set in &microsoft.windows; was modeled, all bevelled edges and
three shades of grey), <application>OpenLook</application>,
and others.</para>
<para>Most newer X applications today will use a
modern-looking widget set, either Qt, used by
<application>KDE</application>, or GTK+, used by the
and variations, including Qt, used by
<application>KDE</application>, and GTK+, used by the
<application>GNOME</application> project. In this respect,
there is some convergence in look-and-feel of the &unix;
desktop, which certainly makes things easier for the novice
@ -319,7 +305,7 @@
<sect1 id="x-install">
<title>Installing X11</title>
<para><application>&xorg;</application> is the default X11
<para><application>&xorg;</application> is the X11
implementation for &os;. <application>&xorg;</application>
is the X server of the open source X Window System
implementation released by the X.Org Foundation.

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

@ -20,6 +20,7 @@ INSTALL_ONLY_COMPRESSED?=
# XML content
SRCS= book.xml
SRCS+= uses.xml
# Images from the cross-document image library
IMAGES_LIB+= callouts/1.png

191
en_US.ISO8859-1/books/porters-handbook/book.xml
View file

@ -1,6 +1,8 @@
<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE book PUBLIC "-//FreeBSD//DTD DocBook XML V4.5-Based Extension//EN"
"../../../share/xml/freebsd45.dtd">
"../../../share/xml/freebsd45.dtd" [
<!ENTITY values.uses SYSTEM "uses.xml">
]>
<!--
The FreeBSD Documentation Project
@ -32,6 +34,7 @@
<year>2010</year>
<year>2011</year>
<year>2012</year>
<year>2013</year>
<holder role="mailto:doc@FreeBSD.org">The FreeBSD Documentation
Project</holder>
</copyright>
@ -1022,6 +1025,27 @@ DOS2UNIX_REGEX= .*\.(c|cpp|h)</programlisting>
incorrectly treated as a newer version since 20000801 is a
numerically greater value than 1).</para>
<tip>
<para>The results of version number comparisons are not
always obvious. &man.pkg.version.1; can be used to test
the comparison of two version number strings. The
<application>pkgng</application> equivalent is
<command>pkg version -t</command>. For example:</para>
<screen>&prompt.user; <userinput>pkg_version -t 0.031 0.29</userinput>
></screen>
<para>Or, for <application>pkgng</application>
users:</para>
<screen>&prompt.user; <userinput>pkg version -t 0.031 0.29</userinput>
></screen>
<para>The <literal>&gt;</literal> output indicates that
version 0.031 is considered greater than version 0.29,
which may not have been obvious to the porter.</para>
</tip>
<para>In situations such as this, the
<makevar>PORTEPOCH</makevar> version should be increased.
If <makevar>PORTEPOCH</makevar> is nonzero it is appended
@ -3769,6 +3793,25 @@ ALWAYS_KEEP_DISTFILES= yes
is the same as <makevar>DEPENDS_TARGET</makevar>.</para>
</sect2>
<sect2 id="uses">
<title><makevar>USES</makevar></title>
<para>There several parameters exist for defining different kind
of features and dependencies that the port in question uses.
They can be specified by adding the following line to the
<filename>Makefile</filename> of the port:</para>
<programlisting>USES= feature[:arguments]</programlisting>
<para>For the complete list of such values, please see <xref
linkend="uses-values"/>.</para>
<warning>
<para><makevar>USES</makevar> cannot be assigned after inclusion of
<filename>bsd.port.pre.mk</filename>.</para>
</warning>
</sect2>
<sect2 id="use-vars">
<title><makevar>USE_<replaceable>*</replaceable></makevar></title>
@ -3822,12 +3865,6 @@ ALWAYS_KEEP_DISTFILES= yes
<command>zip</command>.</entry>
</row>
<row>
<entry><makevar>USE_BISON</makevar></entry>
<entry>The port uses <command>bison</command> for
building.</entry>
</row>
<row>
<entry><makevar>USE_CDRTOOLS</makevar></entry>
<entry>The port requires
@ -4539,27 +4576,6 @@ CONFIGURE_ARGS+= --without-examples
.include &lt;bsd.port.mk&gt;</programlisting>
</example>
<example id="ports-options-old-style-use">
<title>Old-Style Use of <makevar>OPTIONS</makevar></title>
<programlisting>OPTIONS= FOO "Enable option foo" On
.include &lt;bsd.port.pre.mk&gt;
.if defined(WITHOUT_FOO)
CONFIGURE_ARGS+= --without-foo
.else
CONFIGURE_ARGS+= --with-foo
.endif
.include &lt;bsd.port.post.mk&gt;</programlisting>
</example>
<important>
<para>This method of using <makevar>OPTIONS</makevar>
is deprecated, and will be removed at some point.
Do not use this method for new ports.</para>
</important>
</sect3>
<sect3>
@ -5723,17 +5739,13 @@ IGNORE= may not be redistributed because of licensing reasons. Please visit <rep
CPPFLAGS+= -I${LOCALBASE}/include
LDFLAGS+= -L${LOCALBASE}/lib
GNU_CONFIGURE= yes
CONFIGURE_ENV= CPPFLAGS="${CPPFLAGS}" \
LDFLAGS="${LDFLAGS}"</programlisting>
GNU_CONFIGURE= yes</programlisting>
<para>Of course, the code can be more compact if there are no
more flags to pass to <command>configure</command>:</para>
<programlisting>USE_GETTEXT= yes
GNU_CONFIGURE= yes
CONFIGURE_ENV= CPPFLAGS="-I${LOCALBASE}/include" \
LDFLAGS="-L${LOCALBASE}/lib"</programlisting>
GNU_CONFIGURE= yes</programlisting>
</sect2>
<sect2>
@ -5750,13 +5762,17 @@ CONFIGURE_ENV= CPPFLAGS="-I${LOCALBASE}/include" \
<programlisting>GNU_CONFIGURE= yes
.if !defined(WITHOUT_NLS)
.include &lt;bsd.port.options.mk&gt;
.if ${PORT_OPTIONS:MNLS}
USE_GETTEXT= yes
PLIST_SUB+= NLS=""
.else
CONFIGURE_ARGS+= --disable-nls
PLIST_SUB+= NLS="@comment "
.endif</programlisting>
.endif
.include &lt;bsd.port.mk&gt;</programlisting>
<para>The next item on your to-do list is to arrange so that
the message catalog files are included in the packing list
@ -10267,7 +10283,8 @@ etc/orbit.conf.sample
<makevar>SUB_FILES</makevar>. Several common pairs are
automatically defined: <makevar>PREFIX</makevar>,
<makevar>LOCALBASE</makevar>, <makevar>DATADIR</makevar>,
<makevar>DOCSDIR</makevar>, <makevar>EXAMPLESDIR</makevar>.
<makevar>DOCSDIR</makevar>, <makevar>EXAMPLESDIR</makevar>,
<makevar>WWWDIR</makevar>, and <makevar>ETCDIR</makevar>.
Any line beginning with <literal>@comment</literal> will be
deleted from resulting files after a variable
substitution.</para>
@ -10478,7 +10495,7 @@ as .putsy.conf and edit it.</programlisting>
<application>Subversion</application> or &man.portsnap.8;
to keep your whole ports
collection up-to-date, as described in the <ulink
url="&url.books.handbook;/synching.html#CVSUP-CONFIG">Handbook</ulink>.
url="&url.books.handbook;/ports-using.html">Handbook</ulink>.
This will have the added benefit of tracking all the ports'
dependencies.</para>
@ -10497,8 +10514,7 @@ as .putsy.conf and edit it.</programlisting>
<literal>portsmon</literal>). This system attempts to classify
port PRs by portname. To search for PRs about a particular
port, use the <ulink
url="http://portsmon.FreeBSD.org/portoverview.py">
Overview of One Port</ulink>.</para>
url="http://portsmon.FreeBSD.org/portoverview.py">Overview of One Port</ulink>.</para>
<para>If there is no pending PR, the next step is to send an email
to the port's maintainer, as shown by <command>make
@ -10598,7 +10614,7 @@ as .putsy.conf and edit it.</programlisting>
<sect1 id="svn-diff">
<title>Using <literal>SVN</literal> to Make Patches</title>
<para>If you can, please submit a &man.svn.1; diff; they are
<para>If you can, please submit a &man.svn.1; diff &mdash; they are
easier to handle than diffs between <quote>new and old</quote>
directories. Plus it is easier for you to see what you have
changed and to update your diff if something is modified in
@ -10607,7 +10623,7 @@ as .putsy.conf and edit it.</programlisting>
something.</para>
<screen>&prompt.user; <userinput>cd ~/my_wrkdir</userinput> <co id="my-wrkdir"/>
&prompt.user; <userinput>svn co svn://svn.FreeBSD.org/ports/head/dns/pdnsd</userinput> <co id="svn-FreeBSD-org"/>
&prompt.user; <userinput>svn co <replaceable>https://svn0.us-west.FreeBSD.org</replaceable>/ports/head/dns/pdnsd</userinput> <co id="svn-FreeBSD-org"/>
&prompt.user; <userinput>cd ~/my_wrkdir/pdnsd</userinput></screen>
<calloutlist>
@ -10620,8 +10636,12 @@ as .putsy.conf and edit it.</programlisting>
<callout arearefs="svn-FreeBSD-org">
<para><ulink
url="http://svn.FreeBSD.org/">svn.FreeBSD.org</ulink>
is a public <literal>SVN</literal> server.</para>
url="https://svn0.us-west.FreeBSD.org/">svn0.us-west.FreeBSD.org</ulink>
is a public <literal>SVN</literal> server.
Select the closest mirror and verify the mirror server
certificate from the list of <ulink
url="&url.books.handbook;/svn-mirrors.html">Subversion
mirror sites</ulink>.</para>
</callout>
</calloutlist>
@ -15669,6 +15689,41 @@ Reference: &lt;http://www.freebsd.org/ports/portaudit/74a9541d-5d6c-11d8-80e3-00
<entry>9.1-RELEASE.</entry>
</row>
<row>
<entry>901500</entry>
<entry>August 6, 2012</entry>
<entry>9.1-STABLE after branching releng/9.1
(RELENG_9_1).</entry>
</row>
<row>
<entry>901501</entry>
<entry>November 11, 2012</entry>
<entry>9.1-STABLE after LIST_PREV() added to queue.h.</entry>
</row>
<row>
<entry>901502</entry>
<entry>November 28, 2012</entry>
<entry>9.1-STABLE after USB serial jitter buffer requires
rebuild of USB serial device modules.</entry>
</row>
<row>
<entry>901503</entry>
<entry>February 21, 2013</entry>
<entry>9.1-STABLE after USB moved to the driver structure
requiring a rebuild of all USB modules. Also indicates
the presence of nmtree.</entry>
</row>
<row>
<entry>901504</entry>
<entry>March 15, 2013</entry>
<entry>9.1-STABLE after install gained -l, -M, -N and related
flags and cat gained the -l option.</entry>
</row>
<row>
<entry>1000000</entry>
<entry>September 26, 2011</entry>
@ -15900,6 +15955,14 @@ Reference: &lt;http://www.freebsd.org/ports/portaudit/74a9541d-5d6c-11d8-80e3-00
<entry>10-CURRENT after cat gained the -l flag (rev
<svnref>246083</svnref>).</entry>
</row>
<row>
<entry>1000030</entry>
<entry>March 12, 2013</entry>
<entry>10-CURRENT after KPI breakage introduced in the
VM subsystem to support read/write locking (rev
<svnref>248084</svnref>).</entry>
</row>
</tbody>
</tgroup>
</table>
@ -16012,23 +16075,10 @@ Reference: &lt;http://www.freebsd.org/ports/portaudit/74a9541d-5d6c-11d8-80e3-00
.if ${OSVERSION} &gt; 300003
BROKEN= perl is in system
.endif
# only one shlib version number for ELF
.if ${PORTOBJFORMAT} == "elf"
TCL_LIB_FILE= ${TCL_LIB}.${SHLIB_MAJOR}
.else
TCL_LIB_FILE= ${TCL_LIB}.${SHLIB_MAJOR}.${SHLIB_MINOR}
.endif
# software already makes link for ELF, but not for a.out
post-install:
.if ${PORTOBJFORMAT} == "aout"
${LN} -sf liblinpack.so.1.0 ${PREFIX}/lib/liblinpack.so
.endif</programlisting>
</programlisting>
<para>You did remember to use tab instead of spaces after
<literal>BROKEN=</literal> and
<literal>TCL_LIB_FILE=</literal>, did you not?
<!-- smiley -->:-).</para>
</sect1>
@ -16836,4 +16886,29 @@ pre-install:
about creating has already been submitted.</para>
</sect1>
</chapter>
<chapter id="appendices">
<title>Appendices</title>
<sect1 id="uses-values">
<title>Values of <makevar>USES</makevar></title>
<table frame="none">
<title>Values of <makevar>USES</makevar></title>
<tgroup cols="2">
<thead>
<row>
<entry>Feature</entry>
<entry>Arguments</entry>
<entry>Description</entry>
</row>
</thead>
<tbody>
&values.uses;
</tbody>
</tgroup>
</table>
</sect1>
</chapter>
</book>

61
en_US.ISO8859-1/books/porters-handbook/uses.xml Normal file
View file

@ -0,0 +1,61 @@
<!--
The FreeBSD Documentation Project
$FreeBSD$
This file documents the values of the USES make variable. The format is
easy to grasp from the already-added entries below (or use this scheme
below as a skeleton):
<row>
<entry><literal>FEATURE</literal></entry>
<entry>ARGUMENTS</entry>
<entry>DESCRIPTION</entry>
</row>
-->
<row>
<entry><literal>bison</literal></entry>
<entry>none, <literal>build</literal>, <literal>run</literal>,
<literal>both</literal></entry>
<entry>Implies that the port uses <filename
role="package">devel/bison</filename> in one way or another. By
default, with no arguments or with the <literal>build</literal>
argument, it implies <command>bison</command> as a build-time
dependency, <literal>run</literal> implies a run-time dependency, and
<literal>both</literal> implies both run-time and build-time
dependencies.</entry>
</row>
<row>
<entry><literal>fuse</literal></entry>
<entry>none</entry>
<entry>Implies the port will depend on the FUSE library and handle the
the dependency on the kernel module depending on the version of
&os;.
</entry>
</row>
<row>
<entry><literal>pathfix</literal></entry>
<entry>none</entry>
<entry>Look for the <filename>Makefile.in</filename> and
<filename>configure</filename> files in the port's associated
sources and fix common paths to make sure they respect the &os;
hierarchy.</entry>
</row>
<row>
<entry><literal>qmail</literal></entry>
<entry>none, <literal>build</literal>, <literal>run</literal>,
<literal>both</literal>, <literal>vars</literal></entry>
<entry>Implies that the port uses <filename
role="package">mail/qmail</filename> in one way or another. With
the <literal>build</literal> argument, it implies <command>qmail</command>
as a build-time dependency. <literal>run</literal> implies a run-time
dependency. Using no argument or the <literal>both</literal> argument
implies both run-time and build-time dependencies. <literal>vars</literal>
will only set QMAIL variables for the port to use.</entry>
</row>

3
en_US.ISO8859-1/htdocs/Makefile
View file

@ -13,7 +13,6 @@ DOCS= about.xml
DOCS+= administration.xml
DOCS+= applications.xml
DOCS+= art.xml
DOCS+= availability.xml
DOCS+= docs.xml
DOCS+= features.xml
DOCS+= internet.xml
@ -45,7 +44,6 @@ DATA+= freebsd.css
DATA+= google6bb24ed0b804d5e9.html
DATA+= index.css
DATA+= robots.txt
DATA+= vendors.html
# Subdirectories
# XML
@ -76,7 +74,6 @@ SUBDIR+= search
SUBDIR+= security
SUBDIR+= snapshots
SUBDIR+= support
SUBDIR+= tutorials
.if !defined(WEB_ONLY) || empty(WEB_ONLY)
SUBDIR+= doc
SUBDIR+= ports

3
en_US.ISO8859-1/htdocs/about.xml
View file

@ -16,7 +16,8 @@
<h2>What is FreeBSD?</h2>
<p>FreeBSD is an advanced operating system for x86
compatible (including Pentium&reg; and Athlon&trade;), amd64
compatible (including Pentium&reg; and Athlon&trade;),
amd64, x86-64 and x64
compatible (including Opteron&trade;, Athlon&trade;64,
and EM64T), ARM, IA-64, PowerPC, PC-98 and UltraSPARC&reg;
architectures. It is derived from BSD, the version of

85
en_US.ISO8859-1/htdocs/administration.xml
View file

@ -4,6 +4,10 @@
<!ENTITY title "FreeBSD Project Administration and Management">
]>
<!-- NOTE: If any alias listed on this page is modified in the
/etc/aliases on the FreeBSD project's mail server,
then this page must be updated. -->
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>&title;</title>
@ -57,8 +61,6 @@
<li><a href="#t-bugmeister">Bugmeisters &amp; GNATS
Administrators</a></li>
<li><a href="#t-clusteradm">Cluster Administrators</a></li>
<li><a href="#t-pcvs">CVS ports Repository Managers</a></li>
<li><a href="#t-ncvs">CVS src Repository Managers</a></li>
<li><a href="#t-cvsup-master">CVSup Mirror Site
Coordinators</a></li>
<li><a href="#t-dnsadm">DNS Administrators</a></li>
@ -67,6 +69,7 @@
<li><a href="#t-perforce-admin">Perforce Repository
Administrators</a></li>
<li><a href="#t-postmaster">Postmaster Team</a></li>
<li><a href="#t-subversion">Subversion Administrators</a></li>
<li><a href="#t-webmaster">Webmaster Team</a></li>
</ul>
</li>
@ -126,10 +129,9 @@
<li>&a.tabthorpe; &lt;<a href="mailto:tabthorpe@FreeBSD.org">tabthorpe@FreeBSD.org</a>&gt;</li>
<li>&a.marcus; &lt;<a href="mailto:marcus@FreeBSD.org">marcus@FreeBSD.org</a>&gt;</li>
<li>&a.bapt; &lt;<a href="mailto:bapt@FreeBSD.org">bapt@FreeBSD.org</a>&gt;</li>
<li>&a.bdrewery; &lt;<a href="mailto:bdrewery@FreeBSD.org">bdrewery@FreeBSD.org</a>&gt;</li>
<li>&a.decke; &lt;<a href="mailto:decke@FreeBSD.org">decke@FreeBSD.org</a>&gt;</li>
<li>&a.beat; &lt;<a href="mailto:beat@FreeBSD.org">beat@FreeBSD.org</a>&gt;</li>
<li>&a.erwin; &lt;<a href="mailto:erwin@FreeBSD.org">erwin@FreeBSD.org</a>&gt;</li>
<li>&a.linimon; &lt;<a href="mailto:linimon@FreeBSD.org">linimon@FreeBSD.org</a>&gt;</li>
<li>&a.itetcu; &lt;<a href="mailto:itetcu@FreeBSD.org">itetcu@FreeBSD.org</a>&gt;</li>
<li>&a.miwi; &lt;<a href="mailto:miwi@FreeBSD.org">miwi@FreeBSD.org</a>&gt;</li>
</ul>
@ -157,7 +159,7 @@
</ul>
<h3><a name="t-re-builder">Builders Release Engineering Team</a>
&lt;<a href="mailto:re-builder@FreeBSD.org">re-builder@FreeBSD.org</a>&gt;</h3>
&lt;<a href="mailto:re-builders@FreeBSD.org">re-builders@FreeBSD.org</a>&gt;</h3>
<p>The builders release engineering team is responsible
for building and packaging FreeBSD releases on the various supported
@ -233,10 +235,9 @@
<ul>
<li>&a.benl; &lt;<a href="mailto:benl@FreeBSD.org">benl@FreeBSD.org</a>&gt;</li>
<li>&a.bz; &lt;<a href="mailto:bz@FreeBSD.org">bz@FreeBSD.org</a>&gt;</li>
<li>&a.cperciva; &lt;<a href="mailto:cperciva@FreeBSD.org">cperciva@FreeBSD.org</a>&gt;</li>
<li>&a.cperciva; &lt;<a href="mailto:cperciva@FreeBSD.org">cperciva@FreeBSD.org</a>&gt; (Officer Emeritus)</li>
<li>&a.csjp; &lt;<a href="mailto:csjp@FreeBSD.org">csjp@FreeBSD.org</a>&gt;</li>
<li>&a.delphij; &lt;<a href="mailto:delphij@FreeBSD.org">delphij@FreeBSD.org</a>&gt;</li>
<li>&a.delphij; &lt;<a href="mailto:delphij@FreeBSD.org">delphij@FreeBSD.org</a>&gt; (Officer Deputy)</li>
<li>&a.des; &lt;<a href="mailto:des@FreeBSD.org">des@FreeBSD.org</a>&gt;</li>
<li>&a.gavin; &lt;<a href="mailto:gavin@FreeBSD.org">gavin@FreeBSD.org</a>&gt;</li>
<li>&a.jonathan; &lt;<a href="mailto:jonathan@FreeBSD.org">jonathan@FreeBSD.org</a>&gt;</li>
@ -246,6 +247,7 @@
<li>&a.simon; &lt;<a href="mailto:simon@FreeBSD.org">simon@FreeBSD.org</a>&gt;
(Officer)</li>
<li>&a.stas; &lt;<a href="mailto:stas@FreeBSD.org">stas@FreeBSD.org</a>&gt;</li>
<li>&a.trasz; &lt;<a href="mailto:trasz@FreeBSD.org">trasz@FreeBSD.org</a>&gt;</li>
</ul>
<h3><a name="t-vendor">Vendor Relations</a>
@ -314,9 +316,7 @@
acted upon without the proper approval from the appropriate entity.</p>
<ul>
<li>&a.markm; &lt;<a href="mailto:markm@FreeBSD.org">markm@FreeBSD.org</a>&gt;</li>
<li>&a.simon; &lt;<a href="mailto:simon@FreeBSD.org">simon@FreeBSD.org</a>&gt;</li>
<li>&a.kensmith; &lt;<a href="mailto:kensmith@FreeBSD.org">kensmith@FreeBSD.org</a>&gt;</li>
<li>&a.dhw; &lt;<a href="mailto:dhw@FreeBSD.org">dhw@FreeBSD.org</a>&gt;</li>
</ul>
@ -328,7 +328,6 @@
<ul>
<li>&a.simon; &lt;<a href="mailto:simon@FreeBSD.org">simon@FreeBSD.org</a>&gt;</li>
<li>&a.kensmith; &lt;<a href="mailto:kensmith@FreeBSD.org">kensmith@FreeBSD.org</a>&gt;</li>
<li>&a.dhw; &lt;<a href="mailto:dhw@FreeBSD.org">dhw@FreeBSD.org</a>&gt;</li>
</ul>
@ -344,7 +343,6 @@
<li>&a.eadler; &lt; <a href="mailto:eadler@FreeBSD.org">eadler@FreeBSD.org</a>&gt;</li>
<li>&a.gavin; &lt;<a href="mailto:gavin@FreeBSD.org">gavin@FreeBSD.org</a>&gt;</li>
<li>&a.gonzo; &lt;<a href="mailto:gonzo@FreeBSD.org">gonzo@FreeBSD.org</a>&gt;</li>
<li>&a.linimon; &lt;<a href="mailto:linimon@FreeBSD.org">linimon@FreeBSD.org</a>&gt;</li>
</ul>
<h3><a name="t-clusteradm">Cluster Administrators</a>
@ -368,44 +366,6 @@
<li>&a.simon; &lt;<a href="mailto:simon@FreeBSD.org">simon@FreeBSD.org</a>&gt;</li>
</ul>
<h3><a name="t-pcvs">CVS ports Repository Managers</a>
&lt;<a href="mailto:pcvs@FreeBSD.org">pcvs@FreeBSD.org</a>&gt;</h3>
<p>The CVS ports Repository Managers are allowed to directly modify the
repository without using the CVS tool. It is their responsibility to
ensure that technical problems that arise in the repository are
resolved quickly. The CVS ports repository managers have the
authority to back out commits if this is necessary to resolve a CVS
technical problem. Repo-copy requests should be directed to the
repository managers.</p>
<ul>
<li>&a.marcus; &lt;<a href="mailto:marcus@FreeBSD.org">marcus@FreeBSD.org</a>&gt;</li>
<li>&a.joe; &lt;<a href="mailto:joe@FreeBSD.org">joe@FreeBSD.org</a>&gt;</li>
<li>&a.kuriyama; &lt;<a href="mailto:kuriyama@FreeBSD.org">kuriyama@FreeBSD.org</a>&gt;</li>
<li>&a.markm; &lt;<a href="mailto:markm@FreeBSD.org">markm@FreeBSD.org</a>&gt;</li>
<li>&a.simon; &lt;<a href="mailto:simon@FreeBSD.org">simon@FreeBSD.org</a>&gt;</li>
</ul>
<h3><a name="t-ncvs">CVS src Repository Managers</a>
&lt;<a href="mailto:ncvs@FreeBSD.org">ncvs@FreeBSD.org</a>&gt;</h3>
<p>The CVS src Repository Managers are allowed to directly modify the
repository without using the CVS tool. It is their responsibility to
ensure that technical problems that arise in the repository are
resolved quickly. The CVS source repository managers have the
authority to back out commits if this is necessary to resolve a CVS
technical problem. Repo-copy requests should be directed to the
repository managers.</p>
<ul>
<li>&a.joe; &lt;<a href="mailto:joe@FreeBSD.org">joe@FreeBSD.org</a>&gt;</li>
<li>&a.kuriyama; &lt;<a href="mailto:kuriyama@FreeBSD.org">kuriyama@FreeBSD.org</a>&gt;</li>
<li>&a.markm; &lt;<a href="mailto:markm@FreeBSD.org">markm@FreeBSD.org</a>&gt;</li>
<li>&a.simon; &lt;<a href="mailto:simon@FreeBSD.org">simon@FreeBSD.org</a>&gt;</li>
<li>&a.peter; &lt;<a href="mailto:peter@FreeBSD.org">peter@FreeBSD.org</a>&gt;</li>
</ul>
<h3><a name="t-cvsup-master">CVSup Mirror Site Coordinators</a>
&lt;<a href="mailto:cvsup-master@FreeBSD.org">cvsup-master@FreeBSD.org</a>&gt;</h3>
@ -417,7 +377,6 @@
<ul>
<li>&a.kuriyama; &lt;<a href="mailto:kuriyama@FreeBSD.org">kuriyama@FreeBSD.org</a>&gt;</li>
<li>&a.jdp; &lt;<a href="mailto:jdp@FreeBSD.org">jdp@FreeBSD.org</a>&gt;</li>
<li>&a.kensmith; &lt;<a href="mailto:kensmith@FreeBSD.org">kensmith@FreeBSD.org</a>&gt;</li>
</ul>
@ -429,10 +388,10 @@
services.</p>
<ul>
<li>&a.dg; &lt;<a href="mailto:dg@FreeBSD.org">dg@FreeBSD.org</a>&gt;</li>
<li>&a.ps; &lt;<a href="mailto:ps@FreeBSD.org">ps@FreeBSD.org</a>&gt;</li>
<li>&a.kensmith; &lt;<a href="mailto:kensmith@FreeBSD.org">kensmith@FreeBSD.org</a>&gt;</li>
<li>&a.brd; &lt;<a href="mailto:brd@FreeBSD.org">brd@FreeBSD.org</a>&gt;</li>
<li>&a.simon; &lt;<a href="mailto:simon@FreeBSD.org">simon@FreeBSD.org</a>&gt;</li>
<li>&a.peter; &lt;<a href="mailto:peter@FreeBSD.org">peter@FreeBSD.org</a>&gt;</li>
<li>&a.bz; &lt;<a href="mailto:bz@FreeBSD.org">bz@FreeBSD.org</a>&gt;</li>
</ul>
<h3><a name="t-mirror-admin">FTP/WWW Mirror Site Coordinators</a>
@ -445,8 +404,11 @@
the general public to find their closest FTP/WWW mirror.</p>
<ul>
<li>&a.brd; &lt;<a href="mailto:brd@FreeBSD.org">brd@FreeBSD.org</a>&gt;</li>
<li>&a.kuriyama; &lt;<a href="mailto:kuriyama@FreeBSD.org">kuriyama@FreeBSD.org</a>&gt;</li>
<li>&a.simon; &lt;<a href="mailto:simon@FreeBSD.org">simon@FreeBSD.org</a>&gt;</li>
<li>&a.kensmith; &lt;<a href="mailto:kensmith@FreeBSD.org">kensmith@FreeBSD.org</a>&gt;</li>
<li>&a.bz; &lt;<a href="mailto:bz@FreeBSD.org">bz@FreeBSD.org</a>&gt;</li>
</ul>
<h3><a name="t-perforce-admin">Perforce Repository Administrators</a>
@ -459,12 +421,11 @@
administrators.</p>
<ul>
<li>&a.scottl; &lt;<a href="mailto:scottl@FreeBSD.org">scottl@FreeBSD.org</a>&gt;</li>
<li>&a.gibbs; &lt;<a href="mailto:gibbs@FreeBSD.org">gibbs@FreeBSD.org</a>&gt;</li>
<li>&a.kensmith; &lt;<a href="mailto:kensmith@FreeBSD.org">kensmith@FreeBSD.org</a>&gt;</li>
<li>&a.gordon; &lt;<a href="mailto:gordon@FreeBSD.org">gordon@FreeBSD.org</a>&gt;</li>
<li>&a.rwatson; &lt;<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>&gt;</li>
<li>&a.peter; &lt;<a href="mailto:peter@FreeBSD.org">peter@FreeBSD.org</a>&gt;</li>
<li>&a.dhw; &lt;<a href="mailto:dhw@FreeBSD.org">dhw@FreeBSD.org</a>&gt;</li>
</ul>
<h3><a name="t-postmaster">Postmaster Team</a>
@ -483,6 +444,17 @@
<li>&a.dhw; &lt;<a href="mailto:dhw@FreeBSD.org">dhw@FreeBSD.org</a>&gt;</li>
</ul>
<h3><a name="t-subversion">Subversion Administrators</a> &lt;svnadm@&gt;</h3>
<p>The FreeBSD Subversion team is responsible for maintaining the health of
the Subversion Repositories.</p>
<ul>
<li>&a.bz; &lt;<a href="mailto:bz@FreeBSD.org">bz@FreeBSD.org</a>&gt;</li>
<li>&a.peter; &lt;<a href="mailto:peter@FreeBSD.org">peter@FreeBSD.org</a>&gt;</li>
<li>&a.simon; &lt;<a href="mailto:simon@FreeBSD.org">simon@FreeBSD.org</a>&gt;</li>
</ul>
<h3><a name="t-webmaster">Webmaster Team</a>
&lt;<a href="mailto:webmaster@FreeBSD.org">webmaster@FreeBSD.org</a>&gt;</h3>
@ -498,6 +470,7 @@
<li>&a.simon; &lt;<a href="mailto:simon@FreeBSD.org">simon@FreeBSD.org</a>&gt;</li>
<li>&a.jesusr; &lt;<a href="mailto:jesusr@FreeBSD.org">jesusr@FreeBSD.org</a>&gt;</li>
<li>&a.wosch; &lt;<a href="mailto:wosch@FreeBSD.org">wosch@FreeBSD.org</a>&gt;</li>
<li>&a.don; &lt;<a href="mailto:don@FreeBSD.org">don@FreeBSD.org</a>&gt;</li>
</ul>
</body>

5
en_US.ISO8859-1/htdocs/advocacy/index.xml
View file

@ -28,6 +28,11 @@
<h2>Web resources</h2>
<ul>
<li><p><a href="&base;/news/status/status.html">FreeBSD quarterly status reports</a></p>
<p>Quarterly status reports detailing activity within and surrounding FreeBSD.</p></li>
</ul>
<ul>
<li><p><a href="whyusefreebsd.html">Why Use FreeBSD?</a></p>

27
en_US.ISO8859-1/htdocs/availability.xml
View file

@ -1,27 +0,0 @@
<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE html PUBLIC "-//FreeBSD//DTD XHTML 1.0 Transitional-Based Extension//EN"
"http://www.FreeBSD.org/XML/doc/share/xml/xhtml10-freebsd.dtd" [
<!ENTITY title "About FreeBSD's availability">
]>
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="refresh" content="5;url=&base;/index.html"/>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/>
<title>&title;</title>
<cvs:keyword xmlns:cvs="http://www.FreeBSD.org/XML/CVS">$FreeBSD$</cvs:keyword>
</head>
<body class="navinclude.about">
<p>The content of this page has been integrated into the <a
href="&base;/index.html">main FreeBSD webpage</a>. You should
be automatically redirected there in a few seconds. If not,
please follow the link and update your bookmarks.</p>
<p>We apologize for the inconvenience.</p>
</body>
</html>

1
en_US.ISO8859-1/htdocs/cgi/query-pr.cgi
View file

@ -198,6 +198,7 @@ sub main
$patch->filename;
print $patch->data;
print "\n";
Exit();
}

27
en_US.ISO8859-1/htdocs/developers/cvs.xml
View file

@ -24,8 +24,11 @@
<p>In June 2008, development of the base system moved to a different
version control system, <a href="http://subversion.tigris.org/">Subversion</a>
(SVN for short). The <a href="http://svnweb.FreeBSD.org/base/">web
interface</a> is available for browsing the repository. All changes are
also exported back to the CVS repository.</p>
interface</a> is available for browsing the repository. All changes
to the existing live branches (stable/9 and stable/8) are
also exported back to the legacy CVS repository, however the
CVS repositories are deprecated, and so existing users of them
should move away from doing so.</p>
<p>In May 2012, the FreeBSD Documentation Project moved from CVS
to Subversion. Unlike the base system, the documentation SVN
@ -35,11 +38,11 @@
Project SVN repository.</p>
<p>In July 2012, the FreeBSD Ports tree moved from CVS to
Subversion. There is a <a
href="http://svnweb.FreeBSD.org/ports/">web interface</a> for
browsing the repository. The Ports tree is also exported back
to the CVS repository.
It will cease to be exported early 2013.</p>
Subversion. There is a <a
href="http://svnweb.FreeBSD.org/ports/">web interface</a> for
browsing the repository. The Ports tree is also exported back
to the legacy CVS repository.
It will cease to be exported early 2013.</p>
<h2>Legacy - CVS</h2>
@ -50,14 +53,14 @@
the sources under control.</p>
<p>The old web interface can be accessed at <a
href="http://www.freebsd.org/cgi/cvsweb.cgi/">the cvsweb instance
</a>.</p>
href="http://www.freebsd.org/cgi/cvsweb.cgi/">the cvsweb instance
</a>.</p>
<h2>Other options</h2>
<p><a href="&base;/doc/en_US.ISO8859-1/books/handbook/ctm.html">
CTM</a> if you are looking for
very low overhead, batch-mode access (basically, patches through
email).</p>
CTM</a> if you are looking for
very low overhead, batch-mode access (basically, patches through
email).</p>
</body>
</html>

9
en_US.ISO8859-1/htdocs/docs/books.xml
View file

@ -147,11 +147,6 @@
An article with some tips about the subtleties of
CVSup.</p>
<p><a href="&url.articles;/euro/index.html">The Euro symbol
on FreeBSD</a> (euro)<br/>
How to configure FreeBSD and related applications to display the
Euro symbol.</p>
<p><a href="&url.articles;/explaining-bsd/index.html">Explaining
BSD</a> (explaining-bsd)<br/>
An answer to the question ``What is BSD?''</p>
@ -410,12 +405,12 @@
</li>
<li>
<p><a href="http://software.intel.com/sites/oss/pdfs/profiling_debugging_freebsd_kernel_321772.pdf">Profiling
<p><a href="http://software.intel.com/sites/default/files/profiling_debugging_freebsd_kernel_321772.pdf">Profiling
and Debugging the FreeBSD Kernel</a></p>
</li>
<li>
<p><a href="http://software.intel.com/sites/oss/pdfs/debugging_buffer_overruns_322486.pdf">Debugging
<p><a href="http://software.intel.com/sites/default/files/debugging_buffer_overruns_322486.pdf">Debugging
Buffer Overruns in the FreeBSD Kernel</a></p>
</li>

19
en_US.ISO8859-1/htdocs/features.xml
View file

@ -58,6 +58,7 @@
functions with hook points of interest within the kernel.
These allow a structured way to dynamically extend the
kernel at runtime in an ABI preserving manner.</li>
<li><b>Accounting API:</b> has been implemented. It can keep
per-process, per-jail, and per-login class resource
accounting information. Note that this is neither built nor
@ -96,15 +97,15 @@
net.inet.tcp.cc.algorithm.</li>
<li><b>SU+J:</b> &os;'s Fast File System now supports soft
updates with journaling. It introduces an intent log into a
softupdates-enabled file system which eliminates the need for
background fsck(8) even on unclean shutdowns.</li>
updates with journaling. It introduces an intent log into
a softupdates-enabled file system which eliminates the need
for background fsck(8) even on unclean shutdowns.</li>
</ul>
<p><b>&os;&nbsp;8.x</b> brings many new
<p><b>&os;&nbsp;8.x</b> brought many new
features and performance enhancements. With special focus on
a new USB stack, &os;-8.x shipped with experimental support
for NFSv4. As well as a new TTY layer. Which improves
a new USB stack, &os;-8.x also shipped with experimental support
for NFSv4. A new TTY layer was introduced, which improves
scalability and resources handling in SMP enabled systems.</p>
<ul>
@ -117,6 +118,12 @@
benchmarks on SMP machines show substantial performance
improvement over the previous version.</li>
<li><b>Jail improvements:</b> Jails now support multiple IPv4
and IPv6 addresses per jail, and also support SCTP.
Hierarchies of jails (jails-within-jails) are now supported,
and jails can now be restricted to subsets of available
CPUs.</li>
<li><b>Linux emulation:</b> layer has been updated to version
2.6.16 and the default Linux infrastructure port is now
emulators/linux_base-f10 (Fedora 10)</li>

4
en_US.ISO8859-1/htdocs/gnome/index.xsl
View file

@ -130,8 +130,8 @@
<h2>State of the port</h2>
<p>GNOME for FreeBSD is currently fully supported on
8.1, 8.2, 8-STABLE, 9.0, and 9-STABLE, while 7.3, 7.4, 7-STABLE,
and 10.0-CURRENT are provided on a best effort basis.
8.3, 8-STABLE, 9.0, 9.1, and 9-STABLE, while
10.0-CURRENT is provided on a best effort basis.
Most of GNOME has been ported to FreeBSD, but there is still
<a href="docs/volunteer.html">plenty left to be done</a>!</p>

4
en_US.ISO8859-1/htdocs/index.xsl
View file

@ -82,9 +82,9 @@
<h2><a href="&base;/releases/">LATEST RELEASES</a></h2>
<ul id="frontreleaseslist">
<li>Production:&nbsp;<a
href="&u.rel.announce;">&rel.current;</a>,&nbsp;<a href="&u.rel2.announce;">&rel2.current;</a></li>
href="&u.rel.announce;">&rel.current;</a></li>
<li>Legacy: <a
href="&u.rel3.announce;">&rel3.current;</a></li>
href="&u.rel2.announce;">&rel2.current;</a></li>
<xsl:if test="'&beta.testing;' != 'IGNORE'">
<li>Upcoming: <a
href="&base;/where.html#helptest">&betarel.current;-&betarel.vers;</a></li>

1
en_US.ISO8859-1/htdocs/internal/Makefile
View file

@ -22,6 +22,7 @@ DOCS+= machines.xml
DOCS+= mirror.xml
DOCS+= new-account.xml
DOCS+= policies.xml
DOCS+= proposing-committers.xml
DOCS+= releng.xml
DOCS+= resources.xml
DOCS+= statistic.xml

8
en_US.ISO8859-1/htdocs/internal/README.mirror
View file

@ -1,17 +1,17 @@
You can (and are encouraged to) mirror the pages with CVSup.
You can mirror the web pages with csup.
If you are running apache as installed from the ports collection the
following should make a copy of www.freebsd.org available from
http://wwwN.XX.freebsd.org/. Of course, there are possible
variations on the method...
1) The CVSup file to get the WWW pages
1) The csup file to get the WWW pages
(/usr/local/www/data/freebsd.cvsup in the next step):
www release=current host=cvsup.freebsd.org hostbase=/home base=/usr prefix=/usr/local/www/data/www.freebsd.org delete old use-rel-suffix
www release=current host=cvsup.freebsd.org base=/usr prefix=/usr/local/www/data/www.freebsd.org delete use-rel-suffix
2) Add to /etc/crontab
1 5 * * * root /usr/local/bin/cvsup -z -g /usr/local/www/data/freebsd.cvsup
1 5 * * * root /usr/bin/csup -z -g /usr/local/www/data/freebsd.cvsup
2) Add to /usr/local/etc/apache/access.conf:

2
en_US.ISO8859-1/htdocs/internal/about.xml
View file

@ -117,7 +117,7 @@ Building and updating the FreeBSD Web Pages</a></h2>
href="http://www.freebsd.org/build/index.cgi">here</a>.</p>
<h2>Mirroring the FreeBSD Web Pages</h2>
<p>You can (and are encouraged to) <a href="mirror.html">mirror</a>
<p>It is possible to <a href="mirror.html">mirror</a>
the FreeBSD web pages on www.FreeBSD.org.</p>
<p></p><a href="internal.html">FreeBSD Internal Home</a>

2
en_US.ISO8859-1/htdocs/internal/fortunes.xml
View file

@ -23,7 +23,7 @@
<p>If an entry offends more than a couple of FreeBSD committers and
does not contain any reasonable historical reference, the entry should
be in the offensive file. The speaker of the quote is not to be the
not be added. The speaker of the quote is not to be the
basis for categorizing the quote as offensive.</p>
<p>Examples of offensive entries:</p>

35
en_US.ISO8859-1/htdocs/internal/mirror.xml
View file

@ -13,42 +13,27 @@
<body class="navinclude.docs">
<p>You can (and are encouraged to) mirror the FreeBSD web pages
<p>It is possible to mirror the FreeBSD web pages
<tt>www.FreeBSD.org</tt>.
To do this, you need to obtain and install
a program called <em>cvsup</em> on your web server.
This can be done using a program called <em>csup</em>.
<a href="&url.doc.base;/books/handbook/cvsup.html#CVSUP-INSTALL">CVSup</a> is a software package for
csup is a software package in the base system for
distributing and updating collections of files across a network.</p>
<h2>Installing CVSup</h2>
<p>You can build and install it from source by the following commands:</p>
<pre>
# cd /usr/ports/net/cvsup-without-gui
# make all install clean
</pre>
<p>However, installing precompiled package from the FreeBSD
<a href="&url.doc.base;/books/handbook/packages-using.html">packages
collection</a> may be much easier.
Refer to the chapter mentioned for the details.</p>
<h2>Running CVSup</h2>
<h2>Running csup</h2>
<p>If you keep your mirrored FreeBSD web pages in the directory
<tt>/usr/FreeBSD-mirror</tt> and are owned by the user `fred', then
run the following command as user `fred':</p>
<pre>
$ cvsup supfile-www
$ csup supfile-www
</pre>
The file <tt>supfile-www</tt> contain:
<pre>
*default host="cvsup".FreeBSD.org
*default host=cvsup.FreeBSD.org
*default prefix=/usr/FreeBSD-mirror
*default base=/usr/local/etc/cvsup
www release="current" delete use-rel-suffix compress
@ -56,13 +41,7 @@ The file <tt>supfile-www</tt> contain:
<p>This will mirror the FreeBSD web pages into
<tt>/usr/FreeBSD-mirror</tt>. You can install this into fred's
crontab, so that it runs once a day. The pages on www.FreeBSD.org are
updated daily at about 4:30am California time.</p>
<h2>More Information on CVSup</h2>
See the <a href="&url.doc.base;/books/handbook/synching.html#CVSUP">CVSup introduction</a> in the
handbook.
crontab, so that it runs once a day.</p>
<p><a href="internal.html">FreeBSD Internal Home</a></p>

31
en_US.ISO8859-1/htdocs/internal/new-account.xml
View file

@ -29,7 +29,9 @@
<p>Any commit bit requests that do not follow the guidelines outlined
above will be delayed (at best) or earn you negative vibrations from the
respective team / team secretary.
respective team / team secretary. For some guidelines on how the
proposal itself should be written, please see <a
href="proposing-committers.html">a brief summary</a>.
</p>
<p>Responsible party for this procedure is:</p>
@ -73,11 +75,18 @@
and send the following information to accounts@:</p>
<ul>
<li><p><tt>master.passwd</tt> line containing preferred username,
shell, and GECOS info (no password is needed)</p></li>
<li><p>username (lowercase a-z and 0-9)</p></li>
<li><p>Full Name (as would go in a GECOS field)</p></li>
<li><p>optional additional GECOS information (phone, location etc)</p></li>
<li><p>shell (sh, csh/tcsh, bash, zsh are available)</p></li>
<li><p>ssh V2 public key (<strong>version 2 ONLY</strong>)</p></li>
</ul>
<p>Any non-ASCII characters for the <em>Full Name</em> field should be encoded
in UTF-8. Be aware that we have very limited support for this and caution
that they are likely to be frequently corrupted. The number of characters
should kept to a minimum.</p>
<p>The mentor is responsible for obtaining this information from the
new committer in a secure fashion, and providing it to accounts@ in
a secure fashion. PGP-signed email, with the mentor's public key
@ -102,9 +111,9 @@
<p>After the new committer confirms that the account works, the mentor
adds the new committer to the correct <tt>access</tt> file,
using an appropriate commit message. The commit message should at least
contain the committer's full name, the mentor's name and what area
the new committer will start to work in. For src and doc commit
bits, an entry should also be added to the <tt>mentors</tt> file in
contain the committer's full name and username, the mentor's
name and what area the new committer will start to work in.
An entry should also be added to the <tt>mentors</tt> file in
the respective Subversion repository to indicate
the mentor relationship. Having done all that,
the new committer and mentor jointly go through the first commit
@ -121,19 +130,15 @@
<p>There is no pre-set duration for a mentorship. Once the mentor feels
the mentee is ready to 'fly solo' the mentor notifies the developer
community by removing the entry from the <tt>mentors</tt> file in SVN,
or via a forced commit to <tt>access</tt> in CVS with an appropriate
commit message.</p>
community by removing the entry from the <tt>mentors</tt> file in
SVN.</p>
<h2>Transfer Of Mentorship</h2>
<p>Should a need arise to transfer mentorship for a committer
please email the responsible party, as described for a new account
proposal. Typically this request is rubberstamped as-is.
In Subversion, the <tt>mentors</tt> file should be updated.
In CVS, a forced commit to <tt>access</tt> with an appropriate commit
message is to be used to inform the world of the transfer.</p>
In Subversion, the <tt>mentors</tt> file should be updated.</p>
</body>
</html>

56
en_US.ISO8859-1/htdocs/internal/proposing-committers.xml Normal file
View file

@ -0,0 +1,56 @@
<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE html PUBLIC "-//FreeBSD//DTD XHTML 1.0 Transitional-Based Extension//EN"
"http://www.FreeBSD.org/XML/doc/share/xml/xhtml10-freebsd.dtd" [
<!ENTITY title "Proposing Committers">
]>
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>&title;</title>
<cvs:keyword xmlns:cvs="http://www.FreeBSD.org/XML/CVS">$FreeBSD$</cvs:keyword>
</head>
<body class="navinclude.docs">
<p>The following paragraphs contain an advice from &a.kib;, member of
the Core Team, who summarizes what constitutes a good proposal, how
you as potential mentor, could increase your chances to have your
mentee granted a commit bit.</p>
<p>When proposing somebody, you should just forget for a moment that you
know the candidate personally. After that, look unprejudiced on the
person's activity on the mailing lists, and evaluate the patches
submitted.</p>
<p>Now, you can ask yourself, is it enough confidence in both technical
abilities and the social behavior of the candidate, from what you see
only on the media? If you do, then write down the reasons why are
you sure, using the said list of the contributions as the evidence,
and do include the reasoning in the commit bit application.</p>
<p>Due to several failures of the premature granting of commit bits, the
Core Team became quite sensitive to these criteria. Most of the
members only see the activity of applicants on the lists, and not
seeing much there causes the cautious choice.</p>
<p>The Core Team wants to see a good list of the work already done for
&os; (e.g., the long list of the commits, submitted by the applicant,
the list of PRs opened etc.), which can make us confident that the
person has an established interest in the project, backed by the
technical ability and work done.</p>
<p>Also, the history of the good engagement with the community on the
public media, such as mailing list, is a deciding factor too. The
Core Team wants to filter out the controversial personalities, since
it is almost impossible and highly undesirable to revoke the commit
bit, once granted.</p>
<p>Vendor-proposed maintainers for the hardware drivers usually approved
without applying the listed criteria. Still, the Core Team requires
an experienced mentor for a vendor committer to avoid unwanted tension
and to make sure that vendor commits follow the Project procedures and
community expectations.</p>
</body>
</html>

9
en_US.ISO8859-1/htdocs/layout/css/layout.css
View file

@ -401,9 +401,6 @@
padding: 0;
width: 130px;
background-color: #D8D8D8;
-moz-border-radius: 10px;
-webkit-border-radius: 10px;
-khtml-border-radius: 10px;
border-radius: 10px;
}
@ -436,9 +433,6 @@
padding: 0;
width: 180px;
background-color: white;
-moz-border-radius: 10px;
-webkit-border-radius: 10px;
-khtml-border-radius: 10px;
border-radius: 10px;
}
@ -472,9 +466,6 @@
padding: 0;
width: 190px;
background-color: #FACC2E;
-moz-border-radius: 10px;
-webkit-border-radius: 10px;
-khtml-border-radius: 10px;
border-radius: 15px;
}

28
en_US.ISO8859-1/htdocs/news/2012-compromise.xml
View file

@ -62,6 +62,7 @@
<ul>
<li><a href="#announce">Announcement</a></li>
<li><a href="#update20130303">Update: 3rd March 2013</a></li>
<li><a href="#update20121229">Update: 29th December 2012</a></li>
<li><a href="#update20121127">Update: 27th November 2012</a></li>
<li><a href="#update20121122">Update: 22nd November 2012</a></li>
@ -72,6 +73,27 @@
<li><a href="#recommend">Recommendations</a></li>
</ul>
<h1><a name="update20130302">Update: March 3rd, 2013</a></h1>
<p>Redports underwent a full security audit, and as a result could
be brought back on line. This took place on the 5th February, and
since then more backend hardware has been added to bring it back
up to full strength. On 11th February, sanity checks for ports
have been turned back on, reenabling generation and update of the
INDEX files used. The portsnap(8) service has been switched from
CVS to SVN on 25th February. The binary package building
infrastructure has undergone a major security review, and as a
result many changes have been made to the code. The review
completed on the 16th February and we are now in the process of
bringing it up on new hardware. At this point, we expect new
binary packages to be available in 2-4 weeks.</p>
<p>Unless there are any other major changes, this is planned to be
the last status update to this page. An email will be sent to
the <a href="http://lists.freebsd.org/mailman/listinfo/freebsd-announce">
FreeBSD announcements mailing list</a> when the package build
infrastructure is online and packages are once again available.</p>
<h1><a name="update20121229">Update: December 29th, 2012</a></h1>
<p>With the exception of systems relating to the building and testing
@ -94,12 +116,6 @@
<a href="/doc/handbook/ports-using.html">
FreeBSD Handbook</a>.</p>
<p>Unless there are any other major changes, this is planned to be
the last status update to this page. An email will be sent to
the <a href="http://lists.freebsd.org/mailman/listinfo/freebsd-announce">
FreeBSD announcements mailing list</a> when the package build
infrastructure is online and packages are once again available.</p>
<h1><a name="update20121127">Update: November 27th, 2012</a></h1>
<p>Due to the legacy third-party package build controller head

2
en_US.ISO8859-1/htdocs/news/status/Makefile
View file

@ -56,6 +56,8 @@ XMLDOCS+= report-2011-07-2011-09
XMLDOCS+= report-2011-10-2011-12
XMLDOCS+= report-2012-01-2012-03
XMLDOCS+= report-2012-04-2012-06
XMLDOCS+= report-2012-07-2012-09
XMLDOCS+= report-2012-10-2012-12
XSLT.DEFAULT= report.xsl

22
en_US.ISO8859-1/htdocs/news/status/README
View file

@ -25,7 +25,7 @@ Compiling status reports - best practices
4) Putting it all together:
- Copy and paste all reports in a single .xml file and use tidy(1) to get
it well formatted. Usually <url>'s without a description are missing
it well formatted. Usually <url>s without a description are missing
the closing "/>" which is the cause for most of the errors you will
encounter. Sometimes other closing tags are missing.
- Invoking tidy with the following options seems to cause the fewest
@ -44,7 +44,7 @@ Compiling status reports - best practices
</ul>
<p>Some more blabla ...
5) After the a couple iterations of the above, wrap the whole thing in a
5) After a couple of iterations of the above, wrap the whole thing in a
report template:
<?xml version="1.0" encoding="iso-8859-1" ?>
@ -136,14 +136,11 @@ Report//EN"
the html helps. Make sure you have an up-to-date doc tree.
6) Sending it out:
- Just prior to committing, build the html locally.
- Extract a text version: lynx -dump -nolist report.html > report.txt
- Prettify.
- Send out To: hackers, CC: current, stable. New email to: announce@ this
one needs to be approved. Find somebody who can do that before you
start.
- Commit. Also update the next due date in status.sgml and link to the
new report.
- Commit, hooking the report XML to the build but not linking to it
from anywhere. This gives time for other committers to review and
suggest minor changes.
- After a few days, collate and commit the changes. Also update the
next due date in status.xml and link to the new report.
- Add a news entry to head/share/xml/news.xml. Template:
<event>
<title>June-October, 2006 Status Report</title>
@ -152,5 +149,10 @@ Report//EN"
href="&enbase;/news/status/report-2006-06-2006-10.html">now
available</a> with 49 entries.</p>
</event>
- Extract a text version with the command
lynx -dump -nolist report.html > report.txt and prettify it.
- Send out To: hackers, CC: current, stable. New email to: announce@.
This needs to be approved, so find someone who can do that before you
start.
7) Repeat.

4
en_US.ISO8859-1/htdocs/news/status/report-2012-04-2012-06.xml
View file

@ -16,7 +16,7 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/xml/statusreport.dtd">
2012. This quarter was highlighted by having a new Core Team
elected, which took office on July 11th to start its work with a
relatively high number of new members. Note that this is the
second of the three reports planned for 2012.</p>
second of the four reports planned for 2012.</p>
<p>Thanks to all the reporters for the excellent work! This report
contains 17 entries and we hope you enjoy reading it.</p>
@ -524,7 +524,7 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/xml/statusreport.dtd">
<task>Test KDE SC 4.8.95.</task>
<task>Test KDE PIM 4.8.95.</task>
<task>Update out-of-date ports, see <a
href="http://portscout.org/kde@freebsd.org.html">PortScout</a> for a
href="http://portscout.FreeBSD.org/kde@freebsd.org.html">PortScout</a> for a
list.</task>
</help>
</project>

713
en_US.ISO8859-1/htdocs/news/status/report-2012-07-2012-09.xml Normal file
View file

@ -0,0 +1,713 @@
<?xml version="1.0" encoding="iso-8859-1" ?>
<!DOCTYPE report PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for Status Report//EN" "http://www.FreeBSD.org/XML/www/share/xml/statusreport.dtd" >
<!-- $FreeBSD$ -->
<report>
<date>
<month>July-September</month>
<year>2012</year>
</date>
<section>
<title>Introduction</title>
<p>This report covers &os;-related projects between July and
September 2012. This is the third of the four reports planned for
2012.</p>
<p>Highlights from this quarter include successful participation in
Google Summer of Code, major work in areas of the source and
ports trees, and a Developer Summit attended by over 30
developers.</p>
<p>Thanks to all the reporters for the excellent work! This report
contains 12 entries and we hope you enjoy reading it.</p>
</section>
<category>
<name>proj</name>
<description>Projects</description>
</category>
<category>
<name>team</name>
<description>&os; Team Reports</description>
</category>
<category>
<name>kern</name>
<description>Kernel</description>
</category>
<category>
<name>docs</name>
<description>Documentation</description>
</category>
<category>
<name>ports</name>
<description>Ports</description>
</category>
<category>
<name>misc</name>
<description>Miscellaneous</description>
</category>
<category>
<name>soc</name>
<description>&os; in Google Summer of Code</description>
</category>
<project cat='proj'>
<title>&os; on Altera FPGAs</title>
<contact>
<person>
<name>
<given>Brooks</given>
<common>Davis</common>
</name>
<email>brooks@FreeBSD.org</email>
</person>
<person>
<name>
<given>Robert</given>
<common>Watson</common>
</name>
<email>rwatson@FreeBSD.org</email>
</person>
<person>
<name>
<given>Bjoern</given>
<common>Zeeb</common>
</name>
<email>bz@FreeBSD.org</email>
</person>
</contact>
<links>
<url href="http://www.cl.cam.ac.uk/research/security/ctsrd/">
CTSRD Project</url>
<url
href="http://www.cl.cam.ac.uk/research/security/ctsrd/cheri.html">
CHERI</url>
</links>
<body>
<p>In the course of developing the <a
href="http://www.cl.cam.ac.uk/research/security/ctsrd/cheri.html">
CHERI processor</a> as part of the <a
href="http://www.cl.cam.ac.uk/research/security/ctsrd/">CTSRD
project</a> SRI International's Computer Science Laboratory and
the University of Cambridge Computer Laboratory have developed
support for a number of general purpose IP cores for Altera FPGAs
including the Altera Triple Speed Ethernet (ATSE) MAC core, the
Altera University Program SD Card core, and the Altera JTAG UART.
We have also added support for general access to memory mapped
devices on the Avalon bus via the avgen bus. We have implemented
both nexus and flattened device tree (FDT) attachments for these
devices.</p>
<p>In addition to these softcore we have developed support for
the Terasic multi-touch LCD and are working to provide support
for the Terasic HDMI Transmitter Daughter Card. Both of these
work with common development and/or reference boards for Altera
FPGAs. They do require additional IP cores which we plan to
release to the open source community in the near future.</p>
<p>With exception of the ATSE and HDMI drivers we have merged all
of these changes to &os;-CURRENT. We anticipate that these
drivers will be useful for users who with to run &os; on either
hard or soft core CPUs on Altera FPGAs.</p>
<p>This work has been sponsored by DARPA, AFRL, and Google.</p>
</body>
</project>
<project cat='proj'>
<title>Native iSCSI Target</title>
<contact>
<person>
<name>
<given>Edward Tomasz</given>
<common>Napiera&#322;a</common>
</name>
<email>trasz@FreeBSD.org</email>
</person>
</contact>
<links>
</links>
<body>
<p>During the July-September time period, the Native iSCSI Target
project was officially started under sponsorship from the &os;
Foundation. Before the end of September I've written ctld(8), the
userspace part of the target, responsible for handling
configuration, accepting incoming connections, performing
authentication and iSCSI parameter negotiation, and handing off
connections to the kernel. For the time being, I've reused some
parts of protocol-handling code from the istgt project; since
ctld(8) only handles the Login phase, the code can be rewritten
in a much simpler and shorter way in the future.</p>
</body>
</project>
<project cat='proj'>
<title>Parallel rc.d execution</title>
<contact>
<person>
<name>
<given>Kuan-Chung</given>
<common>Chiu</common>
</name>
<email>buganini@gmail.com</email>
</person>
<person>
<name>
<given>Kilian</given>
</name>
<email>kklimek@uos.de</email>
</person>
</contact>
<links>
<url href="https://github.com/buganini/rcexecr" />
<url href="https://github.com/kil/rcorder" />
</links>
<body>
<p>There are two implementations to make rc.d execution parallel.
Compared to Kil's rcorder, rcexecr brings more concurrence and
provides more flexibility than older "early_late_divider"
mechanism but require more invasive /etc patch. Both
implementations have switch to toggle parallel execution. Further
modification/integration needs more discussion.</p>
</body>
<help>
<task>Refine /etc/rc.d/* to eliminate unnecessary waiting.</task>
</help>
</project>
<project cat='team'>
<title>&os; Bugbusting Team</title>
<contact>
<person>
<name>
<given>Eitan</given>
<common>Adler</common>
</name>
<email>eadler@FreeBSD.org</email>
</person>
<person>
<name>
<given>Gavin</given>
<common>Atkinson</common>
</name>
<email>gavin@FreeBSD.org</email>
</person>
<person>
<name>
<given>Oleksandr</given>
<common>Tymoshenko</common>
</name>
<email>gonzo@FreeBSD.org</email>
</person>
</contact>
<links>
<url href="http://www.FreeBSD.org/support.html#gnats" />
<url href="https://wiki.freebsd.org/BugBusting" />
</links>
<body>
<p>In August, Eitan Adler (eadler@) and Oleksandr Tymoshenko
(gonzo@) joined the Bugmeister team. At the same time, Remko
Lodder and Volker Werth stepped down. We extend our thanks to
Volker and Remko for their work in the past, and welcome
Oleksandr and Eitan. Eitan and Oleksandr have been working hard
on migrating from GNATS, and have made significant progress on
evaluating new software, and creating scripts to export data
from GNATS.</p>
<p>The bugbusting team continue work on trying to make the
contents of the GNATS PR database cleaner, more accessible and
easier for committers to find and resolve PRs, by tagging PRs
to indicate the areas involved, and by ensuring that there is
sufficient info within each PR to resolve each issue.</p>
<p>As always, anybody interested in helping out with the PR
queue is welcome to join us in #freebsd-bugbusters on EFnet. We
are always looking for additional help, whether your interests
lie in triaging incoming PRs, generating patches to resolve
existing problems, or simply helping with the database
housekeeping (identifying duplicate PRs, ones that have already
been resolved, etc). This is a great way of getting more
involved with &os;!</p>
</body>
<help>
<task>Further research into tools suitable to replace
GNATS.</task>
<task>Get more users involved with triaging PRs as they come
in.</task>
<task>Assist committers with closing PRs.</task>
</help>
</project>
<project cat='team'>
<title>The &os; Core Team</title>
<contact>
<person>
<name>
<given>Core Team</given>
</name>
<email>core@FreeBSD.org</email>
</person>
</contact>
<body>
<p>Along with the change in the Core Team membership, several
related roles changed hands. Gabor Pali assumed the role of core
secretary from Gavin Atkinson, and David Chisnall replaced Robert
Watson as liaison to the &os; Foundation. The Core Team felt
there was no longer a need for a formal security team liaison, so
that role was retired.</p>
<p>In the third quarter, the Core Team granted access for 2 new
committers and took 2 commit bits into safekeeping.</p>
<p>The Core Team worked with the Port Management Team and Cluster
Administrators to set a date to stop providing CVS exports for
the ports repository, which is February 28, 2013. In the
meantime, the CVS export for 9.1-RELEASE was restored.</p>
</body>
</project>
<project cat='team'>
<title>&os; Foundation</title>
<contact>
<person>
<name>
<given>Deb</given>
<common>Goodkin</common>
</name>
<email>deb@FreeBSDFoundation.org</email>
</person>
</contact>
<links>
<url
href="http://www.freebsdfoundation.org/press/2012Jul-newsletter.shtml">
Semi-annual newsletter</url>
</links>
<body>
<p>The Foundation hosted and sponsored the Cambridge &os;
developer summit in August 2012.</p>
<p>We were represented at the following conferences: OSCON July
2012, Texas LinuxFest, and Ohio LinuxFest.</p>
<p>We negotiated/supervised Foundation funded projects:
Distributed Security Audit Logging, Capsicum Component
Framework, Native iSCSI Target Scoping, and Growing UFS
Filesystems Online.</p>
<p>We negotiated, supervised, and funded hardware needs for
&os; co-location centers.</p>
<p>We welcomed Kirk McKusick to our board of directors. He took
over the responsibility of managing our investments.</p>
<p>We visited companies to discuss their &os; use and to help
facilitate collaboration with the Project.</p>
<p>We managed &os; vendor community mailing list and
meetings.</p>
<p>We created a high quality &os; 9 brochure to help promote
&os;.</p>
<p>Published our <a
href="http://www.freebsdfoundation.org/press/2012Jul-newsletter.shtml">
semi-annual newsletter</a> that highlighted Foundation
funded projects, travel grants for
developers, conferences sponsored and other ways the Foundation
supported the &os; Project.</p>
<p>We hired a technical writer to help with &os;
marketing/promotional material.</p>
<p>We began work on redesigning our website.</p>
</body>
</project>
<project cat='kern'>
<title>&os; on ARMv6/ARMv7</title>
<contact>
<person>
<name>
<given>freebsd-arm mailing list</given>
</name>
<email>freebsd-arm@FreeBSD.org</email>
</person>
</contact>
<links>
</links>
<body>
<p>Support for ARMv6 and ARMv7 architecture has been merged from
project branch to HEAD. This code covers the following parts:
<ul>
<li>General ARMv6/ARMv7 kernel bits (pmap, cache, assembler
routines, etc...)</li>
<li>ARM Generic Interrupt Controller driver</li>
<li>Improved thread-local storage for cpus &gt;=ARMv6</li>
<li>Driver for SMSC LAN95XX and LAN8710A ethernet controllers</li>
<li>Marvell MV78x60 support (multiuser, ARMADA XP kernel config)</li>
<li>TI OMAP4 and AM335x support (multiuser, no GPU or graphics
support, kernel configs for Pandaboard and Beaglebone)</li>
<li>LPC32x0 support (multiuser, frame buffer works with SSD1289
LCD controller. Embedded Artists EA3250 kernel config)</li>
</ul>
</p>
<p>This work was a result of a joint effort by many people,
including but not limited to: Grzegorz Bernacki (gber@),
Aleksander Dutkowski, Ben R. Gray (bgray@), Olivier Houchard
(cognet@), Rafal Jaworowski (raj@) and Semihalf team, Tim
Kientzle (kientzle@), Jakub Wojciech Klama (jceel@), Ian Lepore
(ian@), Warner Losh (imp@), Damjan Marion (dmarion@), Lukasz
Plachno, Stanislav Sedov (stas@), Mark Tinguely and Andrew
Turner (andrew@). Thanks to all, who contributed by
submitting code, testing and giving valuable advice.</p>
</body>
<help>
<task>More hardware bring-ups and more drivers</task>
<task>Finish SMP support</task>
<task>VFP/NEON support</task>
</help>
</project>
<project cat='docs'>
<title>The &os; Japanese Documentation Project</title>
<contact>
<person>
<name>
<given>Hiroki</given>
<common>Sato</common>
</name>
<email>hrs@FreeBSD.org</email>
</person>
<person>
<name>
<given>Ryusuke</given>
<common>Suzuki</common>
</name>
<email>ryusuke@FreeBSD.org</email>
</person>
</contact>
<links>
<url href="http://www.FreeBSD.org/ja/">Japanese &os; Web
Page</url>
<url href="http://www.jp.FreeBSD.org/doc-jp/">The &os; Japanese
Documentation Project Web Page</url>
</links>
<body>
<p>Web page (htdocs): Newsflash and some other updates in the
English version were translated to keep them up-to-date.
Especially "security incident on &os; infrastructure" was
translated and published in a timely manner.</p>
<p>&os; Handbook: Big update in the "advanced-networking". With
this update, merging translation results from the handbook in the
local repository of Japanese documentation project into the main
repository was completed. This chapter is still outdated and
needs more work. The other sections have also constantly been
updated. Especially, new subsection "Using pkgng for Binary
Package Management" was added to "ports" section and "Using
subversion" subsection was added to "mirrors" section.</p>
<p>Article: Some progress was made in "Writing &os; Problem
Reports" and "Writing &os; Problem Reports" articles.</p>
</body>
<help>
<task>Further translation work of outdated documents in the
<tt>ja_JP.eucJP</tt> subtree.</task>
</help>
</project>
<project cat='ports'>
<title>KDE/&os;</title>
<contact>
<person>
<name>
<given>KDE</given>
<common>FreeBSD</common>
</name>
<email>kde@FreeBSD.org</email>
</person>
</contact>
<links>
<url href="http://FreeBSD.kde.org">KDE/&os; home page</url>
<url href="http://FreeBSD.kde.org/area51.php">area51</url>
</links>
<body>
<p>The KDE/&os; team have continued to improve the experience of
KDE software and Qt under &os;. The latest round of improvements
include:
<ul>
<li>Fixes for building Qt with libc++ and C++11</li>
<li>Fixes for Solid-related crashes</li>
<li>Fix battery detection in battery monitor plasmoid</li>
</ul>
</p>
<p>The team has also made many releases and upstreamed many fixes
and patches. The latest round of releases include:
<ul>
<li>KDE SC: 4.9.1 (area51) and 4.8.4 (ports)</li>
<li>Qt: 4.8.3 (area51)</li>
<li>PyQt: 4.9.4 (area51); QScintilla 2.6.2 (area51); SIP:
4.13.3 (area51)</li>
<li>Calligra: 2.4.3, 2.5-RC2, 2.5.0. 2.5.1, 2.5.2 (area51) and
2.4.3, 2.5.0, 2.5.1 (ports)</li>
<li>Amarok: 2.6.0 (area51)</li>
<li>CMake: 2.8.9 (ports)</li>
<li>Digikam (and KIPI-plugins): 2.7.0, 2.8.0, 2.9.0 (area51)
and 2.7.0, 2.9.0 (ports)</li>
<li>QtCreator: 2.6.0-beta (area51)</li>
<li>many smaller ports</li>
</ul>
</p>
<p>The team is always looking for more testers and porters so
please contact us at kde@FreeBSD.org and visit our home page at
<a href="http://FreeBSD.kde.org">http://FreeBSD.kde.org</a>.</p>
</body>
<help>
<task>Please see 2012 Q4 Status Report</task>
<task>Updating out-of-date ports, see
<a href="http://portscout.FreeBSD.org/kde@freebsd.org.html">PortScout</a>
for a list</task>
</help>
</project>
<project cat='ports'>
<title>Ports Collection</title>
<contact>
<person>
<name>
<given>Thomas</given>
<common>Abthorpe</common>
</name>
<email>portmgr-secretary@FreeBSD.org</email>
</person>
<person>
<name>
<given>Port</given>
<common>Management Team</common>
</name>
<email>portmgr@FreeBSD.org</email>
</person>
</contact>
<links>
<url href="http://www.FreeBSD.org/ports/" />
<url href="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/" />
<url href="http://portsmon.freebsd.org/index.html" />
<url href="http://www.freebsd.org/portmgr/index.html" />
<url href="http://blogs.freebsdish.org/portmgr/" />
<url href="http://www.twitter.com/freebsd_portmgr/" />
<url href="http://www.facebook.com/portmgr" />
</links>
<body>
<p>The ports tree approaches 24,000 ports, while the PR count
still is above 1000.</p>
<p>In Q3 we added 2 new committers and took in two commits bit
for safe keeping.</p>
<p>The Ports Management team had performed multiple -exp runs,
verifying how base system updates may affect the ports tree,
as well as providing QA runs for major ports updates.</p>
<p>Beat Gaetzi took over the role of sending out fail mails, a
role that Pav Lucistnik had previously held. Beat also undertook
the task of converting the Ports tree from CVS to Subversion.</p>
<p>Florent Thoumie stepped down from his role on portmgr, he was
instrumental in maintaining the legacy pkg_* code.</p>
</body>
<help>
<task>Most ports PRs are assigned, we now need to focus on
testing, committing and closing.</task>
</help>
</project>
<project cat='misc'>
<title>&os; Developer Summit, Cambridge, UK</title>
<contact>
<person>
<name>
<given>Robert</given>
<common>Watson</common>
</name>
<email>rwatson@FreeBSD.org</email>
</person>
</contact>
<links>
<url href="https://wiki.freebsd.org/201208DevSummit">Developer
Summit Home Page</url>
</links>
<body>
<p>In the end of August, there was an "off-season" Developer
Summit held in Cambridge, UK at the University of Cambridge
Computer Laboratory. This was a three-day event, with a
documentation summit scheduled for the day before. The three
days of the main event were split into three sessions, with two
tracks in each. Some of them even involved ARM developers from
the neighborhoods which proven to be productive, and led to
further engagement between the &os; community and ARM.</p>
<p>The schedule was finalized on the first day, spawning a
plethora of topics to discuss, followed by splitting into groups.
A short summary from each of the groups was presented in the
final session and then published at the event's home page on the
&os; wiki. This summit contributed greatly to arriving to a
tentative plan for throwing the switch to make clang the default
compiler on HEAD. This was further discussed on the mailing list,
and has now happened, bringing us one big step closer to a
GPL-free &os; 10. As part of the program, an afternoon of short
talks from researchers in the Cambridge Computer Laboratory
involved either operating systems work in general or &os; in
particular. Robert Watson showed off a tablet running &os; on a
MIPS-compatible soft-core processor running on an Altera
FPGA.</p>
<p>In association with the event, a dinner was hosted by St. John's
college and co-sponsored by Google and the &os; Foundation. The
day after the conference, a trip was organized to Bletchley Park,
which was celebrating Turing's centenary in 2012.</p>
</body>
</project>
<project cat='soc'>
<title>Google Summer of Code 2012</title>
<contact>
<person>
<name>
<given>
</given>
<common>&os; Summer of Code Administrators</common>
</name>
<email>soc-admins@FreeBSD.org</email>
</person>
</contact>
<links>
<url href="http://www.freebsd.org/projects/summerofcode.html">
FreeBSD Summer of Code page</url>
<url href="https://wiki.freebsd.org/SummerOfCode2012">Summer of
Code 2012 projects</url>
</links>
<body>
<p>Over the Summer of 2012, &os; were once again granted a
place to participate in the Google Summer of Code program. We
received a total of 32 project proposals, and were ultimately
given 15 slots for university students to work on open source
projects mentored by existing &os; developers.</p>
<p>We were able to accept a wide spread of proposals, covering
both the base system and the ports infrastructure. We had
students working on file systems, file integrity checking, and
parallelization in the ports collection. Students worked on
kernel infrastructure, including one project to support CPU
resource limits on users, processes and jails, and one student
improving the BSD callout(9) and timer facilities. Two students
worked on the ARM platform, widely used in embedded systems and
smart phones; one student worked on a significant cleanup and
improvements to the Flattened Device Tree implementation code,
while the other ported &os; to the OMAP3-based BeagleBoard-xM
device. One student worked on improving IPv6 support in
userland tools, whilst another worked on BIOS emulation for the
BHyVE BSD-licensed hypervisor, new in &os; 10. Other students
worked on EFI boot support, userland lock profiling and an
automated kernel crash reporting system.</p>
<p>Overall, a significant proportion of the code produced has
or will be integrated into &os; in one form or another. All of
the work is available in our Summer Of Code Subversion
repository, and some of the work has already been merged back
into the main repositories.</p>
<p>&os; is once again grateful to Google for being selected to
participate in Summer of Code 2012.</p>
</body>
</project>
</report>

1456
en_US.ISO8859-1/htdocs/news/status/report-2012-10-2012-12.xml Normal file
View file

File diff suppressed because it is too large Load diff

6
en_US.ISO8859-1/htdocs/news/status/status.xml
View file

@ -13,7 +13,7 @@
<body class="navinclude.about">
<h2>Next submissions due: February 17th, 2013</h2>
<h2>Next submissions due: April 21st, 2013</h2>
<p>Use the <a href="http://www.FreeBSD.org/cgi/monthly.cgi">xml
generator</a> or download and edit the <a href="report-sample.xml">
@ -47,6 +47,10 @@
<h2>2012</h2>
<ul>
<li><a href="report-2012-10-2012-12.html">October, 2012 -
December, 2012</a></li>
<li><a href="report-2012-07-2012-09.html">July, 2012 -
September, 2012</a></li>
<li><a href="report-2012-04-2012-06.html">April, 2012 -
June, 2012</a></li>
<li><a href="report-2012-01-2012-03.html">January, 2012 -

9
en_US.ISO8859-1/htdocs/platforms/amd64.xml
View file

@ -18,18 +18,19 @@
<p>This page contains information of the FreeBSD port to <a
href="http://www.amd.com/">AMD's</a> AMD64 and <a
href="http://developer.intel.com/technology/intel64/index.htm">Intel&reg;
href="http://www.intel.com/info/em64t">Intel&reg;
64</a> architecture. The
AMD64 architecture was previously known as x86-64 or ``Hammer.''
AMD64 architecture was previously known as <q>Hammer</q>.
The Intel 64 architecture was previously known as Yamhill,
Clackamas Technology (CT), IA-32e, and EM64T (Extended Memory 64-bit
Technology).</p>
Technology). Generically, the platform is often known as
<q>x86-64</q> or <q>x64</q>.</p>
<p>The AMD Opteron&trade;, AMD Athlon&trade; 64, AMD Turion&trade;
64 and newer AMD Sempron&trade; processors use the AMD64
architecture.</p>
<p>The Intel vPro&trade;, Intel Celeron D (some models since ``Prescott''),
<p>The Intel vPro&trade;, Intel Celeron D (some models since <q>Prescott</q>),
Intel Centrino&reg; Duo, Intel Centrino&reg; Pro,
Intel Viiv&trade;, Intel Core&trade;2 Extreme, Intel Core&trade;2 Quad,
Intel Core&trade;2 Duo, Intel Xeon (3000-sequence, 5000-sequence, and

9
en_US.ISO8859-1/htdocs/projects/newbies.xml
View file

@ -95,6 +95,15 @@
answers via the <a href="&base;/search/search.html#mailinglists">search</a>
page.</p></li>
<li><p>The main newsgroup for &os; is <a
href="news:comp.unix.bsd.freebsd.misc">comp.unix.bsd.freebsd.misc</a>.
General UNIX questions are dealt with in the newsgroup <a
href="news:comp.unix.questions">comp.unix.questions</a> and the
associated <a
href="ftp://rtfm.mit.edu/pub/usenet/news.answers/unix-faq/faq/">FAQ</a>
from the RMIT FTP site. Newbies are likely to be most
interested in sections 1 and 2 initially.</p></li>
<li><p><a href="&cgibase;/man.cgi">Manual pages</a> are good
for reference but not always
the best introduction for a novice. The more you work with man pages

6
en_US.ISO8859-1/htdocs/projects/projects.xml
View file

@ -58,12 +58,6 @@ mailing list and participate.</li>
A list of resources to help those new to FreeBSD and &unix; in
general.</li>
<li><a name="BSDsites" href="http://mirrorlist.FreeBSD.org/">
RELEASE/SNAP finder for FreeBSD FTP servers</a>:
A resource that would allow anyone to find a FTP server that contains
particular releases and SNAP of FreeBSD. The database is updated daily
at 3am Melbourne time (10 hours ahead of UTC).</li>
<li><a name="diary" href="http://www.freebsddiary.org/">The FreeBSD
Diary</a>: A collection of how-to entries aimed at UNIX
novices. The aim is to provide a set of step-by-step guides to

8
en_US.ISO8859-1/htdocs/tutorials/Makefile → en_US.ISO8859-1/htdocs/releases/8.4R/Makefile
View file

@ -1,8 +1,4 @@
#
# $FreeBSD$
#
# Build the FreeBSD tutorials/articles outside of the www tree, and then
# install them in to the right place.
.if exists(../Makefile.conf)
.include "../Makefile.conf"
@ -11,6 +7,8 @@
.include "../Makefile.inc"
.endif
DOCS = index.xml
DOCS+= schedule.xml
DATA= docbook.css
.include "${DOC_PREFIX}/share/mk/web.site.mk"

242
en_US.ISO8859-1/htdocs/releases/8.4R/docbook.css Normal file
View file

@ -0,0 +1,242 @@
/*
* Copyright (c) 2001, 2003, 2010 The FreeBSD Documentation Project
* All rights reserved.
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
* 1. Redistributions of source code must retain the above copyright
* notice, this list of conditions and the following disclaimer.
* 2. Redistributions in binary form must reproduce the above copyright
* notice, this list of conditions and the following disclaimer in the
* documentation and/or other materials provided with the distribution.
*
* THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
* ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
* OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
* SUCH DAMAGE.
*
* $FreeBSD$
*/
BODY ADDRESS {
line-height: 1.3;
margin: .6em 0;
}
BODY BLOCKQUOTE {
margin-top: .75em;
line-height: 1.3;
margin-bottom: .75em;
}
HTML BODY {
margin: 1em 8% 1em 10%;
line-height: 1.2;
}
.LEGALNOTICE {
font-size: small;
font-variant: small-caps;
}
BODY DIV {
margin: 0;
}
DL {
margin: .8em 0;
line-height: 1.2;
}
DIV.CALLOUTLIST DT {
float: left;
width: 1em;
}
DIV.CALLOUTLIST DD {
clear: right;
margin-bottom: 1ex;
}
BODY FORM {
margin: .6em 0;
}
H1, H2, H3, H4, H5, H6,
DIV.EXAMPLE P B,
.QUESTION,
DIV.TABLE P B,
DIV.PROCEDURE P B {
color: #990000;
}
BODY H1, BODY H2, BODY H3, BODY H4, BODY H5, BODY H6 {
line-height: 1.3;
margin-left: 0;
}
BODY H1, BODY H2 {
margin: .8em 0 0 -4%;
}
BODY H3, BODY H4 {
margin: .8em 0 0 -3%;
}
BODY H5 {
margin: .8em 0 0 -2%;
}
BODY H6 {
margin: .8em 0 0 -1%;
}
BODY HR {
margin: .6em;
border-width: 0 0 1px 0;
border-style: solid;
border-color: #cecece;
}
BODY IMG.NAVHEADER {
margin: 0 0 0 -4%;
}
OL {
margin: 0 0 0 5%;
line-height: 1.2;
}
BODY PRE {
margin: .75em 0;
line-height: 1.0;
font-family: monospace;
}
BODY TD, BODY TH {
line-height: 1.2;
}
UL, BODY DIR, BODY MENU {
margin: 0 0 0 5%;
line-height: 1.2;
}
HTML {
margin: 0;
padding: 0;
}
BODY P B.APPLICATION {
color: #000000;
}
.FILENAME {
color: #007a00;
}
SVNREF {
color: #007a00;
}
.GUIMENU, .GUIMENUITEM, .GUISUBMENU,
.GUILABEL, .INTERFACE,
.SHORTCUT, .SHORTCUT .KEYCAP {
font-weight: bold;
}
.GUIBUTTON {
background-color: #CFCFCF;
padding: 2px;
}
.ACCEL {
background-color: #F0F0F0;
text-decoration: underline;
}
.SCREEN {
padding: 1ex;
}
.PROGRAMLISTING {
padding: 1ex;
background-color: #eee;
border: 1px solid #ccc;
line-height: 1.1;
}
@media screen { /* hide from IE3 */
a[href]:hover { background: #ffa }
}
.INFORMALTABLE, .TABLE TH {
padding-left: 02.em;
text-align: left;
}
BLOCKQUOTE, .EXAMPLE, .PROGRAMLISTING {
-moz-border-radius: 6px;
-webkit-border-radius: 6px;
-khtml-border-radius: 6px;
border-radius: 6px;
}
BLOCKQUOTE {
padding: 0 2ex;
}
BLOCKQUOTE.NOTE {
color: #222;
background: #eee;
border: 1px solid #ccc;
width: 85%;
}
BLOCKQUOTE.TIP {
color: #004F00;
background: #d8ecd6;
border: 1px solid green;
width: 85%;
}
BLOCKQUOTE.IMPORTANT {
font-style:italic;
border: 1px solid #a00;
border-left: 12px solid #c00;
}
BLOCKQUOTE.WARNING {
color: #9F1313;
background: #f8e8e8;
border: 1px solid #e59595;
width: 85%;
}
BLOCKQUOTE.CAUTION {
color: #3E3535;
background: #FFC;
border: 1px solid #e59595;
width: 85%;
}
.EXAMPLE {
background: #fefde6;
border: 1px solid #f1bb16;
margin: 1em 0;
padding: 0.2em 2em;
width: 90%;
}
.INFORMALTABLE TABLE.CALSTABLE TR TD {
padding-left: 1em;
padding-right: 1em;
}

134
en_US.ISO8859-1/htdocs/releases/8.4R/schedule.xml Normal file
View file

@ -0,0 +1,134 @@
<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE html PUBLIC "-//FreeBSD//DTD XHTML 1.0 Transitional-Based Extension//EN"
"http://www.FreeBSD.org/XML/doc/share/xml/xhtml10-freebsd.dtd" [
<!ENTITY email 'freebsd-qa'>
<!ENTITY local.rel "8.4">
<!ENTITY title "FreeBSD &local.rel; Release Process">
]>
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>&title;</title>
<cvs:keyword xmlns:cvs="http://www.FreeBSD.org/XML/CVS">$FreeBSD$</cvs:keyword>
</head>
<body class="navinclude.download">
<h1>Introduction</h1>
<p>This is the release schedule for FreeBSD &local.rel;. For more
information about the release engineering process, please see the <a
href="&base;/releng/index.html">Release Engineering</a> section of the
web site.</p>
<p>General discussions about the pending release and known issues should be
sent to the public
<a href="mailto:FreeBSD-stable@FreeBSD.org">freebsd-stable</a> mailing list.
</p>
<h1>Schedule</h1>
<table class="tblbasic">
<tr class="heading">
<td>Action</td>
<td>Expected</td>
<td>Actual</td>
<td>Description</td>
</tr>
<tr>
<td>Initial release schedule announcement</td>
<td>-</td>
<td>08&nbsp;February&nbsp;2013</td>
<td>Release Engineers send announcement email to developers with a
rough schedule.</td>
</tr>
<tr>
<td>Announce <tt>doc/</tt> tree slush</td>
<td>-</td>
<td>28&nbsp;February&nbsp;2013</td>
<td>Notification of the impending <tt>doc/</tt> tree slush
should be sent to <tt>doc@</tt>.</td>
</tr>
<tr>
<td>Code freeze begins</td>
<td>08&nbsp;March&nbsp;2013</td>
<td>-</td>
<td>Release Engineers announce that all further commits to the
stable/8 branch will require explicit approval.
Certain blanket approvals will be granted for narrow areas of
development, documentation improvements, etc.</td>
</tr>
<tr>
<td>BETA1</td>
<td>20&nbsp;March&nbsp;2013</td>
<td>-</td>
<td>First beta test snapshot.</td>
</tr>
<tr>
<td><tt>doc/</tt> tree slush</td>
<td>17&nbsp;March&nbsp;2013</td>
<td>17&nbsp;March&nbsp;2013</td>
<td>Non-essential commits to the <tt>en_US.ISO8859-1/</tt>
subtree should be delayed from this point until after the
<tt>doc/</tt> tree tagging, to give translation teams time to
synchronize their work.</td>
</tr>
<tr>
<td>releng/&local.rel; branch</td>
<td>18&nbsp;March&nbsp;2013</td>
<td>-</td>
<td>Subversion branch created, propagated to CVS; future
release engineering proceeds on this branch.</td>
</tr>
<tr>
<td>RC1</td>
<td>30&nbsp;March&nbsp;2013</td>
<td>-</td>
<td>First release candidate.</td>
</tr>
<tr>
<td>RC2</td>
<td>05&nbsp;April&nbsp;2013</td>
<td>-</td>
<td>Second release candidate.</td>
</tr>
<tr>
<td>RELEASE build</td>
<td>12&nbsp;April&nbsp;2013</td>
<td>-</td>
<td>&local.rel;-RELEASE build.</td>
</tr>
<tr>
<td>RELEASE announcement</td>
<td>19&nbsp;April&nbsp;2013</td>
<td>-</td>
<td>&local.rel;-RELEASE press release.</td>
</tr>
<tr>
<td>Turn over to the secteam</td>
<td>-</td>
<td>-</td>
<td>releng/&local.rel; branch is handed over to
the FreeBSD Security Officer Team in one or two weeks after the
announcement.</td>
</tr>
</table>
<!--
<h1>Internal Status / TODO</h1>
<a href="http://wiki.freebsd.org/Releng/8.4TODO">http://wiki.freebsd.org/Releng/8.4TODO</a>
-->
</body>
</html>

2
en_US.ISO8859-1/htdocs/releases/Makefile
View file

@ -16,7 +16,7 @@ SUBDIR+= 4.6.2R 4.7R 4.8R 4.9R 4.10R 4.11R
SUBDIR+= 5.0R 5.1R 5.2R 5.2.1R 5.3R 5.4R 5.5R
SUBDIR+= 6.0R 6.1R 6.2R 6.3R 6.4R
SUBDIR+= 7.0R 7.1R 7.2R 7.3R 7.4R
SUBDIR+= 8.0R 8.1R 8.2R 8.3R
SUBDIR+= 8.0R 8.1R 8.2R 8.3R 8.4R
SUBDIR+= 9.0R 9.1R
.if defined $(NEW_BUILD)

41
en_US.ISO8859-1/htdocs/releases/index.xml
View file

@ -52,6 +52,17 @@
<a href="&u.rel.errata;">Errata</a>
</em></p>
<p><b>Release 9.0</b> (January 2012)
<em>
<a href="9.0R/announce.html">Announcement</a>:
<a href="9.0R/relnotes.html">Release Notes</a>:
<a href="9.0R/installation.html">Installation Instructions</a>:
<a href="9.0R/hardware.html">Hardware Notes</a>:
<a href="9.0R/readme.html">Readme</a>:
<a href="9.0R/errata.html">Errata</a>
</em></p>
<h3>Legacy Releases</h3>
<p><b>Release &rel2.current;</b> (&rel2.current.date;)
<em>
<a href="&u.rel2.announce;">Announcement</a> :
@ -62,16 +73,6 @@
<a href="&u.rel2.errata;">Errata</a>
</em></p>
<h3>Legacy Releases</h3>
<p><b>Release &rel3.current;</b> (&rel3.current.date;)
<em>
<a href="&u.rel3.announce;">Announcement</a> :
<a href="&u.rel3.notes;">Release Notes</a> :
<a href="&u.rel3.hardware;">Hardware Notes</a> :
<a href="&u.rel3.readme;">Readme</a> :
<a href="&u.rel3.errata;">Errata</a>
</em></p>
<a name="future"></a>
<h2>Future Releases</h2>
@ -102,16 +103,6 @@
Information</a> page.</p>
<ul>
<li><b>9.0</b> (January 2012)
<em>
<a href="9.0R/announce.html">Announcement</a>:
<a href="9.0R/relnotes.html">Release Notes</a>:
<a href="9.0R/installation.html">Installation Instructions</a>:
<a href="9.0R/hardware.html">Hardware Notes</a>:
<a href="9.0R/readme.html">Readme</a>:
<a href="9.0R/errata.html">Errata</a>
</em></li>
<li><b>8.2</b> (February 2011)
<em>
<a href="8.2R/announce.html">Announcement</a>:
@ -142,6 +133,16 @@
</em>
</li>
<li><b>7.4</b> (February 2011)
<em>
<a href="7.4R/announce.html">Announcement</a>:
<a href="7.4R/relnotes.html">Release Notes</a>:
<a href="7.4R/hardware.html">Hardware Notes</a>:
<a href="7.4R/readme.html">Readme</a>:
<a href="7.4R/errata.html">Errata</a>
</em>
</li>
<li><b>7.3</b> (March 2010)
<em>
<a href="7.3R/announce.html">Announcement</a>:

10
en_US.ISO8859-1/htdocs/releng/index.xml
View file

@ -52,7 +52,7 @@
<tr>
<td>TBD</td>
<td>&os; 8.4</td>
<td><!-- <a href="&base;/releases/8.4R/schedule.html">Target Schedule</a> --></td>
<td><a href="&base;/releases/8.4R/schedule.html">Target Schedule</a></td>
</tr>
<tr>
@ -146,14 +146,14 @@
<td><tt>RELENG_7</tt></td>
<td>Open</td>
<td>committers</td>
<td>Development branch for 7-STABLE.</td>
<td>Maintenance branch for 7-STABLE (not officially supported).</td>
</tr>
<tr>
<td><tt>RELENG_7_4</tt></td>
<td>Frozen</td>
<td>&contact.so;</td>
<td>FreeBSD 7.4 supported errata fix branch.</td>
<td>FreeBSD 7.4 errata fix branch (not officially supported).</td>
</tr>
<tr>
@ -444,12 +444,10 @@
<p>The FreeBSD Project does not maintain a centralized historical
archive of old release ISO images, but there are still many
options. First, a large collection of the old releases (many
options. A large collection of the old releases (many
complete with the package sets) is at <a
href="ftp://ftp-archive.FreeBSD.org/pub/FreeBSD-Archive/old-releases/">
ftp://ftp-archive.FreeBSD.org/pub/FreeBSD-Archive/old-releases/</a>.
Second, try looking on <a
href="http://mirrorlist.FreeBSD.org">http://mirrorlist.FreeBSD.org</a>.
If you are unable to find an FTP mirror that still contains the
release you are looking for, then you can email CD-ROM vendors to
see if they have any old releases available. In September 2003,

10
en_US.ISO8859-1/htdocs/search/sitemap.xml
View file

@ -1061,7 +1061,7 @@
<term>
<text>Project ideas</text>
<destination>&base;/projects/ideas/index.html</destination>
<destination>https://wiki.freebsd.org/IdeasPage</destination>
</term>
<term>
@ -1270,8 +1270,8 @@
</term>
<term>
<text>Logo design competition</text>
<destination>http://logo-contest.FreeBSD.org/</destination>
<text>Logo</text>
<destination>&base;/logo.html</destination>
</term>
<term>
@ -1520,7 +1520,7 @@
<item>
<text>Project Ideas</text>
<destination>&base;/projects/ideas/index.html</destination>
<destination>https://wiki.freebsd.org/IdeasPage</destination>
</item>
<item>
@ -1665,7 +1665,7 @@
<item>
<text>FreeBSD Project Ideas</text>
<destination>&base;/projects/ideas/index.html</destination>
<destination>https://wiki.freebsd.org/IdeasPage</destination>
</item>
<item>

33
en_US.ISO8859-1/htdocs/security/security.xml
View file

@ -101,6 +101,11 @@
<td>Release Engineering liaison,<br/>
TrustedBSD Project liaison, system security architecture expert</td>
</tr>
<tr valign="top">
<td>&a.delphij; <a
href="mailto:delphij@FreeBSD.org">&lt;delphij@FreeBSD.org&gt;</a></td>
<td>Deputy Security Officer</td>
</tr>
</table>
<p>The Security Officer is supported by the <a
@ -249,20 +254,6 @@
<th>Release Date</th>
<th>Estimated EoL</th>
</tr>
<tr>
<td>RELENG_7</td>
<td>n/a</td>
<td>n/a</td>
<td>n/a</td>
<td>February 28, 2013</td>
</tr>
<tr>
<td>RELENG_7_4</td>
<td>7.4-RELEASE</td>
<td>Extended</td>
<td>February 24, 2011</td>
<td>February 28, 2013</td>
</tr>
<tr>
<td>RELENG_8</td>
<td>n/a</td>
@ -420,6 +411,13 @@
<td>November 28, 2008</td>
<td>November 30, 2010</td>
</tr>
<tr>
<td>RELENG_7</td>
<td>n/a</td>
<td>n/a</td>
<td>n/a</td>
<td>February 28, 2013</td>
</tr>
<tr>
<td>RELENG_7_0</td>
<td>7.0-RELEASE</td>
@ -448,6 +446,13 @@
<td>March 23, 2010</td>
<td>March 31, 2012</td>
</tr>
<tr>
<td>RELENG_7_4</td>
<td>7.4-RELEASE</td>
<td>Extended</td>
<td>February 24, 2011</td>
<td>February 28, 2013</td>
</tr>
<tr>
<td>RELENG_8_0</td>
<td>8.0-RELEASE</td>

22
en_US.ISO8859-1/htdocs/tutorials/index.xml
View file

@ -1,22 +0,0 @@
<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE html PUBLIC "-//FreeBSD//DTD XHTML 1.0 Transitional-Based Extension//EN"
"http://www.FreeBSD.org/XML/doc/share/xml/xhtml10-freebsd.dtd" [
<!ENTITY title "FreeBSD Tutorials">
]>
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>&title;</title>
<cvs:keyword xmlns:cvs="http://www.FreeBSD.org/XML/CVS">$FreeBSD$</cvs:keyword>
</head>
<body class="navinclude.about">
<p>A complete list of documentation pertaining to FreeBSD is now
available at <a href="../docs.html">../docs.html</a>. Please see
that list for further information.</p>
</body>
</html>

19
en_US.ISO8859-1/htdocs/vendors.html
View file

@ -1,19 +0,0 @@
<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!-- $FreeBSD$ -->
<html>
<head>
<meta http-equiv="refresh" content="5;url=doc/en_US.ISO8859-1/books/handbook/mirrors.html" />
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
<title>Vendors who provide FreeBSD</title>
</head>
<body bgcolor="#ffffff">
<p>The list of vendors who carry FreeBSD is available <a
href="doc/en_US.ISO8859-1/books/handbook/mirrors.html">as part of
the FreeBSD Handbook</a>. You should be automatically redirected
there in a few seconds. If not, please follow the link and update
your bookmarks. We apologize for the inconvenience.</p>
</body>
</html>

16
en_US.ISO8859-1/htdocs/where.xml
View file

@ -77,7 +77,7 @@
</tr>
<tr>
<td></td>
<td>amd64</td>
<td>amd64<br/>(x86-64, x64)</td>
<td><a href="&url.rel;/amd64/amd64/&rel.current;-RELEASE">[Distribution]</a></td>
<td><a href="&url.rel;/amd64/amd64/ISO-IMAGES/&rel.current;/">[ISO]</a></td>
</tr>
@ -123,7 +123,7 @@
</tr>
<tr>
<td></td>
<td>amd64</td>
<td>amd64<br/>(x86-64, x64)</td>
<td><a href="&url.rel;/amd64/&rel2.current;-RELEASE">[Distribution]</a></td>
<td><a href="&url.rel;/amd64/ISO-IMAGES/&rel2.current;/">[ISO]</a></td>
</tr>
@ -145,6 +145,7 @@
<td><a href="&url.rel;/sparc64/&rel2.current;-RELEASE">[Distribution]</a></td>
<td><a href="&url.rel;/sparc64/ISO-IMAGES/&rel2.current;/">[ISO]</a></td>
</tr>
<!--
<tr>
<td colspan="2">FreeBSD &rel3.current;-RELEASE</td>
<td colspan="2"></td>
@ -155,28 +156,29 @@
</tr>
<tr>
<td></td>
<td>amd64</td>
<!--<td><a href="&url.rel;/amd64/&rel3.current;-RELEASE">[Distribution]</a></td>-->
<td>amd64<br/>(x86-64, x64)</td>
<td><a href="&url.rel;/amd64/&rel3.current;-RELEASE">[Distribution]</a></td>
<td colspan="2" align="right"><a href="&url.rel;/amd64/ISO-IMAGES/&rel3.current;/">[ISO]</a></td>
</tr>
<tr>
<td></td>
<td>i386</td>
<!--<td><a href="&url.rel;/i386/&rel3.current;-RELEASE">[Distribution]</a></td>-->
<td><a href="&url.rel;/i386/&rel3.current;-RELEASE">[Distribution]</a></td>
<td colspan="2" align="right"><a href="&url.rel;/i386/ISO-IMAGES/&rel3.current;/">[ISO]</a></td>
</tr>
<tr>
<td></td>
<td>pc98</td>
<!--<td><a href="&url.rel;/pc98/&rel3.current;-RELEASE">[Distribution]</a></td>-->
<td><a href="&url.rel;/pc98/&rel3.current;-RELEASE">[Distribution]</a></td>
<td colspan="2" align="right"><a href="&url.rel;/pc98/ISO-IMAGES/&rel3.current;/">[ISO]</a></td>
</tr>
<tr>
<td></td>
<td>sparc64</td>
<!--<td><a href="&url.rel;/sparc64/&rel3.current;-RELEASE">[Distribution]</a></td>-->
<td><a href="&url.rel;/sparc64/&rel3.current;-RELEASE">[Distribution]</a></td>
<td colspan="2" align="right"><a href="&url.rel;/sparc64/ISO-IMAGES/&rel3.current;/">[ISO]</a></td>
</tr>
-->
</tbody>
</table>

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