- Remove the following articles and references to them. Where it is

  reasonable to maintain the reference, use the archived docs.

  5-roadmap
  checkpoint
  dialup-firewall
  diskless-x
  euro
  formatting-media
  hats (content moved to htdocs/internal)
  multi-os
  storage-devices
  vinum
  zip-drive

All of these articles can be found here:
http://docs.freebsd.org/doc/9.0-RELEASE/usr/share/doc/freebsd/en_US.ISO8859-1/articles/

No objection from:	doc@, www@

174 files changed, 35 insertions, 30671 deletions

diff --git a/da_DK.ISO8859-1/articles/Makefile b/da_DK.ISO8859-1/articles/Makefile
index 43ee579ee1..065a20a393 100644
--- a/da_DK.ISO8859-1/articles/Makefile
+++ b/da_DK.ISO8859-1/articles/Makefile
@@ -1,6 +1,5 @@
 # $FreeBSD$
 
-SUBDIR = euro
 SUBDIR+= ipsec-must
 SUBDIR+= pxe
 
diff --git a/da_DK.ISO8859-1/articles/euro/Makefile b/da_DK.ISO8859-1/articles/euro/Makefile
deleted file mode 100644
index 886e21cc9d..0000000000
--- a/da_DK.ISO8859-1/articles/euro/Makefile
+++ /dev/null
@@ -1,14 +0,0 @@
-# $FreeBSD$
-
-DOC?= article
-
-FORMATS?= html
-
-INSTALL_COMPRESSED?=gz
-INSTALL_ONLY_COMPRESSED?=
-
-SRCS= article.sgml
-
-DOC_PREFIX?= ${.CURDIR}/../../..
-
-.include "${DOC_PREFIX}/share/mk/doc.project.mk"
diff --git a/da_DK.ISO8859-1/articles/euro/article.sgml b/da_DK.ISO8859-1/articles/euro/article.sgml
deleted file mode 100644
index 4fc1f30fc9..0000000000
--- a/da_DK.ISO8859-1/articles/euro/article.sgml
+++ /dev/null
@@ -1,368 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1" standalone="no"?>
-<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V4.2-Based Extension//EN"
-	"../../../share/sgml/freebsd42.dtd" [
-<!ENTITY % entities PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Entity Set//DA" "../../share/sgml/entities.ent">
-%entities;
-]>
-
-<article lang="da">
-  <articleinfo>
-    <title>Euro symbolet på
-      <systemitem class="osname">FreeBSD</systemitem></title>
-
-    <authorgroup>
-      <author>
-	<firstname>Aaron</firstname>
-
-	<surname>Kaplan</surname>
-
-	<affiliation>
-	  <address>
-	    <email>aaron@lo-res.org</email>
-	  </address>
-	</affiliation>
-      </author>
-    </authorgroup>
-
-    <copyright>
-      <year>2002</year>
-      <year>2003</year>
-      <holder>The FreeBSD Documentation Project</holder>
-    </copyright>
-
-    <pubdate>$FreeBSD$</pubdate>
-
-    <releaseinfo>$FreeBSD$</releaseinfo>
-
-    <abstract>
-      <para>Dette dokument vil forsøge at hjælpe dig med
-	at komme i gang med det nye <keycap>euro</keycap> symbol
-	på det nye keyboard du var nødt til at
-	købe i starten af 2002 på grund af skiftet til
-	den fælles valuta.  Vi vil først fokusere
-	på de mere vigtige dele, som det at være i stand
-	til at vise symbolet korrekt på konsollen.
-	Senere sektioner vil handle om konfiguration af specifikke
-	programmer som for eksempel <application>X11</application>.
-      </para>
-
-      <para>Megen hjælpende input kom fra Oliver Fromme, Tom Rhodes
-	og utallige andre.  Tak! uden jer ville denne artikel ikke have
-	været mulig!</para>
-
-      &trans.da.jespersen;
-    </abstract>
-  </articleinfo>
-
-  <sect1>
-    <title>Euroen i en nøddeskal</title>
-
-    <para>Hvis du allerede føler dig komfortabel med
-      <ulink url="../../books/handbook/l10n.html">lokalisering</ulink>
-      som det er beskrevet i
-      <systemitem class="osname">FreeBSD</systemitem> Håndbogen,
-      er du måske kun interesseret i de følgende fakta
-      som lader dig komme hurtigt i gang:</para>
-
-    <variablelist>
-      <varlistentry>
-	<term>ISO8859-15</term>
-
-	<listitem>
-	  <para>Dette er en lettere modificering af det almindeligt
-	    brugte ISO8859-1 karatersæt.  Det inkluderer eurosymbolet.
-	    Det bruges til <envar>LANG</envar>, <envar>LC_CTYPE</envar>
-	    miljø variabler.</para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-	<term><filename>iso15-8x16.fnt</filename></term>
-
-	<listitem>
-	  <para>&man.vidcontrol.1; fonten til konsollen</para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-	<term><filename>/usr/share/syscons/keymaps/*.iso.kbd</filename></term>
-
-	<listitem>
-	  <para>Passende tegnsæt afhængigt af dit sprog.
-	    Sæt din <literal>keymap</literal> indtastning i
-	    <filename>rc.conf</filename> til en af disse.</para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-	<term><envar>LC_CTYPE</envar></term>
-
-	<listitem>
-	  <para>Bruges til at specificere den korrekte karakter type
-	    på din lokalitet.</para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-	<term><literal>XkbLayout "<replaceable>lang</replaceable>(euro)"</literal></term>
-
-	<listitem>
-	  <para>XFree86 konfigurations mulighed.</para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-	<term><filename>/usr/X11R6/lib/X11/fonts/*/fonts.alias</filename></term>
-	<listitem>
-	  <para>Vær sikker på at tilpasse dine X11 fonte til
-	    <literal>-*-..-*-iso8859-15</literal></para>
-	</listitem>
-      </varlistentry>
-    </variablelist>
-  </sect1>
-
-  <sect1>
-    <title>En generel bemærkning</title>
-
-    <para>I de følgende sektioner vil vi ofte referere til
-      <emphasis>ISO8859-15</emphasis>. Dette er standard notationen
-      startende med <systemitem class="osname">FreeBSD</systemitem> 4.5.
-      I ældre versioner, var standard notationen enten
-      <emphasis>ISO_8859-15</emphasis> eller
-      <emphasis>DIS_8859-15</emphasis>.
-    </para>
-
-    <para>Hvis du bruger en ældre version af
-      <systemitem class="osname">FreeBSD</systemitem>, skal du være
-      sikker på at kigge på <filename>/usr/share/locale/</filename>
-      for at finde ud af hvilken navnekonvention der bruges.</para>
-  </sect1>
-
-  <sect1>
-    <title>Konsollen</title>
-
-    <sect2>
-      <title>Opsætning af din konsol font</title>
-
-      <para>Afhængigt af din konsols opløsning og
-	størrelse kan du få brug for en af de
-	følgende linier i <filename>rc.conf</filename>:</para>
-
-      <programlisting>font8x16="iso15-8x16.fnt" # from /usr/share/syscons/fonts/*
-font8x14="iso15-8x14.fnt"
-font8x8="iso15-8x8.fnt"</programlisting>
-
-      <para>Dette vil vælge ISO8859-15 også kendt som Latin-9
-	fonten.  ISO8859-15 er en variation af ISO8859-1.  Du kan se
-	forskellen på de to ved at kigge på Euro symbolet:
-	dets decimale værdi er 164.  I ISO8859-1 vil du
-	bemærke en cirkel med fire små
-	streger i hjørnerne.  Dette kaldes ofte "universal currency
-	symbol".  I ISO8859-15, istedet for den lille cirkel, vil du have
-	Euro Symbolet. Ellers er fontene mere eller mindre
-	identiske.</para>
-
-      <warning>
-	<para>I skrivende stund virker det som om den eneste brugbare
-	  font er <literal>iso15-8x16.fnt</literal>. De andre ser ud til
-	  kun at vise ISO8859-1 selvom deres navne tyder på
-	  andet.</para>
-      </warning>
-
-      <note>
-	<para>Ved at specificere denne font vil konsol programmer se
-	  forvrængede ud. Dette er på grund af det faktum
-	  at de antager at du bruger en anden font/karaktersæt
-	  så som ANSI 850.  Et bemærkelsesværdigt
-	  eksempel er <application>/stand/sysinstall</application>.
-	  Det meste af tiden burde det dog ikke være den store
-	  bekymring.</para>
-      </note>
-
-      <para>Som det næste skridt burde du enten reboote dit
-	system for at lade ændringerne tage effekt eller (manuelt)
-	tage de skridt der ville være blevet taget ved systemets
-	start:</para>
-
-      <screen>&prompt.user; <userinput>vidcontrol -f <replaceable>iso15-8x16.fnt</replaceable></userinput></screen>
-
-      <para>For at checke om fonten er blevet valgt kan du eksekvere
-	det følgende korte <command><anchor id="awk-test"/>awk</command>
-	script:</para>
-
-      <programlisting>#!/usr/bin/awk -f
-BEGIN {
-        for(i=160;i&lt;180;i++)
-                printf"%3d %c\n",i,i
-}</programlisting>
-
-      <para>Resultatet skulle afsløre Euro tegnet ved position 164.</para>
-    </sect2>
-
-    <sect2>
-      <title>Opsætning af dit tastatur til Euroen</title>
-
-      <para>De fleste tegnsæt burde allerede være opsat
-	korrekt. f.eks.: Hvis du har et tysk tastatur og dine Umlaut
-	taster virker, kan du sagtens skippe denne sektion eftersom
-	det tegnsæt allerede har opsat hvilkensomhelst
-	tastekombination der er nødvendig (f.eks.: <keycombo
-	action="simul"><keycap>Alt Gr</keycap><keycap>e</keycap></keycombo>)
-	til decimal værdi 164.  Hvis man løber ind i problemer,
-	er den bedste måde at checke på, ved at kigge på
-	<filename>/usr/share/syscons/keymaps/*.kbd</filename>.  Formatet
-	af tegnsættene er beskrevet i &man.keyboard.4;.
-	&man.kbdcontrol.1; kan bruges til at loade et speciallavet
-	tegnsæt.</para>
-
-      <para>Når det korrekte tegnsæt er valgt skal det
-	tilføljes til <filename>/etc/rc.conf</filename> med
-	linien:</para>
-
-      <programlisting>keymap="<replaceable>german.iso</replaceable>" # eller et andet tegnsæt</programlisting>
-
-      <para>Som anført ovenfor er dette skridt nok allerede taget
-	af dig ved installationen (med
-	<application>sysinstall</application>).  Hvis ikke, skal du
-	enten reboote eller loade det nye tegnsæt via
-	&man.kbdcontrol.1;.</para>
-
-      <para>For at verificere tegnsættet, skift til en ny konsol
-	og ved login prompten, <emphasis>istedet for at logge
-	ind</emphasis>, prøv at at taste <keycap>Euro</keycap>
-	tegnet.  Hvis det ikke virker, kan du enten sende en bug report
-	via &man.send-pr.1; eller vær sikker på at du faktisk
-	valgte det rette tegnsæt.</para>
-
-      <note>
-	<para>På dette stadie vil Euro tasten ikke virke i
-	  <application>bash</application> eller
-	  <application>tcsh</application>.</para>
-      </note>
-    </sect2>
-
-    <sect2>
-      <title>Fix miljø variablerne</title>
-
-      <para>Shellsne (bash, tcsh) falder tilbage til &man.readline.3;
-	biblioteket som igen respekterer <envar>LC_CTYPE</envar>
-	miljø variablen.  <envar>LC_CTYPE</envar> skal
-	være sat før din shell kører helt.
-	Helddigvis er det nok at tilføje linien:</para>
-
-      <programlisting>export LC_CTYPE=<replaceable>de_DE</replaceable>.ISO8859-15</programlisting>
-
-      <para>til din <filename>.bash_profile</filename> (bash), eller:</para>
-
-      <programlisting>setenv LC_CTYPE <replaceable>de_DE</replaceable>.ISO8859-15</programlisting>
-
-      <para>til din <filename>.login</filename> (tcsh) fil.
-	<replaceable>de_DE</replaceable> skal selvfølgelig
-	erstattes med dit sprog.  Det næste du skal gøre
-	er at, logge ud, logge ind igen, og verificerer at din Euro
-	tast virker.  Nu burde de fleste af konsol programmerne svare
-	på Euro tasten.  Ekstra konfigurations skridt for
-	specielle programmer som <application>pine</application> er
-	dog måske stadigt nødvendige.</para>
-
-      <note>
-	<para>Et alternativ til at modificere <filename>.login</filename>
-	og <filename>.bash_profile</filename> er at sætte
-	miljø variablerne gennem &man.login.conf.5; mekanismen.
-	Denne indgangsvinkel har den fordel af at sætte visse
-	brugeres login klasser (f.eks.  Franske brugere, Italienske
-	brugere, osv) <emphasis>på et sted</emphasis>.</para>
-      </note>
-    </sect2>
-  </sect1>
-
-  <sect1>
-    <title>Modificering af X11</title>
-
-    <para>Modificer <filename>/etc/XF86Config</filename> på den
-	følgende måde:</para>
-
-    <programlisting>Option "XkbLayout"  "<replaceable>de</replaceable>(euro)"</programlisting>
-
-    <para>Erstat <replaceable>de</replaceable> med dit eget sprog.
-      Nu burde tastaturet være korrekt opsat. Som i konsol
-      sektionen, skal den korrekte font være valgt.  For
-      <application>KDE</application>, gå til <application>KDE
-      control center</application> -&gt; Personalization -&gt; Country
-      &amp; Language -&gt; Charset og skift det til
-      <literal>ISO8859-15</literal>. Lignende skridt tages for
-      <application>kmail</application> og andre programmer.</para>
-
-    <para>En anden god ide er at modificere din
-      <filename>fonts.alias</filename> fil.  Navnlig
-      <literal>fixed</literal> font skulle være skiftet til det
-      korrekte tegnsæt: Forfatterens
-      <filename>/usr/X11R6/lib/X11/fonts/misc/fonts.alias</filename>
-      ser sådan ud:</para>
-
-     <programlisting>! $Xorg: fonts.alias,v 1.3 2000/08/21 16:42:31 coskrey Exp $
-fixed   -misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-iso8859-15
-variable -*-helvetica-bold-r-normal-*-*-120-*-*-*-*-iso8859-15
-(...)</programlisting>
-
-    <para>Som i konsol sektionen, skal specielle programmer stadig
-      have ISO8859-1 fontene konfigureret i deres respektive xrdb
-      databaser.  Et bemærkelsesværdigt eksempel er
-      <application>xterm</application>.  Som en generel tommefingerregel
-      er det nok at ændre den tilsvarende konfigurations fil i
-      <filename>/usr/X11R6/lib/X11/app-defaults</filename> og
-      tilføje den korrekte font.  Lad os demonstrere dette med
-      <application>xterm</application>.</para>
-
-   <screen>&prompt.root; cd /usr/X11R6/lib/X11/app-defaults/
-&prompt.root; vi XTerm</screen>
-
-    <para>Tilføj den følgende linie til begyndelsen
-	af filen:</para>
-
-    <programlisting>*font:     -misc-fixed-medium-r-normal-*-*-120-*-*-c-*-iso8859-15</programlisting>
-
-    <para>Endelig, genstart X og check, at fonte kan vises ved, at
-      køre det ovenstående <link
-      linkend="awk-test">awk script</link>.  Alle større
-      programmer bør respektere tegnsættet og font
-      indstillingen.</para>
-  </sect1>
-
-  <sect1>
-    <title>Åbne problemer</title>
-
-    <para>Forfatteren vil selvfølgelig gerne have feedback.
-      Lad mig meget gerne høre om du har et fix for et af
-      disse åbne problemer:</para>
-
-    <itemizedlist>
-      <listitem>
-        <para>Beskriv en alternativ måde at opsætte XFree86:
-	  <filename role="package">x11/xkeycaps</filename></para>
-      </listitem>
-
-      <listitem>
-        <para>Indstillinger i <application>GNOME</application></para>
-      </listitem>
-
-      <listitem>
-        <para>Indstillinger i <application>XFCE</application></para>
-      </listitem>
-
-      <listitem>
-        <para>Indstillinger for <application>(X)Emacs</application></para>
-      </listitem>
-
-      <listitem>
-        <para>Beskrivelse af UTF-8</para>
-      </listitem>
-
-      <listitem>
-        <para>Beskriv <application>libiconv</application> som en
-	  effektiv måde at konvertere mellem ISO8859-15 og
-	  UTF-{8,16} indefra programmer</para>
-      </listitem>
-    </itemizedlist>
-  </sect1>
-</article>
diff --git a/de_DE.ISO8859-1/articles/Makefile b/de_DE.ISO8859-1/articles/Makefile
index 3f161a2334..34481504f0 100644
--- a/de_DE.ISO8859-1/articles/Makefile
+++ b/de_DE.ISO8859-1/articles/Makefile
@@ -13,7 +13,6 @@ SUBDIR+= laptop
 SUBDIR+= linux-comparison
 SUBDIR+= new-users
 SUBDIR+= solid-state
-SUBDIR+= version-guide
 
 # ROOT_SYMLINKS+= new-users
 
diff --git a/de_DE.ISO8859-1/articles/version-guide/Makefile b/de_DE.ISO8859-1/articles/version-guide/Makefile
deleted file mode 100644
index 39dd218088..0000000000
--- a/de_DE.ISO8859-1/articles/version-guide/Makefile
+++ /dev/null
@@ -1,24 +0,0 @@
-#
-#    The FreeBSD Documentation Project
-#    The FreeBSD German Documentation Project
-#
-#    $FreeBSD$
-#    $FreeBSDde: de-docproj/articles/version-guide/Makefile,v 1.1 2005/08/25 20:14:51 jkois Exp $
-#    basiert auf: 1.3
-#
-# Article: FreeBSD Version Guide
-
-DOC?= article
-
-FORMATS?= html html-split
-WITH_ARTICLE_TOC?= YES
-
-INSTALL_COMPRESSED?=gz
-INSTALL_ONLY_COMPRESSED?=
-
-SRCS=	article.sgml
-
-URL_RELPREFIX?=	../../../..
-DOC_PREFIX?= ${.CURDIR}/../../..
-
-.include "${DOC_PREFIX}/share/mk/doc.project.mk"
diff --git a/de_DE.ISO8859-1/articles/version-guide/article.sgml b/de_DE.ISO8859-1/articles/version-guide/article.sgml
deleted file mode 100644
index 608e6e9bd3..0000000000
--- a/de_DE.ISO8859-1/articles/version-guide/article.sgml
+++ /dev/null
@@ -1,464 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1" standalone="no"?>
-<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V4.2-Based Extension//EN"
-	"../../../share/sgml/freebsd42.dtd" [
-<!ENTITY % entities PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Entity Set//DE" "../../share/sgml/entities.ent">
-%entities;
-]>
-
-<!-- The FreeBSD Documentation Project
-     The FreeBSD German Documentation Project
-
-     $FreeBSD$
-     $FreeBSDde$
-     basiert auf: r38989
--->
-
-<article lang="de">
-  <title>Die für Sie passende FreeBSD-Version bestimmen</title>
-
-  <articleinfo>
-    <authorgroup>
-      <author>
-	<surname>The FreeBSD Documentation Project</surname>
-      </author>
-    </authorgroup>
-
-    <legalnotice id="trademarks" role="trademarks">
-      &tm-attrib.freebsd;
-    </legalnotice>
-
-    <pubdate>$FreeBSD$</pubdate>
-
-    <releaseinfo>$FreeBSD$</releaseinfo>
-
-    <copyright>
-      <year>2005</year>
-      <holder>The FreeBSD Documentation Project</holder>
-<!--      <holder>The FreeBSD German Documentation Project</holder>-->
-    </copyright>
-
-    <abstract>
-      <para>Sie haben sich dafür entschieden, FreeBSD zu
-	installieren.  Dieses Dokument soll Ihnen dabei
-	helfen, sich für eine Version zu entscheiden.</para>
-
-      <para><emphasis>Übersetzt von Johann Kois</emphasis>.</para>
-    </abstract>
-
-  </articleinfo>
-
-  <sect1 id="background">
-    <title>Hintergrundinformationen</title>
-
-    <para>Damit Sie sich für die für Sie am Besten geeignete
-      &os;-Version entscheiden können, müssen Sie einige
-      Konzepte unseres Entwicklungs- und Release Engineering
-      (<literal>RE</literal>)-Prozesses verstehen.</para>
-
-    <para>&os; wird von einer großen Gruppe von fast
-      ausschließlich freiwilligen Mitarbeitern entwickelt.
-      Der Quellcode des Kernels und der Systembibliotheken wird
-      durch ein <firstterm>Versionskontrollsystem</firstterm>
-      verwaltet und kann jederzeit heruntergeladen werden.
-      Zusätzlich werden in regelmäßigen Abständen
-      <literal>binäre Installationspakete</literal> erstellt.
-      Einige dieser Binärversionen durchlaufen einen intensiveren
-      Testprozess und werden danach als <firstterm>Release</firstterm>
-      veröffentlicht.</para>
-
-    <sect2 id="releases">
-      <title>Releases</title>
-
-      <para><literal>Releases</literal> werden durch eine
-	<firstterm>Hauptversionsnummer</firstterm> sowie eine
-	<firstterm>Unterversionsnummer</firstterm> gekennzeichnet.</para>
-
-      <itemizedlist>
-	<listitem>
-	  <para>Das Ziel eines Haupt-Releases ist es, neue Funktionen
-	    einzuführen.  Dafür kann es auch nötig sein,
-	    die Kompatibilität mit Vorgängerversionen
-	    zugunsten der Weiterentwicklung von &os; aufzugeben.
-	    Andererseits werden manchmal Funktionen aus dem System
-	    entfernt, die nicht länger benötigt werden.</para>
-	</listitem>
-
-	<listitem>
-	  <para>Eine Unterversion wird veröffentlicht, um Probleme
-	    zu beheben sowie die Leistung und Stabilität des
-	    Systems zu verbessern.  Dabei hat aber die Erhaltung der
-	    Kompatibilität zwischen den einzelnen Unterversionen
-	    Priorität.  Ist die Einhaltung dieser Vorgaben
-	    gewährleistet, werden gelegentlich auch in
-	    Unterversionen neue Funktionen eingeführt.</para>
-	</listitem>
-      </itemizedlist>
-
-      <para>Beachten Sie aber, dass eine
-	<quote>Release-Version</quote> lediglich den Stand des
-	Quellcodes zu einem bestimmten Zeitpunkt darstellt, dem ein
-	Name (ein sogenanntes <emphasis>Tag</emphasis>) zugewiesen
-	wurde.  So hat das Release Engineering Team dem Release&nbsp;5.4
-	das Tag <literal>RELENG_5_4_0_RELEASE</literal> zugewiesen.  Der
-	aktuelle Entwicklungsstand wird hingegen durch das Tag
-	<literal>HEAD</literal> gekennzeichnet.</para>
-    </sect2>
-
-    <sect2 id="branches">
-      <title>Entwicklungszweige</title>
-
-      <para>Zeitgleich mit der Veröffentlichung einer
-	Release-Version wird ein <firstterm>Zweig</firstterm>
-	(<foreignphrase>branch</foreignphrase>) erzeugt
-	(in unserem Beispiel <literal>RELENG_5_4</literal>).
-	Der Quellcode von <literal>RELENG_5_4_0_RELEASE</literal>
-	bleibt danach unverändert, während sich Dateien
-	des Zweiges <literal>RELENG_5_4</literal> sehr wohl
-	verändern können, wenn Änderungen wie
-	Behebungen von Sicherheitslücken oder anderen
-	Problemen von <literal>HEAD</literal> übernommen
-	werden.</para>
-
-      <para>Während der Lebenszeit einer Hauptversion wird
-	ein weiteres Tag vergeben, beispielsweise
-	<literal>RELENG_5</literal>.  In diesen Zweig können
-	zusätzlich zu den eben genannten Aktualisierungen
-	auch weitere Neuerungen von <literal>HEAD</literal>
-	übernommen werden, um so den Übergang zur
-	nächsten Unterversion vorzubereiten.</para>
-    </sect2>
-
-    <sect2 id="stable-vs-current">
-      <title><firstterm>STABLE</firstterm> versus
-	<firstterm>CURRENT</firstterm></title>
-
-      <para>Während der Lebenszeit einer Hauptversion kann auch
-	ein <literal>STABLE</literal>-Zweig erzeugt werden.  Dadurch
-	wird signalisiert, dass das &os;-Projekt der Ansicht ist, dass
-	dieser Zweig nun so stabil ist, dass er für die meisten
-	Anwender geeignet ist.  Ein Zweig, der vor seiner Eignung
-	für den allgemeinen Einsatz noch weiter getestet werden
-	muss, wird hingegen als <literal>CURRENT</literal>
-	bezeichnet.</para>
-
-      <note><para>Das &os;-Projekt übernimmt keine Garantie
-	dafür, dass die vertriebene Software für alle
-	Einsatzzwecke <emphasis>stabil</emphasis> genug ist.  Diese
-	Entscheidung kann nur der jeweilige Anwender selbst treffen.
-	Bedenken Sie auch, dass das FreeBSD-Projekt sich fast
-	ausschließlich aus Freiwilligen zusammensetzt.  Daher
-	kann auch nicht garantiert werden, dass die Software für
-	Ihre Anforderungen geeignet ist.</para></note>
-    </sect2>
-
-    <sect2 id="ports-vs-packages">
-      <title><firstterm>Ports</firstterm> versus
-	<firstterm>Packages</firstterm></title>
-
-      <para>Neben dem Betriebssystem selbst unterstützt &os;
-	auch Tausende Anwendungen, die unabhängig vom Projekt
-	selbst von Dritten entwickelt werden.  Dazu gehören
-	Window-Systeme, Internetbrowser, E-Mail-Programme,
-	Office-Programme und viele andere mehr.  Das FreeBSD-Projekt
-	stellt dazu in der Regel nur das als
-	<firstterm>Ports-Sammlung</firstterm> bezeichnete Gerüst
-	bereit, damit diese Programme unter &os; installiert werden
-	können.  Ein Programm, dessen Lizenz die Installation
-	aus dem Quellcode erlaubt, wird als <emphasis>Port</emphasis>
-	bezeichnet, ein Programm, das aus einer vorkompilierten
-	Binärdatei installiert wird, hingegen als Paket
-	(<emphasis>package</emphasis>).</para>
-    </sect2>
-  </sect1>
-
-  <sect1 id="past-schedules">
-    <title>Bisherige Release-Zeitpläne</title>
-
-    <para>Während der Entwicklung von &os;&nbsp;5.X traten
-      Probleme auf, deren Tragweite erst im Nachhinein
-      vollkommen klar wurde.  Die Entwicklungsziele für
-      die 5.X-Reihe waren äußerst ambitioniert und sahen
-      unter anderem vor:</para>
-
-    <itemizedlist>
-      <listitem>
-	<para>Die Unterstützung von Mehrprozessor-Systemen
-	  (<foreignphrase>Symmetric MultiProcessing
-	  (SMP)</foreignphrase>).</para>
-      </listitem>
-
-      <listitem>
-	<para>Die Erhöhung der Leistungsfähigkeit durch
-	  die Entwicklung einer neuen Strategie für das
-	  Ressourcenmanagement innerhalb des Kernels.</para>
-      </listitem>
-
-      <listitem>
-	<para>Die zusätzliche Unterstützung von
-	  verschiedenen Prozessor-Architekturen.</para>
-      </listitem>
-
-      <listitem>
-	<para>Die Einführung eines neuen Modells für die
-	  Handhabung von Threads.</para>
-      </listitem>
-
-      <listitem>
-	<para>Die Entwicklung eines neuen Schedulers.</para>
-      </listitem>
-
-      <listitem>
-	<para>Die Unterstützung neuer Technologien wie
-	  Power Management (insbesondere auf Notebooks).</para>
-      </listitem>
-
-      <listitem>
-	<para>All dem übergeordnet war die Festlegung, die
-	  5.X-Serie erst dann für <literal>STABLE</literal>
-	  zu erklären, wenn all diese Aufgaben erledigt
-	  waren.</para>
-      </listitem>
-    </itemizedlist>
-
-    <para>Dies führte dazu, dass zwischen dem Entstehen
-      des <literal>STABLE</literal>-Zweiges von 4.X beziehungsweise
-      5.X mehrere Jahre vergingen.  Dieser Umstand hatte mehrere
-      unerwünschte Auswirkungen:</para>
-
-    <itemizedlist>
-      <listitem>
-	<para>Die große Anzahl der gleichzeitig zu
-	  implementierenden Neuerungen machte es sehr schwierig,
-	  einen Teil davon zu isolieren und in den
-	  <literal>STABLE</literal>-Zweig einzubringen.</para>
-      </listitem>
-
-      <listitem>
-	<para>Anwender, die bestimmte Neuerungen unbedingt
-	  benötigten (etwa die Unterstützung neuester
-	  Hardware), entschieden sich vielfach dafür,
-	  beispielsweise &os;&nbsp;5.2.1 zu installieren, obwohl
-	  es sich dabei um ein <literal>CURRENT</literal>-Release
-	  handelte, das nur für Entwickler und nicht für
-	  den allgemeinen Einsatz vorgesehen war.</para>
-      </listitem>
-
-      <listitem>
-	<para>Um Änderungen aus diesen Versionen wieder in den
-	  aktuellen Entwicklungszweig einzubringen, waren die
-	  Entwickler gezwungen, diese Eigenschaften auf &os;-Versionen
-	  zu unterstützen, die sie nicht als primäre
-	  Entwicklungsplattform nutzten.</para>
-      </listitem>
-
-      <listitem>
-	<para>Die zeitliche Verzögerung bis zum Erscheinen von
-	  &os;&nbsp;5.3, dem ersten <literal>STABLE</literal>-Release,
-	  führte zu umfangreichen Änderungen, was die
-	  Aktualisierung auf die neue Version äußerst
-	  kompliziert machte.</para>
-      </listitem>
-    </itemizedlist>
-
-    <para>Um es auf den Punkt zu bringen:  Niemand war mit dieser
-      Entwicklung zufrieden.</para>
-
-    <para>Aus dieser Problematik wurden daher folgende
-      Rückschlüsse gezogen:</para>
-
-    <itemizedlist>
-      <listitem>
-	<para>Neue Hauptversionen werden künftig nicht mehr so
-	  umfangreiche Änderungen aufweisen.  Dafür werden
-	  solche Versionen häfiger veröffentlicht werden.</para>
-      </listitem>
-
-      <listitem>
-	<para>Soweit möglich, sollen Funktionserweiterungen
-	  künftig voneinander isoliert entwickelt werden.
-	  Dies setzt voraus, dass Teile der Entwicklungsarbeit
-	  außerhalb des Hauptquellcodebaumes erfolgen.
-	  Änderungen werden erst dann in den Hauptentwicklungszweig
-	  eingebracht werden, wenn sichergestellt ist, dass diese die
-	  Stabilität anderer Entwicklungsprojekte nicht
-	  beeinträchtigen.</para>
-      </listitem>
-
-      <listitem>
-	<para>Hauptversionen werden sich künftig an einem Zeitplan
-	  orientieren und nicht mehr an den zu implementierenden
-	  Änderungen.  Wenn bestimmte Eigenschaften zum geplanten
-	  Veröffentlichungszeitpunkt nicht fertig werden, werden
-	  sie vorerst deaktiviert und erst in der nächsten
-	  Hauptversion aktiviert.</para>
-      </listitem>
-    </itemizedlist>
-
-    <para>Durch die häufigere Veröffentlichung von weniger
-      umfangreichen Änderungen erhofft man sich außerdem,
-      dass die Einbringung von neuen Eigenschaften aus
-      <literal>HEAD</literal> in die neue
-      <literal>STABLE</literal>-Version erleichtert wird.  Dadurch
-      können solche Eigenschaften in mehreren Hauptversionen
-      unterstützt werden.  Da es sich dabei in der Regel um
-      isolierte Änderungen handeln wird, verringert sich auch
-      die Wahrscheinlichkeit, dass mit diesen Änderungen neue
-      Probleme eingeführt werden.</para>
-
-    <para>Durch die Fokussierung auf einen Zeitplan statt auf
-      geplante Änderungen wird es für Anwender, Entwickler
-      von externen Programmen sowie &os;-Entwickler einfacher werden,
-      eigene Planungen zu erstellen.</para>
-  </sect1>
-
-  <sect1 id="future-goals">
-    <title>Zukünftige Release-Zeitpläne</title>
-
-    <para>So sehen die derzeitigen Planungen des &os;-Projekts
-      für zukünftige Versionen aus:</para>
-
-    <itemizedlist>
-      <listitem>
-	<para>Alle 18 Monate soll eine neue Hauptversion
-	  veröffentlicht werden.</para>
-      </listitem>
-
-      <listitem>
-	<para>Eine Unterversion soll hingegen alle 4 Monate
-	  veröffentlicht werden.</para>
-      </listitem>
-
-      <listitem>
-	<para>Für das jeweils aktuellste Unterversion-Release
-	  jeder Hauptversion sollen vorkompilierte Pakete angeboten
-	  werden.</para>
-      </listitem>
-
-      <listitem>
-	<para>Sicherheitslücken und andere kritische Probleme
-	  sollen für die aktuellsten Unterversionen jeder
-	  Hauptversion angeboten werden (in sogenannten
-	  <firstterm>security branches</firstterm>).</para>
-      </listitem>
-    </itemizedlist>
-
-    <para>Aufgrund der vielen verschiedenen installierbaren Versionen,
-      ist es allerdings nicht möglich, jede Version zeitlich
-      unbegrenzt zu unterstützen.  Dies liegt zum Teil an nur
-      begrenzt verfügbaren Rechnerkapazitäten, vor allem
-      aber an der ebenfalls nur begrenzt verfügbaren Leistung
-      der freiwilligen Mitarbeiter des &os;-Projekts.</para>
-
-    <para>Interessierte Leser sollten sich auch folgende Seiten
-      ansehen:</para>
-
-    <variablelist>
-      <varlistentry>
-        <term><ulink url="&url.base;/releng/index.html#schedule"></ulink></term>
-        <listitem>
-	  <para>The Release Engineering Schedule</para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-	<term><ulink url="&url.base;/de/security/security.html#supported-branches"></ulink></term>
-	<listitem>
-	  <para>The Security Branch Schedule</para>
-	</listitem>
-      </varlistentry>
-    </variablelist>
-
-    <para>Beide Dokumente gehen näher auf die verschiedenen
-      Entwicklungszweige sowie den Zeitrahmen ein, für den
-      die einzelnen Zweige unterstützt werden.</para>
-  </sect1>
-
-  <sect1 id="decision-points">
-    <title>Wie sollten diese Faktoren meine Entscheidung
-      beeinflussen?</title>
-
-    <para>Die wichtigsten Fragen, die Sie sich vor der Entscheidung
-      für die zu installierende Version stellen sollten, sind:</para>
-
-    <itemizedlist>
-      <listitem>
-	<para>Wie stabil muss Ihre Installation sein?</para>
-      </listitem>
-
-      <listitem>
-	<para>Wie viel Arbeit wollen Sie in den Aktualisierungsprozess
-	  investieren?</para>
-      </listitem>
-
-      <listitem>
-	<para>Wie lange wollen Sie mit einer bestimmten Version
-	  arbeiten, bevor Sie auf eine neuere Version wechseln?</para>
-      </listitem>
-
-      <listitem>
-	<para>Wie sicherheitskritisch ist Ihre Installation?</para>
-      </listitem>
-
-      <listitem>
-	<para>Wollen Sie Ihr System aus dem Quellcode installieren oder
-	  bevorzugen Sie eine Binärinstallation?</para>
-      </listitem>
-
-      <listitem>
-	<para>Sind Sie bereit, sich am &os;-Entwicklungsprozess zu
-	  beteiligen?</para>
-      </listitem>
-    </itemizedlist>
-
-    <para>Es folgen nun einige grobe Richtlinien, die Ihnen bei Ihrer
-      Entscheidung helfen sollen:</para>
-
-    <itemizedlist>
-      <listitem>
-	<para>Wenn Sie an der derzeit stabilsten Version interessiert
-	  sind und möglichst wenig Ressourcen in die
-	  Aktualisierung Ihres Systems investieren wollen, sollten
-	  Sie das aktuellste
-	  <literal>STABLE</literal>-Unterversions-Release
-	  installieren und bei dieser Version verbleiben.  Dabei bleibt
-	  es Ihnen überlassen, ob Sie Änderungen dieses
-	  Zweiges übernehmen wollen oder nicht.</para>
-      </listitem>
-
-      <listitem>
-	<para>Wenn es Ihnen auf auf eine sofortige Verfügbarkeit
-	  ankommt, Sie die neuesten Fähigkeiten oder den
-	  bestmöglichen Sicherheitslevel benötigen und
-	  dazu bereit sind, Zeit in die Aktualisierung Ihres Systems
-	  zu investieren, können Sie dem aktuellen
-	  <literal>STABLE</literal>-Zweig folgen.</para>
-      </listitem>
-
-      <listitem>
-	<para>Wenn Sie Ihr System nicht sofort benötigen und
-	  bereit sind, sich durch einige Probleme zu arbeiten, können
-	  Sie uns dabei helfen, eine neue bevorstehende Hauptversion zu testen,
-	  um für diesen Zweig mittel- bis langfristig die
-	  bestmögliche Stabilität zu erreichen.</para>
-      </listitem>
-
-      <listitem>
-	<para>Nur wenn Sie bereit sind, das System aus dem Quellcode zu
-	  installieren, Zeit haben, Probleme im Basissystem zu suchen
-	  und zu beheben sowie entsprechende Problemberichte zu erstellen
-	  und zusätzlich die entsprechende Mailingliste verfolgen
-	  können, sollten sich dafür entscheiden,
-	  <literal>HEAD</literal> zu folgen.</para>
-      </listitem>
-    </itemizedlist>
-  </sect1>
-
-  <sect1 id="conclusion">
-    <title>Fazit</title>
-
-    <para>Wir hoffen, dass dieser Artikel Ihr Verständnis des
-      &os;-Entwicklungsmodells verbessern und Ihnen Ihnen dabei
-      helfen konnte, sich für die &os;-Version zu entscheiden,
-      die Ihren Anforderungen am Besten entspricht.</para>
-  </sect1>
-</article>
diff --git a/de_DE.ISO8859-1/books/faq/book.sgml b/de_DE.ISO8859-1/books/faq/book.sgml
index ad66f2d0dd..bac5de6098 100644
--- a/de_DE.ISO8859-1/books/faq/book.sgml
+++ b/de_DE.ISO8859-1/books/faq/book.sgml
@@ -1449,19 +1449,6 @@ $FreeBSDde$
       </qandaentry>
 
       <qandaentry>
-        <question id="multiboot">
-          <para>Kann ich mehr als ein Betriebssystem auf meinem PC
-            unterbringen?</para>
-        </question>
-
-        <answer>
-          <para>Sehen Sie sich <ulink
-            url="&url.articles.multi-os.en;/article.html">Die
-            Multi-OS-Seite</ulink> an.</para>
-        </answer>
-      </qandaentry>
-
-      <qandaentry>
         <question id="windows-coexist">
           <para>Kann &windows; neben &os; existieren?</para>
         </question>
@@ -5390,10 +5377,7 @@ kern.sched.name: 4BSD</screen>
             &man.boot0cfg.8; auf beiden Platten booteasy installieren,
             damit Sie in der Lage sind, das alte und das neue System
             abwechselnd zu starten, nachdem der Kopiervorgang
-            abgeschlossen ist.  Im <ulink
-            url="&url.articles.formatting-media.en;/article.html">Formatting-Media
-            Tutorial</ulink> finden Sie weitere Informationen zu
-            diesen Schritten.</para>
+            abgeschlossen ist.</para>
 
 	  <para>Nachdem Sie die neue Platte eingerichtet haben,
 	    können Sie Ihre Daten verschieben.  Dummerweise
diff --git a/de_DE.ISO8859-1/htdocs/docs/books.sgml b/de_DE.ISO8859-1/htdocs/docs/books.sgml
index 64cc0e3889..85ea132435 100644
--- a/de_DE.ISO8859-1/htdocs/docs/books.sgml
+++ b/de_DE.ISO8859-1/htdocs/docs/books.sgml
@@ -101,13 +101,6 @@
 
 <!-- Articles are sorted by pathname -->
 
-    <p><a href="&url.articles;/5-roadmap/index.html">The
-        Roadmap for 5-STABLE</a> (5-roadmap)<br/>
-      Beschreibt die Entwicklungs- und
-        Veröffentlichungspläne hin zum Zweig
-        5-STABLE.  Dieser Artikel ist nur mehr von historischem
-        Interesse.</p>
-
     <p><a href="&url.articles;/bsdl-gpl/index.html">Why you should use
         a BSD style license for your Open Source Project</a> (bsdl-gpl)<br/>
       Beschreibt die Vorteile der Veröffentlichung von
@@ -123,12 +116,6 @@
        Wie FreeBSD einem großen ISP in Lateinamerika helfen
         konnte.</p>
 
-    <p><a href="&url.articles;/checkpoint/index.html">Integration
-        of Checkpoint VPN-1/Firewall-1 and FreeBSD IPsec</a>
-        (checkpoint)<br/>
-      Wie man eine Checkpoint VPN-1/Firewall-1 mit FreeBSD und
-        IPsec konfiguriert.</p>
-
     <p><a href="&url.articles;/committers-guide/index.html">The
         Committer's Guide</a> (committers-guide)<br/>
       Eine Einführung für neue FreeBSD Committer.</p>
@@ -178,22 +165,6 @@
         Advanced Points</a> (cvsup-advanced)<br/>
       Ein Artikel, der die Feinheiten von CVSup beschreibt.</p>
 
-    <p><a href="&url.articles;/dialup-firewall/index.html">Dialup
-        firewalling with FreeBSD</a> (dialup-firewall)<br/>
-      Beschreibt das Einrichten einer Firewall auf einem Rechner
-        mit PPP und ipfw, der über eine Einwahlverbindung und
-        eine dynamisch zugewiesene IP-Adresse mit dem Internet
-        verbunden ist.</p>
-
-    <p><a href="&url.articles;/diskless-x/index.html">Creating
-        a diskless X server</a> (diskless-x)<br/>
-      Wie man einen plattenlosen X-Server einrichtet.</p>
-
-    <p><a href="&url.articles;/euro/index.html">The Euro symbol
-        on FreeBSD</a> (euro)<br/>
-      Wie man FreeBSD und diverse Anwendungen dazu bringen kann,
-        das Euro-Symbol anzuzeigen.</p>
-
     <p><a href="&url.articles.de;/explaining-bsd/index.html">
         Hintergrundwissen zu BSD</a> (explaining-bsd)<br/>
       Eine Antwort auf die Frage: "Was ist BSD?"</p>
@@ -215,11 +186,6 @@
       Die Verwaltung von verschiedenen Schriftarten unter FreeBSD
         sowie deren Einbindung in verschiedene Programme.</p>
 
-    <p><a href="&url.articles;/formatting-media/index.html">Formatting
-        media on FreeBSD</a> (formatting-media)<br/>
-      Die Einrichtung von Speichermedien unter FreeBSD, sowie
-        deren Aufteilung in Slices und Partitionen.</p>
-
     <p><a href="&url.articles;/freebsd-questions/index.html">How
         to get the best results from the FreeBSD-questions mailing list</a>
         (freebsd-questions)<br/>
@@ -243,12 +209,6 @@
      Eine Anleitung zur Erstellung von UFS-Partitionen mit aktiviertem
        Journaling auf Desktop-Systemen.</p>
 
-    <p><a href="&url.articles;/hats/index.html">Working with Hats</a>
-        (hats)<br/>
-      Eine Anleitung für Committer, die den Umgang mit
-        "hats" (also Committern, die für bestimmte
-        Bereiche von FreeBSD verantwortlich sind) beschreibt.</p>
-
     <p><a href="&url.articles;/hubs/index.html">Mirroring FreeBSD</a>
         (hubs)
       <br/>Umfassende Informationen zum Spiegeln der FreeBSD
@@ -296,12 +256,6 @@
         (mh)<br/>
       Eine Einführung in das MH-Mailprogramm.</p>
 
-    <p><a href="&url.articles;/multi-os/index.html">Using
-        FreeBSD with other operating systems</a> (multi-os)<br/>
-      Wie Sie FreeBSD gemeinsam mit einem oder mehreren
-        Betriebssystemen auf dem gleichen Rechner betreiben
-        können.</p>
-
     <p><a href="&url.articles;/nanobsd/index.html">NanoBSD</a>
         (nanobsd)<br/>
       Informationen zu den NanoBSD-Werkzeugen, mit deren Hilfe
@@ -402,37 +356,11 @@
       Beschreibt "solid state"-Gerätedateien unter
         FreeBSD.</p>
 
-    <p><a href="&url.articles;/storage-devices/index.html">Storage Devices</a>
-        (storage-devices)<br/>
-      Detaillierte Informationen über Speichermedien,
-        wie ESDI- und SCSI-Platten, Bandlaufwerke und CD-ROM-Laufwerke
-        unter FreeBSD.</p>
-
-    <p><a href="&url.articles.de;/version-guide/index.html">Die für
-        Sie passende FreeBSD-Version bestimmen</a>
-        (version-guide)<br/>
-      Wie Sie sich für die für Sie richtige
-        FreeBSD-Version entscheiden.  Behandelt werden Releases,
-        Entwicklungszweige, die Unterschiede zwischen -CURRENT und
-        -STABLE, sowie der geplante Entwicklungszyklus des
-        Projekts.</p>
-
-    <p><a href="&url.articles;/vinum/index.html">Bootstrapping
-        Vinum: A Foundation for Reliable Servers</a> (vinum)<br/>
-      Eine Einführung in ausfallsichere Server, sowie eine
-        Schritt-für-Schritt-Anleitung zum Bau eines solchen mit
-        Vinum.</p>
-
     <p><a href="&url.articles;/vm-design/index.html">Design
         elements of the FreeBSD VM system</a> (vm-design)<br/>
       Beschreibt das Design des virtuellen Speichersystems von
         FreeBSD.</p>
 
-    <p><a href="&url.articles;/zip-drive/index.html">Zip-drives
-        and FreeBSD</a> (zip-drive)<br/>
-      Wie man ein Iomega-Ziplaufwerk (SCSI, IDE oder parallel)
-        unter FreeBSD formatiert, einhängt und verwendet.</p>
-
     <h2>Informationen auf anderen Internetseiten</h2>
 
     <p>Verschiedene unabhängige Projekte haben ebenfalls sehr
diff --git a/de_DE.ISO8859-1/htdocs/news/2005/news.xml b/de_DE.ISO8859-1/htdocs/news/2005/news.xml
index 25a275f076..f0016b1c0d 100644
--- a/de_DE.ISO8859-1/htdocs/news/2005/news.xml
+++ b/de_DE.ISO8859-1/htdocs/news/2005/news.xml
@@ -440,7 +440,7 @@
 	  <title>Neuer Artikel:  Eine FreeBSD-Version wählen</title>
 
 	  <p>Ein neuer Artikel, <a
-	    href="&enbase;/doc/de_DE.ISO8859-1/articles/version-guide/">
+	    href="http://docs.freebsd.org/doc/9.0-RELEASE/usr/share/doc/freebsd/en_US.ISO8859-1/articles/version-guide/index.html">
 	    Die für Sie passende FreeBSD-Version bestimmen</a>,
 	    erklärt, wie Sie herausfinden können, welche
 	    FreeBSD-Version Ihren Anforderungen am Besten entspricht.
diff --git a/de_DE.ISO8859-1/htdocs/releases/5.1R/early-adopter.html b/de_DE.ISO8859-1/htdocs/releases/5.1R/early-adopter.html
index 6966819434..9c0f00c534 100644
--- a/de_DE.ISO8859-1/htdocs/releases/5.1R/early-adopter.html
+++ b/de_DE.ISO8859-1/htdocs/releases/5.1R/early-adopter.html
@@ -189,7 +189,7 @@
          target="_top">FreeBSD Release Engineering</a>.
         Informationen über den geplanten Entwicklungszweig
         5-STABLE finden Sie auf der <a
-        href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/5-roadmap/index.html"
+        href="http://docs.freebsd.org/doc/5.1-RELEASE/usr/share/doc/en_US.ISO8859-1/articles/5-roadmap/index.html"
          target="_top">``The Roadmap for 5-STABLE''</a>.</p>
       </div>
 
diff --git a/de_DE.ISO8859-1/htdocs/releases/5.2R/early-adopter.html b/de_DE.ISO8859-1/htdocs/releases/5.2R/early-adopter.html
index 6215d978a7..7d5017ba67 100644
--- a/de_DE.ISO8859-1/htdocs/releases/5.2R/early-adopter.html
+++ b/de_DE.ISO8859-1/htdocs/releases/5.2R/early-adopter.html
@@ -153,7 +153,7 @@ target="_top">Release Engineering Web pages</a> und im Artikel <a
 href="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/releng/index.html"
 target="_top">FreeBSD Release Engineering</a>. Informationen über den geplanten
 Entwicklungszweig 5-STABLE finden Sie auf der <a
-href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/5-roadmap/index.html"
+href="http://docs.freebsd.org/doc/5.2-RELEASE/usr/share/doc/en_US.ISO8859-1/articles/5-roadmap/index.html"
 target="_top">``The Roadmap for 5-STABLE''</a>.</p>
 </div>
 
diff --git a/el_GR.ISO8859-7/articles/Makefile b/el_GR.ISO8859-7/articles/Makefile
index e405415ee0..5294ddcbbb 100644
--- a/el_GR.ISO8859-7/articles/Makefile
+++ b/el_GR.ISO8859-7/articles/Makefile
@@ -7,16 +7,13 @@ SUBDIR = bsdl-gpl
 SUBDIR+= compiz-fusion
 SUBDIR+= contributing
 SUBDIR+= cvs-freebsd
-SUBDIR+= dialup-firewall
 SUBDIR+= explaining-bsd
-SUBDIR+= formatting-media
 SUBDIR+= freebsd-questions
 SUBDIR+= gjournal-desktop
 SUBDIR+= greek-language-support
 SUBDIR+= laptop
 SUBDIR+= linux-users
 SUBDIR+= mailing-list-faq
-SUBDIR+= multi-os
 SUBDIR+= nanobsd
 SUBDIR+= new-users
 SUBDIR+= problem-reports
diff --git a/el_GR.ISO8859-7/articles/dialup-firewall/Makefile b/el_GR.ISO8859-7/articles/dialup-firewall/Makefile
deleted file mode 100644
index 7437b45400..0000000000
--- a/el_GR.ISO8859-7/articles/dialup-firewall/Makefile
+++ /dev/null
@@ -1,16 +0,0 @@
-# $FreeBSD$
-#
-# %SOURCE%	en_US.ISO8859-1/articles/dialup-firewall/Makefile
-# %SRCID%	1.5
-
-DOC?= article
-
-FORMATS?= html
-
-INSTALL_COMPRESSED?=gz
-INSTALL_ONLY_COMPRESSED?=
-
-SRCS= article.sgml
-
-DOC_PREFIX?= ${.CURDIR}/../../..
-.include "${DOC_PREFIX}/share/mk/doc.project.mk"
diff --git a/el_GR.ISO8859-7/articles/dialup-firewall/article.sgml b/el_GR.ISO8859-7/articles/dialup-firewall/article.sgml
deleted file mode 100644
index fbc7135377..0000000000
--- a/el_GR.ISO8859-7/articles/dialup-firewall/article.sgml
+++ /dev/null
@@ -1,357 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-7" standalone="no"?>
-<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V4.2-Based Extension//EN"
-	"../../../share/sgml/freebsd42.dtd" [
-<!ENTITY % entities PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Entity Set//EL" "../../share/sgml/entities.ent">
-%entities;
-]>
-
-<!--
-
-  The FreeBSD Greek Documentation Project
-
-  %SOURCE%	en_US.ISO8859-1/articles/dialup-firewall/article.sgml
-  %SRCID%	1.43
-
--->
-
-<article lang="el">
-  <articleinfo>
-    <title>Óýíäåóç ÌÝóù Ôçëåöþíïõ êáé Ôåß÷ïò Ðñïóôáóßáò óôï FreeBSD</title>
-
-    <authorgroup>
-      <author>
-        <firstname>Marc</firstname>
-        <surname>Silver</surname>
-
-        <affiliation>
-          <address><email>marcs@draenor.org</email></address>
-        </affiliation>
-      </author>
-    </authorgroup>
-
-    <legalnotice id="trademarks" role="trademarks">
-      &tm-attrib.freebsd;
-      &tm-attrib.general;
-    </legalnotice>
-
-    <pubdate>$FreeBSD$</pubdate>
-
-    <releaseinfo>$FreeBSD$</releaseinfo>
-
-    <abstract>
-      <para>Áõôü ôï Üñèñï ðåñéãñÜöåé ðùò ìðïñåßôå íá ñõèìßóåôå Ýíá ôåß÷ïò ðñïóôáóßáò (firewall)
-        ÷ñçóéìïðïéþíôáò ìéá PPP óýíäåóç ìÝóù ôçëåöþíïõ óôï FreeBSD ìå ôï IPFW.
-        Ðéï óõãêåêñéìÝíá, ðåñéãñÜöåé ôç ñýèìéóç åíüò ôåß÷ïõò ðñïóôáóßáò óå ìéá óýíäåóç ìÝóù ôçëåöþíïõ ðïõ
-        Ý÷åé äõíáìéêÞ IP äéåýèõíóç.  Áõôü ôï êåßìåíï äåí áó÷ïëåßôáé ìå ôï ðùò
-        èá ñõèìßóåôå ôçí áñ÷éêÞ óáò óýíäåóç ìÝóù PPP.  Ãéá ðåñéóóüôåñåò
-	ðëçñïöïñßåò ó÷åôéêÜ ìå ôéò ñõèìßóåéò ìéáò óýíäåóçò ìÝóù PPP äåßôå ôç
-	óåëßäá âïÞèåéáò &man.ppp.8;.</para>
-    </abstract>
-  </articleinfo>
-
-  <sect1 id="preface">
-    <title>Ðñüëïãïò</title>
-
-     <para>Áõôü ôï êåßìåíï ðåñéãñÜöåé ôçí äéáäéêáóßá ðïõ ÷ñåéÜæåôáé ãéá íá
-       ñõèìßóåôå Ýíá ôåß÷ïò ðñïóôáóßáò óôï FreeBSD üôáí ç IP äéåýèõíóç äßíåôáé äõíáìéêÜ
-       áðü ôïí ISP óáò.  Ðáñüëï ðïõ Ý÷ù ðñïóðáèÞóåé íá êÜíù áõôü ôï êåßìåíï
-       üóï ôï äõíáôüí ðéï ðëÞñåò êáé óùóôü, åßóôå åõðñüóäåêôïé íá óôåßëåôå ôéò
-       äéïñèþóåéò, ôá ó÷üëéá Þ ôéò ðñïôÜóåéò óáò óôç äéåýèõíóç ôïõ óõããñáöÝá:
-       <email>marcs@draenor.org</email>.</para>
-   </sect1>
-
-  <sect1 id="kernel">
-    <title>ÐáñÜìåôñïé ôïõ ðõñÞíá</title>
-
-    <para>Ãéá íá ìðïñÝóåôå íá ÷ñçóéìïðïéÞóåôå ôï IPFW, ðñÝðåé íá åíóùìáôþóåôå
-      ôçí ó÷åôéêÞ õðïóôÞñéîç óôïí ðõñÞíá óáò.  Ãéá ðåñéóóüôåñåò ðëçñïöïñßåò
-      ó÷åôéêÜ ìå ôç ìåôáãëþôôéóç ôïõ ðõñÞíá, äåßôå ôï <ulink
-        url="&url.books.handbook;/kernelconfig.html">ôìÞìá
-      ñõèìßóåùí ôïõ ðõñÞíá óôï Åã÷åéñßäéï</ulink>.  Èá ðñÝðåé íá ðñïóèÝóåôå
-      ôéò ðáñáêÜôù åðéëïãÝò óôéò ñõèìßóåéò ôïõ ðõñÞíá óáò ãéá íá
-      åíåñãïðïéÞóåôå ôçí õðïóôÞñéîç ãéá ôï IPFW:</para>
-
-    <variablelist>
-      <varlistentry>
-        <term><literal>options IPFIREWALL</literal></term>
-
-        <listitem>
-          <para>Åíåñãïðïéåß ôïí êþäéêá ôåß÷ïõò ðñïóôáóßáò ôïõ ðõñÞíá.</para>
-	  <note>
-	    <para>Áõôü ôï êåßìåíï èåùñåß üôé Ý÷åôå åãêáôáóôÞóåé ôçí Ýêäïóç 5.X
-	    ôïõ FreeBSD Þ ìéá ðéï ðñüóöáôç.  Áí ÷ñçóéìïðïéåßôå ôçí Ýêäïóç 4.X,
-	    ôüôå èá ðñÝðåé íá åíåñãïðïéÞóåôå ôçí åðéëïãÞ
-	    <emphasis>IPFW2</emphasis> êáé íá äéáâÜóåôå ôç óåëßäá âïÞèåéáò
-	    &man.ipfw.8; ãéá ðåñéóóüôåñåò ðëçñïöïñßåò ó÷åôéêÜ ìå ôçí åðéëïãÞ
-	    IPFW2.  ÐñïóÝîôå éäéáßôåñá ôï
-	    ôìÞìá <emphasis>USING IPFW2 IN FreeBSD-STABLE</emphasis>.</para>
-	  </note>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><literal>options IPFIREWALL_VERBOSE</literal></term>
-
-        <listitem>
-          <para>ÓôÝëíåé ôá ìçíýìáôá ãéá ôá êáôÜëëçëá ðáêÝôá óôï log ôïõ
-            óõóôÞìáôïò.</para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><literal>options
-            IPFIREWALL_VERBOSE_LIMIT=<replaceable>500</replaceable></literal></term>
-
-        <listitem>
-          <para>ÂÜæåé êÜðïéï üñéï óôéò öïñÝò ðïõ êÜðïéá åããñáöÞ èá
-            êáôáãñÜöåôáé.  ¸ôóé ìðïñåßôå íá êáôáãñÜöåôå ôá ìçíýìáôá áðü ôï
-	    ôåß÷ïò ðñïóôáóßáò ÷ùñßò ôïí êßíäõíï íá ãåìßóïõí ôá áñ÷åßá
-	    êáôáãñáöÞò ôïõ óõóôÞìáôüò óáò áí äå÷ôåßôå êÜðïéá åðßèåóç.
-	    Ôï üñéï <replaceable>500</replaceable> ìçíõìÜôùí åßíáé ìéá áñêåôÜ
-	    ëïãéêÞ ôéìÞ, áëëÜ ìðïñåßôå íá ðñïóáñìüóåôå áõôÞ ôçí ôéìÞ áíÜëïãá
-	    ìå ôéò áðáéôÞóåéò ôïõ äéêïý óáò äéêôýïõ.</para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><literal>options IPDIVERT</literal></term>
-
-        <listitem>
-          <para>Åíåñãïðïéåß ôá <emphasis>divert</emphasis> sockets, ðïõ èá
-            äïýìå áñãüôåñá ôé êÜíïõí.</para>
-        </listitem>
-      </varlistentry>
-    </variablelist>
-
-    <warning>
-      <para>Ìüëéò ôåëåéþóåôå ìå ôéò ñõèìßóåéò êáé ôçí ìåôáãëþôôéóç ôïõ ðõñÞíá
-	óáò <emphasis>ìçí êÜíåôå åðáíåêêßíçóç!</emphasis>  Áí êÜíåôå
-	åðáíåêêßíçóç óå áõôü ôï óçìåßï ìðïñåß íá êëåéäùèåßôå áðÝîù áðü ôï
-	óýóôçìÜ óáò.  ÐñÝðåé íá ðåñéìÝíåôå ìÝ÷ñé íá åãêáôáóôáèïýí ïé êáíüíåò
-	ôïõ ôåß÷ïõò ðñïóôáóßáò êáé íá åíçìåñùèïýí üëá ôá ó÷åôéêÜ áñ÷åßá
-	ñõèìßóåùí.</para>
-    </warning>
-  </sect1>
-
-  <sect1 id="rcconf">
-    <title>ÁëëáãÝò óôï <filename>/etc/rc.conf</filename> ãéá íá öïñôþíåôáé
-      ôï ôåß÷ïò ðñïóôáóßáò</title>
-
-    <para>Ãéá íá åíåñãïðïéåßôáé ôï ôåß÷ïò ðñïóôáóßáò êáôÜ ôçí åêêßíçóç ôïõ
-      óõóôÞìáôïò êáé ãéá íá ïñßóåôå ôï áñ÷åßï ìå ôïõò êáíüíåò ôïõ ôåß÷ïõò
-      ðñïóôáóßáò, ðñÝðåé íá åíçìåñþóåôå ôï
-      áñ÷åßï <filename>/etc/rc.conf</filename>.  ÁðëÜ ðñïóèÝóôå ôéò ðáñáêÜôù
-      ãñáììÝò:</para>
-
-    <programlisting>firewall_enable="YES"
-firewall_script="/etc/firewall/fwrules"</programlisting>
-
-    <para>Ãéá ðåñéóóüôåñåò ðëçñïöïñßåò ó÷åôéêÜ ìå ôç óçìáóßáò êáèåìéÜò áðü
-      áõôÝò ôéò ãñáììÝò, ñßîôå ìéá ìáôéÜ óôï
-      <filename>/etc/defaults/rc.conf</filename> êáé äéáâÜóôå ôçí man óåëßäá
-      &man.rc.conf.5;</para>
-  </sect1>
-
-  <sect1>
-    <title>ÅíåñãïðïéÞóôå ôçí ÅíóùìáôùìÝíç ÌåôÜöñáóç Äéåõèýíóåùí ôïõ PPP</title>
-
-    <para>Ãéá íá åðéôñÝøåôå óå Üëëá ìç÷áíÞìáôá ôïõ äéêôýïõ óáò íá óõíäÝïíôáé
-      ìå ôïí Ýîù êüóìï ìÝóù ôïõ FreeBSD, ÷ñçóéìïðïéþíôáò ôï
-      ùò <quote>ðýëç</quote>, èá ðñÝðåé íá åíåñãïðïéÞóåôå ôçí åíóùìáôùìÝíç
-      ìåôÜöñáóç äéåõèýíóåùí ôïõ PPP (NAT).  Ãéá íá ãßíåé áõôü, ðñïóèÝóôå óôï
-      áñ÷åßï <filename>/etc/rc.conf</filename> ôéò ðáñáêÜôù ãñáììÝò:</para>
-
-    <programlisting>ppp_enable="YES"
-ppp_mode="auto"
-ppp_nat="YES"
-ppp_profile="<replaceable>ðñïößë_ôçò_óýíäåóçò</replaceable>"</programlisting>
-
-    <para>Óôç èÝóç ôïõ <literal>ðñïößë_ôçò_óýíäåóçò</literal> ðñÝðåé íá âÜëåôå
-      ôï üíïìá ôçò óýíäåóÞò óáò, üðùò ôï Ý÷åôå áðïèçêåýóåé óôï
-      áñ÷åßï <filename>/etc/ppp/ppp.conf</filename>.</para>
-  </sect1>
-
-  <sect1 id="rules">
-    <title>Ïé êáíüíåò ôïõ firewall</title>
-
-    <para>Ôï ìüíï ðïõ áðïìÝíåé ôþñá åßíáé íá ïñßóïõìå ôïõò êáíüíåò ôïõ
-      firewall.  Ïé êáíüíåò ôïõò ïðïßïõò ðåñéãñÜöïõìå åäþ åßíáé áñêåôÜ êáëïß
-      ãéá ôïõò ðåñéóóüôåñïõò ÷ñÞóôåò ìå dialup óýíäåóç, áëëÜ ïýôå õðï÷ñåùôéêïß
-      åßíáé, ïýôå åßíáé äõíáôüí íá ôáéñéÜæïõí ìå ôéò áíÜãêåò üëùí ôùí ÷ñçóôþí
-      dialup.  Ìðïñïýí, üìùò, íá ÷ñçóéìåýóïõí ùò Ýíá êáëü ðáñÜäåéãìá ñõèìßóåùí
-      ôïõ IPFW êáé åßíáé ó÷åôéêÜ åýêïëï íá ôïõò ðñïóáñìüóåôå óôéò äéêÝò óáò
-      áíÜãêåò.</para>
-
-    <para>Áò áñ÷ßóïõìå üìùò ìå ôéò âáóéêÝò áñ÷Ýò åíüò êëåéóôïý ôåß÷ïõò
-      ðñïóôáóßáò.  ¸íá êëåéóôü ôåß÷ïò ðñïóôáóßáò áðáãïñåýåé êáô' áñ÷Þí êÜèå
-      óýíäåóç.  Ï äéá÷åéñéóôÞò ìðïñåß ýóôåñá íá ðñïóèÝóåé êáíüíåò ãéá íá
-      åðéôñÝøåé ìüíï óõãêåêñéìÝíåò óõíäÝóåéò íá ðåñíÜíå áðü ôï ôåß÷ïò
-      ðñïóôáóßáò.  Ç ðéï óõíçèéóìÝíç óåéñÜ ôùí êáíüíùí óå Ýíá êëåéóôü ôåß÷ïò
-      åßíáé: ðñþôá ïé êáíüíåò ðïõ åðéôñÝðïõí ìåñéêÝò óõíäÝóåéò, êáé ôÝëïò ïé
-      êáíüíåò ðïõ áðáãïñåýïõí ïðïéáäÞðïôå Üëëç óýíäåóç.  Ç ëïãéêÞ ðßóù áðü
-      áõôü åßíáé üôé ðñþôá âÜæåôå ôïõò êáíüíåò ðïõ åðéôñÝðïõí ðñÜãìáôá íá
-      ðåñÜóïõí êáé ýóôåñá üëá ôá Üëëá áðáãïñåýïíôáé áõôüìáôá.</para>
-
-    <para>ÖôéÜîôå, ëïéðüí, Ýíá êáôÜëïãï óôïí ïðïßï èá áðïèçêåýïíôáé ïé êáíüíåò
-      ôïõ ôåß÷ïõò ðñïóôáóßáò.  Óå áõôü ôï Üñèñï ÷ñçóéìïðïéïýìå ùò ðáñÜäåéãìá
-      ôïí êáôÜëïãï <filename
-      class="directory">/etc/firewall</filename>.  ÁëëÜîôå êáôÜëïãï ìÝóá óå
-      áõôüí êáé äçìéïõñãÞóôå ôï áñ÷åßï <filename>fwrules</filename> ðïõ ôï
-      üíïìÜ ôïõ åß÷áìå ãñÜøåé óôï <filename>rc.conf</filename>.  Óçìåéþóôå ðùò
-      ìðïñåßôå íá áëëÜîåôå ôï üíïìá ôïõ áñ÷åßïõ áõôïý óå üôé èÝëåôå.  Áõôüò ï
-      ïäçãüò äßíåé áõôü ôï üíïìá óáí ðáñÜäåéãìá êáé ìüíï.</para>
-
-    <para>Áò äïýìå ôþñá Ýíá ðáñÜäåéãìá ôåß÷ïõò ðñïóôáóßáò ìå áñêåôÜ
-      åðåîçãçìáôéêÜ ó÷üëéá.</para>
-
-    <programlisting># Define the firewall command (as in /etc/rc.firewall) for easy
-# reference.  Helps to make it easier to read.
-fwcmd="/sbin/ipfw"
-
-# Define our outside interface.  With userland-ppp this
-# defaults to tun0.
-oif="tun0"
-
-# Define our inside interface.  This is usually your network
-# card.  Be sure to change this to match your own network
-# interface.
-iif="fxp0"
-
-# Force a flushing of the current rules before we reload.
-$fwcmd -f flush
-
-# Divert all packets through the tunnel interface.
-$fwcmd add divert natd all from any to any via tun0
-
-# Check the state of all packets.
-$fwcmd add check-state
-
-# Stop spoofing on the outside interface.
-$fwcmd add deny ip from any to any in via $oif not verrevpath
-
-# Allow all connections that we initiate, and keep their state,
-# but deny established connections that don't have a dynamic rule.
-$fwcmd add allow ip from me to any out via $oif keep-state
-$fwcmd add deny tcp from any to any established in via $oif
-
-# Allow all connections within our network.
-$fwcmd add allow ip from any to any via $iif
-
-# Allow all local traffic.
-$fwcmd add allow all from any to any via lo0
-$fwcmd add deny all from any to 127.0.0.0/8
-$fwcmd add deny ip from 127.0.0.0/8 to any
-
-# Allow internet users to connect to the port 22 and 80.
-# This example specifically allows connections to the sshd and a
-# webserver.
-$fwcmd add allow tcp from any to me dst-port 22,80 in via $oif setup keep-state
-
-# Allow ICMP packets: remove type 8 if you don't want your host
-# to be pingable.
-$fwcmd add allow icmp from any to any via $oif icmptypes 0,3,8,11,12
-
-# Deny and log all the rest.
-$fwcmd add deny log ip from any to any</programlisting>
-
-    <para>Ôþñá Ý÷åôå Ýíá ïëïêëçñùìÝíï ôåß÷ïò ðñïóôáóßáò, ôï ïðïßï óõíäÝóåéò óôéò
-      èýñåò 22 êáé 80 êáé êáôáãñÜöåé üëåò ôéò Üëëåò óõíäÝóåéò óôï áñ÷åßï êáôáãñáöÞò ôïõ
-      óõóôÞìáôïò.  ÐëÝïí åßóôå Ýôïéìïé ãéá åðáíåêêßíçóç.  Ôï ôåß÷ïò ðñïóôáóßáò èá
-      åíåñãïðïéçèåß áõôüìáôá êáé èá öïñôþóåé ôïõò êáíüíåò ðïõ ðñïóèÝóáôå.  Áí äå ãßíåé áõôü Þ Ý÷åôå
-      ïðïéáäÞðïôå ðñïâëÞìáôá, Þ áí Ý÷åôå êÜðïéåò ðñïôÜóåéò ãéá íá
-      äéïñèùèåß áõôü ôï Üñèñï, åðéêïéíùíÞóôå ìáæß ìïõ ìå email.</para>
-  </sect1>
-
-  <sect1>
-    <title>ÅñùôÞóåéò</title>
-
-    <qandaset>
-      <qandaentry>
-        <question>
-          <para>ÂëÝðù ìçíýìáôá üðùò <errorname>limit 500 reached on entry
-            2800</errorname> êáé ìåôÜ áðü áõôü ôï óýóôçìÜ ìïõ óôáìáôÜåé íá
-            êáôáãñÜöåé ôá ðáêÝôá ðïõ åìðïäßæïíôáé áðü ôï ôåß÷ïò ðñïóôáóßáò.
-            Äïõëåýåé áêüìá ôï firewall ìïõ;</para>
-        </question>
-
-        <answer>
-          <para>Áõôü áðëÜ óçìáßíåé ðùò Ý÷åé ÷ñçóéìïðïéçèåß ôï ìÝãéóôï üñéï
-            êáôáãñáöÞò (logging) ãéá áõôü ôïí êáíüíá.  Ï êáíüíáò ï ßäéïò
-            åîáêïëïõèåß íá äïõëåýåé, áëëÜ äåí èá óôÝëíåé ðéá ìçíýìáôá óôï áñ÷åßï êáôáãñáöÞò
-            ôïõ óõóôÞìáôïò ìÝ÷ñé íá ìçäåíßóåôå ðÜëé ôïõò ìåôñçôÝò.  Ìðïñåßôå
-            íá ìçäåíßóåôå ôïõò ìåôñçôÝò ìå ôçí åíôïëÞ</para>
-
-	  <screen>&prompt.root; <userinput>ipfw resetlog</userinput></screen>
-
-	  <para>ÅíáëëáêôéêÜ, ìðïñåßôå íá áõîÞóåôå ôï üñéï
-            êáôáãñáöÞò óôéò ñõèìßóåéò ôïõ ðõñÞíá óáò ìå ôçí åðéëïãÞ
-            <option>IPFIREWALL_VERBOSE_LIMIT</option> üðùò ðåñéãñÜøáìå
-            ðáñáðÜíù.  Ìðïñåßôå íá áëëÜîåôå áõôü ôï üñéï (÷ùñßò íá
-            ìåôáãëùôôßóåôå ðÜëé ôïí ðõñÞíá óáò êáé íá êÜíåôå reboot)
-            ÷ñçóéìïðïéþíôáò ôçí &man.sysctl.8; ôéìÞ
-            net.inet.ip.fw.verbose_limit.</para>
-        </answer>
-      </qandaentry>
-
-      <qandaentry>
-        <question>
-          <para>ÊÜðïéï ëÜèïò ðñÝðåé íá Ýãéíå.  Áêïëïýèçóá ôéò åíôïëÝò êáôÜ
-          ãñÜììá êáé ôþñá êëåéäþèçêá áðÝîù.</para>
-        </question>
-
-        <answer>
-          <para>Áõôüò ï ïäçãüò õðïèÝôåé üôé ÷ñçóéìïðïéåßôå ôï
-            <emphasis>userland-ppp</emphasis>, ãé áõôü êé ïé êáíüíåò ðïõ
-            äßíïíôáé ÷ñçóéìïðïéïýí ôï <devicename>tun0</devicename> interface,
-            ðïõ áíôéóôïé÷åß óôçí ðñþôç óýíäåóç ðïõ öôéÜ÷íåôáé ìå ôï
-            &man.ppp.8; (áëëéþò ãíùóôü êáé ùò <emphasis>user-ppp</emphasis>).
-            Ç åðüìåíç óýíäåóç èá ÷ñçóéìïðïéïýóå ôï
-            <devicename>tun1</devicename>, ìåôÜ ôï
-            <devicename>tun2</devicename> êáé ðÜåé ëÝãïíôáò.</para>
-
-          <para>Èá ðñÝðåé åðßóçò íá èõìÜóôå üôé ôï &man.pppd.8; ÷ñçóéìïðïéåß
-            ôï interface <devicename>ppp0</devicename>, ïðüôå áí îåêéíÞóåôå ôç
-            óýíäåóÞ óáò ìå ôï &man.pppd.8; èá ðñÝðåé íá áíôéêáôáóôÞóåôå ôï
-            <devicename>tun0</devicename> ìå <devicename>ppp0</devicename>.
-            ÐáñáêÜôù èá äåßîïõìå Ýíá åýêïëï ôñüðï íá áëëÜîåôå ôïõò êáíüíåò ôïõ
-            firewall êáôÜëëçëá.  Ïé áñ÷éêïß êáíüíåò óþæïíôáé óå Ýíá áñ÷åßï ìå
-            üíïìá <filename>fwrules_tun0</filename>.</para>
-
-          <screen>          &prompt.user; <userinput>cd /etc/firewall</userinput>
-            /etc/firewall&prompt.user; <userinput>su</userinput>
-            <prompt>Password:</prompt>
-            /etc/firewall&prompt.root; <userinput>mv fwrules fwrules_tun0</userinput>
-            /etc/firewall&prompt.root; <userinput>cat fwrules_tun0 | sed s/tun0/ppp0/g > fwrules</userinput>
-          </screen>
-
-          <para>Ãéá íá êáôáëÜâåôå áí ÷ñçóéìïðïéåßôå ôï &man.ppp.8; Þ ôï
-            &man.pppd.8; ìðïñåßôå íá åîåôÜóåôå ôçí Ýîïäï ôçò &man.ifconfig.8;
-            áöïý åíåñãïðïéçèåß ç óýíäåóÞ óáò.  Ð.÷., ãéá ìéá óýíäåóç ðïõ
-            åíåñãïðïéÞèçêå áðü ôï &man.pppd.8; èá äåßôå êÜôé óáí áõôü
-            (äåß÷íïíôáé ìüíï ïé ó÷åôéêÝò ãñáììÝò):</para>
-
-          <screen>          &prompt.user; <userinput>ifconfig</userinput>
-            <emphasis>(skipped...)</emphasis>
-            ppp0: flags=<replaceable>8051&lt;UP,POINTOPOINT,RUNNING,MULTICAST&gt; mtu 1524</replaceable>
-                    inet <replaceable>xxx.xxx.xxx.xxx</replaceable> --&gt; <replaceable>xxx.xxx.xxx.xxx</replaceable> netmask <replaceable>0xff000000</replaceable>
-            <emphasis>(skipped...)</emphasis>
-            </screen>
-
-          <para>Áðü ôçí Üëëç, ãéá ìéá óýíäåóç ðïõ åíåñãïðïéÞèçêå ìå ôï
-            &man.ppp.8; (<emphasis>user-ppp</emphasis>) èÜ ðñåðå íá äåßôå êÜôé
-            ðáñüìïéï ìå ôï ðáñáêÜôù:</para>
-
-          <screen>          &prompt.user; <userinput>ifconfig</userinput>
-            <emphasis>(skipped...)</emphasis>
-            ppp0: flags=<replaceable>8010&lt;POINTOPOINT,MULTICAST&gt; mtu 1500</replaceable>
-            <emphasis>(skipped...)</emphasis>
-            tun0: flags=<replaceable>8051&lt;UP,POINTOPOINT,RUNNING,MULTICAST&gt; mtu 1524</replaceable>
-                    <emphasis>(IPv6 stuff skipped...)</emphasis>
-                    inet <replaceable>xxx.xxx.xxx.xxx</replaceable> --&gt; <replaceable>xxx.xxx.xxx.xxx</replaceable> netmask <replaceable>0xffffff00</replaceable>
-                    Opened by PID <replaceable>xxxxx</replaceable>
-            <emphasis>(skipped...)</emphasis></screen>
-        </answer>
-      </qandaentry>
-    </qandaset>
-  </sect1>
-</article>
diff --git a/el_GR.ISO8859-7/articles/formatting-media/Makefile b/el_GR.ISO8859-7/articles/formatting-media/Makefile
deleted file mode 100644
index 1ddb11b5a9..0000000000
--- a/el_GR.ISO8859-7/articles/formatting-media/Makefile
+++ /dev/null
@@ -1,16 +0,0 @@
-# $FreeBSD$
-#
-# %SOURCE%	en_US.ISO8859-1/articles/formatting-media/Makefile
-# %SRCID%	1.8
-
-DOC?= article
-
-FORMATS?= html
-
-INSTALL_COMPRESSED?=gz
-INSTALL_ONLY_COMPRESSED?=
-
-SRCS= article.sgml
-
-DOC_PREFIX?= ${.CURDIR}/../../..
-.include "${DOC_PREFIX}/share/mk/doc.project.mk"
diff --git a/el_GR.ISO8859-7/articles/formatting-media/article.sgml b/el_GR.ISO8859-7/articles/formatting-media/article.sgml
deleted file mode 100644
index f3cdf21090..0000000000
--- a/el_GR.ISO8859-7/articles/formatting-media/article.sgml
+++ /dev/null
@@ -1,670 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-7" standalone="no"?>
-<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V4.2-Based Extension//EN"
-	"../../../share/sgml/freebsd42.dtd" [
-<!ENTITY % entities PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Entity Set//EL" "../../share/sgml/entities.ent">
-%entities;
-]>
-
-<!--
-
-  $FreeBSD$
-
-  The FreeBSD Greek Documentation Project
-
-  %SOURCE%	en_US.ISO8859-1/articles/formatting-media/article.sgml
-  %SRCID%	1.31
-
--->
-
-<article lang="el">
-  <articleinfo>
-    <title>Äéáìüñöùóç Áðïèçêåõôéêþí ÌÝóùí ãéá ×ñÞóç ìå ôï FreeBSD</title>
-
-    <subtitle>¸íáò óýíôïìïò ïäçãüò</subtitle>
-
-    <authorgroup>
-      <author>
-        <firstname>Doug</firstname>
-
-        <surname>White</surname>
-
-        <affiliation>
-          <address>
-            <email>dwhite@resnet.uoregon.edu</email>
-          </address>
-        </affiliation>
-      </author>
-    </authorgroup>
-
-    <pubdate>ÌÜñôéïò 1997</pubdate>
-
-    <legalnotice id="trademarks" role="trademarks">
-      &tm-attrib.freebsd;
-      &tm-attrib.iomega;
-      &tm-attrib.opengroup;
-      &tm-attrib.general;
-    </legalnotice>
-
-    <releaseinfo>$FreeBSD$</releaseinfo>
-
-    <abstract>
-      <para>Ôï ðáñüí Ýããñáöï ðåñéãñÜöåé ðþò íá êüøåôå óå ôìÞìáôá (slices),
-        êïììáôéÜóåôå (partition) êáé ìïñöïðïéÞóåôå (format/äéáìüñöùóç)
-        óêëçñïýò äßóêïõò êáé ðáñüìïéá ìÝóá ðïõ ðñïïñßæïíôáé ãéá ÷ñÞóç ìå ôï
-        FreeBSD.  Ôá ðáñáäåßãìáôá äïêéìÜóôçêáí óôï FreeBSD 2.2 áëëÜ ëïãéêÜ
-        äïõëåýïõí êáé óôéò Üëëåò åêäüóåéò.  Ôï êåßìåíï Ý÷åé åíçìåñùèåß ãéá ôçí
-        Ýêäïóç 4 ôïõ FreeBSD.</para>
-    </abstract>
-  </articleinfo>
-
-  <sect1>
-    <title>ÅéóáãùãÞ êáé Ïñéóìïß</title>
-
-    <sect2>
-      <title>ÃåíéêÜ</title>
-
-      <para>Ôï íá ðñïóèÝôåéò äßóêïõò ìå åðéôõ÷ßá óå Ýíá õðÜñ÷ïí óýóôçìá åßíáé
-        ÷áñáêôçñéóôéêü åíüò Ýìðåéñïõ äéá÷åéñéóôÞ óõóôÞìáôïò.  Ôï êüøéìï, ôï
-        êïììÜôéáóìá êáé ç ðñïóèÞêç äßóêùí áðáéôåß éäéáßôåñç ðñïóï÷Þ êáé óùóôÞ
-        óýíôáîç åíôïëþí.  ¸íá ðéèáíü ëÜèïò ìðïñåß íá åîáöáíßóåé Ýíáí ïëüêëçñï
-        äßóêï óå äåõôåñüëåðôá.  Áõôü ôï Ýããñáöï ãñÜöôçêå ùò ðñïóðÜèåéá íá
-        áðëïðïéçèåß ç äéáäéêáóßá êáé íá áðïöåõ÷èïýí áôõ÷Þìáôá.  Åõôõ÷þò,
-        áíáíåþóåéò õðáñ÷üíôùí åñãáëåßùí (êõñßùò ôïõ sysinstall), óôéò
-        ðñüóöáôåò åêäüóåéò ôïõ FreeBSD, Ý÷ïõí âåëôéþóåé ôçí äéáäéêáóßá.</para>
-
-      <para>ÕðÜñ÷ïõí äýï ðéèáíïß ôñüðïé (modes) ìïñöïðïßçóçò:</para>
-
-      <itemizedlist>
-        <listitem>
-          <para><firstterm>óõìâáôÞ ëåéôïõñãßá (compatibility
-            mode)</firstterm>: Äéáìüñöùóç ôïõ äßóêïõ þóôå íá Ý÷åé Ýíá ðßíáêá
-            ôìÞìáôùí (slice table) êáé íá ìðïñåß íá ÷ñçóéìïðïéçèåß ðáñÜëëçëá
-            áðü Üëëá ëåéôïõñãéêÜ óõóôÞìáôá.</para>
-        </listitem>
-
-        <listitem>
-          <para><firstterm>áðïêëåéóôéêÞ ëåéôïõñãßá (dedicated mode)</firstterm>,
-            ìåñéêÝò öïñÝò ëÝãåôáé êáé <firstterm>åðéêßíäõíá áðïêëåéóôéêÞ
-            ëåéôïõñãßá</firstterm>: Äéáìüñöùóç åíüò äßóêïõ ÷ùñßò ðßíáêá
-            partitions.  Áõôü êÜíåé ôçí äéáäéêáóßá ôçò ðñüóèåóçò äßóêïõ
-            åõêïëüôåñç áëëÜ Ýíá ìç-FreeBSD ëåéôïõñãéêü óýóôçìá ðéèáíüí íá ìç
-            ìðïñåß íá äåé ôï äßóêï.  Ç Ýêöñáóç <emphasis>åðéêßíäõíá</emphasis>
-            áíáöÝñåôáé óôïí êßíäõíï ôïõ üôé ôï óýóôçìá ìðïñåß íá ìçí
-            áíáãíùñßóåé Ýíáí äßóêï ìïñöïðïéçìÝíï êáô' áõôüí ôïí ôñüðï.</para>
-        </listitem>
-      </itemizedlist>
-
-      <para>Óôéò ðåñéóóüôåñåò ðåñéðôþóåéò ç áðïêëåéóôéêÞ ëåéôïõñãßá åßíáé ï
-        åõêïëüôåñïò ôñüðïò íá óôçèåß êáé íá ÷ñçóéìïðïéçèåß óå õðÜñ÷ïíôá
-        óõóôÞìáôá, åöüóïí Ýíáò êáéíïýñãéïò äßóêïò óõíÞèùò ðñïïñßæåôáé ìüíï ãéá
-        ôï FreeBSD.  Ðáñüëï ðïõ ç óõìâáôÞ ëåéôïõñãßá äéáóöáëßæåé ìÝãéóôç
-        äéáëåéôïõñãéêüôçôá (interoperability) ìå ìåëëïíôéêÝò åãêáôáóôÜóåéò,
-        åßíáé ðéï ðïëýðëïêç.</para>
-
-      <para>ÐÝñá áðü ôçí åðéëïãÞ ôñüðïõ ëåéôïõñãßáò õðÜñ÷ïõí äýï ìÝèïäïé
-        óôçóßìáôïò ôïõ äßóêïõ.  Ï ðñþôïò ÷ñçóéìïðïéåß ôï åñãáëåßï åãêáôÜóôáóçò
-        ôïõ óõóôÞìáôïò <command>/stand/sysinstall</command>.  Áðü ôï
-        2.1.7-RELEASE êáé ìåôÜ ç <command>sysinstall</command> áðëïðïéåß ôï
-        óôÞóéìï ôùí äßóêùí åðåéäÞ åðéôñÝðåé ôçí áðåõèåßáò áëëáãÞ óôï label
-        (ôßôëïò) êáé óôá ôìÞìáôá (partitions) ôùí äßóêùí.  ÅðéðëÝïí óáò
-        åðéôñÝðåé íá áðïèçêåýóåôå ôéò áëëáãÝò ìüíï óôïí óõãêåêñéìÝíï äßóêï
-        ÷ùñßò íá åðçñåÜæåé ôïõò õðüëïéðïõò.  Ï äåýôåñïò ôñüðïò åßíáé íá
-        åêôåëÝóåôå äéÜöïñåò åíôïëÝò ìå ôï ÷Ýñé áðï ôçí ãñáììÞ åíôïëþí ùò root.
-        Áí åðéëÝîåôå ôçí áðïêëåéóôéêÞ ëåéôïõñãßá ÷ñåéÜæåôå íá åêôåëÝóåôå ìüíï
-        2-3 åíôïëÝò åíþ ìå ôï <command>sysinstall</command> ðñÝðåé äïõëÝøåôå
-        ëéãÜêé ðáñáðÜíù.</para>
-    </sect2>
-
-    <sect2>
-      <title>Ïñéóìïß</title>
-
-      <para>Ç äéá÷åßñéóç äßóêùí óôï &unix; Ý÷åé äþóåé íÝá Ýííïéá óå õðÜñ÷ïõóåò
-        ëÝîåéò.  Ôï ðáñáêÜôù ëåîéëüãéï åîçãåß ôçí ïñïëïãßá ðïõ ÷ñçóéìïðïéïýìå
-        óå áõôü ôï êåßìåíï êáé óôï FreeBSD ãåíéêÜ (ðñïöáíþò).</para>
-
-<!-- I'm tempted to use GLOSSARY here but will resort to a list for now. -->
-
-      <itemizedlist>
-        <listitem>
-          <para>óõìâáôÞ ëåéôïõñãßá (compatibility mode): ç äéáìüñöùóç ôïõ
-            äßóêïõ þóôå íá Ý÷åé Ýíá ðßíáêá ôìÞìáôùí (slice table) êáé íá
-            ìðïñåß íá ÷ñçóéìïðïéçèåß ðáñÜëëçëá ìå Üëëá ëåéôïõñãéêÜ óõóôÞìáôá.
-            Áíôßèåôï ôçò áðïêëåéóôéêÞò ëåéôïõñãßáò.</para>
-        </listitem>
-
-        <listitem>
-          <para>(åðéêßíäõíá) áðïêëåéóôéêÞ ëåéôïõñãßá: ç äéáìüñöùóç ôïõ äßóêïõ
-            êáôÜ ôÝôïéïí ôñüðï þóôå íá ìçí ðåñéÝ÷åé ðßíáêá ôìçìÜôùí (slice
-            table).  Åßíáé ðéï åýêïëç äéáäéêáóßá áëëÜ ï äßóêïò ìðïñåß íá ìç
-            äïõëåýåé óå ìç-FreeBSD ëåéôïõñãéêÜ óõóôÞìáôá.  Áíôßèåôï ôçò
-            óõìâáôÞò ëåéôïõñãßáò.</para>
-        </listitem>
-
-        <listitem>
-          <para>äßóêïò: Ïé óêëçñïß äßóêïé, ôá CDROM, ïé ìáãíçôï-ïðôéêÝò
-	    óõóêåõÝò êáé ôá áöáéñïýìåíá ìÝóá &iomegazip;/&jaz; åßíáé ìåñéêÝò
-	    áðü ôéò óõóêåõÝò ìáæéêÞò áðïèÞêåõóçò äåäïìÝíùí ðïõ
-	    ÷ñçóéìïðïéïýíôáé óÞìåñá.
-	    Ç âáóéêÞ áñ÷Þ ëåéôïõñãßáò áõôþí ôùí ìÝóùí áðïèÞêåõóçò Ýíáò Þ
-	    ðåñéóóüôåñïé äßóêïé ïé ïðïßïé ðåñéóôñÝöïíôáé áðü Ýíá ìïôÝñ, åíþ
-	    ìéá êåöáëÞ êéíåßôáé óå Ýíá ìïíïðÜôé ðÜíù óôçí áêôßíá ôïõ äßóêïõ
-	    êáé äéáâÜæåé áðü ôï äßóêï Þ ãñÜöåé äåäïìÝíá óå áõôüí.
-	    Ôï ãñÜøéìï ãßíåôáé ìå ìåôáâïëÞ êÜðïéïõ öõóéêïý ÷áñáêôçñéóôéêïý ôïõ
-	    äßóêïõ (ìáãíçôéêÞ ñïÞ, áíáêëáóôéêüôçôá, êëð.) åíþ ôï äéÜâáóìá
-	    ãßíåôáé ìå <quote>áíß÷íåõóç</quote> áëëáãþí óôçí ßäéá öõóéêÞ
-	    éäéüôçôá ôïõ äßóêïõ.</para>
-        </listitem>
-
-        <listitem>
-          <para>ôìÞìá (slice): Ìßá õðïäéáßñåóç åíüò äßóêïõ.  Óýìöùíá ìå ôá
-            ðñüôõðá ôùí PC ìðïñïýí íá õðÜñ÷ïõí ìÝ÷ñé 4 ôìÞìáôá óå Ýíáí äßóêï.
-            Ôá ôìÞìáôá áðïôåëïýíôáé áðï óõíå÷üìåíïõò ôïìåßò (sectors).
-            ÕðÜñ÷åé Ýíáò <quote>ðßíáêáò ôìçìÜôùí</quote> (slice table) ðïõ
-            ðåñéÝ÷åé ðëçñïöïñßåò ãéá ôá ôìÞìáôá êáé ÷ñçóéìïðïéåßôáé áðü ôï
-            BIOS ãéá íá âñåß áðü ðïý ìðïñåß íá îåêéíÞóåé ôï óýóôçìá.  Ï
-            ðßíáêáò ôìçìÜôùí ëÝãåôáé êáé <quote>ðßíáêáò êïììáôéþí</quote>
-            (partition table) óå ïñïëïãßá DOS ðïõ öôéÜ÷íåôáé áðï ôï ðñüãñáììá
-            fdisk.</para>
-        </listitem>
-
-        <listitem>
-          <para>êïììÜôé (partition): Ìßá õðïäéáßñåóç åíüò ôìÞìáôïò.  ÓõíÞèùò
-            ÷ñçóéìïðïéåßôáé ãéá áíáöïñÜ óôéò õðïäéáéñÝóåéò ôùí ôìçìÜôùí
-            (slices) ôïõ äßóêïõ óôï FreeBSD.  ÊÜèå óýóôçìá áñ÷åßùí
-            (filesystem) Þ äåõôåñåýïõóáò ìíÞìçò (swap area) óôïí äßóêï
-            âñßóêåôáé óå Ýíá êïììÜôé.  Ôá êïììÜôéá öôéÜ÷íïíôáé ìå ôï åñãáëåßï
-            disklabel.</para>
-        </listitem>
-
-        <listitem>
-          <para>ôïìÝáò (sector): Ç ìéêñüôåñç õðïäéáßñåóç åíüò äßóêïõ.  ÓõíÞèùò
-            Ý÷åé ìÝãåèïò 512 bytes.</para>
-        </listitem>
-      </itemizedlist>
-    </sect2>
-
-    <sect2>
-      <title>Óçìåßá ðïõ ðñÝðåé íá ðñïóÝîåôå êáé ðáãßäåò</title>
-
-      <para>Äþóôå ìåãÜëç ðñïóï÷Þ óôç äéáäéêáóßá, áí äåí ëÜâåôå ôá ìÝôñá óáò
-        êáé ãßíåé ëÜèïò ìðïñåß íá êáôáóôñÝøåôå ôá ðåñéå÷üìåíá Üëëùí äßóêùí ôïõ
-        óõóôÞìáôïò.</para>
-
-      <para><emphasis>ÐñïóÝîôå ôé êÜíåôå.</emphasis> Åßíáé ðïëý åýêïëï íá
-        êáôáóôñÝøåôå ëÜèïò äßóêï äïõëåýïíôáò ìå áõôÝò ôéò åíôïëÝò.  Áí Ý÷åôå
-        áìöéâïëßåò åëÝãîôå ôá ìçíýìáôá ôïõ ðõñÞíá êáôÜ ôç äéáäéêáóßá åêêßíçóçò
-        ãéá íá âñåßôå ôç óùóôÞ óõóêåõÞ äßóêïõ.</para>
-
-      <para>ÖõóéêÜ äåí Ý÷ïõìå êáìßá åõèýíç ãéá æçìéÝò ðïõ ìðïñåß íá
-        ðñïêëçèïýí.  Ç åõèýíç åßíáé äéêÞ óáò!</para>
-    </sect2>
-
-    <sect2>
-      <title>Zip, Jazz, êáé Üëëá áöáéñïýìåíá ìÝóá</title>
-
-      <para>Ïé áöáéñïýìåíïé äßóêïé ìðïñïýí íá äéáìïñöùèïýí óáí êáíïíéêïß
-        äßóêïé.  Ôï óçìáíôéêü åßíáé íá åßíáé óõíäåìÝíïò ï ïäçãüò ôïõ äßóêïõ
-        êáôÜ ôçí åêêßíçóç ôïõ óõóôÞìáôïò êáé ìå äéóêÝôá ìÝóá þóôå íá ìðïñÝóåé
-        ï ðõñÞíáò íá äåß óùóôÜ ôçí ãåùìåôñßá ôïõ äßóêïõ.  ÊïéôÜîôå ôé ëÝåé ç
-        åíôïëÞ <command>dmesg</command> ãéá íá äåßôå áí ç óõóêåõÞ åßíáé óôçí
-        ëßóôá.  Ãéá ðáñÜäåéãìá áí ï ðõñÞíáò ãñÜøåé:
-
-        <informalexample>
-          <screen>Can't get the size</screen>
-        </informalexample>
-
-        ôüôå äåí õðÜñ÷åé äéóêÝôá óôïí ïäçãü.  Áí ãßíåé áõôü èá ðñÝðåé íá
-        åðáíåêêéíÞóåôå ôï ìç÷Üíçìá ðñéí äïêéìÜóåôå íá äéáìïñöþóåôå ôçí
-        äéóêÝôá.</para>
-    </sect2>
-  </sect1>
-
-  <sect1>
-    <title>Äéáìïñöþíïíôáò äßóêïõò ãéá áðïêëåéóôéêÞ ëåéôïõñãßá</title>
-
-    <sect2>
-      <title>ÅéóáãùãÞ</title>
-
-      <para>ÁõôÞ ç ðáñÜãñáöïò ðåñéãñÜöåé ðþò íá öôéÜîåôå äßóêïõò ìüíï ãéá ôï
-        FreeBSD.  Èõìçèåßôå üôé ïé äßóêïé áðïêëåéóôéêÞò ëåéôïõñãßáò äåí ìðïñïýí
-        íá äéáâáóôïýí áðü Üëëá ëåéôïõñãéêÜ, ïýôå íá êÜíïõí boot.</para>
-
-    </sect2>
-
-    <sect2>
-      <title>Ðþò íá öôéÜîåôå äßóêïõò áðïêëåéóôéêÞò ëåéôïõñãßáò ìå ôï
-        Sysinstall</title>
-
-      <para>To <command>/stand/sysinstall</command>, ôï ðñüãñáììá åãêáôÜóôáóçò
-        ôïõ óõóôÞìáôïò, Ý÷åé åðåêôáèåß óôéò ôåëåõôáßåò ôïõ åêäüóåéò þóôå íá
-        áðëïðïéåß ôçí äéáäéêáóßá ÷ùñéóìïý ôùí äßóêùí êáé íá áðáéôåß ëéãüôåñç
-        ðñïóðÜèåéá.  Ôá ðñïãñÜììáôá fdisk êáé disklabel ðïõ õðÜñ÷ïõí óôï
-        sysinstall åßíáé ãñáöéêïý ðåñéâÜëïíôïò (GUI - Graphical User
-        Interface) êáé ìåéþíïõí ôï ìðÝñäåìá ôïõ êïøßìáôïò ôùí äßóêùí.  Åßíáé
-        ðñïöáíþò ï åõêïëüôåñïò ôñüðïò íá êüøåôå äßóêïõò áðü ôçí Ýêäïóç 2.1.7
-        êáé ìåôÜ ôïõ FreeBSD.</para>
-
-      <procedure>
-        <step>
-          <para>ÎåêéíÞóôå ôï sysinstall þò root ãñÜöïíôáò
-
-            <informalexample>
-              <screen>&prompt.root; <userinput>/stand/sysinstall</userinput></screen>
-            </informalexample>
-
-            óôçí ãñáììÞ åíôïëþí.</para>
-        </step>
-
-        <step>
-          <para>ÅðéëÝîôå <command>Index</command>.</para>
-        </step>
-
-        <step>
-          <para>ÅðéëÝîôå <command>Partition</command>.</para>
-        </step>
-
-        <step>
-          <para>ÅðéëÝîôå ôï äßóêï ðïõ èÝëåôå íá åãêáôáóôÞóåôå ÷ñçóéìïðïéþíôáò
-            ôá âåëÜêéá êáé ìåôÜ <keycap>SPACE</keycap>.</para>
-        </step>
-
-        <step>
-          <para>Áí èá ÷ñçóéìïðïéÞóåôå üëï ôï äßóêï ãéá ôï FreeBSD, åðéëÝîôå
-            <command>A</command>.</para>
-        </step>
-
-        <step>
-          <para>Ìüëéò óáò ñùôÞóåé áí üíôùò èÝëåôå íá ôï êÜíåôå áõôü (Do you
-            still want to do this) áðáíôÞóôå <command>Yes</command>.</para>
-        </step>
-
-        <step>
-          <para>ÅðéëÝîôå <command>Write</command>.</para>
-        </step>
-
-        <step>
-          <para>Èá óáò âãÜëåé ìéá ðñïåéäïðïßçóç ó÷åôéêÜ ìå ôçí åããñáöÞ óå
-            õðÜñ÷ïíôá óõóôÞìáôá áðáíôÞóôå <command>Yes</command>.</para>
-        </step>
-
-	<step>
-	  <para>Ìüëéò óáò ñùôÞóåé áí èÝëåôå íá åãêáôáóôÞóåôå Ýíá boot loader,
-	    åðéëÝîôå <command>None</command> ãéá íá áðïöýãåôå ïðïéáäÞðïôå
-	    áëëáãÞ óôï Master Boot Record.  Ç åãêáôÜóôáóç åíüò boot loader
-	    ÷ñåéÜæåôáé ìüíï óå êáéíïýñéåò åãêáôáóôÜóåéò ôïõ &os; Þ áí
-	    ó÷åäéÜæåôå íá ôïðïèåôÞóåôå ôï äßóêï óå êÜðïéï Üëëï
-	    ìç÷Üíçìá.</para>
-	</step>
-
-        <step>
-          <para>ÐáôÞóôå <keycap>ENTER</keycap> óôï åíçìåñùôéêü ìÞíõìá ðïõ
-	    ëÝåé <quote>Wrote FDISK partition information out
-	    successfully</quote>.</para>
-	</step>
-
-        <step>
-          <para>ÅðéëÝîôå <command>Quit</command> ãéá íá âãåßôå áðü ôï FDISK
-            Editor êáé ìåôÜ <keycap>ESCAPE</keycap> ãéá íá åðéóôñÝøåôå óôï
-            Index menu.</para>
-        </step>
-
-        <step>
-          <para>ÅðéëÝîôå <command>Label</command> áðü ôï Index menu.</para>
-        </step>
-
-        <step>
-          <para>ÏíïìÜóôå ôï äßóêï óáò üðùò èÝëåôå (åäþ ïñßæåôå ôá
-            partitions).  Áí èÝëåôå ìüíï Ýíá partition ðáôÞóôå ôï
-            <command>C</command> ãéá íá äçìéïõñãÞóåôå ôï partition.  ÌåôÜ
-            áðëþò äå÷èåßôå ôéò ðñïåðéëïãÝò ãéá ôá ðñïêáèïñéóìÝíá size,
-            partition type Filesystem, êáé mountpoint (ôï ïðïßï äåí
-            ÷ñçóéìïðïéåßôáé).</para>
-        </step>
-
-        <step>
-          <para>ÐáôÞóôå <command>W</command> ìüëéò ôåëåéþóåôå êáé åðéêõñþóôå
-            ôéò áëëáãÝò ãéá íá óõíå÷ßóåôå.  Ôï filesystem èá ðåñáóôåß áõôüìáôá
-            áðü ôçí åíôïëÞ newfs åêôüò áí åðéëÝîåôå ôï áíôßèåôï.  (Áí âÜæåôå
-            êáéíïýñãéï partition óáò óõìöÝñåé íá ôï êÜíåôå!).  Èá óáò äþóåé ôï
-            ëÜèïò:
-
-            <informalexample>
-              <screen>Error mounting /mnt/dev/ad2s1e on /mnt/blah : No such file or directory</screen>
-            </informalexample>
-
-            ÁãíïÞóôå ôï.</para>
-        </step>
-
-        <step>
-          <para>ÐáôÞóôå óõíå÷üìåíá ôï <keycap>ESCAPE</keycap> ãéá íá
-            âãåßôå.</para>
-        </step>
-      </procedure>
-    </sect2>
-
-    <sect2>
-      <title>Ðùò íá öôéÜîåôå äßóêïõò áðïêëåéóôéêÞò ëåéôïõñãßáò ìÝóá áðü ôçí
-        ãñáììÞ åíôïëþí</title>
-
-      <para>ÅêôåëÝóôå ôéò ðáñáêÜôù åíôïëÝò áíôéêáèéóôþíôáò ôï
-        <devicename>ad2</devicename> ìå ôï üíïìá ôçò óõóêåõÞò ôïõ äßóêïõ
-        (ãñÜøôå dmesg íá åëÝãîåôå áí åßíáé óùóôü).</para>
-
-      <informalexample>
-        <screen>&prompt.root; <userinput>dd if=/dev/zero of=/dev/ad2 count=2</userinput>
-&prompt.root; <userinput>disklabel /dev/ad2 | disklabel -B -R -r ad2 /dev/stdin</userinput>
-<lineannotation>ÈÝëïõìå ìüíï Ýíá partition, ïðüôå ìðïñïýìå íá ÷ñçóéìïðïéÞóïõìå ôï êïììÜôé 'c':</lineannotation>
-&prompt.root; <userinput>newfs /dev/ad2c</userinput></screen>
-      </informalexample>
-
-      <para>Áí ÷ñåéÜæåôáé íá áëëÜîåôå ôï disklabel ãéá íá ÷ñçóéìïðïéÞóåôå
-        ðïëëáðëÜ partitions (ãéá ðáñÜäåéãìá áí èÝëåôå swap) ôüôå êÜíôå:</para>
-
-      <informalexample>
-        <screen>&prompt.root; <userinput>dd if=/dev/zero of=/dev/ad2 count=2</userinput>
-&prompt.root; <userinput>disklabel /dev/ad2 > /tmp/label</userinput>
-<lineannotation>Áíïßîôå ôï disklabel ãéá íá ðñïóèÝóåôå partitions:</lineannotation>
-&prompt.root; <userinput>vi /tmp/label</userinput>
-&prompt.root; <userinput>disklabel -B -R -r ad2 /tmp/label</userinput>
-<lineannotation>åêôåëÝóôå ôçí åíôïëÞ newfs óôá partitions üðùò ðñÝðåé</lineannotation></screen>
-      </informalexample>
-
-      <para>Ï äßóêïò óáò åßíáé Ýôïéìïò ðñïò ÷ñÞóç.</para>
-    </sect2>
-  </sect1>
-
-  <sect1>
-    <title>Äéáìïñöþíïíôáò äßóêïõò ãéá óõìâáôÞ ëåéôïõñãßá</title>
-
-    <sect2>
-      <title>ÅéóáãùãÞ</title>
-      <para>Ç ãñáììÞ åíôïëþí åßíáé ìåí ï åõêïëüôåñïò ôñüðïò ãéá íá öôéÜîåôå
-        äßóêïõò áðïêëåéóôéêÞò ëåéôïõñãßáò áëëÜ åßíáé êáé ï äõóêïëüôåñïò ãéá íá
-        öôéÜîåôå óõìâáôïýò äßóêïõò. Ôï <command>fdisk</command> áðü ôçí ãñáììÞ
-        åíôïëþí èÝëåé ðåñéóóüôåñåò ãíþóåéò ìáèçìáôéêþí êáé ðïëëÝò ãíþóåéò
-        ó÷åôéêÜ ìå ôïí ðßíáêá êïììáôéþí, êÜôé ðïõ ðñïöáíþò äåí ÷ñåéÜæåôáé íá
-        ìÜèåôå. Ãé áõôü ÷ñçóéìïðïéÞóôå ôï sysinstall ãéá íá öôéÜîåôå óõìâáôïýò
-        äßóêïõò áêïëïõèþíôáò ôéò ïäçãßåò ðáñáêÜôù.</para>
-    </sect2>
-
-    <sect2>
-      <title>Ðþò íá öôéÜîåôå äßóêïõò óõìâáôÞò ëåéôïõñãßáò ìå ôï
-        Sysinstall</title>
-
-      <procedure>
-        <step>
-          <para>ÎåêéíÞóôå ôï sysinstall þò root ãñÜöïíôáò
-
-            <informalexample>
-              <screen>&prompt.root; <userinput>/stand/sysinstall</userinput></screen>
-            </informalexample>
-
-            óôçí ãñáììÞ åíôïëþí.</para>
-        </step>
-
-        <step>
-          <para>ÅðéëÝîôå <command>Index</command>.</para>
-        </step>
-
-        <step>
-          <para>ÅðéëÝîôå <command>Partition</command>.</para>
-        </step>
-
-        <step>
-          <para>ÅðéëÝîôå ôï äßóêï ðïõ èÝëåôå íá åãêáôáóôÞóåôå ÷ñçóéìïðïéþíôáò
-            ôá âåëÜêéá êáé ìåôÜ <keycap>SPACE</keycap>.</para>
-        </step>
-
-        <step>
-          <para>Áí èá ÷ñçóéìïðïéÞóåôå üëï ôïí äßóêï ãéá ôï FreeBSD,
-            åðéëÝîôå <command>A</command>.</para>
-        </step>
-
-        <step>
-          <para>¼ôáí óáò æçôçèåß:
-
-            <informalexample>
-              <screen>Do you want to do this with a true partition entry so as to remain
-cooperative with any future possible operating systems on the
-drive(s)?</screen>
-            </informalexample>
-
-            (ÈÝëåôå íá ôï êÜíåôå áõôü ìå ðñáãìáôéêÜ êïììÜôéá ãéá íá ðáñáìåßíåé
-            óõìâáôüò ìå Üëëá ëåéôïõñãéêÜ óõóôÞìáôá?)  ÁðáíôÞóôå
-            <command>Yes</command>.</para>
-        </step>
-
-        <step>
-          <para>ÅðéëÝîôå <command>Write</command>.</para>
-        </step>
-
-        <step>
-          <para>¼ôáí óáò æçôçèåß íá åãêáôáóôÞóåôå ôïí boot manager, åðéëÝîôå
-            None ìå ôï <keycap>SPACE</keycap> êáé ìåôÜ <keycap>ENTER</keycap>
-            ãéá OK.</para>
-        </step>
-
-        <step>
-          <para><command>Quit</command> (âãåßôå) áðü ôï FDISK Editor.</para>
-        </step>
-
-        <step>
-          <para>Èá óáò ñùôÞóåé êÜôé ó÷åôéêü ìå ôïí boot manager ðÜëé, åðéëÝîôå
-            <command>None</command> îáíÜ. </para> </step>
-
-        <step>
-          <para>ÅðéëÝîôå <command>Label</command> áðï ôï Index menu.</para>
-        </step>
-
-        <step>
-          <para>ÏíïìÜóôå ôï äßóêï üðùò èÝëåôå (åäþ èá ïñßóåôå ôá
-            partitions). Aí èÝëåôå ìüíï Ýíá partition áðëþò äå÷èåßôå ôéò
-            ðñïåðéëïãÝò ãéá ôá ðñïêáèïñéóìÝíá size, partition type filesystem,
-            êáé mountpoint (ôï ïðïßï äåí ÷ñçóéìïðïéåßôáé).</para>
-        </step>
-
-        <step>
-          <para>Ôï filesystem èá ðåñáóôåß áõôüìáôá áðü ôçí åíôïëÞ newfs åêôüò
-            áí åðéëÝîåôå ôï áíôßèåôï.  Áí âÜæåôå êáéíïýñãéï partition óáò
-            óõìöÝñåé íá ôï êÜíåôå!  Èá óáò äþóåé ôï ëÜèïò:
-
-            <informalexample>
-              <screen>Error mounting /mnt/dev/ad2s1e on /mnt/blah : No such file or directory</screen>
-            </informalexample>
-
-            ÁãíïÞóôå ôï.</para>
-        </step>
-
-        <step>
-          <para>ÐáôÞóôå óõíå÷üìåíá ôï <keycap>ESCAPE</keycap> ãéá íá
-            âãåßôå.</para>
-        </step>
-      </procedure>
-
-      <para>Ï äßóêïò óáò åßíáé Ýôïéìïò ðñïò ÷ñÞóç.</para>
-    </sect2>
-  </sect1>
-
-  <sect1>
-    <title>¶ëëåò ëåéôïõñãßåò ìå ôïõò äßóêïõò</title>
-
-    <sect2>
-      <title>ÐñïóèÝôïíôáò swap.</title>
-
-      <para>Êáèþò Ýíá óýóôçìá åðåêôåßíåôáé, ç áíÜãêç ãéá ìåãáëýôåñï swap
-        ãßíåôáé üëï êáé ðéï åðéôáêôéêÞ. Ðáñüëï ðïõ ôï íá ðñïóôåèåß swap óå Ýíáí
-        õðÜñ÷ïíôá äßóêï åßíáé ôñïìåñÜ äýóêïëï, Ýíáò êáéíïýñãéïò äßóêïò ìðïñåß
-        íá ìïñöïðïéçèåß Ýôóé þóôå íá ðåñéÝ÷åé ôï åðéðëÝïí swap ðïõ óáò
-        ëåßðåé.</para>
-
-      <para>Ãéá íá ðñïóèÝóåôå swap êáèþò âÜæåôå Ýíá äßóêï óôï óýóôçìá:</para>
-
-      <procedure>
-        <step>
-          <para>Êáèþò êüâåôå ôï äßóêï (partitioning) áëëÜîôå ôï disklabel êáé
-            ïñßóôå ÷þñï ãéá swap óôï êïììÜôé (partition) `b' êáé âÜëôå ôïí
-            õðüëïéðï ÷þñï óå êÜðïéï Üëëï êïììÜôé, ð.÷. óôï `a' Þ óôï `e'.  Ôï
-            ìÝãåèïò ðïõ äßíåôå åßíáé óå blocks ôùí 512 bytes.</para>
-        </step>
-
-        <step>
-          <para>¼ôáí êÜíåôå newfs óôïí äßóêï, ÌÇÍ ôï êÜíåôå óôï êïììÜôé `c'.
-            Áíôßèåôá, êÜíôå ôï ìüíï óôï êïììÜôé ðïõ äåí åßíáé swap.</para>
-        </step>
-
-        <step>
-          <para>ÐñïóèÝóôå óôï <filename>/etc/fstab</filename>
-            ôï ðáñáêÜôù:</para>
-
-          <informalexample>
-	    <programlisting>/dev/ad0b                       none            swap    sw 0 0</programlisting>
-          </informalexample>
-
-          <para>ÁëëÜîôå ôï <filename>/dev/ad0b</filename> óôï üíïìá ôçò
-            êáéíïýñãéáò óáò óõóêåõÞò.</para>
-        </step>
-
-        <step>
-          <para>Ãéá íá åíåñãïðïéÞóåôå Üìåóá ôï íÝï swap ÷ñçóéìïðïéÞóôå ôçí
-            åíôïëÞ <command>swapon</command>
-
-            <informalexample>
-              <screen>&prompt.root; <userinput>swapon /dev/da0b</userinput>
-swapon:  added /dev/da0b as swap space</screen>
-            </informalexample>
-          </para>
-        </step>
-      </procedure>
-    </sect2>
-
-    <sect2>
-      <title>ÁíôéãñÜöïíôáò ôá ðåñéå÷üìåíá äßóêùí</title>
-<!-- Should have specific tag -->
-
-      <para>Áðü ôïí:  Renaud Waldura
-        (<email>renaud@softway.com</email>)</para>
-
-      <para>Ãéá íá ìåôáêéíÞóåôå áñ÷åßá áðü ôïí áñ÷éêü óáò äßóêï óå Ýíáí
-        êáéíïýñãéï, êÜíôå:
-
-        <informalexample>
-          <screen>&prompt.root; <userinput>mount /dev/ad2 /mnt</userinput>
-&prompt.root; <userinput>pax -r -w -p e /usr/home /mnt</userinput>
-&prompt.root; <userinput>umount /mnt</userinput>
-&prompt.root; <userinput>rm -rf /usr/home/*</userinput>
-&prompt.root; <userinput>mount /dev/ad2 /usr/home</userinput></screen>
-        </informalexample>
-      </para>
-    </sect2>
-
-    <sect2>
-      <title>ÖôéÜîôå åíùìÝíïõò äßóêïõò ìå ôï CCD</title>
-
-      <para>Áðï ôïí: Stan Brown
-        (<email>stanb@awod.com</email>) </para>
-
-      <para>Ìå ôï Concatenated Disk Driver, Þ áëëéþò CCD, ìðïñåßôå íá Ý÷åôå
-        ðïëëïýò üìïéïõò äßóêïõò áëëÜ íá óõìðåñéöÝñïíôáé ùò Ýíáò.  Ç äéáäéêáóßá
-        ëÝãåôáé óõã÷þíåõóç (striping).  Ìå ôçí åðéêüëëçóç Ý÷åôå êáëýôåñá
-        áðïôåëÝóìáôá óôçí ôá÷ýôçôá åðåéäÞ ìïéñÜæïíôáé ïé åããñáöÝò êáé ïé
-        áíáãíþóåéò óôïõò äßóêïõò.  ÄéáâÜóôå ôéò manual pages &man.ccd.4; êáé
-        &man.ccdconfig.8; Þ ôçí <ulink
-        url="http://stampede.cs.berkeley.edu/ccd/">áñ÷éêÞ óåëßäá ôïõ
-        CCD</ulink> ãéá ðåñéóóüôåñåò ëåðôïìÝñåéåò.</para>
-
-      <para>Ãéá íá ôñÝîåôå CCD ðëÝïí äåí ÷ñåéÜæåóôå åéäéêü ðõñÞíá.  Ìå ôçí
-        åíôïëÞ <command>ccdconfig</command>, öïñôþíåôáé ôï êáôÜëëçëï KLD
-        áõôüìáôá áí ï ðõñÞíáò äåí Ý÷åé Þäç õðïóôÞñéîç ãéá CCD.</para>
-
-      <para>Ôá CCD öôéÜ÷íïíôáé óå partitions ôýðïõ
-        <emphasis>4.2BSD</emphasis>.  Áí èÝëåôå íá ÷ñçóéìïðïéÞóåôå üëï ôïí
-        äßóêï êáé ðÜëé ðñÝðåé íá öôéÜîåôå Ýíá íÝï partition.  Ãéá ðáñÜäåéãìá,
-        ç åíôïëÞ <userinput>disklabel -e</userinput> ìðïñåß íá äåßîåé:</para>
-
-      <informalexample>
-        <screen>#        size   offset    fstype   [fsize bsize bps/cpg]
-  c: 60074784        0    unused        0     0     0   # (Cyl.    0 - 59597)</screen>
-      </informalexample>
-
-      <para>Äåí ìðïñåßôå íá ÷ñçóéìïðïéÞóåôå ôï partition
-        <emphasis>c</emphasis> ãéá CCD, åöüóïí åßíáé ôýðïõ
-        <emphasis>unused</emphasis>.  Áíôßèåôá äçìéïõñãÞóôå Ýíá íÝï partition
-        áêñéâþò ßäéïõ ìåãÝèïõò áëëÜ ôýðïõ <emphasis>4.2BSD</emphasis>:</para>
-
-      <informalexample>
-        <screen>#        size   offset    fstype   [fsize bsize bps/cpg]
-  c: 60074784        0    unused        0     0     0   # (Cyl.    0 - 59597)
-<userinput>   e: 60074784        0    4.2BSD        0     0     0   # (Cyl.    0 - 59597)</userinput></screen>
-      </informalexample>
-
-        <para>Ãéá íá äçìéïõñãÞóåôå Ýíá íÝï CCD, åêôåëÝóôå ôéò ðáñáêÜôù
-          åíôïëÝò. ÐåñéãñÜöïõí ðþò íá ðñïóèÝóåôå ôñåßò äßóêïõò.  Áðëþò áëëÜîôå
-          ôéò óõóêåõÝò üðïõ ÷ñåéÜæåôáé.  Èõìçèåßôå üôé ïé äßóêïé ðñÝðåé íá
-          åßíáé <emphasis>üìïéïé</emphasis>.</para>
-
-      <informalexample>
-        <screen>&prompt.root; <userinput>cd /dev ; sh MAKEDEV ccd0</userinput>
-
-&prompt.root; <userinput>disklabel -r -w da0 auto</userinput>
-&prompt.root; <userinput>disklabel -r -w da1 auto</userinput>
-&prompt.root; <userinput>disklabel -r -w da2 auto</userinput>
-
-&prompt.root; <userinput>disklabel -e da0</userinput>
-<lineannotation>ÐñïóèÝóôå ôï partition e ôýðïõ 4.2BSD</lineannotation>
-&prompt.root; <userinput>disklabel -e da1</userinput>
-<lineannotation>ÐñïóèÝóôå ôï partition e ôýðïõ 4.2BSD</lineannotation>
-&prompt.root; <userinput>disklabel -e da2</userinput>
-<lineannotation>ÐñïóèÝóôå ôï partition e ôýðïõ 4.2BSD</lineannotation>
-
-&prompt.root; <userinput>ccdconfig ccd0 273 0 /dev/da0e /dev/da1e /dev/da2e</userinput>
-
-&prompt.root; <userinput>newfs /dev/ccd0c</userinput></screen>
-      </informalexample>
-
-      <para>Ç ôéìÞ 273 åßíáé ôï ìÝãåèïò ôïõ stripe. Åßíáé ï áñéèìüò ôùí
-        sectors (512 bytes ï êáèÝíáò) óå êÜèå block äåäïìÝíùí ôïõ CCD.
-        Èá ðñÝðåé íá åßíáé ôïõëÜ÷éóôïí 128 kB, êáé äåí ðñÝðåé íá åßíáé äýíáìç
-        ôïõ 2.</para>
-
-      <para>Ôþñá ìðïñåßôå íá êÜíåôå mount êáé íá ÷ñçóéìïðïéÞóåôå ôï CCD óáò
-        ìÝóù ôçò óõóêåõÞò <filename>/dev/ccd0c</filename>.</para>
-
-      <para>¸íá ðéü äõíáôü êáé åõÝëéêôï åíáëëáêôéêü ôïõ CCD åßíáé ôï Vinum.
-        Ðåñéóóüôåñåò ðëçñïöïñßåò óôï <ulink
-        url="http://www.vinumvm.org/">Vinum Project home page</ulink>.</para>
-    </sect2>
-  </sect1>
-
-  <sect1>
-    <title>Åõ÷áñéóôßåò</title>
-
-    <para>Ï óõããñáöÝáò èá Þèåëå íá åõ÷áñéóôÞóåé ôïõò ðáñáêÜôù ãéá ôçí
-      óõíåéóöïñÜ ôïõò óå áõôÞ ôçí åñãáóßá ôïõò:</para>
-
-    <itemizedlist>
-      <listitem>
-        <para>Darryl Okahata (<email>darrylo@hpnmhjw.sr.hp.com</email>)
-          ãéá ôéò áðëÝò ïäçãßåò åãêáôÜóôáóçò åíüò äßóêïõ óå áðïêëåéóôéêü ôñüðï
-          ëåéôïõñãßáò, ôéò ïðïßåò Ý÷ù ðïëëÝò öïñÝò ÷ñçóéìïðïéÞóåé óôçí
-          FreeBSD-questions.</para>
-      </listitem>
-
-      <listitem>
-        <para>&a.jkh;
-          ðïõ Ýêáíå ôï sysinstall ÷ñÞóéìï ãéá ôÝôïéïõ åßäïõò äïõëåéÝò.</para>
-      </listitem>
-
-      <listitem>
-        <para>John Fieber (<email>jfieber@indiana.edu</email>)
-          ðïõ Ýäùóå ôéò ðëçñïöïñßåò êáé ôá ðáñáäåßãìáôá ãéá ôï DocBook DTD
-          ðÜíù óôá ïðïßá áõôü ôï êåßìåíï âáóßæåôáé.</para>
-      </listitem>
-
-      <listitem>
-        <para>&a.grog;
-          ðïõ Ýëåãîå ôçí äïõëåéÜ ìïõ, øÜ÷íïíôáò ãéá áíáêñßâåéåò, êáé ãéá ôçí
-          õðïóôÞñéîç ôïõ óå äéÜöïñá èÝìáôá.</para>
-      </listitem>
-    </itemizedlist>
-  </sect1>
-</article>
diff --git a/el_GR.ISO8859-7/articles/linux-users/article.sgml b/el_GR.ISO8859-7/articles/linux-users/article.sgml
index 1be6e7607d..2db928a22a 100644
--- a/el_GR.ISO8859-7/articles/linux-users/article.sgml
+++ b/el_GR.ISO8859-7/articles/linux-users/article.sgml
@@ -149,10 +149,6 @@ in your /etc/rc.conf. Extra options can be found in startup script.</screen>
 	  <ulink url="ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-6-stable/Latest/"></ulink>
 	  èá êáôåâÜóåôå ôá ðéï ðñüóöáôá ðáêÝôá ðïõ õðÜñ÷ïõí ãéá ôç óåéñÜ
 	  6.X.</para>
-
-	<para>Ìðïñåßôå íá äéáâÜóåôå ðåñéóóüôåñá ãéá ôéò åêäüóåéò ôïõ &os;
-	  óôï Üñèñï <ulink
-	    url="&url.base;/doc/en_US.ISO8859-1/articles/version-guide/">ÅðéëÝãïíôáò ôç ÓùóôÞ ãéá ÅóÜò ¸êäïóç ôïõ &os;</ulink>.</para>
       </note>
 
       <para>Ãéá ðåñéóóüôåñåò ðëçñïöïñßåò ó÷åôéêÜ ìå ôá ðáêÝôá, ðáñáêáëïýìå
diff --git a/el_GR.ISO8859-7/articles/multi-os/Makefile b/el_GR.ISO8859-7/articles/multi-os/Makefile
deleted file mode 100644
index b36397d5ce..0000000000
--- a/el_GR.ISO8859-7/articles/multi-os/Makefile
+++ /dev/null
@@ -1,17 +0,0 @@
-# $FreeBSD$
-#
-# %SOURCE%	en_US.ISO8859-1/articles/multi-os/Makefile
-# %SRCID%	1.12
-
-DOC?= article
-
-FORMATS?= html
-WITH_ARTICLE_TOC?= YES
-
-INSTALL_COMPRESSED?=gz
-INSTALL_ONLY_COMPRESSED?=
-
-SRCS=	article.sgml
-
-DOC_PREFIX?= ${.CURDIR}/../../..
-.include "${DOC_PREFIX}/share/mk/doc.project.mk"
diff --git a/el_GR.ISO8859-7/articles/multi-os/article.sgml b/el_GR.ISO8859-7/articles/multi-os/article.sgml
deleted file mode 100644
index e5beec4198..0000000000
--- a/el_GR.ISO8859-7/articles/multi-os/article.sgml
+++ /dev/null
@@ -1,806 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-7" standalone="no"?>
-<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V4.2-Based Extension//EN"
-	"../../../share/sgml/freebsd42.dtd" [
-<!ENTITY % entities PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Entity Set//EL" "../../share/sgml/entities.ent">
-%entities;
-]>
-
-<!--
-
-  ÅãêáôÜóôáóç êáé ÷ñÞóç ôïõ FreeBSD ìáæß ìå Üëëá ëåéôïõñãéêÜ óõóôÞìáôá.
-
-  The FreeBSD Greek Documentation Project
-
-  %SOURCE%	en_US.ISO8859-1/articles/multi-os/article.sgml
-  %SRCID%	1.39
-
-  $FreeBSD$
--->
-
-<article lang="el">
-  <articleinfo>
-    <title>ÅãêáôÜóôáóç êáé ÷ñÞóç ôïõ FreeBSD ìáæß ìå Üëëá ëåéôïõñãéêÜ óõóôÞìáôá</title>
-
-    <authorgroup>
-      <author>
-	<firstname>Jay</firstname>
-
-	<surname>Richmond</surname>
-
-	<affiliation>
-	  <address>
-	    <email>jayrich@sysc.com</email>
-	  </address>
-	</affiliation>
-      </author>
-    </authorgroup>
-
-    <pubdate>6 August 1996</pubdate>
-
-    <legalnotice id="trademarks" role="trademarks">
-      &tm-attrib.freebsd;
-      &tm-attrib.ibm;
-      &tm-attrib.linux;
-      &tm-attrib.microsoft;
-      &tm-attrib.powerquest;
-      &tm-attrib.general;
-    </legalnotice>
-
-    <releaseinfo>$FreeBSD$</releaseinfo>
-
-    <abstract>
-      <para>Áõôü ôï êåßìåíï ðåñéãñÜöåé ðùò ìðïñåß ôï FreeBSD íá óõíõðÜñîåé
-      	áñìïíéêÜ ìå Üëëá äçìïöéëÞ ëåéôïõñãéêÜ óõóôÞìáôá, üðùò ôï Linux, ôï
-	&ms-dos;, ôï &os2; êáé ôá &windows;&nbsp;95.  Ãéá ôçí âïÞèåéÜ ôïõò óôç
-	óõããñáöÞ áõôïý ôïõ êåéìÝíïõ, èÝëù íá åõ÷áñéóôÞóù ôïõò:
-	Annelise Anderson <email>andrsn@stanford.edu</email>,
-	Randall Hopper <email>rhh@ct.picker.com</email>, êáé &a.jkh;.</para>
-    </abstract>
-  </articleinfo>
-
-  <sect1>
-    <title>Ðåñßëçøç</title>
-
-    <para>Ïé ðåñéóóüôåñïé Üíèñùðïé äåí ìðïñïýí íá óôÞóïõí ðáñáðÜíù áðü Ýíá
-      ëåéôïõñãéêü óýóôçìá ÷ùñßò ìåãÜëï äßóêï, ãé áõôü ðáñáêÜôù èá âñåßôå êáé
-      ðëçñïöïñßåò ãéá ìåãÜëïõò EIDE äßóêïõò.  ÅðåéäÞ õðÜñ÷ïõí ðÜñá ðïëëïß
-      óõíäõáóìïß áðü ðéèáíÜ ëåéôïõñãéêÜ óõóôÞìáôá êáé ñõèìßóåéò óêëçñþí
-      äßóêùí, ôï ôìÞìá <xref linkend="ch5"/> åßíáé ôï ðéï ÷ñÞóéìï.
-      ÐåñéãñÜöåé óõãêåêñéìÝíá ðáñáäåßãìáôá áðü åãêáôáóôÜóåéò, ðïõ äïõëåýïõí
-      ÷ñçóéìïðïéþíôáò ðåñéóóüôåñá áðü Ýíá ëåéôïõñãéêÜ óõóôÞìáôá.</para>
-
-    <para>Áõôü ôï êåßìåíï èåùñåß äåäïìÝíï üôé Ý÷åôå Þäç êÜíåé ÷þñï óôï äßóêï
-      óáò ãéá êÜðïéï ðñüóèåôï ëåéôïõñãéêü óýóôçìá.  ÊÜèå öïñÜ ðïõ áëëÜæåôå
-      ôéò êáôáôìÞóåéò ôïõ äßóêïõ óáò õðÜñ÷åé ï êßíäõíïò íá ÷Üóåôå Þ íá
-      êáôáóôñÝøåôå ôá äåäïìÝíá óôéò õðÜñ÷ïõóåò êáôáôìÞóåéò.  Ðáñüë' áõôÜ, áí ï
-      äßóêïò óáò áõôÞ ôç óôéãìÞ ðåñéÝ÷åé ìüíï DOS êáôáôìÞóåéò, ìðïñåß íá óáò
-      öáíåß ÷ñÞóéìï ôï åñãáëåßï FIPS (ðåñéÝ÷åôáé óôá CD-ROM åãêáôÜóôáóçò ôïõ
-      FreeBSD, óôïí êáôÜëïãï <filename class="directory">\TOOLS</filename>,
-      áëëÜ ìðïñåßôå íá ôï âñåßôå êáé ìÝóù <ulink
-	url="ftp://ftp.FreeBSD.org/pub/FreeBSD/tools/">ftp</ulink>).
-      Ìå ôï FIPS ìðïñåßôå íá áëëÜîåôå ôï ìÝãåèïò ôùí êáôáôìÞóåùí óôï äßóêï
-      óáò, ÷ùñßò íá êáôáóôñáöïýí ôá äåäïìÝíá ðïõ õðÜñ÷ïõí Þäç óå áõôüí.
-      ÕðÜñ÷åé êé Ýíá åìðïñéêü ðñüãñáììá, ðïõ ëÝãåôáé <application>&partitionmagic;</application>, ôï ïðïßï
-      åðéôñÝðåé íá áëëÜîåôå ôï ìÝãåèïò ðïõ Ý÷ïõí Þ íá óâÞóåôå ôéò êáôáôìÞóåéò
-      óáò ÷ùñßò äõóÜñåóôåò óõíÝðåéåò.</para>
-  </sect1>
-
-  <sect1 id="ch2">
-    <title>Óýãêñéóç Äéá÷åéñéóôþí Åêêßíçóçò (boot managers)</title>
-
-    <para>Åäþ ðåñéãñÜöïíôáé êÜðïéïé áðü ôïõò äéÜöïñïõò äéá÷åéñéóôÝò åêêßíçóçò
-      ðïõ ìðïñåß íá óõíáíôÞóåôå.  ÁíÜëïãá ìå ôéò ñõèìßóåéò ôïõ õðïëïãéóôÞ óáò,
-      ìðïñåß íá ÷ñåéáóôåß íá ÷ñçóéìïðïéÞóåôå Ýíá Þ ðåñéóóüôåñïõò óôï ßäéï
-      óýóôçìá.</para>
-
-    <variablelist>
-      <varlistentry>
-	<term>Ôï Boot Easy</term>
-
-	<listitem>
-	  <para>Áõôüò åßíáé ï ðñïêáèïñéóìÝíïò äéá÷åéñéóôÞò åêêßíçóçò ðïõ
-	    ÷ñçóéìïðïéåßôáé ìå ôï FreeBSD.  ¸÷åé ôç äõíáôüôçôá íá îåêéíÞóåé
-	    ó÷åäüí üëá ôá ëåéôïõñãéêÜ óõóôÞìáôá, óõìðåñéëáìâáíïìÝíùí ôùí BSD,
-	    &os2; (HPFS), &windows;&nbsp;95 (FAT Þ FAT32), êáé Linux.  Ç êáôÜôìçóç ðïõ
-	    èá ÷ñçóéìïðïéçèåß äéáëÝãåôáé ìå ôá ðëÞêôñá <keycap>F1</keycap>,
-	    <keycap>F2</keycap>, &hellip;.</para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-	<term>Ï äéá÷åéñéóôÞò åêêßíçóçò ôïõ &os2;</term>
-
-	<listitem>
-	  <para>Áõôüò ï äéá÷åéñéóôÞò åêêßíçóçò ìðïñåß íá îåêéíÞóåé êáôáôìÞóåéò
-	    ôýðïõ FAT, FAT32, HPFS, FFS (FreeBSD) êáé EXT2 (Linux).
-	    Ç êáôÜôìçóç ðïõ èá îåêéíÞóåé
-	    åðéëÝãåôáé ìå ôá âåëÜêéá.  Ï äéá÷åéñéóôÞò åêêßíçóçò ôïõ &os2; åßíáé
-	    ï ìüíïò ðïõ ÷ñçóéìïðïéåß ôï äéêü ôïõ îå÷ùñéóôü ÷þñï óôï äßóêï ãéá
-	    íá êñáôÜåé ðëçñïöïñßåò, áíôßèåôá ìå üëïõò ôïõò Üëëïõò ðïõ
-	    ÷ñçóéìïðïéïýí ôï master boot record (MBR).  Ãé áõôü ðñÝðåé íá
-	    åãêáèßóôáôáé óå ðåñéï÷Þ êïíôÜ óôçí áñ÷Þ ôïõ äßóêïõ, ðñéí áðü ôïí
-	    êýëéíäñï 1024, þóôå íá áðïöåýãïíôáé ðñïâëÞìáôá êáôÜ ôçí åêêßíçóç.
-	    Ìðïñåß íá îåêéíÞóåé êáé ôï Linux ìå ÷ñÞóç ôïõ LILO, üôáí ôï LILO
-	    äåí Ý÷åé åãêáôáóôáèåß óôï MBR áëëÜ óôï boot record ôçò Linux
-	    êáôÜôìçóçò.  ÄéáâÜóôå ðåñéóóüôåñá ãéá ôç ÷ñÞóç ôïõ äéá÷åéñéóôÞ
-	    åêêßíçóçò &os2; ìå Linux óôá <ulink
-	      url="http://www.linuxresources.com/LDP/HOWTO/HOWTO-INDEX.html">Linux
-	    HOWTOs</ulink>.</para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-	<term>OS-BS</term>
-
-	<listitem>
-	  <para>Åíáëëáêôéêüò äéá÷åéñéóôÞò ðïõ ìðïñåßôå íá ÷ñçóéìïðïéÞóåôå áíôß
-	    ãéá ôï Boot Easy.  Äßíåé ìåãáëýôåñï Ýëåã÷ï ôçò äéáäéêáóßáò
-	    åêêßíçóçò, ìå äõíáôüôçôá íá áëëÜîåôå ôçí ðñïêáèïñéóìÝíç êáôÜôìçóç
-	    êáé ôïí ÷ñüíï áíáìïíÞò.  Ïé beta åêäüóåéò ôïõ ðñïãñÜììáôïò
-	    åðéëÝãïõí ôçí åðéëïãÞ ôçò êáôÜôìçóçò ìå ôá âåëÜêéá.  Ìðïñåßôå íá
-	    âñåßôå ôïí OS-BS óôá CD åãêáôÜóôáóçò ôïõ FreeBSD, óôïí êáôÜëïãï
-	    <filename class="directory">\TOOLS</filename> Þ íá ôïí êáôåâÜóåôå ìÝóù
-	    <ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/tools/">ftp</ulink>.</para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-	<term>LILO, Þ LInux LOader</term>
-
-	<listitem>
-	  <para>Áõôüò åßíáé Ýíáò äéá÷åéñéóôÞò åêêßíçóçò ìå
-	    ðåñéïñéóìÝíåò äõíáôüôçôåò.  Ìðïñåß íá îåêéíÞóåé êáé ôï
-	    FreeBSD, áí êáé ÷ñåéÜæåôáé êÜðïéåò áëëáãÝò óôï áñ÷åßï
-	    ñõèìßóåùí ôïõ LILO.</para>
-	</listitem>
-      </varlistentry>
-    </variablelist>
-
-    <note id="fat32">
-      <title>Ó÷åôéêÜ ìå ôï FAT32</title>
-
-      <para>Ôï FAT32 åßíáé ôï óýóôçìá áñ÷åßùí ðïõ Üñ÷éóå íá
-        ÷ñçóéìïðïéåßôáé óôçí Ýêäïóç OEM SR2 ôùí &windows;&nbsp;95 ôçò
-        Microsoft, ðåñßðïõ óôá ôÝëç ôïõ 1996.  Åßíáé ìéá åîÝëéîç ôïõ
-        FAT óõóôÞìáôïò áñ÷åßùí, ðïõ åðéôñÝðåé ôç ÷ñÞóç ìéêñüôåñïõ
-        ìåãÝèïõò cluster óå ìåãÜëïõò äßóêïõò.  ¸÷åé êÜðïéåò äéáöïñÝò
-        üìùò óôç ìïñöÞ ôïõ boot sector êáé ôïõ allocation table, ðïõ
-        ôï êÜíïõí áóýìâáôï ìå êÜðïéïõò äéá÷åéñéóôÝò åêêßíçóçò.</para>
-    </note>
-  </sect1>
-
-  <sect1 id="ch3">
-    <title>Ìéá ôõðéêÞ åãêáôÜóôáóç</title>
-
-    <para>Áò ðïýìå üôé Ý÷åôå äõï ìåãÜëïõò EIDE óêëçñïýò äßóêïõò, êáé èÝëåôå íá
-      åãêáôáóôÞóåôå óå áõôïýò FreeBSD, Linux êáé &windows;&nbsp;95.</para>
-
-    <para>ÐáñáêÜôù èá äïýìå ðùò åãþ (ÓÔÌ: ï óõããñáöÝáò ôïõ Üñèñïõ, Jay
-      Richmond) èá ÷ñçóéìïðïéïýóá áõôïýò ôïõò äßóêïõò:</para>
-
-    <itemizedlist>
-      <listitem>
-	<para><filename>/dev/wd0</filename> (ðñþôïò öõóéêüò äßóêïò)</para>
-      </listitem>
-
-      <listitem>
-	<para><filename>/dev/wd1</filename> (äåýôåñïò öõóéêüò äßóêïò)</para>
-      </listitem>
-    </itemizedlist>
-
-    <para>Êáé ïé äõï äßóêïé Ý÷ïõí 1416 êõëßíäñïõò ï êáèÝíáò.</para>
-
-    <procedure>
-      <step>
-	<para>ÎåêéíÜù áðü ìéá äéóêÝôôá åêêßíçóçò MS-DOS Þ &windows;&nbsp;95 ðïõ
-	  ðåñéÝ÷åé ôï ðñüãñáììá <filename>FDISK.EXE</filename> êáé äçìéïõñãþ
-	  ìéá ìéêñÞ êáôÜôìçóç ôùí 50&nbsp;MB (35-40 ãéá ôá &windows;&nbsp;95,
-	  êáé ëßãï åëåýèåñï ÷þñï) óôïí ðñþôï äßóêï.  Åðßóçò äçìéïõñãþ ìéá
-	  ìåãáëýôåñç êáôÜôìçóç óôïí äåýôåñï äßóêï, ãéá ôá õðüëïéðá äåäïìÝíá
-	  êáé ôéò åöáñìïãÝò ôùí &windows;.</para>
-	</step>
-
-      <step>
-	<para>ÊÜíù åðáíåêêßíçóç êáé óôÞíù ôá &windows;&nbsp;95 óôçí êáôÜôìçóç
-	  <filename>C:</filename>.</para>
-      </step>
-
-      <step>
-	<para>Ôï åðüìåíï âÞìá åßíáé íá óôÞóù ôï Linux.  Äåí åßìáé óßãïõñïò ãéá
-	  üëåò ôéò äéáíïìÝò ôïõ Linux, áëëÜ ôïõëÜ÷éóôïí ôï <ulink url="http://www.slackware.com">Slackware</ulink>
-	  ÷ñçóéìïðïéåß ôï LILO (âë. <xref linkend="ch2"/>).  ¼ôáí äçìéïõñãþ
-	  êáôáôìÞóåéò óôï äßóêï ìïõ ìå ôï <command>fdisk</command> ðñüãñáììá
-	  ôïõ Linux, ôïðïèåôþ üëï ôï Linux óôïí ðñþôï äßóêï (ìéá êáôÜôìçóç ôùí
-	  300&nbsp;MB öôÜíåé ãéá Ýíá êáëü root partition êáé ëßãï swap).</para>
-      </step>
-
-      <step>
-	<para>Áöïý óôÞóù ôï Linux, ôçí þñá ðïõ ìå ñùôÜåé ãéá íá óôÞóåé ôï
-	  LILO, <emphasis>ðñïóÝ÷ù</emphasis> íá óôÞóù ôï LILO óôï boot sector
-	  ôçò Linux êáôÜôìçóÞò ìïõ, êé ü÷é óôï MBR (master boot record).</para>
-      </step>
-
-      <step>
-        <para>Ï õðüëïéðïò ÷þñïò ôïõ äßóêïõ ìðïñåß íá ÷ñçóéìïðïéçèåß áðü ôï
-          FreeBSD.  ÐñïóÝ÷ù ç êáôÜôìçóç óôçí ïðïßá âñßóêåôáé ôï root óýóôçìá
-          áñ÷åßùí ôïõ FreeBSD ìïõ íá ìçí õðåñâáßíåé ôïí êýëéíäñï 1024.  (Ï
-          êýëéíäñïò 1024 åßíáé ðåñßðïõ óôá 528&nbsp;MB óôïõò õðïèåôéêïýò ìáò
-	  äßóêïõò ôùí 720&nbsp;MB.)  Èá ÷ñçóéìïðïéÞóù ôïí õðüëïéðï äßóêï
-	  (ðåñßðïõ 270&nbsp;MB) ãéá ôá óõóôÞìáôá áñ÷åßùí
-	  <filename class="directory">/</filename> êáé
-	  <filename class="directory">/usr</filename> áí ÷ñåéáóôåß.
-	  Ï õðüëïéðïò ÷þñïò ôïõ äåýôåñïõ óêëçñïý äßóêïõ (ôï ìÝãåèïò åîáñôÜôáé
-	  áðü ôï ÷þñï ðïõ èá áöÞóù ãéá ôéò åöáñìïãÝò ôùí &windows;, ðïõ
-	  äçìéïýñãçóá óôï âÞìá 1) ìðïñåß íá ÷ñçóéìïðïéçèåß ãéá ôï óýóôçìá
-	  áñ÷åßùí <filename class="directory">/usr/src</filename> êáé óáí
-	  äåõôåñåýïõóá ìíÞìç (swap space).</para>
-      </step>
-
-      <step>
-	<para>¼ôáí âëÝðù ôïõò äßóêïõò ìå ôï ðñüãñáììá <command>fdisk</command>
-	  ôùí &windows;&nbsp;95, èá ðñÝðåé íá öáßíïíôáé üðùò ðáñáêÜôù:</para>
-
-	<screen>---------------------------------------------------------------------
-
-                  Display Partition Information
-
-Current fixed disk drive: 1
-
-Partition  Status  Type  Volume_Label  Mbytes  System  Usage
-C: 1          A   PRI DOS                50    FAT**     7%
-   2          A   Non-DOS (Linux)       300             43%
-
-Total disk space is  696 Mbytes (1 Mbyte = 1048576 bytes)
-
-Press Esc to continue
-
----------------------------------------------------------------------
-
-                  Display Partition Information
-
-Current fixed disk drive: 2
-
-Partition  Status  Type  Volume_Label  Mbytes  System  Usage
-D: 1          A   PRI DOS                420   FAT**    60%
-
-Total disk space is  696 Mbytes (1 Mbyte = 1048576 bytes)
-
-Press Esc to continue
-
----------------------------------------------------------------------</screen>
-
-	<para>** Åäþ ìðïñåß ï ôýðïò êáôÜôìçóçò íá åßíáé FAT16 Þ FAT32 áí
-	  ÷ñçóéìïðïéåßôáé ç Ýêäïóç OEM SR2 ôùí &windows;.
-	  Âë.&nbsp;<xref linkend="ch2"/>.</para>
-      </step>
-
-      <step>
-	<para>Åãêáèéóôþ ôï FreeBSD. Ðñéí ôçí åãêáôÜóôáóç âåâáéþíïìáé üôé ï
-	  ðñþôïò äßóêïò åßíáé äçëùìÝíïò óáí <quote>NORMAL</quote> óôï BIOS.
-	  Áí äåí åßíáé, ìðïñåß íá ÷ñåéáóôåß íá äþóù ôçí êáíïíéêÞ ãåùìåôñßá ôïõ
-	  äßóêïõ üôáí îåêéíÜåé ï õðïëïãéóôÞò (ãéá íá âñåßôå ôç ãåùìåôñßá ôïõ
-	  äßóêïõ, îåêéíÞóôå ôïí õðïëïãéóôÞ óáò ìå ôá &windows;&nbsp;95 êáé
-	  ôñÝîôå ôï ðñüãñáììá Microsoft Diagnostics
-	  (<filename>MSD.EXE</filename>),Þ åëÝãîôå ôï BIOS).  Ôç ãåùìåôñßá
-	  ôïõ äßóêïõ èá ôçí äþóåôå ìå ôçí ðáñÜìåôñï
-	  <literal>hd0=1416,16,63</literal>, üðïõ
-	  <replaceable>1416</replaceable> åßíáé ï áñéèìüò ôùí êõëßíäñùí ôïõ
-	  óêëçñïý äßóêïõ, <replaceable>16</replaceable> åßíáé ï áñéèìüò ôùí
-	  êåöáëþí óå êÜèå track êáé <replaceable>63</replaceable> åßíáé ï
-	  áñéèìüò ôùí sectors óå êÜèå track ôïõ äßóêïõ.</para>
-      </step>
-
-      <step>
-	<para>¼ôáí öôéÜîù ôéò êáôáôìÞóåéò óôï äßóêï ìïõ, ðñïóÝ÷ù íá
-	  åãêáôáóôáèåß ôï Boot Easy óôïí ðñþôï äßóêï.  Äåí Ý÷åé óçìáóßá íá
-	  êÜíù ôï ßäéï ãéá ôïí äåýôåñï äßóêï, áöïý ôßðïôá äåí îåêéíÜåé áðü
-	  áõôüí.</para>
-      </step>
-
-      <step>
-	<para>¼ôáí êÜíù åðáíåêêßíçóç, ôï Boot Easy èá ðñÝðåé íá áíáãíùñßóåé
-	  ôéò ôñåéò êáôáôìÞóåéò áðü ôéò ïðïßåò ìðïñåß íá îåêéíÞóåé ï
-	  õðïëïãéóôÞò óáí DOS (&windows;&nbsp;95), Linux, êáé BSD (FreeBSD).</para>
-      </step>
-    </procedure>
-  </sect1>
-
-  <sect1 id="ch4">
-    <title>ÅéäéêÝò ÐáñáôçñÞóåéò</title>
-
-    <para>Ôá ðéï ðïëëÜ ëåéôïõñãéêÜ óõóôÞìáôá åßíáé ðïëý áõóôçñÜ ó÷åôéêÜ ìå ôç
-      èÝóç êáé ôïí ôñüðï ðïõ ôïðïèåôïýíôáé óôïí äßóêï.  Ôá &windows;&nbsp;95 êáé ôï
-      DOS áðáéôïýí íá åßíáé óôçí ðñþôç êýñéá êáôÜôìçóç (primary partition) ôïõ
-      ðñþôïõ óêëçñïý äßóêïõ.  Ôï &os2; áðïôåëåß åîáßñåóç.  Ìðïñåß íá
-      åãêáôáóôáèåß óå ïðïéïäÞðïôå äßóêï, óå êýñéá Þ åêôåôáìÝíç êáôÜôìçóç.  Áí
-      äåí åßóôå óßãïõñïé, êñáôÞóôå ôçí áñ÷Þ ôçò êáôÜôìçóçò åêêßíçóçò óå
-      êýëéíäñï ìéêñüôåñï áðü ôïí 1024.</para>
-
-    <para>Áí åãêáôáóôÞóåôå ôá &windows;&nbsp;95 óå Ýíá õðÜñ÷ïí BSD óýóôçìá, èá
-      <emphasis>êáôáóôñÝøåé</emphasis> ôï MBR êáé èá ðñÝðåé íá îáíáóôÞóåôå ôïí
-      ðñïçãïýìåíï boot manager óáò.  Ôï Boot Easy ìðïñåß íá åãêáôáóôáèåß
-      ÷ñçóéìïðïéþíôáò ôï ðñüãñáììá <filename>BOOTINST.EXE</filename> ðïõ
-      õðÜñ÷åé óôïí êáôÜëïãï <filename class="directory">\TOOLS</filename> ôïõ
-      CD-ROM êá óôçíí äéåýèõíóç <ulink
-        url="ftp://ftp.FreeBSD.org/pub/FreeBSD/tools/">ftp</ulink>.
-      Ìðïñåßôå åðßóçò íá îåêéíÞóåôå ðÜëé ôçí äéáäéêáóßá åãêáôÜóôáóçò êáé íá
-      ðÜôå óôïí partition editor.  Áðü åêåß, óçìåéþóôå ôçí êáôÜôìçóç ôïõ
-      FreeBSD óáí bootable, åðéëÝîôå Boot Manager, êáé ôüôå äþóôå W ãéá íá
-      ãñÜøåôå ((W)rite) ôéò ðëçñïöïñßåò óôï MBR.  Ìðïñåßôå ôþñá íá êÜíåôå
-      åðáíåêêßíçóç êáé ôï Boot Easy èá ðñÝðåé íá áíáãíùñßóåé ôçíí êáôÜôìçóç
-      ôùí &windows;&nbsp;95 óáí DOS.</para>
-
-    <para>Óçìåéþóôå åäþ üôé ôï &os2; ìðïñåß íá äéáâÜóåé FAT Þ HPFS êáôáôìÞóåéò,
-      áëëÜ ü÷é êáôáôìÞóåéò ôýðïõ FFS (FreeBSD) Þ EXT2 (Linux).  Áíôßóôïé÷á, ôá
-      &windows;&nbsp;95 ìðïñïýí íá äéáâÜóïõí ìüíï FAT êáé FAT32 óõóôÞìáôá áñ÷åßùí
-      (âë. <xref linkend="ch2"/>).  Ôï FreeBSD ìðïñåß íá äéáâÜóåé ôá
-      ðåñéóóüôåñá óõóôÞìáôá áñ÷åßùí, áëëÜ áõôÞ ôç óôéãìÞ äåí ìðïñåß íá
-      äéáâÜóåé HPFS êáôáôìÞóåéò.  Ôï Linux ìðïñåß íá äéáâÜóåé êáôáôìÞóåéò
-      ôýðïõ HPFS, áëëÜ äåí ìðïñåß íá ãñÜøåé óå áõôÝò.  Ó÷åôéêÜ ðñüóöáôåò
-      åêäüóåéò ôïõ Linux ðçñýíá (2.x) ìðïñïýí íá äéáâÜóïõí êáé íá ãñÜøïõí áðü
-      &windows;&nbsp;95 êáôáôìÞóåéò ôýðïõ VFAT (ôï VFAT åßíáé ðåñßðïõ óáí ôï FAT, ìå
-      ðéï ïõóéáóôéêÞ äéáöïñÜ ôá ìåãÜëá ïíüìáôá áñ÷åßùí).  Ôï Linux ìðïñåß íá
-      äéáâÜóåé êáé íá ãñÜøåé óôá ðåñéóóüôåñá óõóôÞìáôá áñ÷åßùí.  Ôï êáôáëÜâáôå
-      áõôü; Åëðßæù íáé.</para>
-  </sect1>
-
-  <sect1 id="ch5">
-    <title>Ðáñáäåßãìáôá</title>
-
-    <para><emphasis>(Áõôü ôï ôìÞìá ÷ñåéÜæåôáé âåëôéþóåéò,
-      ðáñáêáëþ óôåßëå ôá ðáñáäåßãìáôÜ óáò óôçí äéåýèõíóç
-      <email>jayrich@sysc.com</email>)</emphasis>.</para>
-
-    <para>FreeBSD + Win95: Áí åãêáôáóôÞóåôå ôï FreeBSD ìåôÜ áðü ôá &windows;&nbsp;95,
-      èá ðñÝðåé íá äåßôå ìéá êáôÜôìçóç <literal>DOS</literal> óôï ìåíïý
-      åðéëïãþí ôïõ Boot Easy.  ÁõôÞ åßíáé ç êáôÜôìçóç ôùí &windows;&nbsp;95.
-      Áí åãêáôáóôÞóåôå ôá &windows;&nbsp;95 ìåôÜ áðü ôï FreeBSD, äéáâÜóôå ðáñáðÜíù
-      <xref linkend="ch4"/>.  Áí ï äßóêïò óáò äåí Ý÷åé ðáñáðÜíù áðü 102
-      êõëßíäñïõò, äåí èá ðñÝðåé íá Ý÷åôå ðñüâëçìá íá îåêéíÞóåôå êÜðïéï áðü ôá
-      ëåéôïõñãéêÜ óõóôÞìáôá.  Áí üìùò êÜðïéá áðü ôéò êáôáôìÞóåéò óáò âñßóêåôáé
-      óå êýëéíäñï ìåôÜ áðü ôïí 1024ï êýëéíäñï ôïõ äßóêïõ, êáé ðáßñíåôå
-      ìçíýìáôá üðùò <errorname>invalid system disk</errorname> êÜôù áðü ôï DOS
-      (&windows;&nbsp;95) Þ ôï FreeBSD äåí îåêéíÜåé, äïêéìÜóôå íá øÜîåôå óôï BIOS óáò
-      ãéá ìéá åðéëïãÞ ìå üíïìá <quote>&gt; 1024 cylinder support</quote> Þ
-      <quote>NORMAL/LBA mode</quote>.  Ôï DOS ìðïñåß íá ÷ñåéÜæåôáé íá
-      åíåñãïðïéÞóåôå ôçí åðéëïãÞ LBA (Logical Block Addressing) ãéá íá
-      îåêéíÞóåé óùóôÜ.  Áí ç éäÝá ôçò áëëáãÞò óå LBA mode êÜèå öïñÜ ðïõ èÝëåôå
-      íá îåêéíÞóåôå ôï DOS äåí óáò áñÝóåé ðïëý, ìðïñåßôå íá îåêéíÞóåôå ôï
-      FreeBSD áðü ôï DOS ÷ñçóéìïðïéþíôáò ôï ðñüãñáììá
-      <filename>FBSDBOOT.EXE</filename> áðü ôï CD (áõôü ðñÝðåé íá âñåé ìüíï
-      ôïõ êáé íá îåêéíÞóåé ôçí FreeBSD êáôÜôìçóÞ óáò).</para>
-
-    <para>FreeBSD + &os2; + Win95:  Ôßðïôá äéáöïñåôéêü åäþ.  Ï boot manager ôïõ
-      &os2; ìðïñåß íá îåêéíÞóåé ïðïéïäÞðïôå áðü áõôÜ ôá ëåéôïõñãéêÜ óõóôÞìáôá,
-      ïðüôå äåí èá Ý÷åôå ðñüâëçìá.</para>
-
-    <para>FreeBSD + Linux:  Ìðïñåßôå íá ÷ñçóéìïðïéÞóåôå ôï Boot Easy ãéá íá
-      îåêéíÞóåôå áõôÜ ôá äõï ëåéôïõñãéêÜ óõóôÞìáôá.</para>
-
-    <para>FreeBSD + Linux + Win95:  (âë. <xref linkend="ch3"/>)</para>
-  </sect1>
-
-  <sect1 id="sources">
-    <title>ÄéÜöïñåò ÐçãÝò ÂïÞèåéáò</title>
-
-    <para>ÕðÜñ÷ïõí ðïëëÜ êåßìåíá HOWTO óôçí óõëëïãÞ ôùí <ulink
-        url="http://www.linuxresources.com/LDP/HOWTO/HOWTO-INDEX.html">Linux
-        HOW-TOs</ulink> ðïõ áíáöÝñïíôáé óôï èÝìá ôùí ðïëëáðëþí ëåéôïõñãéêþí
-      óôïí ßäéï óêëçñü äßóêï.</para>
-
-    <para>Ôï êåßìåíï <ulink
-	url="http://www.linuxresources.com/LDP/HOWTO/mini/Linux+DOS+Win95+OS2.html">Linux+DOS+Win95+OS2
-	mini-HOWTO</ulink> ðñïóöÝñåé âïÞèåéá ãéá ôéò ñõèìßóåéò ôïõ &os2; boot
-      manager, êáé ôï êåßìåíï <ulink
-	url="http://www.linuxresources.com/LDP/HOWTO/mini/Linux+FreeBSD.html">Linux+FreeBSD
-
-	mini-HOWTO</ulink> ìðïñåß íá óáò åíäéáöÝñåé áñêåôÜ.  ¸íá Üëëï êåßìåíï
-      ðïõ åßíáé ÷ñÞóéìï åßíáé ôï <ulink
-      url="http://www.in.net/~jkatz/win95/Linux-HOWTO.html">Linux-HOWTO</ulink>.</para>
-
-    <para>Ï ïäçãüò <ulink
-	url="http://www.tburke.net/info/ntldr/ntldr_hacking_guide.htm">The NTLDR
-	Hacking Guide</ulink> ðåñéÝ÷åé ðïëëÝò ðëçñïöïñßåò ãéá ôçí
-      åêêßíçóç ôùí &windows;&nbsp;NT, '95 êáé ôïõ DOS ìáæß ìå Üëëá ëåéôïõñãéêÜ
-      óõóôÞìáôá.</para>
-
-    <para>Êáé ç óõëëïãÞ ïäçãþí <quote>How It Works</quote> ôïõ Hale Landis
-      ðåñéÝ÷åé êÜðïéåò ÷ñÞóéìåò ðëçñïöïñßåò ó÷åôéêÜ ìå ôçí ãåùìåôñßá ôùí
-      äßóêùí êáé ôçí åêêßíçóç ôùí õðïëïãéóôþí.  Ìðïñåßôå íá âñåßôå áõôÞ ôç
-      óõëëïãÞ óôçí äéåýèõíóç
-      <ulink url="ftp://fission.dt.wdc.com/pub/otherdocs/pc_systems/how_it_works/allhiw.zip"></ulink>.</para>
-
-    <para>ÔÝëïò, ìçí îå÷íÜôå ôçí ôåêìçñßùóç ôïõ ðçñýíá ôïõ FreeBSD ãéá ôçí
-      äéáäéêáóßá åêêßíçóçò, ðïõ äéáíÝìåôáé ìáæß ìå ôïí ðçãáßï êþäéêá
-      (áðïóõõìðéÝæåôáé óôï áñ÷åßï <ulink
-      url="/usr/src/sys/i386/boot/biosboot/README.386BSD"></ulink>.</para>
-  </sect1>
-
-  <sect1>
-    <title>Ôå÷íéêÝò ËåðôïìÝñåéåò</title>
-
-    <para><emphasis>(ÃñÜöôçêå áðü ôïí Randall Hopper,
-	<email>rhh@ct.picker.com</email>)</emphasis></para>
-
-    <para>Áõôü ôï ôìÞìá ðñïóðáèåß íá óáò äþóåé áñêåôÝò áðü ôéò âáóéêÝò
-      ðëçñïöïñßåò ãéá ôïõò óêëçñïýò äßóêïõò óáò êáé ôçí äéáäéêáóßá åêêßíçóçò
-      þóôå íá ìðïñåßôå íá áíôéìåôùðßóåôå ôá ðéï ðïëëÜ áðü ôá ðñïâëÞìáôá ðïõ
-      ìðïñåß íá óõíáíôÞóåôå êáèþò ðñïóðáèåßôå íá åãêáôáóôÞóåôå Ýíá Þ
-      ðåñéóóüôåñá ëåéôïõñãéêÜ óõóôÞìáôá.  ÎåêéíÜ ìå ðïëý âáóéêÜ ðñÜãìáôá,
-      ïðüôå ìðïñåßôå íá áãíïÞóåôå ôá ðñþôá ìÝñç êáé íá áñ÷ßóåôå íá äéáâÜæåôå
-      áñãüôåñá, üôáí öáíåß üôé áõôÜ ðïõ ãñÜöïíôáé äåí óáò åßíáé Þäç
-      ãíùóôÜ.</para>
-
-    <sect2>
-      <title>Óêëçñïß Äßóêïé</title>
-
-      <para>Ôñåéò âáóéêïß üñïé ÷ñçóéìïðïéïýíôáé ãéá íá ðåñéãñÜøïõí ôç èÝóç ôùí
-        äåäïìÝíùí óôï óêëçñü äßóêï óáò: ïé êýëéíäñïé (cylinders), ïé êåöáëÝò
-        (heads) êáé ïé ôïìåßò (sectors).  Äåí åßíáé éäéáßôåñá óçìáíôéêü íá
-        ãíùñßæåôå ôé áêñéâþò óçìáßíïõí áõôïß ïé üñïé, åêôüò áðü ôï ãåãïíüò üôé
-        ðñïóäéïñßæïõí ôçí öõóéêÞ èÝóç ôùí äåäïìÝíùí óôï äßóêï óáò.</para>
-
-      <para>Ï äßóêïò óáò Ý÷åé Ýíá óõãêåêñéìÝíï áñéèìü áðü êõëßíäñïõò, Ýíá
-        áñéèìü áðü êåöáëÝò êáé êÜðïéï áñéèìü áðü ôïìåßò óå êÜèå æåõãÜñé
-        êõëßíäñïõ-êåöáëÞò (ôï æåõãÜñé êõëßíäñïõ-êåöáëÞò åßíáé ãíùóôü êáé ùò
-        ìïíïðÜôé Þ track).  ÓõíïëéêÜ áõôÝò ïé ðëçñïöïñßåò ïñßæïõí ôçí
-        <quote>öõóéêÞ ãåùìåôñßá äßóêïõ</quote> ôïõ óêëçñïý äßóêïõ.  Ôï ôõðéêü
-        ìÝãåèïò åíüò ôïìÝá åßíáé 512 bytes êáé óõíÞèùò õðÜñ÷ïõí 63 ôïìåßò óå
-        êÜèå ìïíïðÜôé.  Ï áñéèìüò ôùí êåöáëþ êáé êõëßäñùí äéáöÝñåé áñêåôÜ áðü
-        äßóêï óå äßóêï.  ¸ôóé ìðïñåßôå íá õðïëïãßóåôå ôïí áñéèìü ôùí bytes ðïõ
-        ÷ùñÜíå íá áðïèçêåõèïýí óôï äßóêï óáò õðïëïãßæïíôáò ôçí ôéìÞ:</para>
-
-	<informalexample>
-	  <para>(êýëéíäñïé) &times; (êåöáëÝò) &times; (63
-	    ôïìåßò/ìïíïðÜôé) &times; (512 bytes/ôïìÝá)</para>
-	</informalexample>
-
-      <para>Ãéá ðáñÜäåéãìá, óôïí 1.6 GigWestern Digital AC31600 EIDE óêëçñü
-        äßóêï ìïõ, áõôÝò ïé ôéìÝò åßíáé:</para>
-
-	<informalexample>
-	  <para>(3148 cyl) &times; (16 heads) &times; (63
-	    sectors/track) &times; (512 bytes/sect)</para>
-	</informalexample>
-
-      <para>ðïõ ìáò äßíåé 1.624.670.208 bytes, Þ ðåñßðïõ 1.6 Gig.</para>
-
-      <para>Ìðïñåßôå íá âñåßôå ôçí öõóéêÞ ãåùìåôñßá ôïõ äßóêïõ óáò (ôïí áñéèìü
-        ôùí êõëßíäñùí, ôùí êåöáëþí êáé ôï ðëÞèïò ôùí ôïìÝùí áíÜ ìïíïðÜôé)
-        ÷ñçóéìïðïéþíôáò ôï ðñüãñáììá ATAID Þ Üëëá ðñïãñÜììáôá ðïõ åßíáé
-        äéáèÝóéìá ìÝóù äéêôýïõ.  Ðñïóï÷Þ üìùò.  Áí Ý÷åôå åíåñãïðïéÞóåé ôçí
-        ðñüóâáóç ìå LBA óôï BIOS óáò (âë. <xref linkend="limits"/>), äåí
-        ìðïñåßôå íá ÷ñçóéìïðïéÞóåôå ïðïéïäÞðïôå ðñüãñáììá ãéá íá äéáâÜóåôå ôçí
-        öõóéêÞ ãåùìåôñßá ôïõ äßóêïõ.  Áõôü óõìâáßíåé ãéáôß ðïëëÜ ðñïãñÜììáôá
-        (ð.÷. ôï <filename>MSD.EXE</filename> Þ ôï fdisk ôïõ FreeBSD) äåí
-        äéáâÜæïõí ôçí öõóéêÞ ãåùìåôñßá ôïõ äßóêïõ, áëëÜ ôçí
-        <firstterm>ìåôáöñáóìÝíç ãåùìåôñßá</firstterm> (åéêïíéêïýò áñéèìïýò ðïõ
-        ðñïêýðôïõí áðü ôçí ÷ñÞóç LBA ðñüóâáóçò).  Äåßôå ðáñáêÜôù ôé óçìáßíåé
-        áõôü.</para>
-
-      <para>ÊÜôé Üëëï ðïõ åßíáé ÷ñÞçóéìï ãé áõôïýò ôïõò üñïõò.  Ìå ìéá ôñéÜäá
-        áñéèìþí&mdash;Ýíá áñéèìü êõëßíäñïõ, Ýíá áñéèìü êåöáëÞò êé Ýíá áñéèìü
-        ôïìÝá ìÝóá óôï ìïíïðÜôé&mdash;ìðïñåßôå íá áíáöåñèåßôå óôçí öõóéêÞ èÝóç
-        åíüò óõãêåêñéìÝíïõ ôïìÝá ôïõ äßóêïõ óáò (Ýíá ìðëïê äåäïìÝíùí, ìåãÝèïõò
-        512 bytes).  Ïé êýëéíäñïé êáé ïé êåöáëÝò Ý÷ïõí áñéèìïýò áðü 0 êáé
-        ðÜíù, åíþ ïé ôïìåßò áðü 1 êáé ðÜíù.</para>
-
-      <para>Ãéá áõôïýò ðïõ åíäéáöÝñïíôáé ãéá ðåñéóóüôåñåò ôå÷íéêÝò
-	ëåðôïìÝñåéåò, ðëçñïöïñßåò ãéá ôçí ãåùìåôñßá ôùí äßóêùí, ôïõò ôïìåßò
-	åêêßíçóçò (boot sectors), ôá BIOS, êëð. ìðïñïýí íá âñåèïýí óå ðïëëÜ
-	ìÝñç óôï äéáäßêôõï.  ØÜîôå óôï Lycos, óôï Yahoo, êëð. ãéá
-	<literal>boot sector</literal> Þ ãéá <literal>master boot
-	record</literal>.  ÁíÜìåóá óôéò ÷ñÞóéìåò ðëçñïöïñßåò èá âñåßôå êáé ôçí
-	óåéñÜ êåéìÝíùí <citetitle>How It Works</citetitle> ôïõ Hale Landis.
-	Äåßôå ôï ôìÞìá <xref linkend="sources"/> ãéá ðåñéóóüôåñåò ëåðôïìÝñåéåò
-	êé áíáöïñÝò óå ðçãÝò.</para>
-
-      <para>Ok, áñêåôÜ ìå ôçí ïñïëïãßá.  Õðïôßèåôáé ìéëÜìå ãéá ôçí äéáäéêáóßáò
-        åêêßíçóçò.</para>
-    </sect2>
-
-    <sect2 id="booting">
-      <title>Ç äéáäéêáóßá Åêêßíçóçò</title>
-
-      <para>Óôïí ðñþôï ôïìÝá ôïõ äßóêïõ (Êõë. 0, ÊåöáëÞ 0, ÔïìÝáò 1) õðÜñ÷åé ï
-        Êýñéïò ÔïìÝáò Åêêßíçóçò (Master Boot Record Þ MBR).  ÐåñéÝ÷åé Ýíá
-        ÷Üñôç ôïõ äßóêïõ.  Ïñßæåé ìÝ÷ñé 4 <firstterm>êáôáôìÞóåéò</firstterm>
-        (partitions), êÜèå ìéá áðü ôéò ïðïßåò åßíáé Ýíá óõíå÷Ýò êïììÜôé ôïõ
-        äßóêïõ.  Ôï FreeBSD ïíïìÜæåé ôéò êáôáôìÞóåéò
-        <firstterm>slices</firstterm> ãéá íá áðïöýãåé ôçí óýã÷õóç ìå ôá äéêÜ
-        ôïõ partitions, áëëÜ äåí èá ôï êÜíïõìå áõôü åäþ.  ÊÜèå êáôÜôìçóç
-        ìðïñåß íá ðåñéÝ÷åé ôï äéêü ôçò, îå÷ùñéóôü ëåéôïõñãéêü óýóôçìá.</para>
-
-      <para>ÊÜèå åããñáöÞ êáôÜôìçóçò óôï MBR Ý÷åé Ýíá <firstterm>Partition
-          ID</firstterm>, Ýíá <firstterm>áñ÷éêü êýëéíäñï</firstterm> êáé Ýíá
-        <firstterm>ôåëéêü êýëéíäñï/êåöáëÞ/ôïìÝá</firstterm>.  Ôï Partition ID
-        ïñßæåé ôé ôýðïõ åßíáé ç êáôÜôìçóç (ôé ëåéôïõñãéêü óýóôçìá ðåñéÝ÷åé)
-        êáé ç áñ÷Þ/ôÝëïò ïñßæïõí ðïõ âñßóêåôáé.  Ï <xref linkend="tbl-pid"/>
-        äåß÷íåé êÜðïéïõò áðü ôïõò ðéï êïéíïýò ôýðïõò êáôÜôìçóçò.</para>
-
-      <table id="tbl-pid">
-	<title>Ôýðïé êáôáôìÞóåùí</title>
-
-	<tgroup cols="2">
-	  <thead>
-	    <row>
-	      <entry>Ôýðïò (óôï äåêáåîáäéêü)</entry>
-	      <entry>ÐåñéãñáöÞ</entry>
-	    </row>
-	  </thead>
-
-	  <tbody>
-	    <row>
-	      <entry>01</entry>
-	      <entry>Êýñéá êáôÜôìçóç DOS12 (12-bit FAT)</entry>
-	    </row>
-
-	    <row>
-	      <entry>04</entry>
-	      <entry>Êýñéá êáôÜôìçóç DOS16 (16-bit FAT)</entry>
-	    </row>
-
-	    <row>
-	      <entry>05</entry>
-	      <entry>ÅêôåôáìÝíç êáôÜôìçóç DOS</entry>
-	    </row>
-
-	    <row>
-	      <entry>06</entry>
-	      <entry>Êýñéá êáôÜôìçóç DOS ìåãÜëõ ìåãÝèïõò (&gt; 32MB)</entry>
-	    </row>
-
-	    <row>
-	      <entry>0A</entry>
-	      <entry>&os2;</entry>
-	    </row>
-
-	    <row>
-	      <entry>83</entry>
-	      <entry>Linux (EXT2FS)</entry>
-	    </row>
-
-	    <row>
-	      <entry>A5</entry>
-	      <entry>FreeBSD, NetBSD, 386BSD (UFS)</entry>
-	    </row>
-	  </tbody>
-	</tgroup>
-      </table>
-
-      <para>Óçìåéþóôå ðùò äåí åßíáé äõíáôÞ ç åêêßíçóç áðü ïðïéïäÞðïôå ôýðï
-	êáôÜôìçóçò (ð.÷. áðü åêôåôáìÝíåò êáôáôìÞóåéò DOS).  Áðü êÜðïéïõò
-	ôýðïõò ãßíåôáé, áðü Üëëïõò ü÷é.  Áõôü ðïõ êÜíåé äõíáôÞ ôçí åêêßíçóç
-	áðü ìéá êáôÜôìçóç åßíáé ïé ñõèìßóåéò ôïõ <firstterm>ÔïìÝá Åêêßíçóçò
-	  ÊáôÜôìçóçò</firstterm> ðïõ âñßóêåôáé óôçí áñ÷Þ êÜèå êáôÜôìçóçò.</para>
-
-      <para>¼ôáí ñõèìßóåôå ôïí boot manager ôçò ðñïôéìÞóåþò óáò, áõôüò øÜ÷íåé
-        üëåò ôéò åããñáöÝò êáôáôìÞóåùí ôïí ðßíáêá MBR üëùí ôùí äßóêùí óáò êáé
-        óáò äßíåé ôç äõíáôüôçôá íá ïíïìÜóåôå åããñáöÝò áðü ôç ëßóôá.  ¸ôóé,
-        ìüëéò îåêéíÜôå ôïí õðïëïãéóôÞ óáò, åéäéêüò êþäéêáò óôï Master Boot
-        Sector ôïõ ðñþôïõ äßóêïõ ôïõ óõóôÞìáôïò ôñÝ÷åé êáé îåêéíÜåé ôïí boot
-        manager.  Ï boot manager âñßóêåé óôïí ðßíáêá MBR ôçí åããñáöÞ ãéá ôçí
-        êáôÜôìçóç ðïõ åðéëÝîáôå, âñßóêåé ôçí áñ÷Þ êáé ôï ôÝëïò ôçò êáôÜôìçóçò,
-        öïñôþíåé óôç ìíÞìç ôïíí ÔïìÝá Åêêßíçóçò ÊáôÜôìçóçò áðü áõôÞ ôçí
-        êáôÜôìçóç êáé ðåñíÜåé ôïí Ýëåã÷ï óå áõôüí.  Ï ÔïìÝáò Åêêßíçóçò ôçò
-        êáôÜôìçóçò ðåñéÝ÷åé áñêåôÝò ðëçñïöïñßåò ãéá íá îåêéíÞóåé íá öïñôþíåé
-        ôï ëåéôïõñãéêü óýóôçìá áðü áõôÞ ôçí êáôÜôìçóç.</para>
-
-      <para>ÊÜôé ðïõ äå ôï áíáöÝñáìå ìå ðïëëÝò ëåðôïìÝñåéåò åßíáé óçìáíôéêü
-        êáé ðñÝðåé íá ôï îÝñåôå.  ¼ëïé ïé äßóêïé óáò Ý÷ïõí MBR.  ÁëëÜ, ï
-        ôïìÝáò MBR ðïõ åßíáé óçìáíôéêüò åßíáé áõôüò ðïõ åßíáé óôïí ðñþôï äßóêï
-        ôïõ óõóôÞìáôïò ðïõ áíáãíùñßæåôáé áðü ôï BIOS.  Áí Ý÷åôå ìüíï IDE
-        äßóêïõò åßíáé ï ðñþôïò IDE äßóêïò (äçë. ï êýñéïò äßóêïò ôïõ ðñþôïõ
-        åëåãêôÞ äßóêùí).  Áíôßóôïé÷á ãéá ôá óõóôÞìáôá ðïõ Ý÷ïõí ìüíï SCSI
-        äßóêïõò.  Áí Ý÷åôå êáé IDE êáé SCSI äßóêïõò üìùò, óõíÞèùò åßíáé ïé IDE
-        äßóêïé ðïõ áíáãíùñßæïíôáé ðñþôá áðü ôï BIOS.  Ôüôå ï boot manager
-        ðñÝðåé íá ôïðïèåôçèåß óôï MBR áõôïý ôïõ äßóêïõ, üðùò ðåñéãñÜøáìå
-        ðñéí.</para>
-    </sect2>
-
-    <sect2 id="limits">
-      <title>Ðåñéïñéóìïß Åêêßíçóçò êáé ÐñïåéäïðïéÞóåéò</title>
-
-      <para>Êáé ôþñá ôá åíäéáöÝñïíôá ðñÜãìáôá ãéá ôá ïðïßá èá ðñÝðåé íá
-        ðñïóÝ÷åôå.</para>
-
-      <sect3>
-	<title>Ôï ðåñßöçìï üñéï ôïõ êõëßíäñïõ 1024 êáé ðùò âïçèÜåé ôï LBA
-	  BIOS</title>
-
-	<para>Ôï ðñþôï êïììÜôé ôçò äéáäéêáóßáò åêêßíçóçò ãßíåôáé åî' ïëïêëÞñïõ
-	  ìÝóù ôïõ BIOS (áí áõôüò åßíáé êáéíïýñéïò üñïò ãéá óáò, ôï BIOS åßíáé
-	  Ýíá êïììÜôé ëïãéóìéêïý, áðïèçêåõìÝíï óå Ýíá chip ôçò ìçôñéêÞò
-	  ðëáêÝôáò ôïõ óõóôÞìáôüò óáò, ðïõ ðåñéÝ÷åé ôïí êþäéêá åêêßíçóçò ôïõ
-	  óýóôçìáôïò).  Ãé áõôü ôï ëüãï ôï ðñþôï êïììÜôé ôçò åêêßíçóçò
-	  õðüêåéôáé óôïõò ðåñéïñéóìïýò ôïõ BIOS.</para>
-
-	<para>Ï ôñüðïò ìå ôïí ïðïßï ôï BIOS êáëåßôáé íá äéáâÜóåé ôïí óêëçñü
-	  äßóêï óå áõôü ôï óôÜäéï ôçò åêêßíçóçò (INT 13H, ÓõíÜñôçóç 2)
-	  äåóìåýåé 10 bits ãéá ôïí áñéèìü êõëßíäñïõ, 8 bits ãéá ôïí áñéèìü
-	  êåöáëÞò êáé 6 bits ãéá ôïí áñéèìü ôïìÝá.  Áõôü ðåñéïñßæåé êÜðùò ôïõò
-	  ÷ñÞóôåò áõôÞò ôçò êëÞóçò (ð.÷. ôïõò boot managers ðïõ õðÜñ÷ïõí óôï
-	  MBR ôïõ äßóêïõ óáò, êáèþò êáé ôïõò loaders ôùí ëåéôïõñãéêþí
-	  óõóôçìÜôùí ðïõ õðÜñ÷ïõí óôïõò Üëëïõò ôïìåßò åêêßíçóçò).
-	  Ôá üñéá ðïõ åðéâÜëëåé áõôÞ ç êëÞóç åßíáé:</para>
-
-        <itemizedlist>
-          <listitem>
-            <para>ìÝãéóôïò áñéèìüò êõëßíäñùí = 1024</para>
-          </listitem>
-
-          <listitem>
-            <para>ìÝãéóôïò áñéèìüò êåöáëþíí = 256 heads</para>
-          </listitem>
-
-          <listitem>
-            <para>ìÝãéóôïò áñéèìüò ôïìÝùí/ìïíïðÜôé = 64 (âáóéêÜ 63, ï ôïìÝáò
-              <literal>0</literal> äåí åßíáé äéáèÝóéìïò)</para>
-          </listitem>
-        </itemizedlist>
-
-
-	<para>ÓÞìåñá ïé äßóêïé åßíáé áñêåôÜ ìåãÜëïé, êáé Ý÷ïõí ðÜñá ðïëëïýò
-	  êõëßíäñïõò áëëÜ ü÷é ðÜñá ðïëëÝò êåöáëÝò.  ¸ôóé ëïéðüí, ÷ùñßò
-	  åîáßñåóç, ïé ìåãÜëïé óêëçñïß äßóêïé Ý÷ïõí ðåñéóóüôåñïõò áðü 1024
-	  êõëßíäñïõò.  Áõôü óçìáßíåé ðùò ôï BIOS äåí ìðïñåß íá åêêéíÞóåé ôïí
-	  õðïëïãéóôÞ óáò áðü ïðïéïäÞðïôå óçìåßï ôïõ äßóêïõ.  Ï êþäéêáò
-	  åêêßíçóçò (ï boot manager êáé ï OS loader ðïõ Ý÷åé åãêáôáóôáèåß óå
-	  üëåò ôéò êáôáôìÞóåéò áðü ôéò ïðïßåò èÝëïõìå íá åßíáé äõíáôÞ ç
-	  åêêßíçóç) ðñÝðåé íá åßíáé êÜôù áðü ôï üñéï ôïõ êõëßíäñïõ 1024.
-	  ÃåíéêÜ, áí ï äßóêïò óáò åßíáé Ýíáò ôõðéêüò äßóêïò êé Ý÷åé 16
-	  êåöáëÝò, áõôü óçìáßíåé:</para>
-
-	<informalexample>
-	  <para>1024 êõë/äßóêï &times; 16 êåöáëÝò/äßóêï &times;
-	    63 ôïìåßò/(êõë-êåöáëÞ) &times; 512 bytes/ôïìÝá</para>
-	</informalexample>
-
-	<para>ðïõ åßíáé ðåñßðïõ êïíôÜ óôï üñéï ôùí 528&nbsp;MB ðïõ óõ÷íÜ èá
-	  áêïýóåôå íá áíáöÝñåôáé.</para>
-
-	<para>Åäþ åßíáé ðïõ ç ÷ñÞóç ôïõ BIOS LBA (Logical Block
-	  Addressing&mdash;ËïãéêÞ Äéåõèõíóéïäüôçóç Ìðëïê) Ýñ÷åôáé íá ìáò
-	  âïçèÞóåé.  Ç äéåõèõíóéïäüôçóç LBA äßíåé óôïí ÷ñÞóôç ôùí êëÞóåùí ôïõ
-	  BIOS API Ýíá ôñüðï íá ðñïóðåëÜóåé êõëßíäñïõò ðÜíù áðü ôïí êýëéíäñï
-	  1024 ÷ñçóéìïðïéþíôáò ôéò ßäéåò êëÞóåéò BIOS ïñßæïíôáò äéáöïñåôéêÜ
-	  ôïí êýëéíäñï.  Ïñßæåé ìéá äéáöïñåôéêÞ ïñãÜíùóç ôùí êõëßíäñùí êáé ôùí
-	  êåöáëþí, ãéá íá äþóåé ìÝóù ôïõ BIOS äéáöïñåôéêÞ ìïñöÞ óôï äßóêï, ìå
-	  ëéãüôåñïõò êõëßíäñïõò êáé ðåñéóóüôåñåò êåöáëÝò áðü üôé ðñáãìáôéêÜ
-	  Ý÷åé.  Ìå ëßãá ëüãéá, åêìåôáëëåýåôáé ôï ãåãïíüò üôé ïé äßóêïé Ý÷ïõí
-	  ó÷åôéêÜ ëßãåò êåöáëÝò êáé ðïëý ðåñéóóüôåñïõò êõëßíäñïõò áëëÜæïíôáò
-	  ëßãï ôçí éóïññïðßá ìåôáîý ôïõ áñéèìïý ôùí êõëßíäñùí êáé ôïõ áñéèìïý
-	  ôùí êåöáëþí, Ýôóé þóôå êáé ïé äõï áñéèìïß íá öáßíïíôáé êÜôù áðü ôá
-	  üñéá ðïõ áíáöÝñáìå (1024 êýëéíäñïé, 256 êåöáëÝò).</para>
-
-	<para>Ìå ÷ñÞóç BIOS LBA, ôï üñéï ìåãÝèïõò ôïõ äßóêïõ äåí åßíáé ðëÝïí
-	  åìðüäéï (ôïõëÜ÷éóôïí, ü÷é ìÝ÷ñé ôá 8 Gigabytes).  Áí Ý÷åôå LBA BIOS,
-	  ìðïñåßôå íá âÜëåôå ôï FreeBSD Þ ïðïéïäÞðïôå Üëëï ëåéôïõñãéêü óýóôçìá
-	  ïðïõäÞðïôå èÝëåôå êáé íá ìçí ðåñéïñßæåóôå áðü ôï üñéï ôïõ êõëßíäñïõ
-	  1024.</para>
-
-	<para>Ãéá íá ÷ñçóéìïðïéÞóù îáíÜ ôïí 1.6 Gig Western Digital äßóêï ìïõ
-	  óáí ðáñÜäåéãìá, ç öõóéêÞ ãåùìåôñßá ôïõ åßíáé:</para>
-
-	<informalexample>
-	  <para>(3148 êõë, 16 êåö, 63 ôïìåßò/ìïíïðÜôé, 512 bytes/ôïìÝá)</para>
-	</informalexample>
-
-	<para>ÁëëÜ, ç äéåõèõíóéïäüôçóç LBA ôïõ BIOS ôïí áëëÜæåé óå:</para>
-
-	<informalexample>
-	  <para>(787 êõë, 64 êåö, 63 ôïìåßò/ìïíïðÜôé, 512 bytes/ôïìÝá)</para>
-	</informalexample>
-
-	<para>äßíïíôáò ðñáêôéêÜ ôï ßäéï ìÝãåèïò äßóêïõ, áëëÜ ìå ôïõò áñéèìïýò
-	  êõëßíäñùí êáé êåöáëþí ìÝóá óôá üñéá ôùí êëÞóåùí ôïõ BIOS API
-	  (Ðáñåðéðôüíôùò, Ý÷ù óôÞóåé êáé Linux êáé FreeBSD óå Ýíá áðü ôïõõò
-	  äßóêïõò ìïõ, ðÜíù áðü ôï üñéï ôïõ êõëßíäñïõ 1024.  Êáé ôá äõï
-	  ëåéôïõñãéêÜ óõóôÞìáôá äïõëåýïõí ìéá ÷áñÜ, ÷Üñç óôçí äéåõèõíóéïäüôçóç
-	  LBA ôïõ BIOS).</para>
-      </sect3>
-
-      <sect3>
-	<title>Boot Managers êáé ÊáôáíïìÞ Äßóêùí</title>
-
-	<para>¸íá Üëëï óçìáíôéêü óçìåßï ðïõ áîßæåé íá ðñïóÝîåôå üôáí óôÞíåôå
-	  êÜðïéï boot manager åßíáé íá êñáôÞóåôå áñêåôü ÷þñï ãéá ôïí boot
-	  manager.  Åßíáé êáëýôåñá íá ôïï îÝñåôå áõôü áðü ôçí áñ÷Þ ãéá íá
-	  ãëéôþóåôå áðü ôïí êüðï ôçò åðáíåãêáôÜóôáóçò åíüò ç ðåñéóóüôåñùí áðü
-	  ôá ëåéôïõñãéêÜ óõóôÞìáôÜ óáò.</para>
-
-	<para>Áí áêïëïõèÞóáôå ôéò ïäçãßåò óôï <xref linkend="booting"/> ó÷åôéêÜ
-	  ìå ôï MBR (ðïõ åßíáé ôï MBR), ôïõò Ôïìåßò Åêêßíçóçò, êáé ôçí
-	  äéáäéêáóßá åêêßíçóçò, ìðïñåß íá áíáñùôéÝóôå Þäç ðïõ áêñéâþò óôïí
-	  äßóêï óáò õðÜñ÷åé áõôüò ï êáëüò boot manager.  Å ëïéðüí, êÜðïéïé
-	  boot managers åßíáé áñêåôÜ ìéêñïß þóôå íá ÷ùñÝóïõí ìÝóá óôïí Êýñéï
-	  ÔïìÝá Åêêßíçóçò (MBR.  Êýëéíäñïò 0, êåöáëÞ 0, ôïìÝáò 1) ìáæß ìå ôïí
-	  ðßíáêá êáôáôìÞóåùí.  ÊÜðïéïé Üëëïé ÷ñåéÜæïíôáé ðåñéóóüôåñï ÷þñï êáé
-	  ïõóéáóôéêÜ êáôáëáìâÜíïõí áñêåôïýò ôïìåßò ìåôÜ ôïí MBR, ìÝóá óôï
-	  ìïíïðÜôé ìå êýëéíäñï 0 êáé êåöáëÞ 0, áöïý ôõðéêÜ áõôüò ï ÷þñïò åßíáé
-	  åëåýèåñïò&mdash;ôõðéêÜ.</para>
-
-	<para>Åäþ åßíáé êé ç ðáãßäá.  ÊÜðïéá ëåéôïõñãéêÜ óõóôÞìáôá (Ýíá áðü
-	  áõôÜ åßíáé êáé ôï FreeBSD) óáò åðéôñÝðïõí íá îåêéíÞóåôå ôçí
-	  êáôÜôìçóÞ ôïõò áêñéâþò ìåôÜ ôï MBR óôïí êýëéíäñï 0, êåöáëÞ 0, êáé
-	  ôïìÝá 2 áí èÝëåôå.  Ãéá ðáñÜäåéãìá, áí äþóåôå ôï sysinstall
-	  ðñüãñáììá åãêáôÜóôáóçò ôïõ FreeBSD Ýíá äßóêï ìå Üäåéï ÷þñï óôçí áñ÷Þ
-	  ôïõ äßóêïõ Þ Ýíá ôåëåßùò Üäåéï äßóêï, åêåß èá ðñïóðáèÞóåé íá âÜëåé
-	  ôçí êáôÜôìçóç ôïõ FreeBSD (ôïõëÜ÷éóôïí áõôü Ýêáíå üôáí ôçí ðÜôçóá
-	  åãþ).  ¸ôóé, üôáí ðÜôå íá óôÞóåôå ôïí boot manager óáò, áí ÷ñåéáóôåß
-	  íá ðéÜóåé êÜðïéïõò ôïìåßò áìÝóùò ìåôÜ ôï MBR, èá óâçóôåß ç áñ÷Þ ôçò
-	  ðñþôçò êáôÜôìçóçò ìå äåäïìÝíá.  Óôçí ðåñßðôùóç ôïõ FreeBSD, áõôü
-	  êáôáóôñÝöåé ôçí ðåñéï÷Þ ôïõ disklabel, êÜíïíôáò áäýíáôç ôçí åêêßíçóç
-	  áðü áõôÞ ôçí êáôÜôìçóç.</para>
-
-	<para>Ç åýêïëç ëýóç ãéá íá áðïöýãåôå ôÝôïéá ðñïâëÞìáôá (êáé íá
-	  êñáôÞóåôå ãéá ôïí åáõôü óáò ôçí äõíáôüôçôá ÷ñÞóçò êÜðïéïõ
-	  äéáöïñåôéêïý boot manager óôï ìÝëëïí) åßíáé íá áöÞíåôå ðÜíôá
-	  åëåýèåñï ôï ðñþôï ìïíïðÜôé üôáí öôéÜ÷íåôå êÜðïéåò êáôáôìÞóåéò óôï
-	  äßóêï óáò.  Ìå ëßãá ëüãéá, áöÞóôå åëåýèåñï ôïí ÷þñï áðü ôïí
-	  êýëéíäñï&nbsp;0, êåöáëÞ&nbsp;0, ôïìÝá&nbsp;2 ìÝ÷ñé êáé ôïí
-	  êýëéíäñïnbsp;0, êåöáëÞ&nbsp;1, ôïìÝá&nbsp;1.  ÂáóéêÜ, üôáí öôéÜ÷íåôå
-	  êáôáôìÞóåéò óôçí áñ÷Þ ôïõ äßóêïõ ìå ôï DOS, ôï DOS áöÞíåé áõôü ôïíí
-	  ÷þñï åëåýèåñï (ãé áõôü êáé ðïëëïß boot manager èåùñïýí üôé èá åßíáé
-	  åëåýèåñïò).  Áí öôéÜîåôå ìéá ìéêñÞ êáôÜôìçóç DOS óôçí áñ÷Þ ôïõ
-	  äßóêïõ óáò äåí èá óõíáíôÞóåôå áõôü ôï ðñüâëçìá.  ÐñïóùðéêÜ ì' áñÝóåé
-	  íá äçìéïõñãþ óôçí áñ÷Þ ìéá ìéêñÞ êáôÜôìçóç DOS ìåãÝèïõò 1 MB, êáèþò
-	  Ýôóé áðïöåýãù êáé ôéò áëëáãÝò óôá drive letter ôùí êýñéùí DOS
-	  êáôáôìÞóåþí ìïõ áñãüôåñá áí áëëÜîù ôéò êáôáôìÞóåéò ôïõ äßóêïõ.</para>
-
-	<para>ÁíáöïñéêÜ, ïé ðáñáêÜôù boot managers ÷ñçóéìïðïéïýí ôï Master
-	  Boot Sector áðïèçêåýóïõí äéêü ôïõò êþäéêá Þ/êáé äåäïìÝíá:</para>
-
-	<itemizedlist>
-	  <listitem>
-	    <para>OS-BS 1.35</para>
-	  </listitem>
-
-	  <listitem>
-	    <para>Boot Easy</para>
-	  </listitem>
-
-	  <listitem>
-	    <para>LILO</para>
-	  </listitem>
-	</itemizedlist>
-
-	<para>Áõôïß ïé boot managers ÷ñçóéìïðïéïýí êáé ëßãïõò áêüìá ôïìåßò
-	  ìåôÜ ôï Master Boot Sector:</para>
-
-	<itemizedlist>
-	  <listitem>
-	    <para>OS-BS 2.0 Beta 8 (sectors 2-5)</para>
-	  </listitem>
-
-	  <listitem>
-	    <para>&os2;'s boot manager</para>
-	  </listitem>
-	</itemizedlist>
-      </sect3>
-
-      <sect3>
-	<title>Ôé ãßíåôáé áí ï õðïëïãéóôÞò óáò äåí îåêéíÜåé;</title>
-
-	<para>ÊÜðïéá óôéãìÞ, êáèþò óôÞíåôå äéÜöïñïõò boot managers, ìðïñåß íá
-	  áöÞóåôå ôï MBR óå ôÝôïéá êáôÜóôáóç ðïõ íá ìçí åßíáé äõíáôüí íá
-	  îåêéíÞóåôå ôïí õðïëïãéóôÞ óáò.  Áõôü åßíáé áðßèáíï, áëëÜ ìðïñåß íá
-	  ãßíåé êáèþò áëëÜæåôå êáôáôìÞóåéò ìåôÜ áðü ôçí åãêáôÜóôáóç åíüò boot
-	  manager.</para>
-
-	<para>Áí Ý÷åôå êÜðïéá bootable DOS êáôÜôìçóç óôïí äßóêï óáò, ìðïñåßôå
-	  íá îåêéíÞóåôå ìå ìéá äéóêÝôôá åêêßíçóçò DOS êáé íá ôñÝîåôå:</para>
-
-	<informalexample>
-	  <screen>A:\> <userinput>FDISK /MBR</userinput></screen>
-	</informalexample>
-
-	<para>ãéá íá åðáíáöÝñåôå ôïí áñ÷éêü, áðëü êþäéêá åêêßíçóçò ôïõ DOS óôï
-	  óýóôçìÜ óáò.  Ìðïñåßôå ôüôå íá îåêéíÞóåôå ìå ôï DOS (êáé ìüíï ìå ôï
-	  DOS) áðü ôï óêëçñü óáò äßóêï.  ÅíáëëáêôéêÜ, ìðïñåßôå íá îáíáôñÝîåôå
-	  ôï ðñüãñáììá åãêáôÜóôáóçò ôïõ boot manager óáò áðü ìéá äéóêÝôôá
-	  åêêßíçóçò.</para>
-      </sect3>
-    </sect2>
-  </sect1>
-</article>
diff --git a/el_GR.ISO8859-7/books/faq/book.sgml b/el_GR.ISO8859-7/books/faq/book.sgml
index 376be73920..7cde7f7d33 100644
--- a/el_GR.ISO8859-7/books/faq/book.sgml
+++ b/el_GR.ISO8859-7/books/faq/book.sgml
@@ -1349,18 +1349,6 @@ File: +DESC (ignored)</screen>
       </qandaentry>
 
       <qandaentry>
-	<question id="multiboot">
-	  <para>Ìðïñþ íá Ý÷ù ðåñéóóüôåñá áðü Ýíá ëåéôïõñãéêÜ óõóôÞìáôá óôïí
-	    õðïëïãéóôÞ ìïõ;</para>
-	</question>
-
-	<answer>
-	  <para>Ñßîôå ìéá ìáôéÜ óôçí <ulink
-	      url="&url.articles.multi-os;/index.html">óåëßäá ðïëëáðëþí ëåéôïõñãéêþí</ulink>.</para>
-	</answer>
-      </qandaentry>
-
-      <qandaentry>
 	<question id="windows-coexist">
 	  <para>Ìðïñïýí íá óõíõðÜñîïõí ôá  &windows; ìå ôï &os;;</para>
 	</question>
@@ -5196,18 +5184,6 @@ kern.sched.name: 4BSD</screen>
 
     <qandaset>
       <qandaentry>
-        <question id="adding-disks">
-          <para>How can I add my new hard disk to my FreeBSD system?</para>
-        </question>
-
-        <answer>
-          <para>See the Disk Formatting Tutorial at <ulink
-            url="&url.articles.formatting-media;/index.html">
-            www.FreeBSD.org</ulink>.</para>
-        </answer>
-      </qandaentry>
-
-      <qandaentry>
         <question id="new-huge-disk">
           <para>How do I move my system over to my huge new disk?</para>
         </question>
@@ -5229,10 +5205,7 @@ kern.sched.name: 4BSD</screen>
             and &man.disklabel.8;.  You should also install booteasy
             on both disks with &man.boot0cfg.8;, so that you can
             dual boot to the old or new system after the copying
-            is done.  See the <ulink
-            url="&url.articles.formatting-media;/index.html">
-            formatting-media article</ulink> for details on this
-            process.</para>
+            is done.</para>
 
           <para>Now you have the new disk set up, and are ready
             to move the data.  Unfortunately, you cannot just blindly
diff --git a/en_US.ISO8859-1/articles/5-roadmap/Makefile b/en_US.ISO8859-1/articles/5-roadmap/Makefile
deleted file mode 100644
index a2a3804255..0000000000
--- a/en_US.ISO8859-1/articles/5-roadmap/Makefile
+++ /dev/null
@@ -1,19 +0,0 @@
-#
-# $FreeBSD$
-#
-# Article: FreeBSD 5-STABLE roadmap
-
-DOC?= article
-
-FORMATS?= html
-WITH_ARTICLE_TOC?= YES
-
-INSTALL_COMPRESSED?= gz
-INSTALL_ONLY_COMPRESSED?=
-
-SRCS=	article.sgml
-
-CSS_SHEET_ADDITIONS= extra.css
-
-DOC_PREFIX?= ${.CURDIR}/../../..
-.include "${DOC_PREFIX}/share/mk/doc.project.mk"
diff --git a/en_US.ISO8859-1/articles/5-roadmap/article.sgml b/en_US.ISO8859-1/articles/5-roadmap/article.sgml
deleted file mode 100644
index ba5b06dcab..0000000000
--- a/en_US.ISO8859-1/articles/5-roadmap/article.sgml
+++ /dev/null
@@ -1,633 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1" standalone="no"?>
-<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V4.2-Based Extension//EN"
-	"../../../share/sgml/freebsd42.dtd" [
-<!ENTITY % entities PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Entity Set//EN" "../../share/sgml/entities.ent">
-%entities;
-
-<!ENTITY t.releng.3 "<literal>RELENG_3</literal>">
-<!ENTITY t.releng.4 "<literal>RELENG_4</literal>">
-<!ENTITY t.releng.5 "<literal>RELENG_5</literal>">
-<!ENTITY t.releng.5.1 "<literal>RELENG_5_1</literal>">
-<!ENTITY t.releng.5.2 "<literal>RELENG_5_2</literal>">
-<!ENTITY t.releng.5.3 "<literal>RELENG_5_3</literal>">
-<!ENTITY t.releng.head "<literal>HEAD</literal>">
-]>
-
-<article lang='en'>
-  <articleinfo>
-    <title>The Road Map for 5-STABLE</title>
-
-    <authorgroup>
-      <corpauthor>The &os; Release Engineering Team</corpauthor>
-    </authorgroup>
-
-    <copyright>
-      <year>2003</year>
-      <holder role="mailto:re@FreeBSD.org">The &os; Release
-        Engineering Team</holder>
-    </copyright>
-
-    <legalnotice id="trademarks" role="trademarks">
-      &tm-attrib.freebsd;
-      &tm-attrib.ieee;
-      &tm-attrib.intel;
-      &tm-attrib.sparc;
-      &tm-attrib.sun;
-      &tm-attrib.opengroup;
-      &tm-attrib.general;
-    </legalnotice>
-
-    <pubdate>$FreeBSD$</pubdate>
-
-    <releaseinfo>$FreeBSD$</releaseinfo>
-
-    <abstract>
-      <para> This document is now mostly of historical value.  It
-	presented a roadmap for the development of &os;'s &t.releng.5;
-	branch.  It was originally written in February 2003 (between
-	the 5.0 and 5.1 releases), and was intended to provide a plan
-	for making the &t.releng.5; branch <quote>stable</quote>, both
-	in terms of code quality and finalization of various
-	APIs/ABIs.  For a different perspective, the article
-	<ulink url="&url.articles.version-guide;">
-	  <quote>Choosing the &os; Version That Is Right For You</quote>
-	</ulink>
-	may be of interest.  The version-guide article was written in August
-	2005 (two and a half years later), and it contains a section
-	discussing how these plans and events actually unfolded, as well as
-	some lessons learned.</para>
-    </abstract>
-
-  </articleinfo>
-
-  <sect1 id="intro">
-    <title>Introduction and Background</title>
-
-    <para>After nearly three years of work, &os; 5.0 was released in January
-      of 2003.  Features like the GEOM block layer, Mandatory Access Controls,
-      ACPI, &sparc64; and ia64 platform support, and UFS snapshots, background
-      filesystem checks, and 64-bit inode sizes make it an exciting operating
-      system for both desktop and enterprise users.  However, some important
-      features are not complete.  The foundations for fine-grained locking
-      and preemption in the kernel exist, but much more work is left to be
-      done.  Performance and stability compared to &os;
-      4.<replaceable>X</replaceable> has declined and must be restored and
-      surpassed.</para>
-
-    <para>This is somewhat similar to the situation that &os; faced in the
-      3.<replaceable>X</replaceable> series.  Work on 3-CURRENT trudged along
-      seemingly forever, and finally a cry was made to <quote>just ship
-      it</quote> and clean up later.  This decision resulted in the 3.0 and
-      3.1 releases being very unsatisfying for most, and it was not until 3.2
-      that the series was considered <quote>stable</quote>.  To make matters
-      worse, the &t.releng.3; branch was created along with the 3.0 release,
-      and the &t.releng.head; branch was allowed to advance immediately
-      towards 4-CURRENT.  This resulted in a quick divergence between
-      &t.releng.head; and &t.releng.3;, making maintenance of the &t.releng.3;
-      branch very difficult.  &os; 2.2.8 was left for quite a while as the
-      last production-quality version of &os;.</para>
-
-    <para>Our intent is to avoid repeating that scenario with &os; 5.X.
-      Delaying the &t.releng.5; branch until it is stable and production quality
-      will ensure that it stays maintainable and provides a compelling reason
-      to upgrade from 4.<replaceable>X</replaceable>.  To do this, we must
-      identify the current areas of weakness and set clear goals for
-      resolving them.  This document contains what we as the release
-      engineering team feel are the milestones and issues that must be
-      resolved for the &t.releng.5; branch.  It does not dictate every aspect of
-      &os; development, and we welcome further input.  Nothing that follows
-      is meant to be a sleight against any person or group, or to trivialize
-      any work that has been done.  There are some significant issues,
-      though, that need decisive and unbiased action.</para>
-  </sect1>
-
-  <sect1 id="major-issues">
-    <title>Major issues</title>
-
-    <para>The success of the 5.<replaceable>X</replaceable> series hinges on
-      the ability to deliver fine-grained threading and re-entrancy in the
-      kernel (also known as SMPng) and kernel-supported POSIX threads in
-      userland, while not sacrificing overall system stability or
-      performance.</para>
-
-  <sect2 id="SMPng">
-    <title>SMPng</title>
-
-    <para>The state of SMPng and kernel lockdown is the biggest concern for
-      5.<replaceable>X</replaceable>.  To date, few major systems have come
-      out from under the kernel-wide mutex known as <quote>Giant</quote>.
-      The SMP status page at <ulink url="&url.base;/smp"></ulink>
-      provides a comprehensive breakdown
-      of the overall SMPng status.  Status specific to SMPng progress in
-      device drivers can be found at
-      <ulink url="&url.base;/projects/busdma"></ulink>.
-      In summary:</para>
-
-    <itemizedlist>
-      <listitem>
-        <para>VM: Kernel malloc is locked and free of Giant.  The UMA zone
-          allocator is also free of Giant.  vm_object locking is in progress
-          and is an important step to making the buffer/cache free of
-	  Giant.  Pmap locking remains to be started.</para>
-      </listitem>
-
-      <listitem>
-        <para>GEOM: The GEOM block layer was designed to run free of Giant
-	  and allow GEOM modules and underlying block drivers to run free
-	  of Giant.  Currently, only the &man.ata.4; and &man.aac.4; drivers
-	  are locked and run without Giant.  Work on other block drivers is
-	  in progress.  Locking the CAM subsystem is required for nearly all
-	  SCSI drivers to run without Giant; this work has not started
-	  yet.</para>
-	<para>Additionally, GEOM has the potential to suffer performance loss
-	  due to its upcall and downcall data paths happening in kernel threads.
-	  Improved lightweight context switches might help this.</para>
-      </listitem>
-
-      <listitem>
-        <para>Network: Work has restarted on locking the network stack.
-	  Routing tables, ARP, bridge, IPFW, Fast-Forward, TCP, UDP, IP,
-	  Fast IPSEC, and interface layers are being targeted initially, along
-          with several Ethernet device drivers.  The socket layer, IPv6, and
-          other protocol layers will be targeted later.  The primary goal
-          of this work is to regain the performance found in
-          &os; 4.<replaceable>X</replaceable>.  The cost of context switching
-          to the device driver ithreads and the netisr is still hampering
-          performance.</para>
-      </listitem>
-
-      <listitem>
-        <para>VFS: Initial pre-cleanup started.</para>
-      </listitem>
-
-      <listitem>
-        <para>buffer/cache: Initial work complete on locking the buffer.</para>
-      </listitem>
-
-      <listitem>
-        <para>Proc: Initial proc locking is in place, further progress is
-	  expected for &os; 5.2.</para>
-      </listitem>
-
-      <listitem>
-        <para>CAM: No significant work has occurred on the CAM SCSI
-          layer.</para>
-      </listitem>
-
-      <listitem>
-        <para>Newbus: some work has started on locking down the device_t
-          structure.</para>
-      </listitem>
-
-      <listitem>
-        <para>Pipes: complete</para>
-      </listitem>
-
-      <listitem>
-        <para>File descriptors: complete.</para>
-      </listitem>
-
-      <listitem>
-        <para>Process accounting: jails, credentials, MAC labels, and
-          scheduler are out from under Giant.</para>
-      </listitem>
-
-      <listitem>
-        <para>MAC Framework: complete</para>
-      </listitem>
-
-      <listitem>
-         <para>Timekeeping: complete</para>
-      </listitem>
-
-      <listitem>
-        <para>kernel encryption: crypto drivers and core &man.crypto.4;
-	  framework are Giant-free.  KAME IPsec has not been locked.</para>
-      </listitem>
-
-      <listitem>
-        <para>Sound subsystem: complete, but lock order reversal problems seem
-	  to persist.</para>
-      </listitem>
-
-      <listitem>
-        <para>kernel preemption: preemption for interrupt threads is enabled.
-          However, contention due to Giant covering much of the kernel and
-          most of the device driver interrupt routines causes excessive
-          context switches and might actually be hurting performance.  Work
-          is underway to explore ways to make preemption be
-          conditional.</para>
-      </listitem>
-    </itemizedlist>
-
-  </sect2>
-
-  <sect2 id="interrupts">
-    <title>Interrupt latency and servicing</title>
-
-    <para>SMPng introduced the concept of dedicating kernel threads, known as
-      ithreads, to servicing interrupts.  With this, driver interrupt
-      service routines are allowed to block for mutexes, memory allocations,
-      etc.  While this makes writing drivers easier, it introduces considerable
-      latency into the system due to the complete process context switch which must
-      be performed in order to service the ithread.  This is aggravated by the
-      extensive coverage over the kernel by the Giant mutex, and often results
-      in multiple sleeps and context switches in order to service an interrupt.
-      Drivers that register their interrupt as INTR_MPSAFE are less likely to
-      feel these aggravating effects, but the overhead of doing a context
-      switch remains.  Interrupt service routines that are registered as
-      INTR_FAST are run directly from the interrupt context and do not suffer
-      these problems at all.  However, the INTR_FAST property forces the
-      interrupt line to be exclusive; no sharing can occur on it.  The
-      proliferation of shared interrupts on PC systems makes this
-      undesirable.</para>
-
-    <para>Several ideas have been proposed to help combat this problem:</para>
-    <itemizedlist>
-      <listitem>
-        <para>Special casing ithreads to be lightweight is a possibility.  This
-          might involve reducing the amount of saved context for the ithread,
-          stack-borrowing from another kthread, and/or creating a new fast-path
-          to avoid the mi_switch() routine.</para>
-      </listitem>
-
-      <listitem>
-        <para>A new interrupt model can be introduced to allow drivers to
-          register an 'interrupt filter' along with a normal service routine.
-          This would be similar to the Mac OS X model in use today.  Interrupt
-          filter routines would allow the driver to determine if it is
-          interested in servicing the interrupt, allow it to squelch the
-          interrupt source, and possibly determine and schedule service
-          actions.  It would run in the same context as the low-level interrupt
-          service routine, so sleeping would be strictly forbidden.  If actions
-          that result in sleeping or blocking for long periods are required,
-          the filter would signal to the caller that its normal ithread routine
-          should be scheduled.</para>
-      </listitem>
-    </itemizedlist>
-
-  </sect2>
-
-  <sect2 id="KSE">
-    <title>Kernel-supported application threads</title>
-
-    <para>The FreeBSD 5.1 development cycle saw the KSE package jump into a
-      highly usable state. THR, an alternate threading package based on some
-      of the KSE kernel primitives but implementing purely 1:1 scheduling
-      semantics also appeared and is in a similarly experimental but usable
-      state. Users may interchange these two libraries along with the legacy
-      libc_r library via relinking their apps or by using the new libmap
-      feature of the runtime linker. This excellent progress must be driven
-      to completion before the &t.releng.5; branch point so that the libc_r
-      package can be deprecated.</para>
-
-    <itemizedlist>
-      <listitem>
-        <para>The kernel and userland components for KSE and THR must be
-          completed for all Tier-1 platforms.  The decision on which thread
-          package to sanction as the default will likely be made on a
-          per-platform basis depending on the stability and completeness of
-          each package.</para>
-
-        <para>
-          <table id="KSETable">
-            <title>KSE Status</title>
-            <tgroup cols="4">
-              <thead>
-                <row>
-                  <entry>Platform</entry>
-                  <entry>Kernel</entry>
-                  <entry>Userland</entry>
-                  <entry>Works?</entry>
-                </row>
-              </thead>
-
-              <tbody>
-                <row>
-                  <entry>i386</entry>
-                  <entry>YES</entry>
-                  <entry>YES</entry>
-                  <entry>YES</entry>
-                </row>
-
-                <row>
-                  <entry>alpha</entry>
-                  <entry>NO</entry>
-                  <entry>YES</entry>
-                  <entry>NO</entry>
-                </row>
-
-                <row>
-                  <entry>sparc64</entry>
-                  <entry>YES</entry>
-                  <entry>NO</entry>
-                  <entry>NO</entry>
-                </row>
-
-                <row>
-                  <entry>ia64</entry>
-                  <entry>YES</entry>
-                  <entry>YES</entry>
-                  <entry>YES</entry>
-                </row>
-
-                <row>
-                  <entry>amd64</entry>
-                  <entry>YES</entry>
-                  <entry>YES</entry>
-                  <entry>YES</entry>
-                </row>
-              </tbody>
-            </tgroup>
-          </table>
-
-          <table id="THRTable">
-            <title>THR Status</title>
-            <tgroup cols="4">
-              <thead>
-                <row>
-                  <entry>Platform</entry>
-                  <entry>Kernel</entry>
-                  <entry>Userland</entry>
-                  <entry>Works?</entry>
-                </row>
-              </thead>
-
-              <tbody>
-                <row>
-                  <entry>i386</entry>
-                  <entry>YES</entry>
-                  <entry>YES</entry>
-                  <entry>YES</entry>
-                </row>
-
-                <row>
-                  <entry>alpha</entry>
-                  <entry>YES</entry>
-                  <entry>YES</entry>
-                  <entry>YES</entry>
-                </row>
-
-                <row>
-                  <entry>sparc64</entry>
-                  <entry>YES</entry>
-                  <entry>YES</entry>
-                  <entry>NO</entry>
-                </row>
-
-                <row>
-                  <entry>ia64</entry>
-                  <entry>YES</entry>
-                  <entry>YES</entry>
-                  <entry>YES</entry>
-                </row>
-
-                <row>
-                  <entry>amd64</entry>
-                  <entry>NO</entry>
-                  <entry>NO</entry>
-                  <entry>NO</entry>
-                </row>
-              </tbody>
-            </tgroup>
-          </table>
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>KSE must pass the ACE test suite on all Tier-1 platforms.
-          Additional real-world testing must also be performed to ensure
-          that the libraries are indeed useful.  At a minimum, the following
-          packages should be tested:</para>
-        <itemizedlist>
-          <listitem><para>OpenOffice</para></listitem>
-          <listitem><para>KDE Desktop</para></listitem>
-          <listitem><para>Apache 2.x</para></listitem>
-          <listitem><para>BIND 9.2.x</para></listitem>
-          <listitem><para>MySQL</para></listitem>
-          <listitem><para>&java; 1.4.x</para></listitem>
-        </itemizedlist>
-      </listitem>
-
-    </itemizedlist>
-
-  </sect2>
-  </sect1>
-
-  <sect1 id="goals">
-    <title>Requirements for 5-STABLE</title>
-
-    <para>The &t.releng.5; branch must offer users the same stability and
-      performance that is currently enjoyed in the &t.releng.4; branch.
-      While the goal of SMPng is to allow performance to far exceed what
-      is found in &t.releng.4; and its sibling BSDs, regaining performance
-      to the basic level is of the utmost importance.  The branch must also
-      be mature enough to avoid ABI and API changes while still allowing
-      potential problems to be resolved.</para>
-
-    <sect2 id="API">
-      <title>ABI/API/Infrastructure stability</title>
-        <para>Enough infrastructure must be in place and stable to allow
-          fixes from &t.releng.head; to easily and safely be merged into
-          &t.releng.5;.  Also, we must draw a line as to what subsystems are
-          to be locked down when we go into 5-STABLE.</para>
-
-      <itemizedlist>
-        <listitem>
-          <para>KSE:  Both kernel and userland components must
-            reach the same level of functionality for all Tier-1 platforms,
-            in both UP and SMP configurations.  The definition of <quote>Tier-1
-            platforms</quote> can be found in
-	    <ulink url="&url.articles.committers-guide;/archs.html"></ulink>.
-	    Continued testing against the ACE test
-            suite must be made as the &t.releng.5; branch draws near.  KSE
-            must pose no functional regressions for the ongoing &java;
-            certification program.  Common desktop and server applications
-            must run seamlessly under KSE.  A policy must be decided on as
-            to which platforms will enable KSE as the default threading
-            package, how to allow the user to switch threading packages, and
-            how third-party packages will be made aware of these choices.</para>
-        </listitem>
-
-        <listitem>
-          <para>busdma interface and drivers: architectures like PAE/&i386; and
-            sparc64 which do not have a direct mapping between host memory
-            address space and expansion bus address space require the
-            elimination of vtophys() and friends.  The busdma interface was
-            created to handle exactly this problem, but many drivers do not use
-            it yet.  The busdma project at
-            <ulink url="&url.base;/projects/busdma"></ulink>
-            tracks the
-            progress of this and should be used to determine which drivers
-            must be converted for &t.releng.5; and which can be left behind.
-            No new storage or network drivers shall be allowed into the
-            &os; source tree.  Exceptions for other classes of drivers must
-            be justified in public discussion.</para>
-        </listitem>
-
-        <listitem>
-          <para>PCI resource allocation: PC2003 compliance requires that x86
-            systems no longer configure PCI devices from the system BIOS,
-            leaving this task solely to the OS.  &os; must gain the ability to
-            manage and allocate PCI memory resources on its own.  Implementing
-            this should take into account cardbus, PCI-HotPlug, and laptop
-            docking-station requirements.  This feature will become increasingly
-            critical through the lifetime of &t.releng.5;, and therefore is a
-            requirement for the &t.releng.5; branch.</para>
-        </listitem>
-      </itemizedlist>
-    </sect2>
-
-    <sect2 id="performance">
-    <title>Performance</title>
-      <para>Performance hinges on the progress of SMPng infrastructure in
-        the following areas:</para>
-
-      <itemizedlist>
-        <listitem>
-          <para>Storage:  The GEOM block layer allows storage drivers to
-            run without Giant.  All drivers that interface directly with
-            GEOM (as opposed to sitting underneath CAM or another middleware)
-            must be locked and free of Giant in both their strategy and
-            completion paths.  Their interrupt handlers must also run free
-            of Giant.</para>
-        </listitem>
-
-        <listitem>
-          <para>Network:  The layers in the IPv4 path below the socket layer
-            must be locked and free of Giant. This includes the protocol,
-            routing, bridging, filtering, and hardware layers. Allowances must
-            be made for protocols that are not locked, especially IPv6.
-            Testing must also be performed to ensure stability, correctness,
-            and performance.</para>
-        </listitem>
-
-        <listitem>
-          <para>Interrupt and context switching:  As discussed above, interrupt
-            latency and context switching have a severe impact of performance.
-            Context switching for ithreads and kthreads must be improved.
-            New interrupt handling models that allow for faster and
-            more flexible handling of both traditional and MSI interrupts must
-            be investigated and implemented.</para>
-        </listitem>
-      </itemizedlist>
-    </sect2>
-
-    <sect2 id="benchmarks">
-    <title>Benchmarks and performance testing</title>
-      <para>Having a source of reliable and useful benchmarks is essential
-        to identifying performance problems and guarding against performance
-        regressions.  A <quote>performance team</quote> that is made up of
-        people and resources for formulating, developing, and executing
-        benchmark tests should be put into place soon.  Comparisons should
-        be made against both &os; 4.<replaceable>X</replaceable> and Linux
-        2.4/2.6.  Tests to consider are:</para>
-
-      <itemizedlist>
-        <listitem>
-          <para>the classic <quote>worldstone</quote></para>
-        </listitem>
-
-        <listitem>
-          <para>webstone: <filename role="package">www/webstone</filename></para>
-        </listitem>
-
-        <listitem>
-          <para>Fstress: <ulink url="http://www.cs.duke.edu/ari/fstress/"></ulink></para>
-        </listitem>
-
-        <listitem>
-          <para>ApacheBench: <filename role="package">www/p5-ApacheBench</filename></para>
-        </listitem>
-
-        <listitem>
-          <para>netperf: <filename role="package">benchmarks/netperf</filename></para>
-        </listitem>
-
-        <listitem>
-          <para>Web Polygraph: <ulink url="http://www.web-polygraph.org/"></ulink>
-            Note: does not compile with gcc 3.x yet.</para>
-        </listitem>
-      </itemizedlist>
-    </sect2>
-
-    <sect2 id="features">
-    <title>Features:</title>
-
-      <itemizedlist>
-        <listitem>
-          <para>NEWCARD/OLDCARD: The NEWCARD subsystem was made the default
-            for &os;&nbsp;5.0.  Unfortunately, it does not include support for
-            non-Cardbus bridges and falls victim to interrupt routing
-            problems on some laptops.  The classic 16-bit bridge support,
-            OLDCARD, still exists and can be compiled in, but this is highly
-            inconvenient for users of older laptops.  If OLDCARD cannot be
-            completely deprecated for &t.releng.5;, then provisions must be made
-            to allow users to easily install an OLDCARD-enabled kernel.
-            Documentation should be written to help transition users from
-            OLDCARD to NEWCARD and from &man.pccardd.8; to
-            &man.devd.8;.  The power management and
-            <quote>dumpcis</quote> functionality of &man.pccardc.8; needs to be
-            brought forward to work with NEWCARD, along with the ability to
-            load CIS quirk entries.  Most of this functionality can be
-            integrated into &man.devd.8; and
-            &man.devctl.4;.</para>
-        </listitem>
-
-        <listitem>
-          <para>New scheduler framework: The new scheduler framework is in
-            place, and users can select between the classic 4BSD scheduler
-            and the new ULE scheduler.  A scheduler that demonstrates
-            processor affinity, HyperThreading and KSE awareness, and no
-            regressions in performance or interactivity characteristics must
-            be available for &t.releng.5;.</para>
-        </listitem>
-
-        <listitem>
-           <para>GDB: GDB in the base system must work for sparc64, and
-             must also understand KSE thread semantics.  GDB 5.3 is available
-             and is reported to address the sparc64 issues.</para>
-        </listitem>
-
-      </itemizedlist>
-    </sect2>
-
-    <sect2 id="documentation">
-    <title>Documentation:</title>
-
-      <itemizedlist>
-        <listitem>
-          <para>The manual pages, Handbook, and FAQ should be free from
-            content specific to &os; 4.<replaceable>X</replaceable>, i.e. all
-            text should be equally applicable to &os;
-            5.<replaceable>X</replaceable>.  The installation section of the
-            handbook needs the most work in this area.</para>
-        </listitem>
-
-        <listitem>
-          <para>The release documentation needs to be complete and accurate
-            for all Tier-1 architectures.  The hardware notes and
-            installation guides need specific attention.</para>
-        </listitem>
-      </itemizedlist>
-    </sect2>
-  </sect1>
-
-  <sect1 id="future">
-    <title>Post &t.releng.5; direction</title>
-
-    <para>The focus should be bug fixes and incremental improvements, as with
-      all the -STABLE development branches.  Following the usual procedure,
-      everything should be vetted through the &t.releng.head; branch first and
-      committed to &t.releng.5; with caution.  New device drivers, incremental
-      features, etc, will be welcome in the branch once they have been tested
-      in &t.releng.head; and found stable enough.</para>
-
-    <para>Further SMPng lockdowns will be divided into two categories: driver
-      and subsystem.  The only subsystem that will be sufficiently locked
-      down for &t.releng.5; will be GEOM, so incrementally locking down device
-      drivers under it is a worthy goal for the branch.  Full subsystem
-      lockdowns will have to be fully tested and proven in &t.releng.head; before
-      consideration will be given to merging them into &t.releng.5;.</para>
-  </sect1>
-</article>
diff --git a/en_US.ISO8859-1/articles/5-roadmap/extra.css b/en_US.ISO8859-1/articles/5-roadmap/extra.css
deleted file mode 100644
index 8d13ebf887..0000000000
--- a/en_US.ISO8859-1/articles/5-roadmap/extra.css
+++ /dev/null
@@ -1,16 +0,0 @@
-/*
- * Netscape 4 does not recognize the @import directive of CSS, so we
- * can't add an additional stylesheet layer on top of the default one.
- * Instead, we use this hack to copy this file to the end of
- * docbook.css. 
- *
- * $FreeBSD$
- */
-
-/* @import "docbook.css"; */
-
-/* Customization that looks good for this particular article. */
-
-DIV.TITLEPAGE {
-	text-align: center;
-}
diff --git a/en_US.ISO8859-1/articles/Makefile b/en_US.ISO8859-1/articles/Makefile
index 688669a66e..e1caf23579 100644
--- a/en_US.ISO8859-1/articles/Makefile
+++ b/en_US.ISO8859-1/articles/Makefile
@@ -1,11 +1,9 @@
 # $FreeBSD$
 
 SUBDIR =
-SUBDIR+= 5-roadmap
 SUBDIR+= bsdl-gpl
 SUBDIR+= building-products
 SUBDIR+= casestudy-argentina.com
-SUBDIR+= checkpoint
 SUBDIR+= committers-guide
 SUBDIR+= compiz-fusion
 SUBDIR+= console-server
@@ -16,14 +14,10 @@ SUBDIR+= cups
 SUBDIR+= custom-gcc
 SUBDIR+= cvs-freebsd
 SUBDIR+= cvsup-advanced
-SUBDIR+= dialup-firewall
-SUBDIR+= diskless-x
-SUBDIR+= euro
 SUBDIR+= explaining-bsd
 SUBDIR+= fbsd-from-scratch
 SUBDIR+= filtering-bridges
 SUBDIR+= fonts
-SUBDIR+= formatting-media
 SUBDIR+= freebsd-questions
 SUBDIR+= freebsd-update-server
 SUBDIR+= geom-class
@@ -37,7 +31,6 @@ SUBDIR+= linux-emulation
 SUBDIR+= linux-users
 SUBDIR+= mailing-list-faq
 SUBDIR+= mh
-SUBDIR+= multi-os
 SUBDIR+= nanobsd
 SUBDIR+= new-users
 SUBDIR+= p4-primer
@@ -53,12 +46,8 @@ SUBDIR+= releng-packages
 SUBDIR+= remote-install
 SUBDIR+= serial-uart
 SUBDIR+= solid-state
-SUBDIR+= storage-devices
-SUBDIR+= version-guide
-SUBDIR+= vinum
 SUBDIR+= vm-design
 SUBDIR+= wp-toolbox
-SUBDIR+= zip-drive
 
 # ROOT_SYMLINKS+= new-users
 
diff --git a/en_US.ISO8859-1/articles/checkpoint/Makefile b/en_US.ISO8859-1/articles/checkpoint/Makefile
deleted file mode 100644
index 6e8f8b025d..0000000000
--- a/en_US.ISO8859-1/articles/checkpoint/Makefile
+++ /dev/null
@@ -1,18 +0,0 @@
-#
-# $FreeBSD$
-#
-# Article: Integration of Check Point Firewall-1 and FreeBSD IPsec
-
-DOC?= article
-
-FORMATS?= html
-
-INSTALL_COMPRESSED?=gz
-INSTALL_ONLY_COMPRESSED?=
-
-SRCS=		article.sgml
-IMAGES_EN=	networks.pic
-
-URL_RELPREFIX?=	../../../..
-DOC_PREFIX?= ${.CURDIR}/../../..
-.include "${DOC_PREFIX}/share/mk/doc.project.mk"
diff --git a/en_US.ISO8859-1/articles/checkpoint/article.sgml b/en_US.ISO8859-1/articles/checkpoint/article.sgml
deleted file mode 100644
index acebd7a8f7..0000000000
--- a/en_US.ISO8859-1/articles/checkpoint/article.sgml
+++ /dev/null
@@ -1,435 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1" standalone="no"?>
-<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V4.2-Based Extension//EN"
-	"../../../share/sgml/freebsd42.dtd" [
-<!ENTITY % entities PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Entity Set//EN" "../../share/sgml/entities.ent">
-%entities;
-]>
-
-<!-- Copyright (c) 2001 The FreeBSD Documentation Project
-
-     Redistribution and use in source (SGML DocBook) and 'compiled' forms
-     (SGML, HTML, PDF, PostScript, RTF and so forth) with or without
-     modification, are permitted provided that the following conditions
-     are met:
-
-      1. Redistributions of source code (SGML DocBook) must retain the above
-         copyright notice, this list of conditions and the following
-         disclaimer as the first lines of this file unmodified.
-
-      2. Redistributions in compiled form (transformed to other DTDs,
-         converted to PDF, PostScript, RTF and other formats) 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 DOCUMENTATION IS PROVIDED BY THE FREEBSD DOCUMENTATION PROJECT "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 NIK CLAYTON 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 DOCUMENTATION, EVEN IF ADVISED OF THE
-     POSSIBILITY OF SUCH DAMAGE.
--->
-
-<article lang='en'>
-  <articleinfo>
-    <title>Integration of Check Point <trademark class='registered'>VPN-1</trademark>/<trademark class='registered'>Firewall-1</trademark> and FreeBSD IPsec</title>
-
-    <authorgroup>
-      <author>
-	<firstname>Jon</firstname>
-	<surname>Orbeton</surname>
-
-	<affiliation>
-	  <address><email>jono@securityreports.com</email></address>
-	</affiliation>
-      </author>
-
-      <author>
-	<firstname>Matt</firstname>
-	<surname>Hite</surname>
-
-	<affiliation>
-	  <address><email>mhite@hotmail.com</email></address>
-	</affiliation>
-      </author>
-    </authorgroup>
-
-    <copyright>
-      <year>2001</year>
-      <year>2002</year>
-      <year>2003</year>
-      <holder role="mailto:jono@securityreports.com">Jon Orbeton</holder>
-    </copyright>
-
-    &legalnotice;
-
-    <legalnotice id="trademarks" role="trademarks">
-      &tm-attrib.freebsd;
-      &tm-attrib.check-point;
-      &tm-attrib.general;
-    </legalnotice>
-
-    <pubdate>$FreeBSD$</pubdate>
-
-    <releaseinfo>$FreeBSD$</releaseinfo>
-
-    <abstract>
-      <para>This document explains how to configure a <acronym>VPN</acronym>
-	tunnel between FreeBSD and Check Point's
-	<trademark class='registered'>VPN-1</trademark>/
-	<trademark class='registered'>Firewall-1</trademark>.  Other
-	documents provide similar information, but do not contain instructions
-	specific to VPN-1/Firewall-1 and its integration with FreeBSD.  These
-	documents are listed at the conclusion of this paper for further
-	reference.</para>
-    </abstract>
-  </articleinfo>
-
-  <sect1 id="prerequisites">
-    <title>Prerequisites</title>
-
-    <para>The following is a diagram of the machines and networks referenced
-      in this document.</para>
-
-    <mediaobject>
-      <imageobject>
-        <imagedata fileref="networks"/>
-      </imageobject>
-
-      <textobject>
-        <literallayout class="monospaced">External Interface                    External Interface
-           208.229.100.6                    216.218.197.2
-                       |                    |
-         +--&gt; Firewall-1 &lt;--&gt; Internet &lt;--&gt; FreeBSD GW &lt;--+
-         |                                                |
-FW-1 Protected Nets                              Internal Nets
-199.208.192.0/24                               192.168.10.0/24</literallayout>
-      </textobject>
-
-      <textobject>
-        <phrase>FW-1 net and FreeBSD net</phrase>
-      </textobject>
-    </mediaobject>
-
-    <para>The FreeBSD gateway <acronym>GW</acronym> serves as a firewall and
-      <acronym>NAT</acronym> device for <quote>internal nets.</quote></para>
-
-    <para>The FreeBSD kernel must be compiled to support IPsec.  Use the
-      following kernel options to enable IPsec support in your kernel:</para>
-
-<programlisting>options         IPSEC
-options         IPSEC_ESP
-options         IPSEC_DEBUG</programlisting>
-
-    <para>For instructions on building a custom kernel, refer to the
-      <ulink url="&url.books.handbook;/kernelconfig.html">FreeBSD
-	handbook</ulink>. Please note that <acronym>IP</acronym>
-      protocol&nbsp;50 (<acronym>ESP</acronym>) and <acronym>UDP</acronym>
-      port&nbsp;<literal>500</literal> must be open between the <trademark class='registered'>Firewall-1</trademark>
-      host and the FreeBSD <acronym>GW</acronym>.</para>
-
-    <para>Also, <application>racoon</application> must be installed to support
-      key exchange.  <application>Racoon</application> is part of the FreeBSD
-      ports collection in <filename role="package">security/racoon</filename>.
-      The <application>racoon</application> configuration file will be covered
-      later in this document.</para>
-  </sect1>
-
-  <sect1 id="object">
-      <title>Firewall-1 Network Object Configuration</title>
-
-    <para>Begin by configuring the Firewall-1 Policy.  Open the Policy Editor
-      on the Firewall-1 Management server and create a new
-      <quote>Workstation</quote> Network Object representing FreeBSD
-      <acronym>GW</acronym>.</para>
-
-<programlisting>General Tab:
-		Set name and IP address
-
-VPN Tab:
-		Encryption Schemes Defined:             IKE               ---&gt; Edit
-
-IKE Properties:
-		Key Negotiation Encryption Methods:     3DES
-
-Authentication Method:
-		Pre-Shared Secret ---&gt; Edit</programlisting>
-
-    <para>Select the Firewall Object and set a pre-shared secret.
-      (Do not use our example.)</para>
-
-<programlisting>Support Aggressive Mode:                 Checked
-Supports Subnets:                      Checked</programlisting>
-
-    <para>After setting the pre-shared secret in the Firewall-1 Network Object
-      definition, place this secret in the
-      <filename>/usr/local/etc/racoon/psk.txt</filename> file on FreeBSD
-      <acronym>GW</acronym>.  The format for <filename>psk.txt</filename>
-      is:</para>
-
-<programlisting>208.229.100.6          rUac0wtoo?</programlisting>
-
-  </sect1>
-
-  <sect1 id="rulecfg">
-    <title>Firewall-1 VPN Rule Configuration</title>
-
-    <para>Next, create a Firewall-1 rule enabling encryption between the
-      FreeBSD <acronym>GW</acronym> and the Firewall-1 protected network.
-      In this rule, the network services permitted through the
-      <acronym>VPN</acronym> must be defined.</para>
-
-<programlisting>Source            | Destination        | Service      | Action  | Track
-------------------------------------------------------------------------
-FreeBSD GW        | FW-1 Protected Net | VPN services | Encrypt | Long
-FW-1 Protected Net| FreeBSD GW         |              |         |</programlisting>
-
-    <para><quote>VPN services</quote> are any services (i.e.
-      <command>telnet</command>, <acronym>SSH</acronym>,
-      <acronym>NTP</acronym>, etc.) which remote hosts are permitted to access
-      through the <acronym>VPN</acronym>.  Use caution when permitting
-      services; hosts connecting through a <acronym>VPN</acronym> still
-      represent a potential security risk.  Encrypting the traffic between the
-      two networks offers little protection if a host on either side of the
-      tunnel has been compromised.</para>
-
-    <para>Once the rule specifying data encryption between the FreeBSD
-      <acronym>GW</acronym> and the Firewall-1 protected network has been
-      configured, review the <quote>Action Encrypt</quote> settings.</para>
-
-<programlisting>Encryption Schemes Defined:     IKE ---&gt; Edit
-Transform:                      Encryption + Data Integrity (ESP)
-Encryption Algorithm:           3DES
-Data Integrity:                 MD5
-Allowed Peer Gateway:           Any or Firewall Object
-Use Perfect Forward Secrecy:    Checked</programlisting>
-
-    <para>The use of Perfect Forward Secrecy (<acronym>PFS</acronym>) is
-      optional.  Enabling <acronym>PFS</acronym> will add another layer of
-      encryption security, but does come at the cost of increased
-      <acronym>CPU</acronym> overhead.  If <acronym>PFS</acronym> is not used,
-      uncheck the box above and comment out the
-      <literal>pfs_group&nbsp;1</literal> line in the
-      <filename>racoon.conf</filename> file on FreeBSD <acronym>GW</acronym>.
-      An example <filename>racoon.conf</filename> file is provided later in
-      this document.</para>
-
-  </sect1>
-
-  <sect1 id="policy">
-    <title>FreeBSD <acronym>VPN</acronym> Policy Configuration</title>
-
-    <para>At this point, the <acronym>VPN</acronym> policy on FreeBSD
-      <acronym>GW</acronym> must be defined.  The &man.setkey.8; tool performs
-      this function.</para>
-
-    <para>Below is an example shell script which will flush &man.setkey.8; and
-      add your <acronym>VPN</acronym> policy rules.</para>
-
-<programlisting>#
-# /etc/vpn1-ipsec.sh
-#
-# IP addresses
-#
-#     External Interface                    External Interface
-#       208.229.100.6                       216.218.197.2
-#                   |                       |
-#        +--&gt; Firewall-1 &lt;--&gt; Internet &lt;--&gt; FreeBSD GW &lt;--+
-#        |                                                |
-# FW-1 Protected Nets                              Internal Nets
-#    199.208.192.0/24                                  192.168.10.0/24
-#
-# Flush the policy
-#
-setkey -FP
-setkey -F
-#
-# Configure the Policy
-#
-setkey -c &lt;&lt; END
-spdadd 216.218.197.2/32 199.208.192.0/24 any -P out ipsec
-esp/tunnel/216.218.197.2-208.229.100.6/require;
-spdadd 199.208.192.0/24 216.218.197.2/32 any -P in ipsec
-esp/tunnel/208.229.100.6-216.218.197.2/require;
-END
-#</programlisting>
-
-    <para>Execute the &man.setkey.8; commands:</para>
-
-    <screen>&prompt.root; <userinput>sh /etc/vpn1-ipsec.sh</userinput></screen>
-  </sect1>
-
-  <sect1 id="racoon">
-    <title>FreeBSD <application>Racoon</application> Configuration</title>
-
-    <para>To facilitate the negotiation of IPsec keys on the FreeBSD
-      <acronym>GW</acronym>, the
-      <filename role="package">security/racoon</filename> port must be
-      installed and configured.</para>
-
-    <para>The following is a <application>racoon</application> configuration
-      file suitable for use with the examples outlined in this document.
-      Please make sure you fully understand this file before using it in a
-      production environment.</para>
-
-<programlisting># racoon.conf for use with Check Point VPN-1/Firewall-1
-#
-# search this file for pre_shared_key with various ID key.
-#
-        path pre_shared_key "/usr/local/etc/racoon/psk.txt" ;
-        log debug;
-#
-# "padding" defines some parameter of padding.  You should not touch these.
-#
-        padding
-      {
-        maximum_length 20;      # maximum padding length.
-        randomize off;          # enable randomize length.
-        strict_check off;       # enable strict check.
-        exclusive_tail off;     # extract last one octet.
-      }
-
-        listen
-      {
-        #isakmp ::1 [7000];
-        #isakmp 0.0.0.0 [500];
-        #admin [7002];          # administrative port by kmpstat.
-        #strict_address;        # required all addresses must be bound.
-      }
-#
-# Specification of default various timers.
-#
-        timer
-      {
-#
-# These values can be changed per remote node.
-#
-        counter 5;              # maximum trying count to send.
-        interval 20 sec;        # maximum interval to resend.
-        persend 1;              # the number of packets per a send.
-#
-# timer for waiting to complete each phase.
-#
-        phase1 30 sec;
-        phase2 15 sec;
-      }
-
-        remote anonymous
-      {
-        exchange_mode aggressive,main; # For Firewall-1 Aggressive mode
-
-        #my_identifier address;
-        #my_identifier user_fqdn "";
-        #my_identifier address "";
-        #peers_identifier address "";
-        #certificate_type x509 "" "";
-
-        nonce_size 16;
-        lifetime time 10 min;   # sec,min,hour
-        lifetime byte 5 MB;     # B,KB,GB
-        initial_contact on;
-        support_mip6 on;
-        proposal_check obey;    # obey, strict or claim
-
-        proposal {
-                encryption_algorithm 3des;
-                hash_algorithm md5;
-                authentication_method pre_shared_key;
-                dh_group 2 ;
-        }
-      }
-
-        sainfo anonymous
-      {
-        pfs_group 1;
-        lifetime time 10 min;
-        lifetime byte 50000 KB;
-        encryption_algorithm 3des;
-        authentication_algorithm hmac_md5;
-        compression_algorithm deflate ;
-      }</programlisting>
-
-    <para>Ensure that the <filename>/usr/local/etc/racoon/psk.txt</filename>
-      file contains the pre-shared secret configured in the <quote>Firewall-1
-      Network Object Configuration</quote> section of this document and has
-      mode <literal>600</literal> permissions.</para>
-
-    <screen>&prompt.root; <userinput>chmod 600 /usr/local/etc/racoon/psk.txt</userinput></screen>
-
-  </sect1>
-
-  <sect1 id="startingvpn">
-    <title>Starting the <acronym>VPN</acronym></title>
-
-    <para>You are now ready to launch <application>racoon</application> and
-      test the <acronym>VPN</acronym> tunnel.  For debugging purposes, open
-      the Firewall-1 Log Viewer and define a log filter to isolate entries
-      pertaining to FreeBSD <acronym>GW</acronym>.  You may also find it
-      helpful to &man.tail.1; the <application>racoon</application>
-      log:</para>
-
-    <screen>&prompt.root; <userinput>tail -f /var/log/racoon.log</userinput></screen>
-
-    <para>Start <application>racoon</application> using the following
-      command:</para>
-
-    <screen>&prompt.root; <userinput>/usr/local/sbin/racoon -f /usr/local/etc/racoon/racoon.conf</userinput></screen>
-
-    <para>Once <application>racoon</application> has been launched,
-      &man.telnet.1; to a host on the Firewall-1 protected network.</para>
-
-    <screen>&prompt.root; <userinput>telnet -s 192.168.10.3 199.208.192.66 22</userinput></screen>
-
-    <para>This command attempts to connect to the &man.ssh.1; port on <hostid
-      role="ipaddr">199.208.192.66</hostid>, a machine in the Firewall-1
-      protected network.  The <option>-s</option> switch indicates the source
-      interface of the outbound connection.  This is particularly important
-      when running <acronym>NAT</acronym> and <acronym>IPFW</acronym> on
-      FreeBSD <acronym>GW</acronym>.  Using <literal>-s</literal> and
-      specifying an explicit source address prevents <acronym>NAT</acronym>
-      from mangling the packet prior to tunneling.</para>
-
-    <para>A successful <application>racoon</application> key exchange will
-      output the following to the <filename>racoon.log</filename> log
-      file:</para>
-
-<programlisting>pfkey UPDATE succeeded: ESP/Tunnel 216.218.197.2->208.229.100.6
-pk_recvupdate(): IPSec-SA established: ESP/Tunnel 216.218.197.2->208.229.100.6
-get pfkey ADD message IPsec-SA established: ESP/Tunnel 208.229.100.6->216.218.197.2</programlisting>
-
-    <para>Once key exchange completes (which takes a few seconds), an
-      &man.ssh.1; banner will appear.  If all went well, two <quote>Key
-      Install</quote> messages will be logged in the Firewall-1 Log
-      Viewer.</para>
-
-<programlisting>Action      |  Source        |  Dest.             | Info.
-Key Install |  216.218.197.2 |  208.229.100.6     | IKE Log: Phase 1 (aggressive) completion.
-Key Install |  216.218.197.2 |  208.229.100.6     | scheme: IKE methods</programlisting>
-
-    <para>Under the information column, the full log detail will read:</para>
-
-<programlisting>IKE Log: Phase 1 (aggressive) completion. 3DES/MD5/Pre shared secrets Negotiation Id:
-scheme: IKE methods: Combined ESP: 3DES + MD5 + PFS (phase 2 completion) for host:</programlisting>
-  </sect1>
-
-  <sect1 id="References">
-    <title>References</title>
-
-    <itemizedlist>
-      <listitem>
-	<para>The FreeBSD Handbook: VPN over IPsec.
-        <ulink url="&url.books.handbook;/ipsec.html"></ulink></para>
-      </listitem>
-
-      <listitem>
-        <para>KAME Project.
-	<ulink url="http://www.kame.net"></ulink></para>
-      </listitem>
-    </itemizedlist>
-  </sect1>
-</article>
diff --git a/en_US.ISO8859-1/articles/dialup-firewall/Makefile b/en_US.ISO8859-1/articles/dialup-firewall/Makefile
deleted file mode 100644
index c512d68c66..0000000000
--- a/en_US.ISO8859-1/articles/dialup-firewall/Makefile
+++ /dev/null
@@ -1,18 +0,0 @@
-#
-# $FreeBSD$
-#
-# Article: Dialup firewalling with FreeBSD
-
-DOC?= article
-
-FORMATS?= html
-
-INSTALL_COMPRESSED?=gz
-INSTALL_ONLY_COMPRESSED?=
-
-SRCS=	article.sgml
-
-URL_RELPREFIX?=	../../../..
-DOC_PREFIX?= ${.CURDIR}/../../..
-
-.include "${DOC_PREFIX}/share/mk/doc.project.mk"
diff --git a/en_US.ISO8859-1/articles/dialup-firewall/article.sgml b/en_US.ISO8859-1/articles/dialup-firewall/article.sgml
deleted file mode 100644
index d7f7d39aa9..0000000000
--- a/en_US.ISO8859-1/articles/dialup-firewall/article.sgml
+++ /dev/null
@@ -1,318 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1" standalone="no"?>
-<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V4.2-Based Extension//EN"
-	"../../../share/sgml/freebsd42.dtd" [
-<!ENTITY % entities PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Entity Set//EN" "../../share/sgml/entities.ent">
-%entities;
-]>
-
-<article lang='en'>
-  <articleinfo>
-    <title>Dialup firewalling with FreeBSD</title>
-
-    <authorgroup>
-      <author>
-	<firstname>Marc</firstname>
-	<surname>Silver</surname>
-
-	<affiliation>
-	  <address><email>marcs@draenor.org</email></address>
-	</affiliation>
-      </author>
-    </authorgroup>
-
-    <legalnotice id="trademarks" role="trademarks">
-      &tm-attrib.freebsd;
-      &tm-attrib.general;
-    </legalnotice>
-
-    <pubdate>$FreeBSD$</pubdate>
-
-    <releaseinfo>$FreeBSD$</releaseinfo>
-
-    <abstract>
-      <para>This article documents how to set up a firewall using a PPP
-	dialup with FreeBSD and IPFW, and specifically with firewalling over
-	a dialup with a dynamically assigned IP address.  This document does
-	not include information on setting up an initial PPP connection.
-	For more information on setting up a PPP connection, consult
-	the &man.ppp.8; manual page.</para>
-    </abstract>
-  </articleinfo>
-
-  <sect1 id="preface">
-    <title>Preface</title>
-
-     <para>This document outlines the steps required to set up
-       firewalling with FreeBSD when an IP address is assigned dynamically
-       by your ISP.  While every effort has been made to make this document
-       as informative and correct as possible, you are welcome to mail
-       any corrections, comments or suggestions to the author at
-       <email>marcs@draenor.org</email>.</para>
-   </sect1>
-
-  <sect1 id="kernel">
-    <title>Kernel Options</title>
-
-    <para>In order to use IPFW, support for it must be compiled into the
-      kernel.  For more information on how to recompile the kernel,
-      please see the <ulink
-      url="&url.books.handbook;/kernelconfig.html">kernel configuration
-      section in the Handbook</ulink>.  The following options must be
-      added into your kernel configuration file for IPFW support:</para>
-
-    <variablelist>
-      <varlistentry>
-	<term><literal>options IPFIREWALL</literal></term>
-
-	<listitem>
-	  <para>Enables the kernel firewall code.</para>
-	  <note><para>This document assumes that you are running
-	    &os; 5.X. Users running &os; 4.X will need to
-	    recompile their kernels with <emphasis>IPFW2</emphasis>
-	    support.  &os; 4.X users should consult the &man.ipfw.8;
-	    manual page for more information on using IPFW2 on their
-	    systems, and should pay particular attention to the
-	    <emphasis>USING IPFW2 IN FreeBSD-STABLE</emphasis>
-	    section.</para></note>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-	<term><literal>options IPFIREWALL_VERBOSE</literal></term>
-
-	<listitem>
-	  <para>Sends logged packets to the system logger.</para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-	<term><literal>options
-	    IPFIREWALL_VERBOSE_LIMIT=<replaceable>500</replaceable></literal></term>
-
-	<listitem>
-	  <para>Limits the number of times a matching entry may be logged.
-	    This allows you to log firewall activity without the risk of
-	    syslog flooding in the event of a denial of service attack.
-	    <replaceable>500</replaceable> is a reasonable number to use, but
-	    may be adjusted based on your requirements.</para>
-	</listitem>
-      </varlistentry>
-    </variablelist>
-
-    <warning><para>Once the kernel recompile has been completed,
-      <emphasis>do not reboot</emphasis> your system.  Doing so may result
-      in you being locked out of your own system.  You must only reboot
-      once the ruleset is in place and all the relevant configuration
-      files have been updated.</para></warning>
-
-  </sect1>
-
-  <sect1 id="rcconf">
-    <title>Changing <filename>/etc/rc.conf</filename> to load the
-      firewall</title>
-
-    <para><filename>/etc/rc.conf</filename> needs to be slightly
-      modified in order to tell the system about the firewall and to
-      specify the location for our rules file.  Add the following lines
-      to <filename>/etc/rc.conf</filename>:</para>
-
-    <programlisting>firewall_enable="YES"
-firewall_script="/etc/firewall/fwrules"</programlisting>
-
-    <para>For more information on the functions of these statements take
-     a look at <filename>/etc/defaults/rc.conf</filename> and read
-      &man.rc.conf.5;</para>
-  </sect1>
-
-  <sect1>
-    <title>Enable PPP's network address translation</title>
-
-    <para>In order to allow clients on your network to connect via
-      your gateway, you will need to enable PPP's network address
-      translation (NAT).  In order to use PPP's NAT functions, add the
-      following lines to <filename>/etc/rc.conf</filename>:</para>
-
-    <programlisting>ppp_enable="YES"
-ppp_mode="auto"
-ppp_nat="YES"
-ppp_profile="<replaceable>your_profile</replaceable>"</programlisting>
-
-    <note><para>Take care to change <literal>your_profile</literal> to
-      the name of your own dialup profile.  The profile name should match the
-      name of the dialup connection in
-      your <filename>/etc/ppp/ppp.conf</filename> file.</para></note>
-  </sect1>
-
-  <sect1 id="rules">
-    <title>The rule set for the firewall</title>
-
-    <para>This is the point where we define the firewall rules for your
-      system.  The ruleset that we are about to describe is a generic
-      template for most dialup users.  While it will not suit the exact
-      needs of every user, it provides you with a basic idea of how IPFW
-      works and should be fairly easy to customize.</para>
-
-    <para>First, let's start with the basics of closed firewalling.
-      Closed firewalling is based on the idea that everything is denied
-      by default.  The system administrator may then explicitly add
-      rules for traffic that he or she would like to allow.  Rules
-      should be in the order of allow first, and then deny.  The premise
-      is that you add the rules for everything you would like to allow,
-      and then everything else is automatically denied.</para>
-
-    <para>Following that, let's create the directory where we will store our
-      firewall rules.  In this example, we will use <filename
-      class="directory">/etc/firewall</filename>. Change into the
-      directory and edit the file <filename>fwrules</filename> as we
-      specified in <filename>rc.conf</filename>.  Please note that you
-      can change this filename to anything you wish.  This guide merely
-      gives an example of a filename you may want to use.</para>
-
-    <para>Now, let's look at a nicely commented sample firewall
-      file.</para>
-
-    <programlisting># Define the firewall command (as in /etc/rc.firewall) for easy
-# reference.  Helps to make it easier to read.
-fwcmd="/sbin/ipfw"
-
-# Define our outside interface.  With userland-ppp this
-# defaults to tun0.
-oif="tun0"
-
-# Define our inside interface.  This is usually your network
-# card.  Be sure to change this to match your own network
-# interface.
-iif="fxp0"
-
-# Force a flushing of the current rules before we reload.
-$fwcmd -f flush
-
-# Check the state of all packets.
-$fwcmd add check-state
-
-# Stop spoofing on the outside interface.
-$fwcmd add deny ip from any to any in via $oif not verrevpath
-
-# Allow all connections that we initiate, and keep their state.
-# but deny established connections that don't have a dynamic rule.
-$fwcmd add allow ip from me to any out via $oif keep-state
-$fwcmd add deny tcp from any to any established in via $oif
-
-# Allow all connections within our network.
-$fwcmd add allow ip from any to any via $iif
-
-# Allow all local traffic.
-$fwcmd add allow all from any to any via lo0
-$fwcmd add deny all from any to 127.0.0.0/8
-$fwcmd add deny ip from 127.0.0.0/8 to any
-
-# Allow internet users to connect to the port 22 and 80.
-# This example specifically allows connections to the sshd and a
-# webserver.
-$fwcmd add allow tcp from any to me dst-port 22,80 in via $oif setup keep-state
-
-# Allow ICMP packets: remove type 8 if you don't want your host
-# to be pingable.
-$fwcmd add allow icmp from any to any via $oif icmptypes 0,3,8,11,12
-
-# Deny and log all the rest.
-$fwcmd add deny log ip from any to any</programlisting>
-
-    <para>You now have a fully functional firewall that only allows
-      connections to ports 22 and 80 and will log any other connection
-      attempts. You may now safely reboot and the firewall should
-      be automatically started and the ruleset loaded.  If you find this
-      incorrect in any way or experience any problems, or have any
-      suggestions to improve this page, please email me.</para>
-  </sect1>
-
-  <sect1>
-    <title>Questions</title>
-
-    <qandaset>
-      <qandaentry>
-        <question>
-	  <para>I get messages like <errorname>limit 500 reached on entry
-	    2800</errorname> and after that my machine stops logging
-	    denied packets that match that rule number.  Is my firewall
-	    still working?</para>
-        </question>
-
-	<answer>
-	  <para>This merely means that the maximum logging count for
-            the rule has been reached.  The rule itself is still
-            working, but it will no longer log until such time as you
-	    reset the logging counters.  An example of how to clear your
-	    counters can be found below:</para>
-<screen>&prompt.root; <userinput>ipfw resetlog</userinput></screen>
-	  <para>Alternatively, you may increase the log limit in
-            your kernel configuration with the
-            <option>IPFIREWALL_VERBOSE_LIMIT</option> option as
-            described above.  You may also change this limit (without
-	    recompiling your kernel and having to reboot) by using the
-	    net.inet.ip.fw.verbose_limit &man.sysctl.8; value.</para>
-        </answer>
-      </qandaentry>
-
-      <qandaentry>
-	<question>
-	  <para>There must be something wrong.  I followed your instructions
-	    to the letter and now I am locked out.</para>
-        </question>
-
-	<answer>
-	  <para>This tutorial assumes that you are running
-	    <emphasis>userland-ppp</emphasis>, therefore the supplied rule set
-	    operates on the <devicename>tun0</devicename> interface, which
-	    corresponds to the first connection made with &man.ppp.8; (aka
-	    <emphasis>user-ppp</emphasis>).  Additional connections would use
-	    <devicename>tun1</devicename>, <devicename>tun2</devicename> and so
-	    on.</para>
-
-	  <para>You should also note that &man.pppd.8; uses the
-	    <devicename>ppp0</devicename> interface instead, so if you
-	    start the connection with &man.pppd.8; you must substitute
-	    <devicename>tun0</devicename> for
-	    <devicename>ppp0</devicename>.  A quick way to edit the
-	    firewall rules to reflect this change is shown below. The
-	    original rule set is backed up as
-	    <filename>fwrules_tun0</filename>.</para>
-
-	  <screen>	    &prompt.user; <userinput>cd /etc/firewall</userinput>
-	    /etc/firewall&prompt.user; <userinput>su</userinput>
-	    <prompt>Password:</prompt>
-	    /etc/firewall&prompt.root; <userinput>mv fwrules fwrules_tun0</userinput>
-	    /etc/firewall&prompt.root; <userinput>cat fwrules_tun0 | sed s/tun0/ppp0/g > fwrules</userinput>
-	  </screen>
-
-	  <para>To know whether you are currently using &man.ppp.8; or
-	    &man.pppd.8; you can examine the output of
-	    &man.ifconfig.8; once the connection is up. E.g., for a
-	    connection made with &man.pppd.8; you would see something
-	    like this (showing only the relevant lines):</para>
-
-	  <screen>	    &prompt.user; <userinput>ifconfig</userinput>
-	    <emphasis>(skipped...)</emphasis>
-	    ppp0: flags=<replaceable>8051&lt;UP,POINTOPOINT,RUNNING,MULTICAST&gt; mtu 1524</replaceable>
-                    inet <replaceable>xxx.xxx.xxx.xxx</replaceable> --&gt; <replaceable>xxx.xxx.xxx.xxx</replaceable> netmask <replaceable>0xff000000</replaceable>
-	    <emphasis>(skipped...)</emphasis>
-	    </screen>
-
-	  <para>On the other hand, for a connection made with
-	    &man.ppp.8; (<emphasis>user-ppp</emphasis>) you should see
-	    something similar to this:</para>
-
-	  <screen>	    &prompt.user; <userinput>ifconfig</userinput>
-	    <emphasis>(skipped...)</emphasis>
-	    ppp0: flags=<replaceable>8010&lt;POINTOPOINT,MULTICAST&gt; mtu 1500</replaceable>
-	    <emphasis>(skipped...)</emphasis>
-	    tun0: flags=<replaceable>8051&lt;UP,POINTOPOINT,RUNNING,MULTICAST&gt; mtu 1524</replaceable>
-	            <emphasis>(IPv6 stuff skipped...)</emphasis>
-                    inet <replaceable>xxx.xxx.xxx.xxx</replaceable> --&gt; <replaceable>xxx.xxx.xxx.xxx</replaceable> netmask <replaceable>0xffffff00</replaceable>
-                    Opened by PID <replaceable>xxxxx</replaceable>
-            <emphasis>(skipped...)</emphasis></screen>
-	</answer>
-      </qandaentry>
-    </qandaset>
-  </sect1>
-</article>
diff --git a/en_US.ISO8859-1/articles/diskless-x/Makefile b/en_US.ISO8859-1/articles/diskless-x/Makefile
deleted file mode 100644
index 77fd3e8065..0000000000
--- a/en_US.ISO8859-1/articles/diskless-x/Makefile
+++ /dev/null
@@ -1,16 +0,0 @@
-#
-# $FreeBSD$
-#
-# Article: Diskless X Server: a how to guide
-
-DOC?= article
-
-FORMATS?= html
-
-INSTALL_COMPRESSED?=gz
-INSTALL_ONLY_COMPRESSED?=
-
-SRCS=	article.sgml
-
-DOC_PREFIX?= ${.CURDIR}/../../..
-.include "${DOC_PREFIX}/share/mk/doc.project.mk"
diff --git a/en_US.ISO8859-1/articles/diskless-x/article.sgml b/en_US.ISO8859-1/articles/diskless-x/article.sgml
deleted file mode 100644
index 0a4e226998..0000000000
--- a/en_US.ISO8859-1/articles/diskless-x/article.sgml
+++ /dev/null
@@ -1,353 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1" standalone="no"?>
-<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V4.2-Based Extension//EN"
-	"../../../share/sgml/freebsd42.dtd" [
-<!ENTITY % entities PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Entity Set//EN" "../../share/sgml/entities.ent">
-%entities;
-]>
-
-<!--
-     The FreeBSD Documentation Project
-
-     $FreeBSD$
--->
-
-<article lang='en'>
-  <articleinfo>
-    <title>Diskless X Server: a how to guide</title>
-
-    <authorgroup>
-      <author>
-	<firstname>Jerry</firstname>
-	<surname>Kendall</surname>
-	<affiliation>
-	  <address>
-	    <email>jerry@kcis.com</email>
-	  </address>
-	</affiliation>
-      </author></authorgroup>
-
-    <pubdate>28-December-1996</pubdate>
-
-    <releaseinfo>$FreeBSD$</releaseinfo>
-
-    <copyright>
-      <year>1996</year>
-      <holder>Jerry Kendall</holder>
-    </copyright>
-
-    <legalnotice id="trademarks" role="trademarks">
-      &tm-attrib.freebsd;
-      &tm-attrib.3com;
-      &tm-attrib.microsoft;
-      &tm-attrib.sun;
-      &tm-attrib.general;
-    </legalnotice>
-
-    <abstract>
-      <para>With the help of some friends on the FreeBSD-hackers list, I have
-	been able to create a diskless X terminal.  The creation of the X
-	terminal required first creating a diskless system with minimal
-	utilities mounted via NFS.  These same steps were used to create 2
-	separate diskless systems.  The first is <hostid
-	  role="fqdn">altair.example.com</hostid>.  A diskless X terminal that I
-	run on my old 386DX-40.  It has a 340Meg hard disk but, I did not want
-	to change it.  So, it boots from <hostid
-	  role="fqdn">antares.example.com</hostid> across a Ethernet.  The second
-	system is a 486DX2-66.  I set up a diskless FreeBSD (complete) that
-	uses no local disk.  The server in that case is a Sun 670MP running
-	&sunos; 4.1.3.  The same setup configuration was needed for both.</para>
-
-      <para>I am sure that there is stuff that needs to be added
-	to this.  Please send me any comments.</para>
-    </abstract>
-  </articleinfo>
-
-  <sect1>
-    <title>Creating the boot floppy (On the diskless system)</title>
-
-    <para>Since the network boot loaders will not work with some of the TSR's
-      and such that &ms-dos; uses, it is best to create a dedicated boot floppy
-      or, if you can, create an &ms-dos; menu that will (via the
-      <filename>config.sys</filename>/<filename>autoexec.bat</filename> files)
-      ask what configuration to load when the system starts.  The later is the
-      method that I use and it works great. My &ms-dos; (6.x) menu is
-      below.</para>
-
-    <example>
-      <title><filename>config.sys</filename></title>
-
-      <programlisting>[menu]
-menuitem=normal, normal
-menuitem=unix, unix
-[normal]
-....
-normal config.sys stuff
-...
-[unix]</programlisting>
-    </example>
-
-    <example>
-      <title><filename>autoexec.bat</filename></title>
-
-      <programlisting>@ECHO OFF
-goto %config%
-
-:normal
-...
-normal autoexec.bat stuff
-...
-goto end
-
-:unix
-cd \netboot
-nb8390.com
-
-:end</programlisting>
-    </example>
-  </sect1>
-
-  <sect1>
-    <title>Getting the network boot programs (On the server)</title>
-
-    <para>Compile the <quote>net-boot</quote> programs that are located in
-      <filename>/usr/src/sys/i386/boot/netboot</filename>.  You should read
-      the comments at the top of the <filename>Makefile</filename>.  Adjust as
-      required.  Make a backup of the original in case something goes wrong.  When
-      the build is done, there should be 2 &ms-dos; executables,
-      <filename>nb8390.com</filename> and <filename>nb3c509.com</filename>.
-      One of these two programs will be what you need to run on the diskless
-      server.  It will load the kernel from the boot server.  At this point,
-      put both programs on the &ms-dos; boot floppy created earlier.</para>
-  </sect1>
-
-  <sect1>
-    <title>Determine which program to run (On the diskless system)</title>
-
-    <para>If you know the chipset that your Ethernet adapter uses, this is
-      easy.  If you have the NS8390 chipset, or a NS8390 based chipset, use
-      <filename>nb8390.com</filename>.  If you have a &tm.3com; 509 based chipset,
-      use the <filename>nb3C509.com</filename> boot program.  If you are not
-      sure which you have, try using one, if it says <errorname>No adapter
-	found</errorname>, try the other.  Beyond that, you are pretty much on
-      your own.</para>
-  </sect1>
-
-  <sect1>
-    <title>Booting across the network</title>
-
-    <para>Boot the diskless system with out any config.sys/autoexec.bat
-      files.  Try running the boot program for your Ethernet adapter.</para>
-
-    <para>My Ethernet adapter is running in WD8013 16bit mode so I run
-      <filename>nb8390.com</filename></para>
-
-    <screen><prompt>C:&gt;</prompt> <userinput>cd \netboot</userinput>
-<prompt>C:&gt;</prompt> <userinput>nb8390</userinput>
-
-<prompt>Boot from Network (Y/N) ?</prompt>  <userinput>Y</userinput>
-
-BOOTP/TFTP/NFS bootstrap loader     ESC for menu
-
-Searching for adapter..
-WD8013EBT base 0x0300, memory 0x000D8000, addr 00:40:01:43:26:66
-
-Searching for server...</screen>
-
-    <para>At this point, my diskless system is trying to find a machine to act
-      as a boot server.  Make note of the <literal>addr</literal> line above,
-      you will need this number later.  Reset the diskless system and modify
-      your <filename>config.sys</filename> and
-      <filename>autoexec.bat</filename> files to do these steps automatically
-      for you.  Perhaps in a menu.  If you had to run
-      <command>nb3c509.com</command> instead of <command>nb8390.com</command>
-      the output is the same as above.  If you got <errorname>No adapter
-	found</errorname> at the <literal>Searching for adapter...</literal>
-      message, verify that you did indeed set the compile time defines in the
-      <filename>Makefile</filename> correctly.</para>
-  </sect1>
-
-  <sect1>
-    <title>Allowing systems to boot across the network (On the server)</title>
-
-    <para>Make sure the <filename>/etc/inetd.conf</filename> file has entries
-      for tftp and bootps. Mine are listed below:</para>
-
-    <programlisting>tftp	dgram	udp	wait	nobody	/usr/libexec/tftpd	tftpd /tftpboot
-#
-# Additions by who ever you are
-bootps  dgram  udp  wait  root  /usr/libexec/bootpd bootpd /etc/bootptab</programlisting>
-
-    <para>If you have to change the <filename>/etc/inetd.conf</filename> file,
-      send a <literal>HUP</literal> signal to &man.inetd.8;.  To do this, get the
-      process ID of <command>inetd</command> with <command>ps -ax | grep inetd | grep -v
-	grep</command>.  Once you have it, send it a <literal>HUP</literal> signal.  Do this by
-      <command>kill -HUP &lt;pid&gt;</command>.  This will force <command>inetd</command> to
-      re-read its config file.</para>
-
-    <para>Did you remember to note the <literal>addr</literal> line from the
-      output of the boot loader on the diskless system? Guess what, here is
-      where you need it.</para>
-
-    <para>Add an entry to <filename>/etc/bootptab</filename> (maybe creating the
-      file).  It should be laid out identical to this:</para>
-
-    <programlisting>altair:\
-        :ht=ether:\
-        :ha=004001432666:\
-        :sm=255.255.255.0:\
-        :hn:\
-        :ds=199.246.76.1:\
-        :ip=199.246.76.2:\
-        :gw=199.246.76.1:\
-        :vm=rfc1048:</programlisting>
-
-    <para>The lines are as follows:</para>
-
-    <informaltable frame="none" pgwide="1">
-      <tgroup cols="2">
-	<tbody>
-	  <row>
-	    <entry><literal>altair</literal></entry>
-	    <entry>the diskless systems name without the domain name.</entry>
-	  </row>
-
-	  <row>
-	    <entry><literal>ht=ether</literal></entry>
-	    <entry>the hardware type of <quote>ethernet</quote>.</entry>
-	  </row>
-
-	  <row>
-	    <entry><literal>ha=004001432666</literal></entry>
-	    <entry>the hardware address (the number noted above).</entry>
-	  </row>
-
-	  <row>
-	    <entry><literal>sm=255.255.255.0</literal></entry>
-	    <entry>the subnet mask.</entry>
-	  </row>
-
-	  <row>
-	    <entry><literal>hn</literal></entry>
-	    <entry>tells server to send client's hostname to the
-	      client.</entry>
-	  </row>
-
-	  <row>
-	    <entry><literal>ds=199.246.76.1</literal></entry>
-	    <entry>tells the client who the domain server is.</entry>
-	  </row>
-
-	  <row>
-	    <entry><literal>ip=199.246.76.2</literal></entry>
-	    <entry>tells the client what its IP address is.</entry>
-	  </row>
-
-	  <row>
-	    <entry><literal>gw=199.246.76.1</literal></entry>
-	    <entry>tells the client what the default gateway is.</entry>
-	  </row>
-
-	  <row>
-	    <entry><literal>vm=...</literal></entry>
-	    <entry>just leave it there.</entry>
-	  </row>
-	</tbody>
-      </tgroup>
-    </informaltable>
-
-    <note>
-      <para>Be sure to set up the IP addresses correctly, the addresses above
-	are my own.</para>
-    </note>
-
-    <para>Create the directory <filename>/tftpboot</filename> on the server it will contain the
-      configuration files for the diskless systems that the server will serve.
-      These files will be named <filename>cfg.<replaceable>ip</replaceable></filename> where <replaceable>ip</replaceable> is the IP
-      address of the diskless system.  The config file for <hostid>altair</hostid> is
-      <filename>/tftpboot/cfg.199.246.76.2</filename>.  The contents is:</para>
-
-    <programlisting>rootfs 199.246.76.1:/DiskLess/rootfs/altair
-hostname altair.example.com</programlisting>
-
-    <para>The line <literal>hostname altair.example.com</literal> simply tells
-      the diskless system what its fully qualified domain name is.</para>
-
-    <para>The line <literal>rootfs
-	199.246.76.1:/DiskLess/rootfs/altair</literal> tells the diskless
-      system where its NFS mountable root filesystem is located.</para>
-
-    <note>
-      <para>The NFS mounted root filesystem will be mounted <emphasis>read
-	  only</emphasis>.</para>
-    </note>
-
-    <para>The hierarchy for the diskless system can be re-mounted allowing
-      read-write operations if required.</para>
-
-    <para>I use my spare 386DX-40 as a dedicated X terminal.</para>
-
-    <para>The hierarchy for <hostid>altair</hostid> is:</para>
-
-    <literallayout>/
-/bin
-/etc
-/tmp
-/sbin
-/dev
-/dev/fd
-/usr
-/var
-/var/run</literallayout>
-
-    <para>The actual list of files is:</para>
-
-    <screen>-r-xr-xr-x  1 root  wheel  779984 Dec 11 23:44 ./kernel
--r-xr-xr-x  1 root    bin  299008 Dec 12 00:22 ./bin/sh
--rw-r--r--  1 root  wheel     499 Dec 15 15:54 ./etc/rc
--rw-r--r--  1 root  wheel    1411 Dec 11 23:19 ./etc/ttys
--rw-r--r--  1 root  wheel     157 Dec 15 15:42 ./etc/hosts
--rw-r--r--  1 root    bin    1569 Dec 15 15:26 ./etc/XF86Config.altair
--r-x------  1 bin     bin  151552 Jun 10  1995 ./sbin/init
--r-xr-xr-x  1 bin     bin  176128 Jun 10  1995 ./sbin/ifconfig
--r-xr-xr-x  1 bin     bin  110592 Jun 10  1995 ./sbin/mount_nfs
--r-xr-xr-x  1 bin     bin  135168 Jun 10  1995 ./sbin/reboot
--r-xr-xr-x  1 root    bin   73728 Dec 13 22:38 ./sbin/mount
--r-xr-xr-x  1 root  wheel    1992 Jun 10  1995 ./dev/MAKEDEV.local
--r-xr-xr-x  1 root  wheel   24419 Jun 10  1995 ./dev/MAKEDEV</screen>
-
-    <para>If you are not using &man.devfs.5; (which is the default
-      in FreeBSD&nbsp;5.X), you should make sure that you
-      do not forget to run <command>MAKEDEV all</command> in the
-      <filename>dev</filename> directory.</para>
-
-    <para>My <filename>/etc/rc</filename> for <hostid>altair</hostid>
-      is:</para>
-
-<programlisting>#!/bin/sh
-#
-PATH=/bin:/
-export PATH
-#
-# configure the localhost
-/sbin/ifconfig lo0 127.0.0.1
-#
-# configure the ethernet card
-/sbin/ifconfig ed0 199.246.76.2 netmask 0xffffff00
-#
-# mount the root filesystem via NFS
-/sbin/mount antares:/DiskLess/rootfs/altair /
-#
-# mount the /usr filesystem via NFS
-/sbin/mount antares:/DiskLess/usr /usr
-#
-/usr/X11R6/bin/XF86_SVGA -query antares -xf86config /etc/XF86Config.altair > /dev/null 2>&amp;1
-#
-# Reboot after X exits
-/sbin/reboot
-#
-# We blew up....
-exit 1</programlisting>
-
-    <para>Any comments and all questions welcome.</para>
-  </sect1>
-</article>
diff --git a/en_US.ISO8859-1/articles/euro/Makefile b/en_US.ISO8859-1/articles/euro/Makefile
deleted file mode 100644
index e1247939d0..0000000000
--- a/en_US.ISO8859-1/articles/euro/Makefile
+++ /dev/null
@@ -1,18 +0,0 @@
-#
-# $FreeBSD$
-#
-# Article: The Euro symbol on FreeBSD
-
-DOC?= article
-
-FORMATS?= html
-
-INSTALL_COMPRESSED?=gz
-INSTALL_ONLY_COMPRESSED?=
-
-SRCS=	article.sgml
-
-URL_RELPREFIX?=	../../../..
-DOC_PREFIX?= ${.CURDIR}/../../..
-
-.include "${DOC_PREFIX}/share/mk/doc.project.mk"
diff --git a/en_US.ISO8859-1/articles/euro/article.sgml b/en_US.ISO8859-1/articles/euro/article.sgml
deleted file mode 100644
index e12ab293ea..0000000000
--- a/en_US.ISO8859-1/articles/euro/article.sgml
+++ /dev/null
@@ -1,347 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1" standalone="no"?>
-<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V4.2-Based Extension//EN"
-	"../../../share/sgml/freebsd42.dtd" [
-<!ENTITY % entities PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Entity Set//EN" "../../share/sgml/entities.ent">
-%entities;
-]>
-
-<article lang='en'>
-  <articleinfo>
-    <title>The Euro symbol on
-      <systemitem class="osname">FreeBSD</systemitem></title>
-
-    <authorgroup>
-      <author>
-	<firstname>Aaron</firstname>
-
-	<surname>Kaplan</surname>
-
-	<affiliation>
-	  <address>
-	    <email>aaron@lo-res.org</email>
-	  </address>
-	</affiliation>
-      </author>
-    </authorgroup>
-
-    <copyright>
-      <year>2002</year>
-      <year>2003</year>
-      <holder>The FreeBSD Documentation Project</holder>
-    </copyright>
-
-    <legalnotice id="trademarks" role="trademarks">
-      &tm-attrib.freebsd;
-      &tm-attrib.general;
-    </legalnotice>
-
-    <pubdate>$FreeBSD$</pubdate>
-
-    <releaseinfo>$FreeBSD$</releaseinfo>
-
-    <abstract>
-      <para>This document will try to help you in getting started with the new
-	<keycap>Euro</keycap> Symbol on your new keyboard that you had to buy
-	in early 2002 because of the switch to the new common currency. We
-	will first focus on the more important parts like being able to
-	correctly display the symbol on the console. Later sections will deal
-	with configuring particular programs like
-	<application>X11</application>.
-      </para>
-
-      <para>Lots of helpful input came from Oliver Fromme, Tom Rhodes and
-	countless others. Thanks! Without you this article would not have been
-	possible!
-      </para>
-    </abstract>
-  </articleinfo>
-
-  <sect1>
-    <title>The Euro in a nutshell</title>
-
-    <para>If you already feel comfortable with
-      <ulink url="&url.books.handbook;/l10n.html">localization</ulink> as
-      described in the <systemitem class="osname">FreeBSD</systemitem>
-      Handbook you might be only interested in the following facts which
-      will get you started quickly:</para>
-
-    <variablelist>
-      <varlistentry>
-	<term>ISO8859-15</term>
-
-	<listitem>
-	  <para>This is a slight modification of the commonly used ISO8859-1
-	    character map. It includes the Euro symbol. Used for the
-	    <envar>LANG</envar>, <envar>LC_CTYPE</envar> environment
-	    variables.</para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-	<term><filename>iso15-8x16.fnt</filename></term>
-
-	<listitem>
-	  <para>The &man.vidcontrol.1; font for the console</para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-	<term><filename>/usr/share/syscons/keymaps/*.iso.kbd</filename></term>
-
-	<listitem>
-	  <para>Appropriate keyboard maps depending on your language. Set your
-            <literal>keymap</literal> entry in <filename>rc.conf</filename> to
-            one of these.</para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-	<term><envar>LC_CTYPE</envar></term>
-
-	<listitem>
-	  <para>Used to specify the correct character type in your
-	    locale.</para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-	<term><literal>XkbLayout "<replaceable>lang</replaceable>(euro)"</literal></term>
-
-	<listitem>
-	  <para><application>Xorg</application> config option.</para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-	<term><filename>/etc/X11/xorg.conf</filename></term>
-	<listitem>
-	  <para>Be sure to adapt your X11 fonts to
-	    <literal>-*-..-*-iso8859-15</literal></para>
-	</listitem>
-      </varlistentry>
-    </variablelist>
-  </sect1>
-
-  <sect1 id="general">
-    <title>A general remark</title>
-
-    <para>In the following sections we will often refer to
-      <emphasis>ISO8859-15</emphasis>. This is the standard notation starting
-      with <systemitem class="osname">FreeBSD</systemitem> 4.5. In older
-      versions, the standard notation was either
-      <emphasis>ISO_8859-15</emphasis> or <emphasis>DIS_8859-15</emphasis>.
-    </para>
-
-    <para>If you are using an older version of
-      <systemitem class="osname">FreeBSD</systemitem>, be sure to take a
-      look at <filename>/usr/share/locale/</filename> in order to find out
-      which naming convention is in place.</para>
-  </sect1>
-
-  <sect1 id="console">
-    <title>The console</title>
-
-    <sect2>
-      <title>Setting up your console font</title>
-
-      <para>Depending on your console resolution and size you will need one of
-	the following lines in <filename>rc.conf</filename>:</para>
-
-      <programlisting>font8x16="iso15-8x16.fnt" # from /usr/share/syscons/fonts/*
-font8x14="iso15-8x14.fnt"
-font8x8="iso15-8x8.fnt"</programlisting>
-
-      <para>This will effectively select the ISO8859-15 also known as Latin-9
-	font. ISO8859-15 is a variation of ISO8859-1. You can tell the
-	difference between the two by looking at the Euro symbol: its decimal
-	value is 164. In ISO8859-1 you will notice a circle with four little
-	strokes at the corners. This is often termed the <quote>universal currency
-	symbol</quote>. In ISO8859-15, instead of the little circle, you have the
-	Euro Symbol. Otherwise the fonts are more or less identical.</para>
-
-      <warning>
-	<para>As of the time of this writing the only usable font seems to be
-	  <literal>iso15-8x16.fnt</literal>. The others seem to only show
-	  ISO8859-1 even though the name suggest otherwise.</para>
-      </warning>
-
-      <note>
-        <para>By specifying this font some console applications will look
-	  garbled. This is due to the fact that they assume you are using a
-	  different font/character set such as ANSI 850. One notable example
-	  is <application>sysinstall</application>. However most of the
-	  time this should not be of much concern.</para>
-      </note>
-
-      <para>As the next step you should either reboot your system to let the
-	changes take effect or (manually) take the steps that would have been
-	taken at the system startup:</para>
-
-      <screen>&prompt.user; <userinput>vidcontrol -f <replaceable>iso15-8x16.fnt</replaceable></userinput></screen>
-
-      <para>To check if the font has been selected execute the following short
-	<command><anchor id="awk-test"/>awk</command> script:</para>
-
-      <programlisting>#!/usr/bin/awk -f
-BEGIN {
-        for(i = 160; i &lt; 180 ; i++)
-                printf"%3d %c\n",i,i
-}</programlisting>
-
-      <para>The result should reveal the Euro sign at position 164.</para>
-    </sect2>
-
-    <sect2>
-      <title>Setting up your keyboard for the Euro</title>
-
-      <para>Most keyboard maps should already be set up correctly. I.e: If you
-	have a german keyboard and your Umlaut keys are working, you can
-	safely skip this section since the keyboard already maps whatever key
-	combination is necessary (e.g.: <keycombo action="simul"><keycap>Alt
-	    Gr</keycap><keycap>e</keycap></keycombo>) to decimal value 164.
-	If running into problems, the best way to check is to take a look at
-	<filename>/usr/share/syscons/keymaps/*.kbd</filename>. The format of
-	the key mapping files is described in &man.keyboard.4;.
-	  &man.kbdcontrol.1; can be used to load a custom keymap.</para>
-
-      <para>Once the correct keyboard map is selected, it should be added to
-	<filename>/etc/rc.conf</filename> with the line:</para>
-
-      <programlisting>keymap="<replaceable>german.iso</replaceable>" # or another map</programlisting>
-
-      <para>As stated above, this step has most probably already been taken
-	by you at installation time (with
-	<application>sysinstall</application>). If not, either reboot or
-	load the new keymap via &man.kbdcontrol.1;.</para>
-
-      <para>To verify the keyboard mapping, switch to a new console and at
-	the login prompt, <emphasis>instead of logging</emphasis> in, try to
-	type the <keycap>Euro</keycap> key. If it is not working, either
-	file a bug report via &man.send-pr.1; or make sure you in fact chose
-	the right keyboard map.</para>
-
-      <note>
-        <para>At this stage the Euro key will not yet work in
-	  <application>bash </application> or
-	  <application>tcsh</application>.</para>
-      </note>
-    </sect2>
-
-    <sect2>
-      <title>Fixing the environment variables</title>
-
-      <para>The shells (<application>bash</application>, <application>tcsh</application>) revert to the &man.readline.3; library
-	which in turn respects the <envar>LC_CTYPE</envar> environment
-	variable.  <envar>LC_CTYPE</envar> must be set before the shell is
-	completely running. Luckily it suffices to add the line:</para>
-
-      <programlisting>export LC_CTYPE=<replaceable>de_DE</replaceable>.ISO8859-15</programlisting>
-
-      <para>to your <filename>.bash_profile</filename> (<application>bash</application>), or:</para>
-
-      <programlisting>setenv LC_CTYPE <replaceable>de_DE</replaceable>.ISO8859-15</programlisting>
-
-      <para>to your <filename>.login</filename> (<application>tcsh</application>) file. Of course,
-	<replaceable>de_DE</replaceable> should be replaced by your language.
-	Next, log out, log back in again, and verify your Euro key is working.
-	By now most console applications should respond to the Euro key. Extra
-	configuration steps for special programs like
-	<application>pine</application> might still be necessary
-	however.</para>
-
-      <note>
-	<para>An alternative to modifying <filename>.login</filename> and
-	  <filename>.bash_profile</filename> is to set the environment
-	  variables through the &man.login.conf.5; mechanism.  This approach
-	  has the advantage of assigning login classes to certain users (e.g.
-	  French users, Italian users, etc) <emphasis>in one
-	    place</emphasis>.</para>
-      </note>
-    </sect2>
-  </sect1>
-
-  <sect1 id="x11">
-    <title>Modifying X11</title>
-
-    <para>Modify <filename>/etc/X11/xorg.conf</filename>
-      in the following manner:</para>
-
-    <programlisting>Option "XkbLayout"  "<replaceable>de</replaceable>(euro)"</programlisting>
-
-    <para>Again, replace <replaceable>de</replaceable> with your language. By
-      now, the keyboard should be set up correctly. As in the console section,
-      the correct font must be chosen. For <application>KDE</application>, go
-      to the <application>KDE control center</application> -&gt;
-      Personalization -&gt; Country &amp; Language -&gt; Charset and change it
-      to <literal>ISO8859-15</literal>. Similar steps apply to
-      <application>kmail</application> and other applications.</para>
-
-    <para>Another good idea is to modify your <filename>fonts.alias</filename>
-      files. Notably the <literal>fixed</literal> font should be changed to
-      the right character set: The author's
-      <filename>/usr/X11R6/lib/X11/fonts/misc/fonts.alias</filename> looks
-      like this:</para>
-
-     <programlisting>! $Xorg: fonts.alias,v 1.3 2000/08/21 16:42:31 coskrey Exp $
-fixed   -misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-iso8859-15
-variable -*-helvetica-bold-r-normal-*-*-120-*-*-*-*-iso8859-15
-(...)</programlisting>
-
-    <para>As in the console sections, special applications still have
-      ISO8859-1 fonts configured in their respective &man.xrdb.1; databases. One
-      notable example is <application>xterm</application>. As a general rule
-      of thumb it suffices to change the corresponding configuration file in
-      <filename>/usr/X11R6/lib/X11/app-defaults</filename> and add the correct
-      font. Let us demonstrate this with
-      <application>xterm</application>.</para>
-
-   <screen>&prompt.root; cd /usr/X11R6/lib/X11/app-defaults/
-&prompt.root; vi XTerm</screen>
-
-    <para>Add the following line to the beginning of the file:</para>
-
-    <programlisting>*font:     -misc-fixed-medium-r-normal-*-*-120-*-*-c-*-iso8859-15</programlisting>
-
-    <para>Finally, restart X and make sure, fonts can be displayed by
-      executing the above <link linkend="awk-test">awk script</link>. All
-      major applications should respect the keyboard mapping and the font
-      settings.</para>
-  </sect1>
-
-  <sect1 id="problems">
-    <title>Open problems</title>
-
-    <para>Of course, the author would like to receive feedback. In addition,
-      at least let me know if you have fixes for one of these  open
-      problems:</para>
-
-    <itemizedlist>
-      <listitem>
-        <para>Describe alternative way of setting up <application>Xorg</application>:
-	  <filename role="package">x11/xkeycaps</filename></para>
-      </listitem>
-
-      <listitem>
-        <para>Settings in <application>GNOME</application></para>
-      </listitem>
-
-      <listitem>
-        <para>Settings in <application>XFCE</application></para>
-      </listitem>
-
-      <listitem>
-        <para>Settings for <application>(X)Emacs</application></para>
-      </listitem>
-
-      <listitem>
-        <para>Describe UTF-8</para>
-      </listitem>
-
-      <listitem>
-        <para>Describe <application>libiconv</application> as a effective way
-	  to convert between ISO8859-15 and UTF-{8,16} from within
-	  applications</para>
-      </listitem>
-    </itemizedlist>
-  </sect1>
-</article>
diff --git a/en_US.ISO8859-1/articles/formatting-media/Makefile b/en_US.ISO8859-1/articles/formatting-media/Makefile
deleted file mode 100644
index 90e09b2607..0000000000
--- a/en_US.ISO8859-1/articles/formatting-media/Makefile
+++ /dev/null
@@ -1,16 +0,0 @@
-#
-# $FreeBSD$
-#
-# Article: Formatting Media For Use With FreeBSD
-
-DOC?= article
-
-FORMATS?= html
-
-INSTALL_COMPRESSED?=gz
-INSTALL_ONLY_COMPRESSED?=
-
-SRCS=	article.sgml
-
-DOC_PREFIX?= ${.CURDIR}/../../..
-.include "${DOC_PREFIX}/share/mk/doc.project.mk"
diff --git a/en_US.ISO8859-1/articles/formatting-media/article.sgml b/en_US.ISO8859-1/articles/formatting-media/article.sgml
deleted file mode 100644
index 73951e9780..0000000000
--- a/en_US.ISO8859-1/articles/formatting-media/article.sgml
+++ /dev/null
@@ -1,637 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1" standalone="no"?>
-<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V4.2-Based Extension//EN"
-	"../../../share/sgml/freebsd42.dtd" [
-<!ENTITY % entities PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Entity Set//EN" "../../share/sgml/entities.ent">
-%entities;
-]>
-
-<!-- $FreeBSD$ -->
-
-<article lang='en'>
-  <articleinfo>
-    <title>Formatting Media For Use With FreeBSD</title>
-
-    <subtitle>A Tutorial</subtitle>
-
-    <authorgroup>
-      <author>
-	<firstname>Doug</firstname>
-
-	<surname>White</surname>
-
-	<affiliation>
-	  <address>
-	    <email>dwhite@resnet.uoregon.edu</email>
-	  </address>
-	</affiliation>
-      </author>
-    </authorgroup>
-
-    <pubdate>March 1997</pubdate>
-
-    <releaseinfo>$FreeBSD$</releaseinfo>
-
-    <legalnotice id="trademarks" role="trademarks">
-      &tm-attrib.freebsd;
-      &tm-attrib.iomega;
-      &tm-attrib.opengroup;
-      &tm-attrib.general;
-    </legalnotice>
-
-    <abstract>
-      <para>This document describes how to slice, partition, and
-	format hard disk drives and similar media for use with
-	FreeBSD.  The examples given have been tested under FreeBSD
-	2.2 and should work for other releases.  The text has been updated
-	for FreeBSD version 4.</para>
-    </abstract>
-  </articleinfo>
-
-  <sect1>
-    <title>Introduction &amp; Definitions</title>
-
-    <sect2>
-      <title>Overview</title>
-
-      <para>Successfully adding disks to an existing system is the
-	mark of an experienced system administrator.  Slicing,
-	partitioning, and adding disks requires a careful dance of
-	proper command and name syntax.  One slipped finger and an
-	entire disk could disappear in seconds.  This document is
-	written in an attempt to simplify this process and avoid
-	accidents.  Thankfully, enhancements to existing tools
-	(notably sysinstall) have greatly improved this process in
-	recent releases of FreeBSD.</para>
-
-      <para>There are two possible modes of disk formatting:</para>
-
-      <itemizedlist>
-	<listitem>
-	  <para><firstterm>compatibility mode</firstterm>: Arranging a
-	    disk so that it has a slice table for use with other
-	    operating systems.</para>
-	</listitem>
-
-	<listitem>
-	  <para><firstterm>dedicated mode</firstterm>, sometimes called
-	    <firstterm>dangerously dedicated mode</firstterm>: Formatting a disk
-	    with no slice table.  This makes the process of adding disks easier,
-	    however non-FreeBSD operating systems may not accept the disk.  The
-	    term <emphasis>dangerously</emphasis> refers to the danger that the
-	    system may not recognize a disk formatted in this manner.</para>
-	    </listitem> </itemizedlist>
-
-      <para>For most cases, dedicated mode is the easiest to set up
-	and use in existing systems, as a new disk is usually
-	dedicated entirely to FreeBSD.  However, compatibility mode
-	insures optimum interoperability with future installations at
-	a cost of increased complexity.</para>
-
-      <para>In addition to selecting the mode, two methods of slicing
-	the disk are available.  One is using the system installation
-	tool <command>/stand/sysinstall</command>.  2.1.7-RELEASE and
-	later versions of <command>sysinstall</command> contain code
-	to ease setup of disks during normal system operation, mainly
-	allowing access to the Label and Partition editors and a Write
-	feature which will update just the selected disk and slice
-	without affecting other disks.  The other method is running
-	the tools manually from a root command line.  For
-	dedicated mode, only three or four commands are involved while
-	<command>sysinstall</command> requires some
-	manipulation.</para>
-    </sect2>
-
-    <sect2>
-      <title>Definitions</title>
-
-      <para>&unix; disk management over the centuries has invented many
-	new definitions for old words.  The following glossary covers
-	the definitions used in this document and (hopefully) for
-	FreeBSD in general.</para>
-
-<!-- I'm tempted to use GLOSSARY here but will resort to a list for
-now. -->
-
-      <itemizedlist>
-	<listitem>
-	  <para>compatibility mode:  Arranging a disk so that it has a
-	    slice table for use with other operating systems.  Oppose
-	    dedicated mode.</para>
-	</listitem>
-
-	<listitem>
-	  <para>(dangerously) dedicated mode:  Formatting a disk with no
-	    slice table.  This makes the process of adding disks
-	    easier, however non-FreeBSD operating systems may not
-	    accept the disk.  Oppose compatibility mode.</para>
-	</listitem>
-
-	<listitem>
-	  <para>disk: Hard disks, CDROMs, magneto-optical devices and
-	    &iomegazip;/&jaz; removable media are example of storage devices
-	    commonly used today.  The basic principle of the way these
-	    work is that one or more spinning disks spin by a motor,
-	    while a head, moving on a radial path close to the disks,
-	    reads from or writes data to the disk.  Writing is done by
-	    modifying some physical properties of the disk (magnetic
-	    flow, reflectivity, etc.) while reading is done by
-	    <quote>detecting</quote> changes to the same physical
-	    properties of the disk.</para>
-	</listitem>
-
-	<listitem>
-	  <para>slice: A division of a disk.  Up to four slices are
-	    permitted on one disk in the PC standard.  Slices are
-	    composed of contiguous sectors.  Slices are recorded in a
-	    <quote>slice table</quote> used by the system BIOS to
-	    locate bootable partitions.  The slice table is usually
-	    called the <quote>partition table</quote> in DOS parlance.  Maintained by
-	    the fdisk utility.</para>
-	</listitem>
-
-	<listitem>
-	  <para>partition: A division of a slice.  Usually used in
-	    reference to divisions of the FreeBSD slice of a disk.
-	    Each filesystem and swap area on a disk resides in a
-	    partition.  Maintained using the disklabel utility.</para>
-	</listitem>
-
-	<listitem>
-	  <para>sector:  Smallest subdivision of a disk.  One sector
-	    usually represents 512 bytes of data.</para>
-	</listitem>
-      </itemizedlist>
-    </sect2>
-
-    <sect2>
-      <title>Warnings &amp; Pitfalls</title>
-
-      <para>Building disks is not something to take lightly.  It is
-	quite possible to destroy the contents of other disks in your
-	system if the proper precautions are not taken.</para>
-
-      <para><emphasis>Check your work carefully.</emphasis>  It is very simple
-	to destroy the incorrect disk when working with these
-	commands.  When in doubt consult the kernel boot output for
-	the proper device.</para>
-
-      <para>Needless to say, we are not responsible for any damage to
-	any data or hardware that you may experience.  You work at
-	your own risk!</para>
-    </sect2>
-
-    <sect2>
-      <title>Zip, Jaz, and Other Removables</title>
-
-      <para>Removable disks can be formatted in the same way as normal
-	hard disks.  It is essential to have the disk drive connected
-	to the system and a disk placed in the drive during startup,
-	so the kernel can determine the drive's geometry.  Check the
-	<command>dmesg</command> output and make sure your device and
-	the disk's size is listed.  If the kernel reports
-
-	<informalexample>
-	  <screen>Can't get the size</screen>
-	</informalexample>
-
-	then the disk was not in the drive.  In this case, you will
-	need to restart the machine before attempting to format
-	disks.</para>
-    </sect2>
-  </sect1>
-
-  <sect1>
-    <title>Formatting Disks in Dedicated Mode</title>
-
-    <sect2>
-      <title>Introduction</title>
-
-      <para>This section details how to make disks that are totally
-	dedicated to FreeBSD.  Remember, dedicated mode disks sometimes
-	cannot be booted by the PC architecture.</para>
-    </sect2>
-
-    <sect2>
-      <title>Making Dedicated Mode Disks using Sysinstall</title>
-
-      <para><command>/stand/sysinstall</command>, the system
-	installation utility, has been expanded in recent versions to
-	make the process of dividing disks properly a less tiring
-	affair.  The fdisk and disklabel editors built into sysinstall
-	are GUI tools that remove much of the confusion from slicing
-	disks.  For FreeBSD versions 2.1.7 and later, this is perhaps
-	the simplest way to slice disks.</para>
-
-      <procedure>
-	<step>
-	  <para>Start sysinstall as root by typing
-
-	    <informalexample>
-	      <screen>&prompt.root; <userinput>/stand/sysinstall</userinput></screen>
-	    </informalexample>
-
-	    from the command prompt.</para>
-	</step>
-
-	<step>
-	  <para>Select <command>Index</command>.</para>
-	</step>
-
-	<step>
-	  <para>Select <command>Partition</command>.</para>
-	</step>
-
-	<step>
-	  <para>Select the disk to edit with arrow keys and
-	    <keycap>SPACE</keycap>.</para>
-	</step>
-
-	<step>
-	  <para>If you are using this entire disk for FreeBSD, select
-	    <command>A</command>.</para>
-	</step>
-
-	<step>
-	  <para>When asked if you still want to do this, answer
-	    <command>Yes</command>.</para>
-	</step>
-
-	<step>
-	  <para>Select <command>Write</command>.</para>
-	</step>
-
-	<step>
-	  <para>When warned about writing on installed systems, answer
-	    <command>Yes</command>.</para>
-	</step>
-
-	<step>
-	  <para>When asked about installing a boot loader, select
-	    <command>None</command> to leave the Master Boot Record
-	    untouched.  This is only needed on a new install of &os;
-	    unless the disk will be placed into another machine.</para>
-	</step>
-
-	<step>
-	  <para>Press <keycap>ENTER</keycap> on the message stating
-	    <quote>Wrote FDISK partition information out
-	    successfully</quote>.</para>
-	</step>
-
-	<step>
-	  <para><command>Quit</command>the FDISK Editor and
-	    <keycap>ESCAPE</keycap> back to the Index menu.</para>
-	</step>
-
-	<step>
-	  <para>Select <command>Label</command> from the Index
-	    menu.</para>
-	</step>
-
-	<step>
-	  <para>Label as desired.  For a single partition, enter
-	    <command>C</command> to Create a partition, accept the
-	    default size, partition type Filesystem, and a mountpoint
-	    (which is not used).</para>
-	</step>
-
-	<step>
-	  <para>Enter <command>W</command> when done and confirm to
-	    continue.  The filesystem will be newfs'd for you, unless
-	    you select otherwise (for new partitions you will want to
-	    do this!).  You will get the error:
-
-	    <informalexample>
-	      <screen>Error mounting /mnt/dev/ad2s1e on /mnt/blah : No such file or directory</screen>
-	    </informalexample>
-
-	    Ignore.</para>
-	</step>
-
-	<step>
-	  <para>Exit out by repeatedly pressing
-	    <keycap>ESCAPE</keycap>.</para>
-	</step>
-      </procedure>
-    </sect2>
-
-    <sect2>
-      <title>Making Dedicated Mode Disks Using the Command Line</title>
-
-      <para>Execute the following commands, replacing <devicename>ad2</devicename> with the
-	disk name.</para>
-
-      <informalexample>
-	<screen>&prompt.root; <userinput>dd if=/dev/zero of=/dev/ad2 count=2</userinput>
-&prompt.root; <userinput>disklabel /dev/ad2 | disklabel -B -R -r ad2 /dev/stdin</userinput>
-<lineannotation>We only want one partition, so using slice 'c' should be fine:</lineannotation>
-&prompt.root; <userinput>newfs /dev/ad2c</userinput></screen>
-      </informalexample>
-
-      <para>If you need to edit the disklabel to create multiple
-	partitions (such as swap), use the following: </para>
-
-      <informalexample>
-	<screen>&prompt.root; <userinput>dd if=/dev/zero of=/dev/ad2 count=2</userinput>
-&prompt.root; <userinput>disklabel /dev/ad2 > /tmp/label</userinput>
-<lineannotation>Edit disklabel to add partitions:</lineannotation>
-&prompt.root; <userinput>vi /tmp/label</userinput>
-&prompt.root; <userinput>disklabel -B -R -r ad2 /tmp/label</userinput>
-<lineannotation>newfs partitions appropriately</lineannotation></screen>
-      </informalexample>
-
-      <para>Your disk is now ready for use.</para>
-    </sect2>
-  </sect1>
-
-  <sect1>
-    <title>Making Compatibility Mode Disks</title>
-
-    <sect2>
-      <title>Introduction</title>
-
-      <para>The command line is the easiest way to make dedicated
-	disks, and the worst way to make compatibility disks.  The
-	command-line <command>fdisk</command> utility requires higher math skills and an
-	in-depth understanding of the slice table, which is more than
-	most people want to deal with.  Use sysinstall for
-	compatibility disks, as described below.</para>
-    </sect2>
-
-    <sect2>
-      <title>Making Compatibility Mode Disks Using Sysinstall</title>
-
-      <procedure>
-	<step>
-	  <para>Start sysinstall as root by typing
-
-	    <informalexample>
-	      <screen>&prompt.root; <userinput>/stand/sysinstall</userinput></screen>
-	    </informalexample>
-
-	    from the command prompt.</para>
-	</step>
-
-	<step>
-	  <para>Select <command>Index</command>.</para>
-	</step>
-
-	<step>
-	  <para>Select <command>Partition</command>.</para>
-	</step>
-
-	<step>
-	  <para>Select the disk to edit with arrow keys and
-	    <keycap>SPACE</keycap>.</para>
-	</step>
-
-	<step>
-	  <para>If you are using this entire disk for FreeBSD, select
-	    <command>A</command>.</para>
-	</step>
-
-	<step>
-	  <para>When asked:
-
-	    <informalexample>
-	      <screen>Do you want to do this with a true partition entry so as to remain
-cooperative with any future possible operating systems on the
-drive(s)?</screen>
-	    </informalexample>
-
-	    answer <command>yes</command>.</para>
-	</step>
-
-	<step>
-	  <para>Select <command>Write</command>.</para>
-	</step>
-
-	<step>
-	  <para>When asked to install the boot manager, select None
-	    with <keycap>SPACE</keycap> then hit
-	    <keycap>ENTER</keycap> for OK.</para>
-	</step>
-
-	<step>
-	  <para><command>Quit</command> the FDISK Editor.</para>
-	</step>
-
-	<step>
-	  <para>You will be asked about the boot manager, select
-	    <command>None</command> again. </para>
-	</step>
-
-	<step>
-	  <para>Select <command>Label</command> from the Index
-	    menu.</para>
-	</step>
-
-	<step>
-	  <para>Label as desired.  For a single partition, accept the
-	    default size, type filesystem, and a mountpoint (which
-	    is not used).</para>
-	</step>
-
-	<step>
-	  <para>The filesystem will be newfs'd for you, unless you
-	    select otherwise (for new partitions you will want to do
-	    this!).  You will get the error:
-
-	    <informalexample>
-	      <screen>Error mounting /mnt/dev/ad2s1e on /mnt/blah : No such file or directory</screen>
-	    </informalexample>
-
-	    Ignore.</para>
-	</step>
-
-	<step>
-	  <para>Exit out by repeatedly pressing
-	    <keycap>ESCAPE</keycap>.</para>
-	</step>
-      </procedure>
-
-      <para>Your new disk is now ready for use.</para>
-    </sect2>
-  </sect1>
-
-  <sect1>
-    <title>Other Disk Operations</title>
-
-    <sect2>
-      <title>Adding Swap Space</title>
-
-      <para>As a system grows, its need for swap space can also grow.
-	Although adding swap space to existing disks is very
-	difficult, a new disk can be partitioned with additional swap
-	space.</para>
-
-      <para>To add swap space when adding a disk to a system:</para>
-
-      <procedure>
-	<step>
-	  <para>When partitioning the disk, edit the disklabel and
-	    allocate the amount of swap space to add in partition `b'
-	    and the remainder in another partition, such as `a' or
-	    `e'.  The size is given in 512 byte blocks.</para>
-	</step>
-
-	<step>
-	  <para>When newfsing the drive, do NOT newfs the `c'
-	    partition.  Instead, newfs the partition where the
-	    non-swap space lies.</para>
-	</step>
-
-	<step>
-	  <para>Add an entry to <filename>/etc/fstab</filename> as
-	    follows:</para>
-
-	  <informalexample>
-	    <programlisting>/dev/ad0b                       none            swap    sw 0 0
-	    </programlisting>
-	  </informalexample>
-
-	  <para>Change <filename>/dev/ad0b</filename> to the device of the newly added
-	    space.</para>
-	</step>
-
-	<step>
-	  <para>To make the new space immediately available, use the
-	    <command>swapon</command> command.
-
-	    <informalexample>
-	      <screen>&prompt.root; <userinput>swapon /dev/da0b</userinput>
-swapon:  added /dev/da0b as swap space</screen>
-	    </informalexample>
-	  </para>
-	</step>
-      </procedure>
-    </sect2>
-
-    <sect2>
-      <title>Copying the Contents of Disks</title>
-<!-- Should have specific tag -->
-
-      <para>Submitted By:  Renaud Waldura
-	(<email>renaud@softway.com</email>) </para>
-
-      <para>To move file from your original base disk to the fresh new
-	one, do:
-
-	<informalexample>
-	  <screen>&prompt.root; <userinput>mount /dev/ad2 /mnt</userinput>
-&prompt.root; <userinput>pax -r -w -p e /usr/home /mnt</userinput>
-&prompt.root; <userinput>umount /mnt</userinput>
-&prompt.root; <userinput>rm -rf /usr/home/*</userinput>
-&prompt.root; <userinput>mount /dev/ad2 /usr/home</userinput></screen>
-	</informalexample>
-      </para>
-    </sect2>
-
-    <sect2>
-      <title>Creating Striped Disks using CCD</title>
-
-      <para>Commands Submitted By: Stan Brown
-	(<email>stanb@awod.com</email>) </para>
-
-      <para>The Concatenated Disk Driver, or CCD, allows you to treat
-	several identical disks as a single disk.  Striping can result
-	in increased disk performance by distributing reads and writes
-	across the disks.  See the &man.ccd.4; and &man.ccdconfig.8;
-	manual pages or the <ulink
-	  url="http://stampede.cs.berkeley.edu/ccd/">CCD
-	  Homepage</ulink> for further details.</para>
-
-      <para>You no longer need to build a special kernel to run ccd.  When you
-	run <command>ccdconfig</command>, it will load the KLD for you if the
-	kernel does not contain CCD support.</para>
-
-      <para>You build CCDs on disk partitions of type
-	<emphasis>4.2BSD</emphasis>.  If you want to use the entire disk, you
-	still need to create a new partition.  For example, <userinput>disklabel
-	-e</userinput> might show:</para>
-
-      <informalexample>
-	<screen>#        size   offset    fstype   [fsize bsize bps/cpg]
-  c: 60074784        0    unused        0     0     0   # (Cyl.    0 - 59597)</screen>
-      </informalexample>
-
-      <para>You should not use partition <emphasis>c</emphasis> for the CCD,
-      since it is of type <emphasis>unused</emphasis>.  Instead, create a new
-      partition of exactly the same size, but with type
-      <emphasis>4.2BSD</emphasis>:</para>
-
-      <informalexample>
-	<screen>#        size   offset    fstype   [fsize bsize bps/cpg]
-  c: 60074784        0    unused        0     0     0   # (Cyl.    0 - 59597)
-<userinput>   e: 60074784        0    4.2BSD        0     0     0   # (Cyl.    0 - 59597)</userinput></screen>
-      </informalexample>
-
-	<para>To create a new CCD, execute the following commands.  This
-	describes how to add three disks together; simply add or remove devices
-	as necessary.  Remember that the disks to be striped must be
-	<emphasis>identical.</emphasis></para>
-
-      <informalexample>
-	<screen>&prompt.root; <userinput>cd /dev ; sh MAKEDEV ccd0</userinput>
-
-&prompt.root; <userinput>disklabel -r -w da0 auto</userinput>
-&prompt.root; <userinput>disklabel -r -w da1 auto</userinput>
-&prompt.root; <userinput>disklabel -r -w da2 auto</userinput>
-
-&prompt.root; <userinput>disklabel -e da0</userinput>
-<lineannotation>Add partition e with type 4.2BSD</lineannotation>
-&prompt.root; <userinput>disklabel -e da1</userinput>
-<lineannotation>Add partition e with type 4.2BSD</lineannotation>
-&prompt.root; <userinput>disklabel -e da2</userinput>
-<lineannotation>Add partition e with type 4.2BSD</lineannotation>
-
-&prompt.root; <userinput>ccdconfig ccd0 273 0 /dev/da0e /dev/da1e /dev/da2e</userinput>
-
-&prompt.root; <userinput>newfs /dev/ccd0c</userinput></screen>
-      </informalexample>
-
-      <para>The value 273 is the stripe size.  This is the number of disk
-      sectors (of 512 bytes each) in each block of data on the CCD.  It should
-      be at least 128 kB, and it should not be not be a power of 2.</para>
-
-      <para>Now you can mount and use your CCD by referencing device
-	<filename>/dev/ccd0c</filename>.</para>
-
-      <para>A more powerful and flexible alternative to CCD is Vinum.  See the
-        <ulink url="http://www.vinumvm.org/">Vinum Project home page</ulink>
-        for further details.</para>
-    </sect2>
-  </sect1>
-
-  <sect1>
-    <title>Credits</title>
-
-    <para>The author would like to thank the following individuals for
-      their contributions to this project:</para>
-
-    <itemizedlist>
-      <listitem>
-	<para>Darryl Okahata
-	  (<email>darrylo@hpnmhjw.sr.hp.com</email>) for his simple
-	  dedicated mode setup documentation which I have used
-	  repeatedly on FreeBSD-questions.</para>
-      </listitem>
-
-      <listitem>
-	<para>&a.jkh; for making sysinstall useful for this type of task.
-	  </para>
-      </listitem>
-
-      <listitem>
-	<para>John Fieber (<email>jfieber@indiana.edu</email>) for
-	  making information and examples of the DocBook DTD on which
-	  this document is based.</para>
-      </listitem>
-
-      <listitem>
-	<para>&a.grog; for checking my work and pointing out inaccuracies,
-	  as well as miscellaneous support.</para>
-      </listitem>
-    </itemizedlist>
-  </sect1>
-</article>
diff --git a/en_US.ISO8859-1/articles/linux-users/article.sgml b/en_US.ISO8859-1/articles/linux-users/article.sgml
index b610e2f017..e8a6a5ab98 100644
--- a/en_US.ISO8859-1/articles/linux-users/article.sgml
+++ b/en_US.ISO8859-1/articles/linux-users/article.sgml
@@ -129,10 +129,6 @@ in your /etc/rc.conf. Extra options can be found in startup script.</screen>
           <ulink url="ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-6-stable/Latest/"></ulink>
           to download the most recent packages built for the
 	  6.X series.</para>
-
-        <para>You can read more about the &os; versions in the article
-	  <ulink url="&url.base;/doc/en_US.ISO8859-1/articles/version-guide/">
-	    Choosing the &os; Version That Is Right For You</ulink>.</para>
       </note>
 
       <para>For more information on packages please refer to section 4.4 of
diff --git a/en_US.ISO8859-1/articles/multi-os/Makefile b/en_US.ISO8859-1/articles/multi-os/Makefile
deleted file mode 100644
index 8becfa753e..0000000000
--- a/en_US.ISO8859-1/articles/multi-os/Makefile
+++ /dev/null
@@ -1,17 +0,0 @@
-#
-# $FreeBSD$
-#
-# Article: Installing and Using FreeBSD With Other Operating Systems
-
-DOC?= article
-
-FORMATS?= html
-WITH_ARTICLE_TOC?= YES
-
-INSTALL_COMPRESSED?=gz
-INSTALL_ONLY_COMPRESSED?=
-
-SRCS=	article.sgml
-
-DOC_PREFIX?= ${.CURDIR}/../../..
-.include "${DOC_PREFIX}/share/mk/doc.project.mk"
diff --git a/en_US.ISO8859-1/articles/multi-os/article.sgml b/en_US.ISO8859-1/articles/multi-os/article.sgml
deleted file mode 100644
index 292c8d270e..0000000000
--- a/en_US.ISO8859-1/articles/multi-os/article.sgml
+++ /dev/null
@@ -1,756 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1" standalone="no"?>
-<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V4.2-Based Extension//EN"
-	"../../../share/sgml/freebsd42.dtd" [
-<!ENTITY % entities PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Entity Set//EN" "../../share/sgml/entities.ent">
-%entities;
-]>
-
-<!-- $FreeBSD$ -->
-
-<article lang='en'>
-  <articleinfo>
-    <title>Installing and Using FreeBSD With Other Operating Systems</title>
-
-    <authorgroup>
-      <author>
-	<firstname>Jay</firstname>
-
-	<surname>Richmond</surname>
-
-	<affiliation>
-	  <address>
-	    <email>jayrich@sysc.com</email>
-	  </address>
-	</affiliation>
-      </author>
-    </authorgroup>
-
-    <pubdate>6 August 1996</pubdate>
-
-    <legalnotice id="trademarks" role="trademarks">
-      &tm-attrib.freebsd;
-      &tm-attrib.ibm;
-      &tm-attrib.linux;
-      &tm-attrib.microsoft;
-      &tm-attrib.powerquest;
-      &tm-attrib.general;
-    </legalnotice>
-
-    <releaseinfo>$FreeBSD$</releaseinfo>
-
-    <abstract>
-      <para>This document discusses how to make FreeBSD coexist nicely
-	with other popular operating systems such as Linux, &ms-dos;,
-	&os2;, and &windows; 95.  Special thanks to: Annelise Anderson
-	<email>andrsn@stanford.edu</email>, Randall Hopper
-	<email>rhh@ct.picker.com</email>, and &a.jkh;.</para>
-    </abstract>
-  </articleinfo>
-
-  <sect1>
-    <title>Overview</title>
-
-    <para>Most people can not fit these operating systems together
-      comfortably without having a larger hard disk, so special
-      information on large EIDE drives is included.  Because there are
-      so many combinations of possible operating systems and hard disk
-      configurations, the <xref linkend="ch5"/> section may be of the
-      most use to you.  It contains descriptions of specific working
-      computer setups that use multiple operating systems.</para>
-
-    <para>This document assumes that you have already made room on
-      your hard disk for an additional operating system.  Any time you
-      repartition your hard drive, you run the risk of destroying the
-      data on the original partitions.  However, if your hard drive is
-      completely occupied by DOS, you might find the FIPS utility
-      (included on the FreeBSD CDROM in the
-      <filename>\TOOLS</filename> directory or via <ulink
-	url="ftp://ftp.FreeBSD.org/pub/FreeBSD/tools/">ftp</ulink>)
-      useful.  It lets you repartition your hard disk without
-      destroying the data already on it.  There is also a commercial
-      program available called <application>&partitionmagic;</application>, which lets you size
-      and delete partitions without consequence.</para>
-  </sect1>
-
-  <sect1 id="ch2">
-    <title>Overview of Boot Managers</title>
-
-    <para>These are just brief descriptions of some of the different
-      boot managers you may encounter.  Depending on your computer
-      setup, you may find it useful to use more than one of them on
-      the same system.</para>
-
-    <variablelist>
-      <varlistentry>
-	<term>Boot Easy</term>
-
-	<listitem>
-	  <para>This is the default boot manager used with FreeBSD.
-	    It has the ability to boot most anything, including BSD,
-	    &os2; (HPFS), &windows; 95 (FAT and FAT32), and Linux.
-	    Partitions are selected with the function keys.</para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-	<term>&os2; Boot Manager</term>
-
-	<listitem>
-	  <para>This will boot FAT, FAT32, HPFS, FFS (FreeBSD), and EXT2
-	    (Linux).  Partitions
-	    are selected using arrow keys.  The &os2; Boot Manager is
-	    the only one to use its own separate partition, unlike the
-	    others which use the master boot record (MBR).  Therefore,
-	    it must be installed below the 1024th cylinder to avoid
-	    booting problems.  It can boot Linux using LILO when it is
-	    part of the boot sector, not the MBR.  Go to <ulink
-	      url="http://www.linuxresources.com/LDP/HOWTO/HOWTO-INDEX.html">Linux
-	      HOWTOs</ulink> on the World Wide Web for more
-	    information on booting Linux with the &os2; boot
-	    manager.</para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-	<term>OS-BS</term>
-
-	<listitem>
-	  <para>This is an alternative to Boot Easy.  It gives you more
-	    control over the booting process, with the ability to set
-	    the default partition to boot and the booting timeout.
-	    The beta version of this programs allows you to boot by
-	    selecting the OS with your arrow keys.  It is included on
-	    the FreeBSD CD in the <filename class="directory">\TOOLS</filename>
-	    directory, and via <ulink
-	      url="ftp://ftp.FreeBSD.org/pub/FreeBSD/tools/">ftp</ulink>.</para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-	<term>LILO, or LInux LOader</term>
-
-	<listitem>
-	  <para>This is a limited boot manager.  It will boot FreeBSD,
-	    though some customization work is required in the LILO
-	    configuration file.</para>
-	</listitem>
-      </varlistentry>
-    </variablelist>
-
-    <note id="fat32">
-      <title>About FAT32</title>
-
-      <para>FAT32 is the replacement to the FAT filesystem included in
-	Microsoft's OEM SR2 Beta release, which started replacing FAT
-	on computers pre-loaded with &windows; 95 towards the
-	end of 1996.  It converts the normal FAT filesystem and
-	allows you to use smaller cluster sizes for larger hard
-	drives.  FAT32 also modifies the traditional FAT boot sector
-	and allocation table, making it incompatible with some boot
-	managers.</para>
-    </note>
-  </sect1>
-
-  <sect1 id="ch3">
-    <title>A Typical Installation</title>
-
-    <para>Let's say I have two large EIDE hard drives, and I want to
-      install FreeBSD, Linux, and &windows; 95 on them.</para>
-
-    <para>Here is how I might do it using these hard disks:</para>
-
-    <itemizedlist>
-      <listitem>
-	<para><filename>/dev/wd0</filename> (first physical hard disk)</para>
-      </listitem>
-
-      <listitem>
-	<para><filename>/dev/wd1</filename> (second hard disk)</para>
-      </listitem>
-    </itemizedlist>
-
-    <para>Both disks have 1416 cylinders.</para>
-
-    <procedure>
-      <step>
-	<para>I boot from a &ms-dos; or &windows; 95 boot disk that
-	  contains the <filename>FDISK.EXE</filename> utility and make a small
-	  50&nbsp;MB primary partition (35-40 for &windows; 95, plus a
-	  little breathing room) on the first disk.  Also create a
-	  larger partition on the second hard disk for my &windows;
-	  applications and data.</para>
-	</step>
-
-      <step>
-	<para>I reboot and install &windows; 95 (easier said than done)
-	  on the <filename>C:</filename> partition.</para>
-      </step>
-
-      <step>
-	<para>The next thing I do is install Linux.  I am not sure
-	  about all the distributions of Linux, but <ulink url="http://www.slackware.com">Slackware</ulink> includes
-	  LILO (see <xref linkend="ch2"/>).  When I am partitioning out
-	  my hard disk with Linux <command>fdisk</command>, I would
-	  put all of Linux on the first drive (maybe 300&nbsp;MB for a
-	  nice root partition and some swap space).</para>
-      </step>
-
-      <step>
-	<para>After I install Linux, and are prompted about installing
-	  LILO, make <emphasis>sure</emphasis> that I install it on the boot sector of my
-	  root Linux partition, not in the MBR (master boot
-	  record).</para>
-      </step>
-
-      <step>
-	<para>The remaining hard disk space can go to FreeBSD.  I also
-	  make sure that my FreeBSD root slice does not go beyond the
-	  1024th cylinder.  (The 1024th cylinder is 528&nbsp;MB into the
-	  disk with our hypothetical 720&nbsp;MB disks).  I will use the
-	  rest of the hard drive (about 270&nbsp;MB) for the
-	  <filename class="directory">/usr</filename> and <filename class="directory">/</filename> slices if I wish.  The
-	  rest of the second hard disk (size depends on the amount of
-	  my &windows; application/data partition that I created in step
-	  1) can go to the <filename class="directory">/usr/src</filename> slice and swap
-	  space.</para>
-      </step>
-
-      <step>
-	<para>When viewed with the &windows; 95 <command>fdisk</command>
-	  utility, my hard drives should now look something like this:
-
-	  <screen>---------------------------------------------------------------------
-
-                  Display Partition Information
-
-Current fixed disk drive: 1
-
-Partition  Status  Type  Volume_Label  Mbytes  System  Usage
-C: 1          A   PRI DOS                50    FAT**     7%
-   2          A   Non-DOS (Linux)       300             43%
-
-Total disk space is  696 Mbytes (1 Mbyte = 1048576 bytes)
-
-Press Esc to continue
-
----------------------------------------------------------------------
-
-                  Display Partition Information
-
-Current fixed disk drive: 2
-
-Partition  Status  Type  Volume_Label  Mbytes  System  Usage
-D: 1          A   PRI DOS                420   FAT**    60%
-
-Total disk space is  696 Mbytes (1 Mbyte = 1048576 bytes)
-
-Press Esc to continue
-
----------------------------------------------------------------------</screen>
-	  ** May say FAT16 or FAT32 if you are using the OEM SR2
-	  update.  See <xref linkend="ch2"/>.</para>
-      </step>
-
-      <step>
-	<para>Install FreeBSD.  I make sure to boot with my first hard
-	  disk set at <quote>NORMAL</quote> in the BIOS.  If it is not,
-	  I will have the enter my true disk geometry at boot time (to
-	  get this, boot &windows; 95 and consult Microsoft Diagnostics
-	  (<filename>MSD.EXE</filename>), or check your BIOS) with the
-	  parameter <literal>hd0=1416,16,63</literal> where
-	  <replaceable>1416</replaceable> is the number of cylinders on my hard
-	  disk, <replaceable>16</replaceable> is the number of heads per track,
-	  and <replaceable>63</replaceable> is the number of sectors per track on
-	  the drive.</para>
-      </step>
-
-      <step>
-	<para>When partitioning out the hard disk, I make sure to
-	  install Boot Easy on the first disk.  I do not worry about
-	  the second disk, nothing is booting off of it.</para>
-      </step>
-
-      <step>
-	<para>When I reboot, Boot Easy should recognize my three
-	  bootable partitions as DOS (&windows; 95), Linux, and BSD
-	  (FreeBSD).</para>
-      </step>
-    </procedure>
-  </sect1>
-
-  <sect1 id="ch4">
-    <title>Special Considerations</title>
-
-    <para>Most operating systems are very picky about where and how
-      they are placed on the hard disk.  &windows; 95 and DOS need to be
-      on the first primary partition on the first hard disk.  &os2; is
-      the exception.  It can be installed on the first or second disk
-      in a primary or extended partition.  If you are not sure, keep
-      the beginning of the bootable partitions below the 1024th
-      cylinder.</para>
-
-    <para>If you install &windows; 95 on an existing BSD system, it will
-      <quote>destroy</quote> the MBR, and you will have to reinstall your
-      previous boot manager.  Boot Easy can be reinstalled by using
-      the <filename>BOOTINST.EXE</filename> utility included in the <filename class="directory">\TOOLS</filename> directory on the
-      CDROM, and via <ulink
-	url="ftp://ftp.FreeBSD.org/pub/FreeBSD/tools/">ftp</ulink>.
-      You can also re-start the installation process and go to the
-      partition editor.  From there, mark the FreeBSD partition as
-      bootable, select Boot Manager, and then type W to (W)rite out
-      the information to the MBR.  You can now reboot, and Boot Easy
-      should then recognize &windows; 95 as DOS.</para>
-
-    <para>Please keep in mind that &os2; can read FAT and HPFS
-      partitions, but not FFS (FreeBSD) or EXT2 (Linux) partitions.
-      Likewise, &windows; 95 can only read and write to FAT and FAT32
-      (see <xref linkend="ch2"/>) partitions.  FreeBSD can read most
-      filesystems, but currently cannot read HPFS partitions.  Linux
-      can read HPFS partitions, but can not write to them.  Recent
-      versions of the Linux kernel (2.x) can read and write to &windows;
-      95 VFAT partitions (VFAT is what gives &windows; 95 long file
-      names - it is pretty much the same as FAT).  Linux can read and
-      write to most filesystems.  Got that?  I hope so.</para>
-  </sect1>
-
-  <sect1 id="ch5">
-    <title>Examples</title>
-
-    <para><emphasis>(section needs work, please send your example to
-	<email>jayrich@sysc.com</email>)</emphasis>.</para>
-
-    <para>FreeBSD + &windows; 95:  If you installed FreeBSD after &windows; 95,
-      you should see <literal>DOS</literal> on the Boot Easy menu.  This is
-      &windows; 95.  If you installed &windows; 95 after FreeBSD, read
-      <xref linkend="ch4"/> above.  As long as your hard disk does not
-      have 1024 cylinders you should not have a problem booting.  If
-      one of your partitions goes beyond the 1024th cylinder however,
-      and you get messages like <errorname>invalid system disk</errorname>
-      under DOS (&windows; 95) and FreeBSD will not boot, try looking
-      for a setting in your BIOS called <quote>&gt; 1024 cylinder
-	support</quote> or <quote>NORMAL/LBA</quote> mode.  DOS may need LBA
-      (Logical Block Addressing) in order to boot correctly.  If the
-      idea of switching BIOS settings every time you boot up does not
-      appeal to you, you can boot FreeBSD through DOS via the
-      <filename>FBSDBOOT.EXE</filename> utility on the CD (It should find your
-      FreeBSD partition and boot it.)</para>
-
-    <para>FreeBSD + &os2; + &windows; 95:  Nothing new here.  The &os2; boot manager
-      can boot all of these operating systems, so that should not be a
-      problem.</para>
-
-    <para>FreeBSD + Linux: You can also use Boot Easy to boot both
-      operating systems.</para>
-
-    <para>FreeBSD + Linux + &windows; 95:  (see <xref linkend="ch3"/>)</para>
-  </sect1>
-
-  <sect1 id="sources">
-    <title>Other Sources of Help</title>
-
-    <para>There are many <ulink
-	url="http://www.linuxresources.com/LDP/HOWTO/HOWTO-INDEX.html">Linux
-	HOW-TOs</ulink> that deal with multiple operating systems on
-      the same hard disk.</para>
-
-    <para>The <ulink
-	url="http://www.linuxresources.com/LDP/HOWTO/mini/Linux+DOS+Win95+OS2.html">Linux+DOS+Win95+OS2
-	mini-HOWTO</ulink> offers help on configuring the &os2; boot
-      manager, and the <ulink
-	url="http://www.linuxresources.com/LDP/HOWTO/mini/Linux+FreeBSD.html">Linux+FreeBSD
-	mini-HOWTO</ulink> might be interesting as well.  The <ulink
-	url="http://www.in.net/~jkatz/win95/Linux-HOWTO.html">Linux-HOWTO</ulink>
-      is also helpful.</para>
-
-    <para>The <ulink
-	url="http://www.tburke.net/info/ntldr/ntldr_hacking_guide.htm">&windowsnt;
-	Loader Hacking Guide</ulink> provides good information on
-      multibooting &windowsnt;, &windows; 95, and DOS with other operating
-      systems.</para>
-
-    <para>And Hale Landis's <quote>How It Works</quote> document pack contains some
-      good info on all sorts of disk geometry and booting related
-      topics.  You can find it at
-      <ulink url="ftp://fission.dt.wdc.com/pub/otherdocs/pc_systems/how_it_works/allhiw.zip"></ulink>.</para>
-
-    <para>Finally, do not overlook FreeBSD's kernel documentation on
-      the booting procedure, available in the kernel source
-      distribution (it unpacks to <ulink
-	url="file://localhost/usr/src/sys/i386/boot/biosboot/README.386BSD">/usr/src/sys/i386/boot/biosboot/README.386BSD</ulink>.</para>
-  </sect1>
-
-  <sect1>
-    <title>Technical Details</title>
-
-    <para><emphasis>(Contributed by Randall Hopper,
-	<email>rhh@ct.picker.com</email>)</emphasis></para>
-
-    <para>This section attempts to give you enough basic information
-      about your hard disks and the disk booting process so that you
-      can troubleshoot most problems you might encounter when getting
-      set up to boot several operating systems.  It starts in pretty
-      basic terms, so you may want to skim down in this section until
-      it begins to look unfamiliar and then start reading.</para>
-
-    <sect2>
-      <title>Disk Primer</title>
-
-      <para>Three fundamental terms are used to describe the location
-	of data on your hard disk: Cylinders, Heads, and Sectors.
-	It is not particularly important to know what these terms
-	relate to except to know that, together, they identify where
-	data is physically on your disk.</para>
-
-      <para>Your disk has a particular number of cylinders, number of
-	heads, and number of sectors per cylinder-head (a
-	cylinder-head also known now as a track).  Collectively this
-	information defines the <quote>physical disk geometry</quote> for your hard
-	disk.  There are typically 512 bytes per sector, and 63
-	sectors per track, with the number of cylinders and heads
-	varying widely from disk to disk.  Thus you can figure the
-	number of bytes of data that will fit on your own disk by
-	calculating:</para>
-
-	<informalexample>
-	  <para>(# of cylinders) &times; (# heads) &times; (63
-	    sectors/track) &times; (512 bytes/sect)</para>
-	</informalexample>
-
-      <para>For example, on my 1.6 Gig Western Digital AC31600 EIDE hard
-	disk, that is:</para>
-
-	<informalexample>
-	  <para>(3148 cyl) &times; (16 heads) &times; (63
-	    sectors/track) &times; (512 bytes/sect)</para>
-	</informalexample>
-
-      <para>which is 1,624,670,208 bytes, or around 1.6 Gig.</para>
-
-      <para>You can find out the physical disk geometry (number of
-	cylinders, heads, and sectors/track counts) for your hard
-	disks using ATAID or other programs off the net.  Your hard
-	disk probably came with this information as well.  Be careful
-	though: if you are using BIOS LBA (see <xref
-	  linkend="limits"/>), you can not use just any program to get
-	the physical geometry.  This is because many programs (e.g.
-	<filename>MSD.EXE</filename> or FreeBSD fdisk) do not identify the
-	physical disk geometry; they instead report the
-	<firstterm>translated geometry</firstterm> (virtual numbers from using
-	LBA).  Stay tuned for what that means.</para>
-
-      <para>One other useful thing about these terms.  Given 3
-	numbers&mdash;a cylinder number, a head number, and a
-	sector-within-track number&mdash;you identify a specific
-	absolute sector (a 512 byte block of data) on your disk.
-	Cylinders and Heads are numbered up from 0, and Sectors are
-	numbered up from 1.</para>
-
-      <para>For those that are interested in more technical details,
-	information on disk geometry, boot sectors, BIOSes, etc. can
-	be found all over the net.  Query Lycos, Yahoo, etc. for
-	<literal>boot sector</literal> or <literal>master boot record</literal>.
-	Among the useful info you will find are Hale Landis's
-	<citetitle>How It Works</citetitle> document pack.  See the <xref
-	  linkend="sources"/> section for a few pointers to this
-	pack.</para>
-
-      <para>Ok, enough terminology.  We are talking about booting
-	here.</para>
-    </sect2>
-
-    <sect2 id="booting">
-      <title>The Booting Process</title>
-
-      <para>On the first sector of your disk (Cyl 0, Head 0, Sector 1)
-	lives the Master Boot Record (MBR).  It contains a map of your
-	disk.  It identifies up to 4 <firstterm>partitions</firstterm>, each of
-	which is a contiguous chunk of that disk.  FreeBSD calls
-	partitions <firstterm>slices</firstterm> to avoid confusion with its
-	own partitions, but we will not do that here.  Each partition can
-	contain its own operating system.</para>
-
-      <para>Each partition entry in the MBR has a <firstterm>Partition
-	  ID</firstterm>, a <firstterm>Start Cylinder/Head/Sector</firstterm>, and an
-	<firstterm>End Cylinder/Head/Sector</firstterm>.  The Partition ID
-	tells what type of partition it is (what OS) and the Start/End
-	tells where it is.  <xref linkend="tbl-pid"/> lists a
-	smattering of some common Partition IDs.</para>
-
-      <table id="tbl-pid">
-	<title>Partition IDs</title>
-
-	<tgroup cols="2">
-	  <thead>
-	    <row>
-	      <entry>ID (hex)</entry>
-	      <entry>Description</entry>
-	    </row>
-	  </thead>
-
-	  <tbody>
-	    <row>
-	      <entry>01</entry>
-	      <entry>Primary DOS12 (12-bit FAT)</entry>
-	    </row>
-
-	    <row>
-	      <entry>04</entry>
-	      <entry>Primary DOS16 (16-bit FAT)</entry>
-	    </row>
-
-	    <row>
-	      <entry>05</entry>
-	      <entry>Extended DOS</entry>
-	    </row>
-
-	    <row>
-	      <entry>06</entry>
-	      <entry>Primary big DOS (&gt; 32MB)</entry>
-	    </row>
-
-	    <row>
-	      <entry>0A</entry>
-	      <entry>&os2;</entry>
-	    </row>
-
-	    <row>
-	      <entry>83</entry>
-	      <entry>Linux (EXT2FS)</entry>
-	    </row>
-
-	    <row>
-	      <entry>A5</entry>
-	      <entry>FreeBSD, NetBSD, 386BSD (UFS)</entry>
-	    </row>
-	  </tbody>
-	</tgroup>
-      </table>
-
-      <para>Note that not all partitions are bootable (e.g. Extended
-	DOS).  Some are&mdash;some are not.  What makes a partition
-	bootable is the configuration of the <firstterm>Partition Boot
-	  Sector</firstterm> that exists at the beginning of each
-	partition.</para>
-
-      <para>When you configure your favorite boot manager, it looks up
-	the entries in the MBR partition tables of all your hard disks
-	and lets you name the entries in that list.  Then when you
-	boot, the boot manager is invoked by special code in the
-	Master Boot Sector of the first probed hard disk on your
-	system.  It looks at the MBR partition table entry
-	corresponding to the partition choice you made, uses the Start
-	Cylinder/Head/Sector information for that partition, loads up
-	the Partition Boot Sector for that partition, and gives it
-	control.  That Boot Sector for the partition itself contains
-	enough information to start loading the operating system on
-	that partition.</para>
-
-      <para>One thing we just brushed past that is important to know.
-	All of your hard disks have MBRs.  However, the one that is
-	important is the one on the disk that is first probed by the
-	BIOS.  If you have only IDE hard disks, it is the first IDE disk
-	(e.g. primary disk on first controller).  Similarly for SCSI
-	only systems.  If you have both IDE and SCSI hard disks
-	though, the IDE disk is typically probed first by the BIOS, so
-	the first IDE disk is the first probed disk.  The boot manager
-	you will install will be hooked into the MBR on this first
-	probed hard disk that we have just described.</para>
-    </sect2>
-
-    <sect2 id="limits">
-      <title>Booting Limitations and Warnings</title>
-
-      <para>Now the interesting stuff that you need to watch out
-	for.</para>
-
-      <sect3>
-	<title>The dreaded 1024 cylinder limit and how BIOS LBA helps</title>
-
-	<para>The first part of the booting process is all done
-	  through the BIOS, (if that is a new term to you, the BIOS is
-	  a software chip on your system motherboard which provides
-	  startup code for your computer).  As such, this first part
-	  of the process is subject to the limitations of the BIOS
-	  interface.</para>
-
-	<para>The BIOS interface used to read the hard disk during
-	  this period (INT 13H, Subfunction 2) allocates 10 bits to
-	  the Cylinder Number, 8 bits to the Head Number, and 6 bits
-	  to the Sector Number.  This restricts users of this
-	  interface (i.e. boot managers hooked into your disk's MBR as
-	  well as OS loaders hooked into the Boot Sectors) to the
-	  following limits:</para>
-
-      <itemizedlist>
-	<listitem>
-	  <para>1024 cylinders, max</para>
-	</listitem>
-
-	<listitem>
-	  <para>256 heads, max</para>
-	</listitem>
-
-	<listitem>
-	  <para>64 sectors/track, max (actually 63, <literal>0</literal>
-	    is not available)</para>
-	</listitem>
-      </itemizedlist>
-
-	<para>Now big hard disks have lots of cylinders but not a lot
-	  of heads, so invariably with big hard disks the number of
-	  cylinders is greater than 1024.  Given this and the BIOS
-	  interface as is, you can not boot off just anywhere on your
-	  hard disk.  The boot code (the boot manager and the OS
-	  loader hooked into all bootable partitions' Boot Sectors)
-	  has to reside below cylinder 1024.  In fact, if your hard
-	  disk is typical and has 16 heads, this equates to:</para>
-
-	<informalexample>
-	  <para>1024 cyl/disk &times; 16 heads/disk &times; 63
-	    sect/(cyl-head) &times; 512 bytes/sector</para>
-	</informalexample>
-
-	<para>which is around the often-mentioned 528MB limit.</para>
-
-	<para>This is where BIOS LBA (Logical Block Addressing) comes
-	  in.  BIOS LBA gives the user of the BIOS API calls access to
-	  physical cylinders above 1024 though the BIOS interfaces by
-	  redefining a cylinder.  That is, it remaps your cylinders
-	  and heads, making it appear through the BIOS as though the
-	  disk has fewer cylinders and more heads than it actually
-	  does.  In other words, it takes advantage of the fact that
-	  hard disks have relatively few heads and lots of cylinders
-	  by shifting the balance between number of cylinders and
-	  number of heads so that both numbers lie below the
-	  above-mentioned limits (1024 cylinders, 256 heads).</para>
-
-	<para>With BIOS LBA, the hard disk size limitation is
-	  virtually removed (well, pushed up to 8 Gigabytes anyway).
-	  If you have an LBA BIOS, you can put FreeBSD or any OS
-	  anywhere you want and not hit the 1024 cylinder
-	  limit.</para>
-
-	<para>To use my 1.6 Gig Western Digital as an example again,
-	  its physical geometry is:</para>
-
-	<informalexample>
-	  <para>(3148 cyl, 16 heads, 63 sectors/track, 512
-	    bytes/sector)</para>
-	</informalexample>
-
-	<para>However, my BIOS LBA remaps this to:</para>
-
-	<informalexample>
-	  <para>(787 cyl, 64 heads, 63 sectors/track, 512
-	    bytes/sector)</para>
-	</informalexample>
-
-	<para>giving the same effective size disk, but with cylinder
-	  and head counts within the BIOS API's range (Incidentally, I
-	  have both Linux and FreeBSD existing on one of my hard disks
-	  above the 1024th physical cylinder, and both operating
-	  systems boot fine, thanks to BIOS LBA).</para>
-      </sect3>
-
-      <sect3>
-	<title>Boot Managers and Disk Allocation</title>
-
-	<para>Another gotcha to watch out when installing boot
-	  managers is allocating space for your boot manager.  It is
-	  best to be aware of this issue up front to save yourself
-	  from having to reinstall one or more of your OSs.</para>
-
-	<para>If you followed the discussion in <xref
-	    linkend="booting"/> about the Master Boot Sector (where the
-	  MBR is), Partition Boot Sectors, and the booting process,
-	  you may have been wondering just exactly where on your hard
-	  disk that nifty boot manager is going to live.  Well, some
-	  boot managers are small enough to fit entirely within the
-	  Master Boot Sector (Cylinder 0, Head 0, Sector 0) along with
-	  the partition table.  Others need a bit more room and
-	  actually extend a few sectors past the Master Boot Sector in
-	  the Cylinder 0 Head 0 track, since that is typically
-	  free&hellip;typically.</para>
-
-	<para>That is the catch.  Some operating systems (FreeBSD
-	  included) let you start their partitions right after the
-	  Master Boot Sector at Cylinder 0, Head 0, Sector 2 if you
-	  want.  In fact, if you give FreeBSD's sysinstall a disk with
-	  an empty chunk up front or the whole disk empty, that is
-	  where it will start the FreeBSD partition by default (at least
-	  it did when I fell into this trap).  Then when you go to
-	  install your boot manager, if it is one that occupies a few
-	  extra sectors after the MBR, it will overwrite the front of
-	  the first partition's data.  In the case of FreeBSD, this
-	  overwrites the disk label, and renders your FreeBSD
-	  partition unbootable.</para>
-
-	<para>The easy way to avoid this problem (and leave yourself
-	  the flexibility to try different boot managers later) is
-	  just to always leave the first full track on your disk
-	  unallocated when you partition your disk.  That is, leave
-	  the space from Cylinder 0, Head 0, Sector 2 through Cylinder
-	  0, Head 0, Sector 63 unallocated, and start your first
-	  partition at Cylinder 0, Head 1, Sector 1.  For what it is
-	  worth, when you create a DOS partition at the front of your
-	  disk, DOS leaves this space open by default (this is why
-	  some boot managers assume it is free).  So creating a DOS
-	  partition up at the front of your disk avoids this problem
-	  altogether.  I like to do this myself, creating 1 Meg DOS
-	  partition up front, because it also avoids my primary DOS
-	  drive letters shifting later when I repartition.</para>
-
-	<para>For reference, the following boot managers use the
-	  Master Boot Sector to store their code and data:</para>
-
-	<itemizedlist>
-	  <listitem>
-	    <para>OS-BS 1.35</para>
-	  </listitem>
-
-	  <listitem>
-	    <para>Boot Easy</para>
-	  </listitem>
-
-	  <listitem>
-	    <para>LILO</para>
-	  </listitem>
-	</itemizedlist>
-
-	<para>These boot managers use a few additional sectors after
-	  the Master Boot Sector:</para>
-
-	<itemizedlist>
-	  <listitem>
-	    <para>OS-BS 2.0 Beta 8 (sectors 2-5)</para>
-	  </listitem>
-
-	  <listitem>
-	    <para>The &os2; boot manager</para>
-	  </listitem>
-	</itemizedlist>
-      </sect3>
-
-      <sect3>
-	<title>What if your machine will not boot?</title>
-
-	<para>At some point when installing boot managers, you might
-	  leave the MBR in a state such that your machine will not boot.
-	  This is unlikely, but possible when re-FDISKing underneath
-	  an already-installed boot manager.</para>
-
-	<para>If you have a bootable DOS partition on your disk, you
-	  can boot off a DOS floppy, and run:</para>
-
-	<informalexample>
-	  <screen>A:\> <userinput>FDISK /MBR</userinput></screen>
-	</informalexample>
-
-	<para>to put the original, simple DOS boot code back into the
-	  system.  You can then boot DOS (and DOS only) off the hard
-	  drive.  Alternatively, just re-run your boot manager
-	  installation program off a bootable floppy.</para>
-      </sect3>
-    </sect2>
-  </sect1>
-</article>
diff --git a/en_US.ISO8859-1/articles/storage-devices/Makefile b/en_US.ISO8859-1/articles/storage-devices/Makefile
deleted file mode 100644
index 0439a4f4a3..0000000000
--- a/en_US.ISO8859-1/articles/storage-devices/Makefile
+++ /dev/null
@@ -1,16 +0,0 @@
-#
-# $FreeBSD$
-#
-# Article: Storage Devices
-
-DOC?= article
-
-FORMATS?= html
-
-INSTALL_COMPRESSED?=gz
-INSTALL_ONLY_COMPRESSED?=
-
-SRCS=	article.sgml
-
-DOC_PREFIX?= ${.CURDIR}/../../..
-.include "${DOC_PREFIX}/share/mk/doc.project.mk"
diff --git a/en_US.ISO8859-1/articles/storage-devices/article.sgml b/en_US.ISO8859-1/articles/storage-devices/article.sgml
deleted file mode 100644
index d620050bc6..0000000000
--- a/en_US.ISO8859-1/articles/storage-devices/article.sgml
+++ /dev/null
@@ -1,2646 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1" standalone="no"?>
-<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V4.2-Based Extension//EN"
-	"../../../share/sgml/freebsd42.dtd" [
-<!ENTITY % entities PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Entity Set//EN" "../../share/sgml/entities.ent">
-%entities;
-]>
-
-<article lang='en'>
-  <articleinfo>
-    <title>Storage Devices</title>
-
-    <authorgroup>
-      <author>
-        <firstname>Wilko</firstname>
-        <surname>Bulte</surname>
-
-        <affiliation>
-          <address><email>wilko@FreeBSD.org</email></address>
-        </affiliation>
-      </author>
-    </authorgroup>
-
-    <legalnotice id="trademarks" role="trademarks">
-      &tm-attrib.freebsd;
-      &tm-attrib.general;
-    </legalnotice>
-
-    <pubdate>$FreeBSD$</pubdate>
-
-    <releaseinfo>$FreeBSD$</releaseinfo>
-
-    <abstract>
-      <para>This article talks about storage devices with FreeBSD.</para>
-    </abstract>
-  </articleinfo>
-
-  <sect1 id="esdi">
-    <title>Using ESDI hard disks</title>
-
-    <para><emphasis>Copyright &copy; 1995, &a.wilko;.  24 September
-      1995.</emphasis></para>
-
-    <para>ESDI is an acronym that means Enhanced Small Device
-      Interface. It is loosely based on the good old ST506/412
-      interface originally devised by Seagate Technology, the makers
-      of the first affordable 5.25" Winchester disk.</para>
-
-    <para>The acronym says Enhanced, and rightly so.  In the first
-      place the speed of the interface is higher, 10 or 15
-      Mbits/second instead of the 5 Mbits/second of ST412 interfaced
-      drives.  Secondly some higher level commands are added, making
-      the ESDI interface somewhat <quote>smarter</quote> to the operating system
-      driver writers.  It is by no means as smart as SCSI by the way.
-      ESDI is standardized by ANSI.</para>
-
-    <para>Capacities of the drives are boosted by putting more sectors
-      on each track.  Typical is 35 sectors per track, high capacity
-      drives I have seen were up to 54 sectors/track.</para>
-
-    <para>Although ESDI has been largely obsoleted by IDE and SCSI
-      interfaces, the availability of free or cheap surplus drives
-      makes them ideal for low (or now) budget systems.</para>
-
-      <sect2>
-	<title>Concepts of ESDI</title>
-
-	<sect3>
-	  <title>Physical connections</title>
-
-	  <para>The ESDI interface uses two cables connected to each drive.
-	    One cable is a 34 pin flat cable edge connector that carries the
-	    command and status signals from the controller to the drive and
-	    vice-versa.  The command cable is daisy chained between all the
-	    drives.  So, it forms a bus onto which all drives are
-	    connected.</para>
-
-	  <para>The second cable is a 20 pin flat cable edge connector that
-	    carries the data to and from the drive.  This cable is radially
-	    connected, so each drive has its own direct connection to the
-	    controller.</para>
-
-	  <para>To the best of my knowledge PC ESDI controllers are limited to
-	    using a maximum of 2 drives per controller.  This is compatibility
-	    feature(?) left over from the WD1003 standard that reserves only a
-	    single bit for device addressing.</para>
-	</sect3>
-
-	<sect3>
-	  <title>Device addressing</title>
-
-	  <para>On each command cable a maximum of 7 devices and 1 controller
-	    can be present.  To enable the controller to uniquely  identify
-	    which drive it addresses, each ESDI device is equipped with
-	    jumpers or switches to select the devices address.</para>
-
-	  <para>On PC type controllers the first drive is set to address 0,
-	    the second disk to address 1.  <emphasis>Always make
-	      sure</emphasis> you set each disk to an unique address! So, on a
-	    PC with its two drives/controller maximum the first drive is drive
-	    0, the second is drive 1.</para>
-	</sect3>
-
-	<sect3>
-	  <title>Termination</title>
-
-	  <para>The daisy chained command cable (the 34 pin cable remember?)
-	    needs to be terminated at the last drive on the chain.  For this
-	    purpose ESDI drives come with a termination resistor network that
-	    can be removed or disabled by a jumper when it is not used.</para>
-
-	  <para>So, one and <emphasis>only</emphasis> one drive, the one at
-	    the farthest end of the command cable has its terminator
-	    installed/enabled.  The controller automatically terminates the
-	    other end of the cable.  Please note that this implies that the
-	    controller must be  at one end of the cable and
-	    <emphasis>not</emphasis> in the middle.</para>
-	</sect3>
-      </sect2>
-
-      <sect2>
-	<title>Using ESDI disks with FreeBSD</title>
-
-	<para>Why is ESDI such a pain to get working in the first
-	  place?</para>
-
-	<para>People who tried ESDI disks with FreeBSD are known to have
-	  developed a profound sense of frustration.  A combination of factors
-	  works against you to produce effects that are hard to understand
-	  when you have never seen them before.</para>
-
-	<para>This has also led to the popular legend ESDI and FreeBSD is a
-	  plain NO-GO.  The following sections try to list all the pitfalls
-	  and  solutions.</para>
-
-	<sect3>
-	  <title>ESDI speed variants</title>
-
-	  <para>As briefly mentioned before, ESDI comes in two speed flavors.
-	    The older drives and controllers use a 10 Mbits/second data
-	    transfer rate.  Newer stuff uses 15 Mbits/second.</para>
-
-	  <para>It is not hard to imagine that 15 Mbits/second drive cause
-	    problems on controllers laid out for 10 Mbits/second.  As always,
-	    consult your controller <emphasis>and</emphasis> drive
-	    documentation to see if things match.</para>
-	</sect3>
-
-	<sect3>
-	  <title>Stay on track</title>
-
-	  <para>Mainstream ESDI drives use 34 to 36 sectors per track. Most
-	    (older) controllers cannot handle more than this  number of
-	    sectors.  Newer, higher capacity, drives use higher numbers of
-	    sectors per track.  For instance, I own a 670 MB drive that has 54
-	    sectors per track.</para>
-
-	  <para>In my case, the controller could not handle this number of
-	    sectors.  It proved to work well except that it only used 35
-	    sectors on each track.  This meant losing a lot of disk
-	    space.</para>
-
-	  <para>Once again, check the documentation of your hardware for more
-	    info.  Going out-of-spec like in the example might or might not
-	    work.  Give it a try or get another more capable
-	    controller.</para>
-	</sect3>
-
-	<sect3>
-	  <title>Hard or soft sectoring</title>
-
-	  <para>Most ESDI drives allow hard or soft sectoring to be selected
-	    using a jumper.  Hard sectoring means that the drive will produce
-	    a sector pulse on the start of each new sector. The controller
-	    uses this pulse to tell when it should start to write or
-	    read.</para>
-
-	  <para>Hard sectoring allows a selection of sector size (normally
-	    256, 512 or 1024 bytes per formatted sector).  FreeBSD uses 512
-	    byte sectors.  The number of sectors per track also varies while
-	    still using the same number of bytes per formatted sector.  The
-	    number of <emphasis>unformatted</emphasis> bytes per sector
-	    varies, dependent on your controller it needs more or less
-	    overhead  bytes to work correctly.  Pushing more sectors on a
-	    track  of course gives you more usable space, but might give
-	    problems if your controller needs more bytes than the  drive
-	    offers.</para>
-
-	  <para>In case of soft sectoring, the controller itself determines
-	    where to start/stop reading or writing.  For ESDI hard sectoring
-	    is the default (at least on everything I came across).  I never
-	    felt the urge to try soft sectoring.</para>
-
-	  <para>In general, experiment with sector settings before you install
-	    FreeBSD because you need to re-run the low-level format after each
-	    change.</para>
-	</sect3>
-
-	<sect3>
-	  <title>Low level formatting</title>
-
-	  <para>ESDI drives need to be low level formatted before they are
-	    usable.  A reformat is needed whenever you figgle with the number
-	    of sectors/track jumpers or the physical orientation of the drive
-	    (horizontal, vertical).  So, first think, then format.  The format
-	    time must not be underestimated, for big disks it can take
-	    hours.</para>
-
-	  <para>After a low level format, a surface scan is done to find and
-	    flag bad sectors.  Most disks have a manufacturer bad block list
-	    listed on a piece of paper or adhesive sticker.  In addition, on
-	    most disks the list is also written onto the disk.  Please use the
-	    manufacturer's list.  It is much easier to remap a defect now than
-	    after FreeBSD is installed.</para>
-
-	  <para>Stay away from low-level formatters that mark all sectors of a
-	    track as bad as soon as they find one bad sector.  Not only does
-	    this waste space, it also and more importantly causes you grief
-	    with bad144 (see the section on bad144).</para>
-	</sect3>
-
-	<sect3>
-	  <title>Translations</title>
-
-	  <para>Translations, although not exclusively a ESDI-only problem,
-	    might give you real trouble.  Translations come in multiple
-	    flavors.  Most of them  have in common that they attempt to work
-	    around the limitations posed upon disk geometries by the original
-	    IBM PC/AT design (thanks IBM!).</para>
-
-	  <para>First of all there is the (in)famous 1024 cylinder limit. For
-	    a system to be able to boot, the stuff (whatever operating system)
-	    must be in the first 1024 cylinders of a disk.  Only 10 bits are
-	    available to encode the cylinder number.  For the number of
-	    sectors the limit is 64 (0-63).  When you combine the 1024
-	    cylinder limit with the 16 head limit (also a design feature) you
-	    max out at fairly limited  disk sizes.</para>
-
-	  <para>To work around this problem, the manufacturers of ESDI PC
-	    controllers added a BIOS prom extension on their boards.  This
-	    BIOS extension handles disk I/O for booting (and for some
-	    operating systems <emphasis>all</emphasis> disk I/O) by using
-	    translation.  For instance, a big drive might be presented to the
-	    system as having 32 heads and 64 sectors/track.  The result is
-	    that the number of cylinders is reduced to something below 1024
-	    and is therefore usable by the system without problems.  It is
-	    noteworthy to know that FreeBSD does not use the BIOS after its
-	    kernel has started.  More on this later.</para>
-
-	  <para>A second reason for translations is the fact that most older
-	    system BIOSes could only handle drives with 17 sectors per track
-	    (the old ST412 standard).  Newer system BIOSes usually have a
-	    user-defined drive type (in most cases this is drive type
-	    47).</para>
-
-	  <warning>
-	    <para>Whatever you do to translations after reading this document,
-	      keep in mind that if you have multiple operating systems on the
-	      same disk, all must use the same translation</para>
-	  </warning>
-
-	  <para>While on the subject of translations, I have seen one
-	    controller type (but there are probably more like this) offer the
-	    option to logically split a drive in multiple partitions as a BIOS
-	    option.  I had select 1 drive == 1 partition because this
-	    controller wrote this info onto the disk.  On power-up it read the
-	    info and presented itself to the system based on the info from the
-	    disk.</para>
-	</sect3>
-
-	<sect3>
-	  <title>Spare sectoring</title>
-
-	  <para>Most ESDI controllers offer the possibility to remap bad
-	    sectors.  During/after the low-level format of the disk bad
-	    sectors are marked as such, and a replacement sector is put in
-	    place (logically of course) of the bad one.</para>
-
-	  <para>In most cases the remapping is done by using N-1 sectors on
-	    each track for actual data storage, and sector N itself is the
-	    spare sector.  N is the total number of sectors physically
-	    available on the track.  The idea behind this is that the
-	    operating system sees a <quote>perfect</quote> disk without bad sectors.  In
-	    the case of FreeBSD this concept is not usable.</para>
-
-	  <para>The problem is that the translation from
-	    <emphasis>bad</emphasis> to <emphasis>good</emphasis> is performed
-	    by the BIOS of the ESDI controller.  FreeBSD, being a true 32 bit
-	    operating system, does not use the BIOS after it has been booted.
-	    Instead, it has device drivers that talk directly to the
-	    hardware.</para>
-
-	  <para><emphasis>So: do not use spare sectoring, bad block remapping
-	      or whatever it may be called by the controller manufacturer when
-	      you want to use the disk for FreeBSD.</emphasis></para>
-	</sect3>
-
-	<sect3>
-	  <title>Bad block handling</title>
-
-	  <para>The preceding section leaves us with a problem.  The
-	    controller's bad block handling is not usable and still FreeBSD's
-	    filesystems assume perfect media without any flaws. To solve this
-	    problem, FreeBSD use the <command>bad144</command> tool.  Bad144
-	    (named after a Digital Equipment standard for bad block handling)
-	    scans a FreeBSD slice for bad blocks.  Having found these bad
-	    blocks, it writes a table with the offending block numbers to the
-	    end of the FreeBSD slice.</para>
-
-	  <para>When the disk is in operation, the disk accesses are checked
-	    against the table read from the disk.  Whenever a block number is
-	    requested that is in the <command>bad144</command> list, a
-	    replacement block (also from the end of the FreeBSD slice) is
-	    used.  In this way, the <command>bad144</command> replacement
-	    scheme presents <quote>perfect</quote> media to the FreeBSD filesystems.</para>
-
-	  <para>There are a number of potential pitfalls associated with the
-	    use of <command>bad144</command>.  First of all, the slice cannot
-	    have more than 126 bad sectors.  If your drive has a high number
-	    of bad sectors, you might need to divide it into multiple FreeBSD
-	    slices each containing less than 126 bad sectors.  Stay away from
-	    low-level format programs that mark <emphasis>every</emphasis>
-	    sector of a track as bad when  they find a flaw on the track.  As
-	    you can imagine, the  126 limit is quickly reached when the
-	    low-level format is done this way.</para>
-
-	  <para>Second, if the slice contains the root filesystem, the slice
-	    should be within the 1024 cylinder BIOS limit.  During the boot
-	    process the bad144 list is read using the BIOS and this only
-	    succeeds when the list is within the 1024 cylinder limit.</para>
-
-	  <note>
-	    <para>The restriction is not that only the root
-	      <emphasis>filesystem</emphasis> must be within the 1024 cylinder
-	      limit, but rather the entire <emphasis>slice</emphasis> that
-	      contains the root filesystem.</para>
-	  </note>
-	</sect3>
-
-	<sect3>
-	  <title>Kernel configuration</title>
-
-	  <para>ESDI disks are handled by the same <literal>wd</literal>driver
-	    as IDE and ST412 MFM disks.  The <literal>wd</literal> driver
-	    should work for all WD1003 compatible interfaces.</para>
-
-	  <para>Most hardware is jumperable for one of two different I/O
-	    address ranges and IRQ lines.  This allows you to have  two wd
-	    type controllers in one system.</para>
-
-	  <para>When your hardware allows non-standard strappings, you can use
-	    these with FreeBSD as long as you enter the  correct info into the
-	    kernel config file.  An example from the kernel config file (they
-	    live in <filename>/sys/i386/conf</filename> BTW).</para>
-
-	  <programlisting># First WD compatible controller
-controller      wdc0    at isa? port "IO_WD1" bio irq 14 vector wdintr
-disk            wd0     at wdc0 drive 0
-disk            wd1     at wdc0 drive 1
-# Second WD compatible controller
-controller      wdc1    at isa? port "IO_WD2" bio irq 15 vector wdintr
-disk            wd2     at wdc1 drive 0
-disk            wd3     at wdc1 drive 1</programlisting>
-	</sect3>
-      </sect2>
-
-      <sect2>
-	<title>Particulars on ESDI hardware</title>
-
-	<sect3>
-	  <title>Adaptec 2320 controllers</title>
-
-	  <para>I successfully installed FreeBSD onto a ESDI disk controlled
-	    by a ACB-2320.  No other operating system was present on the
-	    disk.</para>
-
-	  <para>To do so I low level formatted the disk using
-	    <command>NEFMT.EXE</command> (<command>ftp</command>able from
-	    <hostid role="fqdn">www.adaptec.com</hostid>) and answered NO to
-	    the question whether the disk should be formatted with a spare
-	    sector on each track.  The BIOS on the ACD-2320 was disabled.  I
-	    used the <literal>free configurable</literal> option in the system
-	    BIOS to allow the BIOS to boot it.</para>
-
-	  <para>Before using <command>NEFMT.EXE</command> I tried to format
-	    the disk using the ACB-2320 BIOS built-in formatter.  This proved
-	    to be a show stopper, because it did not give me an option to
-	    disable spare sectoring.  With spare sectoring enabled the FreeBSD
-	    installation process broke down on the <command>bad144</command>
-	    run.</para>
-
-	  <para>Please check carefully which
-	    ACB-232<replaceable>xy</replaceable> variant you have. The
-	    <replaceable>x</replaceable> is either <literal>0</literal> or
-	    <literal>2</literal>, indicating a controller without or with a
-	    floppy controller on board.</para>
-
-	  <para>The <literal>y</literal> is more interesting.  It can either
-	    be a blank, a <literal>A-8</literal> or a <literal>D</literal>.  A
-	    blank indicates a plain 10 Mbits/second controller.  An
-	    <literal>A-8</literal> indicates a 15 Mbits/second controller
-	    capable of handling 52 sectors/track.  A <literal>D</literal>
-	    means a 15 Mbits/second controller that can also handle drives
-	    with &gt; 36 sectors/track (also 52?).</para>
-
-	  <para>All variations should be capable of using 1:1 interleaving.
-	    Use 1:1, FreeBSD is fast enough to handle it.</para>
-	</sect3>
-
-	<sect3>
-	  <title>Western Digital WD1007 controllers</title>
-
-	  <para>I successfully installed FreeBSD onto a ESDI disk controlled
-	    by a WD1007 controller.  To be precise, it was a WD1007-WA2.
-	    Other variations of the WD1007 do exist.</para>
-
-	  <para>To get it to work, I had to disable the sector translation and
-	    the WD1007's onboard BIOS.  This implied I could not use the
-	    low-level formatter built into this BIOS.  Instead, I grabbed
-	    <command>WDFMT.EXE</command> from <hostid
-	      role="fqdn">www.wdc.com</hostid> Running this formatted my drive
-	    just fine.</para>
-	</sect3>
-
-	<sect3>
-	  <title>Ultrastor U14F controllers</title>
-
-	  <para>According to multiple reports from the net, Ultrastor ESDI
-	    boards work OK with FreeBSD.  I lack any further info on
-	    particular settings.</para>
-	</sect3>
-      </sect2>
-
-      <sect2 id="esdi-further-reading">
-	<title>Further reading</title>
-
-	<para>If you intend to do some serious ESDI hacking, you might want to
-	  have the official standard at hand:</para>
-
-	<para>The latest ANSI X3T10 committee document is: Enhanced Small
-	  Device Interface (ESDI) [X3.170-1990/X3.170a-1991]    [X3T10/792D
-	  Rev 11]</para>
-
-	<para>On Usenet the newsgroup <ulink
-	    url="news:comp.periphs">comp.periphs</ulink> is a noteworthy place
-	  to look  for more info.</para>
-
-	<para>The World Wide Web (WWW) also proves to be a very handy info
-	  source: For info on Adaptec ESDI controllers see <ulink
-	    url="http://www.adaptec.com/"></ulink>. For
-	  info on Western Digital controllers see
-	  <ulink url="http://www.wdc.com/"></ulink>.</para>
-      </sect2>
-
-      <sect2>
-	<title>Thanks to...</title>
-
-	<para>Andrew Gordon for sending me an Adaptec 2320 controller and ESDI
-	  disk for testing.</para>
-      </sect2>
-    </sect1>
-
-    <sect1 id="scsi">
-      <title>What is SCSI?</title>
-
-      <para><emphasis>Copyright &copy; 1995, &a.wilko;.  July 6,
-	  1996.</emphasis></para>
-
-      <para>SCSI is an acronym for Small Computer Systems Interface.  It is an
-	ANSI standard that has become one of the leading I/O buses in the
-	computer industry.  The foundation of the SCSI standard was laid by
-	Shugart Associates (the same guys that gave the world the first mini
-	floppy disks) when they introduced the SASI bus (Shugart Associates
-	Standard Interface).</para>
-
-      <para>After some time an industry effort was started to come to a more
-	strict standard allowing devices from different vendors to work
-	together.  This effort was recognized in the ANSI SCSI-1 standard.
-	The SCSI-1 standard (approximately 1985) is rapidly becoming obsolete.  The
-	current standard is SCSI-2 (see <link
-	  linkend="scsi-further-reading">Further reading</link>), with SCSI-3
-	on the drawing boards.</para>
-
-      <para>In addition to a physical interconnection standard, SCSI defines a
-	logical (command set) standard to which disk devices must adhere.
-	This standard is called the Common Command Set (CCS) and was developed
-	more or less in parallel with ANSI SCSI-1. SCSI-2 includes the
-	(revised) CCS as part of the standard itself. The commands are
-	dependent on the type of device at hand.  It does not make much sense
-	of course to define a Write command for a scanner.</para>
-
-      <para>The SCSI bus is a parallel bus, which comes in a number of
-	variants.  The oldest and most used is an 8 bit wide bus, with
-	single-ended signals, carried on 50 wires.  (If you do not know what
-	single-ended means, do not worry, that is what this document is all
-	about.)  Modern designs also use 16 bit wide buses, with differential
-	signals.  This allows transfer speeds of 20Mbytes/second, on cables
-	lengths of up to 25 meters.  SCSI-2 allows a maximum bus width of 32
-	bits, using an additional cable. Quickly emerging are Ultra SCSI (also
-	called Fast-20) and Ultra2 (also called Fast-40).  Fast-20 is 20
-	million transfers per second (20 Mbytes/sec on a 8 bit bus), Fast-40
-	is 40 million transfers per second (40 Mbytes/sec on a 8 bit bus).
-	Most hard drives sold today are single-ended Ultra SCSI (8 or 16
-	bits).</para>
-
-      <para>Of course the SCSI bus not only has data lines, but also a number
-	of control signals.  A very elaborate protocol is part of the standard
-	to allow multiple devices to share the bus in an efficient manner.  In
-	SCSI-2, the data is always checked using a separate parity line.  In
-	pre-SCSI-2 designs parity was optional.</para>
-
-      <para>In SCSI-3 even faster bus types are introduced, along with a
-	serial SCSI busses that reduces the cabling overhead and allows a
-	higher maximum bus length.  You might see names like SSA and
-	fibre channel in this context.  None of the serial buses are currently
-	in widespread use (especially not in the typical FreeBSD environment).
-	For this reason the serial bus types are not discussed any
-	further.</para>
-
-      <para>As you could have guessed from the description above, SCSI devices
-	are intelligent.  They have to be to adhere to the SCSI standard
-	(which is over 2 inches thick BTW).  So, for a hard disk drive for
-	instance you do not specify a head/cylinder/sector to address a
-	particular block, but simply the number of the block you want.
-	Elaborate caching schemes, automatic bad block replacement etc are all
-	made possible by this <quote>intelligent device</quote> approach.</para>
-
-      <para>On a SCSI bus, each possible pair of devices can communicate.
-	Whether their function allows this is another matter, but the standard
-	does not restrict it.  To avoid signal contention, the 2 devices have
-	to arbitrate for the bus before using it.</para>
-
-      <para>The philosophy of SCSI is to have a standard that allows
-	older-standard devices to work with newer-standard ones.  So, an old
-	SCSI-1 device should normally work on a SCSI-2 bus.  I say Normally,
-	because it is not absolutely sure that the implementation of an old
-	device follows the (old) standard closely enough to be acceptable on a
-	new bus.  Modern devices are usually more well-behaved, because the
-	standardization has become more strict and is better adhered to by the
-	device manufacturers.</para>
-
-      <para>Generally speaking, the chances of getting a working set of
-	devices on a single bus is better when all the devices are SCSI-2 or
-	newer.  This implies that you do not have to dump all your old stuff
-	when you get that shiny 80GB disk: I own a system on which a pre-SCSI-1
-	disk, a SCSI-2 QIC tape unit, a SCSI-1 helical scan tape unit and 2
-	SCSI-1 disks work together quite happily.  From a performance
-	standpoint you might want to separate your older and newer (=faster)
-	devices however. This is especially advantageous if you have an
-	Ultra160 host adapter where you should separate your U160 devices
-	from the Fast and Wide SCSI-2 devices.</para>
-
-      <sect2>
-	<title>Components of SCSI</title>
-
-	<para>As said before, SCSI devices are smart.  The idea is to put the
-	  knowledge about intimate hardware details onto the SCSI device
-	  itself.  In this way, the host system does not have to worry about
-	  things like how many heads a hard disks has, or how many tracks
-	  there are on a specific tape device.  If you are curious, the
-	  standard specifies commands with which you can query your devices on
-	  their hardware particulars.  FreeBSD uses this capability during
-	  boot to check out what devices are connected and whether they need
-	  any special treatment.</para>
-
-	<para>The advantage of intelligent devices is obvious: the device
-	  drivers on the host can be made in a much more generic fashion,
-	  there is no longer a need to change (and qualify!) drivers for every
-	  odd new device that is introduced.</para>
-
-	<para>For cabling and connectors there is a golden rule: get good
-	  stuff.  With bus speeds going up all the time you will save yourself
-	  a lot of grief by using good material.</para>
-
-	<para>So, gold plated connectors, shielded cabling, sturdy connector
-	  hoods with strain reliefs etc are the way to go. Second golden rule:
-	  do no use cables longer than necessary.  I once spent 3 days hunting
-	  down a problem with a flaky machine only to discover that shortening
-	  the SCSI bus by 1 meter solved the problem.  And the original bus
-	  length was well within the SCSI specification.</para>
-      </sect2>
-
-      <sect2>
-	<title>SCSI bus types</title>
-
-	<para>From an electrical point of view, there are two incompatible bus
-	  types: single-ended and differential.  This means that there are two
-	  different main groups of SCSI devices and controllers, which cannot
-	  be mixed on the same bus.  It is possible however to use special
-	  converter hardware to transform a single-ended bus into a
-	  differential one (and vice versa).  The differences between the bus
-	  types are explained in the next sections.</para>
-
-	<para>In lots of SCSI related documentation there is a sort of jargon
-	  in use to abbreviate the different bus types.  A small list:</para>
-
-	<itemizedlist>
-	  <listitem>
-	    <para>FWD:	Fast Wide Differential</para>
-	  </listitem>
-
-	  <listitem>
-	    <para>FND:	Fast Narrow Differential</para>
-	  </listitem>
-
-	  <listitem>
-	    <para>SE:	Single Ended</para>
-	  </listitem>
-
-	  <listitem>
-	    <para>FN:	Fast Narrow</para>
-	  </listitem>
-
-	  <listitem>
-	    <para>etc.</para>
-	  </listitem>
-	</itemizedlist>
-
-
-	<para>With a minor amount of imagination one can usually imagine what
-	  is meant.</para>
-
-	<para>Wide is a bit ambiguous, it can indicate 16 or 32 bit buses. As
-	  far as I know, the 32 bit variant is not (yet) in use, so wide
-	  normally means 16 bit.</para>
-
-	<para>Fast means that the timing on the bus is somewhat different, so
-	  that on a narrow (8 bit) bus 10 Mbytes/sec are possible instead of 5
-	  Mbytes/sec for <quote>slow</quote> SCSI.  As discussed before, bus speeds of 20
-	  and 40 million transfers/second are also emerging  (Fast-20 == Ultra
-	  SCSI and Fast-40 == Ultra2 SCSI).</para>
-
-	<note>
-	  <para>The data lines &gt; 8 are only used for data transfers and
-	    device addressing.  The transfers of commands and status messages
-	    etc are only performed on the lowest 8 data lines. The standard
-	    allows narrow devices to operate on a wide bus. The usable bus
-	    width is negotiated between the devices.  You have to watch your
-	    device addressing closely when mixing wide and narrow.</para>
-	</note>
-
-	<sect3>
-	  <title>Single ended buses</title>
-
-	  <para>A single-ended SCSI bus uses signals that are either 5 Volts
-	    or 0 Volts (indeed, TTL levels) and are relative to a COMMON
-	    ground reference.  A singled ended 8 bit SCSI bus has
-	    approximately 25 ground lines, who are all tied to a single <quote>rail</quote>
-	    on all devices.  A standard single ended bus has a maximum length
-	    of 6 meters.  If the same bus is used with fast-SCSI devices, the
-	    maximum length allowed drops to 3 meters.  Fast-SCSI means that
-	    instead of 5Mbytes/sec the bus allows 10Mbytes/sec
-	    transfers.</para>
-
-	  <para>Fast-20 (Ultra SCSI) and Fast-40 allow for 20 and 40 million
-	    transfers/second respectively.  So, F20 is 20 Mbytes/second on a 8
-	    bit bus, 40 Mbytes/second on a 16 bit bus etc.  For F20 the max
-	    bus length is 1.5 meters, for F40 it becomes 0.75 meters.  Be
-	    aware that F20 is pushing  the limits quite a bit, so you will
-	    quickly find out if your SCSI bus is electrically sound.</para>
-
-	  <note>
-	    <para>If some devices on your bus use <quote>fast</quote> to communicate your
-	      bus must adhere to the length restrictions for fast
-	      buses!</para>
-	  </note>
-
-	  <para>It is obvious that with the newer fast-SCSI devices the bus
-	    length can become a real bottleneck.  This is why the differential
-	    SCSI bus was introduced in the SCSI-2 standard.</para>
-
-	  <para>For connector pinning and connector types please refer to the
-	    SCSI-2 standard (see <link linkend="scsi-further-reading">Further
-	      reading</link>) itself, connectors etc are listed there in
-	    painstaking detail.</para>
-
-	  <para>Beware of devices using non-standard cabling.  For instance
-	    Apple uses a 25pin D-type connecter (like the one on serial ports
-	    and parallel printers).  Considering that the official SCSI bus
-	    needs 50 pins you can imagine the use of this connector needs some
-	    <quote>creative cabling</quote>.  The reduction of the number of ground wires
-	    they used is a bad idea, you better stick to 50 pins cabling  in
-	    accordance with the SCSI standard.  For Fast-20 and 40 do not even
-	    think about buses like this.</para>
-	</sect3>
-
-	<sect3>
-	  <title>Differential buses</title>
-
-	  <para>A differential SCSI bus has a maximum length of 25 meters.
-	    Quite a difference from the 3 meters for a single-ended fast-SCSI
-	    bus.  The idea behind differential signals is that each bus signal
-	    has its own return wire.  So, each signal is carried on a
-	    (preferably twisted) pair of wires.  The voltage difference
-	    between these two wires determines whether the signal is asserted
-	    or de-asserted.  To a certain extent the voltage difference
-	    between ground and the signal wire pair is not relevant (do not
-	    try 10 kVolts though).</para>
-
-	  <para>It is beyond the scope of this document to explain why this
-	    differential idea is so much better.  Just accept that
-	    electrically seen the use of differential signals gives a much
-	    better noise margin.  You will normally find differential buses in
-	    use for inter-cabinet connections.  Because of the lower cost
-	    single ended is mostly used for shorter buses like inside
-	    cabinets.</para>
-
-	  <para>There is nothing that stops you from using differential stuff
-	    with FreeBSD, as long as you use a controller that has device
-	    driver support in FreeBSD.  As an example, Adaptec marketed the
-	    AHA1740 as a single ended board, whereas the AHA1744 was
-	    differential.  The software interface to the host is identical for
-	    both.</para>
-	</sect3>
-
-	<sect3>
-	  <title>Terminators</title>
-
-	  <para>Terminators in SCSI terminology are resistor networks that are
-	    used to get a correct impedance matching.  Impedance matching is
-	    important to get clean signals on the bus, without reflections or
-	    ringing.  If you once made a long distance telephone call on a bad
-	    line you probably know what reflections are.  With 20Mbytes/sec
-	    traveling over your SCSI bus, you do not want signals echoing
-	    back.</para>
-
-	  <para>Terminators come in various incarnations, with more or less
-	    sophisticated designs.  Of course, there are internal and external
-	    variants.  Many SCSI devices come with a number of sockets in
-	    which a number of resistor networks can (must be!) installed.  If
-	    you remove terminators from a device, carefully store them.  You
-	    will need them when you ever decide to reconfigure your SCSI bus.
-	    There is enough variation in even these simple tiny things to make
-	    finding the exact replacement a frustrating business.  There are
-	    also SCSI devices that have a single jumper to enable or disable a
-	    built-in terminator. There are special terminators you can stick
-	    onto a flat cable bus.  Others look like external connectors, or a
-	    connector hood without a cable.  So, lots of choice as you can
-	    see.</para>
-
-	  <para>There is much debate going on if and when you should switch
-	    from simple resistor (passive) terminators to active terminators.
-	    Active terminators contain slightly more elaborate circuit to give
-	    cleaner bus signals.  The general consensus seems to be that the
-	    usefulness of active termination increases when you have long
-	    buses and/or fast devices.  If you ever have problems with your
-	    SCSI buses you might consider trying an active terminator.  Try to
-	    borrow one first, they reputedly are quite expensive.</para>
-
-	  <para>Please keep in mind that terminators for differential and
-	    single-ended buses are not identical.  You should <emphasis>not
-	      mix</emphasis> the two variants.</para>
-
-	  <para>OK, and now where should you install your terminators? This is
-	    by far the most misunderstood part of SCSI.  And it is by far the
-	    simplest.  The rule is: <emphasis>every single line on the SCSI
-	      bus has 2 (two) terminators, one at each end of the
-	      bus.</emphasis> So, two and not one or three or whatever.  Do
-	    yourself a favor and stick to this rule.  It will save you endless
-	    grief, because wrong termination has the potential to introduce
-	    highly mysterious bugs.  (Note the <quote>potential</quote> here;
-	    the nastiest part is that it may or may not work.)</para>
-
-	  <para>A common pitfall is to have an internal (flat) cable in a
-	    machine and also an external cable attached to the controller. It
-	    seems almost everybody forgets to remove the terminators from the
-	    controller.  The terminator must now be on the last external
-	    device, and not on the controller! In general, every
-	    reconfiguration of a SCSI bus must pay attention to this.</para>
-
-	  <note>
-	    <para>Termination is to be done on a per-line basis.  This means
-	      if you have both narrow and wide buses connected to the same
-	      host adapter, you need to enable termination on the higher 8
-	      bits of the bus on the adapter (as well as the last devices on
-	      each bus, of course).</para>
-	      </note>
-
-	  <para>What I did myself is remove all terminators from my SCSI
-	    devices and controllers.  I own a couple of external terminators,
-	    for both the Centronics-type external cabling and for the internal
-	    flat cable connectors.  This makes reconfiguration much
-	    easier.</para>
-
-	  <para>On modern devices, sometimes integrated terminators are used.
-	    These things are special purpose integrated circuits that can be
-	    enabled or disabled with a control pin.  It is not necessary to
-	    physically remove them from a device.  You may find them on newer
-	    host adapters, sometimes they are software configurable, using
-	    some sort of setup tool.  Some will even auto-detect the cables
-	    attached to the connectors and automatically set up the
-	    termination as necessary.  At any rate, consult your
-	    documentation!</para>
-	</sect3>
-
-	<sect3>
-	  <title>Terminator power</title>
-
-	  <para>The terminators discussed in the previous chapter need power
-	    to operate properly.  On the SCSI bus, a line is dedicated to this
-	    purpose.  So, simple huh?</para>
-
-	  <para>Not so.  Each device can provide its own terminator power to
-	    the terminator sockets it has on-device.  But if you have external
-	    terminators, or when the device supplying the terminator power to
-	    the SCSI bus line is switched off you are in trouble.</para>
-
-	  <para>The idea is that initiators (these are devices that initiate
-	    actions on the bus, a discussion follows) must supply terminator
-	    power.  All SCSI devices are allowed (but not required) to supply
-	    terminator power.</para>
-
-	  <para>To allow for un-powered devices on a bus, the terminator power
-	    must be supplied to the bus via a diode.  This prevents the
-	    backflow of current to un-powered devices.</para>
-
-	  <para>To prevent all kinds of nastiness, the terminator power is
-	    usually fused.  As you can imagine, fuses might blow.  This can,
-	    but does not have to, lead to a non functional bus.  If multiple
-	    devices supply terminator power, a single blown fuse will not put
-	    you out of business.  A single supplier with a blown fuse
-	    certainly will.  Clever external terminators sometimes have a  LED
-	    indication that shows whether terminator power is present.</para>
-
-	  <para>In newer designs auto-restoring fuses that <quote>reset</quote> themselves
-	    after some time are sometimes used.</para>
-	</sect3>
-
-	<sect3>
-	  <title>Device addressing</title>
-
-	  <para>Because the SCSI bus is, ehh, a bus there must be a way to
-	    distinguish or address the different devices connected to
-	    it.</para>
-
-	  <para>This is done by means of the SCSI or target ID.  Each device
-	    has a unique target ID.  You can select the ID to which a device
-	    must respond using a set of jumpers, or a dip switch, or something
-	    similar.  Some SCSI host adapters let you change the target ID
-	    from the boot menu.  (Yet some others will not let you change the
-	    ID from 7.)  Consult the documentation of your device for more
-	    information.</para>
-
-	  <para>Beware of multiple devices configured to use the same ID.
-	    Chaos normally reigns in this case.  A pitfall is that one of the
-	    devices sharing the same ID sometimes even manages to answer to
-	    I/O requests!</para>
-
-	  <para>For an 8 bit bus, a maximum of 8 targets is possible.  The
-	    maximum is 8 because the selection is done bitwise using the 8
-	    data lines on the bus.  For wide buses this increases to the
-	    number of data lines (usually 16).</para>
-
-	  <note>
-	    <para>A narrow SCSI device can not communicate with a SCSI device
-	      with a target ID larger than 7.  This means it is generally not
-	      a good idea to move your SCSI host adapter's target ID to
-	      something higher than 7 (or your CDROM will stop
-	      working).</para>
-	  </note>
-
-	  <para>The higher the SCSI target ID, the higher the priority the
-	    devices has.  When it comes to arbitration between devices that
-	    want to use the bus at the same time, the device that has the
-	    highest SCSI ID will win.  This also means that the SCSI host
-	    adapter usually uses target ID 7.  Note however that the lower 8
-	    IDs have higher priorities than the higher 8 IDs on a wide-SCSI
-	    bus.  Thus, the order of target IDs is: [7 6 .. 1 0 15 14 .. 9 8]
-	    on a wide-SCSI system.  (If you are wondering why the lower 8
-	    have higher priority, read the previous paragraph for a
-	    hint.)</para>
-
-	  <para>For a further subdivision, the standard allows for Logical
-	    Units or LUNs for short.  A single target ID may have multiple
-	    LUNs.  For example, a tape device including a tape changer may
-	    have LUN 0 for the tape device itself, and LUN 1 for the tape
-	    changer.  In this way, the host system can address each of the
-	    functional units of the tape changer as desired.</para>
-	</sect3>
-
-	<sect3>
-	  <title>Bus layout</title>
-
-	  <para>SCSI buses are linear.  So, not shaped like Y-junctions, star
-	    topologies, rings, cobwebs or whatever else people might want to
-	    invent.  One of the most common mistakes is for people with
-	    wide-SCSI host adapters to connect devices on all three connecters
-	    (external connector, internal wide connector, internal narrow
-	    connector).  Do not do that.  It may appear to work if you are
-	    really lucky, but I can almost guarantee that your system will
-	    stop functioning at the most unfortunate moment (this is also
-	    known as <quote>Murphy's law</quote>).</para>
-
-	  <para>You might notice that the terminator issue discussed earlier
-	    becomes rather hairy if your bus is not linear.  Also, if you have
-	    more connectors than devices on your internal SCSI cable, make
-	    sure you attach devices on connectors on both ends instead of
-	    using the connectors in the middle and let one or both ends
-	    dangle.  This will screw up the termination of the bus.</para>
-
-	  <para>The electrical characteristics, its noise margins and
-	    ultimately the reliability of it all are tightly related to linear
-	    bus rule.</para>
-
-	  <para><emphasis>Stick to the linear bus rule!</emphasis></para>
-	</sect3>
-      </sect2>
-
-      <sect2>
-	<title>Using SCSI with FreeBSD</title>
-
-	<sect3>
-	  <title>About translations, BIOSes and magic...</title>
-
-	  <para>As stated before, you should first make sure that you have a
-	    electrically sound bus.</para>
-
-	  <para>When you want to use a SCSI disk on your PC as boot disk, you
-	    must aware of some quirks related to PC BIOSes.  The PC BIOS in
-	    its first incarnation used a low level physical interface to the
-	    hard disk.  So, you had to tell the BIOS (using a setup tool or a
-	    BIOS built-in setup) how your disk physically looked like.  This
-	    involved stating number of heads, number of cylinders, number of
-	    sectors per track, obscure things like precompensation and reduced
-	    write current cylinder etc.</para>
-
-	  <para>One might be inclined to think that since SCSI disks are smart
-	    you can forget about this.  Alas, the arcane setup issue is still
-	    present today.  The system BIOS needs to know how to access your
-	    SCSI disk with the head/cyl/sector method in order to load the
-	    FreeBSD kernel during boot.</para>
-
-	  <para>The SCSI host adapter or SCSI controller you have put in your
-	    AT/EISA/PCI/whatever bus to connect your disk therefore has its
-	    own on-board BIOS.  During system startup, the SCSI BIOS takes
-	    over the hard disk interface routines from the system BIOS.  To
-	    fool the system BIOS, the system setup is normally set to No hard
-	    disk present.  Obvious, is it not?</para>
-
-	  <para>The SCSI BIOS itself presents to the system a so called
-	    <emphasis>translated</emphasis> drive.  This means that a fake
-	    drive table is constructed that allows the PC to boot the drive.
-	    This translation is often (but not always) done using a pseudo
-	    drive with 64 heads and 32 sectors per track.  By varying the
-	    number of cylinders, the SCSI BIOS adapts to the actual drive
-	    size.  It is useful to note that 32 * 64 / 2 = the size of your
-	    drive in megabytes.  The division by 2 is to get from disk blocks
-	    that are normally 512 bytes in size to Kbytes.</para>
-
-	  <para>Right.  All is well now?! No, it is not.  The system BIOS has
-	    another quirk you might run into.  The number of cylinders of a
-	    bootable hard disk cannot be greater than 1024.  Using the
-	    translation above, this is a show-stopper for disks greater than 1
-	    GB.  With disk capacities going up all the time this is causing
-	    problems.</para>
-
-	  <para>Fortunately, the solution is simple: just use another
-	    translation, e.g. with 128 heads instead of 32.  In most cases new
-	    SCSI BIOS versions are available to upgrade older SCSI host
-	    adapters.  Some newer adapters have an option, in the form of a
-	    jumper or software setup selection, to switch the translation the
-	    SCSI BIOS uses.</para>
-
-	  <para>It is very important that <emphasis>all</emphasis> operating
-	    systems on the disk use the <emphasis>same translation</emphasis>
-	    to get the right idea about where to find the relevant partitions.
-	    So, when installing FreeBSD you must answer any questions about
-	    heads/cylinders etc using the translated values your host adapter
-	    uses.</para>
-
-	  <para>Failing to observe the translation issue might lead to
-	    un-bootable systems or operating systems overwriting each others
-	    partitions.  Using fdisk you should be able to see all
-	    partitions.</para>
-
-	  <para>You might have heard some talk of <quote>lying</quote> devices?
-	    Older FreeBSD kernels used to report the geometry of SCSI disks
-	    when booting.  An example from one of my systems:</para>
-
-	  <screen>aha0 targ 0 lun 0: &lt;MICROP 1588-15MB1057404HSP4&gt;
-da0: 636MB (1303250 total sec), 1632 cyl, 15 head, 53 sec, bytes/sec 512</screen>
-
-	  <para>Newer kernels usually do not report this information.
-	    e.g.</para>
-
-	  <screen>(bt0:0:0): "SEAGATE ST41651 7574" type 0 fixed SCSI 2
-da0(bt0:0:0): Direct-Access 1350MB (2766300 512 byte sectors)</screen>
-
-	  <para>Why has this changed?</para>
-
-	  <para>This info is retrieved from the SCSI disk itself.  Newer disks
-	    often use a technique called zone bit recording.  The idea is that
-	    on the outer cylinders of the drive there is more space so more
-	    sectors per track can be put on them.  This results in disks that
-	    have more tracks on outer cylinders than on the inner cylinders
-	    and, last but not least, have more capacity.  You can imagine that
-	    the value reported by the drive when inquiring about the geometry
-	    now becomes suspect at best, and nearly always misleading.  When
-	    asked for a geometry, it is nearly always better to supply the
-	    geometry used by the BIOS, or <emphasis>if the BIOS is never going
-	      to know about this disk</emphasis>, (e.g. it is not a booting
-	    disk) to supply a fictitious geometry that is convenient.</para>
-	</sect3>
-
-	<sect3>
-	  <title>SCSI subsystem design</title>
-
-	  <para>FreeBSD uses a layered SCSI subsystem.  For each different
-	    controller card a device driver is written.  This driver knows all
-	    the intimate details about the hardware it controls.  The driver
-	    has a interface to the upper layers of the SCSI subsystem through
-	    which it receives its commands and reports back any status.</para>
-
-	  <para>On top of the card drivers there are a number of more generic
-	    drivers for a class of devices.  More specific: a driver for tape
-	    devices (abbreviation: sa, for serial access),
-	    magnetic disks (da, for direct access), CDROMs (cd) etc.
-	    In case you are wondering where you can find this stuff, it all
-	    lives in <filename>/sys/cam/scsi</filename>.  See the man pages in
-	    section 4 for more details.</para>
-
-	  <para>The multi level design allows a decoupling of low-level bit
-	    banging and more high level stuff.  Adding support for another
-	    piece of hardware is a much more manageable problem.</para>
-	</sect3>
-
-	<sect3>
-	  <title>Kernel configuration</title>
-
-	  <para>Dependent on your hardware, the kernel configuration file must
-	    contain one or more lines describing your host adapter(s).  This
-	    includes I/O addresses, interrupts etc. Consult the manual page for
-	    your adapter driver to get more info. Apart from that, check out
-	    <filename>/sys/i386/conf/LINT</filename> for an overview of a
-	    kernel config file.  <filename>LINT</filename> contains every
-	    possible option you can dream of.  It does
-	    <emphasis>not</emphasis> imply <filename>LINT</filename> will
-	    actually get you to a working kernel at all.</para>
-
-	  <para>Although it is probably stating the obvious: the kernel config
-	    file should reflect your actual hardware setup.  So, interrupts,
-	    I/O addresses etc must match the kernel config file.  During
-	    system boot messages will be displayed to indicate whether the
-	    configured hardware was actually found.</para>
-
-	  <note>
-	    <para>Note that most of the EISA/PCI drivers (namely
-	      <devicename>ahb</devicename>, <devicename>ahc</devicename>,
-	      <devicename>ncr</devicename> and <devicename>amd</devicename>
-	      will automatically obtain the correct parameters from the host
-	      adapters themselves at boot time; thus, you just need to write,
-	      for instance, <literal>controller ahc0</literal>.</para>
-	  </note>
-
-	  <para>An example loosely based on the FreeBSD 2.2.5-Release kernel
-	    config  file <filename>LINT</filename> with some added comments
-	    (between []):</para>
-
-	  <programlisting># SCSI host adapters: `aha', `ahb', `aic', `bt', `nca'
-#
-# aha: Adaptec 154x
-# ahb: Adaptec 174x
-# ahc: Adaptec 274x/284x/294x
-# aic: Adaptec 152x and sound cards using the Adaptec AIC-6360 (slow!)
-# amd: AMD 53c974 based SCSI cards (e.g., Tekram DC-390 and 390T)
-# bt: Most Buslogic controllers
-# nca: ProAudioSpectrum cards using the NCR 5380 or Trantor T130
-# ncr: NCR/Symbios 53c810/815/825/875 etc based SCSI cards
-# uha: UltraStore 14F and 34F
-# sea: Seagate ST01/02 8 bit controller (slow!)
-# wds: Western Digital WD7000 controller (no scatter/gather!).
-#
-
-[For an Adaptec AHA274x/284x/294x/394x etc controller]
-controller	ahc0
-
-[For an NCR/Symbios 53c875 based controller]
-controller	ncr0
-
-[For an Ultrastor adapter]
-controller	uha0	at isa? port "IO_UHA0" bio irq ? drq 5 vector uhaintr
-
-# Map SCSI buses to specific SCSI adapters
-controller	scbus0	at ahc0
-controller	scbus2	at ncr0
-controller	scbus1  at uha0
-
-# The actual SCSI devices
-disk da0 at scbus0 target 0 unit 0	[SCSI disk 0 is at scbus 0, LUN 0]
-disk da1 at scbus0 target 1             [implicit LUN 0 if omitted]
-disk da2 at scbus1 target 3             [SCSI disk on the uha0]
-disk da3 at scbus2 target 4             [SCSI disk on the ncr0]
-tape sa1 at scbus0 target 6             [SCSI tape at target 6]
-device cd0 at scbus?                    [the first ever CDROM found, no wiring]</programlisting>
-
-	  <para>The example above tells the kernel to look for a ahc (Adaptec
-	    274x) controller, then for an NCR/Symbios board, and so on.  The
-	    lines following the controller specifications  tell the kernel to
-	    configure specific devices but <emphasis>only</emphasis> attach
-	    them when they match the target ID and LUN specified on the
-	    corresponding bus.</para>
-
-	  <para>Wired down devices get <quote>first shot</quote> at the unit
-	    numbers so the first non <quote>wired down</quote> device, is
-	    allocated the unit number  one greater than the highest
-	    <quote>wired down</quote> unit number for that kind of device.  So,
-	    if you had a SCSI tape at target ID 2 it would be configured as
-	    sa2, as the tape at target ID 6 is wired down to unit number
-	    1.</para>
-
-	  <note>
-	    <para>Wired down devices need not be found to get their unit
-	      number.  The unit number for a wired down device is reserved for
-	      that device, even if it is turned off at boot time.  This allows
-	      the device to be turned on and brought on-line at a later time,
-	      without rebooting.  Notice that a device's unit number has
-	      <emphasis>no</emphasis> relationship with its target ID on  the
-	      SCSI bus.</para>
-	  </note>
-
-	  <para>Below is another example of a kernel config file as used by
-	    FreeBSD version &lt; 2.0.5.  The difference with the first example
-	    is that devices are not <quote>wired down</quote>.  <quote>Wired
-	    down</quote> means that you specify which SCSI target belongs to
-	    which device.</para>
-
-	  <para>A kernel built to the config file below will attach  the first
-	    SCSI disk it finds to da0, the second disk to da1 etc. If you ever
-	    removed or added a disk, all other devices of the same type (disk
-	    in this case) would <quote>move around</quote>.  This implies you have to
-	    change <filename>/etc/fstab</filename> each time.</para>
-
-	  <para>Although the old style still works, you  are
-	    <emphasis>strongly</emphasis> recommended to use this new feature.
-	    It will save you a lot of grief whenever you shift your hardware
-	    around on the SCSI buses.  So, when you re-use your old trusty
-	    config file after upgrading from a pre-FreeBSD2.0.5.R system check
-	    this out.</para>
-
-	  <programlisting>[driver for Adaptec 174x]
-controller      ahb0 at isa? bio irq 11 vector ahbintr
-
-[for Adaptec 154x]
-controller      aha0    at isa? port "IO_AHA0" bio irq 11 drq 5 vector ahaintr
-
-[for Seagate ST01/02]
-controller      sea0    at isa? bio irq 5 iomem 0xc8000 iosiz 0x2000 vector seaintr
-
-controller      scbus0
-
-device          da0     [support for 4 SCSI harddisks, da0 up da3]
-device          sa0	[support for 2 SCSI tapes]
-
-[for the CDROM]
-device          cd0     #Only need one of these, the code dynamically grows</programlisting>
-
-	  <para>Both examples support SCSI disks.  If during boot more devices
-	    of a specific type (e.g. da disks) are found than are configured
-	    in the booting kernel, the system will simply allocate more
-	    devices, incrementing the unit number starting at the last number
-	    <quote>wired down</quote>.  If there are no <quote>wired
-	    down</quote> devices then counting starts at unit 0.</para>
-
-	  <para>Use <command>man 4 scsi</command> to check for the latest info
-	    on the SCSI subsystem.  For more detailed info on host adapter
-	    drivers use e.g., <command>man 4 ahc</command> for info on the
-	    Adaptec 294x driver.</para>
-	</sect3>
-
-	<sect3>
-	  <title>Tuning your SCSI kernel setup</title>
-
-	  <para>Experience has shown that some devices are slow to respond to
-	    INQUIRY commands after a SCSI bus reset (which happens at boot
-	    time).  An INQUIRY command is sent by the kernel on boot to see
-	    what kind of device (disk, tape, CDROM etc.) is connected to a
-	    specific target ID.  This process is called device probing by the
-	    way.</para>
-
-	  <para>To work around the <quote>slow response</quote> problem, FreeBSD allows a
-	    tunable delay time before the SCSI devices are probed following a
-	    SCSI bus reset.  You can set this delay time in your kernel
-	    configuration file using a line like:</para>
-
-	  <programlisting>options         SCSI_DELAY=15         #Be pessimistic about Joe SCSI device</programlisting>
-
-	  <para>This line sets the delay time to 15 seconds.  On my own system
-	    I had to use 3 seconds minimum to get my trusty old CDROM drive
-	    to be recognized.  Start with a high value (say 30 seconds or so)
-	    when you have problems  with device recognition.  If this helps,
-	    tune it back until it just stays working.</para>
-	</sect3>
-
-	<sect3 id="scsi-rogue-devices">
-	  <title>Rogue SCSI devices</title>
-
-	  <para>Although the SCSI standard tries to be complete and concise,
-	    it is a complex standard and implementing things correctly is no
-	    easy task.  Some vendors do a better job then others.</para>
-
-	  <para>This is exactly where the <quote>rogue</quote> devices come
-	    into view. Rogues are devices that are recognized by the FreeBSD
-	    kernel as behaving slightly (...) non-standard.  Rogue devices are
-	    reported by the kernel when booting.  An example for two of my
-	    cartridge tape units:</para>
-
-	  <screen>Feb 25 21:03:34 yedi /kernel: ahb0 targ 5 lun 0: &lt;TANDBERG TDC 3600       -06:&gt;
-Feb 25 21:03:34 yedi /kernel: sa0: Tandberg tdc3600 is a known rogue
-
-Mar 29 21:16:37 yedi /kernel: aha0 targ 5 lun 0: &lt;ARCHIVE VIPER 150  21247-005&gt;
-Mar 29 21:16:37 yedi /kernel: sa1: Archive  Viper 150 is a known rogue </screen>
-
-	  <para>For instance, there are devices that respond to all LUNs on a
-	    certain target ID, even if they are actually only one device.  It
-	    is easy to see that the kernel might be fooled into believing that
-	    there are 8 LUNs at that particular target ID. The confusion this
-	    causes is left as an exercise to the reader.</para>
-
-	  <para>The SCSI subsystem of FreeBSD recognizes devices with bad
-	    habits by looking at the INQUIRY response they send when probed.
-	    Because the INQUIRY response also includes the version number of
-	    the device  firmware, it is even possible that for different
-	    firmware versions different workarounds are used. See e.g.
-	    <filename>/sys/cam/scsi/scsi_sa.c</filename> and
-	    <filename>/sys/cam/scsi/scsi_all.c</filename> for more info on how
-	    this is done.</para>
-
-	  <para>This scheme works fine, but keep in mind that it of course
-	    only works for devices that are known to be weird.  If you are the
-	    first to connect your bogus Mumbletech SCSI CDROM you might be
-	    the one that has to define which workaround is needed.</para>
-
-	  <para>After you got your Mumbletech working, please send the
-	    required workaround to the FreeBSD development team for inclusion
-	    in the next release of FreeBSD.  Other Mumbletech owners will be
-	    grateful  to you.</para>
-	</sect3>
-
-	<sect3>
-	  <title>Multiple LUN devices</title>
-
-	  <para>In some cases you come across devices that use multiple
-	    logical units (LUNs) on a single SCSI ID.  In most cases FreeBSD
-	    only probes devices for LUN 0.  An example are so called bridge
-	    boards that connect 2 non-SCSI hard disks to a SCSI bus (e.g. an
-	    Emulex MD21 found in old Sun systems).</para>
-
-	  <para>This means that any devices with LUNs != 0 are not normally
-	    found during device probe on system boot.  To work around this
-	    problem you must add an appropriate entry in /sys/cam/scsi
-	    and rebuild your kernel.</para>
-
-	  <para>Look for a struct that is initialized like below:
-	    (FIXME: which file? Do these entries still exist in this form
-            now that we use CAM?)</para>
-
-	  <programlisting>{
-        T_DIRECT, T_FIXED, "MAXTOR", "XT-4170S", "B5A",
-        "mx1", SC_ONE_LU
-}</programlisting>
-
-	  <para>For your Mumbletech BRIDGE2000 that has more than one LUN, acts
-	    as a SCSI disk and has firmware revision 123 you would add
-	    something like:</para>
-
-	  <programlisting>{
-        T_DIRECT, T_FIXED, "MUMBLETECH", "BRIDGE2000", "123",
-        "da", SC_MORE_LUS
-}</programlisting>
-
-	  <para>The kernel on boot scans the inquiry data it receives against
-	    the table and acts accordingly.  See the source for more
-	    info.</para>
-	</sect3>
-
-	<sect3>
-	  <title>Tagged command queuing</title>
-
-	  <para>Modern SCSI devices, particularly magnetic disks,
-	    support what is called tagged command queuing (TCQ).</para>
-
-	  <para>In a nutshell, TCQ allows the device to have multiple I/O
-	    requests outstanding at the same time.  Because the device is
-	    intelligent, it can optimize its operations (like head
-	    positioning) based on its own request queue.  On  SCSI devices
-	    like RAID (Redundant Array of Independent Disks) arrays the TCQ
-	    function is indispensable to take advantage of the device's
-	    inherent parallelism.</para>
-
-	  <para>Each I/O request is uniquely identified by a <quote>tag</quote>
-	    (hence the name tagged command queuing) and this tag is used by
-	    FreeBSD to see which I/O in the device drivers queue is reported
-	    as complete by the device.</para>
-
-	  <para>It should be noted however that TCQ requires device driver
-	    support and that some devices implemented it <quote>not quite
-	    right</quote> in their firmware.  This problem bit me once, and it
-	    leads to highly mysterious problems.  In such cases, try to
-	    disable TCQ.</para>
-	</sect3>
-
-	<sect3>
-	  <title>Bus-master host adapters</title>
-
-	  <para>Most, but not all, SCSI host adapters are bus mastering
-	    controllers.  This means that they can do I/O on their own without
-	    putting load onto the host CPU for data movement.</para>
-
-	  <para>This is of course an advantage for a multitasking operating
-	    system like FreeBSD.  It must be noted however that there might be
-	    some rough edges.</para>
-
-	  <para>For instance an Adaptec 1542 controller can be set to use
-	    different transfer speeds on the host bus (ISA or AT in this
-	    case).  The controller is settable to different rates because not
-	    all motherboards can handle the higher speeds.  Problems like
-	    hang-ups, bad data etc might be the result of using a higher data
-	    transfer rate then your motherboard can stomach.</para>
-
-	  <para>The solution is of course obvious: switch to a lower data
-	    transfer rate and try if that works better.</para>
-
-	  <para>In the case of a Adaptec 1542, there is an option that can be
-	    put into the kernel config file to allow dynamic determination of
-	    the right, read: fastest feasible, transfer rate.  This option is
-	    disabled by default:</para>
-
-	  <programlisting>options        "TUNE_1542"             #dynamic tune of bus DMA speed</programlisting>
-
-	  <para>Check the manual pages for the host adapter that you use.  Or
-	    better still, use the ultimate documentation (read: driver
-	    source).</para>
-	</sect3>
-      </sect2>
-
-      <sect2>
-	<title>Tracking down problems</title>
-
-	<para>The following list is an attempt to give a guideline for the
-	  most common SCSI problems and their solutions.  It is by no means
-	  complete.</para>
-
-	<itemizedlist>
-	  <listitem>
-	    <para>Check for loose connectors and cables.</para>
-	  </listitem>
-
-	  <listitem>
-	    <para>Check and double check the location and number of your
-	      terminators.</para>
-	  </listitem>
-
-	  <listitem>
-	    <para>Check if your bus has at least one supplier of terminator
-	      power (especially with external terminators.</para>
-	  </listitem>
-
-	  <listitem>
-	    <para>Check if no double target IDs are used.</para>
-	  </listitem>
-
-	  <listitem>
-	    <para>Check if all devices to be used are powered up.</para>
-	  </listitem>
-
-	  <listitem>
-	    <para>Make a minimal bus config with as little devices as
-	      possible.</para>
-	  </listitem>
-
-	  <listitem>
-	    <para>If possible, configure your host adapter to use slow bus
-	      speeds.</para>
-	  </listitem>
-
-	  <listitem>
-	    <para>Disable tagged command queuing to make things as simple as
-	      possible (for a NCR host adapter based system see man
-	      ncrcontrol)</para>
-	  </listitem>
-
-	  <listitem>
-	    <para>If you can compile a kernel, make one with the
-	      <literal>SCSIDEBUG</literal> option, and try accessing the
-	      device with debugging turned on for that device.  If your device
-	      does not even probe at startup, you may have to define the
-	      address of the device that is failing, and the desired debug
-	      level in <filename>/sys/cam/cam_debug.h</filename>. If it
-	      probes but just does not work, you can use the
-	      &man.camcontrol.8; command to dynamically set a debug level to
-	      it in a running kernel (if <literal>CAMDEBUG</literal> is
-	      defined).  This will give you <emphasis>copious</emphasis>
-	      debugging output with which to confuse the gurus. See
-	      <command>man camcontrol</command> for more exact information.  Also
-	      look at <command>man 4 pass</command>.</para>
-	  </listitem>
-	</itemizedlist>
-      </sect2>
-
-      <sect2 id="scsi-further-reading">
-	<title>Further reading</title>
-
-	<para>If you intend to do some serious SCSI hacking, you might want to
-	  have the official standard at hand:</para>
-
-	<para>Approved American National Standards can be purchased from
-	  ANSI at
-
-	  <address>
-	    <otheraddr>13th Floor</otheraddr>
-	    <street>11 West 42nd Street</street>
-	    <city>New York</city>
-	    <state>NY</state> <postcode>10036</postcode>
-	    Sales Dept: <phone>(212) 642-4900</phone>
-	  </address>
-	</para>
-
-	<para>You can also buy many ANSI
-	  standards and most committee draft documents from Global
-	  Engineering Documents,
-
-	  <address>
-	    <street>15 Inverness Way East</street>
-	    <city>Englewood</city>
-	    <state>CO</state>, <postcode>80112-5704</postcode>
-	    Phone: <phone>(800) 854-7179</phone>
-	    Outside USA and Canada: <phone>(303) 792-2181</phone>
-	    Fax: <fax>(303) 792- 2192</fax>
-	  </address>
-	</para>
-
-	<para>Many X3T10 draft documents are available electronically on the
-	  SCSI BBS (719-574-0424) and on the <hostid
-	    role="fqdn">ncrinfo.ncr.com</hostid> anonymous FTP site.</para>
-
-	<para>Latest X3T10 committee documents are:</para>
-
-	<itemizedlist>
-	  <listitem>
-	    <para>AT Attachment (ATA or IDE) [X3.221-1994]
-	      (<emphasis>Approved</emphasis>)</para>
-	  </listitem>
-
-	  <listitem>
-	    <para>ATA Extensions (ATA-2) [X3T10/948D Rev 2i]</para>
-	  </listitem>
-
-	  <listitem>
-	    <para>Enhanced Small Device Interface (ESDI)
-	      [X3.170-1990/X3.170a-1991]
-	      (<emphasis>Approved</emphasis>)</para>
-	  </listitem>
-
-	  <listitem>
-	    <para>Small Computer System Interface &mdash; 2 (SCSI-2)
-	      [X3.131-1994] (<emphasis>Approved</emphasis>)</para>
-	  </listitem>
-
-	  <listitem>
-	    <para>SCSI-2 Common Access Method Transport and SCSI Interface
-	      Module (CAM)  [X3T10/792D Rev 11]</para>
-	  </listitem>
-	</itemizedlist>
-
-	<para>Other publications that might provide you with additional
-	  information are:</para>
-
-	<itemizedlist>
-	  <listitem>
-	    <para><quote>SCSI: Understanding the Small Computer System
-	      Interface</quote>, written by NCR  Corporation.  Available from:
-	      Prentice Hall, Englewood Cliffs, NJ, 07632 Phone: (201) 767-5937
-	      ISBN 0-13-796855-8</para>
-	  </listitem>
-
-	  <listitem>
-	    <para><quote>Basics of SCSI</quote>, a SCSI tutorial written by
-	      Ancot Corporation Contact Ancot for availability information at:
-	      Phone: (415) 322-5322  Fax: (415) 322-0455</para>
-	  </listitem>
-
-	  <listitem>
-	    <para><quote>SCSI Interconnection Guide Book</quote>, an AMP
-	      publication (dated 4/93, Catalog  65237) that lists the various
-	      SCSI connectors and suggests cabling schemes.  Available from
-	      AMP at (800) 522-6752 or (717) 564-0100</para>
-	  </listitem>
-
-	  <listitem>
-	    <para><quote>Fast Track to SCSI</quote>, A Product Guide written by
-	      Fujitsu.  Available from: Prentice Hall, Englewood Cliffs, NJ,
-	      07632 Phone: (201) 767-5937 ISBN 0-13-307000-X</para>
-	  </listitem>
-
-	  <listitem>
-	    <para><quote>The SCSI Bench Reference</quote>, <quote>The SCSI
-	      Encyclopedia</quote>, and the <quote>SCSI Tutor</quote>, ENDL
-	      Publications, 14426 Black Walnut Court, Saratoga CA, 95070
-	      Phone: (408) 867-6642</para>
-	  </listitem>
-
-	  <listitem>
-	    <para><quote>Zadian SCSI Navigator</quote> (quick ref. book) and
-	      <quote>Discover the Power of SCSI</quote>  (First book along with
-	      a one-hour video and tutorial book), Zadian Software, Suite 214,
-	      1210 S. Bascom Ave., San Jose, CA 92128, (408) 293-0800</para>
-	  </listitem>
-	</itemizedlist>
-
-	<para>On Usenet the newsgroups <ulink
-	    url="news:comp.periphs.scsi">comp.periphs.scsi</ulink> and <ulink
-	    url="news:comp.periphs">comp.periphs</ulink> are noteworthy places
-	  to look for more info.  You can also find the <ulink
-	  url="http://scsifaq.org:9080/scsi_faq/scsifaq.html">SCSI-FAQ</ulink>
-	  there, which is posted periodically.</para>
-
-	<para>Most major SCSI device and host adapter suppliers operate FTP
-	  sites and/or BBS systems.  They may be valuable sources of
-	  information about the devices you own.</para>
-      </sect2>
-    </sect1>
-
-    <sect1 id="hw-storage-controllers">
-      <title>* Disk/tape controllers</title>
-
-      <sect2>
-	<title>* SCSI</title>
-
-	<para></para>
-      </sect2>
-
-      <sect2>
-	<title>* IDE</title>
-
-	<para></para>
-      </sect2>
-
-      <sect2>
-	<title>* Floppy</title>
-
-	<para></para>
-      </sect2>
-    </sect1>
-
-    <sect1>
-      <title>Hard drives</title>
-
-      <sect2>
-	<title>SCSI hard drives</title>
-
-	<para><emphasis>Contributed by &a.asami;.  17 February
-	    1998.</emphasis></para>
-
-	<para>As mentioned in the <link linkend="scsi">SCSI</link> section,
-	  virtually all SCSI hard drives sold today are SCSI-2 compliant and
-	  thus will work fine as long as you connect them to a supported SCSI
-	  host adapter.  Most problems people encounter are either due to
-	  badly designed cabling (cable too long, star topology, etc.),
-	  insufficient termination, or defective parts. Please refer to the
-	  <link linkend="scsi">SCSI</link> section first if your SCSI hard
-	  drive is not working.  However, there are a couple of things you may
-	  want to take into account before you purchase SCSI hard drives for
-	  your system.</para>
-
-	<sect3>
-	  <title>Rotational speed</title>
-
-	  <para>Rotational speeds of SCSI drives sold today range from around
-	    4,500RPM to 15,000RPM.  Most of them are either 7,200RPM or
-	    10,000RPM, with 15,000RPM becoming affordable (June 2002).
-	    Even though the 10,000RPM drives can generally transfer
-	    data faster, they run considerably hotter than their 7,200RPM
-	    counterparts.  A large fraction of today's disk drive malfunctions
-	    are heat-related.  If you do not have very good cooling in your PC
-	    case, you may want to stick with 7,200RPM or slower drives.</para>
-
-	  <para>Note that newer drives, with higher areal recording densities,
-	    can deliver much more bits per rotation than older ones.  Today's
-	    top-of-line 7,200RPM drives can sustain a throughput comparable to
-	    10,000RPM drives of one or two model generations ago.  The number
-	    to find on the spec sheet for bandwidth is <quote>internal data
-	    (or transfer) rate</quote>.  It is usually in megabits/sec so
-	    divide it by 8 and you will get the rough approximation of how much
-	    megabytes/sec you can get out of the drive.</para>
-
-	  <para>(If you are a speed maniac and want a 15,000RPM drive for your
-	    cute little PC, be my guest; however, those drives become
-	    extremely hot.  Do not even think about it if you do not have a fan
-	    blowing air <emphasis>directly at</emphasis> the drive or a
-	    properly ventilated disk enclosure.)</para>
-
-	  <para>Obviously, the latest 15,000RPM drives and 10,000RPM drives can
-	    deliver more data than the latest 7,200RPM drives, so if absolute
-	    bandwidth is the necessity for your applications, you have little
-	    choice but to get the faster drives.  Also, if you need low
-	    latency, faster drives are better; not only do they usually have
-	    lower average seek times, but also the rotational delay is one
-	    place where slow-spinning drives can never beat a faster one.
-	    (The average rotational latency is half the time it takes to
-	    rotate the drive once; thus, it is 2 milliseconds for 15,000RPM,
-	    3ms for 10,000RPM
-	    drives, 4.2ms for 7,200RPM drives and 5.6ms for 5,400RPM drives.)
-	    Latency is seek time plus rotational delay. Make sure you
-	    understand whether you need low latency or more accesses per
-	    second, though; in the latter case (e.g., news servers), it may
-	    not be optimal to purchase one big fast drive.  You can achieve
-	    similar or even better results by using the ccd (concatenated
-	    disk) driver to create a striped disk array out of multiple slower
-	    drives for comparable overall cost.</para>
-
-	  <para>Make sure you have adequate air flow around the drive,
-	    especially if you are going to use a fast-spinning drive.  You
-	    generally need at least 1/2&rdquo; (1.25cm) of spacing above and below a
-	    drive.  Understand how the air flows through your PC case.  Most
-	    cases have the power supply suck the air out of the back.  See
-	    where the air flows in, and put the drive where it will have the
-	    largest volume of cool air flowing around it. You may need to seal
-	    some unwanted holes or add a new fan for effective cooling.</para>
-
-	  <para>Another consideration is noise.  Many 10,000 or faster drives
-	    generate a high-pitched whine which is quite unpleasant to most
-	    people.  That, plus the extra fans often required for cooling, may
-	    make 10,000 or faster drives unsuitable for some office and home
-	    environments.</para>
-	</sect3>
-
-	<sect3>
-	  <title>Form factor</title>
-
-	  <para>Most SCSI drives sold today are of 3.5&rdquo; form factor.  They
-	    come in two different heights; 1.6&rdquo; (<quote>half-height</quote>) or
-	    1&rdquo; (<quote>low-profile</quote>).  The half-height drive is the same
-	    height as a CDROM drive.  However, do not forget the spacing rule
-	    mentioned in the previous section.  If you have three standard
-	    3.5&rdquo; drive bays, you will not be able to put three half-height
-	    drives in there (without frying them, that is).</para>
-	</sect3>
-
-	<sect3>
-	  <title>Interface</title>
-
-	  <para>The majority of SCSI hard drives sold today are Ultra,
-	    Ultra-wide, or Ultra160 SCSI. As of this writing (June 2002),
-	    the first Ultra320 host adapters and devices become available.
-	    The maximum bandwidth of Ultra SCSI is 20MB/sec,
-	    and Ultra-wide SCSI is 40MB/sec. Ultra160 can transfer 160MB/sec
-	    and Ultra320 can transfer 320MB/sec.  There is no difference in max
-	    cable length between Ultra and Ultra-wide; however, the more
-	    devices you have on the same bus, the sooner you will start having
-	    bus integrity problems.  Unless you have a well-designed disk
-	    enclosure, it is not easy to make more than 5 or 6 Ultra SCSI
-	    drives work on a single bus.</para>
-
-	  <para>On the other hand, if you need to connect many drives, going
-	    for Fast-wide SCSI may not be a bad idea.  That will have the same
-	    max bandwidth as Ultra (narrow) SCSI, while electronically it is
-	    much easier to get it <quote>right</quote>.  My advice would be: if
-	    you want to connect many disks, get wide or Ultra160 SCSI drives;
-        they usually
-	    cost a little more but it may save you down the road.  (Besides,
-	    if you can not afford the cost difference, you should not be building
-	    a disk array.)</para>
-
-	  <para>There are two variant of wide SCSI drives; 68-pin and 80-pin
-	    SCA (Single Connector Attach).  The SCA drives do not have a
-	    separate 4-pin power connector, and also read the SCSI ID settings
-	    through the 80-pin connector.  If you are really serious about
-	    building a large storage system, get SCA drives and a good SCA
-	    enclosure (dual power supply with at least one extra fan).  They
-	    are more electronically sound than 68-pin counterparts because
-	    there is no <quote>stub</quote> of the SCSI bus inside the disk
-	    canister as in arrays built from 68-pin drives.  They are easier
-	    to install too (you just need to screw the drive in the canister,
-	    instead of trying to squeeze in your fingers in a tight place to
-	    hook up all the little cables (like the SCSI ID and disk activity
-	    LED lines).</para>
-	</sect3>
-      </sect2>
-
-      <sect2>
-	<title>* IDE hard drives</title>
-
-	<para></para>
-      </sect2>
-    </sect1>
-
-    <sect1>
-      <title>Tape drives</title>
-
-      <para><emphasis>Contributed by &a.jmb;.  2 July
-	  1996.</emphasis></para>
-
-      <sect2>
-	<title>General tape access commands</title>
-
-	<para>&man.mt.1; provides generic access to the tape drives.  Some of
-	  the more common commands are <command>rewind</command>,
-	  <command>erase</command>, and <command>status</command>.  See the
-	    &man.mt.1; manual page for a detailed description.</para>
-      </sect2>
-
-      <sect2>
-	<title>Controller Interfaces</title>
-
-	<para>There are several different interfaces that support tape drives.
-	  The interfaces are SCSI, IDE, Floppy and Parallel Port. A wide
-	  variety of tape drives are available for these interfaces.
-	  Controllers are discussed in <link
-	    linkend="hw-storage-controllers">Disk/tape
-	    controllers</link>.</para>
-      </sect2>
-
-      <sect2>
-	<title>SCSI drives</title>
-
-	<para>The &man.st.4; driver provides support for 8mm (Exabyte), 4mm
-	  (DAT: Digital Audio Tape), QIC (Quarter-Inch Cartridge), DLT
-	  (Digital Linear Tape), QIC Mini cartridge and 9-track (remember the
-	  big reels that you see spinning in Hollywood computer rooms) tape
-	  drives.  See the &man.st.4; manual page for a detailed
-	  description.</para>
-
-	<para>The drives listed below are currently being used by members of
-	  the FreeBSD community.  They are not the only drives that will work
-	  with FreeBSD.  They just happen to be the ones that we use.</para>
-
-	<sect3>
-	  <title>4mm (DAT: Digital Audio Tape)</title>
-
-	  <para><link linkend="hw-storage-python-28454">Archive Python
-	      28454</link></para>
-
-	  <para><link linkend="hw-storage-python-04687">Archive Python
-	      04687</link></para>
-
-	  <para><link linkend="hw-storage-hp1533a">HP C1533A</link></para>
-
-	  <para><link linkend="hw-storage-hp1534a">HP C1534A</link></para>
-
-	  <para><link linkend="hw-storage-hp35450a">HP 35450A</link></para>
-
-	  <para><link linkend="hw-storage-hp35470a">HP 35470A</link></para>
-
-	  <para><link linkend="hw-storage-hp35480a">HP 35480A</link></para>
-
-	  <para><link linkend="hw-storage-sdt5000">SDT-5000</link></para>
-
-	  <para><link linkend="hw-storage-wangtek6200">Wangtek
-	      6200</link></para>
-	</sect3>
-
-	<sect3>
-	  <title>8mm (Exabyte)</title>
-
-	  <para><link linkend="hw-storage-exb8200">EXB-8200</link></para>
-
-	  <para><link linkend="hw-storage-exb8500">EXB-8500</link></para>
-
-	  <para><link linkend="hw-storage-exb8505">EXB-8505</link></para>
-	</sect3>
-
-	<sect3>
-	  <title>QIC (Quarter-Inch Cartridge)</title>
-
-	  <para><link linkend="hw-storage-anaconda">Archive Anaconda
-	      2750</link></para>
-
-	  <para><link linkend="hw-storage-viper60">Archive Viper
-	      60</link></para>
-
-	  <para><link linkend="hw-storage-viper150">Archive Viper
-	      150</link></para>
-
-	  <para><link linkend="hw-storage-viper2525">Archive Viper
-	      2525</link></para>
-
-	  <para><link linkend="hw-storage-tandberg3600">Tandberg TDC
-	      3600</link></para>
-
-	  <para><link linkend="hw-storage-tandberg3620">Tandberg TDC
-	      3620</link></para>
-
-	  <para><link linkend="hw-storage-tandberg3800">Tandberg TDC
-	      3800</link></para>
-
-	  <para><link linkend="hw-storage-tandberg4222">Tandberg TDC
-	      4222</link></para>
-
-	  <para><link linkend="hw-storage-wangtek5525es">Wangtek
-	      5525ES</link></para>
-	</sect3>
-
-	<sect3>
-	  <title>DLT (Digital Linear Tape)</title>
-
-	  <para><link linkend="hw-storage-dectz87">Digital TZ87</link></para>
-	</sect3>
-
-	<sect3>
-	  <title>Mini-Cartridge</title>
-
-	  <para><link linkend="hw-storage-ctms3200">Conner CTMS
-	      3200</link></para>
-
-	  <para><link linkend="hw-storage-exb2501">Exabyte 2501</link></para>
-	</sect3>
-
-	<sect3>
-	  <title>Autoloaders/Changers</title>
-
-	  <para><link linkend="hw-storage-hp1553a">Hewlett-Packard HP C1553A
-	      Autoloading DDS2</link></para>
-	</sect3>
-      </sect2>
-
-      <sect2>
-	<title>* IDE drives</title>
-
-	<para></para>
-      </sect2>
-
-      <sect2>
-	<title>Floppy drives</title>
-
-	<para><link linkend="hw-storage-conner420r">Conner 420R</link></para>
-      </sect2>
-
-      <sect2>
-	<title>* Parallel port drives</title>
-
-	<para></para>
-      </sect2>
-
-      <sect2>
-	<title>Detailed Information</title>
-
-	<sect3 id="hw-storage-anaconda">
-	  <title>Archive Anaconda 2750</title>
-
-	  <para>The boot message identifier for this drive is <literal>ARCHIVE
-	      ANCDA 2750 28077 -003 type 1 removable SCSI 2</literal></para>
-
-	  <para>This is a QIC tape drive.</para>
-
-	  <para>Native capacity is 1.35GB when using QIC-1350 tapes.  This
-	    drive will read and write QIC-150 (DC6150), QIC-250 (DC6250), and
-	    QIC-525 (DC6525) tapes as well.</para>
-
-	  <para>Data transfer rate is 350kB/s using &man.dump.8;.
-	    Rates of 530kB/s have been reported when using
-	    Amanda</para>
-
-	  <para>Production of this drive has been discontinued.</para>
-
-	  <para>The SCSI bus connector on this tape drive is reversed from
-	    that on most other SCSI devices.  Make sure that you have enough
-	    SCSI cable to twist the cable one-half turn before and after the
-	    Archive Anaconda tape drive, or turn your other SCSI devices
-	    upside-down.</para>
-
-	  <para>Two kernel code changes are required to use this drive. This
-	    drive will not work as delivered.</para>
-
-	  <para>If you have a SCSI-2 controller, short jumper 6. Otherwise,
-	    the drive behaves are a SCSI-1 device.  When operating as a SCSI-1
-	    device, this drive, <quote>locks</quote> the SCSI bus during some
-	    tape operations, including: fsf, rewind, and rewoffl.</para>
-
-	  <para>If you are using the NCR SCSI controllers, patch the file
-	    <filename>/usr/src/sys/pci/ncr.c</filename> (as shown below).
-	    Build and install a new kernel.</para>
-
-	  <programlisting>*** 4831,4835 ****
-                };
-
-!               if (np-&gt;latetime&gt;4) {
-                        /*
-                        **      Although we tried to wake it up,
---- 4831,4836 ----
-                };
-
-!               if (np-&gt;latetime&gt;1200) {
-                        /*
-                        **      Although we tried to wake it up,</programlisting>
-
-	  <para>Reported by: &a.jmb;</para>
-	</sect3>
-
-	<sect3 id="hw-storage-python-28454">
-	  <title>Archive Python 28454</title>
-
-	  <para>The boot message identifier for this drive is <literal>ARCHIVE
-	      Python 28454-XXX4ASB</literal> <literal>type 1 removable SCSI
-	      2</literal> <literal>density code 0x8c, 512-byte
-	      blocks</literal></para>
-
-	  <para>This is a DDS-1 tape drive.</para>
-
-	  <para>Native capacity is 2.5GB on 90m tapes.</para>
-
-	  <para>Data transfer rate is XXX.</para>
-
-	  <para>This drive was repackaged by Sun Microsystems as model
-	    595-3067.</para>
-
-	  <para>Reported by: Bob Bishop <email>rb@gid.co.uk</email></para>
-
-	  <para>Throughput is in the 1.5 MByte/sec range, however this will
-	    drop if the disks and tape drive are on the same SCSI
-	    controller.</para>
-
-	  <para>Reported by: Robert E. Seastrom
-	    <email>rs@seastrom.com</email></para>
-	</sect3>
-
-	<sect3 id="hw-storage-python-04687">
-	  <title>Archive Python 04687</title>
-
-	  <para>The boot message identifier for this drive is <literal>ARCHIVE
-	      Python 04687-XXX 6580</literal> <literal>Removable Sequential
-	      Access SCSI-2 device</literal></para>
-
-	  <para>This is a DAT-DDS-2 drive.</para>
-
-	  <para>Native capacity is 4GB when using 120m tapes.</para>
-
-	  <para>This drive supports hardware data compression.  Switch 4
-	    controls MRS (Media Recognition System).  MRS tapes have stripes
-	    on the transparent leader.  Switch 4 <emphasis>off</emphasis>
-	    enables MRS, <emphasis>on</emphasis> disables MRS.</para>
-
-	  <para>Parity is controlled by switch 5.  Switch 5
-	    <emphasis>on</emphasis> to enable parity control.  Compression is
-	    enabled with Switch 6 <emphasis>off</emphasis>.  It is possible to
-	    override compression with the <literal>SCSI MODE SELECT</literal>
-	    command (see &man.mt.1;).</para>
-
-	  <para>Data transfer rate is 800kB/s.</para>
-	</sect3>
-
-	<sect3 id="hw-storage-viper60">
-	  <title>Archive Viper 60</title>
-
-	  <para>The boot message identifier for this drive is <literal>ARCHIVE
-	      VIPER 60 21116 -007</literal> <literal>type 1 removable SCSI
-	      1</literal></para>
-
-	  <para>This is a QIC tape drive.</para>
-
-	  <para>Native capacity is 60MB.</para>
-
-	  <para>Data transfer rate is XXX.</para>
-
-	  <para>Production of this drive has been discontinued.</para>
-
-	  <para>Reported by: Philippe Regnauld
-	    <email>regnauld@hsc.fr</email></para>
-	</sect3>
-
-	<sect3 id="hw-storage-viper150">
-	  <title>Archive Viper 150</title>
-
-	  <para>The boot message identifier for this drive is <literal>ARCHIVE
-	      VIPER 150 21531 -004</literal> <literal>Archive Viper 150 is a
-	      known rogue</literal> <literal>type 1 removable SCSI
-	      1</literal>.  A multitude of firmware revisions exist for this
-	    drive.  Your drive may report different numbers (e.g
-	    <literal>21247 -005</literal>.</para>
-
-	  <para>This is a QIC tape drive.</para>
-
-	  <para>Native capacity is 150/250MB.  Both 150MB (DC6150) and 250MB
-	    (DC6250) tapes have the recording format.  The 250MB tapes are
-	    approximately 67% longer than the 150MB tapes.  This drive can
-	    read 120MB tapes as well.  It can not write 120MB tapes.</para>
-
-	  <para>Data transfer rate is 100kB/s</para>
-
-	  <para>This drive reads and writes DC6150 (150MB) and DC6250 (250MB)
-	    tapes.</para>
-
-	  <para>This drives quirks are known and pre-compiled into the SCSI
-	    tape device driver (&man.st.4;).</para>
-
-	  <para>Under FreeBSD 2.2-CURRENT, use <command>mt blocksize
-	      512</command> to set the blocksize.  (The particular drive had
-	    firmware revision 21247 -005.  Other firmware revisions may behave
-	    differently) Previous versions of FreeBSD did not have this
-	    problem.</para>
-
-	  <para>Production of this drive has been discontinued.</para>
-
-	  <para>Reported by: Pedro A M Vazquez
-	    <email>vazquez@IQM.Unicamp.BR</email></para>
-
-	  <para>&a.msmith;</para>
-	</sect3>
-
-	<sect3 id="hw-storage-viper2525">
-	  <title>Archive Viper 2525</title>
-
-	  <para>The boot message identifier for this drive is <literal>ARCHIVE
-	      VIPER 2525 25462 -011</literal> <literal>type 1 removable SCSI
-	      1</literal></para>
-
-	  <para>This is a QIC tape drive.</para>
-
-	  <para>Native capacity is 525MB.</para>
-
-	  <para>Data transfer rate is 180kB/s at 90 inches/sec.</para>
-
-	  <para>The drive reads QIC-525, QIC-150, QIC-120 and QIC-24 tapes.
-	    Writes QIC-525, QIC-150, and QIC-120.</para>
-
-	  <para>Firmware revisions prior to <literal>25462 -011</literal> are
-	    bug ridden and will not function properly.</para>
-
-	  <para>Production of this drive has been discontinued.</para>
-	</sect3>
-
-	<sect3 id="hw-storage-conner420r">
-	  <title>Conner 420R</title>
-
-	  <para>The boot message identifier for this drive is <literal>Conner
-	      tape</literal>.</para>
-
-	  <para>This is a floppy controller, mini cartridge tape drive.</para>
-
-	  <para>Native capacity is XXXX</para>
-
-	  <para>Data transfer rate is XXX</para>
-
-	  <para>The drive uses QIC-80 tape cartridges.</para>
-
-	  <para>Reported by: Mark Hannon
-	    <email>mark@seeware.DIALix.oz.au</email></para>
-	</sect3>
-
-	<sect3 id="hw-storage-ctms3200">
-	  <title>Conner CTMS 3200</title>
-
-	  <para>The boot message identifier for this drive is <literal>CONNER
-	      CTMS 3200 7.00</literal> <literal>type 1 removable SCSI
-	      2</literal>.</para>
-
-	  <para>This is a mini cartridge tape drive.</para>
-
-	  <para>Native capacity is XXXX</para>
-
-	  <para>Data transfer rate is XXX</para>
-
-	  <para>The drive uses QIC-3080 tape cartridges.</para>
-
-	  <para>Reported by: Thomas S. Traylor
-	    <email>tst@titan.cs.mci.com</email></para>
-	</sect3>
-
-	<sect3 id="hw-storage-dectz87">
-	  <title><ulink
-	      url="http://www.digital.com/info/Customer-Update/931206004.txt.html">DEC TZ87</ulink></title>
-
-	  <para>The boot message identifier for this drive is <literal>DEC
-	      TZ87 (C) DEC 9206</literal> <literal>type 1 removable SCSI
-	      2</literal> <literal>density code 0x19</literal></para>
-
-	  <para>This is a DLT tape drive.</para>
-
-	  <para>Native capacity is 10GB.</para>
-
-	  <para>This drive supports hardware data compression.</para>
-
-	  <para>Data transfer rate is 1.2MB/s.</para>
-
-	  <para>This drive is identical to the Quantum DLT2000.  The drive
-	    firmware can be set to emulate several well-known drives,
-	    including an Exabyte 8mm drive.</para>
-
-	  <para>Reported by: &a.wilko;</para>
-	</sect3>
-
-	<sect3 id="hw-storage-exb2501">
-	  <title><ulink
-	      url="http://www.Exabyte.COM:80/Products/Minicartridge/2501/Rfeatures.html">Exabyte EXB-2501</ulink></title>
-
-	  <para>The boot message identifier for this drive is <literal>EXABYTE
-	      EXB-2501</literal></para>
-
-	  <para>This is a mini-cartridge tape drive.</para>
-
-	  <para>Native capacity is 1GB when using MC3000XL
-	    mini cartridges.</para>
-
-	  <para>Data transfer rate is XXX</para>
-
-	  <para>This drive can read and write DC2300 (550MB), DC2750 (750MB),
-	    MC3000 (750MB), and MC3000XL (1GB) mini cartridges.</para>
-
-	  <para>WARNING: This drive does not meet the SCSI-2 specifications.
-	    The drive locks up completely in response to a SCSI MODE_SELECT
-	    command unless there is a formatted tape in the drive.  Before
-	    using this drive, set the tape blocksize with</para>
-
-	  <screen>&prompt.root; <userinput>mt -f /dev/st0ctl.0 blocksize 1024</userinput></screen>
-
-	  <para>Before using a mini cartridge for the first time, the
-	    mini cartridge must be formatted.  FreeBSD 2.1.0-RELEASE and
-	    earlier:</para>
-
-	  <screen>&prompt.root; <userinput>/sbin/scsi -f /dev/rst0.ctl -s 600 -c "4 0 0 0 0 0"</userinput></screen>
-
-	  <para>(Alternatively, fetch a copy of the
-	    <command>scsiformat</command> shell script from FreeBSD
-	    2.1.5/2.2.) FreeBSD 2.1.5 and later:</para>
-
-	  <screen>&prompt.root; <userinput>/sbin/scsiformat -q -w /dev/rst0.ctl</userinput></screen>
-
-	  <para>Right now, this drive cannot really be recommended for
-	    FreeBSD.</para>
-
-	  <para>Reported by: Bob Beaulieu
-	    <email>ez@eztravel.com</email></para>
-	</sect3>
-
-	<sect3 id="hw-storage-exb8200">
-	  <title>Exabyte EXB-8200</title>
-
-	  <para>The boot message identifier for this drive is <literal>EXABYTE
-	      EXB-8200 252X</literal> <literal>type 1 removable SCSI
-	      1</literal></para>
-
-	  <para>This is an 8mm tape drive.</para>
-
-	  <para>Native capacity is 2.3GB.</para>
-
-	  <para>Data transfer rate is 270kB/s.</para>
-
-	  <para>This drive is fairly slow in responding to the SCSI bus during
-	    boot.  A custom kernel may be required (set SCSI_DELAY to 10
-	    seconds).</para>
-
-	  <para>There are a large number of firmware configurations for this
-	    drive, some have been customized to a particular vendor's
-	    hardware.  The firmware can be changed via EPROM
-	    replacement.</para>
-
-	  <para>Production of this drive has been discontinued.</para>
-
-	  <para>Reported by: &a.msmith;</para>
-	</sect3>
-
-	<sect3 id="hw-storage-exb8500">
-	  <title>Exabyte EXB-8500</title>
-
-	  <para>The boot message identifier for this drive is <literal>EXABYTE
-	      EXB-8500-85Qanx0 0415</literal> <literal>type 1 removable SCSI
-	      2</literal></para>
-
-	  <para>This is an 8mm tape drive.</para>
-
-	  <para>Native capacity is 5GB.</para>
-
-	  <para>Data transfer rate is 300kB/s.</para>
-
-	  <para>Reported by: Greg Lehey <email>grog@lemis.de</email></para>
-	</sect3>
-
-	<sect3 id="hw-storage-exb8505">
-	  <title><ulink
-	      url="http://www.Exabyte.COM:80/Products/8mm/8505XL/Rfeatures.html">Exabyte EXB-8505</ulink></title>
-
-	      <para>The boot message identifier for this drive is
-	    <literal>EXABYTE EXB-85058SQANXR1 05B0</literal> <literal>type 1
-	      removable SCSI 2</literal></para>
-
-	  <para>This is an 8mm tape drive which supports compression, and is
-	    upward compatible with the EXB-5200 and EXB-8500.</para>
-
-	  <para>Native capacity is 5GB.</para>
-
-	  <para>The drive supports hardware data compression.</para>
-
-	  <para>Data transfer rate is 300kB/s.</para>
-
-	  <para>Reported by: Glen Foster
-	    <email>gfoster@gfoster.com</email></para>
-	</sect3>
-
-	<sect3 id="hw-storage-hp1533a">
-	  <title>Hewlett-Packard HP C1533A</title>
-
-	  <para>The boot message identifier for this drive is <literal>HP
-	      C1533A 9503</literal> <literal>type 1 removable SCSI
-	      2</literal>.</para>
-
-	  <para>This is a DDS-2 tape drive.  DDS-2 means hardware data
-	    compression and narrower tracks for increased data
-	    capacity.</para>
-
-	  <para>Native capacity is 4GB when using 120m tapes.  This drive
-	    supports hardware data compression.</para>
-
-	  <para>Data transfer rate is 510kB/s.</para>
-
-	  <para>This drive is used in Hewlett-Packard's SureStore 6000eU and
-	    6000i tape drives and C1533A DDS-2 DAT drive.</para>
-
-	  <para>The drive has a block of 8 dip switches.  The proper settings
-	    for FreeBSD are: 1 ON; 2 ON; 3 OFF; 4 ON; 5 ON; 6 ON; 7 ON; 8
-	    ON.</para>
-
-	  <informaltable frame="none" pgwide="1">
-	    <tgroup cols="3">
-	      <thead>
-		<row>
-		  <entry>switch 1</entry>
-		  <entry>switch 2</entry>
-		  <entry>Result</entry>
-		</row>
-	      </thead>
-
-	      <tbody>
-		<row>
-		  <entry>On</entry>
-		  <entry>On</entry>
-		  <entry>Compression enabled at power-on, with host
-		    control</entry>
-		</row>
-
-		<row>
-		  <entry>On</entry>
-		  <entry>Off</entry>
-		  <entry>Compression enabled at power-on, no host
-		    control</entry>
-		</row>
-
-		<row>
-		  <entry>Off</entry>
-		  <entry>On</entry>
-		  <entry>Compression disabled at power-on, with host
-		    control</entry>
-		</row>
-
-		<row>
-		  <entry>Off</entry>
-		  <entry>Off</entry>
-		  <entry>Compression disabled at power-on, no host
-		    control</entry>
-		</row>
-	      </tbody>
-	    </tgroup>
-	  </informaltable>
-
-	  <para>Switch 3 controls MRS (Media Recognition System).  MRS tapes
-	    have stripes on the transparent leader.  These identify the tape
-	    as DDS (Digital Data Storage) grade media.  Tapes that do not have
-	    the stripes will be treated as write-protected.  Switch 3 OFF
-	    enables MRS.  Switch 3 ON disables MRS.</para>
-
-	      <para>See <ulink url="http://www.hp.com/tape/c_intro.html">HP
-	      SureStore Tape Products</ulink> and <ulink
-	      url="http://www.impediment.com/hp/hp_technical.html">Hewlett-Packard
-	      Disk and Tape Technical Information</ulink> for more information
-	    on configuring this drive.</para>
-
-	  <para><emphasis>Warning:</emphasis> Quality control on these drives
-	    varies greatly.  One FreeBSD core-team member has returned 2 of
-	    these drives.  Neither lasted more than 5 months.</para>
-
-	  <para>Reported by: &a.se;</para>
-	</sect3>
-
-	<sect3 id="hw-storage-hp1534a">
-	  <title>Hewlett-Packard HP 1534A</title>
-
-	  <para>The boot message identifier for this drive is <literal>HP
-	      HP35470A T503</literal> <literal>type 1 removable SCSI
-	      2</literal> <literal>Sequential-Access density code 0x13,
-	      variable blocks</literal>.</para>
-
-	  <para>This is a DDS-1 tape drive.  DDS-1 is the original DAT tape
-	    format.</para>
-
-	  <para>Native capacity is 2GB when using 90m tapes.</para>
-
-	  <para>Data transfer rate is 183kB/s.</para>
-
-	  <para>The same mechanism is used in Hewlett-Packard's SureStore
-	    <ulink url="http://www.dmo.hp.com/tape/sst2000.htm">2000i</ulink>
-	    tape drive, C35470A DDS format DAT drive, C1534A DDS format DAT
-	    drive and HP C1536A DDS format DAT drive.</para>
-
-	  <para>The HP C1534A DDS format DAT drive has two indicator lights,
-	    one green and one amber.  The green one indicates tape action:
-	    slow flash during load, steady when loaded, fast flash during
-	    read/write operations.  The amber one indicates warnings: slow
-	    flash when cleaning is required or tape is nearing the end of its
-	    useful life, steady indicates an hard fault.  (factory service
-	    required?)</para>
-
-	  <para>Reported by Gary Crutcher
-	    <email>gcrutchr@nightflight.com</email></para>
-	</sect3>
-
-	<sect3 id="hw-storage-hp1553a">
-	  <title>Hewlett-Packard HP C1553A Autoloading DDS2</title>
-
-	  <para>The boot message identifier for this drive is "".</para>
-
-	  <para>This is a DDS-2 tape drive with a tape changer.  DDS-2 means
-	    hardware data compression and narrower tracks for increased data
-	    capacity.</para>
-
-	  <para>Native capacity is 24GB when using 120m tapes.  This drive
-	    supports hardware data compression.</para>
-
-	  <para>Data transfer rate is 510kB/s (native).</para>
-
-	  <para>This drive is used in Hewlett-Packard's SureStore <ulink
-	      url="http://www.dmo.hp.com/tape/sst12000.htm">12000e</ulink>
-	    tape drive.</para>
-
-	  <para>The drive has two selectors on the rear panel.  The selector
-	    closer to the fan is SCSI id.  The other selector should be set to
-	    7.</para>
-
-	  <para>There are four internal switches.  These should be set: 1 ON;
-	    2 ON; 3 ON; 4 OFF.</para>
-
-	  <para>At present the kernel drivers do not automatically change
-	    tapes at the end of a volume.  This shell script can be used to
-	    change tapes:</para>
-
-	  <programlisting>#!/bin/sh
-PATH="/sbin:/usr/sbin:/bin:/usr/bin"; export PATH
-
-usage()
-{
-        echo "Usage: dds_changer [123456ne] raw-device-name
-        echo "1..6 = Select cartridge"
-        echo "next cartridge"
-        echo "eject magazine"
-        exit 2
-}
-
-if [ $# -ne 2 ] ; then
-        usage
-fi
-
-cdb3=0
-cdb4=0
-cdb5=0
-
-case $1 in
-        [123456])
-                cdb3=$1
-                cdb4=1
-                ;;
-        n)
-                ;;
-        e)
-                cdb5=0x80
-                ;;
-        ?)
-                usage
-                ;;
-esac
-
-scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5"</programlisting>
-	</sect3>
-
-	<sect3 id="hw-storage-hp35450a">
-	  <title>Hewlett-Packard HP 35450A</title>
-
-	  <para>The boot message identifier for this drive is <literal>HP
-	      HP35450A -A C620</literal> <literal>type 1 removable SCSI
-	      2</literal> <literal>Sequential-Access density code
-	      0x13</literal></para>
-
-	  <para>This is a DDS-1 tape drive.  DDS-1 is the original DAT tape
-	    format.</para>
-
-	  <para>Native capacity is 1.2GB.</para>
-
-	  <para>Data transfer rate is 160kB/s.</para>
-
-	  <para>Reported by: Mark Thompson
-	    <email>mark.a.thompson@pobox.com</email></para>
-	</sect3>
-
-	<sect3 id="hw-storage-hp35470a">
-	  <title>Hewlett-Packard HP 35470A</title>
-
-	  <para>The boot message identifier for this drive is <literal>HP
-	      HP35470A 9 09</literal> <literal>type 1 removable SCSI
-	      2</literal></para>
-
-	  <para>This is a DDS-1 tape drive.  DDS-1 is the original DAT tape
-	    format.</para>
-
-	  <para>Native capacity is 2GB when using 90m tapes.</para>
-
-	  <para>Data transfer rate is 183kB/s.</para>
-
-	  <para>The same mechanism is used in Hewlett-Packard's SureStore
-	    <ulink url="http://www.dmo.hp.com/tape/sst2000.htm">2000i</ulink>
-	    tape drive, C35470A DDS format DAT drive, C1534A DDS format DAT
-	    drive, and HP C1536A DDS format DAT drive.</para>
-
-	  <para><emphasis>Warning:</emphasis> Quality control on these drives
-	    varies greatly.  One FreeBSD core-team member has returned 5 of
-	    these drives.  None lasted more than 9 months.</para>
-
-	  <para>Reported by: David Dawes
-	    <email>dawes@rf900.physics.usyd.edu.au</email> (9 09)</para>
-
-	</sect3>
-
-	<sect3 id="hw-storage-hp35480a">
-	  <title>Hewlett-Packard HP 35480A</title>
-
-	  <para>The boot message identifier for this drive is <literal>HP
-	      HP35480A 1009</literal> <literal>type 1 removable SCSI
-	      2</literal> <literal>Sequential-Access density code
-	      0x13</literal>.</para>
-
-	  <para>This is a DDS-DC tape drive.  DDS-DC is DDS-1 with hardware
-	    data compression.  DDS-1 is the original DAT tape format.</para>
-
-	  <para>Native capacity is 2GB when using 90m tapes.  It cannot handle
-	    120m tapes.  This drive supports hardware data compression.
-	    Please refer to the section on <link
-	      linkend="hw-storage-hp1533a">HP C1533A</link> for the proper
-	    switch settings.</para>
-
-	  <para>Data transfer rate is 183kB/s.</para>
-
-	  <para>This drive is used in Hewlett-Packard's SureStore <ulink
-	      url="http://www.dmo.hp.com/tape/sst5000.htm">5000eU</ulink> and
-	    <ulink url="http://www.dmo.hp.com/tape/sst5000.htm">5000i</ulink>
-	    tape drives and C35480A DDS format DAT drive..</para>
-
-	  <para>This drive will occasionally hang during a tape eject
-	    operation (<command>mt offline</command>). Pressing the front
-	    panel button will eject the tape and bring the tape drive back to
-	    life.</para>
-
-	  <para>WARNING: HP 35480-03110 only.  On at least two occasions this
-	    tape drive when used with FreeBSD 2.1.0, an IBM Server 320 and an
-	    2940W SCSI controller resulted in all SCSI disk partitions being
-	    lost.  The problem has not be analyzed or resolved at this
-	    time.</para>
-	</sect3>
-
-	<sect3 id="hw-storage-sdt5000">
-	  <title><ulink
-	      url="http://www.sel.sony.com/SEL/ccpg/storage/tape/t5000.html">Sony SDT-5000</ulink></title>
-
-	  <para>There are at least two significantly different models: one is
-	    a DDS-1 and the other DDS-2.  The DDS-1 version is
-	    <literal>SDT-5000 3.02</literal>.  The DDS-2 version is
-	    <literal>SONY SDT-5000 327M</literal>. The DDS-2 version has a 1MB
-	    cache.  This cache is able to keep the tape streaming in almost
-	    any circumstances.</para>
-
-	  <para>The boot message identifier for this drive is <literal>SONY
-	      SDT-5000 3.02</literal> <literal>type 1 removable SCSI
-	      2</literal> <literal>Sequential-Access density code
-	      0x13</literal></para>
-
-	  <para>Native capacity is 4GB when using 120m tapes.  This drive
-	    supports hardware data compression.</para>
-
-	  <para>Data transfer rate is depends upon the model or the drive. The
-	    rate is 630kB/s for the <literal>SONY SDT-5000 327M</literal>
-	    while compressing the data.  For the <literal>SONY SDT-5000
-	      3.02</literal>, the data transfer rate is 225kB/s.</para>
-
-	  <para>In order to get this drive to stream, set the blocksize to 512
-	    bytes (<command>mt blocksize 512</command>) reported by Kenneth
-	    Merry <email>ken@ulc199.residence.gatech.edu</email>.</para>
-
-	  <para><literal>SONY SDT-5000 327M</literal> information reported by
-	    Charles Henrich <email>henrich@msu.edu</email>.</para>
-
-	  <para>Reported by: &a.jmz;</para>
-	</sect3>
-
-	<sect3 id="hw-storage-tandberg3600">
-	  <title>Tandberg TDC 3600</title>
-
-	  <para>The boot message identifier for this drive is
-	    <literal>TANDBERG TDC 3600 =08:</literal> <literal>type 1
-	      removable SCSI 2</literal></para>
-
-	  <para>This is a QIC tape drive.</para>
-
-	  <para>Native capacity is 150/250MB.</para>
-
-	  <para>This drive has quirks which are known and work around code is
-	    present in the SCSI tape device driver (&man.st.4;).
-	    Upgrading the firmware to XXX version will fix the quirks and
-	    provide SCSI 2 capabilities.</para>
-
-	  <para>Data transfer rate is 80kB/s.</para>
-
-	  <para>IBM and Emerald units will not work.  Replacing the firmware
-	    EPROM of these units will solve the problem.</para>
-
-	  <para>Reported by: &a.msmith;</para>
-	</sect3>
-
-	<sect3 id="hw-storage-tandberg3620">
-	  <title>Tandberg TDC 3620</title>
-
-	  <para>This is very similar to the <link
-	      linkend="hw-storage-tandberg3600">Tandberg TDC 3600</link>
-	    drive.</para>
-
-	  <para>Reported by: &a.joerg;</para>
-	</sect3>
-
-	<sect3 id="hw-storage-tandberg3800">
-	  <title>Tandberg TDC 3800</title>
-
-	  <para>The boot message identifier for this drive is
-	    <literal>TANDBERG TDC 3800 =04Y</literal> <literal>Removable
-	      Sequential Access SCSI-2 device</literal></para>
-
-	  <para>This is a QIC tape drive.</para>
-
-	  <para>Native capacity is 525MB.</para>
-
-	  <para>Reported by: &a.jhs;</para>
-	</sect3>
-
-	<sect3 id="hw-storage-tandberg4222">
-	  <title>Tandberg TDC 4222</title>
-
-	  <para>The boot message identifier for this drive is
-	    <literal>TANDBERG TDC 4222 =07</literal> <literal>type 1 removable
-	      SCSI 2</literal></para>
-
-	  <para>This is a QIC tape drive.</para>
-
-	  <para>Native capacity is 2.5GB.  The drive will read all cartridges
-	    from the 60 MB (DC600A) upwards, and write 150 MB (DC6150)
-	    upwards.  Hardware compression is optionally supported for the 2.5
-	    GB cartridges.</para>
-
-	  <para>This drives quirks are known and pre-compiled into the SCSI
-	    tape device driver (&man.st.4;) beginning with FreeBSD
-	    2.2-CURRENT.  For previous versions of FreeBSD, use
-	    <command>mt</command> to read one block from the tape, rewind the
-	    tape, and then execute the backup program (<command>mt fsr 1; mt
-	      rewind; dump ...</command>)</para>
-
-	  <para>Data transfer rate is 600kB/s (vendor claim with compression),
-	    350 KB/s can even be reached in start/stop mode. The rate
-	    decreases for smaller cartridges.</para>
-
-	  <para>Reported by: &a.joerg;</para>
-	</sect3>
-
-	<sect3 id="hw-storage-wangtek5525es">
-	  <title>Wangtek 5525ES</title>
-
-	  <para>The boot message identifier for this drive is <literal>WANGTEK
-	      5525ES SCSI REV7 3R1</literal> <literal>type 1 removable SCSI
-	      1</literal> <literal>density code 0x11, 1024-byte
-	      blocks</literal></para>
-
-	  <para>This is a QIC tape drive.</para>
-
-	  <para>Native capacity is 525MB.</para>
-
-	  <para>Data transfer rate is 180kB/s.</para>
-
-	  <para>The drive reads 60, 120, 150, and 525MB tapes.  The drive will
-	    not write 60MB (DC600 cartridge) tapes.  In order to overwrite 120
-	    and 150 tapes reliably, first erase (<command>mt erase</command>)
-	    the tape.  120 and 150 tapes used a wider track (fewer tracks per
-	    tape) than 525MB tapes. The <quote>extra</quote> width of the
-	    previous tracks is not overwritten, as a result the new data lies
-	    in a band surrounded on both sides by the previous data unless the
-	    tape have been erased.</para>
-
-	  <para>This drives quirks are known and pre-compiled into the SCSI
-	    tape device driver (&man.st.4;).</para>
-
-	  <para>Other firmware revisions that are known to work are:
-	    M75D</para>
-
-	  <para>Reported by: Marc van Kempen <email>marc@bowtie.nl</email>
-	    <literal>REV73R1</literal> Andrew Gordon
-	    <email>Andrew.Gordon@net-tel.co.uk</email>
-	    <literal>M75D</literal></para>
-	</sect3>
-
-	<sect3 id="hw-storage-wangtek6200">
-	  <title>Wangtek 6200</title>
-
-	  <para>The boot message identifier for this drive is <literal>WANGTEK
-	      6200-HS 4B18</literal> <literal>type 1 removable SCSI
-	      2</literal> <literal>Sequential-Access density code
-	      0x13</literal></para>
-
-	  <para>This is a DDS-1 tape drive.</para>
-
-	  <para>Native capacity is 2GB using 90m tapes.</para>
-
-	  <para>Data transfer rate is 150kB/s.</para>
-
-	  <para>Reported by: Tony Kimball <email>alk@Think.COM</email></para>
-	</sect3>
-      </sect2>
-
-      <sect2>
-	<title>* Problem drives</title>
-
-	<para></para>
-      </sect2>
-    </sect1>
-
-    <sect1>
-      <title>CDROM drives</title>
-
-      <para><emphasis>Contributed by &a.obrien;.  23 November
-	      1997.</emphasis></para>
-
-      <para>Generally speaking those in <emphasis>The FreeBSD
-	Project</emphasis> prefer SCSI CDROM drives over IDE CDROM
-	drives.  However not all SCSI CDROM drives are equal.  Some
-	feel the quality of some SCSI CDROM drives have been
-	deteriorating to that of IDE CDROM drives.  Toshiba used to be
-	the favored stand-by, but many on the SCSI mailing list have
-	found displeasure with the 12x speed XM-5701TA as its volume
-	(when playing audio CDROMs) is not controllable by the various
-	audio player software.</para>
-
-      <para>Another area where SCSI CDROM manufacturers are cutting corners is
-	adherence to the <link linkend="scsi-further-reading">SCSI
-	  specification</link>. Many SCSI CDROMs will respond to <link
-	  linkend="scsi-rogue-devices">multiple LUNs</link> for its target
-	address.  Known violators include the 6x Teac CD-56S 1.0D.</para>
-  </sect1>
-
-</article>
diff --git a/en_US.ISO8859-1/articles/version-guide/Makefile b/en_US.ISO8859-1/articles/version-guide/Makefile
deleted file mode 100644
index e9b3852f11..0000000000
--- a/en_US.ISO8859-1/articles/version-guide/Makefile
+++ /dev/null
@@ -1,19 +0,0 @@
-#
-# $FreeBSD$
-#
-# Article: FreeBSD Version Guide
-
-DOC?= article
-
-FORMATS?= html
-WITH_ARTICLE_TOC?= YES
-
-INSTALL_COMPRESSED?= gz
-INSTALL_ONLY_COMPRESSED?=
-
-SRCS=		article.sgml
-
-URL_RELPREFIX?=	../../../..
-DOC_PREFIX?= ${.CURDIR}/../../..
-
-.include "${DOC_PREFIX}/share/mk/doc.project.mk"
diff --git a/en_US.ISO8859-1/articles/version-guide/article.sgml b/en_US.ISO8859-1/articles/version-guide/article.sgml
deleted file mode 100644
index 2de0f3da73..0000000000
--- a/en_US.ISO8859-1/articles/version-guide/article.sgml
+++ /dev/null
@@ -1,398 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1" standalone="no"?>
-<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V4.2-Based Extension//EN"
-	"../../../share/sgml/freebsd42.dtd" [
-<!ENTITY % entities PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Entity Set//EN" "../../share/sgml/entities.ent">
-%entities;
-<!ENTITY % freebsd.urls.absolute "INCLUDE">
-]>
-
-<article lang='en'>
-  <title>Choosing the FreeBSD Version That Is Right For You</title>
-
-  <articleinfo>
-    <authorgroup>
-      <author>
-	<surname>The FreeBSD Documentation Project</surname>
-      </author>
-    </authorgroup>
-
-    <legalnotice id="trademarks" role="trademarks">
-      &tm-attrib.freebsd;
-    </legalnotice>
-
-    <copyright>
-      <year>2005</year>
-      <holder>The FreeBSD Documentation Project</holder>
-    </copyright>
-
-    <pubdate>$FreeBSD$</pubdate>
-
-    <releaseinfo>$FreeBSD$</releaseinfo>
-
-    <abstract>
-      <para>So you have chosen to install &os;.  Welcome!  This
-	document is designed to help you to decide which version to
-	install.</para>
-    </abstract>
-  </articleinfo>
-
-  <sect1 id="background">
-    <title>Background</title>
-
-    <para>To decide which version of &os; is the best for your needs,
-      it is important to understand a few concepts about our development
-      and Release Engineering (<literal>RE</literal>) processes.</para>
-
-    <para>&os; is developed by a large group of individuals who are
-      almost entirely volunteers.  The source code to the kernel and
-      the most common libraries and utilities is maintained in a
-      <firstterm>source control system</firstterm> and available for
-      the general public to download at any time.  Separately, compiled
-      versions (<literal>binaries</literal>) are made available on a
-      recurring basis.  Some of these binary versions undergo an
-      extensive testing process and are then termed a
-      <firstterm>release</firstterm>.</para>
-
-    <sect2 id="releases">
-      <title>Releases</title>
-
-      <para><literal>Releases</literal> are named with a <firstterm>major
-	version number</firstterm> and <firstterm>minor version
-	number</firstterm>.</para>
-
-      <itemizedlist>
-	<listitem>
-	  <para>The goal of a major release is to introduce a set of new
-	    features.  Inevitably, as new features are added to &os;, or as
-	    older features are no longer useful or are dropped, it is
-	    sometimes necessary to break compatibility with previous major
-	    releases.</para>
-	</listitem>
-
-	<listitem>
-	  <para>The goal of a minor release is primarily to fix bugs and
-	    improve performance and stability.  Keeping both source-level and binary compatibility
-	    from one minor release to another is a priority.  On occasion,
-	    new features may be added to a minor release when it is
-	    believed that these other goals will not be compromised.</para>
-	</listitem>
-      </itemizedlist>
-
-      <para>However, keep in mind that a <quote>release version</quote>
-	is merely a snapshot of the source tree at a particular point in
-	time which is given a particular name (or <emphasis>tag</emphasis>).
-	(For instance, the tag that Release Engineering assigned for the
-	5.4 release was <literal>RELENG_5_4_0_RELEASE</literal>.) Development
-	always continues on what is known as the <literal>HEAD</literal>
-	tag.</para>
-    </sect2>
-
-    <sect2 id="branches">
-      <title>Branches</title>
-
-      <para>At the time of each release, a <firstterm>branch</firstterm>
-	is created, such as <literal>RELENG_5_4</literal>.  Although
-	the source files named by <literal>RELENG_5_4_0_RELEASE</literal>
-	will never change, those on <literal>RELENG_5_4</literal> can,
-	by the adoption of changes from <literal>HEAD</literal> such
-	as fixes for security and other bugs.</para>
-
-      <para>During the life of each major release, another tag is
-	created such as <literal>RELENG_5</literal>.  In addition
-	to security and other bug fixes, other new changes can be
-	brought in from <literal>HEAD</literal> so as to constitute
-	the changes for the next minor release in the sequence.</para>
-    </sect2>
-
-    <sect2 id="stable-vs-current">
-      <title><firstterm>STABLE</firstterm> versus
-	<firstterm>CURRENT</firstterm></title>
-
-      <para>During the lifetime of each major release, an individual
-	branch may also be termed <literal>STABLE</literal>.  This
-	indicates that the &os; Project believes that the branch is
-	of sufficiently proven quality to be used by a wide range of
-	users.  Branches that need further testing before being widely
-	adopted are named <literal>CURRENT</literal>.</para>
-
-      <note><para>The &os; Project cannot in and of itself guarantee
-	that the software that it ships is <emphasis>stable</emphasis>
-	enough for any given installation.  Only each individual user
-	can make that decision.  Please keep in mind that the Project
-	is primarily composed of volunteers and is not able to offer
-	any kind of warranty of fitness.</para></note>
-    </sect2>
-
-    <sect2 id="ports-vs-packages">
-      <title><firstterm>Ports</firstterm> versus
-	<firstterm>Packages</firstterm></title>
-
-      <para>Separately from the files distributed above, &os;
-	supports thousands of applications that are developed by third
-	parties outside of the project itself.  (Examples include
-	windowing systems, Internet browsers, email programs, office
-	suites, and so forth.)  In general, the project itself does
-	not develop this software, only the framework to allow these
-	programs to be installed (termed the <firstterm>Ports
-	Collection</firstterm>).  Applications may be installed
-	either from source, if its licensing terms allow such
-	redistribution (these are called <emphasis>ports</emphasis>),
-	or as compiled binaries if allowed (these are called
-	<emphasis>packages</emphasis>).</para>
-    </sect2>
-  </sect1>
-
-  <sect1 id="past-schedules">
-    <title>Release Scheduling In The Past</title>
-
-    <para>During the development and release of &os; 5.X, many lessons
-      were learned which only became clear in retrospect.  The goals
-      of the 5.X series were very aggressive, and included:</para>
-
-    <itemizedlist>
-      <listitem>
-	<para>To provide support for Symmetric MultiProcessing (SMP)
-	  machines;</para>
-      </listitem>
-
-      <listitem>
-	<para>To increase performance by adopting a new strategy
-	  for dealing with resource contention in the kernel;</para>
-      </listitem>
-
-      <listitem>
-	<para>To add several new processor architectures;</para>
-      </listitem>
-
-      <listitem>
-	<para>To introduce a new threading model;</para>
-      </listitem>
-
-      <listitem>
-	<para>To introduce a new scheduler;</para>
-      </listitem>
-
-      <listitem>
-	<para>To add support for new technologies such as power
-	  management (especially important for laptops); and,
-	  most critically,</para>
-      </listitem>
-
-      <listitem>
-	<para>Not to declare the release series as <literal>STABLE</literal>
-	  until all these tasks were finished.</para>
-      </listitem>
-    </itemizedlist>
-
-    <para>This led to a situation where it was several years between
-      the time that a release in the 4.X series was declared
-      <literal>STABLE</literal> and that a release in the 5.X series
-      was declared <literal>STABLE</literal>.  This had several
-      undesirable effects:</para>
-
-    <itemizedlist>
-      <listitem>
-	<para>The number of simultaneous feature-set changes made it
-	  very difficult to isolate one set of changes for merging
-	  back into the <literal>STABLE</literal> branch;</para>
-      </listitem>
-
-      <listitem>
-	<para>which meant that users who absolutely had to have certain
-	  new features (for instance, to be able to run on modern hardware)
-	  wound up adopting (for instance) &os; 5.2.1 even though it was
-	  advertised as a developer-only release, and regardless of the
-	  fact that a <literal>CURRENT</literal> release was not really
-	  suitable for their needs.</para>
-      </listitem>
-
-      <listitem>
-	<para>In the cases where backmerges were made, this put the
-	  developers in a position of trying to support features on a
-	  version that they themselves were not using as their primary
-	  development platform.</para>
-      </listitem>
-
-      <listitem>
-	<para>The time lag also meant that when 5.3 was finally declared
-	  as the latest <literal>STABLE</literal> release, the accumulated
-	  weight of changes made the upgrading process very painful.</para>
-      </listitem>
-    </itemizedlist>
-
-    <para>To put it bluntly, no one was satisfied with this result.</para>
-
-    <para>The lessons that were learned are:</para>
-
-    <itemizedlist>
-      <listitem>
-	<para>New major releases must have a smaller number of
-	  feature-set changes and be released more often.</para>
-      </listitem>
-
-      <listitem>
-	<para>To the maximum extent possible, feature-set changes
-	  should be isolated from each other.  (This implies that
-	  some development must take place outside of the main
-	  tree and only be merged in when it will not destabilize
-	  other simultaneous development.)</para>
-      </listitem>
-
-      <listitem>
-	<para>Major releases should be targeted at a time
-	  deadline rather than a feature-set deadline.  If some
-	  feature is not ready in time, then it should be disabled
-	  by default and left for the next major release.</para>
-      </listitem>
-    </itemizedlist>
-
-    <para>By releasing smaller sets of changes more often, it is
-      also hoped that less time will be spent trying to merge features
-      from <literal>HEAD</literal> back into the latest
-      <literal>STABLE</literal> version (and thus trying to support
-      those features in more than one major version); and further, that
-      as the changes are more isolated, that the risk of introducing
-      more bugs by doing so is much less.</para>
-
-    <para>Also, by focusing on a time deadline rather than a
-      feature set, it should finally be possible for users, developers
-      of external applications, and the &os; developers themselves to
-      be able to better plan for the future.</para>
-  </sect1>
-
-  <sect1 id="future-goals">
-    <title>Release Scheduling Goals Going Forward</title>
-
-    <para>Here are the current scheduling goals for the Project:</para>
-
-    <itemizedlist>
-      <listitem>
-	<para>To release a new major release every 18 months;</para>
-      </listitem>
-
-      <listitem>
-	<para>To release a new minor release every 4 months;</para>
-      </listitem>
-
-      <listitem>
-	<para>To provide prebuilt packages for the most recent minor
-	  release of each major version;</para>
-      </listitem>
-
-      <listitem>
-	<para>To provide security updates and other critical bug fixes
-	  for the last several minor versions of each major version
-	  (termed <firstterm>security branches</firstterm>).</para>
-      </listitem>
-    </itemizedlist>
-
-    <para>Due to the large number of possible combinations of installable
-      versions, it is not possible to support every version
-      indefinitely; this is due somewhat to the availability of machine
-      resources but primarily due to the amount of volunteer effort
-      that is available.</para>
-
-    <para>Interested readers should also see:</para>
-
-    <variablelist>
-      <varlistentry>
-        <term><ulink url="&url.base;/releng/index.html#schedule"></ulink></term>
-        <listitem>
-	  <para>The Release Engineering Schedule</para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-	<term><ulink url="&url.base;/security/security.html#supported-branches"></ulink></term>
-	<listitem>
-	  <para>The Security Branch Schedule</para>
-	</listitem>
-      </varlistentry>
-    </variablelist>
-
-    <para>These documents go into much greater depth about the background and
-      rationale behind the decisions regarding the supported branches and the
-      lifetime of each branch.</para>
-  </sect1>
-
-  <sect1 id="decision-points">
-    <title>How Do These Factors Affect My Decision?</title>
-
-    <para>The major factors that should affect your decision as to
-      which version to install include:</para>
-
-    <itemizedlist>
-      <listitem>
-	<para>What degree of stability does your installation need?</para>
-      </listitem>
-
-      <listitem>
-	<para>How much effort do you wish to devote to upgrading?</para>
-      </listitem>
-
-      <listitem>
-	<para>How long do you intend to stay on a particular version
-	  between upgrades?</para>
-      </listitem>
-
-      <listitem>
-	<para>How important is security to your installation?</para>
-      </listitem>
-
-      <listitem>
-	<para>Will you be installing from source, or from binaries?</para>
-      </listitem>
-
-      <listitem>
-	<para>Are you willing to help participate in the &os; development
-	  process?</para>
-      </listitem>
-    </itemizedlist>
-
-    <para>Here are some rough guidelines to help you in your decision:</para>
-
-    <itemizedlist>
-      <listitem>
-	<para>If you have a short-term need, would benefit from the highest degree of
-	  stability currently available, and are not able to devote many
-	  resources to upgrading, then you will probably want to install
-	  the latest <literal>STABLE</literal> minor release and remain
-	  with that.  Depending on your security needs, you may or may not
-	  wish to track changes to that branch as they are released.</para>
-      </listitem>
-
-      <listitem>
-	<para>If you have a short-term need, and feature completeness or
-	  the best levels of security are most important to you, and you
-	  are willing to spend time upgrading, you may wish to track the
-	  latest <literal>STABLE</literal> branch.</para>
-      </listitem>
-
-      <listitem>
-	<para>If you are not immediately planning on going into
-	  production, you are willing to work through a certain number
-	  of problems, and a new major release is upcoming within the
-	  next few months, you may wish to investigate installing that
-	  branch to help the project to test it and stabilize it
-	  to make it the best release possible in the medium to long
-	  term.</para>
-      </listitem>
-
-      <listitem>
-	<para>Only if you are willing to install from source, and spend
-	  time debugging problems with the base system and follow up
-	  with problem reports, and track the mailing list that deals
-	  with such issues, should you consider tracking
-	  <literal>HEAD</literal>.</para>
-      </listitem>
-    </itemizedlist>
-  </sect1>
-
-  <sect1 id="conclusion">
-    <title>Conclusion</title>
-
-    <para>We hope that this article serves as a useful starting point
-      for understanding the &os; development model and deciding what version
-      is right for your needs.</para>
-  </sect1>
-</article>
diff --git a/en_US.ISO8859-1/articles/vinum/Makefile b/en_US.ISO8859-1/articles/vinum/Makefile
deleted file mode 100644
index 27dbbd7c65..0000000000
--- a/en_US.ISO8859-1/articles/vinum/Makefile
+++ /dev/null
@@ -1,20 +0,0 @@
-#
-# $FreeBSD$
-#
-# Article: Bootstrapping Vinum
-
-DOC?= article
-
-FORMATS?= html
-WITH_ARTICLE_TOC?= YES
-
-INSTALL_COMPRESSED?=gz
-INSTALL_ONLY_COMPRESSED?=
-
-SRCS=		article.sgml
-IMAGES_EN=	ad0b4aft.eps
-IMAGES_EN+=	ad2b4aft.eps
-IMAGES_EN+=	arch.eps
-
-DOC_PREFIX?= ${.CURDIR}/../../..
-.include "${DOC_PREFIX}/share/mk/doc.project.mk"
diff --git a/en_US.ISO8859-1/articles/vinum/article.sgml b/en_US.ISO8859-1/articles/vinum/article.sgml
deleted file mode 100644
index 5d70c77e4e..0000000000
--- a/en_US.ISO8859-1/articles/vinum/article.sgml
+++ /dev/null
@@ -1,2550 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1" standalone="no"?>
-<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V4.2-Based Extension//EN"
-	"../../../share/sgml/freebsd42.dtd" [
-<!ENTITY % entities PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Entity Set//EN" "../../share/sgml/entities.ent">
-%entities;
-<!ENTITY vinum.ap "<application>Vinum</application>">
-]>
-
-<!-- $FreeBSD$ -->
-<!-- FreeBSD Documentation Project -->
-
-<article lang='en'>
-  <articleinfo>
-    <title>
-      Bootstrapping Vinum: A Foundation for Reliable Servers
-    </title>
-    <author>
-      <firstname>Robert A.</firstname>
-      <surname>Van Valzah</surname>
-    </author>
-    <copyright>
-      <year>2001</year>
-      <holder>Robert A. Van Valzah</holder>
-    </copyright>
-
-    <pubdate>$FreeBSD$</pubdate>
-
-    <releaseinfo>$FreeBSD$</releaseinfo>
-    <legalnotice id="trademarks" role="trademarks">
-      &tm-attrib.freebsd;
-      &tm-attrib.general;
-    </legalnotice>
-  </articleinfo>
-
-  <abstract>
-    <para> In the most abstract sense, these instructions show how
-      to build a pair of disk drives where either one is adequate
-      to keep your server running if the other fails.
-      Life is better if they are both working, but your server will never die
-      unless both disk drives die at once.
-      If you choose ATAPI drives and use a fairly generic kernel, you can
-      be confident that either of these drives can be plugged into most any
-      main board to produce a working server in a pinch.
-      The drives need not be identical.
-      These techniques work equally well with SCSI drives as they do with ATAPI,
-      but I will focus on ATAPI here because main boards with this interface are
-      ubiquitous.
-      After building the foundation of a reliable server as shown here, you
-      can expand to as many disk drives as necessary to build the
-      failure-resilient server of your dreams.</para>
-  </abstract>
-
-  <section id="Introduction">
-    <title>Introduction</title>
-
-    <para>Any machine that is going to provide reliable service needs
-      to have either redundant components on-line or a pool of
-      off-line spares that can be promptly swapped in.  Commodity
-      PC hardware makes it affordable for even small organizations
-      to have some spare parts available that could be pressed
-      into service following the failure of production equipment.
-      In many organizations, a failed power supply, NIC, memory,
-      or main board could easily be swapped with a standby in a
-      matter of minutes and be ready to return to production work.</para>
-
-    <para>If a disk drive fails, however, it often has to be restored
-      from a tape backup.  This may take many hours.  With disk
-      drive capacities rising faster than tape drive capacities,
-      the time needed to restore a failed disk drive seems to
-      increase as technology progresses.</para>
-
-    <para>&vinum.ap;
-      is a volume manager for FreeBSD that provides a standard block
-      I/O layer interface to the filesystem code just as any hardware
-      device driver would.
-      It works by managing partitions
-      of type <literal>vinum</literal> and
-      allows you to subdivide and group the space in such
-      partitions into logical devices called
-      <firstterm>volumes</firstterm> that
-      can be used in the same way as disk partitions.
-      Volumes can
-      be configured for resilience, performance, or both.  Experienced
-      system administrators will immediately recognize the benefits
-      of being able to configure each filesystem to match the way
-      it is most often used.</para>
-
-    <para>In some ways, <application>Vinum</application> is similar to
-      &man.ccd.4;, but it is far more flexible and robust in the face
-      of failures.
-      It is only slightly more difficult to set up than &man.ccd.4;.
-      &man.ccd.4; may meet your needs if you are only interested in
-      concatenation.</para>
-
-    <section id="Terminology">
-      <title>Terminology</title>
-
-      <para>Discussion of storage management can get very tricky
-	simply because of the terminology involved.
-	As we will see below,
-	the terms <firstterm>disk</firstterm>,
-	<firstterm>slice</firstterm>, <firstterm>partition</firstterm>,
-	<firstterm>subdisk</firstterm>, and <firstterm>volume</firstterm>
-	each refer to different things that present the same interface
-	to a kernel function like swapping.
-	The potential for confusion is compounded because the objects
-	that these terms represent can be nested inside each other.</para>
-
-      <para>I will refer to a physical disk drive as a
-	<firstterm>spindle</firstterm>.
-	A <firstterm>partition</firstterm> here means a BSD partition as
-	maintained by <command>disklabel</command>.
-	It does not refer to <firstterm>slices</firstterm> or
-	<firstterm>BIOS partitions</firstterm> as
-	maintained by <command>fdisk</command>.</para>
-    </section>
-
-    <section id="Objects">
-      <title>Vinum Objects</title>
-
-      <para><application>Vinum</application>
-	defines a hierarchy of four objects that it uses to manage storage
-	(see <xref linkend="arch"/>).
-	Different combinations of these objects are used to achieve
-	failure resilience, performance, and/or extra capacity.
-	I will give a whirlwind tour of the objects here--see the
-	<ulink url="http://www.vinumvm.org/">Vinum web site</ulink>
-	for a more thorough description.</para>
-
-      <figure id="arch">
-	<title>Vinum Objects and Architecture</title>
-
-	<mediaobject>
-	  <imageobject>
-	    <imagedata fileref="arch" format="EPS"/>
-	  </imageobject>
-
-	  <textobject>
-	    <literallayout class="monospaced">+-----+------+------+
-| UFS | swap | Etc. |
-+---+-+------+----+ +
-|       volume    | |
-+ V +-------------+ +
-| i      plex     | |
-+ n +-------------+ +
-| u     subdisk   | |
-+ m +-------------+ +
-|        drive    | |
-+-----------------+ +
-| Block I/O devices |
-+-------------------+</literallayout>
-	  </textobject>
-
-	  <textobject>
-	    <phrase>Vinum Objects and Architecture</phrase>
-	  </textobject>
-	</mediaobject>
-      </figure>
-
-      <para>The top object, a vinum <firstterm>volume</firstterm>,
-	implements a virtual disk that
-	provides a standard block I/O layer
-	interface to other parts of the kernel.
-	The bottom object, a vinum <firstterm>drive</firstterm>,
-	uses this same interface to
-	request I/O from physical devices below it.</para>
-
-      <para>In between these two (from top to bottom) we have objects called
-	a vinum <firstterm>plex</firstterm>
-	and a vinum <firstterm>subdisk</firstterm>.
-	As you can probably guess from the name, a vinum subdisk is a
-	contiguous subset of the space available on a vinum drive.
-	It lets you subdivide a vinum drive in much the same way that
-	a disk BSD partition lets you subdivide a BIOS slice.</para>
-
-      <para>A plex allows subdisks to be grouped together making the space
-	of all subdisks available as a single object.</para>
-
-      <para>A plex can be organized with its constituent subdisks concatenated
-	or striped.
-	Both organizations are useful for spreading I/O requests across
-	spindles since plexes reside on distinct spindles.
-	A striped plex will switch spindles each time a multiple of the
-	stripe size is reached.
-	A concatenated plex will switch spindles only when the end of
-	a subdisk is reached.</para>
-
-      <para>An important characteristic of a
-	<application>Vinum</application> volume is that it can be
-	made up of more than one plex.
-	In this case, writes go to all plexes and a read may be satisfied
-	by any plex.
-	Configuring two or more plexes on distinct spindles yields a
-	volume that is resilient to failure.</para>
-
-      <para><application>Vinum</application> maintains a
-	<firstterm>configuration</firstterm>
-	that defines instances of the above objects and the way they
-	are related to each other.
-	This configuration is automatically written to all spindles under
-	<application>Vinum</application> management whenever it changes.</para>
-    </section>
-
-    <section id="Organizations">
-      <title>Vinum Volume/Plex Organization</title>
-
-      <para>Although <application>Vinum</application>
-	can manage any number of spindles,
-	I will only cover scenarios with two spindles here
-	for simplification.
-	See <xref linkend="OrgCompare"/> to see how
-	two spindles organized with <application>Vinum</application>
-	compare to two spindles without <application>Vinum</application>.</para>
-
-      <para>
-	<table id="OrgCompare" frame="all">
-	  <title>Characteristics of Two Spindles Organized with Vinum</title>
-
-	  <tgroup cols="5">
-	    <thead>
-	      <row>
-		<entry>Organization</entry>
-		<entry>Total Capacity</entry>
-		<entry>Failure Resilient</entry>
-		<entry>Peak Read Performance</entry>
-		<entry>Peak Write Performance</entry>
-	      </row>
-	    </thead>
-	    <tbody>
-	      <row>
-		<entry>Concatenated Plexes</entry>
-		<entry>Unchanged, but appears as a single drive</entry>
-		<entry>No</entry>
-		<entry>Unchanged</entry>
-		<entry>Unchanged</entry>
-	      </row>
-	      <row>
-		<entry>Striped Plexes (RAID-0)</entry>
-		<entry>Unchanged, but appears as a single drive</entry>
-		<entry>No</entry>
-		<entry>2x</entry>
-		<entry>2x</entry>
-	      </row>
-	      <row>
-		<entry>Mirrored Volumes (RAID-1)</entry>
-		<entry>1/2, appearing as a single drive</entry>
-		<entry>Yes</entry>
-		<entry>2x</entry>
-		<entry>Unchanged</entry>
-	      </row>
-	    </tbody>
-	  </tgroup>
-	</table>
-      </para>
-
-      <para><xref linkend="OrgCompare"/> shows that striping yields
-	the same capacity and lack of failure resilience
-	as concatenation, but it has better peak read and write performance.
-	Hence we will not be using concatenation in any of the examples here.
-	Mirrored volumes provide the benefits of improved peak read performance
-	and failure resilience--but this comes at a loss in capacity.</para>
-
-      <note><para>Both concatenation and striping bring their benefits over a
-	single spindle at the cost of increased likelihood of failure since
-	more than one spindle is now involved.</para></note>
-
-      <para>When three or more spindles are present,
-	<application>Vinum</application> also supports rotated,
-	block-interleaved parity (also called <firstterm>RAID-5</firstterm>)
-	that provides better
-	capacity than mirroring (but not quite as good as striping), better
-	read performance than both mirroring and striping,
-	and good failure resilience.
-	There is, however,
-	a substantial decrease in write performance with RAID-5.
-	Most of the benefits become more pronounced with five or more
-	spindles.</para>
-
-      <para>The organizations described above may be combined to provide
-	benefits that no single organization can match.
-	For example, mirroring and striping can be combined to provide
-	failure-resilience with very fast read performance.</para>
-
-    </section>
-
-    <section id="History">
-      <title>Vinum History</title>
-
-      <para><application>Vinum</application>
-	is a standard part of even a "minimum" FreeBSD distribution and
-	it has been standard since 3.0-RELEASE.
-	The official pronunciation of the name is
-	<emphasis>VEE-noom</emphasis>.</para>
-
-      <para>&vinum.ap; was inspired by the Veritas Volume Manager, but
-	was not derived from it.
-	The name is a play on that history and the Latin adage
-	<foreignphrase>In Vino Veritas</foreignphrase>
-	(<foreignphrase>Vino</foreignphrase> is the ablative form of
-	<foreignphrase>Vinum</foreignphrase>).
-	Literally translated, that is <quote>Truth lies in wine</quote> hinting that
-	drunkards have a hard time lying.
-	</para>
-
-      <para>I have been using it in production on six different servers for
-	over two years with no data loss.
-	Like the rest of FreeBSD, <application>Vinum</application>
-	provides <quote>rock-stable performance.</quote>
-	(On a personal note, I have seen <application>Vinum</application>
-	panic when I misconfigured something, but I have
-	never had any trouble in normal operation.)
-	Greg Lehey wrote
-	<application>Vinum</application> for FreeBSD,
-	but he is seeking
-	help in porting it to NetBSD and OpenBSD.</para>
-
-      <warning>
-	<para>Just like the rest of FreeBSD, <application>Vinum</application>
-	  is undergoing continuous
-	  development.
-	  Several subtle, but significant bugs have been fixed in recent
-	  releases.
-	  It is always best to use the most recent code base that meets your
-	  stability requirements.</para></warning>
-
-    </section>
-
-    <section id="Strategy">
-      <title>Vinum Deployment Strategy</title>
-
-      <para><application>Vinum</application>,
-	coupled with prudent partition management, lets you
-	keep <quote>warm-spare</quote> spindles on-line so that failures
-	are transparent to users.  Failed spindles can be replaced
-	during regular maintenance periods or whenever it is convenient.
-	When all spindles are working, the server benefits from increased
-	performance and capacity.</para>
-
-      <para>Having redundant copies of your home directory does not
-	help you if the spindle holding root,
-	<filename>/usr</filename>, or swap fails on your server.
-	Hence I focus here on building a simple
-	foundation for a failure-resilient server covering the root,
-	<filename>/usr</filename>,
-	<filename>/home</filename>, and swap partitions.</para>
-
-      <warning>
-	<para><application>Vinum</application>
-	  mirroring does not remove the need for making backups!
-	  Mirroring cannot help you recover from site disasters
-	  or the dreaded
-	  <command>rm -r -f /</command> command.</para></warning>
-    </section>
-
-    <section id="WhyBootstrap">
-      <title>Why Bootstrap Vinum?</title>
-
-      <para>It is possible to add <application>Vinum</application>
-	to a server configuration after
-	it is already in production use, but this is much harder than
-	designing for it from the start.  Ironically,
-	<application>Vinum</application> is not supported by
-	<command>/stand/sysinstall</command>
-	and hence you cannot install
-	<filename>/usr</filename> right onto a
-	<application>Vinum</application> volume.</para>
-
-      <note><para><application>Vinum</application> currently does not
-	support the root filesystem (this feature
-	is in development).</para></note>
-
-      <para>Hence it is a bit
-	tricky to get started using
-	<application>Vinum</application>, but these instructions
-	take you though the process of planning for
-	<application>Vinum</application>, installing FreeBSD
-	without it, and then beginning to use it.</para>
-
-      <para>I have come to call this whole process <quote>bootstrapping Vinum.</quote>
-	That is, the process of getting <application>Vinum</application>
-	initially installed
-	and operating to the point where you have met your resilience
-	or performance goals.  My purpose here is to document a
-	<application>Vinum</application>
-	bootstrapping method that I have found that works well for me.</para>
-    </section>
-
-    <section id="Benefits">
-      <title>Vinum Benefits</title>
-
-      <para>The server foundation scenario I have chosen here allows me
-	to show you examples of configuring for resilience on
-	<filename>/usr</filename> and
-	<filename>/home</filename>.
-	Yet <application>Vinum</application>
-	provides benefits other than resilience--namely
-	performance, capacity, and manageability.
-	It can significantly improve disk performance (especially
-	under multi-user loads).
-	<application>Vinum</application>
-	can easily concatenate many smaller disks to produce the
-	illusion of a single larger disk (but my server foundation
-	scenario does not allow me to illustrate these benefits here).</para>
-
-      <para>For servers with many spindles, <application>Vinum</application>
-	provides substantial
-	benefits in volume management, particularly when coupled with
-	hot-pluggable hardware.  Data can be moved from spindle to
-	spindle while the system is running without loss of production
-	time.  Again, details of this will not be given here, but once
-	you get your feet wet with <application>Vinum</application>,
-	other documentation will help you do things like this.
-	See
-	"<ulink url="http://www.vinumvm.org/vinum/vinum.ps">The Vinum
-	Volume Manager</ulink>" for a technical introduction to
-	<application>Vinum</application>,
-	&man.vinum.8; for a description of the <command>vinum</command>
-	command, and
-	&man.vinum.4;
-	for a description of the vinum device
-	driver and the way <application>Vinum</application>
-	objects are named.</para>
-
-      <note>
-	<para>Breaking up your disk space into smaller and smaller partitions
-	  has the benefit of allowing you to <quote>tune</quote> for the most common
-	  type of access and tends to keep disk hogs <quote>within their pens.</quote>
-	  However it also causes some loss in total available disk space
-	  due to fragmentation.</para></note>
-    </section>
-
-    <section id="DegradedOperation">
-      <title>Server Operation in Degraded Mode</title>
-
-      <para>Some disk failures in this two-spindle scenario will result in
-	<application>Vinum</application>
-	automatically routing
-	all disk I/O to the remaining good spindle.
-	Others will require brief manual intervention on the console
-	to configure the server for degraded mode operation and a quick reboot.
-	Other than actual hardware repairs, most recovery work
-	can be done while the server is running in multi-user degraded
-	mode so there is as little production impact
-	from failures as possible.</para>
-
-      <para>I give the instructions in <xref linkend="Failures"/> needed to
-	configure the server for degraded mode operation
-	in those cases where <application>Vinum</application>
-	cannot do it automatically.
-	I also give the instructions needed to
-	return to normal operation once the failed hardware is repaired.
-	You might call these instructions <application>Vinum</application>
-	failure recovery techniques.</para>
-
-      <para>I recommend practicing using these instructions
-	by recovering from simulated failures.
-	For each failure scenario, I also give tips below for simulating
-	a failure even when your hardware is working well.
-	Even a minimum <application>Vinum</application>
-	system as described in
-	<xref linkend="HW"/>
-	below can be a good place to experiment with
-	recovery techniques without impacting production equipment.</para>
-    </section>
-
-    <section id="HWvsSW">
-      <title>Hardware RAID vs. Vinum (Software RAID)</title>
-
-      <para>Manual intervention is sometimes required to configure a server for
-	degraded mode because
-	<application>Vinum</application>
-	is implemented in software that runs after the FreeBSD
-	kernel is loaded.  One disadvantage of such
-	<firstterm>software RAID</firstterm>
-	solutions is that there is nothing that can be done to hide spindle
-	failures from the BIOS or the FreeBSD boot sequence.  Hence
-	the manual reconfiguration of the server
-	for degraded operation mentioned
-	above just informs the BIOS and boot sequence of failed
-	spindles.
-	<firstterm>Hardware RAID</firstterm> solutions generally have an
-	advantage in that they require no such reconfiguration since
-	spindle failures are hidden from the BIOS and boot sequence.</para>
-
-      <para>Hardware RAID, however, may have some disadvantages that can
-	be significant in some cases:
-	<itemizedlist>
-	  <listitem><para>
-	    The hardware RAID controller itself may become a single
-	    point of failure for the system.
-	  </para></listitem>
-	  <listitem><para>
-	    The data is usually kept in a proprietary
-	    format so that a disk drive cannot be simply plugged
-	    into another main board and booted.
-	  </para></listitem>
-	  <listitem><para>
-	    You often cannot mix and
-	    match drives with different sizes and interfaces.
-	  </para></listitem>
-	  <listitem><para>
-	    You are often limited to the number of drives supported by the
-	    hardware RAID controller (often only four or eight).
-	  </para></listitem>
-	</itemizedlist>
-	In other words, &vinum.ap; may offer advantages in that
-	there is no single point of failure,
-	the drives can boot on most any main board, and
-	you are free to mix and match as many drives using
-	whatever interface you choose.</para>
-
-      <tip>
-	<para>Keep your kernel fairly generic (or at least keep
-	  <filename>/kernel.GENERIC</filename> around).
-	  This will improve the chances that you can come back up on
-	  <quote>foreign</quote> hardware more quickly.</para>
-      </tip>
-
-      <para>The pros and cons discussed above suggest
-	that the root filesystem and swap partition are good
-	candidates for hardware RAID if available.
-	This is especially true for servers where it is difficult for
-	administrators to get console access (recall that this is sometimes
-	required to configure a server for degraded mode operation).
-	A server with only software RAID is well suited to office and home
-	environments where an administrator can be close at hand.</para>
-
-      <note><para>A common myth is that hardware RAID is always faster
-	than software RAID.
-	Since it runs on the host CPU, <application>Vinum</application>
-	often has more CPU power and memory available than a
-	dedicated RAID controller would have.
-	If performance is a prime concern, it is best to benchmark
-	your application running on your CPU with your spindles using
-	both hardware and software RAID systems before making
-	a decision.</para></note>
-
-    </section>
-
-    <section id="HW">
-      <title>Hardware for Vinum</title>
-
-      <para>These instructions may be timely since commodity PC hardware
-	can now easily host several hundred gigabytes of reasonably
-	high-performance disk space at a low price.  Many disk
-	drive manufactures now sell 7,200 RPM disk drives with quite
-	low seek times and high transfer rates through ATA-100
-	interfaces, all at very attractive prices.  Four such drives,
-	attached to a suitable main board and configured with
-	<application>Vinum</application>
-	and prudent partitioning, yields a failure-resilient, high
-	performance disk server at a very reasonable cost.</para>
-
-      <para>However, you can indeed get started with
-	<application>Vinum</application> very simply.
-	A minimum system can be as simple as
-	an old CPU (even a 486 is fine) and a pair of drives
-	that are 500 MB or more.  They need not be the same size or
-	even use the same interface (i.e., it is fine to mix ATAPI and
-	SCSI).  So get busy and give this a try today!  You will have
-	the foundation of a failure-resilient server running in an
-	hour or so!</para>
-    </section>
-  </section>
-
-  <section id="BootstrappingPhases">
-    <title>Bootstrapping Phases</title>
-
-    <para>Greg Lehey suggested this bootstrapping method.
-      It uses knowledge of how <application>Vinum</application>
-      internally allocates disk space to avoid copying data.
-      Instead, <application>Vinum</application>
-      objects are configured so that they occupy the
-      same disk space where <command>/stand/sysinstall</command> built
-      filesystems.
-      The filesystems are thus embedded within
-      <application>Vinum</application> objects without copying.</para>
-
-    <para>There are several distinct phases to the
-      <application>Vinum</application> bootstrapping
-      procedure.  Each of these phases is presented in a separate section below.
-      The section starts with a general overview of the phase and its goals.
-      It then gives example steps for the two-spindle scenario
-      presented here and advice on how to adapt them for your server.
-      (If you are reading for a general understanding
-      of <application>Vinum</application>
-      bootstrapping, the example sections for each phase
-      can safely be skipped.)
-      The remainder of this section gives
-      an overview of the entire bootstrapping process.</para>
-
-    <para>Phase 1 involves planning and preparation.
-      We will balance requirements
-      for the server against available resources and make design
-      tradeoffs.
-      We will plan the transition from no
-      <application>Vinum</application> to
-      <application>Vinum</application>
-      on just one spindle, to <application>Vinum</application>
-      on two spindles.</para>
-
-    <para>In phase 2, we will install a minimum FreeBSD system on a
-      single spindle using partitions of type
-      <literal>4.2BSD</literal> (regular UFS filesystems).</para>
-
-    <para>Phase 3 will embed the non-root filesystems from phase 2 in
-      <application>Vinum</application> objects.
-      Note that <application>Vinum</application> will be up and
-      running at this point,
-      but it cannot yet provide any resilience since it only has
-      one spindle on which to store data.</para>
-
-    <para>Finally in phase 4, we configure <application>Vinum</application>
-      on a second spindle and make a backup copy of the root filesystem.
-      This will give us resilience on all filesystems.</para>
-
-    <section id="P1">
-      <title>Bootstrapping Phase 1: Planning and Preparation</title>
-
-      <para>Our goal in this phase is to define the different partitions
-	we will need and examine their requirements.
-	We will also look at available disk drives and controllers and allocate
-	partitions to them.
-	Finally, we will determine the size of
-	each partition and its use during the bootstrapping process.
-	After this planning is complete, we can optionally prepare to use some
-	tools that will make bootstrapping <application>Vinum</application>
-	easier.</para>
-
-      <para>Several key questions must be answered in this
-	planning phase:</para>
-
-      <itemizedlist>
-	<listitem><para>
-	  What filesystem and partitions will be needed?
-	</para></listitem>
-	<listitem><para>
-	  How will they be used?
-	</para></listitem>
-	<listitem><para>
-	  How will we name each spindle?
-	</para></listitem>
-	<listitem><para>
-	  How will the partitions be ordered for each spindle?
-	</para></listitem>
-	<listitem><para>
-	  How will partitions be assigned to the spindles?
-	</para></listitem>
-	<listitem><para>
-	  How will partitions be configured? Resilience or performance?
-	</para></listitem>
-	<listitem><para>
-	  What technique will be used to achieve resilience?
-	</para></listitem>
-	<listitem><para>
-	  What spindles will be used?
-	</para></listitem>
-	<listitem><para>
-	  How will they be configured on the available controllers?
-	</para></listitem>
-	<listitem><para>
-	  How much space is required for each partition?
-	</para></listitem>
-      </itemizedlist>
-
-      <section id="P1E">
-	<title>Phase 1 Example</title>
-
-	<para>In this example, I will assume a scenario
-	  where we are building
-	  a minimal foundation for a failure-resilient server.
-	  Hence we will need at least root,
-	  <filename>/usr</filename>,
-	  <filename>/home</filename>,
-	  and swap partitions.
-	  The root,
-	  <filename>/usr</filename>, and
-	  <filename>/home</filename> filesystems all need resilience since the
-	  server will not be much good without them.
-	  The swap partition needs performance first and
-	  generally does
-	  not need resilience since nothing it holds needs to be retained
-	  across a reboot.</para>
-
-	<section>
-	  <title>Spindle Naming</title>
-
-	  <para>The kernel would refer to the master spindle on
-	    the primary and secondary ATA controllers as
-	    <devicename>/dev/ad0</devicename> and
-	    <devicename>/dev/ad2</devicename> respectively.
-	    <footnote>
-	      <para>
-		This assumes that you have not removed the line
-		<programlisting>options	ATA_STATIC_ID</programlisting>
-		from your kernel configuration.
-	      </para>
-	    </footnote>
-	    But <application>Vinum</application>
-	    also needs to have a name for each spindle
-	    that will stay the same name regardless
-	    of how it is attached to the CPU (i.e., if the drive moves, the
-	    <application>Vinum</application> name moves with the drive).</para>
-
-	  <para>Some recovery techniques documented below suggest
-	    moving a spindle from
-	    the secondary ATA controller to the primary ATA controller.
-	    (Indeed, the flexibility of making such moves is a key benefit
-	    of <application>Vinum</application>
-	    especially if you are managing a large number of spindles.)
-	    After such a drive/controller swap,
-	    the kernel will see what used to be
-	    <devicename>/dev/ad2</devicename> as
-	    <devicename>/dev/ad0</devicename>
-	    but <application>Vinum</application>
-	    will still call
-	    it by whatever name it had when it was attached to
-	    <devicename>/dev/ad2</devicename>
-	    (i.e., when it was <quote>created</quote> or first made known to
-	    <application>Vinum</application>).</para>
-
-	  <para>Since connections can change, it is best to give
-	    each spindle a unique, abstract
-	    name that gives no hint of how it is attached.
-	    Avoid names that suggest a manufacturer, model number,
-	    physical location, or membership in a sequence
-	    (e.g. avoid names like
-	    <literal>upper</literal>, <literal>lower</literal>, etc.,
-	    <literal>alpha</literal>, <literal>beta</literal>, etc.,
-	    <literal>SCSI1</literal>, <literal>SCSI2</literal>, etc., or
-	    <literal>Seagate1</literal>, <literal>Seagate2</literal> etc.).
-	    Such names are likely to lose their uniqueness or
-	    get out of sequence
-	    someday even if they seem like great names today.</para>
-
-	  <tip>
-	    <para>Once you have picked names for your spindles,
-	      label them with a permanent marker.
-	      If you have hot-swappable hardware, write the names on the sleds
-	      in which the spindles are mounted.
-	      This will significantly reduce the likelihood of
-	      error when you are moving spindles around later as
-	      part of failure recovery or routine system management
-	      procedures.</para></tip>
-
-	  <para>In the instructions that follow,
-	    <application>Vinum</application>
-	    will name the root spindle <literal>YouCrazy</literal>
-	    and the rootback spindle <literal>UpWindow</literal>.
-	    I will only use <devicename>/dev/ad0</devicename>
-	    when I want to refer to whichever
-	    of the two spindles is currently attached as
-	    <devicename>/dev/ad0</devicename>.</para>
-	</section>
-
-	<section>
-	  <title>Partition Ordering</title>
-
-	  <para>Modern disk drives operate with fairly uniform areal
-	    density across the surface of the disk.
-	    That implies that more data is available under the heads without
-	    seeking on the outer cylinders than on the inner cylinders.
-	    We will allocate partitions most critical to system performance
-	    from these outer cylinders as
-	    <command>/stand/sysinstall</command> generally does.</para>
-
-	  <para>The root filesystem is traditionally the outermost, even though
-	    it generally is not as critical to system performance as others.
-	    (However root can have a larger impact on performance if it contains
-	    <filename>/tmp</filename> and <filename>/var</filename> as it
-	    does in this example.)
-	    The FreeBSD boot loaders assume that the
-	    root filesystem lives in the <literal>a</literal> partition.
-	    There is no requirement that the <literal>a</literal>
-	    partition start on the outermost cylinders, but this
-	    convention makes it easier to manage disk labels.</para>
-
-	  <para>Swap performance is critical so it comes next on our way toward
-	    the center.
-	    I/O operations here tend to be large and contiguous.
-	    Having as much data under the heads as possible avoids seeking
-	    while swapping.</para>
-
-	  <para>With all the smaller partitions out of the way, we finish
-	    up the disk with
-	    <filename>/home</filename> and
-	    <filename>/usr</filename>.
-	    Access patterns here tend not to be as intense as for other
-	    filesystems (especially if there is an abundant supply of RAM
-	    and read cache hit rates are high).</para>
-
-	  <para>If the pair of spindles you have are large enough to allow
-	    for more than
-	    <filename>/home</filename> and
-	    <filename>/usr</filename>,
-	    it is fine to plan for additional filesystems here.</para>
-
-	</section>
-
-	<section>
-	  <title>Assigning Partitions to Spindles</title>
-
-	  <para>We will want to assign
-	    partitions to these spindles so that either can fail
-	    without loss of data on filesystems configured for
-	    resilience.</para>
-
-	  <para>Reliability on
-	    <filename>/usr</filename> and
-	    <filename>/home</filename>
-	    is best achieved using <application>Vinum</application>
-	    mirroring.
-	    Resilience will have to come differently, however, for the root
-	    filesystem since <application>Vinum</application>
-	    is not a part of the FreeBSD boot sequence.
-	    Here we will have to settle for two identical
-	    partitions with a periodic copy from the primary to the
-	    backup secondary.</para>
-
-	  <para>The kernel already has support for interleaved swap across
-	    all available partitions so there is no need for help from
-	    <application>Vinum</application> here.
-	    <command>/stand/sysinstall</command>
-	    will automatically configure <filename>/etc/fstab</filename>
-	    for all swap partitions given.</para>
-
-	  <para>The &vinum.ap; bootstrapping method given below
-	    requires a pair of spindles that I will call the
-	    <firstterm>root spindle</firstterm> and the
-	    <firstterm>rootback spindle</firstterm>.</para>
-
-	  <important><para>The rootback spindle must be the same size or
-	    larger than the root spindle.</para></important>
-
-	  <para>These instructions first allocate all space on the root
-	    spindle and then allocate exactly that amount of space on
-	    a rootback spindle.
-	    (After &vinum.ap; is bootstrapped, there is nothing special
-	    about either of these spindles--they are interchangeable.)
-	    You can later use the remaining space on the rootback spindle for
-	    other filesystems.</para>
-
-	  <para>If you have more than two spindles, the
-	    <literal>bootvinum</literal> Perl script and the procedure
-	    below will help you initialize them for use with &vinum.ap;.
-	    However you will have to figure out how to assign partitions
-	    to them on your own.</para>
-
-	</section>
-
-	<section>
-	  <title>Assigning Space to Partitions</title>
-
-	  <para>For this example, I will use two spindles: one with
-	    4,124,673 blocks (about 2 GB) on <devicename>/dev/ad0</devicename>
-	    and one with 8,420,769 blocks (about 4 GB) on
-	    <devicename>/dev/ad2</devicename>.</para>
-
-	  <para>It is best to configure your two spindles on separate
-	    controllers so that both can operate in parallel and
-	    so that you will have failure resilience in case a
-	    controller dies.
-	    Note that mirrored volume write performance will be halved
-	    in cases where both spindles share a controller that requires
-	    they operate serially (as is often the case with ATA controllers).
-	    One spindle will be the master on the primary ATA
-	    controller and the other will be the master on the
-	    secondary ATA controller.</para>
-
-	  <para>Recall that we will be allocating space on the smaller
-	    spindle first and the larger spindle second.</para>
-
-	</section>
-
-	<section id="AssignSmall">
-	  <title>Assigning Partitions on the Root Spindle</title>
-
-	  <para>We will allocate 200,000 blocks (about 93 MB)
-	    for a root filesystem on each spindle
-	    (<devicename>/dev/ad0s1a</devicename> and
-	    <devicename>/dev/ad2s1a</devicename>).
-	    We will initially allocate 200,265 blocks for a swap partition
-	    on each spindle,
-	    giving a total of about 186 MB of
-	    swap space (<devicename>/dev/ad0s1b</devicename> and
-	    <devicename>/dev/ad2s1b</devicename>).</para>
-
-	  <note><para>We will lose 265 blocks from each swap partition
-	    as part of the bootstrapping process.
-	    This is the size of the space used by
-	    <application>Vinum</application> to store configuration
-	    information.
-	    The space will be taken from swap and given to a vinum
-	    partition but will be unavailable for
-	    <application>Vinum</application> subdisks.</para></note>
-
-	  <note><para>I have done the partition allocation in nice round
-	    numbers of blocks just to emphasize where the 265 blocks go.
-	    There is nothing wrong with allocating space in MB if that is
-	    more convenient for you.</para></note>
-
-	  <para>This leaves 4,124,673 - 200,000 - 200,265 = 3,724,408 blocks
-	    (about 1,818 MB) on the root spindle for
-	    <application>Vinum</application>
-	    partitions (<devicename>/dev/ad0s1e</devicename> and
-	    <devicename>/dev/ad2s1f</devicename>).
-	    From this, allocate the 265 blocks for
-	    <application>Vinum</application> configuration information,
-	    1,000,000 blocks (about 488 MB)
-	    for <filename>/home</filename>, and the remaining
-	    2,724,408 blocks (about 1,330 MB) for
-	    <filename>/usr</filename>.
-	    See <xref linkend="ad0b4aft"/> below to see this graphically.</para>
-
-	  <para>The left-hand side of
-	    <xref linkend="ad0b4aft"/> below shows what spindle ad0 will
-	    look like at the end of phase 2.
-	    The right-hand side shows what it will look like at the
-	    end of phase 3.</para>
-
-	  <figure id="ad0b4aft">
-	    <title>Spindle ad0 Before and After Vinum</title>
-
-	    <mediaobject>
-	      <imageobject>
-		<imagedata fileref="ad0b4aft" format="EPS"/>
-	      </imageobject>
-
-	      <textobject>
-		<literallayout class="monospaced">    ad0 Before Vinum    Offset (blocks)    ad0 After Vinum
-+----------------------+ &lt;--      0--&gt; +----------------------+
-|        root          |               |        root          |
-|     /dev/ad0s1a      |               |     /dev/ad0s1a      |
-+----------------------+ &lt;-- 200000--&gt; +----------------------+
-|        swap          |               |        swap          |
-|     /dev/ad0s1b      |               |     /dev/ad0s1b      |
-|                      |     400000--&gt; +----------------------+
-|                      |               | Vinum drive YouCrazy |
-|                      |               |     /dev/ad0s1h      |
-+----------------------+ &lt;-- 400265--&gt; +-----------------+    |
-|        /home         |               |    Vinum sd     |    |
-|     /dev/ad0s1e      |               |    home.p0.s0   |    |
-+----------------------+ &lt;--1400265--&gt; +-----------------+    |
-|        /usr          |               |    Vinum sd     |    |
-|     /dev/ad0s1f      |               |    usr.p0.s0    |    |
-+----------------------+ &lt;--4124673--&gt; +-----------------+----+
-Not to scale</literallayout>
-	      </textobject>
-
-	      <textobject>
-		<phrase>Spindle /dev/ad0 Before and After Vinum</phrase>
-	      </textobject>
-	    </mediaobject>
-	  </figure>
-
-	</section>
-
-	<section id="AssignLarge">
-	  <title>Assigning Partitions on the Rootback Spindle</title>
-
-	  <para>The <filename>/rootback</filename> and swap partition sizes
-	    on the rootback spindle must
-	    match the root and swap partition sizes on the root spindle.
-	    That leaves 8,420,769 - 200,000 - 200,265 = 8,020,504
-	    blocks for the <application>Vinum</application> partition.
-	    Mirrors of <filename>/home</filename> and
-	    <filename>/usr</filename> receive the same allocation as on
-	    the root spindle.
-	    That will leave an extra 2 GB or so that we can deal
-	    with later.
-	    See <xref linkend="ad2b4aft"/> below to see this graphically.</para>
-
-	  <para>The left-hand side of
-	    <xref linkend="ad2b4aft"/> below shows what spindle ad2 will
-	    look like at the beginning of phase 4.
-	    The right-hand side shows what it will look like at the end.</para>
-
-	  <figure id="ad2b4aft">
-	    <title>Spindle ad2 Before and After Vinum</title>
-
-	    <mediaobject>
-	      <imageobject>
-		<imagedata fileref="ad2b4aft" format="EPS"/>
-	      </imageobject>
-
-	      <textobject>
-		<literallayout class="monospaced">    ad2 Before Vinum    Offset (blocks)    ad2 After Vinum
-+----------------------+ &lt;--      0--&gt; +----------------------+
-|      /rootback       |               |      /rootback       |
-|     /dev/ad2s1e      |               |     /dev/ad2s1a      |
-+----------------------+ &lt;-- 200000--&gt; +----------------------+
-|        swap          |               |        swap          |
-|     /dev/ad2s1b      |               |     /dev/ad2s1b      |
-|                      |     400000--&gt; +----------------------+
-|                      |               | Vinum drive UpWindow |
-|                      |               |     /dev/ad2s1h      |
-+----------------------+ &lt;-- 400265--&gt; +-----------------+    |
-|      /NOFUTURE       |               |    Vinum sd     |    |
-|     /dev/ad2s1f      |               |    home.p1.s0   |    |
-|                      |    1400265--&gt; +-----------------+    |
-|                      |               |    Vinum sd     |    |
-|                      |               |    usr.p1.s0    |    |
-|                      |    4124673--&gt; +-----------------+    |
-|                      |               |    Vinum sd     |    |
-|                      |               |    hope.p0.s0   |    |
-+----------------------+ &lt;--8420769--&gt; +-----------------+----+
-Not to scale</literallayout>
-	      </textobject>
-
-	      <textobject>
-		<phrase>Spindle ad2 Before and After Vinum</phrase>
-	      </textobject>
-	    </mediaobject>
-	  </figure>
-
-	</section>
-
-	<section id="floppy">
-	  <title>Preparation of Tools</title>
-
-	  <para>The <literal>bootvinum</literal> Perl script given below in
-	    <xref linkend="Perl"/> will make the
-	    <application>Vinum</application> bootstrapping process much
-	    easier if you can run it on the machine being bootstrapped.
-	    It is over 200 lines and you would not want to type it in.
-	    At this point, I recommend that you
-	    copy it to a floppy or arrange some
-	    alternative method of making it readily available
-	    so that it can be available later when needed.
-	    For example:</para>
-
-<screen>&prompt.root; <userinput>fdformat -f 1440 /dev/fd0</userinput>
-&prompt.root; <userinput>newfs_msdos -f 1440 /dev/fd0</userinput>
-&prompt.root; <userinput>mount_msdos /dev/fd0 /mnt</userinput>
-&prompt.root; <userinput>cp /usr/share/examples/vinum/bootvinum /mnt</userinput></screen>
-
-	  <para>XXX Someday, I would like this script to live in
-	    <filename>/usr/share/examples/vinum</filename>.
-	    Till then, please use this
-	    <ulink url="http://www.BGPBook.Com/vinum/bootvinum">link</ulink>
-	    to get a copy.</para>
-	</section>
-      </section>
-    </section>
-
-    <section id="P2">
-      <title>Bootstrapping Phase 2: Minimal OS Installation</title>
-
-      <para>Our goal in this phase is to complete the smallest possible
-	FreeBSD installation in such a way that we can later install
-	<application>Vinum</application>.
-	We will use only
-	partitions of type <literal>4.2BSD</literal> (i.e., regular UFS file
-	systems) since that is the only type supported by
-	<command>/stand/sysinstall</command>.</para>
-
-      <section id="P2E">
-	<title>Phase 2 Example</title>
-
-	<procedure>
-	  <step>
-	    <para>Start up the FreeBSD installation process by running
-	      <command>/stand/sysinstall</command> from
-	      installation media as you normally would.</para></step>
-
-	  <step>
-	    <para>Fdisk partition all spindles as needed.</para>
-
-	    <important>
-	      <para>Make sure to select BootMgr for all spindles.</para></important>
-	  </step>
-
-	  <step>
-	    <para>Partition the root spindle with appropriate block
-	      allocations as described above in <xref linkend="AssignSmall"/>.
-	      For this example on a 2 GB spindle, I will use
-	      200,000 blocks for root, 200,265 blocks for swap,
-	      1,000,000 blocks for <filename>/home</filename>, and
-	      the rest of the spindle (2,724,408 blocks) for
-	      <filename>/usr</filename>.
-	      (<command>/stand/sysinstall</command>
-	      should automatically assign these to
-	      <devicename>/dev/ad0s1a</devicename>,
-	      <devicename>/dev/ad0s1b</devicename>,
-	      <devicename>/dev/ad0s1e</devicename>, and
-	      <devicename>/dev/ad0s1f</devicename>
-	      by default.)</para>
-
-	    <note><para>If you prefer Soft Updates as I do and you are
-	      using 4.4-RELEASE or better, this is a good time to enable
-	      them.</para></note>
-
-	  </step>
-
-	  <step>
-	    <para>Partition the rootback spindle with the appropriate block
-	      allocations as described above in <xref linkend="AssignLarge"/>.
-	      For this example on a 4 GB spindle, I will use
-	      200,000 blocks for <filename>/rootback</filename>,
-	      200,265 blocks for swap, and
-	      the rest of the spindle (8,020,504 blocks) for
-	      <filename>/NOFUTURE</filename>.
-	      (<command>/stand/sysinstall</command>
-	      should automatically assign these to
-	      <devicename>/dev/ad2s1e</devicename>,
-	      <devicename>/dev/ad2s1b</devicename>, and
-	      <devicename>/dev/ad2s1f</devicename> by default.)</para>
-
-	    <note>
-	      <para>We do not really want to have a
-		<filename>/NOFUTURE</filename> UFS filesystem (we
-		want a vinum partition instead), but that is the
-		best choice we have for the space given the limitations of
-		<command>/stand/sysinstall</command>.
-		Mount point names beginning with <literal>NOFUTURE</literal>
-		and <literal>rootback</literal>
-		serve as sentinels to the bootstrapping
-		script presented in <xref linkend="Perl"/> below.</para></note>
-	  </step>
-
-	  <step>
-	    <para>Partition any other spindles with swap if desired and a
-	      single <filename>/NOFUTURExx</filename> filesystem.</para>
-	  </step>
-
-	  <step>
-	    <para>Select a minimum system install for now even if you
-	      want to end up with more distributions loaded later.</para>
-
-	    <tip>
-	      <para>Do not worry about system configuration options at this
-		point--get <application>Vinum</application>
-		set up and get the partitions in
-		the right places first.</para></tip>
-	  </step>
-
-	  <step>
-	    <para>Exit <command>/stand/sysinstall</command> and reboot.
-	      Do a quick test to verify that the minimum
-	      installation was successful.</para>
-	  </step>
-	</procedure>
-
-	<para>The left-hand side of <xref linkend="ad0b4aft"/> above
-	  and the left-hand side of <xref linkend="ad2b4aft"/> above
-	  show how the disks will look at this point.</para>
-      </section>
-    </section>
-
-    <section id="P3">
-      <title>Bootstrapping Phase 3: Root Spindle Setup</title>
-
-      <para>Our goal in this phase is get <application>Vinum</application>
-	set up and running on the
-	root spindle.
-	We will embed the existing
-	<filename>/usr</filename> and
-	<filename>/home</filename> filesystems in a
-	<application>Vinum</application> partition.
-	Note that the <application>Vinum</application>
-	volumes created will not yet be
-	failure-resilient since we have
-	only one underlying <application>Vinum</application>
-	drive to hold them.
-	The resulting system will automatically start
-	<application>Vinum</application> as it boots to multi-user mode.</para>
-
-      <section id="P3E">
-	<title>Phase 3 Example</title>
-
-	<procedure>
-	  <step>
-	    <para>Login as root.</para>
-	  </step>
-
-	  <step>
-	    <para>We will need a directory in the root filesystem in
-	      which to keep a few files that will be used in the
-	      <application>Vinum</application>
-	      bootstrapping process.</para>
-
-	    <screen>&prompt.root; <userinput>mkdir /bootvinum</userinput>
-&prompt.root; <userinput>cd /bootvinum</userinput></screen>
-	  </step>
-
-	  <step>
-	    <para>Several files need to be prepared for use in bootstrapping.
-	      I have written a Perl script that makes all the required
-	      files for you.
-	      Copy this script to <filename>/bootvinum</filename> by
-	      floppy disk, tape, network, or any convenient means and
-	      then run it.
-	      (If you cannot get this script copied onto the machine being
-	      bootstrapped, then see <xref linkend="ManualBoot"/>
-	      below for a manual alternative.)</para>
-
-	    <screen>&prompt.root; <userinput>cp /mnt/bootvinum .</userinput>
-&prompt.root; <userinput>./bootvinum</userinput></screen>
-
-	    <note><para><literal>bootvinum</literal> produces no output
-	      when run successfully.
-	      If you get any errors,
-	      something may have gone wrong when you were creating
-	      partitions with
-	      <command>/stand/sysinstall</command> above.</para></note>
-
-	    <para>Running <literal>bootvinum</literal> will:</para>
-
-	    <itemizedlist>
-	      <listitem><para>
-		Create <filename>/etc/fstab.vinum</filename>
-		based on what it finds
-		in your existing <filename>/etc/fstab</filename>
-	      </para></listitem>
-	      <listitem><para>
-		Create new disk labels for each spindle mentioned
-		in <filename>/etc/fstab</filename> and keep copies of the
-		current disk labels
-	      </para></listitem>
-	      <listitem><para>
-		Create files needed as input to <command>vinum</command>
-		<option>create</option> for building
-		<application>Vinum</application> objects on each spindle
-	      </para></listitem>
-	      <listitem><para>
-		Create many alternates to <filename>/etc/fstab.vinum</filename>
-		that might come in handy should a spindle fail
-	      </para></listitem>
-	    </itemizedlist>
-
-	    <para>You may want to take a look at these files to learn more
-	      about the disk partitioning required for
-	      <application>Vinum</application> or to learn more about the
-	      commands needed to create
-	      <application>Vinum</application> objects.</para>
-
-	  </step>
-
-	  <step>
-	    <para>We now need to install new spindle partitioning for
-	      <devicename>/dev/ad0</devicename>.
-	      This requires that
-	      <devicename>/dev/ad0s1b</devicename> not be in use for
-	      swapping so we have to reboot in single-user mode.</para>
-
-	    <substeps>
-	      <step>
-		<para>First, reboot the system.</para>
-
-		<screen>&prompt.root; <userinput>reboot</userinput></screen>
-	      </step>
-
-	      <step>
-		<para>Next, enter single-user mode.</para>
-		<screen>Hit [Enter] to boot immediately, or any other key for command prompt.
-Booting [kernel] in 8 seconds...
-
-Type '?' for a list of commands, 'help' for more detailed help.
-ok <userinput>boot -s</userinput></screen>
-
-	      </step>
-	    </substeps>
-	  </step>
-
-	  <step>
-	    <para>In single-user mode, install the new partitioning
-	      created above.</para>
-
-	    <screen>&prompt.root; <userinput>cd /bootvinum</userinput>
-&prompt.root; <userinput>disklabel -R ad0s1 disklabel.ad0s1</userinput>
-&prompt.root; <userinput>disklabel -R ad2s1 disklabel.ad2s1</userinput></screen>
-
-	    <note><para>If you have additional spindles, repeat the
-	      above commands as appropriate for them.</para></note>
-
-	  </step>
-
-	  <step>
-	    <para>We are about to start <application>Vinum</application>
-	      for the first time.
-	      It is going to want to create several device nodes under
-	      <filename>/dev/vinum</filename> so we will need to mount the
-	      root filesystem for read/write access.</para>
-
-	    <screen>&prompt.root; <userinput>fsck -p /</userinput>
-&prompt.root; <userinput>mount /</userinput></screen>
-	  </step>
-
-	  <step>
-	    <para>Now it is time to create the <application>Vinum</application>
-	      objects that
-	      will embed the existing non-root filesystems on
-	      the root spindle in a
-	      <application>Vinum</application> partition.
-	      This will load the <application>Vinum</application>
-	      kernel module and start <application>Vinum</application>
-	      as a side effect.</para>
-
-	    <screen>&prompt.root; <userinput>vinum create create.YouCrazy</userinput></screen>
-
-	    <para>
-	      You should see a list of <application>Vinum</application>
-	      objects created that looks like the following:</para>
-<screen>1 drives:
-D YouCrazy              State: up	Device /dev/ad0s1h	Avail: 0/1818 MB (0%)
-
-2 volumes:
-V home                  State: up	Plexes:       1	Size:        488 MB
-V usr                   State: up	Plexes:       1	Size:       1330 MB
-
-2 plexes:
-P home.p0             C State: up	Subdisks:     1	Size:        488 MB
-P usr.p0              C State: up	Subdisks:     1	Size:       1330 MB
-
-2 subdisks:
-S home.p0.s0            State: up	PO:        0  B Size:        488 MB
-S usr.p0.s0             State: up	PO:        0  B Size:       1330 MB</screen>
-	    <para>
-	      You should also see several kernel messages
-	      which state that the <application>Vinum</application>
-	      objects you have created are now <literal>up</literal>.</para>
-	  </step>
-
-	  <step>
-	    <para>Our non-root filesystems should now be embedded in a
-	      <application>Vinum</application> partition and
-	      hence available through <application>Vinum</application>
-	      volumes.
-	      It is important to test that this embedding worked.</para>
-
-	    <screen>&prompt.root; <userinput>fsck -n /dev/vinum/home</userinput>
-&prompt.root; <userinput>fsck -n /dev/vinum/usr</userinput></screen>
-
-	    <para>This should produce no errors.
-	      If it does produce errors <emphasis>do not fix them</emphasis>.
-	      Instead, go back and examine the root spindle partition tables
-	      before and after <application>Vinum</application>
-	      to see if you can spot the error.
-	      You can back out the partition table changes by using
-	      <command>disklabel -R</command> with the
-	      <filename>disklabel.*.b4vinum</filename> files.</para>
-	  </step>
-
-	  <step>
-	    <para>While we have the root filesystem mounted read/write, this is
-	      a good time to install <filename>/etc/fstab</filename>.</para>
-
-	    <screen>&prompt.root; <userinput>mv /etc/fstab /etc/fstab.b4vinum</userinput>
-&prompt.root; <userinput>cp /etc/fstab.vinum /etc/fstab</userinput></screen>
-	  </step>
-
-	  <step>
-	    <para>We are now done with tasks requiring single-user
-	      mode, so it is safe to go multi-user from here on.</para>
-
-	    <screen>&prompt.root; <userinput>^D</userinput></screen>
-	  </step>
-
-	  <step>
-	    <para>Login as root.</para>
-	  </step>
-
-	  <step>
-	    <para>Edit <filename>/etc/rc.conf</filename> and add this line:
-	      <programlisting>start_vinum="YES"</programlisting></para>
-	  </step>
-	</procedure>
-      </section>
-    </section>
-
-    <section id="P4">
-      <title>Bootstrapping Phase 4: Rootback Spindle Setup</title>
-
-      <para>Our goal in this phase is to get redundant copies of all data
-	from the root spindle to the rootback spindle.
-	We will first create the necessary <application>Vinum</application>
-	objects on the rootback spindle.
-	Then we will ask <application>Vinum</application>
-	to copy the data from the root spindle to the
-	rootback spindle.
-	Finally, we use <command>dump</command> and <command>restore</command>
-	to copy the root filesystem.</para>
-
-      <section id="P4E">
-	<title>Phase 4 Example</title>
-
-	<procedure>
-	  <step>
-	    <para>Now that <application>Vinum</application>
-	      is running on the root spindle, we can bring
-	      it up on the rootback spindle so that our
-	      <application>Vinum</application> volumes can become
-	      failure-resilient.</para>
-
-	    <screen>&prompt.root; <userinput>cd /bootvinum</userinput>
-&prompt.root; <userinput>vinum create create.UpWindow</userinput></screen>
-
-	    <para>You should see a list of <application>Vinum</application>
-	      objects created that
-	      looks like the following:</para>
-
-<screen>2 drives:
-D YouCrazy              State: up       Device /dev/ad0s1h      Avail: 0/1818 MB (0%)
-D UpWindow              State: up       Device /dev/ad2s1h      Avail: 2096/3915 MB (53%)
-
-2 volumes:
-V home                  State: up       Plexes:       2 Size:        488 MB
-V usr                   State: up       Plexes:       2 Size:       1330 MB
-
-4 plexes:
-P home.p0             C State: up       Subdisks:     1 Size:        488 MB
-P usr.p0              C State: up       Subdisks:     1 Size:       1330 MB
-P home.p1             C State: faulty   Subdisks:     1 Size:        488 MB
-P usr.p1              C State: faulty   Subdisks:     1 Size:       1330 MB
-
-4 subdisks:
-S home.p0.s0            State: up       PO:        0  B Size:        488 MB
-S usr.p0.s0             State: up       PO:        0  B Size:       1330 MB
-S home.p1.s0            State: stale    PO:        0  B Size:        488 MB
-S usr.p1.s0             State: stale    PO:        0  B Size:       1330 MB</screen>
-
-	    <para>You should also see several kernel messages
-	      which state that some of the <application>Vinum</application>
-	      objects you have created are now <literal>up</literal>
-	      while others are <literal>faulty</literal> or
-	      <literal>stale</literal>.</para>
-	  </step>
-
-	  <step>
-	    <para>Now we ask <application>Vinum</application>
-	      to copy each of the subdisks on drive
-	      <literal>YouCrazy</literal> to drive <literal>UpWindow</literal>.
-	      This will change the state of the newly created
-	      <application>Vinum</application> subdisks
-	      from <literal>stale</literal> to <literal>up</literal>.
-	      It will also change the state of the newly created
-	      <application>Vinum</application> plexes
-	      from <literal>faulty</literal> to <literal>up</literal>.</para>
-
-	    <para>First, we do the new subdisk we
-	      added to <filename>/home</filename>.</para>
-
-	    <screen>&prompt.root; <userinput>vinum start -w home.p1.s0</userinput>
-reviving home.p1.s0
-<emphasis>(time passes . . . )</emphasis>
-home.p1.s0 is up by force
-home.p1 is up
-home.p1.s0 is up</screen>
-	    <note>
-	      <para>
-		My 5,400 RPM EIDE spindles copied at about 3.5 MBytes/sec.
-		Your mileage may vary.
-	      </para>
-	    </note>
-	  </step>
-
-	  <step>
-	    <para>Next we do the new subdisk we
-	      added to <filename>/usr</filename>.</para>
-
-	    <screen>&prompt.root; <userinput>vinum start -w usr.p1.s0</userinput>
-reviving usr.p1.s0
-<emphasis>(time passes . . . )</emphasis>
-usr.p1.s0 is up by force
-usr.p1 is up
-usr.p1.s0 is up</screen>
-
-	    <para>All <application>Vinum</application>
-	      objects should be in state <literal>up</literal> at this point.
-	      The output of
-	      <command>vinum list</command> should look
-	      like the following:</para>
-
-<screen>2 drives:
-D YouCrazy              State: up	Device /dev/ad0s1h	Avail: 0/1818 MB (0%)
-D UpWindow              State: up	Device /dev/ad2s1h	Avail: 2096/3915 MB (53%)
-
-2 volumes:
-V home                  State: up	Plexes:       2	Size:        488 MB
-V usr                   State: up	Plexes:       2	Size:       1330 MB
-
-4 plexes:
-P home.p0             C State: up	Subdisks:     1	Size:        488 MB
-P usr.p0              C State: up	Subdisks:     1	Size:       1330 MB
-P home.p1             C State: up	Subdisks:     1	Size:        488 MB
-P usr.p1              C State: up	Subdisks:     1	Size:       1330 MB
-
-4 subdisks:
-S home.p0.s0            State: up	PO:        0  B Size:        488 MB
-S usr.p0.s0             State: up	PO:        0  B Size:       1330 MB
-S home.p1.s0            State: up	PO:        0  B Size:        488 MB
-S usr.p1.s0             State: up	PO:        0  B Size:       1330 MB</screen>
-	  </step>
-
-	  <step>
-	    <para>Copy the root filesystem so that you will have a backup.</para>
-
-	    <screen>&prompt.root; <userinput>cd /rootback</userinput>
-&prompt.root; <userinput>dump 0f - / | restore rf -</userinput>
-&prompt.root; <userinput>rm restoresymtable</userinput>
-&prompt.root; <userinput>cd /</userinput></screen>
-
-	    <note>
-	      <para>You may see errors like this:</para>
-
-	      <screen>./tmp/rstdir1001216411: (inode 558) not found on tape
-cannot find directory inode 265
-abort? [yn] <userinput>n</userinput>
-expected next file 492, got 491</screen>
-
-	      <para>They seem to cause no harm.
-		I suspect they are a consequence of dumping the filesystem
-		containing <filename>/tmp</filename> and/or the pipe
-		connecting <command>dump</command> and
-		<command>restore</command>.</para>
-
-	    </note>
-	  </step>
-
-	  <step>
-	    <para>Make a directory on which we can mount a damaged root
-	      filesystem during the recovery process.</para>
-
-	    <screen>&prompt.root; <userinput>mkdir /rootbad</userinput></screen>
-
-	  </step>
-
-	  <step>
-	    <para>Remove sentinel mount points that are now unused.</para>
-
-	    <screen>&prompt.root; <userinput>rmdir /NOFUTURE*</userinput></screen>
-
-	  </step>
-
-	  <step>
-	    <para>Create empty &vinum.ap; drives on remaining spindles.</para>
-
-	    <screen>&prompt.root; <userinput>vinum create create.ThruBank</userinput>
-&prompt.root; <userinput>...</userinput></screen>
-
-	  </step>
-	</procedure>
-
-	<para>At this point, the reliable server foundation is complete.
-	  The right-hand side of <xref linkend="ad0b4aft"/> above
-	  and the right-hand side of <xref linkend="ad2b4aft"/> above
-	  show how the disks will look.</para>
-
-	<para>You may want to do a quick reboot to multi-user and give it
-	  a quick test drive.
-	  This is also a good point to complete installation
-	  of other distributions beyond the minimal install.
-	  Add packages, ports, and users as required.
-	  Configure <filename>/etc/rc.conf</filename> as required.</para>
-
-	<tip>
-	  <para>After you have completed your server configuration,
-	    remember to do one more copy of root to
-	    <filename>/rootback</filename> as shown above before placing
-	    the server into production.</para></tip>
-
-	<tip>
-	  <para>Make a schedule to refresh
-	    <filename>/rootback</filename> periodically.</para></tip>
-
-	<tip>
-	  <para>It may be a good idea to mount
-	    <filename>/rootback</filename> read-only for normal operation
-	    of the server.
-	    This does, however, complicate the periodic refresh a bit.</para></tip>
-
-	<tip>
-	  <para>Do not forget to watch
-	    <filename>/var/log/messages</filename> carefully for errors.
-	    <application>Vinum</application>
-	    may automatically avoid failed hardware in a way that users
-	    do not notice.
-	    You must watch for such failures and get them repaired before a
-	    second failure results in data loss.
-	    You may see
-	    <application>Vinum</application> noting damaged objects
-	    at server boot time.</para></tip>
-
-      </section>
-    </section>
-  </section>
-
-  <section id="FromHere">
-    <title>Where to Go from Here?</title>
-
-    <para>Now that you have established the foundation of a reliable server,
-      there are several things you might want to try next.</para>
-
-    <section>
-      <title>Make a Vinum Volume with Remaining Space</title>
-
-      <para>Following are the steps to create another
-	<application>Vinum</application> volume with space remaining
-	on the rootback spindle.</para>
-
-      <note><para>This volume will not be resilient to spindle failure
-	since it has only one plex on a single spindle.</para></note>
-
-      <procedure>
-	<step>
-	  <para>Create a file with the following contents:</para>
-
-	  <programlisting>volume hope
-  plex name hope.p0 org concat volume hope
-    sd name hope.p0.s0 drive UpWindow plex hope.p0 len 0</programlisting>
-
-	  <note>
-	    <para>Specifying a length of <literal>0</literal> for
-	      the <filename>hope.p0.s0</filename> subdisk
-	      asks <application>Vinum</application>
-	      to use whatever space is left available on the underlying
-	      drive.</para></note>
-	</step>
-
-	<step>
-	  <para>Feed these commands into <command>vinum</command> <option>create</option>.</para>
-	  <screen>&prompt.root; <userinput>vinum create <replaceable>filename</replaceable></userinput></screen>
-	</step>
-
-	<step>
-	  <para>Now we <command>newfs</command> the volume and
-	    <command>mount</command> it.</para>
-
-	  <screen>&prompt.root; <userinput>newfs -v /dev/vinum/hope</userinput>
-&prompt.root; <userinput>mkdir /hope</userinput>
-&prompt.root; <userinput>mount /dev/vinum/hope /hope</userinput></screen>
-
-	</step>
-
-	<step>
-	  <para>Edit <filename>/etc/fstab</filename> if you want
-	    <filename>/hope</filename> mounted at boot time.</para>
-	</step>
-
-      </procedure>
-    </section>
-
-    <section>
-      <title>Try Out More Vinum Commands</title>
-
-      <para>You might already be familiar with
-	<command>vinum</command> <option>list</option> to get a list of
-	all <application>Vinum</application> objects.
-	Try <option>-v</option> following it to see more detail.</para>
-
-      <para>If you have more spindles and you want to bring them up as
-	concatenated, mirrored, or striped volumes, then give
-	<command>vinum</command> <option>concat</option> <replaceable>drivelist</replaceable>,
-	<command>vinum</command> <option>mirror</option> <replaceable>drivelist</replaceable>, or
-	<command>vinum</command> <option>stripe</option> <replaceable>drivelist</replaceable> a try.</para>
-
-      <para>See &man.vinum.8; for sample configurations and important
-	performance considerations before settling on a final organization
-	for your additional spindles.</para>
-
-      <para>The failure recovery instructions below will also give you
-	some experience using more <application>Vinum</application>
-	commands.</para>
-
-    </section>
-  </section>
-
-  <section id="Failures">
-    <title>Failure Scenarios</title>
-
-    <para>This section contains descriptions of various failure scenarios.
-      For each scenario, there is a subsection on how to configure your
-      server for degraded mode operation, how to recover from the failure,
-      how to exit degraded mode, and how to simulate the failure.</para>
-
-    <tip>
-      <para>Make a hard copy of these instructions and leave them inside the CPU
-	case, being careful not to interfere with ventilation.</para></tip>
-
-    <section id="ad0RootBad">
-      <title>Root filesystem on ad0 unusable, rest of drive ok</title>
-
-      <note>
-	<para>We assume here that the boot blocks and disk label on
-	  <devicename>/dev/ad0</devicename> are ok.
-	  If your BIOS can boot from a drive other than
-	  <devicename>C:</devicename>, you may be able to get around this
-	  limitation.</para></note>
-
-      <section id="enter1">
-	<title>Configure Server for Degraded Mode</title>
-
-	<procedure>
-	  <step>
-	    <para>Use BootMgr to load kernel from
-	      <devicename>/dev/ad2s1a</devicename>.</para>
-
-	    <substeps>
-	      <step>
-		<para>Hit <keycap>F5</keycap> in BootMgr to select
-		  <literal>Drive 1</literal>.</para>
-	      </step>
-
-	      <step>
-		<para>Hit <keycap>F1</keycap> to select
-		  <literal>FreeBSD</literal>.</para>
-	      </step>
-	    </substeps>
-	  </step>
-
-	  <step>
-	    <para>After the kernel is loaded, hit any key but enter to interrupt
-	      the boot sequence.
-	      Boot into single-user mode and allow explicit entry of
-	      a root filesystem.</para>
-
-	    <screen>Hit [Enter] to boot immediately, or any other key for command prompt.
-Booting [kernel] in 8 seconds...
-
-Type '?' for a list of commands, 'help' for more detailed help.
-ok <userinput>boot -as</userinput></screen>
-
-	  </step>
-
-	  <step>
-	    <para>Select <filename>/rootback</filename>
-	      as your root filesystem.</para>
-
-	    <screen>Manual root filesystem specification:
-    &lt;fstype>:&lt;device>  Mount &lt;device> using filesystem &lt;fstype>
-			 e.g. ufs:/dev/da0s1a
-    ?                  List valid disk boot devices
-    &lt;empty line>       Abort manual input
-
-  mountroot> <userinput>ufs:/dev/ad2s1a</userinput></screen>
-	  </step>
-
-	  <step>
-	    <para>Now that you are in single-user mode, change
-	      <filename>/etc/fstab</filename> to avoid the
-	      bad root filesystem.</para>
-
-	    <tip>
-	      <para>If you used the <literal>bootvinum</literal> Perl script from <xref linkend="Perl"/>
-		below, then these commands should configure your server for
-		degraded mode.</para>
-
-	      <screen>&prompt.root; <userinput>fsck -p /</userinput>
-&prompt.root; <userinput>mount /</userinput>
-&prompt.root; <userinput>cd /etc</userinput>
-&prompt.root; <userinput>mv fstab fstab.bak</userinput>
-&prompt.root; <userinput>cp fstab_ad0s1_root_bad fstab</userinput>
-&prompt.root; <userinput>cd /</userinput>
-&prompt.root; <userinput>mount -o ro /</userinput>
-&prompt.root; <userinput>vinum start</userinput>
-&prompt.root; <userinput>fsck -p</userinput>
-&prompt.root; <userinput>^D</userinput></screen>
-	    </tip>
-	  </step>
-	</procedure>
-      </section>
-
-      <section>
-	<title>Recovery</title>
-
-	<procedure>
-	  <step>
-	    <para>Restore <devicename>/dev/ad0s1a</devicename> from
-	      backups or copy
-	      <filename>/rootback</filename> to it with these commands:</para>
-
-	    <screen>&prompt.root; <userinput>umount /rootbad</userinput>
-&prompt.root; <userinput>newfs /dev/ad0s1a</userinput>
-&prompt.root; <userinput>tunefs -n enable /dev/ad0s1a</userinput>
-&prompt.root; <userinput>mount /rootbad</userinput>
-&prompt.root; <userinput>cd /rootbad</userinput>
-&prompt.root; <userinput>dump 0f - / | restore rf -</userinput>
-&prompt.root; <userinput>rm restoresymtable</userinput></screen>
-	  </step>
-	</procedure>
-      </section>
-
-      <section>
-	<title>Exiting Degraded Mode</title>
-
-	<procedure>
-	  <step>
-	    <para>Enter single-user mode.</para>
-
-	    <screen>&prompt.root; <userinput>shutdown now</userinput></screen>
-	  </step>
-
-	  <step>
-	    <para>Put <filename>/etc/fstab</filename> back to
-	      normal and reboot.</para>
-
-	    <screen>&prompt.root; <userinput>cd /rootbad/etc</userinput>
-&prompt.root; <userinput>rm fstab</userinput>
-&prompt.root; <userinput>mv fstab.bak fstab</userinput>
-&prompt.root; <userinput>reboot</userinput></screen>
-	  </step>
-
-	  <step>
-	    <para>Reboot and hit <keycap>F1</keycap> to boot from
-	      <devicename>/dev/ad0</devicename> when
-	      prompted by BootMgr.</para>
-	  </step>
-	</procedure>
-      </section>
-
-      <section>
-	<title>Simulation</title>
-
-	<para>This kind of failure can be simulated by shutting down to
-	  single-user mode and then booting as shown above in
-	  <xref linkend="enter1"/>.</para>
-      </section>
-    </section>
-
-    <section id="ad2Bad">
-      <title>Drive ad2 Fails</title>
-
-      <para>This section deals with the total failure of
-	<devicename>/dev/ad2</devicename>.</para>
-
-      <section>
-	<title>Configure Server for Degraded Mode</title>
-
-	<procedure>
-	  <step>
-	    <para>After the kernel is loaded, hit any key but
-	      <keycap>Enter</keycap> to interrupt the boot sequence.
-	      Boot into single-user mode.</para>
-
-	    <screen>Hit [Enter] to boot immediately, or any other key for command prompt.
-Booting [kernel] in 8 seconds...
-
-Type '?' for a list of commands, 'help' for more detailed help.
-ok <userinput>boot -s</userinput></screen>
-
-	  </step>
-
-	  <step>
-	    <para>Change
-	      <filename>/etc/fstab</filename> to avoid the bad drive.
-	      If you used the <literal>bootvinum</literal> Perl script from <xref linkend="Perl"/>
-	      below, then
-	      these commands should configure your server for
-	      degraded mode.</para>
-
-	      <screen>&prompt.root; <userinput>fsck -p /</userinput>
-&prompt.root; <userinput>mount /</userinput>
-&prompt.root; <userinput>cd /etc</userinput>
-&prompt.root; <userinput>mv fstab fstab.bak</userinput>
-&prompt.root; <userinput>cp fstab_only_have_ad0s1 fstab</userinput>
-&prompt.root; <userinput>cd /</userinput>
-&prompt.root; <userinput>mount -o ro /</userinput>
-&prompt.root; <userinput>vinum start</userinput>
-&prompt.root; <userinput>fsck -p</userinput>
-&prompt.root; <userinput>^D</userinput></screen>
-
-	    <para>If you do not have modified versions of
-	      <filename>/etc/fstab</filename> that are ready for use,
-	      then you can use <command>ed</command> to make one.
-	      Alternatively, you can <command>fsck</command> and
-	      <command>mount</command>
-	      <filename>/usr</filename> and then use your
-	      favorite editor.</para>
-
-	  </step>
-	</procedure>
-      </section>
-
-      <section id="ad2Recov">
-	<title>Recovery</title>
-	<procedure>
-
-	  <para>We assume here that your server is up and running multi-user in
-	    degraded mode on just
-	    <devicename>/dev/ad0</devicename> and that you have
-	    a new spindle now on
-	    <devicename>/dev/ad2</devicename> ready to go.</para>
-
-	  <para>You will need a new spindle with enough room to hold root and swap
-	    partitions plus a <application>Vinum</application>
-	    partition large enough to hold
-	    <filename>/home</filename> and <filename>/usr</filename>.</para>
-
-	  <step>
-	    <para>Create a BIOS partition (slice) on the new spindle.</para>
-
-	    <screen>&prompt.root; <userinput>/stand/sysinstall</userinput></screen>
-
-	    <substeps>
-	      <step><para>Select <literal>Custom</literal>.</para></step>
-	      <step><para>Select <literal>Partition</literal>.</para></step>
-	      <step><para>Select <devicename>ad2</devicename>.</para></step>
-	      <step><para>Create a FreeBSD (type 165) slice
-		large enough to hold everything mentioned above.</para></step>
-	      <step><para>Write changes.</para></step>
-	      <step><para>Yes, you are absolutely sure.</para></step>
-	      <step><para>Select BootMgr.</para></step>
-	      <step><para>Quit Partitioning.</para></step>
-	      <step><para>Exit <command>/stand/sysinstall</command>.</para></step>
-	    </substeps>
-	  </step>
-
-	  <step>
-	    <para>Create disk label partitioning based on current
-	      <devicename>/dev/ad0</devicename> partitioning.</para>
-
-	    <screen>&prompt.root; <userinput>disklabel ad0 > /tmp/ad0</userinput>
-&prompt.root; <userinput>disklabel -e ad2</userinput></screen>
-
-	    <para>This will drop you into your favorite editor.</para>
-
-	    <substeps>
-	      <step>
-		<para>Copy the lines for the <literal>a</literal> and
-		  <literal>b</literal> partitions from
-		  <filename>/tmp/ad0</filename> to the
-		  <devicename>ad2</devicename> disklabel.</para>
-	      </step>
-
-	      <step>
-		<para>Add the <literal>size</literal> of the
-		  <literal>a</literal> and
-		  <literal>b</literal> partitions to find the proper
-		  <literal>offset</literal> for the
-		  <literal>h</literal> partition.</para>
-	      </step>
-
-	      <step>
-		<para>Subtract this <literal>offset</literal> from the
-		  <literal>size</literal> of the <literal>c</literal>
-		  partition to find the proper <literal>size</literal> for the <literal>h</literal>
-		  partition.</para>
-	      </step>
-
-	      <step>
-		<para>Define an <literal>h</literal> partition with the
-		  <literal>size</literal> and
-		  <literal>offset</literal> calculated above.</para>
-	      </step>
-
-	      <step>
-		<para>Set the <literal>fstype</literal> column to
-		  <literal>vinum</literal>.</para>
-	      </step>
-
-	      <step>
-		<para>Save the file and quit your editor.</para>
-	      </step>
-	    </substeps>
-	  </step>
-
-	  <step>
-	    <para>Tell <application>Vinum</application>
-	      about the new drive.</para>
-
-	    <substeps>
-	      <step>
-		<para>Ask <application>Vinum</application> to start an
-		  editor with a copy of the current configuration.</para>
-
-		<screen>&prompt.root; <userinput>vinum create</userinput></screen>
-
-	      </step>
-
-	      <step>
-		<para>Uncomment the drive line referring to drive
-		  <literal>UpWindow</literal> and set
-		  <literal>device</literal> to
-		  <devicename>/dev/ad2s1h</devicename>.</para></step>
-
-	      <step>
-		<para>Save the file and quit your editor.</para></step>
-
-	    </substeps>
-	  </step>
-
-	  <step>
-	    <para>Now that <application>Vinum</application>
-	      has two spindles again, revive the mirrors.</para>
-
-	    <screen>&prompt.root; <userinput>vinum start -w usr.p1.s0</userinput>
-&prompt.root; <userinput>vinum start -w home.p1.s0</userinput></screen>
-	  </step>
-
-	  <step>
-	    <para>Now we need to restore
-	      <filename>/rootback</filename> to a current copy of the
-	      root filesystem.
-	      These commands will accomplish this.</para>
-
-	    <screen>&prompt.root; <userinput>newfs /dev/ad2s1a</userinput>
-&prompt.root; <userinput>tunefs -n enable /dev/ad2s1a</userinput>
-&prompt.root; <userinput>mount /dev/ad2s1a /mnt</userinput>
-&prompt.root; <userinput>cd /mnt</userinput>
-&prompt.root; <userinput>dump 0f - / | restore rf -</userinput>
-&prompt.root; <userinput>rm restoresymtable</userinput>
-&prompt.root; <userinput>cd /</userinput>
-&prompt.root; <userinput>umount /mnt</userinput></screen>
-	  </step>
-	</procedure>
-      </section>
-
-      <section>
-	<title>Exiting Degraded Mode</title>
-
-	<procedure>
-	  <step>
-	    <para>Enter single-user mode.</para>
-
-	    <screen>&prompt.root; <userinput>shutdown now</userinput></screen>
-	  </step>
-
-	  <step>
-	    <para>Return <filename>/etc/fstab</filename> to
-	      its normal state and reboot.</para>
-
-	    <screen>&prompt.root; <userinput>cd /etc</userinput>
-&prompt.root; <userinput>rm fstab</userinput>
-&prompt.root; <userinput>mv fstab.bak fstab</userinput>
-&prompt.root; <userinput>reboot</userinput></screen>
-	  </step>
-	</procedure>
-      </section>
-
-      <section>
-	<title>Simulation</title>
-
-	<para>You can simulate this kind of failure by unplugging
-	  <devicename>/dev/ad2</devicename>, write-protecting it,
-	  or by this procedure:</para>
-
-	<procedure>
-	  <step>
-	    <para>Shutdown to single-user mode.</para>
-	  </step>
-
-	  <step>
-	    <para>Unmount all non-root filesystems.</para>
-	  </step>
-
-	  <step>
-	    <para>Clobber any existing <application>Vinum</application>
-	      configuration and partitioning on
-	      <devicename>/dev/ad2</devicename>.</para>
-
-	    <screen>&prompt.root; <userinput>vinum stop</userinput>
-&prompt.root; <userinput>dd if=/dev/zero of=/dev/ad2s1h count=512</userinput>
-&prompt.root; <userinput>dd if=/dev/zero of=/dev/ad2 count=512</userinput></screen>
-	  </step>
-	</procedure>
-      </section>
-    </section>
-
-    <section id="ad0Bad">
-      <title>Drive ad0 Fails</title>
-
-      <para>Some BIOSes can boot from drive 1 or drive 2 (often called
-	<devicename>C:</devicename> or <devicename>D:</devicename>),
-	while others can boot only from drive 1.
-	If your BIOS can boot from either, the fastest road to recovery
-	might be to boot directly from <filename>/dev/ad2</filename>
-	in single-user mode and
-	install <filename>/etc/fstab_only_have_ad2s1</filename> as
-	<filename>/etc/fstab</filename>.
-	You would then have to adapt the <filename>/dev/ad2</filename>
-	failure recovery instructions from <xref linkend="ad2Recov"/> above.</para>
-
-      <para>If your BIOS can only boot from drive one, then you will have to
-	unplug drive <literal>YouCrazy</literal> from the controller for
-	<devicename>/dev/ad2</devicename> and plug it
-	into the controller for <devicename>/dev/ad0</devicename>.
-	Then continue with the instructions for
-	<devicename>/dev/ad2</devicename> failure recovery
-	in <xref linkend="ad2Recov"/> above.</para>
-    </section>
-  </section>
-
-  <appendix id="Perl">
-    <title>bootvinum Perl Script</title>
-
-    <para>The <literal>bootvinum</literal> Perl script below reads <filename>/etc/fstab</filename>
-      and current drive partitioning.
-      It then writes several files in the current directory and several
-      variants of <filename>/etc/fstab</filename> in <filename>/etc</filename>.
-      These files significantly simplify the installation of
-      <application>Vinum</application> and recovery from
-      spindle failures.</para>
-
-    <programlisting>#!/usr/bin/perl -w
-use strict;
-use FileHandle;
-
-my $config_tag1 = '$Id: article.sgml,v 1.17 2012-03-20 08:56:30 pluknet Exp $';
-# Copyright (C) 2001 Robert A. Van Valzah
-#
-# Bootstrap Vinum
-#
-# Read /etc/fstab and current partitioning for all spindles mentioned there.
-# Generate files needed to mirror all filesystems on root spindle.
-#  A new partition table for each spindle
-#  Input for the vinum create command to create Vinum objects on each spindle
-#  A copy of fstab mounting Vinum volumes instead of BSD partitions
-#  Copies of fstab altered for server's degraded modes of operation
-# See handbook for instructions on how to use the files generated.
-# N.B. This bootstrapping method shrinks size of swap partition by the size
-# of Vinum's on-disk configuration (265 sectors).  It embeds existing file
-# systems on the root spindle in Vinum objects without having to copy them.
-# Thanks to Greg Lehey for suggesting this bootstrapping method.
-# Expectations:
-#  The root spindle must contain at least root, swap, and /usr partitions
-#  The rootback spindle must have matching /rootback and swap partitions
-#  Other spindles should only have a /NOFUTURE* filesystem and maybe swap
-#  File systems named /NOFUTURE* will be replaced with Vinum drives
-
-# Change configuration variables below to suit your taste
-my $vip = 'h';					# VInum Partition
-my @drv = ('YouCrazy', 'UpWindow', 'ThruBank',	# Vinum DRiVe names
-  'OutSnakes', 'MeWild', 'InMovie', 'HomeJames', 'DownPrices', 'WhileBlind');
-# No configuration variables beyond this point
-
-my %vols;		# One entry per Vinum volume to be created
-my @spndl;		# One entry per SPiNDLe
-my $rsp;		# Root SPindle (as in /dev/$rsp)
-my $rbsp;		# RootBack SPindle (as in /dev/$rbsp)
-my $cfgsiz = 265;	# Size of Vinum on-disk configuration info in sectors
-my $nxtpas = 2;		# Next fsck pass number for non-root filesystems
-
-# Parse fstab, generating the version we'll need for Vinum and noting
-# spindles in use.
-my $fsin = "/etc/fstab";
-#my $fsin = "simu/fstab";
-open(FSIN, "$fsin") || die("Couldn't open $fsin: $!\n");
-
-my $fsout = "/etc/fstab.vinum";
-open(FSOUT, ">$fsout") || die("Couldn't open $fsout for writing: $!\n");
-
-while (&lt;FSIN>) {
-  my ($dev, $mnt, $fstyp, $opt, $dump, $pass) = split;
-  next if $dev =~ /^#/;
-  if ($mnt eq '/' || $mnt eq '/rootback' || $mnt =~ /^\/NOFUTURE/) {
-    my $dn = substr($dev, 5, length($dev)-6);	# Device Name without /dev/
-    push(@spndl, $dn) unless grep($_ eq $dn, @spndl);
-    $rsp = $dn if $mnt eq '/';
-    next if $mnt =~ /^\/NOFUTURE/;
-  }
-  # Move /rootback from partition e to a
-  if ($mnt =~ /^\/rootback/) {
-    $dev =~ s/e$/a/;
-    $pass = 1;
-    $rbsp = substr($dev, 5, length($dev)-6);
-    print FSOUT "$dev\t\t$mnt\t$fstyp\t$opt\t\t$dump\t$pass\n";
-    next;
-  }
-  # Move non-root filesystems on smallest spindle into Vinum
-  if (defined($rsp) &amp;&amp; $dev =~ /^\/dev\/$rsp/ &amp;&amp; $dev =~ /[d-h]$/) {
-    $pass = $nxtpas++;
-    print FSOUT "/dev/vinum$mnt\t\t$mnt\t\t$fstyp\t$opt\t\t$dump\t$pass\n";
-    $vols{$dev}->{mnt} = substr($mnt, 1);
-    next;
-  }
-  print FSOUT $_;
-}
-close(FSOUT);
-die("Found more spindles than we have abstract names\n") if $#spndl > $#drv;
-die("Didn't find a root partition!\n") if !defined($rsp);
-die("Didn't find a /rootback partition!\n") if !defined($rbsp);
-
-# Table of server's Degraded Modes
-# One row per mode with hash keys
-#   fn	FileName
-#   xpr	eXPRession needed to convert fstab lines for this mode
-#   cm1	CoMment 1 describing this mode
-#   cm2	CoMment 2 describing this mode
-#   FH  FileHandle (dynamically initialized below)
-my @DM = (
-  { cm1 => "When we only have $rsp, comment out lines using $rbsp",
-    fn  => "/etc/fstab_only_have_$rsp",
-    xpr => "s:^/dev/$rbsp:#\$&amp;:",
-  },
-  { cm1 => "When we only have $rbsp, comment out lines using $rsp and",
-    cm2 => "rootback becomes root",
-    fn  => "/etc/fstab_only_have_$rbsp",
-    xpr => "s:^/dev/$rsp:#\$&amp;: || s:/rootback:/\t:",
-  },
-  { cm1 => "When only $rsp root is bad, /rootback becomes root and",
-    cm2 => "root becomes /rootbad",
-    fn  => "/etc/fstab_${rsp}_root_bad",
-    xpr => "s:\t/\t:\t/rootbad: || s:/rootback:/\t:",
-  },
-);
-
-# Initialize output FileHandles and write comments
-foreach my $dm (@DM) {
-  my $fh = new FileHandle;
-  $fh->open(">$dm->{fn}") || die("Can't write $dm->{fn}: $!\n");
-  print $fh "# $dm->{cm1}\n" if $dm->{cm1};
-  print $fh "# $dm->{cm2}\n" if $dm->{cm2};
-  $dm->{FH} = $fh;
-}
-
-# Parse the Vinum version of fstab written above and write versions needed
-# for server's degraded modes.
-open(FSOUT, "$fsout") || die("Couldn't open $fsout: $!\n");
-while (&lt;FSOUT>) {
-  my $line = $_;
-  foreach my $dm (@DM) {
-    $_ = $line;
-    eval $dm->{xpr};
-    print {$dm->{FH}} $_;
-  }
-}
-
-# Parse partition table for each spindle and write versions needed for Vinum
-my $rootsiz;	# ROOT partition SIZe
-my $swapsiz;	# SWAP partition SIZe
-my $rspminoff;	# Root SPindle MINimum OFFset of non-root, non-swap, non-c parts
-my $rspsiz;	# Root SPindle SIZe
-my $rbspsiz;	# RootBack SPindle SIZe
-foreach my $i (0..$#spndl) {
-  my $dlin = "disklabel $spndl[$i] |";
-#  my $dlin = "simu/disklabel.$spndl[$i]";
-  open(DLIN, "$dlin") || die("Couldn't open $dlin: $!\n");
-
-  my $dlout = "disklabel.$spndl[$i]";
-  open(DLOUT, ">$dlout") || die("Couldn't open $dlout for writing: $!\n");
-
-  my $dlb4 = "$dlout.b4vinum";
-  open(DLB4, ">$dlb4") || die("Couldn't open $dlb4 for writing: $!\n");
-
-  my $minoff;		# MINimum OFFset of non-root, non-swap, non-c partitions
-  my $totsiz = 0;	# TOTal SIZe of all non-root, non-swap, non-c partitions
-  my $swapspndl = 0;	# True if SWAP partition on this SPiNDLe
-  while (&lt;DLIN>) {
-    print DLB4 $_;
-    my ($part, $siz, $off, $fstyp, $fsiz, $bsiz, $bps) = split;
-
-    if ($part &amp;&amp; $part eq 'a:' &amp;&amp; $spndl[$i] eq $rsp) {
-	$rootsiz = $siz;
-    }
-    if ($part &amp;&amp; $part eq 'e:' &amp;&amp; $spndl[$i] eq $rbsp) {
-      if ($rootsiz != $siz) {
-	die("Rootback size ($siz) != root size ($rootsiz)\n");
-      }
-    }
-    if ($part &amp;&amp; $part eq 'c:') {
-      $rspsiz  = $siz if $spndl[$i] eq $rsp;
-      $rbspsiz = $siz if $spndl[$i] eq $rbsp;
-    }
-    # Make swap partition $cfgsiz sectors smaller
-    if ($part &amp;&amp; $part eq 'b:') {
-      if ($spndl[$i] eq $rsp) {
-	$swapsiz = $siz;
-      } else {
-	if ($swapsiz != $siz) {
-	  die("Swap partition sizes unequal across spindles\n");
-	}
-      }
-      printf DLOUT "%4s%9d%9d%10s\n", $part, $siz-$cfgsiz, $off, $fstyp;
-      $swapspndl = 1;
-      next;
-    }
-    # Move rootback spindle e partitions to a
-    if ($part &amp;&amp; $part eq 'e:' &amp;&amp; $spndl[$i] eq $rbsp) {
-      printf DLOUT "%4s%9d%9d%10s%9d%6d%6d\n", 'a:', $siz, $off, $fstyp,
-	$fsiz, $bsiz, $bps;
-      next;
-    }
-    # Delete non-root, non-swap, non-c partitions but note their minimum
-    # offset and total size that're needed below.
-    if ($part &amp;&amp; $part =~ /^[d-h]:$/) {
-      $minoff = $off unless $minoff;
-      $minoff = $off if $off &lt; $minoff;
-      $totsiz += $siz;
-      if ($spndl[$i] eq $rsp) {	# If doing spindle containing root
-	my $dev = "/dev/$spndl[$i]" . substr($part, 0, 1);
-	$vols{$dev}->{siz} = $siz;
-	$vols{$dev}->{off} = $off;
-	$rspminoff = $minoff;
-      }
-      next;
-    }
-    print DLOUT $_;
-  }
-  if ($swapspndl) {	# If there was a swap partition on this spindle
-    # Make a Vinum partition the size of all non-root, non-swap,
-    # non-c partitions + the size of Vinum's on-disk configuration.
-    # Set its offset so that the start of the first subdisk it contains
-    # coincides with the first filesystem we're embedding in Vinum.
-    printf DLOUT "%4s%9d%9d%10s\n", "$vip:", $totsiz+$cfgsiz, $minoff-$cfgsiz,
-      'vinum';
-  } else {
-    # No need to mess with size and offset if there was no swap
-    printf DLOUT "%4s%9d%9d%10s\n", "$vip:", $totsiz, $minoff,
-      'vinum';
-  }
-}
-die("Swap partition not found\n") unless $swapsiz;
-die("Swap partition not larger than $cfgsiz blocks\n") unless $swapsiz>$cfgsiz;
-die("Rootback spindle size not >= root spindle size\n") unless $rbspsiz>=$rspsiz;
-
-# Generate input to vinum create command needed for each spindle.
-foreach my $i (0..$#spndl) {
-  my $cfn = "create.$drv[$i]";	# Create File Name
-  open(CF, ">$cfn") || die("Can't open $cfn for writing: $!\n");
-  print CF "drive $drv[$i] device /dev/$spndl[$i]$vip\n";
-  next unless $spndl[$i] eq $rsp || $spndl[$i] eq $rbsp;
-  foreach my $dev (keys(%vols)) {
-    my $mnt = $vols{$dev}->{mnt};
-    my $siz = $vols{$dev}->{siz};
-    my $off = $vols{$dev}->{off}-$rspminoff+$cfgsiz;
-    print CF "volume $mnt\n" if $spndl[$i] eq $rsp;
-    print CF &lt;&lt;EOF;
-  plex name $mnt.p$i org concat volume $mnt
-    sd name $mnt.p$i.s0 drive $drv[$i] plex $mnt.p$i len ${siz}s driveoffset ${off}s
-EOF
-  }
-}</programlisting>
-  </appendix>
-
-  <appendix id="ManualBoot">
-    <title>Manual Vinum Bootstrapping</title>
-
-    <para>The <literal>bootvinum</literal> Perl script in <xref linkend="Perl"/> makes life easier, but
-      it may be necessary to manually perform some or all of the steps that
-      it automates.
-      This appendix describes how you would manually mimic the script.</para>
-
-    <procedure>
-      <step>
-	<para>Make a copy of <filename>/etc/fstab</filename>
-	  to be customized.</para>
-
-	<screen>&prompt.root; <userinput>cp /etc/fstab /etc/fstab.vinum</userinput></screen>
-      </step>
-
-      <step>
-	<para>Edit <filename>/etc/fstab.vinum</filename>.</para>
-
-	<substeps>
-	  <step>
-	    <para>Change the <literal>device</literal> column of
-	      non-root partitions on the root spindle to
-	      <filename>/dev/vinum/mnt</filename>.</para></step>
-
-	  <step>
-	    <para>Change the <literal>pass</literal> column of
-	      non-root partitions on the root spindle to <userinput>2</userinput>,
-	      <userinput>3</userinput>, etc.</para></step>
-
-	  <step>
-	    <para>Delete any lines with mountpoint
-	      matching <filename>/NOFUTURE*</filename>.</para></step>
-
-	  <step>
-	    <para>Change the <literal>device</literal> column of
-	      <filename>/rootback</filename>
-	      from <literal>e</literal> to
-	      <literal>a</literal>.</para></step>
-
-	  <step>
-	    <para>Change the <literal>pass</literal> column of
-	      <filename>/rootback</filename> to
-	      <userinput>1</userinput>.</para></step>
-
-	</substeps>
-      </step>
-
-      <step>
-	<para>Prepare disklabels for editing:</para>
-
-	<screen>&prompt.root; <userinput>cd /bootvinum</userinput>
-&prompt.root; <userinput>disklabel ad0s1 > disklabel.ad0s1</userinput>
-&prompt.root; <userinput>cp disklabel.ad0s1 disklabel.ad0s1.b4vinum</userinput>
-&prompt.root; <userinput>disklabel ad2s1 > disklabel.ad2s1</userinput>
-&prompt.root; <userinput>cp disklabel.ad2s1 disklabel.ad2s1.b4vinum</userinput></screen>
-      </step>
-
-      <step>
-	<para>Edit <filename>/etc/disklabel.ad?s1</filename>.</para>
-
-	<substeps>
-	  <step>
-	    <para>On the root spindle:</para>
-
-	    <substeps>
-	      <step>
-		<para>Decrease the <literal>size</literal> of the
-		  <literal>b</literal> partition by 265 blocks.</para></step>
-
-	      <step>
-		<para>Note the <literal>size</literal> and
-		  <literal>offset</literal> of the <literal>a</literal> and
-		  <literal>b</literal> partitions.</para></step>
-
-	      <step>
-		<para>Note the smallest <literal>offset</literal> for partitions
-		  <literal>d</literal>-<literal>h</literal>.</para></step>
-
-	      <step>
-		<para>Note the <literal>size</literal> and
-		  <literal>offset</literal> for all non-root, non-swap
-		  partitions (<filename>/home</filename> was probably on
-		  <literal>e</literal> and <filename>/usr</filename> was
-		  probably on <literal>f</literal>).</para></step>
-
-	      <step>
-		<para>Delete partitions
-		  <literal>d</literal>-<literal>h</literal>.</para></step>
-
-	      <step>
-		<para>Create a new <literal>h</literal> partition with
-		  <literal>offset</literal> 265 blocks less than the
-		  smallest <literal>offset</literal>
-		  for partitions <literal>d</literal>-<literal>h</literal>
-		  noted above.
-		  Set its <literal>size</literal> to the <literal>size</literal>
-		  of the <literal>c</literal> partition less the
-		  smallest <literal>offset</literal>
-		  for partitions <literal>d</literal>-<literal>h</literal>
-		  noted above + 265 blocks.</para>
-
-		<note>
-		  <para><application>Vinum</application>
-		    can use any partition other than <literal>c</literal>.
-		    It is not strictly necessary to use <literal>h</literal>
-		    for all your <application>Vinum</application>
-		    partitions, but it is good practice to
-		    be consistent across all spindles.</para></note>
-	      </step>
-
-	      <step>
-		<para>Set the <literal>fstype</literal> of this new
-		  partition to <userinput>vinum</userinput>.</para></step>
-	    </substeps>
-	  </step>
-
-	  <step>
-	    <para>On the rootback spindle:</para>
-
-	    <substeps>
-	      <step>
-		<para>Move the <literal>e</literal> partition to
-		  <literal>a</literal>.</para></step>
-
-	      <step>
-		<para>Verify that the <literal>size</literal> of the
-		  <literal>a</literal> and
-		  <literal>b</literal> partitions matches the
-		  root spindle.</para></step>
-
-	      <step>
-		<para>Note the smallest <literal>offset</literal> for partitions
-		  <literal>d</literal>-<literal>h</literal>.</para></step>
-
-	      <step>
-		<para>Delete partitions
-		  <literal>d</literal>-<literal>h</literal>.</para></step>
-
-	      <step>
-		<para>Create a new <literal>h</literal> partition with
-		  <literal>offset</literal> 265 blocks less than the
-		  smallest <literal>offset</literal>
-		  noted above for partitions
-		  <literal>d</literal>-<literal>h</literal>.
-		  Set its <literal>size</literal> to the <literal>size</literal>
-		  of the <literal>c</literal> partition less the
-		  smallest <literal>offset</literal>
-		  for partitions <literal>d</literal>-<literal>h</literal>
-		  noted above + 265 blocks.</para></step>
-
-	      <step>
-		<para>Set the <literal>fstype</literal> of this new
-		  partition to <userinput>vinum</userinput>.</para></step>
-	    </substeps>
-	  </step>
-
-	</substeps>
-      </step>
-
-      <step>
-	<para>Create a file named
-	  <filename>create.YouCrazy</filename> that contains:</para>
-
-	<programlisting>drive YouCrazy device /dev/ad0s1h
-volume home
-  plex name home.p0 org concat volume home
-    sd name home.p0.s0 drive YouCrazy plex home.p0 len $hl driveoffset $ho
-volume usr
-  plex name usr.p0 org concat volume usr
-    sd name usr.p0.s0 drive YouCrazy plex usr.p0 len $ul driveoffset $uo</programlisting>
-
-	<para>Where:</para>
-	<itemizedlist>
-	  <listitem><para>
-	    <literal>$hl</literal> is the length noted above for
-	    <filename>/home</filename>.</para></listitem>
-
-	  <listitem><para>
-	    <literal>$ho</literal> is the offset noted above for
-	    <filename>/home</filename> less the smallest offset
-	    noted above + 265 blocks.</para></listitem>
-
-	  <listitem><para>
-	    <literal>$ul</literal> is the length noted above for
-	    <filename>/usr</filename>.</para></listitem>
-
-	  <listitem><para>
-	    <literal>$uo</literal> is the offset noted above for
-	    <filename>/usr</filename> less the smallest offset
-	    noted above + 265 blocks.</para></listitem>
-	</itemizedlist>
-      </step>
-
-      <step>
-	<para>Create a file named
-	  <filename>create.UpWindow</filename> containing:</para>
-
-	<programlisting>drive UpWindow device /dev/ad2s1h
-  plex name home.p1 org concat volume home
-    sd name home.p1.s0 drive UpWindow plex home.p1 len $hl driveoffset $ho
-  plex name usr.p1 org concat volume usr
-    sd name usr.p1.s0 drive UpWindow plex usr.p1 len $ul driveoffset $uo</programlisting>
-
-	<para>Where <literal>$hl</literal>, <literal>$ho</literal>, <literal>$ul</literal>, and <literal>$uo</literal> are set as above.</para>
-      </step>
-    </procedure>
-  </appendix>
-
-  <appendix id="Acknowledgements">
-    <title>Acknowledgements</title>
-
-    <para>I would like to thank Greg Lehey for writing &vinum.ap; and for
-      providing very helpful comments on early drafts.
-      Several others made helpful suggestions after reviewing later drafts
-      including
-      Dag-Erling Sm&oslash;rgrav,
-      Michael Splendoria,
-      Chern Lee,
-      Stefan Aeschbacher,
-      Fleming Froekjaer,
-      Bernd Walter,
-      Aleksey Baranov, and
-      Doug Swarin.</para>
-  </appendix>
-</article>
diff --git a/en_US.ISO8859-1/articles/zip-drive/Makefile b/en_US.ISO8859-1/articles/zip-drive/Makefile
deleted file mode 100644
index b275408717..0000000000
--- a/en_US.ISO8859-1/articles/zip-drive/Makefile
+++ /dev/null
@@ -1,16 +0,0 @@
-#
-# $FreeBSD$
-#
-# Article: IOmega ZIP Drives
-
-DOC?= article
-
-FORMATS?= html
-
-INSTALL_COMPRESSED?=gz
-INSTALL_ONLY_COMPRESSED?=
-
-SRCS=	article.sgml
-
-DOC_PREFIX?= ${.CURDIR}/../../..
-.include "${DOC_PREFIX}/share/mk/doc.project.mk"
diff --git a/en_US.ISO8859-1/articles/zip-drive/article.sgml b/en_US.ISO8859-1/articles/zip-drive/article.sgml
deleted file mode 100644
index ecdad44243..0000000000
--- a/en_US.ISO8859-1/articles/zip-drive/article.sgml
+++ /dev/null
@@ -1,289 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1" standalone="no"?>
-<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V4.2-Based Extension//EN"
-	"../../../share/sgml/freebsd42.dtd" [
-<!ENTITY % entities PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Entity Set//EN" "../../share/sgml/entities.ent">
-%entities;
-]>
-
-<!-- $FreeBSD$ -->
-
-<article lang='en'>
-  <articleinfo>
-    <title>&iomegazip; Drives</title>
-
-    <authorgroup>
-      <author>
-	<firstname>Jason</firstname>
-	<surname>Bacon</surname>
-
-	<affiliation>
-	  <address><email>acadix@execpc.com</email></address>
-	</affiliation>
-      </author>
-    </authorgroup>
-
-    <legalnotice id="trademarks" role="trademarks">
-      &tm-attrib.freebsd;
-      &tm-attrib.adaptec;
-      &tm-attrib.iomega;
-      &tm-attrib.microsoft;
-      &tm-attrib.opengroup;
-      &tm-attrib.general;
-    </legalnotice>
-
-    <pubdate>$FreeBSD$</pubdate>
-
-    <releaseinfo>$FreeBSD$</releaseinfo>
-  </articleinfo>
-
-  <sect1>
-    <title>&iomegazip; Drive Basics</title>
-
-    <para>&iomegazip; disks are high capacity, removable, magnetic disks, which can be
-      read or written by ZIP drives from IOMEGA corporation.  ZIP disks are
-      similar to floppy disks, except that they are much faster, and have a
-      much greater capacity.  While floppy disks typically hold 1.44
-      megabytes, ZIP disks are available in two sizes, namely 100 megabytes
-      and 250 megabytes.  ZIP drives should not be confused with the
-      super-floppy, a 120 megabyte floppy drive which also handles traditional
-      1.44 megabyte floppies.</para>
-
-    <para>IOMEGA also sells a higher capacity, higher performance drive called
-      the &jaz;/JAZZ drive.  Jaz drives come in 1 gigabyte and 2 gigabyte
-      sizes.</para>
-
-    <para>ZIP drives are available as internal or external units, using one of
-      three interfaces:</para>
-
-    <orderedlist>
-      <listitem>
-	<para>The SCSI (Small Computer Standard Interface) interface is the
-	  fastest, most sophisticated, most expandable, and most expensive
-	  interface.  The SCSI interface is used by all types of computers
-	  from PC's to RISC workstations to minicomputers, to connect all
-	  types of peripherals such as disk drives, tape drives, scanners, and
-	  so on.  SCSI ZIP drives may be internal or external, assuming your
-	  host adapter has an external connector.</para>
-
-	<note>
-	  <para>If you are using an external SCSI device, it is important
-	    never to connect or disconnect it from the SCSI bus while the
-	    computer is running.  Doing so may cause file-system damage on the
-	    disks that remain connected.</para>
-	</note>
-
-	<para>If you want maximum performance and easy setup, the SCSI
-	  interface is the best choice.  This will probably require adding a
-	  SCSI host adapter, since most PC's (except for high-performance
-	  servers) do not have built-in SCSI support.  Each SCSI host adapter
-	  can support either 7 or 15 SCSI devices, depending on the
-	  model.</para>
-
-	<para>Each SCSI device has its own controller, and these
-	  controllers are fairly intelligent and well standardized, (the
-	  second `S' in SCSI is for Standard) so from the operating system's
-	  point of view, all SCSI disk drives look about the same, as do all
-	  SCSI tape drives, etc.  To support SCSI devices, the operating
-	  system need only have a driver for the particular host adapter, and
-	  a generic driver for each type of device, i.e. a SCSI disk driver,
-	  SCSI tape driver, and so on.  There are some SCSI devices that can
-	  be better utilized with specialized drivers (e.g. DAT tape drives),
-	  but they tend to work OK with the generic driver, too.  It is just
-	  that the generic drivers may not support some of the special
-	  features.</para>
-
-	<para>Using a SCSI zip drive is simply a matter of determining which
-	  device file in the <filename>/dev</filename> directory represents
-	  the ZIP drive. This can be determined by looking at the boot
-	  messages while FreeBSD is booting (or in
-	  <filename>/var/log/messages</filename> after booting), where you
-	  will see a line something like this:</para>
-
-	<programlisting>da1: &lt;IOMEGA ZIP 100 D.13&gt; Removable Direct Access SCSI-2 Device</programlisting>
-
-	<para>This means that the ZIP drive is represented by the file
-	  <filename>/dev/da1</filename>.</para>
-      </listitem>
-
-      <listitem>
-	<para>The IDE (Integrated Drive Electronics) interface is a low-cost
-	  disk drive interface used by many desktop PC's.  Most IDE devices
-	  are strictly internal.</para>
-
-	<para>Performance of IDE ZIP drives is comparable to SCSI ZIP drives.
-	  (The IDE interface is not as fast as SCSI, but ZIP drives
-	  performance is limited mainly by the mechanics of the drive, not by
-	  the bus interface.)</para>
-
-	<para>The drawback of the IDE interface is the limitations it imposes.
-	  Most IDE adapters can only support 2 devices, and IDE interfaces are
-	  not typically designed for the long term. For example, the original
-	  IDE interface would not support hard disks with more than 1024
-	  cylinders, which forced a lot of people to upgrade their hardware
-	  prematurely.  If you have plans to expand your PC by adding another
-	  disk, a tape drive, or scanner, you may want to invest in a SCSI
-	  host adapter and a SCSI ZIP drive to avoid problems in the
-	  future.</para>
-
-	<para>IDE devices in FreeBSD are prefixed with an <literal>a</literal>.
-	  For example, an IDE hard disk might be
-	  <filename>/dev/ad0</filename>, an IDE (ATAPI) CDROM might be
-	  <filename>/dev/acd1</filename>, and so on.</para>
-      </listitem>
-
-      <listitem>
-	<para>The parallel port interface is popular for portable external
-	  devices such as external ZIP drives and scanners, because virtually
-	  every computer has a standard parallel port (usually used for
-	  printers).  This makes things easy for people to transfer data
-	  between multiple computers by toting around their ZIP drive.</para>
-
-	<para>Performance will generally be slower than a SCSI or IDE ZIP
-	  drive, since it is limited by the speed of the parallel port.
-	  Parallel port speed varies considerably between various computers,
-	  and can often be configured in the system BIOS.  Some machines will
-	  also require BIOS configuration to operate the parallel port in
-	  bidirectional mode.  (Parallel ports were originally designed only
-	  for output to printers)</para>
-      </listitem>
-    </orderedlist>
-  </sect1>
-
-  <sect1>
-    <title>Parallel ZIP: The <devicename>vpo</devicename> Driver</title>
-
-    <para>To use a parallel-port ZIP drive under FreeBSD, the
-      <devicename>vpo</devicename> driver must be configured into the kernel.
-      Parallel port ZIP drives also have a built-in SCSI controller. The vpo
-      driver allows the FreeBSD kernel to communicate with the ZIP drive's
-      SCSI controller through the parallel port.</para>
-
-    <para>Since the vpo driver is not a standard part of the kernel (as of
-      FreeBSD 3.2), you will need to rebuild the kernel to enable this device.
-      The process of building a kernel is outlined in detail in the
-      <ulink url="&url.books.handbook;/kernelconfig.html">&os; Handbook</ulink>.
-      The following steps outline the process in brief for the
-      purpose of enabling the vpo driver:</para>
-
-    <orderedlist>
-      <listitem>
-	<para>Run <command>/stand/sysinstall</command>, and install the kernel
-	  source code on your system.</para>
-      </listitem>
-
-      <listitem>
-	<para>Create a custom kernel configuration, that includes the
-	  driver for the vpo driver:</para>
-
-	<screen>&prompt.root; <userinput>cd /sys/i386/conf</userinput>
-&prompt.root; <userinput>cp GENERIC MYKERNEL</userinput></screen>
-
-	<para>Edit <filename>MYKERNEL</filename>, change the
-	  <literal>ident</literal> line to <literal>MYKERNEL</literal>, and
-	  uncomment the line describing the vpo driver.</para>
-
-	<para>If you have a second parallel port, you may need to copy the
-	  section for <literal>ppc0</literal> to create a
-	  <literal>ppc1</literal> device.  The second parallel port usually
-	  uses IRQ 5 and address 378.  Only the IRQ is required in the config
-	  file.</para>
-
-	<para>If your root hard disk is a SCSI disk, you might run into a
-	  problem with probing order, which will cause the system to attempt
-	  to use the ZIP drive as the root device.  This will cause a boot
-	  failure, unless you happen to have a FreeBSD root file-system on
-	  your ZIP disk!  In this case, you will need to <quote>wire
-	    down</quote> the root disk, i.e. force the kernel to bind a
-	  specific device to <filename>/dev/da0</filename>, the root SCSI
-	  disk.  It will then assign the ZIP disk to the next available SCSI
-	  disk, e.g. <literal>/dev/da1</literal>. To wire down your SCSI hard
-	  drive as <literal>da0</literal>, change the line
-
-	  <programlisting>device  da0</programlisting>
-
-	  to
-
-	  <programlisting>disk da0 at scbus0 target 0 unit 0</programlisting></para>
-
-	<para>You may need to change the target above to match the SCSI ID of
-	  your disk drive. You should also wire down the scbus0 entry to your
-	  controller.  For example, if you have an &adaptec; 15xx controller,
-	  you would change
-
-	  <programlisting>controller scbus0</programlisting>
-
-	  to
-
-	  <programlisting>controller scbus0 at aha0</programlisting></para>
-
-	<para>Finally, since you are creating a custom kernel configuration,
-	  you can take the opportunity to remove all the unnecessary drivers.
-	  This should be done with a great deal of caution, and only if you
-	  feel confident about making modifications to your kernel
-	  configuration. Removing unnecessary drivers will reduce the kernel
-	  size, leaving more memory available for your applications.  To
-	  determine which drivers are not needed, go to the end of the file
-	  <filename>/var/log/messages</filename>, and look for lines reading
-	  "not found". Then, comment out these devices in your config file.
-	  You can also change other options to reduce the size and increase
-	  the speed of your kernel. Read the section on rebuilding your kernel
-	  for more complete information.</para>
-      </listitem>
-
-      <listitem>
-	<para>Now it is time to compile the kernel:</para>
-
-	<screen>&prompt.root; <userinput>/usr/sbin/config MYKERNEL</userinput>
-&prompt.root; <userinput>cd ../../compile/MYKERNEL</userinput>
-&prompt.root; <userinput>make clean depend &amp;&amp; make all install</userinput></screen>
-      </listitem>
-    </orderedlist>
-
-    <para>After the kernel is rebuilt, you will need to reboot.  Make sure the
-      ZIP drive is connected to the parallel port before the boot begins. You
-      should see the ZIP drive show up in the boot messages as device vpo0 or
-      vpo1, depending on which parallel port the drive is attached to.  It
-      should also show which device file the ZIP drive has been bound to. This
-      will be <filename>/dev/da0</filename> if you have no other SCSI disks in
-      the system, or <filename>/dev/da1</filename> if you have a SCSI hard
-      disk wired down as the root device.</para>
-  </sect1>
-
-  <sect1>
-    <title>Mounting ZIP disks</title>
-
-    <para>To access the ZIP disk, you simply mount it like any other disk
-      device. The file-system is represented as slice 4 on the device, so for
-      SCSI or parallel ZIP disks, you would use:</para>
-
-    <screen>&prompt.root; <userinput>mount_msdos /dev/da1s4 /mnt</userinput></screen>
-
-    <para>For IDE ZIP drives, use:</para>
-
-    <screen>&prompt.root; <userinput>mount_msdos /dev/ad1s4 /mnt</userinput></screen>
-
-    <para>It will also be helpful to update <filename>/etc/fstab</filename> to
-      make mounting easier. Add a line like the following, edited to suit your
-      system:
-
-      <programlisting>/dev/da1s4  /zip msdos rw,noauto  0 0</programlisting>
-
-      and create the directory <filename>/zip</filename>.</para>
-
-    <para>Then, you can mount simply by typing
-
-      <screen>&prompt.root; <userinput>mount /zip</userinput></screen>
-
-      and unmount by typing
-
-      <screen>&prompt.root; <userinput>umount /zip</userinput></screen></para>
-
-    <para>For more information on the format of
-      <filename>/etc/fstab</filename>, see &man.fstab.5;.</para>
-
-    <para>You can also create a FreeBSD file-system on the ZIP disk using
-      &man.newfs.8;.  However, the disk will only be usable on a FreeBSD
-      system, or perhaps a few other &unix; clones that recognize FreeBSD
-      file-systems.  (Definitely not &ms-dos; or &windows;.)</para>
-  </sect1>
-</article>
diff --git a/en_US.ISO8859-1/books/dev-model/book.sgml b/en_US.ISO8859-1/books/dev-model/book.sgml
index 6c8398add2..e3a7053138 100644
--- a/en_US.ISO8859-1/books/dev-model/book.sgml
+++ b/en_US.ISO8859-1/books/dev-model/book.sgml
@@ -714,8 +714,7 @@
 
             <para>
                 Many committers have a special area of responsibility. These
-                roles are called hats
-                <citation><xref linkend="bsd-hats"/></citation>.
+                roles are called hats.
                 These hats can
                 be either project roles, such as public relations officer, or
                 maintainer for a certain area of the
@@ -2572,17 +2571,6 @@
             <bibliomisc role="url"><ulink url="http://election.uk.freebsd.org/candidates.html"></ulink></bibliomisc>
         </biblioentry>
 
-        <biblioentry id="bsd-hats" xreflabel="Losh, 2002">
-            <authorgroup>
-                <author><firstname>Warner</firstname><surname>Losh</surname></author>
-            </authorgroup>
-            <copyright><year>2002</year>
-                <holder>The FreeBSD Documentation Project</holder>
-            </copyright>
-            <title>Working with Hats</title>
-            <bibliomisc role="url"><ulink url="http://www.freebsd.org/doc/en/articles/hats/article.html"></ulink></bibliomisc>
-        </biblioentry>
-
         <biblioentry id="freebsd-handle-pr" xreflabel="FreeBSD, 2002C">
             <authorgroup>
                 <author><firstname>Dag-Erling</firstname><surname>Sm&oslash;rgrav</surname></author>
diff --git a/en_US.ISO8859-1/books/faq/book.sgml b/en_US.ISO8859-1/books/faq/book.sgml
index b130629c22..d7dd638d17 100644
--- a/en_US.ISO8859-1/books/faq/book.sgml
+++ b/en_US.ISO8859-1/books/faq/book.sgml
@@ -1310,19 +1310,6 @@
       </qandaentry>
 
       <qandaentry>
-	<question id="multiboot">
-	  <para>Can I have more than one operating system on my
-	    PC?</para>
-	</question>
-
-	<answer>
-	  <para>Have a look at <ulink
-	      url="&url.articles.multi-os;/index.html"> the multi-OS page</ulink>.
-	    </para>
-	</answer>
-      </qandaentry>
-
-      <qandaentry>
 	<question id="windows-coexist">
 	  <para>Can &windows; co-exist with &os;?</para>
 	</question>
@@ -4804,9 +4791,7 @@ kern.sched.name: 4BSD</screen>
 	    &man.sysinstall.8;, or &man.fdisk.8; and &man.disklabel.8;.
 	    You should also install booteasy on both disks with
 	    &man.boot0cfg.8;, so that you can dual boot to the old or
-	    new system after the copying is done.  See the <ulink
-	      url="&url.articles.formatting-media;/index.html">formatting-media article</ulink>
-	    for details on this process.</para>
+	    new system after the copying is done.</para>
 
 	  <para>Now you have the new disk set up, and are ready to move
 	    the data.  Unfortunately, you cannot just blindly copy the
diff --git a/en_US.ISO8859-1/htdocs/docproj/translations.sgml b/en_US.ISO8859-1/htdocs/docproj/translations.sgml
index 93824d349b..50989b9eb0 100644
--- a/en_US.ISO8859-1/htdocs/docproj/translations.sgml
+++ b/en_US.ISO8859-1/htdocs/docproj/translations.sgml
@@ -94,9 +94,6 @@
   <dd><a href="http://www.cybershade.us/freebsd/bg/fdp/split/">FreeBSD
     Documentation Project Primer for New Contributors</a></dd>
 
-  <dd><a href="http://www.cybershade.us/freebsd/bg/multi-os/">Installing and
-    Using FreeBSD With Other Operating Systems</a></dd>
-
   <dt><i>Documents currently being worked on</i></dt>
 
   <dd>FreeBSD Handbook</dd>
diff --git a/en_US.ISO8859-1/htdocs/docs/books.sgml b/en_US.ISO8859-1/htdocs/docs/books.sgml
index 4b4cf7a49d..12dad2cb08 100644
--- a/en_US.ISO8859-1/htdocs/docs/books.sgml
+++ b/en_US.ISO8859-1/htdocs/docs/books.sgml
@@ -93,12 +93,6 @@
 
 	<!-- Articles are sorted by pathname -->
 
-	    <p><a href="&url.articles;/5-roadmap/index.html">The
-	        Roadmap for 5-STABLE</a> (5-roadmap)<br/>
-	      Describes medium-term development and release engineering
-	        plans leading to the 5-STABLE branch point.  This
-	        article is primarily of historical interest.</p>
-
           <p><a href="&url.articles;/bsdl-gpl/index.html">Why you should use
               a BSD style license for your Open Source Project</a> (bsdl-gpl)<br/>
               Describes the benefits of releasing code under a BSD
@@ -111,12 +105,6 @@
 	    <p><a href="&url.articles;/casestudy-argentina.com/index.html">Argentina.com : A Case Study</a> (casestudy-argentina.com)<br/>
 	      How FreeBSD helped a large ISP in Latin America.</p>
 
-	    <p><a href="&url.articles;/checkpoint/index.html">Integration
-	        of Checkpoint VPN-1/Firewall-1 and FreeBSD IPsec</a>
-	        (checkpoint)<br/>
-	      How to configure Checkpoint VPN-1/Firewall-1 and FreeBSD
-	        IPsec.</p>
-
 	    <p><a href="&url.articles;/committers-guide/index.html">The
 	        Committer's Guide</a> (committers-guide)<br/>
 		Introductory information for FreeBSD committers.</p>
@@ -166,15 +154,6 @@
 	      An article with some tips about the subtleties of
 	        CVSup.</p>
 
-	    <p><a href="&url.articles;/dialup-firewall/index.html">Dialup
-		firewalling with FreeBSD</a> (dialup-firewall)<br/>
-	      How to set up a firewall using PPP and ipfw over a dialup link
-		with dynamically assigned IP addresses.</p>
-
-	    <p><a href="&url.articles;/diskless-x/index.html">Creating
-	        a diskless X server</a> (diskless-x)<br/>
-	      How to create a diskless X server.</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
@@ -200,11 +179,6 @@
 	      A description of the various font technologies in FreeBSD, and
 		how to use them with different programs.</p>
 
-	    <p><a href="&url.articles;/formatting-media/index.html">Formatting
-	        media on FreeBSD</a> (formatting-media)<br/>
-	      How to slice, partition, and format fixed and removable media on
-		FreeBSD.</p>
-
 	    <p><a href="&url.articles;/freebsd-questions/index.html">How
 	        to get the best results from the FreeBSD-questions mailing list</a>
 	        (freebsd-questions)<br/>
@@ -227,12 +201,6 @@
 	      A guide to create UFS partitions configured with journaling
 		for desktop use.</p>
 
-	    <p><a href="&url.articles;/hats/index.html">Working with Hats</a>
-	        (hats)<br/>
-	      A committer's guide to working with ``hats'' (other
-	        committers with authority over specific areas of
-		FreeBSD).</p>
-
 	    <p><a href="&url.articles;/hubs/index.html">Mirroring FreeBSD</a>
 	        (hubs)
 	      <br/>The all in one guide for mirroring the FreeBSD website,
@@ -278,11 +246,6 @@
 	      An introduction to using the MH mail reader on
 		FreeBSD.</p>
 
-	    <p><a href="&url.articles;/multi-os/index.html">Using
-	        FreeBSD with other operating systems</a> (multi-os)<br/>
-	      How to install FreeBSD alongside one or more different operating
-		systems on the same computer.</p>
-
 	    <p><a href="&url.articles;/nanobsd/index.html">Introduction
                 to NanoBSD</a> (nanobsd)<br/>
 	      Information about the NanoBSD tools, which can be used to
@@ -378,35 +341,11 @@
 	        and Solid State Devices</a> (solid-state)<br/>
 	      The use of solid state disk devices in FreeBSD.</p>
 
-	    <p><a href="&url.articles;/storage-devices/index.html">Storage Devices</a>
-	        (storage-devices)<br/>
-	      Detailed information about using storage devices with FreeBSD,
-		including ESDI disks, and SCSI disks, tape drives, and CDROM
-		drives.</p>
-
-	    <p><a href="&url.articles;/version-guide/index.html">Choosing the
-		FreeBSD Version That Is Right For You</a> (version-guide)<br/>
-	      How to decide which version of FreeBSD is right for your
-		needs.  Topics include the releases, branches, the difference
-		between -CURRENT and -STABLE, and the current scheduling goals
-		of the project.</p>
-
-	    <p><a href="&url.articles;/vinum/index.html">Bootstrapping
-	       Vinum: A Foundation for Reliable Servers</a> (vinum)<br/>
-	       A gentle introduction to failure-resilient servers and
-		step-by-step instructions for building one with Vinum.</p>
-
 	    <p><a href="&url.articles;/vm-design/index.html">Design
 	      elements of the FreeBSD VM system</a> (vm-design)<br/>
 	      An easy to follow description of the design of the FreeBSD
 	        virtual memory system.</p>
 
-	    <p><a href="&url.articles;/zip-drive/index.html">Zip-drives
-	        and FreeBSD</a> (zip-drive)<br/>
-	      How to format, mount, and use an Iomega Zip (SCSI, IDE, or
-		parallel) Drive on FreeBSD.</p>
-
-
     <h2>On other web sites</h2>
 
     <p>Various independent efforts have also produced a great deal of useful
diff --git a/en_US.ISO8859-1/htdocs/news/2000/index.sgml b/en_US.ISO8859-1/htdocs/news/2000/index.sgml
index 46d660d774..7f19016175 100644
--- a/en_US.ISO8859-1/htdocs/news/2000/index.sgml
+++ b/en_US.ISO8859-1/htdocs/news/2000/index.sgml
@@ -278,7 +278,7 @@
 	href="http://www.jp.FreeBSD.org/">http://www.jp.FreeBSD.org/</a>.</p>
 
 	<p>A new article is available, explaining how to <a
-	  href="&base;/tutorials/dialup-firewall/index.html">use PPP, natd,
+	  href="http://docs.freebsd.org/doc/9.0-RELEASE/usr/share/doc/freebsd/en_US.ISO8859-1/articles/dialup-firewall/index.html">use PPP, natd,
 	  and ipfw</a> to implement a firewall with a PPP dialup
 	  connection.</p>
 
diff --git a/en_US.ISO8859-1/htdocs/news/2001/news.xml b/en_US.ISO8859-1/htdocs/news/2001/news.xml
index 9187d602b8..66b2627224 100644
--- a/en_US.ISO8859-1/htdocs/news/2001/news.xml
+++ b/en_US.ISO8859-1/htdocs/news/2001/news.xml
@@ -295,7 +295,7 @@
 	  <title>Bootstrapping Vinum: A Foundation for Reliable Servers</title>
 	  <p><a href="mailto:Bob@BGPBook.Com">Bob Van Valzah</a> has submitted
 	    an article introducing <a
-	    href="&base;/doc/en_US.ISO8859-1/articles/vinum/index.html">
+	    href="http://docs.freebsd.org/doc/9.0-RELEASE/usr/share/doc/freebsd/en_US.ISO8859-1/articles/vinum/index.html">
 	    failure-resilient servers and step-by-step instructions
             for building one with Vinum</a>.</p>
 	</event>
diff --git a/en_US.ISO8859-1/htdocs/news/2002/news.xml b/en_US.ISO8859-1/htdocs/news/2002/news.xml
index 00154dad44..6227b87dc7 100644
--- a/en_US.ISO8859-1/htdocs/news/2002/news.xml
+++ b/en_US.ISO8859-1/htdocs/news/2002/news.xml
@@ -809,7 +809,7 @@
 
           <p>Aaron Kaplan has submitted a new article explaining how to
             adjust your system configuration to use the new <a
-              href="&base;/doc/en_US.ISO8859-1/articles/euro/article.html">Euro
+              href="http://docs.freebsd.org/doc/9.0-RELEASE/usr/share/doc/freebsd/en_US.ISO8859-1/articles/euro/index.html">Euro
               symbol on FreeBSD</a>.</p>
         </event>
       </day>
diff --git a/en_US.ISO8859-1/htdocs/news/2005/news.xml b/en_US.ISO8859-1/htdocs/news/2005/news.xml
index 99b48acd8c..66b4737d85 100644
--- a/en_US.ISO8859-1/htdocs/news/2005/news.xml
+++ b/en_US.ISO8859-1/htdocs/news/2005/news.xml
@@ -409,7 +409,7 @@
 	  <title>New Article: Choosing a FreeBSD Version</title>
 
 	  <p>A new article, <a
-	    href="&base;/doc/en_US.ISO8859-1/articles/version-guide/">
+	    href="http://docs.freebsd.org/doc/9.0-RELEASE/usr/share/doc/freebsd/en_US.ISO8859-1/articles/version-guide/index.html">
 	    Choosing the FreeBSD Version That Is Right For You</a>,
 	    discusses considerations that should go into the selection
 	    of the most suitable version of FreeBSD for individual needs.
diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2003-01-2003-02.xml b/en_US.ISO8859-1/htdocs/news/status/report-2003-01-2003-02.xml
index ba8aab7bd1..69f0ca4572 100644
--- a/en_US.ISO8859-1/htdocs/news/status/report-2003-01-2003-02.xml
+++ b/en_US.ISO8859-1/htdocs/news/status/report-2003-01-2003-02.xml
@@ -20,8 +20,8 @@
       projects.  FreeBSD 5.1 is expected to ship in late May or early
       June, with 5.2 following at the end of summer.  A roadmap for
       the push to 5-STABLE is available at <a
-      href="http://www.FreeBSD.org/doc/en/articles/5-roadmap">
-      http://www.FreeBSD.org/doc/en/articles/5-roadmap</a>.  Although
+      href="http://docs.freebsd.org/doc/5.2-RELEASE/usr/share/doc/en_US.ISO8859-1/articles/5-roadmap/index.html">
+      http://docs.freebsd.org/doc/5.2-RELEASE/usr/share/doc/en_US.ISO8859-1/articles/5-roadmap/index.html</a>.  Although
       the 5.x series isn't expected to fully stabilize until the 5.2
       release, 5.1 promises to be an exciting release and a significant
       improvement over 5.0 in terms of speed and stability.</p>
diff --git a/en_US.ISO8859-1/htdocs/projects/newbies.sgml b/en_US.ISO8859-1/htdocs/projects/newbies.sgml
index 0b504f1ea5..6a25db21ce 100644
--- a/en_US.ISO8859-1/htdocs/projects/newbies.sgml
+++ b/en_US.ISO8859-1/htdocs/projects/newbies.sgml
@@ -53,11 +53,7 @@
     <h2><a name="fbsd">Learning about &os;</a></h2>
 
     <ul>
-      <li><p>If you have not yet installed, and have not yet decided
-	  which version of &os; is the best for your needs, the <a
-	  href="&url.articles;/version-guide/index.html">Choosing
-	  the &os; Version That Is Right For You</a> article is meant
-	  to help you to decide.  You should most probably look for the
+      <li><p>You should most probably look for the
 	  <a href="&u.rel.announce;">latest mainstream release</a>.
           (See the Handbook for why you should <strong>not</strong> be tempted
           by any of the other branches.) Before you begin, carefully read the
diff --git a/en_US.ISO8859-1/htdocs/releases/5.1R/early-adopter.html b/en_US.ISO8859-1/htdocs/releases/5.1R/early-adopter.html
index ea045d1811..54b02670b2 100644
--- a/en_US.ISO8859-1/htdocs/releases/5.1R/early-adopter.html
+++ b/en_US.ISO8859-1/htdocs/releases/5.1R/early-adopter.html
@@ -167,7 +167,7 @@
          target="_top">``FreeBSD Release Engineering''</a> article.
         Specific issues for the upcoming 5-STABLE development
         branch can be found in <a
-        href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/5-roadmap/index.html"
+        href="http://docs.freebsd.org/doc/5.1-RELEASE/usr/share/doc/en_US.ISO8859-1/articles/5-roadmap/index.html"
          target="_top">``The Roadmap for 5-STABLE''</a>.</p>
       </div>
 
diff --git a/en_US.ISO8859-1/htdocs/releases/5.1R/schedule.sgml b/en_US.ISO8859-1/htdocs/releases/5.1R/schedule.sgml
index 516209ed7a..15e296f62c 100644
--- a/en_US.ISO8859-1/htdocs/releases/5.1R/schedule.sgml
+++ b/en_US.ISO8859-1/htdocs/releases/5.1R/schedule.sgml
@@ -36,7 +36,7 @@
 
 <p>FreeBSD 5.1 will continue to be released from the 5-CURRENT development
   stream.  For more details about the milestones for reaching
-  5-STABLE, see the <a href="&base;/doc/en/articles/5-roadmap">5-STABLE
+  5-STABLE, see the <a href="http://docs.freebsd.org/doc/5.1-RELEASE/usr/share/doc/en_US.ISO8859-1/articles/5-roadmap/index.html">5-STABLE
   Roadmap</a> page.</p>
 
 <p>The current release engineering <a
diff --git a/en_US.ISO8859-1/htdocs/releases/5.2.1R/early-adopter.html b/en_US.ISO8859-1/htdocs/releases/5.2.1R/early-adopter.html
index ecf20c49e8..0458ac1d48 100644
--- a/en_US.ISO8859-1/htdocs/releases/5.2.1R/early-adopter.html
+++ b/en_US.ISO8859-1/htdocs/releases/5.2.1R/early-adopter.html
@@ -141,7 +141,7 @@ pages</a> and in the <a
 href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/releng/index.html"
 target="_top">``FreeBSD Release Engineering''</a> article. Specific issues for the
 upcoming 5-STABLE development branch can be found in <a
-href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/5-roadmap/index.html"
+href="http://docs.freebsd.org/doc/5.2.1-RELEASE/usr/share/doc/en_US.ISO8859-1/articles/5-roadmap/index.html"
 target="_top">``The Roadmap for 5-STABLE''</a>.</p>
 </div>
 
diff --git a/en_US.ISO8859-1/htdocs/releases/5.2R/early-adopter.html b/en_US.ISO8859-1/htdocs/releases/5.2R/early-adopter.html
index 57a76999f3..eb8f3a9a7e 100644
--- a/en_US.ISO8859-1/htdocs/releases/5.2R/early-adopter.html
+++ b/en_US.ISO8859-1/htdocs/releases/5.2R/early-adopter.html
@@ -141,7 +141,7 @@ pages</a> and in the <a
 href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/releng/index.html"
 target="_top">``FreeBSD Release Engineering''</a> article. Specific issues for the
 upcoming 5-STABLE development branch can be found in <a
-href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/5-roadmap/index.html"
+href="http://docs.freebsd.org/doc/5.2-RELEASE/usr/share/doc/en_US.ISO8859-1/articles/5-roadmap/index.html"
 target="_top">``The Roadmap for 5-STABLE''</a>.</p>
 </div>
 
diff --git a/en_US.ISO8859-1/htdocs/releases/5.2R/schedule.sgml b/en_US.ISO8859-1/htdocs/releases/5.2R/schedule.sgml
index 5fab3ee111..6860147792 100644
--- a/en_US.ISO8859-1/htdocs/releases/5.2R/schedule.sgml
+++ b/en_US.ISO8859-1/htdocs/releases/5.2R/schedule.sgml
@@ -31,7 +31,7 @@
 
 <p>FreeBSD 5.2 will continue to be released from the 5-CURRENT development
   stream.  For more details about the milestones for reaching
-  5-STABLE, see the <a href="&base;/doc/en/articles/5-roadmap">5-STABLE
+  5-STABLE, see the <a href="http://docs.freebsd.org/doc/5.2-RELEASE/usr/share/doc/en_US.ISO8859-1/articles/5-roadmap/index.html">5-STABLE
   Roadmap</a> page.</p>
 
 <p>The current release engineering <a
diff --git a/en_US.ISO8859-1/htdocs/releng/index.sgml b/en_US.ISO8859-1/htdocs/releng/index.sgml
index 218bf622f9..b9a25fb59d 100644
--- a/en_US.ISO8859-1/htdocs/releng/index.sgml
+++ b/en_US.ISO8859-1/htdocs/releng/index.sgml
@@ -400,22 +400,6 @@
 	    ports cluster, how to split up the packages for the release
 	    media, and how to verify that a package set is
 	    consistent.</small></p></li>
-
-    <li><p><a href="&base;/doc/en_US.ISO8859-1/articles/5-roadmap/index.html">FreeBSD
-	  5-STABLE Roadmap</a><br/>
-
-	  <small>Described the roadmap for the project for reaching the RELENG_5
-	    branch.  Included overall status of 5.x, what was left to be done, and
-	    tentative schedules.  Note that this document is now mainly of
-	    historical interest.</small></p></li>
-
-    <li><p><a href="&base;/doc/en_US.ISO8859-1/articles/version-guide/index.html">Choosing
-	  the FreeBSD Version That Is Right For You</a><br/>
-
-	  <small>How to decide which version of FreeBSD is right for your
-	    needs.  Topics include the releases, branches, the difference
-	    between -CURRENT and -STABLE, and the current scheduling goals
-	    of the project.</small></p></li>
   </ul>
 
   <h2><a name="team" id="team">Release Engineering Team</a></h2>
diff --git a/es_ES.ISO8859-1/articles/Makefile b/es_ES.ISO8859-1/articles/Makefile
index 5283b3ca1b..4025d8bd32 100644
--- a/es_ES.ISO8859-1/articles/Makefile
+++ b/es_ES.ISO8859-1/articles/Makefile
@@ -5,8 +5,6 @@ SUBDIR =
 SUBDIR+= casestudy-argentina.com
 SUBDIR+= contributing
 SUBDIR+= cvs-freebsd
-SUBDIR+= dialup-firewall
-SUBDIR+= euro
 SUBDIR+= explaining-bsd
 SUBDIR+= fbsd-from-scratch
 SUBDIR+= fdp-es
@@ -19,8 +17,6 @@ SUBDIR+= p4-primer
 SUBDIR+= problem-reports
 SUBDIR+= pxe
 SUBDIR+= releng
-SUBDIR+= version-guide
-SUBDIR+= zip-drive
 
 DOC_PREFIX?= ${.CURDIR}/../..
 .include "${DOC_PREFIX}/share/mk/doc.project.mk"
diff --git a/es_ES.ISO8859-1/articles/dialup-firewall/Makefile b/es_ES.ISO8859-1/articles/dialup-firewall/Makefile
deleted file mode 100644
index 886e21cc9d..0000000000
--- a/es_ES.ISO8859-1/articles/dialup-firewall/Makefile
+++ /dev/null
@@ -1,14 +0,0 @@
-# $FreeBSD$
-
-DOC?= article
-
-FORMATS?= html
-
-INSTALL_COMPRESSED?=gz
-INSTALL_ONLY_COMPRESSED?=
-
-SRCS= article.sgml
-
-DOC_PREFIX?= ${.CURDIR}/../../..
-
-.include "${DOC_PREFIX}/share/mk/doc.project.mk"
diff --git a/es_ES.ISO8859-1/articles/dialup-firewall/article.sgml b/es_ES.ISO8859-1/articles/dialup-firewall/article.sgml
deleted file mode 100644
index 3d0ee87179..0000000000
--- a/es_ES.ISO8859-1/articles/dialup-firewall/article.sgml
+++ /dev/null
@@ -1,430 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1" standalone="no"?>
-<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V4.2-Based Extension//EN"
-	"../../../share/sgml/freebsd42.dtd" [
-<!ENTITY % entities PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Entity Set//ES" "../../share/sgml/entities.ent">
-%entities;
-]>
-
-<article lang="es">
-  <articleinfo>
-    <title>Cortafuegos con Dialup en FreeBSD</title>
-
-    <authorgroup>
-      <author>
-	<firstname>Marc</firstname>
-	<surname>Silver</surname>
-
-	<affiliation>
-	  <address><email>marcs@draenor.org</email></address>
-	</affiliation>
-      </author>
-    </authorgroup>
-
-    <pubdate>$FreeBSD$</pubdate>
-
-    <releaseinfo>$FreeBSD$</releaseinfo>
-
-    <abstract>
-      <para>En éste artículo se describe cómo
-        configurar un cortafuegos que utiliza conexión PPP con
-        FreeBSD e IPFW y más concretamente el uso de un
-        cortafuegos en una conexión telefónica
-        a la que se le asigna una IP dinámica.  Éste
-        documento no se ocupa de la configuración de la
-        conexión PPP necesaria.</para>
-	&trans.es.carvay;
-    </abstract>
-  </articleinfo>
-
-  <sect1 id="preface">
-    <title>Prefacio</title>
-
-    <para>Uso de un Cortafuegos en una Conexión Telefónica
-       en FreeBSD</para>
-
-     <para>En éste documento se expone el proceso necesario para
-       configurar un cortafuegos en FreeBSD cuando la dirección IP
-       es asignada dinámicamente por el ISP.  Aunque se ha hecho
-       todo lo posible por hacer éste documento tan informativo
-       y correcto como sea posible puede enviar comentarios y/o
-       sugerencias al autor a <email>marcs@draenor.org</email>, que
-       serán bien recibidas.</para>
-   </sect1>
-
-  <sect1 id="kernel">
-    <title>Configuración del Kernel</title>
-
-    <para>Lo primero que tendrá que hacer es recompilar su
-      kernel.  Si necesita más información sobre cómo
-      hacerlo el mejor recurso es <ulink
-	url="../../books/handbook/kernelconfig.html">la sección de
-       Handbook acerca de la configuración del
-      kernel</ulink>.  Necesitará añadir a su fichero de
-      configuración del kernel las siguientes opciones:</para>
-
-    <variablelist>
-      <varlistentry>
-	<term><literal>options IPFIREWALL</literal></term>
-
-	<listitem>
-          <para>Activa el código necesario para el cortafuegos
-            en el kernel.</para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-	<term><literal>options IPFW2</literal></term>
-
-	<listitem>
-          <para>Activa la nueva versión de IPFW.</para>
-	  <important><para>Esto solo debe hacerse en FreeBSD 4.X puesto
-          que en las versiones más recientes vienen incluído
-          por defecto.</para></important>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-	<term><literal>options IPFIREWALL_VERBOSE</literal></term>
-
-	<listitem>
-          <para>Envia los paquetes que se ha decidido sean incluídos
-            en un <filename>log</filename> a la aplicación encargada
-            de gestionar los <filename>logs</filename> del sistema.</para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-	<term><literal>options
-	    IPFIREWALL_VERBOSE_LIMIT=<replaceable>100</replaceable></literal></term>
-
-	<listitem>
-          <para>Limita el número de veces que una entrada que cumple
-            las reglas puede ser incluída en los <filename>logs
-            </filename> del sistema. Esto previene que sus <filename>logs
-            </filename> se vean inundados por entradas repetidas.
-	    <replaceable>100</replaceable> es un número razonable,
-            pero puede ajustarlo a sus necesidades.</para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-	<term><literal>options IPDIVERT</literal></term>
-
-	<listitem>
-          <para>Activa los <quote>sockets</quote> <emphasis>divert</emphasis>,
-            que serán descritos más tarde.</para>
-	</listitem>
-      </varlistentry>
-    </variablelist>
-
-    <para>Hay otras entradas <emphasis>opcionales</emphasis> que pueden
-      compilarse en el kernel para incrementar la seguridad.  No hacen
-      falta para el funcionamiento del cortafuegos pero algunos usuarios
-      especialmente paranoicos pueden querer usarlos.</para>
-
-    <variablelist>
-      <varlistentry>
-	<term><literal>options TCP_DROP_SYNFIN</literal></term>
-
-	<listitem>
-          <para>Ignorar paquetes TCP con SYN y FIN.  Esto evita ser
-           vulnerable al uso de herramientas como
-	  <filename role="package">security/nmap</filename>, que permiten
-           identificar la pila TCP/IP de la máquina, pero incumple
-           el soporte a las extensiones incluídas en el
-           RFC1644.  <emphasis>No</emphasis> se recomienda hacer tal cosa
-           si la máquina va a ejecutar un servidor web.</para>
-	</listitem>
-      </varlistentry>
-     </variablelist>
-
-    <para>No reinicie tras recompilar el kernel.  Si todo sale bien
-      sólo necesitaremos reiniciar una vez en todo el proceso
-      de instalación del cortafuegos.</para>
-  </sect1>
-
-  <sect1 id="rcconf">
-    <title>Modificación de <filename>/etc/rc.conf</filename> para
-      cargar el cortafuegos</title>
-
-    <para>Necesitamos hacer algunos cambios en
-      <filename>/etc/rc.conf</filename> para darle ciertos detalles
-      del cortafuegos.  Es tan simple como añadir las siguientes
-      líneas:</para>
-
-    <programlisting>firewall_enable="YES"
-firewall_script="/etc/firewall/fwrules"
-natd_enable="YES"
-natd_interface="tun0"
-natd_flags="-dynamic"</programlisting>
-
-    <para>Para más información sobre éstas entradas
-     consulte
-     <filename>/etc/defaults/rc.conf</filename> y lea
-      &man.rc.conf.5;</para>
-  </sect1>
-
-  <sect1>
-    <title>Desactivación de la Traducción de Direcciones
-      de Red (NAT) de PPP</title>
-
-    <para>Es posible que ya esté usando la NAT que incluye
-      PPP.  Si es su caso tendrá que desactivarla puesto que
-      los casos que vamos a usar emplean &man.natd.8; para hacerlo.</para>
-
-    <para>Si ya dispone de un grupo de entradas para arrancar
-      automáticamente PPP probablemente se parezca a
-      ésto:</para>
-
-    <programlisting>ppp_enable="YES"
-ppp_mode="auto"
-ppp_nat="YES"
-ppp_profile="<replaceable>profile</replaceable>"</programlisting>
-
-    <para>Si es su caso, tendrá que desactivar
-      específicamente <literal>ppp_nat</literal>
-      asegurándose de que
-      <literal>ppp_nat="NO"</literal> existe en su
-in <filename>/etc/rc.conf</filename>. Tendrá tambié que
-      borrar todas las entradas como
-      <literal>nat enable yes</literal> o
-      <literal>alias enable yes</literal> en
-      <filename>/etc/ppp/ppp.conf</filename>.</para>
-  </sect1>
-
-  <sect1 id="rules">
-    <title>Las Reglas del Cortafuegos</title>
-
-    <para>Casi hemos acabado.  Lo único que nos falta es
-      definir las reglas del cortafuegos, reiniciar y deberíamos
-      tener nuestro cortafuegos funcionando perfectamente.  Soy
-      consciente de que cada cual tendrá necesidades distintas
-      como reglas básicas.  He intentado escribir unas reglas
-      básicas que puedan cubrir las necesidades de un usuario
-      de conexión telefónica normal.  Vamos a comenzar
-      por lo básico de un cortafuegos cerrado.  Lo que se
-      busca es rechazar todo por defecto y dejar pasar solamente
-      lo que necesitemos.  Las reglas deberían ir en la forma
-      <quote>al principio permitir, luego rechazar</quote>.  La premisa
-      es que vamos a an&tilde;adir reglas para lo que vamos a aceptar y
-      luego rechazamos todo lo demás. :)</para>
-
-    <para>Ahora vamos a crear el directorio <filename
-      class="directory">/etc/firewall</filename>. Sitúese en el
-      directorio y edite el fichero <filename>fwrules</filename> tal y
-      como hemos escrito dentro de <filename>rc.conf</filename>.  Por favor,
-      no olvide que puede cambiar el nombre del fichero por cualquier otro
-      que prefiera. Éste documento solamente facilita un ejemplo
-      del nombre del fichero.</para>
-
-    <para>Vamos a echar un vistazo a un ejemplo de fichero de
-      configuración del cortafuegos que hemos comentado
-      cuidadosamente.</para>
-
-    <programlisting># Definimos el comando con el que invocamos al cortafuegos
-# (tal y como hemos incluído en /etc/rc.firewall) para
-# facilitarnos la lectura.
-fwcmd="/sbin/ipfw"
-
-# Fuerza el borrado de todas las reglas existentes en nuestro
-# cortafuegos antes de cargar el contenido de éste fichero.
-$fwcmd -f flush
-
-# Desvía todos los paquetes a través del interfaz tunnel.
-$fwcmd add divert natd all from any to any via tun0
-
-# Permite todas las conexiones incluídas en reglas
-# dinámicas pero rechaza todas aquellas conexiones
-# establecidas que no estén incluídas en alguna
-# regla dinámica.
-$fwcmd add check-state
-$fwcmd add deny tcp from any to any established
-
-# Aceptar todas las conexiones de localhost.
-$fwcmd add allow tcp from me to any out via lo0 setup keep-state
-$fwcmd add deny  tcp from me to any out via lo0
-$fwcmd add allow ip  from me to any out via lo0 keep-state
-
-# Aceptar todas las conexiones desde mi tarjeta de red que yo inicie.
-$fwcmd add allow tcp from me to any out xmit any setup keep-state
-$fwcmd add deny  tcp from me to any
-$fwcmd add allow ip from me to any out xmit any keep-state
-
-# Todo el mundo a lo largo y ancho de Internet puede conectarse
-# a los siguientes servicios de la máquina.  Éste
-# ejemplo permite específicamente las conexiones a sshd
-# y al servidor web.
-$fwcmd add allow tcp from any to me dst-port 22,80 in recv any setup keep-state
-
-# Ésto envía un RESET a todos los paquetes ident.
-$fwcmd add reset log tcp from any to me 113 in recv any
-
-# Activa ICMP: borre el tipo 8 si no quiere que su máquina
-# responda al ping.
-$fwcmd add allow icmp from any to any icmptypes 0,3,8,11,12,13,14
-
-# Rechazamos todo lo demás.
-$fwcmd add deny log ip from any to any</programlisting>
-
-    <para>Ya tiene usted un cortafuegos totalmente funcional que
-      acepta todas las conexiones a los puertos 22 y 80 y registrará
-      cualquier otro tipo de intento de conexión en un fichero
-      <filename>log</filename>.  Ahora podemos reiniciar tranquilamente
-      y su cortafuegos debería empezar a trabajar tal y como le
-      hemos dicho.  Si le parece que hay algún dato incorrecto o
-      tiene alguna sugerencia para mejorar éste documento por
-      favor envíeme un correo electrónico.</para>
-  </sect1>
-
-  <sect1>
-    <title>Preguntas</title>
-
-    <qandaset>
-      <qandaentry>
-	<question>
-          <para>?Por qué utiliza &man.natd.8; y
-            &man.ipfw.8; cuando podría usar  los filtros
-            incluídos en &man.ppp.8;?</para>
-	</question>
-
-	<answer>
-          <para>Seré honesto y diré que no hay una
-            razón clara por la que use <command>ipfw</command> y
-            <command>natd</command> en lugar de los filtros que incorpora
-            <command>ppp</command>.  Tras hablarlo con mucha gente el
-            consenso parece ser que <command>ipfw</command>
-             es mucho más potente y configurable que el filtrado
-             de <command>ppp</command> pero lo que se gana en
-             funcionalidad lo pierde en facilidad de
-             personalización.  Una de las razones por las que
-             prefiero usar esas aplicaciones es que creo má conveniente
-             ejecutar un cortafuegos desde el kernel que desde una
-             aplicación de entorno de usuario.</para>
-
-	</answer>
-      </qandaentry>
-
-      <qandaentry>
-        <question>
-          <para>Me aparecen mensajes como <errorname>limit 100 reached on
-            entry 2800</errorname> y después de eso ya no me aparecen
-            más entradas indicando tráfico rechazado en mis
-            <filename>logs</filename>.  ?Funciona mi
-            cortafuegos?</para>
-        </question>
-
-	<answer>
-          <para>Esto significa simplemente que se ha alcanzado el
-            máximo de entradas que pueden incluírse en el
-            <filename>log</filename> cuando una determinada regla
-            se ha cumplido.  Esa regla sigue
-            funcionando pero no enviaría más entradas al
-            <filename>log</filename> hasta que el contador vuelva a
-            cero. Puede poner a cero ese contador mediante
-            <command>ipfw resetlog</command>.  Además es posible
-            elevar el límite de entradas a introducir en el
-            <filename>log</filename> incluyendo la <quote>option</quote>
-            <option>IPFIREWALL_VERBOSE_LIMIT</option> en el fichero de
-            de configuración del kernel. Por otra parte puede
-            modificar ese valor (sin modificar su kernel y en consecuencia
-            sin reiniciar la máquina) mediante el valor de
-            &man.sysctl.8; net.inet.ip.fw.verbose_limit.</para>
-        </answer>
-      </qandaentry>
-
-      <qandaentry>
-	<question>
-          <para>Supongamos que estoy usando direcciones privadas internas,
-            por ejemplo el rango 192.168.0.0. ?Puedo añadir
-            una regla al cortafuegos mediante un comando como
-	    <literal>$fwcmd add
-	      deny all from any to 192.168.0.0:255.255.0.0 via tun0</literal>
-            para prevenir intentos de acceso desde el exterior para conectar
-            con máquinas de mi red?.</para>
-	</question>
-
-	<answer>
-          <para>La respuesta corta es no.  La razón es que
-	    <command>natd</command> efectúa la traducción
-            de direcciones para <emphasis>cualquier cosa</emphasis> que
-            sea redirigida a través del dispositivo
-	    <devicename>tun0</devicename>.  Eso significa que todos los
-            paquetes entrantes hablarán exclusivamente con la IP
-            asignada dinámicamente y <emphasis>no</emphasis> con la
-            red interna.  Hay que tener en cuenta sin embargo que es posible
-            añadir una regla como
-	    <literal>$fwcmd add deny all from 192.168.0.4:255.255.0.0
-	    to any via tun0</literal>, que evitaría que una de las
-            máquinas de esa red enviara tráfico al exterior
-            a través del cortafuegos.</para>
-	</answer>
-      </qandaentry>
-
-      <qandaentry>
-	<question>
-          <para>Debo de haber hecho algo mal.  He seguido las instrucciones
-            al pie de la letra y no tengo acceso a Internet.</para>
-        </question>
-
-	<answer>
-          <para>Estamos asumiendo que está usando
-	    <emphasis>userland-ppp</emphasis>, en consecuencia el conjunto
-            de reglas que aquí se proponen operan en el interfaz
-	    <devicename>tun0</devicename>, que corresponde a la primera
-            conexión efectuada mediante &man.ppp.8; (más
-            conocido como <emphasis>user-ppp</emphasis>).  Las conexiones
-            efectuadas más tarde recibirán nombres como
-	    <devicename>tun1</devicename>, <devicename>tun2</devicename> y
-	    así sucesivamente.</para>
-
-          <para>Hay que tener también presente que &man.pppd.8;
-            en cambio utiliza el interfaz <devicename>ppp0</devicename>,
-            de modo que si se inicia la conexión con &man.pppd.8; hay
-            que sustituír <devicename>tun0</devicename> por
-	    <devicename>ppp0</devicename>.  A continuación se muestra
-            una forma muy limpia de modificar las reglas del
-            cortafuegos.  Conservaremos un fichero con las reglas originales
-            con el nombre de
-	    <filename>fwrules_tun0</filename>.</para>
-
-	  <screen>	    &prompt.user; <userinput>cd /etc/firewall</userinput>
-	    /etc/firewall&prompt.user; <userinput>su</userinput>
-	    <prompt>Password:</prompt>
-	    /etc/firewall&prompt.root; <userinput>mv fwrules fwrules_tun0</userinput>
-	    /etc/firewall&prompt.root; <userinput>cat fwrules_tun0 | sed s/tun0/ppp0/g > fwrules</userinput>
-	  </screen>
-
-          <para>Para saber exactamente si está usando &man.ppp.8; o
-            &man.pppd.8; examine la salida de &man.ifconfig.8; una vez que
-            establezca la conexión.  V.g., en una conexión
-            hecha mediante &man.pppd.8; debería encontrarse con
-            algo muy similar a lo siguiente (se muestran sólo las
-            líneas relevantes):</para>
-
-	  <screen>	    &prompt.user; <userinput>ifconfig</userinput>
-	    <emphasis>(eliminado...)</emphasis>
-	    ppp0: flags=<replaceable>8051&lt;UP,POINTOPOINT,RUNNING,MULTICAST&gt; mtu 1524</replaceable>
-                    inet <replaceable>xxx.xxx.xxx.xxx</replaceable> --&gt; <replaceable>xxx.xxx.xxx.xxx</replaceable> netmask <replaceable>0xff000000</replaceable>
-	    <emphasis>(eliminado...)</emphasis>
-	    </screen>
-
-
-          <para>Si por el contrario la conexión fué
-            establecida mediante &man.ppp.8;
-	    (<emphasis>user-ppp</emphasis>) ésto es más o
-            menos lo que se encontraría:</para>
-
-	  <screen>	    &prompt.user; <userinput>ifconfig</userinput>
-	    <emphasis>(eliminado...)</emphasis>
-	    ppp0: flags=<replaceable>8010&lt;POINTOPOINT,MULTICAST&gt; mtu 1500</replaceable>
-	    <emphasis>(skipped...)</emphasis>
-	    tun0: flags=<replaceable>8051&lt;UP,POINTOPOINT,RUNNING,MULTICAST&gt; mtu 1524</replaceable>
-	            <emphasis>(IPv6 stuff skipped...)</emphasis>
-                    inet <replaceable>xxx.xxx.xxx.xxx</replaceable> --&gt; <replaceable>xxx.xxx.xxx.xxx</replaceable> netmask <replaceable>0xffffff00</replaceable>
-                    Opened by PID <replaceable>xxxxx</replaceable>
-            <emphasis>(eliminado...)</emphasis></screen>
-	</answer>
-      </qandaentry>
-    </qandaset>
-  </sect1>
-</article>
diff --git a/es_ES.ISO8859-1/articles/euro/Makefile b/es_ES.ISO8859-1/articles/euro/Makefile
deleted file mode 100644
index e1247939d0..0000000000
--- a/es_ES.ISO8859-1/articles/euro/Makefile
+++ /dev/null
@@ -1,18 +0,0 @@
-#
-# $FreeBSD$
-#
-# Article: The Euro symbol on FreeBSD
-
-DOC?= article
-
-FORMATS?= html
-
-INSTALL_COMPRESSED?=gz
-INSTALL_ONLY_COMPRESSED?=
-
-SRCS=	article.sgml
-
-URL_RELPREFIX?=	../../../..
-DOC_PREFIX?= ${.CURDIR}/../../..
-
-.include "${DOC_PREFIX}/share/mk/doc.project.mk"
diff --git a/es_ES.ISO8859-1/articles/euro/article.sgml b/es_ES.ISO8859-1/articles/euro/article.sgml
deleted file mode 100644
index bb98bd13ee..0000000000
--- a/es_ES.ISO8859-1/articles/euro/article.sgml
+++ /dev/null
@@ -1,398 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1" standalone="no"?>
-<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V4.2-Based Extension//EN"
-	"../../../share/sgml/freebsd42.dtd" [
-<!ENTITY % entities PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Entity Set//ES" "../../share/sgml/entities.ent">
-%entities;
-]>
-
-<!-- The FreeBSD Spanish Documentation Project
-     $FreeBSD$
--->
-
-<article lang="es">
-  <articleinfo>
-    <title>El símbolo del Euro en
-      <systemitem class="osname">FreeBSD</systemitem></title>
-
-    <authorgroup>
-      <author>
-	<firstname>Aaron</firstname>
-
-	<surname>Kaplan</surname>
-
-	<affiliation>
-	  <address>
-	    <email>aaron@lo-res.org</email>
-	  </address>
-	</affiliation>
-      </author>
-    </authorgroup>
-
-    <copyright>
-      <year>2002</year>
-      <year>2003</year>
-      <holder>The FreeBSD Documentation Project</holder>
-    </copyright>
-
-    <pubdate>$FreeBSD$</pubdate>
-
-    <releaseinfo>$FreeBSD$</releaseinfo>
-
-<!--
-    <legalnotice id="trademarks" role="trademarks">
-      &tm-attrib.freebsd;
-      &tm-attrib.general;
-    </legalnotice>
--->
-
-    <abstract>
-      <para>Este documento intentará ayudarle a empezar
-	a usar el nuevo símbolo del <keycap>Euro</keycap>
-	en su nuevo teclado, adquirido a principios del 2002
-	debido al cambio de la nueva moneda común.
-	Primero trataremos los aspectos más importantes,
-	como mostrar correctamente el símbolo en la consola.
-	Las secciones posteriores tratarán sobre la
-	configuración de programas en concreto,  como
-	<application>X11</application>.
-      </para>
-
-      <para>Se recibió ayuda muy provechosa de Oliver Fromme,
-	Tom Rhodes y de muchos otros. ¡Gracias! ¡Sin su
-	ayuda, este artículo no habría sido posible!
-      </para>
-      &trans.es.jcamou;
-    </abstract>
-  </articleinfo>
-
-  <sect1>
-    <title>El Euro hecho fácil</title>
-
-    <para>Si ya se siente cómodo con la
-<!--
-      <ulink url="&url.books.handbook;/l10n.html">localización</ulink>
--->
-      <ulink url="http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/l10n.html">localización</ulink>
-      descrita en el Handbook de <systemitem class="osname">FreeBSD
-      </systemitem> puede que sólo esté interesado en los
-      siguientes pasos,  que pueden ayudarle a empezar
-      rápidamente:</para>
-
-    <variablelist>
-      <varlistentry>
-	<term>ISO8859-15</term>
-
-	<listitem>
-	  <para>Ésta es una ligera modificación del
-	  mapa de caracteres ISO8859-1.
-	  Incluye ademá el símbolo del Euro, usado por
-	  las variables <envar>LANG</envar> y <envar>LC_CTYPE</envar>.</para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-	<term><filename>iso15-8x16.fnt</filename></term>
-
-	<listitem>
-	  <para>La fuente &man.vidcontrol.1; para consola</para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-	<term><filename>/usr/share/syscons/keymaps/*.iso.kbd</filename></term>
-
-	<listitem>
-	  <para>Un mapa de caracteres apropiado depende de su idioma.
-	    Defina su entrada de <literal>keymap</literal> en <filename>
-	    rc.conf</filename> usando alguno de éstos.</para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-	<term><envar>LC_CTYPE</envar></term>
-
-	<listitem>
-	  <para>Usado para especificar el tipo correcto de caracteres
-	    correcto.</para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-	<term><literal>XkbLayout "<replaceable>idioma</replaceable>(euro)"
-	  </literal></term>
-
-	<listitem>
-	  <para>Opción de configuración de
-	    <application>XFree86</application>.</para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-	<term><filename>/usr/X11R6/lib/X11/fonts/*/fonts.alias</filename></term>
-	<listitem>
-	  <para>Asegúrese de adaptar sus fuentes X11 a
-	    <literal>-*-..-*-iso8859-15</literal></para>
-	</listitem>
-      </varlistentry>
-    </variablelist>
-  </sect1>
-
-  <sect1>
-    <title>Observación general</title>
-
-    <para>En las siguientes secciones a menudo nos referiremos a
-      <emphasis>ISO8859-15</emphasis>.  Esta es la notación
-      estándar a partir de <systemitem class="osname">FreeBSD
-      </systemitem> 4.5.  En versiones anteriores la notación
-      estándar era <emphasis>ISO_8859-15</emphasis> o
-      <emphasis>DIS_8859-15</emphasis>.
-    </para>
-
-    <para>Si está usando una versión anterior de
-      <systemitem class="osname"> FreeBSD</systemitem> asegúrese
-      de revisar <filename>/usr/share/locale/ </filename> para averiguar
-      la notación que está usando.</para>
-  </sect1>
-
-  <sect1>
-    <title>La consola</title>
-
-    <sect2>
-      <title>Cómo establecer la fuente de la consola</title>
-
-      <para>Dependiendo de la resolución y tamaño de su consola
-	necesesitará una de las siguientes líneas en
-	<filename> rc.conf</filename>:</para>
-
-     <programlisting>font8x16="iso15-8x16.fnt" # from /usr/share/syscons/fonts/*
-font8x14="iso15-8x14.fnt"
-font8x8="iso15-8x8.fnt"</programlisting>
-
-      <para>Esto seleccionará ISO8859-15, también
-	conocida como la fuente Latin-9.  ISO8859-15 es una variación
-	de ISO8859-1.  Es posible encontrar la diferencia entre las dos al
-	ver el símbolo del Euro:  su valor decimal es 164.  En
-	ISO8859-1 notará un círculo con cuatro pequeños
-	brazos en las esquinas.  A menudo recibe el nombre de
-	<quote>símbolo de la moneda universal</quote>.  En ISO8859-15
-	en lugar del pequeño círculo se tiene el símbolo
-	del Euro.  Aparte de eso, las fuentes son idénticas.</para>
-
-      <warning>
-	<para>Cuando se redacta este artículo  la única
-	  fuente que es posible usar es, al parecer,
-	  <literal>iso15-8x16.fnt</literal>.
-	  Las otras aparentemente sólo muestran ISO8859-1 aunque el
-	  nombre sugiera lo contrario.</para>
-      </warning>
-
-      <note>
-	<para>Al especificar esta fuente algunos programas de consola
-	  podrán ver muy alterado su comportamiento.  Esto es debido a
-	  que se asume que  se está usando una fuente o caracter
-	  diferente, por ejemplo ANSI 850.  Un ejemplo notable de ello es
-	  <application>sysinstall</application>.  En muchas ocasiones esto
-	  carece de mayor importancia.</para>
-      </note>
-
-      <para>El siguiente paso es reiniciar el sistema para que los cambios
-	tengan efecto o hacer los pasos que hubiese hecho el sistema al ser
-	reiniciado (manualmente):</para>
-
-      <screen>&prompt.user; <userinput>vidcontrol -f <replaceable>iso15-8x16.fnt</replaceable></userinput></screen>
-
-      <para>Para asegurarse de que la fuente haya sido correctamente
-	seleccionada ejecute el siguiente <quote>script</quote> de
-	<command><anchor id="awk-test"/>awk</command>:</para>
-
-      <programlisting>#!/usr/bin/awk -f
-BEGIN {
-	for(i=160;i&lt;180;i++)
-		printf~%3d %c\n",i,i
-}</programlisting>
-
-      <para>El resultado debe mostrar el símbolo del Euro en
-	la posición 164.</para>
-    </sect2>
-
-    <sect2>
-      <title>Configuración del teclado para el símbolo del
-	Euro</title>
-
-      <para>La mayoría de los teclados ya están configurados
-	correctamente.  Por ejemplo: si se tiene un teclado en alemán
-	y sus teclas Umlaut funcionan puede saltarse esta sección
-	ya que su teclado ya tiene la combinación necesaria (e.g.:
-	<keycombo action="simul"><keycap>Alt Gr</keycap><keycap>e</keycap>
-	</keycombo>) al valor decimal 164.  Si se experimentan
-	problemas la mejor manera de revisarlo es echándole un ojo
-	a <filename>/usr/share/syscons/keymaps/*.kbd</filename>.  El formato
-	de los ficheros de mapeo de teclas se describe en
-	&man.keyboard.4;.  &man.kbdcontrol.1; puede usarse para cargar
-	un mapa en particular.</para>
-      <para>Una vez seleccionado el mapa de teclas correcto debe
-	añadirse a <filename>/etc/rc.conf</filename> con la
-	línea:</para>
-
-      <programlisting>keymap="<replaceable>german.iso</replaceable>" # u otro mapa</programlisting>
-
-      <para>Como ya se mencionó este paso probablemente ya haya
-	sido realizado por usted durante la instalación
-	(con la ayuda de <application>sysinstall</application>).  Si no
-	fue así puede reiniciar o cargar el nuevo mapa de teclado
-	mediante &man.kbdcontrol.1;.</para>
-
-
-      <para>Para verificar el mapeo de las teclas es posible cambiar de
-	consola y cuando pida nombre de usuario, <emphasis>en lugar de
-	teclearlo</emphasis>, intente teclear el <keycap>Euro</keycap>.
-	De no funcionar esto puede mandar un informe de error mediante
-	&man.send-pr.1; o asegurarse de que haya escogido el mapa
-	correcto para el teclado.</para>
-      <note>
-	<para>En este momento la tecla del Euro no funcionará en
-	  <application>bash </application> o
-	  <application>tcsh</application>.</para>
-      </note>
-    </sect2>
-
-    <sect2>
-      <title>Modificar las variables de ambiente</title>
-
-      <para>Las shells (<application>bash</application>,
-	<application>tcsh</application>)
-	recurren a la biblioteca &man.readline.3;, que respeta la
-	variable <envar>LC_CTYPE</envar>.  <envar>LC_CTYPE</envar> debe
-	ser establecida antes de que la shell se ejecute.
-	Afortunadamente es suficiente añadir la siguiente
-	línea:</para>
-
-      <programlisting>exoprt LC_CTYPE=<replaceable>de_DE</replaceable>.ISO8859-15</programlisting>
-
-      <para>a su <filename>.bash_profile</filename>
-	(<application>bash</application>), o:</para>
-
-      <programlisting>setenv LC_CTYPE <replaceable>de_DE</replaceable>.ISO8859-15</programlisting>
-
-      <para>a su <filename>.login</filename>
-	(<application>tcsh</application>).
-	Por supuesto, <replaceable>de_DE</replaceable> debe ser remplazado
-	con su idioma.  A continuación finalice la sesión,
-	inicie sesión nuevamente y verifique si su símbolo
-	del Euro funciona.  A partir de ahora la gran
-	mayoríia de los programas de consola deben responder al Euro.
-	Es probable que sean necesarios algunos pasos adicionales de
-	configuración para programas especiales como
-	<application>pine</application>.
-      </para>
-
-      <note>
-	<para>Una alternativa para modificar <filename>.login</filename> y
-	  <filename>.bash_profile</filename> es establecer las variables
-	  a partir del mecanismo de &man.login.conf.5;.  Este método
-	  tiene la ventaja de asignar tipos de <quote>login</quote> a
-	  ciertos usuarios (por ejemplo usuarios que desean tener su entorno
-	  en francés, italiano, etc) mediante modificaciones de
-	  configuración <emphasis>en un solo lugar</emphasis>.</para>
-      </note>
-    </sect2>
-  </sect1>
-
-  <sect1>
-    <title>Modificar X11</title>
-
-    <para>Modifique <filename>/etc/XF86Config</filename> de la siguiente
-      manera:</para>
-
-    <programlisting>Option "XkbLayout" "<replaceable>de</replaceable>(euro)"</programlisting>
-
-    <para>Recuerde que tendrá que reemplazar
-      <replaceable>de</replaceable> con el código de idioma que haya
-      elegido.  Su teclado debería estar configurado correctamente.
-      De igual modo que en la sección de consola, debe seleccionarse la
-      fuente correcta.  En <application>KDE</application> vaya
-      a su <application>KDE control center</application> -&gt;
-      Personalization -&gt; Country &amp; Language -&gt; Charset
-      y cámbielo a <literal>ISO8859-15</literal>.  En
-      <application>kmail</application> y otros programas tendrá que
-      proceder de forma muy similar.</para>
-
-    <para>Otra buena idea es modificar su ficheros en <filename>
-      fonts.alias</filename>.  Existe un caso especial: la fuente
-      <quote><literal>fixed</literal></quote> debe cambiarse al mapa de
-      caracteres correcto:  El
-      <filename>/usr/X11R6/lib/x11/fonts/misc/fonts.alias</filename>
-      del autor; este es:</para>
-
-     <programlisting>! $Xorg: fonts.alias,v 1.3 2000/08/21 16:42:31 coskrey Exp $
-fixed   -misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-iso8859-15
-ariable -*-helvetica-bold-r-normal-*-*-120-*-*-*-*-iso8859-15
-(...)</programlisting>
-
-    <para>Así como en las secciones de consola, ciertos programas
-      aún tienen las fuentes ISO8859-1 configuradas en su respectiva
-      base de datos de &man.xrdb.1;.  Un ejemplo de esto es
-      <application>xterm</application>.  Como regla general es suficiente
-      con cambiar la configuración correspondiente en
-      <filename>/usr/X11R6/lib/X11/app-defaults</filename> y añadir la
-      fuente correcta.  Veamos un ejemplo con
-      <application>xterm</application>.</para>
-
-  <screen>&prompt.root; cd /usr/X11R6/lib/X11/app-defaults/
-&prompt.root; vi XTerm</screen>
-
-    <para>Añada la siguiente línea al principio del
-       fichero:</para>
-
-    <programlisting>*font:     -misc-fixed-medium-r-normal-*-*-120-*-*-c-*-iso8859-15</programlisting>
-
-    <para>Para finalizar  reinicie X y asegúrese de que las fuentes
-      puedan mostrarse al ejecutar el
-      <link linkend="awk-test">script de awk</link>
-      anterior.  La mayoría de los programas deben respetar el mapa de
-      caracteres y las configuraciones de fuente.</para>
-  </sect1>
-
-  <sect1>
-    <title>Problemas</title>
-
-    <para>Por supuesto que el autor agradecería que le enviara sus
-      comentarios.
-      Además, al menos me gustaría saber si tiene usted
-      solución para alguno de los siguientes problemas:</para>
-    <itemizedlist>
-      <listitem>
-	<para>Alguna manera alternativa de configurar
-	  <application>XFree86</application>:
-	  <filename role="package">x11/xkeycaps</filename></para>
-      </listitem>
-
-      <listitem>
-	<para>Configuraciones para <application>GNOME</application></para>
-      </listitem>
-
-      <listitem>
-	<para>Configuraciones para <application>KDE</application></para>
-      </listitem>
-
-      <listitem>
-	<para>Configuraciones para <application>XFCE</application></para>
-      </listitem>
-
-      <listitem>
-	<para>Configuraciones para <application>(X)Emacs</application></para>
-      </listitem>
-
-      <listitem>
-	<para>Configuración para UTF-8</para>
-      </listitem>
-
-      <listitem>
-	<para>Una configuración que incluya
-	  <application>libiconv</application> como una manera
-	  efectiva de convertir entre ISO8859-15 y UTF-{8, 16} dentro
-	  de los programas</para>
-      </listitem>
-    </itemizedlist>
-  </sect1>
-</article>
diff --git a/es_ES.ISO8859-1/articles/linux-users/article.sgml b/es_ES.ISO8859-1/articles/linux-users/article.sgml
index 5c49fdad63..02fe6c028e 100644
--- a/es_ES.ISO8859-1/articles/linux-users/article.sgml
+++ b/es_ES.ISO8859-1/articles/linux-users/article.sgml
@@ -145,11 +145,6 @@ in your /etc/rc.conf. Extra options can be found in startup script.</screen>
            url="ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-6-stable/Latest/"/>
           si quiere descargar los packages más recientes compilados
 	   para la versión 6.X.</para>
-
-	<para>Si quiere saber más sobre las versiones de &os;
-	  consulte el artículo <ulink
-	     url="&url.base;/doc/es_ES.ISO8859-1/articles/version-guide/">
-	    Cómo elegir la versión apropriada de &os;</ulink>.</para>
       </note>
 
       <para>Para más información sobre los packages consulte
diff --git a/es_ES.ISO8859-1/articles/version-guide/Makefile b/es_ES.ISO8859-1/articles/version-guide/Makefile
deleted file mode 100644
index e9b3852f11..0000000000
--- a/es_ES.ISO8859-1/articles/version-guide/Makefile
+++ /dev/null
@@ -1,19 +0,0 @@
-#
-# $FreeBSD$
-#
-# Article: FreeBSD Version Guide
-
-DOC?= article
-
-FORMATS?= html
-WITH_ARTICLE_TOC?= YES
-
-INSTALL_COMPRESSED?= gz
-INSTALL_ONLY_COMPRESSED?=
-
-SRCS=		article.sgml
-
-URL_RELPREFIX?=	../../../..
-DOC_PREFIX?= ${.CURDIR}/../../..
-
-.include "${DOC_PREFIX}/share/mk/doc.project.mk"
diff --git a/es_ES.ISO8859-1/articles/version-guide/article.sgml b/es_ES.ISO8859-1/articles/version-guide/article.sgml
deleted file mode 100644
index 4472685b82..0000000000
--- a/es_ES.ISO8859-1/articles/version-guide/article.sgml
+++ /dev/null
@@ -1,439 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1" standalone="no"?>
-<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V4.2-Based Extension//EN"
-	"../../../share/sgml/freebsd42.dtd" [
-<!ENTITY % entities PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Entity Set//ES" "../../share/sgml/entities.ent">
-%entities;
-]>
-
-<!-- The FreeBSD Spanish Documentation Project
-     Original Revision: r1.11			-->
-
-<article lang='es'>
-  <title>Cómo elegir la versión apropriada de &os;</title>
-
-  <articleinfo>
-    <authorgroup>
-      <author>
-	<surname>El Proyecto de Documentación de &os;</surname>
-      </author>
-    </authorgroup>
-
-    <legalnotice id="trademarks" role="trademarks">
-      &tm-attrib.freebsd;
-    </legalnotice>
-
-    <copyright>
-      <year>2005</year>
-      <holder>El Proyecto de Documentación de &os;</holder>
-    </copyright>
-
-    <pubdate>$FreeBSD$</pubdate>
-
-    <releaseinfo>$FreeBSD$</releaseinfo>
-
-    <abstract>
-      <para>Así que ha decidido instalar &os;.  ¡Bienvenido!
-	el propósito de este documento es ayudarle seleccionar la
-	versión apropriada.</para>
-
-      &trans.es.gabor;
-
-    </abstract>
-  </articleinfo>
-
-  <sect1 id="background">
-    <title>Introducción</title>
-
-    <para>Antes de decidir cuál de las versiones de &os; quiere
-      usar es importante que comprenda los conceptos relacionados con
-      el desarrollo y el proceso de Ingeniería de Releases
-      (<literal>RE</literal>).</para>
-
-    <para>&os; se desarrolla gracias a un gran grupo de gente,
-      casi siempre voluntarios.  El código fuente del kernel, de las
-      utilidades y de las bibliotecas más
-      comúnes están en un <firstterm>sistema de
-      gestión de código</firstterm> del cual es posible
-      descargarlo en cualquier momento.  Aparte de esto, existen versiones
-       (<literal>binarias</literal>) ya compiladas que se liberan
-       cada poco tiempo.  Una de estas versiones binarias cuidadosamente
-       revisada será en su momento declarada
-      <firstterm>releases</firstterm>.</para>
-
-    <sect2 id="releases">
-      <title>Releases</title>
-
-      <para>El nombre de las <literal>releases</literal> contiene un
-	<firstterm>número mayor de release</firstterm> y un
-	<firstterm>número menor de release</firstterm>.</para>
-
-      <itemizedlist>
-	<listitem>
-	  <para>El propósito de una release mayor es incluir
-	    nuevas funciones.  Es inevitable que, al añadir
-	    nuevas funciones a &os; o al quitarlas, sea necesario algunas
-	    veces perder la compatibilidad con versiones anteriores del
-	    sistema operativo.</para>
-	</listitem>
-
-	<listitem>
-	  <para>El propósito de una release menor es ante todo
-	    corregir errores y mejorar el rendimiento y la estabilidad.
-	    Es importante mantener la compatibilidad entre releases menores
-	    tanto cuando se trata de código como con los programas
-	    ejecutables.  Si se da la ocasión, se añaden nuevas
-	    características a una release menor si estos principios
-	    se mantienen.</para>
-	</listitem>
-      </itemizedlist>
-
-      <para>No obstante, tenga en cuenta que una <quote>release</quote>
-        es solamente una instantánea del árbol de
-	código en un momento dado, gracias a lo cual se le da
-	una etiqueta o <emphasis>tag</emphasis>.  Por ejemplo, la
-	etiqueta que el grupo de ingeniería de releases dio a la
-	release 5.4 fue <literal>RELENG_5_4_0_RELEASE</literal>.  El
-	desarrollo tiene lugar bajo la etiqueta
-	<literal>HEAD</literal>.</para>
-    </sect2>
-
-    <sect2 id="branches">
-      <title>Bifurcaciones</title>
-
-      <para>En el tiempo de sacar cada release, se crea una
-	<firstterm>rama</firstterm>, por ejemplo
-	<literal>RELENG_5_4</literal>.  Aunque el código bajo
-	<literal>RELENG_5_4_0_RELEASE</literal> no cambien,
-	los que están bajo <literal>RELENG_5_4</literal>
-	sí, al aplicar cambios en <literal>HEAD</literal>
-	al corregir problemas de seguridad u otro tipo de fallo.</para>
-    </sect2>
-
-    <sect2 id="stable-vs-current">
-      <title><firstterm>STABLE</firstterm> y
-	<firstterm>CURRENT</firstterm></title>
-
-      <para>Durante la vida de cada release mayor una rama
-	individual puede convertirse en <literal>STABLE</literal>.  Esto
-	indica que el Proyecto &os; cree que la rama ha
-	demostrado suficiente calidad para que la mayoría de los
-	usuarios puedan usarla.  Las ramas que necesitan más
-	pruebas antes de que pueda usarlas cualquiera reciben el nombre
-	de <literal>CURRENT</literal>.</para>
-
-      <note><para>El Proyecto &os; no puede garantizar que el software
-	que se distribuye sea todo lo <emphasis>estable</emphasis>
-	que sea necesario para cualquier necesidad o uso.  Es el usuario
-	quien tiene la última palabra sobre esto.  Por favor,
-	tenga muy en cuenta que el proyecto lo forman voluntarios y no
-	puede ofrecer ningún tipo de garantía.</para></note>
-    </sect2>
-
-    <sect2 id="ports-vs-packages">
-      <title><firstterm>Ports</firstterm> y
-	<firstterm>packages</firstterm></title>
-
-      <para>Aparte de los ficheros que se distribuyen del modo ya descrito
-        antes, &os; permite el uso de miles de aplicaciones fruto del
-	trabajo de desarrolladores que no forman parte del proyecto.
-	Podemos citar como ejemplos sistemas de ventanas, navegadores web,
-	programas de correo electrónico, software ofimático,
-	etc.)  El proyecto en sí no desarrolla estos programas,
-	solamente el <quote>framework</quote> que permite que éstos
-	puedan instalarse;  este <quote>framework</quote> recibe el
-	nombre de <firstterm>Colección de Ports</firstterm>).
-	Se pueden instalar aplicaciones desde el código fuente si su
-	licencia permite este tipo de redistribución; es lo que en
-	&os; se llaman los <emphasis>ports</emphasis>)), o como software
-	compilado si está permitido distribuirlos como tal, en cuyo
-	caso reciben el nombre de <emphasis>packages</emphasis>.</para>
-    </sect2>
-  </sect1>
-
-  <sect1 id="past-schedules">
-    <title>El calendario de releases anteriores</title>
-
-    <para>Durante el desarrollo de la release 5.X de &os; hubo que aprender
-      en carne propia muchas lecciones que solamente pudieron verse con
-      posterioridad.  Los objetivos de la serie 5.X fueron muy
-      ambiciosos. Veamos algunos:</para>
-
-    <itemizedlist>
-      <listitem>
-	<para>Ofrecer soporte para máquinas dotadas de
-	  multiproceso simétrico (Symmetric MultiProcessing,
-	  o  SMP)</para>
-      </listitem>
-
-      <listitem>
-	<para>Mejoras del rendimiento gracias a la adopción
-	  de una nueva estrategia de gestión de recursos en el
-	  kernel</para>
-      </listitem>
-
-      <listitem>
-	<para>Añadir numerosas arquitecturas de procesador</para>
-      </listitem>
-
-      <listitem>
-	<para>Introducción de un nuevo modelo de
-	  <quote>threading</quote></para>
-      </listitem>
-
-      <listitem>
-	<para>Introducción de un nuevo
-	  <quote>scheduler</quote></para>
-      </listitem>
-
-      <listitem>
-	<para>Añadir soporte de nuevas tecnologías como
-	  la gestión de energía (especialmente importante en
-	  máquinas portátiles), y sobre todo</para>
-      </listitem>
-
-      <listitem>
-	<para>no declarar ninguna versión como
-	  <literal>STABLE</literal> hasta que estas tareas no se
-	  hubieran terminado</para>
-      </listitem>
-    </itemizedlist>
-
-    <para>Esto llevó al problema de que había varios
-      años de diferencia entre el momento en el que 4.X
-      se declaró <literal>STABLE</literal> y el momento en el que
-      5.X se llegó a <literal>STABLE</literal>.  Esta circunstancia
-      tuvo diversos efectos no deseados:</para>
-
-    <itemizedlist>
-      <listitem>
-	<para>El número funciones cambiadas simultáneamente
-	  hizo muy difícil aislar esos cambios para hacerlos
-	  compatibles con las versiones anteriores a la creació de
-	  la rama <literal>STABLE</literal>.</para>
-      </listitem>
-
-      <listitem>
-	<para>Eso significó que los usuarios que necesitaban
-	  imperiosamente una nueva función en particular
-	  (por ejemplo el poder ejecutar &os; en hardware moderno)
-	  estaban obligados a usar (por ejemplo) &os; 5.2.1 a pesar de
-	  que oficialmente era una release de uso exclusivo de
-	  desarrolladores, y sin tener en cuenta el hecho de que una
-	  release <literal>CURRENT</literal> no cumplía sus
-	  demandas.</para>
-      </listitem>
-
-      <listitem>
-	<para>En los casos en los que se consiguió la compatibilidad
-	  con versiones anteriores los desarrolladores se encontraron con otro
-	  problema al intentar adaptar ciertas características a una
-	  versión que ellos mismos hacía tiempo que no usaban
-	  como su plataforma de desarrollo principal.</para>
-       </listitem>
-
-      <listitem>
-	<para>El retraso también provocó que cuando 5.3 se
-	  declaró nueva release <literal>STABLE</literal> la
-	  cantidad acumulada de cambios hizo la actualización
-	  complicada.</para>
-      </listitem>
-    </itemizedlist>
-
-    <para>A decir verdad, nadie estaba contento con el resultado.</para>
-
-    <para>Las lecciones que se aprendieron de todo esto fueron:</para>
-
-    <itemizedlist>
-      <listitem>
-	<para>Las nuevas releases mayores deben tener meno cambios
-	  estructurales importantes y deben publicarse con mayor
-	  frecuencia.</para>
-      </listitem>
-
-      <listitem>
-	<para>Siempre que sea posible los cambios estructurales deben
-	  aislarse unos de otros.  Esto obliga a que parte del
-	  desarrollo tengan lugar fuera del árbol principal
-	  y que se integren solamente cuando no afecten a otros
-	  procesos simultáneos de desarrollo.</para>
-      </listitem>
-
-      <listitem>
-	<para>Las releases mayores deben tener fecha de salida
-	  propia no dependiente de la fecha de entrega asignada
-	  a un cambio estructural.  Si un cambio estructural no
-	  está listo a tiempo se incluirá desactivado
-	  por omisión y será incluido en la siguiente
-	  release.</para>
-      </listitem>
-    </itemizedlist>
-
-    <para>Al publicar grupos de cambios más pequeños y
-      de una forma más habitual se intenta también dedicar
-      menos tiempo y esfuerzo aplicando nuevas características de
-      <literal>HEAD</literal> a a la última versión
-      <literal>STABLE</literal> (y poder así usar dichas
-      nuevas características en más de una versión
-      mayor); aún más, al estar los cambios más
-      aislados el riesgo de provocar nuevos problemas de seguridad es
-      mucho menor.</para>
-
-    <para>Además, el concentrarse en una fecha y no en la
-      consecución de una característica lista para
-      integrarse en el sistema, es más fácil planificar
-      para el futuro tanto para los usuarios como a los desarrolladores
-      de aplicaciones ajenas al proyecto y, cómo no, para los
-      desarrolladores de &os;.</para>
-
-    <para>Estas razones (y no el intentar ir a la par de las versiones
-      mayores de otro sistema operativo) son el principal motivo del
-      cambio en el calendario de liberación de versiones de
-      &os;.</para>
-  </sect1>
-
-  <sect1 id="future-goals">
-    <title>Calendario de releases de aquí en adelante</title>
-
-    <para>Estos son los objetivos actuales del calendario del
-      Proyecto:</para>
-
-    <itemizedlist>
-      <listitem>
-	<para>Sacar uan release mayor cada 18 meses</para>
-      </listitem>
-
-      <listitem>
-	<para>Sacar una release menor cada 4 meses</para>
-      </listitem>
-
-      <listitem>
-	<para>Ofrecer paquetes compilados para la release menor más
-	  reciente de cada release mayor</para>
-      </listitem>
-
-      <listitem>
-	<para>Ofrecer actualizaciones de seguridad y otras correcciones de
-	  fallos críticos para las versiones menores más
-	  recientes de cada versión mayor (que reciben el nombre
-	  de <firstterm>ramas de seguridad</firstterm>).</para>
-      </listitem>
-    </itemizedlist>
-
-    <para>Dado el gran número de combinaciones de versiones
-      instalables no es posible dar soporte a todas las releases.
-      Esto es, en parte, debido a la cantidad limitada de máquinas
-      de las que el Proyecto puede disponer, pero sobre todo a que
-      la cantidad de voluntarios disponibles es limitada y su tiempo
-      también.</para>
-
-    <para>Si quiere leer más sobre esto visite</para>
-
-    <variablelist>
-      <varlistentry>
-        <term><ulink url="&url.base;/releng/index.html#schedule"></ulink></term>
-        <listitem>
-	  <para>Calendario de ingeniería de releases</para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-	<term><ulink url="&url.base;/security/security.html#supported-branches"></ulink></term>
-	<listitem>
-	  <para>Calendario de ramas de seguridad</para>
-	</listitem>
-      </varlistentry>
-    </variablelist>
-
-    <para>Estos documentos profundizan en los porqués de las
-      decisiones tomadas sobre las ramas soportadas y el ciclo de vida
-      de cada rama.</para>
-  </sect1>
-
-  <sect1 id="decision-points">
-    <title>?Cómo afectan estos factores a su decisión?</title>
-
-    <para>Los principales factores que influyen en su decisión de
-      qué versión instalar son, entre otros:</para>
-
-    <itemizedlist>
-      <listitem>
-	<para>?Qué grado de estabilidad necesita su
-	  sistema?</para>
-      </listitem>
-
-      <listitem>
-	<para>?Cuántos trabajo quiere dedicar a la
-	  actualización?</para>
-      </listitem>
-
-      <listitem>
-	<para>?Durante cuánto tiempo va a usar una
-	  versión dada entre una actualización y la
-	  que venga más adelante?</para>
-      </listitem>
-
-      <listitem>
-	<para>?Cuánta importancia le da a la seguridad de su
-	  sistema?</para>
-      </listitem>
-
-      <listitem>
-	<para>?Instalará desde código fuente o
-	  binarios?</para>
-      </listitem>
-
-      <listitem>
-	<para>?Va a participar en el desarrollo de &os;?</para>
-      </listitem>
-    </itemizedlist>
-
-    <para>Aquí hay unas normas para ayudarle a tomar una
-      decisión:</para>
-
-    <itemizedlist>
-      <listitem>
-	<para>Si sus necesidades son a corto plazo y quiere disfrutar del
-	  más alto grado posible de estabilidad (y no puede
-	  dedicar muchos recursos a la actualización) probablemente
-	  lo mejor sea instalar la release <literal>STABLE</literal>
-	  más reciente y dejarla como está.  Según
-	  sean sus requisitos de seguridad puede o no aplicar los
-	  parches de seguridad que vayan apareciendo.</para>
-      </listitem>
-
-      <listitem>
-	<para>Si sus necesidades son a corto plazo y las nuevas
-	  características o la seguridad son muy
-	  importantes para usted (y está dispuesto a dedicar
-	  tiempo a las actualizaciones) debería seguir la
-	  rama <literal>STABLE</literal> más reciente.</para>
-      </listitem>
-
-      <listitem>
-	<para>Si no va a poner la máquina en producción,
-	  va a dedicar tiempo a depurar unos cuantos problemas y en
-	  unos cuantos meses va a salir una nueva versión mayor,
-	  puede instalar esa rama y ayudar al Proyecto haciendo pruebas
-	  para hacer el sistema más estable y disponer de la
-	  mejor release posible a medio y largo plazo.</para>
-      </listitem>
-
-      <listitem>
-	<para>Sólamente si quiere instalar desde código
-	  fuente y pasar tiempo depurando problemas del sistema base,
-	  enviar informes de fallos y utilizar las listas de correo
-	  dedicadas a esos fallos debe usar
-	  <literal>HEAD</literal>.</para>
-      </listitem>
-    </itemizedlist>
-  </sect1>
-
-  <sect1 id="conclusion">
-    <title>Conclusión</title>
-
-    <para>Esperamos que este artículo haya servido de ayuda
-      para que comprender el modelo de desarrollo de &os; y
-      pueda decidir qué versión se ajusta más a sus
-      necesidades.</para>
-  </sect1>
-</article>
diff --git a/es_ES.ISO8859-1/articles/zip-drive/Makefile b/es_ES.ISO8859-1/articles/zip-drive/Makefile
deleted file mode 100644
index 886e21cc9d..0000000000
--- a/es_ES.ISO8859-1/articles/zip-drive/Makefile
+++ /dev/null
@@ -1,14 +0,0 @@
-# $FreeBSD$
-
-DOC?= article
-
-FORMATS?= html
-
-INSTALL_COMPRESSED?=gz
-INSTALL_ONLY_COMPRESSED?=
-
-SRCS= article.sgml
-
-DOC_PREFIX?= ${.CURDIR}/../../..
-
-.include "${DOC_PREFIX}/share/mk/doc.project.mk"
diff --git a/es_ES.ISO8859-1/articles/zip-drive/article.sgml b/es_ES.ISO8859-1/articles/zip-drive/article.sgml
deleted file mode 100644
index 89d7190c6f..0000000000
--- a/es_ES.ISO8859-1/articles/zip-drive/article.sgml
+++ /dev/null
@@ -1,327 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1" standalone="no"?>
-<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V4.2-Based Extension//EN"
-	"../../../share/sgml/freebsd42.dtd" [
-<!ENTITY % entities PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Entity Set//ES" "../../share/sgml/entities.ent">
-%entities;
-]>
-
-<!-- $FreeBSD$ -->
-
-<article lang="es">
-  <articleinfo>
-    <title>Unidades ZIP</title>
-
-    <authorgroup>
-      <author>
-	<firstname>Jason</firstname>
-	<surname>Bacon</surname>
-
-	<affiliation>
-	  <address><email>acadix@execpc.com</email></address>
-	</affiliation>
-      </author>
-    </authorgroup>
-   <abstract>
-     &trans.es.bazcar;
-   </abstract>
-
-   <pubdate>$FreeBSD$</pubdate>
-
-   <releaseinfo>$FreeBSD$</releaseinfo>
-  </articleinfo>
-
-  <sect1>
-    <title>Introducción a las Unidades ZIP</title>
-
-    <para>Los discos ZIP son dispositivos magnéticos,
-      extraíbles y de alta capacidad que pueden leerse y
-      escribirse mediante unidades ZIP de IOMEGA. Los discos ZIP son
-      similares a los disquetes (floppy) pero son mucho más
-      rápidos y ofrecen una capacidad de almacenamiento mucho
-      mayor.  Así como los disquetes suelen ser de 1'44 MB los
-      discos ZIP existen en dos tamaños, de 100 y 250 MB.  Los
-      discos ZIP no deben ser confundidos con el formato super-floppy,
-      un dispositivo que usa disquetes de 120 MB pero que admite los
-      discos tradicionales de 1'44 MB.</para>
-
-    <para>IOMEGA distribuye asímismo unidades de rendimiento
-      más alto y mucha mayor capacidad llamadas JAZZ.  Las
-      unidades JAZZ usan discos de 1 y 2 GB.</para>
-
-    <para>Las unidades ZIP están disponibles como dispositivos
-      internos y externos y emplean una de los siguientes
-      interfaces:</para>
-
-    <orderedlist>
-      <listitem>
-        <para>El interfaz SCSI es el más rápido, sofisticado,
-          expandible y caro.  El interfaz SCSI se usa en todo tipo de
-          plataformas, desde PC y estaciones RISC a miniordenadores para
-          conectar todo tipo de periféricos como discos duros,
-          unidades de cinta, scanners, etc.  Los dispositivos ZIP SCSI pueden
-          ser internos o externos, que requieren que la controladora SCSI
-          disponga de un conector externo.</para>
-
-	<note>
-          <para>Si usa una unidad SCSI externa es importante que nunca
-            la conecte o desconecte del bus SCSI mientras el ordenador
-            está funcionando.  Si lo hace puede causar daños
-            en el sistema de ficheros del resto de los discos del
-            sistema.</para>
-	</note>
-
-        <para>Si lo que busca es el máximo rendimiento y una
-          sencilla configuración el interfaz SCSI es la mejor
-          elección.  Probablemente tendrá que
-          añadir una controladora SCSI dado que la mayoría
-          de los PC (salvo los servidores de alto rendimiento) no
-          ofrecen soporte SCSI integrado.  Cada controladora SCSI puede
-          admitir entre 7 y 15 dispositivos SCSI dependiendo del
-          modelo.</para>
-
-        <para>Cada unidad SCSI tiene su propio controlador y
-          esos controladores son razonablemente inteligentes y
-          están bien estandarizados (la segunda S de SCSI
-          viene de Standard), de manera que desde el punto de vista
-          del sistema operativo, todos los dispositivos SCSI parecen
-          ser el mismo, como sucede con las unidades de cinta
-          SCSI, etc.  Para poder utilizar dispositivos SCSI el
-          sistema operativo necesita únicamente un
-          <quote>driver</quote> específico para la controladora
-          que se desea usar y un <quote>driver</quote> genérico
-          para cada tipo de dispositivo, ésto es, un disco SCSI,
-          una unidad de cinta SCSI, etc.  Algunos dispositivos SCSI pueden
-          ser mejor aprovechados mediante <quote>drivers</quote>
-          especializados (v.g. unidades de cinta DAT) pero tienden a
-          funcionar perfectamente con los <quote>drivers</quote>
-          genéricos, que sencillamente puede que no incluyan alguna
-          de las características especiales.</para>
-
-        <para>El usar una unidad ZIP SCSI es algo tan simple como determinar
-          cuál es el fichero de dispositivo en el directorio
-	  <filename>/dev</filename> que representa la unidad
-          ZIP.  Esto puede saberse examinando el mensaje de arranque
-          de FreeBSD (o en <filename>/var/log/messages</filename> tras
-          el arranque), donde debería encontrar algo parecido
-          a:</para>
-
-	<programlisting>da1: &lt;IOMEGA ZIP 100 D.13&gt; Removable Direct Access SCSI-2 Device</programlisting>
-
-        <para>Esto significa que la unidad ZIP está representada por
-           el fichero <filename>/dev/da1</filename>.</para>
-      </listitem>
-
-      <listitem>
-        <para>El interfaz IDE es un interfaz de acceso a discos duros de
-          bajo coste que se usa en la mayoría de los PC de
-          escritorio.  La mayoría de los dispositivos IDE son
-          exclusivamente internos.</para>
-
-        <para>El rendimiento de los dispositivos ZIP IDE es comparable al
-          de los ZIP SCSI.  (El interfaz IDE no es tan rápido como el
-          SCSI pero el rendimiento de los dispositivos ZIP está
-          condicionado principalmente por la parte mecánica del
-          dispositivo, no por el interfaz del bus).</para>
-
-        <para>El inconveniente del interfaz IDE son las limitaciones que
-          conlleva.  La mayoría de adaptadores IDE sólo
-          permiten utilizar dos dispositivos y generalmente los interfaces
-          IDE no están diseñados para perpetuarse en el
-          tiempo.  Por ejemplo, el interfaz IDE original no admite
-          discos duros con más de 1.024 cilindros, lo que
-          obligó a mucha gente a actualizar su hardware antes de lo
-          esperado.  Si prevé añadir nuevo hardware a su PC
-          (otro disco duro, una unidad de cinta, un scanner, etc.) no
-          estaría de más que considerara la idea de adquirir
-          una controladora y un ZIP SCSI para evitar problemas en el
-          futuro.</para>
-
-        <para>En FreeBSD los dispositivos IDE llevan el prefijo
-          <literal>a</literal>.  Por ejemplo, un disco duro IDE
-          podría ser
-	  <filename>/dev/ad0</filename>, y un CDROM IDE (ATAPI)
-          podría ser
-	  <filename>/dev/acd1</filename>, y así sucesivamente.</para>
-      </listitem>
-
-      <listitem>
-        <para>El interfaz de puerto paralelo es muy común en
-          dispositivos externos portátiles como dispositivos
-          ZIP externos y scanners debido a que virtualmente todos los
-          ordenadores disponen de un puerto paralelo estándar
-          (que generalmente se usa con impresoras).  De éste modo
-          se le facilitan las cosas a mucha gente a la hora de transferir
-          datos entre distintos equipos.</para>
-
-        <para>Generalmente el rendimiento es menor que el de dispositivos
-          ZIP IDE o SCSI dadas las limitaciones de velocidad del puerto
-          paralelo.  Ésta puede variar según el caso concreto
-          y con frecuencia puede configurarse en la BIOS del
-          sistema.  En algunos casos es imprescindible configurar en la
-          BIOS el puerto paralelo para que admita el modo bidireccional
-          puesto que los puertos paralelos fueron originalmente concebidos
-          para verter su salida hacia las impresoras.</para>
-      </listitem>
-    </orderedlist>
-  </sect1>
-
-  <sect1>
-    <title>ZIP de Puerto Paralelo: El <quote>driver</quote> <devicename>vpo
-      </devicename></title>
-
-    <para>Para usar en FreeBSD un dispositivo ZIP de puerto paralelo debe
-      incluírse en el kernel el <quote>driver</quote> <devicename>vpo
-      </devicename>.  Los
-      dispositivos ZIP de puerto paralelo disponen de un controlador SCSI
-      integrado.  El <quote>driver</quote> vpo permite al kernel de FreeBSD
-      comunicarse con el controlador SCSI del dispositivo ZIP a través
-      del puerto paralelo.</para>
-
-    <para>Dado que el <quote>driver</quote> vpo no forma parte del kernel
-      GENERIC (el kernel que se instala con FreeBSD) a partir de FreeBSD 3.2
-      necesita recompilar su kernel para activar éste
-      dispositivo.  Una de las maneras de recompilar el kernel se detalla
-      más adelante en éste mismo texto.  Los pasos a seguir
-      para activar el <quote>driver</quote> vpo podrían ser los
-      siguientes:</para>
-
-    <orderedlist>
-      <listitem>
-        <para>Ejecute <command>/stand/sysinstall</command> e instale los
-          fuentes del kernel en su sistema.</para>
-      </listitem>
-
-      <listitem>
-        <para>Crearemos un fichero de configuración del kernel
-          que incluya el <quote>driver</quote> vpo:</para>
-
-	<screen>&prompt.root; <userinput>cd /sys/i386/conf</userinput>
-&prompt.root; <userinput>cp GENERIC MIKERNEL</userinput></screen>
-
-        <para>Editamos <filename>MIKERNEL</filename> para sustituír
-          la entrada <literal>ident</literal> por <literal>MIKERNEL</literal>
-          y descomentamos la línea en la que aparece el <quote>driver
-          </quote>vpo.</para>
-
-        <para>Si dispone de un segundo puerto paralelo deberá
-          copiar la sección <literal>ppc0</literal> para crear
-          el dispositivo <literal>ppc1</literal>.  El segundo puerto
-          paralelo suele usar la IRQ 5 y la dirección
-          378.  Solamente es imprescindible asignar la IRQ en
-          el fichero de configuración.</para>
-
-        <para>Si su disco duro principal es SCSI puede tener problemas
-          durante la prueba de dispositivos SCSI que FreeBSD efectúa
-          en el arranque, dado que el sistema puede intentar utilizar el
-          dispositivo ZIP como disco de inicio.  Esto produciría un
-          fallo en el arranque salvo, claro está, que disponga de
-          un sistema de ficheros raíz en su disco ZIP.  Si ese es
-          su caso debe forzar al kernel a enlazar un dispositivo concreto
-          (en éste caso su disco duro raíz) con
-          <filename>/dev/da0/</filename>. El kernel asignará al
-          disco ZIP el siguiente nombre SCSI disponible, es decir,
-          <literal>/dev/da1</literal>.  Para fijar su disco duro SCSI como
-          <literal>da0</literal> cambie la línea
-
-	  <programlisting>device  da0</programlisting>
-
-	  a
-
-	  <programlisting>disk da0 at scbus0 target 0 unit 0</programlisting></para>
-
-        <para>Quizás necesite modificar la línea anterior para
-          que concuerde con los datos de su dispositivo SCSI.  Del mismo modo
-          tendría que asociar la entrada scbus0 con su controladora.
-          Por ejemplo, si tiene una controladora Adaptec 15xx debería
-          cambiar
-
-	  <programlisting>controller scbus0</programlisting>
-
-	  por
-
-	  <programlisting>controller scbus0 at aha0</programlisting></para>
-
-        <para>Para concluír, dado que está creando un kernel
-          personalizado debería aprovechar la ocasión para
-          eliminar todos los <quote>drivers</quote> que no necesita.  Esto
-          debe hacerse con precaución y solamente cuando tenga
-          la seguridad de que sabe lo que está haciendo con su fichero
-          de configuración.  Si borra los <quote>drivers</quote> que
-          no necesita reducirá el tamaño de su kernel y por
-          lo tanto dispondrá de más memoria que ofrecer a sus
-          aplicaciones.  Para saber qué <quote>drivers</quote> puede
-          borrar vaya al final del fichero <filename>/var/log/messages
-          </filename> y busque líneas que incluyan <literal>not
-           found</literal> (no encontrado).  Comente las líneas de
-          esos <quote>drivers</quote> en su fichero de
-          configuración. Puede cambiar otras opciones más
-          para reducir el tamaño e incrementar la velocidad de su
-          kernel. Lea la sección del Handbook correspondiente a la
-          recompilación del kernel para conocer todos los
-          detalles.</para>
-      </listitem>
-
-      <listitem>
-        <para>Ha llegado el momento de compilar nuestro kernel:</para>
-
-	<screen>&prompt.root; <userinput>/usr/sbin/config MIKERNEL</userinput>
-&prompt.root; <userinput>cd ../../compile/MIKERNEL</userinput>
-&prompt.root; <userinput>make clean depend &amp;&amp; make all install</userinput></screen>
-      </listitem>
-    </orderedlist>
-
-    <para>Una vez finalizado el proceso necesitará
-      reiniciar.  Asegúrese de que la unidad ZIP esté conectada
-      al puerto paralelo antes del arranque.  Verá aparecer el
-      dispositivo ZIP en los mensajes del arranque como vpo0 o vpo1,
-      dependiendo del puerto paralelo al que esté
-      conectado.  Debería aparecer también a qué
-      nombre de dispositivo ha sido enlazado.  Por ejemplo
-      sería <filename>/dev/da0</filename> si no hay en el sistema
-      discos SCSI o <filename>/dev/da1</filename> si tiene como dispositivo
-      principal un disco SCSI.</para>
-  </sect1>
-
-  <sect1>
-    <title>Cómo montar discos ZIP</title>
-
-    <para>Para acceder a un disco ZIP simplemente hay que montarlo como
-      cualquier otro dispositivo de disco.  El sistema de ficheros
-      estará representado como <quote>slice</quote> 4 dentro del
-      dispositivo, tanto para discos SCSI o paralelos. Por ejemplo:</para>
-
-    <screen>&prompt.root; <userinput>mount_msdos /dev/da1s4 /mnt</userinput></screen>
-
-    <para>Para unidades ZIP IDE, utilice:</para>
-
-    <screen>&prompt.root; <userinput>mount_msdos /dev/ad1s4 /mnt</userinput></screen>
-
-    <para>Puede serle útil modificar <filename>/etc/fstab</filename>
-      para montar los discos más fácilmente.  Añada una
-      línea como la siguiente (con las modificaciones necesarias para
-      sus necesidades):
-
-      <programlisting>/dev/da1s4  /zip msdos rw,noauto  0 0</programlisting>
-
-      y crée el directorio <filename>/zip</filename>.</para>
-
-    <para>Hecho esto, puede montar su disco ZIP escribiendo:
-
-      <screen>&prompt.root; <userinput>mount /zip</userinput></screen>
-
-      y para desmontarlo escriba
-
-      <screen>&prompt.root; <userinput>umount /zip</userinput></screen></para>
-
-    <para>Tiene todos los detalles del formato en el que incluír
-       o modificar entradas en <filename>/etc/fstab</filename> en
-      &man.fstab.5;.</para>
-
-    <para>Si quiere puede crear un sistema de ficheros de FreeBSD en un
-      disco ZIP empleando &man.newfs.8;.  Sin embargo eso convertiría
-      a ese disco en legible solamente en un sistema FreeBSD y
-      y quizás en unos pocos sistemas clónicos de &unix;
-      que reconocen el sistema de ficheros de FreeBSD. En cualquier caso
-      DOS y Windows <emphasis>no</emphasis> están entre ellos.</para>
-  </sect1>
-</article>
diff --git a/fr_FR.ISO8859-1/articles/Makefile b/fr_FR.ISO8859-1/articles/Makefile
index 1e5186cc40..0bbbe84584 100644
--- a/fr_FR.ISO8859-1/articles/Makefile
+++ b/fr_FR.ISO8859-1/articles/Makefile
@@ -12,13 +12,9 @@ SUBDIR+= contributing
 SUBDIR+= contributing-ports
 SUBDIR+= contributors
 SUBDIR+= cvsup-advanced
-SUBDIR+= dialup-firewall
-SUBDIR+= diskless-x
-SUBDIR+= euro
 SUBDIR+= explaining-bsd
 SUBDIR+= filtering-bridges
 SUBDIR+= fonts
-SUBDIR+= formatting-media
 SUBDIR+= ip-aliasing
 SUBDIR+= ipsec-must
 SUBDIR+= java-tomcat
@@ -26,7 +22,6 @@ SUBDIR+= laptop
 SUBDIR+= linux-users
 SUBDIR+= make-world
 SUBDIR+= mh
-SUBDIR+= multi-os
 SUBDIR+= nanobsd
 SUBDIR+= new-users
 SUBDIR+= ntfs
@@ -37,7 +32,6 @@ SUBDIR+= problem-reports
 SUBDIR+= programming-tools
 SUBDIR+= pxe
 SUBDIR+= releng-packages
-SUBDIR+= zip-drive
 
 ROOT_SYMLINKS+= new-users
 
diff --git a/fr_FR.ISO8859-1/articles/dialup-firewall/Makefile b/fr_FR.ISO8859-1/articles/dialup-firewall/Makefile
deleted file mode 100644
index b4e09dedad..0000000000
--- a/fr_FR.ISO8859-1/articles/dialup-firewall/Makefile
+++ /dev/null
@@ -1,21 +0,0 @@
-#
-#    The FreeBSD Documentation Project
-#    The FreeBSD French Documentation Project
-#
-#    $FreeBSD$
-#    Original revision: 1.1
-#
-
-
-DOC?= article
-
-FORMATS?= html
-
-INSTALL_COMPRESSED?=gz
-INSTALL_ONLY_COMPRESSED?=
-
-SRCS= article.sgml
-
-DOC_PREFIX?= ${.CURDIR}/../../..
-
-.include "${DOC_PREFIX}/share/mk/doc.project.mk"
diff --git a/fr_FR.ISO8859-1/articles/dialup-firewall/article.sgml b/fr_FR.ISO8859-1/articles/dialup-firewall/article.sgml
deleted file mode 100644
index 305577f417..0000000000
--- a/fr_FR.ISO8859-1/articles/dialup-firewall/article.sgml
+++ /dev/null
@@ -1,417 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1" standalone="no"?>
-<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V4.2-Based Extension//EN"
-	"../../../share/sgml/freebsd42.dtd" [
-<!ENTITY % entities PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Entity Set//FR" "../../share/sgml/entities.ent">
-%entities;
-<!ENTITY % not.published "IGNORE">
-]>
-
-<!--
-     The FreeBSD Documentation Project
-     The FreeBSD French Documentation Project
-
-     $FreeBSD$
-     $Id: article.sgml,v 1.4 2007-01-20 13:34:48 blackend Exp $
-     Original revision: 1.25
--->
-
-<article lang="fr">
-  <articleinfo>
-    <title>Coupe-feu pour connexion par modem avec FreeBSD</title>
-
-    <authorgroup>
-      <author>
-	<firstname>Marc</firstname>
-	<surname>Silver</surname>
-
-	<affiliation>
-	  <address><email>marcs@draenor.org</email></address>
-	</affiliation>
-      </author>
-    </authorgroup>
-
-    <pubdate>$FreeBSD$</pubdate>
-
-    <releaseinfo>$FreeBSD$</releaseinfo>
-
-    <abstract>
-      <para>Cet article expose comment mettre en place un coupe-feu
-        utilisant une connexion PPP par modem avec FreeBSD et IPFW, et
-	spécifiquement l'utilisation de coupe-feux pour une connexion par
-	modem avec adresse IP dynamique.  Ce document ne couvre pas en
-	premier lieu la configuration de votre connexion PPP.</para>
-
-        &trans.a.fonvieille;
-    </abstract>
-  </articleinfo>
-
-  <sect1 id="preface">
-    <title>Préface</title>
-
-    <para>Coupe-feu pour connexion par modem avec FreeBSD</para>
-
-     <para>Ce document couvre le processus requis pour configurer un
-       coupe-feu avec FreeBSD quand votre fournisseur d'accès vous
-       assigne une adresse IP dynamique.  Alors que de nombreux efforts
-       ont été faits afin de rendre ce document aussi instructif et
-       correct que possible, vous êtes encouragés &agrave; envoyer vos
-       commentaires/suggestions &agrave; l'adresse
-       <email>marcs@draenor.org</email>.</para>
-   </sect1>
-
-  <sect1 id="kernel">
-    <title>Options du noyau</title>
-
-    <para>La première chose dont vous aurez besoin est de recompiler votre
-      noyau.  Si vous avez besoin de plus d'informations sur comment
-      recompiler un noyau, alors le meilleur endroit pour commencer est
-      la <ulink url="../../books/handbook/kernelconfig.html">section de
-      configuration du noyau du manuel</ulink>.  Vous devez rajouter les
-      options suivantes dans le fichier de configuration de votre
-      noyau:</para>
-
-    <variablelist>
-      <varlistentry>
-	<term><literal>options IPFIREWALL</literal></term>
-
-	<listitem>
-	  <para>Intègre au noyau le code de filtrage de paquets.</para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-	<term><literal>options IPFIREWALL_VERBOSE</literal></term>
-
-	<listitem>
-	  <para>Envoie les paquets tracés au système de traces.</para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-	<term><literal>options
-	    IPFIREWALL_VERBOSE_LIMIT=<replaceable>100</replaceable></literal></term>
-
-	<listitem>
-	  <para>Limite le nombre de paquets similaires tracés.  Cela
-	    évite que votre fichier de traces soit submergé de nombreuses
-	    entrées répétées.  <replaceable>100</replaceable> est une
-	    valeur raisonnable, mais vous pouvez l'ajuster en fonction
-	    de vos besoins.</para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-	<term><literal>options IPDIVERT</literal></term>
-
-	<listitem>
-	  <para>Autorise le <emphasis>détournement</emphasis> des
-	  sockets, cela sera explicité plus tard.</para>
-	</listitem>
-      </varlistentry>
-    </variablelist>
-
-    <para>Il y a d'autres éléments <emphasis>optionnels</emphasis> que
-      vous pouvez rajouter dans le noyau pour plus de sécurité.  Ils ne
-      sont pas requis pour avoir un filtrage de paquets qui fonctionne,
-      mais il se peut que quelques utilisateurs un peu plus paranoïaques
-      désirent les utiliser.</para>
-
-    <variablelist>
-      <varlistentry>
-	<term><literal>options TCP_DROP_SYNFIN</literal></term>
-
-	<listitem>
-	  <para>Cette option ignore les paquets TCP avec les indicateurs
-	    SYN et FIN activés.  Cela empêche certains utilitaires tel
-	    que nmap etc. d'identifier la pile TCP/IP de la machine,
-	    mais cela rompt le support des extensions RFC1644.  Cela
-	    <emphasis>n'est pas</emphasis> recommandé si la machine
-	    héberge un serveur web.</para>
-	</listitem>
-      </varlistentry>
-     </variablelist>
-
-    <para>Ne pas redémarrer une fois que vous avez recompilé le noyau.
-      Avec un peu de chance, nous n'aurons besoin de redémarrer qu'une
-      fois pour achever l'installation du coupe-feu.</para>
-  </sect1>
-
-  <sect1 id="rcconf">
-    <title>Modifier <filename>/etc/rc.conf</filename> pour charger le
-      coupe-feu</title>
-
-    <para>Nous avons maintenant besoin de quelques modifications de
-      <filename>/etc/rc.conf</filename> afin de signaler notre
-      coupe-feu.  Ajoutez simplement les lignes suivantes:</para>
-
-    <programlisting>firewall_enable="YES"
-firewall_script="/etc/firewall/fwrules"
-natd_enable="YES"
-natd_interface="tun0"
-natd_flags="-dynamic"</programlisting>
-
-    <para>Pour plus d'informations sur la fonction de ces éléments
-      jetez un coup d'oeil &agrave; <filename>/etc/defaults/rc.conf</filename>
-      et lisez la page de manuel &man.rc.conf.5;.</para>
-  </sect1>
-
-  <sect1>
-    <title>Désactiver la traduction d'adresse réseau de PPP</title>
-
-    <para>Il se peut que vous utilisiez déj&agrave; la traduction d'adresse
-      réseau (NAT) intégrée &agrave; PPP.  Si c'est le cas alors vous aurez &agrave;
-      la désactiver, étant donné que nos exemples utilisent &man.natd.8;
-      pour faire la même chose.</para>
-
-    <para>Si vous avez déj&agrave; un ensemble d'options pour démarrer
-      automatiquement PPP, cela doit probablement ressembler &agrave;
-      ceci:</para>
-
-    <programlisting>ppp_enable="YES"
-ppp_mode="auto"
-ppp_nat="YES"
-ppp_profile="<replaceable>profile</replaceable>"</programlisting>
-
-    <para>Si c'est le cas, vous devrez spécifiquement désactiver
-      <literal>ppp_nat</literal> en vous assurant que vous avez bien
-      la ligne <literal>ppp_nat="NO"</literal> dans
-      <filename>/etc/rc.conf</filename>. Vous devrez également
-      retirer les lignes <literal>nat enable yes</literal> ou
-      <literal>alias enable yes</literal> de
-      <filename>/etc/ppp/ppp.conf</filename>.</para>
-  </sect1>
-
-  <sect1 id="rules">
-    <title>Le jeu de règles pour le coupe-feu</title>
-
-    <para>Nous avons presque terminé.  Tout ce qu'il reste &agrave; faire est
-      de définir les règles du coupe-feu et alors nous pourrons
-      redémarrer, et notre coupe-feu devrait fonctionner.  Je me suis rendu
-      compte que chacun désirera quelque chose de légèrement différent
-      quand il est question de son ensemble de règles.  Ce que j'ai
-      essayé de faire est d'écrire un ensemble de règles qui conviendra
-      &agrave; la plupart des utilisateurs de modems.  Vous pouvez bien
-      évidement le modifier selon vos besoins en utilisant les règles
-      suivantes comme fondation pour votre propre ensemble de règles.
-      Tout d'abord commençons avec les bases du filtrage fermé.  Ce que
-      vous voulez faire est de refuser tout par défaut et ensuite
-      n'autoriser que les choses dont vous avez vraiment besoin.  Les
-      règles devraient être ordonnées de façon &agrave; autoriser tout d'abord
-      puis ensuite refuser.  Le principe est que vous ajoutiez les règles
-      pour vos autorisations, et ensuite tout est refusé. :)</para>
-
-    <para>Maintenant, créons le répertoire <filename
-      class="directory">/etc/firewall</filename>.  Allez dans ce
-      répertoire et éditez le fichier <filename>fwrules</filename> comme
-      nous l'avons spécifié dans <filename>rc.conf</filename>.  S'il
-      vous plaît, notez que vous pouvez changer le nom de ce fichier
-      pour celui que vous désirez.  Ce guide donne juste un exemple de
-      nom de fichier.</para>
-
-    <para>Maintenant, jettons un coup d'oeil &agrave; cet exemple de fichier de
-      coupe-feu, qui est minutieusement commenté.</para>
-
-    <programlisting># Règles du coupe-feu
-# Ecrit par Marc Silver (marcs@draenor.org)
-# http://draenor.org/ipfw
-# Librement distribuable
-
-
-# Définie la commande du coupe-feu (comme dans /etc/rc.firewall)
-# pour une référence aisée. Facilite la lecture.
-fwcmd="/sbin/ipfw"
-
-# Vide les règles actuelles avant rechargement.
-$fwcmd -f flush
-
-# Détourne tous les paquets &agrave; travers l'interface tunnel
-$fwcmd add divert natd all from any to any via tun0
-
-# Autorise toutes les données de ma carte réseau et de l'hôte local.
-# Soyez sûr de changer votre carte réseau (la mienne était fxp0) avant
-# de redémarrer.  :)
-$fwcmd add allow ip from any to any via lo0
-$fwcmd add allow ip from any to any via fxp0
-
-# Autorise toute les connexions dont je suis l'initiateur.
-$fwcmd add allow tcp from any to any out xmit tun0 setup
-
-# Une fois les connexions établies, les autorise &agrave; rester ouvertes.
-$fwcmd add allow tcp from any to any via tun0 established
-
-# Tous le monde sur internet est autorisé &agrave; se connecter aux services
-# suivants sur la machine.  Cet exemple autorise spécifiquement les
-# connexions &agrave; ssh et apache.
-$fwcmd add allow tcp from any to any 80 setup
-$fwcmd add allow tcp from any to any 22 setup
-
-# Ceci envoie un RESET &agrave; tous les paquets ident.
-$fwcmd add reset log tcp from any to any 113 in recv tun0
-
-# Autorise les requettes DNS sortantes SEULEMENT vers les serveurs
-# spécifiés.
-$fwcmd add allow udp from any to <replaceable>x.x.x.x</replaceable> 53 out xmit tun0
-
-# Autorise leur retour avec les réponses...  :)
-$fwcmd add allow udp from <replaceable>x.x.x.x</replaceable> 53 to any in recv tun0
-
-# Autorise l'ICMP (pour permettre &agrave; ping et traceroute de fonctionner).
-# Vous pouvez peut-être désirer désactiver ceci, mais je pense que cela
-# répond &agrave; mes besoins de les conserver ainsi.
-$fwcmd add allow icmp from any to any
-
-# Bloque tout le reste.
-$fwcmd add deny log ip from any to any</programlisting>
-
-    <para>Vous disposez désormais d'un coupe-feu tout &agrave; fait fonctionnel
-      qui autorisera les connexions sur les ports 80 et 22 et tracera
-      tout autre tentative de connexion.  Maintenant, vous devriez être
-      en mesure de redémarrer sans risques et votre coupe-feu devrait se
-      lancer sans problèmes.  Si vous trouvez une quelconque erreur ou
-      expérimentez des problèmes, ou que vous avez des suggestions pour
-      améliorer ce document, s'il vous plaît écrivez-moi.</para>
-  </sect1>
-
-  <sect1>
-    <title>Questions</title>
-
-    <qandaset>
-      <qandaentry>
-	<question>
-	  <para>Pourquoi utilisez-vous &man.natd.8; et &man.ipfw.8;
-	    alors que vous pourriez utiliser les filtres intégrés &agrave;
-	    &man.ppp.8;?
-	  </para>
-	</question>
-
-	<answer>
-	  <para>Je serais honnête et dirais qu'il n'y a aucune raison
-	    définitive pour que j'utilise <command>ipfw</command> et
-	    <command>natd</command> plutôt que les filtres intégrés &agrave;
-	    <command>ppp</command>.  D'après les discussions que j'ai eu
-	    avec de nombreuses personnes le consensus semble être
-	    qu'<command>ipfw</command> est certainement plus
-	    puissant et configurable que les filtres
-	    <command>ppp</command>, mais ce qu'il apporte dans la
-	    fonctionnalité il le perd en facilité d'utilisation.  Une
-	    des raisons de mon utilisation est que je préfère que le
-	    filtrage de paquets soit fait au niveau du noyau plutôt que
-	    par un programme utilisateur.</para>
-	</answer>
-      </qandaentry>
-
-      <qandaentry>
-        <question>
-	  <para>J'obtiens des messages du type <errorname>limit 100
-	    reached on entry 2800</errorname> et après cela je ne vois
-	    plus jamais de refus dans mes traces.  Mon coupe-feu
-	    fonctionne-t-il toujours?
-	  </para>
-        </question>
-
-	<answer>
-	  <para>Cela signifie simplement que le nombre maximal de
-	    traces pour la règle a été atteint.  La règle fonctionne
-	    toujours, mais elle n'enregistrera plus de trace jusqu'au
-	    moment ou vous réinitialiserez les compteurs de traces.
-	    Vous pouvez réinitialiser les compteurs de traces avec la
-	    commande <command>ipfw resetlog</command>.  Alternativement,
-	    vous pouvez augmenter la limite de trace dans la
-	    configuration de votre noyau avec l'option
-	    <option>IPFIREWALL_VERBOSE_LIMIT</option> comme décrit
-	    précédemment.  Vous pouvez également changer cette limite
-	    (sans recompiler votre noyau ou avoir &agrave; redémarrer) en
-	    utilisant la valeur &man.sysctl.8;
-	    net.inet.ip.fw.verbose_limit.</para>
-        </answer>
-      </qandaentry>
-
-      <qandaentry>
-	<question>
-	  <para>Si j'utilise des adresses privées en interne, comme
-	    dans la plage 192.168.0.0, pourrais-je ajouter une commande
-	    comme <literal>$fwcmd add deny all from any to
-	    192.168.0.0:255.255.0.0 via tun0</literal> aux règles du
-	    coupe-feu pour prévenir les tentatives externes de
-	    connexions vers les machines internes?</para>
-	</question>
-
-	<answer>
-	  <para>Une réponse simple est non.  La raison de cela est que
-            <command>natd</command> effectue la traduction d'adresse
-	    pour <emphasis>tout</emphasis> ce qui sera détourné &agrave;
-	    travers le périphérique <devicename>tun0</devicename>.  En
-	    ce qui concerne les paquets entrant, ces derniers ne
-	    parleront qu'&agrave; l'adresse IP dynamiquement assignée et
-	    <emphasis>non pas</emphasis> au réseau interne.  Notez que
-	    cependant vous pouvez ajouter une règle comme
-	    <literal>$fwcmd add deny all from 192.168.0.4:255.255.0.0 to
-	    any via tun0</literal> qui limiterait un hôte de votre réseau
-	    interne de sortir via le coupe-feu.</para>
-	</answer>
-      </qandaentry>
-
-      <qandaentry>
-	<question>
-	  <para>Il doit y avoir quelque chose d'erroné.  J'ai suivi vos
-	  instructions &agrave; la lettre et maintenant tout est bloqué.</para>
-        </question>
-
-	<answer>
-	  <para>Ce guide suppose que vous utilisez
-            <emphasis>userland-ppp</emphasis> aussi le jeu de règle
-	    donné intervient sur l'interface
-	    <devicename>tun0</devicename>, qui correspond &agrave; la première
-	    connexion établie avec &man.ppp.8; (a.k.a.
-	    <emphasis>user-ppp</emphasis>).  Les connexions
-	    supplémentaires utiliseront <devicename>tun1</devicename>,
-	    <devicename>tun2</devicename> et ainsi de suite.</para>
-
-	  <para>Vous devriez également noter que &man.pppd.8; utilise
-	    &agrave; la place l'interface <devicename>ppp0</devicename>, donc
-	    si vous établissez une connexion avec &man.pppd.8; vous
-	    devez remplacer <devicename>tun0</devicename> par
-	    <devicename>ppp0</devicename>.  Une façon rapide d'éditer
-	    les règles du coupe-feu pour refléter ce changement est
-	    présentée ci-dessous.  Le jeu de règles original est
-	    sauvegardé sous <filename>fwrules_tun0</filename>.</para>
-
-	  <screen>	    &prompt.user; <userinput>cd /etc/firewall</userinput>
-	    /etc/firewall&prompt.user; <userinput>su</userinput>
-	    <prompt>Password:</prompt>
-	    /etc/firewall&prompt.root; <userinput>mv fwrules fwrules_tun0</userinput>
-	    /etc/firewall&prompt.root; <userinput>cat fwrules_tun0 | sed s/tun0/ppp0/g > fwrules</userinput>
-	  </screen>
-
-	  <para>Pour savoir si vous utilisez actuellement &man.ppp.8; ou
-	    &man.pppd.8; vous pouvez examiner la sortie
-	    d'&man.ifconfig.8; une fois que la connexion est établie.
-	    E.g., pour une connexion faite par &man.pppd.8; vous verriez
-	    quelque chose comme ceci (on ne montre que les lignes
-	    importantes):</para>
-
-	  <screen>	    &prompt.user; <userinput>ifconfig</userinput>
-	    <emphasis>(skipped...)</emphasis>
-	    ppp0: flags=<replaceable>8051&lt;UP,POINTOPOINT,RUNNING,MULTICAST&gt; mtu 1524</replaceable>
-                    inet <replaceable>xxx.xxx.xxx.xxx</replaceable> --&gt; <replaceable>xxx.xxx.xxx.xxx</replaceable> netmask <replaceable>0xff000000</replaceable>
-	    <emphasis>(skipped...)</emphasis>
-	    </screen>
-
-	  <para>D'autre part, pour une connexion faite avec &man.ppp.8;
-	  (<emphasis>user-ppp</emphasis>) vous devriez voir quelque
-	  chose de similaire &agrave;:</para>
-
-	  <screen>	    &prompt.user; <userinput>ifconfig</userinput>
-	    <emphasis>(skipped...)</emphasis>
-	    ppp0: flags=<replaceable>8010&lt;POINTOPOINT,MULTICAST&gt; mtu 1500</replaceable>
-	    <emphasis>(skipped...)</emphasis>
-	    tun0: flags=<replaceable>8051&lt;UP,POINTOPOINT,RUNNING,MULTICAST&gt; mtu 1524</replaceable>
-	            <emphasis>(IPv6 stuff skipped...)</emphasis>
-                    inet <replaceable>xxx.xxx.xxx.xxx</replaceable> --&gt; <replaceable>xxx.xxx.xxx.xxx</replaceable> netmask <replaceable>0xffffff00</replaceable>
-                    Opened by PID <replaceable>xxxxx</replaceable>
-            <emphasis>(skipped...)</emphasis></screen>
-	</answer>
-      </qandaentry>
-    </qandaset>
-  </sect1>
-</article>
diff --git a/fr_FR.ISO8859-1/articles/diskless-x/Makefile b/fr_FR.ISO8859-1/articles/diskless-x/Makefile
deleted file mode 100644
index 72c1d9b8c9..0000000000
--- a/fr_FR.ISO8859-1/articles/diskless-x/Makefile
+++ /dev/null
@@ -1,20 +0,0 @@
-#
-#    The FreeBSD Documentation Project
-#    The FreeBSD French Documentation Project
-#
-#    $FreeBSD$
-#    Original revision: 1.4
-#
-
-DOC?= article
-
-FORMATS?= html
-
-INSTALL_COMPRESSED?=gz
-INSTALL_ONLY_COMPRESSED?=
-
-SRCS= article.sgml
-
-DOC_PREFIX?= ${.CURDIR}/../../..
-
-.include "${DOC_PREFIX}/share/mk/doc.project.mk"
diff --git a/fr_FR.ISO8859-1/articles/diskless-x/article.sgml b/fr_FR.ISO8859-1/articles/diskless-x/article.sgml
deleted file mode 100644
index 2d821c6bf6..0000000000
--- a/fr_FR.ISO8859-1/articles/diskless-x/article.sgml
+++ /dev/null
@@ -1,285 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1" standalone="no"?>
-<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V4.2-Based Extension//EN"
-	"../../../share/sgml/freebsd42.dtd" [
-<!ENTITY % entities PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Entity Set//FR" "../../share/sgml/entities.ent">
-%entities;
-<!ENTITY % not.published "IGNORE">
-]>
-
-<!--
-     The FreeBSD Documentation Project
-     The FreeBSD French Documentation Project
-
-     $FreeBSD$
-     Original revision: n.nn
--->
-
-<article lang="fr">
-  <articleinfo>
-    <title>Mise en oeuvre d'un terminal X sans disque dur</title>
-
-    <authorgroup>
-      <author>
-	<firstname> Jerry</firstname>
-	<surname>Kendall</surname>
-	<affiliation>
-	  <address>
-	    <email>jerry@kcis.com</email>
-	  </address>
-	</affiliation>
-      </author></authorgroup>
-
-    <pubdate>28 Décembre 1996</pubdate>
-
-    <copyright>
-      <year>1996</year>
-      <holder>Jerry Kendall</holder>
-    </copyright>
-
-    <releaseinfo>$FreeBSD$</releaseinfo>
-
-    <abstract>
-      <para>Avec l'aide de quelques amis de la &a.hackers;, j'ai pu mettre en service un terminal X sans disque dur. Pour cela, j'ai d'abord dû installer une station sans disque qui dispose d'un minimum d'utilitaires montés par NFS. J'ai répété l'opération pour disposer de deux systèmes sans disque. Pour les deux, j'ai procédé de la même façon. Le premier est <hostid role="fqdn">altair.kcis.com</hostid>. C'est un terminal X sur mon vieux 386DX-40. Il a bien un disque dur de 340 Mo, mais je ne voulais pas y toucher. Il démarre donc &agrave; partir de <hostid role="fqdn">antares.kcis.com</hostid> sur le réseau Ethernet. Le second est un 486DX2-66. J'ai installé un système FreeBSD (complet) qui n'utilise pas de disque local. Le serveur de démarrage est un Sun 670MP sous SunOs 4.1.3. Les deux systèmes FreeBSD sont configurés de la même façon.</para>
-
-      <para>Je suis sûr qu'il y a des choses &agrave; ajouter &agrave; ce document. Faites-moi s'il vous plaît part de vos commentaires.</para>
-
-      &trans.a.haby;
-    </abstract>
-  </articleinfo>
-
-  <sect1>
-    <title>Préparation de la disquette de démarrage (sur le système sans disque)</title>
-
-    <para>Les gestionnaires de démarrage via le réseau ne sont pas compatibles avec les TSRs et autres qu'utilise MS-DOS, il est préférable de préparer une disquette de démarrage, ou, si vous le pouvez, de mettre en place un menu MS-DOS qui (par l'intermédiaire des fichiers <filename>config.sys</filename>/<filename>autoexec.bat</filename>) vous demande au démarrage quelle configuration charger. C'est cette dernière méthode que j'ai utilisée et elle fonctionne &agrave; merveille. Voici mon menu MS-DOS&nbsp;:</para>
-
-    <example>
-      <title><filename>config.sys</filename></title>
-
-      <programlisting>[menu]
-menuitem=normal, normal
-menuitem=unix, unix
-[normal]
-....
-config.sys habituel
-...
-[unix]</programlisting>
-    </example>
-
-    <example>
-      <title><filename>autoexec.bat</filename></title>
-
-      <programlisting>@ECHO OFF
-goto %config%
-
-:normal
-...
-autoexec.bat habituel
-...
-goto end
-
-:unix
-cd \netboot
-nb8390.com
-
-:end</programlisting>
-    </example>
-  </sect1>
-
-  <sect1>
-    <title>Générer les programmes de démarrage en réseau (sur le serveur)</title>
-
-    <para>Compilez les programmes de &ldquo;démarrage en réseau&rdquo; que vous trouverez dans <filename>/usr/src/sys/i386/boot/netboot</filename>. Lisez les commentaires au début du <filename>Makefile</filename>. Faites les modifications nécessaires. Faites une sauvegarde de l'original, pour vous prémunir en cas de problèmes. Après compilation, vous devriez obtenir deux exécutables, <filename>nb8390.com</filename> et <filename>nb3c509.com</filename>. C'est l'un de ces programmes que vous devrez exécuter sur la machine sans disque. Il chargera le noyau depuis le serveur de démarrage. Recopiez alors ces deux programmes sur la disquette de démarrage que vous avez créée auparavant.</para>
-  </sect1>
-
-  <sect1>
-    <title>Déterminer le programme &agrave; utiliser (sur la machine sans disque)</title>
-
-    <para>Si vous savez quel composant utilise votre carte Ethernet, c'est facile. Si vous avez un circuit NS8390 ou équivalent, servez vous de <filename>nb8390.com</filename>. Si vous avez un circuit de type 3Com 509, utilisez le programme de démarrage <filename>nb3C509.com</filename>. Si vous ne savez pas, essayez l'un et si vous avez le message &ldquo;<errorname>No adapter found</errorname>&rdquo;, essayez avec l'autre. Si rien ne marche, vous êtes livré &agrave; vous-même.</para>
-  </sect1>
-
-  <sect1>
-    <title>Démarrer en réseau</title>
-
-    <para>Démarrez la station sans disque sans fichiers <filename>config.sys/autoexec.bat</filename>. Essayez d'exécuter le programme de démarrage qui correspond &agrave; votre carte Ethernet.</para>
-
-    <para>Ma carte Ethernet utilise le mode 16bit WD8013 16bit, j'exécute donc
-      <filename>nb8390.com</filename>&nbsp;:</para>
-
-    <screen><prompt>C:&gt;</prompt> <userinput>cd \netboot</userinput>
-<prompt>C:&gt;</prompt> <userinput>nb8390</userinput>
-
-<prompt>Boot from Network (Y/N) ?</prompt>  <userinput>Y</userinput>
-
-BOOTP/TFTP/NFS bootstrap loader     ESC for menu
-
-Searching for adapter..
-WD8013EBT base 0x0300, memory 0x000D8000, addr 00:40:01:43:26:66
-
-Searching for server...</screen>
-
-    <para>La machine sans disque essaye maintenant de trouver un serveur de démarrage. Notez la valeur de <literal>addr</literal> sur l'avant dernière ligne, vous en aurez besoin ensuite. Redémarrez la machine sans disque et modifiez vos
-fichiers <filename>config.sys</filename> et <filename>autoexec.bat</filename> pour qu'ils fassent automatiquement ce que vous venez de faire &agrave; la main. Peut-être avec un menu. Si vous aviez dû utiliser <command>nb3c509.com</command> au lieu de <command>nb8390.com</command>, les messages seraient identiques. Si vous obtenez le message &ldquo;<errorname>No adapter found</errorname>&rdquo; après &ldquo;<literal>Searching for adapter...</literal>&rdquo;, vérifiez que vous avez défini les bonnes valeurs dans le <filename>Makefile</filename> au moment de compiler.</para>
-  </sect1>
-
-  <sect1>
-    <title>Permettre aux systèmes de démarrer via le réseau (sur le serveur)</title>
-
-    <para>Vérifiez qu'il y a bien des entrées pour <citerefentry><refentrytitle>tftp</refentrytitle></citerefentry> et <citerefentry><refentrytitle>bootps</refentrytitle></citerefentry> dans le fichier <filename>/etc/inetd.conf</filename>. Voici le mien&nbsp;:</para>
-
-    <programlisting>tftp	dgram	udp	wait	nobody	/usr/libexec/tftpd	tftpd
-#
-# Ajout de qui que vous soyez
-bootps  dgram  udp  wait  root  /usr/libexec/bootpd bootpd /etc/bootptab</programlisting>
-
-    <para>Si vous devez modifier le fichier <filename>/etc/inetd.conf</filename>, envoyez ensuite un signal <literal>HUP</literal> &agrave; <citerefentry><refentrytitle>inetd</refentrytitle></citerefentry>. Pour cela, utilisez la commande <command>ps -ax | grep inetd | grep -v grep</command> pour connaître le numéro de processus d'<citerefentry><refentrytitle>inetd</refentrytitle></citerefentry>. Une fois que vous l'avez, envoyez lui le signal HUP. Cela se fait avec <command>kill -HUP &lt;pid&gt;</command>. Cela obligera <citerefentry><refentrytitle>inetd</refentrytitle></citerefentry> &agrave; relire ses fichiers de configuration.</para>
-
-    <para>Vous avez bien noté la valeur de <literal>addr</literal> dans les messages du programme de démarrage sur la machine sans disque&nbsp;? C'est maintenant que vous allez en avoir besoin.</para>
-
-    <para>Ajoutez une entrée &agrave; <literal>/etc/bootptab</literal> (vous devrez peut-être créer ce fichier). Voici &agrave; quoi elle doit ressembler&nbsp;:</para>
-
-    <programlisting>altair:\
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;:ht=ether:\
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;:ha=004001432666:\
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;:sm=255.255.255.0:\
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;:hn:\
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;:ds=199.246.76.1:\
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;:ip=199.246.76.2:\
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;:gw=199.246.76.1:\
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;:vm=rfc1048:</programlisting>
-
-    <para>Ce qui, ligne par ligne, signifie&nbsp;:</para>
-
-    <informaltable frame="none">
-      <tgroup cols="2">
-	<tbody>
-	  <row>
-	    <entry><literal>altair</literal></entry>
-	    <entry>nom du système sans disque, sans nom de domaine</entry>
-	  </row>
-
-	  <row>
-	    <entry><literal>ht=ether</literal></entry>
-            <entry>type matériel &ldquo;ethernet&rdquo;</entry>
-	  </row>
-
-	  <row>
-	    <entry><literal>ha=004001432666</literal></entry>
-	    <entry>adresse matérielle (le nombre que vous avez noté auparavant)</entry>
-	  </row>
-
-	  <row>
-	    <entry><literal>sm=255.255.255.0</literal></entry>
-	    <entry>masque de sous-réseau</entry>
-	  </row>
-
-	  <row>
-	    <entry><literal>hn</literal></entry>
-	    <entry>dit au serveur de donner au client son nom de machine</entry>
-	  </row>
-
-	  <row>
-	    <entry><literal>ds=199.246.76.1</literal></entry>
-	    <entry>dit au client quel est son serveur de noms de domaine</entry>
-	  </row>
-
-	  <row>
-	    <entry><literal>ip=199.246.76.2</literal></entry>
-	    <entry>dit au client quelle est son adresse IP</entry>
-	  </row>
-
-	  <row>
-	    <entry><literal>gw=199.246.76.1</literal></entry>
-	    <entry>dit au client quelle est sa passerelle par défaut</entry>
-	  </row>
-
-	  <row>
-	    <entry><literal>vm=...</literal></entry>
-	    <entry>laissez cela tel que</entry>
-	  </row>
-	</tbody>
-      </tgroup>
-    </informaltable>
-
-    <note>
-      <para>Veillez &agrave; bien définir les adresses IP, j'ai inventé celles de l'exemple.</para>
-
-    </note>
-
-    <para>Créez le répertoire <filename>/tftpboot</filename> sur le serveur. Il contiendra les fichiers de configuration pour les systèmes sans disque dont ce sera le serveur de démarrage. Ces fichiers s'appelleront <filename>cfg.&lt;ip&gt;</filename>, où &lt;ip&gt; est l'adresse IP de la machine sans disque. Le fichier de configuration pour &ldquo;altair&rdquo; est <filename>/tftpboot/cfg.199.246.76.2</filename>. Voici son contenu&nbsp;:</para>
-
-    <programlisting>rootfs 199.246.76.1:/DiskLess/rootfs/altair
-hostname altair.kcis.com</programlisting>
-
-    <para>La ligne <literal>hostname altair.kcis.com</literal> indique seulement au système sans disque quel est son nom qualifié.</para>
-
-    <para>La ligne <literal>rootfs 199.246.76.1:/DiskLess/rootfs/altair</literal> lui dit où est son système de fichiers racine qui sera monté par NFS.</para>
-
-    <note>
-      <para>Ce système de fichiers racine sera monté en <emphasis>lecture seule</emphasis> par NFS.</para>
-    </note>
-
-    <para>L'arborescence de la machine sans disque peut ensuite être remontée pour autoriser les opérations de lecture/écriture.</para>
-
-    <para>J'utilise mon 386DX-40 comme terminal X dédié.</para>
-
-    <para>Voici l'arborescence d'&ldquo;altair&rdquo;&nbsp;:</para>
-
-    <literallayout>/
-/bin
-/etc
-/tmp
-/sbin
-/dev
-/dev/fd
-/usr
-/var
-/var/run</literallayout>
-
-    <para>Et la liste des fichiers qu'elle contient&nbsp;:</para>
-
-    <screen>-r-xr-xr-x  1 root  wheel  779984 Dec 11 23:44 ./kernel
--r-xr-xr-x  1 root    bin  299008 Dec 12 00:22 ./bin/sh
--rw-r--r--  1 root  wheel     499 Dec 15 15:54 ./etc/rc
--rw-r--r--  1 root  wheel    1411 Dec 11 23:19 ./etc/ttys
--rw-r--r--  1 root  wheel     157 Dec 15 15:42 ./etc/hosts
--rw-r--r--  1 root    bin    1569 Dec 15 15:26 ./etc/XF86Config.altair
--r-x------  1 bin     bin  151552 Jun 10  1995 ./sbin/init
--r-xr-xr-x  1 bin     bin  176128 Jun 10  1995 ./sbin/ifconfig
--r-xr-xr-x  1 bin     bin  110592 Jun 10  1995 ./sbin/mount_nfs
--r-xr-xr-x  1 bin     bin  135168 Jun 10  1995 ./sbin/reboot
--r-xr-xr-x  1 root    bin   73728 Dec 13 22:38 ./sbin/mount
--r-xr-xr-x  1 root  wheel    1992 Jun 10  1995 ./dev/MAKEDEV.local
--r-xr-xr-x  1 root  wheel   24419 Jun 10  1995 ./dev/MAKEDEV</screen>
-
-    <para>N'oubliez pas d'exécuter <command>MAKEDEV all</command> dans le répertoire <filename>dev</filename>.</para>
-
-    <para>Voici enfin mon <filename>/etc/rc</filename> pour <hostid>altair</hostid>&nbsp;:</para>
-
-<programlisting>#!/bin/sh
-#
-PATH=/bin:/
-export PATH
-#
-# configurer l'interface &ldquo;en boucle&rdquo;
-/sbin/ifconfig lo0 127.0.0.1
-#
-# configurer la carte Ethernet
-/sbin/ifconfig ed0 199.246.76.2 netmask 0xffffff00
-#
-# monter le système de fichiers racine via NFS
-/sbin/mount antares:/DiskLess/rootfs/altair /
-#
-# monter le système de fichiers /usr via NFS
-/sbin/mount antares:/DiskLess/usr /usr
-#
-/usr/X11R6/bin/XF86_SVGA -query antares -xf86config /etc/XF86Config.altair > /dev/null 2>&amp;1
-#
-# Rédemarrer lorsque l'on quitte X
-/sbin/reboot
-#
-# Nous avons planté ...
-exit 1</programlisting>
-
-    <para>Vos commentaires et questions sont bienvenus.</para>
-  </sect1>
-</article>
diff --git a/fr_FR.ISO8859-1/articles/euro/Makefile b/fr_FR.ISO8859-1/articles/euro/Makefile
deleted file mode 100644
index 8b003c374a..0000000000
--- a/fr_FR.ISO8859-1/articles/euro/Makefile
+++ /dev/null
@@ -1,22 +0,0 @@
-#
-#    The FreeBSD Documentation Project
-#    The FreeBSD French Documentation Project
-#
-#    $FreeBSD$
-#    Original revision: 1.1
-#
-
-
-
-DOC?= article
-
-FORMATS?= html
-
-INSTALL_COMPRESSED?=gz
-INSTALL_ONLY_COMPRESSED?=
-
-SRCS= article.sgml
-
-DOC_PREFIX?= ${.CURDIR}/../../..
-
-.include "${DOC_PREFIX}/share/mk/doc.project.mk"
diff --git a/fr_FR.ISO8859-1/articles/euro/article.sgml b/fr_FR.ISO8859-1/articles/euro/article.sgml
deleted file mode 100644
index b5a82dd3cc..0000000000
--- a/fr_FR.ISO8859-1/articles/euro/article.sgml
+++ /dev/null
@@ -1,385 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1" standalone="no"?>
-<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V4.2-Based Extension//EN"
-	"../../../share/sgml/freebsd42.dtd" [
-<!ENTITY % entities PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Entity Set//FR" "../../share/sgml/entities.ent">
-%entities;
-<!ENTITY % not.published "IGNORE">
-]>
-
-<!--
-     The FreeBSD Documentation Project
-     The FreeBSD French Documentation Project
-
-     $FreeBSD$
-     $Id: article.sgml,v 1.5 2003-12-29 12:57:18 gioria Exp $
-     Original revision: 1.8
--->
-
-<article lang="fr">
-  <articleinfo>
-    <title>L'Euro et <systemitem class="osname">FreeBSD</systemitem></title>
-
-    <authorgroup>
-      <author>
-	<firstname>Aaron</firstname>
-
-	<surname>Kaplan</surname>
-
-	<affiliation>
-	  <address>
-	    <email>aaron@lo-res.org</email>
-	  </address>
-	</affiliation>
-      </author>
-    </authorgroup>
-
-    <copyright>
-      <year>2002</year>
-      <year>2003</year>
-      <holder>Groupe de Documentation de FreeBSD</holder>
-    </copyright>
-
-    <pubdate>$FreeBSD$</pubdate>
-
-    <releaseinfo>$FreeBSD$</releaseinfo>
-
-	<legalnotice id="trademarks" role="trademarks">
-	&tm-attrib.freebsd;
-	&tm-attrib.general;
-	</legalnotice>
-
-    <abstract>
-      <para>Ce document essaiera de vous aider &agrave; démarrer avec le
-	symbole <keycap>Euro</keycap> présent sur le nouveau clavier
-	que vous avez dû acheter au début 2002 en raison du passage &agrave; la
-	monnaie unique. Nous nous focaliserons en premier lieu sur les
-	parties les plus importantes comme être capable d'afficher
-	correctement le symbole sur la console.
-	Les sections suivantes traiterons de la configuration de
-	programmes particuliers comme <application>X11</application>.
-      </para>
-
-      <para>De nombreuses remarques utiles sont venues d'Oliver Fromme,
-	 Tom Rhodes et d'innombrables autres personnes. Merci! Sans vous
-	 cet article n'aurait pas été possible!
-      </para>
-	&trans.a.fonvieille;
-    </abstract>
-  </articleinfo>
-
-  <sect1>
-    <title>L'Euro en bref</title>
-
-    <para>Si vous vous sentez déj&agrave; &agrave; l'aise avec la
-      <ulink url="../../books/handbook/l10n.html">localisation</ulink>
-	 comme elle est décrite dans le manuel
-	 <systemitem class="osname">FreeBSD</systemitem>
-	vous pourriez être uniquement intéressé que par les faits
-	 suivants qui vous permettront de démarrer rapidement:
-    </para>
-
-    <variablelist>
-      <varlistentry>
-	<term>ISO8859-15</term>
-
-	<listitem>
-	  <para>C'est une légère modification du jeu de caractères
-	ISO8859-1 habituellement utilisé. Il inclut le symbole Euro.
-	Il est utilisé par les variables d'environnement
-	<envar>LANG</envar>, et <envar>LC_CTYPE</envar>.
-	  </para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-	<term><filename>iso15-8x16.fnt</filename></term>
-
-	<listitem>
-	  <para>La police de caractères de &man.vidcontrol.1; pour la
-	 console</para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-	<term><filename>/usr/share/syscons/keymaps/*.iso.kbd</filename></term>
-
-	<listitem>
-	  <para>Les tables de clavier appropriées en fonction de votre
-		langue. Configurez votre table de clavier dans
-		<filename>rc.conf</filename> avec une de ces dernières.
-	  </para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-	<term><envar>LC_CTYPE</envar></term>
-
-	<listitem>
-	  <para>Utilisé pour spécifier le type correct de caractères
-		locaux.</para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-	<term><literal>XkbLayout "<replaceable>lang</replaceable>(euro)"</literal></term>
-
-	<listitem>
-	  <para>Option de configuration d'<application>XFree86</application>.</para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-	<term><filename>/usr/X11R6/lib/X11/fonts/*/fonts.alias</filename></term>
-	<listitem>
-	  <para>Soyez sûr d'ajuster vos polices de caractères pour X11 &agrave;
-	    <literal>-*-..-*-iso8859-15</literal></para>
-	</listitem>
-      </varlistentry>
-    </variablelist>
-  </sect1>
-
-  <sect1>
-    <title>Remarque générale</title>
-
-    <para>Dans les sections suivantes nous ferons souvent référence &agrave;
-      <emphasis>ISO8859-15</emphasis>. C'est la notation standard
-	introduite avec <systemitem class="osname">FreeBSD</systemitem> 4.5.
-	Dans les anciennes versions, la notation standard était soit
-      <emphasis>ISO_8859-15</emphasis> soit <emphasis>DIS_8859-15</emphasis>.
-    </para>
-
-    <para>Si vous utilisez une ancienne version de
-      <systemitem class="osname">FreeBSD</systemitem>, soyez sûr de
-	jeter un oeil &agrave; <filename>/usr/share/locale/</filename> afin de
-	 déterminer quelle convention de notation est utilisée.</para>
-  </sect1>
-
-  <sect1>
-    <title>La console</title>
-
-    <sect2>
-      <title>Configurer la police de caractères de la console</title>
-
-      <para>En fonction de la taille et la résolution de votre console
-	vous aurez besoin d'une des lignes suivantes dans
-	<filename>rc.conf</filename>:</para>
-
-      <programlisting>font8x16="iso15-8x16.fnt" # from /usr/share/syscons/fonts/*
-font8x14="iso15-8x14.fnt"
-font8x8="iso15-8x8.fnt"</programlisting>
-
-      <para>Cela sélectionnera la police de caractère ISO8859-15 aussi
-	connue sous le nom de Latin-9. L'ISO8859-15 est une variation de
-	l'ISO8859-1. On peut voir la différence entre les deux en
-	regardant le symbole Euro: ça valeur décimale est 164. En
-	ISO8859-1 vous remarquerez un cercle avec quatre petits traits
-	aux coins. Il est souvent dénommé le &ldquo;symbole monétaire
-	international&rdquo;. En ISO8859-15, au lieu du cercle, vous avez le
-	symbole Euro. En dehors de cela les polices sont plus ou moins
-	identiques.</para>
-
-      <warning>
-	<para>Au moment de l'écriture de cet article, la seule police
-	utilisable semble être l'<literal>iso15-8x16.fnt</literal>. Les
-	autres semblent uniquement afficher de l'ISO8859-1 en dépit de
-	ce que suggère leur nom.</para>
-      </warning>
-
-      <note>
-        <para>En spécifiant cette police de caractères quelques
-	applications pour la console s'afficheront altérées. Cela est dû
-	au fait qu'elles supposent que vous êtes en train d'utiliser une
-	police différente telle que l'ANSI 850. Un exemple précis est
-	<application>sysinstall</application>. Cependant la
-	plupart du temps cela ne devrait pas affecter les
-	applications.</para>
-      </note>
-
-      <para>Comme étape suivante vous devrez soit redémarrer le système pour que
-	 les changements prennent effet soit (manuellement) effectuer les commandes
-	lancées au démarrage du système:</para>
-
-      <screen>&prompt.user; <userinput>vidcontrol -f <replaceable>iso15-8x16.fnt</replaceable></userinput></screen>
-
-      <para>Pour vérifier si la police a bien été sélectionnée, exécuter la courte
-	 procédure <command><anchor id="awk-test"/>awk</command> suivante :</para>
-
-      <programlisting>#!/usr/bin/awk -f
-BEGIN {
-        for(i=160;i&lt;180;i++)
-                printf"%3d %c\n",i,i
-}</programlisting>
-
-      <para>Le résultat devrait faire apparaître le signe Euro &agrave; la
-	position 164.</para>
-    </sect2>
-
-    <sect2>
-      <title>Configurer votre clavier pour l'Euro</title>
-
-      <para>La plupart des tables de clavier devraient déj&agrave; être
-	correctement configurées. I.e: Si vous avez un clavier allemand et que
-	vos touches Umlaut fonctionnent, vous pouvez sans risque passer
-	cette section dès lors que le clavier fait correspondre quelque soit la
-	combinaison de touches nécessaire (e.g.: <keycombo
-	action="simul"><keycap>Alt Gr</keycap><keycap>e</keycap></keycombo>) la
-	valeur décimale 164. Si des problèmes apparaissent, la meilleur
-	façon de vérifier est de jeter un oeil &agrave;
-	<filename>/usr/share/syscons/keymaps/*.kbd</filename>. Le format
-	des tables de correspondance des touches est décrit dans
-	&man.keyboard.4;. &man.kbdcontrol.1; peut être utilisé pour
-	charger une table de clavier sur spécifique.</para>
-
-      <para>Une fois que la table de clavier correcte est sélectionnée,
-	elle devrait être ajoutée dans	<filename>/etc/rc.conf</filename> avec la
-	ligne:</para>
-
-      <programlisting>keymap="<replaceable>german.iso</replaceable>" # ou une autre table</programlisting>
-
-      <para>Comme cela a été exposé au-dessus, cette étape a
-	probablement déj&agrave; été effectuée par vous-même lors de
-	l'installation (avec <application>sysinstall</application>).
-	Sinon redémarrer ou charger la nouvelle table de clavier via
-	&man.kbdcontrol.1;.</para>
-
-      <para>Pour vérifier le clavier, basculer sur une nouvelle console
-	et &agrave; l'invite de session, <emphasis>au lieu de s'attacher</emphasis>,
-	essayez	de taper sur la touche <keycap>Euro</keycap>. Si cela ne
-	fonctionne pas, remplissez un rapport de bogue via &man.send-pr.1; ou
-	vérifiez que vous avez choisi effectivement la bonne table de clavier.</para>
-
-      <note>
-        <para>A ce stade la touche Euro ne fonctionnera pas encore avec
-	  <application>bash</application> ou
-	  <application>tcsh</application>.</para>
-      </note>
-    </sect2>
-
-    <sect2>
-      <title>Corriger les variables d'environnement</title>
-
-      <para>Les interpréteurs de commandes (<application>bash</application>, <application>tcsh</application>) renvoient vers
-	la bibliothèque &man.readline.3; qui alors respecte la
-	variable d'environnement <envar>LC_CTYPE</envar>. <envar>LC_CTYPE</envar>
-	doit être configurée avant que l'interpréteur de commandes ne soit
-	complètement lancé. Heureusement il suffit d'ajouter la ligne:</para>
-
-	<programlisting>export LC_CTYPE=<replaceable>de_DE</replaceable>.ISO8859-15</programlisting>
-
-	<para>&agrave; votre <filename>.bash_profile</filename> (<application>bash</application>), ou:</para>
-
-	<programlisting>setenv LC_CTYPE <replaceable>de_DE</replaceable>.ISO8859-15</programlisting>
-
-      <para>&agrave; votre fichier <filename>.login</filename> (<application>tcsh</application>). Bien sûr,
-	<replaceable>de_DE</replaceable> devra être remplacé par votre langue.
-	Ensuite, fermez la session, ouvrez une nouvelle session et vérifiez
-	que la touche Euro fonctionne. A partir de maintenant la plupart
-	des applications pour la console devrait répondre &agrave; la touche
-	Euro. Cependant des configurations supplémentaires pour des programmes
-	spécifiques comme <application>pine</application> pourraient
-	être encore nécessaires.</para>
-
-      <note>
-	<para>Une alternative &agrave; la modification des fichiers
-	<filename>.login</filename> et <filename>.bash_profile</filename>
-	est de définir les variables d'environnement par l'intermédiaire
-	de &man.login.conf.5;. Cette approche a l'avantage d'assigner,
-	<emphasis>en un seul endroit</emphasis>, des classes de session pour
-	certains utilisateurs (e.g. utilisateurs français, italiens, etc...).</para>
-      </note>
-    </sect2>
-  </sect1>
-
-  <sect1>
-    <title>Modifier X11</title>
-
-    <para>Modifiez <filename>/etc/XF86Config</filename> de la manière
-	suivante:</para>
-
-    <programlisting>Option "XkbLayout"  "<replaceable>de</replaceable>(euro)"</programlisting>
-
-    <para>Encore une fois, remplacez <replaceable>de</replaceable> avec
-	votre langue. A partir de maintenant, le clavier devrait être
-	correctement configuré. Comme dans la partie consacrée &agrave; la
-	console la police de caractères correcte doit être choisie. Pour
-	<application>KDE</application>, aller dans le
-	<application>centre de contrôle de KDE</application> -&gt;
-	Personnalisation -&gt; Pays &amp; Langue -&gt; Jeu de caractères
-	et le changer pour <literal>ISO8859-15</literal>. Les mêmes
-	étapes s'appliquent &agrave; <application>kmail</application> et
-	autres applications.</para>
-
-    <para>Une autre bonne idée est de modifier votre fichier
-	<filename>fonts.alias</filename>. En particulier la police de
-	caractères <literal>fixed</literal> devra être changée pour le
-	bon jeu de caractère : le fichier
-	<filename>/usr/X11R6/lib/X11/fonts/misc/fonts.alias</filename>
-	de l'auteur ressemble &agrave; :</para>
-
-     <programlisting>! $Xorg: fonts.alias,v 1.3 2000/08/21 16:42:31 coskrey Exp $
-fixed   -misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-iso8859-15
-variable -*-helvetica-bold-r-normal-*-*-120-*-*-*-*-iso8859-15
-(...)</programlisting>
-
-    <para>Comme dans les parties au sujet de la console, des
-	applications spécifiques ont encore les polices de caractères
-	ISO8859-1 configurées dans leur base de données &man.xrdb.1;
-	respectives. Un exemple notable est <application>xterm</application>.
-	En général il suffit juste de modifier le fichier de
-	configuration correspondant dans
-	<filename>/usr/X11R6/lib/X11/app-defaults</filename> et ajouter
-	la police de caractères correcte. Faisons la démonstration avec
-	<application>xterm</application>.</para>
-
-   <screen>&prompt.root; cd /usr/X11R6/lib/X11/app-defaults/
-&prompt.root; vi XTerm</screen>
-
-    <para>Ajoutez la ligne suivante au début du fichier :</para>
-
-    <programlisting>*font:     -misc-fixed-medium-r-normal-*-*-120-*-*-c-*-iso8859-15</programlisting>
-
-    <para>Finalement, redémarrer X et vérifier que les polices de
-	caractères peuvent être affichées en exécutant la
-	<link linkend="awk-test">procédure awk</link> précédente. Les
-	principales applications devraient respecter la table de clavier
-	et la configuration des polices de caractères.</para>
-  </sect1>
-
-  <sect1>
-    <title>Problèmes en suspens</title>
-
-    <para>Bien évidemment l'auteur souhaiterait avoir un retour. Et aussi, tout au moins,
-	contactez-moi si vous avez des éléments pour l'un de ces problèmes en
-	suspens:</para>
-
-    <itemizedlist>
-      <listitem>
-        <para>Décrire une autre façon de configurer <application>XFree86</application>:
-	  <filename role="package">x11/xkeycaps</filename></para>
-      </listitem>
-
-      <listitem>
-        <para>Configuration sous <application>GNOME</application></para>
-      </listitem>
-
-      <listitem>
-        <para>Configuration sous <application>XFCE</application></para>
-      </listitem>
-
-      <listitem>
-        <para>Configuration d'<application>(X)Emacs</application></para>
-      </listitem>
-
-      <listitem>
-        <para>Décrire UTF-8</para>
-      </listitem>
-
-      <listitem>
-        <para>Décrire <application>libiconv</application> comme une
-	méthode efficace de conversion entre ISO8859-15 et UTF-{8,16}
-	directement &agrave; partir des applications.</para>
-
-      </listitem>
-    </itemizedlist>
-  </sect1>
-</article>
diff --git a/fr_FR.ISO8859-1/articles/formatting-media/Makefile b/fr_FR.ISO8859-1/articles/formatting-media/Makefile
deleted file mode 100644
index 72c1d9b8c9..0000000000
--- a/fr_FR.ISO8859-1/articles/formatting-media/Makefile
+++ /dev/null
@@ -1,20 +0,0 @@
-#
-#    The FreeBSD Documentation Project
-#    The FreeBSD French Documentation Project
-#
-#    $FreeBSD$
-#    Original revision: 1.4
-#
-
-DOC?= article
-
-FORMATS?= html
-
-INSTALL_COMPRESSED?=gz
-INSTALL_ONLY_COMPRESSED?=
-
-SRCS= article.sgml
-
-DOC_PREFIX?= ${.CURDIR}/../../..
-
-.include "${DOC_PREFIX}/share/mk/doc.project.mk"
diff --git a/fr_FR.ISO8859-1/articles/formatting-media/article.sgml b/fr_FR.ISO8859-1/articles/formatting-media/article.sgml
deleted file mode 100755
index 193d4a73fe..0000000000
--- a/fr_FR.ISO8859-1/articles/formatting-media/article.sgml
+++ /dev/null
@@ -1,555 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1" standalone="no"?>
-<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V4.2-Based Extension//EN"
-	"../../../share/sgml/freebsd42.dtd" [
-<!ENTITY % entities PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Entity Set//FR" "../../share/sgml/entities.ent">
-%entities;
-<!ENTITY % not.published "IGNORE">
-]>
-
-<!--
-     The FreeBSD Documentation Project
-     The FreeBSD French Documentation Project
-
-     $FreeBSD$
-     Original revision: n.nn
--->
-
-<article lang="fr">
-  <articleinfo>
-    <title>Formatage des supports pour FreeBSD 2.2-RELEASE</title>
-    <subtitle>Un guide</subtitle>
-    <authorgroup>
-      <author>
-        <firstname>Doug</firstname>
-        <surname>White</surname>
-      </author>
-    </authorgroup>
-    <abstract>
-      <para><email>dwhite@resnet.uoregon.edu</email></para>
-      <para>Mars 1997</para>
-      <para>Ce document décrit comment découper, partitionner et formater les
-        disques durs et autres supports similaires pour les utiliser avec
-        FreeBSD. Les exemples proposés ont été testés avec FreeBSD 2.2-GAMMA et
-        devraient être applicables &agrave; d'autres versions.</para>
-
-      &trans.a.haby;
-    </abstract>
-
-    <pubdate>$FreeBSD$</pubdate>
-
-    <releaseinfo>$FreeBSD$</releaseinfo>
-  </articleinfo>
-  <sect1>
-    <title>Introduction et définitions</title>
-      <sect2>
-        <title>Résumé</title>
-        <para>Réussir &agrave; ajouter des disques &agrave; un système existant est la
-          marque d'un administrateur système expérimenté. Découper, partitionner
-          et ajouter des disques requiert de combiner avec soin commande
-          adéquate et syntaxe de nommage. Une frappe malheureuse et un disque
-          entier peut disparaître en quelques secondes. Ce document est une
-          tentative pour simplifier le processus et éviter les accidents.
-          Heureusement, les outils existants (tout particulièrement
-          <citerefentry><refentrytitle>sysinstall</refentrytitle></citerefentry>)
-          ont notablement amélioré ce processus dans les dernières versions de
-          FreeBSD.</para>
-      <para>Il y a deux possibilités de formatage d'un disque:</para>
-      <itemizedlist>
-        <listitem>
-          <para><emphasis>mode compatible</emphasis>: Configurer un disque
-            pour qu'il ait une table des
-            tranches&nbsp;-&nbsp;&ldquo;<foreignphrase>slices</foreignphrase>&rdquo;&nbsp;-&nbsp;utilisable
-            avec d'autres systèmes d'exploitation.</para>
-        </listitem>
-        <listitem>
-          <para><emphasis>mode dangereusement dédié</emphasis>: Formater un
-            disque sans table des
-            tranches&nbsp;-&nbsp;&ldquo;<foreignphrase>slices</foreignphrase>&rdquo;.
-            Cela facilite l'ajout de disques, mais des systèmes d'exploitation
-            autres que FreeBSD risquent de ne pas reconnaître de tels
-            disques.</para>
-        </listitem>
-      </itemizedlist>
-      <para>Dans la plupart des cas, le mode dédié est le plus facile &agrave; mettre
-        en oeuvre et &agrave; utiliser sur des systèmes existants, auquel cas le
-        nouveau disque est en général entièrement dédié &agrave; FreeBSD. Cependant,
-        le mode compatible garantit le maximum d'interopérabilité avec des
-        installations ultérieures, au prix d'une plus grande complexité.</para>
-      <para>En plus du choix du mode, il existe deux méthodes pour découper le
-        disque. La première est d'utiliser l'outil
-        <citerefentry><refentrytitle>/stand/sysinstall</refentrytitle></citerefentry>
-        d'installation du système. A partir de la version 2.1.7-RELEASE de
-        FreeBSD,
-        <citerefentry><refentrytitle>sysinstall</refentrytitle></citerefentry>
-        contient du code qui facilite la
-        configuration de disques en cours d'opération normale du système,
-        donnant essentiellement accès aux éditeurs de labels et de partitions,
-        et comportant un fonctionnalité d'écriture qui ne met &agrave; jour que le
-        disque sélectionné sans toucher aux autres disques. La seconde méthode
-        consiste &agrave; employer les utilitaires, &agrave; la main, depuis la ligne de
-        commande, en session sous le compte super-utilisateur
-        <username>root</username>. Pour le mode dangereusement dédié, il n'y
-        a que trois ou quatre commandes concernées, alors que
-        <citerefentry><refentrytitle>sysinstall</refentrytitle></citerefentry>
-        demande quelques manipulations.</para>
-    </sect2>
-    <sect2>
-      <title>Définitions</title>
-      <para>La gestion de disques Unix a, au fil des siècles, inventé de
-        nombreuses nouvelles définitions pour d'anciens mots. Le glossaire
-        ci-dessous donne les définitions des expressions utilisées dans
-        ce document et (espérons-le) pour ce qui concerne FreeBSD en
-        général.</para>
-      <itemizedlist>
-        <listitem>
-          <para><emphasis>mode compatible</emphasis>: Configurer un disque
-            pour qu'il ait une table des
-            tranches&nbsp;-&nbsp;&ldquo;<foreignphrase>slices</foreignphrase>&rdquo;&nbsp;-&nbsp;utilisable
-            avec d'autres systèmes d'exploitation. C'est le contraire du mode
-            dangereusement dédié.</para>
-        </listitem>
-        <listitem>
-          <para><emphasis>mode dangereusement dédié</emphasis>: Formater un
-            disque sans table des
-            tranches&nbsp;-&nbsp;&ldquo;<foreignphrase>slices</foreignphrase>&rdquo;.
-            Cela facilite l'ajout de disques, mais des systèmes d'exploitation
-            autres que FreeBSD risquent de ne pas reconnaître de tels
-            disques. C'est le contraire du mode compatible.</para>
-        </listitem>
-        <listitem>
-          <para>disque: un disque circulaire recouvert d'un matériau magnétique
-            ou équivalent, qui tourne, mû par un moteur, devant une tête de
-            lecture. Les données sont enregistrées sur le disque en modifiant
-            la magnétisation du support, et peuvent être ensuite relues. Les
-            disques durs, CD-ROMs, disques magnéto-optiques et supports
-            amovibles Zip ou Jaz, sont des exemples de disques.</para>
-        </listitem>
-        <listitem>
-          <para>tranche&nbsp;-&nbsp;&ldquo;<foreignphrase>slice</foreignphrase>&rdquo;:
-            une subdivision du disque. Il peut y avoir jusqu'&agrave; quatre tranches
-            sur un disque d'après le standard PC. Les tranches sont constituées
-            de secteurs adjacents. Les tranches sont décrites par une
-            &ldquo;table des tranches&rdquo; utilisée par le BIOS du système
-            pour localiser les partitions démarrables. La table des tranches
-            est habituellement appelée &ldquo;table des partitions&rdquo; en
-            langage DOS. Les tranches sont gérées par l'utilitaire
-            <citerefentry><refentrytitle>fdisk</refentrytitle></citerefentry>.</para>
-        </listitem>
-        <listitem>
-          <para>partition: une subdivision de la
-            tranche&nbsp;-&nbsp;&ldquo;<foreignphrase>slice</foreignphrase>&rdquo;.
-            Habituellement utilisée pour désigner les divisions de la tranche
-            FreeBSD du disque. Chaque système de fichiers et espace de
-            pagination réside sur une partition. Les partitions sont gérées par
-            l'utilitaire
-            <citerefentry><refentrytitle>disklabel</refentrytitle></citerefentry>.</para>
-        </listitem>
-        <listitem>
-          <para>secteur: la plus petite subdivision d'un disque. Un secteur
-            contient habituellement 512 octets de données.</para>
-        </listitem>
-      </itemizedlist>
-    </sect2>
-    <sect2>
-      <title>Avertissements et pièges &agrave; éviter</title>
-      <para>Installer des disques n'est pas quelque chose &agrave; prendre &agrave; la
-        légère. Il est tout &agrave; fait possible de détruire le contenu d'autres
-        disques de votre système si vous ne prenez pas les précautions
-        nécessaires.</para>
-      <para><emphasis>Vérifiez avec soin ce que vous faites</emphasis>. Il est
-        très facile d'effacer le mauvais disque quand vous utilisez ces
-        commandes. En cas de doute, consultez les messages de démarrage du
-        noyau pour connaître le nom exact du périphérique.</para>
-      <para>Inutile de préciser que nous ne serions en rien responsable des
-        dégâts que vous causeriez &agrave; vos données ou &agrave; votre matériel. Vous
-        travaillez &agrave; vos risques et périls.</para>
-    </sect2>
-    <sect2>
-      <title>Zip, Jaz et autres disques amovibles</title>
-      <para>Les disques amovibles peuvent être formatés de la même façon que les
-        disques durs ordinaires. Il est indispensable que le lecteur soit
-        connecté et qu'il y ait un disque dedans au démarrage du système, pour
-        que le noyau puisse déterminer la géométrie du disque. Consultez les
-        résultats de
-        <citerefentry><refentrytitle>dmesg</refentrytitle></citerefentry>
-        et vérifiez que le disque et sa taille y figurent. Si le noyau émet le
-        message:</para>
-      <programlisting>
-Can't get the size
-      </programlisting>
-      <para>c'est que le disque n'était pas dans le lecteur. Dans ce cas, vous
-        devrez redémarrer la machine avant de formater des disques.</para>
-    </sect2>
-  </sect1>
-  <sect1>
-    <title>Formater des disques en mode dédié</title>
-    <sect2>
-      <title>Introduction</title>
-      <para>Cette section explique en détail comment configurer des disques
-        entièrement dédiés &agrave; FreeBSD. N'oubliez pas que des disques en mode
-        dédié ne peuvent pas être utilisés par l'architecture PC pour démarrer
-        le système.</para>
-    </sect2>
-    <sect2>
-      <title>Formater des disques en mode dédié avec Sysinstall</title>
-      <para><filename>/stand/sysinstall</filename>, l'utilitaire
-        d'installation du système, a été amélioré dans les versions récentes
-        pour rendre le processus de découpage propre des disques moins
-        pénible. Les éditeurs
-        <citerefentry><refentrytitle>fdisk</refentrytitle></citerefentry> et
-        <citerefentry><refentrytitle>disklabel</refentrytitle></citerefentry>
-        inclus dans
-        <citerefentry><refentrytitle>sysinstall</refentrytitle></citerefentry>
-        sont des outils interactifs qui
-        dissipent une bonne partie de la confusion liée aux opérations de
-        découpage de disques en &ldquo;tranches&rdquo;. Avec FreeBSD 2.1.7 et
-        ultérieur, c'est probablement la méthode la plus simple pour le
-        faire.</para>
-      <orderedlist>
-        <listitem>
-          <para>Lancez
-            <citerefentry><refentrytitle>sysinstall</refentrytitle></citerefentry>
-            en tant que super-utilisateur <username>root</username> en
-            tapant:</para>
-          <informalexample>
-<screen>&prompt.root; <userinput>/stand/sysinstall</userinput></screen>
-          </informalexample>
-          <para>sur la ligne de commande.</para>
-        </listitem>
-        <listitem>
-          <para>Sélectionnez <option>Index</option>.</para>
-        </listitem>
-        <listitem>
-          <para>Sélectionnez <option>Partition</option>.</para>
-        </listitem>
-        <listitem>
-          <para>Sélectionnez le disque &agrave; configurer avec les touches Flèches et
-            la barre d'espacement.</para>
-        </listitem>
-        <listitem>
-          <para>Si vous utilisez tout le disque pour FreeBSD, sélectionnez
-            <option>A</option>.</para>
-        </listitem>
-        <listitem>
-          <para>A la question:</para>
-          <programlisting>
-Do you want to do this with a true partition entry so as to remain
-cooperative with any future possible operating systems on the
-drive(s)?
-
-[Voulez-vous créer une vraie entrée de partition pour rester
-compatible avec d'éventuels futurs systèmes d'exploitation
-sur le(s) disque(s)?]
-          </programlisting>
-          <para>répondez <option>No</option> (Non).</para>
-        </listitem>
-        <listitem>
-          <para>Quand on vous demande si vous voulez continuer, répondez
-            <option>Yes</option> (Oui).</para>
-        </listitem>
-        <listitem>
-          <para>Sélectionnez <option>Write</option> (Ecrire).</para>
-        </listitem>
-        <listitem>
-          <para>A l'avertissement &agrave; propos de l'écriture sur des systèmes
-            déj&agrave; installés, répondez <option>Yes</option> (Oui).</para>
-        </listitem>
-        <listitem>
-          <para><option>Quit</option>tez l'éditeur
-            <citerefentry><refentrytitle>fdisk</refentrytitle></citerefentry>
-            et revenez au menu d'<option>Index</option> avec
-            <keycap>Echap</keycap>.</para>
-        </listitem>
-        <listitem>
-          <para>Sélectionnez <option>Label</option> dans le menu
-            d'<option>Index</option>.</para>
-        </listitem>
-        <listitem>
-          <para>Libellez le disque comme vous le souhaitez. Si vous ne voulez
-            qu'une seule partition, tapez <keycap>C</keycap> pour créer une
-            partition, validez la taille proposée par défaut, prenez comme
-            type de partition <option>Filesystem</option> (système de fichiers)
-            et indiquez un point de montage (qui dans ce cas ne sert &agrave;
-            rien).</para>
-        </listitem>
-        <listitem>
-          <para>Tapez <keycap>W</keycap> une fois que vous avez terminé. Le
-            système de fichiers sera initialisé avec
-            <citerefentry><refentrytitle>newfs</refentrytitle></citerefentry>
-            sans que vous n'ayez autre chose &agrave; faire, &agrave; moins que vous ne
-            fassiez un autre choix (pour les nouvelles partitions, il faut
-            initialiser le système de fichiers!). Vous aurez un message
-            d'erreur:</para>
-          <programlisting>
-Error mounting /mnt/dev/wd2s1e on /mnt/blah : No such file or directory
-          </programlisting>
-          <para>Ne vous en occupez pas.</para>
-        </listitem>
-        <listitem>
-          <para>Quittez le programme, en utilisant &agrave; plusieurs reprises la
-            touche <keycap>Echap</keycap>.</para>
-        </listitem>
-      </orderedlist>
-    </sect2>
-    <sect2>
-      <title>Formater des disques en mode dédié depuis la ligne de
-        commande</title>
-      <para>Exécutez les commandes suivantes, en substituant &agrave;
-        <devicename>wd2</devicename> le nom de votre disque. Les lignes
-        qui commencent par <literal>#</literal> sont des commentaires.</para>
-      <informalexample>
-<screen><userinput>dd if=/dev/zero of=/dev/rwd2 count=2</userinput>
-<userinput>disklabel /dev/rwd2 | disklabel -B -R -r wd2 /dev/stdin</userinput>
-# Nous ne voulons qu'une partition, utiliser la tranche 'c' devrait aller:
-<userinput>newfs /dev/rwd2c</userinput></screen>
-      </informalexample>
-      <para>Si vous avez besoin de modifier le label du disque pour créer
-        plusieurs partitions (pour la pagination par exemple), utilisez la
-        séquence suivante:</para>
-      <informalexample>
-<screen><userinput>dd if=/dev/zero of=/dev/rwd2 count=2</userinput>
-<userinput>disklabel /dev/r$d > /tmp/label</userinput>
-# Modifiez le label du disque pour ajouter des partitions:
-<userinput>vi /tmp/label</userinput>
-<userinput>disklabel -B -R -r wd2 /tmp/label</userinput>
-# Créez les systèmes de fichiers sur les partitions avec newfs selon les besoins</screen>
-      </informalexample>
-      <para>Votre disque est maintenant prêt &agrave; être utilisé.</para>
-    </sect2>
-  </sect1>
-  <sect1>
-    <title>Formater des disques en mode compatible</title>
-    <sect2>
-      <title>Introduction</title>
-      <para>Travailler depuis la ligne de commande est la manière la plus facile
-        de formater des disques dédiés, et la pire pour formater des disques
-        compatibles. L'utilitaire en ligne de commande
-        <citerefentry><refentrytitle>fdisk</refentrytitle></citerefentry>
-        demande une bonne connaissance des mathématiques et une compréhension en
-        profondeur de la structure de la table des &ldquo;tranches&rdquo;, qui
-        dépassent ce dont la plupart des gens souhaitent se préoccuper. Utilisez
-        <citerefentry><refentrytitle>sysinstall</refentrytitle></citerefentry>
-        comme décrit dans ce qui suit.</para>
-    </sect2>
-    <sect2>
-      <title>Formater des disques en mode compatible avec Sysinstall</title>
-      <orderedlist>
-        <listitem>
-          <para>Lancez
-            <citerefentry><refentrytitle>sysinstall</refentrytitle></citerefentry>
-            en tant que super-utilisateur <username>root</username> en
-            tapant:</para>
-          <informalexample>
-<screen>&prompt.root; <userinput>/stand/sysinstall</userinput></screen>
-          </informalexample>
-          <para>sur la ligne de commande.</para>
-        </listitem>
-        <listitem>
-          <para>Sélectionnez <option>Index</option>.</para>
-        </listitem>
-        <listitem>
-          <para>Sélectionnez <option>Partition</option>.</para>
-        </listitem>
-        <listitem>
-          <para>Sélectionnez le disque &agrave; configurer avec les touches Flèches et
-            la barre d'espacement.</para>
-        </listitem>
-        <listitem>
-          <para>Si vous utilisez tout le disque pour FreeBSD, sélectionnez
-            <option>A</option>.</para>
-        </listitem>
-        <listitem>
-          <para>A la question:</para>
-          <programlisting>
-Do you want to do this with a true partition entry so as to remain
-cooperative with any future possible operating systems on the
-drive(s)?
-
-[Voulez-vous créer une vraie entrée de partition pour rester
-compatible avec d'éventuels futurs systèmes d'exploitation
-sur le(s) disque(s)?]
-          </programlisting>
-          <para>répondez <option>Yes</option> (Oui).</para>
-        </listitem>
-        <listitem>
-          <para>Sélectionnez <option>Write</option> (Ecrire).</para>
-        </listitem>
-        <listitem>
-          <para><option>Quit</option>tez l'éditeur
-          <citerefentry><refentrytitle>fdisk</refentrytitle></citerefentry>.</para>
-        </listitem>
-        <listitem>
-          <para>A la question &agrave; propos du gestionnaire de démarrage, répondez
-            encore <option>None</option> (aucun).</para>
-        </listitem>
-        <listitem>
-          <para>Sélectionnez <option>Label</option> dans le menu
-            d'<option>Index</option>.</para>
-        </listitem>
-        <listitem>
-          <para>Libellez le disque comme vous le souhaitez. Si vous ne voulez
-            qu'une seule partition, validez la taille proposée par
-            défaut, prenez comme type de partition <option>Filesystem</option>
-            (système de fichiers) et indiquez un point de montage (qui dans ce
-            cas ne sert &agrave; rien).</para>
-        </listitem>
-        <listitem>
-          <para>Le système de fichiers sera initialisé avec
-            <citerefentry><refentrytitle>newfs</refentrytitle></citerefentry>
-            sans que vous n'ayez autre chose &agrave; faire, &agrave; moins que vous ne
-            fassiez un autre choix (pour les nouvelles partitions, il faut
-            initialiser le système de fichiers!). Vous aurez un message
-            d'erreur:</para>
-          <programlisting>
-Error mounting /mnt/dev/wd2s1e on /mnt/blah : No such file or directory
-          </programlisting>
-          <para>Ne vous en occupez pas.</para>
-        </listitem>
-        <listitem>
-          <para>Quittez le programme, en utilisant &agrave; plusieurs reprises la
-            touche <keycap>Echap</keycap>.</para>
-        </listitem>
-      </orderedlist>
-      <para>Votre nouveau disque est prêt &agrave; être utilisé.</para>
-    </sect2>
-  </sect1>
-  <sect1>
-    <title>Autres opérations sur les disques</title>
-    <sect2>
-      <title>Ajout d'espace de pagination</title>
-      <para>Au fur et &agrave; mesure que le système grossit, ses besoins d'espace de
-        pagination peuvent aussi augmenter. Alors qu'il est très difficile
-        d'ajouter de l'espace de pagination &agrave; des disques en service, un nouveau
-        disque peut être partitionné pour mettre en oeuvre de l'espace de
-        pagination supplémentaire.</para>
-      <para>Pour ajouter de l'espace de pagination au moment de l'installation
-        d'un nouveau disque:</para>
-      <orderedlist>
-        <listitem>
-          <para>Au moment de partitionner le disque, éditez son label et
-            allouer la quantité d'espace de pagination voulue en ajoutant une
-            partition 'b' et en affectant le reste &agrave; une autre partition,
-            telle que 'a' ou 'e'. La taille est &agrave; donner en blocs de 512
-            octets.</para>
-        </listitem>
-        <listitem>
-          <para>Au moment de créer les systèmes de fichiers avec
-            <citerefentry><refentrytitle>newfs</refentrytitle></citerefentry>,
-            ne formatez pas la partition 'c'. Formatez &agrave; la place la partition
-            qui n'est pas réservée &agrave; la pagination.</para>
-        </listitem>
-        <listitem>
-          <para>Ajoutez la ligne qui suit &agrave;
-            <filename>/etc/fstab</filename>:</para>
-          <programlisting>
-/dev/wd0b                       none            swap    sw 0 0
-          </programlisting>
-          <para>En remplacant <filename>/dev/wd0b</filename> par le nom du
-            nouvel espace de pagination.</para>
-        </listitem>
-        <listitem>
-          <para>Pour que l'espace de pagination soit immédiatement utilisable,
-            utilisez la commande
-            <citerefentry><refentrytitle>newfs</refentrytitle></citerefentry>:</para>
-          <informalexample>
-<screen>&prompt.user; <userinput>swapon /dev/sd0b</userinput>
-swapon:  added /dev/sd0b as swap space</screen>
-          </informalexample>
-        </listitem>
-      </orderedlist>
-    </sect2>
-    <sect2>
-      <title>Copier le contenu d'un disque sur un autre</title>
-      <para>Proposé par: Renauld Waldura
-        <email>renaud@softway.com</email>.</para>
-      <para>Pour déplacer le contenu d'un disque sur un nouveau, faites:</para>
-      <informalexample>
-<screen>&prompt.root; <userinput>mount /dev/wd2 /mnt</userinput>
-&prompt.root; <userinput>pax -r -w -p e /usr/home /mnt</userinput>
-&prompt.root; <userinput>umount /mnt</userinput>
-&prompt.root; <userinput>rm -rf /usr/home/*</userinput>
-&prompt.root; <userinput>mount /dev/wd2 /usr/home</userinput></screen>
-      </informalexample>
-    </sect2>
-    <sect2>
-      <title>Créer des disques &agrave; écritures réparties avec
-        <devicename>ccd</devicename></title>
-      <para>Commandes transmises par: Stan Brown
-        <email>stanb@awod.com</email>.</para>
-      <para>Le pilote de disques
-        concaténés&nbsp;-&nbsp;&ldquo;<foreignphrase>Concatenated Disk
-        Driver</foreignphrase>&rdquo;, ou CCD&nbsp;-&nbsp;vous permet
-        d'utiliser plusieurs disques comme s'il s'agissait d'un seul. Les
-        écritures réparties peuvent augmenter les performances disque en
-        distribuant les lectures et les écritures sur plusieurs disques.
-        Voyez les pages de manuel de
-        <citerefentry><refentrytitle>ccd</refentrytitle>
-        <manvolnum>4</manvolnum></citerefentry> et
-        <citerefentry><refentrytitle>ccdconfig</refentrytitle>
-        <manvolnum>4</manvolnum></citerefentry> ou la
-        <ulink url="http://stampede.cs.berkeley.edu/ccd/">page de
-        CCD</ulink>, pour plus d'informations.</para>
-      <para>Pour créer un nouveau CCD, exécutez les commandes ci-dessous.
-        Elles décrivent comment concaténer trois disques; ajoutez ou
-        supprimez des périphériques selon vos besoins. Rappelez-vous
-        que les disques sur lesquels se fera la répartition doivent être
-        <emphasis>identiques</emphasis>.</para>
-      <para>Avant d'exécuter ces commandes, vérifiez que vous avez bien
-        ajouté la ligne:</para>
-      <programlisting>
-pseudo-device ccd 4
-      </programlisting>
-      <para>&agrave; la configuration de votre noyau.</para>
-      <informalexample>
-<screen>&prompt.root; <userinput>cd /dev ; sh MAKDEV ccd0</userinput></screen>
-      </informalexample>
-      <informalexample>
-<screen>&prompt.root; <userinput>disklabel -r -w sd0 auto</userinput>
-&prompt.root; <userinput>disklabel -r -w sd1 auto</userinput>
-&prompt.root; <userinput>disklabel -r -w sd2 auto</userinput></screen>
-      </informalexample>
-      <informalexample>
-<screen>&prompt.root; <userinput>disklabel -e sd0c</userinput> # changer le type en 4.2BSD
-&prompt.root; <userinput>disklabel -e sd1c</userinput> # changer le type en 4.2BSD
-&prompt.root; <userinput>disklabel -e sd2c</userinput> # changer le type en 4.2BSD</screen>
-      </informalexample>
-      <informalexample>
-<screen>&prompt.root; <userinput>ccdconfig ccd0 32 0 /dev/sd0c /dev/sd1c /dev/sd2c</userinput></screen>
-      </informalexample>
-      <informalexample>
-<screen>&prompt.root; <userinput>newfs /dev/rccd0c</userinput></screen>
-      </informalexample>
-      <para>Vous pouvez maintenant monter et utiliser votre CCD en le
-        référençant comme périphérique
-        <filename>/dev/ccd0c</filename>.</para>
-    </sect2>
-  </sect1>
-  <sect1>
-    <title>Remerciements</title>
-    <para>L'auteur aimerait remercier les personnes suivantes pour leur
-      contribution &agrave; ce projet:</para>
-    <itemizedlist>
-      <listitem>
-        <para>Darryl Okahata <email>darrylo@hpnmhjw.sr.hp.com</email>,
-          pour sa documentation simple sur la configuration de
-          disques en mode dédié, que j'ai utilisée &agrave; plusieurs reprises
-          sur la &a.questions;.</para>
-      </listitem>
-      <listitem>
-        <para>&a.jkh; pour avoir rendu
-          <citerefentry><refentrytitle>sysinstall</refentrytitle></citerefentry>
-          utile &agrave; ce type de tâches.</para>
-      </listitem>
-      <listitem>
-        <para>John Fieber <email>jfieber@indiana.edu</email> pour avoir
-          mis au point la documentation et les exemples d'utilisation de
-          la <foreignphrase>DTD Docbook</foreignphrase> utilisée
-          pour mettre en forme ce document.</para>
-      </listitem>
-      <listitem>
-        <para>&a.grog; pour avoir contrôlé mon travail et mentionné les
-          inexactitudes, ainsi que pour son concours sur divers points.</para>
-      </listitem>
-    </itemizedlist>
-  </sect1>
-</article>
diff --git a/fr_FR.ISO8859-1/articles/linux-users/article.sgml b/fr_FR.ISO8859-1/articles/linux-users/article.sgml
index 8847e786e5..8792e43f71 100644
--- a/fr_FR.ISO8859-1/articles/linux-users/article.sgml
+++ b/fr_FR.ISO8859-1/articles/linux-users/article.sgml
@@ -168,12 +168,6 @@ in your /etc/rc.conf. Extra options can be found in startup script.</screen>
 	  &agrave; <envar>PACKAGESITE</envar> pour
 	  télécharger les paquetages les plus
 	  récents construits pour les versions 6.X.</para>
-
-	<para>Vous pouvez en savoir plus sur les versions de &os; dans
-	  l'article <ulink
-	  url="&url.base;/doc/en_US.ISO8859-1/articles/version-guide/">
-	  Choisir la version de &os; qui vous convient le
-	  mieux</ulink>.</para>
       </note>
 
       <para>Pour plus d'information concernant les paquetages vous
diff --git a/fr_FR.ISO8859-1/articles/multi-os/Makefile b/fr_FR.ISO8859-1/articles/multi-os/Makefile
deleted file mode 100644
index 72c1d9b8c9..0000000000
--- a/fr_FR.ISO8859-1/articles/multi-os/Makefile
+++ /dev/null
@@ -1,20 +0,0 @@
-#
-#    The FreeBSD Documentation Project
-#    The FreeBSD French Documentation Project
-#
-#    $FreeBSD$
-#    Original revision: 1.4
-#
-
-DOC?= article
-
-FORMATS?= html
-
-INSTALL_COMPRESSED?=gz
-INSTALL_ONLY_COMPRESSED?=
-
-SRCS= article.sgml
-
-DOC_PREFIX?= ${.CURDIR}/../../..
-
-.include "${DOC_PREFIX}/share/mk/doc.project.mk"
diff --git a/fr_FR.ISO8859-1/articles/multi-os/article.sgml b/fr_FR.ISO8859-1/articles/multi-os/article.sgml
deleted file mode 100755
index e49bbee76c..0000000000
--- a/fr_FR.ISO8859-1/articles/multi-os/article.sgml
+++ /dev/null
@@ -1,698 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1" standalone="no"?>
-<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V4.2-Based Extension//EN"
-	"../../../share/sgml/freebsd42.dtd" [
-<!ENTITY % entities PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Entity Set//FR" "../../share/sgml/entities.ent">
-%entities;
-]>
-
-<!--
-     The FreeBSD Documentation Project
-     The FreeBSD French Documentation Project
-
-     $FreeBSD$
-     Original revision: n.nn
--->
-
-<article lang="fr">
-  <articleinfo>
-    <title>Installer et utiliser FreeBSD en même temps que d'autres systèmes d'exploitation</title>
-    <authorgroup>
-      <author>
-        <firstname>Jay</firstname>
-        <surname>Richmond</surname>
-      </author>
-    </authorgroup>
-
-    <pubdate>$FreeBSD$</pubdate>
-
-    <releaseinfo>$FreeBSD$</releaseinfo>
-
-    <abstract>
-      <para><email>jayrich@sysc.com</email></para>
-      <para>6 Aout 1996</para>
-      <para>Ce document explique comment faire cohabiter proprement FreeBSD et
-        d'autres systèmes d'exploitation courants tels que Linux, MS-DOS, OS/2
-        et Windows 95. Remerciements particuliers &agrave; Annelise Anderson
-        <email>andrsn@stanford.edu</email>, Randall Hopper
-        <email>rhh@ct.picker.com</email> et Jordan K. Hubbard
-        <email>jkh@time.cdrom.com</email>.</para>
-
-        &trans.a.haby;
-    </abstract>
-  </articleinfo>
-  <sect1>
-    <title>Résumé</title>
-    <para>La plupart des gens n'arrivent pas &agrave; faire cohabiter leurs divers
-      systèmes d'exploitation sans des disques de grande capacité,
-      des informations sur les gros disques EIDE sont donc incluses. Comme il
-      y a de nombreuses combinaisons possibles de systèmes d'exploitation et
-      de configurations de disques durs, la section
-      <link linkend="examples">Exemples</link> sera peut-être celle
-      qui vous sera la plus utile. Elle décrit plusieurs configurations
-      d'ordinateurs utilisant plusieurs systèmes d'exploitation.</para>
-    <para>Ce document suppose que vous avez déj&agrave; préparé de la place sur votre
-      disque dur pour un système d'exploitation supplémentaire. Chaque fois que
-      vous repartitionnez votre disque dur, vous prenez le risque de détruire
-      les données qui se trouvent sur les partitions existantes. Toutefois, si
-      votre disque est entièrement occupé par DOS, vous trouverez peut-être le
-      programme FIPS (qui se trouve sur le CD-ROM FreeBSD dans le répertoire
-      <filename>\TOOLS</filename> ou que vous pouvez télécharger par
-      <ulink url="ftp://ftp.freebsd.org/pub/FreeBSD/tools">ftp</ulink>) utile.
-      Il vous permet de repartitionner votre disque sans détruire les données
-      qui s'y trouvent. Il existe aussi une programme commercial appelé
-      Partition Magic, qui vous permet de dimensionner et de supprimer des
-      partitions sans dégât.</para>
-  </sect1>
-  <sect1 id="boot-managers">
-    <title>Revue des gestionnaires de démarrage</title>
-    <para>Ce ne sont que de brèves descriptions des différents gestionnaires
-      de démarrage que vous rencontrerez. Selon la configuration de votre
-      ordinateur, vous pourrez trouver utile d'en employer plus d'un sur le
-      même système.</para>
-    <variablelist>
-      <varlistentry>
-        <term>Boot Easy</term>
-        <listitem>
-          <para>C'est le gestionnaire de démarrage par défaut de FreeBSD. Il
-            peut démarrer &agrave; peu près n'importe quoi, y compris BSD, OS/2
-            (HPFS), Windows 95 (FAT et FAT32) et Linux. Les partitions sont
-            sélectionnées &agrave; l'aide des touches fonction.</para>
-        </listitem>
-      </varlistentry>
-      <varlistentry>
-        <term><foreignphrase>OS/2 Boot Manager</foreignphrase></term>
-        <listitem>
-          <para>Il démarrera depuis la FAT, HPFS, FFS (FreeBSD) et EXT2
-            (Linux). Il peut aussi démarrer depuis des partitions FAT32.
-            Les partitions sont sélectionnées avec les touches Flèches.
-            Le gestionnaire de démarrage
-            <foreignphrase>OS/2 Boot Manager</foreignphrase> est le
-            seul &agrave; utiliser sa propre partition distincte, &agrave; l'inverse des
-            autres qui utilisent l'enregistrement principal de démarrage
-            (<foreignphrase>Master Boot
-            Record</foreignphrase>&nbsp;-&nbsp;MBR). Il doit donc être
-            installé dans les 1024 premiers cylindres pour éviter des
-            problèmes de démarrage. Il peut charger Linux en utilisant LILO
-            lorsque ce dernier se trouve sur le secteur de démarrage et non sur
-            le MBR. Allez sur les
-            <ulink url="http://www.freenix.fr/linux/HOWTO">HOWTO Linux</ulink>
-            sur le World Wide Web pour plus d'informations sur le démarrage
-            de Linux avec le gestionnaire de démarrage d'OS/2.</para>
-        </listitem>
-      </varlistentry>
-      <varlistentry>
-        <term>OS-BS</term>
-        <listitem>
-          <para>C'est une alternative &agrave; Boot Easy. Il vous donne plus de
-            contrôle sur le processus de démarrage, avec la possibilité de
-            sélectionner la partition &agrave; démarrer par défaut et le délai de
-            démarrage. La version béta de ce programme vous permet de
-            sélectionner le système d'exploitation &agrave; démarrer avec les
-            touches Flèches. Il est inclus sur le CD-ROM FreeBSD dans le
-            répertoire <filename>\TOOLS</filename> et vous pouvez le
-            télécharger par
-            <ulink url="ftp://ftp.freebsd.org/pub/FreeBSD/tools">ftp</ulink>.</para>
-        </listitem>
-      </varlistentry>
-      <varlistentry>
-        <term>LILO, ou LInux LOader (&ldquo;chargeur Linux&rdquo;)</term>
-        <listitem>
-          <para>C'est un gestionnaire de démarrage limité. Il peut démarrer
-            FreeBSD, mais il faut acommoder son fichier de configuration.</para>
-        </listitem>
-      </varlistentry>
-    </variablelist>
-    <informaltable>
-      <tgroup cols="1">
-        <tbody>
-          <row>
-            <entry><emphasis>A propos de la FAT32:</emphasis> La FAT32
-              remplace le système de fichiers FAT depuis la version Microsoft
-              OEM SR2 Béta, qui sera utilisée sur les ordinateurs avec Windows
-              95 pré-installé vers la fin de 1996. Elle convertit le système
-              de fichiers FAT habituel et permet d'utiliser des tailles
-              d'agrégat&nbsp;-&nbsp;&ldquo;<foreignphrase>cluster</foreignphrase>&rdquo;&nbsp;-&nbsp;plus
-              petites sur de plus gros disques. La FAT32 modifie aussi le
-              secteur de démarrage et la table d'allocation habituels de la FAT,
-              ce qui la rend incompatible avec certains gestionnaires de
-              démarrage.</entry>
-          </row>
-        </tbody>
-      </tgroup>
-    </informaltable>
-  </sect1>
-  <sect1 id="typical">
-    <title>Une configuration typique</title>
-    <para>Supposons que nous ayons deux gros disques EIDE, et que nous
-      voulions y installer FreeBSD, Linux et Windows 95.</para>
-    <para>Voici comment je procéderais avec ces disques durs:</para>
-    <itemizedlist>
-      <listitem>
-        <para><filename>/dev/wd0</filename> (premier disque dur
-          physique),</para>
-      </listitem>
-      <listitem>
-        <para><filename>/dev/wd1</filename> (second disque dur).</para>
-      </listitem>
-    </itemizedlist>
-    <para>Ils ont tous deux 1416 cylindres.</para>
-    <orderedlist>
-      <listitem>
-        <para>Je démarre avec une disquette de démarrage MS-DOS ou
-          Windows qui contient l'utilitaire <filename>FDISK.EXE</filename>
-          et crée une petite partition primaire de 50 Mo (35-40 pour Windows
-          95 et un peu d'espace libre) sur le premier disque. Je crée aussi
-          une partition plus importante sur le second disque pour mes
-          applications et mes données Windows.</para>
-      </listitem>
-      <listitem>
-        <para>Je redémarre et installe Windows 95 (plus facile &agrave; dire qu'&agrave;
-          faire) sur la partition <filename>C:</filename>.</para>
-      </listitem>
-      <listitem>
-        <para>J'installe ensuite Linux. Je ne suis pas certain pour qui
-          concerne toutes les distributions de Linux, mais la Slackware
-          comprend LILO (voyez la section
-          <link linkend="boot-managers">Revue des gestionnaires de
-          démarrage</link>). Au moment de partitionner mon disque dur
-          avec l'utilitaire <filename>fdisk</filename> de Linux,
-          je mets tout Linux sur le premier disque (peut-être 300 Mo
-          pour une partition racine confortable et de l'espace de
-          pagination).</para>
-      </listitem>
-      <listitem>
-        <para>Après avoir installé Linux, et quand on me demande si je veux
-          installer LILO, je fais <emphasis>attention</emphasis> &agrave; l'installer
-          sur le secteur de démarrage de ma partition racine Linux, et non
-          sur le MBR (<foreignphrase>Master Boot
-          Record</foreignphrase>&nbsp;-&nbsp;enregistrement principal de
-          démarrage).</para>
-      </listitem>
-      <listitem>
-        <para>L'espace restant disponible sur le disque peut servir &agrave;
-          FreeBSD. Je vérifie aussi que la
-          tranche&nbsp;-&nbsp;&ldquo;<foreignphrase>slice</foreignphrase>&rdquo;&nbsp;-&nbsp;racine
-          de FreeBSD ne déborde pas de la limite des 1024 cylindres (1024
-          cylindres correspond &agrave; 528 Mo &agrave; partir du début du disque sur nos
-          hypothétiques disques de 720 Mo). J'utiliserai éventuellement le
-          reste du disque dur (environ 270 Mo) pour les tranches
-          <filename>/usr</filename> et <filename>/var</filename>. Le
-          reste du second
-          disque (l'espace disponible dépend de la taille de ma partition
-          d'applications/données Windows que j'ai créée &agrave; l'étape 1) peut être
-          utilisé pour la tranche <filename>/usr/src</filename> et l'espace
-          de pagination.</para>
-      </listitem>
-      <listitem>
-        <para>Vus de l'utilitaire <filename>fdisk</filename> de Windows 95, mes
-          disques ressembleraient &agrave; ceci:</para>
-        <programlisting>
----------------------------------------------------------------------
-
-                  Display Partition Information
-
-Current fixed disk drive: 1
-
-Partition  Status  Type  Volume_Label  Mbytes  System  Usage
-C: 1          A   PRI DOS                50    FAT**     7%
-   2          A   Non-DOS (Linux)       300             43%
-
-Total disk space is  696 Mbytes (1 Mbyte = 1048576 bytes)
-
-Press Esc to continue
-
----------------------------------------------------------------------
-
-                  Display Partition Information
-
-Current fixed disk drive: 2
-
-Partition  Status  Type  Volume_Label  Mbytes  System  Usage
-D: 1          A   PRI DOS                420   FAT**    60%
-
-Total disk space is  696 Mbytes (1 Mbyte = 1048576 bytes)
-
-Press Esc to continue
-
----------------------------------------------------------------------
-        </programlisting>
-        <para>Disons FAT16, ou FAT32 si vous utilisez la mise &agrave; jour
-          OEM SR2 (voyez la section
-          <link linkend="boot-managers">Revue des gestionnaires de
-          démarrage</link>).</para>
-      </listitem>
-      <listitem>
-        <para>J'installe FreeBSD. Je veille &agrave; démarrer avec le premier
-          disque dur défini comme &ldquo;NORMAL&rdquo; dans le paramétrage
-          du BIOS. Sans cela, je devrais indiquer la géométrie réelle de mon
-          disque au démarrage (pour la connaître, démarrez Windows 95 et
-          consultez les diagnostics Microsoft (<filename>MSD.EXE</filename>)
-          ou allez voir dans le BIOS) avec le paramètre
-          <literal>hd0=1416,16,63</literal> où <replaceable>1416</replaceable>
-          est le nombre de cylindres de mon disque dur,
-          <replaceable>16</replaceable> est le nombre de têtes par piste et
-          <replaceable>63</replaceable> est le nombre de secteurs par
-          tête.</para>
-      </listitem>
-      <listitem>
-        <para>Au moment de partitionner le disque dur, je fais attention &agrave;
-          bien installer Boot Easy sur le premier disque. Je ne m'occupe pas
-          du second disque, &agrave; partir duquel rien n'est démarré.</para>
-      </listitem>
-      <listitem>
-        <para>Au redémarrage, Boot Easy devrait reconnaître mes trois
-          partitions démarrables comme DOS (Windows 95), Linux et BSD
-          (FreeBSD)</para>
-      </listitem>
-    </orderedlist>
-  </sect1>
-  <sect1 id="special">
-    <title>Considérations particulières</title>
-    <para>La plupart des systèmes d'exploitation sont très chatouilleux sur la
-      façon et l'endroit où ils sont installés sur le disque dur. Windows 95 et
-      DOS doivent être sur la première partition primaire du premier disque dur.
-      OS/2 fait exception. Il peut être sur le premier ou le second disque et
-      sur une partition primaire ou étendue. Si vous n'êtes pas sûr de vous,
-      gardez le début des partitions démarrables avant le 1024ème
-      cylindre.</para>
-    <para>Si vous installez Windows 95 sur un système BSD existant, cela va
-      &ldquo;écraser&rdquo; le MBR, et vous devrez réinstaller votre précédent
-      gestionnaire de démarrage. Boot Easy peut être réinstallé avec
-      l'utilitaire <filename>BOOTINST.EXE</filename> qui se trouve dans le
-      répertoire <filename>\TOOLS</filename> du CD-ROM, ou peut être téléchargé
-      par <ulink url="ftp://ftp.freebsd.org/pub/FreeBSD/tools">ftp</ulink>.
-      Vous pouvez aussi relancer le processus d'installation et aller dans
-      l'éditeur de partitions. De l&agrave;, indiquez que la partition FreeBSD est
-      démarrable, choisissez l'option <option>Boot Manager</option>
-      (gestionnaire de démarrage) et tapez
-      <literal>W</literal> pour écrire les informations sur le MBR. Vous
-      pouvez maintenant redémarrer, et Boot Easy reconnaîtra votre Windows 95
-      en tant que DOS.</para>
-    <para>N'oubliez pas s'il vous plaît qu'OS/2 peut lire les partitions FAT
-      et HPFS, mais pas les partitions FFS (FreeBSD) ou EXT2 (Linux). De même,
-      Windows 95 ne peut que lire et écrire sur les partitions FAT et FAT32
-      (voyez la section <link linkend="boot-managers">Revue des gestionnaire
-      de démarrage</link>). FreeBSD peut lire la plupart des systèmes de
-      fichiers, mais ne sait pas actuellement lire les partitions HPFS. Linux
-      peut lire les partitions HPFS, mais ne peut pas y écrire. Les versions
-      récentes du noyau Linux (2.x) peuvent lire et écrire les partitions VFAT
-      de Windows 95 (La VFAT est ce qui permet &agrave; Windows d'utiliser des noms
-      de fichiers longs&nbsp;-&nbsp;c'est &agrave; peu près la même chose que la
-      FAT). Linux peut lire et écrire sur la plupart des systèmes de fichiers.
-      Pigé? Je l'espère.</para>
-  </sect1>
-  <sect1 id="examples">
-    <title>Exemples</title>
-    <para><emphasis>(Cette section a besoin d'être revue, envoyez s'il vous
-      plaît vos exemples &agrave; <email>jayrich@sysc.com</email>.)</emphasis></para>
-    <para>FreeBSD + Windows 95: Si vous avez installé FreeBSD après Windows 95,
-      vous devriez voir la mention <literal>DOS</literal> sur le menu de Boot
-      Easy. C'est Windows 95. Si vous avez installé Windows 95 après FreeBSD,
-      lisez la section <link linkend="special">Considérations
-      particulières</link> ci-dessus. Tant que votre disque n'a pas 1024
-      cylindres, vous ne devriez pas avoir de problèmes pour démarrer. Si
-      toutefois une de vos partitions va au-del&agrave; du 1024ème cylindre, et que
-      vous avez des messages du type <literal>invalid system disk</literal>
-      sous DOS (Windows 95) et que FreeBSD ne démarre pas, cherchez dans les
-      paramètres de configuration de votre BIOS quelque chose appelé
-      &ldquo;<literal>&gt; 1024 cylinder support</literal>&rdquo; ou
-      mode &ldquo;<literal>NORMAL/LBA</literal>&rdquo;. DOS peut avoir besoin
-      du LBA (<foreignphrase>Logical Block
-      Adressing</foreignphrase>&nbsp;-&nbsp;Adressage de bloc logique) pour
-      démarrer correctement. Si la perspective de modifier les paramètres du
-      BIOS &agrave; chaque démarrage ne vous enchante pas, vous pouvez démarrer
-      FreeBSD depuis DOS avec l'utilitaire <filename>FBSDBOOT.EXE</filename>
-      du CD (il devrait reconnaître votre partition FreeBSD et la
-      démarrer).</para>
-    <para>FreeBSD + OS/2 + Windows: Rien de nouveau dans ce cas. Le gestionnaire
-      de démarrage d'OS/2 peut démarrer tous ces systèmes d'exploitation, il ne
-      devrait pas y avoir de problème.</para>
-    <para>FreeBSD + Linux: Vous pouvez aussi utiliser Boot Easy pour démarrer
-      les deux systèmes d'exploitation.</para>
-    <para>FreeBSD + Linux + Windows 95: (voyez la section
-      <link linkend="typical">Une installation typique</link>).</para>
-  </sect1>
-  <sect1 id="help">
-    <title>Autres endroits où trouver de l'aide</title>
-    <para>Il y a de nombreux
-      <ulink url="http://www.freenix.fr/linux/HOWTO">HOWTO Linux</ulink>
-      qui traitent des systèmes d'exploitation multiples sur un même
-      disque.</para>
-    <para>Le
-      <ulink url="http://www.linuxresources.com/LDP/HOWTO/mini/Linux+DOS+Win95+OS2.html">mini-HOWTO
-        Linux+DOS+Win95+OS2</ulink> donne des indications sur la configuration
-        du gestionnaire de démarrage d'OS/2, et le
-      <ulink url="http://www.freenix.fr/linux/HOWTO/mini/Linux+FreeBSD.html">mini-HOWTO
-        Linux+FreeBSD</ulink> peut aussi vous intéresser.
-      L'<ulink url="http://www.in.net/~jkatz/win95/Linux-HOWTO.html">HOWTO
-        Linux</ulink> est aussi utile.</para>
-    <para>Le
-      <ulink url="http://www.dorsal.org/~dcl/publications/NTLDR_hacking">Guide
-        de programmation du chargeur NT</ulink> fournit des informations
-        intéressantes sur le démarrage de Windows NT, 95 et DOS avec d'autres
-        systèmes d'exploitation.</para>
-    <para>Le jeu de documents d'Hale Landis, &ldquo;Comment ça marche&rdquo;,
-      contient de bonnes informations sur toutes sortes de géométries de disques
-      et autres sujets liés au démarrage. Voici quelques liens qui peuvent vous
-      aider &agrave; le trouver:</para>
-    <itemizedlist>
-      <listitem>
-        <para><ulink url="ftp://fission.dt.wdc.com/pub/otherdocs/pc_systems/how_it_works/allhiw.zip">ftp://fission.dt.wdc.com/pub/otherdocs/pc_systems/how_it_works/allhiw.zip</ulink>,</para>
-      </listitem>
-      <listitem>
-        <para><ulink url="http://www.cs.yorku.ca/People/frank/docs/">http://www.cs.yorku.ca/People/frank/docs/</ulink>.</para>
-      </listitem>
-    </itemizedlist>
-    <para>Enfin, ne négligez pas la documentation du noyau de FreeBSD sur le
-      processus de démarrage, disponible dans la distribution du source du
-      noyau (elle est installée dans
-      <ulink url="file://localhost/usr/src/sys/i386/boot/biosboot/README.386BSD">/usr/src/sys/i386/boot/biosboot/README.386BSD</ulink>).</para>
-  </sect1>
-  <sect1>
-    <title>Détails Techniques</title>
-    <para><emphasis>(Contribution de Randall Hopper
-      <email>rhh@ct.picker.com</email>)</emphasis></para>
-    <para>Cette section tente de vous donner assez d'informations de base
-      sur vos disques durs et sur le processus de démarrage &agrave; partir d'un
-      disque pour vous permettre de régler la plupart des problèmes que vous
-      pourriez rencontrer lorsque vous configurerez le démarrage de plusieurs
-      systèmes d'exploitation. Elle commence par des choses relativement
-      élémentaires, vous préférerez donc peut-être la parcourir en diagonale
-      jusqu'&agrave; ce que les points abordés vous paraissent moins familiers et
-      commencer alors &agrave; la lire en détail.</para>
-    <sect2>
-      <title>Introduction aux disques</title>
-      <para>Trois termes fondamentaux décrivent la localisation des données
-        sur vos disques durs: Cylindres, Têtes et Secteurs. Il n'est pas très
-        important de savoir &agrave; quoi ils se rapportent sinon qu'ensemble, ils
-        définissent où sont physiquement les données sur le disque.</para>
-      <para>Votre disque a un nombre donné de cylindres, de têtes, et de
-        secteurs par tête-cylindre (un doublet tête-cylindre est aussi appelé
-        une piste). Ensemble, ces informations définissent la &ldquo;géométrie
-        physique&rdquo; de votre disque. Il y a typiquement 512 octets par
-        secteur et 63 secteurs par pistes, le nombre de cylindres et de têtes
-        variant très largement d'un disque &agrave; l'autre. Vous pouvez alors
-        calculer la quantité d'informations que peut enregistrer votre disque
-        par la formule:</para>
-      <programlisting>
-nombre de cylindres X nombre de têtes X 63 secteurs/piste X 512 octets/secteur
-      </programlisting>
-      <para>Par exemple, pour mon disque Western Digital AC31600 EIDE de 1,6 Go,
-cela donne:</para>
-      <programlisting>
-3148 cylindres X 16 têtes X 63 secteurs/piste X 512 octets/secteur
-      </programlisting>
-      <para>c'est-&agrave;-dire 1.624.670.208 octets, ou environ 1,6 Go.</para>
-      <para>Vous pouvez connaître la géométrie physique de votre disque dur
-        (nombre de cylindres, de têtes et de secteurs par piste) avec ATAID
-        ou d'autres programmes que vous trouverez sur l'Internet. Ces
-        informations sont peut-être aussi fournies avec votre disque. Faites
-        cependant attention: si vous utilisez le LBA du BIOS (voyez la section
-        <link linkend="limits">Restrictions pour le démarrage et
-        avertissements</link>), vous ne pouvez pas vous servir de n'importe
-        quel programme pour connaître la géométrie physique. Cela parce que de
-        nombreux programmes (e.g., <filename>MSD.EXE</filename> ou
-        le <filename>fdisk</filename> de FreeBSD) ne reconnaissent pas la
-        géométrie physique, ils listent &agrave; la place la <emphasis>géométrie
-        redéfinie</emphasis> (des valeurs virtuelles dues &agrave; l'utilisation
-        du LBA). Continuez &agrave; lire pour savoir ce que cela veut dire.</para>
-      <para>Une autre chose &agrave; savoir &agrave; propos de ces termes. 3
-        valeurs&nbsp;-&nbsp;un numéro de cylindre, un numéro de tête, et un
-        numéro du secteur sur la piste&nbsp;-&nbsp;identifient l'adresse absolue
-        d'un secteur sur votre disque. Les cylindres et les têtes sont
-        numérotés &agrave; partir de 0, et les numéros de secteurs commencent &agrave;
-        1.</para>
-      <para>Ceux que des détails plus techniques intéressent peuvent
-        trouver un peu partout sur l'Internet des informations sur la géométrie
-        des disques, les secteurs de démarrage, les BIOS, etc. Faites une
-        recherche sur Yahoo, Lycos, etc. pour <literal>boot sector</literal> ou
-        <literal>master boot record</literal>. Parmi les choses utiles que vous
-        trouverez, il y a le jeu de documents
-        &ldquo;Comment ça marche&rdquo;&nbsp;-&nbsp;<foreignphrase>How It
-        Works</foreignphrase> de Hale Landis. Voyez la section
-        <link linkend="help">Autres endroits où trouver de l'aide</link> pour
-        avoir quelques pointeurs vers ces documents.</para>
-      <para>OK, assez de terminologie. Nous sommes censés parler de démarrage
-        ici.</para>
-    </sect2>
-    <sect2 id="booting">
-      <title>Le processus de démarrage</title>
-      <para>Sur le premier secteur de votre disque (cylindre 0, tête 0,
-        secteur 1) se trouve l'enregistrement principal de
-        démarrage&nbsp;-&nbsp;<foreignphrase>Master Boot
-        Record</foreignphrase> (MBR). Il contient une carte de votre disque.
-        Il identifie jusqu'&agrave; <emphasis>4 partitions</emphasis>, chacune d'elle
-        étant un espace contigu sur ce disque. FreeBSD appelle les partitions
-        des tranches&nbsp;-&nbsp;<foreignphrase>slices</foreignphrase>&nbsp;-&nbsp;pour
-        éviter la confusion avec ses propres partitions, mais nous
-        n'utiliserons pas ici ce terme. Chaque partition peut contenir son
-        propre système d'exploitation.</para>
-      <para>Chaque entrée de partition dans le MBR comprend un
-        <emphasis>IDentifiant de partition</emphasis>, un
-        <emphasis>Cylindre/Tête/Secteur de Début</emphasis> et un
-        <emphasis>Cylindre/Tête/Secteur de Fin</emphasis>. L'IDentifiant de
-        partition dit de quel type de partition il s'agit (de quel OS) et le
-        Début/Fin dit où elle se trouve. La table des
-        <link linkend="partitions">IDs de partitions</link> liste un
-        échantillon d'identifiants de partitions usuels.</para>
-      <informaltable id="partitions">
-        <tgroup cols="2">
-          <thead>
-            <row>
-              <entry>ID (hex)</entry>
-              <entry>Description</entry>
-            </row>
-          </thead>
-          <tbody>
-            <row>
-              <entry>01</entry>
-              <entry>DOS12 primaire (FAT 12-bit)</entry>
-            </row>
-            <row>
-              <entry>04</entry>
-              <entry>DOS16 primaire (FAT 16-bit)</entry>
-            </row>
-            <row>
-              <entry>05</entry>
-              <entry>DOS12 étendue</entry>
-            </row>
-            <row>
-              <entry>06</entry>
-              <entry>DOS primaire large (&gt; 32 Mo)</entry>
-            </row>
-            <row>
-              <entry>0A</entry>
-              <entry>OS/2</entry>
-            </row>
-            <row>
-              <entry>83</entry>
-              <entry>Linux (EXT2FS)</entry>
-            </row>
-            <row>
-              <entry>A5</entry>
-              <entry>FreeBSD, NetBSD, 386BSD (UFS)</entry>
-            </row>
-          </tbody>
-        </tgroup>
-      </informaltable>
-      <note>
-        <para>Toutes les partitions ne dont pas démarrables (e.g. DOS étendue).
-          Certaines le sont&nbsp;-&nbsp;d'autres ne le sont pas. Ce qui rend
-          une partition démarrable est la configuration du secteur de démarrage
-          de la
-          partition&nbsp;-&nbsp;<foreignphrase>Partition Boot Sector</foreignphrase>&nbsp;-&nbsp;qui
-          est toujours présent au début de chaque partition.</para>
-      </note>
-      <para>Quand vous configurez votre gestionnaire de démarrage favori, il
-        consulte les entrées dans les tables de partitions du MBR de tous vos
-        disques et vous donne la possibilité de donner un nom &agrave; ces entrées.
-        Quand vous démarrez ensuite, le gestionnaire de démarrage
-        est appelé par du code prévu pour cela &agrave; partir secteur principal de
-        démarrage&nbsp;-&nbsp;<foreignphrase>Master Boot Sector</foreignphrase>&nbsp;-&nbsp;du
-        premier disque trouvé sur votre système. Le gestionnaire consulte
-        l'entrée de la table de partitions du MBR correspondant &agrave; la partition
-        que vous avez choisie, charge le secteur de démarrage de cette partition
-        et lui passe le contrôle. Ce secteur de démarrage de la partition
-        elle-même contient suffisamment d'informations pour commencer &agrave; charger
-        le système d'exploitation qui se trouve sur cette partition.</para>
-      <para>Il y a une chose importante &agrave; savoir dont nous n'avons pas encore
-        parlé. Tous vos disques durs ont un MBR. Toutefois, celui qui est
-        important est celui qui se trouve sur le premier disque reconnu par le
-        BIOS. Si vous n'avez que des disques durs IDE, c'est le premier disque
-        IDE (e.g. le disque maître sur le premier contrôleur). De même pour les
-        systèmes entièrement SCSI. Si vous avez et des disques durs IDE et des
-        disques durs SCSI, le disque IDE est habituellement le premier disque
-        dont la présence est testée par le BIOS, le premier disque IDE est donc
-        le premier disque reconnu. Le gestionnaire de démarrage que vous
-        installerez sera implémenté sur le premier disque dur reconnu comme
-        nous venons de l'expliquer.</para>
-    </sect2>
-    <sect2 id="limits">
-      <title>Restrictions pour le démarrage et avertissements</title>
-      <para>Voici maintenant les choses intéressantes auxquelles il faut
-        faire attention.</para>
-        <sect3>
-          <title>La redoutable limitation &agrave; 1024 cylindres et en quoi le LBA du
-            BIOS peut être utile</title>
-          <para>La première partie du processus de démarrage est entièrement
-            confiée au BIOS, (si ce terme est nouveau pour vous, le BIOS est
-            un circuit électronique sur votre carte mère qui contient le
-            code de démarrage de votre ordinateur). C'est pourquoi cette
-            première partie du processus est soumise aux limitations du
-            BIOS.</para>
-          <para>L'interface BIOS utilisée pour lire le disque dur durant
-            cette phase (INT 13H, Sous-fonction 2) alloue 10 bits pour le
-            numéro de cylindre, 8 bits pour le numéro de tête, et 6 bits
-            pour le numéro de secteur. Cela limite les utilisateurs de
-            cette interface (i.e. les gestionnaires de démarrage implémentés
-            sur le MBR du disque ainsi que les chargeurs de systèmes
-            d'exploitation implémentés sur les secteurs de démarrage) &agrave;:</para>
-          <itemizedlist>
-            <listitem>
-              <para>1024 cylindres au plus,</para>
-            </listitem>
-            <listitem>
-              <para>256 têtes au plus,</para>
-            </listitem>
-            <listitem>
-              <para>64 secteurs/piste au plus, (en fait 63, 0 n'est pas
-                disponible).</para>
-            </listitem>
-          </itemizedlist>
-          <para>Or les diques durs de grande capacité ont beaucoup de
-            cylindres et peu de têtes, le nombre de cylindres de ces disques
-            est donc invariablement supérieurs &agrave; 1024. De ce fait et &agrave; cause
-            de l'interface BIOS telle qu'elle est, vous ne pouvez pas démarrer
-            n'importe où sur votre disque dur. Le code de démarrage (le
-            gestionnaire de démarrage et le chargeur du système d'exploitation
-            implémenté sur les secteurs de démarrage de chaque partition
-            démarrable) doivent se situer avant le 1024ème cylindre. Si votre
-            disque dur est standard et a 16 têtes, cela équivaut &agrave;:</para>
-          <programlisting>
-1024 cylindres/disque X 16 têtes/disque X 63 secteurs/piste X 512 octets
-          </programlisting>
-          <para>c'est-&agrave;-dire la limite souvent citée de 528 Mo.</para>
-          <para>C'est l&agrave; qu'intervient le LBA (<foreignphrase>Logical Block
-             Adressing</foreignphrase>&nbsp;-&nbsp;&ldquo;adressage de bloc
-             logique&rdquo;) du BIOS. Le LBA du BIOS donne &agrave; l'utilisateur
-             des routines de l'API (<foreignphrase>Application Programming
-             Interface</foreignphrase>&nbsp;-&nbsp;&ldquo;interface de
-             programmation&rdquo;) du BIOS, la possibilité d'accéder aux
-             cylindres au-del&agrave; de 1024 avec les interfaces du BIOS en
-             redéfinissant le cylindre. Cela signifie qu'il construit une
-             nouvelle géométrie de vos cylindres et têtes, faisant croire
-             au BIOS que votre disque a moins de cylindres et plus de têtes
-             qu'en réalité. En d'autres termes, il profite du fait que les
-             disques ont relativement peu de têtes et beaucoup de cylindres,
-             pour modifier le rapport entre nombre de cylindres et nombre de
-             têtes de façon &agrave; ce que tous deux soient inférieurs aux limites
-             mentionnées ci-dessus (1024 cylindres, 256 têtes).</para>
-           <para>Pour prendre de nouveau l'exemple de mon Western Digital 1,6
-             Go, il a pour géométrie physique:</para>
-           <programlisting>
-(3148 cylindres, 16 têtes, 63 secteurs/piste, 512 octets/secteur)
-           </programlisting>
-           <para>Alors que le LBA du BIOS la redéfinit comme suit:</para>
-           <programlisting>
-( 787 cylindres, 64 têtes, 63 secteurs/piste, 512 octets/secteur)
-           </programlisting>
-           <para>ce qui correspond &agrave; la même capacité physique, mais avec des
-             nombres de cylindres et de têtes dans les limites acceptables par
-             les API du BIOS. (Au passage, j'ai sur l'un de mes disques, et
-             Linux et FreeBSD au-del&agrave; du 1024ème cylindre, et les deux démarrent
-             sans problème, grâce au LBA du BIOS.)</para>
-        </sect3>
-        <sect3>
-        <title>Gestionnaires de démarrage et allocation de l'espace
-          disque</title>
-        <para>Une autre chose &agrave; laquelle il faut faire attention lorsque vous
-          installez un gestionnaire de démarrage est l'allocation d'espace
-          disque pour ce gestionnaire. Il vaut mieux être informé de cette
-          question avant de commencer pour vous éviter d'avoir &agrave; réinstaller un
-          ou plusieurs de vos systèmes d'exploitation.</para>
-        <para>Si vous avez suivi ce qui a été dit sur le
-          <link linkend="booting">processus de démarrage</link>
-          &agrave; propos du secteur principal de démarrage (où se trouve le MBR),
-          des secteurs de démarrage des partitions et du processus de démarrage,
-          vous vous êtes peut-être demandé où va se trouver ce foutu
-          gestionnaire de démarrage. Bien, certains gestionnaires de démarrage
-          sont suffisamment légers pour tenir entièrement dans le secteur
-          principal de démarrage (cylindre 0, tête 0, secteur 1) avec la table
-          de partitions. D'autres ont besoin d'un peu plus d'espace et débordent
-          en fait de quelques secteurs après le secteur principal de démarrage
-          sur la piste cylindre 0 tête 0, qui sont normalement libres...
-          normalement.</para>
-        <para>L&agrave; est le hic... Certains systèmes d'exploitation (y compris
-          FreeBSD) vous permettent de faire débuter vos partitions juste après
-          le secteur principal de démarrage au cylindre 0, tête 0, secteur 2,
-          si vous le voulez. En fait, si vous donnez au programme
-          <citerefentry><refentrytitle>sysinstall</refentrytitle></citerefentry>
-          de FreeBSD, un disque dont le début est vierge ou un disque totalement
-          vide, c'est l&agrave; qu'il fera commencer par défaut la partition FreeBSD
-          (c'est tout du moins ce qu'il a fait quand je suis tombé dans ce
-          piège). Quand vous installez ensuite le gestionnaire de démarrage, si
-          c'est l'un de ceux qui occupent quelques secteurs supplémentaires
-          après le MBR, il écrase les données qui se trouvent au début de la
-          première partie. Dans le cas de FreeBSD, cela écrase le label du
-          disque et empêche de démarrer votre partition FreeBSD.</para>
-        <para>Le moyen facile d'éviter ce problème (et de vous garder le
-          possibilité d'essayer différents gestionnaires de démarrage par la
-          suite) est de ne pas allouer la première piste du disque quand vous le
-          partitionnez. Cela réserve l'espace entre le cylindre 0, tête 0,
-          secteur 2 et le cylindre 0, tête 0, secteur 63, et votre partition
-          commence au cylindre 1, tête 1, secteur 1. Pour ce que cela vaut,
-          quand vous créez une partition DOS au début de votre disque, DOS
-          laisse par défaut cet espace inoccupé (c'est pourquoi certains
-          gestionnaires de démarrage font l'hypothèse qu'il est disponible).
-          Mettre une partition DOS au début de votre disque vous permet aussi
-          d'éviter le problème. C'est ce que je préfère personnellement faire,
-          mettre une partition DOS de 1 Mo au début, parce que cela évite
-          aussi que la lettre désignant mon disque DOS primaire soit modifiée
-          ensuite quand je repartitionne.</para>
-        <para>Pour servir de référence, les gestionnaires de démarrage
-          suivants n'utilisent que le secteur principal de démarrage pour
-          mettre leur code et leurs données:</para>
-        <itemizedlist>
-          <listitem>
-            <para>OS-BS 1.35,</para>
-          </listitem>
-          <listitem>
-            <para>Boot Easy,</para>
-          </listitem>
-          <listitem>
-            <para>LILO.</para>
-          </listitem>
-        </itemizedlist>
-        <para>Ces gestionnaires de démarrage occupent quelques secteurs
-          supplémentaires après le secteur principal de démarrage:</para>
-        <itemizedlist>
-          <listitem>
-            <para>OS-BS 2.0 Béta 8 (secteurs 2-5),</para>
-          </listitem>
-          <listitem>
-            <para>gestionnaire de démarrage d'OS/2.</para>
-          </listitem>
-        </itemizedlist>
-      </sect3>
-      <sect3>
-        <title>Que faire si votre système ne démarre pas?</title>
-        <para>Il se peut qu'&agrave; un moment donné
-          de l'installation d'un gestionnaire
-          de démarrage, vous laissiez le MBR dans un état tel que votre machine
-          ne redémarre plus. C'est peu probable, mais possible lorsque vous
-          refaites un FDISK alors qu'il y a déj&agrave; un gestionnaire de démarrage
-          installé.</para>
-        <para>Si vous avez une partition DOS démarrable, vous pouvez démarrer
-          avec une disquette de démarrage DOS, et lancer:</para>
-        <informalexample>
-<screen><prompt>A:\></prompt> <userinput>FDISK /MBR</userinput></screen>
-        </informalexample>
-        <para>pour réinstaller le code d'origine de démarrage simple du DOS
-          seul sur le système. Vous pouvez alors démarrer DOS (et DOS
-          uniquement) depuis le disque dur. Une autre solution consiste &agrave;
-          réexécuter le programme d'installation de votre gestionnaire de
-          démarrage &agrave; partir d'une disquette démarrable.</para>
-      </sect3>
-    </sect2>
-  </sect1>
-</article>
diff --git a/fr_FR.ISO8859-1/articles/zip-drive/Makefile b/fr_FR.ISO8859-1/articles/zip-drive/Makefile
deleted file mode 100644
index 886e21cc9d..0000000000
--- a/fr_FR.ISO8859-1/articles/zip-drive/Makefile
+++ /dev/null
@@ -1,14 +0,0 @@
-# $FreeBSD$
-
-DOC?= article
-
-FORMATS?= html
-
-INSTALL_COMPRESSED?=gz
-INSTALL_ONLY_COMPRESSED?=
-
-SRCS= article.sgml
-
-DOC_PREFIX?= ${.CURDIR}/../../..
-
-.include "${DOC_PREFIX}/share/mk/doc.project.mk"
diff --git a/fr_FR.ISO8859-1/articles/zip-drive/article.sgml b/fr_FR.ISO8859-1/articles/zip-drive/article.sgml
deleted file mode 100644
index 246c35defd..0000000000
--- a/fr_FR.ISO8859-1/articles/zip-drive/article.sgml
+++ /dev/null
@@ -1,300 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1" standalone="no"?>
-<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V4.2-Based Extension//EN"
-	"../../../share/sgml/freebsd42.dtd" [
-<!ENTITY % entities PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Entity Set//FR" "../../share/sgml/entities.ent">
-%entities;
-]>
-
-<!--
-     The FreeBSD Documentation Project
-     The FreeBSD French Documentation Project
-
-     $FreeBSD$
-     Version française : Michel Boucey
-     Original revision: n.nn
-
--->
-
-<article lang="fr">
-  <articleinfo>
-    <title>Les lecteurs ZIP</title>
-
-    <authorgroup>
-      <author>
-	<firstname>Jason</firstname>
-	<surname>Bacon</surname>
-
-	<affiliation>
-	  <address><email>acadix@execpc.com</email></address>
-	</affiliation>
-      </author>
-    </authorgroup>
-
-    <pubdate>$FreeBSD$</pubdate>
-
-    <releaseinfo>$FreeBSD$</releaseinfo>
-
-   <abstract>
-
-      &trans.a.boucey;
-   </abstract>
-  </articleinfo>
-
-  <sect1>
-    <title>Les bases au sujet des lecteurs ZIP</title>
-
-    <para>Les disques ZIP sont des disques magnétiques amovibles de grande
-      capacité, accessibles en lecture et en écriture par les lecteurs ZIP de
-      marque IOMEGA.  Les disques ZIP sont similaires aux disquettes, en
-      étant cependant bien plus rapides et en ayant une capacité bien
-      supérieure. Alors qu'une disquette comporte typiquement 1.44 Mo,
-      les disques ZIP sont disponibles en deux capacités, &agrave; savoir 100 Mo
-      et 250 Mo. Les lecteurs ZIP ne  doivent pas être confondus avec
-      super-disquette, un lecteur de disquette de 120 Mo de capacité,
-      qui accepte aussi les traditionnelles disquettes de 1.44 Mo de
-      capacité.</para>
-
-    <para>IOMEGA vends aussi un lecteur &agrave; la capacité et aux performances
-      supérieurs appelé JAZZ.  Les lecteurs JAZZ sont livrés en 1 Go et 2
-      Go de capacité.</para>
-
-    <para>Les lecteurs ZIP sont disponibles en unité interne ou externe,
-      utilisant l'une des trois interfaces suivantes :</para>
-
-    <orderedlist>
-      <listitem>
-	<para>L'interface SCSI (Small Computer Standard Interface) est
-	  l'interface la plus rapide, la plus sophistiquée, la plus extensible,
-	  et la plus chère.  L'interface SCSI est utilisée sur tous types
-	  d'ordinateur, du PC &agrave; la station de travail RISC, jusqu'aux
-	  mini-ordinateurs, pour connecter tous types de périphériques
-	  tels que lecteurs de disque, lecteurs de bande, scanners, etc.
-	  Les lecteurs ZIP SCSI peuvent être internes ou externes, étant
-	  entendu que votre adaptateur SCSI possède un connecteur
-	  externe.</para>
-
-	<note>
-	  <para>Si vous utilisez un matériel SCSI externe, il est important
-	    de ne jamais le connecter ni le déconnecter tout pendant
-	    que l'ordinateur est en fonctionnement. Faire ceci risque de
-	    causer des dommages aux systèmes de fichiers sur les disques
-	    en cours de connection.</para>
-	</note>
-
-	<para>Si vous souhaitez le maximum de performance et la plus grande
-	  facilité d'installation, l'interface SCSI est le meilleur choix.  Cela
-	  demandera certainement l'adjonction d'un adaptateur SCSI, puisque la
-	  majorité des PC (exception faite des serveurs hautes performances)
-	  ne comportent pas d'origine de support SCSI.  Chaque adaptateur peut
-	  prendre en charge 7 ou 15 périphériques SCSI, selon le modèle.</para>
-
-	<para>Chaque périphérique SCSI a son propre contrôleur, et ces
-	  contrôleurs sont assez intelligents et bien standardisés (le
-	  second `S' de SCSI est l'abréviation de Standard), ce qui signifie
-	  , du point de vue du système d'exploitation, que tous les lecteurs de
-	  disques SCSI sont quasiment identiques, ceci vaut aussi pour les
-	  lecteurs de bandes, etc.  Pour prendre en charge du matériel SCSI, le
-	  système d'exploitation n'a besoin que d'un pilote (driver) propre &agrave;
-	  l'adaptateur utilisé, et un pilote générique propre &agrave; chaque type de
-	  matériel, &agrave; savoir un pilote pour disque SCSI, un pilote pour lecteur
-	  de bande, et ainsi de suite.  Il y a certains matériels SCSI qui
-	  peuvent être mieux utilisés grâce &agrave; des pilotes spécialisés (comme par
-	  exemple les lecteurs DAT), mais, généralement, ils fonctionnent bien
-	  avec le pilote générique. Il se peut alors que le pilote générique ne prenne pas
-	  en compte un certain nombre de caractéristiques spécifiques.</para>
-
-	<para>Utiliser un lecteur ZIP SCSI consiste simplement &agrave; déterminer
-	  quel fichier matériel dans le répertoire <filename>/dev</filename>
-	  représente le lecteur ZIP. Pour ce faire, on peut observer les messages lors
-	  de l'amorçage de BSD (ou dans <filename>/var/log/messages</filename> après le
-	  démarrage), où vous verrez une ligne ressemblant fort &agrave; ceci:</para>
-
-	<programlisting>da1: &lt;IOMEGA ZIP 100 D.13&gt; Removable Direct Access SCSI-2 Device</programlisting>
-
-	<para>Cela signifie que le lecteur ZIP est représenté par le fichier
-	  <filename>/dev/da1</filename>.</para>
-      </listitem>
-
-      <listitem>
-	 <para>L'interface IDE (Integrated Drive Electronics) est une interface
-	   de lecteur de disque bon marché utilisée pour les ordinateurs de bureau.
-	   La plus grande partie des matériels IDE est strictement interne.</para>
-
-	<para>Les performances des lecteurs ZIP IDE sont comparables &agrave; celles des
-	  lecteurs ZIP SCSI (l'interface IDE n'est pas aussi rapide que l'interface
-	  SCSI, mais les performances des lecteurs ZIP sont limitées essentiellement
-	  par leur mécanique, non pas &agrave; cause du bus SCSI).</para>
-
-	<para>L'inconvénient de l'interface IDE sont les limites qu'elle impose.
-	  La plupart des adaptateurs IDE ne peuvent prendre en charge que deux
-	  périphériques, et ne sont en général pas conçues pour le long terme. Par
-	  exemple, l'interface originelle IDE ne prend pas en charge les disques durs
-	  comportant plus de 1024 cylindres, ce qui oblige de nombreuses personnes &agrave;
-	  mettre &agrave; jour prématurément leurs équipements.  Si vous prévoyez d'étendre
-	  votre PC par l'adjonction d'un nouveau disque dur, d'un lecteur de bande,
-	  ou d'un scanner, vous pouvez investir dans un adaptateur SCSI et ZIP SCSI
-	  afin d'éviter des problèmes dans le futur.</para>
-
-	<para>Les périphériques IDE sous FreeBSD sont préfixés par un <literal>w</literal>.
-	  Par exemple, un disque dur IDE peut être <filename>/dev/wd0</filename>,
-	  un lecteur de CDROM IDE (ATAPI) peut être <filename>/dev/wcd1</filename>,
-	  et ainsi de suite.</para>
-      </listitem>
-
-      <listitem>
-	<para>L'interface port parallèle est populaire grâce aux périphériques externes
-	  portables tels que lecteurs ZIP externes, scanners, parce que potentiellement
-	  chaque ordinateur possède un port parallèle standard (habituellement utilisé
-	  pour les imprimantes).  Ceci rend aisé pour tout un chacun le transfert de données
-	  entre ordinateurs par simple le transport de ces lecteurs ZIP.</para>
-
-	<para>Les performances seront en général moindre qu'avec un lecteur ZIP ou IDE,
-	  du fait de la vitesse limitée du port parallèle. Cette vitesse varie
-	  considérablement d'un ordinateur &agrave; l'autre, et peut souvent être configurée
-	  &agrave; partir du système BIOS. Certaines machines demanderont une configuration du
-	  BIOS pour pouvoir faire fonctionner le port parallèle en mode bidirectionnel
-	  (Les ports parallèles ont seulement été conçus &agrave; l'origine pour fournir des
-	  données sortantes vers les imprimantes)</para>
-      </listitem>
-    </orderedlist>
-  </sect1>
-
-  <sect1>
-    <title>ZIP parallèle : Le pilote <devicename>vpo</devicename></title>
-
-    <para>Pour utiliser un lecteur ZIP port parallèle sous FreeBSD, le pilote
-      <devicename>vpo</devicename> doit être configuré dans le noyau. Les lecteurs
-      ZIP port parallèle ont aussi un contrôleur SCSI intégré. Le pilote vpo autorise
-      le noyau FreeBSD &agrave; communiquer avec le contrôleur SCSI du lecteur ZIP au travers
-      du port parallèle.</para>
-
-    <para>Depuis que le pilote vpo ne fait plus parti du noyau en standard (au
-      moins pour FreeBSD 3.2), vous avez &agrave; reconstruire le noyau afin de rendre
-      accessible ce périphérique.  La démarche de reconstruction d'un noyau est indiquée
-      en détails dans une autre section.  Les étapes suivantes indiquent brièvement
-      la démarche &agrave; suivre afin de mettre en état de marche le pilote vpo:</para>
-
-    <orderedlist>
-      <listitem>
-	<para>Lancer <command>/stand/sysinstall</command>, et installer les sources
-	  du noyau sur votre système.</para>
-
-	<screen>&prompt.root; <userinput>cd /sys/i386/conf</userinput>
-&prompt.root; <userinput>cp GENERIC MYKERNEL</userinput></screen>
-
-	<para>Editer <filename>MYKERNEL</filename>, changer la ligne
-	  <literal>ident</literal> en <literal>MYKERNEL</literal>, et décommenter
-	  la ligne décrivant le pilote vpo.</para>
-
-	<para>Si vous possédez un second port parallèle, vous pourriez avoir besoin
-	  de copier la section dédiée &agrave; <literal>ppc0</literal> pour créer le
-	  périphérique <literal>ppc1</literal>.  Le second port parallèle utilise
-	  généralement l'IRQ 5 et l'adresse 378.  Seul l'IRQ est requise pour le
-	  fichier de configuration.</para>
-
-	<para>Si votre disque dur est un SCSI, vous courez au devant d'un problème
-	  dans l'ordre de la détection des périphériques, qui entraînera le système
-	  &agrave; tenter d'utiliser le lecteur ZIP en tant que périphérique racine. Le démarrage
-	  échouera alors, &agrave; moins que vous ayez installé un système de fichiers racine
-	  sur le disque ZIP! Dans ce cas, vous aurez besoin de forcer le noyau &agrave; lier
-	  le disque SCSI racine &agrave; <filename>/dev/da0</filename>, &agrave; savoir le disque SCSI
-	  racine. Cela assignera alors le disque ZIP au prochain disque SCSI disponible,
-	  &agrave; savoir <literal>/dev/da1</literal>. Pour forcer votre disque dur SCSI en
-	  <literal>da0</literal>, changer la ligne
-
-	  <programlisting>device  da0</programlisting>
-
-	  en
-
-	  <programlisting>disk da0 at scbus0 target 0 unit 0</programlisting></para>
-
-	<para>Vous aurez probablement &agrave; changer la cible afin de la faire correspondre &agrave;
-	  l' ID SCSI de votre disque dur. Vous devrez aussi forcer l'entrée scbus0  afin
-	  de l'ajuster &agrave; votre contrôleur.  Par exemple, si vous avez un contrôleur 15xx
-	  de chez Adaptec, vous changerez
-
-	  <programlisting>controller scbus0</programlisting>
-
-	  en
-
-	  <programlisting>controller scbus0 at aha0</programlisting></para>
-
-	<para>En dernier lieu, puisque vous êtes en train d'éditer le fichier de
-	  configuration du noyau, profitez-en pour ôter tous les pilotes inutiles.
-	  Cela doit être fait avec de grandes précautions, et seulement si vous avez
-	  assez confiance en vous en ce qui concerne les modifications du noyau. Ôter
-	  les pilotes inutiles réduira la taille du noyau, laissant plus de mémoire disponible
-	  &agrave; vos applications.  Afin de déterminer les pilotes qui ne sont pas nécessaires,
-	  allez &agrave; la fin du fichier <filename>/var/log/messages</filename>, et recherchez
-	  les lignes comportant "not found" (non trouvé). Commenter alors ces périphériques
-	  dans votre fichier de configuration (par un # en tête de ligne). Vous pouvez aussi
-	  changer d'autres options afin de réduire la taille et d'accroître la rapidité de
-	  votre noyau. Lisez la section concernant la reconstruction du noyau pour de
-	  plus amples informations.</para>
-      </listitem>
-
-      <listitem>
-	<para>Il est maintenant temps de compiler le noyau:</para>
-
-	<screen>&prompt.root; <userinput>/usr/sbin/config MYKERNEL</userinput>
-&prompt.root; <userinput>cd ../../compile/MYKERNEL</userinput>
-&prompt.root; <userinput>make clean depend &amp;&amp; make all install</userinput></screen>
-      </listitem>
-    </orderedlist>
-
-    <para>Après le reconstruction du noyau, vous devez redémarrer.  Assurez-vous
-      que le lecteur ZIP est connecté au port parallèle avant que le démarrage ne
-      commence. Vous devriez voir apparaître le lecteur ZIP parmi les messages de
-      démarrage en tant que périphérique vp0 ou vp1, selon le port parallèle auquel
-      le lecteur est rattaché.  Vous devez pouvoir voir aussi &agrave; quel fichier
-      périphérique le lecteur ZIP a été associé. Ce sera <filename>/dev/da0</filename>
-      si vous n'avez pas d'autre disque SCSI dans le système, ou <filename>/dev/da1</filename>
-      si vous avez un disque dur SCSI &agrave; la racine de votre système.</para>
-  </sect1>
-
-  <sect1>
-    <title>Monter les disques ZIP</title>
-
-    <para>Pour accéder &agrave; un disque ZIP, vous avez simplement &agrave; le monter, comme
-      n'importe quel autre périphérique. Le système de fichiers est représenté
-      par la quatrième tranche sur le périphérique, que ce soit pour un disque ZIP
-      en SCSI ou en parallèle, vous devriez faire:</para>
-
-    <screen>&prompt.root; <userinput>mount_msdos /dev/da1s4 /mnt</userinput></screen>
-
-    <para>Pour les lecteurs ZIP IDE:</para>
-
-    <screen>&prompt.root; <userinput>mount_msdos /dev/wd1s4 /mnt</userinput></screen>
-
-    <para>Cela facilitera aussi les choses de mettre &agrave; jour <filename>/etc/fstab</filename>
-      afin de rendre le montage plus aisé. Ajoutez une ligne telle que la suivante, ajustée
-      &agrave; votre système:
-
-      <programlisting>/dev/da1s4  /zip msdos rw,noauto  0 0</programlisting>
-
-      et créer le répertoire <filename>/zip</filename>.</para>
-
-    <para>Vous pouvez alors monter simplement en tapant
-
-      <screen>&prompt.root; <userinput>mount /zip</userinput></screen>
-
-      et démonter en entrant
-
-      <screen>&prompt.root; <userinput>umount /zip</userinput></screen></para>
-
-    <para>Pour savoir plus sur le format de <filename>/etc/fstab</filename>,
-      voir &man.fstab.5;.</para>
-
-    <para>Vous pouvez aussi créer un système de fichiers FreeBSD sur un disque
-      ZIP en utilisant &man.newfs.8;.  Cependant, le disque ne sera utilisable
-      que par un système FreeBSD, et peut-être par quelques clônes Unix
-      reconnaissant le système de fichiers FreeBSD (mais certainement pas par
-      DOS ou Windows).</para>
-  </sect1>
-</article>
-
-
-
-
-
-
diff --git a/fr_FR.ISO8859-1/htdocs/docproj/translations.sgml b/fr_FR.ISO8859-1/htdocs/docproj/translations.sgml
index 6b8cf199cc..d124dbd1ed 100644
--- a/fr_FR.ISO8859-1/htdocs/docproj/translations.sgml
+++ b/fr_FR.ISO8859-1/htdocs/docproj/translations.sgml
@@ -114,9 +114,6 @@
   <dd><a href="http://www.cybershade.us/freebsd/bg/fdp/split/">Introduction au Projet de
     Documentation de FreeBSD pour les nouveaux participants</a></dd>
 
-  <dd><a href="http://www.cybershade.us/freebsd/bg/multi-os/">Installer et
-    Utiliser FreeBSD avec d'autres Systèmes d'Exploitation</a></dd>
-
   <dt><i>Documents en cours de traduction</i></dt>
 
   <dd>Manuel de référence FreeBSD</dd>
diff --git a/fr_FR.ISO8859-1/htdocs/docs/books.sgml b/fr_FR.ISO8859-1/htdocs/docs/books.sgml
index 32bb1502b9..3c446f64a3 100644
--- a/fr_FR.ISO8859-1/htdocs/docs/books.sgml
+++ b/fr_FR.ISO8859-1/htdocs/docs/books.sgml
@@ -116,14 +116,6 @@
 
 	  <!-- Articles are sorted by pathname -->
 
-	<p><a
-	  href="&enbase;/doc/en_US.ISO8859-1/articles/5-roadmap/index.html">Le
-	  planning de développement de la 5-STABLE.</a>
-	  (5-roadmap)<br/>
-	  Décrit les projets de développement &agrave;
-	  moyen terme et de production de version menant &agrave; la
-	  branche 5-STABLE.</p>
-
 	<p><a href="&enbase;/&url.articles;/bsdl-gpl/index.html">Pourquoi
 	  devriez-vous utiliser une licence de type BSD pour votre
 	  projet de logiciel libre</a> (bsdl-gpl)<br/>
@@ -142,13 +134,6 @@
 	  Amérique latine.</p>
 
 	<p><a
-	  href="&enbase;/doc/en_US.ISO8859-1/articles/checkpoint/index.html">Intégration
-	  de Checkpoint VPN-1/Firewall-1 et FreeBSD IPsec.</a>
-	  (checkpoint)<br/>
-	  Comment configurer Checkpoint VPN-1/Firewall-1 et FreeBSD
-	  IPsec.</p>
-
-	<p><a
 	  href="&enbase;/doc/&url.doc.langcode;/articles/committers-guide/index.html">Le
 	  Guide du "Committer"</a> (committers-guide)<br/>
 	  Informations pour les "committers" FreeBSD.></p>
@@ -192,23 +177,6 @@
 	  Un article avec quelques astuces sur les subtilités
 	  de CVSup.</p>
 
-	<p><a href="&enbase;/doc/&url.doc.langcode;/articles/dialup-firewall/index.html">Firewall
-	  avec connexion modem sous FreeBSD</a> (dialup-firewall)<br/>
-	  Comment mettre en place un firewall en utilisant PPP et ipfw
-	  avec une connexion modem et des adresses IP dynamiques.</p>
-
-	<p><a
-	  href="&enbase;/doc/&url.doc.langcode;/articles/diskless-x/index.html">Mise
-	  en oeuvre d'un terminal X sans disque dur</a>
-	  (diskless-x)<br/>
-	  Comment mettre en place un terminal X sans disque dur.</p>
-
-	<p><a
-	  href="&enbase;/doc/&url.doc.langcode;/articles/euro/article.html">Le
-	  symbole Euro sous FreeBSD</a> (euro)<br/>
-	  Comment configurer FreeBSD et les applications pour afficher
-	  le symbole Euro.</p>
-
 	<p><a
 	  href="&enbase;/doc/en_US.ISO8859-1/articles/explaining-bsd/index.html">Expliquer
 	  BSD</a> (explaining-bsd)<br/>
@@ -235,13 +203,6 @@
 	  programmes.</p>
 
 	<p><a
-	  href="&enbase;/doc/&url.doc.langcode;/articles/formatting-media/index.html">Formatage
-	  des supports de données sous FreeBSD</a>
-	  (formatting-media)<br/>
-	  Comment découper, partitionner et formater les
-	  supports fixes et amovibles sous FreeBSD.</p>
-
-	<p><a
 	  href="&enbase;/doc/en_US.ISO8859-1/articles/freebsd-questions/index.html">Comment
 	  obtenir les meilleurs résultats sur la liste de
 	  diffusion FreeBSD-questions</a> (freebsd-questions)<br/>
@@ -250,13 +211,6 @@
 	  diffusion -questions.</p>
 
 	<p><a
-	  href="&enbase;/doc/en_US.ISO8859-1/articles/hats/index.html">Travailler
-	  avec les "chefs"</a> (hats)<br/>
-	  Un guide du "committer" pour travailler avec les "chefs"
-	  (d'autres "committers" qui ont autorité sur certaines
-	  parties spécifiques de FreeBSD).</p>
-
-	<p><a
 	  href="&enbase;/doc/en_US.ISO8859-1/articles/hubs/index.html">Créer
 	  un site miroir de FreeBSD</a> (hubs)<br/>
 	  Le guide complet pour créer un miroir du site web
@@ -298,14 +252,6 @@
 	  Une introduction &agrave; l'utilisation du lecteur de
 	  courrier électronique MH sur FreeBSD.</p>
 
-	<p><a
-	  href="&enbase;/doc/&url.doc.langcode;/articles/multi-os/index.html">Utiliser
-	  FreeBSD avec d'autres systèmes d'exploitation</a>
-	  (multi-os)<br/>
-	  Comment installer FreeBSD en plus d'un ou plusieurs
-	  systèmes d'exploitation différents sur le
-	  même ordinateur.</p>
-
 	<p><a href="&enbase;/doc/&url.doc.langcode;/articles/new-users/index.html">Premiers
 	  Pas avec FreeBSD</a> (new-users)<br/>
 	  Pour les nouveaux venus &agrave; FreeBSD et &unix;.</p>
@@ -406,43 +352,12 @@
 	  &agrave; état solide sous FreeBSD.</p>
 
 	<p><a
-	  href="&enbase;/doc/en_US.ISO8859-1/articles/storage-devices/index.html">Les
-	  Périphériques de Stockage</a>
-	  (storage-devices)<br/>
-	  Informations détaillées sur l'utilisation des
-	  périphériques de stockage avec FreeBSD,
-	  notamment les disques ESDI et SCSI, les lecteurs de bandes
-	  et les lecteurs de CDROM.</p>
-
-	<p><a href="&enbase;/&url.articles;/version-guide/index.html">Choisir la
-	  bonne version de FreeBSD</a> (version-guide)<br/>
-	  Comment décider quelle version de FreeBSD est la plus
-	  adaptée &agrave; vos besoins.  Parmi les sujets
-	  abordés, les versions officielles, les branches, les
-	  différences entre -CURRENT et -STABLE, et les
-	  objectifs de planification actuels du projet.</p>
-
-	<p><a
-	  href="&enbase;/doc/en_US.ISO8859-1/articles/vinum/index.html">Aborder
-	  Vinum: une base pour des serveurs &agrave; haute
-	  fiabilité</a> (vinum)<br/>
-	  Une première introduction aux serveurs &agrave;
-	  tolérance de panne et un guide pas-&agrave;-pas pour
-	  en construire un avec l'aide de Vinum.</p>
-
-	<p><a
 	  href="&enbase;/doc/en_US.ISO8859-1/articles/vm-design/index.html">Conception
 	  du système de mémoire virtuelle de FreeBSD</a>
 	  (vm-design)<br/>
 	  Une description simple d'accès de la conception du
 	  système de mémoire virtuelle de FreeBSD.</p>
 
-	<p><a
-	  href="&enbase;/doc/&url.doc.langcode;/articles/zip-drive/index.html">Les
-	  lecteurs Zip et FreeBSD</a> (zip-drive)<br/>
-	  Comment formater, monter et utiliser un Zip Iomega (SCSI,
-	  IDE, ou parallèle) sous FreeBSD.</p>
-
     <h2>Sur d'autres sites web</h2>
 
       <p>Divers efforts indépendants ont aussi produit une
diff --git a/fr_FR.ISO8859-1/htdocs/news/2000/index.sgml b/fr_FR.ISO8859-1/htdocs/news/2000/index.sgml
index 1327f12d31..3f8b81a3a8 100644
--- a/fr_FR.ISO8859-1/htdocs/news/2000/index.sgml
+++ b/fr_FR.ISO8859-1/htdocs/news/2000/index.sgml
@@ -285,7 +285,7 @@
 	href="http://www.jp.FreeBSD.org/">http://www.jp.FreeBSD.org/</a>.</p>
 
 	<p>Nouvel article qui explique comment <a
-	  href="&base;/tutorials/dialup-firewall/index.html">utiliser PPP, natd,
+	  href="http://docs.freebsd.org/doc/9.0-RELEASE/usr/share/doc/freebsd/en_US.ISO8859-1/articles/dialup-firewall/index.html">utiliser PPP, natd,
 	  et ipfw</a> pour mettre en place un firewall avec une connexion
 	  PPP en dialup.</p>
 
diff --git a/fr_FR.ISO8859-1/htdocs/news/2001/news.xml b/fr_FR.ISO8859-1/htdocs/news/2001/news.xml
index 089d2ae170..a391d500e3 100644
--- a/fr_FR.ISO8859-1/htdocs/news/2001/news.xml
+++ b/fr_FR.ISO8859-1/htdocs/news/2001/news.xml
@@ -314,7 +314,7 @@
 	  <title>"Bootstrapping" Vinum : une base pour des serveurs fiables</title>
 	  <p><a href="mailto:Bob@BGPBook.Com">Bob Van Valzah</a> propose
 	    un article d'introduction <a
-	    href="$base/../doc/en_US.ISO8859-1/articles/vinum/index.html">
+	    href="http://docs.freebsd.org/doc/9.0-RELEASE/usr/share/doc/freebsd/en_US.ISO8859-1/articles/vinum/index.html">
 	    aux serveurs à haute-disponibilité et décrit les étapes à suivre
             pour réaliser ce type de serveur avec l'aide de Vinum</a>.</p>
 	</event>
diff --git a/fr_FR.ISO8859-1/htdocs/news/2002/news.xml b/fr_FR.ISO8859-1/htdocs/news/2002/news.xml
index a86d2d389c..cf5957602b 100644
--- a/fr_FR.ISO8859-1/htdocs/news/2002/news.xml
+++ b/fr_FR.ISO8859-1/htdocs/news/2002/news.xml
@@ -836,7 +836,7 @@
 
           <p>Aaron Kaplan a réalisé un nouvel article qui explique comment
             configurer votre système pour utiliser le nouveau <a
-              href="$base/../doc/fr_FR.ISO8859-1/articles/euro/article.html">symbole
+              href="http://docs.freebsd.org/doc/9.0-RELEASE/usr/share/doc/freebsd/fr_FR.ISO8859-1/articles/euro/index.html">symbole
               Euro sur FreeBSD</a>.</p>
         </event>
       </day>
diff --git a/fr_FR.ISO8859-1/htdocs/releng/index.sgml b/fr_FR.ISO8859-1/htdocs/releng/index.sgml
index a281542331..054dceb4a3 100644
--- a/fr_FR.ISO8859-1/htdocs/releng/index.sgml
+++ b/fr_FR.ISO8859-1/htdocs/releng/index.sgml
@@ -277,25 +277,6 @@
         configurer un groupe de machines pour en faire un "cluster de ports", comment
         regrouper les paquetages pour le media utilisé et comment vérifier la cohérence
         d'un ensemble de paquetages.</small></p></li>
-
-  <li><p><a
-        href="&enbase;/doc/en_US.ISO8859-1/articles/5-roadmap/index.html">Feuille de route de FreeBSD
-        5-STABLE</a><br/>
-
-      <small>Décrit la feuille de route du projet pour atteindre la branche RELENG_5.
-        Incluait le statut général de 5.x, ce qu'il restait &agrave; faire et
-        des plannings (provisoires).  Notez que ce document a maintenant un intérêt
-        principalement historique.</small></p></li>
-
-  <li><p><a
-	href="&enbase;/doc/en_US.ISO8859-1/articles/version-guide/index.html">Choisir
-	la bonne version de FreeBSD</a><br/>
-
-      <small>Comment décider quelle version de FreeBSD est la plus
-	adaptée &agrave; vos besoins.  Parmi les sujets abordés, les versions officielles, les branches, les différences
-	entre -CURRENT et -STABLE, et les objectifs de planification actuels
-	du projet.</small></p></li>
-
 </ul>
 
 <a name="team"></a>
diff --git a/hu_HU.ISO8859-2/articles/Makefile b/hu_HU.ISO8859-2/articles/Makefile
index 4fc98c0b3e..b1637ae754 100644
--- a/hu_HU.ISO8859-2/articles/Makefile
+++ b/hu_HU.ISO8859-2/articles/Makefile
@@ -10,14 +10,11 @@ MAINTAINER=	gabor@FreeBSD.org
 
 SUBDIR =	compiz-fusion
 SUBDIR+=	cups
-SUBDIR+=	dialup-firewall
 SUBDIR+=	explaining-bsd
 SUBDIR+=	gjournal-desktop
 SUBDIR+=	laptop
 SUBDIR+=	linux-comparison
 SUBDIR+=	linux-users
-SUBDIR+=	multi-os
-SUBDIR+=	version-guide
 
 DOC_PREFIX?= ${.CURDIR}/../..
 .include "${DOC_PREFIX}/share/mk/doc.project.mk"
diff --git a/hu_HU.ISO8859-2/articles/dialup-firewall/Makefile b/hu_HU.ISO8859-2/articles/dialup-firewall/Makefile
deleted file mode 100644
index e9d923ec7e..0000000000
--- a/hu_HU.ISO8859-2/articles/dialup-firewall/Makefile
+++ /dev/null
@@ -1,28 +0,0 @@
-# $FreeBSD$
-#
-# Article: Dialup firewalling with FreeBSD
-#
-# %SOURCE%    en_US.ISO8859-1/articles/dialup-firewall/Makefile
-# %SRCID%     1.5
-#
-
-#
-# Tidy messes up iso-8859-2 characters
-#
-
-NO_TIDY= yes
-
-MAINTAINER= doc@FreeBSD.org
-
-DOC?= article
-
-FORMATS?= html
-INSTALL_COMPRESSED?= gz
-INSTALL_ONLY_COMPRESSED?=
-
-SRCS=	article.sgml
-
-URL_RELPREFIX?=	../../../..
-DOC_PREFIX?= ${.CURDIR}/../../..
-
-.include "${DOC_PREFIX}/share/mk/doc.project.mk"
diff --git a/hu_HU.ISO8859-2/articles/dialup-firewall/article.sgml b/hu_HU.ISO8859-2/articles/dialup-firewall/article.sgml
deleted file mode 100644
index 84e00f9f47..0000000000
--- a/hu_HU.ISO8859-2/articles/dialup-firewall/article.sgml
+++ /dev/null
@@ -1,425 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-2" standalone="no"?>
-<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V4.2-Based Extension//EN"
-	"../../../share/sgml/freebsd42.dtd" [
-<!ENTITY % entities PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Entity Set//HU" "../../share/sgml/entities.ent">
-%entities;
-]>
-
-<!-- The FreeBSD Hungarian Documentation Project
-     Translated by: PALI, Gabor <pgj@FreeBSD.org>
-     %SOURCE%	en_US.ISO8859-1/articles/dialup-firewall/article.sgml
-     %SRCID%	1.43
--->
-
-<article lang="hu">
-  <articleinfo>
-    <title>Tûzfal létrehozása
-      betárcsázós kapcsolatokhoz &os;-vel</title>
-
-    <authorgroup>
-      <author>
-	<firstname>Marc</firstname>
-	<surname>Silver</surname>
-
-	<affiliation>
-	  <address><email>marcs@draenor.org</email></address>
-	</affiliation>
-      </author>
-    </authorgroup>
-
-    <legalnotice id="trademarks" role="trademarks">
-      &tm-attrib.freebsd;
-      &tm-attrib.general;
-    </legalnotice>
-
-    <pubdate>$FreeBSD$</pubdate>
-
-    <releaseinfo>$FreeBSD$</releaseinfo>
-
-    <abstract>
-      <para>Ebben a cikkben bemutatjuk, hogyan lehet beállítani
-	tûzfalat a PPP-típusú kapcsolatokhoz a &os; valamint
-	az IPFW segítségével, különös
-	tekintettel az olyan esetekre, ahol dinamikusan kiosztott
-	IP-címmel használjuk a rendszert.  Ez a
-	leírás azonban nem tartalmazza magának a
-	PPP-kapcsolatnak a beállítását.  A
-	PPP-kapcsolatok létrehozásához kérjük
-	tekintse át a &man.ppp.8; man oldalt.</para>
-
-	<para><emphasis>Fordította: Páli Gábor,
-	  utolsó ellenõrzés:
-	  2010.11.28.</emphasis></para>
-    </abstract>
-  </articleinfo>
-
-  <sect1 id="preface">
-    <title>Bevezetés</title>
-
-    <para>A leírásban felvázoljuk azokat a
-      lépéseket, amelyek szükségesek az Internet
-      szolgáltatónk által dinamikusan kiosztott
-      IP címmel rendelkezõ rendszerünk
-      tûzfalának kiépítéséhez.
-      Habár ezen cikk szerzõje minden megtett, hogy ez a
-      leírás minél hasznosabb és pontosabb
-      legyen, örömmel várja az esetleges
-      megjegyzéseket és	javaslatokat a
-      <email>marcs@draenor.org</email> címen.</para>
-   </sect1>
-
-  <sect1 id="kernel">
-    <title>Beállítások a rendszermagban</title>
-
-    <para>Az IPFW használatához bele kell fordítani
-      némi támogatást a rendszer magjába.  Ha
-      többet szeretne tudni a rendszermag
-      újrafordításáról,
-      kérjük, olvassa el a <ulink
-	url="&url.books.handbook;/kernelconfig.html">	a rendszermag
-	beállításáról szóló
-	fejezetet a Kézikönyvben</ulink>.  Az IPFW
-      támogatásához az alábbi sorokat kell
-      még hozzáírni a rendszermag
-      konfigurációs állományához:</para>
-
-    <variablelist>
-      <varlistentry>
-	<term><literal>options IPFIREWALL</literal></term>
-
-	<listitem>
-	  <para>Elérhetõvé teszi a rendszermag
-	    tûzfalért felelõs rutinjait.</para>
-
-	  <note><para>A cikk a &os; 5.X-es verziójának
-	    használatát feltételezi.  Azoknak a
-	    felhasználóknak, akik még a &os; 4.X-es
-	    verzióját használják, a
-	    rendszermagjukat a <emphasis>IPFW2</emphasis>
-	    támogatással kell újrafordítaniuk.
-	    A &os; 4.X felhasználóknak továbbá
-	    javasolt elolvasniuk ezzel kapcsolatosan a &man.ipfw.8; man
-	    oldalt, kiemelten odafigyelve a
-	    <emphasis>IPFW2 HASZNÁLATA A &os;-STABLE-ben</emphasis>
-	    fejezetre.</para></note>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-	<term><literal>options IPFIREWALL_VERBOSE</literal></term>
-
-	<listitem>
-	  <para>Naplózott csomagok küldése a
-	    rendszernaplóba.</para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-	<term><literal>options
-	    IPFIREWALL_VERBOSE_LIMIT=<replaceable>500</replaceable></literal></term>
-
-	<listitem>
-	  <para>Korlátozza az egyezõ tartalmú sorok
-	    naplózásának mennyiségét.
-	    Ezzel lehetõvé válik, hogy a
-	    rendszernapló elárasztásának
-	    kockázata nélkül naplózzuk a
-	    tûzfal minden egyes tevékenységét,
-	    például egy "denial of service" (DoS)
-	    típusú támadás esetén.
-	    Itt az <replaceable>500</replaceable> egy viszonylag jó
-	    kiindulási érték lehet, de nyugodtan
-	    változtathajuk igényeink szerint.</para>
-	</listitem>
-      </varlistentry>
-    </variablelist>
-
-    <warning><para>Amikor a rendszermag újrafordítása
-      befejezõdött, <emphasis>ne indítsuk újra
-      egybõl</emphasis> a rendszerünket.  Ha így
-      cselekszünk, könnyedén kizárhatjuk magunkat
-      belõle!  Csak azután szabad újraindítanunk
-      és ezzel mûködésbe hozni a tûzfalat,
-      miután a hozzá tartozó szabályok a
-      megfelelõ helyre kerültek és minden hozzájuk
-      kapcsolódó konfigurációs
-      állományt megfelelõen
-      beállítottunk.</para></warning>
-  </sect1>
-
-  <sect1 id="rcconf">
-    <title>Az <filename>/etc/rc.conf</filename> módosítása
-      a tûzfal betöltéséhez</title>
-
-    <para>Az <filename>/etc/rc/rc.conf</filename> konfigurációs
-      állományt kell némileg átírnunk
-      a tûzfal betöltéséhez, valamint a
-      hozzá tartozó szabályokat tartalmazó
-      állomány helyének megadásához.
-      Adjuk tehát hozzá az alábbi sorokat a
-      <filename>/etc/rc/rc.conf</filename>-hoz:</para>
-
-    <programlisting>firewall_enable="YES"
-firewall_script="/etc/firewall/fwrules"</programlisting>
-
-    <para>Ha többet szeretne tudni ezeknek a soroknak a
-      jelentésérõl, akkor nézze át a
-      <filename>/etc/defaults/rc.conf</filename> állományt
-      és olvassa el a &man.rc.conf.5; man oldalt.</para>
-  </sect1>
-
-  <sect1>
-    <title>A PPP-ben levõ címfordítás
-      bekapcsolása</title>
-
-    <para>Amennyiben a helyi hálózatunkban fellelhetõ
-      további kliensek számára is szeretnénk
-      elérhetõvé tenni az Internetet az
-      átjárónkon át, szükségünk
-      lesz a PPP-ben található hálózati
-      címfordítás (Network Address Translation, NAT)
-      beindítására.  Ezt az
-      <filename>/etc/rc.conf</filename>-ben a következõ
-      sorok hozzáadásával tehetjük meg:</para>
-
-    <programlisting>ppp_enable="YES"
-ppp_mode="auto"
-ppp_nat="YES"
-ppp_profile="<replaceable>internet_beallitasok</replaceable>"</programlisting>
-
-    <note>
-      <para>Ne felejtsük el kicserélni az
-	<literal>internet_beallitasok</literal>
-	értékét a saját
-	betárcsázós
-	beállításait tartalmazó
-	állomány nevére!  Ennek nevének meg
-	kell egyeznie a beállításaink
-	<filename>/etc/ppp/ppp.conf</filename> állományban
-	szereplõ nevével.</para>
-    </note>
-  </sect1>
-
-  <sect1 id="rules">
-    <title>A tûzfal szabályai</title>
-
-    <para>Most fogjuk megadni a rendszerünk tûzfalának
-      szabályait.  Az itt ismertetésre kerülõ
-      szabályok egy olyan általános sablont
-      kívánnak bemutatni, amely a legtöbb
-      betárcsázós felhasználó
-      számára megfelelnek.  Habár
-      kétségtelen, hogy nem fogja mindenki igényeit
-      tökéletesen kielégíteni, azonban segít
-      megmutatni az IPFW mûködésének alapelveit
-      és könnyedén tovább is
-      fejleszthetõ.</para>
-
-    <para>Elsõként kezdjük a "zárt tûzfal"
-      alapjaival.  A zárt tûzfal lényegében azon a
-      feltevésen alapszik, hogy alapvetõen mindent kizárunk
-      a rendszerbõl.  Ezt követõen a rendszergazda
-      egyesével megadhatja azokat szabályokat, amelyeket
-      engedélyezni kíván valamit.  A szabályok
-      közül elöszõr mindig azokat adjuk meg, amikkel
-      engedélyezünk, majd azokat, amikkel tiltunk.  Az
-      alapfeltételezés szerint tehát a szabályokkal
-      megadunk mindent, amit engedélyezünk a tûzfalon,
-      és minden más pedig automatikusan tiltásra
-      kerül.</para>
-
-    <para>Ezt követõen hozzunk létre egy
-      könyvtárat, ahol majd tárolni a fogjuk a
-      tûzfalunk beállításait.  Ebben a
-      példában a
-      <filename class="directory">/etc/firewall/</filename>
-      könyvtárat fogjuk használni erre a célra.
-      Lépjünk be ebbe a könyvtárba és hozzunk
-      létre egy <filename>fwrules</filename> nevû
-      állományt, ahogy azt az <filename>rc.conf</filename>-ban
-      is megadtuk.  Természetesen ez az elnevezés sem
-      kötött, nyugodtan megváltoztathatjuk bármire.
-      A leírás pusztán csak egy példát
-      ad erre.</para>
-
-    <para>Most pedig nézzünk egy megjegyzésekkel
-      tûzdelt szabályokat tartalmazó
-      állományt:</para>
-
-    <programlisting># Definiálunk egy parancsot a tûzfalat összeállító program elérésére
-# (ld. /etc/rc.firewall). Remélhetõleg így könnyebb is lesz olvasni.
-fwcmd="/sbin/ipfw"
-
-# Megadjuk a külsõ hálózati csatolót. Ha felhasználói ppp-t használunk,
-# akkor ez valószínûleg a tun0 lesz.
-oif="tun0"
-
-# Megadjuk a belsõ hálózati csatolót. Ez többnyire (a helyi hálózaton
-# is elerhetõ) hálózati kártyánk lesz. Mindenképpen ellenõrizzük, hogy
-# jól adtuk-e meg!
-iif="fxp0"
-
-# Töröltessünk a rendszerben jelenleg érvényben levõ össze szabályt,
-# még mielõtt betöltenénk a sajátjainkat.
-$fwcmd -f flush
-
-# Ellenõrizzük az összes csomag állapotát.
-$fwcmdl add check-state
-
-# Tiltsuk le az elrejtést a külsõ csatolón.
-$fwcmd add deny ip from any to any in via $oif not verrevpath
-
-# Engedélyezzünk minden általunk kezdeményezett kapcsolatot és
-# tartsuk is meg az állapotukat. Ellenben tiltsunk minden olyat,
-# amihez nincs semmilyen dinamikus szabály.
-$fwcmd add allow ip from me to any out via $oif keep-state
-$fwcmd add deny tcp from any to any established in via $oif
-
-# Engedélyezzünk minden kapcsolatot a helyi hálózaton.
-$fwcmd add allow ip from any to any via $iif
-
-# Engedélyezzük a helyi (gépen belüli) forgalmat.
-$fwcmd add allow all from any to any via lo0
-$fwcmd add deny all from any to 127.0.0.0/8
-$fwcmd add deny ip from 127.0.0.0/8 to any
-
-# Engedélyezzük az Internetrõl hozzánk látogatóknak, hogy elérhessék
-# a 22-es ill. a 80-as portokat. Így ez a példa kifejezetten az SSH
-# (sshd) es HTTP (webszerver) típusú kapcsolatokat engedélyezi.
-$fwcmd add allow tcp from any to me dst-port 22,80 in via $oif setup keep-state
-
-# Engedélyezzük az ICMP csomagokat: vegyük ki a 8-as típust, ha nem
-# szeretnénk a gépünket pingek által elérhetõvé tenni.
-$fwcmd add allow icmp from any to any via $oif icmptypes 0,3,8,11,12
-
-# Tiltsunk és naplózzunk minden mást.
-$fwcmd add deny log ip from any to any</programlisting>
-
-    <para>Most már van egy teljesen mûködõképes
-      tûzfalunk, amely csak és kizárólag a 22-es,
-      80-es portokon enged kapcsolatot létesíteni, és
-      minden egyéb próbálkozást naplóz.
-      Így már nyugodtan újraindíthatjuk a
-      rendszerünket, és ezt követõen a tûzfalunk
-      magától elindul és a hozzá tartozó
-      szabályrendszer betöltõdik.  Ha bármilyen
-      hibát találna benne vagy problémába
-      ütközne a használata során, esetleg valamilyen
-      építõ jellegû javaslata van, kérem,
-      keressen meg e-mailben!</para>
-  </sect1>
-
-  <sect1>
-    <title>Kérdések</title>
-
-    <qandaset>
-      <qandaentry>
-        <question>
-	  <para><errorname>limit 500 reached on entry 2800</errorname>.
-	    Ilyen és ehhez hasonló hibaüzeneteket kapok,
-	    miután a számítógépem abbahagyja
-	    a szabályhoz tartozó eldobott csomagok
-	    naplózását.  Mûködik még
-	    ilyenkor ea tûzfalam?</para>
-        </question>
-
-	<answer>
-	  <para>Ez csupán annyit jelent, hogy az adott szabályt
-	    elérte a hozzá tartozó maximális
-	    naplóbejegyzést.  A szabály maga még
-	    mindig aktív, viszont addig nem fog tudni naplózni,
-	    amíg nem töröljük valahogy a
-	    bejegyzésszámlálóját.
-	    Például így lehet törölni az
-	    említett számlálót:
-	  </para>
-
-	  <screen>&prompt.root; <userinput>ipfw resetlog</userinput></screen>
-
-	  <para>Vagy úgy is elkerülhetjük ezt a
-	    hibaüzenetet, ha növeljük a szabályhoz
-	    tartozó naplóbejegyzések számát
-	    a rendszermag konfigurációs
-	    állományában, az
-	    <option>IPFIREWALL_VERBOSE_LIMIT</option>
-	    beállítás
-	    megváltoztatásával, a fentebb leírt
-	    módon.  A rendszermag újrafordítása
-	    eacute;s a rendszer újraindítása
-	    nélkül is megváltoztatható ez a
-	    korlát, a net.inet.ip.fw.verbose_limit &man.sysctl.8;
-	    használatával.</para>
-	</answer>
-      </qandaentry>
-
-      <qandaentry>
-	<question>
-	  <para>Valami nem stimmel.  Követtem a leírásban
-	    szereplõ utasításokat pontról pontra, de
-	    kizártam magamat.</para>
-	</question>
-
-	<answer>
-	  <para>A leírás feltételezi, hogy
-	    <emphasis>felhasználói ppp-t</emphasis>
-	    használunk, és ezért a megadott
-	    szabályok a <devicename>tun0</devicename> (amely megfelel
-	    a &man.ppp.8; (azaz <emphasis>felhasználói ppp,
-	    user-ppp</emphasis>) által létrehozott elsõ
-	    kapcsolatnak) felületen keresztül mûködnek.
-	    A további kapcsolatok rendre a
-	    <devicename>tun1</devicename>, <devicename>tun2</devicename> stb.
-	    neveket használják.</para>
-
-	  <para>Továbbá érdemes megjegyezni, hogy a
-	    &man.pppd.8; ehelyett a <devicename>ppp0</devicename>
-	    felületet használja, így tehát ha a
-	    PPP-kapcsolatot a &man.pppd.8;-al indítottuk el, akkor a
-	    <devicename>tun0</devicename> neveket mindenhol
-	    <devicename>ppp0</devicename> nevekre kell cserélni.
-	    Íme egy példa arra, hogyan írjuk át
-	    gyorsan a szabályainkat ilyen alakúra (az
-	    eredeti szabályokat pedig
-	    <filename>fwrules_tun0</filename> néven
-	    elmentjük):</para>
-
-	  <screen>&prompt.user; <userinput>cd /etc/firewall</userinput>
-	    /etc/firewall&prompt.user; <userinput>su</userinput>
-	    <prompt>Password:</prompt>
-	    /etc/firewall&prompt.root; <userinput>mv fwrules fwrules_tun0</userinput>
-	    /etc/firewall&prompt.root; <userinput>cat fwrules_tun0 | sed s/tun0/ppp0/g > fwrules</userinput></screen>
-
-	  <para>Legkönnyebben úgy tudjuk kideríteni, hogy
-	    van &man.ppp.8;-t vagy éppen &man.pppd.8;-t
-	    használunk, hogy átnézzük az
-	    &man.ifconfig.8; kimenetét, amikor már van
-	    aktív kapcsolatunk.  Például, ha a
-	    kapcsolatot a &man.pppd.8;-vel hoztuk létre, akkor valami
-	    ilyesmit kellene látnunk (csak a lényeget
-	    mutatjuk):</para>
-
-	  <screen>&prompt.user; <userinput>ifconfig</userinput>
-	    <emphasis>(kimarad...)</emphasis>
-	    ppp0: flags=<replaceable>8051&lt;UP,POINTOPOINT,RUNNING,MULTICAST&gt; mtu 1524</replaceable>
-                    inet <replaceable>xxx.xxx.xxx.xxx</replaceable> --&gt; <replaceable>xxx.xxx.xxx.xxx</replaceable> netmask <replaceable>0xff000000</replaceable>
-	    <emphasis>(kimarad...)</emphasis></screen>
-
-	  <para>Másrészt viszont a &man.ppp.8;-vel (vagyis
-	    <emphasis>felhasználói ppp</emphasis>-vel)
-	     létesített kapcsolatok esetén
-	     nagyjából ezt:</para>
-
-	  <screen>&prompt.user; <userinput>ifconfig</userinput>
-	    <emphasis>(kimarad...)</emphasis>
-	    ppp0: flags=<replaceable>8010&lt;POINTOPOINT,MULTICAST&gt; mtu 1500</replaceable>
-	    <emphasis>(kimarad...)</emphasis>
-	    tun0: flags=<replaceable>8051&lt;UP,POINTOPOINT,RUNNING,MULTICAST&gt; mtu 1524</replaceable>
-	            <emphasis>(IPv6 kimarad...)</emphasis>
-                    inet <replaceable>xxx.xxx.xxx.xxx</replaceable> --&gt; <replaceable>xxx.xxx.xxx.xxx</replaceable> netmask <replaceable>0xffffff00</replaceable>
-                    Opened by PID <replaceable>xxxxx</replaceable>
-            <emphasis>(kimarad...)</emphasis></screen>
-	</answer>
-      </qandaentry>
-    </qandaset>
-  </sect1>
-</article>
diff --git a/hu_HU.ISO8859-2/articles/multi-os/Makefile b/hu_HU.ISO8859-2/articles/multi-os/Makefile
deleted file mode 100644
index caeacfd520..0000000000
--- a/hu_HU.ISO8859-2/articles/multi-os/Makefile
+++ /dev/null
@@ -1,28 +0,0 @@
-# $FreeBSD$
-#
-# Article: Installing and Using FreeBSD With Other Operating Systems
-#
-# %SOURCE%    en_US.ISO8859-1/articles/multi-os/Makefile
-# %SRCID%     1.12
-#
-
-#
-# Tidy messes up iso-8859-2 characters
-#
-
-NO_TIDY= yes
-
-MAINTAINER= doc@FreeBSD.org
-
-DOC?= article
-
-FORMATS?= html
-INSTALL_COMPRESSED?= gz
-INSTALL_ONLY_COMPRESSED?=
-
-SRCS=	article.sgml
-
-URL_RELPREFIX?=	../../../..
-DOC_PREFIX?= ${.CURDIR}/../../..
-
-.include "${DOC_PREFIX}/share/mk/doc.project.mk"
diff --git a/hu_HU.ISO8859-2/articles/multi-os/article.sgml b/hu_HU.ISO8859-2/articles/multi-os/article.sgml
deleted file mode 100644
index 5357eab957..0000000000
--- a/hu_HU.ISO8859-2/articles/multi-os/article.sgml
+++ /dev/null
@@ -1,975 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-2" standalone="no"?>
-<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V4.2-Based Extension//EN"
-	"../../../share/sgml/freebsd42.dtd" [
-<!ENTITY % entities PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Entity Set//HU" "../../share/sgml/entities.ent">
-%entities;
-]>
-
-<!-- The FreeBSD Hungarian Documentation Project
-     Translated by: PALI, Gabor <pgj@FreeBSD.org>
-     %SOURCE%	en_US.ISO8859-1/articles/multi-os/article.sgml
-     %SRCID%	1.39
--->
-
-<article lang="hu">
-  <articleinfo>
-    <title>A &os; telepítése és használata
-      más operációs rendszerekkel együtt</title>
-
-    <authorgroup>
-      <author>
-	<firstname>Jay</firstname>
-	<surname>Richmond</surname>
-	<affiliation>
-	  <address>
-	    <email>jayrich@sysc.com</email>
-	  </address>
-	</affiliation>
-      </author>
-    </authorgroup>
-
-    <pubdate>1996. augusztus 6.</pubdate>
-
-    <legalnotice id="trademarks" role="trademarks">
-      &tm-attrib.freebsd;
-      &tm-attrib.ibm;
-      &tm-attrib.linux;
-      &tm-attrib.microsoft;
-      &tm-attrib.powerquest;
-      &tm-attrib.general;
-    </legalnotice>
-
-    <releaseinfo>$FreeBSD$</releaseinfo>
-
-    <abstract>
-      <para>Ez a leírás azt tárgyalja, miképpen
-	lehet a &os;-t olyan más népszerû
-	operációs rendszerek, mint mondjuk a &linux; &ms-dos;,
-	&os2; és &windows;&nbsp;95 mellé telepíteni
-	és használni.  Külön köszönet:
-	Annelise Anderson <email>andrsn@stanford.edu</email>,
-	Randall Hopper <email>rhh@ct.picker.com</email> és
-	&a.jkh;.</para>
-
-      <para><emphasis>Fordította: Páli Gábor,
-	utolsó ellenõrzés:
-	2010.11.28.</emphasis></para>
-    </abstract>
-  </articleinfo>
-
-  <sect1>
-    <title>Áttekintés</title>
-
-    <para>A legtöbben nem tudják az említett
-      operációs rendszereket kényelmesen egymás
-      mellé rakni egy kisebb méretû merevlemezen,
-      ezért a nagyobb EIDE-meghajtókkal kapcsolatos
-      ismeretekrõl is szó fog esni.  Mivel rengeteg
-      kombinációja létezik a különféle
-      operációs rendszereknek és merevlemezeknek,
-      valószínûleg az <xref linkend="ch5"/> fog a
-      leírás leghasznosabb részének bizonyulni.
-      Itt találhatóak meg ugyanis azok a speciális
-      beállítási sémák, amelyek több
-      operációs rendszer használata esetén
-      alkalmazhatóak.</para>
-
-    <para>Ez a cikk feltételezi, hogy a merevlemezünkön
-      már elõkészítettünk kellõ
-      mennyiségû szabad helyet az újabb
-      operációs rendszer(ek) számára.  Minden egyes
-      alkalommal, amikor újra felosztjuk a merevlemezünket,
-      egyúttal kockára tesszük a meglevõ
-      partícióinkon levõ adataink
-      épségét is. Viszont ha a merevlemezünkön
-      teljes egészében csak a DOS található, akkor
-      a FIPS nevû segédprogramot hasznosnak fogjuk találni
-      (megtalálható a &os; CDROM-on, a
-      <filename class="directory">\TOOLS</filename> alkönyvtárban,
-      vagy <ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/tools/">FTP-n</ulink>.
-      Segítségével anélkül tudjuk
-      partícionálni a merevlemezünket,
-      hogy kockára tennénk a rajta levõ adatainkat
-      biztonságát.  Valamint létezik még egy
-      <application>&partitionmagic;</application> nevû kereskedelmi
-      alkalmazás is, amellyel minden komoly következmény
-      nélkül tudunk partíciókat
-      átméretezni és törölni.</para>
-  </sect1>
-
-  <sect1 id="ch2">
-    <title>A boot managerek áttekintése</title>
-
-    <para>Csak röviden bemutatnánk néhány elterjedt
-      boot managert.  Közülük, a
-      számítógépünk
-      kiépítésétõl függõen, egyet
-      vagy többet jó eséllyel tudunk majd
-      használni.</para>
-
-    <variablelist>
-      <varlistentry>
-	<term>Boot Easy</term>
-	<listitem>
-	  <para> Ez a &os; alapértelmezett boot managere.  Szinte
-	    bármilyen rendszert képes indítani,
-	    többek közt a BSD, &os2; (HPFS), &windows;&nbsp;95 (FAT
-	    és FAT32) és &linux; típusú
-	    rendszereket.  Az indítandó partíciót a
-	    funkcióbillentyûkkel választhatjuk ki.</para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-	<term>&os2; Boot Manager</term>
-	<listitem>
-	  <para> Elindítja a FAT, FAT32, HPFS, FFS (&os;) és EXT2
-	    (&linux;) partíciókat, amelyet a nyilakkal
-	    választhatunk ki. Az &os2; Boot Manager az egyetlen az itt
-	    felsoroltak közül, amely a saját
-	    partícióját használja, miközben az
-	    összes többi a Master Boot Record (MBR)-ot.  Ennek
-	    következtében az 1024. cilinder elé kell
-	    telepítenünk, hogy elkerüljük az ezzel
-	    kapcsolatos esetleges indítási
-	    problémákat.  LILO-val telepített &linux;-ot
-	    csak akkor képes indítani, amikor az a boot
-	    szektorban található, nem pedig az MBR-ben.  Az
-	    Interneten található <ulink
-	      url="http://www.linuxresources.com/LDP/HOWTO/HOWTO-INDEX.html">&linux; hogyanok</ulink>
-	    között további információkat
-	    találhatunk az &os2; boot manager és a &linux;
-	    kapcsolatáról.</para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-	<term>OS-BS</term>
-	<listitem>
-	  <para>Ez egy másik boot manager a Boot Easy mellett.
-	    Valamivel több kontrollt ad a rendszerindítási
-	    folyamat felett, például
-	    beállítható benne az alapértelmezett
-	    indított partíció és egy
-	    várakozási idõ.  A program béta
-	    változatában már a nyilak
-	    segítségével lehet kiválasztani az
-	    indítandó operációs rendszert.
-	    Szintén megtalálható a &os; CD-jén
-	    a <filename class="directory">\TOOLS</filename>
-	    könyvtárban vagy <ulink
-	      url="ftp://ftp.FreeBSD.org/pub/FreeBSD/tools/">FTP-n</ulink>.</para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-	<term>LILO, avagy LInux LOader</term>
-	<listitem>
-	  <para>Ez egy korlátozott képességû boot
-	    manager.  Képes elindítani a &os;-t, habár
-	    ehhez szükség van némi finomhangolásra
-	    a hozzátartozó konfigurációs
-	    állományban.</para>
-	</listitem>
-      </varlistentry>
-    </variablelist>
-
-    <note id="fat32">
-      <title>Röviden FAT32-rõl</title>
-
-      <para>A FAT32 a FAT állományrendszer
-	kiváltására szolgál, amelyet a Microsoft
-	1996 végén, a &windows;&nbsp;95&nbsp;OSR2 béta
-	változatától kezdõdõen indított
-	útjának, ezzel lecserélve a &windows;&nbsp;95-tel
-	telepített számítógépek
-	alapértelmezett FAT típusú
-	állományrendszerét.  Úgy alakítja
-	át a megszokott FAT-ot, hogy lehetõvé teszi a
-	kisebb kiosztási egységek használatát
-	nagyobb merevlemezeken is.  Továbbá a FAT32-ben
-	megváltoztatták a hagyományos FAT boot
-	szektorát és kiosztási
-	táblázatát is,
-	összeférhetetlenné téve ezáltal
-	néhány boot managerrel.</para>
-    </note>
-  </sect1>
-
-  <sect1 id="ch3">
-    <title>Egy átlagos telepítés</title>
-
-    <para>Tegyük fel, hogy van két nagyobb EIDE merevlemezünk
-      és szeretnénk rájuk &os;-t, &linux;-ot és
-      &windows;&nbsp;95-öt telepíteni.</para>
-
-    <para>Íme, hogyan tennénk mindezt az alábbi
-      merevlemezekkel:</para>
-
-    <itemizedlist>
-      <listitem>
-	<para><filename>/dev/wd0</filename> (az elsõ fizikai lemez)</para>
-      </listitem>
-
-      <listitem>
-	<para><filename>/dev/wd1</filename> (második fizikai
-	  lemez)</para>
-      </listitem>
-    </itemizedlist>
-
-    <para>Mindkét lemeznek 1416 cilindere van.</para>
-
-    <procedure>
-      <step><para>Elsõként indítsunk az &ms-dos; vagy
-	&windows;&nbsp;95 rendszerindító lemezével,
-	amelyen az <filename>FDISK.EXE</filename> segédprogram
-	található.  Ennek segítségével
-	készítünk egy kis, nagyjából
-	50&nbsp;MB méretû elsõdleges partíciót
-	(35-40-et a &windows;&nbsp;95-nek, meg hagyunk egy kis helyet
-	levegõzni is) az elsõ lemezen.  Ezen kívül
-	még készítsünk egy nagyobb
-	partíciót a második merevlemezen, ahol a
-	&windows;os alkalmazásaink és az adataink foglalnak
-	majd helyet.</para></step>
-
-      <step><para>Indítsuk újra a gépet és
-	telepítsük fel a &windows;&nbsp;95-öt a
-	<filename>C:</filename> partícióra (amit
-	egyébként könnyebb mondani, mint
-	megtenni).</para></step>
-
-      <step><para>Következõként a &linux;-ot
-	telepítsük fel.  Nem vagyok benne biztos, hogy ez mindegyik
-	&linux;-disztribúcióra igaz, de a <ulink
-	  url="http://www.slackware.com">Slackware</ulink> tartalmazza a LILO-t
-	(ld. <xref linkend="ch2"/>).  A &linux;-os <command>fdisk</command>
-	parancsával tovább partíciónálva
-	én a &linux;-ot az elsõ lemezre tenném
-	(nagyjából 300&nbsp;MB elegendõ egy
-	kövérebb rendszerpartíciónak és
-	némi lapozóállománynak).</para></step>
-
-      <step><para>Miután feltelepítettük a &linux;-ot
-	és éppen a LILO elhelyezése elõtt
-	állunk, <emphasis>mindenképpen</emphasis>
-	ellenõrizzük, hogy a &linux;-os
-	rendszerpartíció boot szektorába
-	telepítjük, nem pedig az MBR-be!</para></step>
-
-      <step><para>A fennmaradó hely mehet mind a &os;-nek.
-	Vigyázzunk, hogy a &os; rendszerslice-a ne kerüljön az
-	1024. cilinderen túlra.  (Az 1024. cilinder az
-	528.&nbsp;MB-nál található a most
-	feltételezett 720&nbsp;MB-os lemezükön.)  A merevlemez
-	többi részét (nagyjából 270&nbsp;MB)
-	az <filename class="directory">/usr</filename> és
-	<filename class="directory">/</filename> slice-okra is fel lehet
-	használni.  A második lemez fennmaradó
-	részén (aminek a mérete az 1.
-	lépésben kialakított, &windows;-os
-	alkalmazásoknak és adatoknak szánt
-	partíció méretétõl függ)
-	még elfér a
-	<filename class="directory">/usr/src</filename> slice és
-	a lapozóállomány.</para></step>
-
-      <step><para>Ha most megnézzük a &windows;&nbsp;95
-	<command>fdisk</command> programjával, a merevlemezeket
-	valahogy így láthatjuk:
-
-	<screen>
----------------------------------------------------------------------
-
-                  Partíció információinak megjelenítése
-
-Aktuális merevlemezes meghajtó: 1
-
-Partíció  Állapot  Típus    Kötetcímke  Megabájt    Rendszer   Felhasznált
- C: 1        A    PRI DOS                   50       FAT**         7%
-    2        A    Non-DOS (Linux)          300                    43%
-
-
-
-Teljes lemezterület:  696 megabájt (1 megabájt = 1048576 bájt)
-
-
-
-
-
-
-
-
-A folytatáshoz nyomja meg az Esc billentyût.
----------------------------------------------------------------------
-
-                  Partíció információinak megjelenítése
-
-Aktuális merevlemezes meghajtó: 2
-
-Partíció  Állapot  Típus    Kötetcímke  Megabájt    Rendszer   Felhasznált
- D: 1        A    PRI DOS                  420       FAT**        60%
-
-
-
-
-Teljes lemezterület:  696 megabájt (1 megabájt = 1048576 bájt)
-
-
-
-
-
-
-
-
-
-A folytatáshoz nyomja meg az Esc billentyût.
----------------------------------------------------------------------
-	</screen>** Ez FAT16 vagy FAT32 lehet attól függõen,
-	  hogy OSR2-t használunk-e.  Lásd
-	  <xref linkend="ch2"/>.</para></step>
-
-      <step><para> Telepítsük fel a &os;-t. Mindenképpen
-	az elsõ merevlemezrõl indítsuk el a
-	számítógépet, ezért a BIOS-ban
-	állítsuk <quote>NORMAL</quote>-ra.  Ha nem az lenne,
-	adjuk meg a lemez valós geometriáját
-	indításkor (a lekérdezéséhez
-	indítsuk el &windows;&nbsp;95-öt, majd a Microsoft
-	Diagnostics-ot (<filename>MSD.EXE</filename>, esetleg
-	nézzük meg a BIOS-ban) a <literal>hd0=1416,16,63</literal>
-	paraméterrel, ahol a <replaceable>1416</replaceable> megadja a
-	merevlemez cilindereinek számát, a
-	<replaceable>16</replaceable> a fejek számát
-	sávonként, valamint a <replaceable>63</replaceable> a
-	szektorok számát sávonként.</para></step>
-
-      <step><para>A merevlemez partícionálása során
-	a Boot Easy-t mindenképpen az elsõ lemezre tegyük.
-	A második lemez miatt különösebben ne
-	aggódjunk, semmi bootolni való nincs rajta.</para></step>
-
-      <step><para>Újraindítás után a Boot Easy
-	várhatóan felismeri mind a három
-	indítható partíciót: DOS
-	(&windows;&nbsp;95), &linux; és BSD (&os;)
-	néven.</para></step>
-    </procedure>
-  </sect1>
-
-  <sect1 id="ch4">
-    <title>Különösen megfontolandók</title>
-
-    <para>A legtöbb operációs rendszer meglehetõsen
-      kényes abban a tekintetben, hogy hova helyezzük õket a
-      merevlemezen.  A &windows;&nbsp;95-öt és DOS-t az elsõ
-      merevlemez elsõ elsõdleges partíciójára
-      kell telepítenünk.  Az &os2; innen nézve
-      kívételnek számít, mivel egyaránt
-      telepíthetõ az elsõ vagy a második merevlemezre
-      is, tetszõleges elsõdleges vagy kiterjesztett
-      partícióra.  Ha nem vagyunk benne biztosak, az
-      indítható partíciókat tegyük mindig az
-      1024. cilinder elé.</para>
-
-    <para>Ha a &windows;&nbsp;95-öt egy már meglévõ BSD
-      rendszer mellé telepítjük, <quote>tönkre fogja
-	tenni</quote> az MBR-t, és ezért újra kell
-      telepítenünk a korábbi boot managerünket.  A Boot
-      Easy-t a &os; telepítõ CDROM-jának
-      <filename class="directory">\TOOLS</filename>
-      könyvtárában található, vagy az  <ulink
-	url="ftp://ftp.FreeBSD.org/pub/FreeBSD/tools/">FTP-n</ulink>
-      letölthetõ <filename>BOOTINST.EXE</filename>
-      segítségével tudjuk visszarakni.  Másik
-      lehetõség gyanánt elindíthatjuk a
-      telepítõt is, és megkereshetjük benne a
-      partíciószerkesztõt.  Itt jelöljük meg
-      &os;-t tartalmazó partíciót
-      indíthatónak (<emphasis>bootable</emphasis>), majd
-      válasszuk a Boot Managert és nyomjuk le a W-t (mint
-      (W)rite out) a boot manager tényleges MBR-be
-      írásához.  Most már
-      újraindíthatjuk a számítógépet
-      és a Boot Easy pedig felismeri a &windows;&nbsp;95-öt mint
-      DOS.</para>
-
-    <para>Nem szabad elfelejtenünk, hogy az &os2; ugyan képes FAT
-      és HPFS partíciókat olvasni, viszont FFS-t (&os;)
-      és EXT2-t (&linux;) nem!  Ehhez hasonlóan a
-      &windows;&nbsp;95 csak FAT és FAT32 partícókat (ld.
-      <xref linkend="ch2"/>) tud írni és olvasni.  A &os; ismeri a
-      legtöbb állományrendszert, de jelenleg nem tud HPFS
-      partíciókat olvasni.  A &linux; képes HPFS
-      partíciókat olvasni, de nem tudja írni õket.  A
-      &linux; kernel legújabb (2.x-es) változatai már
-      képesek írni és olvasni a &windows;&nbsp;95 VFAT
-      partícióit (a VFAT az, aminek a
-      segítségével a &windows;&nbsp;95 képes
-      hosszú állományneveket kezelni &mdash;
-      egyébként teljesen olyan, mint a FAT). A &linux;
-      tehát képes írni és olvasni a legtöbb
-      állományrendszert.  Érthetõ?
-      Remélem!</para>
-  </sect1>
-
-  <sect1 id="ch5">
-    <title>Példák</title>
-
-    <para><emphasis>(ennek a szakasznak szüksége van még
-      némi átdolgozásra, várjuk
-      a hozzászólásokat a témában a
-      <email>jayrich@sysc.com</email> címre)</emphasis>.</para>
-
-    <para>&os; + &windows;&nbsp;95: Ha a &os;-t a &windows;&nbsp;95 után
-      telepítettük, akkor a &windows;&nbsp;95-öt a Boot Easy
-      menüjében <literal>DOS</literal>-ként kell
-      látnunk.  Ha viszont a &windows;&nbsp;95-öt a &os;
-      után telepítettük, olvassuk el a fenti <xref
-	linkend="ch4"/>t.  Amíg nincsenek olyan merevlemezeink, amelyek
-      mérete meghaladná az 1024 cilindert, nem kell
-      különösebben aggódnunk a bootolás miatt.
-      Amikor azonban valamelyik partíciónk az 1024. cilinder
-      fölé merészkedik és DOS (vagy
-      &windows;&nbsp;95) alatt olyan hibaüzeneteket kapunk, mint mondjuk a
-      <errorname>Rossz rendszerlemez</errorname>, valamint a
-      &os; sem képes elindulni, keressünk meg a BIOS-unk
-      beállításai között <quote>&gt; 1024
-      cylinder support</quote>-ot (1024-nél több cilinder
-      támogatása) vagy a <quote>NORMAL/LBA</quote> nevezetû
-      módot.  A DOS-nak ebben az esetben ugyanis szüksége
-      lehet az LBA (Logical Block Addressing) bekapcsolására a
-      bootoláshoz.  Ha nem akarjunk minden egyes
-      rendszerindításkor eljátszani ezt, a CD-n
-      található <filename>FBSDBOOT.EXE</filename>
-      segítségével akár a DOS-on keresztül is
-      el tudjuk indítani a &os;-t. (Ez ugyanis megkeresi a &os;-s
-      partíciót és elindítja azt).</para>
-
-    <para>&os; + &os2; + &windows;&nbsp;95: Nincs új a nap alatt.  Az
-      &os2; boot managere képes elindítani mindezen
-      operációs rendszereket, ez a kombináció
-      tehát nem okozhat problémát.</para>
-
-    <para>&os; + &linux;: A Boot Easy segítségével mind a
-      két rendszer elindítható.</para>
-
-    <para>&os; + &linux; + &windows;&nbsp;95: (ld. <xref linkend="ch3"/>)</para>
-  </sect1>
-
-  <sect1 id="sources">
-    <title>Egyéb hasznos helyek</title>
-
-    <para>Számtalan <ulink
-	url="http://www.linuxresources.com/LDP/HOWTO/HOWTO-INDEX.html">&linux;
-	hogyan</ulink> foglalkozik az egy merevlemezre telepíthetõ
-      operációs rendszerek
-      problémájával.</para>
-
-    <para>A <ulink
-	url="http://www.linuxresources.com/LDP/HOWTO/mini/Linux+DOS+Win95+OS2.html">&linux;+DOS+Win95+OS2
-	mini-hogyan</ulink> az &os2; boot managerével kapcsolatosan
-      nyújt némi segítséget, valamint a <ulink
-	url="http://www.linuxresources.com/LDP/HOWTO/mini/Linux+FreeBSD.html">&linux;+&os;
-	mini-hogyan</ulink> is érdekes olvasmány lehet.  A <ulink
-	url="http://www.in.net/~jkatz/win95/Linux-HOWTO.html">&linux;-hogyan</ulink>
-       is fontos információkat tartalmazhat.</para>
-
-    <para>A <ulink
-	url="http://www.tburke.net/info/ntldr/ntldr_hacking_guide.htm">&windowsnt;
-	Loader Hacking Guide</ulink>-ban sok érdekesség
-      megtalálható a &windowsnt;, &windows;&nbsp;95 és DOS
-      más operációs rendszerekkel együtt
-      történõ használatáról.</para>
-
-    <para>Hale Landis <quote>Hogyan is mûködik?</quote> c.
-      leírása is rengeteg hasznos apróságot
-      árul el a különfél lemez
-      geometriákról és a rendszerindítással
-      kapcsolatos egyéb tudnivalókról.  Ezt
-      <ulink url="ftp://fission.dt.wdc.com/pub/otherdocs/pc_systems/how_it_works/allhiw.zip">itt</ulink>
-      találhatjuk meg.</para>
-
-    <para>Végezetül, erõsen javallott tüzetesen
-      átnézni a &os; rendszermag
-      rendszerindításáról szóló
-      dokumentációját is, amely megtalálható
-      a rendszermag forrásában (alapértelmezés
-      szerint a <ulink
-	url="file://localhost/usr/src/sys/i386/boot/biosboot/README.386BSD">/usr/src/sys/i386/boot/biosboot/README.386BSD</ulink>
-      helyre kerül).</para>
-  </sect1>
-
-  <sect1>
-    <title>Technikai részletek</title>
-
-    <para><emphasis>(Köszönet érte Randall Hoppernek
-      <email>rhh@ct.picker.com</email>)</emphasis></para>
-
-    <para>Ebben a szakaszban megpróbálunk kellõ
-      mennyiségû alapvetõ ismeretet átadni a
-      használatban levõ merevlemezekrõl, valamint ezen lemezek
-      rendszerindítási folyamatáról, elegendõt
-      ahhoz, hogy le tudjuk küzdeni azokat a leggyakoribb
-      problémákat, amelyek több operációs
-      rendszer indítása során leselkednek ránk.
-      Teljesen a kezdetektõl indul, ezért javasolt egészen
-      addig a pontig ugrani az olvasásban, ahol már ismeretlen
-      dolgok is kezdenek feltûnni.</para>
-
-    <sect2>
-      <title>Amit tudni érdemes a lemezekrõl</title>
-
-      <para>Három alapvetõ jellemzõ írja le a
-	merevlemezen található adatok pontos helyét:
-	cilinder, fej, szektor.  Igazából nem teljesen
-	lényeges tudni, hogy ezek milyen viszonyban is állnak
-	egymással, kivéve annyit, hogy ezek együttesen
-	azonosítják be fizikailag a lemezen
-	található adatokat.</para>
-
-      <para>Egy merevlemeznek van adott számú cilindere, feje
-	és szektora az egyes cilinder-fej párosok mentén
-	(amelyet egyébként sávnak is neveznek).  Ezek az
-	információk adják meg együttesen a merevlemez
-	<quote>fizikai geometriáját</quote>.
-	Általában 512 byte található
-	szektoronként valamint 63 szektor fejenként, azonban a
-	cilinderek és a fejek száma jelentõsen
-	változik lemezenként.  Ezért a merevlemezen
-	maximálisan tárolható adatok
-	mennyiségét a következõképpen lehet
-	kiszámítani ezek ismeretében:</para>
-
-      <informalexample><para>(a cilinderek száma) &times; (a fejek
-	száma) &times; (63 szektor/sáv) &times; (512
-	byte/szektor)</para></informalexample>
-
-      <para>Például, ez egy 1,6 gigabyte-os Western Digial
-	AC31600 EIDA merevlemez esetén:</para>
-
-      <informalexample><para>(3148 cilinder) &times; (16 fej) &times;
-	(63 szektor/sáv) &times; (512
-	byte/szektor)</para></informalexample>
-
-      <para>amely 1 624 670 208 byte-nak felel meg, ami pedig
-	nagyjából 1,6 gigabyte.</para>
-
-      <para>Az egyes merevlemezek fizikai geometriáját (a
-	cilinderek, fejek és a sávonkénti szektorok
-	számát) az ATAID és az Interneten
-	megtalálható egyéb hasonló programokkal
-	lehet lekérdezni.  De valószínûleg
-	magán a merevlemezen is megtalálható ez az adat.
-	Azonban nem árt óvatosnak lennünk: ha a BIOS-ban
-	LBA-t állítottunk be (ld. <xref linkend="limits"/>),
-	az említett programok egyikét sem tudjuk
-	használni.  Ezért sem képes sok más program
-	(pl. az <filename>MSD.EXE</filename> vagy a &os; fdisk)
-	megállapítani a fizikai lemez geometriát; helyette
-	az <firstterm>átértelmezett geometriát</firstterm>
-	(a LBA-ból származó virtuális
-	azámadatokat) adják vissza.  Errõl még
-	beszélni fogunk.</para>
-
-      <para>Még egy apróság ezzel kapcsolatban.  A 3
-	szám &mdash; nevezetesen a cilinderek, a fejek és a
-	szektorok sávonkénti száma &mdash;
-	ismeretében képesek vagyunk betájolni egy
-	konkrét abszolút szektort (vagyis egy 512 byte-os
-	adatblokkot) a lemezünkön.  A cilindereket és fejeket
-	0-tól, míg a szektorokat 1-tõl szokták
-	számozni.</para>
-
-      <para>Azok számára, akik még jobban el akarnak
-	mélyedni a technikai részletekben, a lemezek
-	geometriájában, a boot szektorok és BIOS-ok stb.
-	titkaiban, mindent megtalálhatnak róluk az Interneten.
-	Keressenek rá bátran a Lycos, Yahoo stb.
-	szolgáltatásokban a <literal>boot sector</literal> vagy
-	<literal>master boot record</literal> szavakra.  A sok hasznos ismeret
-	között esetleg találkozni fogunk Hale Landis
-	<citetitle>Hogyan is mûködik?</citetitle> c.
-	leírásgyûjteményével is.  Ezzel
-	kapcsolatban ld. a <xref linkend="sources"/>t.</para>
-
-      <para>Rendben, ennyi elég is lesz a
-	terminológiáról. Beszéljük a
-	bootolásról!</para>
-    </sect2>
-
-    <sect2 id="booting">
-      <title>A rendszerindítás folyamata</title>
-
-      <para>A merevlemez elsõ szektorában (azaz a 0. cilinder, 0.
-	fej, 1. szektor) lakozik a Master Boot Record (MBR).  Ez tartalmazza
-	lényegében a teljes lemez térképét.
-	Legfeljebb 4 <firstterm>partíciót</firstterm>
-	képes tárolni, amelyek mindegyike a lemez egy-egy
-	folytonos darabkája.  A &os; ezeket a partíciókat
-	egyébként <firstterm>slice-oknak</firstterm> hívja
-	annak érdekében, hogy elkerülje a saját
-	partícióival történõ
-	összetévesztésüket, habár mi most nem
-	így fogunk tenni.  Minden egyes partícióra
-	telepíthetõ egy-egy operációs rendszer
-	is.</para>
-
-      <para>Az MBR-ben található összes
-	partíciós bejegyzésnek van egy ún.
-	<firstterm>partíció
-	  azonosítója</firstterm>, egy <firstterm>kezdõ
-	  cilinder/fej/szektor értéke</firstterm> és egy
-	<firstterm>befejezõ cilinder/fej/szektor
-	  értéke</firstterm>.  A partíció
-	azonosítója megadja, hogy az adott partíció
-	milyen típusú (milyen operációs rendszer
-	használja), a kezdõ/befejezõ értéke
-	pedig azt, hol található.  A <xref linkend="tbl-pid"/>ban
-	a teljesség igénye nélkül felsoroltunk
-	néhány ismertebb azonosítót.</para>
-
-      <table id="tbl-pid">
-	<title>Partíció azonosítók</title>
-
-	<tgroup cols="2">
-	  <thead>
-	    <row>
-	      <entry>Az. (hex)</entry>
-	      <entry>Leírás</entry>
-	    </row>
-	  </thead>
-
-	  <tbody>
-	    <row>
-	      <entry>01</entry>
-	      <entry>Elsõdleges DOS12 (12 bites FAT)</entry>
-	    </row>
-
-	    <row>
-	      <entry>04</entry>
-	      <entry>Elsõdleges DOS16 (16 bites FAT)</entry>
-	    </row>
-
-	    <row>
-	      <entry>05</entry>
-	      <entry>Kiterjesztett DOS</entry>
-	    </row>
-
-	    <row>
-	      <entry>06</entry>
-	      <entry>Elsõdleges nagy DOS (&gt; 32MB)</entry>
-	    </row>
-
-	    <row>
-	      <entry>0A</entry>
-	      <entry>&os2;</entry>
-	    </row>
-
-	    <row>
-	      <entry>83</entry>
-	      <entry>&linux; (EXT2FS)</entry>
-	    </row>
-
-	    <row>
-	      <entry>A5</entry>
-	      <entry>&os;, NetBSD, 386BSD (UFS)</entry>
-	    </row>
-	  </tbody>
-	</tgroup>
-      </table>
-
-      <para>Megjegyezzük, hogy nem mindegyik partíció
-	indítható (ilyen pl. a kiterjesztett DOS).  Egyesek igen
-	&mdash; mások pedig nem.  Amitõl egy partíció
-	bootolhatóvá válik, az a
-	<firstterm>partíció boot szektora</firstterm>, amely az
-	egyes partíciók elején
-	található.</para>
-
-      <para>Amikor beállítjuk a kedvenc boot managerünket,
-	az tulajdonképpen átnézi az összes merevlemez
-	MBR-jeinek partíciós táblájában
-	található bejegyzéseket és
-	lehetõvé teszi számunkra, hogy elnevezgessük
-	õket.  Majd amikor elindítjuk a
-	számítógépet, a boot manager az
-	elsõként próbált merevlemez Master Boot
-	Recordjában elhelyezett speciális program
-	segítségével életre kel.  Felkeresi
-	a választásunknak megfelelõ partíciót
-	az MBR partíciós táblájában,
-	és felhasználva az így megismert kezdõ
-	cilinder/fej/szektor adatokat, betölti az adott
-	partíció boot szektorát, majd átadja neki a
-	vezérlést.  A partíció boot szektora ezek
-	után már elegendõ információt
-	tartalmaz a rajta levõ operációs rendszer
-	indításához.</para>
-
-     <para>Egyetlen fontos tudnivalót nem említettünk meg
-	még: minden merevlemezen található MBR.  Azonban
-	ezek közül csak az tekinthetõ fontosnak, amely a BIOS
-	által elsõként próbált lemezen
-	található.  Ha csak IDE csatolós merevlemezeink
-	vannak, ez általában az elsõ IDE lemez (pl. az
-	elsõdleges lemez az elsõ vezérlõn).  Ugyanez a
-	helyzet a csak SCSI-t tartalmazó rendszerekben.  Ha viszont van
-	IDE és SCSI merevlemezünk is, a BIOS
-	általában az IDE lemezeket próbálja
-	elõször elindítani, így az elsõként
-	elindított lemez az elsõ IDE lemez.  A boot managert
-	tehát az elsõként elinduló merevlemez
-	MBR-jébe kell elhelyeznünk a fentiekben leírtak
-	szerint.</para>
-    </sect2>
-
-    <sect2 id="limits">
-      <title>A rendszerindítás korlátai és
-	veszélyei</title>
-
-      <para>Most pedig következzen mindaz, amire nagyon oda kell
-	figyelnünk.</para>
-
-      <sect3>
-	<title>A rettegett 1024 cilinderes korlát és hogyan
-	  segít ezen az LBA</title>
-
-	<para>A bootolás folyamatának elsõ
-	  része a BIOS-on keresztül megy végbe (ha
-	  még nem ismernénk: a BIOS az az alaplapon
-	  található chip, amely a
-	  számítógép
-	  indításához nélkülözhetetlen
-	  rutinokat tárolja).  Mint olyan, a folyamat elsõ
-	  része tehát a BIOS interfészének
-	  korlátozásaitól függ.</para>
-
-	<para>Ezen idõtartam alatt a BIOS által nyújtott
-	  interfészt használjuk a merevlemez
-	  olvasására (13H megszakítás, 2-es
-	  funkció), amely 10 bitet használ a cilinderek, 8 bitet
-	  a fejek és 6 bitet a szektorok
-	  számozására.  Ezzel lekorlátozza
-	  használóját (tehát az MBR-bõl
-	  induló boot managereket és a boot szektorokban
-	  található betöltõket) az
-	  alábbiakra:</para>
-
-	<itemizedlist>
-	  <listitem>
-	    <para>legfejlebb 1024 cilinderre</para>
-	  </listitem>
-
-	  <listitem>
-	    <para>legfejlebb 256 fejre</para>
-	  </listitem>
-
-	  <listitem>
-	    <para>legfejlebb 64 szektorra sávonként (ami
-	      ténylegesen 63, mivel a <literal>0.</literal>
-	      nem használható)</para>
-	  </listitem>
-        </itemizedlist>
-
-	<para>Mostanában azonban a nagyobb merevlemezeknek tengernyi
-	  cilinderük van, de nem túl sok fejük, ezért
-	  ezek a lemezek szinte kivétel nélkül
-	  átlépik az 1024 cilinderes határt.  Ha
-	  vesszük ezt a tényt és összevetjük a
-	  BIOS által kínált interfésszel,
-	  rájöhetünk, hogy nem bootolhatunk akárhonnan
-	  a lemezrõl.  A rendszerindító kódnak
-	  (tehát a boot managernek és az összes
-	  indítható partícióban
-	  található betöltõnek) az 1024. cilinder alatt
-	  kell lennie.  Tényekre fordítva a szót, ha van
-	  egy átlagos merevlemezünk, aminek 16 feje van, ez
-	  nagyjából:</para>
-
-	<informalexample><para>1024 cilinder/lemez &times; 16 fej/lemez
-	  &times; 63 szektor/(cilinder - fej) &times; 512
-	  byte/szektor,</para></informalexample>
-
-	<para>ami megfelel a sokszor emlegetett 528 MB-os
-	  határnak.</para>
-
-	<para>Itt jön a képbe a BIOS LBA (Logical Block
-	  Addressing).  Ennek segítségével ugyanis a
-	  BIOS-hívások használója képes
-	  hozzáférni az 1024. feletti fizikai cilinderekhez is a
-	  BIOS-on keresztül, méghozzá a cilinderek
-	  átdefiniálásával.  Vagyis
-	  újraértelmezi a cilinderek és a fejek
-	  számát, és ezzel olyan képzetet ad,
-	  mintha a merevlemeznek kevesebb cilindere de több feje lenne,
-	  mint a valóságban.  Másképp fogalmazva,
-	  kihasználja azt a helyzetet, hogy a modern merevlemezekben
-	  viszonylag kevés fej és sok cilinder
-	  található, ezért eltolja a kettõ
-	  között nyugvó osztást, aminek
-	  köszönhetõen mind a két érték az
-	  imént említett határok (1024 cilinder, 256 fej)
-	  alatt tud maradni.</para>
-
-	<para>A BIOS LBA használatával a merevlemezek ezen
-	  korlátozása virtuálisan el is tûnik (nos,
-	  valójában csak 8 gigabyte-nyival arrébb
-	  kerül).  Ha LBA-t támogató BIOS-unk van, akkor a
-	  &os;-t és minden más operációs
-	  rendszert bárhova pakolhatunk, hiszen így nem fogunk az
-	  1024 cilinderes korlátba ütközni.</para>
-
-	<para>Az elõbb példaként felhozott 1,6 gigabyte-os
-	  Western Digital esetén tehát a fizikai
-	  geometria:</para>
-
-	<informalexample><para>(3148 cilinder, 16 fej, 63 szektor/sáv,
-	  512 byte/szektor)</para></informalexample>
-
-	<para>Azonban a BIOS LBA ezt így fordítja
-	  át:</para>
-
-	<informalexample><para>(787 cilinder, 64 fej, 63 szektor/sáv,
-	  512 byte/szektor),</para></informalexample>
-
-	<para>ami ugyanazt a tényleges lemezméretet
-	  eredményezi, azonban a cilinder- és fejadatok a
-	  BIOS-hívások által kezelhetõ
-	  tartományba esnek.  (Mellékesen megjegyzem, hogy nekem
-	  pont egy &linux; és egy &os; partícióm van az
-	  egyik merevlemezemen, éppen az 1024. cilinder felett,
-	  és mind a kettõ remekül bootol, hála az
-	  LBA-nak).</para>
-      </sect3>
-
-      <sect3>
-	<title>Boot managerek és a lemez kiosztása</title>
-
-	<para> Egy másik fontos dolog, amire figyelnünk kell a boot
-	  managerek telepítése során, az éppen a
-	  boot managernek foglalt hely a lemezen.  A legjobb erre már
-	  elõre gondolni, és ezzel elkerüljük egy vagy
-	  több operációs rendszerünk
-	  újratelepítését.</para>
-
-	<para>Ha nyomonkövettük a Master Boot Recordról (avagy
-	  hol is található az MBR), a partíciók
-	  boot szektoráról és a
-	  rendszerindítási folyamatról szóló
-	  <xref linkend="booting"/>t, felmerülhet bennünk a
-	  kérdés, hogy a merevlemezükön hova is fog
-	  kerülni maga a boot manager.  Nos, egyes boot managerek
-	  kellõen kis méretûek ahhoz, hogy teljes
-	  egészében elférjenek a Master Boot Recordban
-	  (0. cilinder, 0. fej, 1. szektor), a partíciós
-	  tábla mellett.  Másoknak ellenben valamivel több
-	  helyre van szüksége és tulajdonképpen a 0.
-	  cilinder 0. fejének sávjában nyúlnak
-	  túl az MBR-en néhány szektornyival, mivel azok
-	  általában szabadon maradnak&hellip;
-	  általában.</para>
-
-	<para>És itt jön a csel! Egyes operációs
-	  rendszerek (köztük a &os; is) megengedik, hogy a
-	  partíciójuk akár közvetlenül a Master
-	  Boot Record után kezdõdjön a 0. cilinder 0.
-	  fejének 2. szektorában. Tulajdonképpen, ha
-	  a &os; telepítõjének egy olyan lemezt adunk meg,
-	  amelynek az eleje vagy a teljes egésze
-	  éppenséggel üres, a &os;
-	  partícióját alapértelmezés szerint
-	  közvetlenül ide rakja (legalább is így tette,
-	  amikor megpróbáltam telepíteni).  Ezután
-	  szépen felrakjuk a boot managert, és ha az
-	  éppenséggel hajlamos elfoglalni az MBR után
-	  következõ néhány szektort, akkor ezzel
-	  együtt felül is írja az elsõ
-	  partíció adatait.  A &os; esetében így
-	  felülírja a lemezcímkét, amitõl a &os;
-	  partíció ezáltal bootolhatatlanná
-	  válik.</para>
-
-	<para>Ha egyszerûen el akarjuk kerülni ezt a
-	  problémát (és megadni az esélyt
-	  más, kevésbé rugalmas boot managerek
-	  számára), akkor hagyjuk szabadon a lemezen
-	  található elsõ sávot.  Vagyis ne
-	  tegyünk semmilyen partíciót a 0. cilinder, 0. fej,
-	  2. szektorától kezdõdõen egészen a 0.
-	  cilinder, 0. fej 63. szektoráig, hanem helyezzük azt a
-	  0. cilinder 1. fejének 1. szektorára.  Ugyan nem
-	  mernék rá megesküdni, de ha létrehozunk egy
-	  DOS partíciót a lemez elején, a DOS
-	  alapértelmezés szerint ezt a területet szabadon
-	  hagyja (ezért is gondolja úgy néhány boot
-	  manager, hogy szabad).  Ezt inkább magam szeretem
-	  csinálni, ezért létrehozok egy 1 megás
-	  DOS partíciót a lemez elején, mivel ezzel
-	  ráadásul meg tudom akadályozni, hogy
-	  elsõleges DOS meghajtónevek felcserélõdjenek
-	  egy újrapartícionálást
-	  követõen.</para>
-
-	<para>Hivatkozásképpen, a következõ boot
-	  managerek használják a Master Boot Recordot az adataik
-	  és kódjuk tárolására:</para>
-
-	<itemizedlist>
-	  <listitem>
-	    <para>OS-BS 1.35</para>
-	  </listitem>
-
-	  <listitem>
-	    <para>Boot Easy</para>
-	  </listitem>
-
-	  <listitem>
-	    <para>LILO</para>
-	  </listitem>
-	</itemizedlist>
-
-	<para>Ezek a boot managerek használnak további
-	  szektorokat a Master Boot Record után:</para>
-
-	<itemizedlist>
-	  <listitem>
-	    <para>OS-BS 2.0 Beta 8 (2-5. szektorok)</para>
-	  </listitem>
-
-	  <listitem>
-	    <para>Az  &os2; boot managere</para>
-	  </listitem>
-	</itemizedlist>
-      </sect3>
-
-      <sect3>
-	<title>Mit tegyünk, ha nem indul el a rendszer a
-	  számítógépünkön?</title>
-
-	<para>Egyes esetekben elõfordulhat, hogy a boot managerek
-	  telepítése során az MBR-t olyan állapotba
-	  sikerül hozni, ahonnan a
-	  számítógépünk nem képes
-	  elindulni.  Ugyan nem valószínû, de
-	  megtörténhet, amikor ismételten használjuk
-	  az FDISK-et egy már meglevõ boot manager alatt.</para>
-
-	<para>Ha van a lemezen egy bootolható DOS
-	  partíció, akkor indítsuk el azt egy
-	  DOS-os rendszerlemezrõl, és írjuk be:</para>
-
-	<informalexample>
-	  <screen>A:\> <userinput>FDISK /MBR</userinput></screen>
-	</informalexample>
-
-	<para>Ennek segítségével vissza tudunk rakni egy
-	  egyszerû DOS rendszerbetöltõ kódot az MBR-be,
-	  ami után be tudjuk tölteni a DOS-t (de csak a DOS-t)
-	  a merevlemezrõl.  Másik megoldás lehet, hogy
-	  simán újra felrakjuk a boot managerünket egy
-	  rendszerindító lemezrõl.</para>
-      </sect3>
-    </sect2>
-  </sect1>
-</article>
diff --git a/hu_HU.ISO8859-2/articles/version-guide/Makefile b/hu_HU.ISO8859-2/articles/version-guide/Makefile
deleted file mode 100644
index 510cfe66ea..0000000000
--- a/hu_HU.ISO8859-2/articles/version-guide/Makefile
+++ /dev/null
@@ -1,28 +0,0 @@
-# $FreeBSD$
-#
-# Article: FreeBSD Version Guide
-#
-# %SOURCE%    en_US.ISO8859-1/articles/version-guide/Makefile
-# %SRCID%     1.3
-#
-
-#
-# Tidy messes up iso-8859-2 characters
-#
-
-NO_TIDY= yes
-
-MAINTAINER= doc@FreeBSD.org
-
-DOC?= article
-
-FORMATS?= html
-INSTALL_COMPRESSED?= gz
-INSTALL_ONLY_COMPRESSED?=
-
-SRCS=	article.sgml
-
-URL_RELPREFIX?=	../../../..
-DOC_PREFIX?= ${.CURDIR}/../../..
-
-.include "${DOC_PREFIX}/share/mk/doc.project.mk"
diff --git a/hu_HU.ISO8859-2/articles/version-guide/article.sgml b/hu_HU.ISO8859-2/articles/version-guide/article.sgml
deleted file mode 100644
index 24d3373217..0000000000
--- a/hu_HU.ISO8859-2/articles/version-guide/article.sgml
+++ /dev/null
@@ -1,525 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-2" standalone="no"?>
-<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V4.2-Based Extension//EN"
-	"../../../share/sgml/freebsd42.dtd" [
-<!ENTITY % entities PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Entity Set//HU" "../../share/sgml/entities.ent">
-%entities;
-]>
-
-<!-- The FreeBSD Hungarian Documentation Project
-     Translated by: PALI, Gabor <pgj@FreeBSD.org>
-     %SOURCE%	en_US.ISO8859-1/articles/version-guide/article.sgml
-     %SRCID%	1.15
--->
-
-<article lang="hu">
-  <title>Válasszuk ki a nekünk igazán megfelelõ &os;
-    verziót!</title>
-
-  <articleinfo>
-    <authorgroup>
-      <author>
-	<surname>A &os; Dokumentációs Projekt</surname>
-      </author>
-    </authorgroup>
-
-    <legalnotice id="trademarks" role="trademarks">
-      &tm-attrib.freebsd;
-    </legalnotice>
-
-    <copyright>
-      <year>2005</year>
-      <holder>A &os; Dokumentációs Projekt</holder>
-    </copyright>
-
-    <pubdate>$FreeBSD$</pubdate>
-
-    <releaseinfo>$FreeBSD$</releaseinfo>
-
-    <abstract>
-      <para>Ön a &os; telepítését választotta.
-	Üdvözöljük! Ezt a leírást annak
-	szellemében készítettük, hogy
-	segítsünk eligazodni a telepíthetõ
-	verziók között.</para>
-
-      <para><emphasis>Fordította: Páli Gábor,
-	utolsó ellenõrzés:
-	2010.11.28.</emphasis></para>
-    </abstract>
-  </articleinfo>
-
-  <sect1 id="background">
-    <title>Háttér</title>
-
-    <para>A leginkább megfelelõ verzió
-      kiválasztásához fontos megértenünk
-      néhány alapvetõ fogalmat a &os; fejlesztési
-      modelljével és az ún.
-      Release Engineering (<literal>RE</literal>,
-      <quote>kiadásépítés</quote>)
-      folyamatával kapcsolatosan.</para>
-
-    <para>A &os;-t nagyrészt független önkéntesek
-      hatalmas csoportja fejleszti.  A rendszermag, a legalapvetõbb
-      függvénykönyvtárak, valamint a hozzájuk
-      tartozó segédprogramok forrásait egy
-      <firstterm>verziókövetõ rendszerben</firstterm>
-      tárolják, amely bárki által és
-      bármikor tetszõlegesen letölthetõ.  Ettõl
-      függetlenül ezek lefordított változatai
-      (<literal>binárisai</literal>) is rendszeresen
-      elérhetõek.  Néhány ilyen binárist
-      alapos és széleskörû tesztelési
-      folyamatnak vetnek alá, majd
-      <firstterm>kiadásnak</firstterm> címkézik fel
-      õket.</para>
-
-    <sect2 id="releases">
-      <title>Kiadások</title>
-
-      <para>A <literal>kiadások</literal> (release)
-	általában	rendelkeznek egy
-	<firstterm>fõverziószámmal</firstterm> és
-	egy <firstterm>alverziószámmal</firstterm>.</para>
-
-      <itemizedlist>
-	<listitem>
-	  <para>A fõverziószámok feladata, hogy jelezze az
-	    újabb, nagyobb változtatásokat a rendszerben.
-	    Ilyenkor természetesen elkerülhetetlen, hogy ennek
-	    következtében komolyabb átszervezéseken
-	    menjen át a &os;, vagy éppen a régebbi,
-	    már hasztalannak tekintett részei eltûnjenek.
-	    Emiatt gyakran még a korábbi fõbb
-	    kiadásokkal kapcsolatban is elveszhet bizonyos
-	    mértékû kompatibilitás.</para>
-	</listitem>
-
-	<listitem>
-	  <para>Az alverziószámok jelzik a
-	    megbízhatóságot és a
-	    teljesítményt érintõ kisebb
-	    hibajavításokat.  Ebben az esetben mind a
-	    forráskód-, mind pedig a bináris szintû
-	    kompatibilitás megtartása egyik elsõdleges
-	    feladatunk.  Alkalmanként az alverziókba is
-	    kerülhetnek újítások, de csak akkor, ha
-	    ezek nem fenyegetik a velük szemben kitûzött
-	    összes többi célt.</para>
-	</listitem>
-      </itemizedlist>
-
-      <para>Azonban sose szabad elfelejtenünk, hogy egy <quote>kiadott
-	verzió</quote> nem több, mint a forrásról egy
-	adott idõben és egy adott néven
-	(<emphasis>címkével</emphasis> ellátott)
-	készített pillanatfelvétel.
-	(Például az 5.4-es kiadáshoz a
-	kiadásépítõk a
-	<literal>RELENG_5_4_0_RELEASE</literal> címkét
-	tették.) A fejlesztés a <literal>HEAD</literal>
-	néven ismert címkével azonban mindig halad
-	tovább.</para>
-    </sect2>
-
-    <sect2 id="branches">
-      <title>Fejlesztési ágak</title>
-
-      <para>Minden kiadás alkalmával létrehoznak egy
-	<firstterm>fejlesztési ágat</firstterm>, mint mondjuk a
-	<literal>RELENG_5_4</literal>.  Habár a
-	<literal>RELENG_5_4_0_RELEASE</literal> címkével
-	ellátott források már nem fognak a
-	továbbiakban változni, a <literal>RELENG_5_4</literal>
-	címkével rendelkezõk ellenben még igen,
-	méghozzá a <literal>HEAD</literal> ágból
-	származó biztonsági vagy egyéb
-	javítások, esetleg kisebb változtatások
-	nyomán.</para>
-
-      <para>Egy-egy fõbb kiadáshoz még egy másik
-	címkét is létrehoznak, mint mondjuk a
-	<literal>RELENG_5</literal>.  A biztonsági és
-	egyéb javításokon túl más
-	módosítások is áthozhatóak a
-	<literal>HEAD</literal> ágból, így
-	tulajdonképpen ez lesz az aktív ág, amikor a
-	következõ kiadást készítik
-	elõ az adott vonalban.</para>
-    </sect2>
-
-    <sect2 id="stable-vs-current">
-      <title><firstterm>STABLE</firstterm> vagy
-	<firstterm>CURRENT</firstterm>?</title>
-
-      <para>Minden egyes nagyobb kiadás életciklusában
-	létrejön még egy további fejlesztési
-	ág, amelyet <literal>STABLE</literal>-nek
-	(megbízhatónak) neveznek.  Ezzel jelzi a &os; Projekt,
-	hogy véleménye szerint az adott ágban
-	szereplõ módosítások minõsége
-	elegendõ a szélesebb körû használathoz.
-	Azokat az ágakat pedig, amelyeknek további
-	tesztelésre van szükségük a komolyabb
-	használathoz, <literal>CURRENT</literal>-nek
-	(aktuálisnak) nevezik.</para>
-
-      <note><para>A &os; Projekt nem tudja garantálni, hogy
-	<emphasis>stable</emphasis>-ként szállított
-	szoftverek elegendõek egy telepítéshez.  Ezt
-	mindenkinek magának kell eldöntenie.  Nem szabad
-	elfelejteni, hogy ez a projekt elsõsorban
-	önkéntesekbõl áll és nem képes a
-	mûködésre semminemû szavatosságot
-	vállalni.</para></note>
-    </sect2>
-
-    <sect2 id="ports-vs-packages">
-      <title><firstterm>Portok</firstterm> vagy
-	<firstterm>csomagok</firstterm>?</title>
-
-      <para>Az említett állományokon kívül a
-	&os; még több ezernyi, külsõ fejlesztõk
-	által készített alkalmazásokat is
-	támogat.  (Ilyenek a különbözõ
-	ablakkezelõ rendszerek, böngészõk, levelezõ
-	kliensek, irodai programcsomagok, és így tovább.)
-	Általánosságban véve nem a projekt maga
-	fejleszti ezeket a szoftvereket, csupán egy keretrendszert
-	biztosít a telepítésükhöz (amelyet
-	<firstterm>Ports Collection</firstterm>-nek
-	(<quote>portgyûjtemények</quote>) neveznek).
-	Attól függõen, ahogy ezt a licenszelésük
-	megengedi, ezek az alkalmazások telepíthetõek
-	forrásból (ezeket nevezik
-	<emphasis>portoknak</emphasis>), vagy elõre lefordított
-	binárisokból (ezeket nevezik
-	<emphasis>csomagoknak</emphasis>).</para>
-    </sect2>
-  </sect1>
-
-  <sect1 id="past-schedules">
-    <title>Ahogy eddig ütemeztük a kiadásokat</title>
-
-    <para>A &os;&nbsp;5.X verziójának fejlesztése
-      és kiadása során sok-sok olyan tapasztalatot
-      szereztünk, amelyek csak utólag váltak
-      világossá számunkra.  Az 5.X-es vonal
-      célkitûzései meglehetõsen agresszívek
-      voltak és magukban foglalták a
-      következõket:</para>
-
-    <itemizedlist>
-      <listitem>
-	<para>Az SMP (Symmetric MultiProcessing) rendszerek
-	  támogatása</para>
-      </listitem>
-
-      <listitem>
-	<para>A teljesítmény növelése a kernelen
-	  belüli erõforrás-kiosztás egy új
-	  stratégia szerinti átdolgozásával</para>
-      </listitem>
-
-      <listitem>
-	<para>Számos új processzor architektúra
-	  támogatása</para>
-      </listitem>
-
-      <listitem>
-	<para>Egy új szálkezelési modell
-	  bevezetése</para>
-      </listitem>
-
-      <listitem>
-	<para>Egy új ütemezõ bevezetése</para>
-      </listitem>
-
-      <listitem>
-	<para>Új technológiák, mint például
-	  az energiagazdálkodás, támogatása
-	  (különösen laptopok esetén); és ami a
-	  legfontosabb:</para>
-      </listitem>
-
-      <listitem>
-	<para>Addig nem tekintjük ezt a vonalt
-	  <literal>STABLE</literal>-nek, amíg az imént felsorolt
-	  feladatok be nem fejezõdnek.</para>
-      </listitem>
-    </itemizedlist>
-
-    <para>Ez egy olyan helyzet kialakulásához vezetett, ahol
-      évek teltek el a 4.X vonal <literal>STABLE</literal> és az
-      5.X vonal <literal>STABLE</literal> kiadásai között.  Ez
-      magával hozott néhány tényleges
-      kellemetlenséget:</para>
-
-    <itemizedlist>
-      <listitem>
-	<para>Az egyszerre kivitelezendõ újításokhoz
-	  kapcsolódó módosítások nagy
-	  száma jelentõs mértékben
-	  megnehezítette az egyes módosítások
-	  elkülönítését és
-	  beolvasztását a <literal>STABLE</literal>
-	  ágba.</para>
-      </listitem>
-
-      <listitem>
-	<para>Ez pedig azt jelentette, hogy azok a felhasználók,
-	  akiknek igazán szüksége volt bizonyos
-	  újításokra (például, hogy
-	  képesek legyenek futattni a rendszer egy modern hardveren),
-	  kényszerûen átálltak (mondjuk) a
-	  &os;&nbsp;5.2.1-es verziójára, annak ellenére,
-	  hogy az kifejezetten egy fejlesztõi kiadás volt,
-	  és hogy <literal>CURRENT</literal> kiadás
-	  lévén nem felelt meg teljes egészében
-	  minden igényüknek.</para>
-      </listitem>
-
-      <listitem>
-	<para>A beolvasztások során a fejlesztõk néha
-	  olyan helyzetbe kerültek, ahol olyan verzión kellett az
-	  újításaikat támogatniuk, amelyeket nem
-	  elsõdleges fejlesztõi platformként
-	  használtak.</para>
-      </listitem>
-
-      <listitem>
-	<para>A késés továbbá azt jelentette, hogy
-	  mire az 5.3 végre <literal>STABLE</literal> szintû
-	  kiadássá válhatott, az idõközben
-	  felgyülemlett módosítások terhe
-	  kínszenvedéssé tette a frissítési
-	  folyamatot.</para>
-      </listitem>
-    </itemizedlist>
-
-    <para>Úgy szólván senki sem volt elégedett
-      ezzel az eredménnyel.</para>
-
-    <para>A következõket tanultuk mindezekbõl:</para>
-
-    <itemizedlist>
-      <listitem>
-	<para>A fõbb kiadásoknak kevesebb
-	  újítást kell tartalmazniuk és gyakrabban
-	  kell megjelenniük.</para>
-      </listitem>
-
-      <listitem>
-	<para>A lehetõ legjobban el kell szigetelni
-	  egymástól a különbözõ
-	  újításokhoz kapcsolódó
-	  módosításokat.  (Ez egyben arra is utal, hogy
-	  bizonyos fejlesztéseket nem az aktív forrásokon
-	  belül végezni, és majd csak akkor beolvasztani
-	  õket, ha már nem veszélyeztetik egyik
-	  párhuzamos fejlesztést sem.)</para>
-      </listitem>
-
-      <listitem>
-	<para>A fõbb kiadások határidejét
-	  inkább idõben kell megszabni, nem pedig az
-	  újítások mértékében.  Ha az
-	  egyes újítások nem készülnek el
-	  idõre, akkor ki kell õket kapcsolni és meghagyni egy
-	  késõbbi kiadásra.</para>
-      </listitem>
-    </itemizedlist>
-
-    <para>Kevesebb újítással és gyakoribb
-      megjelenéssel remélhetõleg csökkeni fog az egyes
-      módosítások beolvasztásához
-      szükséges idõ a <literal>HEAD</literal>
-      ágból a legfrissebb <literal>STABLE</literal> ágba
-      (és ezáltal nem csak egyetlen fejlesztési vonalban
-      maradnak támogathatók). Továbbá, mivel ezek
-      az módosítások kellõképpen elszigeltek
-      egymástól, az integrálás során
-      keletkezõ hibák kockázata is csökken.</para>
-
-    <para>Sõt, az idõben megkötött határidõknek
-      köszönhetõen végre könnyebben tervezhetnek
-      elõre a felhasználók, a külsõ
-      alkalmazások fejlesztõi és maguk a &os;
-      fejlesztõi is egyaránt.</para>
-  </sect1>
-
-  <sect1 id="future-goals">
-    <title>Ahogyan majd szeretnénk ütemezni a
-      kiadásokat</title>
-
-    <para>Íme a Projekt jelenlegi céljai az
-      ütemezésben:</para>
-
-    <itemizedlist>
-      <listitem>
-	<para>Minden 18 hónapban új fõbb kiadás
-	  megjelentetése;</para>
-      </listitem>
-
-      <listitem>
-	<para>Minden 4 hónapban új kisebb kiadás
-	  megjelentetése;</para>
-      </listitem>
-
-      <listitem>
-	<para>Minden fõbb kiadás legfrissebb
-	  kiadásához elõkészített csomagokat
-	  nyújtani;</para>
-      </listitem>
-
-      <listitem>
-	<para>Minden fõbb kiadás legutóbbi
-	  néhány kiadásához biztonsági
-	  frissítéseket és kritikus
-	  hibajavításokat (<firstterm>biztonsági
-	  fejlesztõi ágak</firstterm>) nyújtani;</para>
-      </listitem>
-    </itemizedlist>
-
-    <para>Tekintettel a telepíthetõ verziók
-      kombinációjának nagy számára, nem
-      lehet minden egyes verziót korlátlanul támogatni;
-      ezt részben a rendelkezésre álló gépi
-      erõforrások korlátozzák, de leginkább a
-      projektben résztvevõ önkéntesek által
-      nyújtott segítség mennyisége.</para>
-
-    <para>Az érdeklõdõk figyelmébe ajánljuk
-      továbbá:</para>
-
-    <variablelist>
-      <varlistentry>
-	<term>
-	  <ulink
-	    url="&url.base;/releng/index.html#schedule"></ulink></term>
-	<listitem>
-	  <para>The Release Engineering Schedule</para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-	<term>
-	  <ulink
-	    url="&url.base;/security/security.html#supported-branches"></ulink></term>
-	<listitem>
-	  <para>The Security Branch Schedule</para>
-	</listitem>
-      </varlistentry>
-    </variablelist>
-
-    <para>Az említett dokumentumok még nagyobb
-      mélységben részletezik a tárgyalt
-      hátteret, és feltárják azokat folyamatokat,
-      amelyek a támogatott fejlesztõi ágakat és azok
-      élettartalmát illetõ döntéseket
-      befolyásolják.</para>
-  </sect1>
-
-  <sect1 id="decision-points">
-    <title>Hogyan befolyásolják ezek a tényezõk
-      a döntésünket?</title>
-
-    <para>Az alábbi kérdések megválaszolása
-      határozhatja meg a döntést a megfelelõ
-      verzió kiválasztásában:</para>
-
-    <itemizedlist>
-      <listitem>
-	<para>Milyen mértékû
-	  megbízhatóságot várunk el a
-	  rendszertõl?</para>
-      </listitem>
-
-      <listitem>
-	<para>Mennyire vagyunk hajlandóak frissíteni a
-	  rendszerünket?</para>
-      </listitem>
-
-      <listitem>
-	<para>Mennyire gyakran szeretnénk frissíteni a
-	  rendszerünket?</para>
-      </listitem>
-
-      <listitem>
-	<para>Mennyire fontos számunkra a biztonság?</para>
-      </listitem>
-
-      <listitem>
-	<para>Forráskódból vagy bináris
-	  állományokból akarunk telepíteni?</para>
-      </listitem>
-
-      <listitem>
-	<para>Szeretnénk részt venni a &os;
-	  fejlesztésében?</para>
-      </listitem>
-    </itemizedlist>
-
-    <para>Néhány további vázlatos
-      útmutatás a döntéshez:</para>
-
-    <itemizedlist>
-      <listitem>
-	<para>Ha rövid idõn belül az elérhetõ
-	  legnagyobb mértékû
-	  megbízhatóságból szeretnénk
-	  profitálni, viszont nincs lehetõségünk
-	  frissíteni, akkor minden bizonnyal a legfrissebb
-	  <literal>STABLE</literal> jelzésû kiadást lenne
-	  hasznos feltelepítenünk és használnunk.
-	  Biztonsági igényeinknek megfelelõen érdemes
-	  követni az adott kiadáshoz megjelenõ
-	  javításokat.</para>
-      </listitem>
-
-      <listitem>
-	<para>Ha rövid idõn belül vagy
-	  szükségünk van a legfrissebb
-	  újításokra vagy pedig a biztonsági
-	  javításokra, valamint az idõt és
-	  erõforrást sem sajnáljuk a
-	  frissítésre, érdemes a legújabb
-	  <literal>STABLE</literal> ágat követnünk.</para>
-      </listitem>
-
-      <listitem>
-	<para>Ha nem kívánjuk közvetlenül
-	  élesben használni a rendszert és csak bizonyos
-	  problémák érdekelnek minket, valamint a
-	  következõ nagyobb kiadás néhány
-	  hónapon belül megjelenik, valószínûleg
-	  érdemes elgondolkodni annak az ágnak
-	  telepítésén, ezzel is segítve a projektet
-	  a kiadás tesztelésében,
-	  megbízhatóvá tételében és
-	  úgy egyáltalán jobbá tenni a
-	  hosszú távú használatra.</para>
-      </listitem>
-
-      <listitem>
-	<para>Ha csak forrásból szeretnénk
-	  telepíteni és hibákat keresni az
-	  alaprendszerben, vagy éppen utánajárni az ismert
-	  hibáknak, illetve nyomon követni õket az ezzel
-	  kapcsolatos levelezõlistán, érdemes a
-	  <literal>HEAD</literal> fejlesztési ágat
-	  használnunk.</para>
-      </listitem>
-    </itemizedlist>
-  </sect1>
-
-  <sect1 id="conclusion">
-    <title>Végszó</title>
-
-    <para>Reméljük, ez a leírás hasznos
-      kiindulásnak szolgált a &os; fejlesztési
-      modelljének megértésében és az
-      igényeinknek legjobban megfelelõ verzió
-      kiválasztásában!</para>
-  </sect1>
-</article>
diff --git a/hu_HU.ISO8859-2/books/faq/book.sgml b/hu_HU.ISO8859-2/books/faq/book.sgml
index b16fb555be..be83063cf4 100644
--- a/hu_HU.ISO8859-2/books/faq/book.sgml
+++ b/hu_HU.ISO8859-2/books/faq/book.sgml
@@ -1652,22 +1652,6 @@
       </qandaentry>
 
       <qandaentry>
-	<question id="multiboot">
-	  <para>A számítógépre lehet
-	    egynél több operációs rendszert is
-	    telepíteni?</para>
-	</question>
-
-	<answer>
-	  <para>Olvassuk el a <quote><ulink
-	    url="&url.articles.multi-os;/index.html">A &os;
-	    telepítése és használata
-	    más operációs rendszerekkel
-	    együtt</ulink></quote> címû cikket.</para>
-	</answer>
-      </qandaentry>
-
-      <qandaentry>
 	<question id="windows-coexist">
 	  <para>&windows; mellé is telepíhetõ
 	    &os;?</para>
@@ -6680,11 +6664,7 @@ kern.sched.name: 4BSD</screen>
 	    mind a két lemezre, így miután
 	    átmásoltuk a régi rendszerünket az
 	    új lemezre, ennek megtartásával ki
-	    tudjuk próbálni az új rendszert.  A
-	    <ulink
-	      url="&url.articles.formatting-media.en;/index.html">lemezek formázásáról szóló</ulink>
-	    cikkben olvashatunk ennek pontosabb
-	    részleteirõl.</para>
+	    tudjuk próbálni az új rendszert.</para>
 
 	  <para>Most, miután sikeresen beállítottuk
 	    az új lemezt, készen állunk az adatok
diff --git a/hu_HU.ISO8859-2/htdocs/docs/books.sgml b/hu_HU.ISO8859-2/htdocs/docs/books.sgml
index f7dcdb72ca..8936eb7cce 100644
--- a/hu_HU.ISO8859-2/htdocs/docs/books.sgml
+++ b/hu_HU.ISO8859-2/htdocs/docs/books.sgml
@@ -146,12 +146,6 @@
       internetszolgáltatónak.</p>
 
     <p><a
-	href="&url.articles;/checkpoint/index.html">A Checkpoint VPN-1/Firewall-1 és a &os; IPSec integrációja</a>
-      (checkpoint)<br/>
-      Hogyan konfiguráljunk Checkpoint VPN-1/Firewall-1-et a &os;
-      IPSec implementációjával együtt.</p>
-
-    <p><a
 	href="&url.articles;/committers-guide/index.html">A committerek útmutatója</a>
       (committers-guide)<br/>
       Fontos bevezetõ a commit jogot nyert &os; fejlesztõknek
@@ -220,27 +214,6 @@
       bonyolultabb funkcióit.</p>
 
     <p><a
-	href="&url.articles;/dialup-firewall/index.html">Tûzfal létrehozása betárcsázós kapcsolatokhoz &os;-vel</a>
-      (dialup-firewall) [<a href="&url.articles.hu;/dialup-firewall/index.html">magyarul</a>]<br/>
-      Hogyan állítsunk be egy tûzfalat a PPP
-      és az ipfw használatával dinamikusan
-      kiosztott IP-címek esetén.</p>
-
-    <p><a
-	href="&url.articles;/diskless-x/index.html">Lemez nélküli X szerver használata</a>
-      (diskless-x)<br/>
-      Hogyan hozzunk létre lemez nélküli X
-      szervert.</p>
-
-    <p><a
-	href="&url.articles;/euro/index.html">Az euró szimbólum használata a &os;-ben</a>
-      (euro)<br/>
-      Hogyan konfiguráljuk a &os;-t és a hozzá
-      kapcsolódó alkalmazásokat az euró
-      szimbólumának
-      megjelenítéséhez.</p>
-
-    <p><a
 	href="&url.articles;/explaining-bsd/index.html">A BSD bemutatása</a>
       (explaining-bsd) [<a href="&url.articles.hu;/explaining-bsd/index.html">magyarul</a>]<br/>
       A válasz arra a kérdésre, hogy mi az a
@@ -272,14 +245,6 @@
       használatáról.</p>
 
     <p><a
-	href="&url.articles;/formatting-media/index.html">Adathordozók formázása &os; alatt</a>
-      (formatting-media)<br/>
-      Hogyan osszuk fel slice-okra és partíciókra a
-      fix vagy éppen cserélhetõ lemezt, és
-      hogyan formázzuk meg azokat a &os; operációs
-      rendszerben.</p>
-
-    <p><a
 	href="&url.articles;/freebsd-questions/index.html">Hogyan használjuk hatékonyan a &os;-questions levelezési listát?</a>
       (freebsd-questions)<br/>
       Tippek és trükkök arra, hogyan szerezzünk
@@ -302,13 +267,6 @@
       környezetben bemutató leírás.</p>
 
     <p><a
-	href="&url.articles;/hats/index.html">Munka kitüntetett szerepekkel</a>
-      (hats)<br/>
-      A committerek útmutatója, hogyan dolgozzanak
-      kitüntetett szerepekben, fennhatósággal a &os;
-      bizonyos területei felett.</p>
-
-    <p><a
 	href="&url.articles;/hubs/index.html">A &os; tükrözése</a>
       (hubs)<br/>
       Útmutató a &os; honlapjának, CVSup
@@ -368,13 +326,6 @@
       használatába &os; alatt.</p>
 
     <p><a
-	href="&url.articles;/multi-os/index.html">A &os; telepítése és használata más operációs rendszerekkel együtt</a>
-      (multi-os) [<a href="&url.articles.hu;/multi-os/index.html">magyarul</a>]<br/>
-      Hogyan telepítsük a &os;-t más
-      operációs rendszer mellé, ugyanarra a
-      számítógépre.</p>
-
-    <p><a
 	href="&url.articles;/nanobsd/index.html">A NanoBSD bemutatása</a>
       (nanobsd)<br/>
       A NanoBSD eszközeinek bemutatása, amelyek
@@ -508,46 +459,12 @@
       &os;-ben.</p>
 
     <p><a
-	href="&url.articles;/storage-devices/index.html">Háttértárak</a>
-      (storage-devices)<br/>
-      Részletes információk a
-      háttértárak
-      használatáról a &os;-ben, beleértve az
-      ESDI és SCSI eszközöket, szalagos tárakat
-      és CD-ROM olvasókat.</p>
-
-    <p><a
-	href="&url.articles;/version-guide/index.html">Válasszuk ki a nekünk igazán megfelelõ &os; verziót!</a>
-      (version-guide) [<a href="&url.articles.hu;/version-guide/index.html">magyarul</a>]<br/>
-      Hogyan válasszuk ki az igényeinek megfelelõ
-      &os; verziót.  Elmagyarázza a kiadások
-      és a fejlesztési ágak rendszerét,
-      és leírja a -CURRENT és -STABLE közti
-      különbségeket, illetve a projekt jelenlegi
-      fejlesztési ütemezését.</p>
-
-    <p><a
-	href="&url.articles;/vinum/index.html">Rendszerindítás Vinummal: A megbízható szerverek alapja</a>
-      (vinum)<br/>
-      Egy remek bevezetés a hibatûrõ szerverekrõl
-      és egy lépésrõl-lépésre
-      haladó útmutató, amely bemutatja, hogyan
-      hozhatunk létre ilyet Vinummal.</p>
-
-    <p><a
 	href="&url.articles;/vm-design/index.html">A &os; VM alrendszer elemeinek felépítése</a>
       (vm-design)<br/>
       Egy könnyen érthetõ leírás a &os;
       virtuális memóriát kezelõ
       alrendszerérõl.</p>
 
-    <p><a
-	href="&url.articles;/zip-drive/index.html">Zip meghajtók és a &os;</a>
-      (zip-drive)<br/>
-      Hogyan formázzunk, csatlakoztassunk és
-      használjunk Iomega Zip (SCSI, IDE, vagy párhuzamos)
-      meghajtókat a &os;-n.</p>
-
     <h2>Egyéb oldalakon</h2>
 
     <p>Számos önálló
diff --git a/it_IT.ISO8859-15/articles/Makefile b/it_IT.ISO8859-15/articles/Makefile
index d646345f96..ef1a5ebb3e 100644
--- a/it_IT.ISO8859-15/articles/Makefile
+++ b/it_IT.ISO8859-15/articles/Makefile
@@ -2,10 +2,8 @@
 
 SUBDIR =
 SUBDIR+= committers-guide
-SUBDIR+= euro
 SUBDIR+= explaining-bsd
 SUBDIR+= filtering-bridges
-SUBDIR+= multi-os
 SUBDIR+= new-users
 SUBDIR+= vm-design
 
diff --git a/it_IT.ISO8859-15/articles/euro/Makefile b/it_IT.ISO8859-15/articles/euro/Makefile
deleted file mode 100644
index 2588133637..0000000000
--- a/it_IT.ISO8859-15/articles/euro/Makefile
+++ /dev/null
@@ -1,18 +0,0 @@
-#
-# $FreeBSD$
-#
-# Articolo: Il simbolo dell'Euro su FreeBSD
-
-DOC?= article
-
-FORMATS?= html
-
-INSTALL_COMPRESSED?=gz
-INSTALL_ONLY_COMPRESSED?=
-
-SRCS=	article.sgml
-
-URL_RELPREFIX?= ../../../..
-DOC_PREFIX?= ${.CURDIR}/../../..
-
-.include "${DOC_PREFIX}/share/mk/doc.project.mk"
diff --git a/it_IT.ISO8859-15/articles/euro/article.sgml b/it_IT.ISO8859-15/articles/euro/article.sgml
deleted file mode 100644
index be1443c897..0000000000
--- a/it_IT.ISO8859-15/articles/euro/article.sgml
+++ /dev/null
@@ -1,389 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-15" standalone="no"?>
-<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V4.2-Based Extension//EN"
-	"../../../share/sgml/freebsd42.dtd" [
-<!ENTITY % entities PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Entity Set//IT" "../../share/sgml/entities.ent">
-%entities;
-]>
-
-<!--
-     The FreeBSD Italian Documentation Project
-
-     $FreeBSD$
-     Original revision: 1.11
--->
-
-<article lang="it">
-  <articleinfo>
-    <title>Il simbolo dell'Euro su <systemitem
-        class="osname">FreeBSD</systemitem></title>
-
-    <authorgroup>
-      <author>
-        <firstname>Aaron</firstname>
-
-        <surname>Kaplan</surname>
-
-        <affiliation>
-          <address><email>aaron@lo-res.org</email></address>
-        </affiliation>
-      </author>
-    </authorgroup>
-
-    <copyright>
-      <year>2002</year>
-
-      <year>2003</year>
-
-      <holder>The FreeBSD Italian Documentation Project</holder>
-    </copyright>
-
-    <legalnotice id="trademarks" role="trademarks">
-      &tm-attrib.freebsd;
-      &tm-attrib.general;
-    </legalnotice>
-
-    <pubdate>$FreeBSD$</pubdate>
-
-    <releaseinfo>$FreeBSD$</releaseinfo>
-
-    <abstract>
-      <para>Questo documento cercherà di aiutarvi ad usare il nuovo
-        simbolo dell'<keycap>Euro</keycap> presente sulla vostra nuova tastiera
-        comprata all'inizio del 2002 per l'avvento della nuova valuta comune.
-        Inizieremo dalle parti più importanti come essere in grado di
-        visualizzare correttamente il simbolo in console.  Le sezioni successive
-        tratteranno la configurazione di specifici programmi come
-        <application>X11</application>.</para>
-
-      <para>Molti utili suggerimenti sono stati forniti da Oliver Fromm,
-        Tom Rhodes e innumerevoli altri.
-        Grazie! Senza di voi non sarebbe stato possibile realizzare questo
-        articolo!</para>
-
-      &trans.it.dema;
-    </abstract>
-  </articleinfo>
-
-  <sect1>
-    <title>L'Euro in 5 minuti</title>
-
-    <para>Se avete già familiarità con la
-      <ulink url="&url.books.handbook;/l10n.html">localization</ulink> come
-      descritta nel Manuale di <systemitem class="osname">FreeBSD</systemitem>
-      potreste essere interessanti solamente alle seguenti informazioni che
-      vi consentiranno di iniziare velocemente ad usare l'Euro:</para>
-
-    <variablelist>
-      <varlistentry>
-        <term>ISO8859-15</term>
-
-        <listitem>
-          <para>Questa è una versione leggermente modificata della
-            più comune mappa caratteri ISO8859-1.
-            Include il simbolo dell'Euro.  Usata per le variabili d'ambiente
-            <envar>LANG</envar> e <envar>LC_CTYPE</envar>.</para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><filename>iso15-8x16.fnt</filename></term>
-
-        <listitem>
-          <para>Il font per la console da usare con &man.vidcontrol.1;</para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><filename>/usr/share/syscons/keymaps/*.iso.kbd</filename></term>
-
-        <listitem>
-          <para>Mappe di tastiera per le diverse lingue.  Impostate la vostra
-            variabile <literal>keymap</literal> in <filename>rc.conf</filename>
-            ad una di queste mappe.</para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><envar>LC_CTYPE</envar></term>
-
-        <listitem>
-          <para>Usata per impostare il corretto tipo di caratteri nelle vostre
-            impostazioni locali.</para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><literal>XkbLayout
-            "<replaceable>lingua</replaceable>(euro)"</literal></term>
-
-        <listitem>
-          <para>Opzione di configurazione di
-            <application>XFree86</application>.</para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><filename>/usr/X11R6/lib/X11/fonts/*/fonts.alias</filename></term>
-
-        <listitem>
-          <para>Assicuratevi di modificare i nomi dei vostri file dei font di
-            X11 a <literal>-*-..-*-iso8859-15</literal></para>
-        </listitem>
-      </varlistentry>
-    </variablelist>
-  </sect1>
-
-  <sect1 id="general">
-    <title>Nota generale</title>
-
-    <para>Nelle sezioni seguenti ci riferiremo spesso a
-      <emphasis>ISO8859-15</emphasis>.
-      Questa è la notazione standard a partire da
-      <systemitem class="osname">FreeBSD</systemitem> 4.5.
-      Nelle versioni più vecchie la notazione standard era invece
-      <emphasis>ISO_8859-15</emphasis> oppure
-      <emphasis>DIS_8859-15</emphasis>.</para>
-
-    <para>Se state usando una versione di
-      <systemitem class="osname">FreeBSD</systemitem> più vecchia,
-      assicuratevi di guardare in
-      <filename>/usr/share/locale/</filename> per scoprire quale notazione
-      è in uso nel vostro sistema.</para>
-  </sect1>
-
-  <sect1 id="console">
-    <title>La console</title>
-
-    <sect2>
-      <title>Configurare il font della console</title>
-
-      <para>In base alla risoluzione e dimensione della vostra console
-        dovrete mettere una delle seguenti linee in
-        <filename>rc.conf</filename>:</para>
-
-      <programlisting>font8x16="iso15-8x16.fnt" # da /usr/share/syscons/fonts/*
-font8x14="iso15-8x14.fnt"
-font8x8="iso15-8x8.fnt"</programlisting>
-
-      <para>Questo imposterà effettivamente il font ISO8859-15 conosciuto
-        anche come Latin-9.  ISO8859-15 è una variazione di ISO8859-1.
-        Potete notare la differenza tra i due esaminando il simbolo dell'Euro:
-        il suo valore decimale è 164.  Nell'ISO8859-1 noterete un
-        cerchietto con quattro piccoli segnetti agli angoli.  Questo è
-        spesso chiamato <quote>simbolo universale di valuta</quote>.
-        Nell'ISO8859-15, invece del cerchietto, avrete il simbolo dell'Euro.
-        Per il resto i font sono più o meno identici.</para>
-
-      <warning>
-        <para>Al momento della stesura di questo articolo l'unico font
-          utilizzabile sembra essere l'<literal>iso15-8x16.fnt</literal>.
-          Gli altri sembrano avere l'aspetto dello ISO8859-1 sebbene il nome
-          suggerisca altrimenti.</para>
-      </warning>
-
-      <note>
-        <para>Impostando questo font alcune applicazioni da console avranno
-        un aspetto <quote>rovinato</quote>.
-        Questo è dovuto al fatto che esse si
-        aspettano di trovare un diverso set di font/caratteri come per esempio
-        l'ANSI 850.  Un tipico esempio è
-        <application>sysinstall</application>.
-        Comunque questo non dovrebbe essere un problema nella maggior parte
-        dei casi.</para>
-      </note>
-
-      <para>Il vostro prossimo passo dovrebbe essere o riavviare il vostro
-        sistema affinché i cambiamenti abbiano effetto oppure
-        (manualmente) effettuare le modifiche nello stesso modo in cui
-        avverrebbero all'avvio:</para>
-
-      <screen>&prompt.user; <userinput>vidcontrol -f <replaceable>iso15-8x16.fnt</replaceable></userinput></screen>
-
-      <para>Per controllare se il font è stato impostato eseguite il
-        seguente piccolo script
-        <command><anchor id="awk-test"/>awk</command>:</para>
-
-      <programlisting>#!/usr/bin/awk -f
-BEGIN {
-        for(i=160;i&lt;180;i++)
-                printf"%3d %c\n",i,i
-}</programlisting>
-
-      <para>Il risultato dovrebbe mostrare il simbolo dell'Euro nella
-        posizione 164.</para>
-    </sect2>
-
-    <sect2>
-      <title>Configurare la vostra tastiera per l'Euro</title>
-
-      <para>La maggior parte delle mappe di tastiera dovrebbe essere già
-        correttamente impostata.  Per esempio, se avete una tastiera
-        italiana e vi funzionano le lettere accentate, potete tranquillamente
-        saltare questa sezione visto che la tastiera mappa correttamente la
-        combinazioni di caratteri, qualunque essa sia,
-        (ad esempio: <keycombo action="simul">
-          <keycap>Alt Gr</keycap>
-          <keycap>e</keycap>
-        </keycombo>) al valore decimale 164.
-        Se avete problemi la cosa migliore è controllare i file in
-        <filename>/usr/share/syscons/keymaps/*.kbd</filename>.
-        Il formato dei file delle mappe di tastiera è descritto in
-        &man.keyboard.4;. &man.kbdcontrol.1; può essere usato per
-        caricare una mappa personalizzata.</para>
-
-      <para>Una volta che è stata trovata la corretta mappa di tastiera,
-        dovete aggiungerla a <filename>/etc/rc.conf</filename> con la
-        linea:</para>
-
-      <programlisting>keymap="<replaceable>it.iso</replaceable>" # o un'altra mappa</programlisting>
-
-      <para>Come spiegato in precedenza, questo passo probabilmente lo avete
-        già fatto al momento dell'installazione (con
-        <application>sysinstall</application>).
-        In caso contrario, riavviate oppure caricate la nuova mappa con
-        &man.kbdcontrol.1;.</para>
-
-      <para>Per verificare la nuova mappatura della tastiera, passate ad una
-        nuova console e al prompt di login, <emphasis>invece di
-        loggarvi</emphasis>, provate a premere il tasto <keycap>Euro</keycap>.
-        Se non funziona assicuratevi di aver correttamente impostato la
-        giusta mappa di tastiera oppure inviate una segnalazione di bug
-        con &man.send-pr.1;.</para>
-
-      <note>
-        <para>Al momento il tasto Euro non funziona ancora con
-          <application>bash</application> o
-          <application>tcsh</application>.</para>
-      </note>
-    </sect2>
-
-    <sect2>
-      <title>Correggere le variabili d'ambiente</title>
-
-      <para>Le shell (<application>bash</application>,
-        <application>tcsh</application>) si basano sulla libreria
-        &man.readline.3;, la quale a sua volta utilizza la variabile d'ambiente
-        <envar>LC_CTYPE</envar>.  <envar>LC_CTYPE</envar> deve essere impostata
-        prima che la shell sia completamente operativa.
-        Fortunatamente è sufficiente aggiungere la linea:</para>
-
-      <programlisting>export LC_CTYPE=<replaceable>it_IT</replaceable>.ISO8859-15</programlisting>
-
-      <para>al vostro file <filename>.bash_profile</filename>
-        (<application>bash</application>), oppure:</para>
-
-      <programlisting>setenv LC_CTYPE <replaceable>it_IT</replaceable>.ISO8859-15</programlisting>
-
-      <para>al vostro file <filename>.login</filename>
-        (<application>tcsh</application>).  Naturalmente,
-        <replaceable>it_IT</replaceable> deve essere sostituito con la
-        vostra lingua.  Poi, sloggatevi e riloggatevi nuovamente, e verificate
-        che il tasto Euro funzioni.
-        Già così la maggior parte delle applicazioni console
-        dovrebbe funzionare correttamente col tasto Euro.
-        Ulteriori configurazioni per programmi speciali come
-        <application>pine</application> potrebbero essere comunque
-        necessarie.</para>
-
-      <note>
-        <para>Un'alternativa alla modifica di <filename>.login</filename> e
-          <filename>.bash_profile</filename> è quella di impostare le
-          variabili d'ambiente tramite &man.login.conf.5;.  Questo approccio
-          ha il vantaggio di assegnare classi di login a determinati utenti
-          (esempio, utenti Francesi, utenti Tedeschi, ecc.)
-          <emphasis>in un solo posto</emphasis>.</para>
-      </note>
-    </sect2>
-  </sect1>
-
-  <sect1 id="x11">
-    <title>Modificare X11</title>
-
-    <para>Modificate <filename>/etc/XF86Config</filename>
-      (<filename>/etc/X11/XF86Config</filename> se stai usando &xfree86;)
-      nel seguente modo:</para>
-
-    <programlisting>Option "XkbLayout"  "<replaceable>it</replaceable>(euro)"</programlisting>
-
-    <para>Come sempre, rimpiazzate <replaceable>it</replaceable> con la
-      vostra lingua.  Così facendo la tastiera dovrebbe essere
-      configurata correttamente.  Come in console, deve essere scelto il font
-      adatto.  Per le applicazioni <application>KDE</application> andate in
-      <application>KDE control center</application> -&gt;
-      Personalization -&gt; Country &amp; Language -&gt; Charset e
-      cambiatelo in <literal>ISO8859-15</literal>.
-      Simili modifiche si devono effettuare per
-      <application>kmail</application> e altre applicazioni.</para>
-
-    <para>Un'altra buona idea è modificare i vostri file
-      <filename>fonts.alias</filename>.
-      In particolar modo il font <literal>fixed</literal> dovrebbe essere
-      modificato per usare la giusta mappa caratteri. Il file
-      <filename>/usr/X11R6/lib/X11/fonts/misc/fonts.alias</filename>
-      dell'autore è mostrato come esempio:</para>
-
-     <programlisting>! $Xorg: fonts.alias,v 1.3 2000/08/21 16:42:31 coskrey Exp $
-fixed   -misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-iso8859-15
-variable -*-helvetica-bold-r-normal-*-*-120-*-*-*-*-iso8859-15
-(...)</programlisting>
-
-    <para>Come in console, applicazioni speciali hanno ancora i font
-      ISO8859-1 configurati nei loro rispettivi database &man.xrdb.1;.
-      Un esempio importante è <application>xterm</application>.
-      Come regola generale è sufficiente cambiare il corrispondente file
-      di configurazione in
-      <filename>/usr/X11R6/lib/X11/app-defaults</filename>
-      e aggiungere il font corretto.  Ecco come fare per
-      <application>xterm</application>.</para>
-
-   <screen>&prompt.root; cd /usr/X11R6/lib/X11/app-defaults/
-&prompt.root; vi XTerm</screen>
-
-    <para>Aggiungete la seguente linea all'inizio del file:</para>
-
-    <programlisting>*font:     -misc-fixed-medium-r-normal-*-*-120-*-*-c-*-iso8859-15</programlisting>
-
-    <para>Infine, fate ripartire X e assicuratevi che i font siano
-      visualizzati correttamente eseguendo il precedente
-      <link linkend="awk-test">script awk</link>.
-      Tutte le principali applicazioni dovrebbero rispettare la mappatura di
-      tastiera e l'impostazione del font.</para>
-  </sect1>
-
-  <sect1 id="problems">
-    <title>Problemi non ancora risolti</title>
-
-    <para>Naturalmente, l'autore gradirebbe ricevere i vostri commenti.
-      Inoltre, fatemi almeno sapere se avete soluzioni per questi problemi
-      irrisolti.</para>
-
-    <itemizedlist>
-      <listitem>
-        <para>Descrivere metodi alternativi per configurare
-          <application>XFree86</application>:
-          <filename role="package">x11/xkeycaps</filename></para>
-      </listitem>
-
-      <listitem>
-        <para>Impostazioni in <application>GNOME</application></para>
-      </listitem>
-
-      <listitem>
-        <para>Impostazioni in <application>XFCE</application></para>
-      </listitem>
-
-      <listitem>
-        <para>Impostazioni per <application>(X)Emacs</application></para>
-      </listitem>
-
-      <listitem>
-        <para>Descrivere l'UTF-8</para>
-      </listitem>
-
-      <listitem>
-        <para>Descrivere <application>libiconv</application> come un buon
-          sistema per convertire applicazioni da ISO8859-15 a UTF-{8,16}</para>
-      </listitem>
-    </itemizedlist>
-  </sect1>
-</article>
diff --git a/it_IT.ISO8859-15/articles/multi-os/Makefile b/it_IT.ISO8859-15/articles/multi-os/Makefile
deleted file mode 100644
index a12328b7cb..0000000000
--- a/it_IT.ISO8859-15/articles/multi-os/Makefile
+++ /dev/null
@@ -1,17 +0,0 @@
-#
-# $FreeBSD$
-#
-# Articolo: Installazione e Utilizzo di FreeBSD con altri Sistemi Operativi
-
-DOC?= article
-
-FORMATS?= html
-WITH_ARTICLE_TOC?= YES
-
-INSTALL_COMPRESSED?=gz
-INSTALL_ONLY_COMPRESSED?=
-
-SRCS=	article.sgml
-
-DOC_PREFIX?= ${.CURDIR}/../../..
-.include "${DOC_PREFIX}/share/mk/doc.project.mk"
diff --git a/it_IT.ISO8859-15/articles/multi-os/article.sgml b/it_IT.ISO8859-15/articles/multi-os/article.sgml
deleted file mode 100644
index 884a11a68b..0000000000
--- a/it_IT.ISO8859-15/articles/multi-os/article.sgml
+++ /dev/null
@@ -1,792 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-15" standalone="no"?>
-<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V4.2-Based Extension//EN"
-	"../../../share/sgml/freebsd42.dtd" [
-<!ENTITY % entities PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Entity Set//IT" "../../share/sgml/entities.ent">
-%entities;
-]>
-
-<!--
-     The FreeBSD Italian Documentation Project
-
-     $FreeBSD$
-     Original revision: 1.39
--->
-
-<article lang="it">
-  <articleinfo>
-    <title>Installazione e Utilizzo di FreeBSD con altri Sistemi
-      Operativi</title>
-
-    <authorgroup>
-      <author>
-        <firstname>Jay</firstname>
-
-        <surname>Richmond</surname>
-
-        <affiliation>
-          <address><email>jayrich@sysc.com</email></address>
-        </affiliation>
-      </author>
-    </authorgroup>
-
-    <pubdate>6 Agosto 1996</pubdate>
-
-    <legalnotice id="trademarks" role="trademarks">
-      &tm-attrib.freebsd;
-      &tm-attrib.ibm;
-      &tm-attrib.linux;
-      &tm-attrib.microsoft;
-      &tm-attrib.powerquest;
-      &tm-attrib.general;
-    </legalnotice>
-
-    <releaseinfo>$FreeBSD$</releaseinfo>
-
-    <abstract>
-      <para>Questo documento spiega come far coesistere felicemente
-        FreeBSD con altri sistemi operativi come Linux, &ms-dos;,
-        &os2;, e &windows; 95.
-        Un ringraziamento speciale va a: Annelise Anderson
-        <email>andrsn@stanford.edu</email>, Randall Hopper
-        <email>rhh@ct.picker.com</email>, e &a.jkh;.</para>
-
-      &trans.it.max;
-    </abstract>
-  </articleinfo>
-
-  <sect1>
-    <title>Introduzione</title>
-
-    <para>Molta gente non può far convivere questi sistemi operativi
-      senza avere a disposizione un hard disk di grosse dimensioni,
-      perciò sono state incluse informazioni speciali sui drive EIDE
-      di grosse dimensioni.  Poiché ci sono così tante
-      combinazioni di possibili sistemi operativi e configurazioni di hard disk,
-      la <xref linkend="ch5"/> potrebbe esserti di aiuto più
-      di altre.  Contiene descrizioni di specifiche configurazioni che
-      usano molteplici sistemi operativi.</para>
-
-    <para>Questo documento assume che tu abbia già fatto posto sul tuo
-      hard disk per un altro sistema operativo.  Ogni volta che
-      ripartizioni il tuo hard disk, corri il rischio di distruggere
-      e quindi perdere i dati sulle partizioni originali.  In ogni caso,
-      se il tuo hard disk è completamente occupato dal DOS, potresti
-      usare FIPS (incluso nel CDROM di FreeBSD nella directory
-      <filename class="directory">\TOOLS</filename> oppure via
-      <ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/tools/">ftp</ulink>).
-      Ti permette di ripartizionare il tuo hard disk senza distruggere i
-      dati già contenuti.  C'è anche un programma commerciale
-      chiamato <application>&partitionmagic;</application>, che ti permette
-      di ridimensionare e cancellare partizioni senza conseguenze.</para>
-  </sect1>
-
-  <sect1 id="ch2">
-    <title>Panoramica sui Boot Manager</title>
-
-    <para>Si tratta solo di brevi descrizioni dei diversi boot manager che
-      potresti trovare.  A seconda del tuo computer, potresti trovare
-      utile usarne più di uno sullo stesso sistema.</para>
-
-    <variablelist>
-      <varlistentry>
-        <term>Boot Easy</term>
-
-        <listitem>
-          <para>Questo è il boot manager standard fornito con FreeBSD.
-            Ha la possibilità di far partire qualsiasi cosa, incluso BSD,
-            &os2; (HPFS), &windows; 95 (FAT e FAT32), e Linux.
-            Le partizioni vengono scelte con i tasti funzione (F1-F12).</para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term>Boot Manager di &os2;</term>
-
-        <listitem>
-          <para>Questo fa partire FAT, FAT32, HPFS, FFS (FreeBSD), ed EXT2
-            (Linux).  Le partizioni vengono scelte usando i tasti freccia.
-            L'&os2; Boot Manager è
-            l'unico ad usare una propria partizione separata, diversamente
-            dagli altri, che usano il master boot record (MBR).  Di conseguenza,
-            deve essere installato prima del 1024esimo cilindro per evitare
-            problemi di avvio.  Può far partire Linux usando LILO quando
-            questo è parte del settore di avvio, non dell'MBR.
-            Leggi gli <ulink
-              url="http://www.linuxresources.com/LDP/HOWTO/HOWTO-INDEX.html">HOWTO
-              di Linux</ulink> sul World Wide Web per avere più
-            informazioni su come far partire Linux con il boot manager di
-            &os2;.</para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term>OS-BS</term>
-
-        <listitem>
-          <para>Questa è un'alternativa a Boot Easy.  Ti dà
-            più controllo sul processo di avvio, con la
-            possibilità di impostare la partizione di default da cui
-            partire e il timeout di avvio.
-            La versione beta di questo programma ti permette di avviare
-            scegliendo il sistema operativo con i tasti freccia.  È
-            incluso nel cd di FreeBSD nella directory
-            <filename>\TOOLS</filename> oppure via <ulink
-              url="ftp://ftp.FreeBSD.org/pub/FreeBSD/tools/">ftp</ulink>.</para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term>LILO, o LInux LOader</term>
-
-        <listitem>
-          <para>Questo è un boot manager limitato.  Farà partire
-            FreeBSD, sebbene siano necessari alcuni accorgimenti e sistemazioni
-            nel file di configurazione.</para>
-        </listitem>
-      </varlistentry>
-    </variablelist>
-
-    <note id="fat32">
-      <title>A proposito di FAT32</title>
-
-      <para>FAT32 è il rimpiazzo al file system FAT incluso nella Release
-        Beta SR2 di Microsoft, che dovrebbe essere installata
-        con &windows; 95 a partire dalla fine del 1996.  Converte il
-        normale file system FAT e ti permette di usare cluster di
-        dimensioni più piccole per hard disk di dimensioni maggiori.
-        Inoltre FAT32 modifica il settore di avvio tradizionale e la tabella
-        di allocazione, rendendola incompatibile con alcuni Boot
-        Manager.</para>
-    </note>
-  </sect1>
-
-  <sect1 id="ch3">
-    <title>Una Installazione Tipica</title>
-
-    <para>Diciamo che ho due grandi hard disk EIDE e voglio installarci
-      FreeBSD, Linux, e &windows; 95.</para>
-
-    <para>Ecco come potrei fare usando questi due hard disk:</para>
-
-    <itemizedlist>
-      <listitem>
-        <para><filename>/dev/wd0</filename> (Primo hard disk)</para>
-      </listitem>
-
-      <listitem>
-        <para><filename>/dev/wd1</filename> (Secondo hard disk)</para>
-      </listitem>
-    </itemizedlist>
-
-    <para>Tutti e due hanno 1416 cilindri.</para>
-
-    <procedure>
-      <step>
-        <para>Parto dalla partizione &ms-dos; o dal dischetto di avvio
-          di &windows; 95 che contiene l'utility <filename>FDISK.EXE</filename>
-          e creo una piccola partizione primaria da 50&nbsp;MB
-          (35-40 per &windows; 95, più un po' di spazio per respirare)
-          sul primo disco.  Creo anche una partizione più grande sul
-          secondo hard disk per le applicazioni di &windows; e per i
-          dati.</para>
-      </step>
-
-      <step>
-        <para>Faccio ripartire ed installo &windows; 95 (più facile a
-          dirsi che a farsi) sulla partizione <filename>C:</filename>.</para>
-      </step>
-
-      <step>
-        <para>La prossima cosa che farò sarà installare Linux.
-          Non sono sicuro per le altre distribuzioni, ma la <ulink
-            url="http://www.slackware.com">Slackware</ulink> include
-          LILO (guarda la <xref linkend="ch2"/>).  Quando ripartiziono il
-          mio hard disk con l'<command>fdisk</command> di Linux,
-          metterò tutto ciò che riguarda Linux sul primo hard
-          disk (probabilmente 300&nbsp;MB per una partizione di
-          root decente e un po' di spazio di swap).</para>
-      </step>
-
-      <step>
-        <para>Dopo aver installato Linux, quando viene chiesto di
-          installare LILO, <emphasis>assicurati</emphasis> di installarlo sul
-          settore di avvio della partizione di Linux, non
-          nell'MBR (Master Boot Record).</para>
-      </step>
-
-      <step>
-        <para>La parte rimanente di hard disk va a FreeBSD.
-          Assicurati anche che la <quote>slice</quote> root di FreeBSD
-          non vada oltre il 1024esimo cilindro.  (Il 1024esimo
-          cilindro è circa intorno ai 528&nbsp;MB in un disco ipotetico,
-          il mio, di 720&nbsp;MB).  Userò il resto dell'hard disk
-          (circa 270&nbsp;MB) per <filename class="directory">/usr</filename> e
-          <filename class="directory">/</filename>.  Il resto del secondo hard
-          disk (la grandezza varia a seconda di quanto spazio
-          ho lasciato agli applicativi e ai dati per &windows;
-          quando ho creato la partizione nel primo passo) può
-          essere usata per <filename class="directory">/usr/src</filename>
-          e per lo spazio di swap.</para>
-      </step>
-
-      <step>
-        <para>Se visualizzato con l'utility <command>fdisk</command>
-          di &windows; 95, l'hard disk dovrebbe risultare in questo modo:
-          <screen>---------------------------------------------------------------------
-
-                  Display Partition Information
-
-Current fixed disk drive: 1
-
-Partition  Status  Type  Volume_Label  Mbytes  System  Usage
-C: 1          A   PRI DOS                50    FAT**     7%
-   2          A   Non-DOS (Linux)       300             43%
-
-Total disk space is  696 Mbytes (1 Mbyte = 1048576 bytes)
-
-Press Esc to continue
-
----------------------------------------------------------------------
-
-                  Display Partition Information
-
-Current fixed disk drive: 2
-
-Partition  Status  Type  Volume_Label  Mbytes  System  Usage
-D: 1          A   PRI DOS                420   FAT**    60%
-
-Total disk space is  696 Mbytes (1 Mbyte = 1048576 bytes)
-
-Press Esc to continue
-
----------------------------------------------------------------------</screen>
-          ** Potrebbe essere FAT16 o FAT32 se stai usando l'aggiornamento OEM
-          SR2.  Guarda la <xref linkend="ch2"/>.</para>
-      </step>
-
-      <step>
-        <para>Installazione di FreeBSD.  Assicurati di avviare il computer
-          con il primo hard disk configurato con <quote>NORMAL</quote> nel BIOS.
-          Se non è così, dovrai settare la vera geometria
-          del disco all'avvio (per arrivare a fare ciò, fai partire
-          &windows; 95 e consulta  Microsoft Diagnostics
-          (<filename>MSD.EXE</filename>), o controlla il BIOS) con il
-          parametro <literal>hd0=1416,16,63</literal> dove <replaceable>
-          1416</replaceable> è il numero di cilindri sull'hard disk,
-          <replaceable>16</replaceable> è il numero di testine per
-          traccia, o <quote>heads per track</quote>, e
-          <replaceable>63</replaceable> è il numero di settori per
-          traccia sul drive.</para>
-      </step>
-
-      <step>
-        <para>Quando partiziono l'hard disk, cerco sempre di mettere Boot
-          Easy sul primo hard disk.  Non mi preoccupo del secondo hard
-          disk, non parte nulla da quello.</para>
-      </step>
-
-      <step>
-        <para>Al riavvio, Boot Easy dovrebbe riconoscere le tre partizioni
-          avviabili, cioè quella DOS (ovvero &windows; 95), Linux, e
-          BSD (FreeBSD).</para>
-      </step>
-    </procedure>
-  </sect1>
-
-  <sect1 id="ch4">
-    <title>Considerazioni Speciali</title>
-
-    <para>Molti sistemi operativi sono molto pignoli su come e dove devono
-      essere messi sull'hard disk.  &windows; 95 deve essere sulla prima
-      partizione primaria sul primo hard disk.  &os2; fa eccezione.  Può
-      essere installato in una partizione primaria o estesa sul primo o sul
-      secondo hard disk.  Se non sei sicuro, mantieni la parte avviabile di
-      partizione sotto il 1024esimo cilindro.</para>
-
-    <para>Se installi &windows; 95 su un sistema BSD esistente, questo
-      <quote>distruggerà</quote> l'MBR, e dovrai reinstallare il boot
-      manager precedente.  Boot Easy può essere reinstallato usando
-      l'utility <filename>BOOTINST.EXE</filename> inclusa nella directory
-      <filename class="directory">\TOOLS</filename> sul cdrom, oppure
-      via <ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/tools/"> ftp</ulink>.
-      Puoi anche ricominciare l'installazione e andare all'editor delle
-      partizioni.  Da lì, marcare la partizione di FreeBSD come
-      avviabile, scegliere Boot Manager, e quindi digitare W per scrivere le
-      informazioni nell'MBR.  Puoi ora riavviare, e Boot Easy dovrebbe
-      riconoscere &windows; 95 e DOS.</para>
-
-    <para>Ricordati che &os2; può leggere partizioni FAT e HPFS, ma non
-      FFS (FreeBSD) o EXT2 (Linux).  Diversamente &windows; 95 può
-      leggere e scrivere solo su FAT o FAT32 (guarda la <xref linkend="ch2"/>).
-      FreeBSD può leggere gran parte degli altri file system, ma al
-      momento non può leggere partizioni HPFS.  Linux può leggere
-      partizioni HPFS, ma non può scrivervi.  Versioni recenti del kernel
-      di Linux (2.x) possono leggere e scrivere su partizioni di &windows; 95 di
-      tipo VFAT (VFAT è ciò che permette a &windows; 95 di avere
-      i nomi di file lunghi - è molto simile alla FAT).
-      Linux può leggere e scrivere sulla maggior parte dei file system.
-      Capito? Lo spero...</para>
-  </sect1>
-
-  <sect1 id="ch5">
-    <title>Esempi</title>
-
-    <para><emphasis>(La sezione ha bisogno di lavoro, per favore spedisci
-        il tuo esempio a <email>jayrich@sysc.com</email>)</emphasis>.</para>
-
-    <para>FreeBSD + &windows; 95: Se hai installato FreeBSD dopo &windows; 95,
-      dovresti vedere <literal>DOS</literal> nel menu di Boot Easy.  Questo
-      è &windows; 95.  Se hai installato &windows; 95 dopo FreeBSD, leggi
-      la <xref linkend="ch4"/> sopra.
-      Fin quando il tuo hard disk non ha più di 1024 cilindri, non
-      dovrebbero esserci problemi.
-      Se una partizione va oltre il 1024esimo cilindro, e hai
-      messaggi di errore come <errorname>invalid system disk</errorname> sotto
-      DOS (&windows; 95) e FreeBSD non parte, prova a cercare una opzione nel
-      BIOS chiamata <quote>&gt; 1024 cylinder support</quote> o
-      <quote>NORMAL/LBA mode</quote>.
-      DOS potrebbe necessitare dell'LBA (Logical Block Addressing -
-      Indirizzamento Logico dei Blocchi) per partire correttamente.  Se l'idea
-      di cambiare delle impostazioni nel BIOS ogni volta che si accende il
-      computer non ti piace, puoi far partire FreeBSD da DOS con l'utility
-      <filename>FBSDBOOT.EXE</filename> che trovi sul CD (dovrebbe trovare la
-      tua partizione FreeBSD e farla partire).</para>
-
-    <para>FreeBSD + &os2; + &windows; 95: Nulla di nuovo qui.  Il boot manager
-      di &os2; può far partire tutti questi sistemi operativi,
-      cosicché non dovrebbero esserci problemi.</para>
-
-    <para>FreeBSD + Linux: Puoi usare Boot Easy per far partire tutti e due i
-      sistemi operativi.</para>
-
-    <para>FreeBSD + Linux + &windows; 95: (guarda la <xref
-        linkend="ch3"/>)</para>
-  </sect1>
-
-  <sect1 id="sources">
-    <title>Altre Fonti di Aiuto</title>
-
-    <para>Ci sono molti <ulink
-      url="http://www.linuxresources.com/LDP/HOWTO/HOWTO-INDEX.html">HOW-TO su
-        Linux</ulink> che trattano come affrontare il problema di avere
-      più sistemi operativi sullo stesso hard disk.</para>
-
-    <para>Il <ulink
-        url="http://www.linuxresources.com/LDP/HOWTO/mini/Linux+DOS+Win95+OS2.html">Linux+DOS+Win95+OS2
-        mini-HOWTO</ulink> offre aiuto su come configurare il boot manager di
-      &os2; e il <ulink
-        url="http://www.linuxresources.com/LDP/HOWTO/mini/Linux+FreeBSD.html">Linux+FreeBSD
-        mini-HOWTO</ulink> potrebbe essere anch'esso interessante.
-      Anche il <ulink
-        url="http://www.in.net/~jkatz/win95/Linux-HOWTO.html">Linux-HOWTO</ulink>
-      è di grande aiuto.</para>
-
-    <para>L'<ulink
-        url="http://www.tburke.net/info/ntldr/ntldr_hacking_guide.htm">&windowsnt;
-        Loader Hacking Guide</ulink> fornisce buone informazioni sul
-      multibooting di &windowsnt;, '95, e DOS con altri sistemi
-      operativi.</para>
-
-    <para>E il pacchetto di Hale Landis, <quote>How It Works</quote> contiene
-      alcune utili informazioni su tutti i tipi di geometrie dei drive e su
-      argomenti legati al processo di avvio.  Puoi trovarlo su <ulink
-        url="ftp://fission.dt.wdc.com/pub/otherdocs/pc_systems/how_it_works/allhiw.zip"></ulink>.</para>
-
-    <para>Inoltre non perderti la documentazione del kernel di FreeBSD sul
-      processo di avvio, disponibile nella distribuzione dei sorgenti del kernel
-      (si scompatta in <ulink
-        url="file://localhost/usr/src/sys/i386/boot/biosboot/README.386BSD">file:/usr/src/sys/i386/boot/biosboot/README.386BSD</ulink>.</para>
-  </sect1>
-
-  <sect1>
-    <title>Dettagli Tecnici</title>
-
-    <para><emphasis>(Contributo di Randall Hopper,
-      <email>rhh@ct.picker.com</email>)</emphasis></para>
-
-    <para>Questa sezione prova a fornire abbastanza informazioni di base
-      sugli hard disk e sul processo di avvio così da
-      essere poi capaci di determinare le cause dei problemi più
-      frequenti che potreste affrontare al momento dell'installazione e della
-      configurazione di più sistemi operativi.  Inizia con un
-      linguaggio semplice, così potresti voler scorrere la pagina fino a
-      quando non ti sembri difficile e cominciare quindi da quel punto a
-      leggere.</para>
-
-    <sect2>
-      <title>Introduzione agli Hard Disk</title>
-
-      <para>Sono generalmente usati tre termini fondamentali per descrivere
-        l'allocazione dei dati sull'hard disk: Cylinders (Cilindri), Heads
-        (Testine), e Sectors (Settori).  Non è particolarmente importante
-        sapere esattamente cosa significano questi termini e quale sia il loro
-        compito specifico, ma interessa sapere che, insieme, identificano dove
-        si trovano fisicamente i dati sull'hard disk.</para>
-
-      <para>Ogni hard disk ha un particolare numero di cilindri, di testine, e
-        di settori per ogni parte di cilindro relativa a una singola testina
-        (che generalmente viene chiamato track, o traccia).
-        Questi dati contribuiscono a determinare la geometria
-        fisica del disco dell'hard disk.  Ci sono
-        generalmente 512 byte per settore, e 63 settori per traccia, mentre
-        il numero di cilindri e testine varia a seconda del tipo di hard disk.
-        In questo modo puoi trovare la quantità di dati che il disco
-        potrebbe contenere semplicemente calcolando:</para>
-
-      <informalexample>
-        <para>(numero di cilindri) &times; (numero di testine) &times; (63
-          settori/traccia) &times; (512 byte/settore)</para>
-      </informalexample>
-
-      <para>Per esempio, sul mio Western Digital AC31600 EIDE, questo
-        è:</para>
-
-      <informalexample>
-        <para>(3148 cilindri) &times; (16 testine) &times; (63
-          settori/traccia) &times; (512 byte/settore)</para>
-      </informalexample>
-
-      <para>che sarebbe 1,624,670,208 byte, o circa 1.6 Giga.</para>
-
-      <para>Puoi scoprire la geometria fisica del disco (cioè il numero
-        di cilindri, testine, e il fattore settori/tracciati) del tuo hard disk
-        usando ATAID o altri programmi reperibili su Internet.  Probabilmente il
-        tuo hard disk ti è stato venduto con queste informazioni.
-        Comunque stai attento: se stai usando l'opzione LBA del BIOS (vedi la
-        <xref linkend="limits"/>), non puoi usare un qualsiasi programma per
-        conoscere la geometria fisica.  Questo perché molti programmi (ad
-        esempio <filename>MSD.EXE</filename> o l'fdisk di FreeBSD) non
-        identificano la geometria fisica del disco, fanno invece riferimento
-        alla <firstterm>geometria traslata</firstterm> (Numeri virtuali usando
-        LBA).  Continua a leggere per saperne di più.</para>
-
-      <para>Un altro aspetto interessante di questi termini.  Dati 3
-        numeri&mdash;un numero di cilindri, un numero di testine, e un numero
-        di settori per tracciato&mdash;si può identificare uno specifico
-        settore assoluto (un blocco di 512 byte di dati) sull'hard disk.  I
-        cilindri e le testine sono numerati partendo da 0, e i settori sono
-        numerati partendo da 1.</para>
-
-      <para>Per quelli che sono interessati a dettagli più tecnici,
-        informazioni sulla geometria dei dischi, settori di avvio, BIOS, e
-        altro, possono trovare grandi quantità di informazioni in
-        Internet.  Basta fare una ricerca con Lycos, Yahoo e altri digitando
-        <literal>boot sector</literal> o <literal>master boot record</literal>.
-        Tra le numerose informazioni utili che si possono trovare c'è il
-        pacchetto di documentazione <citetitle>How It Works</citetitle> (in
-        italiano <quote>Come Funziona</quote>) di Hale Landis.  Guarda la
-        <xref linkend="sources"/> per alcuni puntatori a questo
-        pacchetto.</para>
-
-      <para>Ok, troppa terminologia finora. Adesso parliamo del processo di
-        avvio.</para>
-    </sect2>
-
-    <sect2 id="booting">
-      <title>Il Processo di Avvio</title>
-
-      <para>Sul primo settore del tuo disco (Cyl 0, Head 0, Sector 1) risiede
-        il Master Boot Record (MBR).  Questo contiene una mappa del tuo disco.
-        Identifica fino a 4 <firstterm>partizioni</firstterm>, ciascuna delle
-        quali è uno spazio, una parte, di quel disco.  FreeBSD chiama
-        queste partizioni <firstterm>slices</firstterm> per evitare confusione
-        con le sue partizioni, di cui ora non parleremo.
-        Ciascuna partizione può contenere un sistema operativo
-        diverso.</para>
-
-      <para>Ogni elemento che rappresenta una partizione presente nell'MBR ha un
-        <firstterm>Partition ID</firstterm>, un valore <firstterm>Start
-          Cylinder/Head/Sector</firstterm>, e un valore <firstterm>End
-          Cylinder/Head/Sector</firstterm>.  Il Partition ID mostra di che tipo
-        di partizione si tratta (di che sistema operativo) e i valori di
-        inizio/fine dicono dove questa si trova.  La <xref linkend="tbl-pid"/>
-        mostra una lista di partition ID più comuni.</para>
-
-      <table id="tbl-pid">
-        <title>Partition ID</title>
-
-        <tgroup cols="2">
-          <thead>
-            <row>
-              <entry>ID (hex)</entry>
-
-              <entry>Descrizione</entry>
-            </row>
-          </thead>
-
-          <tbody>
-            <row>
-              <entry>01</entry>
-
-              <entry>DOS12 primaria (12-bit FAT)</entry>
-            </row>
-
-            <row>
-              <entry>04</entry>
-
-              <entry>DOS16 primaria (16-bit FAT)</entry>
-            </row>
-
-            <row>
-              <entry>05</entry>
-
-              <entry>DOS estesa</entry>
-            </row>
-
-            <row>
-              <entry>06</entry>
-
-              <entry>DOS primaria di grande dimensione (&gt; 32MB)</entry>
-            </row>
-
-            <row>
-              <entry>0A</entry>
-
-              <entry>&os2;</entry>
-            </row>
-
-            <row>
-              <entry>83</entry>
-
-              <entry>Linux (EXT2FS)</entry>
-            </row>
-
-            <row>
-              <entry>A5</entry>
-
-              <entry>FreeBSD, NetBSD, 386BSD (UFS)</entry>
-            </row>
-          </tbody>
-        </tgroup>
-      </table>
-
-      <para>Nota che non tutte le partizioni sono avviabili (per esempio quelle
-        DOS estese).  Alcune lo sono, altre no.  Ciò che rende una
-        partizione avviabile è la configurazione del <firstterm>Partition
-          Boot Sector</firstterm> che si trova all'inizio di ciascuna
-        partizione.</para>
-
-      <para>Quando configuri il tuo boot manager preferito, questo cerca gli
-        elementi nella tavola delle partizioni sull'MBR di tutti i tuoi hard
-        disk e fa in modo che tu possa dare un nome a tutte gli elementi della
-        lista.  Quindi all'avvio, il boot manager viene invocato da un codice
-        particolare presente nell'MBR del primo hard disk che viene rilevato sul
-        tuo sistema.  Questo guarda la tavola delle partizioni dell'MBR
-        corrispondente alla partizione che hai scelto, usa l'informazione sullo
-        Start Cylinder/Head/Sector per quella partizione, carica il Partition
-        Boot Sector per quella partizione, e sli dà il controllo.
-        Quel settore di avvio per la partizione contiene abbastanza informazioni
-        per cominciare a caricare il sistema operativo di quella
-        partizione.</para>
-
-      <para>Un particolare che abbiamo sorvolato e che è importante
-        conoscere.  Tutti gli hard disk hanno l'MBR.  Ad ogni modo, quello
-        importante è quello del disco che viene rilevato per primo dal
-        BIOS.  Se hai solo hard disk IDE, è il primo disco IDE
-        (cioè il disco primario del controller primario).
-        Stessa cosa per i sistemi SCSI.  Se hai sia
-        SCSI che IDE invece, i dischi IDE vengono riconosciuti per primi dal
-        BIOS, quindi il primo disco IDE è quello che viene riconosciuto
-        per primo.  Il boot manager che installerai si troverà quindi
-        sull'MBR del primo disco riconosciuto come descritto.</para>
-    </sect2>
-
-    <sect2 id="limits">
-      <title>Limitazioni sull'Avvio e Avvertimenti</title>
-
-      <para>Ora un po' di cose interessanti alle quali devi stare
-        attento.</para>
-
-      <sect3>
-        <title>Il maledetto limite dei 1024 cilindri e l'aiuto dell'LBA del
-          BIOS</title>
-
-        <para>La prima parte del processo di avvio viene effettuata attraverso
-          il BIOS, (se questo è un termine nuovo per te, il BIOS è
-          un chip contenente del software presente sulla scheda madre che
-          contiene il codice di avviamento per il computer).  Quindi, questa
-          prima parte del processo è soggetta alle limitazioni
-          dell'interfaccia del BIOS.</para>
-
-        <para>L'interfaccia BIOS usata per leggere gli hard disk in questo
-          momento (INT 13H, Subfunction 2) alloca 10 bit per il Cylinder Number,
-          8 bit per l'Head Number, e 6 bit per il Sector Number.  Questo porta
-          gli utenti ad essere sottoposti a dei limiti (per esempio i boot
-          manager installati nell'MBR così come i loader installati nei
-          Boot Sector) che ora vediamo:</para>
-
-        <itemizedlist>
-          <listitem>
-            <para>1024 cilindri, massimo</para>
-          </listitem>
-
-          <listitem>
-            <para>256 testine, massimo</para>
-          </listitem>
-
-          <listitem>
-            <para>64 settori/traccia, massimo (in realtà 63,
-              <literal>0</literal> non è disponibile)</para>
-          </listitem>
-        </itemizedlist>
-
-        <para>Ora, hard disk grossi hanno molti cilindri, ma non molte testine,
-          quindi invariabilmente con grandi hard disk il numero di cilindri
-          sarà più alto di 1024.  A causa di questo e della
-          situazione dell'interfaccia BIOS, non puoi far partire un sistema
-          operativo da qualsiasi punto del disco.  Il codice di avvio (il boot
-          manager e il loader del sistema operativo devono essere nei settori di
-          avvio di tutte le partizioni avviabili) deve risiedere entro il limite
-          dei 1024 cilindri.  In pratica, se il tuo hard disk è generico
-          e contiene 16 testine, questo si tramuta in:</para>
-
-        <informalexample>
-          <para>1024 cilindri/disco &times; 16 testine/disco &times; 63
-            settori/traccia &times; 512 byte/settore</para>
-        </informalexample>
-
-        <para>che è intorno al summenzionato limite dei 528MB.</para>
-
-        <para>Qui è dove entra in gioco l'LBA (Logical Block Addressing,
-          Indirizzamento Logico dei Blocchi) del BIOS.  L'LBA del BIOS fornisce
-          all'utente delle API del BIOS accesso ai cilindri fisici oltre al
-          1024esimo attraverso l'interfaccia BIOS ridefinendo un cilindro.
-          Quindi, rimappa cilindri e testine, facendo sembrare al BIOS che il
-          computer contenga meno cilindri e più testine di quanto in
-          realtà non ne abbia.
-          In altre parole, si avvantaggia del fatto che gli hard disk hanno
-          relativamente poche testine e molti cilindri semplicemente bilanciando
-          tra cilindri e testine facendo in modo che tutti e due i numeri
-          rimangano sotto la soglia (1024 cilindri, 256 testine).</para>
-
-        <para>Con l'LBA del BIOS, la limitazione agli hard disk è
-          virtualmente eliminata (beh, spostata ad 8 Gigabyte).  Se hai un BIOS
-          che supporta l'LBA, puoi mettere FreeBSD o qualsiasi altro OS in
-          qualsiasi parte tu voglia senza toccare il limite dei 1024
-          cilindri.</para>
-
-        <para>Per usare ancora l'esempio del mio Western Digital da 1.6
-          Giga, la sua geometria fisica è:</para>
-
-        <informalexample>
-          <para>(3148 cilindri, 16 testine, 63 settori/traccia, 512
-            byte/settore)</para>
-        </informalexample>
-
-        <para>Ad ogni modo, il mio LBA del BIOS rimappa questo in:</para>
-
-        <informalexample>
-          <para>(787 cilindri, 64 testine, 63 settori/traccia, 512
-            byte/settore)</para>
-        </informalexample>
-
-        <para>dandomi la stessa grandezza effettiva di disco, ma con numero di
-          cilindri e testine entro i limiti dell'API del BIOS (casualmente,
-          ho sia Linux che FreeBSD installati su uno dei miei hard disk sopra il
-          1024esimo cilindro fisico, e tutti e due partono perfettamente, grazie
-          all'LBA del BIOS).</para>
-      </sect3>
-
-      <sect3>
-        <title>Boot Manager e Allocazione del Disco</title>
-
-        <para>Un altro punto di cui tener conto al momento al momento
-          dell'installazione di un boot manager, è quello di ricordarsi
-          di allocare spazio per il tuo boot manager.  È meglio aver
-          presente fin da subito questo problema, per non accorgersene troppo
-          tardi e dover quindi reinstallare uno o più sistemi
-          operativi.</para>
-
-        <para>Se hai seguito il discorso nella <xref linkend="booting"/> a
-          proposito del Master Boot Sector (dove si trova l'MBR), dei Partition
-          Boot Sectors, e dell processo di avvio, potresti esserti chiesto
-          esattamente dove quel piccolo boot manager risiede sul tuo hard disk.
-          Bene, alcuni boot manager sono abbastanza piccoli da risiedere nel
-          Master Boot Sector (Cilindro 0, Testina 0, Settore 0) insieme alla
-          tabella delle partizioni.  Alcuni invece hanno bisogno di un po' di
-          spazio in più e si estendono su alcuni settori oltre il Master
-          Boot Sector nella traccia del Cilindro 0 Testina 0, dato che questa
-          è tipicamente libera.</para>
-
-        <para>Ecco qui.  Alcuni sistemi operativi (incluso FreeBSD) fanno in
-          modo che le loro partizioni possano cominciare subito dopo il Master
-          Boot Sector, cioè al cilindro 0, testina 0, settore 2 se vuoi.
-          Infatti, se dai al sysinstall di FreeBSD un disco con una parte
-          iniziale vuota oppure un disco vuoto, quello è il punto da cui
-          comincerà la partizione FreeBSD di default (o almeno lo ha
-          fatto quando sono caduto in questa trappola).  Poi quando vai ad
-          installare il tuo boot manager, se è uno che occupa alcuni
-          settori oltre all'MBR, andrà a sovrascrivere la parte iniziale
-          dei dati della prima partizione.  Nel caso di FreeBSD, questo
-          sovrascrive il label del disco, e fa in modo da rendere non avviabile
-          la partizione di FreeBSD.</para>
-
-        <para>Il modo più semplice per eliminare questo problema (e
-          lasciarti la flessibilità di provare in seguito differenti boot
-          manager) è quello di lasciare sempre la prima traccia del tuo
-          hard disk completamente libera quando partizioni il tuo hard disk.
-          Ciò significa lasciare libero lo spazio tra il cilindro 0,
-          testina 0, settore 2 fino a cilindro 0, testina 0, settore 63, e
-          cominciare la prima partizione sul cilindro 0, testina 1, settore 1.
-          Per ciò che vale, quando crei una partizione DOS all'inizio del
-          tuo hard disk, il DOS lascia sempre questo spazio libero di default
-          (ecco perché molti boot manager presumono che sia libero).
-          Quindi creare una partizione DOS all'inizio del disco toglie questi
-          problemi tutti insieme.  Mi piace fare da solo, creando una partizione
-          DOS da 1 mega all'inizio, perché questo evita che cambino le
-          lettere dei drive DOS quando ripartiziono in seguito.</para>
-
-        <para>Come riferimento, i seguenti boot manager usano il Master Boot
-          Sector per immagazzinare il loro codice e i loro dati:</para>
-
-        <itemizedlist>
-          <listitem>
-            <para>OS-BS 1.35</para>
-          </listitem>
-
-          <listitem>
-            <para>Boot Easy</para>
-          </listitem>
-
-          <listitem>
-            <para>LILO</para>
-          </listitem>
-        </itemizedlist>
-
-        <para>Questi boot manager usano alcuni settori addizionali dopo
-          il Master Boot Sector:</para>
-
-        <itemizedlist>
-          <listitem>
-            <para>OS-BS 2.0 Beta 8 (settori 2-5)</para>
-          </listitem>
-
-          <listitem>
-            <para>Boot Manager di &os2;</para>
-          </listitem>
-        </itemizedlist>
-      </sect3>
-
-      <sect3>
-        <title>Cosa fare se il tuo computer non parte?</title>
-
-        <para>In alcuni momenti quando installi dei boot manager, potresti
-          lasciare l'MBR in uno stato in cui il computer non riesce più a
-          partire.  Questo è spiacevole, ma possibile quando si utilizza
-          FDISK su di un boot manager già installato.</para>
-
-        <para>Se hai una partizione DOS avviabile sul tuo hard disk, puoi
-          partire da un floppy DOS, e poi eseguire il comando:</para>
-
-        <informalexample>
-          <screen>A:\> <userinput>FDISK /MBR</userinput></screen>
-        </informalexample>
-
-        <para>Per mettere il codice originale di avvio del DOS nel sistema.
-          Puoi ora avviare DOS (e solamente DOS) dall'hard disk.
-          Alternativamente, puoi far ripartire il programma di installazione del
-          tuo boot manager da un floppy avviabile.</para>
-      </sect3>
-    </sect2>
-  </sect1>
-</article>
diff --git a/it_IT.ISO8859-15/htdocs/docs/books.sgml b/it_IT.ISO8859-15/htdocs/docs/books.sgml
index 09ef85e4a4..40b8540695 100644
--- a/it_IT.ISO8859-15/htdocs/docs/books.sgml
+++ b/it_IT.ISO8859-15/htdocs/docs/books.sgml
@@ -48,11 +48,6 @@
         Guida del Committer</a> (<tt>committers-guide</tt>)<br/>
       <small>Informazioni introduttive per i committer di FreeBSD.</small></p>
 
-    <p><a href="&url.articles;/euro/article.html">Il simbolo
-        dell'Euro su FreeBSD</a> (<tt>euro</tt>)<br/>
-      <small>Come configurare FreeBSD e le applicazioni relative per
-        visualizzare il simbolo dell'Euro.</small></p>
-
     <p><a href="&url.articles;/explaining-bsd/index.html">Panoramica
 	su BSD</a> (<tt>explaining-bsd</tt>)<br/>
       <small>Una risposta alla domanda ``Cos'è BSD?''</small></p>
@@ -62,11 +57,6 @@
       <small>Configurazione di firewall e packet filtering su host FreeBSD che
         fungono da bridge anziché da router.</small></p>
 
-    <p><a href="&url.articles;/multi-os/index.html">Utilizzo
-        di FreeBSD con altri Sistemi Operativi</a> (<tt>multi-os</tt>)<br/>
-      <small>Come installare FreeBSD insieme ad uno o più differenti sistemi
-        operativi sullo stesso computer.</small></p>
-
     <p><a href="&url.articles;/new-users/index.html">Primi
         Passi con FreeBSD</a> (<tt>new-users</tt>)<br/>
       <small>Per persone che arrivano a FreeBSD e &unix; per la prima
diff --git a/ja_JP.eucJP/articles/Makefile b/ja_JP.eucJP/articles/Makefile
index bfaff05e6d..59d7dacf69 100644
--- a/ja_JP.eucJP/articles/Makefile
+++ b/ja_JP.eucJP/articles/Makefile
@@ -2,10 +2,8 @@
 # Original revision: 1.47
 
 SUBDIR =
-#SUBDIR+= 5-roadmap
 #SUBDIR+= bsdl-gpl
 #SUBDIR+= casestudy-argentina.com
-#SUBDIR+= checkpoint
 #SUBDIR+= committers-guide
 #SUBDIR+= console-server
 SUBDIR+= contributing
@@ -13,14 +11,10 @@ SUBDIR+= contributing
 SUBDIR+= contributors
 #SUBDIR+= cvs-freebsd
 #SUBDIR+= cvsup-advanced
-SUBDIR+= dialup-firewall
-SUBDIR+= diskless-x
-#SUBDIR+= euro
 #SUBDIR+= explaining-bsd
 SUBDIR+= fbsd-from-scratch
 #SUBDIR+= filtering-bridges
 SUBDIR+= fonts
-#SUBDIR+= formatting-media
 #SUBDIR+= freebsd-questions
 #SUBDIR+= geom-class
 #SUBDIR+= hats
@@ -31,7 +25,6 @@ SUBDIR+= ipsec-must
 #SUBDIR+= linux-comparison
 #SUBDIR+= mailing-list-faq
 #SUBDIR+= mh
-SUBDIR+= multi-os
 #SUBDIR+= new-users
 #SUBDIR+= pam
 #SUBDIR+= portbuild
@@ -43,11 +36,8 @@ SUBDIR+= problem-reports
 #SUBDIR+= releng-packages
 #SUBDIR+= serial-uart
 #SUBDIR+= solid-state
-#SUBDIR+= storage-devices
-#SUBDIR+= version-guide
 #SUBDIR+= vinum
 #SUBDIR+= vm-design
-SUBDIR+= zip-drive
 
 # ROOT_SYMLINKS+= new-users
 
diff --git a/ja_JP.eucJP/articles/dialup-firewall/Makefile b/ja_JP.eucJP/articles/dialup-firewall/Makefile
deleted file mode 100644
index 23047691fe..0000000000
--- a/ja_JP.eucJP/articles/dialup-firewall/Makefile
+++ /dev/null
@@ -1,20 +0,0 @@
-#
-# $FreeBSD$
-#
-# Article: Dialup firewalling with FreeBSD
-#
-# Original revision: 1.5
-
-DOC?= article
-
-FORMATS?= html
-
-INSTALL_COMPRESSED?=gz
-INSTALL_ONLY_COMPRESSED?=
-
-SRCS=	article.sgml
-
-URL_RELPREFIX?=	../../../..
-DOC_PREFIX?=	${.CURDIR}/../../..
-
-.include "${DOC_PREFIX}/share/mk/doc.project.mk"
diff --git a/ja_JP.eucJP/articles/dialup-firewall/article.sgml b/ja_JP.eucJP/articles/dialup-firewall/article.sgml
deleted file mode 100644
index 9e8cd272e7..0000000000
--- a/ja_JP.eucJP/articles/dialup-firewall/article.sgml
+++ /dev/null
@@ -1,350 +0,0 @@
-<?xml version="1.0" encoding="euc-jp" standalone="no"?>
-<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V4.2-Based Extension//EN"
-	"../../../share/sgml/freebsd42.dtd" [
-<!ENTITY % entities PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Entity Set//JA" "../../share/sgml/entities.ent">
-%entities;
-]>
-
-<!--
-     The FreeBSD Documentation Project
-     The FreeBSD Japanese Documentation Project
-
-     Original revision: 1.40
-     $FreeBSD$
--->
-
-<!--
-Ìõ:
-ÁÒÉÊ rushani@bl.mmtr.or.jp
--->
-
-<article lang='ja'>
-  <articleinfo>
-    <title>FreeBSD ¤Ë¤è¤ë¥À¥¤¥¢¥ë¥¢¥Ã¥×¼°¥Õ¥¡¥¤¥¢¥¦¥©¡¼¥ë¤Î¹½ÃÛ</title>
-
-    <authorgroup>
-      <author>
-	<firstname>Marc</firstname>
-	<surname>Silver</surname>
-
-	<affiliation>
-	  <address><email>marcs@draenor.org</email></address>
-	</affiliation>
-      </author>
-    </authorgroup>
-
-    <legalnotice id="trademarks" role="trademarks">
-      &tm-attrib.freebsd;
-      &tm-attrib.general;
-    </legalnotice>
-
-    <pubdate>$FreeBSD$</pubdate>
-
-    <releaseinfo>$FreeBSD$</releaseinfo>
-
-    <abstract>
-      <para>
-        ¤³¤Îµ­»ö¤Ï FreeBSD ¤Î PPP ¥À¥¤¥¢¥ë¥¢¥Ã¥×¤È IPFW
-        ¤òÍѤ¤¤Ê¤¬¤é¤É¤Î¤è¤¦¤Ë¥Õ¥¡¥¤¥¢¥¦¥©¡¼¥ë¤ò¥»¥Ã¥È¥¢¥Ã¥×¤¹¤ë¤«¡¢
-	ÆäËưŪ¤Ë³ä¤êÅö¤Æ¤é¤ì¤¿
-	IP ¥¢¥É¥ì¥¹¤Ë¤è¤ë¥À¥¤¥¢¥ë¥¢¥Ã¥×¾å¤Î¥Õ¥¡¥¤¥¢¥¦¥©¡¼¥ë¤Ë¤Ä¤¤¤Æ¡¢
-	»ö¼Â¤ò¸µ¤Ë¾ÜºÙ¤ËÀâÌÀ¤·¤Þ¤¹¡£
-	¤Ê¤ª¡¢»Ï¤á¤Ë¤·¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤ PPP Àܳ¤ÎÀßÄê¤Ë¤Ä¤¤¤Æ¤Ï¿¨¤ì¤Æ
-	¤¤¤Þ¤»¤ó¡£PPP Àܳ¤ÎÀßÄê¤Ë¤Ä¤¤¤Æ¾Ü¤·¤¤¤³¤È¤Ï¡¢&man.ppp.8; ¤Î¥Þ
-	¥Ë¥å¥¢¥ë¤ò»²¹Í¤Ë¤·¤Æ¤¯¤À¤µ¤¤¡£</para>
-    </abstract>
-  </articleinfo>
-
-  <sect1 id="preface">
-    <title>½øʸ</title>
-
-    <para>FreeBSD ¤Ë¤è¤ë¥À¥¤¥¢¥ë¥¢¥Ã¥×¼°¥Õ¥¡¥¤¥¢¥¦¥©¡¼¥ë¤Î¹½ÃÛ</para>
-
-    <para>
-      ¤³¤Îʸ½ñ¤Ï¤¢¤Ê¤¿¤Î ISP ¤Ë¤è¤Ã¤Æ
-      IP ¥¢¥É¥ì¥¹¤¬Æ°Åª¤Ë³ä¤êÅö¤Æ¤é¤ì¤ë¾ì¹ç¤Ë¡¢FreeBSD ¤Ç
-      ¥Õ¥¡¥¤¥¢¥¦¥©¡¼¥ë¤òÀßÄꤹ¤ë¤Î¤ËɬÍפʼê½ç¤Î³µÎ¬¤ò½Ò¤Ù¤ë¤â¤Î¤Ç¤¹¡£
-      ¤³¤Îʸ½ñ¤ò²Äǽ¤Ê¸Â¤êÍ­±×¤ÇÀµ³Î¤Ê¤â¤Î¤Ë¤¹¤ë¤¿¤á¤ËÅØÎϤ·¤Æ¤¤¤ë¤Î¤Ç¡¢
-      ¤É¤¦¤¾½¤Àµ¡¢°Õ¸«¤äÄó°Æ¤ò¡¢
-      <email>marcs@draenor.org</email>
-      °¸¤ÇÃø¼Ô¤ËÁ÷¤Ã¤Æ²¼¤µ¤¤¡£</para>
-   </sect1>
-
-  <sect1 id="kernel">
-    <title>¥«¡¼¥Í¥ë¥ª¥×¥·¥ç¥ó</title>
-
-    <para>IPFW ¤ò»È¤¦¤¿¤á¤Ë¤Ï¡¢¤½¤ì¤ËÂбþ¤¹¤ë¤è¤¦¤Ë¥«¡¼¥Í¥ë¤ò
-      ¥³¥ó¥Ñ¥¤¥ë¤·¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£
-      ¥«¡¼¥Í¥ë¤òºÆ¥³¥ó¥Ñ¥¤¥ë¤¹¤ëÊýË¡¤Ë¤Ä¤¤¤Æ¤Î¤µ¤é¤Ê¤ë¾ðÊó¤Ï¡¢
-      <ulink url="&url.books.handbook;/kernelconfig.html">¥Ï¥ó¥É¥Ö¥Ã¥¯¤Î
-      ¥«¡¼¥Í¥ë¤Î¥³¥ó¥Õ¥£¥°¥ì¡¼¥·¥ç¥ó¤ÎÀá</ulink>¤ò¤´Í÷¤¯¤À¤µ¤¤¡£
-      IPFW ¤ËÂбþ¤¹¤ë¤Ë¤Ï¡¢¥«¡¼¥Í¥ë¤ÎÀßÄê¥Õ¥¡¥¤¥ë¤Ë°Ê²¼¤Î¥ª¥×¥·¥ç¥ó¤ò
-      Äɲ䷤ʤ±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£</para>
-
-    <variablelist>
-      <varlistentry>
-	<term><literal>options IPFIREWALL</literal></term>
-
-	<listitem>
-	  <para>¥«¡¼¥Í¥ë¤Î¥Õ¥¡¥¤¥¢¥¦¥©¡¼¥ë¤Î¥³¡¼¥É¤òÍ­¸ú¤Ë¤·¤Þ¤¹¡£</para>
-	  <note><para>¤³¤Îʸ½ñ¤Ç¤Ï¡¢&os; 5.X ¤òÆ°¤«¤·¤Æ¤¤¤ë¤È²¾Äꤷ¤Æ
-	    ¤¤¤Þ¤¹¡£&os; 4.X ¤òÆ°¤«¤·¤Æ¤¤¤ë¥æ¡¼¥¶¡¼¤Ï¡¢¥«¡¼¥Í¥ë¤ò
-	    <emphasis>IPFW2</emphasis> ¤ËÂбþ¤¹¤ë¤è¤¦
-	    ºÆ¥³¥ó¥Ñ¥¤¥ë¤·¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£&os; 4.X ¤Î¥æ¡¼¥¶¡¼¤Ï¡¢
-	    ¥·¥¹¥Æ¥à¤Ç IPFW2 ¤òÍøÍѤ¹¤ë¤¿¤á¤Î¾ÜºÙ¤Ï
-	    &man.ipfw.8; ¤Î¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤ò»²¹Í¤Ë¤·¤Æ¤¯¤À¤µ¤¤¡£Æäˡ¢
-	    <emphasis>USING IPFW2 IN FreeBSD-STABLE</emphasis>
-	    ¤È¤¤¤¦Àá¤ÏÃí°Õ¿¼¤¯Æɤó¤Ç¤¯¤À¤µ¤¤¡£</para></note>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-	<term><literal>options IPFIREWALL_VERBOSE</literal></term>
-
-	<listitem>
-	  <para>¥·¥¹¥Æ¥à¤Î logger ¤Øµ­Ï¿¤µ¤ì¤¿¥Ñ¥±¥Ã¥È¤òÁ÷¤ê¤Þ¤¹¡£</para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-	<term><literal>options
-	    IPFIREWALL_VERBOSE_LIMIT=<replaceable>500</replaceable></literal></term>
-
-	<listitem>
-	  <para>Åö¤Æ¤Ï¤Þ¤ë¥¨¥ó¥È¥ê¤¬µ­Ï¿¤µ¤ì¤¦¤ë¿ô¤òÀ©¸Â¤·¤Þ¤¹¡£
-	    ¤³¤ì¤Ï¡¢¥µ¡¼¥Ó¥¹ÉÔǽ (DoS) ¹¶·â¤¬µ¯¤­¤Æ¤â¡¢syslog ¤¬°î¤ì¤ë
-	    ´í¸±¤òÈò¤±¤Æ¡¢¥Õ¥¡¥¤¥¢¥¦¥©¡¼¥ë¤Î³èÆ°¤òµ­Ï¿¤Ç¤­¤ë¤è¤¦¤Ë¤·¤Þ¤¹¡£
-	    <replaceable>500</replaceable> ¤ÏÂÅÅö¤Ê¿ô¤Ç¤¹¤¬¡¢¤¢¤Ê¤¿¤Î
-	    Í×·ï¤Ë´ð¤Å¤¤¤ÆÄ´À°¤Ç¤­¤Þ¤¹¡£</para>
-	</listitem>
-      </varlistentry>
-    </variablelist>
-
-    <warning><para>¥«¡¼¥Í¥ë¤ÎºÆ¥³¥ó¥Ñ¥¤¥ë¤¬´°Î»¤·¤Æ¤â¡¢¥·¥¹¥Æ¥à¤ò
-      <emphasis>ºÆµ¯Æ°¤·¤Ê¤¤¤Ç</emphasis>²¼¤µ¤¤¡£
-      ¤½¤¦¤·¤Æ¤·¤Þ¤¦¤È¡¢·ë²ÌŪ¤Ë¥·¥¹¥Æ¥à¤«¤éÊĤá½Ð¤µ¤ì¤Æ¤·¤Þ¤¦
-      ²ÄǽÀ­¤¬¤¢¤ê¤Þ¤¹¡£¥ë¡¼¥ë¥»¥Ã¥È¤òŬÀÚ¤ËÇÛÃÖ¤·¡¢´ØÏ¢¤¹¤ëÀßÄê¥Õ¥¡¥¤¥ë¤ò
-      ¤¹¤Ù¤Æ¹¹¿·¤¹¤ë¤Þ¤Ç¤ÏºÆµ¯Æ°¤·¤Æ¤Ï¤¤¤±¤Þ¤»¤ó¡£</para></warning>
-  </sect1>
-
-  <sect1 id="rcconf">
-    <title>¥Õ¥¡¥¤¥¢¥¦¥©¡¼¥ë¤òÅëºÜ¤¹¤ë¤è¤¦¤Ë
-      <filename>/etc/rc.conf</filename> ¤òÊѹ¹¤¹¤ë</title>
-
-    <para>¥·¥¹¥Æ¥à¤Ç¥Õ¥¡¥¤¥¢¥¦¥©¡¼¥ë¤òÍ­¸ú¤Ë¤·¡¢¥ë¡¼¥ë¥Õ¥¡¥¤¥ë¤Î¤¢¤ê¤«¤ò
-      »ØÄꤹ¤ë¤¿¤á¤Ë <filename>/etc/rc.conf</filename>
-      ¤ò¼ã´³Êѹ¹¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
-      <filename>/etc/rc.conf</filename> ¤Ë°Ê²¼¤Î¹Ô¤ò²Ã¤¨¤Æ¤¯¤À¤µ¤¤¡£</para>
-
-    <programlisting>firewall_enable="YES"
-firewall_script="/etc/firewall/fwrules"</programlisting>
-
-    <para>
-      ¾åµ­¤ÎÀßÄê¤Ë´Ø¤¹¤ë¤è¤ê¾Ü¤·¤¤¾ðÊó¤Ï
-      <filename>/etc/defaults/rc.conf</filename> ¤ò»²¾È¤·¤¿¾å¤Ç¡¢
-      &man.rc.conf.5; ¤òÆɤó¤Ç²¼¤µ¤¤¡£</para>
-  </sect1>
-
-  <sect1>
-    <title>PPP ¤Î¥Í¥Ã¥È¥ï¡¼¥¯¥¢¥É¥ì¥¹ÊÑ´¹¤òÍ­¸ú¤Ë¤¹¤ë</title>
-
-    <para>¥Í¥Ã¥È¥ï¡¼¥¯Æâ¤Î¥¯¥é¥¤¥¢¥ó¥È¤¬¥²¡¼¥È¥¦¥§¥¤·Ðͳ¤ÇÀܳ¤Ç¤­¤ë
-      ¤è¤¦¤Ë¤¹¤ë¤Ë¤Ï¡¢PPP ¤Î¥Í¥Ã¥È¥ï¡¼¥¯¥¢¥É¥ì¥¹ÊÑ´¹ (NAT) ¤òÍ­¸ú¤Ë
-      ¤·¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£PPP ¤Î NAT µ¡Ç½¤òÍøÍѤ¹¤ë¤Ë¤Ï¡¢¼¡¤Î¹Ô¤ò
-      <filename>/etc/rc.conf</filename> ¤ËÄɲ䷤Ƥ¯¤À¤µ¤¤¡£</para>
-
-    <programlisting>ppp_enable="YES"
-ppp_mode="auto"
-ppp_nat="YES"
-ppp_profile="<replaceable>your_profile</replaceable>"</programlisting>
-
-    <note><para><literal>your_profile</literal> ¤ò¤¢¤Ê¤¿¼«¿È¤Î¥À¥¤¥¢¥ë
-      ¥¢¥Ã¥×¥×¥í¥Õ¥¡¥¤¥ë¤ËÊѹ¹¤¹¤ë¤è¤¦¤Ë¤·¤Æ¤¯¤À¤µ¤¤¡£</para></note>
-  </sect1>
-
-  <sect1 id="rules">
-    <title>¥Õ¥¡¥¤¥¢¥¦¥©¡¼¥ë¤Ø¤Î¥ë¡¼¥ë¥»¥Ã¥È</title>
-
-    <para>¤³¤³¤Ç¤¢¤Ê¤¿¤Î¥·¥¹¥Æ¥àÍѤΥե¡¥¤¥¢¥¦¥©¡¼¥ë¥ë¡¼¥ë¤òÄêµÁ¤·¤Þ¤¹¡£
-      »ä¤¿¤Á¤¬µ­½Ò¤¹¤ë¥ë¡¼¥ë¥»¥Ã¥È¤Ï¡¢ÂçÉôʬ¤Î¥À¥¤¥¢¥ë¥¢¥Ã¥×¥æ¡¼¥¶¸þ¤±¤Î
-      °ìÈÌŪ¤Ê¿÷·¿¤Ç¤¹¡£¥æ¡¼¥¶Ëè¤ÎÍ×µá¤Ë¤Ô¤Ã¤¿¤ê¹ç¤ï¤Ê¤¤¤Ç¤·¤ç¤¦¤¬¡¢IPFW
-      ¤ÎÆ°ºî¤Ë¤Ä¤¤¤Æ´ðËÜŪ¤ÊÍý²ò¤òÆÀ¤é¤ì¡¢Í×µá¤Ë¹ç¤ï¤»¤ÆÀßÄê¤òÊѹ¹¤¹¤ë
-      ¤Î¤Ï·ë¹½´Êñ¤Ê¤Ï¤º¤Ç¤¹¡£</para>
-
-    <para>¤Þ¤º¤Ï¡¢Êĺ¿Åª¤Ê¥Õ¥¡¥¤¥¢¥¦¥©¡¼¥ë¤Î´ðÁ䫤é»Ï¤á¤Þ¤·¤ç¤¦¡£Êĺ¿Åª¤Ê
-      ¥Õ¥¡¥¤¥¢¥¦¥©¡¼¥ë¤Ï¡¢ÀßÄ꤬¤Ê¤¤¾ì¹ç¤Ï¤¹¤Ù¤ÆµñÈݤ¹¤ë¤È¤¤¤¦¹Í¤¨¤Ë
-      ´ð¤Å¤¤¤Æ¤¤¤Þ¤¹¡£¤½¤ì¤«¤é¡¢´ÉÍý¼Ô¤Ïµö²Ä¤·¤¿¤¤ÄÌ¿®ÍѤΥ롼¥ë¤òÌÀ¼¨Åª¤Ë
-      ÄɲäǤ­¤Þ¤¹¡£ÄÌ¿®ÍѤΥ롼¥ë¤Ï¡¢µö²Ä¤¬Àè¤Ç¤½¤ì¤«¤éµñÈݤȤ¤¤¦
-      ½çÈ֤Ǥ¢¤ë¤Ù¤­¤Ç¤¹¡£µö²Ä¤·¤¿¤¤¤â¤Î¤¹¤Ù¤Æ¤Ë¤Ä¤¤¤Æ¥ë¡¼¥ë¤òÄɲ䷤ơ¢
-      ¤½¤ì°Ê³°¤Ï¤¹¤Ù¤Æ¼«Æ°Åª¤ËµñÈݤµ¤ì¤ë¤³¤È¤òÁ°Äó¤È¤·¤Þ¤¹¡£</para>
-
-    <para>¤½¤ì¤Ç¤Ï¡¢¥Õ¥¡¥¤¥¢¥¦¥©¡¼¥ë¤Î¥ë¡¼¥ë¤òÊݸ¤¹¤ë¥Ç¥£¥ì¥¯¥È¥ê¤ò
-      ºîÀ®¤·¤Þ¤·¤ç¤¦¡£¤³¤ÎÎã¤Ç¤Ï¡¢
-      <filename class="directory">/etc/firewall</filename> ¤òÍѤ¤¤Þ¤¹¡£
-      ¥Ç¥£¥ì¥¯¥È¥ê¤ò¤½¤³¤ØÊѹ¹¤·¡¢
-      <filename>rc.conf</filename> ¤Çµ¬Äꤷ¤¿
-      <filename>fwrules</filename> ¥Õ¥¡¥¤¥ë¤òÊÔ½¸¤·¤Þ¤¹¡£
-      ¤³¤Î¥Õ¥¡¥¤¥ë̾¤ò¼«Ê¬¤¬Ë¾¤àǤ°Õ¤Î¤â¤Î¤ËÊѹ¹¤Ç¤­¤ë¤È¤¤¤¦¤³¤È¤Ëµ¤¤ò¤Ä¤±¤Æ¤¯¤À¤µ¤¤¡£
-      ¤³¤Î¼ê°ú¤­¤Ï¤¢¤Ê¤¿¤¬»È¤ª¤¦¤È¤¹¤ë¤«¤â¤·¤ì¤Ê¤¤¥Õ¥¡¥¤¥ë̾¤Î°ìÎã¤ò
-      Í¿¤¨¤ë¤À¤±¤Ç¤¹¡£</para>
-
-    <para>¤½¤ì¤Ç¤Ï¡¢¤­¤Á¤ó¤ÈÃí¼á¤¬»Ü¤µ¤ì¤¿¥Õ¥¡¥¤¥¢¥¦¥©¡¼¥ë¥Õ¥¡¥¤¥ë¤Î
-      Îã¤ò¸«¤Æ¤ß¤Þ¤·¤ç¤¦¡£</para>
-
-    <programlisting># (/etc/rc.firewall ¤Ë¤¢¤ë¤è¤¦¤Ë) »²¾È¤ò´Êñ¤Ë¤¹¤ë¤¿¤á¤Ë¥Õ¥¡¥¤¥¢¥¦¥©¡¼¥ë¤Î
-# ¥³¥Þ¥ó¥É¤òÄêµÁ¤·¤Þ¤¹¡£Æɤߤ䤹¤¯¤¹¤ë¤Î¤ËÌòΩ¤Á¤Þ¤¹¡£
-fwcmd="/sbin/ipfw"
-
-# ³°¸þ¤±¥¤¥ó¥¿¥Õ¥§¡¼¥¹¤òÄêµÁ¤·¤Þ¤¹¡£¥æ¡¼¥¶¡¼¥é¥ó¥É ppp ¤Ç¤Ï¡¢
-# ²¿¤âÀßÄꤷ¤Ê¤¤¤È tun0 ¤Ë¤Ê¤ê¤Þ¤¹¡£
-oif="tun0"
-
-# Æâ¸þ¤±¥¤¥ó¥¿¥Õ¥§¡¼¥¹¤òÄêµÁ¤·¤Þ¤¹¡£Ä̾ï¤Ï¥Í¥Ã¥È¥ï¡¼¥¯¥«¡¼¥É¤Ë
-# ¤Ê¤ê¤Þ¤¹¡£¤³¤ì¤òɬ¤º¤¢¤Ê¤¿¤Î¥Í¥Ã¥È¥ï¡¼¥¯¥¤¥ó¥¿¥Õ¥§¡¼¥¹¤Ë
-# ¹ç¤ï¤»¤ÆÊѹ¹¤¹¤ë¤è¤¦¤Ë¤·¤Æ¤¯¤À¤µ¤¤¡£
-iif="fxp0"
-
-# ¥ë¡¼¥ë¤òºÆÆɹþ¤ß¤¹¤ëÁ°¤Ë¡¢¸½ºß¤Î¥ë¡¼¥ë¤ò¶¯À©Åª¤Ë¾Ãµî¤·¤Þ¤¹¡£
-$fwcmd -f flush
-
-# ¤¹¤Ù¤Æ¤Î¥Ñ¥±¥Ã¥È¤Î¾õÂÖ¤ò³Îǧ¤·¤Þ¤¹¡£
-$fwcmd add check-state
-
-# ³°¸þ¤±¥¤¥ó¥¿¥Õ¥§¡¼¥¹Â¦¤Ç¤Ê¤ê¤¹¤Þ¤·¤òËɤ®¤Þ¤¹¡£
-$fwcmd add deny ip from any to any in via $oif not verrevpath
-
-# »ä¤¿¤Á¤¬³«»Ï¤·¤¿Àܳ¤Ï¤¹¤Ù¤Æµö²Ä¤·¡¢¾õÂÖ¤òÊݸ¤·¤Þ¤¹¡£
-# ¤·¤«¤·¡¢Æ°Åª¤Ê¥ë¡¼¥ë¤ò»ý¤¿¤Ê¤¤³ÎΩ¤·¤¿Àܳ¤ÏµñÈݤ·¤Þ¤¹¡£
-$fwcmd add allow ip from me to any out via $oif keep-state
-$fwcmd add deny tcp from any to any established in via $oif
-
-# ¥Í¥Ã¥È¥ï¡¼¥¯Æâ¤ÎÀܳ¤Ï¤¹¤Ù¤Æµö²Ä¤·¤Þ¤¹¡£
-$fwcmd add allow ip from any to any via $iif
-
-# ¥í¡¼¥«¥ë¤ÊÄÌ¿®¤ò¤¹¤Ù¤Æµö²Ä¤·¤Þ¤¹¡£
-$fwcmd add allow all from any to any via lo0
-$fwcmd add deny all from any to 127.0.0.0/8
-$fwcmd add deny ip from 127.0.0.0/8 to any
-
-# ¥¤¥ó¥¿¡¼¥Í¥Ã¥È¦¤Î¥æ¡¼¥¶¤Ë 22 ÈÖ¤È 80 È֥ݡ¼¥È¤ØÀܳ¤¹¤ë¤³¤È¤ò
-# µö²Ä¤·¤Þ¤¹¡£¤³¤ÎÎã¤Ç¤Ï¡¢sshd ¤È¥¦¥§¥Ö¥µ¡¼¥Ð¤Ø¤ÎÀܳ¤òÆä˵ö²Ä¤·¤Æ¤¤¤Þ¤¹¡£
-$fwcmd add allow tcp from any to me dst-port 22,80 in via $oif setup keep-state
-
-# ICMP ¥Ñ¥±¥Ã¥È¤òµö²Ä¤·¤Þ¤¹¡£¥Û¥¹¥È¤ò ping(8) ¤Ë±þÅú¤µ¤»¤¿¤¯¤Ê¤±¤ì¤Ð¡¢
-# icmptypes ¤«¤é 8 ¤òºï½ü¤·¤Æ¤¯¤À¤µ¤¤¡£
-$fwcmd add allow icmp from any to any via $oif icmptypes 0,3,8,11,12
-
-# »Ä¤ê¤Î¤¹¤Ù¤Æ¤òµñÈݤ·¤Æµ­Ï¿¤·¤Þ¤¹¡£
-$fwcmd add deny log ip from any to any</programlisting>
-
-    <para>22 ÈÖ¤È 80 È֥ݡ¼¥È¤Ø¤ÎÀܳ¤Î¤ß¤òµö²Ä¤·¡¢¤½¤ì°Ê³°¤Ë»î¤ß¤é¤ì¤¿
-      Àܳ¤Ï¤¹¤Ù¤Æµ­Ï¿¤¹¤ë¡¢´°Á´¤Ëµ¡Ç½¤¹¤ë¥Õ¥¡¥¤¥¢¥¦¥©¡¼¥ë¤¬¤Ç¤­¤Þ¤·¤¿¡£
-      ¤³¤ì¤Ç°ÂÁ´¤ËºÆµ¯Æ°¤¹¤ë¤³¤È¤¬¤Ç¤­¡¢¥Õ¥¡¥¤¥¢¥¦¥©¡¼¥ë¤¬¼«Æ°Åª¤Ë
-      µ¯Æ°¤·¤Æ¥ë¡¼¥ë¥»¥Ã¥È¤¬Æɤ߹þ¤Þ¤ì¤ë¤Ï¤º¤Ç¤¹¡£
-      ¤â¤·¤³¤ì¤Ë²¿¤«´Ö°ã¤¤¤ò¸«¤Ä¤±¤¿¤ê¡¢²¿¤«ÌäÂê¤ËÅö¤¿¤Ã¤¿¤ê¡¢
-      ¤³¤Î¥Ú¡¼¥¸¤ò²þÁ±¤¹¤ëÄó°Æ¤¬¤¢¤ë¤Ê¤é¡¢
-      ¤É¤¦¤«»ä¤ËÅŻҥ᡼¥ë¤òÁ÷¤Ã¤Æ²¼¤µ¤¤¡£</para>
-  </sect1>
-
-  <sect1>
-    <title>¼ÁÌä</title>
-
-    <qandaset>
-      <qandaentry>
-        <question>
-	  <para>
-	    <errorname>limit 500 reached on entry 2800</errorname>
-	    ¤Î¤è¤¦¤Ê¥á¥Ã¥»¡¼¥¸¤¬½Ð¤¿¸å¡¢»ä¤Î¥Þ¥·¥ó¤Ï¤½¤Î¥ë¡¼¥ëÈÖ¹æ¤ËÂÐ
-	    ±þ¤¹¤ëµñÈݤµ¤ì¤¿¥Ñ¥±¥Ã¥È¤òµ­Ï¿¤·¤Ê¤¯¤Ê¤ê¤Þ¤·¤¿¡£
-	    ¥Õ¥¡¥¤¥¢¥¦¥©¡¼¥ë¤Ï¤Þ¤ÀÆ°ºî¤·¤Æ¤¤¤ë¤Î¤Ç¤·¤ç¤¦¤«?</para>
-        </question>
-
-	<answer>
-	  <para>ñ¤Ë¤½¤Î¥ë¡¼¥ë¤Î¥í¥°¥«¥¦¥ó¥È¤¬ºÇÂçÃͤË㤷¤¿
-	    ¤È¤¤¤¦¤³¤È¤ò°ÕÌ£¤·¤Æ¤¤¤Þ¤¹¡£¥ë¡¼¥ë¼«ÂΤϤޤÀµ¡Ç½¤·¤Æ¤¤¤Þ¤¹¤¬¡¢
-	    ¥í¥°¥«¥¦¥ó¥¿¤ò¥ê¥»¥Ã¥È¤¹¤ë¤Þ¤Ç¤½¤ì°Ê¾å¥í¥°¤òµ­Ï¿¤·¤Þ¤»¤ó¡£
-	    ¥«¥¦¥ó¥¿¤Î¥ê¥»¥Ã¥ÈÊýË¡¤ÎÎã¤ò°Ê²¼¤Ë¼¨¤·¤Þ¤¹¡£</para>
-<screen>&prompt.root; <userinput>ipfw resetlog</userinput></screen>
-	  <para>¤Þ¤¿¡¢¤³¤Î¸Â³¦Ãͤò¾å½Ò¤Î
-	    <option>IPFIREWALL_VERBOSE_LIMIT</option> ¥ª¥×¥·¥ç¥ó¤Ç
-	    Êѹ¹¤¹¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹¡£
-	    ¤µ¤é¤Ë¡¢¤³¤Î¸Â³¦ÃÍ¤Ï (¥«¡¼¥Í¥ë¤òºÆ¹½ÃÛ¤·¤ÆºÆµ¯Æ°¤»¤º¤Ë)
-	    &man.sysctl.8; ¤Î net.inet.ip.fw.verbose_limit ÊÑ¿ô¤Ë¤è¤ê
-	    Êѹ¹¤¹¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹¡£</para>
-        </answer>
-      </qandaentry>
-
-      <qandaentry>
-	<question>
-	  <para>
-	    ²¿¤«´Ö°ã¤Ã¤Æ¤¤¤ë¤Ë°ã¤¤¤¢¤ê¤Þ¤»¤ó¡£
-	    »ä¤Ï¤¢¤Ê¤¿¤ÎÀâÌÀ¤Ëʸ»úÄ̤꽾¤¤¤Þ¤·¤¿¤¬¡¢
-	    Äù¤á½Ð¤µ¤ì¤Æ¤·¤Þ¤¤¤Þ¤·¤¿¡£</para>
-        </question>
-
-	<answer>
-	  <para>
-	    ¤³¤Î¥Á¥å¡¼¥È¥ê¥¢¥ë¤Ï¤¢¤Ê¤¿¤¬
-	    <emphasis>userland-ppp</emphasis>
-	    ¤ò²ÔƯ¤·¤Æ¤¤¤Æ¡¢¤½¤Î·ë²Ì
-	    <devicename>tun0</devicename>
-	    [&man.ppp.8; (¤Þ¤¿¤Î̾¤ò <emphasis>user-ppp</emphasis>)
-	    ¤Çºî¤é¤ì¤ëºÇ½é¤ÎÀܳ¤ËÁêÅö¤·¤Þ¤¹]
-	    ¥¤¥ó¥¿¥Õ¥§¡¼¥¹¾å¤Ç¶¡µë¤µ¤ì¤¿¥ë¡¼¥ë¥»¥Ã¥È¤¬Æ°ºî¤·¤Æ¤¤¤ë¤³¤È¤òÁÛÄꤷ¤Æ¤¤¤Þ¤¹¡£
-	    ¤µ¤é¤Ê¤ëÀܳ¤Ï
-	    <devicename>tun1</devicename>¡¢<devicename>tun2</devicename>
-	    ¤Ê¤É¤òÍѤ¤¤Þ¤¹¡£</para>
-
-	  <para>
-	    &man.pppd.8; ¤¬
-	    <devicename>ppp0</devicename>
-	    ¥¤¥ó¥¿¥Õ¥§¡¼¥¹¤òÂå¤ï¤ê¤ËÍѤ¤¤ë¤È¤¤¤¦¤³¤È¤Ë¤âÃí°Õ¤¹¤ë¤¹¤Ù¤­¤Ç¤¹¡£
-	    ¤è¤Ã¤Æ &man.pppd.8; ¤Ë¤è¤ëÀܳ¤ò»Ï¤á¤ë¤Ê¤é
-	    <devicename>ppp0</devicename> ¤ÎÂå¤ï¤ê¤Ë
-	    <devicename>tun0</devicename> ¤òÍѤ¤¤Æ²¼¤µ¤¤¡£
-	    ¤³¤ÎÊѹ¹¤òÈ¿±Ç¤¹¤ë¥Õ¥¡¥¤¥¢¥¦¥©¡¼¥ë¤Î¥ë¡¼¥ë¤ò
-	    ÊÔ½¸¤¹¤ëÁáÆ»¤Ï°Ê²¼¤Ë¼¨¤µ¤ì¤Æ¤¤¤Þ¤¹¡£
-	    ¸µ¤Î¥ë¡¼¥ë¥»¥Ã¥È¤Ï <filename>fwrules_tun0</filename>
-	    ¤È¤·¤Æ¥Ð¥Ã¥¯¥¢¥Ã¥×¤µ¤ì¤Æ¤¤¤Þ¤¹¡£</para>
-
-	  <screen>	    &prompt.user; <userinput>cd /etc/firewall</userinput>
-	    /etc/firewall&prompt.user; <userinput>su</userinput>
-	    <prompt>Password:</prompt>
-	    /etc/firewall&prompt.root; <userinput>mv fwrules fwrules_tun0</userinput>
-	    /etc/firewall&prompt.root; <userinput>cat fwrules_tun0 | sed s/tun0/ppp0/g > fwrules</userinput>
-	  </screen>
-
-	  <para>
-	    ¤¤¤Ã¤¿¤óÀܳ¤¬³ÎΩ¤·¤¿¤é¡¢
-	    ¸½ºß &man.ppp.8; ¤« &man.pppd.8; ¤Î¤É¤Á¤é¤òÍøÍѤ·¤Æ¤¤¤ë¤«¤òÃΤ뤿¤á¤Ë
-	    &man.ifconfig.8; ¤Î½ÐÎϤǸ¡ºº¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
-	    Îã¤È¤·¤Æ¡¢&man.pppd.8; ¤ÇºîÀ®¤µ¤ì¤¿Àܳ¤Ç¤Ï¡¢
-	    ¤³¤Î¤è¤¦¤Ê¤â¤Î¤¬Ìܤˤ¹¤ë¤Ç¤·¤ç¤¦
-	    (´Ø·¸¤Î¤¢¤ë¤â¤Î¤À¤±¼¨¤·¤Æ¤¤¤Þ¤¹)¡£</para>
-
-	  <screen>	    &prompt.user; <userinput>ifconfig</userinput>
-	    <emphasis>(skipped...)</emphasis>
-	    ppp0: flags=<replaceable>8051&lt;UP,POINTOPOINT,RUNNING,MULTICAST&gt; mtu 1524</replaceable>
-                    inet <replaceable>xxx.xxx.xxx.xxx</replaceable> --&gt; <replaceable>xxx.xxx.xxx.xxx</replaceable> netmask <replaceable>0xff000000</replaceable>
-	    <emphasis>(skipped...)</emphasis>
-	    </screen>
-
-	  <para>
-	    ¾Êý¤Ç¡¢&man.ppp.8; (<emphasis>user-ppp</emphasis>)
-	    ¤ÇºîÀ®¤µ¤ì¤¿Àܳ¤Ç¤Ï¡¢
-	    ¤¢¤Ê¤¿¤Ï¤³¤ì¤Ë»÷¤¿¤â¤Î¤òÌܤˤ¹¤ë¤Ï¤º¤Ç¤¹¡£</para>
-
-	  <screen>	    &prompt.user; <userinput>ifconfig</userinput>
-	    <emphasis>(skipped...)</emphasis>
-	    ppp0: flags=<replaceable>8010&lt;POINTOPOINT,MULTICAST&gt; mtu 1500</replaceable>
-	    <emphasis>(skipped...)</emphasis>
-	    tun0: flags=<replaceable>8051&lt;UP,POINTOPOINT,RUNNING,MULTICAST&gt; mtu 1524</replaceable>
-	            <emphasis>(IPv6 stuff skipped...)</emphasis>
-                    inet <replaceable>xxx.xxx.xxx.xxx</replaceable> --&gt; <replaceable>xxx.xxx.xxx.xxx</replaceable> netmask <replaceable>0xffffff00</replaceable>
-                    Opened by PID <replaceable>xxxxx</replaceable>
-            <emphasis>(skipped...)</emphasis></screen>
-	</answer>
-      </qandaentry>
-    </qandaset>
-  </sect1>
-</article>
diff --git a/ja_JP.eucJP/articles/diskless-x/Makefile b/ja_JP.eucJP/articles/diskless-x/Makefile
deleted file mode 100644
index 4a33b0d45d..0000000000
--- a/ja_JP.eucJP/articles/diskless-x/Makefile
+++ /dev/null
@@ -1,19 +0,0 @@
-#
-# $FreeBSD$
-#
-# Article: Diskless X Server: a how to guide
-#
-# Original revision: 1.8
-
-DOC?= article
-
-FORMATS?= html
-
-INSTALL_COMPRESSED?=gz
-INSTALL_ONLY_COMPRESSED?=
-
-SRCS=	article.sgml
-
-DOC_PREFIX?= ${.CURDIR}/../../..
-
-.include "${DOC_PREFIX}/share/mk/doc.project.mk"
diff --git a/ja_JP.eucJP/articles/diskless-x/article.sgml b/ja_JP.eucJP/articles/diskless-x/article.sgml
deleted file mode 100644
index 7309def020..0000000000
--- a/ja_JP.eucJP/articles/diskless-x/article.sgml
+++ /dev/null
@@ -1,387 +0,0 @@
-<?xml version="1.0" encoding="euc-jp" standalone="no"?>
-<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V4.2-Based Extension//EN"
-	"../../../share/sgml/freebsd42.dtd" [
-<!ENTITY % entities PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Entity Set//JA" "../../share/sgml/entities.ent">
-%entities;
-]>
-
-<!--
-    The FreeBSD Documentation Project
-    The FreeBSD Japanese Documentation Project
-
-    Original revision: 1.17
-    $FreeBSD$
--->
-
-<!--
-Ìõ:
-°ìµÜ μ ryo@azusa.shinshu-u.ac.jp
-¿ù¼ µ®»Î sugimura@jp.FreeBSD.org
--->
-
-<article lang='ja'>
-  <articleinfo>
-    <title>¥Ç¥£¥¹¥¯Ìµ¤·¤Î X ¥µ¡¼¥Ð: °ì¤Ä¤Î¥¬¥¤¥É</title>
-
-    <authorgroup>
-      <author>
-	<firstname>Jerry</firstname>
-
-	<surname>Kendall</surname>
-
-	<affiliation>
-	  <address>
-	    <email>jerry@kcis.com</email>
-	  </address>
-	</affiliation>
-      </author>
-    </authorgroup>
-
-    <pubdate>1996/12/28</pubdate>
-
-    <copyright>
-      <year>1996</year>
-      <holder>Jerry Kendall</holder>
-    </copyright>
-
-    <legalnotice id="trademarks" role="trademarks">
-      &tm-attrib.freebsd;
-      &tm-attrib.3com;
-      &tm-attrib.microsoft;
-      &tm-attrib.sun;
-      &tm-attrib.general;
-    </legalnotice>
-
-    <releaseinfo>$FreeBSD$</releaseinfo>
-
-    <abstract>
-      <para>FreeBSD-hackers ¥á¡¼¥ê¥ó¥°¥ê¥¹¥È¤Îͧ¿Í¤¿¤Á¤Î½õ¤±¤Ë¤è¤Ã¤Æ¡¢
-	¤ï¤¿¤·¤Ï¥Ç¥£¥¹¥¯¤Î̵¤¤ X üËö¤òºî¤ë¤³¤È¤¬¤Ç¤­¤Þ¤·¤¿¡£
-	X üËö¤ÎºîÀ®¤Ë¤Ï¡¢NFS ¤Ë¤è¤Ã¤Æ¥Þ¥¦¥ó¥È¤µ¤ì¤¿ºÇ¾®¤Î¥æ¡¼¥Æ¥£¥ê¥Æ¥£¤ò»ý¤Ä
-	¥Ç¥£¥¹¥¯Ìµ¤·¤Î¥·¥¹¥Æ¥à¤òºî¤é¤Ê¤¯¤Æ¤Ï¤Ê¤ê¤Þ¤»¤ó¤Ç¤·¤¿¡£
-	Ʊ¤¸ÊýË¡¤ò»È¤Ã¤Æ 2 ¤Ä¤ÎÊÌ¡¹¤Ê¥Ç¥£¥¹¥¯Ìµ¤·¤Î¥·¥¹¥Æ¥à¤òºî¤ê¤Þ¤·¤¿¡£
-	°ì¤ÄÌÜ¤Ï <hostid role="fqdn">altair.example.com</hostid> ¤Ç¤¹¡£
-	¤½¤ì¤Ï 340M ¤Î¥Ï¡¼¥É¥Ç¥£¥¹¥¯¤¬ÉÕ¤¤¤Æ¤¤¤Þ¤¹¤¬¡¢¸ò´¹¤·¤¿¤¯¤¢¤ê¤Þ¤»¤ó¤Ç¤·¤¿¡£
-	¤½¤Î¤¿¤á¡¢¤½¤Î¥Þ¥·¥ó¤Ï <hostid role="fqdn">antares.example.com</hostid>
-	¤«¤é¥¤¡¼¥µ¥Í¥Ã¥È¤òÄ̤¸¤Æ¥Ö¡¼¥È¤¹¤ë¤è¤¦¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£
-	2 ¤ÄÌܤΥ·¥¹¥Æ¥à¤Ï 486DX2-66 ¤Ç¤¹¡£
-	¤ï¤¿¤·¤ÏÁ´¤¯¥í¡¼¥«¥ë¥Ç¥£¥¹¥¯¤Î¤Ê¤¤¥Ç¥£¥¹¥¯Ìµ¤·¤Î FreeBSD ¤ò (´°àú¤Ë)
-	¥»¥Ã¥È¥¢¥Ã¥×¤·¤Þ¤·¤¿¡£
-	¤½¤Î¾ì¹ç¤Î¥µ¡¼¥Ð¤Ï &sunos; 4.1.3 ¤¬Æ°¤¤¤Æ¤¤¤ë Sun 670MP ¤Ç¤¹¡£
-	¥»¥Ã¥È¥¢¥Ã¥×¤ÎÀßÄê¤ÏξÊý¤ËƱ¤¸¤â¤Î¤¬É¬ÍפǤ·¤¿¡£</para>
-
-      <para>¤ï¤¿¤·¤Ï¤³¤Îʸ½ñ¤Ë²Ã¤¨¤Ê¤¯¤Æ¤Ï¤Ê¤é¤Ê¤¤ÆâÍƤ¬¤Þ¤À¤¢¤ë¤È»×¤Ã¤Æ¤¤¤Þ¤¹¡£
-	¤É¤ó¤Ê¤³¤È¤Ç¤â¤´°Õ¸«¤¬¤¢¤ê¤Þ¤·¤¿¤éÁ÷¤Ã¤Æ¤¯¤À¤µ¤¤¡£</para>
-    </abstract>
-  </articleinfo>
-
-  <sect1>
-    <title>¥Ö¡¼¥È¥Õ¥í¥Ã¥Ô¡¼¤òºî¤ë (¥Ç¥£¥¹¥¯Ìµ¤·¤Î¥·¥¹¥Æ¥à¾å¤Ç)</title>
-
-    <para>¥Í¥Ã¥È¥ï¡¼¥¯¥í¡¼¥À¤Ï TSR ¤Ê¤É¤Î
-      &ms-dos; ¤¬»È¤¦¤â¤Î¤¬¤¢¤ë¤È¤¦¤Þ¤¯Æ¯¤«¤Ê¤¤¤³¤È¤¬¤¢¤ë¤Î¤Ç¡¢
-      ºÇ¤âÎɤ¤ÊýË¡¤ÏÀìÍѤΥ֡¼¥È¥Õ¥í¥Ã¥Ô¡¼¤òºî¤ë¤«¡¢
-      ¤â¤·¤Ç¤­¤ì¤Ð¡¢&ms-dos;
-      ¤Î¥á¥Ë¥å¡¼¤òºî¤Ã¤Æ¥·¥¹¥Æ¥à¤¬µ¯Æ°¤¹¤ë¤È¤­¤Ë¤É¤ÎÀßÄê¤òÍ­¸ú¤Ë¤¹¤ë¤«¤òʹ¤¤¤Æ¤¯¤ë¤è¤¦¤Ë¤¹¤ë¤³¤È¤Ç¤¹¡£
-      (<filename>config.sys</filename>/<filename>autoexec.bat</filename>
-      ¥Õ¥¡¥¤¥ë¤Ë¤è¤Ã¤Æ)
-      ¼¡¤Ëµó¤²¤ë¤Î¤Ï¤ï¤¿¤·¤¬»È¤Ã¤Æ¤¤¤ë¤â¤Î¤Ç¡¢¤Á¤ã¤ó¤ÈÆ°ºî¤·¤Æ¤¤¤ë¤â¤Î¤Ç¤¹¡£
-      ¤ï¤¿¤·¤Î &ms-dos; (6.x) ¥á¥Ë¥å¡¼¤ò²¼¤ËºÜ¤»¤Þ¤¹¡£</para>
-
-    <example>
-      <title><filename>config.sys</filename></title>
-
-      <programlisting>[menu]
-menuitem=normal, normal
-menuitem=unix, unix
-[normal]
-....
-normal config.sys stuff
-...
-[unix]</programlisting>
-    </example>
-
-    <example>
-      <title><filename>autoexec.bat</filename></title>
-
-      <programlisting>@ECHO OFF
-goto %config%
-
-:normal
-...
-normal autoexec.bat stuff
-...
-goto end
-
-:unix
-cd \netboot
-nb8390.com
-
-:end</programlisting>
-    </example>
-  </sect1>
-
-  <sect1>
-    <title>¥Í¥Ã¥È¥ï¡¼¥¯¥Ö¡¼¥È¤Î¥×¥í¥°¥é¥à¤ò¼ê¤ËÆþ¤ì¤ë (¥µ¡¼¥Ð¾å¤Ç)</title>
-
-    <para><filename>/usr/src/sys/i386/boot/netboot</filename> ¤Ë¤¢¤ë
-      <quote>net-boot</quote> ¥×¥í¥°¥é¥à¤ò¥³¥ó¥Ñ¥¤¥ë¤·¤Æ¤¯¤À¤µ¤¤¡£
-      ¤½¤Î¤È¤­¤Ë¤Ï
-      <filename>Makefile</filename>
-      ¤ÎÀèƬ¤Ë¤¢¤ë¥³¥á¥ó¥È¤òÆɤó¤Ç¤ª¤­¤Þ¤·¤ç¤¦¡£
-      Í׵ᤵ¤ì¤ë¤è¤¦¤ËÄ´À°¤·¤Æ¤¯¤À¤µ¤¤¡£
-      Ç°¤Î¤¿¤á¤Ë¡¢¥ª¥ê¥¸¥Ê¥ë¤Î¥Õ¥¡¥¤¥ë¤Ï¤É¤³¤«¤Ë¥Ð¥Ã¥¯¥¢¥Ã¥×¤ò¼è¤Ã¤Æ¤ª¤¤¤Æ¤¯¤À¤µ¤¤¡£
-      ¥Ó¥ë¥É¤¬½ª¤ï¤Ã¤¿¤é¡¢2 ¤Ä¤Î &ms-dos; ¤Î¼Â¹Ô¥Õ¥¡¥¤¥ë
-      <filename>nb8390.com</filename> ¤È <filename>nb3c509.com</filename>
-      ¤¬¤Ç¤­¤Æ¤¤¤ë¤Ï¤º¤Ç¤¹¡£
-      ¤³¤ì¤é¤Î 2 ¤Ä¤Î¥×¥í¥°¥é¥à¤Î 1 ¤Ä¤Ï¥Ç¥£¥¹¥¯Ìµ¤·¤Î¥µ¡¼¥Ð¾å¤ÇÆ°¤«¤¹¤Î¤ËɬÍפˤʤë¤â¤Î¤Ç¤¹¡£
-      ¤½¤ì¤Ï¥Ö¡¼¥È¥µ¡¼¥Ð¤«¤é¥«¡¼¥Í¥ë¤ò¥í¡¼¥É¤¹¤ë¤â¤Î¤Ç¤¹¡£
-      ¤³¤³¤Ç¤ÏξÊý¤Î¥×¥í¥°¥é¥à¤òÀèÄøºî¤Ã¤¿
-      &ms-dos; ¤Î¥Ö¡¼¥È¥Õ¥í¥Ã¥Ô¡¼¤ËÆþ¤ì¤Æ¤ª¤­¤Þ¤¹¡£</para>
-  </sect1>
-
-  <sect1>
-    <title>¤É¤Î¥×¥í¥°¥é¥à¤ò¼Â¹Ô¤¹¤ë¤«¤òÄ´¤Ù¤ë (¥Ç¥£¥¹¥¯Ìµ¤·¤Î¥·¥¹¥Æ¥à¾å¤Ç)</title>
-
-    <para>¤â¤·¤¢¤Ê¤¿¤Î¥¤¡¼¥µ¥Í¥Ã¥È¥¢¥À¥×¥¿¤¬»È¤Ã¤Æ¤¤¤ë¥Á¥Ã¥×¥»¥Ã¥È¤òÃΤäƤ¤¤ë¤Ê¤é¡¢
-      ¤³¤ì¤Ï´Êñ¤Ê¤³¤È¤Ç¤¹¡£¤â¤·¤½¤ì¤¬ NS8390 ¥Á¥Ã¥×¥»¥Ã¥È¤«¡¢
-      NS8390 ¤ò¥Ù¡¼¥¹¤È¤¹¤ë¥Á¥Ã¥×¥»¥Ã¥È¤Ç¤¢¤ì¤Ð¡¢<filename>nb8390.com</filename>
-      ¤ò»È¤Ã¤Æ¤¯¤À¤µ¤¤¡£¤â¤· &tm.3com; 509 ¤ò¥Ù¡¼¥¹¤È¤¹¤ë¥Á¥Ã¥×¥»¥Ã¥È¤Ê¤é¡¢
-      <filename>nb3C509.com</filename> ¥Ö¡¼¥È¥×¥í¥°¥é¥à¤ò»È¤Ã¤Æ¤¯¤À¤µ¤¤¡£
-      ¤â¤·¤¢¤Ê¤¿¤Î»ý¤Ã¤Æ¤¤¤ë¤â¤Î¤¬¤è¤¯¤ï¤«¤é¤Ê¤±¤ì¤Ð¡¢°ì¤Ä»î¤·¤Æ¤ß¤Æ¡¢¤½¤³¤Ç
-      <errorname>No adapter found</errorname>
-      ¤È¸À¤ï¤ì¤¿¤é¤Þ¤¿Â¾¤Î¤ò»î¤·¤Æ¤ß¤Æ¤¯¤À¤µ¤¤¡£¤½¤ì¤Ç¤â¤À¤á¤À¤Ã¤¿¤é¡¢
-      ¤¢¤Ê¤¿¤Î¤â¤Î¤Ï¤È¤Æ¤âÄÁ¤·¤¤¤È¤¤¤¦¤³¤È¤Ç¤¹¡£</para>
-  </sect1>
-
-  <sect1>
-    <title>¥Í¥Ã¥È¥ï¡¼¥¯¤ÈÄ̤¸¤Æ¥Ö¡¼¥È¤¹¤ë</title>
-
-    <para>config.sys/autoexec.bat
-      ¥Õ¥¡¥¤¥ë¤â»È¤ï¤º¤Ë¥Ç¥£¥¹¥¯Ìµ¤·¤Î¥·¥¹¥Æ¥à¤òΩ¤Á¾å¤²¤Æ¤ß¤Æ¤¯¤À¤µ¤¤¡£
-      ¤¢¤Ê¤¿¤Î¥¤¡¼¥µ¥Í¥Ã¥È¥¢¥À¥×¥¿¤Î¤¿¤á¤Î¥Ö¡¼¥È¥×¥í¥°¥é¥à¤ò¼Â¹Ô¤·¤Æ¤ß¤Þ¤·¤ç¤¦¡£</para>
-
-    <para>¤ï¤¿¤·¤Î¥¤¡¼¥µ¥Í¥Ã¥È¥¢¥À¥×¥¿¤Ï WD8013 16bit ¥â¡¼¥É¤ÇÆ°¤¤¤Æ¤¤¤ë¤Î¤Ç
-      <filename>nb8390.com</filename> ¤ò¼Â¹Ô¤·¤Þ¤¹¡£</para>
-
-    <screen><prompt>C:&gt;</prompt> <userinput>cd \netboot</userinput>
-<prompt>C:&gt;</prompt> <userinput>nb8390</userinput>
-
-<prompt>Boot from Network (Y/N) ?</prompt>  <userinput>Y</userinput>
-
-BOOTP/TFTP/NFS bootstrap loader     ESC for menu
-
-Searching for adapter..
-WD8013EBT base 0x0300, memory 0x000D8000, addr 00:40:01:43:26:66
-
-Searching for server...</screen>
-
-    <para>¤³¤³¤Ç¤Ï¡¢
-      ¤ï¤¿¤·¤Î¥Ç¥£¥¹¥¯Ìµ¤·¤Î¥·¥¹¥Æ¥à¤Ï¥Ö¡¼¥È¥µ¡¼¥Ð¤È¤·¤Æ¿¶¤ëÉñ¤¦¤è¤¦¤Ê¥Þ¥·¥ó¤òõ¤·¤Ë¤¤¤³¤¦¤È¤·¤Þ¤¹¡£
-      ¾å¤Î <literal>addr</literal> ¹Ô¤òµ­Ï¿¤·¤Æ¤ª¤¤¤Æ¤¯¤À¤µ¤¤¡£
-      ¤¢¤È¤«¤é¤½¤Î¿ô¤¬É¬Íפˤʤê¤Þ¤¹¡£¥Ç¥£¥¹¥¯Ìµ¤·¤Î¥·¥¹¥Æ¥à¤òºÆµ¯Æ°¤·¤Æ¡¢
-      ¤¢¤Ê¤¿¤Î <filename>config.sys</filename> ¤ä
-      <filename>autoexec.bat</filename> ¥Õ¥¡¥¤¥ë¤ò½¤Àµ¤·¤Æ
-      ¤³¤ì¤é¤ÎÁàºî¤¬¼«Æ°¤Ç¹Ô¤ï¤ì¤ë¤è¤¦¤Ë¤·¤Æ¤¯¤À¤µ¤¤¡£
-      ¤ª¤½¤é¤¯¥á¥Ë¥å¡¼¤ÎÉôʬ¤Ë¤Ê¤ë¤Ç¤·¤ç¤¦¡£
-      ¤â¤· <command>nb3c509.com</command> ¤ò
-      <command>nb8390.com</command>
-      ¤ÎÂå¤ï¤ê¤Ë»È¤ï¤Ê¤¯¤Æ¤Ï¤¤¤±¤Ê¤«¤Ã¤¿¤È¤·¤Æ¤â¡¢½ÐÎϤϾå¤ÈƱ¤¸¤Ç¤¹¡£
-      ¤â¤· <literal>Searching for adapter..</literal>
-      ¤È¤¤¤¦¥á¥Ã¥»¡¼¥¸¤¬½Ð¤ë¤È¤­¤Ë
-      <errorname>No adapter found</errorname> ¤È¤¤¤¦¤³¤È¤ò¸À¤ï¤ì¤¿¤é¡¢
-      <filename>Makefile</filename>
-      ¤ÇÄêµÁ¤µ¤ì¤Æ¤¤¤ë¥³¥ó¥Ñ¥¤¥ë»þ´Ö¤¬Àµ¤·¤¯¥»¥Ã¥È¤µ¤ì¤Æ¤¤¤ë¤«¤É¤¦¤«¤ò³Îǧ¤·¤Æ¤ß¤Æ¤¯¤À¤µ¤¤¡£</para>
-  </sect1>
-
-  <sect1>
-    <title>¥·¥¹¥Æ¥à¤¬¥Í¥Ã¥È¥ï¡¼¥¯±Û¤·¤Ë¥Ö¡¼¥È¤¹¤ë¤³¤È¤òµö²Ä¤¹¤ë (¥µ¡¼¥Ð¾å¤Ç)</title>
-
-    <para><filename>/etc/inetd.conf</filename> ¥Õ¥¡¥¤¥ë¤¬ tftp ¤ä
-      bootps ¤Ë¤Ä¤¤¤Æ¤Î¥¨¥ó¥È¥ê¤ò»ý¤Ã¤Æ¤¤¤ë¤«¤É¤¦¤«¤ò³Îǧ¤·¤Æ¤¯¤À¤µ¤¤¡£
-      ¤ï¤¿¤·¤Î¤Ï¼¡¤Î¤è¤¦¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£</para>
-
-    <programlisting>tftp	dgram	udp	wait	nobody	/usr/libexec/tftpd	tftpd /tftpboot
-#
-# Additions by who ever you are
-bootps  dgram  udp  wait  root  /usr/libexec/bootpd bootpd /etc/bootptab</programlisting>
-
-    <para>¤â¤· <filename>/etc/inetd.conf</filename> ¥Õ¥¡¥¤¥ë¤òÊѹ¹¤·¤¿¤È¤­¤Ë¤Ï¡¢
-      &man.inetd.8; ¤Ë <literal>HUP</literal> ¥·¥°¥Ê¥ë¤òÁ÷¤Ã¤Æ¤¯¤À¤µ¤¤¡£
-      ¤³¤ì¤ò¤¹¤ë¤Ë¤Ï¡¢<command>inetd</command> ¤Î¥×¥í¥»¥¹ ID ¤ò
-      <command>ps -ax | grep inetd | grep -v grep</command> ¤·¤Æ
-      ¼èÆÀ¤·¤Æ¤¯¤À¤µ¤¤¡£¥×¥í¥»¥¹ ID ¤¬¤ï¤«¤Ã¤¿¤é¡¢
-      ¤½¤ì¤Ë¸þ¤±¤Æ HUP ¥·¥°¥Ê¥ë¤òÁ÷¤Ã¤Æ¤¯¤À¤µ¤¤¡£
-      ¤³¤ì¤Ï <command>kill -HUP &lt;pid&gt;</command> ¤È¤·¤Æ¹Ô¤¤¤Þ¤¹¡£
-      ¤³¤ì¤Ë¤è¤Ã¤Æ <command>inetd</command> ¤Ï¤½¤ÎÀßÄê¥Õ¥¡¥¤¥ë¤òÆɤßľ¤·¤Þ¤¹¡£</para>
-
-    <para>¥Ç¥£¥¹¥¯Ìµ¤·¥·¥¹¥Æ¥à¾å¤Ç¥Ö¡¼¥È¥í¡¼¥À¤¬½ÐÎϤ·¤¿ <literal>addr</literal>
-      ¤Î½ÐÎϤò³Ð¤¨¤Æ¤¤¤ë¤Ç¤·¤ç¤¦¤«? ¤³¤³¤Ç¤½¤ì¤¬É¬ÍפȤʤë¤Î¤Ç¤¹¡£</para>
-
-    <para><filename>/etc/bootptab</filename> (¤ª¤½¤é¤¯¥Õ¥¡¥¤¥ë¤òºîÀ®¤·¤Æ) ¤Ë
-      ¥¨¥ó¥È¥ê¤ò²Ã¤¨¤Æ¤¯¤À¤µ¤¤¡£¤½¤ì¤Ï¤³¤ì¤ÈƱÍͤνñ¼°¤Ç½ñ¤­¤Þ¤·¤ç¤¦¡£</para>
-
-    <programlisting>altair:\
-        :ht=ether:\
-        :ha=004001432666:\
-        :sm=255.255.255.0:\
-        :hn:\
-        :ds=199.246.76.1:\
-        :ip=199.246.76.2:\
-        :gw=199.246.76.1:\
-        :vm=rfc1048:</programlisting>
-
-    <para>¤³¤ì¤é¤Î¹Ô¤Ï¼¡¤Î¤è¤¦¤Ê°ÕÌ£¤Ç¤¹¡£</para>
-
-    <informaltable frame="none" pgwide="1">
-      <tgroup cols="2">
-	<tbody>
-	  <row>
-	    <entry><literal>altair</literal></entry>
-	    <entry>¥É¥á¥¤¥ó̾¤ò½ü¤¤¤¿¥Ç¥£¥¹¥¯Ìµ¤·¤Î¥·¥¹¥Æ¥à¤Î̾Á°</entry>
-	  </row>
-
-	  <row>
-	    <entry><literal>ht=ether</literal></entry>
-	    <entry><quote>¥¤¡¼¥µ¥Í¥Ã¥È</quote>¥Ï¡¼¥É¥¦¥§¥¢¥¿¥¤¥×</entry>
-	  </row>
-
-	  <row>
-	    <entry><literal>ha=004001432666</literal></entry>
-	    <entry>(Àè¤Ëµ­Ï¿¤·¤¿) ¥Ï¡¼¥É¥¦¥§¥¢¤Î¥¢¥É¥ì¥¹</entry>
-	  </row>
-
-	  <row>
-	    <entry><literal>sm=255.255.255.0</literal></entry>
-	    <entry>¥µ¥Ö¥Í¥Ã¥È¥Þ¥¹¥¯</entry>
-	  </row>
-
-	  <row>
-	    <entry><literal>hn</literal></entry>
-	    <entry>¥¯¥é¥¤¥¢¥ó¥È¤Ë¥¯¥é¥¤¥¢¥ó¥È¤Î¥Û¥¹¥È̾¤òÁ÷¤ë¤è¤¦¡¢
-	      ¥µ¡¼¥Ð¤ËÅÁ¤¨¤Þ¤¹</entry>
-	  </row>
-
-	  <row>
-	    <entry><literal>ds=199.246.76.1</literal></entry>
-	    <entry>¥É¥á¥¤¥ó¥µ¡¼¥Ð¤¬¤É¤ì¤Ê¤Î¤«¤ò¥¯¥é¥¤¥¢¥ó¥È¤ËÅÁ¤¨¤Þ¤¹</entry>
-	  </row>
-
-	  <row>
-	    <entry><literal>ip=199.246.76.2</literal></entry>
-	    <entry>¥¯¥é¥¤¥¢¥ó¥È¤Î IP ¥¢¥É¥ì¥¹¤¬²¿¤Ê¤Î¤«¤ò
-	      ¥¯¥é¥¤¥¢¥ó¥È¤ËÅÁ¤¨¤Þ¤¹</entry>
-	  </row>
-
-	  <row>
-	    <entry><literal>gw=199.246.76.1</literal></entry>
-	    <entry>¥Ç¥Õ¥©¥ë¥È¥²¡¼¥È¥¦¥§¥¤¤¬¤É¤ì¤Ê¤Î¤«¤ò
-	      ¥¯¥é¥¤¥¢¥ó¥È¤ËÅÁ¤¨¤Þ¤¹</entry>
-	  </row>
-
-	  <row>
-	    <entry><literal>vm=...</literal></entry>
-	    <entry>¤³¤ì¤Ï¤½¤Î¤Þ¤Þ¤Ë¤·¤Æ¤ª¤¤¤Æ¤¯¤À¤µ¤¤</entry>
-	  </row>
-	</tbody>
-      </tgroup>
-    </informaltable>
-
-    <note>
-      <para>IP ¥¢¥É¥ì¥¹¤ÏÀµ¤·¤¯ÀßÄꤷ¤Æ¤¯¤À¤µ¤¤¡£
-	¾å¤Î¥¢¥É¥ì¥¹¤Ï¤ï¤¿¤·¤À¤±¤Î¤â¤Î¤Ç¤¹¡£</para>
-    </note>
-
-    <para><filename>/tftpboot</filename> ¥Ç¥£¥ì¥¯¥È¥ê¤ò¥µ¡¼¥Ð¤ËºîÀ®¤·¤Æ¡¢
-      ¥µ¡¼¥Ð¤¬¥µ¡¼¥Ó¥¹¤ò¹Ô¤¦¥Ç¥£¥¹¥¯Ìµ¤·¤Î¥·¥¹¥Æ¥à¤Î¤¿¤á¤ÎÀßÄê¥Õ¥¡¥¤¥ë¤ò¤³¤Î¥Ç¥£¥ì¥¯¥È¥ê¤ËÆþ¤ì¤Æ¤ª¤­¤Þ¤¹¡£
-      ¤³¤ì¤é¤Î¥Õ¥¡¥¤¥ë¤Ï <filename>cfg.<replaceable>ip</replaceable></filename>
-      ¤È¤¤¤¦Ì¾Á°¤Ë¤Ê¤Ã¤Æ¤¤¤Æ¡¢<replaceable>ip</replaceable>
-      ¤Ï¥Ç¥£¥¹¥¯Ìµ¤·¥·¥¹¥Æ¥à¤Î IP ¥¢¥É¥ì¥¹¤òɽ¤·¤Æ¤¤¤Þ¤¹¡£
-      <hostid>altair</hostid> ¤ÎÀßÄê¥Õ¥¡¥¤¥ë¤Ï <filename>/tftpboot/cfg.199.246.76.2</filename>
-      ¤È¤Ê¤ê¤Þ¤¹¡£¤³¤ÎÃæ¿È¤Ï¼¡¤Î¤è¤¦¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹:</para>
-
-    <programlisting>rootfs 199.246.76.1:/DiskLess/rootfs/altair
-hostname altair.example.com</programlisting>
-
-    <para><literal>hostname altair.example.com</literal>
-      ¤Î¹Ô¤Ïñ¤Ë¥Ç¥£¥¹¥¯Ìµ¤·¤Î¥·¥¹¥Æ¥à¤¬¤É¤Î¤è¤¦¤Ê´°Á´¤Ê¥É¥á¥¤¥ó̾¤ò»ý¤Ã¤Æ¤¤¤ë¤Î¤«¤òɽ¤·¤Æ¤¤¤Þ¤¹¡£</para>
-
-    <para><literal>rootfs 199.246.76.1:/DiskLess/rootfs/altair</literal>
-      ¤Î¹Ô¤Ï¥Ç¥£¥¹¥¯Ìµ¤·¤Î¥·¥¹¥Æ¥à¤¬
-      NFS ¤Ç¥Þ¥¦¥ó¥È¤Ç¤­¤ë¥ë¡¼¥È¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î¾ì½ê¤òɽ¤·¤Æ¤¤¤Þ¤¹¡£</para>
-
-    <note>
-      <para>NFS ¤Ç¥Þ¥¦¥ó¥È¤µ¤ì¤¿¥ë¡¼¥È¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Ï
-	<emphasis>Æɤ߽Ф·µö²Ä¤À¤±¤Ç</emphasis> ¥Þ¥¦¥ó¥È¤µ¤ì¤Þ¤¹¡£</para>
-    </note>
-
-    <para>¥Ç¥£¥¹¥¯Ìµ¤·¤Î¥·¥¹¥Æ¥à¤Î³¬ÁؤÏÍ׵ᤵ¤ì¤ì¤ÐÆɤ߽ñ¤­²Äǽ¤Ë¤·¤Æ¡¢
-      ¥Þ¥¦¥ó¥È¤·Ä¾¤¹¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£</para>
-
-    <para>¤ï¤¿¤·¤ÏͽÈ÷¤Î 386DX-40 ¤òÀìÍѤΠX üËö¤È¤·¤Æ»ÈÍѤ·¤Æ¤¤¤Þ¤¹¡£</para>
-
-    <para><hostid>altair</hostid> ¤Î³¬Áؤϼ¡¤ÎÄ̤ê¤Ç¤¹¡£</para>
-
-    <literallayout>/
-/bin
-/etc
-/tmp
-/sbin
-/dev
-/dev/fd
-/usr
-/var
-/var/run</literallayout>
-
-    <para>¼ÂºÝ¤Î¥Õ¥¡¥¤¥ë¤Î¥ê¥¹¥È¤Ï¼¡¤ÎÄ̤ê¤Ç¤¹¡£</para>
-
-    <screen>-r-xr-xr-x  1 root  wheel  779984 Dec 11 23:44 ./kernel
--r-xr-xr-x  1 root    bin  299008 Dec 12 00:22 ./bin/sh
--rw-r--r--  1 root  wheel     499 Dec 15 15:54 ./etc/rc
--rw-r--r--  1 root  wheel    1411 Dec 11 23:19 ./etc/ttys
--rw-r--r--  1 root  wheel     157 Dec 15 15:42 ./etc/hosts
--rw-r--r--  1 root    bin    1569 Dec 15 15:26 ./etc/XF86Config.altair
--r-x------  1 bin     bin  151552 Jun 10  1995 ./sbin/init
--r-xr-xr-x  1 bin     bin  176128 Jun 10  1995 ./sbin/ifconfig
--r-xr-xr-x  1 bin     bin  110592 Jun 10  1995 ./sbin/mount_nfs
--r-xr-xr-x  1 bin     bin  135168 Jun 10  1995 ./sbin/reboot
--r-xr-xr-x  1 root    bin   73728 Dec 13 22:38 ./sbin/mount
--r-xr-xr-x  1 root  wheel    1992 Jun 10  1995 ./dev/MAKEDEV.local
--r-xr-xr-x  1 root  wheel   24419 Jun 10  1995 ./dev/MAKEDEV</screen>
-
-    <para>(FreeBSD&nbsp;5.X ¤Ë¤ª¤¤¤Æ½é´ü¾õÂÖ¤ÇÍ­¸ú¤Ë¤Ê¤Ã¤Æ¤¤¤ë) &man.devfs.5;
-      ¤òÍøÍѤ·¤Æ¤¤¤Ê¤¤¤Î¤Ç¤¢¤ì¤Ð¡¢<filename>dev</filename> ¥Ç¥£¥ì¥¯¥È¥ê¤Ç
-      <command>MAKEDEV all</command>
-      ¤¹¤ë¤Î¤ò˺¤ì¤º¤Ë¡£</para>
-
-    <para><hostid>altair</hostid> ¤Î <filename>/etc/rc</filename> ¤Ï
-      ¼¡¤ÎÄ̤ê¤Ç¤¹¡£</para>
-
-<programlisting>#!/bin/sh
-#
-PATH=/bin:/
-export PATH
-#
-# localhost ¤ÎÀßÄê
-/sbin/ifconfig lo0 127.0.0.1
-#
-# ¥¤¡¼¥µ¥Í¥Ã¥È¥«¡¼¥É¤ÎÀßÄê
-/sbin/ifconfig ed0 199.246.76.2 netmask 0xffffff00
-#
-# NFS ¤Ç root ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ò¥Þ¥¦¥ó¥È¤¹¤ë
-/sbin/mount antares:/DiskLess/rootfs/altair /
-#
-# NFS ¤Ç /usr ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ò¥Þ¥¦¥ó¥È¤¹¤ë
-/sbin/mount antares:/DiskLess/usr /usr
-#
-/usr/X11R6/bin/XF86_SVGA -query antares -xf86config /etc/XF86Config.altair > /dev/null 2&gt;&amp;1
-#
-# X ¤ò½ªÎ»¤¹¤ë¤ÈºÆµ¯Æ°
-/sbin/reboot
-#
-# ¤¦¤Þ¤¯¹Ô¤«¤Ê¤¤¤È¤­¤Ë¤Ï....
-exit 1</programlisting>
-
-    <para>¥³¥á¥ó¥È¤ä¼ÁÌä¤Ï¤É¤ó¤Ê¤â¤Î¤Ç¤â´¿·Þ¤·¤Þ¤¹¡£</para>
-  </sect1>
-</article>
diff --git a/ja_JP.eucJP/articles/multi-os/Makefile b/ja_JP.eucJP/articles/multi-os/Makefile
deleted file mode 100644
index bb708815e9..0000000000
--- a/ja_JP.eucJP/articles/multi-os/Makefile
+++ /dev/null
@@ -1,19 +0,0 @@
-#
-# $FreeBSD$
-#
-# Article: Installing and Using FreeBSD With Other Operating Systems
-#
-# Original revision: 1.12
-
-DOC?= article
-
-FORMATS?= html
-WITH_ARTICLE_TOC?= YES
-
-INSTALL_COMPRESSED?=gz
-INSTALL_ONLY_COMPRESSED?=
-
-SRCS=	article.sgml
-
-DOC_PREFIX?= ${.CURDIR}/../../..
-.include "${DOC_PREFIX}/share/mk/doc.project.mk"
diff --git a/ja_JP.eucJP/articles/multi-os/article.sgml b/ja_JP.eucJP/articles/multi-os/article.sgml
deleted file mode 100644
index 81a0de8236..0000000000
--- a/ja_JP.eucJP/articles/multi-os/article.sgml
+++ /dev/null
@@ -1,850 +0,0 @@
-<?xml version="1.0" encoding="euc-jp" standalone="no"?>
-<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V4.2-Based Extension//EN"
-	"../../../share/sgml/freebsd42.dtd" [
-<!ENTITY % entities PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Entity Set//JA" "../../share/sgml/entities.ent">
-%entities;
-]>
-
-<!--
-     The FreeBSD Documentation Project
-     The FreeBSD Japanese Documentation Project
-
-     Original revision: 1.39
-     $FreeBSD$
--->
-
-<article lang='ja'>
-  <articleinfo>
-    <title>FreeBSD ¤È¾¤Î OS ¤ò¶¦Â¸¤µ¤»¤ë¤Ë¤Ï</title>
-
-    <authorgroup>
-      <author>
-	<firstname>Jay</firstname>
-
-	<surname>Richmond</surname>
-
-	<affiliation>
-	  <address>
-	    <email>jayrich@sysc.com</email>
-	  </address>
-	</affiliation>
-      </author>
-    </authorgroup>
-
-    <pubdate>1996 ǯ 8 ·î 6 Æü</pubdate>
-
-    <legalnotice id="trademarks" role="trademarks">
-      &tm-attrib.freebsd;
-      &tm-attrib.ibm;
-      &tm-attrib.linux;
-      &tm-attrib.microsoft;
-      &tm-attrib.powerquest;
-      &tm-attrib.general;
-    </legalnotice>
-
-    <releaseinfo>$FreeBSD$</releaseinfo>
-
-    <abstract>
-      <para>
-	¤³¤³¤Ç¤Ï¡¢FreeBSD ¤ò (Linux¡¢&ms-dos;¡¢&os;2¡¢&windows; 95 ¤Ê¤É)
-	¿Íµ¤¤Î¤¢¤ë¾¤Î OS ¤È¤¦¤Þ¤¯Æ±µï¤µ¤»¤ëÊýË¡¤Ë¤Ä¤¤¤ÆÀâÌÀ¤·¤Þ¤¹¡£
-	¤³¤Îʸ¾Ï¤ò½ñ¤¯¤Ë¤¢¤¿¤ê¡¢
-	Annelise Anderson <email>andrsn@stanford.edu</email>¡¢
-	Randall Hopper <email>rhh@ct.picker.com</email>¡¢
-	&a.jkh;	¤Ë¤Ï¡¢ÆäˤªÀ¤Ïäˤʤê¤Þ¤·¤¿¡£
-      </para>
-    </abstract>
-  </articleinfo>
-
-  <sect1>
-    <title>³µÍ×</title>
-
-    <para>ÂçÍÆÎ̤Υǥ£¥¹¥¯¤¬¤Ê¤¤¤È¡¢ÂçȾ¤Î¿Í¤ÏÊ£¿ô¤Î OS ¤ò
-      ¤¦¤Þ¤¯¶¦Â¸¤µ¤»¤ë¤³¤È¤Ï¤Ç¤­¤Þ¤»¤ó¡£¤½¤Î¤¿¤á¡¢¤³¤Îʸ½ñ¤Ë¤ÏÂçÍÆÎÌ
-      EIDE ¥É¥é¥¤¥Ö¤Ë´Ø¤¹¤ëµ­½Ò¤â´Þ¤Þ¤ì¤Æ¤¤¤Þ¤¹¡£
-      Ê£¿ô¤Î OS ¤òƱµï¤µ¤»¤ë¾ì¹ç¡¢¥Ï¡¼¥É¥Ç¥£¥¹¥¯¤ÎÀßÄê¤ä
-      OS ¤ÎÁȹ礻¤È¤¤¤¦¤Î¤ÏÈó¾ï¤Ë¤¿¤¯¤µ¤ó¤¢¤ê¤Þ¤¹¤¬¡¢
-      ¤ª¤½¤é¤¯ <xref linkend="ch5"/> ¤¬ºÇ¤âÌò¤ËΩ¤Ä¾Ï¤Ç¤·¤ç¤¦¡£
-      ¤½¤Î¾Ï¤Ë¤Ï¡¢Ê£¿ô¤Î OS ¤ò»ÈÍѤ¹¤ë¤¿¤á¤ËÆäËɬÍפÊ
-      ¥³¥ó¥Ô¥å¡¼¥¿ÀßÄê¤Ë¤Ä¤¤¤Æ¤Î¾ÜºÙ¤¬½ñ¤«¤ì¤Æ¤¤¤Þ¤¹¡£</para>
-
-    <para>¤³¤Îʸ½ñ¤Ç¤Ï¡¢¥Ï¡¼¥É¥Ç¥£¥¹¥¯¤Ë
-      OS ¤òÄɲäǤ­¤ë¤À¤±¤Î¶õ¤­ÍÆÎ̤¬¤¢¤ë¤³¤È¤òÁ°Äó¤È¤·¤Æ¤¤¤Þ¤¹¡£
-      ¥Ï¡¼¥É¥Ç¥£¥¹¥¯¤Î¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤òºÆÅÙÀÚ¤êľ¤¹¤È¡¢
-      ´û¸¤Î¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤Ë¤¢¤ë¥Ç¡¼¥¿¤ò²õ¤¹¤³¤È¤Ë¤Ê¤ê¤«¤Í¤Þ¤»¤ó¡£
-      ¤·¤«¤·¡¢¥Ï¡¼¥É¥Ç¥£¥¹¥¯¤¬´°Á´¤Ë DOS ¤ÇÀê¤á¤é¤ì¤Æ¤¤¤ë¤è¤¦¤Ç¤¢¤ì¤Ð¡¢
-      (FreeBSD CDROM ¤ÎÃæ¤Î <filename>\TOOLS</filename> ¥Ç¥£¥ì¥¯¥È¥ê¡¢
-      ¤¢¤ë¤¤¤Ï <ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/tools/">ftp
-      </ulink> ¤«¤é¼èÆÀ¤Ç¤­¤ë) FIPS ¥æ¡¼¥Æ¥£¥ê¥Æ¥£¤¬Ìò¤ËΩ¤Ä¤³¤È¤Ç¤·¤ç¤¦¡£
-      ¤³¤Î¥Ä¡¼¥ë¤ò»È¤¨¤Ð¡¢¥Ç¡¼¥¿¤òÇ˲õ¤¹¤ë¤³¤È¤Ê¤¯¥Ï¡¼¥É¥Ç¥£¥¹¥¯¤Î
-      ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤òÀÚ¤êľ¤¹¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
-      ¤Þ¤¿¡¢¥Ç¡¼¥¿¤òÇ˲õ¤»¤º¤Ë¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤Î¥µ¥¤¥º¤òÊѹ¹¤·¤¿¤êºï½ü¤Ç¤­¤ë
-      <application>&partitionmagic;</application>
-      ¤È¤¤¤¦¾¦ÍÑ¤Î¥×¥í¥°¥é¥à¤â½Ð²ó¤Ã¤Æ¤¤¤Þ¤¹¡£</para>
-  </sect1>
-
-  <sect1 id="ch2">
-    <title>¥Ö¡¼¥È¥Þ¥Í¡¼¥¸¥ã¤Î³µÍ×</title>
-
-    <para>¤³¤³¤Ç¤Ï¡¢¤ª¤½¤é¤¯¤¢¤Ê¤¿¤¬Ìܤˤ¹¤ë¤Ç¤¢¤í¤¦¡¢
-      ¤¤¤¯¤Ä¤«¤Î¥Ö¡¼¥È¥Þ¥Í¡¼¥¸¥ã¤Ë¤Ä¤¤¤Æ´Êñ¤ËÀâÌÀ¤·¤Þ¤¹¡£
-      ¥³¥ó¥Ô¥å¡¼¥¿¤ÎÀßÄê¤Ë¤è¤Ã¤Æ¤Ï¡¢Æ±¤¸¥·¥¹¥Æ¥à¾å¤Ç 1 ¤Ä°Ê¾å¤Î
-      ¥Ö¡¼¥È¥Þ¥Í¡¼¥¸¥ã¤ò»ÈÍѤ·¤¿Êý¤¬ÊØÍø¤Ê¾ì¹ç¤¬¤¢¤ê¤Þ¤¹¡£</para>
-
-    <variablelist>
-      <varlistentry>
-	<term>Boot Easy</term>
-
-	<listitem>
-	  <para>¤³¤ì¤Ï¡¢FreeBSD ¤Çɸ½à¤Ë»ÈÍѤµ¤ì¤Æ¤¤¤ë
-	    ¥Ö¡¼¥È¥Þ¥Í¡¼¥¸¥ã¤Ç¤¹¡£
-            ÂçȾ¤Î OS ¤¬µ¯Æ°²Äǽ¤Ç¡¢
-            BSD¡¢&os2; (HPFS)¡¢&windows; 95 (FAT ¤ª¤è¤Ó FAT32)¡¢Linux
-	    ¤Ê¤É¤ò¥µ¥Ý¡¼¥È¤·¤Þ¤¹¡£
-	    ¥Õ¥¡¥ó¥¯¥·¥ç¥ó¥­¡¼¤Çµ¯Æ°¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤òÁªÂò¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£</para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-	<term>&os2; Boot Manager</term>
-
-	<listitem>
-	  <para>¤³¤ì¤Ï¡¢FAT¡¢FAT32¡¢HPFS¡¢FFS (FreeBSD)¡¢¤ª¤è¤Ó EXT2 (Linux)
-            ¤Îµ¯Æ°¤ËÂбþ¤·¤Æ¤¤¤Þ¤¹¡£
-	    ¥Ñ¡¼¥Æ¥£¥·¥ç¥óÁªÂò¤Ï¡¢¥«¡¼¥½¥ë¥­¡¼¤Ç¹Ô¤¤¤Þ¤¹¡£
-	    &os2; Boot Manager ¤Ï¡¢Â¾¤Î¥Þ¥¹¥¿¡¼¥Ö¡¼¥È¥ì¥³¡¼¥É (MBR) ¤ò
-            »ÈÍѤ¹¤ë¥Ö¡¼¥È¥Þ¥Í¡¼¥¸¥ã¤È°Û¤Ê¤ê¡¢
-	    Í£°ì¡¢¼«Ê¬ÍѤˤҤȤĥѡ¼¥Æ¥£¥·¥ç¥ó¤òÀêÍ­¤·¤Þ¤¹¡£
-	    ¤½¤Î¤¿¤á¡¢µ¯Æ°»þ¤ÎÌäÂê¤òÈò¤±¤ë¤¿¤á¤Ë¡¢
-	    Âè 1024 ÈÖÌܤè¤êÁ°¤Î¥·¥ê¥ó¥À¤Ë¥¤¥ó¥¹¥È¡¼¥ë¤·¤Ê¤±¤ì¤Ð¤¤¤±¤Þ¤»¤ó¡£
-	    ¥Ö¡¼¥È¥Þ¥Í¡¼¥¸¥ã¤¬ MBR ¤Ç¤Ï¤Ê¤¯¡¢µ¯Æ°¥»¥¯¥¿¤Î°ìÉô¤Ë¤¢¤ë¾ì¹ç¤Ï¡¢
-	    LILO ¤ò»È¤Ã¤Æ¤¤¤ë Linux ¤òµ¯Æ°¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
-	    &os2; Boot Manager ¤Ç Linux ¤òµ¯Æ°¤µ¤»¤ëÊýË¡¤Î¾ÜºÙ¤Ï¡¢
-	    ¼¡¤Î¥µ¥¤¥È
-	    <ulink url="http://www.linuxresources.com/LDP/HOWTO/HOWTO-INDEX.html">Linux HOWTO</ulink>
-	    ¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£</para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-	<term>OS-BS</term>
-
-	<listitem>
-	  <para>¤³¤ì¤Ï¡¢Boot Easy ¤ËÎà»÷¤·¤¿¤â¤Î¤Ç¡¢
-            µ¯Æ°¤Î¥¿¥¤¥à¥¢¥¦¥ÈÀßÄê¤äµ¯Æ°¤Î¥Ç¥Õ¥©¥ë¥È¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤ò·è¤á¤ë¤È¤¤¤Ã¤¿¡¢
-            µ¯Æ°¥×¥í¥»¥¹¤ÎºÙ¤«¤¤À©¸æ¤¬²Äǽ¤Ç¤¹¡£
-	    ¤³¤Î¥×¥í¥°¥é¥à¤Î¥Ù¡¼¥¿ÈǤǤϡ¢
-            ¥«¡¼¥½¥ë¥­¡¼¤òÍѤ¤¤Æµ¯Æ°¤¹¤ë OS ¤òÁªÂò¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
-	    ¤³¤ì¤Ï¡¢FreeBSD CD-ROM ¤Î
-	    <filename class="directory">\TOOLS</filename> ¥Ç¥£¥ì¥¯¥È¥ê¡¢
-	    ¤¢¤ë¤¤¤Ï <ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/tools/">
-	      ftp</ulink> ¤Ë¼ýÏ¿¤µ¤ì¤Æ¤¤¤Þ¤¹¡£</para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-	<term>LILO - LInux LOader</term>
-
-	<listitem>
-	  <para>¤³¤ì¤Ï¡¢Æ°ºî¤¬¸ÂÄꤵ¤ì¤¿¥Ö¡¼¥È¥Þ¥Í¡¼¥¸¥ã¤Ç¤¹¡£
-	    FreeBSD ¤òµ¯Æ°¤¹¤ë¤³¤È¤Ï¤Ç¤­¤Þ¤¹¤¬¡¢
-	    LILO ¤ÎÀßÄê¥Õ¥¡¥¤¥ë¤ò¾¯¡¹ÊÔ½¸¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£</para>
-	</listitem>
-      </varlistentry>
-    </variablelist>
-
-    <note id="fat32">
-      <title>FAT32 ¤Ë¤Ä¤¤¤Æ</title>
-
-      <para>FAT32 ¤Ï FAT ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ËÂå¤ï¤ë¤â¤Î¤Ç¤¹¡£
-        ¤³¤ì¤Ï Microsoft ¤Î OEM SR2 ¥Ù¡¼¥¿ÈÇ
-        (ÌõÃí: &windows; 95 ¤Î OEM ÈǤΰì¤Ä)
-        ¤Ë´Þ¤Þ¤ì¤Æ¤¤¤Æ¡¢1996 ǯËö¤Ø¸þ¤±¤Æ¡¢&windows; 95 ¤¬¥×¥ê¥¤¥ó¥¹¥È¡¼¥ë¤µ¤ì¤¿
-	¥³¥ó¥Ô¥å¡¼¥¿¤Ç¹­¤¯ÍøÍѤµ¤ì»Ï¤á¤Þ¤·¤¿¡£
-	&windows; 95 ¤Ï½¾Íè¤Î FAT ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤òÊÑ´¹¤·¡¢
-	ÂçÍÆÎ̤Υϡ¼¥É¥Ç¥£¥¹¥¯¤Ç¤è¤ê¾®¤µ¤Ê¥µ¥¤¥º¤Î¥¯¥é¥¹¥¿¤òÍøÍѲÄǽ¤Ë¤·¤Þ¤¹¡£
-	¤Þ¤¿¡¢FAT32 ¤Ï½¾Íè¤Î FAT µ¯Æ°¥»¥¯¥¿¤ä¥¢¥í¥±¡¼¥·¥ç¥ó¥Æ¡¼¥Ö¥ë¤ò
-	Êѹ¹¤¹¤ë¤¿¤á¡¢¤¤¤¯¤Ä¤«¤Î¥Ö¡¼¥È¥Þ¥Í¡¼¥¸¥ã¤ÏÍøÍѤǤ­¤Ê¤¯¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£</para>
-    </note>
-  </sect1>
-
-  <sect1 id="ch3">
-    <title>ɸ½àŪ¤Ê¥¤¥ó¥¹¥È¡¼¥ë</title>
-
-    <para>¤Ç¤Ï¡¢ÂçÍÆÎ̤ΠEIDE ¥Ï¡¼¥É¥Ç¥£¥¹¥¯¤¬ 2 ¤Ä¤¢¤ê¡¢
-      FreeBSD¡¢Linux¡¢&windows; 95 ¤òƱµï¤µ¤»¤¿¤¤¡¢
-      ¤È¤¤¤¦¾ì¹ç¤ò¹Í¤¨¤Þ¤·¤ç¤¦¡£</para>
-
-    <para>¤³¤Î¤è¤¦¤Ê¥Ï¡¼¥É¥Ç¥£¥¹¥¯¤ò»ÈÍѤ·¤¿¾ì¹ç¤Î
-      °ìÎã¤Ë¤Ä¤¤¤Æ¸«¤Æ¤ß¤Þ¤·¤ç¤¦:</para>
-
-    <itemizedlist>
-      <listitem>
-	<para><filename>/dev/wd0</filename> (1 ÈÖÌܤÎʪÍýŪ¤Ê¥Ï¡¼¥É¥Ç¥£¥¹¥¯)</para>
-      </listitem>
-
-      <listitem>
-	<para><filename>/dev/wd1</filename> (2 ÈÖÌܤΥϡ¼¥É¥Ç¥£¥¹¥¯)</para>
-      </listitem>
-    </itemizedlist>
-
-    <para>ξÊý¤Î¥Ç¥£¥¹¥¯¤È¤â 1416 ¥·¥ê¥ó¥À¤¢¤ê¤Þ¤¹¡£</para>
-
-    <procedure>
-      <step>
-	<para><filename>FDISK.EXE</filename> ¥æ¡¼¥Æ¥£¥ê¥Æ¥£¤¬Æþ¤Ã¤Æ¤¤¤ë
-	  &ms-dos;¡¢¤¢¤ë¤¤¤Ï &windows; 95 boot ¥Ç¥£¥¹¥¯¤«¤éµ¯Æ°¤µ¤»¡¢
-	  1 ÈÖÌܤΥǥ£¥¹¥¯¾å¤Ë 50MB ¤Î¥×¥é¥¤¥Þ¥ê¥Ñ¡¼¥Æ¥£¥·¥ç¥ó
-	  (&windows; 95 ËÜÂΤËɬÍ×¤Ê 35-40MB ¤Ë¡¢¾¯¡¹Í¾Ê¬¤Ê¶õ¤­¤ò²Ã¤¨¤¿¤â¤Î)
-          ¤òºîÀ®¤·¤Þ¤¹¡£
-          ¤Þ¤¿¡¢&windows; ¥¢¥×¥ê¥±¡¼¥·¥ç¥ó¤È¥Ç¡¼¥¿ÍѤȤ·¤Æ¡¢
-          2ÈÖÌܤΥϡ¼¥É¥Ç¥£¥¹¥¯¾å¤ËÂ礭¤á¤Î¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤òºîÀ®¤·¤Þ¤¹¡£</para>
-      </step>
-
-      <step>
-	<para>ºÆµ¯Æ°¤·¡¢<filename>C:</filename>
-          ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¾å¤Ë &windows; 95 ¤ò¥¤¥ó¥¹¥È¡¼¥ë¤·¤Þ¤¹
-          (°ì¸À¤Ç½ª¤ï¤é¤»¤é¤ì¤ë¤Û¤É´Êñ¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¤¬)¡£</para>
-      </step>
-
-      <step>
-	<para>¼¡¤Ë Linux ¤ò¥¤¥ó¥¹¥È¡¼¥ë¤·¤Þ¤¹¡£
-          ¤¹¤Ù¤Æ¤Î Linux ¥Ç¥£¥¹¥È¥ê¥Ó¥å¡¼¥·¥ç¥ó¤Ë¤Ä¤¤¤Æ³Îǧ¤·¤¿¤ï¤±¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¤¬¡¢
-	  ¾¯¤Ê¤¯¤È¤â
-	  <ulink url="http://www.slackware.com">Slackware</ulink>
-	  ¤Ë¤Ï LILO (<xref linkend="ch2"/> »²¾È)
-	  ¤¬´Þ¤Þ¤ì¤Æ¤¤¤Þ¤¹¡£Linux ¤Î <command>fdisk</command>
-          ¥³¥Þ¥ó¥É¤ò»È¤Ã¤Æ¡¢¥Ï¡¼¥É¥Ç¥£¥¹¥¯¤òÀÚ¤êʬ¤±¤ë¤È¤·¤¿¤é¡¢
-          ¤ï¤¿¤·¤Î¾ì¹ç¤ÏºÇ½é¤Î¥É¥é¥¤¥Ö (¥ë¡¼¥È¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤È¥¹¥ï¥Ã¥×
-          ¤ò¹ç¤ï¤»¤Æ¤À¤¤¤¿¤¤ 300MB¤¯¤é¤¤) ¤Ë Linux
-          ¤ÎÁ´¥·¥¹¥Æ¥à¤òÆþ¤ì¤ë¤Ç¤·¤ç¤¦¡£</para>
-      </step>
-
-      <step>
-	<para>Linux ¤ò¥¤¥ó¥¹¥È¡¼¥ë¤·¤Æ¤«¤é LILO
-          ¤ò¥¤¥ó¥¹¥È¡¼¥ë¤¹¤ë¤«¤É¤¦¤«Ê¹¤«¤ì¤¿»þ¡¢
-	  LILO ¤Î¥¤¥ó¥¹¥È¡¼¥ëÀè¤Ï
-          MBR (¥Þ¥¹¥¿¡¼¥Ö¡¼¥È¥ì¥³¡¼¥É) ¤Ç¤Ï¤Ê¤¯
-          Linux ¤Î¥ë¡¼¥È¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¾å¤Ë¤Ê¤Ã¤Æ¤¤¤ë¤³¤È¤ò
-          <emphasis>ɬ¤º</emphasis>³Îǧ¤·¤Æ²¼¤µ¤¤¡£</para>
-      </step>
-
-      <step>
-	<para>»Ä¤ê¤Î¥Ï¡¼¥É¥Ç¥£¥¹¥¯¤Ï¡¢¤¹¤Ù¤Æ FreeBSD ¤Ë¤¢¤Æ¤Þ¤¹¡£
-	  ¤³¤Î»þ¡¢FreeBSD ¤Î¥ë¡¼¥È¥¹¥é¥¤¥¹¤¬ 1024 ¥·¥ê¥ó¥À¤ò±Û¤¨¤Ê¤¤¤è¤¦¤Ë
-	  µ¤¤òÉÕ¤±¤Þ¤¹ (¤³¤³¤ÇÁÛÄꤷ¤Æ¤¤¤ë 720MB ¤Î¥Ç¥£¥¹¥¯¤Î¾ì¹ç¡¢
-	  1024 ¥·¥ê¥ó¥À¤Ï 528MB ¤Î°ÌÃ֤ˤ¢¤ê¤Þ¤¹)¡£
-	  »Ä¤ê¤Î¥Ï¡¼¥É¥Ç¥£¥¹¥¯ (270MB) ¤Ï¡¢
-          <filename class="directory">/usr</filename> ¤È
-	  <filename class="directory">/</filename> ¥¹¥é¥¤¥¹¤Ë¤¢¤Æ¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹¡£
-	  2 ÈÖÌܤΥǥ£¥¹¥¯¤Î»Ä¤ê¤Ï¡¢
-	  <filename class="directory">/usr/src</filename>
-	  ¤È¥¹¥ï¥Ã¥×Îΰè¤Ë»ÈÍѤ·¤Þ¤¹¡£
-	  ¤³¤Î»Ä¤ê¤ÎÍÆÎ̤ϡ¢¼ê½ç 1) ¤ÇºîÀ®¤·¤¿ &windows; ¥¢¥×¥ê¥±¡¼¥·¥ç¥ó /
-	  ¥Ç¡¼¥¿¤Î¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤Ë°Í¸¤·¤Þ¤¹¡£</para>
-      </step>
-
-      <step>
-	<para>&windows; 95 <command>fdisk</command>
-          ¥æ¡¼¥Æ¥£¥ê¥Æ¥£¤Ç¸«¤¿¾ì¹ç¡¢
-	  ¥Ï¡¼¥É¥É¥é¥¤¥Ö¤Ï¼¡¤Î¤è¤¦¤Ë¸«¤¨¤Æ¤¤¤ë¤Ï¤º¤Ç¤¹¡£
-
-	  <screen>---------------------------------------------------------------------
-
-                  Îΰè¾ðÊó¤òɽ¼¨
-
-¸½ºß¤Î¥Ï¡¼¥É¥Ç¥£¥¹¥¯: 1
-
-Î롏      ¾õÂÖ     ¼ïÎà   ¥Ü¥ê¥å¡¼¥à¥é¥Ù¥ë M¥Ð¥¤¥È  ¥·¥¹¥Æ¥à  »ÈÍÑ
-C: 1         A    PRI DOS                     50     FAT**     7%
-   2         A    Non-DOS (Linux)            300              43%
-
-¥Ç¥£¥¹¥¯¤ÎÁíÍÆÎÌ¤Ï 696 M¥Ð¥¤¥È¤Ç¤¹¡£(1 M ¥Ð¥¤¥È = 1048576 ¥Ð¥¤¥È)
-
-³¤±¤ë¤Ë¤Ï Esc ¥­¡¼¤ò²¡¤·¤Æ¤¯¤À¤µ¤¤¡£
-
----------------------------------------------------------------------
-
-                  Îΰè¾ðÊó¤òɽ¼¨
-
-¸½ºß¤Î¥Ï¡¼¥É¥Ç¥£¥¹¥¯: 2
-
-Î롏      ¾õÂÖ     ¼ïÎà   ¥Ü¥ê¥å¡¼¥à¥é¥Ù¥ë M¥Ð¥¤¥È  ¥·¥¹¥Æ¥à  »ÈÍÑ
-D: 1         A    PRI DOS                    420     FAT**    60%
-
-¥Ç¥£¥¹¥¯¤ÎÁíÍÆÎÌ¤Ï 696 M¥Ð¥¤¥È¤Ç¤¹¡£(1 M¥Ð¥¤¥È = 1048576 ¥Ð¥¤¥È)
-
-³¤±¤ë¤Ë¤Ï Esc ¥­¡¼¤ò²¡¤·¤Æ¤¯¤À¤µ¤¤¡£
-
----------------------------------------------------------------------</screen>
-
-	  Ãí) ºÇ¿·¤Î OEM SR2 ¤ò¤ª»È¤¤¤Î¾ì¹ç¤Ï¡¢
-          ** ¤ÎÉôʬ¤¬ FAT16¡¢FAT32 ¤Èɽ¼¨¤µ¤ì¤ë¤³¤È¤¬¤¢¤ê¤Þ¤¹¡£
-	  ¾Ü¤·¤¯¤Ï <xref linkend="ch2"/> ¤ò¤´Í÷²¼¤µ¤¤¡£</para>
-      </step>
-
-      <step>
-	<para>FreeBSD ¤ò¥¤¥ó¥¹¥È¡¼¥ë¤·¤Þ¤¹¡£
-	  ºÇ½é¤Î¥Ï¡¼¥É¥Ç¥£¥¹¥¯¤¬ BIOS ¤Ç <quote>NORMAL</quote>
-	  ¤ÈÀßÄꤵ¤ì¤¿¾õÂ֤ǵ¯Æ°¤¹¤ë¤³¤È¤ò³Îǧ¤·¤Þ¤¹¡£
-	  ¤½¤¦¤Ç¤Ê¤¤¾ì¹ç¤Ï¡¢
-	  µ¯Æ°»þ¤ËŬÀڤʥǥ£¥¹¥¯¥¸¥ª¥á¥È¥ê¾ðÊó¤òÆþÎϤ·¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó
-	  (¥¸¥ª¥á¥È¥ê¾ðÊó¤òÆÀ¤ë¤Ë¤Ï¡¢&windows; 95 ¤òµ¯Æ°¤·¤Æ
-	  Microsoft Diagnostics (<filename>MSD.EXE</filename>) ¤ÇÄ´¤Ù¤ë¤«¡¢
-	  BIOS ¤Îµ¡Ç½¤Ç¥Á¥§¥Ã¥¯¤·¤Æ²¼¤µ¤¤)¡£
-	  ¤³¤³¤Ç¤Î¥Ñ¥é¥á¡¼¥¿ <literal>hd0=1416,16,63</literal> ¤Ï¡¢
-	  <replaceable>1416</replaceable> ¤Ï¥Ï¡¼¥É¥Ç¥£¥¹¥¯¤Î¥·¥ê¥ó¥À¿ô¤Ç¤¢¤ê¡¢
-	  <replaceable>16</replaceable> ¤Ï¥È¥é¥Ã¥¯¤¢¤¿¤ê¤Î¥Ø¥Ã¥É¿ô¡¢
-	  <replaceable>63</replaceable> ¤Ï¥È¥é¥Ã¥¯¤¢¤¿¤ê¤Î¥»¥¯¥¿¿ô¤Ç¤¹¡£</para>
-      </step>
-
-      <step>
-	<para>¥Ï¡¼¥É¥Ç¥£¥¹¥¯¤Î¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤òÀÚ¤ë»þ¤Ë¤Ï¡¢
-	  Boot Easy ¤¬ 1 ÈÖÌܤΥǥ£¥¹¥¯¤Ë¥¤¥ó¥¹¥È¡¼¥ë¤µ¤ì¤Æ¤¤¤ë¤³¤È¤ò³Îǧ¤·¤Þ¤¹¡£
-	  2 ÈÖÌܤΥϡ¼¥É¥Ç¥£¥¹¥¯¤Ïµ¯Æ°¤È´Ø·¸¤Ê¤¤¤Î¤Ç¡¢
-          ¤³¤Á¤é¤Ë¤Ä¤¤¤Æ¿´ÇÛ¤¹¤ëɬÍפϤ¢¤ê¤Þ¤»¤ó¡£</para>
-      </step>
-
-      <step>
-	<para>ºÆµ¯Æ°¤¹¤ë¤È¡¢Boot Easy ¤¬ DOS (&windows; 95)¡¢
-          Linux¡¢BSD (FreeBSD) ¤È¤¤¤¦¡¢
-          3 ¤Ä¤Îµ¯Æ°²Äǽ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤òǧ¼±¤·¤Þ¤¹¡£</para>
-      </step>
-    </procedure>
-  </sect1>
-
-  <sect1 id="ch4">
-    <title>Ãí°Õ¤È¹Í»¡</title>
-
-    <para>ÂçÉôʬ¤Î OS ¤Ï¡¢¼«Ê¬¤¬¥Ï¡¼¥É¥Ç¥£¥¹¥¯¤Î¤É¤ÎÎΰè¤Ë¡¢
-      ¤É¤Î¤è¤¦¤ËÇÛÃÖ¤·¤Æ¤¤¤ë¤«¡¢¤È¤¤¤¦¤³¤È¤òÈó¾ï¤Ëµ¤¤Ë¤·¤Þ¤¹¡£
-      &windows; 95 ¤ä DOS ¤Ï¡¢1 ÈÖÌܤΥϡ¼¥É¥Ç¥£¥¹¥¯¤Î
-      ´ðËÜÎΰè¤Ë¥¤¥ó¥¹¥È¡¼¥ë¤µ¤ì¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¤¬¡¢
-      &os2; ¤ÏÎ㳰Ū¤Ë¡¢¥Ï¡¼¥É¥Ç¥£¥¹¥¯¤Î 1 ÈÖÌÜ ¤È 2 ÈÖÌÜ¡¢
-      ´ðËÜÎΰè¤È³ÈÄ¥Îΰè¤ò¤Þ¤Ã¤¿¤¯Ìä¤ï¤º¤Ë¥¤¥ó¥¹¥È¡¼¥ë¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
-      ¤è¤¯Ê¬¤«¤é¤Ê¤±¤ì¤Ð¡¢µ¯Æ°²Äǽ¤Ê¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤ò
-      1024 ¥·¥ê¥ó¥ÀÆâ¤ËÆþ¤ì¤ë¤è¤¦¤Ë¤·¤Æ²¼¤µ¤¤¡£</para>
-
-    <para>BSD ¥·¥¹¥Æ¥à¤¬Â¸ºß¤·¤Æ¤¤¤ë¤È¤³¤í¤Ë
-      &windows; 95 ¤òºÜ¤»¤ë¤È¡¢MBR ¤¬ <quote>Ç˲õ</quote> ¤µ¤ì¤Æ¤·¤Þ¤¤¤Þ¤¹¡£
-      ¤½¤Î¤¿¤á¡¢¥Ö¡¼¥È¥Þ¥Í¡¼¥¸¥ã¤ÎºÆ¥¤¥ó¥¹¥È¡¼¥ë¤¬É¬Íפˤʤê¤Þ¤¹¡£
-      Boot Easy ¤Ï¡¢CDROM ¤Î
-      <filename class="directory">\TOOLS</filename> ¥Ç¥£¥ì¥¯¥È¥ê¤¢¤ë¤¤¤Ï
-      <ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/tools/">ftp</ulink>
-      ¥µ¥¤¥È¤Ë´Þ¤Þ¤ì¤ë <filename>BOOTINST.EXE</filename> ¥æ¡¼¥Æ¥£¥ê¥Æ¥£¤òÍѤ¤¤Æ¡¢
-      ºÆ¥¤¥ó¥¹¥È¡¼¥ë¤¹¤ë¤³¤È¤¬²Äǽ¤Ç¤¹¡£
-      ¤Þ¤¿¡¢¥¤¥ó¥¹¥È¡¼¥é¤Î¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¥¨¥Ç¥£¥¿¤ò»È¤Ã¤Æ
-      Boot Easy ¤òºÆ¥¤¥ó¥¹¥È¡¼¥ë¤¹¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹¡£
-      ¤½¤³¤«¤é¡¢FreeBSD ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤ò bootable ¤È¤·¤Æ¥Þ¡¼¥¯¤ò¤Ä¤±¡¢
-      Boot Manager ¤òÁªÂò¤·¤Þ¤¹¡£
-      Êѹ¹¤·¤¿¾ðÊó¤ò MBR ¤Ë (W)rite out (= Êݸ) ¤¹¤ë¤¿¤á¡¢W ¤òÆþÎϤ·¤Þ¤¹¡£
-      ¤½¤·¤ÆºÆµ¯Æ°¤¹¤ë¤È¡¢
-      Boot Easy ¤¬ &windows; 95 ¤ò DOS ¤È¤·¤Æǧ¼±¤¹¤ë¤Ï¤º¤Ç¤¹¡£</para>
-
-    <para>&os2; ¤Ï FAT¡¢HPFS ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤òǧ¼±¤·¤Þ¤¹¤¬¡¢
-      FFS (FreeBSD)¡¢EXT2 (Linux) ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤òǧ¼±¤·¤Ê¤¤¤³¤È¤ò³Ð¤¨¤Æ¤ª¤¤¤Æ²¼¤µ¤¤¡£
-      ƱÍͤˡ¢&windows; 95 ¤Ï¡¢FAT ¤È FAT32
-      ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤·¤«Æɤ߽ñ¤­¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤»¤ó (<xref linkend="ch2"/> ¤ò»²¾È)¡£
-      FreeBSD ¤Ï¡¢ ¤Û¤È¤ó¤É¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤òÆɤळ¤È¤¬¤Ç¤­¤Þ¤¹¤¬¡¢
-      ¸½»þÅÀ¤Ç HPFS ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤ÎÆɤ߹þ¤ß¤Ë¤ÏÂбþ¤·¤Æ¤¤¤Þ¤»¤ó¡£
-      Linux ¤Ç¤Ï¡¢HPFS ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤òÆɤळ¤È¤¬¤Ç¤­¤Þ¤¹¤¬¡¢
-      ½ñ¤­¹þ¤ß¤Ï¤Ç¤­¤Þ¤»¤ó¡£
-      ºÇ¶á¤Î Linux ¥«¡¼¥Í¥ë (2.x) ¤Î¥Ð¡¼¥¸¥ç¥ó¤Ç¤Ï¡¢
-      &windows; 95 VFAT ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤ËÆɤ߽ñ¤­¤¬¤Ç¤­¤Þ¤¹
-      (VFAT ¤Ï¡¢&windows; 95 ¤ÇŤ¤¥Õ¥¡¥¤¥ë̾¤òÍøÍѲÄǽ¤Ë¤¹¤ë¤â¤Î¤Ç¡¢
-      ¤Û¤È¤ó¤É FAT ¤È°ì½ï¤Ç¤¹)¡£
-      ¤Ä¤Þ¤ê Linux ¤Ï¡¢¤Û¤È¤ó¤É¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ËÆɤ߽ñ¤­¤¬¤Ç¤­¤ë¤ï¤±¤Ç¤¹¡£
-      ¤ï¤«¤ê¤Þ¤·¤¿?  ¤½¤¦´üÂÔ¤·¤Æ¡Ä¡£</para>
-  </sect1>
-
-  <sect1 id="ch5">
-    <title>Îã</title>
-
-    <para><emphasis>(¤³¤Î¾Ï¤Ï¤Þ¤À¤Þ¤À¼ê¤òÆþ¤ì¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
-	Îɤ¤Î㤬¤¢¤Ã¤¿¤é¡¢ <email>jayrich@sysc.com</email>
-	¤Þ¤Ç¥á¡¼¥ë¤òÁ÷¤Ã¤Æ²¼¤µ¤¤¡£)</emphasis></para>
-
-    <para>FreeBSD + &windows; 95:
-      &windows; 95 ¤Î¸å¤Ë FreeBSD ¤òºÜ¤»¤¿¾ì¹ç¤Ï¡¢
-      Boot Easy ¥á¥Ë¥å¡¼¤Î <literal>DOS</literal> ¤È¤¤¤¦Éôʬ¤ò³Îǧ¤·¤Æ²¼¤µ¤¤¡£
-      ¤³¤ì¤¬ &windows; 95 ¤Ë¤Ê¤ê¤Þ¤¹¡£
-      ¤â¤·¡¢FreeBSD ¤Î¸å¤Ë &windows; 95 ¤òºÜ¤»¤Æ¤·¤Þ¤Ã¤¿¾ì¹ç¤Ï¡¢
-      ¾åµ­¤Î <xref linkend="ch4"/> ¤òÆɤó¤Ç²¼¤µ¤¤¡£
-      ¤ª»ý¤Á¤Î¥Ï¡¼¥É¥Ç¥£¥¹¥¯¤¬ 1024 ¥·¥ê¥ó¥À¤ò±Û¤¨¤Ê¤¤¾ì¹ç¤Ï¡¢
-      µ¯Æ°»þ¤ÎÌäÂê¤Ï¤¢¤ê¤Þ¤»¤ó¡£
-      ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤Î¤¦¤Á 1 ¤Ä¤Ç¤â 1024 ¤ò±Û¤¨¤¿¤â¤Î¤¬¤¢¤ê¡¢
-      DOS (&windows; 95) ¤Ç
-      <errorname>invalid system disk</errorname> ¤Èɽ¼¨¤µ¤ì¤¿¤ê¡¢
-      FreeBSD ¤Çµ¯Æ°¤Ç¤­¤Ê¤¤¾ì¹ç¤Ë¤Ï¡¢BIOS ¤Î
-      <quote>&gt;1024 cylinder support</quote> ¤¢¤ë¤¤¤Ï
-      <quote>NORMAL/LBA</quote> ¥â¡¼¥É¤ÎÀßÄê¤ò³Îǧ¤·¤Æ²¼¤µ¤¤¡£
-      DOS ¤¬Àµ¾ï¤Ëµ¯Æ°¤¹¤ë¤Ë¤Ï¡¢¤ª¤½¤é¤¯ LBA (Logical Block Addressing)
-      ¥â¡¼¥É¤¬É¬Íפˤʤê¤Þ¤¹¡£
-      Ëè²óµ¯Æ°»þ¤ËBIOS ¤ÎÀßÄê¤òÀÚÂؤ¨¤ëÊýË¡¤ò¤È¤ê¤¿¤¯¤Ê¤¤¾ì¹ç¤Ë¤Ï¡¢
-      CD ¤Ë¼ýÏ¿¤µ¤ì¤Æ¤¤¤ë <filename>FBSDBOOT.EXE</filename>
-      ¥æ¡¼¥Æ¥£¥ê¥Æ¥£¤ò»È¤¤¡¢DOS ¤ò·Ðͳ¤·¤Æ FreeBSD
-      ¤òµ¯Æ°¤µ¤»¤ëÊýË¡¤â¤¢¤ê¤Þ¤¹ (¤³¤Î¥×¥í¥°¥é¥à¤Ï¡¢
-      FreeBSD ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤ò¸«ÉÕ¤±¤Æ¡¢µ¯Æ°¤·¤Þ¤¹)¡£</para>
-
-    <para>FreeBSD + &os2; + &windows; 95:
-      ÆäËÃí°Õ¤¹¤Ù¤­¤³¤È¤Ï¤¢¤ê¤Þ¤»¤ó¡£
-      &os2; ¤Î¥Ö¡¼¥È¥Þ¥Í¡¼¥¸¥ã¤Ï¡¢¤³¤ì¤é¤¹¤Ù¤Æ¤Î OS
-      ¤òµ¯Æ°¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¤Î¤Ç¡¢ÌäÂê¤Ï¤Ê¤¤¤Ç¤·¤ç¤¦¡£</para>
-
-    <para>FreeBSD + Linux:
-      ξÊý¤Î OS ¤òµ¯Æ°¤¹¤ë¤Î¤Ë¡¢Boot Easy ¤ò»È¤¦¤³¤È¤â¤Ç¤­¤Þ¤¹¡£</para>
-
-    <para>FreeBSD + Linux + &windows; 95:
-      (<xref linkend="ch3"/> ¤ò»²¾È)</para>
-  </sect1>
-
-  <sect1 id="sources">
-    <title>¾¤Î»²¹Í¤È¤Ê¤ë»ñÎÁ</title>
-
-    <para>¥Ï¡¼¥É¥Ç¥£¥¹¥¯¾å¤ËÊ£¿ô¤Î OS ¤òƱµï¤µ¤»¤ëÊýË¡¤Ë¤Ä¤¤¤Æ
-      ¼è¤ê°·¤Ã¤Æ¤¤¤ë <ulink
-	url="http://www.linuxresources.com/LDP/HOWTO/HOWTO-INDEX.html">Linux
-	HOW-TO</ulink> ¤Ï¡¢¤¿¤¯¤µ¤ó¤¢¤ê¤Þ¤¹¡£</para>
-
-    <para><ulink url="http://www.linuxresources.com/LDP/HOWTO/mini/Linux+DOS+Win95+OS2.html">
-        Linux+DOS+Win95+OS2 mini-HOWTO</ulink> ¤Ë¤Ï¡¢
-      &os2; ¥Ö¡¼¥È¥Þ¥Í¡¼¥¸¥ã¤Î¾ÜºÙ¤ÊÀßÄêË¡¤¬½ñ¤«¤ì¤Æ¤¤¤Þ¤¹¡£¤Þ¤¿¡¢
-      <ulink url="http://www.linuxresources.com/LDP/HOWTO/mini/Linux+FreeBSD.html">
-        Linux+FreeBSD mini-HOWTO</ulink> ¤âƱÍͤ˻²¹Í¤È¤Ê¤ë¤Ç¤·¤ç¤¦¡£
-      ¤µ¤é¤Ë¡¢<ulink url="http://www.in.net/~jkatz/win95/Linux-HOWTO.html">Linux-HOWTO</ulink>
-      ¤È¤¤¤¦¥µ¥¤¥È¤â¤¢¤ê¤Þ¤¹¡£</para>
-
-    <para><ulink url="http://www.tburke.net/info/ntldr/ntldr_hacking_guide.htm">&windowsnt;
-	Loader Hacking Guide</ulink> ¤Ë¤Ï¡¢
-      &windowsnt;¡¢&windows; 95¡¢DOS ¤ò¡¢Â¾¤Î OS
-      ¤È¥Þ¥ë¥Á¥Ö¡¼¥È¤¹¤ëÊýË¡¤Ë¤Ä¤¤¤Æ¤Î¾ðÊ󤬽ñ¤«¤ì¤Æ¤¤¤Þ¤¹¡£</para>
-
-    <para>Hale Landis ¤Î <quote>How It Works (Æ°ºî¤Î»ÅÁȤß)</quote> ¥É¥­¥å¥á¥ó¥È½¸¤Ë¤Ï¡¢
-      ¤¢¤é¤æ¤ë¼ïÎà¤Î¥Ç¥£¥¹¥¯¥¸¥ª¥á¥È¥ê¾ðÊó¤ä¡¢µ¯Æ°¤Ë´Ø¤¹¤ë¾ðÊ󤬴ޤޤì¤Æ¤¤¤Þ¤¹¡£
-      ¤Þ¤¿¡¢°Ê²¼¤Î¥ê¥ó¥¯
-      <ulink url="ftp://fission.dt.wdc.com/pub/otherdocs/pc_systems/how_it_works/allhiw.zip"></ulink>
-      ¤Ë¤¢¤ë¤â¤Î¤â»²¹Í¤Ë¤Ê¤ë¤Ç¤·¤ç¤¦¡£</para>
-
-    <para>ºÇ¸å¤Ë¡¢
-      ÇÛÉÛ¤µ¤ì¤Æ¤¤¤ë¥«¡¼¥Í¥ë¥½¡¼¥¹ (<ulink url="file://localhost/usr/src/sys/i386/boot/biosboot/README.386BSD">/usr/src/sys/i386/boot/biosboot/README.386BSD</ulink>
-      ¤ËŸ³«¤µ¤ì¤Æ¤¤¤Þ¤¹) ¤Ë´Þ¤Þ¤ì¤Æ¤¤¤ë¡¢FreeBSD
-      ¥«¡¼¥Í¥ë¤Îʸ½ñ¤â¸«Íî¤È¤µ¤Ê¤¤¤è¤¦¤Ë¤·¤Æ¤¯¤À¤µ¤¤¡£</para>
-  </sect1>
-
-  <sect1>
-    <title>µ»½ÑŪ¤Ê¾ÜºÙ</title>
-
-    <para><emphasis>(Randall Hopper¡¢
-        <email>rhh@ct.picker.com</email> ¤Î´ó¹Æ¤Ë¤è¤ë¤â¤Î¤Ç¤¹)</emphasis></para>
-
-    <para>¤³¤Î¾Ï¤Ï¡¢
-      ¥Ï¡¼¥É¥Ç¥£¥¹¥¯¤ä¥Ï¡¼¥É¥Ç¥£¥¹¥¯¤Îµ¯Æ°¥×¥í¥»¥¹¤Ë´Ø¤¹¤ë´ðÁÃÃ챤òÄ󶡤·¤Þ¤¹¡£
-      ¤³¤ì¤Ï¡¢Ê£¿ô¤Î OS ¤òµ¯Æ°¤¹¤ëÀßÄê¤ÇÌäÂ꤬µ¯¤³¤Ã¤¿»þ¡¢
-      ¤½¤ì¤ò²ò·è¤¹¤ë¤Î¤ËÌòΩ¤Ä¤Ç¤·¤ç¤¦¡£
-      ºÇ½é¤Ï¤´¤¯´ðËÜŪ¤ÊÍѸ줫¤é»Ï¤Þ¤ê¤Þ¤¹¤Î¤Ç¡¢
-      ¾ÏÁ´ÂΤòή¤·Æɤߤ·¤Æ¡¢¸«´·¤ì¤Ê¤¤ÆâÍƤ¬½Ð¤Æ¤¯¤ë¤È¤³¤í¤«¤é
-      Æɤ߻Ϥá¤Æ¤â¹½¤¤¤Þ¤»¤ó¡£</para>
-
-    <sect2>
-      <title>¥Ï¡¼¥É¥Ç¥£¥¹¥¯¤Î´ðÁÃ</title>
-
-      <para>¤Þ¤º¡¢¥Ï¡¼¥É¥Ç¥£¥¹¥¯¾å¤Î¥Ç¡¼¥¿¤Î°ÌÃÖ¤ò¼¨¤¹¤Î¤Ë»È¤ï¤ì¤ë¡¢
-	´ðËܤȤʤëÍѸ줬 3 ¤Ä¤¢¤ê¤Þ¤¹¡£¤½¤ì¤Ï¡¢¥·¥ê¥ó¥À¡¢¥Ø¥Ã¥É¡¢¥»¥¯¥¿¤Ç¤¹¡£
-	¤³¤ì¤é¤ÎÍѸì¤Î´Ø·¸¤òÃΤ뤳¤È¤¬¡¢¤È¤ê¤ï¤±½ÅÍפȸÀ¤¦¤ï¤±¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£
-	¤¬¡¢¤³¤ì¤é¤¬¥Ç¥£¥¹¥¯¾å¤ÎʪÍýŪ¤Ê¥Ç¡¼¥¿¤Î°ÌÃÖ¤ò¼¨¤¹¡¢
-	¤È¤¤¤¦¤³¤È¤Ï³Ð¤¨¤Æ¤ª¤­¤Þ¤·¤ç¤¦¡£</para>
-
-      <para>¥Ï¡¼¥É¥Ç¥£¥¹¥¯¤Ë¤Ï¤½¤ì¤¾¤ì¡¢
-        ¸ÇÍ­¤Î¤Î¥·¥ê¥ó¥À¿ô¡¢¥Ø¥Ã¥É¿ô¡¢¥·¥ê¥ó¥À¥Ø¥Ã¥É¤´¤È¤Î¥»¥¯¥¿¿ô¤¬¤¢¤ê¤Þ¤¹
-	(¥·¥ê¥ó¥À¥Ø¥Ã¥É¤Ï¥È¥é¥Ã¥¯¤È¤â¸Æ¤Ð¤ì¤Þ¤¹)¡£
-	¤³¤Î¾ðÊó¤Ï¡¢¥Ï¡¼¥É¥Ç¥£¥¹¥¯¤Î<quote>¥Ç¥£¥¹¥¯¥¸¥ª¥á¥È¥ê</quote>¤òÄêµÁ¤·¤Þ¤¹¡£
-	¥»¥¯¥¿¿ô¤ÏÂçÄñ¤Î¾ì¹ç¡¢1 ¥»¥¯¥¿¤¬ 512 ¥Ð¥¤¥È¡¢
-        1 ¥È¥é¥Ã¥¯¤¬ 63 ¥»¥¯¥¿¤ËÂбþ¤¹¤ë¤è¤¦¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹¤¬¡¢
-        ¥·¥ê¥ó¥À¤È¥Ø¥Ã¥É¤Î¿ô¤Ï¥Ç¥£¥¹¥¯¤Ë¤è¤Ã¤Æ¤µ¤Þ¤¶¤Þ¤Ç¤¹¡£
-        ¤³¤Î¤è¤¦¤Ë¡¢·×»»¤¹¤ë¤È¡¢
-	¥Ç¥£¥¹¥¯¤ËǼ¤á¤ë¤³¤È¤Î¤Ç¤­¤ë¥Ç¡¼¥¿¤Î¥Ð¥¤¥È¿ô¤¬Ê¬¤«¤ê¤Þ¤¹:</para>
-
-      <informalexample>
-        <para>(¥·¥ê¥ó¥À¿ô) &times; (¥Ø¥Ã¥É¿ô) &times; (63
-          ¥»¥¯¥¿/¥È¥é¥Ã¥¯) &times; (512 ¥Ð¥¤¥È/¥»¥¯¥¿)</para>
-      </informalexample>
-
-      <para>¤¿¤È¤¨¤Ð Western Digital AC31600 EIDE
-	¥Ï¡¼¥É¥Ç¥£¥¹¥¯¤Î¾ì¹ç¡¢¼¡¤Î¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£</para>
-
-      <informalexample>
-        <para>(3148 ¥·¥ê¥ó¥À) &times; (16 ¥Ø¥Ã¥É) &times; (63
-          ¥»¥¯¥¿/¥È¥é¥Ã¥¯) &times; (512 ¥Ð¥¤¥È/¥»¥¯¥¿)</para>
-      </informalexample>
-
-      <para>¤³¤ì¤ò·×»»¤¹¤ë¤È 1,624,670,208 ¥Ð¥¤¥È¡¢
-        ¤Ä¤Þ¤êÌó 1.6 GB ¤Ë¤Ê¤ê¤Þ¤¹¡£</para>
-
-      <para>
-        ¥Ï¡¼¥É¥Ç¥£¥¹¥¯¤ÎʪÍýŪ¤Ê¥Ç¥£¥¹¥¯¥¸¥ª¥á¥È¥ê¾ðÊó
-        (¥·¥ê¥ó¥À¿ô¡¢¥Ø¥Ã¥É¿ô¡¢¥È¥é¥Ã¥¯¤¢¤¿¤ê¤Î¥»¥¯¥¿¿ô) ¤Ï¡¢
-        ATAID ¤Ê¤É¤Î¥¤¥ó¥¿¡¼¥Í¥Ã¥È¾å¤Ë¤¢¤ë¥×¥í¥°¥é¥à¤òÍѤ¤¤Æ
-	Ä´¤Ù¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£¤ª¤½¤é¤¯¥Ï¡¼¥É¥Ç¥£¥¹¥¯¼«ÂΤˤ⡢
-        ¤³¤¦¤¤¤Ã¤¿¾ðÊó¤¬ÉÕ°¤·¤Æ¤¤¤ë¤Ç¤·¤ç¤¦¡£
-	¤·¤«¤·Ãí°Õ¤·¤ÆÍߤ·¤¤¤Î¤Ç¤¹¤¬¡¢BIOS LBA
-        (<xref linkend="limits"/> »²¾È)
-        ¤ò»ÈÍѤ·¤Æ¤¤¤ë¾ì¹ç¡¢
-        ʪÍýŪ¤Ê¥¸¥ª¥á¥È¥ê¾ðÊó¤òÆÀ¤ë¤¿¤á¤Î¥×¥í¥°¥é¥à¤Ï¤É¤ó¤Ê¤â¤Î¤Ç¤âÎɤ¤¡¢
-        ¤È¤¤¤¦¤ï¤±¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£
-	¤³¤ì¤Ï¡¢¿ô¿¤¯¤Î¥×¥í¥°¥é¥à
-	(¤¿¤È¤¨¤Ð <filename>MSD.EXE</filename> ¤ä FreeBSD ¤Î fdisk)
-        ¤¬ÊªÍýŪ¤Ê¥Ç¥£¥¹¥¯¥¸¥ª¥á¥È¥ê¾ðÊó¤òǧ¼±¤·¤Ê¤¤¤¿¤á¤Ç¤¹¡£
-	¤³¤ì¤é¤Ï¤½¤ÎÂå¤ê¤Ë¡¢
-        <firstterm>ÊÑ´¹¤µ¤ì¤¿¥¸¥ª¥á¥È¥ê</firstterm> (LBA ¤ò»È¤Ã¤¿²¾ÁÛŪ¤Ê¥»¥¯¥¿¿ô)
-        ¤òÊó¹ð¤·¤Þ¤¹¡£
-	¤³¤Î¸ÀÍÕ¤¬²¿¤ò°ÕÌ£¤·¤Æ¤¤¤ë¤Î¤«¤Ë¤Ä¤¤¤Æ¤Ï¡¢¸å½Ò¤·¤Þ¤¹¡£</para>
-
-      <para>¤³¤ì¤é¤ÎÍѸì¤Ë¤Ä¤¤¤ÆÌòΩ¤Ä¤³¤È¤È¤·¤Æ¤Ï¡¢
-        Í¿¤¨¤é¤ì¤¿»°¤Ä¤Î¿ô»ú&mdash;¥·¥ê¥ó¥À¿ô¡¢¥Ø¥Ã¥À¿ô¡¢
-        ¥È¥é¥Ã¥¯¤¢¤¿¤ê¤Î¥»¥¯¥¿¿ô&mdash;¤Ï¡¢¥Ï¡¼¥É¥Ç¥£¥¹¥¯¾å¤ÎÆÃÄê¤Î¥»¥¯¥¿
-	(¥Ç¡¼¥¿¤Î 512 ¥Ð¥¤¥È¥Ö¥í¥Ã¥¯) ¤òÀäÂаÌÃ֤ǷèÄꤷ¤Þ¤¹¡£
-	¥·¥ê¥ó¥À¡¢¥Ø¥Ã¥É¤Ï 0 ¤«¤é¡¢¥»¥¯¥¿¤Ï 1 ¤«¤éÈÖ¹æÉÕ¤±¤µ¤ì¤Þ¤¹¡£</para>
-
-      <para>¤µ¤é¤Ë¾Ü¤·¤¤µ»½Ñ¾ðÊó¤Ë¶½Ì£¤¬¤¢¤ëÊý¤Ë¤Ï¡¢
-	¥Ç¥£¥¹¥¯¥¸¥ª¥á¥È¥ê¡¢µ¯Æ°¥»¥¯¥¿¡¢BIOS ¤Ê¤É¤Ë´Ø¤¹¤ë¾ðÊó¤Ï
-	¥Í¥Ã¥È¾å¤Î»ê¤ë¤È¤³¤í¤ÇÆÀ¤ë¤³¤È¤¬¤Ç¤­¤ë¤³¤È¤ò¤ªÃΤ餻¤·¤Æ¤ª¤­¤Þ¤¹¡£
-	Lycos¡¢Yahoo ¤Ê¤É¤Ç
-	<literal>boot sector (µ¯Æ°¥»¥¯¥¿)</literal>¡¢
-	<literal>master boot record (¥Þ¥¹¥¿¡¼¥Ö¡¼¥È¥ì¥³¡¼¥É)</literal>
-	¤Ê¤É¤ò¸¡º÷¤·¤Æ¤ß¤Æ¤¯¤À¤µ¤¤¡£
-	¤½¤ì¤é¤ÎÌòΩ¤Ä¾ðÊó¤ÎÃæ¤Ç¤â¡¢
-        Hale Landis ¤Î <citetitle>How It Works (Æ°ºî¤Î»ÅÁȤß)</citetitle>
-	¥É¥­¥å¥á¥ó¥È½¸¤Ï»²¹Í¤Ë¤Ê¤ê¤Þ¤¹¡£¤³¤Î¥É¥­¥å¥á¥ó¥È½¸¤Ë´Ø¤·¤Æ¤Ï
-	<xref linkend="sources"/> ¤Î¾Ï¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£
-      </para>
-
-      <para>¤â¤¦ÍѸì¤Ë¤Ä¤¤¤Æ¤Ï½½Ê¬¤Ç¤¹¤Í¡£
-        ¼¡¤Ïµ¯Æ°¤Ë¤Ä¤¤¤Æ¤ªÏä·¤Þ¤¹¡£</para>
-    </sect2>
-
-    <sect2 id="booting">
-      <title>µ¯Æ°¤Î¥×¥í¥»¥¹</title>
-
-      <para>¥Ï¡¼¥É¥Ç¥£¥¹¥¯¤Î°ìÈÖÀèƬ¤Î¥»¥¯¥¿¾å
-	(¥·¥ê¥ó¥À 0¡¢¥Ø¥Ã¥É 0¡¢¥»¥¯¥¿ 1) ¤Ë¤Ï¡¢
-        ¥Þ¥¹¥¿¡¼¥Ö¡¼¥È¥ì¥³¡¼¥É (MBR) ¤¬Â¸ºß¤·¤Þ¤¹¡£
-	MBR ¤Ë¤Ï¡¢¥Ï¡¼¥É¥Ç¥£¥¹¥¯¤Î¥Þ¥Ã¥×¾ðÊ󤬴ޤޤì¤Æ¤¤¤Æ¡¢
-	ºÇÂç 4 ¤Ä¤Î <firstterm>¥Ñ¡¼¥Æ¥£¥·¥ç¥ó</firstterm>
-	¤òǧ¼±¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£¤½¤ì¤¾¤ì¤Î¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤Ï¡¢
-        ¥Ç¥£¥¹¥¯¾å¤ÎϢ³¤·¤¿¥Ç¡¼¥¿Îΰè¤Î²ô¤Ç¤¹¡£
-        FreeBSD ¤Ç¤Ï¡¢¤³¤Î¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤ò <firstterm>¥¹¥é¥¤¥¹</firstterm>
-        ¤È¸Æ¤ó¤Ç¤¤¤Þ¤¹¡£¤³¤ì¤Ï¡¢FreeBSD
-        Æȼ«¤Î¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤Èº®Í𤷤ʤ¤¤è¤¦¤Ë¤Ç¤¹¤¬¡¢
-        ¤³¤³¤Ç¤Ï¥¹¥é¥¤¥¹¤È¤¤¤¦¸ÀÍդϻȤ¤¤Þ¤»¤ó¡£
-	³Æ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤Ë¤Ï¡¢¤½¤ì¤¾¤ìÊ̤ΠOS ¤òÆþ¤ì¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£</para>
-
-      <para>MBR ¤Î³Æ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¥¨¥ó¥È¥ê¤Ë¤Ï¡¢
-	<firstterm>¥Ñ¡¼¥Æ¥£¥·¥ç¥ó ID</firstterm>¡¢
-	<firstterm>¥·¥ê¥ó¥À/¥Ø¥Ã¥É/¥»¥¯¥¿¤Î³«»Ï°ÌÃÖ</firstterm>¡¢
-	<firstterm>¥·¥ê¥ó¥À/¥Ø¥Ã¥É/¥»¥¯¥¿¤Î½ªÎ»°ÌÃÖ</firstterm>
-        ¤¬¤¢¤ê¤Þ¤¹¡£¥Ñ¡¼¥Æ¥£¥·¥ç¥ó ID ¤Ï¡¢¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤Î¼ïÎà
-	(¤É¤Î OS ¤ò»ÈÍѤ·¤Æ¤¤¤ë¤«) ¤ò¡¢
-	³«»Ï°ÌÃÖ/½ªÎ»°ÌÃÖ ¤Ï¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤Î°ÌÃÖ¤ò¼¨¤·¤Þ¤¹¡£
-	<xref linkend="tbl-pid"/> ¤Ë¡¢
-          Îɤ¯»È¤ï¤ì¤ë¥Ñ¡¼¥Æ¥£¥·¥ç¥ó ID ¤Î¥ê¥¹¥È¤ò¼¨¤·¤Þ¤¹¡£</para>
-
-      <table id="tbl-pid">
-	<title>¥Ñ¡¼¥Æ¥£¥·¥ç¥ó ID - Partition IDs</title>
-
-	<tgroup cols="2">
-	  <thead>
-	    <row>
-	      <entry>ID (hex)</entry>
-	      <entry>ÀâÌÀ</entry>
-	    </row>
-	  </thead>
-
-	  <tbody>
-	    <row>
-	      <entry>01</entry>
-	      <entry>DOS12 ´ðËÜÎΰè (12-bit FAT)</entry>
-	    </row>
-
-	    <row>
-	      <entry>04</entry>
-	      <entry>DOS16 ´ðËÜÎΰè (16-bit FAT)</entry>
-	    </row>
-
-	    <row>
-	      <entry>05</entry>
-	      <entry>DOS ³ÈÄ¥Îΰè</entry>
-	    </row>
-
-	    <row>
-	      <entry>06</entry>
-	      <entry>ÂçÍÆÎÌ DOS ´ðËÜÎΰè (&gt; 32MB)</entry>
-	    </row>
-
-	    <row>
-	      <entry>0A</entry>
-	      <entry>&os2;</entry>
-	    </row>
-
-	    <row>
-	      <entry>83</entry>
-	      <entry>Linux (EXT2FS)</entry>
-	    </row>
-
-	    <row>
-	      <entry>A5</entry>
-	      <entry>FreeBSD¡¢NetBSD¡¢386BSD (UFS)</entry>
-	    </row>
-	  </tbody>
-	</tgroup>
-      </table>
-
-      <para>Ãí: ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤Ë¤Ï¡¢µ¯Æ°¤¬¤Ç¤­¤Ê¤¤¤â¤Î¤â¤¢¤ê¤Þ¤¹
-        (Î㤨¤Ð DOS ³ÈÄ¥Îΰè)¡£
-	¤Ä¤Þ¤ê¡¢¤Ç¤­¤ë¤â¤Î¤â¤¢¤ì¤Ð¡¢¤Ç¤­¤Ê¤¤¤â¤Î¤â¤¢¤ë¤È¤¤¤¦¤ï¤±¤Ç¤¹¡£
-	¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤¬µ¯Æ°²Äǽ¤«¤É¤¦¤«¤Ï¡¢
-	³Æ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤ÎÀèƬ¤Ë¸ºß¤¹¤ë
-	<firstterm>¥Ñ¡¼¥Æ¥£¥·¥ç¥óµ¯Æ°¥»¥¯¥¿</firstterm>¤ÎÀßÄê¤Ç·è¤Þ¤ê¤Þ¤¹¡£</para>
-
-      <para>¹¥¤ß¤Î¥Ö¡¼¥È¥Þ¥Í¡¼¥¸¥ã¤òÀßÄꤷ¤¿¾ì¹ç¤ò¹Í¤¨¤Æ¤ß¤Þ¤¹¡£
-        ¥Ö¡¼¥È¥Þ¥Í¡¼¥¸¥ã¤Ï¡¢Àܳ¤µ¤ì¤Æ¤¤¤ë¤¹¤Ù¤Æ¤Î¥Ï¡¼¥É¥Ç¥£¥¹¥¯¤Î
-        MBR ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¥Æ¡¼¥Ö¥ë¤Î¥¨¥ó¥È¥ê¤ò¥ê¥¹¥È¥¢¥Ã¥×¤·¡¢
-        ¤½¤·¤Æ¤½¤Î¥ê¥¹¥È¤«¤é¡¢¤É¤Î¥¨¥ó¥È¥ê¤òµ¯Æ°¤¹¤ë¤Î¤«
-        ÁªÂò¤Ç¤­¤ë¤è¤¦¤Ë¤·¤Æ¤¯¤ì¤Þ¤¹¡£
-	¥Ö¡¼¥È¥Þ¥Í¡¼¥¸¥ã¤Ï¡¢
-        µ¯Æ°¤ÎºÝ¡¢ºÇ½é¤ËÀܳ¤¬¸¡½Ð¤µ¤ì¤¿¥Ï¡¼¥É¥Ç¥£¥¹¥¯¤Î¥Þ¥¹¥¿¡¼¥Ö¡¼¥È¥»¥¯¥¿¤Ë¤¢¤ë¡¢
-	ÆÃÊÌ¤Ê¥×¥í¥°¥é¥à¥³¡¼¥É¤Ë¤è¤Ã¤Æ¸Æ¤Ó½Ð¤µ¤ì¤Þ¤¹¡£
-        ¸Æ¤Ó½Ð¤µ¤ì¤¿¥Ö¡¼¥È¥Þ¥Í¡¼¥¸¥ã¤Ï¡¢ÁªÂò¤·¤¿¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤ËÂбþ¤¹¤ë¥¨¥ó¥È¥ê¤ò
-	MBR ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¥Æ¡¼¥Ö¥ë¤«¤éÄ´¤Ù¡¢
-        ¥·¥ê¥ó¥À/¥Ø¥Ã¥É/¥»¥¯¥¿¤Î³«»Ï°ÌÃÖ¤ò¼èÆÀ¤·¤Þ¤¹¡£
-	¤½¤ì¤«¤é¡¢¤½¤Î¥¸¥ª¥á¥È¥ê¾ðÊó¤ò»È¤¦¤³¤È¤Ç¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤Îµ¯Æ°¥»¥¯¥¿¤òÆɤ߹þ¤ß¡¢
-        À©¸æ¤ò¤½¤Á¤é¤ËÅϤ·¤Þ¤¹¡£
-	Æɤ߹þ¤Þ¤ì¤ëµ¯Æ°¥»¥¯¥¿¤Ë¤Ï¡¢¤½¤Î¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¾å¤Î OS
-        ¤ò¥í¡¼¥É¤¹¤ë¤¿¤á¤ËɬÍפʾðÊ󤬴ޤޤì¤Æ¤¤¤Þ¤¹¡£</para>
-
-      <para>º£¡¢¤«¤ë¤¯¿¨¤ì¤¿ÆâÍƤòÍý²ò¤¹¤ë¤³¤È¤Ï¡¢¤È¤Æ¤â½ÅÍפǤ¹¡£
-	¥Ï¡¼¥É¥Ç¥£¥¹¥¯¤Ë¤Ï¡¢É¬¤º MBR ¤¬Â¸ºß¤·¤Þ¤¹¡£
-	¤·¤«¤·½ÅÍפʤΤϡ¢¤½¤Î¤¦¤Á BIOS ¤Ë¤è¤êºÇ½é¤ËÀܳ¤¬¸¡½Ð¤µ¤ì¤¿
-	¥Ï¡¼¥É¥Ç¥£¥¹¥¯¾å¤Ë¤¢¤ë¤â¤Î¤Ç¤¹¡£
-	IDE ¥Ï¡¼¥É¥Ç¥£¥¹¥¯¤À¤±¤ò»ÈÍѤ·¤Æ¤¤¤ë¤Ê¤é¡¢
-	ºÇ½é¤ÎIDE ¥Ç¥£¥¹¥¯¤Ç¤¹ (Î㤨¤Ð¡¢ºÇ½é¤Î¥³¥ó¥È¥í¡¼¥é¡¼¤Î¥×¥é¥¤¥Þ¥ê¦)¡£
-	SCSI ¤À¤±¤Ç¹½À®¤µ¤ì¤¿¥·¥¹¥Æ¥à¤Î¾ì¹ç¤â¡¢Æ±¤¸¤³¤È¤¬¸À¤¨¤Þ¤¹¡£
-	¤â¤·¡¢IDE ¤È SCSI ¤ÎξÊý¤Î¥Ï¡¼¥É¥Ç¥£¥¹¥¯¤ò»ý¤Ã¤Æ¤¤¤ë¾ì¹ç¤Ë¤Ï¡¢
-	¿¤¯¤Î¾ì¹ç¡¢IDE ¥Ç¥£¥¹¥¯¤¬Àè¤Ë¸¡½Ð¤µ¤ì¤ë¤¿¤á¡¢
-        1 ÂæÌܤΠIDE ¥Ç¥£¥¹¥¯¤¬¡¢ºÇ½é¤Ë¸¡½Ð¤µ¤ì¤ë¥Ï¡¼¥É¥Ç¥£¥¹¥¯¤Ë¤Ê¤ê¤Þ¤¹¡£
-	Àè¤Û¤É½Ò¤Ù¤¿¤è¤¦¤Ë¡¢¥¤¥ó¥¹¥È¡¼¥ë¤¹¤ë¥Ö¡¼¥È¥Þ¥Í¡¼¥¸¥ã¤Ï¡¢
-	ºÇ½é¤Ë¸¡½Ð¤µ¤ì¤¿¥Ï¡¼¥É¥Ç¥£¥¹¥¯¾å¤Î MBR ¤Ë³ÊǼ¤µ¤ì¤ë¤³¤È¤Ë¤Ê¤ê¤Þ¤¹¡£</para>
-    </sect2>
-
-    <sect2 id="limits">
-      <title>µ¯Æ°¤ÎÀ©¸Â¤ÈÃí°Õ»ö¹à</title>
-
-      <para>¤³¤³¤Ç¤Ï¡¢ÍÑ¿´¤·¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¡¢¶½Ì£¿¼¤¤ÆâÍƤˤĤ¤¤Æ¤ªÏä·¤Þ¤¹¡£</para>
-
-      <sect3>
-	<title>¶²ÉݤΠ1024 ¥·¥ê¥ó¥ÀÀ©¸Â¤È BIOS LBA ¤ÎºîÍÑ</title>
-
-	<para>µ¯Æ°¥×¥í¥»¥¹¤ÎºÇ½é¤ÎÉôʬ¤Ï¡¢¤¹¤Ù¤Æ BIOS ¤Ë¤è¤Ã¤Æ¼Â¸½¤µ¤ì¤Æ¤¤¤Þ¤¹¡£
-	  (BIOS ¤È¤Ï¡¢¥³¥ó¥Ô¥å¡¼¥¿¤Î¤¿¤á¤Î¥¹¥¿¡¼¥È¥¢¥Ã¥×¥³¡¼¥É¤òÄ󶡤¹¤ë¡¢
-          ¥·¥¹¥Æ¥à¥Þ¥¶¡¼¥Ü¡¼¥É¤ËºÜ¤Ã¤Æ¤¤¤ë¥½¥Õ¥È¥¦¥§¥¢¥Á¥Ã¥×¤Î¤³¤È¤Ç¤¹)¡£
-	  ¤½¤Î¤¿¤á¡¢¤³¤ÎºÇ½é¤Î¥×¥í¥»¥¹¤Ï BIOS
-          ¥¤¥ó¥¿¥Õ¥§¡¼¥¹¤Ë¤è¤Ã¤ÆÀ©¸Â¤ò¼õ¤±¤Þ¤¹¡£</para>
-
-	<para>¤³¤Î¥×¥í¥»¥¹¤Î´Ö¡¢¥Ï¡¼¥É¥Ç¥£¥¹¥¯¤òÆɤ߹þ¤à¤¿¤á¤Ë»ÈÍѤµ¤ì¤¿
-	  BIOS ¥¤¥ó¥¿¥Õ¥§¡¼¥¹ (INT 13H¡¢Subfunction 2) ¤Ï¡¢
-	  ¥·¥ê¥ó¥ÀÈÖ¹æ¤Ø 10 ¥Ó¥Ã¥È¡¢¥Ø¥Ã¥ÉÈÖ¹æ¤Ø 8 ¥Ó¥Ã¥È¡¢
-	  ¥»¥¯¥¿ÈÖ¹æ¤Ø 6 ¥Ó¥Ã¥È³ä¤êÅö¤Æ¤Þ¤¹¡£
-	  ¤³¤ì¤¬¤³¤Î¥¤¥ó¥¿¥Õ¥§¡¼¥¹¤ò»È¤¦¾ì¹ç
-	  (Îã ¡Ä ¥Ï¡¼¥É¥Ç¥£¥¹¥¯¤Î MBR ¤«¤é¸Æ¤Ó½Ð¤µ¤ì¤ë¥Ö¡¼¥È¥Þ¥Í¡¼¥¸¥ã¤ä¡¢
-	  µ¯Æ°¥»¥¯¥¿¤«¤é¸Æ¤Ó½Ð¤µ¤ì¤ë OS ¥í¡¼¥À¡¼¤Ê¤É)
-	  ¤Ë¼¡¤Î¤è¤¦¤ÊÀ©¸Â¤òÍ¿¤¨¤ë¤Î¤Ç¤¹:</para>
-
-      <itemizedlist>
-	<listitem>
-	  <para>ºÇÂç 1024 ¥·¥ê¥ó¥À</para>
-	</listitem>
-
-	<listitem>
-	  <para>ºÇÂç 256 ¥Ø¥Ã¥É</para>
-	</listitem>
-
-	<listitem>
-	  <para>ºÇÂç 64 ¥»¥¯¥¿/¥È¥é¥Ã¥¯ (¼ÂºÝ¤Ë¤Ï 63 ¤Ç <literal>0</literal>
-	    ¤ÏÍøÍѤǤ­¤Þ¤»¤ó)</para>
-	</listitem>
-      </itemizedlist>
-
-	<para>¤µ¤Æ¡¢ÍÆÎ̤ÎÂ礭¤Ê¥Ï¡¼¥É¥Ç¥£¥¹¥¯¤Ë¤Ï¿¤¯¤Î¥·¥ê¥ó¥À¤¬¤¢¤ê¤Þ¤¹¤¬¡¢
-          ¥Ø¥Ã¥É¤Ï¿¿ô¤¢¤ê¤Þ¤»¤ó¡£
-	  ¤½¤Î¤¿¤á¡¢ÂçÍÆÎ̤Υϡ¼¥É¥Ç¥£¥¹¥¯¤Ë¤ª¤¤¤Æ¤Ï¡¢
-          ¥·¥ê¥ó¥À¿ô¤¬ 1024 ¤ò±Û¤¨¤Þ¤¹¡£
-          ¤³¤Î¤³¤È¤ä BIOS ¥¤¥ó¥¿¥Õ¥§¡¼¥¹¤ò¹Íθ¤¹¤ë¤È¡¢
-	  ¥Ï¡¼¥É¥Ç¥£¥¹¥¯¤Î¤É¤³¤«¤é¤Ç¤âµ¯Æ°¤Ç¤­¤ë¤È¤Ï¸Â¤é¤Ê¤¤¤Î¤Ç¤¹¡£
-	  ¤¹¤Ù¤Æ¤Îµ¯Æ°²Äǽ¤Ê¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤Îµ¯Æ°¥»¥¯¥¿¤«¤é¸Æ¤Ó½Ð¤µ¤ì¤ë¥Ö¡¼¥È¥Þ¥Í¡¼¥¸¥ã¤ä
-          OS ¥í¡¼¥À¡¼¤Ï 1024 ¥·¥ê¥ó¥À¤è¤ê²¼¤Î¥·¥ê¥ó¥À¤Ë¸ºß¤·¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£
-	  ¼ÂºÝ¤Ë¡¢¤ª»È¤¤¤Î¥Ï¡¼¥É¥Ç¥£¥¹¥¯¤¬Åµ·¿Åª¤Ê¤â¤Î¤Ç¥Ø¥Ã¥É¤¬ 16 ¤Ç¤¢¤ì¤Ð¡¢
-	  ¼¡¤Î¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹:</para>
-
-	<informalexample>
-	  <para>1024 ¥·¥ê¥ó¥À/¥Ç¥£¥¹¥¯ &times; 16 ¥Ø¥Ã¥É/¥Ç¥£¥¹¥¯ &times; 63
-	    ¥»¥¯¥¿/(¥·¥ê¥ó¥À - ¥Ø¥Ã¥É) &times; 512 ¥Ð¥¤¥È/¥»¥¯¥¿</para>
-	</informalexample>
-
-	<para>¤³¤ì¤¬¡¢¤è¤¯¸À¤ï¤ì¤ë 528MB À©¸Â¤Ç¤¹¡£</para>
-
-	<para>¤³¤³¤¬ BIOS LBA (Logical Block Addressing)
-          ¤¬Æþ¤Ã¤Æ¤¯¤ë¤È¤³¤í¤Ç¤¹¡£
-	  BIOS LBA ¤Ï¥·¥ê¥ó¥À¤òºÆÄêµÁ¤¹¤ë¤³¤È¤Ë¤è¤ê¡¢
-	  BIOS API ¤ò¸Æ¤Ó½Ð¤¹¥³¡¼¥É¤¬ BIOS ¥¤¥ó¥¿¥Õ¥§¡¼¥¹·Ðͳ¤Ç 1024 ¥·¥ê¥ó¥À
-	  ¤è¤ê¾å¤ÎʪÍý¥·¥ê¥ó¥À¤Ë¥¢¥¯¥»¥¹¤¹¤ë¤è¤¦¤Ë¤·¤Þ¤¹¡£
-	  ¤Ä¤Þ¤ê¡¢BIOS ¤òÄ̤·¤Æ¸«¤ë¾ì¹ç¤Ë¡¢¼ÂºÝ¤è¤ê¾¯¤Ê¤¤¥·¥ê¥ó¥À¿ô¡¢
-	  ¿¤¤¥Ø¥Ã¥É¿ô¤È¤·¤Æ°·¤ï¤ì¤ë¤è¤¦¤Ë¥·¥ê¥ó¥À¿ô¡¢
-	  ¥Ø¥Ã¥É¿ô¤òºÆ¥Þ¥Ã¥×¤·¤Æ¤¯¤ì¤ë¤Î¤Ç¤¹¡£
-	  ¸À¤¤Âؤ¨¤ì¤Ð¡¢¥·¥ê¥ó¥À¿ô¤È¥Ø¥Ã¥É¿ô¤Î¥Ð¥é¥ó¥¹¤òÊѹ¹¤¹¤ë¤³¤È¤Ç¡¢
-	  ¥Ï¡¼¥É¥Ç¥£¥¹¥¯¤¬ÁêÂÐŪ¤Ë¥Ø¥Ã¥É¤¬¾¯¤Ê¤¯¡¢
-	  ¥·¥ê¥ó¥À¤¬Â¿¤¯¤Ê¤ë¤È¤¤¤¦¤³¤È¤òÍøÍѤ¹¤ë¤³¤È¤Ë¤è¤ê¡¢
-	  ÁÐÊý¤Î¿ô¤¬¾åµ­¤Ë½Ò¤Ù¤é¤ì¤Æ¤¤¤ëÀ©¸Â (1024 ¥·¥ê¥ó¥À¡¢256 ¥Ø¥Ã¥É)
-	  ¤ò±Û¤¨¤Ê¤¤¤È¸À¤¦¤³¤È¤Ë¤Ê¤ê¤Þ¤¹¡£</para>
-
-	<para>BIOS LBA ¤òÍѤ¤¤ë¤³¤È¤Ç¡¢
-	  ¥Ï¡¼¥É¥Ç¥£¥¹¥¯ÍÆÎ̤ÎÀ©¸Â¤¬²¾ÁÛŪ¤Ë¤Ê¤¯¤Ê¤ê¤Þ¤·¤¿
-	  (¤Þ¤¡¡¢8GB ¤Þ¤Ç¾å¤¬¤Ã¤¿¤È¸À¤¦¤È¤³¤í¤Ç¤·¤ç¤¦¤«)¡£
-	  LBA BIOS ¤ò»ÈÍѤ·¤Æ¤¤¤ë¾ì¹ç¤Ï¡¢FreeBSD ¤Þ¤¿¤Ï ¾¤Î OS
-	  ¤ò¤É¤³¤Ë¤Ç¤âºÜ¤»¤ë¤³¤È¤¬¤Ç¤­¡¢
-	  1024 ¤Î¥·¥ê¥ó¥ÀÀ©¸Â¤Ë°ú¤Ã¤«¤«¤ë¤³¤È¤â¤¢¤ê¤Þ¤»¤ó¡£</para>
-
-	<para>1.6GB Western Digital ¤òºÆÅÙÎã¤È¤·¤Æ¹Í¤¨¤Æ¤ß¤Þ¤·¤ç¤¦¡£
-	  ʪÍýŪ¤Ê¥¸¥ª¥á¥È¥ê¤Ï¡¢¼¡¤Î¤È¤ª¤ê¤Ç¤¹:</para>
-
-	<informalexample>
-	  <para>(3148 ¥·¥ê¥ó¥À¡¢16 ¥Ø¥Ã¥É¡¢63 ¥»¥¯¥¿/¥È¥é¥Ã¥¯¡¢512
-	    ¥Ð¥¤¥È/¥»¥¯¥¿)</para>
-	</informalexample>
-
-	<para>¤·¤«¤·¤Ê¤¬¤é¡¢BIOS LBA ¤Ï¼¡¤Î¤è¤¦¤ËºÆ¥Þ¥Ã¥Ô¥ó¥°¤ò¹Ô¤¤¤Þ¤¹:
-	</para>
-
-	<informalexample>
-	  <para>(787 ¥·¥ê¥ó¥À¡¢64 ¥Ø¥Ã¥É¡¢63 ¥»¥¯¥¿/¥È¥é¥Ã¥¯¡¢512
-	    ¥Ð¥¤¥È/¥»¥¯¥¿)</para>
-	</informalexample>
-
-	<para>¼ÂºÝ¤Ë¤ÏƱ¤¸¥µ¥¤¥º¤Î¥Ç¥£¥¹¥¯¤Ê¤Î¤Ç¤¹¤¬¡¢
-	  ¥·¥ê¥ó¥À¤È¥Ø¥Ã¥É¤Î·×»»¤Ï BIOS API ¤ÎÈÏ°ÏÆâ¤Ç¹Ô¤ï¤ì¤Þ¤¹
-	  (¶öÁ³¤Ë¤â¡¢»ä¤Î¥Ï¡¼¥É¥Ç¥£¥¹¥¯¤Î°ì¤Ä¤Ë¤Ï¡¢
-	  Linux ¤È FreeBSD ¤¬ÊªÍýŪ¤Ê¥·¥ê¥ó¥À 1024 ÈÖÌܤè¤ê¾å¤ËºÜ¤Ã¤Æ¤¤¤Þ¤¹¡£
-	  ¤³¤ì¤é¤ÎOS ¤¬ÌäÂê¤Ê¤¯µ¯Æ°¤¹¤ë¤Î¤â¡¢BIOS LBA ¤Î¤ª¤«¤²¤Ê¤Î¤Ç¤¹)¡£</para>
-      </sect3>
-
-      <sect3>
-	<title>¥Ö¡¼¥È¥Þ¥Í¡¼¥¸¥ã¤È¥Ç¥£¥¹¥¯¤Î³ä¤êÅö¤Æ</title>
-
-	<para>¥Ö¡¼¥È¥Þ¥Í¡¼¥¸¥ã¤Î¥¤¥ó¥¹¥È¡¼¥ë»þ¡¢
-	  ¾¤Ëµ¤¤ò¤Ä¤±¤Í¤Ð¤¤¤±¤Ê¤¤¤³¤È¤Ï¡¢
-	  ¥Ö¡¼¥È¥Þ¥Í¡¼¥¸¥ãÍѤȤ·¤ÆÎΰè¤ò³ä¤êÅö¤Æ¤ë¤³¤È¤Ç¤¹¡£
-	  1 ¤Ä¡¢¤¢¤ë¤¤¤ÏÊ£¿ô¤Î OS ¤ÎºÆ¥¤¥ó¥¹¥È¡¼¥ë¤ò;µ·¤Ê¤¯¤µ¤ì¤¿¤¯¤Ê¤¤¤Ê¤é¡¢
-	  °ìÈÖµ¤¤Ë¤·¤Ê¤¯¤Æ¤Ï¤¤¤±¤Ê¤¤¥È¥Ô¥Ã¥¯¤Ç¤¹¡£
-	</para>
-
-	<para>(MBR ¤Î¤¢¤ë) ¥Þ¥¹¥¿¡¼¥Ö¡¼¥È¥»¥¯¥¿¡¢
-	  ¥Ñ¡¼¥Æ¥£¥·¥ç¥óµ¯Æ°¥»¥¯¥¿¡¢µ¯Æ°¥×¥í¥»¥¹ ¤Ë¤Ä¤¤¤Æ¤Î
-	  <xref linkend="booting"/> ¤ÎÀâÌÀ¤òÆɤó¤À¸å¤Ï¡¢
-	  ¼«Ê¬¤Î¥Ï¡¼¥É¥Ç¥£¥¹¥¯¤Î¤É¤³¤Ë¡¢
-	  ¤³¤Îµ¤¤Î¤­¤¯¥Ö¡¼¥È¥Þ¥Í¡¼¥¸¥ã¤¬Â¸ºß¤¹¤ë¤Î¤«µ¤¤Ë¤Ê¤ë¤È¤³¤í¤Ç¤¹¤Í¡£
-	  ¤½¤ì¤Ï¤È¸À¤¤¤Þ¤¹¤È¡¢¤¤¤¯¤Ä¤«¤Î¥Ö¡¼¥È¥Þ¥Í¡¼¥¸¥ã¤Ï¡¢
-	  ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¥Æ¡¼¥Ö¥ë¤ÎÎ٤Ρ¢¥Þ¥¹¥¿¡¼¥Ö¡¼¥È¥»¥¯¥¿
-	  (¥·¥ê¥ó¥À 0¡¢¥Ø¥Ã¥É 0¡¢¥»¥¯¥¿ 1) ¤ËǼ¤Þ¤êÀÚ¤ëÄø¤Ë¾®¤µ¤¤¤Î¤Ç¤¹¡£
-	  ¥Ö¡¼¥È¥Þ¥Í¡¼¥¸¥ã¤Ë¤è¤Ã¤Æ¤Ï¤â¤¦¾¯¤·ÍÆÎ̤¬É¬Íפʤâ¤Î¤â¤¢¤ê¡¢
-	  ¤½¤ÎÎΰè¤Ï°ìÈ̤ˤ϶õ¤¤¤Æ¤¤¤ë¤¿¤á¡¢
-	  ¥·¥ê¥ó¥À 0 ¥Ø¥Ã¥É 0 ¥»¥¯¥¿ 1 ¤Ë¤¢¤ë¥Þ¥¹¥¿¡¼¥Ö¡¼¥È¥»¥¯¥¿¤ò
-	  ±Û¤¨¤¿¤¤¤¯¤Ä¤«¤Î¥»¥¯¥¿¤Ë¤Þ¤Ç¼«¿È¤ò³ÈÄ¥¤·¤Æ¤¤¤Þ¤¹¡£
-	</para>
-
-	<para>¤¢¤ê¤¬¤¿¤¤¤³¤È¤Ë
-	  (FreeBSD ¤ò´Þ¤à) OS ¤Î¤¤¤¯¤Ä¤«¤Ï¡¢
-          ɬÍפʤé¤Ð¥Þ¥¹¥¿¡¼¥Ö¡¼¥È¥»¥¯¥¿¤Îľ¸å¡¢
-	  ¥·¥ê¥ó¥À 0¡¢¥Ø¥Ã¥É 0¡¢¥»¥¯¥¿ 2 ¤«¤é¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤ò
-	  µ¯Æ°¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
-	  ¼ÂºÝ¤Ë¡¢ÀèƬ¤Ë¶õ¤­¤Î¤¢¤ë¡¢¤¢¤ë¤¤¤ÏÁ´ÂΤ¬¶õ¤Î¥Ç¥£¥¹¥¯¤Ç
-	  FreeBSD ¤Î sysinstall ¤ò¼Â¹Ô¤¹¤ë¤È¡¢¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï¤½¤Î¾ì½ê¤«¤é
-	  FreeBSD ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤¬»Ï¤Þ¤ê¤Þ¤¹
-	  (¾¯¤Ê¤¯¤È¤â»ä¤¬¹Ô¤Ã¤¿»þ¤Ï¤½¤¦¤Ç¤·¤¿)¡£
-	  ¤½¤·¤Æ¡¢MBR ¤Î¸å¤Ë¤¢¤ë¤¤¤¯¤Ä¤«¤Î¥»¥¯¥¿¤ò¾ÃÈñ¤¹¤ë¤è¤¦¤Ê
-	  ¥Ö¡¼¥È¥Þ¥Í¡¼¥¸¥ã¤ò¥¤¥ó¥¹¥È¡¼¥ë¤¹¤ë¾ì¹ç¡¢
-	  ºÇ½é¤Î¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤Î¥Ç¡¼¥¿¤ÎÀèƬ¤¬¾å½ñ¤­¤µ¤ì¤Þ¤¹¡£
-	  FreeBSD ¤Î¾ì¹ç¤Ï¡¢¥Ç¥£¥¹¥¯¥é¥Ù¥ë¤¬¾å½ñ¤­¤µ¤ì¡¢
-	  FreeBSD ¤¬µ¯Æ°¤Ç¤­¤Ê¤¯¤Ê¤ê¤Þ¤¹¡£</para>
-
-	<para>¤³¤Î¤è¤¦¤ÊÌäÂê¤òÈò¤±¤ë´Êñ¤ÊÊýË¡¤È¤·¤Æ¤Ï
-	  (¤Þ¤¿¡¢¸å¤Ç°Û¤Ê¤ë¥Ö¡¼¥È¥Þ¥Í¡¼¥¸¥ã¤ò»î¤¹½ÀÆðÀ­¤ò»ý¤¿¤¹¤¿¤á¤Ë¤â)¡¢
-	  ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤òÀÚ¤ë»þ¤Ë¡¢
-	  ¥Ï¡¼¥É¥Ç¥£¥¹¥¯¤ÎºÇ½é¤Î¥È¥é¥Ã¥¯¤ò³ä¤êÅö¤Æ¤Ê¤¤¤Þ¤Þ
-	  ¤Þ¤ë¤Þ¤ë»Ä¤·¤Æ¤ª¤¯¤³¤È¤Ç¤¹¡£
-	  ¤Ä¤Þ¤ê¡¢¥·¥ê¥ó¥À 0¡¢¥Ø¥Ã¥É 0¡¢¥»¥¯¥¿ 2 ¤«¤é¥·¥ê¥ó¥À 0¡¢
-	  ¥Ø¥Ã¥É 0¡¢¥»¥¯¥¿ 63 ¤Þ¤Ç¤ò¶õ¤±¤Æ¤ª¤­¡¢
-	  ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤ò¥·¥ê¥ó¥À 0¡¢¥Ø¥Ã¥É 1¡¢¥»¥¯¥¿ 1
-	  ¤«¤é³«»Ï¤¹¤ë¤È¤¤¤¦¤³¤È¤Ç¤¹¡£
-	  ¹¹¤ËÎɤ¤¤³¤È¤Ë¡¢¥Ï¡¼¥É¥Ç¥£¥¹¥¯¤ÎÀèƬ¤Ë DOS ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤ò
-	  ºîÀ®¤¹¤ëºÝ¡¢DOS ¤Ï¥Ç¥Õ¥©¥ë¥È¤Ç¤³¤Î¾ì½ê¤ò¶õ¤±¤Æ¤ª¤­¤Þ¤¹
-	  (¤³¤ì¤¬¥Ö¡¼¥È¥Þ¥Í¡¼¥¸¥ã¤Î¤¤¤¯¤Ä¤«¤Ï¤½¤Î¾ì½ê¤¬¶õ¤­¤À¤È
-	  ²¾Äꤹ¤ë¤È¤¤¤¦Íýͳ¤Ç¤¹)¡£
-	  ¤È¤¤¤¦¤ï¤±¤Ç¡¢¥Ç¥£¥¹¥¯¤ÎÀèƬ¤Ë DOS ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤òºîÀ®¤¹¤ë¤³¤È¤Ç
-	  ¤³¤ÎÌäÂê¤òÈò¤±¤ë¤³¤È¤¬¤Ç¤­¤ë¤Î¤Ç¤¹¡£
-	  »ä¤Ï¤³¤Î¤ä¤êÊý¤¬¹¥¤ß¤Ç¡¢¼«Ê¬¤Ç 1MB ¤Î DOS ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤òÀèƬ¤Ë
-	  ºîÀ®¤·¤Þ¤¹¡£¤½¤¦¤¹¤ë¤È¡¢¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤òÀÚ¤êľ¤¹»þ¡¢
-	  DOS ¤Î¥É¥é¥¤¥Ö̾¤ò¤º¤é¤¹¤³¤È¤âɬÍפʤ¤¤Î¤Ç¤¹¡£</para>
-
-	<para>»²¹Í¤È¤·¤Æ¡¢¼¡¤Î¥Ö¡¼¥È¥Þ¥Í¡¼¥¸¥ã¤Ï¥³¡¼¥É¤È¥Ç¡¼¥¿¤ò
-	  µ­Ï¿¤¹¤ëºÝ¤Ë¥Þ¥¹¥¿¡¼¥Ö¡¼¥È¥»¥¯¥¿¤ò»ÈÍѤ·¤Þ¤¹:</para>
-
-	<itemizedlist>
-	  <listitem>
-	    <para>OS-BS 1.35</para>
-	  </listitem>
-
-	  <listitem>
-	    <para>Boot Easy</para>
-	  </listitem>
-
-	  <listitem>
-	    <para>LILO</para>
-	  </listitem>
-	</itemizedlist>
-
-	<para>¼¡¤Î¥Ö¡¼¥È¥Þ¥Í¡¼¥¸¥ã¤Ï¥Þ¥¹¥¿¡¼¥Ö¡¼¥È¥»¥¯¥¿¤Î¸å¤Ë¤¢¤ë
-	  ¥»¥¯¥¿¤ò¤¤¤¯¤Ä¤«»ÈÍѤ·¤Þ¤¹:</para>
-
-	<itemizedlist>
-	  <listitem>
-	    <para>OS-BS 2.0 Beta 8 (sectors 2-5)</para>
-	  </listitem>
-
-	  <listitem>
-	    <para>&os2; boot manager</para>
-	  </listitem>
-	</itemizedlist>
-      </sect3>
-
-      <sect3>
-	<title>¥Þ¥·¥ó¤¬µ¯Æ°¤·¤Ê¤¤¾ì¹ç¤Ï¤É¤¦¤¹¤ë¤«?</title>
-
-	<para>¥Ö¡¼¥È¥Þ¥Í¡¼¥¸¥ã¤ò¥¤¥ó¥¹¥È¡¼¥ë¤·¤¿ºÝ¤Ë¡¢
-	  MBR ¤¬µ¯Æ°¤·¤Ê¤¤¾õÂ֤ˤ·¤Æ¤·¤Þ¤¦¤³¤È¤¬¤¢¤ê¤Þ¤¹¡£
-	  ¤¢¤Þ¤ê¤Ê¤¤¤³¤È¤Ç¤¹¤¬¡¢´û¤Ë¥¤¥ó¥¹¥È¡¼¥ë¤·¤¿¥Ö¡¼¥È¥Þ¥Í¡¼¥¸¥ã¤¬
-	  ¤¢¤ë¾õÂÖ¤Ç FDISK ¤·¤Æ¤·¤Þ¤¦¤Èµ¯¤³¤ë¤³¤È¤¬¤¢¤ê¤Þ¤¹¡£</para>
-
-	<para>¥Ï¡¼¥É¥Ç¥£¥¹¥¯¤Ëµ¯Æ°²Äǽ¤Ê DOS ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤¬¤¢¤ë¾ì¹ç¡¢
-	  DOS ¥Õ¥í¥Ã¥Ô¡¼¤«¤éµ¯Æ°¤·¤Þ¤¹¡£¼¡¤ò¼Â¹Ô¤·¤Þ¤¹:</para>
-
-	<informalexample>
-	  <screen>A:\&gt; <userinput>FDISK /MBR</userinput></screen>
-	</informalexample>
-
-	<para>¥ª¥ê¥¸¥Ê¥ë¤ËÌ᤹¤Ë¤Ï¡¢¥·¥ó¥×¥ë¤Ê DOS ¤Îµ¯Æ°¥³¡¼¥É¤ò
-	  ¥·¥¹¥Æ¥à¤ËÌᤷ¤Þ¤¹¡£¤½¤¦¤¹¤ë¤È¡¢¥Ï¡¼¥É¥Ç¥£¥¹¥¯¤«¤é DOS
-	  (DOS ¤Ë¸Â¤ë) ¤òµ¯Æ°¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
-	  ¤â¤¦°ì¤Ä¤Î¼ê¤È¤·¤Æ¤Ï¡¢µ¯Æ°²Äǽ¤Ê¥Õ¥í¥Ã¥Ô¡¼¤ò»È¤Ã¤Æ¡¢
-	  ¥Ö¡¼¥È¥Þ¥Í¡¼¥¸¥ã¤Î¥¤¥ó¥¹¥È¡¼¥ë¥×¥í¥°¥é¥à¤òºÆÅټ¹Ԥ·¤Þ¤¹¡£</para>
-      </sect3>
-    </sect2>
-  </sect1>
-</article>
diff --git a/ja_JP.eucJP/articles/zip-drive/Makefile b/ja_JP.eucJP/articles/zip-drive/Makefile
deleted file mode 100644
index 1c2f7a0648..0000000000
--- a/ja_JP.eucJP/articles/zip-drive/Makefile
+++ /dev/null
@@ -1,18 +0,0 @@
-#
-# $FreeBSD$
-#
-# Article: IOmega ZIP Drivse
-#
-# Original revision: 1.4
-
-DOC?= article
-
-FORMATS?= html
-
-INSTALL_COMPRESSED?=gz
-INSTALL_ONLY_COMPRESSED?=
-
-SRCS=	article.sgml
-
-DOC_PREFIX?= ${.CURDIR}/../../..
-.include "${DOC_PREFIX}/share/mk/doc.project.mk"
diff --git a/ja_JP.eucJP/articles/zip-drive/article.sgml b/ja_JP.eucJP/articles/zip-drive/article.sgml
deleted file mode 100644
index 942643d3ca..0000000000
--- a/ja_JP.eucJP/articles/zip-drive/article.sgml
+++ /dev/null
@@ -1,345 +0,0 @@
-<?xml version="1.0" encoding="euc-jp" standalone="no"?>
-<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V4.2-Based Extension//EN"
-	"../../../share/sgml/freebsd42.dtd" [
-<!ENTITY % entities PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Entity Set//JA" "../../share/sgml/entities.ent">
-%entities;
-]>
-
-<!--
-    The FreeBSD Documentation Project
-    The FreeBSD Japanese Documentation Project
-
-    Original revision: 1.15
-    $FreeBSD$
--->
-<!--
-Ìõ:
-¹âÅÄ Ãμù otemachi@osaka.interq.or.jp
--->
-<article lang='ja'>
-  <articleinfo>
-    <title>&iomegazip; ¥É¥é¥¤¥Ö</title>
-
-    <authorgroup>
-      <author>
-	<firstname>Jason</firstname>
-	<surname>Bacon</surname>
-
-	<affiliation>
-	  <address><email>acadix@execpc.com</email></address>
-	</affiliation>
-      </author>
-    </authorgroup>
-
-    <legalnotice id="trademarks" role="trademarks">
-      &tm-attrib.freebsd;
-      &tm-attrib.adaptec;
-      &tm-attrib.iomega;
-      &tm-attrib.microsoft;
-      &tm-attrib.opengroup;
-      &tm-attrib.general;
-    </legalnotice>
-
-    <pubdate>$FreeBSD$</pubdate>
-
-    <releaseinfo>$FreeBSD$</releaseinfo>
-  </articleinfo>
-
-  <sect1>
-    <title>&iomegazip; ¥É¥é¥¤¥Ö¤Î´ðÁÃ</title>
-
-    <para>&iomegazip; ¥Ç¥£¥¹¥¯¤Ï¡¢¥¢¥¤¥ª¥á¥¬¼Ò¤«¤éȯÇ䤵¤ì¤Æ¤¤¤ë
-      ZIP ¥Ç¥£¥¹¥¯¥É¥é¥¤¥Ö¤ÇÆɤ߽ñ¤­²Äǽ¤ÊÂçÍÆÎ̤Υê¥à¡¼¥Ð¥Ö¥ë¼§µ¤¥Ç¥£¥¹¥¯¤Ç¤¹¡£
-      ZIP ¥Ç¥£¥¹¥¯¤Ï¥Õ¥í¥Ã¥Ô¡¼¥Ç¥£¥¹¥¯¤È»÷¤Æ¤¤¤Þ¤¹¤¬¡¢
-      ZIP ¥Ç¥£¥¹¥¯¤ÎÊý¤¬Èó¾ï¤Ë¹â®¤ÇÈæ³Ó¤Ë¤Ê¤é¤Ê¤¤¤Û¤ÉÂçÍÆÎ̤Ǥ¹¡£
-      ¤È¤¤¤¦¤Î¤Ï¥Õ¥í¥Ã¥Ô¡¼¥Ç¥£¥¹¥¯¤ÎÍÆÎ̤¬ÂçÄñ
-      1.44M ¥Ð¥¤¥È¤Ç¤¢¤ë¤Î¤ËÂФ·¡¢ZIP
-      ¥Ç¥£¥¹¥¯¤ÎÍÆÎ̤ϡ¢100M ¥Ð¥¤¥È¤«
-      250M ¥Ð¥¤¥È¤ÎÆó¼ïÎढ¤ê¤Þ¤¹¡£
-      120M ¥Ð¥¤¥È¤ÎÍÆÎ̤ò»ý¤Á¡¢
-      ½¾Íè¤Î 1.44M ¥Ð¥¤¥È¤Î¥Ç¥£¥¹¥¯¤â»ÈÍѤǤ­¤ë
-      SuperDisk ¤È¤¤¤¦¥Õ¥í¥Ã¥Ô¡¼¤¬¤¢¤ê¤Þ¤¹¤¬¡¢ZIP
-      ¥Ç¥£¥¹¥¯¤È¤Ïº®Æ±¤·¤Ê¤¤¤Ç¤¯¤À¤µ¤¤¡£</para>
-
-    <para>¥¢¥¤¥ª¥á¥¬¼Ò¤Ï¡¢&jaz;/JAZZ
-      ¥É¥é¥¤¥Ö¤È¤¤¤¦¤µ¤é¤ËÂçÍÆÎ̤ÇÍ¥¤ì¤¿À­Ç½¤ò»ý¤Ã¤¿¥Ç¥£¥¹¥¯¥É¥é¥¤¥Ö¤âȯÇ䤷¤Æ¤¤¤Þ¤¹¡£
-      JAZZ ¥É¥é¥¤¥Ö¤ÎÍÆÎÌ¤Ï 1G ¥Ð¥¤¥È¤« 2G ¥Ð¥¤¥È¤ÎÆó¼ïÎà¤Ç¤¹¡£</para>
-
-    <para>ZIP ¥É¥é¥¤¥Ö¤Ë¤Ï¡¢°Ê²¼¤Î 3 ¼ïÎà¤Î¥¤¥ó¥¿¥Õ¥§¡¼¥¹¤¬ÍÑ°Õ¤µ¤ì¤Æ¤ª¤ê¡¢
-      Æ⢤⳰ÉÕ¤±¤â²Äǽ¤Ç¤¹¡£</para>
-
-    <orderedlist>
-      <listitem>
-	<para>SCSI (Small Computer Standard Interface)
-          ¤ÏºÇ¤â¹â®¡¦Àº¹ª¤Ç³ÈÄ¥À­¤â¹â¤¯¡¢
-          ¤½¤·¤ÆºÇ¤â¹â²Á¤Ê¥¤¥ó¥¿¥Õ¥§¡¼¥¹¤Ç¤¹¡£
-          SCSI ¥¤¥ó¥¿¥Õ¥§¡¼¥¹¤Ï¡¢
-          ¥Ç¥£¥¹¥¯¥É¥é¥¤¥Ö¡¢¥Æ¡¼¥×¥É¥é¥¤¥Ö¡¢
-          ¥¹¥­¥ã¥Ê¡¼¤Ê¤É¤È¤¤¤Ã¤¿¤¹¤Ù¤Æ¤Î¥¿¥¤¥×¤Î¼þÊÕµ¡´ï¤ÈÀܳ¤¹¤ë¤¿¤á¤Ë¡¢
-          PC ¤«¤é RISC ¥ï¡¼¥¯¥¹¥Æ¡¼¥·¥ç¥ó¡¢
-          ¥ß¥Ë¥³¥ó¤Ë»ê¤ë¤Þ¤Ç¡¢¤Û¤È¤ó¤É¤Î¥³¥ó¥Ô¥å¡¼¥¿¤Ç»ÈÍѤµ¤ì¤Æ¤­¤Þ¤·¤¿¡£
-          SCSI Âбþ ZIP ¥É¥é¥¤¥Ö¤Ï¡¢
-          Æ⢤â (¤â¤· SCSI ¥Û¥¹¥È¥¢¥À¥×¥¿¤Ë³°ÉÕ¤±¥³¥Í¥¯¥¿¤¬¤¢¤ì¤Ð)
-          ³°ÉÕ¤±¤â²Äǽ¤Ç¤¹¡£</para>
-
-	<note>
-	  <para>SCSI ¤ÇÀܳ¤µ¤ì¤¿³°ÉÕ¤±¤ÎÁõÃÖ¤ò»ÈÍѤ¹¤ëºÝ¡¢
-            Æ°ºîÃæ¤Ë SCSI ¥Ð¥¹¤«¤é¥±¡¼¥Ö¥ë¤òÈ´¤­º¹¤·¤·¤Ê¤¤¤Ç¤¯¤À¤µ¤¤¡£
-            ¤µ¤â¤Ê¤¤¤È¡¢ÁÞÆþ¤µ¤ì¤Æ¤¤¤¿¥Ç¥£¥¹¥¯¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ò»½ý
-            ¤¹¤ë¶²¤ì¤¬¤¢¤ê¤Þ¤¹¡£</para>
-	</note>
-
-	<para>ºÇ¹â¤Î¥Ñ¥Õ¥©¡¼¥Þ¥ó¥¹¤È¥»¥Ã¥È¥¢¥Ã¥×¤Î¼ê·Ú¤µ¤ò˾¤à¤Ê¤é¡¢
-          SCSI ¤Ï¥Ù¥¹¥È¥Á¥ç¥¤¥¹¤Ç¤¹¡£
-          °ìÉô¤Î¥Ï¥¤¥¨¥ó¥É¥µ¡¼¥Ð¤ò½ü¤­¡¢Â¿¤¯¤Î PC ¤Ï¥Ó¥ë¥È¥¤¥ó¤Î
-          SCSI ¤ò¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤Ê¤¤¤¿¤á¡¢
-          SCSI ¥Û¥¹¥È¥¢¥À¥×¥¿¤òÄɲäǹØÆþ¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
-          ¼ïÎà¤Ë¤â¤è¤ê¤Þ¤¹¤¬¡¢SCSI ¥Û¥¹¥È¥¢¥À¥×¥¿¤Ï 7 Â椫 15 Âæ¤Î
-          SCSI ¥Ç¥Ð¥¤¥¹¤òÀܳ¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£</para>
-
-	<para>¤½¤ì¤¾¤ì¤Î SCSI ¥Ç¥Ð¥¤¥¹¤Ï¤½¤ì¼«¿È¤Î¥³¥ó¥È¥í¡¼¥é¤ò»ý¤Ã¤Æ¤ª¤ê¡¢
-          ¤½¤·¤Æ¤½¤ì¤é¤ÏÈó¾ï¤Ë¸­¤¯¡¢¤è¤¯É¸½à²½¤µ¤ì¤Æ¤¤¤ë¤Î¤Ç
-          (SCSI ¤Î 2 ÈÖÌܤΠ"S" ¤Ï "ɸ½à" ¤òɽ¤·¤Þ¤¹)¡¢
-          OS ¤Ï SCSI ¤Î¥Ç¥£¥¹¥¯¥É¥é¥¤¥Ö¤ò¤¹¤Ù¤ÆƱ¤¸¤è¤¦¤Ë°·¤¦¤³¤È¤¬¤Ç¤­¡¢
-          ¤Þ¤¿¤½¤ì¤Ï SCSI ¤Î¥Æ¡¼¥×¥É¥é¥¤¥Ö¤Ê¤É¤âƱÍͤǤ¹¡£
-          SCSI ¥Ç¥Ð¥¤¥¹¤ò»ÈÍѤ¹¤ë¤¿¤á¤Ë¤Ï¡¢¥Û¥¹¥È¥¢¥À¥×¥¿ÍѤΥɥ饤¥Ð¤È
-          SCSI ¥Ç¥£¥¹¥¯¥É¥é¥¤¥ÖÍѥɥ饤¥Ð¡¢
-          SCSI ¥Æ¡¼¥×¥É¥é¥¤¥ÖÍѥɥ饤¥Ð¤È¤¤¤Ã¤¿ÁõÃÖ¤ËÂбþ¤¹¤ëɸ½à¤Î¥É¥é¥¤¥Ð¤òÍÑ°Õ¤¹¤ë¤À¤±¤ÇÎɤ¤¤Î¤Ç¤¹¡£
-          ¤µ¤é¤Ëµ¡¼ï¤ËÆò½¤·¤¿¥É¥é¥¤¥Ð (¤¿¤È¤¨¤Ð DAT
-          ¥É¥é¥¤¥Ö¤Ê¤É) ¤â¸ºß¤·¤Þ¤¹¤¬¡¢
-          ÂçÄñɸ½à¤Î¥É¥é¥¤¥Ð¤ò»ÈÍѤ·¤Æ¤âÆ°ºî¤·¤Þ¤¹¡£
-          ¤½¤¦¤¤¤Ã¤¿ÆÃÊ̤ʥɥ饤¥Ð¤Ï¡¢
-          µ¡¼ïÆÃÍ­¤Îµ¡Ç½¤òÍøÍѤ¹¤ë¤¿¤á¤Ë½ñ¤«¤ì¤¿¤â¤Î¤Ç¤¹¡£</para>
-
-	<para>ZIP ¥É¥é¥¤¥Ö¤ò»ÈÍѤ¹¤ë¤¿¤á¤Ë¤Ï¡¢
-          ñ¤Ë <filename>/dev</filename>
-          ¤ÎÃ椫¤é ZIP ¥É¥é¥¤¥Ö¤Î¥Ç¥Ð¥¤¥¹¥Õ¥¡¥¤¥ë¤ò¸«¤Ä¤±¤ë¤À¤±¤ÇÎɤ¤¤Î¤Ç¤¹¡£
-          ZIP ¥É¥é¥¤¥Ö¤Î¥Ç¥Ð¥¤¥¹¥Õ¥¡¥¤¥ë¤Ïµ¯Æ°»þ¤Ëɽ¼¨¤µ¤ì¤ë¥Ö¡¼¥È¥á¥Ã¥»¡¼¥¸¤«¡¢
-	  <filename>/var/log/messages</filename> ¤ÎÃ椫¤é</para>
-
-	<programlisting>da1: &lt;IOMEGA ZIP 100 D.13&gt; Removable Direct Access
-SCSI-2 Device</programlisting>
-
-	<para>¤È¤¤¤¦¥á¥Ã¥»¡¼¥¸¤ò¸«¤Ä¤±¤ë¤³¤È¤ÇÆÃÄê¤Ç¤­¤Þ¤¹¡£
-          ¾å¤ÎÎã¤Î¾ì¹ç¡¢
-          ZIP ¥É¥é¥¤¥Ö¤Î¥Ç¥Ð¥¤¥¹¥Õ¥¡¥¤¥ë¤Ï
-	  <filename>/dev/da1</filename>
-          ¤Ç¤¢¤ë¤È¤¤¤¦¤³¤È¤òɽ¤·¤Æ¤¤¤Þ¤¹¡£</para>
-      </listitem>
-
-      <listitem>
-        <para>IDE (Integrated Drive Electronics) ¥¤¥ó¥¿¥Õ¥§¡¼¥¹¤Ï¡¢
-          ¿¤¯¤Î¥Ç¥¹¥¯¥È¥Ã¥× PC ¤Ç»ÈÍѤµ¤ì¤Æ¤¤¤ëÄã²Á³Ê¤Ê¥¤¥ó¥¿¥Õ¥§¡¼¥¹¤Ç¤¹¡£
-          ¤Û¤È¤ó¤É¤Î IDE ¥Ç¥Ð¥¤¥¹¤Ïɬ¤ºÆ⢤ˤʤäƤ¤¤Þ¤¹¡£</para>
-
-	<para>IDE Àܳ¤Î ZIP ¥É¥é¥¤¥Ö¤ÎÀ­Ç½¤Ï
-          SCSI Àܳ¤Î ZIP ¥É¥é¥¤¥Ö¤ËɤŨ¤·¤Þ¤¹¡£
-          (IDE ¥¤¥ó¥¿¥Õ¥§¡¼¥¹¤Ï SCSI ¤è¤ê¹â®¤Ç¤Ï¤Ê¤¤¤Î¤Ç¤¹¤¬¡¢
-          ZIP ¥É¥é¥¤¥Ö¤ÎÀ­Ç½¤Ï¡¢Àܳ¤µ¤ì¤Æ¤¤¤ë¥Ð¥¹¥¤¥ó¥¿¥Õ¥§¡¼¥¹¤è¤ê¤â
-          ¤à¤·¤í ZIP ¥É¥é¥¤¥Ö¤½¤Î¤â¤Î¤ÎÀ­Ç½¤ËÂ礭¤¯°Í¸¤¹¤ë¤¿¤á¤Ç¤¹)¡£</para>
-
-	<para>IDE ¥¤¥ó¥¿¥Õ¥§¡¼¥¹¤Î·çÅÀ¤Ï¡¢
-          ¤½¤Îµ¬³Ê¤¬Äê¤á¤¿À©¸Â»ö¹à¤½¤Î¤â¤Î¤Ç¤¹¡£
-          ¤Û¤È¤ó¤É¤Î IDE ¥¢¥À¥×¥¿¤Ï 2 ¤Ä¤Î¥Ç¥Ð¥¤¥¹¤·¤«¥µ¥Ý¡¼¥È¤·¤Æ¤ª¤é¤º¡¢
-          ÂçÄñŤ¤´ü´Ö¤ò·Ð¤ÆÀ߷פµ¤ì¤¿¤â¤Î¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£
-          ¤¿¤È¤¨¤Ð¸µÍè¤Î IDE ¥¤¥ó¥¿¥Õ¥§¡¼¥¹¤Ï¡¢
-          ¿¤¯¤Î¿Í¡¹¤Ë¥¢¥Ã¥×¥°¥ì¡¼¥É¤ò¶¯¤¤¤¿
-          1024 ¥·¥ê¥ó¥À°Ê¾å¤Î¥Ï¡¼¥É¥Ç¥£¥¹¥¯¤ò¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤Þ¤»¤ó¡£
-          ¤â¤· ZIP ¥É¥é¥¤¥Ö¤Î¾¤Î¥Ç¥£¥¹¥¯¥É¥é¥¤¥Ö¤ä¥Æ¡¼¥×¥É¥é¥¤¥Ö¡¢
-          ¥¹¥­¥ã¥Ê¡¼¤Ê¤É¤È¤¤¤Ã¤¿ÁõÃÖ¤ò PC ¤ËÄɲ乤뤳¤È¤ò·×²è¤·¤Æ¤¤¤ë¤Ê¤é¡¢
-          ¾­Í赯¤³¤ë¤Ç¤¢¤í¤¦ÌäÂê¤ò²óÈò¤¹¤ë¤¿¤á¤Ë¤â¡¢
-          SCSI ¥Û¥¹¥È¥¢¥À¥×¥¿¤È
-          SCSI ÀܳÍÑ ZIP ¥É¥é¥¤¥Ö¤ËÅê»ñ¤·¤¿Êý¤¬¤è¤¤¤«¤âÃΤì¤Þ¤»¤ó¡£</para>
-
-	<para>FreeBSD¤Ë¤ª¤¤¤Æ¡¢IDE¥Ç¥Ð¥¤¥¹¤ÎÀèƬʸ»ú¤Ï <literal>a</literal> ¤Ç¤¹¡£
-	  ¤¿¤È¤¨¤Ð¡¢IDE¤Î¥Ï¡¼¥É¥Ç¥£¥¹¥¯¥É¥é¥¤¥Ö¤Ï
-	  <filename>/dev/ad0</filename> ¤Ç¡¢IDE (ATAPI) ¤ÎCD-ROM¥É¥é¥¤¥Ö¤Ï
-	  <filename>/dev/acd1</filename> ¤È¤¤¤Ã¤¿¶ñ¹ç¤Ç¤¹¡£</para>
-      </listitem>
-
-      <listitem>
-	<para>¥Ñ¥é¥ì¥ë¥Ý¡¼¥È¥¤¥ó¥¿¥Õ¥§¡¼¥¹¤Ï¡¢
-          ¼ÂºÝ¤Ë¿¤¯¤Î¥³¥ó¥Ô¥å¡¼¥¿¡¼¤¬É¸½à¥Ñ¥é¥ì¥ë¥Ý¡¼¥È¤òÈ÷¤¨¤Æ¤¤¤ë¤¿¤á
-          (ÉáÃʤϥץê¥ó¥¿Àܳ¤Ë»È¤ï¤ì¤Þ¤¹)
-          ZIP ¥É¥é¥¤¥Ö¤ä¥¹¥­¥ã¥Ê¤È¤¤¤Ã¤¿¡¢
-          ¥Ý¡¼¥¿¥Ö¥ë¤Ê³°ÉÕ¤±¥Ç¥Ð¥¤¥¹¤ÎÀܳ¤Ë¤ª¤¤¤Æ¥Ý¥Ô¥å¥é¡¼¤Ê¥¤¥ó¥¿¥Õ¥§¥¤¥¹¤Ç¤¹¡£
-          ¤½¤Î¤¿¤á ZIP ¥É¥é¥¤¥Ö¤ò»ý¤Á±¿¤ó¤Ç¡¢
-          ´Êñ¤Ë¥³¥ó¥Ô¥å¡¼¥¿´Ö¤Î¥Õ¥¡¥¤¥ë¤Î¤ä¤ê¤È¤ê¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£</para>
-
-	<para>°ìÈ̤ˡ¢¥Ñ¥é¥ì¥ë¥Ý¡¼¥ÈÀܳ¤Î ZIP
-          ¥É¥é¥¤¥Ö¤Ï¥Ñ¥é¥ì¥ë¥Ý¡¼¥È¤Î®Å٤ˤè¤Ã¤ÆžÁ÷®ÅÙ¤¬À©¸Â¤µ¤ì¤ë¤¿¤á¡¢
-          SCSI ¤ä IDE ¤ÇÀܳ¤µ¤ì¤¿¾ì¹ç¤è¤êÄ㮤Ǥ¹¡£
-          ¥Ñ¥é¥ì¥ë¥Ý¡¼¥È¤Î®Å٤ϥ³¥ó¥Ô¥å¡¼¥¿¤Ë¤è¤Ã¤ÆÈó¾ï¤Ë¤Þ¤Á¤Þ¤Á¤Ç¡¢
-          ¤Þ¤¿ BIOS ¤«¤éÀßÄꤹ¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹¡£
-          ¤Þ¤¿ÁÐÊý¸þÄÌ¿®¤ò»ÈÍѲÄǽ¤Ë¤¹¤ë¤¿¤á¤Ë
-          BIOS ¤ÎÀßÄ꤬ɬÍפȤʤë¥Þ¥·¥ó¤â¤¢¤ê¤Þ¤¹
-          (¥Ñ¥é¥ì¥ë¥Ý¡¼¥È¤Ï¸µÍè¡¢
-          ¥×¥ê¥ó¥¿¤Ø¤Î½ÐÎϤΤߤòÌÜŪ¤ËÀ߷פµ¤ì¤¿¤â¤Î¤Ç¤¹)¡£</para>
-      </listitem>
-    </orderedlist>
-  </sect1>
-
-  <sect1>
-    <title>¥Ñ¥é¥ì¥ë¥Ý¡¼¥È¤ËÀܳ¤¹¤ë: <devicename>vpo</devicename> ¥É¥é¥¤¥Ð</title>
-
-    <para>ZIP ¥É¥é¥¤¥Ö¤ò¥Ñ¥é¥ì¥ë¥Ý¡¼¥È¤ËÀܳ¤·¤Æ»ÈÍѤ¹¤ë¤Ë¤Ï¡¢
-      ¥«¡¼¥Í¥ë¤Ë
-      <devicename>vpo</devicename> ¥É¥é¥¤¥Ð¤¬ÀßÄꤵ¤ì¤Æ¤¤¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
-      ¥Ñ¥é¥ì¥ë¥Ý¡¼¥ÈÀܳ¤Î ZIP ¥É¥é¥¤¥Ö¤Ï¥Ó¥ë¥È¥¤¥ó¤Î
-      SCSI ¥³¥ó¥È¥í¡¼¥é¤ò»ý¤Ã¤Æ¤ª¤ê¡¢
-      vpo¥É¥é¥¤¥Ð¤ò»ÈÍѤ¹¤ë¤È¥Ñ¥é¥ì¥ë¥Ý¡¼¥È¤òÄ̤¸¤Æ
-      ZIP ¥É¥é¥¤¥Ö¤Î SCSI ¥³¥ó¥È¥í¡¼¥é¤òÆɤ߹þ¤à¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£</para>
-
-    <para>vpo ¤Ïɸ½à¤Î¥«¡¼¥Í¥ë¥ª¥×¥·¥ç¥ó¤Ç¤Ï¤Ê¤¤¤¿¤á
-      (FreeBSD 3.2 ¸½ºß)
-      ¥Ç¥Ð¥¤¥¹¤ò»ÈÍѲÄǽ¤Ë¤¹¤ë¤¿¤á¤Ë¥«¡¼¥Í¥ë¤òºÆ¹½ÃÛ¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
-      ¥«¡¼¥Í¥ëºÆ¹½Ãۤξܺ٤ʼê½ç¤Ë¤Ä¤¤¤Æ¤Ï
-      <ulink url="&url.books.handbook;/kernelconfig.html">&os;
-	¥Ï¥ó¥É¥Ö¥Ã¥¯</ulink>¤ò¤´Í÷¤¯¤À¤µ¤¤¡£
-      °Ê²¼¤Ï¡¢vpo ¥É¥é¥¤¥Ð¤ò»ÈÍѲÄǽ¤Ë¤¹¤ë¤¿¤á¤ÎÂç¤Þ¤«¤Ê¼ê½ç¤Ç¤¹¡£</para>
-
-    <orderedlist>
-      <listitem>
-	<para>¤Þ¤º¡¢<command>/stand/sysinstall</command>
-          ¤ò¼Â¹Ô¤·¡¢¥·¥¹¥Æ¥à¤Ë¥«¡¼¥Í¥ë¤Î¥½¡¼¥¹¥³¡¼¥É¤ò¥¤¥ó¥¹¥È¡¼¥ë¤·¤Æ¤¯¤À¤µ¤¤¡£</para>
-       </listitem>
-
-       <listitem>
-        <para>¼¡¤Ë¡¢
-          vpo ¥É¥é¥¤¥Ð¤ò´Þ¤à¥«¡¼¥Í¥ë¥³¥ó¥Õ¥£¥°¥Õ¥¡¥¤¥ë¤òºî¤ê¤Þ¤¹:</para>
-
-	<screen>&prompt.root; <userinput>cd /sys/i386/conf</userinput>
-&prompt.root; <userinput>cp GENERIC MYKERNEL</userinput></screen>
-
-	<para>¤³¤Î <filename>MYKERNEL</filename>
-          ¤òÊÔ½¸¤·¡¢
-	  <literal>ident</literal> ¤Î¹Ô¤ò <literal>MYKERNEL</literal>
-          ¤ËÊѹ¹¤·¤Þ¤¹¡£
-          ¤½¤·¤Æ vpo ¥É¥é¥¤¥Ð¤Ë¤Ä¤¤¤Æ½ñ¤«¤ì¤¿¹Ô¤Î¥³¥á¥ó¥È¤ò²ò½ü¤·¤Æ¤¯¤À¤µ¤¤¡£</para>
-
-	<para>¤â¤·¥Ñ¥é¥ì¥ë¥Ý¡¼¥È¤¬Æó¤Ä¤¢¤ë¾ì¹ç¡¢¤½¤ì¤ËÍѤ¤¤ë
-          <literal>ppc1</literal> ¥Ç¥Ð¥¤¥¹¥Õ¥¡¥¤¥ë¤òºî¤ë¤¿¤á¤Ë
-          <literal>ppc0</literal> ¤ò¥³¥Ô¡¼¤¹¤ëɬÍפ¬¤¢¤ë¾ì¹ç¤¬¤¢¤ê¤Þ¤¹¡£
-          Æó¤ÄÌܤΥѥé¥ì¥ë¥Ý¡¼¥È¤ÏÉáÄÌ IRQ5 ¤È
-          I/O ¥Ý¡¼¥È¥¢¥É¥ì¥¹ 378 ÈÖ¤ò»ÈÍѤ·¤Þ¤¹¡£
-          ¥«¡¼¥Í¥ë¥³¥ó¥Õ¥£¥°¥Õ¥¡¥¤¥ë¤Ëµ­½Ò¤¹¤ëɬÍפ¬¤¢¤ë¤Î¤Ï IRQ ¤À¤±¤Ç¤¹¡£</para>
-
-	<para>¤â¤·¥ë¡¼¥È¤Î¥Ï¡¼¥É¥Ç¥£¥¹¥¯¥É¥é¥¤¥Ö¤¬
-          SCSI Àܳ¤Ç¤¢¤Ã¤¿¾ì¹ç¡¢µ¯Æ°¥Ç¥£¥¹¥¯¤ÎÆɤ߹þ¤ß½ç½ø¤Ë¸í¤ê¤¬À¸¤¸¡¢
-          ¥·¥¹¥Æ¥à¤¬ ZIP ¥É¥é¥¤¥Ö¤«¤éµ¯Æ°¤·¤è¤¦¤È¤·¤Æ¤·¤Þ¤¦¾ì¹ç¤¬¤¢¤ê¤Þ¤¹¡£
-          ¤³¤¦¤Ê¤Ã¤¿¤é¡¢¤¢¤Ê¤¿¤¬ ZIP ¥Ç¥£¥¹¥¯¤Ë
-          FreeBSD ¤Î¥ë¡¼¥È¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Ç¤â½ñ¤­¹þ¤Þ¤Ê¤¤¸Â¤ê¡¢
-          µ¯Æ°¤Ë¤Ï¼ºÇÔ¤¹¤ë¤Ç¤·¤ç¤¦!
-          ¤½¤¦¤·¤¿¾ì¹ç¤Ï¡¢¥ë¡¼¥È¤Î¥Ç¥£¥¹¥¯¤ò<quote>¡Ö¤Ä¤Ê¤®¤«¤¨ (wire down)¡×</quote>¡¢
-          ¤¹¤Ê¤ï¤Á¡¢¥«¡¼¥Í¥ë¤ËÆÃÄê¤Î¥Ç¥Ð¥¤¥¹¤ò
-          SCSI ¥Ï¡¼¥É¥Ç¥£¥¹¥¯ <filename>/dev/da0</filename>
-          ¤Ë¶¯À©Åª¤Ë¥Ð¥¤¥ó¥É¤µ¤»¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
-          ¤½¤¦¤¹¤ì¤Ð¡¢ZIP ¥Ç¥£¥¹¥¯¥É¥é¥¤¥Ö¤ÏÆóÈÖÌܤÎ
-          SCSI ¥Ç¥Ð¥¤¥¹¡¢¤Ä¤Þ¤ê
-          <literal>/dev/da1</literal> ¤È¤·¤Æ¤­¤Á¤ó¤Èǧ¼±¤µ¤ì¤Þ¤¹¡£
-          SCSI ¥Ï¡¼¥É¥Ç¥£¥¹¥¯¤ò
-          <literal>da0</literal> ¤Ë¡Ö¤Ä¤Ê¤®¤«¤¨¡×¤¹¤ë¤Ë¤Ï¡¢
-
-	  <programlisting>device da0</programlisting>
-
-	  ¤Î¹Ô¤ò
-
-	  <programlisting>disk da0 at scbus0 target 0 unit 0</programlisting>
-
-          ¤ËÊѹ¹¤·¤Æ¤¯¤À¤µ¤¤¡£</para>
-
-	<para>¤½¤ÎºÝ¡¢¥Ï¡¼¥É¥Ç¥£¥¹¥¯¤Î SCSI ID ¤Ë¹ç¤¦¤è¤¦¤Ë
-          ¾åµ­¤Î¹Ô¤òÊѹ¹¤¹¤ëɬÍפ¬¤¢¤ë¤«¤âÃΤì¤Þ¤»¤ó¡£
-          ¤¿¤È¤¨¤Ð¡¢&adaptec; 15xx ¥³¥ó¥È¥í¡¼¥é¤ÎºÜ¤Ã¤¿ SCSI
-          ¥Û¥¹¥È¥¢¥À¥×¥¿¤ò¤ª»ý¤Á¤Ê¤é¡¢²¼¤Î¤è¤¦¤Ë
-          scbus0 ¤ò SCSI ¥³¥ó¥È¥í¡¼¥é¤Ë¤Ä¤Ê¤®¤«¤¨¤Æ¤¯¤À¤µ¤¤¡£
-
-	  <programlisting>controller scbus0</programlisting>
-
-	  ¤ò
-
-	  <programlisting>controller scbus0 at aha0</programlisting>
-
-          ¤ËÊѹ¹¤·¤Þ¤¹¡£</para>
-
-	<para>ºÇ¸å¤Ë¡¢¥«¡¼¥Í¥ë¥³¥ó¥Õ¥£¥°¥Õ¥¡¥¤¥ë¤òºîÀ®¤·¤¿¤é¡¢
-          ÉÔÍפʥɥ饤¥Ð¤ò¤¹¤Ù¤Æºï½ü¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
-          ¤½¤ÎºÝ¤Ë¤ÏºÙ¿´¤ÎÃí°Õ¤òʧ¤¦É¬Íפ¬¤¢¤ê¤Þ¤¹¤¬¡¢
-          ¤¢¤È¤Ï¥³¥ó¥Õ¥£¥°¥Õ¥¡¥¤¥ë¤Î¹¹¿·¤¬À®¸ù¤¹¤ë¤³¤È¤ò¿®ÍѤ¹¤ë¤·¤«¤¢¤ê¤Þ¤»¤ó¡£
-          ÉÔÍפʥɥ饤¥Ð¤òºï½ü¤¹¤ë¤³¤È¤Ç¥«¡¼¥Í¥ë¤Î¥µ¥¤¥º¤ò¾®¤µ¤¯¤¹¤ë¤³¤È¤¬¤Ç¤­¡¢
-          ¥¢¥×¥ê¥±¡¼¥·¥ç¥ó¤Ë³ä¤êÅö¤Æ¤é¤ì¤ë¥á¥â¥ê¤ÎÎΰè¤ò³ÈÂ礹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
-          ÉÔÍפʥɥ饤¥Ð¤òÆÃÄꤹ¤ë¤¿¤á¤Ë¡¢
-          <filename>/var/log/messages</filename>
-          ¤ÎºÇ¸å¤ÎÊý¤Î¹Ô¤Ç¡Önot found¡×¤È½ñ¤«¤ì¤Æ¤¤¤ëÉôʬ¤ò¸«¤Ä¤±¡¢
-          ¤½¤ì¤é¤Î¥Ç¥Ð¥¤¥¹¤ò¥³¥á¥ó¥È¥¢¥¦¥È¤·¤Þ¤¹¡£
-          ¥«¡¼¥Í¥ë¤Î¥µ¥¤¥º¤ò½Ì¾®¤·¡¢
-          Æɤ߹þ¤ß¤òÁ᤯¤¹¤ë¤¿¤á¤Ë¾¤Î¥ª¥×¥·¥ç¥ó¤òºï¤ë¤³¤È¤â¹Í¤¨¤é¤ì¤Þ¤¹¡£
-          ¥«¡¼¥Í¥ëºÆ¹½ÃۤκݤËɽ¼¨¤µ¤ì¤ë¥á¥Ã¥»¡¼¥¸¤«¤é¡¢
-          ÉÔÍפʥª¥×¥·¥ç¥ó¤Ë´Ø¤·¤Æ¤Î¤µ¤é¤Ë¾Ü¤·¤¤¾ðÊó¤¬ÆÀ¤é¤ì¤Þ¤¹¡£</para>
-      </listitem>
-
-      <listitem>
-	<para>¤Ç¤Ï¥«¡¼¥Í¥ë¤ò´°À®¤µ¤»¤Þ¤·¤ç¤¦¡£</para>
-
-	<screen>&prompt.root; <userinput>/usr/sbin/config MYKERNEL</userinput>
-&prompt.root; <userinput>cd ../../compile/MYKERNEL</userinput>
-&prompt.root; <userinput>make clean depend &amp;&amp; make all
-install</userinput></screen>
-      </listitem>
-    </orderedlist>
-
-    <para>¥«¡¼¥Í¥ë¤¬ºÆ¹½ÃÛ¤µ¤ì¤¿¤é¡¢ºÆµ¯Æ°¤·¤Þ¤¹¡£
-      µ¯Æ°¤¬³«»Ï¤¹¤ëÁ°¤Ë¡¢ZIP
-      ¥É¥é¥¤¥Ö¤¬¥Ñ¥é¥ì¥ë¥Ý¡¼¥È¤ËÀܳ¤µ¤ì¤Æ¤¤¤ë¤«¤É¤¦¤«³Îǧ¤·¤Æ¤¯¤À¤µ¤¤¡£
-      ¥Ö¡¼¥È¥á¥Ã¥»¡¼¥¸¤ÎÃæ¤Ç ZIP ¥É¥é¥¤¥Ö¤¬
-      vpo0 ¤ä vpo1
-      (¤³¤ì¤é¤ÏÀܳ¤µ¤ì¤Æ¤¤¤ë¥Ñ¥é¥ì¥ë¥Ý¡¼¥È¤Ë°Í¸¤¹¤ë)
-      ¤È¤·¤Æǧ¼±¤µ¤ì¤Æ¤¤¤ë¤«³Îǧ¤·¤Æ¤¯¤À¤µ¤¤¡£
-      ¤³¤ì¤¬ ZIP ¥É¥é¥¤¥Ö¤Î¥Ç¥Ð¥¤¥¹¥Õ¥¡¥¤¥ë¤Ç¤¹¡£
-      ¤³¤³¤Çɽ¼¨¤µ¤ì¤ë ZIP ¤Î¥Ç¥Ð¥¤¥¹¥Õ¥¡¥¤¥ë¤Ï¡¢
-      ¤â¤·¥·¥¹¥Æ¥à¤Ë¾¤Î SCSI ¥Ç¥£¥¹¥¯¤¬¤Ê¤¤¾ì¹ç¤Ï
-      <filename>/dev/da0</filename> ¤È¤Ê¤ê¡¢
-      SCSI ¥Ï¡¼¥É¥Ç¥£¥¹¥¯¥É¥é¥¤¥Ö¤¬¥ë¡¼¥È¥Ç¥Ð¥¤¥¹¤È¤·¤Æ¤Ä¤Ê¤®¤«¤¨¤é¤ì¤Æ¤¤¤ë¤Ê¤é¤Ð
-      <filename>/dev/da1</filename> ¤È¤Ê¤ê¤Þ¤¹¡£</para>
-  </sect1>
-
-  <sect1>
-    <title>ZIP ¥Ç¥£¥¹¥¯¤ò¥Þ¥¦¥ó¥È¤¹¤ë</title>
-
-    <para>ZIP ¥Ç¥£¥¹¥¯¤Ë¥¢¥¯¥»¥¹¤¹¤ë¤Ë¤Ï¡¢
-      ¾¤Î¼ïÎà¤Î¥Ç¥£¥¹¥¯¤ÈƱ¤¸¤è¤¦¤Ë¥Þ¥¦¥ó¥È¤¹¤ë¤À¤±¤Ç¤¹¡£
-      ¥Ç¥Ð¥¤¥¹¾å¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤¬¥¹¥é¥¤¥¹ 4 ¤È¤Ê¤Ã¤Æ¤¤¤Æ¡¢
-      SCSI ¤â¤·¤¯¤Ï¥Ñ¥é¥ì¥ëÀܳ¤Î ZIP ¥Ç¥£¥¹¥¯¤Ê¤é¡¢</para>
-
-    <screen>&prompt.root; <userinput>mount_msdos /dev/da1s4 /mnt</userinput></screen>
-
-    <para>IDE Àܳ¤Î ZIP ¥É¥é¥¤¥Ö¤Ê¤é¡¢</para>
-
-    <screen>&prompt.root; <userinput>mount_msdos /dev/ad1s4 /mnt</userinput></screen>
-
-    <para><filename>/etc/fstab</filename> ¤ò¹¹¿·¤¹¤ì¤Ð¡¢
-      ¥Þ¥¦¥ó¥È¤Ï¤µ¤é¤Ë´Êñ¤Ë¤Ê¤ê¤Þ¤¹¡£
-      ¼«Ê¬¤Î¥·¥¹¥Æ¥à¤Ë¹ç¤¦¤è¤¦¤ËÊÔ½¸¤·¤Æ¡¢°Ê²¼¤Î¤è¤¦¤Ê¹Ô¤ò²Ã¤¨¤Þ¤·¤ç¤¦¡£</para>
-
-    <programlisting>/dev/da1s4  /zip msdos rw,noauto  0 0</programlisting>
-
-    <para>¤½¤·¤Æ¥Ç¥£¥ì¥¯¥È¥ê <filename>/zip</filename> ¤òºîÀ®¤·¤Þ¤¹¡£</para>
-
-    <para>¥Þ¥¦¥ó¥È¤¹¤ë¤Ë¤Ï¡¢</para>
-
-    <screen>&prompt.root; <userinput>mount /zip</userinput></screen>
-
-    <para>¥Þ¥¦¥ó¥È¤ò²ò½ü¤¹¤ë¤Ë¤Ï¡¢</para>
-
-    <screen>&prompt.root; <userinput>umount /zip</userinput></screen>
-
-    <para><filename>/etc/fstab</filename>
-      ¤Î¥Õ¥©¡¼¥Þ¥Ã¥È¤Ë´Ø¤¹¤ë¾ÜºÙ¤Ï¡¢&man.fstab.5; ¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£</para>
-
-    <para>¤Þ¤¿¡¢ZIP ¥Ç¥£¥¹¥¯¾å¤Ë FreeBSD
-      ¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤òºîÀ®¤¹¤ë¤Ë¤Ï &man.newfs.8; ¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£
-      ¤¿¤À¤·¡¢¤³¤Î¥Ç¥£¥¹¥¯¤Ï FreeBSD ¤«¡¢FreeBSD
-      ¤òǧ¼±¤¹¤ë¤´¤¯¾¯¿ô¤Î &unix; ¥¯¥í¡¼¥ó¤Î¤ß¤Ë¤ª¤¤¤Æ»ÈÍѤ¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹
-      (&ms-dos; ¤ä &windows; ¾å¤Ç¤Ï»ÈÍѤǤ­¤Þ¤»¤ó)¡£</para>
-  </sect1>
-</article>
diff --git a/ja_JP.eucJP/books/faq/book.sgml b/ja_JP.eucJP/books/faq/book.sgml
index 9236dc090d..d51b31cb6d 100644
--- a/ja_JP.eucJP/books/faq/book.sgml
+++ b/ja_JP.eucJP/books/faq/book.sgml
@@ -1535,19 +1535,6 @@ File: +DESC (ignored)</screen>
       </qandaentry>
 
       <qandaentry>
-        <question id="multiboot">
-          <para>¼«Ê¬¤Î PC ¤ËÊ£¿ô¤Î¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤òÆþ¤ì¤ë¤Ë¤Ï?</para>
-        </question>
-
-        <answer>
-          <para>
-            <ulink url="http://www.FreeBSD.org/tutorials/multi-os/">multi-OS
-              ¤Î¥Ú¡¼¥¸</ulink>¤ò¤´Í÷¤¯¤À¤µ¤¤¡£
-          </para>
-        </answer>
-      </qandaentry>
-
-      <qandaentry>
         <question id="windows-coexist">
           <para>Ʊ¤¸¥Þ¥·¥ó¤Ç Windows 95/98 ¤È¶¦Â¸¤Ç¤­¤Þ¤¹¤«?</para>
         </question>
@@ -6317,17 +6304,6 @@ device sio5 at isa? port 0x2b8 tty flags 0x501 vector siointr</programlisting>
       </qandaentry>
 
       <qandaentry>
-        <question id="adding-disks">
-          <para>FreeBSD ¥·¥¹¥Æ¥à¤Ë¿·¤·¤¤¥Ï¡¼¥É¥Ç¥£¥¹¥¯¤òÄɲ乤ë¤Ë¤Ï?</para>
-        </question>
-
-        <answer>
-          <para><ulink url="../../tutorials/formatting-media/">www.FreeBSD.org</ulink>
-            ¤Ë½ñ¤«¤ì¤Æ¤¤¤ë¥Ç¥£¥¹¥¯¥Õ¥©¡¼¥Þ¥Ã¥È¥Á¥å¡¼¥È¥ê¥¢¥ë¤ò»²¾È¤·¤Æ¤¯¤À¤µ¤¤¡£</para>
-        </answer>
-      </qandaentry>
-
-      <qandaentry>
         <question id="removable-drives">
           <para>¿·¤·¤¤¥ê¥à¡¼¥Ð¥Ö¥ë¥É¥é¥¤¥Ö¤ò»ý¤Ã¤Æ¤¤¤Þ¤¹¤¬¡¢¤É¤¦¤ä¤Ã¤Æ»È¤¦¤Î?</para>
         </question>
diff --git a/ja_JP.eucJP/htdocs/docproj/translations.sgml b/ja_JP.eucJP/htdocs/docproj/translations.sgml
index ce4a6fa9bb..a4e75a62a7 100644
--- a/ja_JP.eucJP/htdocs/docproj/translations.sgml
+++ b/ja_JP.eucJP/htdocs/docproj/translations.sgml
@@ -96,8 +96,6 @@
   <dd><a href="http://www.cybershade.us/freebsd/bg/fdp/split/">¿·¤·¤¤
     ¹×¸¥¼Ô¤Î¤¿¤á¤Î FreeBSD ¥É¥­¥å¥á¥ó¥Æ¡¼¥·¥ç¥ó¥×¥í¥¸¥§¥¯¥ÈÆþÌç</a></dd>
 
-  <dd><a href="http://www.cybershade.us/freebsd/bg/multi-os/">FreeBSD ¤È¾¤Î OS ¤ò¶¦Â¸¤µ¤»¤ëÊýË¡</a></dd>
-
   <dt><i>¸½ºßºî¶È¤·¤Æ¤¤¤ë¥É¥­¥å¥á¥ó¥È</i></dt>
 
   <dd>FreeBSD ¥Ï¥ó¥É¥Ö¥Ã¥¯</dd>
diff --git a/ja_JP.eucJP/htdocs/docs/books.sgml b/ja_JP.eucJP/htdocs/docs/books.sgml
index 8af56697b2..3adbd8f821 100644
--- a/ja_JP.eucJP/htdocs/docs/books.sgml
+++ b/ja_JP.eucJP/htdocs/docs/books.sgml
@@ -100,12 +100,6 @@
 
 	<!-- Articles are sorted by pathname -->
 
-	    <p><a href="&url.en.articles;/5-roadmap/index.html">The
-	        Roadmap for 5-STABLE</a> (5-roadmap) (±Ñ¸ìÈǤΤß)<br/>
-	      5-STABLE ¥Ö¥é¥ó¥ÁºîÀ®¤Þ¤Ç¤Î
-	      Ãæ´üŪ¤Ê³«È¯¤È¥ê¥ê¡¼¥¹¥¨¥ó¥¸¥Ë¥¢¥ê¥ó¥°¤Î·×²è¤Ç¤¹¡£
-	      ¼ç¤ËÎò»ËŪ¤Ë¶½Ì£¿¼¤¤Ê¸½ñ¤Ç¤¹¡£</p>
-
             <p><a href="&url.en.articles;/bsdl-gpl/index.html">Why you should use
 		a BSD style license for your Open Source Project</a>
 	        (bsdl-gpl) (±Ñ¸ìÈǤΤß)<br/>
@@ -120,12 +114,6 @@
 	      FreeBSD ¤¬¤É¤Î¤è¤¦¤Ë¥é¥Æ¥ó¥¢¥á¥ê¥«¤ÎÂ絬ÌÏ ISP
 	      ¤ÎÌò¤ËΩ¤Ã¤¿¤«¡£</p>
 
-	    <p><a href="&url.en.articles;/checkpoint/index.html">Integration
-	        of Checkpoint VPN-1/Firewall-1 and FreeBSD IPsec</a>
-	        (checkpoint) (±Ñ¸ìÈǤΤß)<br/>
-	      Checkpoint VPN-1/Firewall-1 ¤È FreeBSD IPsec
-	      ¤òÀßÄꤹ¤ëÊýË¡¤Ç¤¹¡£</p>
-
 	    <p><a href="&url.en.articles;/committers-guide/index.html">The
 	        Committer's Guide</a> (committers-guide) (±Ñ¸ìÈǤΤß)<br/>
 	      FreeBSD committers ¤Î¤¿¤á¤ÎÆþÌç½ñ¤Ç¤¹¡£</p>
@@ -175,21 +163,6 @@
 	        Advanced Points</a> (cvsup-advanced) (±Ñ¸ìÈǤΤß)<br/>
 	      CVSup ¤ÎÍ­ÍѤµ¤ò°ú¤­½Ð¤¹¥Æ¥¯¥Ë¥Ã¥¯¤ò¾Ò²ð¤·¤¿µ­»ö¤Ç¤¹¡£</p>
 
-	    <p><a href="&url.ja.articles;/dialup-firewall/index.html">FreeBSD
-		¤Ë¤è¤ë¥À¥¤¥¢¥ë¥¢¥Ã¥×¼°¥Õ¥¡¥¤¥¢¥¦¥©¡¼¥ë¤Î¹½ÃÛ</a>
-		(dialup-firewall)<br/>
-	      ¥À¥¤¥ä¥ë¥¢¥Ã¥×¤ÇưŪ¤Ë³ä¤êÅö¤Æ¤é¤ì¤¿ IP ¥¢¥É¥ì¥¹¤Ç PPP ¤È ipfw
-	      ¤ò»È¤Ã¤Æ¥Õ¥¡¥¤¥ä¥¦¥©¡¼¥ë¤òÀßÄꤹ¤ëÊýË¡¤Ç¤¹¡£</p>
-
-	    <p><a href="&url.ja.articles;/diskless-x/index.html">
-	        ¥Ç¥£¥¹¥¯¥ì¥¹ X ¥µ¡¼¥Ð¤Îºî¤êÊý</a> (diskless-x)<br/>
-	      ¥Ç¥£¥¹¥¯Ìµ¤·¤Î X ¥µ¡¼¥Ð¤ò¹½ÃÛ¤¹¤ëÊýË¡¤Ç¤¹¡£</p>
-
-	    <p><a href="&url.en.articles;/euro/index.html">The Euro symbol
-	        on FreeBSD</a> (euro) (±Ñ¸ìÈǤΤß)<br/>
-	      ¿·¤·¤¤¥æ¡¼¥íµ­¹æ¤òɽ¼¨¤¹¤ë¤è¤¦¤Ë FreeBSD
-	      ¤È´ØÏ¢¤¹¤ë¥¢¥×¥ê¥±¡¼¥·¥ç¥ó¤òÀßÄꤹ¤ëÊýË¡¤Ç¤¹¡£</p>
-
 	    <p><a href="&url.en.articles;/explaining-bsd/index.html">Explaining
 		BSD</a> (explaining-bsd) (±Ñ¸ìÈǤΤß)<br/>
 	      ``BSD ¤È¤Ï¤Ê¤Ë¤«?'' ¤È¤¤¤¦¼ÁÌä¤ËÂФ¹¤ëÅú¤¨¤Ç¤¹¡£</p>
@@ -210,11 +183,6 @@
 	      FreeBSD ¤Ë¤ª¤±¤ë¤µ¤Þ¤¶¤Þ¤Ê¥Õ¥©¥ó¥Èµ»½Ñ¤ÎÀâÌÀ¤È¡¢
 	      ¥×¥í¥°¥é¥à¤«¤é¤½¤ì¤ò»È¤¦ÊýË¡¤ò²òÀ⤷¤Æ¤¤¤Þ¤¹¡£</p>
 
-	    <p><a href="&url.en.articles;/formatting-media/index.html">Formatting
-	        media on FreeBSD</a> (formatting-media) (±Ñ¸ìÈǤΤß)<br/>
-	      FreeBSD ¤Ç¸ÇÄê¥Ç¥£¥¹¥¯¤ä¥ê¥à¡¼¥Ð¥Ö¥ë¥Ç¥£¥¹¥¯¤ò slice, partition
-	      ¤Ëʬ³ä¤·¡¢¥Õ¥©¡¼¥Þ¥Ã¥È¤¹¤ë¤¿¤á¤Î²òÀâ¤Ç¤¹¡£</p>
-
 	    <p><a href="&url.en.articles;/freebsd-questions/index.html">How
 	        to get the best results from the FreeBSD-questions mailing list</a>
 	        (freebsd-questions) (±Ñ¸ìÈǤΤß)<br/>
@@ -238,12 +206,6 @@
 	      ¥Ç¥¹¥¯¥È¥Ã¥×ÍÑÅӤΠPC ¤Ë¡¢¥¸¥ã¡¼¥Ê¥ê¥ó¥°µ¡Ç½¤òÄɲä·¤¿
 	      UFS ¥Ñ¡¼¥Æ¥£¥·¥ç¥ó¤òºîÀ®¤¹¤ëÊýË¡¤Ë¤Ä¤¤¤Æ¤Î¥¬¥¤¥É¤Ç¤¹¡£</p>
 
-	    <p><a href="&url.en.articles;/hats/index.html">Working with Hats</a>
-	        (hats) (±Ñ¸ìÈǤΤß)<br/>
-	      ``˹»Ò'' ¤ò¤«¤Ö¤Ã¤Æ¤¤¤ë¿Í
-	      (FreeBSD ¤ÎÆÃÄêʬÌî¤Ë¸¢°Ò¤ò»ý¤Ã¤Æ¤¤¤ë committer)
-	      ¤È¤È¤â¤Ëºî¶È¤¹¤ë¤¿¤á¤Î committer ¸þ¤±¤ÎÆþÌç½ñ¡£</p>
-
 	    <p><a href="&url.en.articles;/hubs/index.html">Mirroring FreeBSD</a>
 	        (hubs) (±Ñ¸ìÈǤΤß)<br/>
 	      FreeBSD ¤Î¥¦¥§¥Ö¥µ¥¤¥È¡¢CVSup ¥µ¡¼¥Ð¡¢FTP
@@ -285,12 +247,6 @@
 	        (mh) (±Ñ¸ìÈǤΤß)<br/>
 	      FreeBSD ¤Ç MH ¥á¡¼¥ë¥ê¡¼¥À¤ò»È¤¦¤¿¤á¤ÎÆþÌç½ñ¤Ç¤¹¡£</p>
 
-	    <p><a href="&url.ja.articles;/multi-os/index.html">FreeBSD
-	        ¤ò¾¤Î¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤È¶¦Â¸¤µ¤»¤ëÊýË¡</a>
-		(multi-os)<br/>
-	      °ì¤Ä¤Î¥³¥ó¥Ô¥å¡¼¥¿¤Ë FreeBSD ¤È¡¢
-	      Ê̤Υª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤ò¥¤¥ó¥¹¥È¡¼¥ë¤¹¤ë¤¿¤á¤ÎÊýË¡¤Ç¤¹¡£</p>
-
 	    <p><a href="&url.en.articles;/nanobsd/index.html">Introduction
                 to NanoBSD</a> (nanobsd) (±Ñ¸ìÈǤΤß)<br/>
 	      NanoBSD ¤ÎÆþÌç½ñ¤Ç¤¹¡£NanoBSD ¤Ï
@@ -380,35 +336,10 @@
 	        and Solid State Devices</a> (solid-state) (±Ñ¸ìÈǤΤß)<br/>
 	      FreeBSD ¤Ë¤ª¤±¤ëȾƳÂΥǥ£¥¹¥¯¤ÎÍøÍѤˤĤ¤¤Æ¤Îµ­»ö¤Ç¤¹¡£</p>
 
-	    <p><a href="&url.en.articles;/storage-devices/index.html">
-		Storage Devices</a> (storage-devices) (±Ñ¸ìÈǤΤß)<br/>
-	      ESDI ¥Ç¥£¥¹¥¯¡¢SCSI ¥Ç¥£¥¹¥¯¡¢¥Æ¡¼¥×¥É¥é¥¤¥Ö¡¢CDROM
-	      ¥É¥é¥¤¥Ö¤Ê¤É¤Î¥¹¥È¥ì¡¼¥¸¥Ç¥Ð¥¤¥¹¤ò
-	      FreeBSD ¤Ç»È¤¦ºÝ¤Î¾ÜºÙ¤Ê¾ðÊó¤Ç¤¹¡£</p>
-
-	    <p><a href="&url.en.articles;/version-guide/index.html">Choosing
-		the FreeBSD Version That Is Right For You</a>
-		(version-guide) (±Ñ¸ìÈǤΤß)<br/>
-	      ¤¢¤Ê¤¿¤ÎÍ×µá¤ËÂФ·¤Æ¡¢¤É¤Î¥Ð¡¼¥¸¥ç¥ó¤Î FreeBSD
-	      ¤¬Å¬ÀÚ¤«È½ÃǤ¹¤ëÊýË¡¤Ë¤Ä¤¤¤Æ½Ò¤Ù¤¿µ­»ö¤Ç¤¹¡£
-	      ¥ê¥ê¡¼¥¹¡¢¥Ö¥é¥ó¥Á¡¢-CURRENT ¤È -STABLE ¤Î°ã¤¤¤ä¡¢
-	      ¸½»þÅÀ¤Î¥×¥í¥¸¥§¥¯¥È¤ÎͽÄê¤ò°·¤Ã¤Æ¤¤¤Þ¤¹¡£</p>
-
-	    <p><a href="&url.ja.articles;/vinum/index.html">Bootstrapping
-	       Vinum: (¿®ÍêÀ­¤Î¹â¤¤¥µ¡¼¥Ð¤Î´ðÁÃ)</a> (vinum)<br/>
-	       ¸Î¾ã²óÉüÀ­¤Î¹â¤¤¥µ¡¼¥Ð¤È¤Ï¤É¤¦¤¤¤¦¤â¤Î¤«¤òÃúÇ«¤Ë¾Ò²ð¤·¡¢
-	       Vinum ¤ò»È¤Ã¤¿¹½ÃÛ¤ò¼ê½ç¤òÄɤäƲòÀ⤷¤¿µ­»ö¤Ç¤¹¡£</p>
-
 	    <p><a href="&url.en.articles;/vm-design/index.html">Design
 	      elements of the FreeBSD VM system</a> (vm-design) (±Ñ¸ìÈǤΤß)<br/>
 	      FreeBSD ¤Î²¾ÁÛ¥á¥â¥ê¥·¥¹¥Æ¥à¤ÎÀ߷פˤĤ¤¤Æ¤Î¤ï¤«¤ê¤ä¤¹¤¤²òÀâ¤Ç¤¹¡£</p>
 
-	    <p><a href="&url.ja.articles;/zip-drive/index.html">Zip
-		¥É¥é¥¤¥Ö¤È FreeBSD</a> (zip-drive)<br/>
-	      Iomega Zip (SCSI, IDE¡¢¥Ñ¥é¥ì¥ë) ¥É¥é¥¤¥Ö¤ò FreeBSD
-	      ¤Ç¥Õ¥©¡¼¥Þ¥Ã¥È¡¢¥Þ¥¦¥ó¥È¤·¤Æ»È¤¦ÊýË¡¤Ç¤¹¡£</p>
-
-
     <h2>¾¤Î¥¦¥§¥Ö¥µ¥¤¥È</h2>
 
     <p>FreeBSD ¤Ë¤Ä¤¤¤Æ¤ÎÇüÂç¤ÊÎ̤ξðÊ󤬡¢
diff --git a/ja_JP.eucJP/htdocs/news/2001/news.xml b/ja_JP.eucJP/htdocs/news/2001/news.xml
index 4c24c1e1f3..a0cfc09efd 100644
--- a/ja_JP.eucJP/htdocs/news/2001/news.xml
+++ b/ja_JP.eucJP/htdocs/news/2001/news.xml
@@ -299,7 +299,7 @@
 	<event>
 	  <title>Vinum ¤ÎÀßÄê: ¿®ÍêÀ­¤Î¹â¤¤¥µ¡¼¥Ð¹½ÃۤδðÁÃ</title>
 	  <p><a href="mailto:Bob@BGPBook.Com">Bob Van Valzah</a> »á¤Ë¤è¤ê¡¢
-            <a href="&base;/../doc/en_US.ISO8859-1/articles/vinum/index.html">
+            <a href="http://docs.freebsd.org/doc/9.0-RELEASE/usr/share/doc/freebsd/en_US.ISO8859-1/articles/vinum/index.html">
               ¾ã³²¤ËÂѤ¨¤ë¥µ¡¼¥Ð¤È¤Ï¤É¤¦¤¤¤¦¤â¤Î¤«¡¢
               ¤½¤·¤Æ Vinum
               ¤ò»È¤Ã¤Æ¤½¤Î¤è¤¦¤Ê¥µ¡¼¥Ð¤ò¹½ÃÛ¤¹¤ë¼ê½ç¤Ë¤Ä¤¤¤Æ</a>¾Ò²ð¤¹¤ëµ­»ö¤¬
diff --git a/ja_JP.eucJP/htdocs/releases/5.1R/early-adopter.html b/ja_JP.eucJP/htdocs/releases/5.1R/early-adopter.html
index b4a1af9d0c..be78be516e 100644
--- a/ja_JP.eucJP/htdocs/releases/5.1R/early-adopter.html
+++ b/ja_JP.eucJP/htdocs/releases/5.1R/early-adopter.html
@@ -168,7 +168,7 @@
          target="_top">``FreeBSD ¥ê¥ê¡¼¥¹¥¨¥ó¥¸¥Ë¥¢¥ê¥ó¥°''</a>
         ¤È¤¤¤¦µ­»ö¤ò¤´Í÷¤¯¤À¤µ¤¤¡£ ¤­¤¿¤ë 5-STABLE
         ³«È¯¥Ö¥é¥ó¥Á¤Ë¤Ä¤¤¤Æ¤ÎÆõ­»ö¹à¤Ï <a
-        href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/5-roadmap/index.html"
+        href="http://docs.freebsd.org/doc/5.1-RELEASE/usr/share/doc/en_US.ISO8859-1/articles/5-roadmap/index.html"
          target="_top">``5-STABLE ³«È¯¥Ö¥é¥ó¥Á¤Î¥í¡¼¥É¥Þ¥Ã¥×''</a>
         ¤È¤¤¤¦µ­»ö¤ò¤´Í÷¤¯¤À¤µ¤¤¡£</p>
       </div>
diff --git a/ja_JP.eucJP/htdocs/releases/5.2.1R/early-adopter.html b/ja_JP.eucJP/htdocs/releases/5.2.1R/early-adopter.html
index df6c7fa790..54be9d310d 100644
--- a/ja_JP.eucJP/htdocs/releases/5.2.1R/early-adopter.html
+++ b/ja_JP.eucJP/htdocs/releases/5.2.1R/early-adopter.html
@@ -148,7 +148,7 @@ target="_top">¥ê¥ê¡¼¥¹¥¨¥ó¥¸¥Ë¥¢¥ê¥ó¥°¤Î¥¦¥§¥Ö¥Ú¡¼¥¸</a> ¤ª¤è¤Ó¡¢<a
 href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/releng/index.html"
 target="_top">``FreeBSD ¥ê¥ê¡¼¥¹¥¨¥ó¥¸¥Ë¥¢¥ê¥ó¥°''</a> ¤È¤¤¤¦µ­»ö¤ò¤´Í÷¤¯¤À¤µ¤¤¡£ ¤­¤¿¤ë
 5-STABLE ³«È¯¥Ö¥é¥ó¥Á¤Ë¤Ä¤¤¤Æ¤ÎÆõ­»ö¹à¤Ï <a
-href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/5-roadmap/index.html"
+href="http://docs.freebsd.org/doc/5.2.1-RELEASE/usr/share/doc/en_US.ISO8859-1/articles/5-roadmap/index.html"
 target="_top">``5-STABLE ³«È¯¥Ö¥é¥ó¥Á¤Î¥í¡¼¥É¥Þ¥Ã¥×''</a> ¤È¤¤¤¦µ­»ö¤ò¤´Í÷¤¯¤À¤µ¤¤¡£</p>
 </div>
 
diff --git a/ja_JP.eucJP/htdocs/releases/5.2R/early-adopter.html b/ja_JP.eucJP/htdocs/releases/5.2R/early-adopter.html
index a95cb9878d..54e74bb430 100644
--- a/ja_JP.eucJP/htdocs/releases/5.2R/early-adopter.html
+++ b/ja_JP.eucJP/htdocs/releases/5.2R/early-adopter.html
@@ -148,7 +148,7 @@ target="_top">¥ê¥ê¡¼¥¹¥¨¥ó¥¸¥Ë¥¢¥ê¥ó¥°¤Î¥¦¥§¥Ö¥Ú¡¼¥¸</a> ¤ª¤è¤Ó¡¢<a
 href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/releng/index.html"
 target="_top">``FreeBSD ¥ê¥ê¡¼¥¹¥¨¥ó¥¸¥Ë¥¢¥ê¥ó¥°''</a> ¤È¤¤¤¦µ­»ö¤ò¤´Í÷¤¯¤À¤µ¤¤¡£ ¤­¤¿¤ë
 5-STABLE ³«È¯¥Ö¥é¥ó¥Á¤Ë¤Ä¤¤¤Æ¤ÎÆõ­»ö¹à¤Ï <a
-href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/5-roadmap/index.html"
+href="http://docs.freebsd.org/doc/5.2-RELEASE/usr/share/doc/en_US.ISO8859-1/articles/5-roadmap/index.html"
 target="_top">``5-STABLE ³«È¯¥Ö¥é¥ó¥Á¤Î¥í¡¼¥É¥Þ¥Ã¥×''</a> ¤È¤¤¤¦µ­»ö¤ò¤´Í÷¤¯¤À¤µ¤¤¡£</p>
 </div>
 
diff --git a/ja_JP.eucJP/share/sgml/news.xml b/ja_JP.eucJP/share/sgml/news.xml
index 9ed08378a6..f872316ec6 100644
--- a/ja_JP.eucJP/share/sgml/news.xml
+++ b/ja_JP.eucJP/share/sgml/news.xml
@@ -1832,7 +1832,7 @@
 	  <title>¿·¥Á¥å¡¼¥È¥ê¥¢¥ë: "FreeBSD ¤Ç¥æ¡¼¥íµ­¹æ"</title>
 
 	  <p>Aaron Kaplan ¤Ï FreeBSD ¤Ç¿·¤·¤¤
-	    <a href="&base;/../doc/en_US.ISO8859-1/articles/euro/article.html">
+	    <a href="http://docs.freebsd.org/doc/9.0-RELEASE/usr/share/doc/freebsd/en_US.ISO8859-1/articles/euro/index.html">
 	      ¥æ¡¼¥íµ­¹æ¤ò»È¤¦</a> ÍѤ˥·¥¹¥Æ¥à¤òÀßÄꤹ¤ëÊýË¡¤ò
 	    µ­½Ò¤·¤¿µ­»ö¤ò´ó¹Æ¤·¤Æ¤¯¤ì¤Þ¤·¤¿¡£</p>
 	</event>
diff --git a/pl_PL.ISO8859-2/articles/Makefile b/pl_PL.ISO8859-2/articles/Makefile
index 062991f2e2..0f295c4dd2 100644
--- a/pl_PL.ISO8859-2/articles/Makefile
+++ b/pl_PL.ISO8859-2/articles/Makefile
@@ -1,7 +1,6 @@
 # $FreeBSD$
 
 SUBDIR =
-SUBDIR+= dialup-firewall
 SUBDIR+= filtering-bridges
 SUBDIR+= new-users
 
diff --git a/pl_PL.ISO8859-2/articles/dialup-firewall/Makefile b/pl_PL.ISO8859-2/articles/dialup-firewall/Makefile
deleted file mode 100644
index 886e21cc9d..0000000000
--- a/pl_PL.ISO8859-2/articles/dialup-firewall/Makefile
+++ /dev/null
@@ -1,14 +0,0 @@
-# $FreeBSD$
-
-DOC?= article
-
-FORMATS?= html
-
-INSTALL_COMPRESSED?=gz
-INSTALL_ONLY_COMPRESSED?=
-
-SRCS= article.sgml
-
-DOC_PREFIX?= ${.CURDIR}/../../..
-
-.include "${DOC_PREFIX}/share/mk/doc.project.mk"
diff --git a/pl_PL.ISO8859-2/articles/dialup-firewall/article.sgml b/pl_PL.ISO8859-2/articles/dialup-firewall/article.sgml
deleted file mode 100644
index f1c6e0cb56..0000000000
--- a/pl_PL.ISO8859-2/articles/dialup-firewall/article.sgml
+++ /dev/null
@@ -1,401 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-2" standalone="no"?>
-<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V4.2-Based Extension//EN"
-	"../../../share/sgml/freebsd42.dtd" [
-<!ENTITY % entities PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Entity Set//PL" "../../share/sgml/entities.ent">
-%entities;
-]>
-
-<!--
-     The FreeBSD Polish Documentation Project
-
-     $FreeBSD$
-     Original revision: 1.25
--->
-
-<article lang="pl">
-  <articleinfo>
-    <title>Firewall na po³±czeniu modemowym w FreeBSD</title>
-
-    <authorgroup>
-      <author>
-	<firstname>Marc</firstname>
-	<surname>Silver</surname>
-	<affiliation>
-	  <address><email>marcs@draenor.org</email></address>
-	</affiliation>
-      </author>
-    </authorgroup>
-
-    <pubdate>$FreeBSD$</pubdate>
-
-    <releaseinfo>$FreeBSD$</releaseinfo>
-
-    <abstract>
-      <para>W niniejszym artykule przedstawiono instrukcjê konfiguracji
-        firewalla przy dynamicznie przydzielanym adresie IP, a tak¿e
-	przepis na uruchomienie takiego firewalla w FreeBSD, korzystaj±c
-	z IPFW.
-	Artyku³ nie zawiera instrukcji konfigurowania po³±czenia
-	PPP.</para>
-    </abstract>
-  </articleinfo>
-
-  <sect1 id="preface">
-    <title>Wstêp</title>
-
-    <para>Firewall na po³±czeniu modemowym w FreeBSD</para>
-
-     <para>Niniejszy artyku³ opisuje konfiguracjê firewalla w FreeBSD
-       w przypadku, gdy adres IP przydzielany jest dynamicznie przez
-       dostawcê us³ug internetowych. Do³o¿ono wszelkich starañ, aby
-       artyku³ zawiera³ przydatne informacje i by³ wolny od b³êdów,
-       jednak¿e wszelkie uwagi i sugestie s± mile widziane, proszê
-       kierowaæ je do <email>marcs@draenor.org</email>.</para>
-   </sect1>
-
-   <sect1 id="kernel">
-    <title>Opcjê j±dra</title>
-
-    <para>Na pocz±tek bêdziemy musieli przekompilowaæ j±dro. Wiecej
-      informacji na temat kompilowania j±dra znale¼æ mo¿na w <ulink
-      url="../../books/handbook/kernelconfig.html">czê¶ci Podrêcznika
-      po¶wiêconej konfiguracji j±dra</ulink>. Do pliku konfiguracyjnego
-      j±dra dopisujemy nastêpuj±ce opcje:</para>
-
-    <variablelist>
-      <varlistentry>
-	<term><literal>options IPFIREWALL</literal></term>
-
-	<listitem>
-	  <para>W³aczenie obs³ugi firewalla w j±drze.</para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-	<term><literal>options IPFIREWALL_VERBOSE</literal></term>
-
-	<listitem>
-	  <para>Wysy³anie informacji o pakietach do logów systemowych.</para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-	<term><literal>options
-	    IPFIREWALL_VERBOSE_LIMIT=<replaceable>100</replaceable></literal></term>
-
-	<listitem>
-	  <para>Ograniczenie liczby pakietów zapisywanych w logach;
-	    dziêki temu plik loga nie zostanie zapchany wieloma
-	    powtarzaj±cymi siê wpisami. Warto¶æ
-	    <replaceable>100</replaceable> jest sensowna, mo¿na jednak
-	    wstawiæ inn±, odpowiedni± dla w³asnych potrzeb.</para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-	<term><literal>options IPDIVERT</literal></term>
-
-	<listitem>
-	  <para>W³±czenie gniazd divert.</para>
-	</listitem>
-      </varlistentry>
-    </variablelist>
-
-    <para>Mo¿na dopisaæ jeszcze kilka wierszy
-      <emphasis>opcjonalnych</emphasis>, które zwiêkszaj± poziom
-      bezpieczeñstwa. Firewall pracuje poprawnie równie¿ bez nich,
-      jednak¿e bardziej ostro¿ni u¿ytkownicy mog± zechcieæ z nich
-      skorzystaæ.</para>
-
-    <variablelist>
-      <varlistentry>
-	<term><literal>options TCP_DROP_SYNFIN</literal></term>
-
-	<listitem>
-	  <para>Ignorowanie pakietów TCP z ustawionymi flagami
-	    SYN i FIN. Zapobiega to mo¿liwo¶ci identyfikacji stosu TCP/IP
-	    przy pomocy narzêdzi takich jak nmap, jest to jednak wbrew
-	    ustaleniom dokumentu RFC1644. Nie powinno byæ stosowane,
-	    je¶li na maszynie ma dzia³aæ serwer WWW.</para>
-	</listitem>
-      </varlistentry>
-     </variablelist>
-
-    <para>Po kompilacji j±dra nie trzeba od razu prze³adowywaæ systemu.
-      Je¶li wszystko pójdzie zgodnie z planem, wystarczy jedno
-      prze³adowanie po ukoñczeniu konfiguracji firewalla.</para>
-  </sect1>
-
-  <sect1 id="rcconf">
-    <title>Uruchamianie firewalla w
-      <filename>/etc/rc.conf</filename></title>
-
-    <para>Trzeba teraz wprowadziæ pewne zmiany w
-      <filename>/etc/rc.conf</filename>, by uwzglêdnia³ on firewalla.
-      Dodajemy nastêpuj±ce linijki:</para>
-
-    <programlisting>firewall_enable="YES"
-firewall_script="/etc/firewall/fwrules"
-natd_enable="YES"
-natd_interface="tun0"
-natd_flags="-dynamic"</programlisting>
-
-    <para>Informacje na temat dzia³ania powy¿szych poleceñ mo¿na
-      znale¼æ w <filename>/etc/defaults/rc.conf</filename> oraz
-      &man.rc.conf.5;.</para>
-  </sect1>
-
-  <sect1>
-    <title>Wy³±czenie t³umaczenia adresów przez PPP</title>
-
-    <para>Je¿eli wykorzystywane jest t³umaczenie adresów
-      sieciowych
-      wbudowane w PPP, trzeba bêdzie je wy³±czyæ. W naszych przyk³adach
-      t³umaczeniem zajmuje siê &man.natd.8;.</para>
-
-    <para>Fragment pliku odpowiedzialny za automatyczne uruchomienie
-      PPP wygl±da zapewne tak:</para>
-
-    <programlisting>ppp_enable="YES"
-ppp_mode="auto"
-ppp_nat="YES"
-ppp_profile="<replaceable>profile</replaceable>"</programlisting>
-
-    <para>Je¶li tak w³a¶nie jest, trzeba bêdzie wy³±czyæ
-      <literal>ppp_nat</literal> wpisuj±c
-      <literal>ppp_nat="NO"</literal> w
-      <filename>/etc/rc.conf</filename>. Ponadto nale¿y usun±æ
-      wpisy <literal>nat enable yes</literal> lub
-      <literal>alias enable yes</literal> w
-      <filename>/etc/ppp/ppp.conf</filename>.</para>
-  </sect1>
-
-  <sect1 id="rules">
-    <title>Regu³y firewalla</title>
-
-    <para>Wiêkszo¶æ pracy mamy ju¿ za sob±. Pozosta³o ju¿ tylko
-      ustalenie regu³ firewalla, po czym bêdzie mo¿na dokonaæ
-      prze³adowania systemu i powinni¶my otrzymaæ dzia³aj±cego
-      firewalla. Zdajê sobie sprawê, ¿e zbiór regu³ zale¿y od
-      indywidualnych
-      potrzeb, stara³em siê jednak przygotowaæ regu³y odpowiednie
-      dla wiêkszo¶ci u¿ytkowników ³±cz komutowanych. Mo¿na je
-      oczywi¶cie dostosowaæ samodzielnie, traktuj±c poni¿sze regu³y
-      jako punkt wyj¶cia. Zacznijmy od zamkniêtego firewalla: z
-      za³o¿enia wszystkie pakiety s± blokowane, przepuszczaæ
-      bêdziemy jedynie to, co jest nam rzeczywi¶cie potrzebne.
-      Regu³y powinny najpierw okre¶laæ, co jest przepuszczane, potem
-      co jest blokowane. Podajemy wiêc wszystkie regu³y
-      przepuszczaj±ce, a potem nakazujemy blokowaæ ca³± resztê.
-      :)</para>
-
-    <para>Stwórzmy teraz katalog <filename
-      class="directory">/etc/firewall</filename>. W nim utwórzmy plik
-      <filename>fwrules</filename>, zgodnie z tym, co napisali¶my
-      w <filename>rc.conf</filename>. Mo¿emy oczywi¶cie nazwaæ ten
-      plik jak nam siê ¿ywnie podoba, proponowana tu nazwa jest
-      jedn± z mo¿liwo¶ci.</para>
-
-    <para>Spójrzmy teraz na przyk³adowy plik firewalla, opatrzony
-      komentarzami.</para>
-
-
-    <programlisting>
-# Regu³y firewalla
-# Autor: Marc Silver (marcs@draenor.org)
-# http://draenor.org/ipfw
-#
-
-# Definicja komendy firewalla (jak w /etc/rc.firewall) upraszcza
-# jej wywo³ywanie i czyni plik bardziej czytelnym.
-fwcmd="/sbin/ipfw"
-
-# Wyczyszczenie aktualnie obowi±zuj±cych regu³.
-$fwcmd -f flush
-
-# Przekierowanie wszystkich pakietów przez interfejs tun0.
-$fwcmd add divert natd all from any to any via tun0
-
-# Przepuszczanie danych przesy³anych przez kartê sieciow± i lokalnie.
-# Upewnij siê, ¿e wpisa³e¶ tu w³a¶ciw± kartê (w moim przypadku fxp0)
-# zanim prze³adujesz system. :)
-$fwcmd add allow ip from any to any via lo0
-$fwcmd add allow ip from any to any via fxp0
-
-# Przepuszczanie wszystkich po³±czeñ nawi±zywanych przez nas.
-$fwcmd add allow tcp from any to any out xmit tun0 setup
-
-# Pozwalamy, by po³±czenia nawi±zane mog³y pozostaæ otwarte.
-$fwcmd add allow tcp from any to any via tun0 established
-
-# Zezwolenie na po³±czenia z zewn±trz z okre¶lonymi us³ugami na
-# naszej maszynie. Przyk³adowo dopuszczamy po³±czenia z ssh i apache.
-$fwcmd add allow tcp from any to any 80 setup
-$fwcmd add allow tcp from any to any 22 setup
-
-# Wysy³amy RESET w odpowiedzi na pakiety ident.
-$fwcmd add reset log tcp from any to any 113 in recv tun0
-
-# Pozwalamy na wychodz±ce zapytania DNS do wybranych serwerów.
-$fwcmd add allow udp from any to <replaceable>x.x.x.x</replaceable> 53 out xmit tun0
-
-# I oczywi¶cie pozwalamy im odpowiedzieæ... :)
-$fwcmd add allow udp from <replaceable>x.x.x.x</replaceable> 53 to any in recv tun0
-
-# Dopuszczenie pakietów ICMP (dziêki którym dzia³aj± ping i traceroute).
-# Mo¿na zdecydowaæ siê na ich blokowanie, ja jednak my¶lê, ¿e mi siê
-# przydadz±.
-$fwcmd add allow icmp from any to any
-
-# Odrzucenie ca³ej reszty.
-$fwcmd add deny log ip from any to any
-</programlisting>
-
-    <para>Zbudowali¶my w pe³ni sprawny firewall zezwalaj±cy na po³±czenia
-      z portami 80 i 22, oraz rejestruj±cy próby po³±czenia z czymkolwiek
-      innym. Po prze³adowaniu systemu powinien ju¿ nale¿ycie
-      funkcjonowaæ. Je¿eli jakiekolwiek z podanych tu informacji
-      oka¿± siê b³êdne, b±d¼ bêd± powodowaæ problemy, proszê o
-      zawiadomienie emailem. Mile widziane s± równie¿ pomys³y
-      na ulepszenie niniejszej strony.</para>
-  </sect1>
-
-  <sect1>
-    <title>Pytania</title>
-
-    <qandaset>
-      <qandaentry>
-	<question>
-	  <para>Dlaczego korzystasz z &man.natd.8; i &man.ipfw.8;, a
-	    nie z filtrów wbudowanych w &man.ppp.8;?</para>
-	</question>
-
-	<answer>
-	  <para>Mówi±c szczerze, nie ma konkretnego powodu dla którego
-	    zdecydowa³em siê na <command>ipfw</command> i
-	    <command>natd</command>, a nie filtrowanie wbudowane w
-	    <command>ppp</command>. Dyskusje przeprowadzone z
-	    ró¿nymi osobami doprowadzi³y do stwierdzenia, i¿
-	    <command>ipfw</command> jest z pewno¶ci± bardziej
-	    rozbudowany i ma wiêksze mo¿liwo¶ci konfiguracji ni¿
-	    filtry <command>ppp</command>, jest jednak trudniejszy
-	    w u¿ywaniu. Jednym z powodów mojego wyboru jest
-	    to, ¿e wolê, by firewall dzia³a³ na poziomie j±dra systemu,
-	    a nie programu u¿ytkownika.</para>
-	</answer>
-      </qandaentry>
-
-      <qandaentry>
-        <question>
-	  <para>Otrzymujê komunikat w rodzaju <errorname>limit 100
-	    reached on entry 2800</errorname>, po którym w logach
-	    nie pojawiaj± siê informacje o zablokowanych pakietach.
-	    Czy mój firewall nadal dzia³a?</para>
-        </question>
-
-	<answer>
-	  <para>Taki komunikat oznacza jedynie, ¿e osi±gniêty zosta³
-	    limit rejestrowania regu³y. Sama regu³a wci±¿ obowi±zuje,
-	    nie bêdzie ju¿ jednak rejestrowana, dopóki liczniki
-	    rejestrowania nie zostan± wyzerowane; mo¿na to zrobiæ
-	    poleceniem <command>ipfw resetlog</command>. Innym
-	    rozwi±zaniem jest zwiêkszenie limitu w konfiguracji
-	    j±dra przy pomocy opcji
-	    <option>IPFIREWALL_VERBOSE_LIMIT</option>, tak jak
-	    jest to opisane wcze¶niej. Limit mo¿na tak¿e ustawiæ
-	    zmieniaj±c warto¶æ net.inet.ip.fw.verbose_limit
-	    przy pomocy &man.sysctl.8;.</para>
-        </answer>
-      </qandaentry>
-
-      <qandaentry>
-	<question>
-	  <para>W sieci wewnêtrznej korzystam z adresów z puli prywatnej,
-	    np. z zakresu 192.168.0.0, czy mogê uzupe³niæ regu³y firewalla
-	    wpisem w rodzaju
-	    <literal>$fwcmd add deny all from any to
-	    192.168.0.0:255.255.0.0 via tun0</literal> aby uniemo¿liwiæ
-	    próby po³±czeñ z zewn±trz z lokalnymi maszynami?</para>
-	</question>
-
-	<answer>
-	  <para>Nie, poniewa¿ <emphasis>wszystko</emphasis> co
-	    przechodzi przez <devicename>tun0</devicename> podlega
-	    t³umaczeniu adresów realizowanemu przez
-	    <command>natd</command>.
-	    Pakiety przychodz±ce z zewn±trz trafiaj± wy³±cznie do
-	    dynamicznie przydzielonego adresu IP, a
-	    <emphasis>nie</emphasis> do sieci wewnêtrznej. Zauwa¿my
-	    jednak, ¿e mo¿na dodaæ regu³ê w rodzaju <literal>$fwcmd
-	    add deny all from 192.168.0.4:255.255.0.0 to any
-	    via tun0</literal>, która zabroni maszynie w sieci
-	    wewnêtrznej komunikowania siê ze ¶wiatem przez
-	    firewall.</para>
-	</answer>
-      </qandaentry>
-
-      <qandaentry>
-	<question>
-	  <para>Co¶ musi byæ nie tak. Postêpowa³em dok³adnie wed³ug
-	    wskazówek i jestem w kropce.</para>
-        </question>
-
-	<answer>
-	  <para>W artykule przyjmujemy, ¿e korzystamy z
-	    <emphasis>userland-ppp</emphasis>, regu³y obowi±zuj± wiêc
-	    dla interfejsu <devicename>tun0</devicename>, odpowiadaj±cemu
-	    pierwszemu po³±czeniu nawi±zanemu przez &man.ppp.8;
-	    (zwanemu tak¿e <emphasis>user-ppp</emphasis>). Dodatkowym
-	    po³±czeniom odpowiadaæ bêd± interfejsy
-	    <devicename>tun1</devicename>, <devicename>tun2</devicename>
-	    itd. </para>
-
-	  <para>W przypadku &man.pppd.8; jest
-	    z kolei wykorzystywany
-	    interfejs <devicename>ppp0</devicename>, je¶li
-	    wiêc po³±czenie jest realizowane za po¶rednictwem
-	    &man.pppd.8;, w miejscu <devicename>tun0</devicename>
-	    trzeba wstawiæ <devicename>ppp0</devicename>. Poni¿ej
-	    przedstawiona jest szybka metoda uwzglêdnienia tej zmiany
-	    w regu³ach firewalla. Oryginalny plik z regu³ami
-	    zachowywany jest pod nazw±
-	    <filename>fwrules_tun0</filename>.</para>
-
-	  <screen>	    &prompt.user; <userinput>cd /etc/firewall</userinput>
-	    /etc/firewall&prompt.user; <userinput>su</userinput>
-	    <prompt>Password:</prompt>
-	    /etc/firewall&prompt.root; <userinput>mv fwrules fwrules_tun0</userinput>
-	    /etc/firewall&prompt.root; <userinput>cat fwrules_tun0 | sed s/tun0/ppp0/g > fwrules</userinput>
-	  </screen>
-
-	  <para>By przekonaæ siê, czy w u¿yciu jest &man.ppp.8;, czy
-	    &man.pppd.8;, mo¿na po nawi±zaniu po³±czenia
-	    pos³u¿yæ siê &man.ifconfig.8;. W przypadku po³±czenia
-	    nawi±zanego przez &man.pppd.8; zobaczyliby¶my co¶
-	    w rodzaju (pomijaj±c nieistotne informacje):</para>
-
-	  <screen>	    &prompt.user; <userinput>ifconfig</userinput>
-	    <emphasis>(nieistotne...)</emphasis>
-	    ppp0: flags=<replaceable>8051&lt;UP,POINTOPOINT,RUNNING,MULTICAST&gt; mtu 1524</replaceable>
-                    inet <replaceable>xxx.xxx.xxx.xxx</replaceable> -************-&gt; <replaceable>xxx.xxx.xxx.xxx</replaceable> netmask <replaceable>0xff000000</replaceable>
-	    <emphasis>(nieistotne...)</emphasis>
-	    </screen>
-
-	  <para>Natomiast gdy nawi±zanie po³±czenia odby³o siê za
-	    po¶rednictwem &man.ppp.8; (<emphasis>user-ppp</emphasis>),
-	    ujrzymy co¶ takiego:</para>
-
-	  <screen>	    &prompt.user; <userinput>ifconfig</userinput>
-	    <emphasis>(nieistotne...)</emphasis>
-	    ppp0: flags=<replaceable>8010&lt;POINTOPOINT,MULTICAST&gt; mtu 1500</replaceable>
-	    <emphasis>(nieistotne...)</emphasis>
-	    tun0: flags=<replaceable>8051&lt;UP,POINTOPOINT,RUNNING,MULTICAST&gt; mtu 1524</replaceable>
-	            <emphasis>(nieistotne IPv6...)</emphasis>
-                    inet <replaceable>xxx.xxx.xxx.xxx</replaceable> -************-&gt; <replaceable>xxx.xxx.xxx.xxx</replaceable> netmask <replaceable>0xffffff00</replaceable>
-                    Opened by PID <replaceable>xxxxx</replaceable>
-            <emphasis>(nieistotne...)</emphasis></screen>
-	</answer>
-      </qandaentry>
-    </qandaset>
-  </sect1>
-</article>
diff --git a/pt_BR.ISO8859-1/articles/linux-users/article.sgml b/pt_BR.ISO8859-1/articles/linux-users/article.sgml
index 8f0f35a99c..24fd1f2698 100644
--- a/pt_BR.ISO8859-1/articles/linux-users/article.sgml
+++ b/pt_BR.ISO8859-1/articles/linux-users/article.sgml
@@ -166,11 +166,6 @@ in your /etc/rc.conf. Extra options can be found in startup script.</screen>
 	  url="ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-6-stable/Latest/"></ulink>
 	  para baixar os pacotes mais recentes compilados para a 
 	  série 6.X.</para>
-
-	<para>Você pode ler mais sobre as versões do 
-	  &os; no artigo <ulink
-	  url="&url.base;/doc/en_US.ISO8859-1/articles/version-guide/">
-	  Escolhendo a Versão do &os; Certa para Você</ulink>.</para>
       </note>
 
       <para>Para mais informações sobre pacotes, por 
diff --git a/pt_BR.ISO8859-1/books/faq/book.sgml b/pt_BR.ISO8859-1/books/faq/book.sgml
index f0d503d809..4da177597b 100644
--- a/pt_BR.ISO8859-1/books/faq/book.sgml
+++ b/pt_BR.ISO8859-1/books/faq/book.sgml
@@ -1564,16 +1564,6 @@ File: +DESC (ignored)</screen>
       </qandaentry>
 
       <qandaentry>
-	<question id="multiboot">
-	  <para>Posso ter mais de um sistema operacional no meu PC?</para>
-	</question>
-
-	<answer>
-	  <para>De uma olhada na página de <ulink url="../../articles/multi-os/index.html">múltiplos-SO</ulink>.</para>
-	</answer>
-      </qandaentry>
-
-      <qandaentry>
 	<question id="windows-coexist">
 	  <para>O Windows 95/98 pode co-existir com o FreeBSD?</para>
 	</question>
@@ -6596,20 +6586,6 @@ device sio5 at isa? port 0x2b8 tty flags 0x501 vector siointr</programlisting>
 
     <qandaset>
       <qandaentry>
-	<question id="adding-disks">
-	  <para>Como procedo para adicionar um novo disco
-	    rígido no FreeBSD?</para>
-	</question>
-
-	<answer>
-	  <para>Veja o Tutorial sobre a Formatação de
-	    Discos no sítio<ulink
-	      url="../../articles/formatting-media/index.html">
-	      www.FreeBSD.org</ulink>.</para>
-	</answer>
-      </qandaentry>
-
-      <qandaentry>
 	<question id="new-huge-disk">
 	  <para>Como eu mudo todo o meu sistema operacional para um
 	    disco novo?</para>
@@ -6642,11 +6618,7 @@ device sio5 at isa? port 0x2b8 tty flags 0x501 vector siointr</programlisting>
 	    possa alternar a inicialização entre o novo
 	    sistema e a configuração atual do mesmo,
 	    até que a cópia dos dados tenha sido
-	    efetuada.  Veja o artigo <ulink
-	      url="../../articles/formatting-media/index.html">
-	    </ulink>referente a formatação de
-	    mídias para obter mais detalhes quanto a esse
-	    processo.</para>
+	    efetuada.</para>
 
 	  <para>Agora, com um novo disco configurado, você
 	    está pronto para começar a mover os dados da
diff --git a/ru_RU.KOI8-R/articles/5-roadmap/Makefile b/ru_RU.KOI8-R/articles/5-roadmap/Makefile
deleted file mode 100644
index ec8b6857b7..0000000000
--- a/ru_RU.KOI8-R/articles/5-roadmap/Makefile
+++ /dev/null
@@ -1,24 +0,0 @@
-#
-# The FreeBSD Russian Documentation Project
-#
-# $FreeBSD$
-# $FreeBSDru: frdp/doc/ru_RU.KOI8-R/articles/5-roadmap/Makefile,v 1.2 2005/06/14 06:18:55 gad Exp $
-#
-# Original revision: r20561
-#
-# Article: FreeBSD 5-STABLE roadmap
-
-DOC?= article
-
-FORMATS?= html
-WITH_ARTICLE_TOC?=YES
-
-INSTALL_COMPRESSED?= gz
-INSTALL_ONLY_COMPRESSED?=
-
-SRCS=  article.sgml
-
-CSS_SHEET_ADDITIONS= extra.css
-
-DOC_PREFIX?= ${.CURDIR}/../../..
-.include "${DOC_PREFIX}/share/mk/doc.project.mk"
diff --git a/ru_RU.KOI8-R/articles/5-roadmap/article.sgml b/ru_RU.KOI8-R/articles/5-roadmap/article.sgml
deleted file mode 100644
index a3198bc882..0000000000
--- a/ru_RU.KOI8-R/articles/5-roadmap/article.sgml
+++ /dev/null
@@ -1,721 +0,0 @@
-<?xml version="1.0" encoding="koi8-r" standalone="no"?>
-<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V4.2-Based Extension//EN"
-	"../../../share/sgml/freebsd42.dtd" [
-<!ENTITY % entities PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Entity Set//RU" "../../share/sgml/entities.ent">
-%entities;
-<!ENTITY t.releng.3 "<literal>RELENG_3</literal>">
-<!ENTITY t.releng.4 "<literal>RELENG_4</literal>">
-<!ENTITY t.releng.5 "<literal>RELENG_5</literal>">
-<!ENTITY t.releng.5.1 "<literal>RELENG_5_1</literal>">
-<!ENTITY t.releng.5.2 "<literal>RELENG_5_2</literal>">
-<!ENTITY t.releng.5.3 "<literal>RELENG_5_3</literal>">
-<!ENTITY t.releng.head "<literal>HEAD</literal>">
-]>
-
-<!--
-     The FreeBSD Russian Documentation Project
-
-     $FreeBSDru: frdp/doc/ru_RU.KOI8-R/articles/5-roadmap/article.sgml,v 1.7 2007/05/15 06:07:48 gad Exp $
-
-     Original revision: r30798
--->
-
-<article lang="ru">
-  <articleinfo>
-    <title>îÁÐÒÁ×ÌÅÎÉÑ ÒÁÂÏÔ × 5-STABLE</title>
-
-    <authorgroup>
-      <corpauthor>The &os; Release Engineering Team</corpauthor>
-    </authorgroup>
-
-    <copyright>
-      <year>2003</year>
-      <holder role="mailto:re@FreeBSD.org">The &os; Release
-	Engineering Team</holder>
-    </copyright>
-
-    <legalnotice id="trademarks" role="trademarks">
-      &tm-attrib.freebsd;
-      &tm-attrib.ieee;
-      &tm-attrib.intel;
-      &tm-attrib.sparc;
-      &tm-attrib.sun;
-      &tm-attrib.opengroup;
-      &tm-attrib.general;
-    </legalnotice>
-
-    <pubdate>$FreeBSD$</pubdate>
-
-    <releaseinfo>$FreeBSD$</releaseinfo>
-
-    <abstract>
-      <para>äÁÎÎÙÊ ÄÏËÕÍÅÎÔ ÔÅÐÅÒØ ÉÍÅÅÔ × ÏÓÎÏ×ÎÏÍ ÉÓÔÏÒÉÞÅÓËÏÅ ÚÎÁÞÅÎÉÅ.
-	ïÎ ÒÁÓÓËÁÚÙ×ÁÌ Ï ÎÁÐÒÁ×ÌÅÎÉÉ ÒÁÂÏÔ × ÒÁÚÒÁÂÏÔËÅ ×ÅÒÓÉÊ &os;
-	&t.releng.5; ×ÅÔËÉ.  ðÅÒ×ÏÎÁÞÁÌØÎÁÑ ×ÅÒÓÉÑ ÄÏËÕÍÅÎÔÁ ÐÏÑ×ÉÌÁÓØ
-	× ÆÅ×ÒÁÌÅ 2003 Ç. (ÍÅÖÄÕ ÒÅÌÉÚÁÍÉ 5.0 É 5.1), É ÐÒÅÄÐÏÌÁÇÁÌÏÓØ,
-	ÞÔÏ ÏÎ ÂÕÄÅÔ ÉÓÐÏÌØÚÏ×ÁÔØÓÑ ÄÌÑ ÐÒÅÄÏÓÔÁ×ÌÅÎÉÑ ÐÌÁÎÁ ÐÏ ÐÅÒÅ×ÏÄÕ
-	&t.releng.5; ×ÅÔËÉ × <quote>ÓÔÁÂÉÌØÎÏÅ</quote>
-	ÓÏÓÔÏÑÎÉÅ, ËÁË ÐÏ ËÁÞÅÓÔ×Õ ËÏÄÁ, ÔÁË É ÐÏ ÄÏÒÁÂÏÔËÅ ÒÁÚÌÉÞÎÙÈ API/ABI.
-	÷ ËÁÞÅÓÔ×Å ÉÎÏÇÏ ×ÚÇÌÑÄÁ ÎÁ ÐÒÏÂÌÅÍÕ ÍÏÖÅÔ ÂÙÔØ ÉÎÔÅÒÅÓÎÁ ÓÔÁÔØÑ
-	<ulink url="&url.articles.version-guide;">
-	  <quote>÷ÙÂÏÒ ÐÏÄÈÏÄÑÝÅÊ ÄÌÑ ×ÁÓ ×ÅÒÓÉÉ &os;</quote>
-	</ulink>.  óÔÁÔØÑ <quote>÷ÙÂÏÒ ÐÏÄÈÏÄÑÝÅÊ ÄÌÑ ×ÁÓ ×ÅÒÓÉÉ &os;</quote>
-	ÂÙÌÁ ÎÁÐÉÓÁÎÁ × á×ÇÕÓÔÅ 2005 Ç. (ÎÁ Ä×Á Ó ÐÏÌÏ×ÉÎÏÊ ÇÏÄÁ ÐÏÚÖÅ)
-	É ÓÏÄÅÒÖÉÔ ÒÁÚÄÅÌ, × ËÏÔÏÒÏÍ ÏÐÉÓÙ×ÁÅÔÓÑ ËÁË ÒÁÚ×ÏÒÁÞÉ×ÁÌÉÓØ
-	ÐÌÁÎÙ É ÓÏÂÙÔÉÑ, Á ÔÁËÖÅ ËÁËÉÅ ÕÒÏËÉ ÂÙÌÉ ÐÏÌÕÞÅÎÙ.</para>
-    </abstract>
-  </articleinfo>
-
-  <sect1 id="intro">
-    <title>÷×ÅÄÅÎÉÅ É ÉÎÆÏÒÍÁÃÉÑ ÏÂÝÅÇÏ ÈÁÒÁËÔÅÒÁ</title>
-
-    <para>÷ ÑÎ×ÁÒÅ 2003 ÇÏÄÁ, ÐÏÓÌÅ ÐÒÉÍÅÒÎÏ ÔÒ£È ÌÅÔ ÒÁÂÏÔÙ, ÂÙÌÁ ×ÙÐÕÝÅÎÁ
-      &os; 5.0.  ôÁËÉŠţ ×ÏÚÍÏÖÎÏÓÔÉ, ËÁË ÔÅÈÎÏÌÏÇÉÑ GEOM, ÍÁÎÄÁÔÎÙÊ ËÏÎÔÒÏÌØ
-      ÄÏÓÔÕÐÁ, ACPI, ÐÏÄÄÅÒÖËÁ ÁÒÈÉÔÅËÔÕÒ &sparc64; É ia64, ÒÁÂÏÔÁ Ó
-      ÍÇÎÏ×ÅÎÎÙÍÉ ËÏÐÉÑÍÉ UFS, ÆÏÎÏ×ÁÑ ÐÒÏ×ÅÒËÁ ÃÅÌÏÓÔÎÏÓÔÉ ÆÁÊÌÏ×ÏÊ ÓÉÓÔÅÍÙ É
-      64-ÒÁÚÒÑÄÎÁÑ ÒÁÚÍÅÒÎÏÓÔØ ÕÚÌÏ× ÆÁÊÌÏ×ÏÊ ÓÉÓÔÅÍÙ ÄÅÌÁÀÔ ÜÔÕ ÏÐÅÒÁÃÉÏÎÎÕÀ
-      ÓÉÓÔÅÍÕ ÐÒÉ×ÌÅËÁÔÅÌØÎÏÊ ËÁË ÄÌÑ ËÏÒÐÏÒÁÔÉ×ÎÏÇÏ, ÔÁË É ÐÅÒÓÏÎÁÌØÎÏÇÏ
-      ÉÓÐÏÌØÚÏ×ÁÎÉÑ.  ïÄÎÁËÏ ÒÁÂÏÔÁ ÎÁÄ ÎÅËÏÔÏÒÙÍÉ ×ÁÖÎÙÍÉ ×ÏÚÍÏÖÎÏÓÔÑÍÉ ÅÝ£
-      ÎÅ ÚÁ×ÅÒÛÅÎÁ.  ðÒÏÇÒÁÍÍÎÁÑ ÏÓÎÏ×Á ÄÌÑ ×ÙÓÏËÏÔÏÞÎÏÊ ÂÌÏËÉÒÏ×ËÉ É
-      ×ÙÔÅÓÎÑÅÍÏÓÔÉ ÚÁÄÁÞ × ÑÄÒÅ ÕÖÅ ÉÍÅÅÔÓÑ, ÏÄÎÁËÏ ÐÒÅÄÓÔÏÉÔ ÓÄÅÌÁÔØ ÅÝ£
-      ÂÏÌØÛÅ.  ðÒÏÉÚ×ÏÄÉÔÅÌØÎÏÓÔØ É ÓÔÁÂÉÌØÎÏÓÔØ ÐÏ ÓÒÁ×ÎÅÎÉÀ Ó &os;
-      4.<replaceable>X</replaceable> ÎÅÓËÏÌØËÏ ÓÎÉÚÉÌÁÓØ, ÏÄÎÁËÏ ÜÔÉ
-      ÈÁÒÁËÔÅÒÉÓÔÉËÉ ÄÏÌÖÎÙ ÂÙÔØ ×ÏÓÓÔÁÎÏ×ÌÅÎÙ É ÄÁÖÅ ÕÌÕÞÛÅÎÙ.</para>
-
-    <para>üÔÏ ÎÅÓËÏÌØËÏ ÎÁÐÏÍÉÎÁÅÔ ÓÉÔÕÁÃÉÀ, Ó ËÏÔÏÒÏÊ &os; ÓÔÁÌËÉ×ÁÌÁÓØ ×
-      ÌÉÎÅÊËÅ 3.<replaceable>X</replaceable>.  òÁÂÏÔÁ ÎÁÄ 3-CURRENT
-      ÚÁÔÑÇÉ×ÁÌÁÓØ ÄÏ ÂÅÓËÏÎÅÞÎÏÓÔÉ, É ÎÁËÏÎÅà ÂÙÌÏ ÐÒÉÎÑÔÏ ÒÅÛÅÎÉÅ
-      <quote>ÐÒÏÓÔÏ ×ÙÐÕÓÔÉÔØ Å£</quote>, Á ÄÏÒÁÂÏÔÁÔØ ÐÏÚÖÅ.  ôÁËÏÅ ÒÅÛÅÎÉÅ
-      ÐÒÉ×ÅÌÏ Ë ÔÏÍÕ, ÞÔÏ ËÁÞÅÓÔ×Ï ÒÅÌÉÚÏ× 3.0 É 3.1 ÎÅ ÍÏÇÌÏ ÕÄÏ×ÌÅÔ×ÏÒÉÔØ
-      ÂÏÌØÛÉÎÓÔ×Ï ÐÏÌØÚÏ×ÁÔÅÌÅÊ, É ÔÁË ÂÙÌÏ ÄÏ ×ÅÒÓÉÉ 3.2, ËÏÇÄÁ ÌÉÎÅÊËÁ ÂÙÌÁ
-      ÐÒÉÚÎÁÎÁ <quote>ÓÔÁÂÉÌØÎÏÊ</quote>.  èÕÖÅ ÔÏÇÏ, ×ÅÔËÁ &t.releng.3; ÂÙÌÁ
-      ÓÏÚÄÁÎÁ ÎÁ ÏÓÎÏ×Å ÒÅÌÉÚÁ 3.0, Á ×ÅÔËÁ &t.releng.head; ÄÏÌÖÎÁ ÂÙÌÁ ×ÅÓÔÉ Ë
-      4-CURRENT.  ÷ ÒÅÚÕÌØÔÁÔÅ ×ÅÔËÉ &t.releng.head; É &t.releng.3; ÓÔÁÌÉ
-      ÓÉÌØÎÏ ÏÔÌÉÞÁÔØÓÑ, ÞÔÏ ÚÎÁÞÉÔÅÌØÎÏ ÏÓÌÏÖÎÉÌÏ ÐÏÄÄÅÒÖËÕ ×ÅÔËÉ
-      &t.releng.3;.  &os; 2.2.8 ÂÙÌÁ ÏÓÔÁ×ÌÅÎÁ ËÁË ÐÏÓÌÅÄÎÑÑ ×ÅÒÓÉÑ &os;,
-      ÐÏÄÈÏÄÑÝÁÑ ÄÌÑ ÐÒÏÄÕËÔÉ×ÎÏÊ ÜËÓÐÌÕÁÔÁÃÉÉ.</para>
-
-    <para>îÁÛÅÊ ÚÁÄÁÞÅÊ Ñ×ÌÑÅÔÓÑ ÎÅÄÏÐÕÝÅÎÉÅ ÐÏ×ÔÏÒÅÎÉÑ ÔÁËÏÇÏ ÓÃÅÎÁÒÉÑ ×Ï
-      &os; 5.x.  ïÔËÌÁÄÙ×ÁÎÉÅ ×ÅÔËÉ &t.releng.5; ÄÏ ÍÏÍÅÎÔÁ, ËÏÇÄÁ ÏÎÁ ÓÔÁÎÅÔ
-      ÓÔÁÂÉÌØÎÏÊ É ÄÏÓÔÉÇÎÅÔ ËÁÞÅÓÔ×Á ÐÒÏÄÕËÔÁ, ÇÏÔÏ×ÏÇÏ Ë ÒÅÁÌØÎÏÊ
-      ÜËÓÐÌÕÁÔÁÃÉÉ, ÏÂÅÓÐÅÞÉÔ ÂÕÄÕÝÕÀ ÐÏÄÄÅÒÖËÕ ÜÔÏÊ ïó É ÏÂßÅËÔÉ×ÎÕÀ ÐÒÉÞÉÎÕ
-      ÐÅÒÅÈÏÄÁ Ó ×ÅÒÓÉÉ 4.<replaceable>X</replaceable>,  äÌÑ ÜÔÏÇÏ ÍÙ ÄÏÌÖÎÙ
-      ÏÐÒÅÄÅÌÉÔØ ÓÌÁÂÙÅ ÍÅÓÔÁ É ÎÁÍÅÔÉÔØ ÓÐÏÓÏÂÙ ÉÈ ÕÓÔÒÁÎÅÎÉÑ.  ÷ ÜÔÏÍ
-      ÄÏËÕÍÅÎÔÅ ÏÐÉÓÁÎÙ ÔÅ ÍÏÍÅÎÔÙ, ËÏÔÏÒÙÅ ÍÙ, ËÁË ÇÒÕÐÐÁ ÐÏ ÐÏÄÇÏÔÏ×ËÅ
-      ÒÅÌÉÚÏ×, ÓÞÉÔÁÅÍ ÚÎÁÞÉÔÅÌØÎÙÍÉ É ÔÅ ×ÏÐÒÏÓÙ, ËÏÔÏÒÙÅ ÄÏÌÖÎÙ ÂÙÔØ ÒÅÛÅÎÙ
-      ÄÏ ÓÏÚÄÁÎÉÑ ×ÅÔËÉ &t.releng.5;.  úÄÅÓØ ÎÅ ÏÐÒÅÄÅÌÑÀÔÓÑ ×ÓÅ ÁÓÐÅËÔÙ ÒÁÂÏÔÙ
-      ÎÁÄ &os;, É ÍÙ ÇÏÔÏ×Ù Ë ÄÁÌØÎÅÊÛÅÍÕ ÏÂÓÕÖÄÅÎÉÀ.  îÉÞÅÇÏ ÉÚ ÔÏÇÏ, ÞÔÏ
-      ÎÁÐÉÓÁÎÏ ÄÁÌÅÅ, ÎÅ Ñ×ÌÑÅÔÓÑ ÉÎÓÉÎÕÁÃÉÑÍÉ ÐÒÏÔÉ× ËÁËÏÊ ÂÙ ÔÏ ÎÉ ÂÙÌÏ
-      ÐÅÒÓÏÎÙ ÉÌÉ ÇÒÕÐÐÙ, ÃÅÌØÀ ÎÅ Ñ×ÌÑÅÔÓÑ ÕÐÒÏÝÅÎÉÅ ÎÉËÁËÏÊ ÓÄÅÌÁÎÎÏÊ ËÅÍ-ÔÏ
-      ÒÁÂÏÔÙ.  ïÄÎÁËÏ ÉÍÅÀÔÓÑ ÎÅËÏÔÏÒÙÅ ×ÁÖÎÙÅ ×ÏÐÒÏÓÙ, ËÏÔÏÒÙÅ ÔÒÅÂÕÀÔ
-      ÒÅÛÉÔÅÌØÎÙÈ É ÂÅÓÐÒÉÓÔÒÁÓÔÎÙÈ ÄÅÊÓÔ×ÉÊ.</para>
-  </sect1>
-
-  <sect1 id="major-issues">
-    <title>ïÓÎÏ×ÎÙÅ ×ÏÐÒÏÓÙ</title>
-
-    <para>õÓÐÅÈ ÌÉÎÅÊËÉ 5.<replaceable>X</replaceable> ÚÁ×ÉÓÉÔ ÏÔ ×ÏÚÍÏÖÎÏÓÔÉ
-      ÐÒÅÄÏÓÔÁ×ÉÔØ ×ÙÓÏËÏÔÏÞÎÏÅ ÕÐÒÁ×ÌÅÎÉÅ ÐÏÔÏËÁÍÉ ×ÙÐÏÌÎÅÎÉÑ É ÐÏ×ÔÏÒÑÅÍÏÓÔØ
-      ×ÙÚÏ×Ï× × ÑÄÒÅ (ÞÔÏ ÉÚ×ÅÓÔÎÏ ËÁË SMPng), Á ÔÁËÖÅ ÐÏÄÄÅÒÖËÉ ÎÁ ÕÒÏ×ÎÅ ÑÄÒÁ
-      POSIX-ÐÏÔÏËÏ× ×ÙÐÏÌÎÅÎÉÑ ÐÏÌØÚÏ×ÁÔÅÌØÓËÏÇÏ ÕÒÏ×ÎÑ, ÎÅ ÖÅÒÔ×ÕÑ ÐÒÉ ÜÔÏÍ
-      ÏÂÝÅÊ ÓÔÁÂÉÌØÎÏÓÔØÀ ÉÌÉ ÐÒÏÉÚ×ÏÄÉÔÅÌØÎÏÓÔØÀ ÓÉÓÔÅÍÙ.</para>
-
-    <sect2 id="SMPng">
-      <title>SMPng</title>
-
-      <para>òÁÂÏÔÁÍ ÎÁÄ SMPng É ÂÌÏËÉÒÏ×ËÁÍÉ ÎÁ ÕÒÏ×ÎÅ ÑÄÒÁ ÕÄÅÌÑÅÔÓÑ ÓÁÍÏÅ
-	ÂÏÌØÛÏÅ ×ÎÉÍÁÎÉÅ ÄÌÑ 5.<replaceable>X</replaceable>.  îÁ ÔÅËÕÝÉÊ ÍÏÍÅÎÔ
-	ÂÙÌÏ ×ÙÐÕÝÅÎÏ ÎÅÓËÏÌØËÏ ×ÅÒÓÉÊ ÓÉÓÔÅÍÙ Ó ÇÌÏÂÁÌØÎÙÍÉ ÓÅÍÁÆÏÒÁÍÉ ÎÁ ×Ó£
-	ÑÄÒÏ, ÉÚ×ÅÓÔÎÙÍÉ ËÁË <quote>Giant</quote>.  óÔÒÁÎÉÃÁ Ï ÓÏÓÔÏÑÎÉÉ ÒÁÂÏÔ
-	ÎÁÄ SMP ÐÏ ÁÄÒÅÓÕ <ulink url="&url.base;/smp"></ulink>
-	ÓÏÄÅÒÖÉÔ ÉÓÞÅÒÐÙ×ÁÀÝÕÀ ÉÎÆÏÒÍÁÃÉÀ Ï ÏÂÝÅÍ ÓÏÓÔÏÑÎÉÉ SMPng.  éÎÆÏÒÍÁÃÉÑ
-	ÐÏ ËÏÎËÒÅÔÎÏ ÒÁÂÏÔÁÍ ÎÁÄ SMPng × ÄÒÁÊ×ÅÒÁÈ ÕÓÔÒÏÊÓÔ× ÍÏÖÅÔ ÂÙÔØ ÎÁÊÄÅÎÁ
-	ÎÁ ÓÔÒÁÎÉÃÅ <ulink
-	url="&url.base;/projects/busdma"></ulink>.  ÷ ÃÅÌÏÍ:</para>
-
-      <itemizedlist>
-	<listitem>
-	  <para>VM: ÆÕÎËÃÉÑ ÑÄÒÁ malloc ÉÚÏÌÉÒÏ×ÁÎÁ É ÏÓ×ÏÂÏÖÄÅÎÁ
-	    ÏÔ Giant.  áÌÌÏËÁÔÏÒ ÚÏÎ UMA ÔÁËÖÅ ÎÅ ÉÓÐÏÌØÚÕÅÔ Giant.
-	    éÚÏÌÑÃÉÑ vm_object ÎÁÈÏÄÉÔÓÑ × ÒÁÂÏÔÅ É Ñ×ÌÑÅÔÓÑ ×ÁÖÎÙÍ ÛÁÇÏÍ ×
-	    ÉÓËÌÀÞÅÎÉÉ Giant ÉÚ ÒÁÂÏÔÙ Ó ÂÕÆÅÒÁÍÉ/ËÜÛÅÍ.  éÚÏÌÑÃÉÑ pmap ÅÝ£
-	    ÎÅ ÒÅÁÌÉÚÏ×Ù×ÁÌÁÓØ.</para>
-	</listitem>
-
-	<listitem>
-	  <para>GEOM: ÕÒÏ×ÅÎØ ÂÌÏËÏ× GEOM ÂÙÌ ÒÁÚÒÁÂÏÔÁÎ Ó ÕÞ£ÔÏÍ ÒÁÂÏÔÙ ÂÅÚ
-	    Giant É ÏÎ ÐÏÚ×ÏÌÑÅÔ ÒÁÂÏÔÁÔØ ÍÏÄÕÌÑÍ GEOM É ÎÉÚÌÅÖÁÝÉÍ ÄÒÁÊ×ÅÒÁÍ
-	    ÂÌÏÞÎÙÈ ÕÓÔÒÏÊÓÔ× ÂÅÚ Giant.  îÁ ÄÁÎÎÙÊ ÍÏÍÅÎÔ ÔÏÌØËÏ ÄÒÁÊ×ÅÒÙ
-	    &man.ata.4; É &man.aac.4; ÒÁÚÄÅÌÅÎÙ É ÒÁÂÏÔÁÀÔ ÂÅÚ
-	    Giant.  òÁÂÏÔÁ ÎÁÄ ÏÓÔÁÌØÎÙÍÉ ÄÒÁÊ×ÅÒÁÍÉ ÂÌÏÞÎÙÈ ÕÓÔÒÏÊÓÔ× ×ÅÄ£ÔÓÑ.
-	    éÚÏÌÑÃÉÑ CAM-ÐÏÄÓÉÓÔÅÍÙ ÔÒÅÂÕÅÔ ÏÔËÁÚÁ ÏÔ ÉÓÐÏÌØÚÏ×ÁÎÉÑ Giant
-	    ÐÒÁËÔÉÞÅÓËÉ ×Ï ×ÓÅÈ ÄÒÁÊ×ÅÒÁÈ SCSI; ÒÁÂÏÔÁ ÎÁÄ ÜÔÉÍ ÅÝ£ ÎÅ
-	    ÎÁÞÉÎÁÌÁÓØ.</para>
-
-	  <para>ëÒÏÍÅ ÔÏÇÏ, × GEOM ÉÍÅÅÔÓÑ ÏÐÁÓÎÏÓÔØ ÓÎÉÖÅÎÉÑ
-	    ÐÒÏÉÚ×ÏÄÉÔÅÌØÎÏÓÔÉ ÉÚ-ÚÁ ÏÂÒÁÂÏÔËÉ ÅÀ ×ÙÛÅÓÔÏÑÝÉÈ É ÎÉÖÅÓÔÏÑÝÉÈ
-	    ÐÏÔÏËÏ× ÄÁÎÎÙÈ × ÐÏÔÏËÁÈ ×ÙÐÏÌÎÅÎÉÑ ÑÄÒÁ.  ÷ ÒÅÛÅÎÉÉ ÜÔÏÊ ÐÒÏÂÌÅÍÙ
-	    ÍÏÖÅÔ ÐÏÍÏÞØ ÕÌÕÞÛÅÎÉÅ É ÕÐÒÏÝÅÎÉÅ ÔÅÈÎÏÌÏÇÉÉ ÐÅÒÅËÌÀÞÅÎÉÑ
-	    ËÏÎÔÅËÓÔÏ× ×ÙÐÏÌÎÅÎÉÑ.</para>
-	</listitem>
-
-	<listitem>
-	  <para>óÅÔØ: ÒÁÂÏÔÁ ÐÏ ÐÅÒÅ×ÏÄÕ ÎÁ ÉÚÏÌÑÃÉÀ ÓÅÔÅ×ÏÇÏ ÓÔÅËÁ ÂÙÌÁ
-	    ÎÁÞÁÔÁ ÚÁÎÏ×Ï.  éÚÎÁÞÁÌØÎÏ ÃÅÌÑÍÉ ÂÙÌÉ ÔÁÂÌÉÃÙ ÍÁÒÛÒÕÔÉÚÁÃÉÉ, ARP,
-	    ÆÕÎËÃÉÉ ÍÏÓÔÁ, IPFW, Fast-Forward, TCP, UDP, IP, Fast IPSEC É
-	    ÕÒÏ×ÎÉ ÉÎÔÅÒÆÅÊÓÏ×, Á ÔÁËÖÅ ÎÅËÏÔÏÒÙÅ ÄÒÁÊ×ÅÒÙ ÕÓÔÒÏÊÓÔ× Ethernet.
-	    ðÏÚÖÅ ÂÙÌÉ ÐÏÓÔÁ×ÌÅÎÙ ÃÅÌÉ ÐÏ ÉÚÏÌÑÃÉÉ ÕÒÏ×ÎÅÊ ÓÏËÅÔÏ×, IPv6 É
-	    ÄÒÕÇÉÈ ÓÅÔÅ×ÙÈ ÐÒÏÔÏËÏÌÏ×.  ïÓÎÏ×ÎÏÊ ÚÁÄÁÞÅÊ ÜÔÏÊ ÒÁÂÏÔÙ Ñ×ÌÑÅÔÓÑ
-	    ×ÏÓÓÔÁÎÏ×ÌÅÎÉÅ ÐÒÏÉÚ×ÏÄÉÔÅÌØÎÏÓÔÉ, ÄÏÓÔÉÇÎÕÔÏÊ ×Ï &os;
-	    4.<replaceable>X</replaceable>.  úÁÔÒÁÔÙ ÎÁ ÐÅÒÅËÌÀÞÅÎÉÅ ËÏÎÔÅËÓÔÏ×
-	    ÎÁ ithreads É netisr × ÄÒÁÊ×ÅÒÁÈ ÕÓÔÒÏÊÓÔ× ×Ó£ ÅÝ£ ÓÉÌØÎÏ ×ÌÉÑÀÔ ÎÁ
-	    ÐÒÏÉÚ×ÏÄÉÔÅÌØÎÏÓÔØ.</para>
-	</listitem>
-
-	<listitem>
-	  <para>VFS: ÎÁÞÁÔÁ ÐÒÅÄ×ÁÒÉÔÅÌØÎÁÑ ÐÏÄÇÏÔÏ×ËÁ.</para>
-	</listitem>
-
-	<listitem>
-	  <para>âÕÆÅÒ/ËÜÛ: ÚÁËÏÎÞÅÎÁ ÎÁÞÁÌØÎÁÑ ÒÁÂÏÔÁ ÐÏ ÉÚÏÌÑÃÉÉ
-	     ÂÕÆÅÒÏ×.</para>
-	</listitem>
-
-	<listitem>
-	  <para>Proc: ÎÁÞÁÌØÎÏÅ ÉÚÏÌÑÃÉÑ proc ÕÖÅ ÅÓÔØ, ×Ï &os; 5.2 ÏÖÉÄÁÅÔÓÑ
-	    ÅÝ£ ÂÏÌØÛÉÊ ÐÒÏÇÒÅÓÓ.</para>
-	</listitem>
-
-	<listitem>
-	  <para>CAM: ÎÁ ÕÒÏ×ÎÅ CAM SCSI ÚÎÁÞÉÔÅÌØÎÏÊ ÒÁÂÏÔÙ ÎÅ
-	    ÐÒÏÄÅÌÁÎÏ.</para>
-	</listitem>
-
-	<listitem>
-	  <para>Newbus: ÂÙÌÁ ÐÒÏÄÅÌÁÎÁ ÎÅËÏÔÏÒÁÑ ÒÁÂÏÔÁ ÐÏ ÉÚÏÌÑÃÉÉ ÓÔÒÕËÔÕÒÙ
-	    device_t.</para>
-	</listitem>
-
-	<listitem>
-	  <para>Pipes: ÚÁ×ÅÒÛÅÎÏ</para>
-	</listitem>
-
-	<listitem>
-	  <para>æÁÊÌÏ×ÙÅ ÄÅÓËÒÉÐÔÏÒÙ: ÚÁ×ÅÒÛÅÎÏ.</para>
-	</listitem>
-
-	<listitem>
-	  <para>Process accounting: jails, credentials, MAC labels É
-	    ÐÌÁÎÉÒÏ×ÝÉË ÎÅ ÉÓÐÏÌØÚÕÀÔ Giant.</para>
-	</listitem>
-
-	<listitem>
-	  <para>ôÅÈÎÏÌÏÇÉÑ MAC: ÚÁ×ÅÒÛÅÎÏ</para>
-	</listitem>
-
-	<listitem>
-	  <para>Timekeeping: ÚÁ×ÅÒÛÅÎÏ</para>
-	</listitem>
-
-	<listitem>
-	  <para>Kernel encryption: ËÒÉÐÔÏÇÒÁÆÉÞÅÓËÉÅ ÄÒÁÊ×ÅÒÙ É ÑÄÒÏ ÔÅÈÎÏÌÏÇÉÉ
-	    &man.crypto.4; ÎÅ ÉÓÐÏÌØÚÕÀÔ Giant.  KAME IPsec ÎÅ
-	    ÏÔÄÅÌÑÀÔÓÑ.</para>
-	</listitem>
-
-	<listitem>
-	  <para>áÕÄÉÏ-ÐÏÄÓÉÓÔÅÍÁ: ÚÁ×ÅÒÛÅÎÏ, ÏÄÎÁËÏ ÏÓÔÁÀÔÓÑ ÐÒÏÂÌÅÍÙ Ó
-	    ÏÂÒÁÔÎÙÍ ÐÏÒÑÄËÏÍ ÉÚÏÌÑÃÉÊ.</para>
-	</listitem>
-
-	<listitem>
-	  <para>÷ÙÔÅÓÎÑÅÍÏÓÔØ ÑÄÒÁ: ×ËÌÀÞÅÎÁ ×ÙÔÅÓÎÑÅÍÏÓÔØ ÄÌÑ ÐÏÔÏËÏ×
-	    ×ÙÐÏÌÎÅÎÉÑ ÐÒÅÒÙ×ÁÎÉÊ.  ïÄÎÁËÏ ÎÅÓÏÇÌÁÓÏ×ÁÎÎÏÓÔØ ÉÚ-ÚÁ ÔÏÇÏ, ÞÔÏ
-	    Giant ÉÓÐÏÌØÚÕÅÔÓÑ × ÂÏÌØÛÉÎÓÔ×Å ËÏÄÁ ÑÄÒÁ É ÐÏÄÐÒÏÇÒÁÍÍÁÈ
-	    ÏÂÒÁÂÏÔËÉ ÐÒÅÒÙ×ÁÎÉÊ ÄÒÁÊ×ÅÒÏ× ÕÓÔÒÏÊÓÔ×, ×ÙÚÙ×ÁÅÔ ÍÎÏÖÅÓÔ×Ï
-	    ÌÉÛÎÉÈ ÐÅÒÅËÌÀÞÅÎÉÊ ËÏÎÔÅËÓÔÁ É ÍÏÖÅÔ ÓËÁÚÁÔØÓÑ ÎÁ
-	    ÐÒÏÉÚ×ÏÄÉÔÅÌØÎÏÓÔÉ.  ÷ÅÄ£ÔÓÑ ÒÁÂÏÔÁ ÐÏ ×ÙÑÓÎÅÎÉÀ ÔÏÇÏ, ËÁË ÓÄÅÌÁÔØ
-	    ×ÙÔÅÓÎÑÅÍÏÓÔØ ÕÓÌÏ×ÎÏÊ.</para>
-	</listitem>
-      </itemizedlist>
-    </sect2>
-
-    <sect2 id="interrupts">
-      <title>úÁÄÅÒÖËÉ ÎÁ ÐÒÅÒÙ×ÁÎÉÑ É ÉÈ ÏÂÒÁÂÏÔËÁ</title>
-
-      <para>÷ SMPng ÐÏÑ×ÉÌÁÓØ ËÏÎÃÅÐÃÉÑ ×ÙÄÅÌÅÎÎÙÈ ÐÏÔÏËÏ× ×ÙÐÏÌÎÅÎÉÑ ÑÄÒÁ,
-	ÉÚ×ÅÓÔÎÙÈ ÐÏÄ ÎÁÚ×ÁÎÉÅÍ ithreads, ÄÌÑ ÏÂÓÌÕÖÉ×ÁÎÉÑ ÐÒÅÒÙ×ÁÎÉÊ.  ó ÎÉÍÉ
-	ÐÏÄÐÒÏÇÒÁÍÍÙ ÏÂÓÌÕÖÉ×ÁÎÉÑ ÐÒÅÒÙ×ÁÎÉÊ ÏÔ ÕÓÔÒÏÊÓÔ× ÍÏÇÕÔ ÓÏÚÄÁ×ÁÔØ
-	ÂÌÏËÉÒÏ×ËÉ ÄÌÑ ×ÙÓÔÁ×ÌÅÎÉÑ ÓÅÍÁÆÏÒÏ×, ×ÙÄÅÌÅÎÉÑ ÐÁÍÑÔÉ É ÔÁË ÄÁÌÅÅ.
-	èÏÔÑ ÜÔÏ ÏÂÌÅÇÞÁÅÔ ÎÁÐÉÓÁÎÉÅ ÄÒÁÊ×ÅÒÏ×, ÐÒÉ ÜÔÏÍ ÐÏÎÉÖÁÅÔÓÑ
-	ÒÅÁËÔÉ×ÎÏÓÔØ ÓÉÓÔÅÍÙ ÉÚ-ÚÁ ÐÏÌÎÏÇÏ ÐÅÒÅËÌÀÞÅÎÉÑ ËÏÎÔÅËÓÔÁ ÐÒÏÃÅÓÓÁ,
-	ËÏÔÏÒÏÅ ÄÏÌÖÎÏ ÂÙÔØ ×ÙÐÏÌÎÅÎÏ ÄÌÑ ÏÂÓÌÕÖÉ×ÁÎÉÑ ithread.  üÔÏ
-	ÕÓÕÇÕÂÌÑÅÔÓÑ ÚÎÁÞÉÔÅÌØÎÙÍ ÉÓÐÏÌØÚÏ×ÁÎÉÅÍ ÑÄÒÏÍ ÓÅÍÁÆÏÒÁ Giant, É ÞÁÓÔÏ
-	ÐÒÉ×ÏÄÉÔ Ë ÍÎÏÖÅÓÔ×Õ ÐÁÕÚ É ÐÅÒÅËÌÀÞÅÎÉÊ ËÏÎÔÅËÓÔÏ× ÄÌÑ ÏÂÓÌÕÖÉ×ÁÎÉÑ
-	ÐÒÅÒÙ×ÁÎÉÑ.  äÒÁÊ×ÅÒÙ, ËÏÔÏÒÙÅ ÚÁÒÅÇÉÓÔÒÉÒÏ×ÁÌÉ Ó×ÏÉ ÐÒÅÒÙ×ÁÎÉÑ ËÁË
-	INTR_MPSAFE, ÍÅÎØÛÅ ×ÓÅÇÏ ÐÏÞÕ×ÓÔ×ÕÀÔ ÜÔÏÔ ÜÆÆÅËÔ, ÏÄÎÁËÏ ÐÏÔÅÒÉ ÎÁ
-	ÐÅÒÅËÌÀÞÅÎÉÅ ËÏÎÔÅËÓÔÁ ÏÓÔÁÎÕÔÓÑ.  ðÏÄÐÒÏÇÒÁÍÍÙ ÏÂÓÌÕÖÉ×ÁÎÉÑ
-	ÐÒÅÒÙ×ÁÎÉÊ, ÚÁÒÅÇÉÓÔÒÉÒÏ×ÁÎÎÙÅ ËÁË INTR_FAST, ÒÁÂÏÔÁÀÔ ÎÅÐÏÓÒÅÄÓÔ×ÅÎÎÏ
-	ÉÚ ËÏÎÔÅËÓÔÁ ÐÒÅÒÙ×ÁÎÉÑ, É ÎÁ ÎÉÈ ×Ï×ÓÅ ÎÅ ÓËÁÚÙ×ÁÀÔÓÑ ÜÔÉ ÐÒÏÂÌÅÍÙ.
-	ïÄÎÁËÏ ÕËÁÚÁÎÉÅ Ó×ÏÊÓÔ×Á INTR_FAST ÚÁÓÔÁ×ÌÑÅÔ ÌÉÎÉÀ ÐÒÅÒÙ×ÁÎÉÊ ÓÔÁÔØ
-	ÜËÓËÌÀÚÉ×ÎÏÊ; Å£ ÎÅÌØÚÑ ÉÓÐÏÌØÚÏ×ÁÔØ ÏÄÎÏ×ÒÅÍÅÎÎÏ Ó ÞÅÍ-ÔÏ.  âÏÌØÛÏÅ
-	ËÏÌÉÞÅÓÔ×Ï ÓÏ×ÍÅÓÔÎÏ ÉÓÐÏÌØÚÕÅÍÙÈ ÐÒÅÒÙ×ÁÎÉÊ ÎÁ PC-ÓÉÓÔÅÍÁÈ ÄÅÌÁÅÔ ÜÔÏ
-	ÎÅÖÅÌÁÔÅÌØÎÙÍ.</para>
-
-      <para>äÌÑ ÐÏÍÏÝÉ × ÒÅÛÅÎÉÉ ÜÔÏÊ ÐÒÏÂÌÅÍÙ ÂÙÌÉ ÐÒÅÄÌÏÖÅÎÙ ÎÅÓËÏÌØËÏ
-	ÉÄÅÊ:</para>
-
-      <itemizedlist>
-	<listitem>
-	  <para>ëÁË ×ÁÒÉÁÎÔ &mdash; ÚÁÄÅÊÓÔ×Ï×ÁÔØ ÏÓÏÂÙÊ ×ÉÄ ÌÅÇËÏ×ÅÓÎÙÈ
-	    ithread.  üÔÏ ÍÏÇÌÏ ÂÙ ÐÒÉ×ÅÓÔÉ Ë ÕÍÅÎØÛÅÎÉÀ ËÏÌÉÞÅÓÔ×Á ÓÏÈÒÁÎÑÅÍÙÈ
-	    ËÏÎÔÅËÓÔÏ× ÄÌÑ ithread, Ë ÚÁÉÍÓÔ×Ï×ÁÎÉÀ ÓÔÅËÁ ÉÚ ÄÒÕÇÏÇÏ kthread
-	    É/ÉÌÉ Ë ÓÏÚÄÁÎÉÀ ÎÏ×ÏÇÏ ÂÙÓÔÒÏÇÏ ÐÕÔÉ, ÉÓËÌÀÞÁÀÝÅÇÏ ×ÙÚÏ×
-	    mi_switch().</para>
-	</listitem>
-
-	<listitem>
-	  <para>íÏÖÎÏ ××ÅÓÔÉ ÎÏ×ÕÀ ÍÏÄÅÌØ ÏÂÒÁÂÏÔËÉ ÐÒÅÒÙ×ÁÎÉÊ, ËÏÔÏÒÁÑ
-	    ÐÏÚ×ÏÌÉÔ ÄÒÁÊ×ÅÒÁÍ ÒÅÇÉÓÔÒÉÒÏ×ÁÔØ 'ÆÉÌØÔÒ ÐÒÅÒÙ×ÁÎÉÊ' ×ÍÅÓÔÅ Ó
-	    ÏÂÙÞÎÏÊ ÐÒÏÃÅÄÕÒÏÊ ÏÂÒÁÂÏÔËÉ.  üÔÏ ÂÕÄÅÔ ÐÏÈÏÖÅ ÎÁ ÍÏÄÅÌØ,
-	    ÉÓÐÏÌØÚÕÅÍÕÀ ÓÅÊÞÁÓ × Mac OS X.  ðÒÏÃÅÄÕÒÙ ÆÉÌØÔÒÁÃÉÉ ÐÒÅÒÙ×ÁÎÉÊ
-	    ÐÏÚ×ÏÌÑÔ ÄÒÁÊ×ÅÒÕ ÏÐÒÅÄÅÌÑÔØ, ÄÏÌÖÅÎ ÌÉ ÏÎ ÕÞÁÓÔ×Ï×ÁÔØ × ÏÂÒÁÂÏÔËÅ
-	    ÐÒÅÒÙ×ÁÎÉÑ, ÐÏÚ×ÏÌÑÔ ÅÍÕ ÐÏÄÁ×ÌÑÔØ ÉÓÔÏÞÎÉË ÐÒÅÒÙ×ÁÎÉÊ É, ×ÏÚÍÏÖÎÏ,
-	    ÏÐÒÅÄÅÌÑÔØ É ÐÌÁÎÉÒÏ×ÁÔØ ÄÅÊÓÔ×ÉÑ ÐÏ ÅÇÏ ÏÂÒÁÂÏÔËÅ.  ïÎÁ ÂÕÄÅÔ
-	    ÒÁÂÏÔÁÔØ × ÔÏÍ ÖÅ ÓÁÍÏÍ ËÏÎÔÅËÓÔÅ, ÞÔÏ É ÎÉÚËÏÕÒÏ×ÎÅ×ÁÑ ÐÒÏÃÅÄÕÒÁ
-	    ÏÂÓÌÕÖÉ×ÁÎÉÑ ÐÒÅÒÙ×ÁÎÉÑ, ÔÁË ÞÔÏ ÐÁÕÚÙ ÂÕÄÕÔ Ö£ÓÔËÏ ÚÁÐÒÅÝÅÎÙ.
-	    åÓÌÉ ÔÒÅÂÕÀÔÓÑ ÄÅÊÓÔ×ÉÑ, ËÏÔÏÒÙÅ ÐÒÉ×ÏÄÑÔ Ë ÐÁÕÚÁÍ ÉÌÉ ÂÌÏËÉÒÏ×ËÅ
-	    ÎÁ ÄÏÌÇÉÊ ÐÅÒÉÏÄ, ÆÉÌØÔÒ ÂÕÄÕÔ ÓÉÇÎÁÌÉÚÉÒÏ×ÁÔØ Ï ÜÔÏÍ ×ÙÚÙ×ÁÀÝÅÊ
-	    ÓÔÏÒÏÎÅ, ÞÔÏ ÄÏÌÖÎÁ ÂÙÔØ ÚÁÐÌÁÎÉÒÏ×ÁÎÁ ÏÂÙÞÎÁÑ
-	    ithread-ÐÒÏÃÅÄÕÒÁ.</para>
-	</listitem>
-      </itemizedlist>
-    </sect2>
-
-    <sect2 id="KSE">
-      <title>ðÏÔÏËÉ ÐÒÉÌÏÖÅÎÉÊ, ÐÏÄÄÅÒÖÉ×ÁÅÍÙÅ ÑÄÒÏÍ</title>
-
-      <para>÷ ÐÒÏÃÅÓÓÅ ÒÁÂÏÔÙ ÎÁÄ FreeBSD 5.1 ÐÁËÅÔ KSE ÂÙÌ ÄÏ×ÅģΠÄÏ ×ÅÓØÍÁ
-	ÐÒÉÇÏÄÎÏÇÏ Ë ÉÓÐÏÌØÚÏ×ÁÎÉÀ ÓÏÓÔÏÑÎÉÑ.  ôÁËÖÅ ÐÏÑ×ÉÌÓÑ THR,
-	ÁÌØÔÅÒÎÁÔÉ×ÎÙÊ ÐÁËÅÔ ÐÏ ÕÐÒÁ×ÌÅÎÉÀ ÐÏÔÏËÁÍÉ ×ÙÐÏÌÎÅÎÉÑ, ÏÓÎÏ×ÁÎÎÙÊ ÎÁ
-	ÎÅËÏÔÏÒÙÈ ÐÒÉÍÉÔÉ×ÁÈ KSE ÕÒÏ×ÎÑ ÑÄÒÁ, ÎÏ ÒÅÁÌÉÚÕÀÝÉÊ ÉÓËÌÀÞÉÔÅÌØÎÏ
-	ÐÏÄÈÏÄ ÐÌÁÎÉÒÏ×ÁÎÉÑ ÚÁÄÁÞ 1:1, ÔÁËÖÅ ÎÁÈÏÄÉÔÓÑ × ÐÏÄÏÂÎÏÍ
-	ÜËÓÐÅÒÉÍÅÎÔÁÌØÎÏÍ, ÎÏ ÐÒÉÇÏÄÎÏÍ Ë ÒÁÂÏÔÅ ÓÏÓÔÏÑÎÉÉ.  ðÏÌØÚÏ×ÁÔÅÌÉ ÍÏÇÕÔ
-	ÍÅÎÑÔØ ÜÔÉ Ä×Å ÂÉÂÌÉÏÔÅËÉ ÓÏ ÓÔÁÒÏÊ ÂÉÂÌÉÏÔÅËÏÊ libc_r ÐÏÓÒÅÄÓÔ×ÏÍ
-	ÐÅÒÅËÏÍÐÏÎÏ×ËÉ Ó×ÏÉÈ ÐÒÉÌÏÖÅÎÉÊ ÉÌÉ ÐÒÉ ÐÏÍÏÝÉ ÎÏ×ÏÊ ÔÅÈÎÉËÉ libmap
-	ËÏÍÐÏÎÏ×ÝÉËÁ ×ÒÅÍÅÎÉ ×ÙÐÏÌÎÅÎÉÑ.  ôÁËÏÊ ÚÎÁÞÉÔÅÌØÎÙÊ ÐÒÏÇÒÅÓÓ × ÈÏÄÅ
-	ÒÁÂÏÔ ÄÏÌÖÅÎ ÐÒÉ×ÅÓÔÉ Ë ÉÈ ÚÁ×ÅÒÛÅÎÉÀ ÄÏ ÍÏÍÅÎÔÁ ÐÏÑ×ÌÅÎÉÑ ×ÅÔËÉ
-	&t.releng.5;, ÔÁË ÞÔÏ ÐÁËÅÔ libc_r ÍÏÖÅÔ ÏËÁÚÁÔØÓÑ ÎÅÎÕÖÎÙÍ.</para>
-
-      <itemizedlist>
-	<listitem>
-	  <para>ëÏÍÐÏÎÅÎÔÙ ÕÒÏ×ÎÑ ÑÄÒÁ É ÐÏÌØÚÏ×ÁÔÅÌØÓËÏÇÏ ÕÒÏ×ÎÑ ÄÌÑ KSE É THR
-	    ÄÏÌÖÎÙ ÂÙÔØ ÓÏÚÄÁÎÙ ÄÌÑ ×ÓÅÈ ÐÌÁÔÆÏÒÍ ÕÒÏ×ÎÑ Tier-1.  òÅÛÅÎÉÅ Ï ÔÏÍ,
-	    ËÁËÏÊ ÐÁËÅÔ ÒÅÁÌÉÚÁÃÉÉ ÐÏÔÏËÏ× ×ÙÐÏÌÎÅÎÉÑ ÂÕÄÅÔ ÉÓÐÏÌØÚÏ×ÁÔØÓÑ ÐÏ
-	    ÕÍÏÌÞÁÎÉÀ, ÂÕÄÅÔ, ÓËÏÒÅÅ ×ÓÅÇÏ, ÐÒÉÎÉÍÁÔØÓÑ ÄÌÑ ËÁÖÄÏÊ ÐÌÁÔÆÏÒÍÙ
-	    ÏÔÄÅÌØÎÏ, × ÚÁ×ÉÓÉÍÏÓÔÉ ÏÔ ÓÔÁÂÉÌØÎÏÓÔÉ É ÚÁ×ÅÒÛ£ÎÎÏÓÔÉ ËÁÖÄÏÇÏ
-	    ÐÁËÅÔÁ.</para>
-
-	  <para>
-	    <table id="KSETable">
-	      <title>óÏÓÔÏÑÎÉÅ KSE</title>
-
-	      <tgroup cols="4">
-		<thead>
-		  <row>
-		    <entry>ðÌÁÔÆÏÒÍÁ</entry>
-
-		    <entry>õÒÏ×ÅÎØ ÑÄÒÏ</entry>
-
-		    <entry>ðÏÌØÚÏ×ÁÔÅÌØÓËÉÊ ÕÒÏ×ÅÎØ</entry>
-
-		    <entry>òÁÂÏÔÁÅÔ?</entry>
-		  </row>
-		</thead>
-
-		<tbody>
-		  <row>
-		    <entry>i386</entry>
-
-		    <entry>äá</entry>
-
-		    <entry>äá</entry>
-
-		    <entry>äá</entry>
-		  </row>
-
-		  <row>
-		    <entry>alpha</entry>
-
-		    <entry>îåô</entry>
-
-		    <entry>äá</entry>
-
-		    <entry>îåô</entry>
-		  </row>
-
-		  <row>
-		    <entry>sparc64</entry>
-
-		    <entry>äá</entry>
-
-		    <entry>îåô</entry>
-
-		    <entry>îåô</entry>
-		  </row>
-
-		  <row>
-		    <entry>ia64</entry>
-
-		    <entry>äá</entry>
-
-		    <entry>äá</entry>
-
-		    <entry>äá</entry>
-		  </row>
-
-		  <row>
-		    <entry>amd64</entry>
-
-		    <entry>äá</entry>
-
-		    <entry>äá</entry>
-
-		    <entry>äá</entry>
-		  </row>
-		</tbody>
-	      </tgroup>
-	    </table>
-
-	    <table id="THRTable">
-	      <title>óÏÓÔÏÑÎÉÅ THR</title>
-
-	      <tgroup cols="4">
-		<thead>
-		  <row>
-		    <entry>ðÌÁÔÆÏÒÍÁ</entry>
-
-		    <entry>õÒÏ×ÅÎØ ÑÄÒÁ</entry>
-
-		    <entry>ðÏÌØÚÏ×ÁÔÅÌØÓËÉÊ ÕÒÏ×ÅÎØ</entry>
-
-		    <entry>òÁÂÏÔÁÅÔ?</entry>
-		  </row>
-		</thead>
-
-		<tbody>
-		  <row>
-		    <entry>i386</entry>
-
-		    <entry>äá</entry>
-
-		    <entry>äá</entry>
-
-		    <entry>äá</entry>
-		  </row>
-
-		  <row>
-		    <entry>alpha</entry>
-
-		    <entry>äá</entry>
-
-		    <entry>äá</entry>
-
-		    <entry>äá</entry>
-		  </row>
-
-		  <row>
-		    <entry>sparc64</entry>
-
-		    <entry>äá</entry>
-
-		    <entry>äá</entry>
-
-		    <entry>îåô</entry>
-		  </row>
-
-		  <row>
-		    <entry>ia64</entry>
-
-		    <entry>äá</entry>
-
-		    <entry>äá</entry>
-
-		    <entry>äá</entry>
-		  </row>
-
-		  <row>
-		    <entry>amd64</entry>
-
-		    <entry>îåô</entry>
-
-		    <entry>îåô</entry>
-
-		    <entry>îåô</entry>
-		  </row>
-		</tbody>
-	      </tgroup>
-	    </table>
-	  </para>
-	</listitem>
-
-	<listitem>
-	  <para>KSE ÄÏÌÖÅÎ ÐÒÏÊÔÉ ÎÁÂÏÒ ÔÅÓÔÏ× ACE ÎÁ ×ÓÅÈ ÐÌÁÔÆÏÒÍÁÈ ÓÔÁÔÕÓÁ
-	    Tier-1.  þÔÏÂÙ ÕÂÅÄÉÔØÓÑ × ÔÏÍ, ÞÔÏ ×ÓÅ ÂÉÂÌÉÏÔÅËÉ ÎÁ ÓÁÍÏÍ ÄÅÌÅ
-	    ÒÁÂÏÔÏÓÐÏÓÏÂÎÙ, ÎÅÏÂÈÏÄÉÍÏ ×ÙÐÏÌÎÉÔØ ÄÏÐÏÌÎÉÔÅÌØÎÏÅ ÔÅÓÔÉÒÏ×ÁÎÉÅ
-	    ÎÁ ÒÅÁÌØÎÙÈ ÚÁÄÁÞÁÈ.  ëÁË ÍÉÎÉÍÕÍ, ÄÏÌÖÎÙ ÂÙÔØ ÐÒÏÔÅÓÔÉÒÏ×ÁÎÙ
-	    ÓÌÅÄÕÀÝÉÅ ÐÁËÅÔÙ:</para>
-
-	  <itemizedlist>
-	    <listitem><para>OpenOffice</para></listitem>
-
-	    <listitem><para>KDE Desktop</para></listitem>
-
-	    <listitem><para>Apache 2.x</para></listitem>
-
-	    <listitem><para>BIND 9.2.x</para></listitem>
-
-	    <listitem><para>MySQL</para></listitem>
-
-	    <listitem><para>&java; 1.4.x</para></listitem>
-	  </itemizedlist>
-	</listitem>
-      </itemizedlist>
-    </sect2>
-  </sect1>
-
-  <sect1 id="goals">
-    <title>ôÒÅÂÏ×ÁÎÉÑ Ë 5-STABLE</title>
-
-    <para>÷ÅÔËÁ &t.releng.5; ÄÏÌÖÎÁ ÄÁÔØ ÐÏÌØÚÏ×ÁÔÅÌÑÍ ÔÁËÕÀ ÖÅ ÓÔÁÂÉÌØÎÏÓÔØ É
-      ÐÒÏÉÚ×ÏÄÉÔÅÌØÎÏÓÔØ, ËÏÔÏÒÁÑ ÓÅÊÞÁÓ ÄÏÓÔÉÇÎÕÔÁ × ×ÅÔËÅ &t.releng.4;.  èÏÔÑ
-      ÃÅÌØÀ ÒÁÂÏÔ ÎÁÄ SMPng Ñ×ÌÑÅÔÓÑ ÚÎÁÞÉÔÅÌØÎÏÅ ÐÏ×ÙÛÅÎÉÅ ÐÒÏÉÚ×ÏÄÉÔÅÌØÎÏÓÔÉ
-      ÐÏ ÓÒÁ×ÎÅÎÉÀ Ó ÉÍÅÀÝÅÊÓÑ × &t.releng.4; É ÒÏÄÓÔ×ÅÎÎÙÈ ×ÁÒÉÁÎÔÁÈ BSD,
-      ÐÏÌÕÞÅÎÉÅ ÈÏÔÑ ÂÙ ÒÁÎÅÅ ÄÏÓÔÉÇÎÕÔÏÊ ÐÒÏÉÚ×ÏÄÉÔÅÌØÎÏÓÔÉ Ñ×ÌÑÅÔÓÑ ÓÁÍÏÊ
-      ×ÁÖÎÏÊ ÚÁÄÁÞÅÊ.  ÷ÅÔËÁ ÄÏÌÖÎÁ ÂÙÔØ ÄÏÓÔÁÔÏÞÎÏ ÇÏÔÏ×ÏÊ, ÞÔÏÂÙ ÉÚÂÅÖÁÔØ
-      ÉÚÍÅÎÅÎÉÊ × ABI É API, ÎÏ ÐÏÚ×ÏÌÑÔØ ÒÅÛÁÔØ ÐÏÔÅÎÃÉÁÌØÎÙÅ ÐÒÏÂÌÅÍÙ.</para>
-
-    <sect2 id="API">
-      <title>óÔÁÂÉÌØÎÏÓÔØ ABI/API/ÉÎÆÒÁÓÔÒÕËÔÕÒÙ</title>
-
-      <para>éÎÆÒÁÓÔÒÕËÔÕÒÁ ÄÏÌÖÎÁ ÂÙÔØ ÄÏÓÔÁÔÏÞÎÏ ÐÏÄÇÏÔÏ×ÌÅÎÎÏÊ É ÕÓÔÏÑ×ÛÅÊÓÑ,
-	ÞÔÏÂÙ ÉÓÐÒÁ×ÌÅÎÉÑ ÉÚ ×ÅÔËÉ &t.releng.head; ÍÏÖÎÏ ÂÙÌÏ ÌÅÇËÏ É
-	ÂÅÚÂÏÌÅÚÎÅÎÎÏ ÐÅÒÅÎÏÓÉÔØ × &t.releng.5;.  ëÒÏÍÅ ÔÏÇÏ, ÍÙ ÄÏÌÖÎÙ
-	ÏÐÒÅÄÅÌÉÔØÓÑ, ËÁËÉÅ ÐÏÄÓÉÓÔÅÍÙ ÄÏÌÖÎÙ ÒÁÂÏÔÁÔØ Ó ÂÌÏËÉÒÏ×ËÁÍÉ ÐÒÉ
-	ÐÅÒÅÈÏÄÅ Ë 5-STABLE.</para>
-
-      <itemizedlist>
-	<listitem>
-	  <para>KSE: É ËÏÍÐÏÎÅÎÔÙ ÕÒÏ×ÎÑ ÑÄÒÁ, É ËÏÍÐÏÎÅÎÔÙ ÐÏÌØÚÏ×ÁÔÅÌØÓËÏÇÏ
-	    ÕÒÏ×ÎÑ ÄÏÌÖÎÙ ÄÏÓÔÉÞØ ÏÄÉÎÁËÏ×ÏÇÏ ÕÒÏ×ÎÑ ÆÕÎËÃÉÏÎÁÌØÎÏÓÔÉ ×Ï ×ÓÅÈ
-	    ÐÌÁÔÆÏÒÍÁÈ ÕÒÏ×ÎÑ Tier-1 × UP É SMP ËÏÎÆÉÇÕÒÁÃÉÑÈ.  ïÐÒÅÄÅÌÅÎÉÅ
-	    ÔÏÇÏ, ÞÔÏ Ñ×ÌÑÅÔÓÑ <quote>ÐÌÁÔÆÏÒÍÁÍÉ ÒÁÎÇÁ Tier-1</quote>, ÍÏÖÎÏ
-	    ÎÁÊÔÉ × <ulink
-	    url="&url.articles.committers-guide;/archs.html"></ulink>.  ðÒÉ
-	    ÐÒÉÂÌÉÖÅÎÉÉ Ë ×ÙÐÕÓËÕ ×ÅÔËÉ &t.releng.5; ÄÏÌÖÎÏ
-	    ÐÒÏÄÏÌÖÉÔØÓÑ ÔÅÓÔÉÒÏ×ÁÎÉÅ ÎÁ ÐÁËÅÔÅ ÔÅÓÔÏ× ACE.  ÷ KSE ÎÅ ÄÏÌÖÎÏ
-	    ÄÏÐÕÓËÁÔØÓÑ ÕÍÅÎØÛÅÎÉÅ ÆÕÎËÃÉÏÎÁÌØÎÏÓÔÉ ÄÌÑ ÂÕÄÕÝÅÊ ÐÒÏÇÒÁÍÍÙ
-	    ÓÅÒÔÉÆÉËÁÃÉÉ &java;.  òÁÓÐÒÏÓÔÒÁΣÎÎÙÅ ÐÒÉËÌÁÄÎÙÅ É ÓÅÒ×ÅÒÎÙÅ
-	    ÐÒÉÌÏÖÅÎÉÑ ÄÏÌÖÎÙ ÒÁÂÏÔÁÔØ × KSE ÂÅÚ ÐÒÏÂÌÅÍ.  äÏÌÖÎÁ ÂÙÔØ
-	    ÏÐÒÅÄÅÌÅÎÁ ÐÏÌÉÔÉËÁ ÏÔÎÏÓÉÔÅÌØÎÏ ÔÏÇÏ, ÎÁ ËÁËÉÈ ÐÌÁÔÆÏÒÍÁÈ KSE
-	    ÂÕÄÅÔ ÉÓÐÏÌØÚÏ×ÁÔØÓÑ × ËÁÞÅÓÔ×Å ÓÔÁÎÄÁÒÔÎÏÇÏ ÐÁËÅÔÁ ÄÌÑ ÏÒÇÁÎÉÚÁÃÉÉ
-	    ÐÏÔÏËÏ× ×ÙÐÏÌÎÅÎÉÑ, ËÁË ÐÏÌØÚÏ×ÁÔÅÌØ ÍÏÖÅÔ ÐÅÒÅËÌÀÞÁÔØÓÑ ÍÅÖÄÕ
-	    ÔÁËÉÍÉ ÐÁËÅÔÁÍÉ É ËÁË ÐÁËÅÔÙ ÓÔÏÒÏÎÎÉÈ ÒÁÚÒÁÂÏÔÞÉËÏ× ÄÏÌÖÎÙ
-	    ÏÔÓÌÅÖÉ×ÁÔØ ÔÁËÉÅ ÉÚÍÅÎÅÎÉÑ.</para>
-	</listitem>
-
-	<listitem>
-	  <para>éÎÔÅÒÆÅÊÓ É ÄÒÁÊ×ÅÒÙ busdma: ÔÁËÉÅ ÁÒÈÉÔÅËÔÕÒÙ, ËÁË PAE/&i386;
-	    É sparc64, × ËÏÔÏÒÙÈ ÏÔÓÕÔÓÔ×ÕÅÔ ÐÒÑÍÏÅ ÏÔÏÂÒÁÖÅÎÉÅ ÁÄÒÅÓÎÏÇÏ
-	    ÐÒÏÓÔÒÁÎÓÔ×Á ÈÏÓÔÁ × ÁÄÒÅÓÎÏÅ ÐÒÏÓÔÒÁÎÓÔ×Ï ÐÌÁÔ ÒÁÓÛÉÒÅÎÉÑ, ÔÒÅÂÕÀÔ
-	    ÉÓËÌÀÞÅÎÉÑ ÆÕÎËÃÉÉ vtophys() É ÅÊ ÐÏÄÏÂÎÙÈ.  éÎÔÅÒÆÅÊÓ busdma ÂÙÌ
-	    ÓÏÚÄÁÌ ÄÌÑ ÒÅÛÅÎÉÑ ÉÍÅÎÎÏ ÜÔÏÊ ÐÒÏÂÌÅÍÙ, ÏÄÎÁËÏ ÍÎÏÇÉÅ ÄÒÁÊ×ÅÒÙ
-	    ÅÇÏ ÅÝ£ ÎÅ ÉÓÐÏÌØÚÕÀÔ.  ðÒÏÅËÔ busdma ÎÁ ÓÔÒÁÎÉÃÅ <ulink
-	    url="&url.base;/projects/busdma"></ulink> ÏÔÓÌÅÖÉ×ÁÅÔ
-	    ÈÏÄ ÜÔÉÈ ÒÁÂÏÔ É ÜÔÏ ÍÏÖÎÏ ÉÓÐÏÌØÚÏ×ÁÔØ ÄÌÑ ÏÐÒÅÄÅÌÅÎÉÑ ÔÏÇÏ, ËÁËÉÅ
-	    ÄÒÁÊ×ÅÒÙ ÄÏÌÖÎÙ ÂÙÔØ ÐÒÅÏÂÒÁÚÏ×ÁÎÙ ÄÌÑ &t.releng.5;, Á ËÁËÉÅ ÍÏÖÎÏ
-	    ÏÓÔÁ×ÉÔØ.  ÷ ÄÅÒÅ×Å ÉÓÈÏÄÎÙÈ ÔÅËÓÔÏ× &os; ÎÅ ÄÏÌÖÎÏ ÂÙÔØ ÎÏ×ÙÈ
-	    ÄÒÁÊ×ÅÒÏ× ÄÌÑ ÕÓÔÒÏÊÓÔ× ÈÒÁÎÅÎÉÑ ÉÌÉ ÓÅÔÅ×ÙÈ ÄÒÁÊ×ÅÒÏ×.  éÓËÌÀÞÅÎÉÑ
-	    ÄÌÑ ÄÒÕÇÉÈ ËÌÁÓÓÏ× ÄÒÁÊ×ÅÒÏ× ÎÕÖÎÏ ÓÏÇÌÁÓÏ×Ù×ÁÔØ × ÏÔËÒÙÔÏÍ
-	    ÏÂÓÕÖÄÅÎÉÉ.</para>
-	</listitem>
-
-	<listitem>
-	  <para>òÁÓÐÒÅÄÅÌÅÎÉÅ ÒÅÓÕÒÓÏ× PCI: ÓÏÏÔ×ÅÔÓÔ×ÉÅ ÓÐÅÃÉÆÉËÁÃÉÉ PC2003
-	    ÔÒÅÂÕÅÔ, ÞÔÏ ÓÉÓÔÅÍÙ x86 ÎÅ ËÏÎÆÉÇÕÒÉÒÏ×ÁÌÉ ÕÓÔÒÏÊÓÔ×Á PCI ÉÚ
-	    ÓÉÓÔÅÍÎÏÊ BIOS, ÏÓÔÁ×ÌÑÑ ÜÔÕ ÚÁÄÁÞÕ ÉÓËÌÀÞÉÔÅÌØÎÏ ïó.  ÷Ï &os;
-	    ÄÏÌÖÎÁ ÐÏÑ×ÉÔØÓÑ ×ÏÚÍÏÖÎÏÓÔØ ÕÐÒÁ×ÌÅÎÉÑ É ÒÁÓÐÒÅÄÅÌÅÎÉÑ ÒÅÓÕÒÓÏ×
-	    ÐÁÍÑÔÉ PCI Ó×ÏÉÍÉ ÓÉÌÁÍÉ.  òÅÁÌÉÚÁÃÉÑ ÜÔÏÇÏ ÄÏÌÖÎÁ ÐÒÉÎÑÔØ ×Ï
-	    ×ÎÉÍÁÎÉÅ ÓÕÝÅÓÔ×Ï×ÁÎÉÅ ÔÒÅÂÏ×ÁÎÉÊ cardbus, PCI-HotPlug É ÄÏËÏ× ÄÌÑ
-	    ÌÜÐÔÏÐÏ×.  üÔÁ ×ÏÚÍÏÖÎÏÓÔØ ÓÔÁÎÅÔ ÅÝ£ ÂÏÌÅÅ ËÒÉÔÉÞÎÏÊ × ÔÅÞÅÎÉÅ
-	    ÖÉÚÎÉ ×ÅÔËÉ &t.releng.5;, É ÐÏÜÔÏÍÕ Ñ×ÌÑÅÔÓÑ ÔÒÅÂÏ×ÁÎÉÅÍ Ë ×ÙÐÕÓËÕ
-	    &t.releng.5;.</para>
-	</listitem>
-      </itemizedlist>
-    </sect2>
-
-    <sect2 id="performance">
-      <title>ðÒÏÉÚ×ÏÄÉÔÅÌØÎÏÓÔØ</title>
-
-      <para>ðÒÏÉÚ×ÏÄÉÔÅÌØÎÏÓÔØ ÚÁ×ÉÓÉÔ ÏÔ ÈÏÄÁ ÒÁÂÏÔ ÎÁÄ ÉÎÆÒÁÓÔÒÕËÔÕÒÏÊ SMPng
-	× ÓÌÅÄÕÀÝÉÈ ÏÂÌÁÓÔÑÈ:</para>
-
-      <itemizedlist>
-	<listitem>
-	  <para>õÓÔÒÏÊÓÔ×Á ÈÒÁÎÅÎÉÑ: ÔÅÈÎÏÌÏÇÉÑ GEOM ÐÏÚ×ÏÌÑÅÔ ÄÒÁÊ×ÅÒÁÍ
-	    ÕÓÔÒÏÊÓÔ× ÈÒÁÎÅÎÉÑ ÒÁÂÏÔÁÔØ ÂÅÚ ÉÓÐÏÌØÚÏ×ÁÎÉÑ Giant.  ÷ÓÅ ÄÒÁÊ×ÅÒÙ,
-	    ËÏÔÏÒÙÅ ×ÚÁÉÍÏÄÅÊÓÔ×ÕÀÔ ÎÁÐÒÑÍÕÀ Ó GEOM (× ÐÒÏÔÉ×ÏÐÏÌÏÖÎÏÓÔØ ÔÅÍ,
-	    ÞÔÏ ÎÁÈÏÄÑÔÓÑ ÎÉÖÅ ÕÒÏ×ÎÑ CAM ÉÌÉ ÄÒÕÇÏÇÏ ÐÒÏÍÅÖÕÔÏÞÎÏÇÏ ÓÌÏÑ),
-	    ÄÏÌÖÎÙ ÉÚÏÌÉÒÏ×ÁÔØÓÑ É ÉÚÂÁ×ÌÑÔØÓÑ ÏÔ ÉÓÐÏÌØÚÏ×ÁÎÉÑ Giant ËÁË ×
-	    ÞÁÓÔÉ strategy, ÔÁË É completion.  éÈ ÏÂÒÁÂÏÔÞÉËÉ ÐÒÅÒÙ×ÁÎÉÊ ÔÁËÖÅ
-	    ÄÏÌÖÎÙ ÉÚÂÁ×ÉÔØÓÑ ÏÔ Giant.</para>
-	</listitem>
-
-	<listitem>
-	  <para>óÅÔØ: ÕÒÏ×ÎÉ × ÒÁÂÏÔÅ IPv4, ÌÅÖÁÝÉÅ ÎÉÖÅ ÕÒÏ×ÎÑ ÓÏËÅÔÏ×, ÄÏÌÖÎÙ
-	    ÂÙÔØ ÉÚÏÌÉÒÏ×ÁÎÎÙÍÉ É ÎÅ ÉÓÐÏÌØÚÏ×ÁÔØ Giant.  óÀÄÁ ×ËÌÀÞÁÅÔÓÑ
-	    ÐÒÏÔÏËÏÌ, ÍÁÒÛÒÕÔÉÚÁÃÉÑ, ÏÒÇÁÎÉÚÁÃÉÑ ÍÏÓÔÁ, ÆÉÌØÔÒÁÃÉÑ É ÁÐÐÁÒÁÔÎÙÊ
-	    ÕÒÏ×ÅÎØ.  óËÉÄËÉ ÄÏÌÖÎÙ ÂÙÔØ ÓÄÅÌÁÎÙ ÄÌÑ ÐÒÏÔÏËÏÌÏ×, ËÏÔÏÒÙÅ ÎÅ
-	    ÉÚÏÌÉÒÕÀÔÓÑ, ÏÓÏÂÅÎÎÏ IPv6.  äÌÑ ÄÏÓÔÉÖÅÎÉÑ ÓÔÁÂÉÌØÎÏÓÔÉ,
-	    ËÏÒÒÅËÔÎÏÓÔÉ É ÐÒÏÉÚ×ÏÄÉÔÅÌØÎÏÓÔÉ ÔÁËÖÅ ÎÅÏÂÈÏÄÉÍÏ ×ÙÐÏÌÎÉÔØ
-	    ÔÅÓÔÉÒÏ×ÁÎÉÅ.</para>
-	</listitem>
-
-	<listitem>
-	  <para>ðÒÅÒÙ×ÁÎÉÑ É ÐÅÒÅËÌÀÞÅÎÉÅ ËÏÎÔÅËÓÔÏ×: ËÁË ÏÂÓÕÖÄÁÌÏÓØ ×ÙÛÅ,
-	    ÚÁÄÅÒÖËÉ × ÐÒÅÒÙ×ÁÎÉÑÈ É ÐÅÒÅËÌÀÞÅÎÉÑÈ ËÏÎÔÅËÓÔÏ× ÉÍÅÀÔ ÂÏÌØÛÏÅ
-	    ×ÌÉÑÎÉÅ ÎÁ ÐÒÏÉÚ×ÏÄÉÔÅÌØÎÏÓÔØ.  ðÅÒÅËÌÀÞÅÎÉÅ ËÏÎÔÅËÓÔÏ× ÄÌÑ ithread
-	    É kthread ÎÁ ×ÓÅÈ ÐÌÁÔÆÏÒÍÁÈ ÄÏÌÖÎÏ ÂÙÔØ ÕÌÕÞÛÅÎÏ.  äÏÌÖÎÁ ÂÙÔØ
-	    ÉÓÓÌÅÄÏ×ÁÎÁ É ÒÅÁÌÉÚÏ×ÁÎÁ ×ÏÚÍÏÖÎÏÓÔØ ÓÏÚÄÁÎÉÑ ÎÏ×ÏÊ ÍÏÄÅÌÉ
-	    ÏÂÒÁÂÏÔËÉ ÐÒÅÒÙ×ÁÎÉÊ, ËÏÔÏÒÁÑ ÐÏÚ×ÏÌÑÅÔ ×ÙÐÏÌÎÑÔØ ÂÏÌÅÅ ÂÙÓÔÒÕÀ É
-	    ÇÉÂËÕÀ ÏÂÒÁÂÏÔËÕ ËÁË ÏÂÙÞÎÙÈ, ÔÁË É MSI ÐÒÅÒÙ×ÁÎÉÊ.</para>
-	</listitem>
-      </itemizedlist>
-    </sect2>
-
-    <sect2 id="benchmarks">
-      <title>óÔÁÎÄÁÒÔÎÙÅ ÔÅÓÔÙ É ÔÅÓÔÉÒÏ×ÁÎÉÅ ÐÒÏÉÚ×ÏÄÉÔÅÌØÎÏÓÔÉ</title>
-
-      <para>äÌÑ ×ÙÑ×ÌÅÎÉÑ ÐÒÏÂÌÅÍ Ó ÐÒÏÉÚ×ÏÄÉÔÅÌØÎÏÓÔØÀ É ÂÏÒØÂÙ Ó Å£
-	ÕÈÕÄÛÅÎÉÅÍ ÎÅÏÂÈÏÄÉÍÏ ÉÎÆÏÒÍÁÔÉ×ÎÏÅ É ÎÁÄ£ÖÎÏÅ ÐÒÏ×ÅÄÅÎÉÅ ÔÅÓÔÏ×.
-	÷ÓËÏÒÅ ÄÏÌÖÎÁ ÂÙÔØ ÓÆÏÒÍÉÒÏ×ÁÎÁ <quote>ÇÒÕÐÐÁ
-	ÐÒÏÉÚ×ÏÄÉÔÅÌØÎÏÓÔÉ</quote> ÉÚ ÌÀÄÅÊ É ÒÅÓÕÒÓÏ× ÄÌÑ ÆÏÒÍÕÌÉÒÏ×ÁÎÉÑ,
-	ÒÁÚÒÁÂÏÔËÉ É ×ÙÐÏÌÎÅÎÉÑ ÓÔÁÎÄÁÒÔÎÙÈ ÔÅÓÔÏ× ÐÒÏÉÚ×ÏÄÉÔÅÌØÎÏÓÔÉ.
-	óÒÁ×ÎÅÎÉÑ ÄÏÌÖÎÙ ÄÅÌÁÔØÓÑ ËÁË Ó &os; 4.<replaceable>X</replaceable>,
-	ÔÁË É Linux 2.4/2.6.  ðÒÅÄÐÏÌÁÇÁÀÔÓÑ ÓÌÅÄÕÀÝÉÅ ÔÅÓÔÙ:</para>
-
-      <itemizedlist>
-	<listitem>
-	  <para>ËÌÁÓÓÉÞÅÓËÉÊ <quote>worldstone</quote></para>
-	</listitem>
-
-	<listitem>
-	  <para>webstone: <filename
-	    role="package">www/webstone</filename></para>
-	</listitem>
-
-	<listitem>
-	  <para>Fstress: <ulink
-	    url="http://www.cs.duke.edu/ari/fstress/"></ulink></para>
-	</listitem>
-
-	<listitem>
-	  <para>ApacheBench: <filename
-	    role="package">www/p5-ApacheBench</filename></para>
-	</listitem>
-
-	<listitem>
-	  <para>netperf: <filename
-	    role="package">benchmarks/netperf</filename></para>
-	</listitem>
-
-	<listitem>
-	  <para>Web Polygraph: <ulink
-	    url="http://www.web-polygraph.org/"></ulink>  úÁÍÅÞÁÎÉÅ: ÐÏËÁ ÎÅ
-	    ËÏÍÐÉÌÉÒÕÅÔÓÑ Ó gcc 3.x.</para>
-	</listitem>
-      </itemizedlist>
-    </sect2>
-
-    <sect2 id="features">
-      <title>ïÓÏÂÙÅ ×ÏÚÍÏÖÎÏÓÔÉ:</title>
-
-      <itemizedlist>
-	<listitem>
-	  <para>NEWCARD/OLDCARD: ÐÏÄÓÉÓÔÅÍÁ NEWCARD ×Ï &os;&nbsp;5.0 ÓÄÅÌÁÎÁ
-	    ÉÓÐÏÌØÚÕÅÍÏÊ ÐÏ ÕÍÏÌÞÁÎÉÀ.  ë ÓÏÖÁÌÅÎÉÀ, × ÎÅÊ ÏÔÓÕÔÓÔ×ÕÅÔ
-	    ÐÏÄÄÅÒÖËÁ ÄÌÑ ÎÅ-Cardbus ÍÏÓÔÏ× É ÎÁ ÎÅËÏÔÏÒÙÈ ÌÜÐÔÏÐÁÈ ÏÎÁ
-	    ÎÅ ÒÁÂÏÔÁÅÔ ÉÚ-ÚÁ ÐÒÏÂÌÅÍ Ó ÍÁÒÛÒÕÔÉÚÁÃÉÅÊ ÐÒÅÒÙ×ÁÎÉÊ.
-	    ëÌÁÓÓÉÞÅÓËÁÑ ÒÅÁÌÉÚÁÃÉÉ ÐÏÄÄÅÒÖËÉ 16-ÂÉÔÎÙÈ ÍÏÓÔÏ×, OLDCARD,
-	    ÐÒÏÄÏÌÖÁÅÔ ÓÕÝÅÓÔ×Ï×ÁÔØ É ÍÏÖÅÔ ÂÙÔØ ×ËÏÍÐÉÌÉÒÏ×ÁÎÁ, ÏÄÎÁËÏ ÜÔÏ
-	    ÎÅÕÄÏÂÎÏ ÄÌÑ ÐÏÌØÚÏ×ÁÔÅÌÅÊ ÓÔÁÒÙÈ ÌÜÐÔÏÐÏ×.  åÓÌÉ ÏÔ OLDCARD
-	    ÄÌÑ &t.releng.5; ÎÅÌØÚÑ ÂÕÄÅÔ ÐÏÌÎÏÓÔØÀ ÏÔËÁÚÁÔØÓÑ, ÔÏ ÄÏÌÖÎÙ ÂÙÔØ
-	    ÓÄÅÌÁÎÙ ÛÁÇÉ, ËÏÔÏÒÙÅ ÐÏÚ×ÏÌÑÔ ÐÏÌØÚÏ×ÁÔÅÌÑÍ ÌÅÇËÏ ÕÓÔÁÎÁ×ÌÉ×ÁÔØ
-	    ÑÄÒÏ Ó ÐÏÄÄÅÒÖËÏÊ OLDCARD.  äÏÌÖÎÁ ÂÙÔØ ÎÁÐÉÓÁÎÁ ÄÏËÕÍÅÎÔÁÃÉÑ ×
-	    ÐÏÍÏÝØ ÐÏÌØÚÏ×ÁÔÅÌÑÍ ÐÏ ÐÅÒÅÈÏÄÕ ÏÔ OLDCARD Ë NEWCARD É ÏÔ
-	    &man.pccardd.8; Ë &man.devd.8;.  æÕÎËÃÉÏÎÁÌØÎÏÓÔØ ÐÏ ÕÐÒÁ×ÌÅÎÉÀ
-	    ÜÌÅËÔÒÏÐÉÔÁÎÉÅÍ É <quote>dumpcis</quote> ÕÔÉÌÉÔÙ &man.pccardc.8;
-	    ÄÏÌÖÎÁ ÂÙÔØ ÕÓÉÌÅÎÁ ÐÏÄÄÅÒÖËÏÊ NEWCARD, Á ÔÁËÖÅ ×ÏÚÍÏÖÎÏÓÔØÀ
-	    ÐÏÄÇÒÕÖÁÔØ ÉÎÆÏÒÍÁÃÉÀ Ï ÎÅÓÔÁÎÄÁÒÔÎÏÍ ÏÂÏÒÕÄÏ×ÁÎÉÉ CIS.  ïÓÎÏ×ÎÏÊ
-	    ÏÂß£Í ÜÔÉÈ ÆÕÎËÃÉÊ ÍÏÖÅÔ ÂÙÔØ ÉÎÔÅÇÒÉÒÏ×ÁÎ × &man.devd.8; É
-	    &man.devctl.4;.</para>
-	</listitem>
-
-	<listitem>
-	  <para>îÏ×ÙÊ ÐÌÁÎÉÒÏ×ÝÉË ÚÁÄÁÞ: ÏÎ ÕÖÅ ÇÏÔÏ×, É ÐÏÌØÚÏ×ÁÔÅÌÉ ÍÏÇÕÔ
-	    ×ÙÂÉÒÁÔØ ÍÅÖÄÕ ËÌÁÓÓÉÞÅÓËÉÍ ÐÌÁÎÉÒÏ×ÝÉËÏÍ 4BSD É ÎÏ×ÙÍ
-	    ÐÌÁÎÉÒÏ×ÝÉËÏÍ ULE.  ÷ ×ÅÔËÅ &t.releng.5; ÄÏÌÖÅÎ ÂÙÔØ ÐÌÁÎÉÒÏ×ÝÉË,
-	    ÉÍÅÀÝÉÊ ÐÒÉ×ÑÚËÕ Ë ÐÒÏÃÅÓÓÏÒÕ, ÐÏÄÄÅÒÖËÕ HyperThreading É KSE,
-	    Á ÔÁËÖÅ ÏÔÓÕÔÓÔ×ÉÅ ÓÎÉÖÅÎÉÑ ÐÒÏÉÚ×ÏÄÉÔÅÌØÎÏÓÔÉ ÉÌÉ ×ÒÅÍÅÎÉ ÒÅÁËÃÉÉ
-	    ÓÉÓÔÅÍÙ.</para>
-	</listitem>
-
-	<listitem>
-	   <para>GDB: GDB × ÏÓÎÏ×ÎÏÍ ÓÉÓÔÅÍÎÏÍ ÎÁÂÏÒÅ ÄÏÌÖÅÎ ÒÁÂÏÔÁÔØ ÓÏ
-	     sparc64, Á ÔÁËÖÅ ÐÏÎÉÍÁÔØ ÐÏÔÏËÉ KSE.  õÖÅ ÉÍÅÅÔÓÑ GDB 5.3,
-	     ÓÏÏÂÝÁÅÔÓÑ, ÞÔÏ ÏÎ ÒÅÛÁÅÔ ÐÒÏÂÌÅÍÙ ÓÏ sparc64.</para>
-	</listitem>
-      </itemizedlist>
-    </sect2>
-
-    <sect2 id="documentation">
-      <title>äÏËÕÍÅÎÔÁÃÉÑ:</title>
-
-      <itemizedlist>
-	<listitem>
-	  <para>óÐÒÁ×ÏÞÎÙÅ ÓÔÒÁÎÉÃÙ, òÕËÏ×ÏÄÓÔ×Ï É FAQ ÄÏÌÖÎÙ ÂÙÔØ ÏÞÉÝÅÎÙ ÏÔ
-	    ÓÏÄÅÒÖÉÍÏÇÏ, ÓÐÅÃÉÆÉÞÎÏÇÏ ÄÌÑ &os; 4.<replaceable>X</replaceable>,
-	    ÔÏ ÅÓÔØ ×ÅÓØ ÔÅËÓÔ ÄÏÌÖÅÎ ÐÏÄÈÏÄÉÔØ É ÄÌÑ &os;
-	    5.<replaceable>X</replaceable>.  âÏÌØÛÅ ×ÓÅÇÏ ÒÁÂÏÔÙ ÚÄÅÓØ
-	    ÐÒÅÄÓÔÏÉÔ ÓÄÅÌÁÔØ × ÒÁÚÄÅÌÅ òÕËÏ×ÏÄÓÔ×Á ÐÏ ÕÓÔÁÎÏ×ËÅ.</para>
-	</listitem>
-
-	<listitem>
-	  <para>äÏËÕÍÅÎÔÁÃÉÑ Ë ÒÅÌÉÚÕ ÄÏÌÖÎÁ ÂÙÔØ ÐÏÌÎÏÊ É ÔÏÞÎÏÊ ÄÌÑ ×ÓÅÈ
-	    ÁÒÈÉÔÅËÔÕÒ ÕÒÏ×ÎÑ Tier-1.  ïÓÏÂÏÇÏ ×ÎÉÍÁÎÉÑ ÔÒÅÂÕÀÔ ÚÁÍÅÞÁÎÉÑ ÐÏ
-	    ÏÂÏÒÕÄÏ×ÁÎÉÀ É ÉÎÓÔÒÕËÃÉÉ ÐÏ ÕÓÔÁÎÏ×ËÅ.</para>
-	</listitem>
-      </itemizedlist>
-    </sect2>
-  </sect1>
-
-  <sect1 id="future">
-    <title>îÁÐÒÁ×ÌÅÎÉÅ ÒÁÂÏÔ ÐÏÓÌÅ &t.releng.5;</title>
-
-    <para>ëÁË ÜÔÏ ÐÒÏÉÓÈÏÄÉÔ É Ó ÄÒÕÇÉÍÉ ×ÅÔËÁÍÉ -STABLE, × ÏÓÎÏ×ÎÏÍ ÒÁÂÏÔÁ
-      ÎÁÄ ÎÅÊ ÄÏÌÖÎÁ ÚÁËÌÀÞÁÔØÓÑ × ÉÓÐÒÁ×ÌÅÎÉÉ ÏÛÉÂÏË É ÐÏÓÌÅÄÏ×ÁÔÅÌØÎÏÍ
-      ÕÌÕÞÛÅÎÉÉ.  ëÁË ÏÂÙÞÎÏ, ×Ó£ ÄÏÌÖÎÏ ÐÒÏÈÏÄÉÔØ ÐÒÏ×ÅÒËÕ × ×ÅÔËÅ
-      &t.releng.head;, Á ÚÁÔÅÍ ×ÎÉÍÁÔÅÌØÎÏ ÐÅÒÅÎÏÓÉÔØÓÑ × &t.releng.5;.  îÏ×ÙÅ
-      ÄÒÁÊ×ÅÒÙ ÕÓÔÒÏÊÓÔ×, ÄÏÐÏÌÎÉÔÅÌØÎÙÅ ×ÏÚÍÏÖÎÏÓÔÉ É ÔÏÍÕ ÐÏÄÏÂÎÙÅ ÒÁÚÒÁÂÏÔËÉ
-      ÐÒÉ×ÅÔÓÔ×ÕÀÔÓÑ × ÜÔÏÊ ×ÅÔËÅ ÔÏÌØËÏ ÐÏÓÌÅ ÐÒÏ×ÅÒËÉ
-      × &t.releng.head;.</para>
-
-    <para>äÁÌØÎÅÊÛÁÑ ÉÚÏÌÑÃÉÑ SMPng ÂÕÄÅÔ ÒÁÚÄÅÌÅÎÁ ÎÁ Ä×Å ËÁÔÅÇÏÒÉÉ, ÄÒÁÊ×ÅÒ É
-      ÐÏÄÓÉÓÔÅÍÁ.  åÄÉÎÓÔ×ÅÎÎÏÊ ÐÏÄÓÉÓÔÅÍÏÊ, ËÏÔÏÒÁÑ ÂÕÄÅÔ ÄÏÓÔÁÔÏÞÎÏ
-      ÉÚÏÌÉÒÏ×ÁÎÎÏÊ Ë ×ÙÈÏÄÕ &t.releng.5;, ÂÕÄÅÔ GEOM, ÔÁË ÞÔÏ ÐÏÓÔÅÐÅÎÎÏÅ
-      ÉÚÏÌÉÒÏ×ÁÎÉÅ ÄÒÁÊ×ÅÒÏ× ÕÓÔÒÏÊÓÔ× ÐÏÄ Å£ ÕÐÒÁ×ÌÅÎÉÅÍ Ñ×ÌÑÅÔÓÑ ÄÏÓÔÏÊÎÏÊ
-      ÚÁÄÁÞÅÊ ÜÔÏÊ ×ÅÔËÉ.  ðÏÌÎÁÑ ÉÚÏÌÑÃÉÑ ÐÏÄÓÉÓÔÅÍÙ ÂÕÄÅÔ ×ÙÐÏÌÎÅÎÁ É
-      ÏÐÒÏÂÏ×ÁÎÁ × ×ÅÔËÅ &t.releng.head; ÄÏ ÔÏÇÏ, ËÁË ÂÕÄÅÔ ÐÒÉÎÑÔÏ ÒÅÛÅÎÉÅ
-      Ï ÐÅÒÅÎÏÓŠţ × ×ÅÔËÕ &t.releng.5;.</para>
-  </sect1>
-</article>
diff --git a/ru_RU.KOI8-R/articles/5-roadmap/extra.css b/ru_RU.KOI8-R/articles/5-roadmap/extra.css
deleted file mode 100644
index 3884f8cb26..0000000000
--- a/ru_RU.KOI8-R/articles/5-roadmap/extra.css
+++ /dev/null
@@ -1,21 +0,0 @@
-/*
- * The FreeBSD Russian Documentation Project
- *
- * $FreeBSD$
- * $FreeBSDru: frdp/doc/ru_RU.KOI8-R/articles/5-roadmap/extra.css,v 1.1 2004/01/06 18:19:42 andy Exp $
- *
- * Original revision: r16035
- *
- * Netscape 4 does not recognize the @import directive of CSS, so we
- * can't add an additional stylesheet layer on top of the default one.
- * Instead, we use this hack to copy this file to the end of
- * docbook.css. 
- */
-
-/* @import "docbook.css"; */
-
-/* Customization that looks good for this particular article. */
-
-DIV.TITLEPAGE {
-	text-align: center;
-}
diff --git a/ru_RU.KOI8-R/articles/Makefile b/ru_RU.KOI8-R/articles/Makefile
index e554baca50..ede82a5c3f 100644
--- a/ru_RU.KOI8-R/articles/Makefile
+++ b/ru_RU.KOI8-R/articles/Makefile
@@ -8,8 +8,6 @@
 #
 
 SUBDIR =
-SUBDIR+= 5-roadmap
-SUBDIR+= checkpoint
 SUBDIR+= committers-guide
 SUBDIR+= console-server
 SUBDIR+= contributing
@@ -18,25 +16,19 @@ SUBDIR+= cups
 SUBDIR+= custom-gcc
 SUBDIR+= cvs-freebsd
 SUBDIR+= cvsup-advanced
-SUBDIR+= dialup-firewall
-SUBDIR+= diskless-x
-SUBDIR+= euro
 SUBDIR+= explaining-bsd
 SUBDIR+= fbsd-from-scratch
 #SUBDIR+= filtering-bridges
 SUBDIR+= fonts
-SUBDIR+= formatting-media
 SUBDIR+= freebsd-questions
 SUBDIR+= geom-class
 SUBDIR+= gjournal-desktop
-SUBDIR+= hats
 SUBDIR+= hubs
 SUBDIR+= ipsec-must
 SUBDIR+= laptop
 SUBDIR+= linux-comparison
 SUBDIR+= mailing-list-faq
 SUBDIR+= mh
-SUBDIR+= multi-os
 SUBDIR+= new-users
 SUBDIR+= pam
 SUBDIR+= portbuild
@@ -47,11 +39,8 @@ SUBDIR+= releng
 SUBDIR+= releng-packages
 #SUBDIR+= serial-uart
 SUBDIR+= solid-state
-#SUBDIR+= storage-devices
 #SUBDIR+= vinum
-SUBDIR+= version-guide
 SUBDIR+= vm-design
-SUBDIR+= zip-drive
 
 # ROOT_SYMLINKS+= new-users
 
diff --git a/ru_RU.KOI8-R/articles/checkpoint/Makefile b/ru_RU.KOI8-R/articles/checkpoint/Makefile
deleted file mode 100644
index 3a6b2d8686..0000000000
--- a/ru_RU.KOI8-R/articles/checkpoint/Makefile
+++ /dev/null
@@ -1,22 +0,0 @@
-#
-# The FreeBSD Russian Documentation Project
-#
-# $FreeBSD$
-# $FreeBSDru: frdp/doc/ru_RU.KOI8-R/articles/checkpoint/Makefile,v 1.1 2004/01/10 08:43:19 andy Exp $
-#
-# Original revision: r27200
-#
-
-DOC?= article
-
-FORMATS?= html
-
-INSTALL_COMPRESSED?=gz
-INSTALL_ONLY_COMPRESSED?=
-
-SRCS=		article.sgml
-IMAGES_EN=	networks.pic
-
-URL_RELPREFIX?=	../../../..
-DOC_PREFIX?= ${.CURDIR}/../../..
-.include "${DOC_PREFIX}/share/mk/doc.project.mk"
diff --git a/ru_RU.KOI8-R/articles/checkpoint/article.sgml b/ru_RU.KOI8-R/articles/checkpoint/article.sgml
deleted file mode 100644
index 333d5c623f..0000000000
--- a/ru_RU.KOI8-R/articles/checkpoint/article.sgml
+++ /dev/null
@@ -1,450 +0,0 @@
-<?xml version="1.0" encoding="koi8-r" standalone="no"?>
-<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V4.2-Based Extension//EN"
-	"../../../share/sgml/freebsd42.dtd" [
-<!ENTITY % entities PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Entity Set//RU" "../../share/sgml/entities.ent">
-%entities;
-]>
-
-<!--
-     The FreeBSD Russian Documentation Project
-
-     $FreeBSDru: frdp/doc/ru_RU.KOI8-R/articles/checkpoint/article.sgml,v 1.5 2004/07/16 12:05:55 den Exp $
-
-     Original revision: r27201
--->
-
-<!-- Copyright (c) 2001 The FreeBSD Documentation Project
-
-     Redistribution and use in source (SGML DocBook) and 'compiled' forms
-     (SGML, HTML, PDF, PostScript, RTF and so forth) with or without
-     modification, are permitted provided that the following conditions
-     are met:
-
-      1. Redistributions of source code (SGML DocBook) must retain the above
-         copyright notice, this list of conditions and the following
-         disclaimer as the first lines of this file unmodified.
-
-      2. Redistributions in compiled form (transformed to other DTDs,
-         converted to PDF, PostScript, RTF and other formats) 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 DOCUMENTATION IS PROVIDED BY THE FREEBSD DOCUMENTATION PROJECT "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 NIK CLAYTON 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 DOCUMENTATION, EVEN IF ADVISED OF THE
-     POSSIBILITY OF SUCH DAMAGE.
--->
-
-<article lang="ru">
-  <articleinfo>
-    <title>éÎÔÅÇÒÁÃÉÑ FreeBSD IPsec É Check Point <trademark
-      class='registered'>VPN-1</trademark>/<trademark
-      class='registered'>Firewall-1</trademark></title>
-
-    <authorgroup>
-      <author>
-	<firstname>Jon</firstname>
-
-	<surname>Orbeton</surname>
-
-	<affiliation>
-	  <address><email>jono@securityreports.com</email></address>
-	</affiliation>
-      </author>
-
-      <author>
-	<firstname>Matt</firstname>
-
-	<surname>Hite</surname>
-
-	<affiliation>
-	  <address><email>mhite@hotmail.com</email></address>
-	</affiliation>
-      </author>
-    </authorgroup>
-
-    <copyright>
-      <year>2001</year>
-      <year>2002</year>
-      <year>2003</year>
-
-      <holder role="mailto:jono@securityreports.com">Jon Orbeton</holder>
-    </copyright>
-
-    &legalnotice;
-
-    <legalnotice id="trademarks" role="trademarks">
-      &tm-attrib.freebsd;
-      &tm-attrib.check-point;
-      &tm-attrib.general;
-    </legalnotice>
-
-    <pubdate>$FreeBSD$</pubdate>
-
-    <releaseinfo>$FreeBSD$</releaseinfo>
-
-    <abstract>
-      <para>÷ ÜÔÏÍ ÄÏËÕÍÅÎÔÅ ÏÐÉÓÙ×ÁÅÔÓÑ, ËÁË ÎÁÓÔÒÏÉÔØ
-	<acronym>VPN</acronym>-ÔÕÎÎÅÌÉÒÏ×ÁÎÉÅ ÍÅÖÄÕ FreeBSD É
-	<trademark class='registered'>VPN-1</trademark>/
-	<trademark class='registered'>Firewall-1</trademark> ËÏÍÐÁÎÉÉ
-	Check Point.  ÷ ÄÒÕÇÉÈ ÉÍÅÀÝÉÈÓÑ ÐÕÂÌÉËÁÃÉÑÈ ÄÁ£ÔÓÑ ÔÁËÁÑ ÉÎÆÏÒÍÁÃÉÑ,
-	ÎÏ × ÎÅÊ ÎÅ ÓÏÄÅÒÖÁÔÓÑ ÉÎÓÔÒÕËÃÉÉ, ÓÐÅÃÉÆÉÞÎÙÅ ÄÌÑ VPN-1/Firewall-1 É
-	ÅÇÏ ÉÎÔÅÇÒÁÃÉÉ Ó FreeBSD.  ïÎÉ ÐÅÒÅÞÉÓÌÅÎÙ × ÚÁ×ÅÒÛÁÀÝÅÊ ÞÁÓÔÉ ÜÔÏÊ
-	ÒÁÂÏÔÙ ÄÌÑ ÄÁÌØÎÅÊÛÅÇÏ ÉÚÕÞÅÎÉÑ.</para>
-    </abstract>
-  </articleinfo>
-
-  <sect1 id="prerequisites">
-    <title>éÓÈÏÄÎÙÅ ÄÁÎÎÙÅ</title>
-
-    <para>äÁÌÅÅ ÐÏËÁÚÁÎÁ ÓÈÅÍÁ ÒÁÓÐÏÌÏÖÅÎÉÑ ÍÁÛÉÎ É ÓÅÔÅÊ, Ï ËÏÔÏÒÙÈ ÉÄ£Ô ÒÅÞØ
-      × ÜÔÏÍ ÄÏËÕÍÅÎÔÅ.</para>
-
-    <mediaobject>
-      <imageobject>
-	<imagedata fileref="networks"/>
-      </imageobject>
-
-      <textobject>
-	<literallayout class="monospaced">         ÷ÎÅÛÎÉÊ ÉÎÔÅÒÆÅÊÓ                ÷ÎÅÛÎÉÊ ÉÎÔÅÒÆÅÊÓ
-           208.229.100.6                    216.218.197.2
-                       |                    |
-         +--&gt; Firewall-1 &lt;--&gt; Internet &lt;--&gt; FreeBSD GW &lt;--+
-         |                                                |
-óÅÔÉ ÐÏÄ ÚÁÝÉÔÏÊ FW-1                              ÷ÎÕÔÒÅÎÎÉÅ ÓÅÔÉ
-199.208.192.0/24                               192.168.10.0/24</literallayout>
-      </textobject>
-
-      <textobject>
-	<phrase>óÅÔØ FW-1 É ÓÅÔØ FreeBSD</phrase>
-      </textobject>
-    </mediaobject>
-
-    <para>ûÌÀÚ <acronym>GW</acronym> ÎÁ ÏÓÎÏ×Å FreeBSD ×ÙÓÔÕÐÁÅÔ × ËÁÞÅÓÔ×Å
-      ÍÅÖÓÅÔÅ×ÏÇÏ ÜËÒÁÎÁ É <acronym>NAT</acronym>-ÕÓÔÒÏÊÓÔ×Á ÄÌÑ
-      <quote>×ÎÕÔÒÅÎÎÉÈ ÓÅÔÅÊ.</quote></para>
-
-    <para>ñÄÒÏ FreeBSD ÄÏÌÖÎÏ ÂÙÔØ ÐÏÓÔÒÏÅÎÏ Ó ÐÏÄÄÅÒÖËÏÊ IPsec.  äÌÑ ×ËÌÀÞÅÎÉÑ
-      IPsec × ×ÁÛÅÍ ÑÄÒÅ ÉÓÐÏÌØÚÕÊÔÅ ÓÌÅÄÕÀÝÉÅ ÐÁÒÁÍÅÔÒÙ ÑÄÒÁ:</para>
-
-    <programlisting>options         IPSEC
-options         IPSEC_ESP
-options         IPSEC_DEBUG</programlisting>
-
-    <para>äÌÑ ÐÏÌÕÞÅÎÉÑ ÉÎÆÏÒÍÁÃÉÉ ÐÏ ÐÏÓÔÒÏÅÎÉÀ ÎÅÓÔÁÎÄÁÒÔÎÏÇÏ ÑÄÒÁ,
-      ÏÂÒÁÔÉÔÅÓØ Ë <ulink url="&url.books.handbook;/kernelconfig.html">
-      òÕËÏ×ÏÄÓÔ×Õ ÐÏ FreeBSD</ulink>.  ðÏÖÁÌÕÊÓÔÁ, ÚÁÍÅÔØÔÅ, ÞÔÏ ÍÅÖÄÕ ÈÏÓÔÁÍÉ
-      <trademark class='registered'>Firewall-1</trademark> É
-      <acronym>GW</acronym> Ó FreeBSD ÄÏÌÖÎÙ ÂÙÔØ ÒÁÚÒÅÛÅÎÙ ÓÏÅÄÉÎÅÎÉÑ
-      <acronym>IP</acronym> protocol&nbsp;50 (<acronym>ESP</acronym>) É
-      <acronym>UDP</acronym> port&nbsp;<literal>500</literal>.</para>
-
-    <para>ëÒÏÍÅ ÔÏÇÏ, ÄÌÑ ÐÏÄÄÅÒÖËÉ ÏÂÍÅÎÁ ËÌÀÞÁÍÉ ÄÏÌÖÅÎ ÂÙÔØ ÕÓÔÁÎÏ×ÌÅÎ
-      ÐÁËÅÔ <application>racoon</application>.
-      <application>Racoon</application> Ñ×ÌÑÅÔÓÑ ÞÁÓÔØÀ ËÏÌÌÅËÃÉÉ ÐÏÒÔÏ×
-      FreeBSD É ÎÁÈÏÄÉÔÓÑ × ÐÁËÁÄÖÅ <filename
-      role="package">security/racoon</filename>.  æÁÊÌ ËÏÎÆÉÇÕÒÁÃÉÉ
-      <application>racoon</application> ÂÕÄÅÔ ÏÐÉÓÁÎ ÎÉÖÅ × ÜÔÏÍ
-      ÄÏËÕÍÅÎÔÅ.</para>
-  </sect1>
-
-  <sect1 id="object">
-    <title>îÁÓÔÒÏÊËÁ ÓÅÔÅ×ÙÈ ÏÂßÅËÔÏ× × Firewall-1</title>
-
-    <para>îÁÞÎÉÔÅ Ó ÎÁÓÔÒÏÊËÉ ÐÏÌÉÔÉËÉ Firewall-1.  ïÔËÒÏÊÔÅ ÒÅÄÁËÔÏÒ ÐÏÌÉÔÉË
-      Policy Editor ÎÁ ÓÅÒ×ÅÒÅ ÕÐÒÁ×ÌÅÎÉÑ Firewall-1 É ÓÏÚÄÁÊÔÅ ÎÏ×ÙÊ ÓÅÔÅ×ÏÊ
-      ÏÂßÅËÔ (Network Object) ÔÉÐÁ <quote>Workstation</quote>, ËÏÔÏÒÙÊ ÂÕÄÅÔ
-      ÐÒÅÄÓÔÁ×ÌÑÔØ ÍÁÛÉÎÕ <acronym>GW</acronym> Ó FreeBSD.</para>
-
-   <programlisting>General Tab:
-		Set name and IP address
-
-VPN Tab:
-		Encryption Schemes Defined:             IKE               ---&gt; Edit
-
-IKE Properties:
-		Key Negotiation Encryption Methods:     3DES
-
-Authentication Method:
-		Pre-Shared Secret ---&gt; Edit</programlisting>
-
-    <para>÷ÙÂÅÒÉÔÅ Firewall Object É ÕÓÔÁÎÏ×ÉÔÅ ÚÁÒÁÎÅÅ ÉÚ×ÅÓÔÎÙÊ ÐÁÒÏÌØ.  (îÅ
-      ÉÓÐÏÌØÚÕÊÔÅ ÅÇÏ ÉÚ ÎÁÛÅÇÏ ÐÒÉÍÅÒÁ.)</para>
-
-    <programlisting>Support Aggressive Mode:                 Checked
-Supports Subnets:                      Checked</programlisting>
-
-    <para>ðÏÓÌÅ ÕÓÔÁÎÏ×ËÉ ÉÚ×ÅÓÔÎÏÇÏ ÐÁÒÏÌÑ × ÏÐÒÅÄÅÌÅÎÉÉ ÓÅÔÅ×ÏÇÏ ÏÂßÅËÔÁ
-      Firewall-1, ÕËÁÖÉÔÅ ÜÔÏÔ ÐÁÒÏÌØ × ÆÁÊÌÅ
-      <filename>/usr/local/etc/racoon/psk.txt</filename> × ÓÉÓÔÅÍÅ FreeBSD ÎÁ
-      <acronym>GW</acronym>.  æÏÒÍÁÔ ÆÁÊÌÁ <filename>psk.txt</filename>
-      ÔÁËÏ×:</para>
-
-    <programlisting>208.229.100.6          rUac0wtoo?</programlisting>
-  </sect1>
-
-  <sect1 id="rulecfg">
-    <title>ëÏÎÆÉÇÕÒÁÃÉÑ VPN-ÐÒÁ×ÉÌÁ × Firewall-1</title>
-
-    <para>ôÅÐÅÒØ ÓÏÚÄÁÊÔÅ × Firewall-1 ÐÒÁ×ÉÌÏ, ×ËÌÀÞÁÀÝÅÅ ÛÉÆÒÏ×ÁÎÉÅ ÍÅÖÄÕ
-      ÍÁÛÉÎÏÊ <acronym>GW</acronym> Ó FreeBSD É ÓÅÔØÀ, ÚÁÝÉÝ£ÎÎÏÊ Firewall-1.
-      ÷ ÜÔÏÍ ÐÒÁ×ÉÌÅ ÄÏÌÖÎÙ ÂÙÔØ ÚÁÄÁÎÙ ÓÅÔÅ×ÙÅ ÓÅÒ×ÉÓÙ, ÒÁÚÒÅÛ£ÎÎÙÅ Ë ÒÁÂÏÔÅ
-      ÞÅÒÅÚ <acronym>VPN</acronym>.</para>
-
-    <programlisting>Source            | Destination        | Service      | Action  | Track
-------------------------------------------------------------------------
-FreeBSD GW        | FW-1 Protected Net | VPN services | Encrypt | Long
-FW-1 Protected Net| FreeBSD GW         |              |         |</programlisting>
-
-    <para><quote>VPN-ÓÅÒ×ÉÓÁÍÉ</quote> Ñ×ÌÑÀÔÓÑ ÌÀÂÙÅ ÓÅÒ×ÉÓÙ (ÔÏ ÅÓÔØ
-      <command>telnet</command>, <acronym>SSH</acronym>,
-      <acronym>NTP</acronym> É ÔÁË ÄÁÌÅÅ), Ë ËÏÔÏÒÙÍ ÒÁÚÒÅۣΠÄÏÓÔÕÐ ÕÄÁÌ£ÎÎÏÍÕ
-      ÈÏÓÔÕ ÞÅÒÅÚ <acronym>VPN</acronym>.  âÕÄØÔÅ ×ÎÉÍÁÔÅÌØÎÙ ÐÒÉ ×ËÌÀÞÅÎÉÉ
-      ÓÅÒ×ÉÓÏ×; ÈÏÓÔÙ, ÐÏÄËÌÀÞÁÅÍÙÅ ÞÅÒÅÚ <acronym>VPN</acronym>, ÐÒÏÄÏÌÖÁÀÔ
-      ÐÒÅÄÓÔÁ×ÌÑÔØ ÐÏÔÅÎÃÉÁÌØÎÕÀ ÏÐÁÓÎÏÓÔØ.  ûÉÆÒÏ×ÁÎÉÅ ÔÒÁÆÉËÁ ÍÅÖÄÕ Ä×ÕÍÑ
-      ÓÅÔÑÍÉ ÄÁ£Ô ÓÌÁÂÕÀ ÚÁÝÉÔÕ, ÅÓÌÉ ÌÀÂÏÊ ÉÚ ÈÏÓÔÏ× ÎÁ ÏÂÅÉÈ ÓÔÏÒÏÎÁÈ ÔÕÎÎÅÌÑ
-      ÂÙÌ ×ÚÌÏÍÁÎ.</para>
-
-    <para>ðÏÓÌÅ ÎÁÓÔÒÏÊËÉ ÐÒÁ×ÉÌÁ ÛÉÆÒÏ×ÁÎÉÑ ÄÁÎÎÙÈ ÍÅÖÄÕ ÍÁÛÉÎÏÊ
-      <acronym>GW</acronym> Ó FreeBSD É ÓÅÔØÀ, ÚÁÝÉÝ£ÎÎÏÊ Firewall-1,
-      ÐÒÏÓÍÏÔÒÉÔÅ ÎÁÓÔÒÏÊËÉ <quote>Action Encrypt</quote>.</para>
-
-    <programlisting>Encryption Schemes Defined:     IKE ---&gt; Edit
-Transform:                      Encryption + Data Integrity (ESP)
-Encryption Algorithm:           3DES
-Data Integrity:                 MD5
-Allowed Peer Gateway:           Any or Firewall Object
-Use Perfect Forward Secrecy:    Checked</programlisting>
-
-    <para>éÓÐÏÌØÚÏ×ÁÎÉÅ ÔÅÈÎÏÌÏÇÉÉ Perfect Forward Secrecy
-      (<acronym>PFS</acronym>) Ñ×ÌÑÅÔÓÑ ÎÅÏÂÑÚÁÔÅÌØÎÙÍ.  ÷ËÌÀÞÅÎÉÅ
-      <acronym>PFS</acronym> ÄÏÂÁ×ÉÔ ÅÝ£ ÏÄÉÎ ÕÒÏ×ÅÎØ ÂÅÚÏÐÁÓÎÏÓÔÉ ÎÁ ÕÒÏ×ÎÅ
-      ÛÉÆÒÏ×ÁÎÉÑ ÄÁÎÎÙÈ, ÏÄÎÁËÏ ÐÒÉ×ÅÄ£Ô Ë Õ×ÅÌÉÞÅÎÉÀ ÎÁÇÒÕÚËÉ ÎÁ
-      <acronym>CPU</acronym>.  åÓÌÉ <acronym>PFS</acronym> ÎÅ ÉÓÐÏÌØÚÕÅÔÓÑ,
-      ÔÏ ×ÙËÌÀÞÉÔÅ ÆÌÁÇ ×ÙÛÅ É ÚÁËÏÍÍÅÎÔÉÒÕÊÔÅ ÓÔÒÏÞËÕ
-      <literal>pfs_group&nbsp;1</literal> × ÆÁÊÌÅ
-      <filename>racoon.conf</filename> ÎÁ ÍÁÛÉÎÅ <acronym>GW</acronym> Ó
-      FreeBSD.  ðÒÉÍÅÒ ÆÁÊÌÁ <filename>racoon.conf</filename> ÄÁÎ × ÜÔÏÍ
-      ÄÁÌØÛÅ.</para>
-  </sect1>
-
-  <sect1 id="policy">
-    <title>ëÏÎÆÉÇÕÒÁÃÉÑ ÐÏÌÉÔÉËÉ <acronym>VPN</acronym> ×Ï FreeBSD</title>
-
-    <para>îÁ ÜÔÏÍ ÜÔÁÐÅ ÄÏÌÖÎÁ ÂÙÔØ ÚÁÄÁÎÁ ÐÏÌÉÔÉËÁ <acronym>VPN</acronym> ÎÁ
-      ÍÁÛÉÎÅ <acronym>GW</acronym> Ó FreeBSD.  üÔÕ ÆÕÎËÃÉÀ ×ÙÐÏÌÎÑÅÔ ÕÔÉÌÉÔÁ
-      &man.setkey.8;.</para>
-
-    <para>îÉÖÅ ÄÁ£ÔÓÑ ÐÒÉÍÅÒ ÓËÒÉÐÔÁ ËÏÍÁÎÄÎÏÇÏ ÐÒÏÃÅÓÓÏÒÁ, ËÏÔÏÒÙÊ ÓÂÒÁÓÙ×ÁÅÔ
-      &man.setkey.8; É ÄÏÂÁ×ÌÑÅÔ ×ÁÛÉ ÐÒÁ×ÉÌÁ ÐÏÌÉÔÉËÉ
-      <acronym>VPN</acronym>.</para>
-
-    <programlisting>#
-# /etc/vpn1-ipsec.sh
-#
-# IP addresses
-#
-#     External Interface                    External Interface
-#       208.229.100.6                       216.218.197.2
-#                   |                       |
-#        +--&gt; Firewall-1 &lt;--&gt; Internet &lt;--&gt; FreeBSD GW &lt;--+
-#        |                                                |
-# FW-1 Protected Nets                              Internal Nets
-#    199.208.192.0/24                                  192.168.10.0/24
-#
-# Flush the policy
-#
-setkey -FP
-setkey -F
-#
-# Configure the Policy
-#
-setkey -c &lt;&lt; END
-spdadd 216.218.197.2/32 199.208.192.0/24 any -P out ipsec
-esp/tunnel/216.218.197.2-208.229.100.6/require;
-spdadd 199.208.192.0/24 216.218.197.2/32 any -P in ipsec
-esp/tunnel/208.229.100.6-216.218.197.2/require;
-END
-#</programlisting>
-
-    <para>÷ÙÐÏÌÎÉÔÅ ËÏÍÁÎÄÙ &man.setkey.8;:</para>
-
-    <screen>&prompt.root; <userinput>sh /etc/vpn1-ipsec.sh</userinput></screen>
-  </sect1>
-
-  <sect1 id="racoon">
-    <title>ëÏÎÆÉÇÕÒÁÃÉÑ <application>Racoon</application> ×Ï FreeBSD</title>
-
-    <para>äÌÑ ÏÂÅÓÐÅÞÅÎÉÑ ÓÏÇÌÁÓÏ×ÁÎÉÑ ËÌÀÞÅÊ IPsec ÎÁ ÍÁÛÉÎÅ
-      <acronym>GW</acronym> Ó FreeBSD, ÎÅÏÂÈÏÄÉÍÏ ÕÓÔÁÎÏ×ÉÔØ É ÓËÏÎÆÉÇÕÒÉÒÏ×ÁÔØ
-      ÐÏÒÔ <filename role="package">security/racoon</filename>.</para>
-
-    <para>äÁÌÅÅ ÐÒÉ×ÏÄÉÔÓÑ ÆÁÊÌ ËÏÎÆÉÇÕÒÁÃÉÉ <application>racoon</application>,
-      ËÏÔÏÒÙÊ ÐÏÄÈÏÄÉÔ ÄÌÑ ÉÓÐÏÌØÚÏ×ÁÎÉÑ Ó ÐÒÉÍÅÒÁÍÉ, ÏÐÉÓÁÎÎÙÍÉ × ÜÔÏÍ
-      ÄÏËÕÍÅÎÔÅ.  ðÏÖÁÌÕÊÓÔÁ, ÐÅÒÅÄ ÅÇÏ ÉÓÐÏÌØÚÏ×ÁÎÉÅÍ × ÒÅÁÌØÎÏÊ ÜËÓÐÌÕÁÔÁÃÉÉ
-      ÕÂÅÄÉÔÅÓØ, ÞÔÏ ÐÏÌÎÏÓÔØÀ ÐÏÎÉÍÁÅÔÅ ÅÇÏ ÎÁÚÎÁÞÅÎÉÅ.</para>
-
-    <programlisting># racoon.conf for use with Check Point VPN-1/Firewall-1
-#
-# search this file for pre_shared_key with various ID key.
-#
-        path pre_shared_key "/usr/local/etc/racoon/psk.txt" ;
-        log debug;
-#
-# "padding" defines some parameter of padding.  You should not touch these.
-#
-        padding
-      {
-        maximum_length 20;      # maximum padding length.
-        randomize off;          # enable randomize length.
-        strict_check off;       # enable strict check.
-        exclusive_tail off;     # extract last one octet.
-      }
-
-        listen
-      {
-        #isakmp ::1 [7000];
-        #isakmp 0.0.0.0 [500];
-        #admin [7002];          # administrative port by kmpstat.
-        #strict_address;        # required all addresses must be bound.
-      }
-#
-# Specification of default various timers.
-#
-        timer
-      {
-#
-# These values can be changed per remote node.
-#
-        counter 5;              # maximum trying count to send.
-        interval 20 sec;        # maximum interval to resend.
-        persend 1;              # the number of packets per a send.
-#
-# timer for waiting to complete each phase.
-#
-        phase1 30 sec;
-        phase2 15 sec;
-      }
-
-        remote anonymous
-      {
-        exchange_mode aggressive,main; # For Firewall-1 Aggressive mode
-
-        #my_identifier address;
-        #my_identifier user_fqdn "";
-        #my_identifier address "";
-        #peers_identifier address "";
-        #certificate_type x509 "" "";
-
-        nonce_size 16;
-        lifetime time 10 min;   # sec,min,hour
-        lifetime byte 5 MB;     # B,KB,GB
-        initial_contact on;
-        support_mip6 on;
-        proposal_check obey;    # obey, strict or claim
-
-        proposal {
-                encryption_algorithm 3des;
-                hash_algorithm md5;
-                authentication_method pre_shared_key;
-                dh_group 2 ;
-        }
-      }
-
-        sainfo anonymous
-      {
-        pfs_group 1;
-        lifetime time 10 min;
-        lifetime byte 50000 KB;
-        encryption_algorithm 3des;
-        authentication_algorithm hmac_md5;
-        compression_algorithm deflate ;
-      }</programlisting>
-
-    <para>ðÒÏ×ÅÒØÔÅ, ÞÔÏ ÆÁÊÌ
-      <filename>/usr/local/etc/racoon/psk.txt</filename> ÓÏÄÅÒÖÉÔ ÔÏÔ ÖÅ ÓÁÍÙÊ
-      ÚÁÒÁÎÅÅ ÉÚ×ÅÓÔÎÙÊ ÐÁÒÏÌØ, ÞÔÏ ÎÁÓÔÒÁÉ×ÁÌÓÑ ÐÒÉ ÐÏÍÏÝÉ ÒÁÚÄÅÌÁ
-      <quote>îÁÓÔÒÏÊËÁ ÓÅÔÅ×ÙÈ ÏÂßÅËÔÏ× × Firewall-1</quote> ÜÔÏÇÏ ÄÏËÕÍÅÎÔÁ,
-      É ÉÍÅÅÔ ÒÅÖÉÍ ÄÏÓÔÕÐÁ <literal>600</literal>.</para>
-
-    <screen>&prompt.root; <userinput>chmod 600 /usr/local/etc/racoon/psk.txt</userinput></screen>
-  </sect1>
-
-  <sect1 id="startingvpn">
-    <title>úÁÐÕÓË <acronym>VPN</acronym> × ÒÁÂÏÔÕ</title>
-
-    <para>ôÅÐÅÒØ ×Ù ÇÏÔÏ×Ù Ë ÚÁÐÕÓËÕ <application>racoon</application> É
-      ÔÅÓÔÉÒÏ×ÁÎÉÀ ÔÕÎÎÅÌÑ <acronym>VPN</acronym>.  äÌÑ ÃÅÌÅÊ ÏÔÌÁÄËÉ ÏÔËÒÏÊÔÅ
-      Log Viewer ÎÁ Firewall-1 É ÚÁÄÁÊÔÅ ÆÉÌØÔÒ ÐÒÏÔÏËÏÌÉÒÏ×ÁÎÉÑ ÄÌÑ ×ÙÄÅÌÅÎÉÑ
-      ÚÁÐÉÓÅÊ, ÏÔÎÏÓÑÝÉÈÓÑ Ë ÍÁÛÉÎÅ <acronym>GW</acronym> Ó FreeBSD.  ÷ÁÍ ÍÏÖÅÔ
-      ÔÁËÖÅ ÐÒÉÇÏÄÉÔØÓÑ ÐÒÏÓÍÏÔÒ ÖÕÒÎÁÌÁ <application>racoon</application> ÐÒÉ
-      ÐÏÍÏÝÉ ËÏÍÁÎÄÙ &man.tail.1;:</para>
-
-    <screen>&prompt.root; <userinput>tail -f /var/log/racoon.log</userinput></screen>
-
-    <para>úÁÐÕÓÔÉÔÅ <application>racoon</application> ÐÏÓÒÅÄÓÔ×ÏÍ ÓÌÅÄÕÀÝÅÊ
-      ËÏÍÁÎÄÙ:</para>
-
-    <screen>&prompt.root; <userinput>/usr/local/sbin/racoon -f /usr/local/etc/racoon/racoon.conf</userinput></screen>
-
-    <para>ðÏÓÌÅ ÚÁÐÕÓËÁ <application>racoon</application> ×ÙÐÏÌÎÉÔÅ ÐÏÄËÌÀÞÅÎÉÅ
-      ÐÏ &man.telnet.1; Ë ÈÏÓÔÕ × ÓÅÔÉ, ÚÁÝÉÝ£ÎÎÏÊ Firewall-1.</para>
-
-    <screen>&prompt.root; <userinput>telnet -s 192.168.10.3 199.208.192.66 22</userinput></screen>
-
-    <para>ðÏ ÜÔÏÊ ËÏÍÁÎÄÅ ×ÙÐÏÌÎÑÅÔÓÑ ÐÏÐÙÔËÁ ÐÏÄËÌÀÞÅÎÉÑ Ë &man.ssh.1;-ÐÏÒÔÕ
-      ÍÁÛÉÎÙ <hostid role="ipaddr">199.208.192.66</hostid>, ÔÏÊ, ÞÔÏ ÎÁÈÏÄÉÔÓÑ
-      × ÓÅÔÉ, ÚÁÝÉÝ£ÎÎÏÊ Firewall-1.  ðÁÒÁÍÅÔÒ <option>-s</option> ÚÁÄÁ£Ô
-      ÉÓÐÏÌØÚÕÅÍÙÊ ÉÎÔÅÒÆÅÊÓ × ÉÓÈÏÄÑÝÅÍ ÓÏÅÄÉÎÅÎÉÉ.  üÔÏ, × ÞÁÓÔÎÏÓÔÉ, ×ÁÖÎÏ
-      ÐÒÉ ÉÓÐÏÌØÚÏ×ÁÎÉÉ ÎÁ ÍÁÛÉÎÅ <acronym>GW</acronym> Ó FreeBSD ÔÅÈÎÏÌÏÇÉÊ
-      <acronym>NAT</acronym> É <acronym>IPFW</acronym>.  éÓÐÏÌØÚÏ×ÁÎÉÅ
-      <literal>-s</literal> É Ñ×ÎÏÅ ÚÁÄÁÎÉÅ ÉÓÈÏÄÑÝÅÇÏ ÁÄÒÅÓÁ ÎÅ ÐÏÚ×ÏÌÉÔ
-      <acronym>NAT</acronym> ÐÏÄÍÅÎÑÔØ ÐÁËÅÔÙ ÐÅÒÅÄ ÔÕÎÎÅÌÉÒÏ×ÁÎÉÅÍ.</para>
-
-    <para>ðÒÉ ÕÓÐÅÛÎÏÍ ÏÂÍÅÎÅ ËÌÀÞÁÍÉ <application>racoon</application> ×ÙÄÁÓÔ
-      × ÆÁÊÌ ÐÒÏÔÏËÏÌÁ <filename>racoon.log</filename> ÓÌÅÄÕÀÝÅÅ:</para>
-
-    <programlisting>pfkey UPDATE succeeded: ESP/Tunnel 216.218.197.2->208.229.100.6
-pk_recvupdate(): IPSec-SA established: ESP/Tunnel 216.218.197.2->208.229.100.6
-get pfkey ADD message IPsec-SA established: ESP/Tunnel 208.229.100.6->216.218.197.2</programlisting>
-
-    <para>ðÏÓÌÅ ÔÏÇÏ, ËÁË ÏÂÍÅÎ ËÌÀÞÁÍÉ ÂÕÄÅÔ ÚÁ×ÅÒۣΠ(ÞÔÏ ÚÁÎÉÍÁÅÔ ÎÅÓËÏÌØËÏ
-      ÓÅËÕÎÄ), ÂÕÄÅÔ ×ÙÄÁÎÁ ÚÁÓÔÁ×ËÁ &man.ssh.1;.  åÓÌÉ ×Ó£ ÐÒÏÛÌÏ ÎÏÒÍÁÌØÎÏ,
-      × ÓÒÅÄÓÔ×Å Log Viewer ÎÁ Firewall-1 ÂÕÄÅÔ ÚÁÆÉËÓÉÒÏ×ÁÎÏ Ä×Á ÓÏÏÂÝÅÎÉÑ
-      <quote>Key Install</quote>.</para>
-
-    <programlisting>Action      |  Source        |  Dest.             | Info.
-Key Install |  216.218.197.2 |  208.229.100.6     | IKE Log: Phase 1 (aggressive) completion.
-Key Install |  216.218.197.2 |  208.229.100.6     | scheme: IKE methods</programlisting>
-
-    <para>÷ ÉÎÆÏÒÍÁÃÉÏÎÎÏÊ ËÏÌÏÎËÅ ÐÏÄÒÏÂÎÙÊ ÐÒÏÔÏËÏÌ ÂÕÄÅÔ ×ÙÇÌÑÄÅÔØ
-      ÔÁË:</para>
-
-    <programlisting>IKE Log: Phase 1 (aggressive) completion. 3DES/MD5/Pre shared secrets Negotiation Id:
-scheme: IKE methods: Combined ESP: 3DES + MD5 + PFS (phase 2 completion) for host:</programlisting>
-  </sect1>
-
-  <sect1 id="References">
-    <title>óÓÙÌËÉ</title>
-
-    <itemizedlist>
-      <listitem>
-	<para>òÕËÏ×ÏÄÓÔ×Ï FreeBSD: VPN ÞÅÒÅÚ IPsec <ulink
-	  url="&url.books.handbook;/ipsec.html"></ulink></para>
-      </listitem>
-
-      <listitem>
-	<para>ðÒÏÅËÔ KAME <ulink url="http://www.kame.net"></ulink></para>
-      </listitem>
-    </itemizedlist>
-  </sect1>
-</article>
diff --git a/ru_RU.KOI8-R/articles/dialup-firewall/Makefile b/ru_RU.KOI8-R/articles/dialup-firewall/Makefile
deleted file mode 100644
index 93458eb3a5..0000000000
--- a/ru_RU.KOI8-R/articles/dialup-firewall/Makefile
+++ /dev/null
@@ -1,26 +0,0 @@
-#
-# $FreeBSD$
-# $FreeBSDru: frdp/doc/ru_RU.KOI8-R/articles/dialup-firewall/Makefile,v 1.2 2001/07/25 10:26:31 phantom Exp $
-#
-# Original revision: r7299
-#
-
-MAINTAINER=andy@FreeBSD.org.ua
-
-DOC?= article
-
-FORMATS?= html
-
-INSTALL_COMPRESSED?= gz
-INSTALL_ONLY_COMPRESSED?=
-
-#
-# SRCS lists the individual SGML files that make up the document. Changes
-# to any of these files will force a rebuild
-#
-
-# SGML content
-SRCS=  article.sgml
-
-DOC_PREFIX?= ${.CURDIR}/../../..
-.include "${DOC_PREFIX}/share/mk/doc.project.mk"
diff --git a/ru_RU.KOI8-R/articles/dialup-firewall/article.sgml b/ru_RU.KOI8-R/articles/dialup-firewall/article.sgml
deleted file mode 100644
index 3fd74f207d..0000000000
--- a/ru_RU.KOI8-R/articles/dialup-firewall/article.sgml
+++ /dev/null
@@ -1,388 +0,0 @@
-<?xml version="1.0" encoding="koi8-r" standalone="no"?>
-<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V4.2-Based Extension//EN"
-	"../../../share/sgml/freebsd42.dtd" [
-<!ENTITY % entities PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Entity Set//RU" "../../share/sgml/entities.ent">
-%entities;
-]>
-
-<!--
-     The FreeBSD Russian Documentation Project
-
-     $FreeBSD$
-     $FreeBSDru: frdp/doc/ru_RU.KOI8-R/articles/dialup-firewall/article.sgml,v 1.3 2004/07/16 12:05:57 den Exp $
-
-     Original revision: r9218
--->
-
-<article lang="ru">
-  <articleinfo>
-    <title>ðÏÓÔÒÏÅÎÉÅ ÍÅÖÓÅÔÅ×ÏÇÏ ÜËÒÁÎÁ ÎÁ ËÏÍÍÕÔÉÒÕÅÍÏÍ ËÁÎÁÌÅ Ó×ÑÚÉ ÐÒÉ
-      ÐÏÍÏÝÉ FreeBSD</title>
-
-    <authorgroup>
-      <author>
-	<firstname>Marc</firstname>
-	<surname>Silver</surname>
-
-	<affiliation>
-	  <address><email>marcs@draenor.org</email></address>
-	</affiliation>
-      </author>
-    </authorgroup>
-
-    <pubdate>$FreeBSD$</pubdate>
-
-    <releaseinfo>$FreeBSD$</releaseinfo>
-
-    <abstract>
-      <para>üÔÁ ÓÔÁÔØÑ ÏÐÉÓÙ×ÁÅÔ, ËÁË ÎÁÓÔÒÏÉÔØ ÍÅÖÓÅÔÅ×ÏÊ ÜËÒÁÎ ÐÒÉ ÐÏÍÏÝÉ
-        ×ÏÚÍÏÖÎÏÓÔÅÊ PPP ÐÏ ÒÁÂÏÔÅ ÎÁ ËÏÍÍÕÔÉÒÕÅÍÏÍ ËÁÎÁÌÅ Ó×ÑÚÉ Ó FreeBSD É
-        IPFW, É, × ÞÁÓÔÎÏÓÔÉ, ÏÐÉÓÙ×ÁÅÔÓÑ ÎÁÓÔÒÏÊËÁ ÍÅÖÓÅÔÅ×ÏÇÏ ÜËÒÁÎÁ ÐÒÉ
-        ÉÓÐÏÌØÚÏ×ÁÎÉÉ ËÏÍÍÕÔÉÒÕÅÍÏÇÏ ËÁÎÁÌÁ Ó×ÑÚÉ Ó ÄÉÎÁÍÉÞÅÓËÉ ×ÙÄÅÌÑÅÍÙÍ
-        ÁÄÒÅÓÏÍ IP.  üÔÏÔ ÄÏËÕÍÅÎÔ ÎÅ ÏÐÉÓÙ×ÁÅÔ ÎÁÞÁÌØÎÕÀ ÎÁÓÔÒÏÊËÕ
-        PPP-ÓÏÅÄÉÎÅÎÉÑ.</para>
-    </abstract>
-  </articleinfo>
-
-  <sect1 id="preface">
-    <title>÷×ÅÄÅÎÉÅ</title>
-
-    <para>ðÏÓÔÒÏÅÎÉÅ ÍÅÖÓÅÔÅ×ÏÇÏ ÜËÒÁÎÁ ÎÁ ËÏÍÍÕÔÉÒÕÅÍÏÍ ËÁÎÁÌÅ Ó×ÑÚÉ ÐÒÉ
-       ÐÏÍÏÝÉ FreeBSD</para>
-
-    <para>üÔÏÔ ÄÏËÕÍÅÎÔ ÐÒÅÄÎÁÚÎÁÞÅÎ ÄÌÑ ÔÏÇÏ, ÞÔÏÂÙ ÏÐÉÓÁÔØ ÄÅÊÓÔ×ÉÑ,
-      ÔÒÅÂÕÅÍÙÅ ÄÌÑ ÎÁÓÔÒÏÊËÉ ÍÅÖÓÅÔÅ×ÏÇÏ ÜËÒÁÎÁ ÐÒÉ ÐÏÍÏÝÉ FreeBSD × ÓÌÕÞÁÅ,
-      ËÏÇÄÁ IP-ÁÄÒÅÓ ×ÙÄÅÌÑÅÔÓÑ ÄÉÎÁÍÉÞÅÓËÉ ×ÁÛÉÍ ÐÒÏ×ÁÊÄÅÒÏÍ.  èÏÔÑ
-      ÐÒÉÌÁÇÁÌÉÓØ ×ÓÅ ÕÓÉÌÉÑ ÄÌÑ ÔÏÇÏ, ÞÔÏÂÙ ÓÄÅÌÁÔØ ÜÔÏÔ ÄÏËÕÍÅÎÔ ÍÁËÓÉÍÁÌØÎÏ
-      ÉÎÆÏÒÍÁÔÉ×ÎÙÍ É ÐÒÁ×ÉÌØÎÙÍ, ×ÓÅ ÖÅ ÐÒÉÓÙÌÁÊÔÅ Ó×ÏÉ ËÏÍÍÅÎÔÁÒÉÉ É
-      ÐÏÖÅÌÁÎÉÑ <ulink
-      url="mailto:marcs@draenor.org">ÓÏÓÔÁ×ÉÔÅÌÀ</ulink>.</para>
-   </sect1>
-
-  <sect1 id="kernel">
-    <title>ðÁÒÁÍÅÔÒÙ ÑÄÒÁ</title>
-
-    <para>ðÒÅÖÄÅ ×ÓÅÇÏ ×ÁÍ ÎÕÖÎÏ ÐÅÒÅËÏÍÐÉÌÉÒÏ×ÁÔØ ×ÁÛÅ ÑÄÒÏ FreeBSD.  åÓÌÉ ×ÁÍ
-      ÎÕÖÎÁ ÂÏÌÅÅ ÐÏÄÒÏÂÎÁÑ ÉÎÆÏÒÍÁÃÉÑ Ï ÔÏÍ, ËÁË ÜÔÏ ÓÄÅÌÁÔØ, ÔÏ ÌÕÞÛÅ ×ÓÅÇÏ
-      ÎÁÞÁÔØ Ó <ulink
-      url="http://www.FreeBSD.org/handbook/kernelconfig.html">ÒÁÚÄÅÌÁ
-      òÕËÏ×ÏÄÓÔ×Á Ï ËÏÎÆÉÇÕÒÁÃÉÉ ÑÄÒÁ</ulink>.  ÷ÁÍ ÎÕÖÎÏ ×ËÌÀÞÉÔØ × ÑÄÒÏ
-      ÓÌÅÄÕÀÝÉÅ ÐÁÒÁÍÅÔÒÙ:</para>
-
-    <variablelist>
-      <varlistentry>
-	<term><literal>options IPFIREWALL</literal></term>
-
-	<listitem>
-	  <para>÷ËÌÀÞÁÅÔ ÍÅÖÓÅÔÅ×ÏÊ ÜËÒÁÎ × ÑÄÒÅ.</para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-	<term><literal>options IPFIREWALL_VERBOSE</literal></term>
-
-	<listitem>
-	  <para>ðÏÓÙÌÁÅÔ ÓÏÏÂÝÅÎÉÑ Ï ÖÕÒÎÁÌÉÒÕÅÍÙÈ ÐÁËÅÔÁÈ × ÓÉÓÔÅÍÎÙÊ
-            ÖÕÒÎÁÌ.</para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-	<term><literal>options
-	    IPFIREWALL_VERBOSE_LIMIT=<replaceable>100</replaceable></literal></term>
-
-	<listitem>
-	  <para>ïÇÒÁÎÉÞÉ×ÁÅÔ ËÏÌÉÞÅÓÔ×Ï ÚÁÐÉÓÙ×ÁÅÍÙÈ × ÖÕÒÎÁÌ ÓÏ×ÐÁÄÁÀÝÉÈ
-            ÓÏÏÂÝÅÎÉÊ.  üÔÏ ÐÏÚ×ÏÌÑÅÔ ÉÚÂÁ×ÉÔØÓÑ ÏÔ ÚÁÐÏÌÎÅÎÉÑ ÆÁÊÌÏ× ÐÒÏÔÏËÏÌÁ
-            ÍÎÏÖÅÓÔ×ÏÍ ÐÏ×ÔÏÒÑÀÝÉÈÓÑ ÚÁÐÉÓÅÊ.  <replaceable>100</replaceable>
-            Ñ×ÌÑÅÔÓÑ ÐÏÄÈÏÄÑÝÉÍ ÄÌÑ ÉÓÐÏÌØÚÏ×ÁÎÉÑ ÐÁÒÁÍÅÔÒÏÍ, ÎÏ ×Ù ÍÏÖÅÔÅ
-            ÉÚÍÅÎÉÔØ ÅÇÏ × ÚÁ×ÉÓÉÍÏÓÔÉ ÏÔ ×ÁÛÉÈ ÐÏÔÒÅÂÎÏÓÔÅÊ.</para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-	<term><literal>options IPDIVERT</literal></term>
-
-	<listitem>
-	  <para>÷ËÌÀÞÁÅÔ ÉÓÐÏÌØÚÏ×ÁÎÉÅ <emphasis>ÐÅÒÅÎÁÐÒÁ×ÌÑÀÝÉÈ</emphasis>
-            ÓÏËÅÔÏ×, ÞÔÏ ÂÕÄÅÔ ÐÏËÁÚÁÎÏ ÎÉÖÅ.</para>
-	</listitem>
-      </varlistentry>
-    </variablelist>
-
-    <para>éÍÅÅÔÓÑ ÔÁËÖÅ ÅÝÅ ÎÅÓËÏÌØËÏ îåïâñúáôåìøîùè ÐÁÒÁÍÅÔÒÏ×, ËÏÔÏÒÙÅ ×Ù
-      ÍÏÖÅÔÅ ÕËÁÚÁÔØ × ÑÄÒÅ ÄÌÑ ÄÏÓÔÉÖÅÎÉÑ ÄÏÐÏÌÎÉÔÅÌØÎÏÊ ÂÅÚÏÐÁÓÎÏÓÔÉ.  äÌÑ
-      ÒÁÂÏÔÙ ÍÅÖÓÅÔÅ×ÏÇÏ ÜËÒÁÎÁ ÜÔÏÇÏ ÎÅ ÔÒÅÂÕÅÔÓÑ, ÎÏ ÎÅËÏÔÏÒÙÅ ÐÁÒÁÎÏÉÄÁÌØÎÏ
-      ÎÁÓÔÒÏÅÎÎÙÅ ÐÏÌØÚÏ×ÁÔÅÌÉ ÍÏÇÕÔ ×ÓÅ ÖÅ ÉÍÉ ×ÏÓÐÏÌØÚÏ×ÁÔØÓÑ.</para>
-
-    <variablelist>
-      <varlistentry>
-	<term><literal>options TCP_RESTRICT_RST</literal></term>
-
-	<listitem>
-	  <para>üÔÏÔ ÐÁÒÁÍÅÔÒ ÂÌÏËÉÒÕÅÔ ×ÓÅ ÐÁËÅÔÙ TCP RST.  üÔÏ ÌÕÞÛÅ
-            ÉÓÐÏÌØÚÏ×ÁÔØ × ÓÉÓÔÅÍÁÈ, ËÏÔÏÒÙÅ ÍÏÇÕÔ ÐÏÄ×ÅÒÇÁÔØÓÑ ÆÌÕÄ-ÁÔÁËÁÍ
-            SYN (ÈÏÒÏÛÉÍ ÐÒÉÍÅÒÏÍ Ñ×ÌÑÀÔÓÑ ÓÅÒ×ÅÒÙ IRC) ÉÌÉ ÔÅÍÉ, ËÔÏ ÎÅ
-            ÈÏÞÅÔ ÂÙÔØ ÌÅÇËÏ ÐÏÄ×ÅÒÇÎÕÔÙÍ ÓËÁÎÉÒÏ×ÁÎÉÀ ÐÏÒÔÏ×.</para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-	<term><literal>options TCP_DROP_SYNFIN</literal></term>
-
-	<listitem>
-	  <para>ðÒÉ ÉÓÐÏÌØÚÏ×ÁÎÉÉ ÜÔÏÇÏ ÐÁÒÁÍÅÔÒÁ TCP-ÐÁËÅÔÙ Ó ÐÏÌÑÍÉ SYN É
-            FIN ÉÇÎÏÒÉÒÕÀÔÓÑ.  üÔÏ ÐÏÚ×ÏÌÉÔ ÉÚÂÅÖÁÔØ ÒÁÓÐÏÚÎÁ×ÁÎÉÑ
-            ÉÓÐÏÌØÚÕÅÍÏÇÏ ÎÁ ÍÁÛÉÎÅ ÔÉÐÁ ÓÔÅËÁ ÔÁËÉÍÉ ÕÔÉÌÉÔÁÍÉ, ËÁË nmap,
-            ÎÏ ÐÒÉ ÜÔÏÍ ÎÅÌØÚÑ ÂÕÄÅÔ ÉÓÐÏÌØÚÏ×ÁÔØ ÒÁÓÛÉÒÅÎÉÑ RFC1644.  åÓÌÉ ÎÁ
-            ÍÁÛÉÎÅ ÂÕÄÅÔ ÒÁÂÏÔÁÔØ ×ÅÂ-ÓÅÒ×ÅÒ, ÄÅÌÁÔØ ÜÔÏ îå
-            ÒÅËÏÍÅÎÄÕÅÔÓÑ.</para>
-	</listitem>
-      </varlistentry>
-     </variablelist>
-
-    <para>îÅ ÐÅÒÅÚÁÇÒÕÖÁÊÔÅ ÍÁÛÉÎÕ ÓÒÁÚÕ ÖÅ ÐÏÓÌÅ ÐÅÒÅËÏÍÐÉÌÑÃÉÉ ÑÄÒÁ.  äÌÑ
-      ÚÁ×ÅÒÛÅÎÉÑ ÎÁÓÔÒÏÊËÉ ÍÅÖÓÅÔÅ×ÏÇÏ ÜËÒÁÎÁ ÎÁÍ, Ë ÓÞÁÓÔØÀ, ÄÏÓÔÁÔÏÞÎÏ ÂÕÄÅÔ
-      ×ÙÐÏÌÎÉÔØ ÐÅÒÅÚÁÇÒÕÚËÕ ×ÓÅÇÏ ÏÄÉÎ ÒÁÚ .</para>
-  </sect1>
-
-  <sect1 id="rcconf">
-    <title>éÚÍÅÎÅÎÉÅ <filename>/etc/rc.conf</filename> ÄÌÑ ÚÁÇÒÕÚËÉ ÍÅÖÓÅÔÅ×ÏÇÏ
-      ÜËÒÁÎÁ</title>
-
-    <para>ôÅÐÅÒØ ÎÁÍ ÎÕÖÎÏ ×ÎÅÓÔÉ ÎÅËÏÔÏÒÙÅ ÉÚÍÅÎÅÎÉÑ × ÆÁÊÌ
-      <filename>/etc/rc.conf</filename> ÄÌÑ ÔÏÇÏ, ÞÔÏÂÙ ÕËÁÚÁÔØ Ï ×ËÌÀÞÅÎÉÉ
-      ÍÅÖÓÅÔÅ×ÏÇÏ ÜËÒÁÎÁ.  ðÒÏÓÔÏ ÄÏÂÁ×ØÔÅ ÓÌÅÄÕÀÝÉÅ ÓÔÒÏËÉ:</para>
-
-    <programlisting>
-firewall_enable="YES"
-firewall_script="/etc/firewall/fwrules"
-natd_enable="YES"
-natd_interface="tun0"
-natd_flags="-dynamic"
-    </programlisting>
-
-    <para>äÌÑ ÐÏÌÕÞÅÎÉÑ ÂÏÌÅÅ ÐÏÌÎÏÊ ÉÎÆÏÒÍÁÃÉÉ Ï ÔÏÍ, ÞÔÏ ÄÅÌÁÀÔ ÜÔÉ ÓÔÒÏËÉ,
-      ×ÚÇÌÑÎÉÔÅ ÎÁ ÓÏÄÅÒÖÉÍÏÅ ÆÁÊÌÁ <filename>/etc/defaults/rc.conf</filename>
-      É ÐÒÏÞÔÉÔÅ &man.rc.conf.5;</para>
-  </sect1>
-
-  <sect1>
-    <title>÷ÙËÌÀÞÅÎÉÅ ÍÅÈÁÎÉÚÍÁ ÐÒÅÏÂÒÁÚÏ×ÁÎÉÑ ÓÅÔÅ×ÙÈ ÁÄÒÅÓÏ× × PPP</title>
-
-    <para>íÏÖÅÔ, ×Ù ÕÖÅ ÉÓÐÏÌØÚÕÅÔÅ ×ÓÔÒÏÅÎÎÙÊ × PPP ÍÅÈÁÎÉÚÍ ÐÒÅÏÂÒÁÚÏ×ÁÎÉÑ
-      ÓÅÔÅ×ÙÈ ÁÄÒÅÓÏ× (NAT).  åÓÌÉ ÜÔÏ ×ÁÛ ÓÌÕÞÁÊ, ÔÏ ×ÁÍ ÎÕÖÎÏ ÜÔÏ ×ÙËÌÀÞÉÔØ,
-      ÔÁË ËÁË × ÜÔÉÈ ÐÒÉÍÅÒÁÈ ÄÌÑ ÔÅÈ ÖÅ ÓÁÍÙÈ ÃÅÌÅÊ ÉÓÐÏÌØÚÕÅÔÓÑ
-      &man.natd.8;.</para>
-
-    <para>åÓÌÉ Õ ×ÁÓ ÕÖÅ ÅÓÔØ ÂÌÏË ÄÉÒÅËÔÉ× ÄÌÑ Á×ÔÏÍÁÔÉÞÅÓËÏÇÏ ÚÁÐÕÓËÁ PPP,
-      ÔÏ ÏÎ, ÓËÏÒÅÅ ×ÓÅÇÏ, ×ÙÇÌÑÄÉÔ ÐÒÉÍÅÒÎÏ ÔÁË:</para>
-
-    <programlisting>
-ppp_enable="YES"
-ppp_mode="auto"
-ppp_nat="YES"
-ppp_profile="<replaceable>profile</replaceable>"
-    </programlisting>
-
-    <para>åÓÌÉ ÜÔÏ ÔÁË, ÔÏ ÕÄÁÌÉÔÅ ÓÔÒÏÞËÕ <literal>ppp_nat="YES"</literal>.
-      ÷ÁÍ ÔÁËÖÅ ÐÏÔÒÅÂÕÅÔÓÑ ÕÄÁÌÉÔØ ×ÓÅ ÓÔÒÏÞËÉ
-      <literal>nat enable yes</literal> É <literal>alias enable yes</literal>
-      × ÆÁÊÌÅ <filename>/etc/ppp/ppp.conf</filename>.</para>
-  </sect1>
-
-  <sect1 id="rules">
-    <title>îÁÂÏÒ ÐÒÁ×ÉÌ ÄÌÑ ÍÅÖÓÅÔÅ×ÏÇÏ ÜËÒÁÎÁ</title>
-
-    <para>ôÅÐÅÒØ ÍÙ ×ÙÐÏÌÎÉÌÉ ÐÒÁËÔÉÞÅÓËÉ ×ÓÅ.  åÄÉÎÓÔ×ÅÎÎÏÅ, ÞÔÏ ÏÓÔÁÌÏÓØ
-      ÓÄÅÌÁÔØ, ÔÁË ÜÔÏ ÚÁÄÁÔØ ÐÒÁ×ÉÌÁ ÄÌÑ ÍÅÖÓÅÔÅ×ÏÇÏ ÜËÒÁÎÁ, ÐÏÓÌÅ ÞÅÇÏ ÍÙ
-      ÍÏÖÅÍ ×ÙÐÏÌÎÉÔØ ÐÅÒÅÚÁÇÒÕÚËÕ, É ÍÅÖÓÅÔÅ×ÏÊ ÜËÒÁÎ ÄÏÌÖÅÎ ÚÁÒÁÂÏÔÁÔØ.  ñ
-      ÐÏÎÉÍÁÀ, ÞÔÏ × ËÁÖÄÏÍ ËÏÎËÒÅÔÎÏÍ ÓÌÕÞÁÅ ÐÏÔÒÅÂÕÅÔÓÑ ÎÁÂÏÒ ÐÒÁ×ÉÌ, ×ÅÓØÍÁ
-      ÏÔÌÉÞÁÀÝÉÊÓÑ ÏÔ ÐÒÅÄÌÁÇÁÅÍÏÇÏ.  ñ ×ÓÅÇÏ ÌÉÛØ ÐÏÐÙÔÁÌÓÑ ÎÁÐÉÓÁÔØ ÎÁÂÏÒ
-      ÐÒÁ×ÉÌ, ËÏÔÏÒÙÅ ÄÏÌÖÎÙ ÐÏÄÏÊÔÉ ÂÏÌØÛÉÎÓÔ×Õ ÐÏÌØÚÏ×ÁÔÅÌÅÊ ËÏÍÍÕÔÉÒÕÅÍÏÇÏ
-      ÄÏÓÔÕÐÁ.  ÷Ù ÍÏÖÅÔÅ ÔÒÉ×ÉÁÌØÎÏ ÉÚÍÅÎÉÔØ ÉÈ ÐÏÄ ×ÁÛÉ ÔÒÅÂÏ×ÁÎÉÑ, ×ÚÑ×
-      ÎÉÖÅÓÌÅÄÕÀÝÉÅ ÐÒÁ×ÉÌÁ × ËÁÞÅÓÔ×Å ÏÓÎÏ×Ù.  îÏ ÓÎÁÞÁÌÁ ÒÁÓÓÍÏÔÒÉÍ ÏÓÎÏ×Ù
-      ÚÁËÒÙÔÏÇÏ ÍÅÖÓÅÔÅ×ÏÇÏ ÜËÒÁÎÁ.  ÷Ù ÈÏÔÉÔÅ ÚÁÐÒÅÔÉÔØ ÐÏ ÕÍÏÌÞÁÎÉÀ ×ÓÅ, Á
-      ÚÁÔÅÍ ÏÔËÒÙ×ÁÔØ ÔÏÌØËÏ ÔÏ, ÞÔÏ ×ÁÍ ÎÕÖÎÏ.  ðÒÁ×ÉÌÁ ÄÏÌÖÎÙ ÓÌÅÄÏ×ÁÔØ ×
-      ÐÏÒÑÄËÅ, ËÏÇÄÁ ÓÎÁÞÁÌÁ ÉÄÕÔ ÒÁÚÒÅÛÁÀÝÉÅ ÐÒÁ×ÉÌÁ, Á ÚÁÔÅÍ ÚÁÐÒÅÝÁÀÝÉÅ.
-      ðÏÌÁÇÁÅÍ, ÞÔÏ ×Ù ÄÏÂÁ×ÉÔÅ Ó×ÏÉ ÒÁÚÒÅÛÁÀÝÉÅ ÐÒÁ×ÉÌÁ, Á ÚÁÔÅÍ ×ÓÅ ÏÓÔÁÌØÎÏÅ
-      ÂÕÄÅÔ ÚÁÐÒÅÝÅÎÏ. :)</para>
-
-    <para>ôÅÐÅÒØ ÓÏÚÄÁÄÉÍ ËÁÔÁÌÏÇ /etc/firewall.  ðÅÒÅÊÄÉÔÅ × ÜÔÏÔ ËÁÔÁÌÏÇ É
-      ÏÔÒÅÄÁËÔÉÒÕÊÔÅ ÆÁÊÌ fwrules, ËÏÔÏÒÙÊ ÍÙ ÕËÁÚÁÌÉ × rc.conf.  ðÏÖÁÌÕÊÓÔÁ,
-      ÏÔÍÅÔØÔÅ, ÞÔÏ ×Ù ÍÏÖÅÔÅ ÉÚÍÅÎÉÔØ ÜÔÏ ÉÍÑ ÎÁ ÌÀÂÏÅ ÄÒÕÇÏÅ.  ÷ ÜÔÏÍ
-      ÒÕËÏ×ÏÄÓÔ×Å ÉÍÑ ÆÁÊÌÁ ÄÁÅÔÓÑ × ËÁÞÅÓÔ×Å ÐÒÉÍÅÒÁ.</para>
-
-    <para>äÁ×ÁÊÔÅ ×ÚÇÌÑÎÅÍ ÎÁ ÐÒÉÍÅÒ ÆÁÊÌÁ ÄÌÑ ÍÅÖÓÅÔÅ×ÏÇÏ ÜËÒÁÎÁ, É ÐÏÄÒÏÂÎÏ
-      ÏÐÉÛÅÍ ÅÇÏ ÓÏÄÅÒÖÉÍÏÅ.</para>
-
-    <programlisting>
-# Firewall rules
-# Written by Marc Silver (marcs@draenor.org)
-# http://draenor.org/ipfw
-# Freely distributable
-
-
-# Define the firewall command (as in /etc/rc.firewall) for easy
-# reference.  Helps to make it easier to read.
-fwcmd="/sbin/ipfw"
-
-# Force a flushing of the current rules before we reload.
-$fwcmd -f flush
-
-# Divert all packets through the tunnel interface.
-$fwcmd add divert natd all from any to any via tun0
-
-# Allow all data from my network card and localhost.  Make sure you
-# change your network card (mine was fxp0) before you reboot.  :)
-$fwcmd add allow ip from any to any via lo0
-$fwcmd add allow ip from any to any via fxp0
-
-# Allow all connections that I initiate.
-$fwcmd add allow tcp from any to any out xmit tun0 setup
-
-# Once connections are made, allow them to stay open.
-$fwcmd add allow tcp from any to any via tun0 established
-
-# Everyone on the internet is allowed to connect to the following
-# services on the machine.  This example shows that people may connect
-# to ssh and apache.
-$fwcmd add allow tcp from any to any 80 setup
-$fwcmd add allow tcp from any to any 22 setup
-
-# This sends a RESET to all ident packets.
-$fwcmd add reset log tcp from any to any 113 in recv tun0
-
-# Allow outgoing DNS queries ONLY to the specified servers.
-$fwcmd add allow udp from any to <replaceable>x.x.x.x</replaceable> 53 out xmit tun0
-
-# Allow them back in with the answers...  :)
-$fwcmd add allow udp from <replaceable>x.x.x.x</replaceable> 53 to any in recv tun0
-
-# Allow ICMP (for ping and traceroute to work).  You may wish to
-# disallow this, but I feel it suits my needs to keep them in.
-$fwcmd add 65435 allow icmp from any to any
-
-# Deny all the rest.
-$fwcmd add 65435 deny log ip from any to any
-    </programlisting>
-
-    <para>ôÅÐÅÒØ Õ ×ÁÓ ÅÓÔØ ÐÏÌÎÏÆÕÎËÃÉÏÎÁÌØÎÙÊ ÍÅÖÓÅÔÅ×ÏÊ ÜËÒÁÎ, ËÏÔÏÒÙÊ
-      ÒÁÚÒÅÛÁÅÔ ÓÏÅÄÉÎÅÎÉÑ Ë ÐÏÒÔÁÍ 80 É 22, É ÏÔÏÂÒÁÖÁÅÔ × ÖÕÒÎÁÌÅ ×ÓÅ
-      ÏÓÔÁÌØÎÙÅ ÐÏÐÙÔËÉ ÓÏÅÄÉÎÅÎÉÑ.  ôÅÐÅÒØ Õ ×ÁÓ ÄÏÌÖÎÁ ÕÓÐÅÛÎÏ ÐÒÏÊÔÉ
-      ÐÅÒÅÚÁÇÒÕÚËÁ É ×ÁÛ ÍÅÖÓÅÔÅ×ÏÊ ÜËÒÁÎ ÄÏÌÖÅÎ ÎÏÒÍÁÌØÎÏ ÚÁÒÁÂÏÔÁÔØ.  åÓÌÉ ×Ù
-      ÏÂÎÁÒÕÖÉÔÅ, ÞÔÏ ÜÔÏ ÎÅ ÔÁË, Õ ×ÁÓ ×ÏÚÎÉËÎÕÔ ÐÒÏÂÌÅÍÙ ÉÌÉ Õ ×ÁÓ ×ÏÚÎÉËÎÕÔ
-      ÐÏÖÅÌÁÎÉÑ, ÐÏÖÁÌÕÊÓÔÁ, ÎÁÐÉÛÉÔÅ ÍÎÅ ÐÉÓØÍÏ ÐÏ ÜÌÅËÔÒÏÎÎÏÊ ÐÏÞÔÅ.</para>
-  </sect1>
-
-  <sect1>
-    <title>÷ÏÐÒÏÓÙ</title>
-
-    <qandaset>
-      <qandaentry>
-	<question>
-	  <para>ðÏÞÅÍÕ ×Ù ÉÓÐÏÌØÚÕÅÔÅ natd É ipfw, ËÏÇÄÁ ÍÏÖÎÏ ÉÓÐÏÌØÚÏ×ÁÔØ
-            ×ÓÔÒÏÅÎÎÙÅ ÆÉÌØÔÒÙ ppp?</para>
-	</question>
-
-	<answer>
-	  <para>óËÁÖÕ ÞÅÓÔÎÏ, ÞÔÏ ÏÐÒÅÄÅÌÅÎÎÏÊ ÐÒÉÞÉÎÙ, ÏÂßÑÓÎÑÀÝÅÊ, ÐÏÞÅÍÕ Ñ
-            ÉÓÐÏÌØÚÕÀ ipfw É natd ×ÍÅÓÔÏ ×ÓÔÒÏÅÎÎÙÈ × ppp ÆÉÌØÔÒÏ×.  ÷
-            ÒÅÚÕÌØÔÁÔÅ ÏÂÓÕÖÄÅÎÉÊ ÜÔÏÇÏ ×ÏÐÒÏÓÁ Ó ÄÒÕÇÉÍÉ ÌÀÄØÍÉ Ñ ÐÒÉÛÅÌ Ë
-            ÍÎÅÎÉÀ, ÞÔÏ, ÈÏÔÑ ipfw Ñ×ÌÑÅÔÓÑ ÇÏÒÁÚÄÏ ÂÏÌÅÅ ÍÏÝÎÙÍ É ÇÉÂËÉÍ
-            ÉÎÓÔÒÕÍÅÎÔÏÍ, ÞÅÍ ÆÉÌØÔÒÙ ppp, ÎÏ ×ÓÅ, ÞÔÏ ÏÎ ×ÙÉÇÒÙ×ÁÅÔ ×
-            ÛÉÒÏÔÅ ×ÏÚÍÏÖÎÏÓÔÅÊ, ÐÒÏÉÇÒÙ×ÁÅÔ × ÌÅÇËÏÓÔÉ ÎÁÓÔÒÏÊËÉ.  ïÄÎÏÊ ÉÚ
-            ÐÒÉÞÉÎ, ÐÏ ËÏÔÏÒÏÊ Ñ ÅÇÏ ÉÓÐÏÌØÚÕÀ, Ñ×ÌÑÅÔÓÑ ÔÏ, ÞÔÏ Ñ ÐÒÅÄÐÏÞÉÔÁÀ
-            ÆÕÎËÃÉÉ ÍÅÖÓÅÔÅ×ÏÇÏ ÜËÒÁÎÁ, ÒÅÁÌÉÚÕÅÍÙÅ × ÑÄÒÅ, Á ÎÅ ×
-            ÐÏÌØÚÏ×ÁÔÅÌØÓËÏÊ ÐÒÏÇÒÁÍÍÅ.</para>
-	</answer>
-      </qandaentry>
-
-      <qandaentry>
-	<question>
-	  <para>åÓÌÉ ×Ï ×ÎÕÔÒÅÎÎÅÊ ÓÅÔÉ Ñ ÉÓÐÏÌØÚÕÀ ÔÁËÉÅ ÁÄÒÅÓÁ, ËÁË
-	    192.168.0.0, ÔÏ ÍÏÇÕ ÌÉ Ñ ÄÏÂÁ×ÉÔØ ËÏÍÁÎÄÕ ÔÉÐÁ <literal>$fwcmd add
-            deny all from any to 192.168.0.0:255.255.0.0 via tun0</literal> Ë
-            ÐÒÁ×ÉÌÁÍ ÍÅÖÓÅÔÅ×ÏÇÏ ÜËÒÁÎÁ ÄÌÑ ÐÒÅÄÏÔ×ÒÁÝÅÎÉÑ ÐÏÐÙÔÏË ÐÏÄËÌÀÞÉÔØÓÑ
-            ÉÚ×ÎÅ Ë ÍÁÛÉÎÁÍ ×Ï ×ÎÕÔÒÅÎÎÅÊ ÓÅÔÉ?</para>
-	</question>
-
-	<answer>
-	  <para>ðÒÏÓÔÏÊ ÏÔ×ÅÔ ×ÙÇÌÑÄÉÔ ËÁË ÎÅÔ.  ðÒÉÞÉÎÏÊ ÜÔÏÇÏ Ñ×ÌÑÅÔÓÑ ÔÏ,
-            ÞÔÏ natd ×ÙÐÏÌÎÑÅÔ ÐÒÅÏÂÒÁÚÏ×ÁÎÉÑ ÄÌÑ <emphasis>×ÓÅÇÏ</emphasis>
-            ÔÒÁÆÉËÁ, ÐÅÒÅÎÁÐÒÁ×ÌÑÅÍÏÇÏ ÞÅÒÅÚ ÕÓÔÒÏÊÓÔ×Ï tun0.  äÏ ÔÅÈ ÐÏÒ, ÐÏËÁ
-            ÜÔÏ ÔÁË, ×ÈÏÄÑÝÉÅ ÐÁËÅÔÙ ÂÕÄÕÔ ÎÁÐÒÁ×ÌÑÔØÓÑ ÔÏÌØËÏ ÎÁ ÄÉÎÁÍÉÞÅÓËÉ
-            ÎÁÚÎÁÞÅÎÎÙÊ IP-ÁÄÒÅÓ, Á îå ×Ï ×ÎÕÔÒÅÎÎÀÀ ÓÅÔØ.  ïÄÎÁËÏ ÚÁÍÅÔØÔÅ,
-            ÞÔÏ ×Ù ÍÏÖÅÔÅ ÄÏÂÁ×ÉÔØ, ÎÁÐÒÉÍÅÒ, ÐÒÁ×ÉÌÏ <literal>$fwcmd add deny
-            all from 192.168.0.4:255.255.0.0 to any via tun0</literal>, ËÏÔÏÒÏÅ
-            ÂÕÄÅÔ ÏÇÒÁÎÉÞÉ×ÁÔØ ËÏÍÍÕÎÉËÁÃÉÉ ÈÏÓÔÁ × ×ÁÛÅÊ ×ÎÕÔÒÅÎÎÅÊ ÓÅÔÉ Ó
-            ×ÎÅÛÎÉÍ ÍÉÒÏÍ ÞÅÒÅÚ ÍÅÖÓÅÔÅ×ÏÊ ÜËÒÁÎ.</para>
-	</answer>
-      </qandaentry>
-
-      <qandaentry>
-	<question>
-	  <para>þÔÏ-ÔÏ ÚÄÅÓØ ÎÅÐÒÁ×ÉÌØÎÏ.  ñ ÓÌÅÄÏ×ÁÌ ×ÁÛÉÍ ÕËÁÚÁÎÉÑÍ ×ÐÌÏÔØ ÄÏ
-            ÂÕË×Ù, É ÔÅÐÅÒØ ÄÏÓÔÕÐ ÚÁÂÌÏËÉÒÏ×ÁÎ.</para>
-        </question>
-
-	<answer>
-	  <para>÷ ÜÔÏÍ ÄÏËÕÍÅÎÔÅ ÐÒÅÄÐÏÌÁÇÁÅÔÓÑ, ÞÔÏ ×Ù ÒÁÂÏÔÁÅÔÅ Ó ÐÒÏÇÒÁÍÍÏÊ
-            <emphasis>ppp</emphasis> ÕÒÏ×ÎÑ ÐÏÌØÚÏ×ÁÔÅÌÑ, ÐÏÜÔÏÍÕ ÐÒÅÄÌÁÇÁÅÍÙÊ
-            ÎÁÂÏÒ ÐÒÁ×ÉÌ ÒÁÂÏÔÁÅÔ Ó ÉÎÔÅÒÆÅÊÓÏÍ <devicename>tun0</devicename>,
-            ËÏÔÏÒÙÊ ÓÏÏÔ×ÅÔÓÔ×ÕÅÔ ÐÅÒ×ÏÍÕ ÓÏÅÄÉÎÅÎÉÀ, ÄÅÌÁÅÍÏÍÕ ÕÔÉÌÉÔÏÊ
-            &man.ppp.8; (ÉÚ×ÅÓÔÎÏÊ ÔÁËÖÅ ËÁË <emphasis>user-ppp</emphasis>).
-            äÏÐÏÌÎÉÔÅÌØÎÙÅ ÓÏÅÄÉÎÅÎÉÑ ÂÕÄÕÔ ÉÓÐÏÌØÚÏ×ÁÔØ ÕÓÔÒÏÊÓÔ×Á
-	    <devicename>tun1</devicename>, <devicename>tun2</devicename> É ÔÁË
-            ÄÁÌÅÅ.</para>
-
-	  <para>÷Ù ÄÏÌÖÎÙ ÔÁËÖÅ ÏÔÍÅÔÉÔØ, ÞÔÏ ÐÒÏÇÒÁÍÍÁ &man.pppd.8;
-            ÉÓÐÏÌØÚÕÅÔ ÄÒÕÇÏÊ ÉÎÔÅÒÆÅÊÓ, <devicename>ppp0</devicename>,
-            ÐÏÜÔÏÍÕ, ÅÓÌÉ ×Ù ÏÓÕÝÅÓÔ×ÌÑÅÔÅ ÓÏÅÄÉÎÅÎÉÅ Ó ÐÏÍÏÝØÀ ÐÒÏÇÒÁÍÍÙ
-            &man.pppd.8;, ÔÏ ÄÏÌÖÎÙ ÚÁÍÅÎÉÔØ <devicename>tun0</devicename> ÎÁ
-            <devicename>ppp0</devicename>.  âÙÓÔÒÙÊ ÓÐÏÓÏ ÉÚÍÅÎÉÔØ ÐÒÁ×ÉÌÁ ÄÌÑ
-            ÍÅÖÓÅÔÅ×ÏÇÏ ÜËÒÁÎÁ ÐÏËÁÚÁÎ ÎÉÖÅ.  ïÒÉÇÉÎÁÌØÎÙÊ ÎÁÂÏÒ ÐÒÁ×ÉÌ ÂÕÄÅÔ
-            ÓÏÈÒÁÎÅÎ × ÆÁÊÌÅ <filename>fwrules_tun0</filename>.</para>
-
-	  <screen>
-	    &prompt.user; <userinput>cd /etc/firewall</userinput>
-	    /etc/firewall&prompt.user; <userinput>su</userinput>
-	    <prompt>Password:</prompt>
-	    /etc/firewall&prompt.root; <userinput>mv fwrules fwrules_tun0</userinput>
-	    /etc/firewall&prompt.root; <userinput>cat fwrules_tun0 | sed s/tun0/ppp0/g > fwrules</userinput>
-	  </screen>
-
-	  <para>äÌÑ ÔÏÇÏ, ÞÔÏÂÙ ÕÚÎÁÔØ, ÉÓÐÏÌØÚÕÅÔÅ ÌÉ ×Ù &man.ppp.8; ÉÌÉ
-	    &man.pppd.8;, ×Ù ÍÏÖÅÔÅ ÐÏÓÍÏÔÒÅÔØ ×Ù×ÏÄ ËÏÍÁÎÄÙ &man.ifconfig.8;
-	    ÐÏÓÌÅ ÕÓÔÁÎÏ×ËÉ ÓÏÅÄÉÎÅÎÉÑ.  îÁÐÒÉÍÅÒ, ÄÌÑ ÓÏÅÄÉÎÅÎÉÑ, ×ÙÐÏÌÎÑÅÍÏÇÏ
-            ÐÒÉ ÐÏÍÏÝÉ ÐÒÏÇÒÁÍÍÙ &man.pppd.8;, ×Ù Õ×ÉÄÉÔÅ ÎÅÞÔÏ, ÐÏÈÏÖÅÅ ÎÁ
-            ÓÌÅÄÕÀÝÅÅ (ÐÏËÁÚÁÎÙ ÔÏÌØËÏ ÏÔÎÏÓÑÝÉÅÓÑ Ë ÄÅÌÕ ÓÔÒÏÞËÉ):</para>
-
-	  <screen>
-	    &prompt.user; <userinput>ifconfig</userinput>
-	    <emphasis>(skipped...)</emphasis>
-	    ppp0: flags=<replaceable>8051&lt;UP,POINTOPOINT,RUNNING,MULTICAST&gt; mtu 1524</replaceable>
-                    inet <replaceable>xxx.xxx.xxx.xxx</replaceable> --&gt; <replaceable>xxx.xxx.xxx.xxx</replaceable> netmask <replaceable>0xff000000</replaceable>
-	    <emphasis>(skipped...)</emphasis>
-          </screen>
-
-	  <para>ó ÄÒÕÇÏÊ ÓÔÏÒÏÎÙ, ÄÌÑ ÓÏÅÄÉÎÅÎÉÊ, ×ÙÐÏÌÎÑÅÍÙÈ ÐÏÓÒÅÄÓÔ×ÏÍ
-            &man.ppp.8; (<emphasis>user-ppp</emphasis>), ×Ù ÄÏÌÖÎÙ Õ×ÉÄÅÔØ
-            ÎÅÞÔÏ ×ÒÏÄÅ ÓÌÅÄÕÀÝÅÇÏ:</para>
-
-	  <screen>
-	    &prompt.user; <userinput>ifconfig</userinput>
-	    <emphasis>(skipped...)</emphasis>
-	    ppp0: flags=<replaceable>8010&lt;POINTOPOINT,MULTICAST&gt; mtu 1500</replaceable>
-	    <emphasis>(skipped...)</emphasis>
-	    tun0: flags=<replaceable>8051&lt;UP,POINTOPOINT,RUNNING,MULTICAST&gt; mtu 1524</replaceable>
-	            <emphasis>(IPv6 stuff skipped...)</emphasis>
-                    inet <replaceable>xxx.xxx.xxx.xxx</replaceable> --&gt; <replaceable>xxx.xxx.xxx.xxx</replaceable> netmask <replaceable>0xffffff00</replaceable>
-                    Opened by PID <replaceable>xxxxx</replaceable>
-            <emphasis>(skipped...)</emphasis>
-          </screen>
-	</answer>
-      </qandaentry>
-    </qandaset>
-  </sect1>
-</article>
diff --git a/ru_RU.KOI8-R/articles/diskless-x/Makefile b/ru_RU.KOI8-R/articles/diskless-x/Makefile
deleted file mode 100644
index d7c1b3d6c6..0000000000
--- a/ru_RU.KOI8-R/articles/diskless-x/Makefile
+++ /dev/null
@@ -1,21 +0,0 @@
-#
-# The FreeBSD Russian Documentation Project
-#
-# $FreeBSD$
-# $FreeBSDru: frdp/doc/ru_RU.KOI8-R/articles/diskless-x/Makefile,v 1.4 2005/06/12 07:19:45 gad Exp $
-#
-# Original revision: r20561
-#
-# Article: Diskless X Server: a how to guide
-
-DOC?= article
-
-FORMATS?= html
-
-INSTALL_COMPRESSED?=gz
-INSTALL_ONLY_COMPRESSED?=
-
-SRCS=  article.sgml
-
-DOC_PREFIX?= ${.CURDIR}/../../..
-.include "${DOC_PREFIX}/share/mk/doc.project.mk"
diff --git a/ru_RU.KOI8-R/articles/diskless-x/article.sgml b/ru_RU.KOI8-R/articles/diskless-x/article.sgml
deleted file mode 100644
index 3a6a549b59..0000000000
--- a/ru_RU.KOI8-R/articles/diskless-x/article.sgml
+++ /dev/null
@@ -1,377 +0,0 @@
-<?xml version="1.0" encoding="koi8-r" standalone="no"?>
-<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V4.2-Based Extension//EN"
-	"../../../share/sgml/freebsd42.dtd" [
-<!ENTITY % entities PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Entity Set//RU" "../../share/sgml/entities.ent">
-%entities;
-]>
-
-<!--
-     The FreeBSD Russian Documentation Project
-
-     $FreeBSD$
-     $FreeBSDru: frdp/doc/ru_RU.KOI8-R/articles/diskless-x/article.sgml,v 1.8 2005/06/12 07:18:50 gad Exp $
-
-     Original revision: r23070
--->
-
-<article lang="ru">
-  <articleinfo>
-    <title>âÅÚÄÉÓËÏ×ÙÊ X-ÓÅÒ×ÅÒ: ÒÕËÏ×ÏÄÓÔ×Ï ÐÏ ÎÁÓÔÒÏÊËÅ</title>
-
-    <authorgroup>
-      <author>
-	<firstname>Jerry</firstname>
-	<surname>Kendall</surname>
-	<affiliation>
-	  <address>
-	    <email>jerry@kcis.com</email>
-	  </address>
-	</affiliation>
-      </author></authorgroup>
-
-    <pubdate>28 ÄÅËÁÂÒÑ 1996</pubdate>
-
-    <copyright>
-      <year>1996</year>
-
-      <holder>Jerry Kendall</holder>
-    </copyright>
-
-    <legalnotice id="trademarks" role="trademarks">
-      &tm-attrib.freebsd;
-      &tm-attrib.3com;
-      &tm-attrib.microsoft;
-      &tm-attrib.sun;
-      &tm-attrib.general;
-    </legalnotice>
-
-    <releaseinfo>$FreeBSD$</releaseinfo>
-
-    <abstract>
-      <para>ó ÐÏÍÏÝØÀ ÎÅÓËÏÌØËÉÈ ÄÒÕÚÅÊ ÉÚ ÓÐÉÓËÁ ÒÁÓÓÙÌËÉ FreeBSD-hackers Ñ
-        ÓÍÏÇ ÎÁÓÔÒÏÉÔØ ÂÅÚÄÉÓËÏ×ÙÊ X-ÔÅÒÍÉÎÁÌ.  óÏÚÄÁÎÉÅ X-ÔÅÒÍÉÎÁÌÁ,
-        ×Ï-ÐÅÒ×ÙÈ, ÔÒÅÂÕÅÔ ÓÎÁÞÁÌÁ ÎÁÓÔÒÏÊËÉ ÂÅÚÄÉÓËÏ×ÏÊ ÓÉÓÔÅÍÙ Ó ÍÉÎÉÍÁÌØÎÙÍ
-        ÎÁÂÏÒÏÍ ÕÔÉÌÉÔ, ÄÏÓÔÕÐÎÙÈ ÞÅÒÅÚ NFS.  ôÅ ÖÅ ÓÁÍÙÅ ÛÁÇÉ ÂÙÌÉ ÐÒÉÍÅÎÅÎÙ
-        ÄÌÑ ÓÏÚÄÁÎÉÑ Ä×ÕÈ ÒÁÚÎÙÈ ÂÅÚÄÉÓËÏ×ÙÈ ÓÉÓÔÅÍ.  ðÅÒ×ÁÑ ÉÚ ÎÉÈ ÂÙÌÁ
-        <hostid role="fqdn">altair.example.com</hostid>.  âÅÚÄÉÓËÏ×ÙÊ
-        X-ÔÅÒÍÉÎÁÌ, ËÏÔÏÒÙÊ ÒÁÂÏÔÁÌ ÎÁ ÍÏÅÊ ÓÔÁÒÏÊ ÍÁÛÉÎÅ 386DX-40.  îÁ ÎÅÊ ÂÙÌ
-        ÄÉÓË ÏÂßÅÍÏÍ 340 ÍÅÇÁÂÁÊÔ, ÎÏ Ñ ÎÅ ÈÏÔÅÌ ÅÇÏ ÍÅÎÑÔØ.  ôÁË ÞÔÏ ÍÁÛÉÎÁ
-        ÚÁÇÒÕÖÁÌÁÓØ Ó <hostid role="fqdn">antares.example.com</hostid> ÐÏ ÓÅÔÉ
-        Ethernet.  ÷ÔÏÒÏÊ ÓÉÓÔÅÍÏÊ Ñ×ÌÑÅÔÓÑ 486DX2-66.  ñ ÎÁÓÔÒÏÉÌ (ÐÏÌÎÏÓÔØÀ)
-        ÂÅÚÄÉÓËÏ×ÕÀ ÓÉÓÔÅÍÕ FreeBSD, ËÏÔÏÒÁÑ ÎÅ ÉÓÐÏÌØÚÕÅÔ ÌÏËÁÌØÎÙÊ ÄÉÓË.
-        óÅÒ×ÅÒÏÍ × ÜÔÏÍ ÓÌÕÞÁÅ ×ÙÓÔÕÐÁÅÔ Sun 670MP ÐÏÄ ÕÐÒÁ×ÌÅÎÉÅÍ &sunos;
-        4.1.3.  ÷ ÏÂÏÉÈ ÓÌÕÞÁÑÈ ÔÒÅÂÏ×ÁÌÁÓØ ÏÄÎÁ É ÔÁ ÖÅ ÎÁÞÁÌØÎÁÑ
-        ÎÁÓÔÒÏÊËÁ.</para>
-
-      <para>ñ Õ×ÅÒÅÎ, ÞÔÏ Ë ÜÔÏÍÕ ÅÓÔØ ÞÔÏ ÄÏÂÁ×ÉÔØ.  ðÏÖÁÌÕÊÓÔÁ, ÐÒÉÓÙÌÁÊÔÅ
-        ÍÎÅ ÌÀÂÙÅ ÚÁÍÅÞÁÎÉÑ.</para>
-    </abstract>
-  </articleinfo>
-
-  <sect1>
-    <title>óÏÚÄÁÎÉÅ ÚÁÇÒÕÚÏÞÎÏÊ ÄÉÓËÅÔÙ (ÎÁ ÂÅÚÄÉÓËÏ×ÏÊ ÓÉÓÔÅÍÅ)</title>
-
-    <para>ôÁË ËÁË ÓÅÔÅ×ÙÅ ÎÁÞÁÌØÎÙÅ ÚÁÇÒÕÚÞÉËÉ ÎÅ ÂÕÄÕÔ ÒÁÂÏÔÁÔØ Ó ÎÅËÏÔÏÒÙÍÉ
-      ÒÅÚÉÄÅÎÔÎÙÍÉ (TSR) É ÐÒÏÞÉÍÉ ÐÒÏÇÒÁÍÍÁÍÉ, ÉÓÐÏÌØÚÕÅÍÙÍÉ × &ms-dos;, ÔÏ
-      ÌÕÞÛÅ ÓÏÚÄÁÔØ ÏÔÄÅÌØÎÕÀ ÚÁÇÒÕÚÏÞÎÕÀ ÄÉÓËÅÔÕ, ÉÌÉ, ÅÓÌÉ ×Ù ÍÏÖÅÔÅ, ÓÏÚÄÁÔØ
-      ÍÅÎÀ &ms-dos;, ËÏÔÏÒÏÅ ÂÕÄÅÔ (ÐÒÉ ÐÏÍÏÝÉ ÆÁÊÌÏ×
-      <filename>config.sys</filename>/<filename>autoexec.bat</filename>)
-      ÓÐÒÁÛÉ×ÁÔØ, ËÁËÕÀ ËÏÎÆÉÇÕÒÁÃÉÀ ÓÌÅÄÕÅÔ ÚÁÇÒÕÚÉÔØ ÐÒÉ ÚÁÐÕÓËÅ ÓÉÓÔÅÍÙ.
-      ñ ÉÓÐÏÌØÚÏ×ÁÌ ÐÏÓÌÅÄÎÉÊ ÍÅÔÏÄ É ÏÎ ÐÒÅËÒÁÓÎÏ ÒÁÂÏÔÁÅÔ.  íÏÅ ÍÅÎÀ &ms-dos;
-      (6.x) ÐÒÉ×ÏÄÉÔÓÑ ÎÉÖÅ.</para>
-
-    <example>
-      <title><filename>config.sys</filename></title>
-
-      <programlisting>[menu]
-menuitem=normal, normal
-menuitem=unix, unix
-[normal]
-....
-normal config.sys stuff
-...
-[unix]</programlisting>
-    </example>
-
-    <example>
-      <title><filename>autoexec.bat</filename></title>
-
-      <programlisting>@ECHO OFF
-goto %config%
-
-:normal
-...
-normal autoexec.bat stuff
-...
-goto end
-
-:unix
-cd \netboot
-nb8390.com
-
-:end</programlisting>
-    </example>
-  </sect1>
-
-  <sect1>
-    <title>ðÏÌÕÞÅÎÉÅ ÐÒÏÇÒÁÍÍ ÄÌÑ ÓÅÔÅ×ÏÊ ÚÁÇÒÕÚËÉ (ÎÁ ÓÅÒ×ÅÒÅ)</title>
-
-    <para>ïÔËÏÍÐÉÌÉÒÕÊÔÅ ÐÒÏÇÒÁÍÍÙ <quote>net-boot</quote>, ÒÁÓÐÏÌÏÖÅÎÎÙÅ ×
-      ËÁÔÁÌÏÇÅ <filename>/usr/src/sys/i386/boot/netboot</filename>.  ÷Ù ÄÏÌÖÎÙ
-      ÐÒÏÞÅÓÔØ ÚÁÍÅÞÁÎÉÑ × ÎÁÞÁÌÅ ÆÁÊÌÁ <filename>Makefile</filename>.
-      éÚÍÅÎÉÔÅ ÎÁÓÔÒÏÊËÉ, ËÁË ÜÔÏ ÎÕÖÎÏ.  óÄÅÌÁÊÔÅ ÒÅÚÅÒ×ÎÕÀ ËÏÐÉÀ ÏÒÉÇÉÎÁÌÁ
-      ÎÁ ÔÏÔ ÓÌÕÞÁÊ, ÅÓÌÉ ÞÔÏ-ÔÏ ÐÏÊÄ£Ô ÎÅ ÔÁË, ËÁË ÏÖÉÄÁÌÏÓØ.  ëÏÇÄÁ
-      ÐÏÓÔÒÏÅÎÉÅ ÂÕÄÅÔ ÚÁËÏÎÞÅÎÏ, ÄÏÌÖÎÏ ÐÏÌÕÞÉÔØÓÑ 2
-      ×ÙÐÏÌÎÉÍÙÈ ÆÁÊÌÁ ÄÌÑ &ms-dos;, <filename>nb8390.com</filename> É
-      <filename>nb3c509.com</filename>.  ïÄÎÁ ÉÚ ÜÔÉÈ ÐÒÏÇÒÁÍÍ É ÂÕÄÅÔ ÔÅÍ, ÞÔÏ
-      ×ÁÍ ÎÕÖÎÏ ÚÁÐÕÓÔÉÔØ ÎÁ ÂÅÚÄÉÓËÏ×ÏÍ ÓÅÒ×ÅÒÅ.  ïÎÁ ÂÕÄÅÔ ÚÁÇÒÕÖÁÔØ ÑÄÒÏ
-      Ó ÓÅÒ×ÅÒÁ.  îÁ ÜÔÏÍ ÜÔÁÐÅ ÐÏÍÅÓÔÉÔÅ ÏÂÅ ÐÒÏÇÒÁÍÍÙ ÎÁ ÚÁÇÒÕÚÏÞÎÕÀ ÄÉÓËÅÔÕ
-      &ms-dos;, ÓÏÚÄÁÎÎÕÀ ÒÁÎÅÅ.</para>
-  </sect1>
-
-  <sect1>
-    <title>ïÐÒÅÄÅÌÉÔÅ, ËÁËÕÀ ÐÒÏÇÒÁÍÍÕ ÎÕÖÎÏ ÚÁÐÕÓËÁÔØ (ÎÁ ÂÅÚÄÉÓËÏ×ÏÊ
-      ÓÉÓÔÅÍÅ)</title>
-
-    <para>åÓÌÉ ×Ù ÚÎÁÅÔÅ, ËÁËÏÊ ÎÁÂÏÒ ÍÉËÒÏÓÈÅÍ ÉÓÐÏÌØÚÕÅÔÓÑ × ×ÁÛÅÍ ÁÄÁÐÔÅÒÅ
-      Ethernet, ÜÔÏ ÌÅÇËÏ.  åÓÌÉ Õ ×ÁÓ ÉÓÐÏÌØÚÕÅÔÓÑ ÎÁÂÏÒ ÍÉËÒÏÓÈÅÍ NS8390 ÉÌÉ
-      ÄÒÕÇÏÊ ÎÁ ÅÅ ÏÓÎÏ×Å, ÔÏ ÎÕÖÎÏ ÉÓÐÏÌØÚÏ×ÁÔØ
-      <filename>nb8390.com</filename>.  åÓÌÉ Õ ×ÁÓ ÉÓÐÏÌØÚÕÅÔÓÑ ÎÁÂÏÒ ÍÉËÒÏÓÈÅÍ
-      ÎÁ ÏÓÎÏ×Å &tm.3com; 509, ÔÏ ÉÓÐÏÌØÚÕÊÔÅ ÐÒÏÇÒÁÍÍÕ ÚÁÇÒÕÚËÉ
-      <filename>nb3C509.com</filename>.  åÓÌÉ ×Ù ÎÅ Õ×ÅÒÅÎÙ × ÔÏÍ, ÞÔÏ Õ ×ÁÓ
-      ÕÓÔÁÎÏ×ÌÅÎÏ, ÐÏÐÒÏÂÕÊÔÅ ÉÓÐÏÌØÚÏ×ÁÔØ ÌÀÂÏÊ, É ÅÓÌÉ ÏÎ ×ÙÄÁÓÔ ÓÏÏÂÝÅÎÉÅ
-      <errorname>No adapter found</errorname>, ÐÏÐÒÏÂÕÊÔÅ ÄÒÕÇÏÊ.  ëÒÏÍÅ ÜÔÏÇÏ,
-      ×ÁÍ ÎÉÞÅÇÏ ÎÅ ÏÓÔÁÅÔÓÑ ÄÅÌÁÔØ.</para>
-  </sect1>
-
-  <sect1>
-    <title>úÁÇÒÕÚËÁ ÐÏ ÓÅÔÉ</title>
-
-    <para>úÁÇÒÕÚÉÔÅ ÂÅÚÄÉÓËÏ×ÕÀ ÓÉÓÔÅÍÕ ÂÅÚ ËÁËÉÈ-ÌÉÂÏ ÆÁÊÌÏ×
-      config.sys/autoexec.bat.  ðÏÐÒÏÂÕÊÔÅ ÚÁÐÕÓÔÉÔØ ÚÁÇÒÕÚÏÞÎÕÀ ÐÒÏÇÒÁÍÍÕ ÄÌÑ
-      ×ÁÛÅÇÏ ÁÄÁÐÔÅÒÁ Ethernet.</para>
-
-    <para>íÏÊ ÁÄÁÐÔÅÒ Ethernet ÒÁÂÏÔÁÅÔ ÎÁ ÎÁÂÏÒÅ WD8013 × 16-ÒÁÚÒÑÄÎÏÍ ÒÅÖÉÍÅ,
-      ÔÁË ÞÔÏ Ñ ÚÁÐÕÓËÁÀ <filename>nb8390.com</filename></para>
-
-    <screen><prompt>C:&gt;</prompt> <userinput>cd \netboot</userinput>
-<prompt>C:&gt;</prompt> <userinput>nb8390</userinput>
-
-<prompt>Boot from Network (Y/N) ?</prompt>  <userinput>Y</userinput>
-
-BOOTP/TFTP/NFS bootstrap loader     ESC for menu
-
-Searching for adapter..
-WD8013EBT base 0x0300, memory 0x000D8000, addr 00:40:01:43:26:66
-
-Searching for server...</screen>
-
-    <para>ôÅÐÅÒØ ÍÏÑ ÂÅÚÄÉÓËÏ×ÁÑ ÓÉÓÔÅÍÁ ÐÙÔÁÅÔÓÑ ÎÁÊÔÉ ÍÁÛÉÎÕ, ËÏÔÏÒÁÑ
-      ×ÙÓÔÕÐÁÅÔ × ËÁÞÅÓÔ×Å ÓÅÒ×ÅÒÁ ÚÁÇÒÕÚËÉ.  úÁÐÏÍÎÉÔÅ ÓÔÒÏËÕ
-      <literal>addr</literal> ×ÙÛÅ, ÐÏÚÖÅ ÏÎÁ ×ÁÍ ÐÏÎÁÄÏÂÉÔÓÑ.  ðÅÒÅÚÁÇÒÕÚÉÔÅ
-      ÂÅÚÄÉÓËÏ×ÕÀ ÓÉÓÔÅÍÕ É ÉÚÍÅÎÉÔÅ ×ÁÛÉ ÆÁÊÌÙ <filename>config.sys</filename>
-      É <filename>autoexec.bat</filename>, ÞÔÏÂÙ ÏÎÉ ×ÙÐÏÌÎÑÌÉ ÜÔÉ ÄÅÊÓÔ×ÉÑ
-      Á×ÔÏÍÁÔÉÞÅÓËÉ.  íÏÖÅÔ ÂÙÔØ, × ÍÅÎÀ.  åÓÌÉ ×Ù ÚÁÐÕÓËÁÌÉ
-      <command>nb3c509.com</command>,  Á ÎÅ <command>nb8390.com</command>, ÔÏ
-      ×Ù×ÏÄÉÍÙÅ ÓÏÏÂÝÅÎÉÑ ÂÕÄÕÔ ÔÏÞÎÏ ÔÁËÉÍÉ ÖÅ.  åÓÌÉ ×Ù ÐÏÌÕÞÉÌÉ ÓÏÏÂÝÅÎÉÅ
-      <errorname>No adapter found</errorname> ÐÏÓÌÅ <literal>Searching for
-      adapter...</literal>, ÐÒÏ×ÅÒØÔÅ ÐÒÁ×ÉÌØÎÏÓÔØ ÚÁÄÁÎÉÑ ÐÁÒÁÍÅÔÒÏ× ×ÒÅÍÅÎÉ
-      ËÏÍÐÉÌÑÃÉÉ × ÆÁÊÌÅ <filename>Makefile</filename>.</para>
-  </sect1>
-
-  <sect1>
-    <title>îÁÓÔÒÏÊËÁ ×ÏÚÍÏÖÎÏÓÔÉ ÓÉÓÔÅÍÁÍ ÚÁÇÒÕÖÁÔØÓÑ ÐÏ ÓÅÔÉ (ÎÁ
-      ÓÅÒ×ÅÒÅ)</title>
-
-    <para>ðÒÏ×ÅÒØÔÅ, ÞÔÏ × ÆÁÊÌÅ <filename>/etc/inetd.conf</filename> ÉÍÅÀÔÓÑ
-      ÚÁÐÉÓÉ ÄÌÑ tftp É bootps.  îÉÖÅ ÐÏËÁÚÁÎÙ ÍÏÉ ÚÁÐÉÓÉ:</para>
-
-    <programlisting>
-tftp	dgram	udp	wait	nobody	/usr/libexec/tftpd	tftpd /tftpboot
-#
-# Additions by who ever you are
-bootps  dgram  udp  wait  root  /usr/libexec/bootpd bootpd /etc/bootptab
-    </programlisting>
-
-    <para>åÓÌÉ ×Ù ÉÚÍÅÎÉÌÉ ÆÁÊÌ <filename>/etc/inetd.conf</filename>, ÔÏ
-      ÐÏÛÌÉÔÅ ÐÒÏÇÒÁÍÍÅ &man.inetd.8; ÓÉÇÎÁÌ <literal>HUP</literal>.  äÌÑ ÜÔÏÇÏ
-      ÎÁÊÄÉÔÅ ID ÐÒÏÃÅÓÓÁ <command>inetd</command> ËÏÍÁÎÄÏÊ <command>ps
-      -ax | grep inetd | grep -v grep</command>.  ðÏÓÌÅ ÜÔÏÇÏ ÐÏÛÌÉÔÅ ÅÍÕ
-      ÓÉÇÎÁÌ <literal>HUP</literal>.  üÔÏ ÄÅÌÁÅÔÓÑ ËÏÍÁÎÄÏÊ <command>kill
-      -HUP &lt;pid&gt;</command>.  üÔÏ ÚÁÓÔÁ×ÉÔ <command>inetd</command>
-      ÐÏ×ÔÏÒÎÏ ÐÒÏÞÅÓÔØ Ó×ÏÊ ËÏÎÆÉÇÕÒÁÃÉÏÎÎÙÊ ÆÁÊÌ.</para>
-
-    <para>îÅ ÚÁÂÙÌÉ ÌÉ ×Ù ÓÔÒÏËÕ Ó <literal>addr</literal> ÉÚ ×Ù×ÏÄÁ ÎÁÞÁÌØÎÏÇÏ
-      ÚÁÇÒÕÚÞÉËÁ ÎÁ ÂÅÚÄÉÓËÏ×ÏÊ ÓÉÓÔÅÍÅ?  ëÁË ×Ù ÍÏÖÅÔÅ ÕÇÁÄÁÔØ, ÔÅÐÅÒØ ÏÎ ×ÁÍ
-      ÔÒÅÂÕÅÔÓÑ.</para>
-
-    <para>äÏÂÁ×ØÔÅ ÚÁÐÉÓØ × ÆÁÊÌ <filename>/etc/bootptab</filename> (ÍÏÖÅÔ
-      ÂÙÔØ, ×ÁÍ ÐÏÔÒÅÂÕÅÔÓÑ ÅÇÏ ÓÏÚÄÁÔØ).  ïÎÁ ÄÏÌÖÎÁ ÉÍÅÔØ ÓÌÅÄÕÀÝÉÊ
-      ×ÉÄ:</para>
-
-    <programlisting>altair:\
-        :ht=ether:\
-        :ha=004001432666:\
-        :sm=255.255.255.0:\
-        :hn:\
-        :ds=199.246.76.1:\
-        :ip=199.246.76.2:\
-        :gw=199.246.76.1:\
-        :vm=rfc1048:</programlisting>
-
-    <para>óÔÒÏËÉ ÉÍÅÀÔ ÔÁËÏÊ ÓÍÙÓÌ:</para>
-
-    <informaltable frame="none" pgwide="1">
-    <tgroup cols="2">
-    <tbody>
-      <row>
-        <entry><literal>altair</literal></entry>
-	<entry>ÎÁÚ×ÁÎÉÅ ÂÅÚÄÉÓËÏ×ÏÊ ÓÉÓÔÅÍÙ ÂÅÚ ÄÏÍÅÎÎÏÊ ÞÁÓÔÉ.</entry>
-      </row>
-
-      <row>
-        <entry><literal>ht=ether</literal></entry>
-        <entry>ÔÉÐ ÏÂÏÒÕÄÏ×ÁÎÉÑ <quote>ethernet</quote>.</entry>
-      </row>
-
-      <row>
-        <entry><literal>ha=004001432666</literal></entry>
-        <entry>ÁÐÐÁÒÁÔÎÙÊ ÁÄÒÅÓ (ÞÉÓÌÏ, ÚÁÐÉÓÁÎÎÏÅ ÒÁÎÅÅ).</entry>
-      </row>
-
-      <row>
-        <entry><literal>sm=255.255.255.0</literal></entry>
-        <entry>ÍÁÓËÁ ÐÏÄÓÅÔÉ.</entry>
-      </row>
-
-      <row>
-        <entry><literal>hn</literal></entry>
-        <entry>ÕËÁÚÙ×ÁÅÔ ÓÅÒ×ÅÒÕ ÐÏÓÙÌÁÔØ ËÌÉÅÎÔÕ ÅÇÏ ÉÍÑ ÈÏÓÔÁ.</entry>
-      </row>
-
-      <row>
-        <entry><literal>ds=199.246.76.1</literal></entry>
-        <entry>ÕËÁÚÙ×ÁÅÔ ËÌÉÅÎÔÕ ÒÁÓÐÏÌÏÖÅÎÉÅ ÓÅÒ×ÅÒÁ ÉÍÅÎ.</entry>
-      </row>
-
-      <row>
-        <entry><literal>ip=199.246.76.2</literal></entry>
-
-        <entry>ÕËÁÚÙ×ÁÅÔ ËÌÉÅÎÔÕ ÅÇÏ IP-ÁÄÒÅÓ.</entry>
-      </row>
-
-      <row>
-        <entry><literal>gw=199.246.76.1</literal></entry>
-        <entry>ÕËÁÚÙ×ÁÅÔ ËÌÉÅÎÔÕ ÍÁÒÛÒÕÔÉÚÁÔÏÒ ÐÏ ÕÍÏÌÞÁÎÉÀ.</entry>
-      </row>
-
-      <row>
-        <entry><literal>vm=...</literal></entry>
-        <entry>ÐÒÏÓÔÏ ÏÓÔÁ×ØÔÅ ÜÔÏ ÔÁË.</entry>
-      </row>
-    </tbody>
-    </tgroup>
-    </informaltable>
-
-    <note>
-      <para>ðÒÏ×ÅÒØÔÅ ÐÒÁ×ÉÌØÎÏÓÔØ ÎÁÓÔÒÏÊËÉ IP-ÁÄÒÅÓÏ×, ÁÄÒÅÓÁ ×ÙÛÅ Ñ×ÌÑÀÔÓÑ
-        ÍÏÉÍÉ.</para>
-    </note>
-
-    <para>óÏÚÄÁÊÔÅ ËÁÔÁÌÏÇ <filename>/tftpboot</filename>, × ËÏÔÏÒÏÍ ÂÕÄÕÔ
-      ÒÁÓÐÏÌÁÇÁÔØÓÑ ËÏÎÆÉÇÕÒÁÃÉÏÎÎÙÅ ÆÁÊÌÙ ÄÌÑ ÂÅÚÄÉÓËÏ×ÙÈ ÓÉÓÔÅÍ, ËÏÔÏÒÙÅ
-      ÂÕÄÅÔ ÏÂÓÌÕÖÉ×ÁÔØ ÓÅÒ×ÅÒ.  üÔÉ ÆÁÊÌÙ ÂÕÄÕÔ ÉÍÅÎÏ×ÁÔØÓÑ
-      <filename>cfg.<replaceable>ip</replaceable></filename>, ÇÄÅ
-      <replaceable>ip</replaceable> Ñ×ÌÑÅÔÓÑ IP-ÁÄÒÅÓÏÍ ÂÅÚÄÉÓËÏ×ÏÊ ÓÉÓÔÅÍÙ.
-      ëÏÎÆÉÇÕÒÁÃÉÏÎÎÙÊ ÆÁÊÌ ÄÌÑ <hostid>altair</hostid> ÂÕÄÅÔ ÎÏÓÉÔØ ÎÁÚ×ÁÎÉÅ
-      <filename>/tftpboot/cfg.199.246.76.2</filename>.  åÇÏ ÓÏÄÅÒÖÉÍÏÅ:</para>
-
-    <programlisting>rootfs 199.246.76.1:/DiskLess/rootfs/altair
-hostname altair.example.com</programlisting>
-
-    <para>óÔÒÏËÁ <literal>hostname altair.example.com</literal> ÐÒÏÓÔÏ
-      ÕËÁÚÙ×ÁÅÔ ÂÅÚÄÉÓËÏ×ÏÊ ÓÉÓÔÅÍŠţ ÐÏÌÎÏÅ ÄÏÍÅÎÎÏÅ ÉÍÑ.</para>
-
-    <para>óÔÒÏËÁ <literal>rootfs 199.246.76.1:/DiskLess/rootfs/altair</literal>
-      ÕËÁÚÙ×ÁÅÔ ÂÅÚÄÉÓËÏ×ÏÊ ÓÉÓÔÅÍÅ ÍÅÓÔÏÐÏÌÏÖÅÎÉÅ ÅÅ ËÏÒÎÅ×ÏÊ ÆÁÊÌÏ×ÏÊ
-      ÓÉÓÔÅÍÙ, ÍÏÎÔÉÒÕÅÍÏÊ ÐÏ ÐÒÏÔÏËÏÌÕ NFS.</para>
-
-    <note>
-      <para>ëÏÒÎÅ×ÁÑ ÆÁÊÌÏ×ÁÑ ÓÉÓÔÅÍÁ, ÍÏÎÔÉÒÕÅÍÁÑ ÞÅÒÅÚ NFS, ÂÕÄÅÔ
-        ÍÏÎÔÉÒÏ×ÁÔØÓÑ × ÒÅÖÉÍÅ <emphasis>ÔÏÌØËÏ ÄÌÑ ÞÔÅÎÉÑ</emphasis>.</para>
-    </note>
-
-    <para>äÅÒÅ×Ï ÄÌÑ ÂÅÚÄÉÓËÏ×ÏÊ ÓÉÓÔÅÍÙ ÍÏÖÅÔ ÂÙÔØ ÓÍÏÎÔÉÒÏ×ÁÎÏ ÐÏ×ÔÏÒÎÏ Ó
-      ÐÒÁ×ÏÍ ÎÁ ×ÙÐÏÌÎÅÎÉÅ ÏÐÅÒÁÃÉÊ ÞÔÅÎÉÑ É ÚÁÐÉÓÉ, ÅÓÌÉ ÜÔÏ
-      ÐÏÔÒÅÂÕÅÔÓÑ.</para>
-
-    <para>ñ ÉÓÐÏÌØÚÕÀ Ó×ÏÊ ÎÉËÏÍÕ ÎÅ ÎÕÖÎÙÊ 386DX-40 × ËÁÞÅÓÔ×Å ×ÙÄÅÌÅÎÎÏÇÏ
-      X-ÔÅÒÍÉÎÁÌÁ.</para>
-
-    <para>äÅÒÅ×Ï ÄÌÑ <hostid>altair</hostid> ÉÍÅÅÔ ÔÁËÏÊ ×ÉÄ:</para>
-
-    <literallayout>/
-/bin
-/etc
-/tmp
-/sbin
-/dev
-/dev/fd
-/usr
-/var
-/var/run</literallayout>
-
-    <para>÷ÏÔ ÒÅÁÌØÎÙÊ ÓÐÉÓÏË ÆÁÊÌÏ×:</para>
-
-    <screen>
--r-xr-xr-x  1 root  wheel  779984 Dec 11 23:44 ./kernel
--r-xr-xr-x  1 root    bin  299008 Dec 12 00:22 ./bin/sh
--rw-r--r--  1 root  wheel     499 Dec 15 15:54 ./etc/rc
--rw-r--r--  1 root  wheel    1411 Dec 11 23:19 ./etc/ttys
--rw-r--r--  1 root  wheel     157 Dec 15 15:42 ./etc/hosts
--rw-r--r--  1 root    bin    1569 Dec 15 15:26 ./etc/XF86Config.altair
--r-x------  1 bin     bin  151552 Jun 10  1995 ./sbin/init
--r-xr-xr-x  1 bin     bin  176128 Jun 10  1995 ./sbin/ifconfig
--r-xr-xr-x  1 bin     bin  110592 Jun 10  1995 ./sbin/mount_nfs
--r-xr-xr-x  1 bin     bin  135168 Jun 10  1995 ./sbin/reboot
--r-xr-xr-x  1 root    bin   73728 Dec 13 22:38 ./sbin/mount
--r-xr-xr-x  1 root  wheel    1992 Jun 10  1995 ./dev/MAKEDEV.local
--r-xr-xr-x  1 root  wheel   24419 Jun 10  1995 ./dev/MAKEDEV
-    </screen>
-
-    <para>åÓÌÉ ×Ù ÎÅ ÉÓÐÏÌØÚÕÅÔÅ &man.devfs.5; (ËÏÔÏÒÁÑ ×Ï FreeBSD&nbsp;5.X
-      ÐÏ ÕÍÏÌÞÁÎÉÀ ÁËÔÉ×ÉÒÏ×ÁÎÁ), ÔÏ ÄÏÌÖÎÙ ÕÂÅÄÉÔØÓÑ, ÞÔÏ ÚÁÐÕÓËÁÌÉ ËÏÍÁÎÄÕ
-      <command>MAKEDEV all</command> × ËÁÔÁÌÏÇÅ
-      <filename>dev</filename>.</para>
-
-    <para>íÏÊ <filename>/etc/rc</filename> ÄÌÑ <hostid>altair</hostid> ×ÙÇÌÑÄÉÔ
-      ×ÏÔ ÔÁË:</para>
-
-<programlisting>#!/bin/sh
-#
-PATH=/bin:/
-export PATH
-#
-# configure the localhost
-/sbin/ifconfig lo0 127.0.0.1
-#
-# configure the ethernet card
-/sbin/ifconfig ed0 199.246.76.2 netmask 0xffffff00
-#
-# mount the root filesystem via NFS
-/sbin/mount antares:/DiskLess/rootfs/altair /
-#
-# mount the /usr filesystem via NFS
-/sbin/mount antares:/DiskLess/usr /usr
-#
-/usr/X11R6/bin/XF86_SVGA -query antares -xf86config /etc/XF86Config.altair > /dev/null 2&gt;&amp;1
-#
-# Reboot after X exits
-/sbin/reboot
-#
-# We blew up....
-exit 1</programlisting>
-
-    <para>ðÒÉ×ÅÔÓÔ×ÕÀÔÓÑ ÌÀÂÙÅ ÚÁÍÅÞÁÎÉÑ É ×ÏÐÒÏÓÙ.</para>
-  </sect1>
-</article>
diff --git a/ru_RU.KOI8-R/articles/euro/Makefile b/ru_RU.KOI8-R/articles/euro/Makefile
deleted file mode 100644
index 144f94fb10..0000000000
--- a/ru_RU.KOI8-R/articles/euro/Makefile
+++ /dev/null
@@ -1,23 +0,0 @@
-#
-# The FreeBSD Russian Documentation Project
-#
-# $FreeBSD$
-# $FreeBSDru: frdp/doc/ru_RU.KOI8-R/articles/euro/Makefile,v 1.3 2005/06/12 06:08:28 gad Exp $
-#
-# Original revision: r21827
-#
-# Article: The Euro Symbol on FreeBSD
-
-DOC?= article
-
-FORMATS?= html
-
-INSTALL_COMPRESSED?=gz
-INSTALL_ONLY_COMPRESSED?=
-
-SRCS= 	article.sgml
-
-URL_RELPREFIX?=		../../../..
-DOC_PREFIX?= ${.CURDIR}/../../..
-
-.include "${DOC_PREFIX}/share/mk/doc.project.mk"
diff --git a/ru_RU.KOI8-R/articles/euro/article.sgml b/ru_RU.KOI8-R/articles/euro/article.sgml
deleted file mode 100644
index f37754ef59..0000000000
--- a/ru_RU.KOI8-R/articles/euro/article.sgml
+++ /dev/null
@@ -1,361 +0,0 @@
-<?xml version="1.0" encoding="koi8-r" standalone="no"?>
-<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V4.2-Based Extension//EN"
-	"../../../share/sgml/freebsd42.dtd" [
-<!ENTITY % entities PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Entity Set//RU" "../../share/sgml/entities.ent">
-%entities;
-]>
-
-<!--
-     The FreeBSD Russian Documentation Project
-
-     $FreeBSDru: frdp/doc/ru_RU.KOI8-R/articles/euro/article.sgml,v 1.8 2006/02/09 14:56:27 marck Exp $
-
-     Original revision: r38182
--->
-
-<article lang="ru">
-  <articleinfo>
-    <title>óÉÍ×ÏÌ Å×ÒÏ ×Ï <systemitem
-      class="osname">FreeBSD</systemitem></title>
-
-    <authorgroup>
-      <author>
-	<firstname>Aaron</firstname>
-
-	<surname>Kaplan</surname>
-
-	<affiliation>
-	  <address>
-	    <email>aaron@lo-res.org</email>
-	  </address>
-	</affiliation>
-      </author>
-    </authorgroup>
-
-    <copyright>
-      <year>2002</year>
-      <year>2003</year>
-      <holder>The FreeBSD Documentation Project</holder>
-    </copyright>
-
-    <legalnotice id="trademarks" role="trademarks">
-      &tm-attrib.freebsd;
-      &tm-attrib.general;
-    </legalnotice>
-
-    <pubdate>$FreeBSD$</pubdate>
-
-    <releaseinfo>$FreeBSD$</releaseinfo>
-
-    <abstract>
-      <para>÷ ÜÔÏÍ ÄÏËÕÍÅÎÔÅ ÂÕÄÅÔ ÓÄÅÌÁÎÁ ÐÏÐÙÔËÁ ÐÏÍÏÞØ ×ÁÍ ÎÁÞÁÔØ ÒÁÂÏÔÕ Ó
-	ÎÏ×ÙÍ ÓÉÍ×ÏÌÏÍ <keycap>Euro</keycap> ÎÁ ×ÁÛÅÊ ÎÏ×ÏÊ ËÌÁ×ÉÁÔÕÒÅ, ËÏÔÏÒÕÀ
-	×Ù ËÕÐÉÌÉ × ÎÁÞÁÌÅ 2002 ÇÏÄÁ ÄÌÑ ÐÅÒÅÈÏÄÁ ÎÁ ÎÏ×ÕÀ ÏÂÝÕÀ ×ÁÌÀÔÕ.
-	óÎÁÞÁÌÁ ÍÙ ÓËÏÎÃÅÎÔÒÉÒÕÅÍÓÑ ÎÁ ÂÏÌÅÅ ×ÁÖÎÙÈ ×ÏÐÒÏÓÁÈ, ÔÁËÉÈ, ËÁË
-	ÐÒÁ×ÉÌØÎÏÅ ÏÔÏÂÒÁÖÅÎÉÅ ÓÉÍ×ÏÌÁ ÎÁ ËÏÎÓÏÌÉ.  ðÏÓÌÅÄÕÀÝÉÅ ÒÁÚÄÅÌÙ
-	ÐÏÓ×ÑÝÅÎÙ ÎÁÓÔÒÏÊËÅ ËÏÎËÒÅÔÎÙÈ ÐÒÏÇÒÁÍÍ ÔÉÐÁ
-	<application>X11</application>.</para>
-
-      <para>íÎÏÇÏ ÐÏÌÅÚÎÏÊ ÉÎÆÏÒÍÁÃÉÉ ÂÙÌÏ ÐÏÌÕÞÅÎÏ ÏÔ Oliver Fromme, Tom
-	Rhodes É ÍÎÏÇÉÈ ÄÒÕÇÉÈ.  óÐÁÓÉÂÏ!  âÅÚ ×ÁÓ ÜÔÏÊ ÓÔÁÔØÉ ÂÙ ÎÅ
-	ÂÙÌÏ!</para>
-    </abstract>
-  </articleinfo>
-
-  <sect1>
-    <title>ï å×ÒÏ ×ËÒÁÔÃÅ</title>
-
-    <para>åÓÌÉ ×Ù ÕÖÅ ÞÕ×ÓÔ×ÕÅÔÅ ÓÅÂÑ Õ×ÅÒÅÎÎÏ ÐÒÉ ÒÁÂÏÔÅ Ó <ulink
-      url="&url.books.handbook;/l10n.html">ÌÏËÁÌÉÚÁÃÉÅÊ</ulink>, ËÁË ÏÎÁ
-      ÏÐÉÓÁÎÁ ×Ï òÕËÏ×ÏÄÓÔ×Å ÐÏ <systemitem
-      class="osname">FreeBSD</systemitem>, ÔÏ ×ÁÓ ÍÏÇÕÔ ÚÁÉÎÔÅÒÅÓÏ×ÁÔØ ÔÏÌØËÏ
-      ÓÌÅÄÕÀÝÉÅ ÆÁËÔÙ, ËÏÔÏÒÙÅ ÐÏÍÏÇÕÔ ×ÁÍ ÂÙÓÔÒÏ ×ÎÉËÎÕÔØ × ÓÕÔØ:</para>
-
-    <variablelist>
-      <varlistentry>
-	<term>ISO8859-15</term>
-
-	<listitem>
-	  <para>üÔÏ ÎÅÓËÏÌØËÏ ÍÏÄÉÆÉÃÉÒÏ×ÁÎÎÁÑ ×ÅÒÓÉÑ ÛÉÒÏËÏ ÉÓÐÏÌØÚÕÅÍÏÇÏ
-	    ÎÁÂÏÒÁ ÓÉÍ×ÏÌÏ× ISO8859-1.  ÷ ÎÅÇÏ ×ËÌÀÞÅÎ ÓÉÍ×ÏÌ å×ÒÏ.
-	    éÓÐÏÌØÚÕÅÔÓÑ ÄÌÑ ÚÁÄÁÎÉÑ ÐÅÒÅÍÅÎÎÙÈ ÏËÒÕÖÅÎÉÑ <envar>LANG</envar> É
-	    <envar>LC_CTYPE</envar>.</para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-	<term><filename>iso15-8x16.fnt</filename></term>
-
-	<listitem>
-	  <para>ûÒÉÆÔ &man.vidcontrol.1; ÄÌÑ ËÏÎÓÏÌÉ</para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-	<term><filename>/usr/share/syscons/keymaps/*.iso.kbd</filename></term>
-
-	<listitem>
-	  <para>ëÌÁ×ÉÁÔÕÒÎÙÅ ÒÁÓËÌÁÄËÉ, ÓÏÏÔ×ÅÔÓÔ×ÕÀÝÉÅ ×ÁÛÅÍÕ ÑÚÙËÕ.  õËÁÖÉÔÅ
-	    ÏÄÎÕ ÉÚ ÎÉÈ × ËÁÞÅÓÔ×Å ÚÎÁÞÅÎÉÑ ÄÌÑ ÐÁÒÁÍÅÔÒÁ
-	    <literal>keymap</literal> ÉÚ ÆÁÊÌÁ
-	    <filename>rc.conf</filename>.</para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-	<term><envar>LC_CTYPE</envar></term>
-
-	<listitem>
-	  <para>éÓÐÏÌØÚÕÅÔÓÑ ÄÌÑ ÕËÁÚÁÎÉÑ ÐÒÁ×ÉÌØÎÏÇÏ ÔÉÐÁ ÓÉÍ×ÏÌÏ× ÐÒÉ ×ÁÛÅÊ
-	    ÌÏËÁÌÉÚÁÃÉÉ.</para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-	<term><literal>XkbLayout "<replaceable>lang</replaceable>(euro)"</literal></term>
-
-	<listitem>
-	  <para>ðÁÒÁÍÅÔÒ ÎÁÓÔÒÏÊËÉ <application>Xorg</application>.</para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-	<term><filename>/etc/X11/xorg.conf</filename></term>
-	<listitem>
-	  <para>ïÂÑÚÁÔÅÌØÎÏ ÐÒÉ×ÅÄÉÔÅ ×ÁÛÉ ÛÒÉÆÔÙ ÄÌÑ X11 Ë ×ÉÄÕ
-	    <literal>-*-..-*-iso8859-15</literal></para>
-	</listitem>
-      </varlistentry>
-    </variablelist>
-  </sect1>
-
-  <sect1 id="general">
-    <title>ïÂÝÅÅ ÚÁÍÅÞÁÎÉÅ</title>
-
-    <para>÷ ÐÏÓÌÅÄÕÀÝÉÈ ÒÁÚÄÅÌÁÈ ÍÙ ÂÕÄÅÍ ÞÁÓÔÏ ÏÂÒÁÝÁÔØÓÑ Ë ÔÅÒÍÉÎÕ
-      <emphasis>ISO8859-15</emphasis>.  üÔÏ ÓÔÁÎÄÁÒÔÎÏÅ ÏÂÏÚÎÁÞÅÎÉÅ ÎÁÞÉÎÁÑ Ó
-      <systemitem class="osname">FreeBSD</systemitem> 4.5.  ÷ ÂÏÌÅÅ ÓÔÁÒÙÈ
-      ×ÅÒÓÉÑÈ ÓÔÁÎÄÁÒÔÎÙÍ ÏÂÏÚÎÁÞÅÎÉÅÍ ÂÙÌÏ <emphasis>ISO_8859-15</emphasis>
-      ÉÌÉ <emphasis>DIS_8859-15</emphasis>.</para>
-
-    <para>åÓÌÉ ×Ù ÉÓÐÏÌØÚÕÅÔÅ ÂÏÌÅÅ ÓÔÁÒÕÀ ×ÅÒÓÉÀ <systemitem
-      class="osname">FreeBSD</systemitem>, ÏÂÑÚÁÔÅÌØÎÏ ÐÏÓÍÏÔÒÉÔÅ × ËÁÔÁÌÏÇÅ
-      <filename>/usr/share/locale/</filename>, ËÁËÏÅ ÉÓÐÏÌØÚÕÅÔÓÑ ÓÏÇÌÁÛÅÎÉÅ ÐÏ
-      ÎÁÉÍÅÎÏ×ÁÎÉÀ.</para>
-  </sect1>
-
-  <sect1 id="console">
-    <title>ëÏÎÓÏÌØ</title>
-
-    <sect2>
-      <title>îÁÓÔÒÏÊËÁ ÛÒÉÆÔÁ ÄÌÑ ËÏÎÓÏÌÉ</title>
-
-      <para>÷ ÚÁ×ÉÓÉÍÏÓÔÉ ÏÔ ÒÁÚÒÅÛÅÎÉÑ ×ÁÛÅÊ ËÏÎÓÏÌÉ É Å£ ÒÁÚÍÅÒÁ ×ÁÍ ÎÕÖÎÏ
-	ÚÁÄÁÔØ ÏÄÎÕ ÉÚ ÔÁËÉÈ ÓÔÒÏË × <filename>rc.conf</filename>:</para>
-
-      <programlisting>font8x16="iso15-8x16.fnt" # ÉÚ /usr/share/syscons/fonts/*
-font8x14="iso15-8x14.fnt"
-font8x8="iso15-8x8.fnt"</programlisting>
-
-      <para>üÔÏ ÐÒÉ×ÅÄ£Ô Ë ×ÙÂÏÒÕ ÛÒÉÆÔÁ ISO8859-15, ÉÚ×ÅÓÔÎÏÍÕ ÔÁËÖÅ ËÁË
-	Latin-9.  ISO8859-15 Ñ×ÌÑÅÔÓÑ ×ÁÒÉÁÎÔÏÍ ISO8859-1.  ÷Ù ÍÏÖÅÔÅ Õ×ÉÄÅÔØ
-	ÒÁÚÎÉÃÕ ÍÅÖÄÕ ÎÉÍÉ, ÐÏÓÍÏÔÒÅ× ÎÁ ÓÉÍ×ÏÌ å×ÒÏ: ÅÇÏ ÄÅÓÑÔÉÞÎÏÅ ÚÎÁÞÅÎÉÅ
-	ÒÁ×ÎÏ 164.  ÷ ISO8859-1 ×Ù Õ×ÉÄÉÔÅ ËÒÕÖÏË Ó ÞÅÔÙÒØÍÑ ÐÏÌÏÓËÁÍÉ ÐÏ
-	ÕÇÌÁÍ.  þÁÓÔÏ ÏÎ ÎÁÚÙ×ÁÅÔÓÑ <quote>ÕÎÉ×ÅÒÓÁÌØÎÙÍ ÓÉÍ×ÏÌÏÍ ×ÁÌÀÔÙ</quote>.  ÷
-	ISO8859-15 ÍÅÓÔÏ ÍÁÌÅÎØËÏÇÏ ËÒÕÖËÁ ÚÁÎÉÍÁÅÔ ÓÉÍ×ÏÌ å×ÒÏ.  åÓÌÉ ÅÇÏ ÎÅÔ,
-	ÔÏ ÛÒÉÆÔÙ ÂÏÌÅÅ ÉÌÉ ÍÅÎÅÅ ÉÄÅÎÔÉÞÎÙ.</para>
-
-      <warning>
-	<para>îÁ ÍÏÍÅÎÔ ÎÁÐÉÓÁÎÉÑ ÜÔÏÇÏ ÄÏËÕÍÅÎÔÁ ÅÄÉÎÓÔ×ÅÎÎÙÍ ÐÒÉÇÏÄÎÙÍ Ë
-	  ÉÓÐÏÌØÚÏ×ÁÎÉÀ ÛÒÉÆÔÏÍ ÂÙÌ <literal>iso15-8x16.fnt</literal>.  äÒÕÇÉÅ
-	  ×ÙÄÁ×ÁÌÉ ISO8859-1, ÈÏÔÑ ÎÁÚ×ÁÎÉÅ ÇÏ×ÏÒÉÌÏ Ï ÄÒÕÇÏÍ.</para>
-      </warning>
-
-      <note>
-	<para>ðÏÓÌÅ ÚÁÄÁÎÉÑ ÜÔÏÇÏ ÛÒÉÆÔÁ ÓÏÏÂÝÅÎÉÑ ÎÅËÏÔÏÒÙÈ ËÏÎÓÏÌØÎÙÈ
-	  ÐÒÉÌÏÖÅÎÉÊ ÂÕÄÕÔ ×ÙÇÌÑÄÅÔØ ÉÓËÁÖ£ÎÎÙÍÉ.  üÔÏ ÐÒÏÉÓÈÏÄÉÔ × ÓÉÌÕ ÔÏÇÏ,
-	  ÞÔÏ ÏÎÉ ÐÒÅÄÐÏÌÁÇÁÀÔ ÉÓÐÏÌØÚÏ×ÁÎÉÅ ÄÒÕÇÏÇÏ ÛÒÉÆÔÁ/ÎÁÂÏÒÁ ÓÉÍ×ÏÌÏ×,
-	  ÔÁËÏÇÏ, ËÁË ANSI 850.  ïÄÎÉÍ ÉÚ ÐÒÉÍÅÒÏ× ÍÏÖÅÔ ×ÙÓÔÕÐÁÔØ
-	  <application>sysinstall</application>.  ïÄÎÁËÏ × ÂÏÌØÛÉÎÓÔ×Å
-	  ÓÌÕÞÁÅ× ÜÔÏ ÎÅ ÉÍÅÅÔ ÂÏÌØÛÏÇÏ ÚÎÁÞÅÎÉÑ É ÓÉÌØÎÏ ÎÅ ÂÅÓÐÏËÏÉÔ.</para>
-      </note>
-
-      <para>óÌÅÄÕÀÝÉÍ ÛÁÇÏÍ ×Ù ÄÏÌÖÎÙ ÌÉÂÏ ÐÅÒÅÚÁÇÒÕÚÉÔØ ×ÁÛÕ ÓÉÓÔÅÍÕ ÄÌÑ ÔÏÇÏ,
-	ÞÔÏÂÙ ÉÚÍÅÎÅÎÉÑ ×ÓÔÕÐÉÌÉ × ÓÉÌÕ, ÌÉÂÏ (×ÒÕÞÎÕÀ) ×ÙÐÏÌÎÉÔØ ÔÅ ÄÅÊÓÔ×ÉÑ,
-	ËÏÔÏÒÙÅ ÐÒÏÉÓÈÏÄÑÔ ÐÒÉ ÎÁÞÁÌÅ ÒÁÂÏÔÙ ÓÉÓÔÅÍÙ:</para>
-
-      <screen>&prompt.user; <userinput>vidcontrol -f <replaceable>iso15-8x16.fnt</replaceable></userinput></screen>
-
-      <para>äÌÑ ÐÒÏ×ÅÒËÉ ÔÏÇÏ, ÂÙÌ ÌÉ ×ÙÂÒÁÎ ÛÒÉÆÔ, ×ÙÐÏÌÎÉÔÅ ÔÁËÏÊ ËÏÒÏÔËÉÊ
-	ÓËÒÉÐÔ ÎÁ ÑÚÙËÅ <command><anchor id="awk-test"/>awk</command>:</para>
-
-      <programlisting>#!/usr/bin/awk -f
-BEGIN {
-        for(i=160;i&lt;180;i++)
-                printf"%3d %c\n",i,i
-}</programlisting>
-
-      <para>÷ ÒÅÚÕÌØÔÁÔÅ ÚÎÁË å×ÒÏ ÄÏÌÖÅÎ ÂÙÔØ × ÐÏÚÉÃÉÉ 164.</para>
-    </sect2>
-
-    <sect2>
-      <title>îÁÓÔÒÏÊËÁ ×ÁÛÅÊ ËÌÁ×ÉÁÔÕÒÙ ÎÁ ÉÓÐÏÌØÚÏ×ÁÎÉÅ å×ÒÏ</title>
-
-      <para>âÏÌØÛÉÎÓÔ×Ï ËÌÁ×ÉÁÔÕÒÎÙÈ ÒÁÓËÌÁÄÏË ÕÖÅ ÄÏÌÖÎÏ ÂÙÔØ ËÏÒÒÅËÔÎÏ
-	ÎÁÓÔÒÏÅÎÏ.  äÒÕÇÉÍÉ ÓÌÏ×ÁÍÉ: åÓÌÉ Õ ×ÁÓ ÎÅÍÅÃËÁÑ ËÌÁ×ÉÁÔÕÒÁ É ×ÁÛÉ
-	ËÌÁ×ÉÛÉ Ó ÕÍÌÑÕÔÁÍÉ ÒÁÂÏÔÁÀÔ, ÔÏ ×Ù ÍÏÖÅÔÅ ÐÒÏÐÕÓÔÉÔØ ÜÔÏÔ ÒÁÚÄÅÌ, ÔÁË
-	ËÁË ËÌÁ×ÉÁÔÕÒÁ ÕÖÅ ÏÔÏÂÒÁÖÁÅÔ ËÁËÕÀ-ÔÏ ËÏÍÂÉÎÁÃÉÀ ËÌÁ×ÉÛ (Ë
-	ÐÒÉÍÅÒÕ: <keycombo action="simul"><keycap>Alt Gr</keycap>
-	<keycap>e</keycap></keycombo>) × ÓÉÍ×ÏÌ Ó ÄÅÓÑÔÉÞÎÙÍ ÚÎÁÞÅÎÉÅÍ 164.
-	åÓÌÉ ×Ù ÓÔÁÌËÉ×ÁÅÔÅÓØ Ó ÐÒÏÂÌÅÍÁÍÉ, ÌÕÞÛÅ ×ÓÅÇÏ ÐÒÏ×ÅÒÉÔØ × ËÁÔÁÌÏÇÅ
-	<filename>/usr/share/syscons/keymaps/*.kbd</filename>.  æÏÒÍÁÔ ÆÁÊÌÏ×
-	ÒÁÓËÌÁÄÏË ËÌÁ×ÉÁÔÕÒÙ ÏÐÉÓÁÎ × &man.keyboard.4;.  õÔÉÌÉÔÁ
-	&man.kbdcontrol.1; ÍÏÖÅÔ ÉÓÐÏÌØÚÏ×ÁÔØÓÑ ÄÌÑ ÚÁÇÒÕÚËÉ ÐÏÌØÚÏ×ÁÔÅÌØÓËÉÈ
-	ËÌÁ×ÉÁÔÕÒÎÙÈ ÒÁÓËÌÁÄÏË.</para>
-
-      <para>ðÏÓÌÅ ×ÙÂÏÒÁ ÐÒÁ×ÉÌØÎÏÊ ËÌÁ×ÉÁÔÕÒÎÏÊ ÒÁÓËÌÁÄËÉ ÏÎÁ ÄÏÌÖÎÁ ÂÙÔØ
-	ÕËÁÚÁÎÁ × ÆÁÊÌÅ	<filename>/etc/rc.conf</filename> ÔÁËÏÊ ÓÔÒÏËÏÊ:</para>
-
-      <programlisting>keymap="<replaceable>german.iso</replaceable>" # or another map</programlisting>
-
-      <para>ëÁË ÕËÁÚÁÎÏ ×ÙÛÅ, ÜÔÏÔ ÛÁÇ, ÓËÏÒÅÅ ×ÓÅÇÏ, ÂÙÌ ÕÖÅ ×ÁÍÉ ×ÙÐÏÌÎÅÎ ×Ï
-	×ÒÅÍÑ ÕÓÔÁÎÏ×ËÉ (× <application>sysinstall</application>).  åÓÌÉ ÜÔÏ ÎÅ
-	ÔÁË, ÌÉÂÏ ÐÅÒÅÚÁÇÒÕÚÉÔÅÓØ, ÌÉÂÏ ÚÁÇÒÕÚÉÔÅ ÎÏ×ÕÀ ËÌÁ×ÉÁÔÕÒÎÕÀ ÒÁÓËÌÁÄËÕ
-	ÐÏÓÒÅÄÓÔ×ÏÍ &man.kbdcontrol.1;.</para>
-
-      <para>äÌÑ ÐÒÏ×ÅÒËÉ ÒÁÓËÌÁÄËÉ ËÌÁ×ÉÁÔÕÒÙ, ÐÅÒÅËÌÀÞÉÔÅÓØ ÎÁ ÄÒÕÇÕÀ ËÏÎÓÏÌØ
-	É × ÐÒÉÇÌÁÛÅÎÉÉ ÎÁ ×ÈÏÄ × ÓÉÓÔÅÍÕ <emphasis>×ÍÅÓÔÏ ÉÍÅÎÉ
-	×ÈÏÄÁ</emphasis> ÐÏÐÒÏÂÕÊÔÅ ÎÁÂÒÁÔØ ËÌÁ×ÉÛÕ <keycap>Euro</keycap>.
-	åÓÌÉ ÏÎÁ ÎÅ ÒÁÂÏÔÁÅÔ, ÏÔÐÒÁ×ØÔÅ ÓÏÏÂÝÅÎÉÅ Ï ÏÛÉÂËÅ ÞÅÒÅÚ
-	&man.send-pr.1; ÌÉÂÏ ÐÒÏ×ÅÒØÔÅ, ÞÔÏ ×Ù ÄÅÊÓÔ×ÉÔÅÌØÎÏ ×ÙÂÒÁÌÉ ÐÒÁ×ÉÌØÎÕÀ
-	ÒÁÓËÌÁÄËÕ ËÌÁ×ÉÁÔÕÒÙ.</para>
-
-      <note>
-	<para>îÁ ÜÔÏÍ ÜÔÁÐÅ ËÌÁ×ÉÛÁ Euro ÅÝ£ ÎÅ ÒÁÂÏÔÁÅÔ ×
-	  <application>bash</application> ÉÌÉ
-	  <application>tcsh</application>.</para>
-      </note>
-    </sect2>
-
-    <sect2>
-      <title>éÓÐÒÁ×ÌÅÎÉÅ ÐÅÒÅÍÅÎÎÙÈ ÏËÒÕÖÅÎÉÑ</title>
-
-      <para>ëÏÍÁÎÄÎÙÅ ÐÒÏÃÅÓÓÏÒÙ (<application>bash</application>, <application>tcsh</application>) ÏÂÒÁÝÁÀÔÓÑ Ë ÂÉÂÌÉÏÔÅËÅ
-	&man.readline.3;, ËÏÔÏÒÁÑ, × Ó×ÏÀ ÏÞÅÒÅÄØ, ÉÓÐÏÌØÚÕÅÔ ÐÅÒÅÍÅÎÎÕÀ
-	ÏËÒÕÖÅÎÉÑ <envar>LC_CTYPE</envar>.  <envar>LC_CTYPE</envar> ÄÏÌÖÎÁ ÂÙÔØ
-	ÚÁÄÁÎÁ ÄÏ ÐÏÌÎÏÇÏ ÚÁÐÕÓËÁ ÏÂÏÌÏÞËÉ.  ë ÓÞÁÓÔØÀ, ÄÌÑ ÜÔÏÇÏ ÄÏÓÔÁÔÏÞÎÏ
-	ÄÏÂÁ×ÉÔØ ÓÔÒÏËÕ:</para>
-
-      <programlisting>export LC_CTYPE=<replaceable>de_DE</replaceable>.ISO8859-15</programlisting>
-
-      <para>× ×ÁÛ <filename>.bash_profile</filename> (<application>bash</application>), ÉÌÉ:</para>
-
-      <programlisting>setenv LC_CTYPE <replaceable>de_DE</replaceable>.ISO8859-15</programlisting>
-
-      <para>× ×ÁÛ ÆÁÊÌ <filename>.login</filename> (tcsh).  ëÏÎÅÞÎÏ ÖÅ,
-	<replaceable>de_DE</replaceable> ÄÏÌÖÎÏ ÂÙÔØ ÚÁÍÅÎÅÎÏ ÎÁ ÔÏ, ÞÔÏ
-	ÓÏÏÔ×ÅÔÓÔ×ÕÅÔ ×ÁÛÅÍÕ ÑÚÙËÕ.  úÁÔÅÍ ÚÁ×ÅÒÛÉÔÅ ÒÁÂÏÔÕ Ó ÓÉÓÔÅÍÏÊ, ×ÏÊÄÉÔÅ
-	× ÓÉÓÔÅÍÕ ÓÎÏ×Á É ÐÒÏ×ÅÒØÔÅ, ÞÔÏ ËÌÁ×ÉÛÁ å×ÒÏ ÒÁÂÏÔÁÅÔ.  ôÅÐÅÒØ
-	ÂÏÌØÛÉÎÓÔ×Ï ËÏÎÓÏÌØÎÙÈ ÐÒÉÌÏÖÅÎÉÊ ÄÏÌÖÎÏ ×ÏÓÐÒÉÎÉÍÁÔØ ËÌÁ×ÉÛÕ å×ÒÏ.
-	ïÄÎÁËÏ ÄÌÑ ÓÐÅÃÉÁÌÉÚÉÒÏ×ÁÎÎÙÈ ÐÒÏÇÒÁÍÍ, ÔÁËÉÈ, ËÁË, ÎÁÐÒÉÍÅÒ,
-	<application>pine</application>, ÍÏÇÕÔ ÐÏÔÒÅÂÏ×ÁÔØÓÑ ÄÏÐÏÌÎÉÔÅÌØÎÙÅ
-	ÛÁÇÉ ÐÏ ÉÈ ÎÁÓÔÒÏÊËÅ.</para>
-
-      <note>
-	<para>áÌØÔÅÒÎÁÔÉ×ÏÊ ÉÚÍÅÎÅÎÉÀ <filename>.login</filename> É
-	  <filename>.bash_profile</filename> Ñ×ÌÑÅÔÓÑ ÚÁÄÁÎÉÅ ÐÅÒÅÍÅÎÎÙÈ
-	  ÏËÒÕÖÅÎÉÑ ÞÅÒÅÚ ÍÅÈÁÎÉÚÍ &man.login.conf.5;.  üÔÏÔ ÐÏÄÈÏÄ ÉÍÅÅÔ
-	  ÐÒÅÉÍÕÝÅÓÔ×Ï × ÎÁÚÎÁÞÅÎÉÉ ËÌÁÓÓÏ× ×ÈÏÄÁ × ÓÉÓÔÅÍÕ ÏÐÒÅÄÅÌÅÎÎÙÍ
-	  ÐÏÌØÚÏ×ÁÔÅÌÑÍ (Ë ÐÒÉÍÅÒÕ, ÆÒÁÎÃÕÚÁÍ, ÉÔÁÌØÑÎÃÁÍ, É ÔÁË ÄÁÌÅÅ)
-	  <emphasis>× ÏÄÎÏÍ ÍÅÓÔÅ</emphasis>.</para>
-      </note>
-    </sect2>
-  </sect1>
-
-  <sect1 id="x11">
-    <title>îÁÓÔÒÏÊËÁ X11</title>
-
-    <para>éÚÍÅÎÉÔÅ <filename>/etc/X11/xorg.conf</filename> ÓÌÅÄÕÀÝÉÍ
-      ÏÂÒÁÚÏÍ:</para>
-
-    <programlisting>Option "XkbLayout"  "<replaceable>de</replaceable>(euro)"</programlisting>
-
-    <para>é ÓÎÏ×Á, ÚÁÍÅÎÉÔÅ <replaceable>de</replaceable> ÎÁ ÔÏ, ÞÔÏ
-      ÓÏÏÔ×ÅÔÓÔ×ÕÅÔ ×ÁÛÅÍÕ ÑÚÙËÕ.  ó ÜÔÏÇÏ ÍÏÍÅÎÔÁ ËÌÁ×ÉÁÔÕÒÁ ÄÏÌÖÎÁ ÂÙÔØ
-      ÎÁÓÔÒÏÅÎÁ ÐÒÁ×ÉÌØÎÏ.  ëÁË É × ÒÁÚÄÅÌÅ Ï ËÏÎÓÏÌÉ, ÄÏÌÖÅÎ ÂÙÔØ ×ÙÂÒÁÎ
-      ÐÒÁ×ÉÌØÎÙÊ ÛÒÉÆÔ.  ÷ ÓÌÕÞÁÅ <application>KDE</application> ÐÅÒÅÊÄÉÔÅ Ë
-      <application>KDE control center</application> -&gt;
-      Personalization -&gt; Country &amp; Language -&gt; Charset É ÓÍÅÎÉÔÅ ÅÇÏ
-      ÎÁ <literal>ISO8859-15</literal>.  ðÏÄÏÂÎÙÅ ÖÅ ÛÁÇÉ ÄÏÌÖÎÙ ÂÙÔØ ×ÙÐÏÌÎÅÎÙ
-      ÄÌÑ <application>kmail</application> É ÄÒÕÇÉÈ ÐÒÉÌÏÖÅÎÉÊ.</para>
-
-    <para>äÒÕÇÉÍ ÈÏÒÏÛÉÍ ÓÐÏÓÏÂÏÍ Ñ×ÌÑÅÔÓÑ ÉÚÍÅÎÅÎÉÅ ×ÁÛÉÈ ÆÁÊÌÏ×
-      <filename>fonts.alias</filename>.  óÌÅÄÕÅÔ ÏÔÍÅÔÉÔØ, ÞÔÏ ÛÒÉÆÔ
-      <literal>fixed</literal> ÄÏÌÖÅÎ ÂÙÔØ ÉÚÍÅÎÅÎ ÎÁ ÐÒÁ×ÉÌØÎÙÊ ÎÁÂÏÒ
-      ÓÉÍ×ÏÌÏ×: ÆÁÊÌ Á×ÔÏÒÁ
-      <filename>/usr/X11R6/lib/X11/fonts/misc/fonts.alias</filename> ×ÙÇÌÑÄÉÔ
-      ÐÒÉÍÅÒÎÏ ÔÁË:</para>
-
-     <programlisting>! $Xorg: fonts.alias,v 1.3 2000/08/21 16:42:31 coskrey Exp $
-fixed   -misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-iso8859-15
-variable -*-helvetica-bold-r-normal-*-*-120-*-*-*-*-iso8859-15
-(...)</programlisting>
-
-    <para>ëÁË É × ÒÁÚÄÅÌÁÈ Ï ËÏÎÓÏÌÉ, × ÓÐÅÃÉÁÌÉÚÉÒÏ×ÁÎÎÙÈ ÐÒÉÌÏÖÅÎÉÑÈ ×Ó£ ÅÝ£
-      ÍÏÇÕÔ ÏÓÔÁÔØÓÑ ÎÁÓÔÒÏÅÎÎÙÍÉ ÛÒÉÆÔÙ ISO8859-1 × ÉÈ ÂÁÚÁÈ ÄÁÎÎÙÈ &man.xrdb.1;.
-      ïÄÎÉÍ ÉÚ ×ÉÄÉÍÙÈ ÐÒÉÍÅÒÏ× Ñ×ÌÑÅÔÓÑ <application>xterm</application>.
-      ëÁË ÐÒÁ×ÉÌÏ, ÄÏÓÔÁÔÏÞÎÏ ÉÚÍÅÎÉÔØ ÓÏÏÔ×ÅÔÓÔ×ÕÀÝÉÊ ËÏÎÆÉÇÕÒÁÃÉÏÎÎÙÊ ÆÁÊÌ ÉÚ
-      ËÁÔÁÌÏÇÁ <filename>/usr/X11R6/lib/X11/app-defaults</filename>, ÄÏÂÁ×É×
-      ÐÒÁ×ÉÌØÎÙÊ ÛÒÉÆÔ.  ðÒÏÄÅÍÏÎÓÔÒÉÒÕÅÍ ÜÔÏ ÎÁ ÐÒÉÍÅÒÅ
-      <application>xterm</application>.</para>
-
-   <screen>&prompt.root; cd /usr/X11R6/lib/X11/app-defaults/
-&prompt.root; vi XTerm</screen>
-
-    <para>äÏÂÁ×ØÔÅ ÔÁËÕÀ ÓÔÒÏËÕ × ÎÁÞÁÌÏ ÆÁÊÌÁ:</para>
-
-    <programlisting>*font:     -misc-fixed-medium-r-normal-*-*-120-*-*-c-*-iso8859-15</programlisting>
-
-    <para>é ÎÁËÏÎÅÃ, ÐÅÒÅÚÁÐÕÓÔÉÔÅ X É ÐÒÏ×ÅÒØÔÅ, ÞÔÏ ÛÒÉÆÔÙ ÍÏÇÕÔ ×Ù×ÏÄÉÔØÓÑ,
-      ×ÙÐÏÌÎÉ× ×ÙÛÅÐÒÉ×ÅÄ£ÎÎÙÊ <link linkend="awk-test">ÓËÒÉÐÔ ÎÁ awk</link>.
-      ÷ÓÅ ÏÓÎÏ×ÎÙÅ ÐÒÉÌÏÖÅÎÉÑ ÄÏÌÖÎÙ ×ÏÓÐÒÉÎÑÔØ ËÌÁ×ÉÁÔÕÒÎÕÀ ÒÁÓËÌÁÄËÕ É
-      ÎÁÓÔÒÏÊËÉ ÛÒÉÆÔÁ.</para>
-  </sect1>
-
-  <sect1 id="problems">
-    <title>ïÔËÒÙÔÙÅ ÐÒÏÂÌÅÍÙ</title>
-
-    <para>ëÏÎÅÞÎÏ, Á×ÔÏÒ ÂÕÄÅÔ ÒÁÄ ÐÏÌÕÞÉÔØ ÏÔËÌÉËÉ.  ëÒÏÍÅ ÔÏÇÏ, ÐÏ ËÒÁÊÎÅÊ
-      ÍÅÒÅ ÄÁÊÔÅ ÍÎÅ ÚÎÁÔØ, ÅÓÌÉ ÌÉ Õ ×ÁÓ ÒÅÛÅÎÉÑ ÄÌÑ ÓÌÅÄÕÀÝÉÈ ÏÔËÒÙÔÙÈ
-      ÐÒÏÂÌÅÍ:</para>
-
-    <itemizedlist>
-      <listitem>
-	<para>ïÐÉÓÁÎÉÅ ÁÌØÔÅÒÎÁÔÉ×ÎÏÇÏ ÓÐÏÓÏÂÁ ÎÁÓÔÒÏÊËÉ <application>Xorg</application>:
-	  <filename role="package">x11/xkeycaps</filename></para>
-      </listitem>
-
-      <listitem>
-	<para>îÁÓÔÒÏÊËÉ × <application>GNOME</application></para>
-      </listitem>
-
-      <listitem>
-	<para>îÁÓÔÒÏÊËÉ × <application>XFCE</application></para>
-      </listitem>
-
-      <listitem>
-	<para>îÁÓÔÒÏÊËÉ ÄÌÑ <application>(X)Emacs</application></para>
-      </listitem>
-
-      <listitem>
-	<para>ïÐÉÓÁÎÉÅ UTF-8</para>
-      </listitem>
-
-      <listitem>
-	<para>ïÐÉÓÁÎÉÅ <application>libiconv</application> ËÁË ÜÆÆÅËÔÉ×ÎÏÇÏ
-	  ÓÐÏÓÏÂÁ ÐÒÅÏÂÒÁÚÏ×ÁÎÉÑ ÍÅÖÄÕ ISO8859-15 É UTF-{8,16} ×ÎÕÔÒÉ
-	  ÐÒÉÌÏÖÅÎÉÊ</para>
-      </listitem>
-    </itemizedlist>
-  </sect1>
-</article>
diff --git a/ru_RU.KOI8-R/articles/formatting-media/Makefile b/ru_RU.KOI8-R/articles/formatting-media/Makefile
deleted file mode 100644
index 7b4e2ce43d..0000000000
--- a/ru_RU.KOI8-R/articles/formatting-media/Makefile
+++ /dev/null
@@ -1,21 +0,0 @@
-#
-# The FreeBSD Russian Documentation Project
-#
-# $FreeBSD$
-# $FreeBSDru: frdp/doc/ru_RU.KOI8-R/articles/formatting-media/Makefile,v 1.4 2006/03/29 19:55:13 gad Exp $
-#
-# Original revision: r20561
-#
-# Article: Formatting Media For Use With FreeBSD
-
-DOC?= article
-
-FORMATS?= html
-
-INSTALL_COMPRESSED?=gz
-INSTALL_ONLY_COMPRESSED?=
-
-SRCS= article.sgml
-
-DOC_PREFIX?= ${.CURDIR}/../../..
-.include "${DOC_PREFIX}/share/mk/doc.project.mk"
diff --git a/ru_RU.KOI8-R/articles/formatting-media/article.sgml b/ru_RU.KOI8-R/articles/formatting-media/article.sgml
deleted file mode 100644
index c7d7d4ba98..0000000000
--- a/ru_RU.KOI8-R/articles/formatting-media/article.sgml
+++ /dev/null
@@ -1,661 +0,0 @@
-<?xml version="1.0" encoding="koi8-r" standalone="no"?>
-<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V4.2-Based Extension//EN"
-	"../../../share/sgml/freebsd42.dtd" [
-<!ENTITY % entities PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Entity Set//RU" "../../share/sgml/entities.ent">
-%entities;
-]>
-
-<!--
-     The FreeBSD Russian Documentation Project
-
-     $FreeBSD$
-     $FreeBSDru: frdp/doc/ru_RU.KOI8-R/articles/formatting-media/article.sgml,v 1.6 2006/03/29 19:55:13 gad Exp $
-
-     Original revision: r30695
--->
-
-<article lang="ru">
-  <articleinfo>
-    <title>æÏÒÍÁÔÉÒÏ×ÁÎÉÅ ÎÏÓÉÔÅÌÅÊ ÄÌÑ ÉÓÐÏÌØÚÏ×ÁÎÉÑ Ó FreeBSD</title>
-
-    <subtitle>õÞÅÂÎÏÅ ÐÏÓÏÂÉÅ</subtitle>
-
-    <authorgroup>
-      <author>
-	<firstname>Doug</firstname>
-
-	<surname>White</surname>
-
-	<affiliation>
-	  <address>
-	    <email>dwhite@resnet.uoregon.edu</email>
-	  </address>
-	</affiliation>
-      </author>
-    </authorgroup>
-
-    <pubdate>íÁÒÔ 1997</pubdate>
-
-    <legalnotice id="trademarks" role="trademarks">
-      &tm-attrib.freebsd;
-      &tm-attrib.iomega;
-      &tm-attrib.opengroup;
-      &tm-attrib.general;
-    </legalnotice>
-
-    <releaseinfo>$FreeBSD$</releaseinfo>
-
-<!--
-    <para>ðÅÒÅ×ÏÄ ÎÁ ÒÕÓÓËÉÊ ÑÚÙË: áÎÄÒÅÊ úÁÈ×ÁÔÏ×
-      (<email>andy@FreeBSD.org</email>)</para>
--->
-
-    <abstract>
-      <para>üÔÏÔ ÄÏËÕÍÅÎÔ ÏÐÉÓÙ×ÁÅÔ, ËÁË ÒÁÚÂÉÔØ ÎÁ ÓÌÁÊÓÙ, ÒÁÚÄÅÌÙ É
-	ÏÔÆÏÒÍÁÔÉÒÏ×ÁÔØ ÄÉÓËÏ×ÙÅ É ÐÏÄÏÂÎÙÅ ÉÍ ÕÓÔÒÏÊÓÔ×Á ÄÌÑ ÉÓÐÏÌØÚÏ×ÁÎÉÑ Ó
-	FreeBSD.  ðÒÉ×ÏÄÉÍÙÅ ÐÒÉÍÅÒÙ ÂÙÌÉ ÐÒÏÔÅÓÔÉÒÏ×ÁÎÙ ×Ï FreeBSD 2.2 É
-	ÄÏÌÖÎÙ ÒÁÂÏÔÁÔØ É × ÄÒÕÇÉÈ ÒÅÌÉÚÁÈ.  ôÅËÓÔ ÂÙÌ ÄÏÐÏÌÎÅÎ ÄÌÑ FreeBSD
-	×ÅÒÓÉÉ 4.</para>
-    </abstract>
-  </articleinfo>
-
-  <sect1>
-    <title>÷×ÅÄÅÎÉÅ É ÏÐÒÅÄÅÌÅÎÉÑ</title>
-
-    <sect2>
-      <title>ïÂÚÏÒ</title>
-
-      <para>õÓÐÅÛÎÏÅ ×ÙÐÏÌÎÅÎÉÅ ÄÏÂÁ×ÌÅÎÉÑ ÄÉÓËÏ× × ÓÕÝÅÓÔ×ÕÀÝÕÀ ÓÉÓÔÅÍÕ
-	Ñ×ÌÑÅÔÓÑ ÐÒÉÚÎÁËÏÍ ÏÐÙÔÎÏÓÔÉ ÓÉÓÔÅÍÎÏÇÏ ÁÄÍÉÎÉÓÔÒÁÔÏÒÁ.  òÁÚÂÉÅÎÉÅ ÎÁ
-	ÓÌÁÊÓÙ, ÒÁÚÄÅÌÙ É ÄÏÂÁ×ÌÅÎÉÅ ÄÉÓËÏ× ÔÒÅÂÕÀÔ ÔÝÁÔÅÌØÎÏÓÔÉ × ÐÏÄÂÏÒÅ
-	ËÏÍÁÎÄ É ÉÈ ÐÁÒÁÍÅÔÒÏ×.  ïÄÎÏ ÎÅ×ÅÒÎÏÅ ÎÁÖÁÔÉÅ, É ×ÓÅ ÓÏÄÅÒÖÉÍÏÅ
-	ÄÉÓËÁ ÍÏÖÅÔ ÉÓÞÅÚÎÕÔØ ÚÁ ÓÞÉÔÁÎÎÙÅ ÓÅËÕÎÄÙ.  üÔÏÔ ÄÏËÕÍÅÎÔ ÂÙÌ ÎÁÐÉÓÁÎ
-	× ÐÏÐÙÔËÅ ÕÐÒÏÓÔÉÔØ ÜÔÏÔ ÐÒÏÃÅÓÓ É ÉÚÂÅÖÁÔØ ÏÛÉÂÏË.  ë ÓÞÁÓÔØÀ,
-	ÕÓÏ×ÅÒÛÅÎÓÔ×Ï×ÁÎÉÑ × ÉÍÅÀÝÉÈÓÑ ÉÎÓÔÒÕÍÅÎÔÁÈ (× ÞÁÓÔÎÏÓÔÉ, sysinstall)
-	×ÅÓØÍÁ ÕÐÒÏÓÔÉÌÉ ÜÔÏÔ ÐÒÏÃÅÓÓ × ÐÏÓÌÅÄÎÉÈ ÒÅÌÉÚÁÈ FreeBSD.</para>
-
-      <para>óÕÝÅÓÔ×ÕÀÔ Ä×Á ÒÅÖÉÍÁ ÆÏÒÍÁÔÉÒÏ×ÁÎÉÑ ÄÉÓËÁ:</para>
-
-      <itemizedlist>
-	<listitem>
-	  <para><firstterm>ÒÅÖÉÍ ÏÂÅÓÐÅÞÅÎÉÑ ÓÏ×ÍÅÓÔÉÍÏÓÔÉ</firstterm>:
-	    ðÏÄÇÏÔÏ×ËÁ ÄÉÓËÁ ÔÁË, ÞÔÏÂÙ ÏÎ ÉÍÅÌ ÔÁÂÌÉÃÕ ÓÌÁÊÓÏ×, ËÏÔÏÒÕÀ
-	    ÍÏÖÎÏ ÉÓÐÏÌØÚÏ×ÁÔØ Ó ÄÒÕÇÉÍÉ ÏÐÅÒÁÃÉÏÎÎÙÍÉ ÓÉÓÔÅÍÁÍÉ.</para>
-	</listitem>
-
-	<listitem>
-	  <para><firstterm>ÒÅÖÉÍ ÜËÓËÌÀÚÉ×ÎÏÇÏ ÉÓÐÏÌØÚÏ×ÁÎÉÑ</firstterm>,
-	    ÉÎÏÇÄÁ ÎÁÚÙ×ÁÅÍÙÊ <firstterm>ÏÐÁÓÎÙÍ ÒÅÖÉÍÏÍ</firstterm>:
-	    æÏÒÍÁÔÉÒÏ×ÁÎÉÅ ÄÉÓËÁ ÂÅÚ ÔÁÂÌÉÃÙ ÓÌÁÊÓÏ×.  üÔÏ ÕÐÒÏÝÁÅÔ ÐÒÏÃÅÓÓ
-	    ÄÏÂÁ×ÌÅÎÉÑ ÄÉÓËÏ×, ÎÏ ÄÒÕÇÉÅ ÏÐÅÒÁÃÉÏÎÎÙÅ ÓÉÓÔÅÍÙ ÎÅ ÓÍÏÇÕÔ
-	    ÒÁÂÏÔÁÔØ Ó ÄÉÓËÏÍ.  ôÅÒÍÉÎ <emphasis>ÏÐÁÓÎÙÊ</emphasis> ÏÔÎÏÓÉÔÓÑ Ë
-	    ÏÐÁÓÎÏÓÔÉ ÎÅ ÒÁÓÐÏÚÎÁ×ÁÎÉÑ ÓÉÓÔÅÍÏÊ ÄÉÓËÁ, ÏÔÆÏÒÍÁÔÉÒÏ×ÁÎÎÏÇÏ ÜÔÉÍ
-	    ÓÐÏÓÏÂÏÍ.</para>
-	</listitem>
-      </itemizedlist>
-
-      <para>÷ ÂÏÌØÛÉÎÓÔ×Å ÓÌÕÞÁÅ× ÜËÓËÌÀÚÉ×ÎÙÊ ÒÅÖÉÍ Ñ×ÌÑÅÔÓÑ ÓÁÍÙÍ ÐÒÏÓÔÙÍ ×
-	ÉÓÐÏÌØÚÏ×ÁÎÉÉ Ó ÓÕÝÅÓÔ×ÕÀÝÉÍÉ ÓÉÓÔÅÍÁÍÉ, ÔÁË ËÁË ÎÏ×ÙÊ ÄÉÓË, ËÁË
-	ÐÒÁ×ÉÌÏ, ÐÒÅÄÎÁÚÎÁÞÅÎ ÉÓËÌÀÞÉÔÅÌØÎÏ ÄÌÑ FreeBSD.  ïÄÎÁËÏ ÒÅÖÉÍ
-	ÏÂÅÓÐÅÞÅÎÉÑ ÓÏ×ÍÅÓÔÉÍÏÓÔÉ ÄÁÅÔ ÍÁËÓÉÍÕÍ ×ÏÚÍÏÖÎÏÓÔÅÊ × ÂÕÄÕÝÉÈ
-	ÕÓÔÁÎÏ×ËÁÈ ÃÅÎÏÊ ÂÏÌØÛÅÊ ÓÌÏÖÎÏÓÔÉ.</para>
-
-      <para>ëÒÏÍÅ ×ÙÂÏÒÁ ÒÅÖÉÍÁ, ÉÍÅÀÔÓÑ Ä×Á ÓÐÏÓÏÂÁ ÒÁÚÂÉÅÎÉÑ ÄÉÓËÁ ÎÁ ÓÌÁÊÓÙ.
-	ïÄÉÎ ÚÁËÌÀÞÁÅÔÓÑ × ÉÓÐÏÌØÚÏ×ÁÎÉÉ ÉÎÓÔÒÕÍÅÎÔÁ ÕÓÔÁÎÏ×ËÉ ÓÉÓÔÅÍÙ
-	<command>/stand/sysinstall</command>.  2.1.7-RELEASE É ÂÏÌÅÅ ÐÏÚÄÎÉÅ
-	×ÅÒÓÉÉ <command>sysinstall</command> ÓÏÄÅÒÖÁÔ ËÏÄ ÄÌÑ ÏÂÌÅÇÞÅÎÉÑ
-	ÕÓÔÁÎÏ×ËÉ ÄÉÓËÏ× ×Ï ×ÒÅÍÑ ÏÂÙÞÎÙÈ ÓÉÓÔÅÍÎÙÈ ÒÁÂÏÔ, × ÏÓÎÏ×ÎÏÍ ÄÁ×ÁÑ
-	ÄÏÓÔÕÐ Ë ÒÅÄÁËÔÏÒÕ ÒÁÚÄÅÌÏ× É ÒÁÚÍÅÔËÅ ÄÉÓËÁ É ×ÏÚÍÏÖÎÏÓÔÉ ÚÁÐÉÓÁÔØ
-	ÉÚÍÅÎÅÎÉÑ, ÐÒÉÞÅÍ ÂÕÄÅÔ ÏÂÎÏ×ÌÑÔØÓÑ ÉÎÆÏÒÍÁÃÉÑ ÔÏÌØËÏ ÎÁ ×ÙÂÒÁÎÎÏÍ
-	ÄÉÓËÅ É ÓÌÁÊÓÅ, ÎÅ ÚÁÔÒÁÇÉ×ÁÑ ÄÒÕÇÉÅ ÄÉÓËÉ.  äÒÕÇÏÊ ÍÅÔÏÄ ÓÏÓÔÏÉÔ ×
-	ÒÕÞÎÏÍ ÚÁÐÕÓËÅ ÕÔÉÌÉÔ ÁÄÍÉÎÉÓÔÒÁÔÏÒÏÍ ÉÚ ËÏÍÁÎÄÎÏÊ ÓÔÒÏËÉ.  äÌÑ ÒÅÖÉÍÁ
-	ÜËÓËÌÀÚÉ×ÎÏÇÏ ÉÓÐÏÌØÚÏ×ÁÎÉÑ ÉÓÐÏÌØÚÕÀÔÓÑ ÔÏÌØËÏ ÔÒÉ ÉÌÉ ÞÅÔÙÒÅ ËÏÍÁÎÄÙ,
-	ÈÏÔÑ <command>sysinstall</command> ÔÒÅÂÕÅÔ ÎÅËÏÔÏÒÙÈ ÕÈÉÝÒÅÎÉÊ.</para>
-    </sect2>
-
-    <sect2>
-      <title>ïÐÒÅÄÅÌÅÎÉÑ</title>
-
-      <para>úÁ ×ÅËÁ ÓÕÝÅÓÔ×Ï×ÁÎÉÑ ÕÐÒÁ×ÌÅÎÉÑ ÄÉÓËÁÍÉ × &unix; ÂÙÌÏ ÐÒÉÄÕÍÁÎÏ
-	ÍÎÏÇÏ ÎÏ×ÙÈ ÎÁÚ×ÁÎÉÊ ÄÌÑ ÓÔÁÒÙÈ ×ÅÝÅÊ.  ÷ ÓÌÅÄÕÀÝÅÍ ÓÌÏ×ÁÒÉËÅ ÄÁÎÙ
-	ÏÐÒÅÄÅÌÅÎÉÑ ÔÅÒÍÉÎÏ×, ÉÓÐÏÌØÚÕÅÍÙÈ × ÜÔÏÍ ÄÏËÕÍÅÎÔÅ É (ÎÁÄÅÅÍÓÑ) ×Ï
-	FreeBSD ×ÏÏÂÝÅ.</para>
-
-<!-- I'm tempted to use GLOSSARY here but will resort to a list for
-now. -->
-
-      <itemizedlist>
-	<listitem>
-	  <para>ÒÅÖÉÍ ÏÂÅÓÐÅÞÅÎÉÑ ÓÏ×ÍÅÓÔÉÍÏÓÔÉ: òÁÚÂÉÅÎÉÅ ÄÉÓËÁ ÔÁË, ÞÔÏ ÎÁ
-	    ÎÅÍ ÐÒÉÓÕÔÓÔ×ÕÅÔ ÔÁÂÌÉÃÁ ÓÌÁÊÓÏ×, ÉÓÐÏÌØÚÕÅÍÁÑ É ÄÒÕÇÉÍÉ
-	    ÏÐÅÒÁÃÉÏÎÎÙÍÉ ÓÉÓÔÅÍÁÍÉ.  ðÒÏÔÉ×ÏÐÏÌÏÖÅÎ ÒÅÖÉÍÕ ÜËÓËÌÀÚÉ×ÎÏÇÏ
-	    ÉÓÐÏÌØÚÏ×ÁÎÉÑ.</para>
-	</listitem>
-
-	<listitem>
-	  <para>(ÏÐÁÓÎÙÊ) ÒÅÖÉÍ ÜËÓËÌÀÚÉ×ÎÏÇÏ ÉÓÐÏÌØÚÏ×ÁÎÉÑ: æÏÒÍÁÔÉÒÏ×ÁÎÉÅ
-	    ÄÉÓËÁ ÂÅÚ ÉÓÐÏÌØÚÏ×ÁÎÉÑ ÔÁÂÌÉÃÙ ÓÌÁÊÓÏ×.  üÔÏ ÕÐÒÏÝÁÅÔ ÐÒÏÃÅÓÓ
-	    ÄÏÂÁ×ÌÅÎÉÑ ÄÉÓËÏ×, ÏÄÎÁËÏ ÄÒÕÇÉÅ (ÎÅ FreeBSD) ÏÐÅÒÁÃÉÏÎÎÙÅ ÓÉÓÔÅÍÙ
-	    ÎÅ ÓÍÏÇÕÔ ÒÁÓÐÏÚÎÁÔØ ÄÉÓË.  ðÒÏÔÉ×ÏÐÏÌÏÖÅÎ ÒÅÖÉÍÕ ÏÂÅÓÐÅÞÅÎÉÑ
-	    ÓÏ×ÍÅÓÔÉÍÏÓÔÉ.</para>
-	</listitem>
-
-	<listitem>
-	  <para>ÄÉÓË: ÖÅÓÔËÉÅ ÄÉÓËÉ, ËÏÍÐÁËÔ-ÄÉÓËÉ, ÍÁÇÎÉÔÏ-ÏÐÔÉÞÅÓËÉÅ É
-	    ÓßÅÍÎÙÅ ÎÏÓÉÔÅÌÉ &iomegazip;/&jaz; Ñ×ÌÑÀÔÓÑ ÐÒÉÍÅÒÁÍÉ ÕÓÔÒÏÊÓÔ×ÁÍÉ
-	    ÈÒÁÎÅÎÉÑ, ÎÁÉÂÏÌÅÅ ÞÁÓÔÏ ÉÓÐÏÌØÚÕÅÍÙÍÉ × ÎÁÛÉ ÄÎÉ.  ïÓÎÏ×ÎÏÊ
-	    ÐÒÉÎÃÉÐ ÉÈ ÒÁÂÏÔÙ ÚÁËÌÀÞÁÅÔÓÑ × ÔÏÍ, ÞÔÏ ÎÅÓËÏÌØËÏ ËÒÕÔÑÝÉÈÓÑ ÄÉÓËÏ×
-	    ÒÁÓËÒÕÞÉ×ÁÀÔÓÑ ÍÏÔÏÒÞÉËÏÍ, × ÔÏ ×ÒÅÍÑ ËÁË ÇÏÌÏ×ËÁ, Ä×ÉÖÕÝÁÑÓÑ ÐÏ
-	    ÒÁÄÉÁÌØÎÏÊ ÌÉÎÉÉ ÞÉÔÁÅÔ ÉÌÉ ÚÁÐÉÓÙ×ÁÅÔ ÄÁÎÎÙÅ Ó ÄÉÓËÁ.  úÁÐÉÓØ
-	    ÐÒÏÉÓÈÏÄÉÔ ÐÕÔÅÍ ÉÚÍÅÎÅÎÉÑ ÆÉÚÉÞÅÓËÉÈ Ó×ÏÊÓÔ× ÄÉÓËÁ (ÍÁÇÎÉÔÎÏÇÏ
-	    ÐÏÔÏËÁ, ËÏÜÆÆÉÃÉÅÎÔÁ ÏÔÒÁÖÅÎÉÑ ÐÏ×ÅÒÈÎÏÓÔÉ (reflectivity) É Ô.Ä.),
-	    Á ÞÔÅÎÉÅ, ÐÕÔ£Í <quote>ÏÐÒÅÄÅÌÅÎÉÑ</quote> ÉÚÍÅÎÅÎÉÊ ÔÅÈ ÖÅ ÆÉÚÉÞÅÓËÉÈ
-	    Ó×ÏÊÓÔ× ÄÉÓËÁ.</para>
-	</listitem>
-
-	<listitem>
-	  <para>ÓÌÁÊÓ: þÁÓÔØ ÄÉÓËÁ.  îÁ ÏÄÎÏÍ ÄÉÓËÅ ÐÏ ÓÔÁÎÄÁÒÔÁÍ PC ÍÏÖÅÔ
-	    ÒÁÓÐÏÌÁÇÁÔØÓÑ ÄÏ ÞÅÔÙÒÅÈ ÓÌÁÊÓÏ×.  óÌÁÊÓÙ ÓÏÓÔÏÑÔ ÉÚ
-	    ÐÏÓÌÅÄÏ×ÁÔÅÌØÎÏ ÒÁÓÐÏÌÁÇÁÀÝÉÈÓÑ ÓÅËÔÏÒÏ×.  éÎÆÏÒÍÁÃÉÑ Ï ÓÌÁÊÓÁÈ
-	    ÚÁÐÉÓÙ×ÁÅÔÓÑ × <quote>ÔÁÂÌÉÃÕ ÓÌÁÊÓÏ×</quote>, ÉÓÐÏÌØÚÕÅÍÕÀ
-	    ÓÉÓÔÅÍÎÙÍ BIOS ÄÌÑ ÎÁÈÏÖÄÅÎÉÑ ÚÁÇÒÕÚÏÞÎÙÈ ÒÁÚÄÅÌÏ×.  ôÁÂÌÉÃÁ
-	    ÓÌÁÊÓÏ× × ÔÅÒÍÉÎÏÌÏÇÉÉ DOS ÏÂÙÞÎÏ ÎÁÚÙ×ÁÅÔÓÑ ÔÁÂÌÉÃÅÊ ÒÁÚÄÅÌÏ×
-	    (<quote>Partition Table</quote>).  õÐÒÁ×ÌÑÅÔÓÑ ÕÔÉÌÉÔÏÊ fdisk.</para>
-	</listitem>
-
-	<listitem>
-	  <para>ÒÁÚÄÅÌ: þÁÓÔØ ÓÌÁÊÓÁ.  ïÂÙÞÎÏ ÉÓÐÏÌØÚÕÅÔÓÑ ÄÌÑ ÏÂÏÚÎÁÞÅÎÉÑ
-	    ÞÁÓÔÅÊ ÓÌÁÊÓÁ FreeBSD ÎÁ ÄÉÓËÅ.  ëÁÖÄÁÑ ÆÁÊÌÏ×ÁÑ ÓÉÓÔÅÍÁ É ÏÂÌÁÓÔØ
-	    ÐÏÄËÁÞËÉ ÎÁ ÄÉÓËÅ ÒÁÓÐÏÌÁÇÁÀÔÓÑ × ÒÁÚÄÅÌÅ.  õÐÒÁ×ÌÑÅÔÓÑ ÕÔÉÌÉÔÏÊ
-	    disklabel.</para>
-	</listitem>
-
-	<listitem>
-	  <para>ÓÅËÔÏÒ: óÁÍÁÑ ÍÁÌÁÑ ÞÁÓÔØ ÄÉÓËÁ.  ïÄÉÎ ÓÅËÔÏÒ, ËÁË ÐÒÁ×ÉÌÏ,
-	    ÈÒÁÎÉÔ 512 ÂÁÊÔ ÄÁÎÎÙÈ.</para>
-	</listitem>
-      </itemizedlist>
-    </sect2>
-
-    <sect2>
-      <title>ðÒÅÄÏÓÔÅÒÅÖÅÎÉÑ &amp; ìÏ×ÕÛËÉ</title>
-
-      <para>ðÏÄÇÏÔÏ×ËÁ ÄÉÓËÁ ÎÅ Ñ×ÌÑÅÔÓÑ ÐÒÏÓÔÙÍ ÐÒÏÃÅÓÓÏÍ.  ÷ÅÓØÍÁ ×ÏÚÍÏÖÎÏ
-	ÕÎÉÞÔÏÖÅÎÉÅ ÓÏÄÅÒÖÉÍÏÇÏ ÄÒÕÇÉÈ ÄÉÓËÏ× ×ÁÛÅÊ ÓÉÓÔÅÍÙ, ÅÓÌÉ ÎÅ ÂÙÔØ
-	ÁËËÕÒÁÔÎÙÍ.</para>
-
-      <para><emphasis>ôÝÁÔÅÌØÎÏ ÐÒÏ×ÅÒÑÊÔÅ Ó×ÏÀ ÒÁÂÏÔÕ.</emphasis>  ïÞÅÎØ
-	ÐÒÏÓÔÏ ÕÎÉÞÔÏÖÉÔØ ÉÎÆÏÒÍÁÃÉÀ ÎÅ ÎÁ ÔÏÍ ÄÉÓËÅ ÐÒÉ ÒÁÂÏÔÅ Ó ÜÔÉÍÉ
-	ËÏÍÁÎÄÁÍÉ.  åÓÌÉ ÓÏÍÎÅ×ÁÅÔÅÓØ, ÏÂÒÁÔÉÔÅÓØ Ë ÓÏÏÂÝÅÎÉÑÍ, ×ÙÄÁ×ÁÅÍÙÍ ÐÒÉ
-	ÚÁÇÒÕÚËÅ ÑÄÒÁ, ÄÌÑ ÏÐÒÅÄÅÌÅÎÉÑ ×ÅÒÎÏÇÏ ÉÍÅÎÉ ÕÓÔÒÏÊÓÔ×Á.</para>
-
-      <para>éÚÌÉÛÎÅ ÇÏ×ÏÒÉÔØ, ÞÔÏ ÍÙ ÎÅ ÏÔ×ÅÞÁÅÍ ÚÁ ËÁËÕÀ ÂÙ ÔÏ ÎÉ ÂÙÌÏ ÐÏÒÞÕ
-	ÄÁÎÎÙÈ ÉÌÉ ÏÂÏÒÕÄÏ×ÁÎÉÑ, Ó ËÏÔÏÒÙÍÉ ×Ù ÍÏÖÅÔÅ ÓÔÏÌËÎÕÔØÓÑ.  òÁÂÏÔÁÊÔÅ
-	ÎÁ Ó×ÏÊ ÓÔÒÁÈ É ÒÉÓË!</para>
-    </sect2>
-
-    <sect2>
-      <title>Zip, Jaz É ÄÒÕÇÉÅ ÓÍÅÎÎÙÅ ÎÏÓÉÔÅÌÉ</title>
-
-      <para>óÍÅÎÎÙÅ ÄÉÓËÉ ÍÏÇÕÔ ÂÙÔØ ÏÔÆÏÒÍÁÔÉÒÏ×ÁÎÙ ÔÏÞÎÏ ÔÁË ÖÅ, ËÁË ÏÂÙÞÎÙÅ
-	ÖÅÓÔËÉÅ ÄÉÓËÉ.  äÌÑ ÏÐÒÅÄÅÌÅÎÉÑ ÐÁÒÁÍÅÔÒÏ× ÄÉÓËÁ ÄÏÓÔÁÔÏÞÎÏ ÐÏÄËÌÀÞÉÔØ
-	ÐÒÉ×ÏÄ Ë ÓÉÓÔÅÍÅ É ×ÓÔÁ×ÉÔØ ÔÕÄÁ ÄÉÓË ×Ï ×ÒÅÍÑ ÚÁÇÒÕÚËÉ.  ðÒÏÓÍÏÔÒÉÔÅ
-	×Ù×ÏÄ ËÏÍÁÎÄÙ <command>dmesg</command> É ÕÄÏÓÔÏ×ÅÒØÔÅÓØ, ÞÔÏ × ÎÅÍ
-	ÐÒÉÓÕÔÓÔ×ÕÀÔ ×ÁÛÅ ÕÓÔÒÏÊÓÔ×Ï É ÒÁÚÍÅÒ ÄÉÓËÁ.  åÓÌÉ ÑÄÒÏ ×ÙÄÁÅÔ
-
-	<informalexample>
-	  <screen>Can't get the size</screen>
-	</informalexample>
-
-	ÔÏ ÄÉÓËÁ × ÕÓÔÒÏÊÓÔ×Å ÎÅÔ.  ÷ ÔÁËÏÍ ÓÌÕÞÁÅ ×ÁÍ ÎÕÖÎÏ ÐÅÒÅÚÁÐÕÓÔÉÔØ
-	ÍÁÛÉÎÕ ÐÅÒÅÄ ÔÅÍ, ËÁË ÐÙÔÁÔØÓÑ ÏÔÆÏÒÍÁÔÉÒÏ×ÁÔØ ÄÉÓËÉ.</para>
-    </sect2>
-  </sect1>
-
-  <sect1>
-    <title>æÏÒÍÁÔÉÒÏ×ÁÎÉÅ ÄÉÓËÏ× × ÒÅÖÉÍÅ ÜËÓËÌÀÚÉ×ÎÏÇÏ ÉÓÐÏÌØÚÏ×ÁÎÉÑ</title>
-
-    <sect2>
-      <title>÷×ÅÄÅÎÉÅ</title>
-
-      <para>÷ ÜÔÏÍ ÒÁÚÄÅÌÅ ÐÏÄÒÏÂÎÏ ÏÐÉÓÁÎÏ, ËÁË ÓÄÅÌÁÔØ ÄÉÓËÉ ÐÏÌÎÏÓÔØÀ
-	ÐÒÅÄÎÁÚÎÁÞÅÎÎÙÍÉ ÄÌÑ FreeBSD.  ðÏÍÎÉÔÅ, ÞÔÏ ÉÎÏÇÄÁ ÄÉÓËÉ,
-	ÐÏÄÇÏÔÏ×ÌÅÎÎÙÅ ÄÌÑ ÒÅÖÉÍÁ ÜËÓËÌÀÚÉ×ÎÏÇÏ ÉÓÐÏÌØÚÏ×ÁÎÉÑ, ÎÅ ÍÏÇÕÔ ÂÙÔØ
-	ÚÁÇÒÕÚÏÞÎÙÍÉ × ÁÒÈÉÔÅËÔÕÒÅ PC.</para>
-    </sect2>
-
-    <sect2>
-      <title>ðÏÄÇÏÔÏ×ËÁ ÄÉÓËÏ× × ÒÅÖÉÍÅ ÜËÓËÌÀÚÉ×ÎÏÇÏ ÉÓÐÏÌØÚÏ×ÁÎÉÑ ÐÒÉ ÐÏÍÏÝÉ
-	ÕÔÉÌÉÔÙ sysinstall</title>
-
-      <para><command>/stand/sysinstall</command>, ÐÒÏÇÒÁÍÍÁ ÕÓÔÁÎÏ×ËÉ ÓÉÓÔÅÍÙ,
-	× ÐÏÓÌÅÄÎÉÈ ×ÅÒÓÉÑÈ ÂÙÌÁ ÒÁÓÛÉÒÅÎÁ ÔÁË, ÞÔÏ ÐÏÚ×ÏÌÑÅÔ ÓÄÅÌÁÔØ ÐÒÏÃÅÓÓ
-	ÐÏÄÇÏÔÏ×ËÉ ÄÉÓËÏ× ÐÒÏÓÔÏÊ ÚÁÄÁÞÅÊ.  òÅÄÁËÔÏÒÙ fdisk É disklabel,
-	×ÓÔÒÏÅÎÎÙÅ × sysinstall, Ñ×ÌÑÀÔÓÑ ÉÎÓÔÒÕÍÅÎÔÁÍÉ Ó ÇÒÁÆÉÞÅÓËÉÍ
-	ÐÏÌØÚÏ×ÁÔÅÌØÓËÉÍ ÉÎÔÅÒÆÅÊÓÏÍ, ÕÓÔÒÁÎÑÀÝÉÍÉ ÂÏÌØÛÉÎÓÔ×Ï ÎÅÑÓÎÏÓÔÅÊ ÐÒÉ
-	ÒÁÚÂÉÅÎÉÉ ÄÉÓËÏ×.  äÌÑ ×ÅÒÓÉÊ FreeBSD 2.1.7 É ×ÙÛÅ ÜÔÏ, ÎÁ×ÅÒÎÏÅ, ÓÁÍÙÊ
-	ÐÒÏÓÔÏÊ ÓÐÏÓÏ ÐÏÄÇÏÔÏ×ËÉ ÄÉÓËÏ×.</para>
-
-      <procedure>
-	<step>
-	  <para>úÁÐÕÓÔÉÔÅ sysinstall ËÁË ÐÏÌØÚÏ×ÁÔÅÌØ root, ÎÁÂÒÁ×
-
-	    <informalexample>
-	      <screen>&prompt.root; <userinput>/stand/sysinstall</userinput></screen>
-	    </informalexample>
-
-	    × ËÏÍÁÎÄÎÏÊ ÓÔÒÏËÅ.</para>
-	</step>
-
-	<step>
-	  <para>÷ÙÂÅÒÉÔÅ ÐÕÎËÔ <command>Index</command>.</para>
-	</step>
-
-	<step>
-	  <para>÷ÙÂÅÒÉÔÅ ÐÕÎËÔ <command>Partition</command>.</para>
-	</step>
-
-	<step>
-	  <para>÷ÙÂÅÒÉÔÅ ÄÉÓË ÄÌÑ ÒÅÄÁËÔÉÒÏ×ÁÎÉÑ Ó ÐÏÍÏÝØÀ ËÌÁ×ÉÛ ÕÐÒÁ×ÌÅÎÉÑ
-	    ËÕÒÓÏÒÏÍ É ËÌÁ×ÉÛÉ <keycap>ÐÒÏÂÅÌÁ</keycap>.</para>
-	</step>
-
-	<step>
-	  <para>åÓÌÉ ×Ù ÉÓÐÏÌØÚÕÅÔÅ ÜÔÏÔ ÄÉÓË ÐÏÌÎÏÓÔØÀ ÄÌÑ FreeBSD, ×ÙÂÅÒÉÔÅ
-	    <command>A</command>.</para>
-	</step>
-
-	<step>
-	  <para>ëÏÇÄÁ ÂÕÄÅÔ ÚÁÄÁÎ ×ÏÐÒÏÓ Ï ÔÏÍ, ÄÅÊÓÔ×ÉÔÅÌØÎÏ ÌÉ ×Ù ÈÏÔÉÔÅ ÜÔÏ
-	    ÓÄÅÌÁÔØ, ÏÔ×ÅÔØÔÅ <command>Yes</command>.</para>
-	</step>
-
-	<step>
-	  <para>÷ÙÂÅÒÉÔÅ <command>Write</command>.</para>
-	</step>
-
-	<step>
-	  <para>ðÒÉ ×ÙÄÁÞÅ ÐÒÅÄÕÐÒÅÖÄÅÎÉÑ Writing on installed systems,
-	    ÏÔ×ÅÔØÔÅ <command>Yes</command>.</para>
-	</step>
-
-	<step>
-	  <para>ëÏÇÄÁ ÂÕÄÅÔ ÚÁÄÁÎ ×ÏÐÒÏÓ ÐÏ ÐÏ×ÏÄÕ ÕÓÔÁÎÏ×ËÉ ÍÅÎÅÄÖÅÒÁ
-	    ÚÁÇÒÕÚËÉ, ×ÙÂÅÒÉÔÅ <command>None</command>, ÔÅÍ ÓÁÍÙÍ ÏÓÔÁ×É×
-	    MBR ÂÅÚ ÉÚÍÅÎÅÎÉÊ.  üÔÏ ÎÅÏÂÈÏÄÉÍÏ ÌÉÛØ ÐÒÉ ÎÏ×ÏÊ ÉÎÓÔÁÌÌÑÃÉÉ
-	    &os; ÅÓÌÉ ÎÅ ÐÌÁÎÉÒÕÅÔÓÑ ÕÓÔÁÎÏ×ËÁ ÄÉÓËÁ × ÄÒÕÇÕÀ ÍÁÛÉÎÕ.</para>
-	</step>
-
-	<step>
-	  <para>îÁÖÍÉÔÅ <keycap>ENTER</keycap> × ÏÔ×ÅÔ ÎÁ ÓÏÏÂÝÅÎÉÅ
-	    <quote>Wrote FDISK partition information out
-	    successfully</quote>.</para>
-	</step>
-
-	<step>
-	  <para>÷ÙÂÅÒÉÔÅ <command>Quit</command> ÄÌÑ ×ÙÈÏÄÁ ÉÚ ÒÅÄÁËÔÏÒÁ FDISK
-	    É ÎÁÖÍÉÔÅ <keycap>ESCAPE</keycap> ÄÌÑ ×ÏÚ×ÒÁÔÁ × ÍÅÎÀ Index.</para>
-	</step>
-
-	<step>
-	  <para>÷ÙÂÅÒÉÔÅ ÐÕÎËÔ <command>Label</command> ÉÚ ÍÅÎÀ Index.</para>
-	</step>
-
-	<step>
-	  <para>òÁÚÍÅÔØÔÅ ÄÉÓË ÔÁË, ËÁË ÜÔÏ ÎÕÖÎÏ.  äÌÑ ÒÁÂÏÔÙ Ó ÅÄÉÎÓÔ×ÅÎÎÙÍ
-	     ÒÁÚÄÅÌÏÍ ÎÁÖÍÉÔÅ <command>C</command> ÄÌÑ ÓÏÚÄÁÎÉÑ ÒÁÚÄÅÌÁ, ÐÒÉÍÉÔÅ
-	     ÒÁÚÍÅÒ ÐÏ ÕÍÏÌÞÁÎÉÀ, ÕÓÔÁÎÏ×ÉÔÅ ÔÉÐ ÒÁÚÄÅÌÁ × Filesystem É ÕËÁÖÉÔÅ
-	     ÔÏÞËÕ ÍÏÎÔÉÒÏ×ÁÎÉÑ (ËÏÔÏÒÁÑ ÎÅ ÉÓÐÏÌØÚÕÅÔÓÑ).</para>
-	</step>
-
-	<step>
-	  <para>îÁÖÍÉÔÅ <command>W</command>, ËÏÇÄÁ ×ÓÅ ÚÁËÏÎÞÉÔÅ É ÚÁÈÏÔÉÔÅ
-	    ÐÒÏÄÏÌÖÉÔØ.  æÁÊÌÏ×ÁÑ ÓÉÓÔÅÍÁ ÂÕÄÅÔ ÒÁÚÍÅÞÅÎÁ ×ÎÏ×Ø, ÅÓÌÉ ×Ù ÎÅ
-	    ÕËÁÚÁÌÉ ÐÒÏÔÉ×ÎÏÅ (ÄÌÑ ÎÏ×ÙÈ ÒÁÚÄÅÌÏ× ×ÁÍ ÜÔÏ ÄÅÌÁÔØ ÎÅÏÂÈÏÄÉÍÏ!).
-	    ÷Ù ÐÏÌÕÞÉÔÅ ÓÏÏÂÝÅÎÉÅ ÏÂ ÏÛÉÂËÅ:
-
-	    <informalexample>
-	      <screen>Error mounting /mnt/dev/ad2s1e on /mnt/blah : No such file or directory</screen>
-	    </informalexample>
-
-	    ðÒÏÉÇÎÏÒÉÒÕÊÔÅ ÜÔÏ ÓÏÏÂÝÅÎÉÅ.</para>
-	</step>
-
-	<step>
-	  <para>÷ÙÊÄÉÔÅ ÐÏ ÎÅÓËÏÌØËÉÍ ÎÁÖÁÔÉÑÍ ËÌÁ×ÉÛÉ
-	    <keycap>ESCAPE</keycap>.</para>
-	</step>
-      </procedure>
-    </sect2>
-
-    <sect2>
-      <title>ðÏÄÇÏÔÏ×ËÁ ÄÉÓËÁ Ë ÉÓÐÏÌØÚÏ×ÁÎÉÀ × ÜËÓËÌÀÚÉ×ÎÏÍ ÒÅÖÉÍÅ ÉÚ
-	ËÏÍÁÎÄÎÏÊ ÓÔÒÏËÉ</title>
-
-      <para>÷ÙÐÏÌÎÉÔÅ ÓÌÅÄÕÀÝÉÅ ËÏÍÁÎÄÙ, ÚÁÍÅÎÑÑ <devicename>ad2</devicename> ÎÁ ÉÍÑ ×ÁÛÅÇÏ
-	ÄÉÓËÁ.</para>
-
-      <informalexample>
-	<screen>
-&prompt.root; <userinput>dd if=/dev/zero of=/dev/ad2 count=2</userinput>
-&prompt.root; <userinput>disklabel /dev/ad2 | disklabel -B -R -r ad2 /dev/stdin</userinput>
-<lineannotation>We only want one partition, so using slice 'c' should be fine:</lineannotation>
-&prompt.root; <userinput>newfs /dev/ad2c</userinput></screen>
-      </informalexample>
-
-      <para>åÓÌÉ ×ÁÍ ÎÕÖÎÏ ÏÔÒÅÄÁËÔÉÒÏ×ÁÔØ ÍÅÔËÕ ÄÉÓËÁ ÄÌÑ ÓÏÚÄÁÎÉÑ ÎÅÓËÏÌØËÉÈ
-	ÒÁÚÄÅÌÏ× (ÎÁÐÒÉÍÅÒ, ÒÁÚÄÅÌÁ ÐÏÄËÁÞËÉ), ×ÙÐÏÌÎÉÔÅ ÓÌÅÄÕÀÝÅÅ:</para>
-
-      <informalexample>
-	<screen>
-&prompt.root; <userinput>dd if=/dev/zero of=/dev/ad2 count=2</userinput>
-&prompt.root; <userinput>disklabel /dev/ad2 > /tmp/label</userinput>
-<lineannotation>Edit disklabel to add partitions:</lineannotation>
-&prompt.root; <userinput>vi /tmp/label</userinput>
-&prompt.root; <userinput>disklabel -B -R -r ad2 /tmp/label</userinput>
-<lineannotation>newfs partitions appropriately</lineannotation></screen>
-      </informalexample>
-
-      <para>ôÅÐÅÒØ ×ÁÛ ÄÉÓË ÇÏÔÏ× Ë ÒÁÂÏÔÅ.</para>
-    </sect2>
-  </sect1>
-
-  <sect1>
-    <title>óÏÚÄÁÎÉÅ ÄÉÓËÏ× ÄÌÑ ÉÓÐÏÌØÚÏ×ÁÎÉÑ × ÒÅÖÉÍÅ ÓÏ×ÍÅÓÔÉÍÏÓÔÉ</title>
-
-    <sect2>
-      <title>÷×ÅÄÅÎÉÅ</title>
-
-      <para>ðÒÉ ÐÏÄÇÏÔÏ×ËÅ ÄÉÓËÏ× ÄÌÑ ÉÓÐÏÌØÚÏ×ÁÎÉÑ × ÜËÓËÌÀÚÉ×ÎÏÍ ÒÅÖÉÍÅ ÐÒÏÝÅ
-	×ÓÅÇÏ ×ÏÓÐÏÌØÚÏ×ÁÔØÓÑ ËÏÍÁÎÄÎÏÊ ÓÔÒÏËÏÊ, ÎÏ ÜÔÏÇÏ ÄÅÌÁÔØ ÎÅ ÓÌÅÄÕÅÔ ÐÒÉ
-	ÐÏÄÇÏÔÏ×ËÅ ÄÉÓËÏ× ÄÌÑ ÉÓÐÏÌØÚÏ×ÁÎÉÑ × ÒÅÖÉÍÅ ÓÏ×ÍÅÓÔÉÍÏÓÔÉ.  õÔÉÌÉÔÁ
-	ËÏÍÁÎÄÎÏÊ ÓÔÒÏËÉ <command>fdisk</command> ÔÒÅÂÕÅÔ ÓÌÏÖÎÙÈ ×ÙÞÉÓÌÅÎÉÊ É ÇÌÕÂÏËÏÇÏ ÐÏÎÉÍÁÎÉÑ
-	ÕÓÔÒÏÊÓÔ×Á ÔÁÂÌÉÃÙ ÓÌÁÊÓÏ×, ÞÔÏ ÄÁÎÏ ÎÅ ËÁÖÄÏÍÕ.  ðÒÉ ÐÏÄÇÏÔÏ×ËÅ ÄÉÓËÏ×
-	ÄÌÑ ÉÓÐÏÌØÚÏ×ÁÎÉÑ × ÒÅÖÉÍÅ ÓÏ×ÍÅÓÔÉÍÏÓÔÉ ÉÓÐÏÌØÚÕÊÔÅ sysinstall.</para>
-    </sect2>
-
-    <sect2>
-      <title>ðÏÄÇÏÔÏ×ËÁ ÄÉÓËÏ×, ÉÓÐÏÌØÚÕÅÍÙÈ × ÒÅÖÉÍÅ ÓÏ×ÍÅÓÔÉÍÏÓÔÉ, ÐÒÉ ÐÏÍÏÝÉ
-	sysinstall</title>
-
-      <procedure>
-	<step>
-	  <para>úÁÐÕÓÔÉÔÅ sysinstall, ÒÁÂÏÔÁÑ ËÁË ÐÏÌØÚÏ×ÁÔÅÌØ root, ÎÁÂÒÁ×
-
-	    <informalexample>
-	      <screen>&prompt.root; <userinput>/stand/sysinstall</userinput></screen>
-	    </informalexample>
-
-	    × ËÏÍÁÎÄÎÏÊ ÓÔÒÏËÅ.</para>
-	</step>
-
-	<step>
-	  <para>÷ÙÂÅÒÉÔÅ ÐÕÎËÔ ÍÅÎÀ <command>Index</command>.</para>
-	</step>
-
-	<step>
-	  <para>÷ÙÂÅÒÉÔÅ ÐÕÎËÔ ÍÅÎÀ <command>Partition</command>.</para>
-	</step>
-
-	<step>
-	  <para>÷ÙÂÅÒÉÔÅ ÄÉÓË ÄÌÑ ÒÁÂÏÔÙ ÐÒÉ ÐÏÍÏÝÉ ËÌÁ×ÉÛ ÕÐÒÁ×ÌÅÎÉÑ ËÕÒÓÏÒÏÍ
-	    É ËÌÁ×ÉÛÉ <keycap>SPACE</keycap>.</para>
-	</step>
-
-	<step>
-	  <para>åÓÌÉ ×Ù ÓÏÂÉÒÁÅÔÅÓØ ÉÓÐÏÌØÚÏ×ÁÔØ ÄÌÑ FreeBSD ×ÅÓØ ÄÉÓË, ÎÁÖÍÉÔÅ
-	    <command>A</command>.</para>
-	</step>
-
-	<step>
-	  <para>ëÏÇÄÁ ÂÕÄÅÔ ×ÙÄÁÎ ×ÏÐÒÏÓ:
-
-	    <informalexample>
-	      <screen>
-Do you want to do this with a true partition entry so as to remain
-cooperative with any future possible operating systems on the
-drive(s)?</screen>
-	    </informalexample>
-
-	    ÏÔ×ÅÔØÔÅ <command>yes</command>.</para>
-	</step>
-
-	<step>
-	  <para>÷ÙÂÅÒÉÔÅ <command>Write</command>.</para>
-	</step>
-
-	<step>
-	  <para>ëÏÇÄÁ ÂÕÄÅÔ ×ÙÄÁÎÏ ÄÉÁÌÏÇÏ×ÏÅ ÏËÎÏ ÄÌÑ ÕÓÔÁÎÏ×ËÉ ÍÅÎÅÄÖÅÒÁ
-	    ÚÁÇÒÕÚËÉ, ×ÙÂÅÒÉÔÅ None ÐÒÉ ÐÏÍÏÝÉ ËÌÁ×ÉÛÉ <keycap>SPACE</keycap>,
-	    Á ÚÁÔÅÍ ÎÁÖÍÉÔÅ <keycap>ENTER</keycap> ÄÌÑ ÐÏÄÔ×ÅÒÖÄÅÎÉÑ.</para>
-	</step>
-
-	<step>
-	  <para>÷ÙÂÅÒÉÔÅ <command>Quit</command> ÄÌÑ ×ÙÈÏÄÁ ÉÚ FDISK.</para>
-	</step>
-
-	<step>
-	  <para>ðÏÓÌÅ ×ÙÄÁÞÉ ÐÒÅÄÕÐÒÅÖÄÅÎÉÑ Ï ÍÅÎÅÄÖÅÒÅ ÚÁÇÒÕÚËÉ, ×ÙÂÅÒÉÔÅ
-	    <command>None</command> ÓÎÏ×Á.</para>
-	</step>
-
-	<step>
-	  <para>÷ÙÂÅÒÉÔÅ ÐÕÎËÔ <command>Label</command> ÉÚ ÍÅÎÀ Index.</para>
-	</step>
-
-	<step>
-	  <para>òÁÚÍÅÔØÔÅ ÄÉÓË ÔÁË, ËÁË ×ÁÍ ÎÕÖÎÏ.  ÷ ÓÌÕÞÁÅ ÅÄÉÎÓÔ×ÅÎÎÏÇÏ
-	    ÒÁÚÄÅÌÁ ÐÒÉÍÉÔÅ ÒÁÚÍÅÒ ÐÏ ÕÍÏÌÞÁÎÉÀ, ÔÉÐ Ó ÎÁÌÉÞÉÅÍ ÆÁÊÌÏ×ÏÊ
-	    ÓÉÓÔÅÍÙ É ÔÏÞËÕ ÍÏÎÔÉÒÏ×ÁÎÉÑ (ËÏÔÏÒÁÑ ÎÅ ÂÕÄÅÔ
-	    ÉÓÐÏÌØÚÏ×ÁÔØÓÑ).</para>
-	</step>
-
-	<step>
-	  <para>æÁÊÌÏ×ÁÑ ÓÉÓÔÅÍÁ ÂÕÄÅÔ ×ÎÏ×Ø ÓÏÚÄÁÎÁ, ÅÓÌÉ ×Ù ÎÅ ÚÁÄÁÌÉ
-	    ÏÂÒÁÔÎÏÅ (ÜÔÕ ÏÐÅÒÁÃÉÀ ÏÂÑÚÁÔÅÌØÎÏ ÎÕÖÎÏ ÄÅÌÁÔØ ÄÌÑ ÎÏ×ÙÈ
-	    ÒÁÚÄÅÌÏ×!).  ÷Ù ÐÏÌÕÞÉÔÅ ÓÏÏÂÝÅÎÉÅ Ï ÏÛÉÂËÅ:
-
-	    <informalexample>
-	      <screen>Error mounting /mnt/dev/ad2s1e on /mnt/blah : No such file or directory</screen>
-	    </informalexample>
-
-	    ðÒÏÉÇÎÏÒÉÒÕÊÔÅ ÅÇÏ.</para>
-	</step>
-
-	<step>
-	  <para>÷ÙÊÄÉÔÅ, ÐÏÓÌÅÄÏ×ÁÔÅÌØÎÏ ÎÁÖÉÍÁÑ
-	    <keycap>ESCAPE</keycap>.</para>
-	</step>
-      </procedure>
-
-      <para>ôÅÐÅÒØ ×ÁÛ ÎÏ×ÙÊ ÄÉÓË ÇÏÔÏ× Ë ÉÓÐÏÌØÚÏ×ÁÎÉÀ.</para>
-    </sect2>
-  </sect1>
-
-  <sect1>
-    <title>äÒÕÇÉÅ ÏÐÅÒÁÃÉÉ Ó ÄÉÓËÏÍ</title>
-
-    <sect2>
-      <title>äÏÂÁ×ÌÅÎÉÅ ÐÒÏÓÔÒÁÎÓÔ×Á ÄÌÑ ÐÏÄËÁÞËÉ</title>
-
-      <para>ðÒÉ ÒÏÓÔÅ ÓÉÓÔÅÍÙ ÍÏÖÅÔ ÒÁÓÔÉ É ÔÒÅÂÏ×ÁÎÉÅ Ë ÏÂßÅÍÕ ×ÉÒÔÕÁÌØÎÏÊ
-	ÐÁÍÑÔÉ.  èÏÔÑ ÄÏÂÁ×ÌÅÎÉÅ ÄÉÓËÏ×ÏÇÏ ÐÒÏÓÔÒÁÎÓÔ×Á ÄÌÑ ÐÏÄËÁÞËÉ × ÓÌÕÞÁÅ
-	ÕÖÅ ÉÍÅÀÝÉÈÓÑ ÄÉÓËÏ× Ñ×ÌÑÅÔÓÑ ÏÞÅÎØ ÓÌÏÖÎÏÊ ÚÁÄÁÞÅÊ, ÍÏÖÎÏ ÐÏÄÇÏÔÏ×ÉÔØ
-	ÎÏ×ÙÊ ÄÉÓË Ó ÄÏÐÏÌÎÉÔÅÌØÎÙÍ ÐÒÏÓÔÒÁÎÓÔ×ÏÍ ÄÌÑ ÐÏÄËÁÞËÉ.</para>
-
-      <para>äÌÑ ÄÏÂÁ×ÌÅÎÉÑ ÐÒÏÓÔÒÁÎÓÔ×Á ÐÏÄËÁÞËÉ ÐÒÉ ÄÏÂÁ×ÌÅÎÉÉ ÄÉÓËÁ Ë
-	ÓÉÓÔÅÍÅ:</para>
-
-      <procedure>
-	<step>
-	  <para>ðÒÉ ÒÁÚÂÉÅÎÉÉ ÄÉÓËÁ ÎÁ ÒÁÚÄÅÌÙ, ÏÔÒÅÄÁËÔÉÒÕÊÔÅ ÍÅÔËÕ ÄÉÓËÁ,
-	    ×ÙÄÅÌÉ× ÎÅËÏÔÏÒÏÅ ÏÂßÅÍ ÄÉÓËÁ ÄÌÑ ÒÁÚÄÅÌÁ `b', Á ÏÓÔÁÔÏË
-	    ÒÁÓÐÒÅÄÅÌÉ× × ÄÒÕÇÉÅ ÒÁÚÄÅÌÙ, ÎÁÐÒÉÍÅÒ, `a' ÉÌÉ `e'.  òÁÚÍÅÒÙ
-	    ÕËÁÚÙ×ÁÀÔÓÑ × ÂÌÏËÁÈ ÐÏ 512 ÂÁÊÔ.</para>
-	</step>
-
-	<step>
-	  <para>ðÒÉ ÓÏÚÄÁÎÉÉ ÎÏ×ÙÈ ÆÁÊÌÏ×ÙÈ ÓÉÓÔÅÍ ÎÁ ÄÉÓËÅ, îå ÄÅÌÁÊÔÅ ÜÔÏÇÏ
-	    ÄÌÑ ÒÁÚÄÅÌÁ `c'.  ÷ÍÅÓÔÏ ÜÔÏÇÏ ×ÙÐÏÌÎÉÔÅ ÓÏÚÄÁÎÉÅ ÎÏ×ÙÈ ÆÁÊÌÏ×ÙÈ
-	    ÓÉÓÔÅÍ ÄÌÑ ÒÁÚÄÅÌÏ×, ÎÅ ÓÏÄÅÒÖÁÝÉÈ ÐÒÏÓÔÒÁÎÓÔ×Ï ÄÌÑ
-	    ÐÏÄËÁÞËÉ.</para>
-	</step>
-
-	<step>
-	  <para>äÏÂÁ×ØÔÅ ÔÁËÕÀ ÓÔÒÏÞËÕ × ÆÁÊÌ
-	    <filename>/etc/fstab</filename>:</para>
-
-	  <informalexample>
-	    <programlisting>
-/dev/ad0b                       none            swap    sw 0 0
-	    </programlisting>
-	  </informalexample>
-
-	  <para>úÁÍÅÎÉÔÅ ÚÄÅÓØ <filename>/dev/ad0b</filename> ÎÁ ÉÍÑ ÕÓÔÒÏÊÓÔ×Á Ó ÔÏÌØËÏ ÞÔÏ
-	    ÄÏÂÁ×ÌÅÎÎÙÍ ÐÒÏÓÔÒÁÎÓÔ×ÏÍ.</para>
-	</step>
-
-	<step>
-	  <para>þÔÏÂÙ ÓÄÅÌÁÔØ ÐÒÏÓÔÒÁÎÓÔ×Ï ÄÌÑ ÐÏÄËÁÞËÉ ÎÅÍÅÄÌÅÎÎÏ ÄÏÓÔÕÐÎÙÍ,
-	    ×ÏÓÐÏÌØÚÕÊÔÅÓØ ËÏÍÁÎÄÏÊ <command>swapon</command>.
-
-	    <informalexample>
-	      <screen>&prompt.root; <userinput>swapon /dev/da0b</userinput>
-swapon:  added /dev/da0b as swap space</screen>
-	    </informalexample>
-	  </para>
-	</step>
-      </procedure>
-    </sect2>
-
-    <sect2>
-      <title>ëÏÐÉÒÏ×ÁÎÉÅ ÓÏÄÅÒÖÉÍÏÇÏ ÄÉÓËÏ×</title>
-<!-- Should have specific tag -->
-
-      <para>ðÒÅÄÏÓÔÁ×ÉÌ:  Renaud Waldura
-	(<email>renaud@softway.com</email>) </para>
-
-      <para>äÌÑ ÐÅÒÅÎÏÓÁ ÆÁÊÌÏ× Ó ×ÁÛÅÇÏ ÓÔÁÒÏÇÏ ÄÉÓËÁ ÎÁ ÎÏ×ÙÊ, ×ÙÐÏÌÎÉÔÅ:
-
-	<informalexample>
-	  <screen>&prompt.root; <userinput>mount /dev/ad2 /mnt</userinput>
-&prompt.root; <userinput>pax -r -w -p e /usr/home /mnt</userinput>
-&prompt.root; <userinput>umount /mnt</userinput>
-&prompt.root; <userinput>rm -rf /usr/home/*</userinput>
-&prompt.root; <userinput>mount /dev/ad2 /usr/home</userinput></screen>
-	</informalexample>
-      </para>
-    </sect2>
-
-    <sect2>
-      <title>ïÂßÅÄÉÎÅÎÉÅ ÄÉÓËÏ× Ó ÐÏÍÏÝØÀ CCD</title>
-
-      <para>ëÏÍÁÎÄÙ ÐÒÅÄÏÓÔÁ×ÉÌ: Stan Brown
-	(<email>stanb@awod.com</email>) </para>
-
-      <para>äÒÁÊ×ÅÒ CCD (Concatenated Disk Driver) ÐÏÚ×ÏÌÑÅÔ ×ÁÍ ÉÓÐÏÌØÚÏ×ÁÔØ
-	ÎÅÓËÏÌØËÏ ÉÄÅÎÔÉÞÎÙÈ ÄÉÓËÏ× ËÁË ÏÄÉÎ ÄÉÓË.  ïÂßÅÄÉÎÅÎÉÅ ÄÉÓËÏ× ÍÏÖÅÔ
-	ÐÏ×ÙÓÉÔØ ÐÒÏÉÚ×ÏÄÉÔÅÌØÎÏÓÔØ ÞÅÒÅÚ ÒÁÓÐÒÅÄÅÌÅÎÉÅ ÏÐÅÒÁÃÉÊ ÞÔÅÎÉÑ É
-	ÚÁÐÉÓÉ ÍÅÖÄÕ ÄÉÓËÁÍÉ.  ïÂÒÁÔÉÔÅÓØ Ë ÓÔÒÁÎÉÃÁÍ ÓÐÒÁ×ÏÞÎÏÊ ÓÉÓÔÅÍÙ
-	&man.ccd.4; É &man.ccdconfig.8; ÉÌÉ Ë <ulink
-	url="http://stampede.cs.berkeley.edu/ccd/">ÄÏÍÁÛÎÅÊ ÓÔÒÁÎÉÃÅ
-	CCD</ulink> ÄÌÑ ÐÏÌÕÞÅÎÉÑ ÐÏÄÒÏÂÎÏÊ ÉÎÆÏÒÍÁÃÉÉ.</para>
-
-      <para>÷ÁÍ ÂÏÌØÛÅ ÎÅ ÎÕÖÎÏ ËÏÍÐÉÌÉÒÏ×ÁÔØ ÓÐÅÃÉÁÌØÎÏÅ ÑÄÒÏ ÄÌÑ
-	ÉÓÐÏÌØÚÏ×ÁÎÉÑ ccd.  ëÏÇÄÁ ×Ù ÚÁÐÕÓËÁÅÔÅ ËÏÍÁÎÄÕ
-	<command>ccdconfig</command>, ÏÎÁ ÚÁÇÒÕÚÉÔ ÓÏÏÔ×ÅÔÓÔ×ÕÀÝÉÊ KLD, ÅÓÌÉ ×
-	ÑÄÒÅ ÎÅÔ ÐÏÄÄÅÒÖËÉ CCD.</para>
-
-      <para>÷Ù ÍÏÖÅÔÅ ÓÔÒÏÉÔØ ÏÂßÅÄÉÎÅÎÎÙÅ ÄÉÓËÉ × ÒÁÚÄÅÌÁÈ ÔÉÐÁ
-	<emphasis>4.2BSD</emphasis>.  åÓÌÉ ×Ù ÈÏÔÉÔÅ ÉÓÐÏÌØÚÏ×ÁÔØ ×ÅÓØ ÄÉÓË, ÔÏ
-	×ÁÍ ×ÓÅ ÒÁ×ÎÏ ÎÕÖÎÏ ÓÏÚÄÁÔØ ÎÏ×ÙÊ ÒÁÚÄÅÌ.  îÁÐÒÉÍÅÒ,
-	<userinput>disklabel -e</userinput> ÍÏÖÅÔ ×ÙÄÁ×ÁÔØ:</para>
-
-      <informalexample>
-	<screen>
-#        size   offset    fstype   [fsize bsize bps/cpg]
-  c: 60074784        0    unused        0     0     0   # (Cyl.    0 - 59597)</screen>
-      </informalexample>
-
-      <para>÷Ù ÎÅ ÓÍÏÖÅÔÅ ÉÓÐÏÌØÚÏ×ÁÔØ ÒÁÚÄÅÌ <emphasis>c</emphasis> ÄÌÑ CCD,
-	ÔÁË ËÁË ÏÎ ÉÍÅÅÔ ÔÉÐ <emphasis>unused</emphasis>.  ÷ÍÅÓÔÏ ÜÔÏÇÏ
-	ÓÏÚÄÁÊÔÅ ÎÏ×ÙÊ ÒÁÚÄÅÌ ÔÏÞÎÏ ÔÁËÏÇÏ ÖÅ ÒÁÚÍÅÒÁ, ÎÏ ÔÉÐÁ
-	<emphasis>4.2BSD</emphasis>:</para>
-
-      <informalexample>
-	<screen>
-#        size   offset    fstype   [fsize bsize bps/cpg]
-  c: 60074784        0    unused        0     0     0   # (Cyl.    0 - 59597)
-<userinput>   e: 60074784        0    4.2BSD        0     0     0   # (Cyl.    0 - 59597)</userinput></screen>
-      </informalexample>
-
-      <para>äÌÑ ÓÏÚÄÁÎÉÑ ÎÏ×ÏÇÏ CCD ×ÙÐÏÌÎÉÔÅ ÓÌÅÄÕÀÝÉÅ ËÏÍÁÎÄÙ.  úÄÅÓØ
-	ÏÐÉÓÁÎÏ, ËÁË ÏÂßÅÄÉÎÉÔØ ÔÒÉ ÄÉÓËÁ; ÐÒÏÓÔÏ ÄÏÂÁ×ÌÑÊÔÅ ÉÌÉ ÕÂÉÒÁÊÔÅ
-	ÕÓÔÒÏÊÓÔ×Á ÐÏ ÍÅÒÅ ÎÅÏÂÈÏÄÉÍÏÓÔÉ.  ðÏÍÎÉÔÅ, ÞÔÏ ÏÂßÅÄÉÎÑÅÍÙÅ ÄÉÓËÉ
-	ÄÏÌÖÎÙ ÂÙÔØ <emphasis>ÉÄÅÎÔÉÞÎÙÍÉ</emphasis>.</para>
-
-      <informalexample>
-	<screen>
-&prompt.root; <userinput>cd /dev ; sh MAKEDEV ccd0</userinput>
-
-&prompt.root; <userinput>disklabel -r -w da0 auto</userinput>
-&prompt.root; <userinput>disklabel -r -w da1 auto</userinput>
-&prompt.root; <userinput>disklabel -r -w da2 auto</userinput>
-
-&prompt.root; <userinput>disklabel -e da0</userinput>
-<lineannotation>Add partition e with type 4.2BSD</lineannotation>
-&prompt.root; <userinput>disklabel -e da1</userinput>
-<lineannotation>Add partition e with type 4.2BSD</lineannotation>
-&prompt.root; <userinput>disklabel -e da2</userinput>
-<lineannotation>Add partition e with type 4.2BSD</lineannotation>
-
-&prompt.root; <userinput>ccdconfig ccd0 273 0 /dev/da0e /dev/da1e /dev/da2e</userinput>
-
-&prompt.root; <userinput>newfs /dev/ccd0c</userinput></screen>
-      </informalexample>
-
-      <para>úÎÁÞÅÎÉÅ 273 ÚÁÄÁÅÔ ÒÁÚÍÅÒ ÂÌÏËÁ ÄÁÎÎÙÈ.  üÔÏ ÞÉÓÌÏ ÓÅËÔÏÒÏ× ÄÉÓËÁ,
-	(ËÁÖÄÙÊ ÐÏ 512 ÂÁÊÔ) × ËÁÖÄÏÍ ÂÌÏËÅ ÄÁÎÎÙÈ × CCD.  ïÎ ÄÏÌÖÅÎ ÂÙÔØ ÒÁ×ÅÎ
-	ÐÏ ËÒÁÊÎÅÊ ÍÅÒÅ 128 kB, É ÄÏÌÖÅÎ ÂÙÔØ ÓÔÅÐÅÎØÀ ÞÉÓÌÁ 2.</para>
-
-      <para>ôÅÐÅÒØ ×Ù ÍÏÖÅÔÅ ÓÍÏÎÔÉÒÏ×ÁÔØ É ÉÓÐÏÌØÚÏ×ÁÔØ ×ÁÛ CCD ÞÅÒÅÚ
-	ÕÓÔÒÏÊÓÔ×Ï <filename>/dev/ccd0c</filename>.</para>
-
-      <para>âÏÌÅÅ ÍÏÝÎÏÊ É ÇÉÂËÏÊ ÁÌØÔÅÒÎÁÔÉ×ÏÊ ÄÌÑ CCD Ñ×ÌÑÅÔÓÑ Vinum.
-	ïÂÒÁÔÉÔÅÓØ Ë <ulink url="http://www.vinumvm.org/">ÄÏÍÁÛÎÅÊ ÓÔÒÁÎÉÃÅ
-	ÐÒÏÅËÔÁ Vinum</ulink> ÄÌÑ ÐÏÌÕÞÅÎÉÑ ÐÏÄÒÏÂÎÏÊ ÉÎÆÏÒÍÁÃÉÉ.</para>
-    </sect2>
-  </sect1>
-
-  <sect1>
-    <title>âÌÁÇÏÄÁÒÎÏÓÔÉ</title>
-
-    <para>á×ÔÏÒ ×ÙÒÁÖÁÅÔ ÂÌÁÇÏÄÁÒÎÏÓÔÉ ÔÅÍ, ËÔÏ ÐÒÉÎÉÍÁÌ ÕÞÁÓÔÉÅ × ÜÔÏÍ
-      ÐÒÏÅËÔÅ:</para>
-
-    <itemizedlist>
-      <listitem>
-	<para>Darryl Okahata (<email>darrylo@hpnmhjw.sr.hp.com</email>) ÚÁ
-	  ÐÏÎÑÔÎÏÅ ÏÐÉÓÁÎÉÅ ÎÁÓÔÒÏÊËÉ ÄÉÓËÁ ÄÌÑ ÒÅÖÉÍÁ ÜËÓËÌÀÚÉ×ÎÏÇÏ
-	  ÉÓÐÏÌØÚÏ×ÁÎÉÑ, ËÏÔÏÒÏÅ Ñ ÐÏÓÔÏÑÎÎÏ ÉÓÐÏÌØÚÕÀ × ÓÐÉÓËÅ ÒÁÓÓÙÌËÉ
-	  FreeBSD-questions.</para>
-      </listitem>
-
-      <listitem>
-	<para>&a.jkh; ÚÁ ÔÏ, ÞÔÏ ÏÎ ÓÄÅÌÁÌ sysinstall ÐÏÄÈÏÄÑÝÉÍ
-	  ÉÎÓÔÒÕÍÅÎÔÏÍ ÄÌÑ ×ÙÐÏÌÎÅÎÉÑ ÔÁËÉÈ ÒÁÂÏÔ.</para>
-      </listitem>
-
-      <listitem>
-	<para>John Fieber (<email>jfieber@indiana.edu</email>) ÚÁ ÓÏÚÄÁÎÉÅ
-	  ÐÒÉÍÅÒÏ× É ÐÒÅÄÏÓÔÁ×ÌÅÎÉÅ ÉÎÆÏÒÍÁÃÉÉ Ï DocBook DTD, ÎÁ ÏÓÎÏ×Å ÞÅÇÏ
-	  ÎÁÐÉÓÁÎ ÜÔÏÔ ÄÏËÕÍÅÎÔ.</para>
-      </listitem>
-
-      <listitem>
-	<para>&a.grog; ÚÁ ÐÒÏ×ÅÒËÕ ÍÏÅÊ ÒÁÂÏÔÙ É ÕËÁÚÁÎÉÑ ÎÁ ÎÅÔÏÞÎÏÓÔÉ,
-	  Á ÔÁËÖÅ ÚÁ ÐÏÄÄÅÒÖËÕ.</para>
-      </listitem>
-    </itemizedlist>
-  </sect1>
-</article>
diff --git a/ru_RU.KOI8-R/articles/hats/Makefile b/ru_RU.KOI8-R/articles/hats/Makefile
deleted file mode 100644
index 7ec525e935..0000000000
--- a/ru_RU.KOI8-R/articles/hats/Makefile
+++ /dev/null
@@ -1,22 +0,0 @@
-#
-# The FreeBSD Russian Documentation Project
-#
-# $FreeBSD$
-# $FreeBSDru: frdp/doc/ru_RU.KOI8-R/articles/hats/Makefile,v 1.1 2005/05/28 17:22:18 andy Exp $
-#
-# Article: Working with Hats
-#
-# Original revision: r20561
-#
-
-DOC?= article
-
-FORMATS?= html
-
-INSTALL_COMPRESSED?=gz
-INSTALL_ONLY_COMPRESSED?=
-
-SRCS=	article.sgml
-
-DOC_PREFIX?= ${.CURDIR}/../../..
-.include "${DOC_PREFIX}/share/mk/doc.project.mk"
diff --git a/ru_RU.KOI8-R/articles/hats/article.sgml b/ru_RU.KOI8-R/articles/hats/article.sgml
deleted file mode 100644
index ac61e0bdd8..0000000000
--- a/ru_RU.KOI8-R/articles/hats/article.sgml
+++ /dev/null
@@ -1,137 +0,0 @@
-<?xml version="1.0" encoding="koi8-r" standalone="no"?>
-<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V4.2-Based Extension//EN"
-	"../../../share/sgml/freebsd42.dtd" [
-<!ENTITY % entities PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Entity Set//RU" "../../share/sgml/entities.ent">
-%entities;
-]>
-
-<!--
-     The FreeBSD Russian Documentation Project
-
-     $FreeBSDru: frdp/doc/ru_RU.KOI8-R/articles/hats/article.sgml,v 1.3 2007/05/15 08:01:21 gad Exp $
-
-     Original revision: r28570
--->
-
-<article lang='ru'>
-  <articleinfo>
-    <title>òÁÂÏÔÁ ÄÏÌÖÎÏÓÔÎÙÈ ÌÉÃ</title>
-
-    <authorgroup>
-      <author>
-	<firstname>õÏÒÎÅÒ</firstname>
-	<surname>ìÏÛ</surname>
-	<contrib>ôÅËÓÔ ÐÒÅÄÏÓÔÁ×ÉÌ</contrib>
-      </author>
-    </authorgroup>
-
-    <copyright>
-      <year>2002</year>
-      <year>2003</year>
-      <holder role="mailto:imp@FreeBSD.org">õÏÒÎÅÒ ìÏÛ</holder>
-    </copyright>
-
-    <pubdate>$FreeBSD$</pubdate>
-
-    <releaseinfo>$FreeBSD$</releaseinfo>
-  </articleinfo>
-
-  <note>
-    <para>üÔÏÔ ÄÏËÕÍÅÎÔ ÎÅ Ñ×ÌÑÅÔÓÑ ÏÆÉÃÉÁÌØÎÙÍ ÚÁÑ×ÌÅÎÉÅÍ ðÒÁ×ÌÅÎÉÑ, ÎÏ
-      ÐÅÒÓÏÎÁÌØÎÏÊ ÉÎÔÅÒÐÒÅÔÁÃÉÅÊ ÏÄÎÏÇÏ ÉÚ ÅÇÏ ÞÌÅÎÏ× ÐÏÚÉÃÉÉ ðÒÁ×ÌÅÎÉÑ, ËÁË
-      ÄÅÊÓÔ×ÉÔÅÌØÎÏÇÏ ÞÌÅÎÁ ðÒÁ×ÌÅÎÉÑ É ËÁË ÂÙ×ÛÅÇÏ ÒÕËÏ×ÏÄÉÔÅÌÑ ÄÅÐÁÒÔÁÍÅÎÔÁ
-      ÂÅÚÏÐÁÓÎÏÓÔÉ.  üÔÏ ×ÓÅÇÏ ÌÉÛØ ÏÂÝÉÅ ÕËÁÚÁÎÉÑ, Á ÎÅ ÐÁÌËÁ ÄÌÑ ÂÉÔØÑ.  ëÁË
-      &man.style.9; ×ÙÓÔÕÐÁÅÔ × ÒÏÌÉ ÏÂÝÅÇÏ ÒÕËÏ×ÏÄÓÔ×Á ÄÌÑ ÎÁÐÉÓÁÎÉÑ ÉÓÈÏÄÎÏÇÏ
-      ËÏÄÁ, ÔÁË É ÜÔÏÔ ÄÏËÕÍÅÎÔ ÎÅ ÐÒÅÔÅÎÄÕÅÔ ÎÁ ÒÏÌØ ÔÅÓÎÏÇÏ ËÏÓÔÀÍÁ.</para>
-  </note>
-
-  <para>ëÏÇÄÁ ÕÐÒÁ×ÌÑÀÝÉÊ ÓÏ×ÅÔ ÎÁÚÎÁÞÁÅÔ ËÏÍÕ-ÔÏ ÄÏÌÖÎÏÓÔØ, ÅÇÏ ÕÞÁÓÔÎÉËÉ
-    ÐÏÌÁÇÁÀÔ, ÞÔÏ ÞÅÌÏ×ÅË ÂÕÄÅÔ ÏÔ×ÅÞÁÔØ ÚÁ ÏÐÒÅÄÅÌ£ÎÎÕÀ ÞÁÓÔØ ÄÅÒÅ×Á ÉÓÈÏÄÎÙÈ
-    ÔÅËÓÔÏ×.  ðÒÁ×ÌÅÎÉÅ ÓÞÉÔÁÅÔ, ÞÔÏ ÎÁÚÎÁÞÅÎÎÏÊ ÐÅÒÓÏÎÅ ÂÕÄÅÔ ÐÒÉÎÁÄÌÅÖÁÔØ
-    ÐÏÓÌÅÄÎÅÅ ÓÌÏ×Ï × ÜÔÏÊ ÏÂÌÁÓÔÉ ËÏÄÁ, ÌÉÂÏ ÞÅÌÏ×ÅË ÂÕÄÅÔ ÐÏÎÉÍÁÔØ, ÞÔÏ ÅÇÏ
-    Ë×ÁÌÉÆÉËÁÃÉÉ ÎÅ È×ÁÔÁÅÔ, É ÏÂÒÁÔÉÔÓÑ ÚÁ Ë×ÁÌÉÆÉÃÉÒÏ×ÁÎÎÏÊ ÐÏÍÏÝØÀ.
-    ðÒÁ×ÌÅÎÉÅ ÒÁÓÓÞÉÔÙ×ÁÅÔ ÎÁ ÔÏ, ÞÔÏ ÜÔÏÔ ÞÅÌÏ×ÅË ÂÕÄÅÔ ÒÕËÏ×ÏÄÉÔØ
-    ÒÁÚÒÁÂÏÔËÁÍÉ ÜÔÏÊ ÞÁÓÔÉ ËÏÄÁ.  éÎÏÇÄÁ ÜÔÏ ÏÚÎÁÞÁÅÔ ×ÅÄÅÎÉÅ ÅÖÅÄÎÅ×ÎÏÊ
-    ÐÒÏÁËÔÉ×ÎÏÊ ÄÅÑÔÅÌØÎÏÓÔÉ, Á × ÎÅËÏÔÏÒÙÈ ÓÌÕÞÁÑÈ ÐÒÅÄÐÏÌÁÇÁÅÔ ÒÅÁËÔÉ×ÎÙÊ
-    ÐÏÄÈÏÄ Ë ÐÒÏÓÍÏÔÒÕ ËÏÄÁ, ÒÁÚÍÅÝÁÅÍÏÇÏ × ÄÅÒÅ×Å ÉÓÈÏÄÎÙÈ ÔÅËÓÔÏ×.</para>
-
-  <para>ëÏÇÄÁ ÒÁÚÒÁÂÏÔÞÉËÉ ÐÒÅÄÌÁÇÁÀÔ ÐÁÔÞÉ, ËÏÔÏÒÙÅ ÐÏÔÅÎÃÉÁÌØÎÏ ÍÏÇÕÔ
-    ÏÔÒÁÚÉÔØÓÑ ÎÁ ÄÁÎÎÏÊ ÏÂÌÁÓÔÉ ÄÅÒÅ×Á ÉÓÈÏÄÎÙÈ ÔÅËÓÔÏ×, ðÒÁ×ÌÅÎÉÅ ÏÖÉÄÁÅÔ,
-    ÞÔÏ ÄÏÌÖÎÏÓÔÎÏÅ ÌÉÃÏ ÉÌÉ ÅÇÏ ÐÏÌÎÏÍÏÞÎÙÊ ÐÒÅÄÓÔÁ×ÉÔÅÌØ ÐÒÏÓÍÏÔÒÑÔ ÜÔÉ
-    ÐÁÔÞÉ.  ðÒÁ×ÌÅÎÉÅ ÐÏÌÁÇÁÅÔ, ÞÔÏ ÄÏÌÖÎÏÓÔÎÏÅ ÌÉÃÏ ÂÕÄÅÔ ÒÁÂÏÔÁÔØ Ó
-    ÞÅÌÏ×ÅËÏÍ, ÐÒÅÄÌÏÖÉ×ÛÉÍ ÐÁÔÞ, ÄÌÑ ÒÅÛÅÎÉÑ ÐÒÏÂÌÅÍ, ËÏÔÏÒÙÅ ÍÏÇÕÔ ×ÏÚÎÉËÎÕÔØ
-    Ó ÜÔÉÍ ÐÁÔÞÅÍ.  ðÒÁ×ÌÅÎÉÅ ÓÞÉÔÁÅÔ, ÞÔÏ ÄÏÌÖÎÏÓÔÎÏÅ ÌÉÃÏ ÐÒÅÄÌÏÖÉÔ ÒÅÛÅÎÉÑ É
-    ÂÕÄÅÔ ÒÁÂÏÔÁÔØ Ó ÒÁÚÒÁÂÏÔÞÉËÏÍ ÄÏ ÍÏÍÅÎÔÁ ÄÏÓÔÉÖÅÎÉÑ ËÏÍÐÒÏÍÉÓÓÁ.
-    ðÒÁ×ÌÅÎÉÅ ÏÖÉÄÁÅÔ ÏÔ ÄÏÌÖÎÏÓÔÎÏÇÏ ÌÉÃÁ ËÏÒÒÅËÔÎÏÇÏ ÐÏ×ÅÄÅÎÉÑ.  ÷ ÐÏÒÑÄËÅ
-    ×ÅÝÅÊ ÔÒÅÂÏ×ÁÔØ ÏÔ ÄÏÌÖÎÏÓÔÎÙÈ ÌÉà ÓÌÅÄÏ×ÁÎÉÑ ÏÂÙÞÎÙÍ ÐÒÁ×ÉÌÁÍ ÐÒÏÅËÔÁ ÐÒÉ
-    ÐÒÏÓÍÏÔÒÅ ÐÁÔÞÅÊ (Ë ÐÒÉÍÅÒÕ, ÞÔÏ ÏÎÉ × ÃÅÌÏÍ ÓÏÏÔ×ÅÔÓÔ×ÕÀÔ &man.style.9;
-    ÉÌÉ ÏÂÝÅÐÒÉÎÑÔÏÍÕ ÆÏÒÍÁÔÕ ÆÁÊÌÁ, ÞÔÏ ÉÚÍÅÎÅÎÉÑ × ÏÆÏÒÍÌÅÎÉÉ É ÓÏÄÅÒÖÉÍÏÍ
-    ÆÁÊÌÁ ÂÕÄÕÔ ×ÙÐÏÌÎÑÔØÓÑ ÏÔÄÅÌØÎÏ.).</para>
-
-  <para>ðÒÉ ×ÏÚÎÉËÎÏ×ÅÎÉÉ ÒÁÚÎÏÇÌÁÓÉÊ ðÒÁ×ÌÅÎÉÅ ÏÖÉÄÁÅÔ, ÞÔÏ ÄÏÌÖÎÏÓÔÎÏÅ
-    ÌÉÃÏ ÐÒÉÌÏÖÉÔ ×ÓÅ ÕÓÉÌÉÑ ÄÌÑ ÎÁÈÏÖÄÅÎÉÑ ËÏÍÐÒÏÍÉÓÓÁ ÌÉÂÏ ÄÒÕÇÏÇÏ ÓÐÏÓÏÂÁ
-    ÒÁÚÒÅÛÅÎÉÑ ËÏÎÆÌÉËÔÁ.  äÏÌÖÎÏÓÔÎÏÅ ÌÉÃÏ ÄÏÌÖÎÏ ÏÂÝÁÔØÓÑ ÓÏ ×ÓÅÍÉ
-    ÕÞÁÓÔÎÉËÁÍÉ ËÏÒÒÅËÔÎÏ.  ðÒÁ×ÌÅÎÉÅ ÐÏÎÉÍÁÅÔ, ÞÔÏ × ÏÓÏÂÏ ÏÓÔÒÙÈ ÓÌÕÞÁÑÈ
-    ÄÏÌÖÎÏÓÔÎÏÍÕ ÌÉÃÕ ÔÒÅÂÕÅÔÓÑ ÂÏÌØÛÁÑ ÄÕÂÉÎËÁ É ×ÏÚÍÏÖÎÏÓÔØ ÓËÁÚÁÔØ
-    <quote>ÎÅÔ, ÜÔÏ ÉÚÍÅÎÅÎÉÅ ÎÁÍ ÎÅ ÐÏÄÈÏÄÉÔ É ÎÅ ÍÏÖÅÔ ÂÙÔØ ×ËÌÀÞÅÎÏ ×
-    ÉÓÈÏÄÎÙÊ ËÏÄ (ÉÌÉ ÄÏÌÖÎÏ ÂÙÔØ ÏÔÍÅÎÅÎÏ)</quote>.  ðÒÁ×ÌÅÎÉÅ ÒÁÓÓÍÁÔÒÉ×ÁÅÔ
-    ÜÔÏ ÐÒÏÑ×ÌÅÎÉÅ ×ÌÁÓÔÉ ËÁË ÐÏÓÌÅÄÎÅÅ ÉÚ ×ÏÚÍÏÖÎÙÈ ÓÒÅÄÓÔ×, É ÎÅ ÂÕÄÅÔ
-    ÏÄÏÂÒÑÔØ ÄÅÊÓÔ×ÉÑ ÄÏÌÖÎÏÓÔÎÙÈ ÌÉÃ, ÐÒÉÍÅÎÑÀÝÉÈ ÅÇÏ ÓÌÉÛËÏÍ ÞÁÓÔÏ ÉÌÉ ×
-    ËÁÞÅÓÔ×Å ÐÅÒ×ÏÊ ÒÅÁËÃÉÉ.</para>
-
-  <para>úÁÞÁÓÔÕÀ ÒÅÁÌØÎÁÑ ÖÉÚÎØ ÐÅÒÅÓÅËÁÅÔÓÑ Ó ×ÏÚÍÏÖÎÏÓÔØÀ ÄÏÌÖÎÏÓÔÎÏÇÏ ÌÉÃÁ
-    ÐÏ ×ÙÐÏÌÎÅÎÉÀ Ó×ÏÉÈ ÏÂÑÚÁÎÎÏÓÔÅÊ.  õÓÌÏ×ÉÅÍ, ÓÏÂÌÀÄÅÎÉÅ ËÏÔÏÒÏÇÏ ðÒÁ×ÌÅÎÉÅ
-    ÏÂÙÞÎÏ ÔÒÅÂÕÅÔ ÏÔ ÄÏÌÖÎÏÓÔÎÏÇÏ ÌÉÃÁ, Ñ×ÌÑÅÔÓÑ ÎÁÌÉÞÉÅ ÐÒÅÄÓÔÁ×ÉÔÅÌÑ,
-    ËÏÔÏÒÙÊ ÍÏÖÅÔ ×ÙÐÏÌÎÑÔØ ÒÁÂÏÔÕ ÐÒÉ ÏÔÓÕÔÓÔ×ÉÉ ÓÁÍÏÇÏ ÄÏÌÖÎÏÓÔÎÏÇÏ ÌÉÃÁ.
-    ïÖÉÄÁÅÔÓÑ, ÞÔÏ ÜÔÏÔ ÐÒÅÄÓÔÁ×ÉÔÅÌØ Ñ×ÌÑÅÔÓÑ ÁËÔÉ×ÎÙÍ ÕÞÁÓÔÎÉËÏÍ ÔÏÊ ËÏÍÁÎÄÙ,
-    ËÏÔÏÒÏÊ ÒÕËÏ×ÏÄÉÔ ÄÏÌÖÎÏÓÔÎÏÅ ÌÉÃÏ, É ÈÏÒÏÛÏ ÚÎÁÅÔ ×ÓÅ ÐÒÏÂÌÅÍÙ,
-    ÏÔÎÏÓÑÝÉÅÓÑ Ë ÔÏÊ ÞÁÓÔÉ ÄÅÒÅ×Á ÉÓÈÏÄÎÙÈ ÔÅËÓÔÏ×, ËÏÔÏÒÏÊ ÚÁÎÉÍÁÅÔÓÑ
-    ÄÏÌÖÎÏÓÔÎÏÅ ÌÉÃÏ.  ðÒÅÄÐÏÌÁÇÁÅÔÓÑ, ÞÔÏ ÐÒÅÄÓÔÁ×ÉÔÅÌØ ÓÍÏÖÅÔ ÒÁÂÏÔÁÔØ ×
-    ÏÔÓÕÔÓÔ×ÉÅ ÄÏÌÖÎÏÓÔÎÏÇÏ ÌÉÃÁ.  ë ÐÒÉÍÅÒÕ, ÐÒÅÄÓÔÁ×ÉÔÅÌÉ ÒÕËÏ×ÏÄÉÔÅÌÑ
-    ÄÅÐÁÒÔÁÍÅÎÔÁ ÂÅÚÏÐÁÓÎÏÓÔÉ ÒÁÓÓÙÌÁÀÔ ÂÀÌÌÅÔÅÎÉ ÂÅÚÏÐÁÓÎÏÓÔÉ, ËÏÇÄÁ
-    ÒÕËÏ×ÏÄÉÔÅÌÑ ÎÅÔ ÒÑÄÏÍ.  ÷ ÏÓÏÂÙÈ ÓÌÕÞÁÑÈ ÐÒÅÄÓÔÁ×ÉÔÅÌØ ÍÏÖÅÔ ÏÔÌÏÖÉÔØ
-    ÒÅÛÅÎÉÅ ×ÏÐÒÏÓÁ ÄÏ ÐÏÑ×ÌÅÎÉÑ ÄÏÌÖÎÏÓÔÎÏÇÏ ÌÉÃÁ, ÎÏ ÜÔÏ ÄÏÌÖÎÏ ÂÙÔØ ÓËÏÒÅÅ
-    ÉÓËÌÀÞÅÎÉÅÍ, ÞÅÍ ÐÒÁ×ÉÌÏÍ, ÏÓÏÂÅÎÎÏ ÅÓÌÉ ÄÏÌÖÎÏÓÔÎÏÅ ÌÉÃÏ ÄÏÌÖÎÏ ×ÅÒÎÕÔØÓÑ
-    ÔÏÌØËÏ × ÄÁÌ£ËÏÍ ÂÕÄÕÝÅÍ.</para>
-
-  <para>äÏÌÖÎÏÓÔÎÙÅ ÌÉÃÁ ÏÔ×ÅÞÁÀÔ ÐÅÒÅÄ ðÒÁ×ÌÅÎÉÅÍ.  åÓÌÉ ÏÎÉ ÒÁÂÏÔÁÀÔ ÈÏÒÏÛÏ,
-    ÔÏ ðÒÁ×ÌÅÎÉÅ ÏÓÔÁ×ÌÑÀÔ ÉÈ × ÐÏËÏÅ.  åÓÌÉ ÄÏÌÖÎÏÓÔÎÙÅ ÌÉÃÁ Ó ÒÁÂÏÔÏÊ ÎÅ
-    ÓÐÒÁ×ÌÑÀÔÓÑ, ÔÏ ðÒÁ×ÌÅÎÉÅ ÍÏÖÅÔ ÏÓ×ÏÂÏÄÉÔØ ÉÈ ÏÔ ÚÁÎÉÍÁÅÍÏÊ ÄÏÌÖÎÏÓÔÉ.
-    ðÒÅÄÐÏÌÁÇÁÅÔÓÑ, ÞÔÏ ÄÏÌÖÎÏÓÔÎÙÅ ÌÉÃÁ ÒÁÂÏÔÁÀÔ Ó ðÒÁ×ÌÅÎÉÅÍ, ÅÓÌÉ Õ ÎÅÇÏ
-    ÅÓÔØ ÐÒÅÔÅÎÚÉÉ Ë ×ÙÐÏÌÎÅÎÉÀ ÏÂÑÚÁÎÎÏÓÔÅÊ ÄÏÌÖÎÏÓÔÎÙÈ ÌÉÃ.  äÏÌÖÎÏÓÔÎÙÅ ÌÉÃÁ
-    ×ÙÐÏÌÎÑÀÔ ×ÏÌÀ ðÒÁ×ÌÅÎÉÑ.</para>
-
-  <para>éÎÏÇÄÁ ðÒÁ×ÌÅÎÉÅ ×ÙÄ×ÉÇÁÅÔ ÄÏÐÏÌÎÉÔÅÌØÎÙÅ É ÓÐÅÃÉÆÉÞÅÓËÉÅ ÔÒÅÂÏ×ÁÎÉÑ Ë
-    ÏÐÒÅÄÅÌ£ÎÎÏÍÕ ÄÏÌÖÎÏÓÔÎÏÍÕ ÌÉÃÕ, ËÏÔÏÒÙÅ ÏÔÌÉÞÁÀÔÓÑ ÏÔ ÔÒÅÂÏ×ÁÎÉÊ ËÏ ×ÓÅÍ
-    ÏÓÔÁÌØÎÙÍ ÄÏÌÖÎÏÓÔÑÍ.  üÔÉ ÕÓÌÏ×ÉÑ ÓÏ ×ÒÅÍÅÎÅÍ ÍÏÇÕÔ ÍÅÎÑÔØÓÑ.</para>
-
-  <para>ïÔ ËÏÍÍÉÔÔÅÒÏ× É ÐÒÏÞÉÅ ÌÉÃ, ÒÁÂÏÔÁÀÝÉÈ Ó ÄÏÌÖÎÏÓÔÎÙÍÉ ÌÉÃÁÍÉ,
-    ÏÖÉÄÁÅÔÓÑ ÓÏÂÌÀÄÅÎÉÅ ÏÂÝÉÈ ÎÏÒÍ ÐÏ×ÅÄÅÎÉÑ É ÐÒÏÑ×ÌÅÎÉÅ ×ÅÖÌÉ×ÏÓÔÉ ÐÏ
-    ÏÔÎÏÛÅÎÉÀ Ë ÄÏÌÖÎÏÓÔÎÙÍ ÌÉÃÁÍ.  ðÒÅÄÐÏÌÁÇÁÅÔÓÑ, ÞÔÏ ÏÎÉ ÒÁÂÏÔÁÀÔ Ó
-    ÄÏÌÖÎÏÓÔÎÙÍ ÌÉÃÏÍ É ÅÇÏ ÇÒÕÐÐÏÊ ÄÏÑ ×ÙÒÁÂÏÔËÉ ÒÅÛÅÎÉÑ, ÐÏÄÈÏÄÑÝÅÇÏ ×ÓÅÍ.
-    ÷ ÓÌÕÞÁÅ, ÅÓÌÉ ËÏÍÐÒÏÍÉÓÓ ÎÅ ÍÏÖÅÔ ÂÙÔØ ÄÏÓÔÉÇÎÕÔ, ÏÔ ËÏÍÍÉÔÔÅÒÏ× ÏÖÉÄÁÅÔÓÑ
-    ÔÁËÔÉÞÎÏÅ ÓÌÅÄÏ×ÁÎÉÅ ÒÅÛÅÎÉÀ, ÐÒÉÎÑÔÏÍÕ ÄÏÌÖÎÏÓÔÎÙÍ ÌÉÃÏÍ.  ÷
-    ÉÓËÌÀÞÉÔÅÌØÎÙÈ ÓÌÕÞÁÑÈ ÐÒÏÔÉ× ÜÔÏÇÏ ÒÅÛÅÎÉÑ ÍÏÖÅÔ ÂÙÔØ ÐÏÄÁÎÁ ÁÐÅÌÌÑÃÉÑ
-    ðÒÁ×ÌÅÎÉÀ.  ïÄÎÁËÏ ÏÂÙÞÎÏ ðÒÁ×ÌÅÎÉÅ ÎÅ ÏÔÍÅÎÑÅÔ ÒÅÛÅÎÉÑ ÄÏÌÖÎÏÓÔÎÙÈ ÌÉÃ,
-    ÅÓÌÉ ÔÏÌØËÏ ÏÎÉ ÎÅ ÔÅÒÑÀÔ ÄÏ×ÅÒÉÑ ÉÌÉ ÏÂßÅËÔÉ×ÎÏÓÔÉ.  ðÒÁ×ÌÅÎÉÅ ÎÅ Ñ×ÌÑÅÔÓÑ
-    ÔÅÈÎÉÞÅÓËÉÍ ÓÏ×ÅÔÏÍ, É ÎÁÚÎÁÞÁÅÔ ÄÏÌÖÎÏÓÔÎÙÈ ÌÉà ÄÌÑ ×ÙÐÏÌÎÅÎÉÑ ÆÕÎËÃÉÊ
-    ÔÅÈÎÉÞÅÓËÉÈ ÓÏ×ÅÔÏ× ÎÅÂÏÌØÛÉÈ ÍÁÓÛÔÁÂÏ×, ÞÔÏÂÙ ÏÂÓÕÖÄÅÎÉÑ ÐÒÏÈÏÄÉÌÉ ×
-    ÓÏÏÔ×ÅÔÓÔ×ÕÀÝÅÊ ÓÒÅÄÅ.</para>
-
-  <para>åÓÌÉ ËÏÍÍÉÔÔÅÒ ÓÞÉÔÁÅÔ, ÞÔÏ ÄÏÌÖÎÏÓÔÎÏÅ ÌÉÃÏ ÐÒÅ×ÙÛÁÅÔ Ó×ÏÉ ÐÏÌÎÏÍÏÞÉÑ
-    ÉÌÉ ÞÁÓÔÏ ÇÒÕÂÉÔ ÒÁÚÒÁÂÏÔÞÉËÁÍ, ÔÏ ÏÎÉ ÄÏÌÖÎÙ ÓÏÏÂÝÉÔØ Ï ÜÔÏÍ ðÒÁ×ÌÅÎÉÀ.
-    üÔÁ ÐÒÏÂÌÅÍÁ ÍÏÖÅÔ ÉÍÅÔØ ÔÅÈÎÉÞÅÓËÉÊ, ÓÏÃÉÁÌØÎÙÊ ÉÌÉ ÐÒÏÃÅÄÕÒÎÙÊ ÈÁÒÁËÔÅÒ,
-    Á ÍÏÖÅÔ ÐÒÅÄÓÔÁ×ÌÑÔØ ÓÏÂÏÊ ÎÅËÕÀ ËÏÍÂÉÎÁÃÉÀ ÉÌÉ ÐÏÄÍÎÏÖÅÓÔ×Ï ×ÓÅÈ ÕËÁÚÁÎÎÙÈ
-    ÐÒÉÚÎÁËÏ×.  ðÒÁ×ÌÅÎÉÅ ÒÁÓÓÍÏÔÒÉÔ ×ÁÛ ÓÌÕÞÁÊ É ×ÙÎÅÓÅÔ Ó×Ï£ ÒÅÛÅÎÉÅ.
-    ðÒÁ×ÌÅÎÉÅ ÒÁÓÓÍÁÔÒÉ×ÁÅÔ ËÏÎËÒÅÔÎÙÅ ÖÁÌÏÂÙ, Á ÎÅ ÐÒÅÔÅÎÚÉÉ ÏÂÝÅÇÏ ÈÁÒÁËÔÅÒÁ,
-    ÔÁË ËÁË ÉÈ ÌÅÇÞÅ ÒÁÚÒÅÛÉÔØ.</para>
-
-  <para>ðÒÁ×ÌÅÎÉÅ ÓÞÉÔÁÅÔ, ÞÔÏ ËÏÍÍÉÔÔÅÒÙ ÒÁÂÏÔÁÀÔ ×ÍÅÓÔÅ ÎÁÄ ÒÅÛÅÎÉÅÍ Ó×ÏÉÈ
-    ÐÒÏÂÌÅÍ × ÓÏÏÔ×ÅÔÓÔ×ÕÀÝÉÈ ÓÐÉÓËÁÈ ÒÁÓÓÙÌËÉ.  äÏÌÖÎÏÓÔÎÏÅ ÌÉÃÏ É ÅÇÏ ÇÒÕÐÐÁ
-    ÄÏÌÖÎÙ ÏÔÎÏÓÉÔÅÌØÎÏ ÒÅÄËÏ ×ÙÓÔÕÐÁÔØ × ÒÏÌÉ ÉÍÅÎÎÏ ÄÏÌÖÎÏÓÔÎÏÇÏ ÌÉÃÁ, Á
-    ÏÂÙÞÎÏ ËÁË ÐÒÏÓÔÏ ÒÑÄÏ×ÏÊ ËÏÍÍÉÔÔÅÒ.  (ïÄÎÉÍ ÉÚ ÉÓËÌÀÞÅÎÉÅÍ ÉÚ ÜÔÏÇÏ
-    ÐÒÁ×ÉÌÁ Ñ×ÌÑÅÔÓÑ ÄÏÌÖÎÏÓÔØ ÒÕËÏ×ÏÄÉÔÅÌÑ ÄÅÐÁÒÔÁÍÅÎÔÁ ÂÅÚÏÐÁÓÎÏÓÔÉ, ËÏÔÏÒÙÊ
-    ÄÏÌÖÅÎ ÕÓÔÒÁÎÑÔØ ÕÑÚ×ÉÍÏÓÔÉ ×ÔÁÊÎÅ, ÄÏ ÍÏÍÅÎÔÁ ÏÂßÑ×ÌÅÎÉÑ Ï ÉÈ ÎÁÌÉÞÉÉ.)
-    äÏÌÖÎÏÓÔÎÏÅ ÌÉÃÏ ÄÏÌÖÎÏ ÂÙÔØ <quote>ÐÅÒ×ÙÍ ÓÒÅÄÉ ÒÁ×ÎÙÈ</quote>, Á ÎÅ
-    ÐÒÅÄÓÅÄÁÔÅÌÅÍ ÓÏ×ÅÔÁ ÄÉÒÅËÔÏÒÏ×.</para>
-</article>
diff --git a/ru_RU.KOI8-R/articles/multi-os/Makefile b/ru_RU.KOI8-R/articles/multi-os/Makefile
deleted file mode 100644
index a3b6d98cca..0000000000
--- a/ru_RU.KOI8-R/articles/multi-os/Makefile
+++ /dev/null
@@ -1,22 +0,0 @@
-#
-# The FreeBSD Russian Documentation Project
-#
-# $FreeBSD$
-# $FreeBSDru: frdp/doc/ru_RU.KOI8-R/articles/multi-os/Makefile,v 1.1 2005/05/19 15:55:28 gad Exp $
-#
-# Original revision: r20561
-#
-# Article: Installing and Using FreeBSD With Other Operating Systems
-
-DOC?= article
-
-FORMATS?= html
-WITH_ARTICLE_TOC?= YES
-
-INSTALL_COMPRESSED?=gz
-INSTALL_ONLY_COMPRESSED?=
-
-SRCS=	article.sgml
-
-DOC_PREFIX?= ${.CURDIR}/../../..
-.include "${DOC_PREFIX}/share/mk/doc.project.mk"
diff --git a/ru_RU.KOI8-R/articles/multi-os/article.sgml b/ru_RU.KOI8-R/articles/multi-os/article.sgml
deleted file mode 100644
index 9e0d66961a..0000000000
--- a/ru_RU.KOI8-R/articles/multi-os/article.sgml
+++ /dev/null
@@ -1,736 +0,0 @@
-<?xml version="1.0" encoding="koi8-r" standalone="no"?>
-<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V4.2-Based Extension//EN"
-	"../../../share/sgml/freebsd42.dtd" [
-<!ENTITY % entities PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Entity Set//RU" "../../share/sgml/entities.ent">
-%entities;
-]>
-
-<!--
-     The FreeBSD Russian Documentation Project
-
-     $FreeBSDru: frdp/doc/ru_RU.KOI8-R/articles/multi-os/article.sgml,v 1.3 2005/06/10 08:03:28 den Exp $
-     $FreeBSD$
-
-     Original revision: r21891
--->
-
-<article lang="ru">
-  <articleinfo>
-    <title>õÓÔÁÎÏ×ËÁ É ÉÓÐÏÌØÚÏ×ÁÎÉÅ FreeBSD ÓÏ×ÍÅÓÔÎÏ Ó ÄÒÕÇÉÍÉ ÏÐÅÒÁÃÉÏÎÎÙÍÉ ÓÉÓÔÅÍÁÍÉ</title>
-
-    <authorgroup>
-      <author>
-	<firstname>Jay</firstname>
-
-	<surname>Richmond</surname>
-
-	<affiliation>
-	  <address>
-	    <email>jayrich@sysc.com</email>
-	  </address>
-	</affiliation>
-      </author>
-      <author>
-	<firstname>÷ÉÔÁÌÉÊ</firstname>
-	<surname>âÏÇÄÁÎÏ×</surname>
-	<contrib>ðÅÒÅ×ÏÄ ÎÁ ÒÕÓÓËÉÊ ÑÚÙË: </contrib>
-      </author>
-    </authorgroup>
-
-    <pubdate>6 Á×ÇÕÓÔÁ 1996</pubdate>
-
-    <legalnotice id="trademarks" role="trademarks">
-      &tm-attrib.freebsd;
-      &tm-attrib.ibm;
-      &tm-attrib.linux;
-      &tm-attrib.microsoft;
-      &tm-attrib.powerquest;
-      &tm-attrib.general;
-    </legalnotice>
-
-    <releaseinfo>$FreeBSD$</releaseinfo>
-
-    <abstract>
-      <para>÷ ÜÔÏÍ ÄÏËÕÍÅÎÔÅ ÏÐÉÓÙ×ÁÅÔÓÑ ËÁË ÚÁÓÔÁ×ÉÔØ FreeBSD ÎÏÒÍÁÌØÎÏ ÓÏÓÕÝÅÓÔ×Ï×ÁÔØ
-	Ó ÄÒÕÇÉÍÉ ÐÏÐÕÌÑÒÎÙÍÉ ÏÐÅÒÁÃÉÏÎÎÙÍÉ ÓÉÓÔÅÍÁÍÉ, ÔÁËÉÍÉ ËÁË, Linux, &ms-dos;,
-	&os2;, É &windows; 95.  ïÔÄÅÌØÎÏÅ ÓÐÁÓÉÂÏ: Annelise Anderson
-	<email>andrsn@stanford.edu</email>, Randall Hopper
-	<email>rhh@ct.picker.com</email>, É &a.jkh;.</para>
-    </abstract>
-  </articleinfo>
-
-  <sect1>
-    <title>÷×ÅÄÅÎÉÅ</title>
-
-    <para>âÏÌØÛÉÎÓÔ×Ï ÌÀÄÅÊ ÎÅ × ÓÏÓÔÏÑÎÉÉ ÕÓÔÁÎÏ×ÉÔØ ÎÅÓËÏÌØËÏ  ÏÐÅÒÁÃÉÏÎÎÙÈ
-      ÓÉÓÔÅÍ ÂÅÚ ÐÒÉÍÅÎÅÎÉÑ ÄÏÐÏÌÎÉÔÅÌØÎÏÇÏ ×ÉÎÞÅÓÔÅÒÁ ÂÏÌØÛÅÇÏ ÒÁÚÍÅÒÁ.
-      ðÏ ÜÔÏÊ ÐÒÉÞÉÎÅ ÂÙÌÁ ÄÏÂÁ×ÌÅÎÁ ÉÎÆÏÒÍÁÃÉÑ ÐÏ ÒÁÂÏÔÅ Ó EIDE ÄÉÓËÁÍÉ.  óÕÝÅÓÔ×ÕÅÔ
-      ÂÏÌØÛÏÅ ËÏÌÉÞÅÓÔ×Ï ×ÓÅ×ÏÚÍÏÖÎÙÈ ËÏÍÂÉÎÁÃÉÊ ÕÓÔÁÎÁ×ÌÉ×ÁÅÍÙÈ ÏÐÅÒÁÃÉÏÎÎÙÈ ÓÉÓÔÅÍ
-      É ËÏÎÆÉÇÕÒÁÃÉÊ Ö£ÓÔËÏÇÏ ÄÉÓËÁ, ÐÏÜÔÏÍÕ <xref linkend="ch5"/> ÍÏÖÅÔ ÏËÁÚÁÔØÓÑ ÎÁÉÂÏÌÅÅ
-      ÐÏÌÅÚÎÙÍ.  ÷ ÎÅÍ ÓÏÄÅÒÖÁÔÓÑ ÏÐÉÓÁÎÉÑ ÓÐÅÃÉÆÉÞÎÙÈ ÒÁÂÏÞÉÈ ËÏÎÆÉÇÕÒÁÃÉÊ, ÉÓÐÏÌØÚÕÀÝÉÈ ÎÅÓËÏÌØËÏ
-      ÏÐÅÒÁÃÉÏÎÎÙÈ ÓÉÓÔÅÍ.</para>
-
-    <para>þÔÅÎÉÅ ÄÁÎÎÏÇÏ ÄÏËÕÍÅÎÔÁ ÐÒÅÄÐÏÌÁÇÁÅÔ, ÞÔÏ ÎÁ ×ÁÛÅÍ Ö£ÓÔËÏÍ ÄÉÓËÅ
-      ÉÍÅÅÔÓÑ ×ÙÄÅÌÅÎÎÏÅ ÐÒÏÓÔÒÁÎÓÔ×Ï ÄÌÑ ÒÁÚÍÅÝÅÎÉÑ ÄÏÐÏÌÎÉÔÅÌØÎÏÊ ÏÐÅÒÁÃÉÏÎÎÏÊ
-      ÓÉÓÔÅÍÙ.  ÷ÓÑËÉÊ ÒÁÚ, ÐÒÉ ÉÚÍÅÎÅÎÉÉ ÔÁÂÌÉÃÙ ÒÁÚÄÅÌÏ×, ÐÏ×ÙÛÁÅÔÓÑ
-      ÒÉÓË ÐÏÒÞÉ ÄÁÎÎÙÈ ÎÁ ÕÖÅ ÓÕÝÅÓÔ×ÕÀÝÉÈ ÒÁÚÄÅÌÁÈ.  ÷ ÓÌÕÞÁÅ, ÅÓÌÉ ÒÁÚÄÅÌ DOS
-      ÅÄÉÎÓÔ×ÅÎÎÙÊ ÎÁ ×ÁÛÅÍ ÄÉÓËÅ, ×Ù ÍÏÖÅÔÅ ÉÓÐÏÌØÚÏ×ÁÔØ ÕÔÉÌÉÔÕ FIPS, ÎÁÈÏÄÑÝÕÀÓÑ
-      ÎÁ ËÏÍÐÁËÔ-ÄÉÓËÅ Ó FreeBSD × ËÁÔÁÌÏÇÅ <filename>\TOOLS</filename>
-      ÉÌÉ ÎÁ <ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/tools/">ftp</ulink>.
-      ó Å£ ÐÏÍÏÝØÀ ×Ù ÍÏÖÅÔÅ ÉÚÍÅÎÑÔØ ÔÁÂÌÉÃÕ ÒÁÚÄÅÌÏ× ÂÅÚ ÐÏÔÅÒÉ ÄÁÎÎÙÈ.  óÕÝÅÓÔ×ÕÅÔ ÔÁËÖÅ
-      ËÏÍÍÅÒÞÅÓËÁÑ ÐÒÏÇÒÁÍÍÁ <application>&partitionmagic;</application>, ËÏÔÏÒÁÑ ÄÁ£Ô
-      ×ÏÚÍÏÖÎÏÓÔØ ÉÚÍÅÎÑÔØ ÒÁÚÍÅÒ É ÕÄÁÌÑÔØ ÒÁÚÄÅÌÙ ÂÅÚ ÔÑÖ£ÌÙÈ ÐÏÓÌÅÄÓÔ×ÉÊ.</para>
-  </sect1>
-
-  <sect1 id="ch2">
-    <title>ïÂÚÏÒ ÍÅÎÅÄÖÅÒÏ× ÚÁÇÒÕÚËÉ</title>
-
-    <para>îÉÖÅ ÐÒÅÄÓÔÁ×ÌÅÎÙ ÏÐÉÓÁÎÉÑ ÎÅËÏÔÏÒÙÈ ÞÁÓÔÏ ×ÓÔÒÅÞÁÅÍÙÈ ÍÅÎÅÄÖÅÒÏ× ÚÁÇÒÕÚËÉ.
-      ÷ ÚÁ×ÉÓÉÍÏÓÔÉ ÏÔ ÕÓÔÁÎÏ×ÏË ×ÁÛÅÇÏ ËÏÍÐØÀÔÅÒÁ, ×ÏÚÍÏÖÎÏ, ×Ù ÂÕÄÅÔÅ
-      ÉÓÐÏÌØÚÏ×ÁÔØ ÎÅÓËÏÌØËÏ ÉÚ ÎÉÈ ÎÁ ÏÄÎÏÊ ÓÉÓÔÅÍÅ.</para>
-
-    <variablelist>
-      <varlistentry>
-	<term>Boot Easy</term>
-
-	<listitem>
-	  <para>üÔÏÔ ÍÅÎÅÄÖÅÒ ÚÁÇÒÕÚËÉ ÉÓÐÏÌØÚÕÅÔÓÑ ×Ï FreeBSD ÐÏ ÕÍÏÌÞÁÎÉÀ.
-	    ïÎ ÍÏÖÅÔ ÚÁÇÒÕÖÁÔØ ÌÀÂÕÀ ÏÐÅÒÁÃÉÏÎÎÕÀ ÓÉÓÔÅÍÕ, ×ËÌÀÞÁÑ BSD,
-	    &os2; (HPFS), &windows; 95 (FAT É FAT32), É Linux.
-	    òÁÚÄÅÌÙ ×ÙÂÉÒÁÀÔÓÑ Ó ÐÏÍÏÝØÀ ÆÕÎËÃÉÏÎÁÌØÎÙÈ ËÌÁ×ÉÛ.</para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-	<term>&os2; Boot Manager</term>
-
-	<listitem>
-	  <para>üÔÏÔ ÍÅÎÅÄÖÅÒ ÍÏÖÅÔ ÒÁÂÏÔÁÔØ Ó ÒÁÚÄÅÌÁÍÉ FAT, FAT32, HPFS,
-            FFS (FreeBSD), É EXT2 (Linux).  òÁÚÄÅÌÙ ×ÙÂÉÒÁÀÔÓÑ Ó ÐÏÍÏÝØÀ
-            ËÌÁ×ÉÛ ÓÏ ÓÔÒÅÌËÁÍÉ.  The &os2; Boot Manager ÅÄÉÎÓÔ×ÅÎÎÙÊ ÍÅÎÅÄÖÅÒ
-	    ÚÁÇÒÕÚËÉ, ÉÓÐÏÌØÚÕÀÝÉÊ Ó×ÏÊ ÏÔÄÅÌØÎÙÊ ÒÁÚÄÅÌ, × ÏÔÌÉÞÉÉ ÏÔ
-	    ÄÒÕÇÉÈ, ËÏÔÏÒÙÅ ÉÓÐÏÌØÚÕÀÔ master boot record (MBR).  óÌÅÄÏ×ÁÔÅÌØÎÏ,
-	    ÏÎ ÄÏÌÖÅÎ ÂÙÔØ ÕÓÔÁÎÏ×ÌÅÎ ÄÏ 1024 ÃÉÌÉÎÄÒÁ, ÞÔÏÂÙ ÉÚÂÅÖÁÔØ ÐÒÏÂÌÅÍ
-	    Ó ÚÁÇÒÕÚËÏÊ.  äÁÎÎÙÊ ÍÅÎÅÄÖÅÒ ÍÏÖÅÔ ÚÁÇÒÕÖÁÔØ Linux, ÉÓÐÏÌØÚÕÑ LILO,
-	    ËÏÇÄÁ ÐÏÓÌÅÄÎÉÊ ÎÁÈÏÄÉÔÓÑ × ÚÁÇÒÕÚÏÞÎÏÍ ÓÅËÔÏÒÅ ÒÁÚÄÅÌÁ.  óÍÏÔÒÉÔÅ <ulink
-	    url="http://www.linuxresources.com/LDP/HOWTO/HOWTO-INDEX.html">Linux
-	    HOWTOs</ulink> ÄÌÑ ÄÏÐÏÌÎÉÔÅÌØÎÏÊ ÉÎÆÏÒÍÁÃÉÉ Ï ÚÁÇÒÕÚËÅ Linux
-	    Ó ÐÏÍÏÝØÀ the &os2; boot manager.</para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-	<term>OS-BS</term>
-
-	<listitem>
-	  <para>äÁÎÎÙÊ ÍÅÎÅÄÖÅÒ - ÁÌØÔÅÒÎÁÔÉ×Á Boot Easy.  ïÎ ÐÒÅÄÏÓÔÁ×ÌÑÅÔ
-	    ÂÏÌØÛÅ ËÏÎÔÒÏÌÑ ÎÁÄ ÐÒÏÃÅÓÓÏÍ ÚÁÇÒÕÚËÉ, Ó ×ÏÚÍÏÖÎÏÓÔØÀ ×ÙÂÏÒÁ ÒÁÚÄÅÌÁ ÐÏ
-	    ÕÍÏÌÞÁÎÉÀ É booting timeout.  âÅÔÁ ×ÅÒÓÉÉ ÜÔÉÈ ÐÒÏÇÒÁÍÍ ÐÏÚ×ÏÌÑÀÔ ×ÙÂÉÒÁÔØ
-	    ïó Ó ÐÏÍÏÝØÀ ÓÔÒÅÌÏË.  äÁÎÎÕÀ ÐÒÏÇÒÁÍÍÕ ÍÏÖÎÏ ÎÁÊÔÉ ÎÁ ÄÉÓËÅ
-	    Ó FreeBSD × ÐÁÐËÅ <filename class="directory">\TOOLS</filename> ÉÌÉ ÎÁ <ulink
-	      url="ftp://ftp.FreeBSD.org/pub/FreeBSD/tools/">ftp</ulink>.</para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-	<term>LILO, ÉÌÉ  LInux LOader</term>
-
-	<listitem>
-	  <para>ïÇÒÁÎÉÞÅÎÎÙÊ ÍÅÎÅÄÖÅÒ ÚÁÇÒÕÚËÉ.  ðÏÓÌÅ ÎÅËÏÔÏÒÙÈ ÍÁÎÉÐÕÌÑÃÉÊ Ó
-	    ËÏÎÆÉÇÕÒÁÃÉÏÎÎÙÍ ÆÁÊÌÏÍ, ÓÐÏÓÏÂÅÎ ÚÁÇÒÕÖÁÔØ FreeBSD.</para>
-	</listitem>
-      </varlistentry>
-    </variablelist>
-
-    <note id="fat32">
-      <title>îÅÓËÏÌØËÏ ÓÌÏ× ÐÒÏ FAT32</title>
-
-      <para>FAT32 - ÜÔÏ ÚÁÍÅÎÁ ÆÁÊÌÏ×ÏÊ ÓÉÓÔÅÍÙ FAT, ×ÐÅÒ×ÙÅ
-	ÐÏÑ×É×ÛÁÑÓÑ × Microsoft's OEM SR2 Beta release.  ó×ÏÉÍ
-	ÐÏÑ×ÌÅÎÉÅÍ Ë ËÏÎÃÕ 1996 ÇÏÄÁ, FAT32 ÎÁÞÁÌÁ ×ÙÔÅÓÎÑÔØ FAT
-	Ó ËÏÍÐØÀÔÅÒÏ× Ó ÕÓÔÁÎÏ×ÌÅÎÎÏÊ &windows; 95.  FAT32 - ÜÔÏ
-	ÐÒÏÄÏÌÖÅÎÉÅ ÆÁÊÌÏ×ÏÊ ÓÉÓÔÅÍÙ FAT.  ïÎÁ ÐÏÚ×ÏÌÑÅÔ ÉÓÐÏÌØÚÏ×ÁÔØ
-	ËÌÁÓÔÅÒÙ ÍÅÎØÛÅÇÏ ÒÁÚÍÅÒÁ ÄÌÑ ÂÏÌØÛÉÈ Ö£ÓÔËÉÈ ÄÉÓËÏ×.  ôÁËÖÅ
-	ÂÙÌÉ ×ÎÅÓÅÎÙ ÉÚÍÅÎÅÎÉÑ × ÓÔÒÕËÔÕÒÕ ÚÁÇÒÕÚÏÞÎÏÇÏ ÓÅËÔÏÒÁ É × ÔÁÂÌÉÃÕ
-	ÓÅËÔÏÒÏ×, ÓÄÅÌÁ× Å£ ÔÅÍ ÓÁÍÙÍ, ÎÅÓÏ×ÍÅÓÔÉÍÏÊ Ó ÎÅËÏÔÏÒÙÍÉ ÍÅÎÅÄÖÅÒÁÍÉ
-	ÚÁÇÒÕÚËÉ.</para>
-    </note>
-  </sect1>
-
-  <sect1 id="ch3">
-    <title>ðÒÉÍÅÒ ÔÉÐÉÞÎÏÊ ÕÓÔÁÎÏ×ËÉ</title>
-
-    <para>ðÒÅÄÐÏÌÏÖÉÍ, ÞÔÏ Õ ÍÅÎÑ ÅÓÔØ 2 EIDE ÄÉÓËÁ ÂÏÌØÛÏÇÏ ÏÂߣÍÁ.  íÎÅ
-      ÎÁÄÏ ÕÓÔÁÎÏ×ÉÔØ FreeBSD, Linux É &windows; 95.</para>
-
-    <para>÷ÏÔ ËÁË ÂÙ Ñ ÜÔÏ ÓÄÅÌÁÌ:</para>
-
-    <itemizedlist>
-      <listitem>
-	<para><filename>/dev/wd0</filename> (ÐÅÒ×ÙÊ Ö£ÓÔËÉÊ ÄÉÓË)</para>
-      </listitem>
-
-      <listitem>
-	<para><filename>/dev/wd1</filename> (×ÔÏÒÏÊ Ö£ÓÔËÉÊ ÄÉÓË)</para>
-      </listitem>
-    </itemizedlist>
-
-    <para>õ ÏÂÏÉÈ ÄÉÓËÏ× 1416 ÃÉÌÉÎÄÒÁ.</para>
-
-    <procedure>
-      <step>
-	<para>éÓÐÏÌØÚÕÑ  ÚÁÇÒÕÚÏÞÎÕÀ ÄÉÓËÅÔÕ ÏÔ &ms-dos; ÉÌÉ &windows; 95, Ó
-	  ÐÏÍÏÝØÀ ÕÔÉÌÉÔÙ <filename>FDISK.EXE</filename> ÎÁ ÐÅÒ×ÏÍ ÄÉÓËÅ
-	  ÓÏÚÄÁÀ ÐÅÒ×ÉÞÎÙÊ (primary) ÒÁÚÄÅÌ ÒÁÚÍÅÒÏÍ 50&nbsp;MB (35-40
-	  ÄÌÑ &windows; 95, ÐÌÀÓ ÎÅÍÎÏÇÏ Ó×ÏÂÏÄÎÏÇÏ ÍÅÓÔÁ) .  úÁÔÅÍ ÎÁ ×ÔÏÒÏÍ
-	  ÄÉÓËÅ ÓÏÚÄÁÀ ÒÁÚÄÅÌ ÐÏÂÏÌØÛÅ ÄÌÑ ÍÏÉÈ &windows; ÐÒÉÌÏÖÅÎÉÊ É ÄÁÎÎÙÈ.</para>
-	</step>
-
-      <step>
-	<para>ðÅÒÅÚÁÇÒÕÖÁÀÓØ É ÕÓÔÁÎÁ×ÌÉ×ÁÀ &windows; 95 (ÌÅÇÞÅ ÓËÁÚÁÔØ, ÞÅÍ ÓÄÅÌÁÔØ)
-	  ÎÁ ÄÉÓË <filename>C:</filename> .</para>
-      </step>
-
-      <step>
-	<para>äÁÌØÛÅ ÕÓÔÁÎÁ×ÌÉ×ÁÀ Linux.  îÅ Õ×ÅÒÅÎ ÐÒÏ ×ÓÅ ÄÉÓÔÒÉÂÕÔÉ×Ù Linux,
-	  ÎÏ × <ulink url="http://www.slackware.com">Slackware</ulink> LILO
-	  ×ËÌÀÞÅÎ ÐÏ ÕÍÏÌÞÁÎÉÀ (ÓÍÏÔÒÉÔÅ <xref linkend="ch2"/>).  ó ÐÏÍÏÝØÀ
-	   <command>fdisk</command> ÏÔ Linux ×ÙÄÅÌÑÀ ÍÅÓÔÏ ÎÁ ÐÅÒ×ÏÍ
-	  ÄÉÓËÅ (ÐÒÉÍÅÒÎÏ 300&nbsp;MB ÐÏÄ ÂÏÌØÛÏÊ ÒÁÚÄÅÌ root É ÎÅÍÎÏÇÏ ÐÏÄ swap).</para>
-      </step>
-
-      <step>
-	<para>LILO ÕÓÔÁÎÁ×ÌÉ×ÁÀ × ÚÁÇÒÕÚÏÞÎÙÊ ÓÅËÔÏÒ Linux root ÒÁÚÄÅÌÁ, Á ÎÅ ×
-	  MBR (master boot record).</para>
-      </step>
-
-      <step>
-	<para>ïÓÔÁ×ÛÅÅÓÑ ÎÁ ÄÉÓËÁÈ ÍÅÓÔÏ ÏÔÄÁÀ FreeBSD.  õÂÅÖÄÁÀÓØ, ÞÔÏ
-	  ÍÏÊ FreeBSD root ÒÁÚÄÅÌ ÎÅ ×ÙÈÏÄÉÔ ÚÁ ÐÒÅÄÅÌÙ 1024 ÃÉÌÉÎÄÒÁ (ÎÁ ÎÁÛÉÈ
-	  ÇÉÐÏÔÅÔÉÞÅÓËÉÈ 720&nbsp;MB ÄÉÓËÁÈ 1024 ÃÉÌÉÎÄÒ ÒÁ×ÅÎ 528&nbsp;MB).
-	  ðÒÏÓÔÒÁÎÓÔ×Ï ÐÅÒ×ÏÇÏ ÄÉÓËÁ (ÐÒÉÍÅÒÎÏ 270&nbsp;MB) ÏÔÄÁÍ ÐÏÄ ÒÁÚÄÅÌÙ
-	  <filename class="directory">/usr</filename> É <filename class="directory">/</filename>.
-	  ïÓÔÁÔÏË ×ÔÏÒÏÇÏ Ö£ÓÔËÏÇÏ ÄÉÓËÁ (ÅÇÏ ÒÁÚÍÅÒ ÚÁ×ÉÓÉÔ ÏÔ ÒÁÚÍÅÒÁ ÒÁÚÄÅÌÁ ÐÏÄ
-	  &windows; ÐÒÉÌÏÖÅÎÉÑ/ÄÁÎÎÙÅ, ×ÙÄÅÌÅÎÎÏÇÏ ÍÎÏÀ ÎÁ ÐÅÒ×ÏÍ ÛÁÇÅ)
-	  ÍÏÖÎÏ ×ÙÄÅÌÉÔØ ÐÏÄ <filename class="directory">/usr/src</filename> ÒÁÚÄÅÌ É swap
-	  ÐÒÏÓÔÒÁÎÓÔ×Ï.</para>
-      </step>
-
-      <step>
-	<para>ðÒÉ ÐÒÏÓÍÏÔÒÅ × ÐÒÏÇÒÁÍÍÅ <command>fdisk</command> ÏÔ &windows; 95
-	  ÍÏÉ ÄÉÓËÉ ÄÏÌÖÎÙ ×ÙÇÌÑÄÅÔØ ÐÒÉÍÅÒÎÏ ÔÁË:
-
-	  <screen>---------------------------------------------------------------------
-
-                  Display Partition Information
-
-Current fixed disk drive: 1
-
-Partition  Status  Type  Volume_Label  Mbytes  System  Usage
-C: 1          A   PRI DOS                50    FAT**     7%
-   2          A   Non-DOS (Linux)       300             43%
-
-Total disk space is  696 Mbytes (1 Mbyte = 1048576 bytes)
-
-Press Esc to continue
-
----------------------------------------------------------------------
-
-                  Display Partition Information
-
-Current fixed disk drive: 2
-
-Partition  Status  Type  Volume_Label  Mbytes  System  Usage
-D: 1          A   PRI DOS                420   FAT**    60%
-
-Total disk space is  696 Mbytes (1 Mbyte = 1048576 bytes)
-
-Press Esc to continue
-
----------------------------------------------------------------------</screen>
-	  ** FAT16 ÉÌÉ FAT32.  úÁ×ÉÓÉÔ ÏÔ ÔÏÇÏ, ÉÓÐÏÌØÚÕÅÔÓÑ ÌÉ OEM SR2
-	  update.  ðÏÄÒÏÂÎÅÅ × <xref linkend="ch2"/> .</para>
-      </step>
-
-      <step>
-	<para>õÓÔÁÎÁ×ÌÉ×ÁÀ FreeBSD.  ÷ ÎÁÓÔÒÏÊËÁÈ BIOS ÄÌÑ ÍÏÅÇÏ ÐÅÒ×ÏÇÏ ÄÉÓËÁ
-	  ÄÏÌÖÎÁ ÓÔÏÑÔØ ÏÐÃÉÑ <quote>NORMAL</quote>.  åÓÌÉ ÜÔÏ ÎÅ ÔÁË, ÔÏ
-	  Ñ ××ÏÖÕ ÒÅÁÌØÎÙÅ ÄÁÎÎÙÅ ÇÅÏÍÅÔÒÉÉ ÄÉÓËÁ ×Ï ×ÒÅÍÑ
-	  ÚÁÇÒÕÚËÉ.  þÔÏÂÙ ÉÈ ÕÚÎÁÔØ - ÚÁÇÒÕÖÁÀ &windows; 95 É ÓÍÏÔÒÀ ÎÅÏÂÈÏÄÉÍÕÀ
-	  ÉÎÆÏÒÍÁÃÉÀ × Microsoft Diagnostics (<filename>MSD.EXE</filename>)
-	  ÉÌÉ ÓÍÏÔÒÀ ÉÈ × BIOS.  ÷×ÏÖÕ <literal>hd0=1416,16,63</literal>,
-	   ÇÄÅ <replaceable>1416</replaceable> - ËÏÌÉÞÅÓÔ×Ï ÃÉÌÉÎÄÒÏ× ÎÁ ÍÏÅÍ
-	  ÄÉÓËÅ, <replaceable>16</replaceable> - ËÏÌÉÞÅÓÔ×Ï ÇÏÌÏ×ÏË,
-	   <replaceable>63</replaceable> - ËÏÌÉÞÅÓÔ×Ï ÓÅËÔÏÒÏ× ÎÁ ÄÏÒÏÖËÕ.</para>
-      </step>
-
-      <step>
-	<para>ðÒÉ ÒÁÚÂÉ×ËÅ ÄÉÓËÁ ÕÓÔÁÎÁ×ÌÉ×ÁÀ Boot Easy ÎÁ ÐÅÒ×ÙÊ Ö£ÓÔËÉÊ
-	  ÄÉÓË.  îÅ ÓÔÏÉÔ ÂÅÓÐÏËÏÉÔØÓÑ Ï ×ÔÏÒÏÍ ÄÉÓËÅ, Ô.Ë. ÔÁÍ ÎÅÞÅÍÕ ÚÁÇÒÕÖÁÔØÓÑ.</para>
-      </step>
-
-      <step>
-	<para>ðÏÓÌÅ ÐÅÒÅÚÁÇÒÕÚËÉ Boot Easy ÄÏÌÖÅÎ ÏÐÒÅÄÅÌÉÔØ ÍÏÉ ÔÒÉ
-	  ÚÁÇÒÕÖÁÅÍÙÈ ÒÁÚÄÅÌÁ, ËÁË DOS (&windows; 95), Linux É BSD (FreeBSD).</para>
-      </step>
-    </procedure>
-  </sect1>
-
-  <sect1 id="ch4">
-    <title>÷ÁÖÎÙÅ ÚÁÍÅÞÁÎÉÑ</title>
-
-    <para>âÏÌØÛÉÎÓÔ×Ï ÏÐÅÒÁÃÉÏÎÎÙÈ ÓÉÓÔÅÍ ÏÞÅÎØ ÐÒÉÄÉÒÞÉ×Ù × ×ÏÐÒÏÓÁÈ, ÇÄÅ É
-      ËÁË ÏÎÉ ÂÕÄÕÔ ÕÓÔÁÎÏ×ÌÅÎÙ ÎÁ ÄÉÓËÅ.  &windows; 95 É DOS ÄÏÌÖÎÙ ÂÙÔØ
-      ÕÓÔÁÎÏ×ÌÅÎÙ × ÐÅÒ×ÉÞÎÙÊ (primary) ÒÁÚÄÅÌ ÎÁ ÐÅÒ×ÏÍ Ö£ÓÔËÏÍ ÄÉÓËÅ.  &os2;
-      ÎÅ ÔÒÅÂÕÅÔ ÔÁËÉÈ ÏÇÒÁÎÉÞÅÎÉÊ.  ïÎÁ ÍÏÖÅÔ ÂÙÔØ ÕÓÔÁÎÏ×ÌÅÎÁ ÎÁ ÐÅÒ×ÙÊ ÉÌÉ
-      ×ÔÏÒÏÊ ÄÉÓË × ÐÅÒ×ÉÞÎÙÊ (primary) ÉÌÉ ÒÁÓÛÉÒÅÎÎÙÊ (extended) ÒÁÚÄÅÌ.  åÓÌÉ ×Ù ÎÅ
-      Õ×ÅÒÅÎÙ, ÔÏ ÒÁÓÐÏÌÁÇÁÊÔÅ ÎÁÞÁÌÏ ÚÁÇÒÕÚÏÞÎÙÈ ÒÁÚÄÅÌÏ× ÄÏ 1024 ÃÉÌÉÎÄÒÁ.</para>
-
-    <para>åÓÌÉ ×Ù ÕÓÔÁÎÁ×ÌÉ×ÁÅÔÅ &windows; 95 ÎÁ ËÏÍÐØÀÔÅÒ Ó ÕÖÅ ÕÓÔÁÎÏ×ÌÅÎÎÏÊ BSD
-      ÓÉÓÔÅÍÏÊ, ÔÏ ÕÓÔÁÎÏ×ËÁ <quote>ÕÎÉÞÔÏÖÉÔ</quote> ×ÁÛ MBR, É ×ÁÍ ÎÁÄÏ ÂÕÄÅÔ ÚÁÎÏ×Ï
-      ÐÅÒÅÕÓÔÁÎÏ×ÉÔØ ×ÁÛ ÐÒÅÄÙÄÕÝÉÊ ÚÁÇÒÕÚÞÉË.  Boot Easy ÍÏÖÅÔ ÂÙÔØ
-      ÐÅÒÅÕÓÔÁÎÏ×ÌÅÎ Ó ÐÏÍÏÝØÀ ÐÒÏÇÒÁÍÍÙ <filename>BOOTINST.EXE</filename>,
-      ÒÁÓÐÏÌÏÖÅÎÎÏÊ ÎÁ ÕÓÔÁÎÏ×ÏÞÎÏÍ ÄÉÓËÅ FreeBSD ×
-      ËÁÔÁÌÏÇÅ <filename class="directory">\TOOLS</filename> ÉÌÉ
-      ÎÁ <ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/tools/">ftp</ulink>.
-      ôÁËÖÅ ×Ù ÍÏÖÅÔÅ ÚÁÎÏ×Ï ÎÁÞÁÔØ ÐÒÏÃÅÓÓ ÕÓÔÁÎÏ×ËÉ.  ÷ ÒÅÄÁËÔÏÒÅ ÒÁÚÄÅÌÏ×
-      ÄÌÑ FreeBSD ÒÁÚÄÅÌÁ ÐÏÓÔÁ×ØÔÅ ÆÌÁÇ "ÚÁÇÒÕÚÏÞÎÙÊ", ×ÙÂÅÒÉÔÅ ÍÅÎÅÄÖÅÒ ÚÁÇÒÕÚËÉ,
-      Á ÚÁÔÅÍ ÎÁÖÍÉÔÅ W, ÞÔÏÂÙ ÚÁÐÉÓÁÔØ ((W)rite) ÉÎÆÏÒÍÁÃÉÀ × MBR.  ðÏÓÌÅ ÐÅÒÅÚÁÇÒÕÚÉ
-      Boot Easy ÄÏÌÖÅÎ ÏÐÒÅÄÅÌÉÔØ &windows; 95, ËÁË DOS.</para>
-
-    <para>úÁÍÅÔØÔÅ, ÞÔÏ &os2; ÐÏÄÄÅÒÖÉ×ÁÅÔ FAT É HPFS, ÎÏ ÎÅ FFS (FreeBSD)
-      ÉÌÉ EXT2 (Linux) ÒÁÚÄÅÌÙ.  áÎÁÌÏÇÉÞÎÏ, &windows; 95 ÍÏÖÅÔ ÒÁÂÏÔÁÔØ ÔÏÌØËÏ Ó
-      ÆÁÊÌÏ×ÙÍÉ ÓÉÓÔÅÍÁÍÉ FAT É FAT32 (ÓÍÏÔÒÉÔÅ <xref linkend="ch2"/>).  FreeBSD ÍÏÖÅÔ
-      ÒÁÂÏÔÁÔØ Ó ÂÏÌØÛÉÎÓÔ×ÏÍ ÆÁÊÌÏ×ÙÈ ÓÉÓÔÅÍ, ÎÏ ÎÁ ÓÅÇÏÄÎÑÛÎÉÊ ÄÅÎØ ÎÅ
-      ÐÏÄÄÅÒÖÉ×ÁÅÔ HPFS ÒÁÚÄÅÌÙ.  Linux ÍÏÖÅÔ ÞÉÔÁÔØ HPFS ÒÁÚÄÅÌÙ, ÎÏ ÎÅ ÍÏÖÅÔ
-      ÐÉÓÁÔØ ÎÁ ÎÉÈ.  ðÏÓÌÅÄÎÉÅ ×ÅÒÓÉÉ Linux kernel (2.x) ÐÏÄÄÅÒÖÉ×ÁÀÔ &windows; 95
-      VFAT ÒÁÚÄÅÌÙ (VFAT ÐÏÄÄÅÒÖÉ×ÁÅÔ ÄÌÉÎÎÙÅ ÉÍÅÎÁ ÆÁÊÌÏ× × &windows; 95,
-      Á × ÏÓÎÏ×ÎÏÍ ÜÔÏ ÔÏÔ ÖÅ ÓÁÍÙÊ FAT).  Linux ÔÏÖÅ ÕÍÅÅÔ ÒÁÂÏÔÁÔØ Ó ÂÏÌØÛÉÍ
-      ËÏÌÉÞÅÓÔ×ÏÍ ÆÁÊÌÏ×ÙÈ ÓÉÓÔÅÍ.</para>
-  </sect1>
-
-  <sect1 id="ch5">
-    <title>ðÒÉÍÅÒÙ</title>
-
-    <para><emphasis>(çÌÁ×Á ÎÕÖÄÁÅÔÓÑ × ÄÏÒÁÂÏÔËÅ, ÐÏÖÁÌÕÊÓÔÁ ÐÒÉÓÙÌÁÊÔÅ ×ÁÛÉ ÐÒÉÍÅÒÙ
-        ÎÁ ÁÄÒÅÓ <email>jayrich@sysc.com</email>)</emphasis>.</para>
-
-    <para>FreeBSD + &windows; 95:  åÓÌÉ ×Ù ÕÓÔÁÎÏ×ÉÌÉ FreeBSD ÓÌÅÄÏÍ ÚÁ  &windows; 95,
-      ÔÏ × ÍÅÎÀ Boot Easy ×Ù Õ×ÉÄÉÔÅ <literal>DOS</literal>.  üÔÏ É ÅÓÔØ
-      &windows; 95.  åÓÌÉ ÖÅ ×Ù ÕÓÔÁÎÏ×ÉÌÉ &windows; 95 ÐÏÓÌÅ FreeBSD, ÔÏ ÐÏÖÁÌÕÊÓÔÁ
-      ÐÒÏÞÔÉÔÅ <xref linkend="ch4"/> .  åÓÌÉ Õ ×ÁÛÅÇÏ ÄÉÓËÁ ÍÅÎØÛÅ 1024 ÃÉÌÉÎÄÒÏ×, ÔÏ
-      Õ ×ÁÓ ÎÅ ÄÏÌÖÎÏ ÂÙÔØ ÐÒÏÂÌÅÍ Ó ÚÁÇÒÕÚËÏÊ.  åÓÌÉ ÏÄÉÎ ÉÚ ×ÁÛÉÈ ÒÁÚÄÅÌÏ× ÌÅÖÉÔ
-      ÚÁ ÄÏÐÕÓÔÉÍÙÍÉ ÇÒÁÎÉÃÁÍÉ, Á ÏÔ DOS (&windows; 95) ×Ù ÐÏÌÕÞÁÅÔÅ ÓÏÏÂÝÅÎÉÑ,
-      ÔÉÐÁ <errorname>invalid system disk</errorname>, Á FreeBSD ÏÔËÁÚÙ×ÁÅÔÓÑ
-      ÚÁÇÒÕÖÁÔØÓÑ, ÔÏ ÐÒÏ×ÅÒØÔÅ ÎÁÌÉÞÉÅ ÏÐÃÉÉ <quote>&gt; 1024 cylinder
-      support</quote> ÉÌÉ <quote>NORMAL/LBA</quote> ÒÅÖÉÍÁ × ×ÁÛÅÍ BIOS.  DOS, ÄÌÑ
-      ÎÏÒÍÁÌØÎÏÊ ÚÁÇÒÕÚËÉ, ÍÏÖÅÔ ÎÕÖÄÁÔØÓÑ × LBA (Logical Block Addressing).  åÓÌÉ
-      ÐÅÒÅËÌÀÞÅÎÉÅ ÎÁÓÔÒÏÅË × BIOS ËÁÖÄÙÊ ÒÁÚ ÐÒÉ ÚÁÇÒÕÚËÅ ÎÅ ÐÒÉ×ÌÅËÁÅÔ ×ÁÓ, ÔÏ
-      ×Ù ÍÏÖÅÔÅ ÚÁÇÒÕÖÁÔØ FreeBSD ÉÚ DOS, ÉÓÐÏÌØÚÕÑ ÕÔÉÌÉÔÕ <filename>FBSDBOOT.EXE</filename>,
-      ÒÁÓÐÏÌÏÖÅÎÎÕÀ ÎÁ ×ÁÛÅÍ CD (ÎÁÈÏÄÉÔ FreeBSD ÒÁÚÄÅÌ É ÚÁÇÒÕÖÁÅÔ ÅÇÏ).</para>
-
-    <para>FreeBSD + &os2; + &windows; 95:  The &os2; Boot Manager ÍÏÖÅÔ
-      ÚÁÇÒÕÖÁÔØ ×ÓÅ ÜÔÉ ÓÉÓÔÅÍÙ. äÕÍÁÀ, ÞÔÏ ÚÄÅÓØ ÎÅ ÄÏÌÖÎÏ ÂÙÔØ ÐÒÏÂÌÅÍ.</para>
-
-    <para>FreeBSD + Linux: íÏÖÅÔÅ ÉÓÐÏÌØÚÏ×ÁÔØ Boot Easy.</para>
-
-    <para>FreeBSD + Linux + &windows; 95:  (ÓÍÏÔÒÉÔÅ <xref linkend="ch3"/>)</para>
-  </sect1>
-
-  <sect1 id="sources">
-    <title>äÒÕÇÉÅ ÉÓÔÏÞÎÉËÉ ÉÎÆÏÒÍÁÃÉÉ</title>
-
-    <para>óÕÝÅÓÔ×ÕÅÔ ÂÏÌØÛÏÅ ËÏÌÉÞÅÓÔ×Ï <ulink
-	url="http://www.linuxresources.com/LDP/HOWTO/HOWTO-INDEX.html">Linux
-	HOW-TOs</ulink>, × ËÏÔÏÒÙÈ ÒÁÓÓÍÁÔÒÉ×ÁÀÔÓÑ ×ÏÐÒÏÓÙ ÉÓÐÏÌØÚÏ×ÁÎÉÑ ÎÅÓËÏÌØËÉÈ ÏÐÅÒÁÃÉÏÎÎÙÈ
-        ÓÉÓÔÅÍ ÎÁ ÏÄÎÏÍ ÄÉÓËÅ.</para>
-
-    <para>÷ <ulink
-	url="http://www.linuxresources.com/LDP/HOWTO/mini/Linux+DOS+Win95+OS2.html">Linux+DOS+Win95+OS2
-	mini-HOWTO</ulink> ÍÏÖÎÏ ÎÁÊÔÉ ÉÎÆÏÒÍÁÃÉÀ ÐÏ ÎÁÓÔÒÏÊËÅ &os2; boot
-      manager.  ðÏÌÅÚÎÙÍÉ ÍÏÇÕÔ ÂÙÔØ ÓÌÅÄÕÀÝÉÅ ÓÓÙÌËÉ: <ulink
-	url="http://www.linuxresources.com/LDP/HOWTO/mini/Linux+FreeBSD.html">Linux+FreeBSD
-	mini-HOWTO</ulink>, É <ulink url="http://www.in.net/~jkatz/win95/Linux-HOWTO.html">Linux-HOWTO</ulink>.</para>
-
-    <para>óÔÁÔØÑ <ulink
-	url="http://www.tburke.net/info/ntldr/ntldr_hacking_guide.htm">&windowsnt;
-	Loader Hacking Guide</ulink> ÓÏÄÅÒÖÉÔ ÐÏÌÅÚÎÕÀ ÉÎÆÏÒÍÁÃÉÀ ÐÏ
-	ÍÕÌØÔÉÚÁÇÒÕÚËÅ &windowsnt;, &windows; 95 É DOS Ó ÄÒÕÇÉÍÉ ÏÐÅÒÁÃÉÏÎÎÙÍÉ
-	ÓÉÓÔÅÍÁÍÉ.</para>
-
-    <para>÷ ÁÒÈÉ×Å ÄÏËÕÍÅÎÔÁÃÉÉ ÏÔ Hale Landis <quote>How It Works</quote> ÓÏÄÅÒÖÉÔÓÑ
-      ÍÎÏÇÏ ÉÎÔÅÒÅÓÎÏÊ ÉÎÆÏÒÍÁÃÉÉ ÐÏ ×ÓÅÍ ×ÉÄÁÍ ÇÅÏÍÅÔÒÉÉ ÄÉÓËÁ É ÐÏ ÐÒÏÃÅÓÓÕ
-      ÚÁÇÒÕÚËÉ.  äÏÓÔÕÐÅÎ ÐÏ ÁÄÒÅÓÕ:
-      <ulink url="ftp://fission.dt.wdc.com/pub/otherdocs/pc_systems/how_it_works/allhiw.zip"></ulink>.</para>
-
-    <para>é ÎÁËÏÎÅÃ, ÎÅ ÚÁÂÙ×ÁÊÔÅ ÐÒÏ ÄÏËÕÍÅÎÔÁÃÉÀ ÑÄÒÁ FreeBSD ÐÏ ÐÒÏÃÅÄÕÒÅ
-      ÚÁÇÒÕÚËÉ, ÄÏÓÔÕÐÎÕÀ × ÉÓÈÏÄÎÙÈ ÔÅËÓÔÁÈ ÑÄÒÁ (ÓÍÏÔÒÉÔÅ
-      ÆÁÊÌ <ulink
-      url="file://localhost/usr/src/sys/i386/boot/biosboot/README.386BSD">/usr/src/sys/i386/boot/biosboot/README.386BSD</ulink>.</para>
-  </sect1>
-
-  <sect1>
-    <title>ôÅÈÎÉÞÅÓËÉÅ ÐÏÄÒÏÂÎÏÓÔÉ</title>
-
-    <para><emphasis>(çÌÁ×Õ ÎÁÐÉÓÁÌ Randall Hopper,
-	<email>rhh@ct.picker.com</email>)</emphasis></para>
-
-    <para>÷ ÜÔÏÊ ÇÌÁ×Å Ñ ÐÏÐÙÔÁÀÓØ ÄÁÔØ ÄÏÓÔÁÔÏÞÎÏ ÏÓÎÏ×ÎÏÊ ÉÎÆÏÒÍÁÃÉÉ,
-      ËÁÓÁÀÝÅÊÓÑ Ö£ÓÔËÉÈ ÄÉÓËÏ× É ÐÒÏÃÅÓÓÁ ÚÁÇÒÕÚËÉ, ÔÁË, ÞÔÏÂÙ ÐÒÉ ÎÁÌÉÞÉÉ
-      ÏÐÒÅÄÅÌÅÎÎÙÈ ÐÒÏÂÌÅÍ, Õ ×ÁÓ ÎÅ ×ÏÚÎÉËÌÏ ÔÒÕÄÎÏÓÔÅÊ ÐÒÉ ÉÈ
-      ÒÁÚÒÅÛÅÎÉÉ.  çÌÁ×Á ÎÁÞÉÎÁÅÔÓÑ Ó ÄÏ×ÏÌØÎÏ ÐÒÏÓÔÙÈ ÔÅÒÍÉÎÏ×,
-      ÔÁË ÞÔÏ, ÐÒÉ ÖÅÌÁÎÉÉ ×Ù ÍÏÖÅÔÅ ÓÐÏËÏÊÎÏ ÐÒÏÐÕÓÔÉÔØ ÞÁÓÔØ ÇÌÁ×Ù
-      É ÎÁÞÁÔØ ÞÔÅÎÉÅ Ó ÎÅÚÎÁËÏÍÏÊ ÄÌÑ ×ÁÓ ÉÎÆÏÒÍÁÃÉÉ.</para>
-
-    <sect2>
-      <title>÷×ÏÄÎÁÑ ÉÎÆÏÒÍÁÃÉÑ ÐÏ ÄÉÓËÁÍ</title>
-
-      <para>óÕÝÅÓÔ×ÕÅÔ ÔÒÉ ÆÕÎÄÁÍÅÎÔÁÌØÎÙÈ ÔÅÒÍÉÎÁ, ÏÐÒÅÄÅÌÑÀÝÉÈ
-	ÒÁÓÐÏÌÏÖÅÎÉÅ ÄÁÎÎÙÈ ÎÁ Ö£ÓÔËÏÍ ÄÉÓËÅ: ÃÉÌÉÎÄÒÙ, ÇÏÌÏ×ËÉ É
-	ÓÅËÔÏÒÁ (Cylindres, Heads, Sectors).  óÏ×ÓÅÍ ÎÅ ÏÂÑÚÁÔÅÌØÎÏ
-	ÚÎÁÔØ, ÞÔÏ ÏÚÎÁÞÁÅÔ × ÏÔÄÅÌØÎÏÓÔÉ ËÁÖÄÙÊ ÉÚ ÜÔÉÈ ÔÅÒÍÉÎÏ×,
-	ÇÌÁ×ÎÏÅ, ÞÔÏ ×ÍÅÓÔÅ ÏÎÉ ÏÐÒÅÄÅÌÑÀÔ ÆÉÚÉÞÅÓËÏÅ ÒÁÓÐÏÌÏÖÅÎÉÅ
-	ÄÁÎÎÙÈ ÎÁ ×ÁÛÅÍ ×ÉÎÞÅÓÔÅÒÅ.</para>
-
-      <para>îÁ ÄÉÓËÅ ÎÁÈÏÄÉÔÓÑ ÏÐÒÅÄÅÌÅÎÎÏÅ ËÏÌÉÞÅÓÔ×Ï ÃÉÌÉÎÄÒÏ×, ÇÏÌÏ×ÏË
-	É ÓÅËÔÏÒÏ× ÎÁ ÃÉÌÉÎÄÒ-ÇÏÌÏ×ËÕ (ÄÒÕÇÏÅ ÎÁÚ×ÁÎÉÅ - ÄÏÒÏÖËÁ (track) ).  ÷ÍÅÓÔÅ
-	ÄÁÎÎÁÑ  ÉÎÆÏÒÍÁÃÉÑ ÏÐÒÅÄÅÌÑÅÔ
-	<quote>ÆÉÚÉÞÅÓËÕÀ ÇÅÏÍÅÔÒÉÀ ÄÉÓËÁ</quote>.  ÷ ÏÄÎÏÍ ÓÅËÔÏÒÅ 512 ÂÁÊÔ,
-	É 63 ÓÅËÔÏÒÁ ÎÁ ÏÄÎÏÊ ÄÏÒÏÖËÅ.  ëÏÌÉÞÅÓÔ×Ï ÃÉÌÉÎÄÒÏ× É ÇÏÌÏ×ÏË
-	ÒÁÚÌÉÞÎÏ Õ ËÁÖÄÏÇÏ ÄÉÓËÁ.  ôÁËÉÍ ÏÂÒÁÚÏÍ ÍÏÖÎÏ ÐÏÄÓÞÉÔÁÔØ ÒÁÚÍÅÒ
-	×ÁÛÅÇÏ ÄÉÓËÁ × ÂÁÊÔÁÈ:</para>
-
-	<informalexample>
-	  <para>(# of cylinders) &times; (# heads) &times; (63
-	    sectors/track) &times; (512 bytes/sect)</para>
-	</informalexample>
-
-      <para>÷ÏÚØÍÅÍ, Ë ÐÒÉÍÅÒÕ, ÍÏÊ ÖÅÓÔËÉÊ ÄÉÓË 1.6Gb Western Digital AC31600 EIDE:</para>
-
-	<informalexample>
-	  <para>(3148 cyl) &times; (16 heads) &times; (63
-	    sectors/track) &times; (512 bytes/sect)</para>
-	</informalexample>
-
-      <para>ðÏÌÕÞÁÀ 1,624,670,208 ÂÁÊÔ, ÞÔÏ ÐÒÉÍÅÒÎÏ ÒÁ×ÎÏ 1.6 ÇÉÇÁÂÁÊÔ.</para>
-
-      <para>ëÁË ×Ù ÍÏÖÅÔÅ ÚÁÍÅÔÉÔØ, ÆÉÚÉÞÅÓËÁÑ ÇÅÏÍÅÔÒÉÑ ÄÉÓËÁ
-	(ËÏÌÉÞÅÓÔ×Ï ÃÉÌÉÎÄÒÏ×, ÇÏÌÏ×ÏË É ÓÅËÔÏÒÏ× ÎÁ ÄÏÒÏÖËÕ), ÐÏËÁÚÙ×ÁÅÍÁÑ ×
-	ÐÒÏÇÒÁÍÍÅ ATAID É ×Ï ÍÎÏÇÉÈ ÄÒÕÇÉÈ ÎÅ ÓÏÏÔ×ÅÔÓÔ×ÕÅÔ
-	ÄÅÊÓÔ×ÉÔÅÌØÎÏÓÔÉ.  ÷ÅÒÏÑÔÎÏ ×ÁÛ Ö£ÓÔËÉÊ ÄÉÓË ÔÏÖÅ ÈÁÒÁËÔÅÒÉÚÕÅÔÓÑ
-	ÐÁÒÁÍÅÔÒÁÍÉ, ÐÏÌÕÞÅÎÎÙÍÉ ÜÔÉÍÉ ÐÒÏÇÒÁÍÍÁÍÉ.  âÕÄØÔÅ
-	ÏÓÔÏÒÏÖÎÙ:  ÅÓÌÉ ×Ù ÉÓÐÏÌØÚÕÊÔÅ BIOS LBA (ÓÍÏÔÒÉÔÅ <xref linkend="limits"/>),
-	×Ù ÎÅ ÍÏÖÅÔÅ ÉÓÐÏÌØÚÏ×ÁÔØ ÌÀÂÕÀ ÐÒÏÇÒÁÍÍÕ ÄÌÑ ÐÏÌÕÞÅÎÉÑ
-	ÄÁÎÎÙÈ ÆÉÚÉÞÅÓËÏÊ ÇÅÏÍÅÔÒÉÉ.  üÔÏ ÐÒÏÉÓÈÏÄÉÔ ÐÏ ÐÒÉÞÉÎÅ ÔÏÇÏ,
-	ÞÔÏ ÍÎÏÇÉÅ ÐÒÏÇÒÁÍÍÙ (ÎÁÐÒÉÍÅÒ, <filename>MSD.EXE</filename> ÉÌÉ
-	fdisk ÏÔ FreeBSD) ÎÅ ÒÁÂÏÔÁÀÔ Ó ÆÉÚÉÞÅÓËÏÊ ÇÅÏÍÅÔÒÉÅÊ,
-	×ÍÅÓÔÏ ÜÔÏÇÏ ÏÎÉ ÐÏËÁÚÙ×ÁÀÔ
-	ÄÁÎÎÙÅ <firstterm>ÉÚÍÅÎÅÎÎÏÊ ÇÅÏÍÅÔÒÉÉ</firstterm> (×ÉÒÔÕÁÌØÎÙÅ ÎÏÍÅÒÁ,
-	ÐÏÌÕÞÅÎÎÙÅ Ó ÐÏÍÏÝØÀ LBA).  þÉÔÁÊÔÅ ÄÁÌØÛÅ, ÞÔÏÂÙ ÕÚÎÁÔØ ÞÔÏ ÜÔÏ ÚÎÁÞÉÔ.</para>
-
-      <para>îÏÍÅÒ ÃÉÌÉÎÄÒÁ, ÎÏÍÅÒ ÇÏÌÏ×ËÉ É
-	ÎÏÍÅÒ ÓÅËÔÏÒÁ × ÐÒÅÄÅÌÁÈ ÄÏÒÏÖËÉ ÈÁÒÁËÔÅÒÉÚÕÀÔ ÓÅËÔÏÒ ÎÁ
-	ÄÉÓËÅ (ÂÌÏË ÄÁÎÎÙÈ ÒÁÚÍÅÒÏÍ × 512B).  ãÉÌÉÎÄÒÙ É ÇÏÌÏ×ËÉ ÎÕÍÅÒÕÀÔÓÑ
-	ÎÁÞÉÎÁÑ Ó ÎÕÌÑ, Á ÓÅËÔÏÒÁ Ó ÅÄÉÎÉÃÙ.</para>
-
-      <para>äÌÑ ÔÅÈ ËÔÏ ÚÁÉÎÔÅÒÅÓÏ×ÁÌÓÑ ÄÏÐÏÌÎÉÔÅÌØÎÏÊ ÉÎÆÏÒÍÁÃÉÅÊ, ËÁÓÁÀÝÅÊÓÑ
-	ÇÅÏÍÅÔÒÉÉ ÄÉÓËÁ, ÚÁÇÒÕÚÏÞÎÙÈ ÓÅËÔÏÒÏ×, BIOS É Ô.Ä. ÍÏÇÕÔ ÎÁÊÔÉ ×ÓÅ
-	ÎÅÏÂÈÏÄÉÍÏÅ × ÓÅÔÉ. ðÒÏ×ÅÒØÔÅ Query Lycos, Yahoo É ÄÒ. ÐÏ ËÌÀÞÅ×ÙÍ ÓÌÏ×ÁÍ
-	<literal>boot sector</literal> ÉÌÉ <literal>master boot record</literal>.
-	óÒÅÄÉ ÄÒÕÇÏÊ ÐÏÌÅÚÎÏÊ ÉÎÆÏÒÍÁÃÉÉ, ×Ù ÎÁÊÄÅÔÅ ÁÒÈÉ× ÄÏËÕÍÅÎÔÏ× ÏÔ
-	Hale Landis <citetitle>How It Works</citetitle>.  ÷  <xref
-	  linkend="sources"/> ÎÁÈÏÄÉÔÓÑ ÓÓÙÌËÁ ÎÁ ÜÔÏÔ ÁÒÈÉ×.</para>
-
-      <para>äÏÓÔÁÔÏÞÎÏ ÔÅÒÍÉÎÏÌÏÇÉÉ.  äÁ×ÁÊÔÅ ÐÏÇÏ×ÏÒÉÍ Ï ÚÁÇÒÕÚËÅ.</para>
-    </sect2>
-
-    <sect2 id="booting">
-      <title>ðÒÏÃÅÓÓ ÚÁÇÒÕÚËÉ</title>
-
-      <para>÷ ÐÅÒ×ÏÍ ÓÅËÔÏÒÅ ×ÁÛÅÇÏ ÄÉÓËÁ (0 ÃÉÌÉÎÄÒ, 0 ÇÏÌÏ×ËÁ, 1 ÓÅËÔÏÒ)
-	ÎÁÈÏÄÉÔÓÑ ÇÌÁ×ÎÁÑ ÚÁÇÒÕÚÏÞÎÁÑ ÚÁÐÉÓØ (Master Boot
-	Record (MBR) ).  ÷ ÎÅÊ ÓÏÄÅÒÖÉÔÓÑ ÉÎÆÏÒÍÁÃÉÑ Ï ÒÁÚÄÅÌÁÈ
-	×ÁÛÅÇÏ ÄÉÓËÁ.  ôÁÍ ÍÏÖÅÔ ÈÒÁÎÉÔØÓÑ ÉÎÆÏÒÍÁÃÉÑ Ï 4
-	<firstterm>ÒÁÚÄÅÌÁÈ</firstterm>.  äÌÑ ÏÂÏÚÎÁÞÅÎÉÑ ÒÁÚÄÅÌÏ× ×Ï FreeBSD ÉÓÐÏÌØÚÕÀÔ
-	ÔÅÒÍÉÎ <firstterm>slices</firstterm> (ÓÌÁÊÓÙ), ÞÔÏÂÙ ÎÅ ×ÏÚÎÉËÁÌÏ ÐÕÔÁÎÉÃÙ Ó Å£
-	ÓÏÂÓÔ×ÅÎÎÙÍÉ ÒÁÚÄÅÌÁÍÉ, ÎÏ ÜÔÏ ÎÅ ÏÔÎÏÓÉÔÓÑ Ë ÎÁÛÅÊ ÔÅÍÅ.  îÁ ËÁÖÄÙÊ ÉÚ ÒÁÚÄÅÌÏ×
-	ÍÏÖÎÏ ÕÓÔÁÎÏ×ÉÔØ ÏÐÅÒÁÃÉÏÎÎÕÀ ÓÉÓÔÅÍÕ.</para>
-
-      <para>ëÁÖÄÁÑ ÚÁÐÉÓØ × MBR ÓÏÓÔÏÉÔ ÉÚ ÐÏÌÅÊ <firstterm>Partition
-	  ID</firstterm>, <firstterm>Start Cylinder/Head/Sector</firstterm> É
-	<firstterm>End Cylinder/Head/Sector</firstterm>.  Partition ID
-	ÓÏÏÂÝÁÅÔ ÎÁÍ Ë ËÁËÏÍÕ ÔÉÐÕ ÆÁÊÌÏ×ÏÊ ÓÉÓÔÅÍÙ (Ë ËÁËÏÊ ïó) ÏÔÎÏÓÉÔÓÑ ÄÁÎÎÙÊ
-	ÒÁÚÄÅÌ, Á Start/End ÇÏ×ÏÒÉÔ Ï ÍÅÓÔÏÎÁÈÏÖÄÅÎÉÉ ÄÁÎÎÏÇÏ
-	ÒÁÚÄÅÌÁ.  ÷ ÔÁÂÌÉÃÅ <xref linkend="tbl-pid"/> ÐÒÅÄÓÔÁ×ÌÅÎÏ ÎÅÓËÏÌØËÏ
-	ÐÒÉÍÅÒÏ× Partition IDs.</para>
-
-      <table id="tbl-pid">
-	<title>Partition IDs</title>
-
-	<tgroup cols="2">
-	  <thead>
-	    <row>
-	      <entry>ID (hex)</entry>
-	      <entry>Description</entry>
-	    </row>
-	  </thead>
-
-	  <tbody>
-	    <row>
-	      <entry>01</entry>
-	      <entry>Primary DOS12 (12-bit FAT)</entry>
-	    </row>
-
-	    <row>
-	      <entry>04</entry>
-	      <entry>Primary DOS16 (16-bit FAT)</entry>
-	    </row>
-
-	    <row>
-	      <entry>05</entry>
-	      <entry>Extended DOS</entry>
-	    </row>
-
-	    <row>
-	      <entry>06</entry>
-	      <entry>Primary big DOS (&gt; 32MB)</entry>
-	    </row>
-
-	    <row>
-	      <entry>0A</entry>
-	      <entry>&os2;</entry>
-	    </row>
-
-	    <row>
-	      <entry>83</entry>
-	      <entry>Linux (EXT2FS)</entry>
-	    </row>
-
-	    <row>
-	      <entry>A5</entry>
-	      <entry>FreeBSD, NetBSD, 386BSD (UFS)</entry>
-	    </row>
-	  </tbody>
-	</tgroup>
-      </table>
-
-      <para>îÅ ×ÓÅ ÒÁÚÄÅÌÙ ÍÏÇÕÔ ÂÙÔØ ÚÁÇÒÕÖÁÅÍÙÍÉ (ÎÁÐÒÉÍÅÒ, Extended
-	DOS).  îÅËÏÔÏÒÙÅ ÍÏÇÕÔ&mdash;ÎÅËÏÔÏÒÙÅ ÎÅÔ.  îÁÓÔÒÏÊËÁ
-	<firstterm>ÚÁÇÒÕÚÏÞÎÏÇÏ ÓÅËÔÏÒÁ ÒÁÚÄÅÌÁ</firstterm>, ÐÒÉÓÕÔÓÔ×ÕÀÝÅÇÏ
-	× ÎÁÞÁÌÅ, ÐÏÚ×ÏÌÑÅÔ ÓÄÅÌÁÔØ ÒÁÚÄÅÌ ÚÁÇÒÕÖÁÅÍÙÍ.</para>
-
-      <para>ëÏÇÄÁ ×Ù ÎÁÓÔÒÁÉ×ÁÅÔÅ ×ÁÛ ÌÀÂÉÍÙÊ ÚÁÇÒÕÚÞÉË,
-	ÏÎ ÐÒÏÓÍÁÔÒÉ×ÁÅÔ MBR ËÁÖÄÏÇÏ ÄÉÓËÁ É ÄÁÅÔ ×ÁÍ ×ÏÚÍÏÖÎÏÓÔØ ÐÒÉÓ×ÏÉÔØ
-	ÉÍÅÎÁ ÎÁÊÄÅÎÎÙÍ ÒÁÚÄÅÌÁÍ. ðÒÉ ÚÁÇÒÕÚËÅ ÉÚ MBR ×ÁÛÅÇÏ ÐÅÒ×ÏÇÏ
-	ÄÉÓËÁ ÚÁÐÕÓËÁÅÔÓÑ ÍÅÎÅÄÖÅÒ ÚÁÇÒÕÚËÉ. ïÎ ÐÒÏÓÍÁÔÒÉ×ÁÅÔ ÉÎÆÏÒÍÁÃÉÀ
-	Ï ×ÙÂÒÁÎÎÏÍ ×ÁÍÉ ÒÁÚÄÅÌÅ É ÉÓÐÏÌØÚÕÅÔ ÚÎÁÞÅÎÉÅ ÐÏÌÑ
-	Start Cylinder/Head/Sector ÄÌÑ ÐÅÒÅÄÁÞÉ ÕÐÒÁ×ÌÅÎÉÑ ÚÁÇÒÕÚÏÞÎÏÍÕ ÓÅËÔÏÒÕ
-	×ÁÛÅÇÏ ÒÁÚÄÅÌÁ.  ÷ Ó×ÏÀ ÏÞÅÒÅÄØ ÜÔÏÔ ÚÁÇÒÕÚÏÞÎÙÊ ÓÅËÔÏÒ ÓÏÄÅÒÖÉÔ
-	ÄÏÓÔÁÔÏÞÎÏ ÉÎÆÏÒÍÁÃÉÉ ÄÌÑ ÚÁÇÒÕÚËÉ ÏÐÅÒÁÃÉÏÎÎÏÊ ÓÉÓÔÅÍÙ.</para>
-
-	<para>ïÄÉÎ ÎÅÍÁÌÏ×ÁÖÎÙÊ ÍÏÍÅÎÔ:  ÎÁ ËÁÖÄÏÍ ÄÉÓËÅ ÅÓÔØ Ó×ÏÊ MBR, ÎÏ
-	ÉÓÐÏÌØÚÕÅÔÓÑ MBR ÔÏÇÏ ÄÉÓËÁ, ËÏÔÏÒÙÊ ÏÐÒÅÄÅÌÑÅÔÓÑ BIOS
-	ÐÅÒ×ÙÍ.  åÓÌÉ Õ ×ÁÓ ÔÏÌØËÏ IDE ÄÉÓËÉ,
-	ÔÏ ÏÓÎÏ×ÎÙÍ ÂÕÄÅÔ ÐÅÒ×ÙÊ ÄÉÓË ÎÁ ÐÅÒ×ÏÍ ËÏÎÔÒÏÌ£ÒÅ.  ðÏÈÏÖÁÑ
-	ÓÈÅÍÁ É ÄÌÑ SCSI ÄÉÓËÏ×.  åÓÌÉ Õ ×ÁÓ ÉÍÅÅÔÓÑ
-	É IDE, É SCSI ÄÉÓË, ÔÏ BIOS ÐÅÒ×ÙÍ ÏÐÒÅÄÅÌÉÔ IDE ÄÉÓË.  úÁÇÒÕÚÏÞÎÙÊ
-	ÍÅÎÅÄÖÅÒ ÂÕÄÅÔ ÕÓÔÁÎÏ×ÌÅÎ ÎÁ ÐÅÒ×ÙÊ ÏÐÒÅÄÅÌÉ×ÛÉÊÓÑ ÄÉÓË.</para>
-    </sect2>
-
-    <sect2 id="limits">
-      <title>ïÇÒÁÎÉÞÅÎÉÑ ÐÒÉ ÚÁÇÒÕÚËÅ É ÐÒÅÄÕÐÒÅÖÄÅÎÉÑ</title>
-
-      <para>éÎÔÅÒÅÓÎÁÑ ÉÎÆÏÒÍÁÃÉÑ, ËÏÔÏÒÕÀ ÓÔÏÉÔ ÐÒÏÞÉÔÁÔØ.</para>
-
-      <sect3>
-	<title>ïÇÒÁÎÉÞÅÎÉÅ × 1024 ÃÉÌÉÎÄÒÁ É ÞÅÍ ÍÏÖÅÔ ÐÏÍÏÞØ BIOS LBA</title>
-
-	<para>ðÅÒ×ÁÑ ÞÁÓÔØ ÚÁÇÒÕÚÏÞÎÏÇÏ ÐÒÏÃÅÓÓÁ ÐÒÏÉÓÈÏÄÉÔ ÎÁ ÕÒÏ×ÎÅ
-	  BIOS (ÅÓÌÉ ÜÔÏ ÔÅÒÍÉÎ ÎÏ×ÙÊ ÄÌÑ ×ÁÓ, BIOS ÜÔÏ ÐÒÏÇÒÁÍÍÉÒÕÅÍÙÊ
-	  ÞÉÐ, ÎÁÈÏÄÑÝÉÊÓÑ ÎÁ ÍÁÔÅÒÉÎÓËÏÊ ÐÌÁÔÅ, ËÏÔÏÒÙÊ ÏÂÅÓÐÅÞÉ×ÁÅÔ
-	  ËÏÍÐØÀÔÅÒ ÚÁÇÒÕÚÏÞÎÙÍ ËÏÄÏÍ).  é ÔÁË, ÐÅÒ×ÁÑ ÞÁÓÔØ ÐÒÏÃÅÓÓÁ
-	  ÚÁÇÒÕÚËÉ ÍÏÖÅÔ ÐÏÄ×ÅÒÇÁÔØÓÑ ÏÇÒÁÎÉÞÅÎÉÑÍ BIOS.</para>
-
-	<para>îÁ ÄÁÎÎÏÍ ÜÔÁÐÅ ÉÎÔÅÒÆÅÊÓ BIOS ÐÒÏÉÚ×ÏÄÉÔ ÞÔÅÎÉÅ
-	  ÄÉÓËÁ (INT 13H, 2 ÐÏÄÆÕÎËÃÉÑ) É ×ÙÄÅÌÑÅÔ 10 ÂÉÔ ÎÁ ÎÏÍÅÒ
-	  ÃÉÌÉÎÄÒÁ, 8 ÂÉÔ ÎÁ ÎÏÍÅÒ ÇÏÌÏ×ËÉ É 6 ÂÉÔ ÎÁ ÎÏÍÅÒ
-	  ÓÅËÔÏÒÁ.  üÔÏ ÓÉÌØÎÏ ÏÇÒÁÎÉÞÉ×ÁÅÔ ÐÏÌØÚÏ×ÁÔÅÌÅÊ
-	  ÄÁÎÎÏÇÏ ÉÎÔÅÒÆÅÊÓÁ (ÍÅÎÅÄÖÅÒÏ× ÚÁÇÒÕÚËÉ, ÎÁÈÏÄÑÝÉÈÓÑ × MBR, Á
-	  ÔÁËÖÅ ÚÁÇÒÕÚÞÉËÏ× ïó, ÎÁÈÏÄÑÝÉÈÓÑ × ÚÁÇÒÕÚÏÞÎÙÈ ÓÅËÔÏÒÁÈ) ÓÌÅÄÕÀÝÉÍÉ
-	  ÚÎÁÞÅÎÉÑÍÉ:</para>
-
-      <itemizedlist>
-	<listitem>
-	  <para>íÁËÓÉÍÁÌØÎÏ ×ÏÚÍÏÖÎÏÅ ËÏÌÉÞÅÓÔ×Ï ÃÉÌÉÎÄÒÏ× - 1024</para>
-	</listitem>
-
-	<listitem>
-	  <para>íÁËÓÉÍÁÌØÎÏ ×ÏÚÍÏÖÎÏÅ ËÏÌÉÞÅÓÔ×Ï ÇÏÌÏ×ÏË - 256</para>
-	</listitem>
-
-	<listitem>
-	  <para>íÁËÓÉÍÁÌØÎÏ ×ÏÚÍÏÖÎÏÅ ËÏÌÉÞÅÓÔ×Ï ÓÅËÔÏÒÏ× ÎÁ ÄÏÒÏÖËÕ -
-	  64 (ÅÓÌÉ ÔÏÞÎÅÅ, ÔÏ 63, <literal>0</literal>
-	  ÎÅ ÉÓÐÏÌØÚÕÅÔÓÑ)</para>
-	</listitem>
-      </itemizedlist>
-
-	<para>÷ ÎÁÓÔÏÑÝÅÅ ×ÒÅÍÑ Õ Ö£ÓÔËÉÈ ÄÉÓËÏ× ÂÏÌØÛÏÅ ËÏÌÉÞÅÓÔ×Ï
-	  ÃÉÌÉÎÄÒÏ×, ÎÏ ÍÁÌÏ ÇÏÌÏ×ÏË É, ÎÅÓÏÍÎÅÎÎÏ, ÞÔÏ ËÏÌÉÞÅÓÔ×Ï
-	  ÃÉÌÉÎÄÒÏ× × ÓÏ×ÒÅÍÅÎÎÙÈ ×ÉÎÞÅÓÔÅÒÁÈ ÐÒÅ×ÙÛÁÅÔ 1024.  õÞÉÔÙ×ÁÑ
-	  ÄÁÎÎÙÊ ÆÁËÔ É ÉÎÔÅÒÆÅÊÓ BIOS ÍÙ ÔÅÐÅÒØ ÎÅ ÍÏÖÅÍ ÇÒÕÚÉÔØÓÑ Ó
-	  ÌÀÂÏÇÏ ÍÅÓÔÁ ÄÉÓËÁ.  úÁÇÒÕÚÏÞÎÙÊ ËÏÄ (ÍÅÎÅÄÖÅÒÙ ÚÁÇÒÕÚËÉ É
-	  ÚÁÇÒÕÚÞÉËÉ ïó, ÎÁÈÏÄÑÝÉÅÓÑ ÎÁ ×ÓÅÈ
-	  ÚÁÇÒÕÖÁÅÍÙÈ ÒÁÚÄÅÌÁÈ) ÄÏÌÖÅÎ ÒÁÓÐÏÌÁÇÁÔØÓÑ ÄÏ 1024
-	  ÃÉÌÉÎÄÒÁ.  åÓÌÉ Õ ×ÁÓ ÏÂÙÞÎÙÊ ÖÅÓÔËÉÊ ÄÉÓË Ó 16 ÇÏÌÏ×ËÁÍÉ,
-	  ÔÏ ÏÎ ÒÁ×ÅÎ:</para>
-
-	<informalexample>
-	  <para>1024 cyl/disk &times; 16 heads/disk &times; 63
-	    sect/(cyl-head) &times; 512 bytes/sector</para>
-	</informalexample>
-
-	<para>üÔÏ ÐÒÉÍÅÒÎÏ ÒÁ×ÎÏ ÞÁÓÔÏ ÕÐÏÍÉÎÁÅÍÏÍÕ ÌÉÍÉÔÕ × 528MB.</para>
-
-	<para>÷ÏÔ ÚÄÅÓØ ÎÁ ÐÏÍÏÝØ ÐÒÉÈÏÄÉÔ ÒÅÖÉÍ BIOS
-	  LBA (Logical Block Addressing).  BIOS LBA ÐÒÅÄÏÓÔÁ×ÌÑÅÔ
-	  ÐÏÌØÚÏ×ÁÔÅÌÑÍ ×ÙÚÏ×Ï× BIOS API ÄÏÓÔÕÐ Ë ÃÉÌÉÎÄÒÁÍ, ÌÅÖÁÝÉÍ
-	  ×ÙÛÅ 1024 ÃÉÌÉÎÄÒÁ, ÐÏÓÒÅÄÓÔ×ÏÍ ÐÅÒÅÏÐÒÅÄÅÌÅÎÉÑ
-	  ÃÉÌÉÎÄÒÁ.  äÁÎÎÙÊ ÒÅÖÉÍ ÐÅÒÅÎÁÚÎÁÞÁÅÔ ËÏÌÉÞÅÓÔ×Ï ÃÉÌÉÎÄÒÏ× É
-	  ËÏÌÉÞÅÓÔ×Ï ÇÏÌÏ×ÏË, ÄÅÌÁÑ ÅÇÏ ÄÌÑ BIOS ÄÉÓËÏÍ, ×ÉÄÉÍÙÍ
-	  Ó ÍÅÎØÛÉÍ ËÏÌÉÞÅÓÔ×ÏÍ ÃÉÌÉÎÄÒÏ× É ÂÏÌØÛÉÍ ËÏÌÉÞÅÓÔ×ÏÍ
-	  ÇÏÌÏ×ÏË.  äÒÕÇÉÍÉ ÓÌÏ×ÁÍÉ, ÉÓÐÏÌØÚÕÅÔÓÑ ÐÒÅÉÍÕÝÅÓÔ×Ï ÔÏÇÏ ÆÁËÔÁ,
-	  ÞÔÏ Ö£ÓÔËÉÅ ÄÉÓËÉ ÉÍÅÀÔ ÓÒÁ×ÎÉÔÅÌØÎÏ ÎÅÂÏÌØÛÏÅ ËÏÌÉÞÅÓÔ×Ï
-	  ÇÏÌÏ×ÏË É ÇÏÒÁÚÄÏ ÂÏÌØÛÅ ÃÉÌÉÎÄÒÏ×.  ðÒÏÉÓÈÏÄÉÔ ÉÚÍÅÎÅÎÉÅ
-	  ÂÁÌÁÎÓÁ ÍÅÖÄÕ ËÏÌÉÞÅÓÔ×ÏÍ ÃÉÌÉÎÄÒÏ× É ÇÏÌÏ×ÏË, ÔÁË, ÞÔÏ
-	  ÔÅÐÅÒØ ÏÂÁ ÐÁÒÁÍÅÔÒÁ ÕÍÅÝÁÀÔÓÑ × ×ÙÛÅ ÕÐÏÍÑÎÕÔÙÅ
-	  ÏÇÒÁÎÉÞÅÎÉÑ (1024 ÃÉÌÉÎÄÒÁ, 256 ÇÏÌÏ×ÏË).</para>
-
-	<para>ó BIOS LBA ÐÒÅÄÅÌ ÏÂߣÍÁ Ö£ÓÔËÏÇÏ ÄÉÓËÁ ×ÉÒÔÕÁÌØÎÏ
-	  ÕÂÉÒÁÅÔÓÑ (ÐÅÒÅÎÏÓÉÔÓÑ ÎÁ 8çÂ).  åÓÌÉ Õ ×ÁÓ ÐÏÄÄÅÒÖÉ×ÁÅÔÓÑ
-	  LBA BIOS, ÔÏ ×Ù ÍÏÖÅÔÅ ÕÓÔÁÎÏ×ÉÔØ FreeBSD ÉÌÉ ÌÀÂÕÀ ÄÒÕÇÕÀ
-	  ïó × ËÁËÏÅ ÕÇÏÄÎÏ ÍÅÓÔÏ ÎÁ ÄÉÓËÅ, ÎÅ ÂÏÑÓØ 1024 ÃÉÌÉÎÄÒÁ.</para>
-
-	<para>÷ÏÚØÍÅÍ, Ë ÐÒÉÍÅÒÕ, ÍÏÊ Ö£ÓÔËÉÊ ÄÉÓË
-	  1.6 Gig Western Digital. ÷ÏÔ ÄÁÎÎÙÅ ÅÇÏ ÆÉÚÉÞÅÓËÏÊ ÇÅÏÍÅÔÒÉÉ:</para>
-
-	<informalexample>
-	  <para>(3148 cyl, 16 heads, 63 sectors/track, 512
-	    bytes/sector)</para>
-	</informalexample>
-
-	<para>BIOS LBA ÐÒÅÏÂÒÁÚÕÅÔ ÉÈ Ë ×ÉÄÕ:</para>
-
-	<informalexample>
-	  <para>(787 cyl, 64 heads, 63 sectors/track, 512
-	    bytes/sector)</para>
-	</informalexample>
-
-	<para>÷ ÉÔÏÇÅ ÐÏÌÕÞÁÅÔÓÑ ÔÏÔ ÖÅ ÒÁÚÍÅÒ ÄÉÓËÁ, ÎÏ Ó
-	  ËÏÌÉÞÅÓÔ×ÏÍ ÃÉÌÉÎÄÒÏ× É ÇÏÌÏ×ÏË, ÌÅÖÁÝÉÍ × ÐÒÅÄÅÌÁÈ
-	  ÚÎÁÞÅÎÉÊ BIOS API.  îÁ ÏÄÎÏÍ ÉÚ ÍÏÉÈ ÄÉÓËÏ× ÕÓÔÁÎÏ×ÌÅÎÎÙÅ
-	  Linux É FreeBSD ÎÁÈÏÄÑÔÓÑ ÚÁ 1024 ÆÉÚÉÞÅÓËÉÍ
-	  ÃÉÌÉÎÄÒÏÍ.  âÌÁÇÏÄÁÒÑ BIOS LBA, ÏÂÅ ÏÐÅÒÁÃÉÏÎÎÙÅ ÓÉÓÔÅÍÙ
-	  ÎÏÒÍÁÌØÎÏ ÚÁÇÒÕÖÁÀÔÓÑ.</para>
-      </sect3>
-
-      <sect3>
-	<title>÷ÙÄÅÌÅÎÉÅ ÄÏÐÏÌÎÉÔÅÌØÎÏÇÏ ÍÅÓÔÁ ÄÌÑ ÍÅÎÅÄÖÅÒa ÚÁÇÒÕÚËÉ</title>
-
-	<para>äÒÕÇÏÊ ÍÏÍÅÎÔ, ÎÁ ËÏÔÏÒÙÊ ÓÌÅÄÕÅÔ ÏÂÒÁÔÉÔØ
-	  ×ÎÉÍÁÎÉÅ - ×ÙÄÅÌÅÎÉÅ ÐÒÏÓÔÒÁÎÓÔ×Á ÄÌÑ ÍÅÎÅÄÖÅÒÁ
-	  ÚÁÇÒÕÚËÉ.  óÌÅÄÕÅÔ ÈÏÒÏÛÏ ÒÁÚÂÉÒÁÔØÓÑ × ÄÁÎÎÏÍ ×ÏÐÒÏÓÅ, ÞÔÏÂÙ
-	  ÉÚÂÁ×ÉÔØ ÓÅÂÑ ÏÔ ÐÏ×ÔÏÒÎÙÈ ÐÅÒÅÕÓÔÁÎÏ×ÏË ÏÄÎÏÊ ÉÌÉ ÎÅÓËÏÌØËÉÈ
-	  ïó.</para>
-
-	<para>åÓÌÉ ×Ù ÓÍÏÔÒÅÌÉ <xref linkend="booting"/> É ÞÉÔÁÌÉ ÐÒÏ
-	  ÇÌÁ×ÎÕÀ ÚÁÇÒÕÚÏÞÎÕÀ ÚÁÐÉÓØ (MBR), ÚÁÇÒÕÚÏÞÎÙÅ ÓÅËÔÏÒÁ ÒÁÚÄÅÌÏ× É
-	  ÐÒÏÃÅÓÓ ÚÁÇÒÕÚËÉ, ×ÏÚÍÏÖÎÏ Õ ×ÁÓ ÐÏÑ×ÉÌÓÑ ×ÏÐÒÏÓ Ï ÔÏÍ,
-	  ÇÄÅ ×ÁÛ ÍÅÎÅÄÖÅÒ ÚÁÇÒÕÚËÉ ÂÕÄÅÔ ÒÁÓÐÏÌÁÇÁÔØÓÑ.  îÅËÏÔÏÒÙÅ
-	  ÍÅÎÅÄÖÅÒÙ ÄÏ×ÏÌØÎÏ ÍÁÌÙ É ÏÎÉ ×ÍÅÓÔÅ Ó ÔÁÂÌÉÃÅÊ ÒÁÚÄÅÌÏ×
-	  ÎÏÒÍÁÌØÎÏ ÕÍÅÝÁÀÔÓÑ × Master Boot Sector.  äÒÕÇÉÅ ÔÒÅÂÕÀÔ
-	  ÄÏÐÏÌÎÉÔÅÌØÎÏÇÏ ÐÒÏÓÔÒÁÎÓÔ×Á É ÏÂÙÞÎÏ ÉÓÐÏÌØÚÕÀÔ ÎÅÓËÏÌØËÏ
-	  ÓÅËÔÏÒÏ× ÎÁ ÄÏÒÏÖËÅ Ó 0 ÃÉÌÉÎÄÒÏÍ É 0 ÇÏÌÏ×ËÏÊ, ÎÁÈÏÄÑÝÅÊÓÑ
-	   ÐÏÓÌÅ MBR, ÔÁË ËÁË ÏÂÙÞÎÏ ÏÎÁ Ó×ÏÂÏÄÎÁ&hellip;ÏÂÙÞÎÏ.</para>
-
-	<para>÷ ÜÔÏÍ É ÓÏÓÔÏÉÔ ÕÌÏ×ËÁ.  îÅËÏÔÏÒÙÅ ÏÐÅÒÁÃÉÏÎÎÙÅ ÓÉÓÔÅÍÙ,
-	  ×ËÌÀÞÁÑ FreeBSD, ÐÏÚ×ÏÌÑÀÔ ÓÏÚÄÁ×ÁÔØ ÒÁÚÄÅÌÙ, ÎÁÞÉÎÁÀÝÉÅÓÑ
-	  ÓÒÁÚÕ ÐÏÓÌÅ MBR (0 ÃÉÌÉÎÄÒ, 0 ÇÏÌÏ×ËÁ, 2 ÓÅËÔÏÒ).   åÓÌÉ ×
-	  ÐÒÏÇÒÁÍÍÅ sysinstall ×Ù ÕËÁÖÉÔÅ ÐÏÌÎÏÓÔØÀ Ó×ÏÂÏÄÎÙÊ ÄÉÓË
-	  ÉÌÉ Ó Ó×ÏÂÏÄÎÙÍ ÐÒÏÓÔÒÁÎÓÔ×ÏÍ × ÎÁÞÁÌÅ, ÔÏ FreeBSD ÓÏÚÄÁÓÔ
-	  ÒÁÚÄÅÌ, ÎÁÞÉÎÁÀÝÉÊÓÑ ÉÍÅÎÎÏ Ó ÓÁÍÏÇÏ ÎÁÞÁÌÁ ÄÉÓËÁ (ÔÁË ÂÙÌÏ,
-	  ËÏÇÄÁ Ñ × ÐÏÓÌÅÄÎÉÊ ÒÁÚ ÚÁÎÉÍÁÌÓÑ ÜÔÉÍ ×ÏÐÒÏÓÏÍ).  úÁÔÅÍ,
-	  ËÏÇÄÁ ×Ù ÂÕÄÅÔÅ ÕÓÔÁÎÁ×ÌÉ×ÁÔØ ÍÅÎÅÄÖÅÒ ÚÁÇÒÕÚËÉ, ÔÒÅÂÕÀÝÉÊ
-	  ÎÅÓËÏÌØËÏ ÄÏÐÏÌÎÉÔÅÌØÎÙÈ ÓÅËÔÏÒÏ×, ÔÏ ×Ù ÚÁÔÒÅÔÅ ÎÁÞÁÌØÎÙÅ
-	  ÄÁÎÎÙÅ ÐÅÒ×ÏÇÏ ÒÁÚÄÅÌÁ.  ÷ ÓÌÕÞÁÅ Ó FreeBSD, ×Ù ÐÏÔÅÒÑÅÔÅ
-	  disk label, ÞÔÏ ÐÒÉ×ÅÄÅÔ Ë ÎÅ×ÏÚÍÏÖÎÏÓÔÉ ÚÁÇÒÕÚËÉ Ó FreeBSD
-	  ÒÁÚÄÅÌÁ.</para>
-
-	<para>óÁÍÙÊ ÐÒÏÓÔÏÊ ÐÕÔØ ÉÚÂÅÖÁÔØ ÄÁÎÎÏÊ ÐÒÏÂÌÅÍÙ É
-	  ÐÏÚÖÅ ÐÏÐÒÏÂÏ×ÁÔØ ÄÒÕÇÉÅ ÍÅÎÅÄÖÅÒÙ ÚÁÇÒÕÚËÉ - ÐÒÉ ÒÁÚÂÉ×ËÅ
-	  ÄÉÓËÁ ×ÓÅÇÄÁ ÏÓÔÁ×ÌÑÔØ ÐÅÒ×ÕÀ ÄÏÒÏÖËÕ ÄÉÓËÁ ×ÎÅ
-	  ÒÁÚÄÅÌÏ×.  üÔÏ ÚÎÁÞÉÔ, ÞÔÏ ÎÁÄÏ ÏÓÔÁ×ÉÔØ Ó×ÏÂÏÄÎÏÅ ÍÅÓÔÏ,
-	  ÎÁÞÉÎÁÑ Ó 0 ÃÉÌÉÎÄÒÁ, 0 ÇÏÌÏ×ËÉ, 2 ÓÅËÔÏÒÁ ÄÏ 0 ÃÉÌÉÎÄÒÁ, 1 ÇÏÌÏ×ËÉ,
-	  63 ÓÅËÔÏÒÁ É ÓÏÚÄÁÔØ ÐÅÒ×ÙÊ ÒÁÚÄÅÌ, ÎÁÞÉÎÁÀÝÉÊÓÑ Ó
-	  0 ÃÉÌÉÎÄÒÁ, 1 ÇÏÌÏ×ËÉ, 1 ÓÅËÔÏÒÁ.  ðÏÌÅÚÎÏ × ÎÁÞÁÌÅ ÄÉÓËÁ
-	  ÓÏÚÄÁ×ÁÔØ DOS ÒÁÚÄÅÌ, ÔÁË ËÁË ÏÎ ÏÓÔÁ×ÌÑÅÔ ÄÁÎÎÏÅ ÍÅÓÔÏ Ó×ÏÂÏÄÎÙÍ
-	  (ÐÏ ÜÔÏÊ ÐÒÉÞÉÎÅ ÍÅÎÅÄÖÅÒÙ ÚÁÇÒÕÚËÉ ÐÒÅÄÐÏÌÁÇÁÀÔ, ÞÔÏ
-	  ÎÁÞÁÌÏ ÄÉÓËÁ Ó×ÏÂÏÄÎÏ).  ñ ÐÒÅÄÐÏÞÉÔÁÀ ÓÏÚÄÁ×ÁÔØ × ÎÁÞÁÌÅ
-	  ÄÉÓËÁ DOS ÒÁÚÄÅÌ ÒÁÚÍÅÒÏÍ × 1 ÍÅÇÁÂÁÊÔ, ÔÁË ËÁË ÜÔÏ ÔÁËÖÅ ÐÒÅÄÏÔ×ÒÁÝÁÅÔ
-	  ÉÚÍÅÎÅÎÉÑ ÂÕË× ÄÉÓËÏ×, ÐÒÅÄÓÔÁ×ÌÑÀÝÉÈ ÐÅÒ×ÉÞÎÙÅ (primary) ÒÁÚÄÅÌÙ,
-	  ÐÒÉ ÐÏÓÌÅÄÕÀÝÅÍ ÉÚÍÅÎÅÎÉÉ ÔÁÂÌÉÃÙ ÒÁÚÄÅÌÏ×.</para>
-
-	<para>óÌÅÄÕÀÝÉÅ ÍÅÎÅÄÖÅÒÙ ÚÁÇÒÕÚËÉ ÉÓÐÏÌØÚÕÀÔ Master Boot Sector
-	  ÄÌÑ ÈÒÁÎÅÎÉÑ Ó×ÏÅÇÏ ËÏÄÁ É ÄÁÎÎÙÈ:</para>
-
-	<itemizedlist>
-	  <listitem>
-	    <para>OS-BS 1.35</para>
-	  </listitem>
-
-	  <listitem>
-	    <para>Boot Easy</para>
-	  </listitem>
-
-	  <listitem>
-	    <para>LILO</para>
-	  </listitem>
-	</itemizedlist>
-
-	<para>üÔÉ ÍÅÎÅÄÖÅÒÙ ÚÁÇÒÕÚËÉ ÔÒÅÂÕÀÔ ÎÅÓËÏÌØËÏ ÄÏÐÏÌÎÉÔÅÌØÎÙÈ ÓÅËÔÏÒÏ×
-	  ÐÏÓÌÅ Master Boot Sector:</para>
-
-	<itemizedlist>
-	  <listitem>
-	    <para>OS-BS 2.0 Beta 8 (ÓÅËÔÏÒÁ ÓÏ 2 ÐÏ 5)</para>
-	  </listitem>
-
-	  <listitem>
-	    <para>The &os2; boot manager</para>
-	  </listitem>
-	</itemizedlist>
-      </sect3>
-
-      <sect3>
-	<title>þÔÏ ÄÅÌÁÔØ ÅÓÌÉ ËÏÍÐØÀÔÅÒ ×ÄÒÕÇ ÏÔËÁÚÙ×ÁÅÔÓÑ ÚÁÇÒÕÖÁÔØÓÑ?</title>
-
-	<para>÷ ÎÅËÏÔÏÒÙÊ ÍÏÍÅÎÔ, ÐÒÉ ÕÓÔÁÎÏ×ËÅ ÚÁÇÒÕÚÞÉËÏ×, ×ÁÛ MBR ÍÏÖÅÔ
-	  ÏËÁÚÁÔØÓÑ × ÔÁËÏÍ ÓÏÓÔÏÑÎÉÉ, ÞÔÏ ×Ù ÎÅ ÓÍÏÖÅÔÅ
-	  ÚÁÇÒÕÚÉÔØÓÑ.  üÔÏ ÍÁÌÏ×ÅÒÏÑÔÎÏ, ÎÏ ×ÏÚÍÏÖÎÏ, ÎÁÐÒÉÍÅÒ, ÐÒÉ
-	  ÐÏ×ÔÏÒÎÏÍ ÒÁÚÂÉÅÎÉÉ ÄÉÓËÁ Ó ÕÖÅ ÕÓÔÁÎÏ×ÌÅÎÎÙÍ ÚÁÇÒÕÚÞÉËÏÍ.</para>
-
-	<para>åÓÌÉ Õ ×ÁÓ ÉÍÅÅÔÓÑ DOS ÒÁÚÄÅÌ, ÔÏ ×Ù ÍÏÖÅÔÅ ÚÁÇÒÕÚÉÔØÓÑ Ó
-	  ÚÁÇÒÕÚÏÞÎÏÊ DOS ÄÉÓËÅÔÙ É ×ÙÐÏÌÎÉÔØ ËÏÍÁÎÄÕ:</para>
-
-	<informalexample>
-	  <screen>A:\> <userinput>FDISK /MBR</userinput></screen>
-	</informalexample>
-
-	<para>üÔÏ ÚÁÎÏ×Ï ÕÓÔÁÎÏ×ÉÔ × MBR ÚÁÇÒÕÚÏÞÎÙÊ ËÏÄ
-	  DOS.  ôÅÐÅÒØ ×Ù ÍÏÖÅÔÅ ÚÁÇÒÕÖÁÔØ DOS É ÔÏÌØËÏ DOS.
-	  áÎÁÌÏÇÉÞÎÏ, ÐÒÏÓÔÏ ÐÅÒÅÚÁÐÕÓÔÉÔÅ ÕÓÔÁÎÏ×ËÕ ×ÁÛÅÇÏ ÍÅÎÅÄÖÅÒÁ
-	  ÚÁÇÒÕÚËÉ Ó ÚÁÇÒÕÚÏÞÎÏÊ ÄÉÓËÅÔÙ.</para>
-      </sect3>
-    </sect2>
-  </sect1>
-</article>
diff --git a/ru_RU.KOI8-R/articles/version-guide/Makefile b/ru_RU.KOI8-R/articles/version-guide/Makefile
deleted file mode 100644
index 935df9a4fc..0000000000
--- a/ru_RU.KOI8-R/articles/version-guide/Makefile
+++ /dev/null
@@ -1,24 +0,0 @@
-#
-# The FreeBSD Russian Documentation Project
-#
-# $FreeBSDru: frdp/doc/ru_RU.KOI8-R/articles/version-guide/Makefile,v 1.1 2005/10/09 16:19:35 gad Exp $
-# $FreeBSD$
-#
-# Original revision: r25395
-#
-# Article: FreeBSD Version Guide
-
-DOC?= article
-
-FORMATS?= html
-WITH_ARTICLE_TOC?= YES
-
-INSTALL_COMPRESSED?= gz
-INSTALL_ONLY_COMPRESSED?=
-
-SRCS=		article.sgml
-
-URL_RELPREFIX?=	../../../..
-DOC_PREFIX?= ${.CURDIR}/../../..
-
-.include "${DOC_PREFIX}/share/mk/doc.project.mk"
diff --git a/ru_RU.KOI8-R/articles/version-guide/article.sgml b/ru_RU.KOI8-R/articles/version-guide/article.sgml
deleted file mode 100644
index a021c7feea..0000000000
--- a/ru_RU.KOI8-R/articles/version-guide/article.sgml
+++ /dev/null
@@ -1,414 +0,0 @@
-<?xml version="1.0" encoding="koi8-r" standalone="no"?>
-<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V4.2-Based Extension//EN"
-	"../../../share/sgml/freebsd42.dtd" [
-<!ENTITY % freebsd.urls.absolute "INCLUDE">
-<!ENTITY % entities PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Entity Set//RU" "../../share/sgml/entities.ent">
-%entities;
-]>
-
-<!--
-     The FreeBSD Documentation Project
-
-     The FreeBSD Russian Documentation Project
-
-     $FreeBSDru: frdp/doc/ru_RU.KOI8-R/articles/version-guide/article.sgml,v 1.4 2006/02/09 14:56:28 marck Exp $
-     $FreeBSD$
-
-     Original revision: r38989
--->
-
-<article lang="ru">
-  <title>÷ÙÂÏÒ ÐÏÄÈÏÄÑÝÅÊ ÄÌÑ ×ÁÓ ×ÅÒÓÉÉ FreeBSD</title>
-
-  <articleinfo>
-    <authorgroup>
-      <author>
-	<surname>The FreeBSD Documentation Project</surname>
-      </author>
-    </authorgroup>
-
-    <legalnotice id="trademarks" role="trademarks">
-      &tm-attrib.freebsd;
-    </legalnotice>
-
-    <copyright>
-      <year>2005</year>
-      <holder>The FreeBSD Documentation Project</holder>
-    </copyright>
-
-    <pubdate>$FreeBSD$</pubdate>
-
-    <releaseinfo>$FreeBSD$</releaseinfo>
-
-    <abstract>
-      <para>éÔÁË, ×Ù ÒÅÛÉÌÉ ÕÓÔÁÎÏ×ÉÔØ &os;.  äÏÂÒÏ ÐÏÖÁÌÏ×ÁÔØ!  üÔÏÔ
-	ÄÏËÕÍÅÎÔ ÎÁÐÉÓÁÎ ÄÌÑ ÔÏÇÏ, ÞÔÏÂÙ ÐÏÍÏÞØ ×ÁÍ × ×ÙÂÏÒÅ ×ÅÒÓÉÉ ÄÌÑ
-	ÕÓÔÁÎÏ×ËÉ.</para>
-    </abstract>
-  </articleinfo>
-
-  <sect1 id="background">
-    <title>÷×ÏÄÎÁÑ ÉÎÆÏÒÍÁÃÉÑ</title>
-
-    <para>þÔÏÂÙ ÒÅÛÉÔØ ËÁËÁÑ ×ÅÒÓÉÑ &os; ÂÏÌØÛÅ ×ÓÅÇÏ ÐÏÄÈÏÄÉÔ ÄÌÑ ×ÁÛÉÈ
-      ÎÕÖÄ, ×ÁÖÎÏ ÐÏÎÉÍÁÔØ ÎÅÓËÏÌØËÏ ËÏÎÃÅÐÃÉÊ, ËÁÓÁÀÝÉÈÓÑ ÎÁÛÉÈ ÐÒÏÃÅÓÓÏ×
-      ÒÁÚÒÁÂÏÔËÉ É ÐÏÄÇÏÔÏ×ËÉ ÒÅÌÉÚÏ× (Release Engineering, <literal>RE</literal>).</para>
-
-    <para>&os; ÒÁÚÒÁÂÁÔÙ×ÁÅÔÓÑ ÂÏÌØÛÏÊ ÇÒÕÐÐÏÊ ÌÀÄÅÊ, Ñ×ÌÑÀÝÉÈÓÑ ÐÏÞÔÉ
-      ÐÏÌÎÏÓÔØÀ ÄÏÂÒÏ×ÏÌØÃÁÍÉ.  éÓÈÏÄÎÙÊ ËÏÄ ÑÄÒÁ, ÓÁÍÙÈ ÒÁÓÐÒÏÓÔÒÁΣÎÎÙÈ
-      ÂÉÂÌÉÏÔÅË É ÕÔÉÌÉÔ ÐÏÄÄÅÒÖÉ×ÁÅÔÓÑ × <firstterm>ÓÉÓÔÅÍÅ ËÏÎÔÒÏÌÑ
-      ÉÓÈÏÄÎÏÇÏ ËÏÄÁ</firstterm> (source control system) É ÄÏÓÔÕÐÅÎ
-      ÛÉÒÏËÏÊ ÐÕÂÌÉËÅ ÄÌÑ ÓËÁÞÉ×ÁÎÉÑ × ÌÀÂÏÅ ×ÒÅÍÑ.  ïÔÄÅÌØÎÏ,
-      ÓËÏÍÐÉÌÉÒÏ×ÁÎÎÙÅ ×ÅÒÓÉÉ (<literal>ÂÉÎÁÒÎÉËÉ</literal>) ÄÏÓÔÕÐÎÙ ÎÁ
-      ÒÅËÕÒÒÅÎÔÎÏÊ ÏÓÎÏ×Å.  îÅËÏÔÏÒÙÅ ÉÚ ÜÔÉÈ Ä×ÏÉÞÎÙÈ ×ÅÒÓÉÊ ÐÒÏÈÏÄÑÔ
-      ÛÉÒÏËÏÅ ÔÅÓÔÉÒÏ×ÁÎÉÅ É ÚÁÔÅÍ ÏÂÏÚÎÁÞÁÀÔÓÑ, ËÁË <firstterm>release</firstterm>.</para>
-
-    <sect2 id="releases">
-      <title>òÅÌÉÚÙ</title>
-
-      <para>éÍÅÎÁ <literal>òÅÌÉÚÏ×</literal> ÓÔÒÏÑÔÓÑ ÉÚ <firstterm>ÓÔÁÒÛÅÇÏ
-	ÎÏÍÅÒÁ ×ÅÒÓÉÉ</firstterm> É <firstterm>ÍÌÁÄÛÅÇÏ ÎÏÍÅÒÁ
-	×ÅÒÓÉÉ</firstterm>.</para>
-
-      <itemizedlist>
-	<listitem>
-	  <para>ãÅÌØ ÓÔÁÒÛÅÇÏ ÒÅÌÉÚÁ - ××ÅÓÔÉ ÎÏ×ÙÅ ×ÏÚÍÏÖÎÏÓÔÉ.  ôÁË ËÁË
-	    ÎÏ×ÙÅ ÆÕÎËÃÉÏÎÁÌØÎÙÅ ×ÏÚÍÏÖÎÏÓÔÉ ÄÏÂÁ×ÌÑÀÔÓÑ × &os;, Á ÓÔÁÒÙÅ
-	    &mdash; ÓÔÁÎÏ×ÑÔÓÑ ÎÅ×ÏÓÔÒÅÂÏ×ÁÎÙÍÉ ÉÌÉ ÕÄÁÌÑÀÔÓÑ ×ÏÏÂÝÅ, ÔÏ
-	    ×ÏÚÎÉËÁÅÔ ÉÎÏÇÄÁ ÎÅÏÂÈÏÄÉÍÏÓÔØ ÕÂÒÁÔØ ÓÏ×ÍÅÓÔÉÍÏÓÔØ Ó ÐÒÅÄÙÄÕÝÉÍÉ
-	    ÓÔÁÒÛÉÍÉ ÒÅÌÉÚÁÍÉ.</para>
-	</listitem>
-
-	<listitem>
-	  <para>ãÅÌØ ÍÌÁÄÛÅÇÏ ÒÅÌÉÚÁ - × ÏÓÎÏ×ÎÏÍ ÉÓÐÒÁ×ÌÅÎÉÅ ÏÛÉÂÏË É
-	    ÕÌÕÞÛÅÎÉÅ ÐÒÏÉÚ×ÏÄÉÔÅÌØÎÏÓÔÉ É ÓÔÁÂÉÌØÎÏÓÔÉ.  ðÏÄÄÅÒÖÁÎÉÅ Ä×ÏÉÞÎÏÊ
-	    ÓÏ×ÍÅÓÔÉÍÏÓÔÉ É ÓÏ×ÍÅÓÔÉÍÏÓÔÉ ÉÓÈÏÄÎÙÈ ËÏÄÏ× ÍÅÖÄÕ Ä×ÕÍÑ ÍÌÁÄÛÉÍÉ
-	    ÒÅÌÉÚÁÍÉ ÐÒÉÏÒÉÔÅÔÎÏ.  éÎÏÇÄÁ ÎÏ×ÙÅ ×ÏÚÍÏÖÎÏÓÔÉ ÍÏÇÕÔ ÂÙÔØ
-	    ÄÏÂÁ×ÌÅÎÙ × ÍÌÁÄÛÉÊ ÒÅÌÉÚ, ËÏÇÄÁ ×ÉÄÎÏ, ÞÔÏ ÄÒÕÇÉÅ ÃÅÌÉ ÎÅ ÂÕÄÕÔ
-	    ÎÁÒÕÛÅÎÙ.</para>
-	</listitem>
-      </itemizedlist>
-
-      <para>ôÅÍ ÎÅ ÍÅÎÅÅ, ÐÏÍÎÉÔÅ, ÞÔÏ <quote>ÒÅÌÉÚ</quote> - ÜÔÏ
-	ÐÒÏÓÔÏ ÓÎÜÐÛÏÔ ÄÅÒÅ×Á ÉÓÈÏÄÎÏÇÏ ËÏÄÁ × ÏÐÒÅÄÅÌ£ÎÎÙÊ ÍÏÍÅÎÔ ×ÒÅÍÅÎÉ,
-	ËÏÔÏÒÏÍÕ ÐÒÉÓ×ÁÉ×ÁÅÔÓÑ ËÏÎËÒÅÔÎÏÅ ÉÍÑ (<emphasis>ÔÜÇ</emphasis>).
-	(ë ÐÒÉÍÅÒÕ, ÔÜÇ ×Ï ×ÒÅÍÑ ÐÏÄÇÏÔÏ×ËÉ ÒÅÌÉÚÁ ÐÒÉÓ×ÏÅÎÎÙÊ ÒÅÌÉÚÕ 5.4 ÂÙÌ
-	<literal>RELENG_5_4_0_RELEASE</literal>).  òÁÚÒÁÂÏÔËÁ ×ÓÅÇÄÁ
-	ÐÒÏÄÏÌÖÁÅÔÓÑ × ÔÁË ÎÁÚÙ×ÁÅÍÏÍ ÔÜÇÅ <literal>HEAD</literal>.</para>
-    </sect2>
-
-    <sect2 id="branches">
-      <title>÷ÅÔËÉ</title>
-
-      <para>÷Ï ×ÒÅÍÑ ËÁÖÄÏÇÏ ÒÅÌÉÚÁ ÓÏÚÄÁÅÔÓÑ <firstterm>×ÅÔËÁ</firstterm>
-	(Ë ÐÒÉÍÅÒÕ, <literal>RELENG_5_4</literal>).  éÓÈÏÄÎÙÅ ÆÁÊÌÙ, ÎÁÚ×ÁÎÎÙÅ
-	<literal>RELENG_5_4_0_RELEASE</literal> ÉÚÍÅÎÑÔØÓÑ ÎÉËÏÇÄÁ ÎÅ ÂÕÄÕÔ, ÔÅ
-	ËÏÔÏÒÙÅ × <literal>RELENG_5_4</literal> ÉÚÍÅÎÑÔØÓÑ ÍÏÇÕÔ ÐÕÔ£Í ÐÒÉÎÑÔÉÑ
-	ÉÚÍÅÎÅÎÉÊ ÉÚ <literal>HEAD</literal>, ÔÁËÉÈ ËÁË ÉÓÐÒÁ×ÌÅÎÉÑ
-	× ÂÅÚÏÐÁÓÎÏÓÔÉ É ÄÒÕÇÉÅ ÏÛÉÂËÉ.</para>
-
-      <para>÷Ï ×ÒÅÍÑ ÖÉÚÎÉ ËÁÖÄÏÇÏ ÓÔÁÒÛÅÇÏ ÒÅÌÉÚÁ ÓÏÚÄÁ£ÔÓÑ ÔÜÇ (Ë ÐÒÉÍÅÒÕ,
-	<literal>RELENG_5</literal>).  ÷ ÄÏÐÏÌÎÅÎÉÅ Ë ÉÓÐÒÁ×ÌÅÎÉÑÍ ×
-	ÂÅÚÏÐÁÓÎÏÓÔÉ É ÉÓÐÒÁ×ÌÅÎÉÑÍ ÄÒÕÇÉÈ ÏÛÉÂÏË, ÎÏ×ÙÅ ÉÚÍÅÎÅÎÉÑ ÍÏÇÕÔ ÂÙÔØ
-	ÐÒÉÎÑÔÙ ÉÚ <literal>HEAD</literal>, É ÔÁËÉÍ ÏÂÒÁÚÏÍ ÓÏÓÔÁ×ÑÔ
-	ÉÚÍÅÎÅÎÉÑ ÄÌÑ ÓÌÅÄÕÀÝÅÇÏ ÍÌÁÄÛÅÇÏ ÒÅÌÉÚÁ × ÐÏÓÌÅÄÏ×ÁÔÅÌØÎÏÓÔÉ.</para>
-    </sect2>
-
-    <sect2 id="stable-vs-current">
-      <title><firstterm>STABLE</firstterm> ÐÒÏÔÉ×
-	<firstterm>CURRENT</firstterm></title>
-
-      <para>÷Ï ×ÒÅÍÑ ÖÉÚÎÉ ËÁÖÄÏÇÏ ÓÔÁÒÛÅÇÏ ÒÅÌÉÚÁ, ÏÔÄÅÌØÎÁÑ ×ÅÔËÁ
-	ÍÏÖÅÔ ÔÁËÖÅ ÎÁÚÙ×ÁÔØÓÑ <literal>STABLE</literal>.  üÔÏ
-	ÏÚÎÁÞÁÅÔ, ÞÔÏ ÐÒÏÅËÔ &os; ÓÞÉÔÁÅÔ, ÞÔÏ ×ÅÔ×Ø ÉÍÅÅÔ ÄÏÓÔÁÔÏÞÎÏ
-	ÄÏËÁÚÁÎÎÕÀ ÓÔÁÂÉÌØÎÏÓÔØ ÄÌÑ ÉÓÐÏÌØÚÏ×ÁÎÉÑ ÛÉÒÏËÉÍ ËÒÕÇÏÍ
-	ÐÏÌØÚÏ×ÁÔÅÌÅÊ.  ÷ÅÔ×É, ËÏÔÏÒÙÅ ÎÕÖÄÁÀÔÓÑ × ÄÁÌØÎÅÊÛÅÍ
-	ÔÅÓÔÉÒÏ×ÁÎÉÉ ÐÅÒÅÄ ÔÅÍ, ËÁË ÓÔÁÔØ × ÚÎÁÞÉÔÅÌØÎÏÊ ÓÔÅÐÅÎÉ ÐÒÉÎÑÔÏÊ
-	ÎÁÚÙ×ÁÀÔÓÑ <literal>CURRENT</literal>.</para>
-
-      <note><para>ðÒÏÅËÔ &os; ÎÉ ×ÎÕÔÒÉ, ÎÉ ×ÎÅ ÓÅÂÑ ÎÅ ÍÏÖÅÔ ÇÁÒÁÎÔÉÒÏ×ÁÔØ,
-	ÞÔÏ ÐÒÏÇÒÁÍÍÎÏÅ ÏÂÅÓÐÅÞÅÎÉÅ, ËÏÔÏÒÏÅ ÏÎÏ ×ÙÐÕÓËÁÅÔ Ñ×ÌÑÅÔÓÑ
-	ÄÏÓÔÁÔÏÞÎÏ <emphasis>ÓÔÁÂÉÌØÎÙÍ</emphasis> ÄÌÑ ÌÀÂÏÊ ÄÁÎÎÏÊ
-	ÓÉÓÔÅÍÙ.  ôÏÌØËÏ ËÁÖÄÙÊ ÉÎÄÉ×ÉÄÕÁÌØÎÙÊ ÐÏÌØÚÏ×ÁÔÅÌØ ÍÏÖÅÔ ÓÄÅÌÁÔØ
-	ÔÁËÏÅ ÒÅÛÅÎÉÅ.  ðÏÖÁÌÕÊÓÔÁ, ÐÏÍÎÉÔÅ, ÞÔÏ ðÒÏÅËÔ × ÏÓÎÏ×ÎÏÍ ÓÏÓÔÏÉÔ
-	ÉÚ ÄÏÂÒÏ×ÏÌØÃÅ× É ÎÅ ÍÏÖÅÔ ÐÒÅÄÌÁÇÁÔØ ÌÀÂÏÊ ×ÉÄ ÇÁÒÁÎÔÉÉ
-	ÐÒÉÇÏÄÎÏÓÔÉ.</para></note>
-    </sect2>
-
-    <sect2 id="ports-vs-packages">
-      <title><firstterm>ðÏÒÔÙ</firstterm> ÐÒÏÔÉ×
-	<firstterm>ðÁËÅÔÏ×</firstterm></title>
-
-      <para>ïÔÄÅÌØÎÏ ÏÔ ÆÁÊÌÏ×, ÒÁÓÐÒÏÓÔÒÁÎÑÅÍÙÈ ×ÙÛÅÕËÁÚÁÎÎÏ, &os;
-	ÐÏÄÄÅÒÖÉ×ÁÅÔ ÔÙÓÑÞÉ ÐÒÉÌÏÖÅÎÉÊ, ËÏÔÏÒÙÅ ÒÁÚÒÁÂÁÔÙ×ÁÀÔÓÑ
-	ÔÒÅÔØÉÍÉ ÌÉÃÁÍÉ, ×ÎÅ ÓÁÍÏÇÏ ÐÒÏÅËÔÁ.  (óÀÄÁ ×ËÌÀÞÅÎÙ
-	ÏËÏÎÎÙÅ ÓÉÓÔÅÍÙ, ÉÎÔÅÒÎÅÔ ÂÒÁÕÚÅÒÙ, ÐÏÞÔÏ×ÙÅ ÐÒÏÇÒÁÍÍÙ,
-	ÏÆÉÓÎÙÅ ÐÁËÅÔÙ, É ÔÁË ÄÁÌÅÅ)  ÷ ÏÂÝÅÍ, ÓÁÍ ÐÒÏÅËÔ ÎÅ
-	ÒÁÚÒÁÂÁÔÙ×ÁÅÔ ÜÔÏ ÐÒÏÇÒÁÍÍÎÏÅ ÏÂÅÓÐÅÞÅÎÉÅ, ÔÏÌØËÏ ÉÎÆÒÁÓÔÒÕËÔÕÒÕ,
-	ÐÏÚ×ÏÌÑÀÝÕÀ ÕÓÔÁÎÏ×ÉÔØ ÜÔÉ ÐÒÏÇÒÁÍÍÙ (ÎÁÚÙ×ÁÅÔÓÑ <firstterm>ëÏÌÌÅËÃÉÑ
-	ÐÏÒÔÏ×</firstterm>).  ðÒÉÌÏÖÅÎÉÑ ÍÏÇÕÔ ÂÙÔØ ÕÓÔÁÎÏ×ÌÅÎÙ ÌÉÂÏ
-	ÉÚ ÉÓÈÏÄÎÉËÏ×, ÅÓÌÉ ÕÓÌÏ×ÉÑ ÌÉÃÅÎÚÉÉ ÐÏÚ×ÏÌÑÀÔ ÔÁËÏÅ
-	ÒÁÓÐÒÏÓÔÒÁÎÅÎÉÅ (ÏÎÉ ÎÁÚÙ×ÁÀÔÓÑ <emphasis>ÐÏÒÔÙ</emphasis>),
-	ÌÉÂÏ × ×ÉÄÅ ÓËÏÍÐÉÌÉÒÏ×ÁÎÎÙÈ Ä×ÏÉÞÎÙÈ ÆÁÊÌÏ×, ÅÓÌÉ ÒÁÚÒÅÛÅÎÏ (ÏÎÉ
-	ÎÁÚÙ×ÁÀÔÓÑ <emphasis>ÐÁËÅÔÙ</emphasis>).</para>
-    </sect2>
-  </sect1>
-
-  <sect1 id="past-schedules">
-    <title>ðÌÁÎÉÒÏ×ÁÎÉÅ ÒÅÌÉÚÏ× × ÐÒÏÛÌÏÍ</title>
-
-    <para>÷Ï ×ÒÅÍÑ ÒÁÚÒÁÂÏÔËÉ É ×ÙÐÕÓËÁ &os; 5.X ÂÙÌÏ ÐÏÌÕÞÅÎÏ ÍÎÏÇÏ
-      ÕÒÏËÏ×, ËÏÔÏÒÙÅ ÓÔÁÌÉ ÑÓÎÙ ÔÏÌØËÏ ÒÅÔÒÏÓÐÅËÔÉ×ÎÏ.  ãÅÌÉ ÓÅÒÉÉ 5.X
-      ÂÙÌÉ ÏÞÅÎØ ÍÏÝÎÙÍÉ É ×ËÌÀÞÁÌÉ:</para>
-
-    <itemizedlist>
-      <listitem>
-	<para>ïÂÅÓÐÅÞÉÔØ ÐÏÄÄÅÒÖËÕ ÍÁÛÉÎ Ó ÓÉÍÍÅÔÒÉÞÎÏÊ ÍÕÌØÔÉÐÒÏÃÅÓÓÏÒÎÏÓÔØÀ
-	  (Symmetric MultiProcessing, SMP);</para>
-      </listitem>
-
-      <listitem>
-	<para>õ×ÅÌÉÞÉÔØ ÐÒÏÉÚ×ÏÄÉÔÅÌØÎÏÓÔØ, ÐÕÔ£Í ÐÒÉÍÅÎÅÎÉÑ ÎÏ×ÏÊ ÓÔÒÁÔÅÇÉÉ
-	  ÒÁÂÏÔÙ Ó ËÏÎËÕÒÅÎÃÉÅÊ ÒÅÓÕÒÓÏ× × ÑÄÒÅ;</para>
-      </listitem>
-
-      <listitem>
-	<para>äÏÂÁ×ÉÔØ ÎÅÓËÏÌØËÏ ÎÏ×ÙÈ ÁÒÈÉÔÅËÔÕÒ ÐÒÏÃÅÓÓÏÒÏ×;</para>
-      </listitem>
-
-      <listitem>
-	<para>÷×ÅÓÔÉ ÎÏ×ÕÀ ÍÏÄÅÌØ ÔÒÅÄÏ×;</para>
-      </listitem>
-
-      <listitem>
-	<para>÷×ÅÓÔÉ ÎÏ×ÙÊ ÐÌÁÎÉÒÏ×ÝÉË;</para>
-      </listitem>
-
-      <listitem>
-	<para>äÏÂÁ×ÉÔØ ÐÏÄÄÅÒÖËÕ ÎÏ×ÙÈ ÔÅÈÎÏÌÏÇÉÊ, ÔÁËÉÈ ËÁË
-	  ÕÐÒÁ×ÌÅÎÉÅ ÐÉÔÁÎÉÅÍ (ÜÔÏ ÏÓÏÂÅÎÎÏ ×ÁÖÎÏ ÄÌÑ ÌÜÐÔÏÐÏ×);
-	  É ÎÁÉÂÏÌÅÅ ËÒÉÔÉÞÎÏ,</para>
-      </listitem>
-
-      <listitem>
-	<para>îÅ ÏÂßÑ×ÌÑÔØ ÓÅÒÉÉ ÒÅÌÉÚÏ×, ËÁË <literal>STABLE</literal>
-	  ÄÏ ÔÅÈ ÐÏÒ, ÐÏËÁ ×ÓÅ ÜÔÉ ÚÁÄÁÞÉ ÎÅ ÂÕÄÕÔ ×ÙÐÏÌÎÅÎÙ.</para>
-      </listitem>
-    </itemizedlist>
-
-    <para>üÔÏ ÐÒÉ×ÅÌÏ Ë ÓÉÔÕÁÃÉÉ, ËÏÇÄÁ ÍÅÖÄÕ ÍÏÍÅÎÔÏÍ ×ÒÅÍÅÎÅÍ, ËÏÇÄÁ
-      ÒÅÌÉÚ ÉÚ ÓÅÒÉÉ 4.X ÂÙÌ ÏÂßÑ×ÌÅÎ, ËÁË <literal>STABLE</literal> É
-      ÍÏÍÅÎÔÏÍ, ËÏÇÄÁ ÒÅÌÉÚ ÉÚ 5.X ÂÙÌ ÏÂßÑ×ÌÅÎ, ËÁË <literal>STABLE</literal>
-      ÐÒÏÛÌÏ ÎÅÓËÏÌØËÏ ÌÅÔ.  üÔÏ ÉÍÅÌÏ ÎÅÓËÏÌØËÏ ÎÅÖÅÌÁÔÅÌØÎÙÈ ÜÆÆÅËÔÏ×:</para>
-
-    <itemizedlist>
-      <listitem>
-	<para>ëÏÌÉÞÅÓÔ×Ï ÏÄÎÏ×ÒÅÍÅÎÎÙÈ ÉÚÍÅÎÅÎÉÊ ÇÒÕÐÐ ÈÁÒÁËÔÅÒÉÓÔÉË ÓÄÅÌÁÌÏ
-	  ÏÞÅÎØ ÓÌÏÖÎÙÍ ÉÚÏÌÉÒÏ×ÁÎÉÅ ÏÄÎÏÇÏ ÎÁÂÏÒÁ ÉÚÍÅÎÅÎÉÊ ÄÌÑ ÓÌÉÑÎÉÑ
-	  ÏÂÒÁÔÎÏ × <literal>STABLE</literal> ×ÅÔËÕ;</para>
-      </listitem>
-
-      <listitem>
-	<para>ÞÔÏ ÏÚÎÁÞÁÌÏ, ÞÔÏ ÐÏÌØÚÏ×ÁÔÅÌÉ, ËÏÔÏÒÙÅ ÄÏÌÖÎÙ ÉÍÅÔØ ÏÐÒÅÄÅÌ£ÎÎÙÅ
-	  ÎÏ×ÙÅ ×ÏÚÍÏÖÎÏÓÔÉ (Ë ÐÒÉÍÅÒÕ, ÉÓÐÏÌØÚÏ×ÁÔØ ÓÏ×ÒÅÍÅÎÎÏÅ ÏÂÏÒÕÄÏ×ÁÎÉÅ)
-	  ÒÁÂÏÔÁÌÉ ÐÕÔ£Í ÁÄÁÐÔÉÒÏ×ÁÎÉÑ (Ë ÐÒÉÍÅÒÕ) &os; 5.2.1 ÈÏÔÑ ÏÎ ÂÙÌ
-	  ÉÚ×ÅÓÔÅÎ, ËÁË ÒÅÌÉÚ ÔÏÌØËÏ ÄÌÑ ÒÁÚÒÁÂÏÔÞÉËÏ×, É ÎÅÚÁ×ÉÓÉÍÏ ÏÔ ÔÏÇÏ
-	  ÆÁËÔÁ, ÞÔÏ <literal>CURRENT</literal> ÒÅÌÉÚ ÎÅ ÓÏ×ÓÅÍ ÐÏÄÈÏÄÉÌ
-	  ÄÌÑ ÉÈ ÎÕÖÄ.</para>
-      </listitem>
-
-      <listitem>
-	<para>÷ ÓÌÕÞÁÑÈ, ËÏÇÄÁ ÏÂÒÁÔÎÙÅ ÓÌÉÑÎÉÑ ÉÍÅÌÉ ÍÅÓÔÏ, ÜÔÏ ÐÏÓÔÁ×ÉÌÏ
-	  ÒÁÚÒÁÂÏÔÞÉËÏ× × ÐÏÌÏÖÅÎÉÅ, ËÏÇÄÁ ÏÎÉ ÐÙÔÁÌÉÓØ ÐÏÄÄÅÒÖÉ×ÁÔØ
-	  ÈÁÒÁËÔÅÒÉÓÔÉËÉ (feautures) ÎÁ ×ÅÒÓÉÉ, ËÏÔÏÒÕÀ ÏÎÉ ÓÁÍÉ
-	  ÎÅ ÉÓÐÏÌØÚÏ×ÁÌÉ, ËÁË ÐÅÒ×ÉÞÎÕÀ ÐÌÁÔÆÏÒÍÕ ÄÌÑ ÒÁÚÒÁÂÏÔËÉ.</para>
-      </listitem>
-
-      <listitem>
-	<para>úÁÄÅÒÖËÁ ×Ï ×ÒÅÍÅÎÉ ÔÁËÖÅ ÚÎÁÞÉÌÁ, ÞÔÏ ËÏÇÄÁ 5.3 ÂÙÌ ÎÁËÏÎÅÃ
-	  ÏÂßÑ×ÌÅÎ ÓÁÍÙÍ ÐÏÓÌÅÄÎÉÍ <literal>STABLE</literal> ÒÅÌÉÚÏÍ,
-	  ÎÁËÏÐÉ×ÛÅÅÓÑ ËÏÌÉÞÅÓÔ×Ï ÉÚÍÅÎÅÎÉÊ ÓÄÅÌÁÌÏ ÐÒÏÃÅÓÓ ÏÂÎÏ×ÌÅÎÉÑ
-	  ÏÞÅÎØ ÂÏÌÅÚÎÅÎÎÙÍ.</para>
-      </listitem>
-    </itemizedlist>
-
-    <para>âÏÌÅÅ ËÒÁÔËÏ, ÎÉËÔÏ ÎÅ ÂÙÌ ÄÏ×ÏÌÅÎ ÒÅÚÕÌØÔÁÔÏÍ.</para>
-
-    <para>õÒÏËÉ, ËÏÔÏÒÙÅ ÂÙÌÉ ÐÏÌÕÞÅÎÙ:</para>
-
-    <itemizedlist>
-      <listitem>
-	<para>îÏ×ÙÅ ÓÔÁÒÛÉÅ ÒÅÌÉÚÙ ÄÏÌÖÎÙ ÉÍÅÔØ ÍÅÎØÛÅÅ ËÏÌÉÞÅÓÔ×Ï
-	  ÓÅÒØÅÚÎÙÈ ÉÚÍÅÎÅÎÉÊ ÈÁÒÁËÔÅÒÉÓÔÉË É ×ÙÐÕÓËÁÔØÓÑ ÂÏÌÅÅ ÞÁÓÔÏ.</para>
-      </listitem>
-
-      <listitem>
-	<para>÷ ÓÁÍÏÊ ÂÏÌØÛÏÊ ÓÔÅÐÅÎÉ, ÓÅÒØÅÚÎÙÅ ÉÚÍÅÎÅÎÉÑ ÄÏÌÖÎÙ
-	  ÉÚÏÌÉÒÏ×ÁÔØÓÑ ÄÒÕÇ ÏÔ ÄÒÕÇÁ.  (üÔÏ ÐÏÄÒÁÚÕÍÅ×ÁÅÔ, ÞÔÏ ÎÅËÏÔÏÒÁÑ
-	  ÒÁÚÒÁÂÏÔËÁ ÄÏÌÖÎÁ ×ÅÓÔÉÓØ ×ÎÅ ÏÓÎÏ×ÎÏÇÏ ÄÅÒÅ×Á É ÍÏÖÅÔ
-	  ÂÙÔØ ÏÂßÅÄÉÎÅÎÁ Ó ÏÓÎÏ×ÎÙÍ ÄÅÒÅ×ÏÍ ÔÏÌØËÏ ÐÒÉ ÕÓÌÏ×ÉÉ, ÞÔÏ ÜÔÏ ÎÅ
-	  ÎÁÒÕÛÉÔ ÄÒÕÇÕÀ ÏÄÎÏ×ÒÅÍÅÎÎÏ ÐÒÏÄÏÌÖÁÀÝÕÀÓÑ ÒÁÚÒÁÂÏÔËÕ.)</para>
-      </listitem>
-
-      <listitem>
-	<para>óÔÁÒÛÉÅ ÒÅÌÉÚÙ ÄÏÌÖÎÙ ÏÒÉÅÎÔÉÒÏ×ÁÔØÓÑ ÎÁ ÐÏÓÌÅÄÎÉÊ ÓÒÏË ÐÏ
-	  ×ÒÅÍÅÎÉ, Á ÎÅ ÎÁ ÐÏÓÌÅÄÎÉÊ ÓÒÏË ÐÏ ËÏÌÉÞÅÓÔ×Õ ÈÁÒÁËÔÅÒÉÓÔÉË.
-	  åÓÌÉ ËÁËÁÑ-ÔÏ ×ÏÚÍÏÖÎÏÓÔØ (ÈÁÒÁËÔÅÒÉÓÔÉËÁ) ÎÅ ÚÁËÏÎÞÅÎÁ ×Ï×ÒÅÍÑ,
-	  ÔÏ ÏÎÁ ÄÏÌÖÎÁ ÂÙÔØ ÕÂÒÁÎÁ É ÏÓÔÁ×ÌÅÎÁ ÄÏ ÓÌÅÄÕÀÝÅÇÏ ÓÔÁÒÛÅÇÏ
-	  ÒÅÌÉÚÁ.</para>
-      </listitem>
-    </itemizedlist>
-
-    <para>ó ÐÏÍÏÝØÀ ÂÏÌÅÅ ÞÁÓÔÏÇÏ ×ÙÐÕÓËÁ ÍÅÎØÛÅÇÏ ËÏÌÉÞÅÓÔ×Á ÉÚÍÅÎÅÎÉÊ,
-      ÔÁËÖÅ ÓÕÝÅÓÔ×ÕÅÔ ÎÁÄÅÖÄÁ, ÞÔÏ ÍÅÎØÛÅ ×ÒÅÍÅÎÉ ÂÕÄÅÔ ÐÒÏ×ÏÄÉÔØÓÑ, ÐÙÔÁÑÓØ
-      ÚÁÎÉÍÁÔØÓÑ ÓÌÉÑÎÉÅÍ ÈÁÒÁËÔÅÒÉÓÔÉË ÉÚ <literal>HEAD</literal> ÏÂÒÁÔÎÏ
-      × ÐÏÓÌÅÄÎÀÀ <literal>STABLE</literal> ×ÅÒÓÉÀ (É ÔÅÍ ÓÁÍÙÍ ÐÙÔÁÑÓØ
-      ÐÏÄÄÅÒÖÉ×ÁÔØ ÜÔÉ ÈÁÒÁËÔÅÒÉÓÔÉËÉ ÂÏÌÅÅ, ÞÅÍ × ÏÄÎÏÊ ÓÔÁÒÛÅÊ ×ÅÒÓÉÉ);
-      É ÄÁÌÅÅ, ÞÅÍ ÉÚÍÅÎÅÎÉÑ ÂÏÌÅÅ ÉÚÏÌÉÒÏ×ÁÎÙ, ÔÅÍ ÒÉÓË ÐÏÑ×ÌÅÎÉÑ ÎÏ×ÙÈ ÏÛÉÂÏË
-      ÎÁÍÎÏÇÏ ÍÅÎØÛÅ.</para>
-
-    <para>ôÁËÖÅ, ÆÏËÕÓÉÒÕÑÓØ ÂÏÌØÛÅ ÎÁ ÐÏÓÌÅÄÎÉÊ ÓÒÏË ÐÏ ×ÒÅÍÅÎÉ ÎÅÖÅÌÉ ÐÏ
-      ËÏÌÉÞÅÓÔ×Õ ÈÁÒÁËÔÅÒÉÓÔÉË, × ÉÔÏÇÅ ÂÕÄÅÔ ×ÏÚÍÏÖÎÙÍ ÄÌÑ ÐÏÌØÚÏ×ÁÔÅÌÅÊ,
-      ÒÁÚÒÁÂÏÔÞÉËÏ× ×ÎÅÛÎÉÈ ÐÒÉÌÏÖÅÎÉÊ É ÓÁÍÉÈ ÒÁÚÒÁÂÏÔÞÉËÏ× &os; ÉÍÅÔØ ÂÏÌÅÅ
-      ÌÕÞÛÉÊ ÐÌÁÎ ÎÁ ÂÕÄÕÝÅÅ.</para>
-  </sect1>
-
-  <sect1 id="future-goals">
-    <title>õÌÕÞÛÅÎÉÑ ÃÅÌÅÊ ÐÌÁÎÉÒÏ×ÁÎÉÑ ÒÅÌÉÚÏ×</title>
-
-    <para>÷ÏÔ ÔÅËÕÝÉÅ ÃÅÌÉ × ÐÌÁÎÉÒÏ×ÁÎÉÉ ÄÌÑ ðÒÏÅËÔÁ:</para>
-
-    <itemizedlist>
-      <listitem>
-	<para>÷ÙÐÕÓËÁÔØ ÎÏ×ÙÊ ÓÔÁÒÛÉÊ ÒÅÌÉÚ ËÁÖÄÙÅ 18 ÍÅÓÑÃÅ×;</para>
-      </listitem>
-
-      <listitem>
-	<para>÷ÙÐÕÓËÁÔØ ÎÏ×ÙÊ ÍÌÁÄÛÉÊ ÒÅÌÉÚ ËÁÖÄÙÅ 4 ÍÅÓÑÃÁ;</para>
-      </listitem>
-
-      <listitem>
-	<para>ïÂÅÓÐÅÞÉ×ÁÔØ ÐÒÅÄ×ÁÒÉÔÅÌØÎÏ ÓÏÂÒÁÎÎÙÅ ÐÁËÅÔÙ ÄÌÑ ÐÏÓÌÅÄÎÅÇÏ
-	  ÒÅÌÉÚÁ ËÁÖÄÏÊ ÓÔÁÒÛÅÊ ×ÅÒÓÉÉ;</para>
-      </listitem>
-
-      <listitem>
-	<para>ïÂÅÓÐÅÞÉÔØ ÏÂÎÏ×ÌÅÎÉÑ × ÂÅÚÏÐÁÓÎÏÓÔÉ É ÄÒÕÇÉÅ ËÒÉÔÉÞÅÓËÉÅ
-	  ÉÓÐÒÁ×ÌÅÎÉÑ ÏÛÉÂÏË ÄÌÑ ÐÏÓÌÅÄÎÉÈ ÎÅÓËÏÌØËÉÈ ÍÌÁÄÛÉÈ ×ÅÒÓÉÊ ËÁÖÄÏÊ
-	  ÓÔÁÒÛÅÊ ×ÅÒÓÉÉ (<firstterm>×ÅÔËÉ ÕÌÕÞÛÅÎÉÊ
-	  × ÂÅÚÏÐÁÓÎÏÓÔÉ</firstterm>, security branches).</para>
-      </listitem>
-    </itemizedlist>
-
-    <para>éÚ-ÚÁ ÂÏÌØÛÏÇÏ ËÏÌÉÞÅÓÔ×Á ×ÏÚÍÏÖÎÙÈ ËÏÍÂÉÎÁÃÉÊ ÕÓÔÁÎÁ×ÌÉ×ÁÅÍÙÈ
-      ×ÅÒÓÉÊ, ÎÅ×ÏÚÍÏÖÎÏ ÐÏÄÄÅÒÖÉ×ÁÔØ ËÁÖÄÕÀ ×ÅÒÓÉÀ ÂÅÓÓÒÏÞÎÏ; ÜÔÏ ÏÔ
-      ÞÁÓÔÉ ÉÚ-ÚÁ ÎÅÈ×ÁÔËÉ ÍÁÛÉÎÎÙÈ ÒÅÓÕÒÓÏ×, ÎÏ × ÏÓÎÏ×ÎÏÍ ÉÚ-ÚÁ
-      ÉÍÅÀÝÉÈÓÑ ÕÓÉÌÉÊ ÄÏÂÒÏ×ÏÌØÃÅ×.</para>
-
-      <para>úÁÉÎÔÅÒÅÓÏ×ÁÎÎÙÍ ÞÉÔÁÔÅÌÑÍ ÒÅËÏÍÅÎÄÕÅÔÓÑ ÔÁËÖÅ ÐÒÏÓÍÏÔÒÅÔØ:</para>
-
-      <variablelist>
-	<varlistentry>
-	  <term><ulink url="&url.base;/releng/index.html#schedule"></ulink></term>
-	  <listitem>
-	    <para>ÒÁÓÐÉÓÁÎÉÅ ÐÏÄÇÏÔÏ×ËÉ ÒÅÌÉÚÏ×</para>
-	  </listitem>
-	</varlistentry>
-
-	<varlistentry>
-	  <term><ulink url="&url.base;/security/security.html#supported-branches"></ulink></term>
-	  <listitem>
-	    <para>ÒÁÓÐÉÓÁÎÉÅ ×ÅÔÏË ÕÌÕÞÛÅÎÉÊ × ÂÅÚÏÐÁÓÎÏÓÔÉ</para>
-	  </listitem>
-	</varlistentry>
-      </variablelist>
-
-      <para>ïÂÁ ÄÏËÕÍÅÎÔÁ ÓÏÄÅÒÖÁÔ ÂÏÌÅÅ ÄÅÔÁÌØÎÕÀ ÉÎÆÏÒÍÁÃÉÀ ÐÏ ÐÒÅÄÐÏÓÙÌËÁÍ
-	É ÒÁÚÕÍÎÙÅ ÏÂÏÓÎÏ×ÁÎÉÑ ÜÔÉÈ ÒÅÛÅÎÉÊ ËÁÓÁÔÅÌØÎÏ ÐÏÄÄÅÒÖÉ×ÁÅÍÙÈ ×ÅÔÏË
-	É ×ÒÅÍÅÎÉ ÖÉÚÎÉ ËÁÖÄÏÊ ×ÅÔËÉ.</para>
-  </sect1>
-
-  <sect1 id="decision-points">
-    <title>ëÁË ÜÔÉ ÆÁËÔÏÒÙ ÐÏ×ÌÉÑÀÔ ÎÁ ÍÏ£ ÒÅÛÅÎÉÅ?</title>
-
-    <para>ïÓÎÏ×ÎÙÅ ÆÁËÔÏÒÙ, ËÏÔÏÒÙÅ ÍÏÇÕÔ ÐÏ×ÌÉÑÔØ ÎÁ ×ÁÛÅ ÒÅÛÅÎÉÅ
-      × ×ÙÂÏÒÅ ×ÅÒÓÉÉ ÄÌÑ ÕÓÔÁÎÏ×ËÉ:</para>
-
-    <itemizedlist>
-      <listitem>
-	<para>ëÁËÕÀ ÓÔÅÐÅÎØ ÓÔÁÂÉÌØÎÏÓÔÉ ÔÒÅÂÕÅÔ ×ÁÛÁ ÓÉÓÔÅÍÁ?</para>
-      </listitem>
-
-      <listitem>
-	<para>óËÏÌØËÏ ÕÓÉÌÉÊ ×Ù ÈÏÔÉÔÅ ÐÒÉËÌÁÄÙ×ÁÔØ ÄÌÑ ÏÂÎÏ×ÌÅÎÉÊ?</para>
-      </listitem>
-
-      <listitem>
-	<para>ëÁË ÄÏÌÇÏ ×Ù ÐÌÁÎÉÒÕÊÔÅ ÏÓÔÁ×ÁÔØÓÑ ÎÁ ÏÄÎÏÊ ×ÅÒÓÉÉ ÍÅÖÄÕ
-	  ÏÂÎÏ×ÌÅÎÉÑÍÉ?</para>
-      </listitem>
-
-      <listitem>
-	<para>ëÁË ×ÁÖÎÁ ÂÅÚÏÐÁÓÎÏÓÔØ ÄÌÑ ×ÁÛÅÊ ÓÉÓÔÅÍÙ?</para>
-      </listitem>
-
-      <listitem>
-	<para>âÕÄÅÔÅ ÌÉ ×Ù ÕÓÔÁÎÁ×ÌÉ×ÁÔØÓÑ ÉÚ ÉÓÈÏÄÎÉËÏ× ÉÌÉ ÐÏÓÒÅÄÓÔ×ÏÍ
-	  Ä×ÏÉÞÎÙÈ ÆÁÊÌÏ×?</para>
-      </listitem>
-
-      <listitem>
-	<para>öÅÌÁÅÔÅ ÌÉ ×Ù ÐÏÍÏÞØ ÕÞÁÓÔ×Ï×ÁÔØ × ÐÒÏÃÅÓÓÅ
-	  ÒÁÚÒÁÂÏÔËÉ &os;?</para>
-      </listitem>
-    </itemizedlist>
-
-    <para>÷ÏÔ ÎÅËÏÔÏÒÙÅ ÐÒÉÍÅÒÎÙÅ ÉÎÓÔÒÕËÃÉÉ ÄÌÑ ÐÏÍÏÝÉ ×ÁÍ × ×ÁÛÅÍ
-      ÒÅÛÅÎÉÉ:</para>
-
-    <itemizedlist>
-      <listitem>
-	<para>åÓÌÉ ×ÁÛÉ ÎÕÖÄÙ ÉÍÅÀÔ ËÒÁÔËÏÓÒÏÞÎÙÊ ÈÁÒÁËÔÅÒ, ÅÓÔØ ÐÏÔÒÅÂÎÏÓÔØ ×
-	  ÓÁÍÏÊ ×ÙÓÏËÏÊ ÓÔÅÐÅÎÉ ÓÔÁÂÉÌØÎÏÓÔÉ, ÄÏÓÔÕÐÎÏÊ ÎÁ ÄÁÎÎÙÊ ÍÏÍÅÎÔ É
-	  ÎÅ ÓÏÂÉÒÁÅÔÅÓØ ÏÂÎÏ×ÌÑÔØ ÂÏÌØÛÏÅ ËÏÌÉÞÅÓÔ×Ï ÒÅÓÕÒÓÏ×, ÔÏ ×Ù ×ÏÚÍÏÖÎÏ
-	  ÚÁÈÏÔÉÔÅ ÕÓÔÁÎÏ×ÉÔØ ÐÏÓÌÅÄÎÉÊ ÍÌÁÄÛÉÊ <literal>STABLE</literal>
-	  ÒÅÌÉÚ É ÏÓÔÁÔØÓÑ Ó ÎÉÍ.  ÷ ÚÁ×ÉÓÉÍÏÓÔÉ ÏÔ ×ÁÛÉÈ ÔÒÅÂÏ×ÁÎÉÊ
-	  Ë ÂÅÚÏÐÁÓÎÏÓÔÉ, ×Ù ÍÏÖÅÔÅ ÓÌÅÄÉÔØ ÚÁ ÉÚÍÅÎÅÎÉÑÍÉ × ÜÔÕ ×ÅÔËÕ,
-	  ÐÏ ÍÅÒÅ ÉÈ ÐÏÑ×ÌÅÎÉÑ.</para>
-      </listitem>
-
-      <listitem>
-	<para>åÓÌÉ ×ÁÛÉ ÎÕÖÄÙ ÉÍÅÀÔ ËÒÁÔËÏÓÒÏÞÎÙÊ ÈÁÒÁËÔÅÒ, É ÐÏÌÎÏÔÁ
-	  ×ÏÚÍÏÖÎÏÓÔÅÊ ÉÌÉ ÎÁÉÌÕÞÛÉÅ ÕÒÏ×ÎÉ ÂÅÚÏÐÁÓÎÏÓÔÉ ÎÁÉÂÏÌÅÅ ×ÁÖÎÙ
-	  ÄÌÑ ×ÁÓ, É ×Ù ÖÅÌÁÅÔÅ ÐÒÏ×ÏÄÉÔØ ×ÒÅÍÑ, ÏÂÎÏ×ÌÑÑÓØ, ×Ù ÍÏÖÅÔÅ
-	  ÉÓÐÏÌØÚÏ×ÁÔØ ÐÏÓÌÅÄÎÀÀ <literal>STABLE</literal> ×ÅÔËÕ.</para>
-      </listitem>
-
-      <listitem>
-	<para>åÓÌÉ ×Ù ÎÅ ÐÌÁÎÉÒÕÅÔÅ ÓÒÁÚÕ ÐÒÏÍÙÛÌÅÎÎÏÅ ÉÓÐÏÌØÚÏ×ÁÎÉÅ, Á ÈÏÔÉÔÅ
-	  ÐÏÒÁÂÏÔÁÔØ Ó ÐÒÏÂÌÅÍÁÍÉ, É ÎÏ×ÙÊ ÓÔÁÒÛÉÊ ÒÅÌÉÚ ÐÏÑ×ÌÑÅÔÓÑ ×
-	  ÓÌÅÄÕÀÝÉÅ ÎÅÓËÏÌØËÏ ÍÅÓÑÃÅ×, ÔÏ ×Ù ÍÏÖÅÔÅ ÐÏÉÓÓÌÅÄÏ×ÁÔØ, ÕÓÔÁÎÏ×É×
-	  ÜÔÕ ×ÅÔËÕ, ÞÔÏÂÙ ÐÏÍÏÞØ ðÒÏÅËÔÕ ÐÒÏÔÅÓÔÉÒÏ×ÁÔØ ÅÇÏ, ÓÔÁÂÉÌÉÚÉÒÏ×ÁÔØ,
-	  ÓÄÅÌÁÔØ ÅÇÏ ÓÁÍÙÍ ÌÕÞÛÉÍ ÒÅÌÉÚÏÍ Ó ÕÒÏ×ÎÅÍ ËÁÞÅÓÔ×Á
-	  ×ÙÛÅ ÓÒÅÄÎÅÇÏ.</para>
-      </listitem>
-
-      <listitem>
-	<para>ôÏÌØËÏ ÅÓÌÉ ×Ù ÐÏÖÅÌÁÅÔÅ ÕÓÔÁÎÁ×ÌÉ×ÁÔØÓÑ ÉÚ ÉÓÈÏÄÎÉËÏ× É
-	  ÐÒÏ×ÏÄÉÔØ ×ÒÅÍÑ, ÚÁÎÉÍÁÑÓØ ÏÔÌÁÄËÏÊ ÐÒÏÂÌÅÍ Ó ÂÁÚÏ×ÏÊ ÓÉÓÔÅÍÏÊ
-	  É ÄÁÌØÛÅ ÐÅÒÅÄÁ×ÁÔØ ÉÈ ÐÏÓÒÅÄÓÔ×ÏÍ ÓÏÏÂÝÅÎÉÊ Ï ÏÛÉÂËÁÈ É
-	  ÐÒÏÓÌÅÖÉ×ÁÔØ ÓÐÉÓÏË ÒÁÓÓÙÌËÉ, × ËÏÔÏÒÏÍ ÏÂÓÕÖÄÁÀÔÓÑ ÔÁËÉÅ
-	  ×ÏÐÒÏÓÙ, ×Ù ÍÏÖÅÔÅ ÒÁÓÓÍÏÔÒÅÔØ ÄÌÑ ÉÓÐÏÌØÚÏ×ÁÎÉÑ
-	  <literal>HEAD</literal>.</para>
-      </listitem>
-    </itemizedlist>
-  </sect1>
-
-  <sect1 id="conclusion">
-    <title>úÁËÌÀÞÅÎÉÅ</title>
-
-    <para>íÙ ÎÁÄÅÅÍÓÑ, ÞÔÏ ÜÔÁ ÓÔÁÔØÑ ÐÏÓÌÕÖÉÌÁ ÐÏÌÅÚÎÏÊ ÓÔÁÒÔÏ×ÏÊ ÔÏÞËÏÊ ×
-      ÐÏÎÉÍÁÎÉÉ ÍÏÄÅÌÉ ÒÁÚÒÁÂÏÔËÉ &os; É × ÒÅÛÅÎÉÉ ÔÏÇÏ, ËÁËÁÑ ×ÅÒÓÉÑ ÎÁÉÂÏÌÅÅ
-      ÐÏÄÈÏÄÉÔ ÄÌÑ ×ÁÛÉÈ ÎÕÖÄ.</para>
-  </sect1>
-</article>
diff --git a/ru_RU.KOI8-R/articles/zip-drive/Makefile b/ru_RU.KOI8-R/articles/zip-drive/Makefile
deleted file mode 100644
index 161adf62ca..0000000000
--- a/ru_RU.KOI8-R/articles/zip-drive/Makefile
+++ /dev/null
@@ -1,21 +0,0 @@
-#
-# The FreeBSD Russian Documentation Project
-#
-# $FreeBSD$
-# $FreeBSDru: frdp/doc/ru_RU.KOI8-R/articles/zip-drive/Makefile,v 1.4 2005/10/28 18:00:47 gad Exp $
-#
-# Original revision: r20561
-#
-# Article: IOmega ZIP Drives
-
-DOC?= article
-
-FORMATS?= html
-
-INSTALL_COMPRESSED?= gz
-INSTALL_ONLY_COMPRESSED?=
-
-SRCS=  article.sgml
-
-DOC_PREFIX?= ${.CURDIR}/../../..
-.include "${DOC_PREFIX}/share/mk/doc.project.mk"
diff --git a/ru_RU.KOI8-R/articles/zip-drive/article.sgml b/ru_RU.KOI8-R/articles/zip-drive/article.sgml
deleted file mode 100644
index 99014398fc..0000000000
--- a/ru_RU.KOI8-R/articles/zip-drive/article.sgml
+++ /dev/null
@@ -1,320 +0,0 @@
-<?xml version="1.0" encoding="koi8-r" standalone="no"?>
-<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V4.2-Based Extension//EN"
-	"../../../share/sgml/freebsd42.dtd" [
-<!ENTITY % entities PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Entity Set//RU" "../../share/sgml/entities.ent">
-%entities;
-]>
-
-<!--
-     The FreeBSD Russian Documentation Project
-
-     $FreeBSD$
-     $FreeBSDru: frdp/doc/ru_RU.KOI8-R/articles/zip-drive/article.sgml,v 1.5 2005/10/28 18:00:47 gad Exp $
-
-     Original revision: r22090
--->
-
-<article lang="ru">
-  <articleinfo>
-    <title>õÓÔÒÏÊÓÔ×Á &iomegazip;</title>
-
-    <authorgroup>
-      <author>
-	<firstname>Jason</firstname>
-	<surname>Bacon</surname>
-
-	<affiliation>
-	  <address><email>acadix@execpc.com</email></address>
-	</affiliation>
-      </author>
-    </authorgroup>
-
-    <legalnotice id="trademarks" role="trademarks">
-      &tm-attrib.freebsd;
-      &tm-attrib.adaptec;
-      &tm-attrib.iomega;
-      &tm-attrib.microsoft;
-      &tm-attrib.opengroup;
-      &tm-attrib.general;
-    </legalnotice>
-
-    <pubdate>$FreeBSD$</pubdate>
-
-    <releaseinfo>$FreeBSD$</releaseinfo>
-  </articleinfo>
-
-  <sect1>
-    <title>ïÂÚÏÒ ÕÓÔÒÏÊÓÔ× &iomegazip;</title>
-
-    <para>äÉÓËÉ &iomegazip; Ñ×ÌÑÀÔÓÑ ÓÍÅÎÎÙÍÉ ÍÁÇÎÉÔÎÙÍÉ ÄÉÓËÁÍÉ ÂÏÌØÛÏÊ
-      ÅÍËÏÓÔÉ, ÞÔÅÎÉÅ É ÚÁÐÉÓØ ÎÁ ËÏÔÏÒÙÅ ÍÏÖÅÔ ×ÙÐÏÌÎÑÔØÓÑ ÕÓÔÒÏÊÓÔ×ÁÍÉ
-      ZIP ÏÔ ËÏÒÐÏÒÁÃÉÉ IOMEGA.  äÉÓËÉ ZIP ÐÏÈÏÖÉ ÎÁ ÄÉÓËÅÔÙ, ËÒÏÍÅ
-      ÔÏÇÏ, ÞÔÏ ÏÎÉ ÒÁÂÏÔÁÀÔ
-      ÇÏÒÁÚÄÏ ÂÙÓÔÒÅÅ, É ÉÍÅÀÔ ÇÏÒÁÚÄÏ ÂÏÌØÛÕÀ ÅÍËÏÓÔØ.  ëÏÇÄÁ ËÁË ÄÉÓËÅÔÙ
-      ÏÂÙÞÎÏ ÉÍÅÀÔ ÅÍËÏÓÔØ × 1.44 ÍÅÇÁÂÁÊÔÁ, ÄÉÓËÉ ZIP ÍÏÇÕÔ ÂÙÔØ Ä×ÕÈ
-      ÒÁÚÎÏ×ÉÄÎÏÓÔÅÊ, ÏÂßÅÍÁÍÉ 100 É 250 ÍÅÇÁÂÁÊÔ.  äÉÓËÉ ZIP ÎÅ ÎÕÖÎÏ
-      ÐÕÔÁÔØ Ó ÓÕÐÅÒ-ÄÉÓËÅÔÁÍÉ ÏÂßÅÍÏÍ × 120 ÍÅÇÁÂÁÊÔ, ÐÒÉ×ÏÄ ÄÌÑ ËÏÔÏÒÙÈ ÍÏÖÅÔ
-      ÔÁËÖÅ ÒÁÂÏÔÁÔØ É Ó ÏÂÙÞÎÙÍÉ ÄÉÓËÅÔÁÍÉ ÏÂßÅÍÏÍ 1.44 ÍÅÇÁÂÁÊÔÁ.</para>
-
-    <para>IOMEGA ÐÒÏÄÁÅÔ ÔÁËÖÅ ÂÏÌÅÅ ÅÍËÏÅ É ÐÒÏÉÚ×ÏÄÉÔÅÌØÎÏÅ ÕÓÔÒÏÊÓÔ×Ï,
-      ËÏÔÏÒÏÅ ÎÁÚÙ×ÁÅÔÓÑ &jaz;/JAZZ.  óÕÝÅÓÔ×ÕÀÔ ÕÓÔÒÏÊÓÔ×Á Jaz ÅÍËÏÓÔØÀ 1 É 2
-      ÇÉÇÁÂÁÊÔÁ.</para>
-
-    <para>õÓÔÒÏÊÓÔ×Á ZIP ÐÒÏÄÁÀÔÓÑ ËÁË ×Ï ×ÎÅÛÎÅÍ, ÔÁË É ×Ï ×ÎÕÔÒÅÎÎÅÍ
-      ÉÓÐÏÌÎÅÎÉÉ, É ÉÓÐÏÌØÚÕÀÔ ÏÄÉÎ ÉÚ ÔÒÅÈ ÉÎÔÅÒÆÅÊÓÏ×:</para>
-
-    <orderedlist>
-      <listitem>
-	<para>éÎÔÅÒÆÅÊÓ SCSI (Small Computer Standard Interface) Ñ×ÌÑÅÔÓÑ ÓÁÍÙÍ
-          ÂÙÓÔÒÙÍ, ÓÌÏÖÎÙÍ, ÒÁÓÛÉÒÑÅÍÙÍ É ÓÁÍÙÍ ÄÏÒÏÇÉÍ.  éÎÔÅÒÆÅÊÓ SCSI
-          ÐÒÉÍÅÎÑÅÔÓÑ ×Ï ×ÓÅÈ ÔÉÐÁÈ ËÏÍÐØÀÔÅÒÏ× ÏÔ PC ÄÏ ÒÁÂÏÞÉÈ ÓÔÁÎÃÉÊ RISC É
-          ÍÉÎÉËÏÍÐØÀÔÅÒÏ×, ÄÌÑ ÐÏÄËÌÀÞÅÎÉÑ ÒÁÚÎÏÏÂÒÁÚÎÏÊ ÐÅÒÉÆÅÒÉÉ, ÔÁËÏÊ, ËÁË
-          ÄÉÓËÏ×ÙÅ É ÌÅÎÔÏÞÎÙÅ ÎÁËÏÐÉÔÅÌÉ, ÓËÁÎÅÒÙ É ÔÁË ÄÁÌÅÅ.  õÓÔÒÏÊÓÔ×Á ZIP
-          Ó ÉÎÔÅÒÆÅÊÓÏÍ SCSI ÍÏÇÕÔ ÂÙÔØ ×Ï ×ÎÕÔÒÅÎÎÅÍ É ×ÎÅÛÎÅÍ ÉÓÐÏÌÎÅÎÉÉ, É
-          ÐÒÅÄÐÏÌÁÇÁÅÔÓÑ, ÞÔÏ ×ÁÛ ÁÄÁÐÔÅÒ ÉÍÅÅÔ ×ÎÅÛÎÉÊ ÒÁÚßÅÍ.</para>
-
-	<note>
-	  <para>åÓÌÉ ×Ù ÉÓÐÏÌØÚÕÅÔÅ ×ÎÅÛÎÅÅ ÕÓÔÒÏÊÓÔ×Ï SCSI, ÎÉ × ËÏÅÍ ÓÌÕÞÁÅ
-            ÎÅÌØÚÑ ÐÏÄËÌÀÞÁÔØ ÉÌÉ ÏÔËÌÀÞÁÔØ ÅÇÏ ÏÔ ÛÉÎÙ SCSI ÐÒÉ ÒÁÂÏÔÁÀÝÅÍ
-            ËÏÍÐØÀÔÅÒÅ.  ÷ ÐÒÏÔÉ×ÎÏÍ ÓÌÕÞÁÅ ÜÔÏ ÍÏÖÅÔ ÐÒÉ×ÅÓÔÉ Ë ÐÏÒÞÅ ÆÁÊÌÏ×ÏÊ
-            ÓÉÓÔÅÍÙ ÎÁ ÄÉÓËÁÈ, ËÏÔÏÒÙÅ ÂÙÌÉ ÐÏÄËÌÀÞÅÎÙ.</para>
-	</note>
-
-	<para>åÓÌÉ ×Ù ÈÏÔÉÔÅ ÄÏÂÉÔØÓÑ ÍÁËÓÉÍÁÌØÎÏÊ ÐÒÏÉÚ×ÏÄÉÔÅÌØÎÏÓÔÉ É
-          ÐÒÏÓÔÏÔÙ ÕÓÔÁÎÏ×ËÉ, ÔÏ ÌÕÞÛÅ ×ÓÅÇÏ ÉÓÐÏÌØÚÏ×ÁÔØ ÉÎÔÅÒÆÅÊÓ SCSI.  üÔÏ
-          ÍÏÖÅÔ ÐÏÔÒÅÂÏ×ÁÔØ ÄÏÂÁ×ÌÅÎÉÑ SCSI-ÁÄÁÐÔÅÒÁ, ÔÁË ËÁË ÂÏÌØÛÉÎÓÔ×Ï PC
-          (ÚÁ ÉÓËÌÀÞÅÎÉÅÍ ×ÙÓÏËÏÐÒÏÉÚ×ÏÄÉÔÅÌØÎÙÈ ÓÅÒ×ÅÒÏ×) ÎÅ ÉÍÅÀÔ ×ÓÔÒÏÅÎÎÏÊ
-          ÐÏÄÄÅÒÖËÉ SCSI.  ëÁÖÄÙÊ SCSI-ÁÄÁÐÔÅÒ, × ÚÁ×ÉÓÉÍÏÓÔÉ ÏÔ ÍÏÄÅÌÉ, ÍÏÖÅÔ
-          ÐÏÄÄÅÒÖÉ×ÁÔØ 7 ÉÌÉ 15 ÕÓÔÒÏÊÓÔ× SCSI.</para>
-
-	<para>ëÁÖÄÏÅ SCSI-ÕÓÔÒÏÊÓÔ×Ï ÉÍÅÅÔ ÓÏÂÓÔ×ÅÎÎÙÊ ËÏÎÔÒÏÌÌÅÒ, É ÜÔÉ
-          ËÏÎÔÒÏÌÌÅÒÙ ×ÅÓØÍÁ ÓÌÏÖÎÙ É ÈÏÒÏÛÏ ÓÔÁÎÄÁÒÔÉÚÏ×ÁÎÙ (×ÔÏÒÁÑ ÂÕË×Á
-          `S' × ÓÌÏ×Å SCSI ÏÚÎÁÞÁÅÔ Standard), ÔÁË ÞÔÏ Ó ÔÏÞËÉ ÚÒÅÎÉÑ
-          ÏÐÅÒÁÃÉÏÎÎÏÊ ÓÉÓÔÅÍÙ ×ÓÅ ÄÉÓËÉ SCSI ×ÙÇÌÑÄÑÔ ÐÒÉÍÅÒÎÏ ÏÄÉÎÁËÏ×Ï, ÔÏ
-          ÖÅ ÓÁÍÏÅ ËÁÓÁÅÔÓÑ ÓÔÒÉÍÅÒÏ× SCSI É ÔÁË ÄÁÌÅÅ.  äÌÑ ÐÏÄÄÅÒÖËÉ
-          ÕÓÔÒÏÊÓÔ× SCSI ÏÐÅÒÁÃÉÏÎÎÏÊ ÓÉÓÔÅÍÅ ÎÕÖÅÎ ÄÒÁÊ×ÅÒ ÔÏÌØËÏ ÄÌÑ
-          ËÏÎËÒÅÔÎÏÇÏ ÁÄÁÐÔÅÒÁ É ÕÎÉ×ÅÒÓÁÌØÎÙÊ ÄÒÁÊ×ÅÒ ÄÌÑ ËÁÖÄÏÇÏ ÔÉÐÁ
-          ÕÓÔÒÏÊÓÔ×, ÄÒÕÇÉÍÉ ÓÌÏ×ÁÍÉ, ÄÒÁÊ×ÅÒ SCSI-ÄÉÓËÁ, ÄÒÁÊ×ÅÒ SCSI-ÓÔÒÉÍÅÒÁ
-          É ÔÁË ÄÁÌÅÅ.  åÓÌÉ ÎÅËÏÔÏÒÙÅ ÕÓÔÒÏÊÓÔ×Á SCSI, Ó ËÏÔÏÒÙÍÉ ÌÕÞÛÅ
-          ÉÓÐÏÌØÚÏ×ÁÔØ ÓÐÅÃÉÁÌÉÚÉÒÏ×ÁÎÎÙÍÉ ÄÒÁÊ×ÅÒÁÍÉ (Ë ÐÒÉÍÅÒÕ, ÓÔÒÉÍÅÒÙ
-          DAT), ÎÏ ÏÎÉ ÂÕÄÕÔ ÒÁÂÏÔÁÔØ É Ó ÕÎÉ×ÅÒÓÁÌØÎÙÍ ÄÒÁÊ×ÅÒÏÍ.  ðÒÏÓÔÏ
-          ÕÎÉ×ÅÒÓÁÌØÎÙÊ ÄÒÁÊ×ÅÒ ÍÏÖÅÔ ÎÅ ÐÏÄÄÅÒÖÉ×ÁÔØ ÎÅËÏÔÏÒÙÈ ×ÏÚÍÏÖÎÏÓÔÅÊ
-          ËÏÎËÒÅÔÎÏÇÏ ÕÓÔÒÏÊÓÔ×Á.</para>
-
-	<para>éÓÐÏÌØÚÏ×ÁÎÉÅ SCSI-ÕÓÔÒÏÊÓÔ×Á ZIP Ó×ÏÄÉÔÓÑ Ë ÏÐÒÅÄÅÌÅÎÉÀ ÔÏÇÏ,
-          ËÁËÏÊ ÆÁÊÌ ÕÓÔÒÏÊÓÔ×Á × ËÁÔÁÌÏÇÅ <filename>/dev</filename>
-          ÓÏÏÔ×ÅÔÓÔ×ÕÅÔ ÕÓÔÒÏÊÓÔ×Õ ZIP.  üÔÏ ÍÏÖÅÔ ÂÙÔØ ×ÙÑÓÎÅÎÏ ÐÏ ÓÏÏÂÝÅÎÉÑÍ,
-          ×ÙÄÁÀÝÉÍÓÑ ÐÒÉ ÚÁÇÒÕÚËÅ FreeBSD (ÐÏÓÌÅ ÚÁÇÒÕÚËÉ ÉÈ ÍÏÖÎÏ ÎÁÊÔÉ ×
-          ÆÁÊÌÅ <filename>/var/log/messages</filename>), ÓÒÅÄÉ ËÏÔÏÒÙÈ ×Ù
-          Õ×ÉÄÉÔÅ ÔÁËÉÅ ÓÔÒÏÞËÉ:</para>
-
-	<programlisting>
-da1: &lt;IOMEGA ZIP 100 D.13&gt; Removable Direct Access SCSI-2 Device
-        </programlisting>
-
-	<para>üÔÏ ÏÚÎÁÞÁÅÔ, ÞÔÏ ÕÓÔÒÏÊÓÔ×Õ ZIP ÓÏÏÔ×ÅÔÓÔ×ÕÅÔ
-	  <filename>/dev/da1</filename>.</para>
-      </listitem>
-
-      <listitem>
-        <para>éÎÔÅÒÆÅÊÓ IDE (Integrated Drive Electronics) Ñ×ÌÑÅÔÓÑ ÄÅÛÅ×ÙÍ
-          ÉÎÔÅÒÆÅÊÓÏÍ, ÉÓÐÏÌØÚÕÅÍÙÍ ÄÉÓËÁÍÉ ÎÁ ÍÎÏÇÉÈ ÎÁÓÔÏÌØÎÙÈ ðë.
-          âÏÌØÛÉÎÓÔ×Ï IDE-ÕÓÔÒÏÊÓÔ× Ñ×ÌÑÀÔÓÑ ÔÏÌØËÏ ×ÎÕÔÒÅÎÎÉÍÉ.</para>
-
-	<para>ðÒÏÉÚ×ÏÄÉÔÅÌØÎÏÓÔØ ÕÓÔÒÏÊÓÔ× ZIP Ó ÉÎÔÅÒÆÅÊÓÏÍ IDE ÓÒÁ×ÎÉÍÁ ÓÏ
-          SCSI-ÕÓÔÒÏÊÓÔ×ÁÍÉ ZIP.  (éÎÔÅÒÆÅÊÓ IDE ÎÅ ÔÁË ÂÙÓÔÒ, ËÁË SCSI, ÎÏ
-          ÐÒÏÉÚ×ÏÄÉÔÅÌØÎÏÓÔØ ÕÓÔÒÏÊÓÔ× ZIP ÏÇÒÁÎÉÞÅÎÁ × ÏÓÎÏ×ÎÏÍ ÍÅÈÁÎÉËÏÊ
-          ÕÓÔÒÏÊÓÔ×Á, Á ÎÅ ÉÎÔÅÒÆÅÊÓÏÍ ÛÉÎÙ.)</para>
-
-	<para>íÉÎÕÓÏÍ ÐÒÉ ÉÓÐÏÌØÚÏ×ÁÎÉÉ ÉÎÔÅÒÆÅÊÓÁ IDE Ñ×ÌÑÅÔÓÑ ÅÇÏ
-          ÏÇÒÁÎÉÞÅÎÎÏÓÔØ.  âÏÌØÛÉÎÓÔ×Ï ÁÄÁÐÔÅÒÏ× IDE ÍÏÖÅÔ ÐÏÄÄÅÒÖÉ×ÁÔØ ÔÏÌØËÏ
-          Ä×Á ÕÓÔÒÏÊÓÔ×Á, É ÉÎÔÅÒÆÅÊÓ IDE ÎÅ ÂÙÌ ÒÁÓÓÞÉÔÁÎ ÎÁ ÛÉÒÏËÏÅ
-          ÐÒÉÍÅÎÅÎÉÅ.  îÁÐÒÉÍÅÒ, ÏÒÉÇÉÎÁÌØÎÙÊ ÉÎÔÅÒÆÅÊÓ IDE ÎÅ ÐÏÄÄÅÒÖÉ×ÁÅÔ
-          ×ÉÎÞÅÓÔÅÒÙ Ó ËÏÌÉÞÅÓÔ×ÏÍ ÄÏÒÏÖÅË, ÐÒÅ×ÙÛÁÀÝÉÍ 1024, ÞÔÏ ÚÁÓÔÁ×ÌÑÅÔ
-          ÍÎÏÇÉÈ ÎÅÏÂÄÕÍÁÎÎÏ ÏÂÎÏ×ÌÑÔØ ÁÐÐÁÒÁÔÕÒÕ.  åÓÌÉ Õ ×ÁÓ ÅÓÔØ ÐÌÁÎÙ ÐÏ
-          ÒÁÓÛÉÒÅÎÉÀ ×ÏÚÍÏÖÎÏÓÔÅÊ ×ÁÛÅÇÏ ðë ÄÏÂÁ×ÌÅÎÉÅÍ ÄÏÐÏÌÎÉÔÅÌØÎÏÇÏ ÄÉÓËÁ,
-          ÓÔÒÉÍÅÒÁ ÉÌÉ ÓËÁÎÅÒÁ, ×ÁÍ ÓÔÏÉÔ ÚÁÄÕÍÁÔØÓÑ Ï ÐÒÉÏÂÒÅÔÅÎÉÉ
-          SCSI-ÁÄÁÐÔÅÒÁ É ÕÓÔÒÏÊÓÔ×Á ZIP Ó ÉÎÔÅÒÆÅÊÓÏÍ SCSI ×Ï ÉÚÂÅÖÁÎÉÅ
-          ÐÒÏÂÌÅÍ × ÂÕÄÕÝÅÍ.</para>
-
-	<para>IDE ÕÓÔÒÏÊÓÔ×Á ×Ï FreeBSD ÐÒÅÄ×ÁÒÑÀÔÓÑ ÂÕË×ÏÊ
-          <literal>a</literal>.  îÁÐÒÉÍÅÒ, ÖÅÓÔËÉÊ ÄÉÓË IDE ÍÏÖÅÔ ÎÁÚÙ×ÁÔØÓÑ
-	  <filename>/dev/ad0</filename>, IDE (ATAPI) ÐÒÉ×ÏÄ ËÏÍÐÁËÔ-ÄÉÓËÏ×
-          ÍÏÖÅÔ ÎÁÚÙ×ÁÔØÓÑ <filename>/dev/acd1</filename>, É ÔÁË ÄÁÌÅÅ.</para>
-      </listitem>
-
-      <listitem>
-	<para>éÎÔÅÒÆÅÊÓ ÐÁÒÁÌÌÅÌØÎÏÇÏ ÐÏÒÔÁ ÐÏÐÕÌÑÒÅÎ ÄÌÑ ÐÅÒÅÎÏÓÉÍÙÈ ×ÎÅÛÎÉÈ
-          ÕÓÔÒÏÊÓÔ×, ÔÁËÉÈ, ËÁË ×ÎÅÛÎÉÅ ÕÓÔÒÏÊÓÔ×Á ZIP É ÓËÁÎÅÒÙ, ÐÏÔÏÍÕ ÞÔÏ
-          ÐÒÁËÔÉÞÅÓËÉ ÌÀÂÏÊ ËÏÍÐØÀÔÅÒ ÉÍÅÅÔ ÓÔÁÎÄÁÒÔÎÙÊ ÐÁÒÁÌÌÅÌØÎÙÊ ÐÏÒÔ
-          (ÏÂÙÞÎÏ ÉÓÐÏÌØÚÕÅÍÙÊ ÄÌÑ ÐÏÄËÌÀÞÅÎÉÑ ÐÒÉÎÔÅÒÁ).  üÔÏ ÕÐÒÏÝÁÅÔ ÖÉÚÎØ
-          ÔÅÍ, ËÔÏ ÐÅÒÅÎÏÓÉÔ ÄÁÎÎÙÅ ÍÅÖÄÕ ÎÅÓËÏÌØËÉÍÉ ËÏÍÐØÀÔÅÒÁÍÉ ÐÏÓÒÅÄÓÔ×ÏÍ
-          Ó×ÏÅÇÏ ZIP-ÕÓÔÒÏÊÓÔ×Á.</para>
-
-	<para>ëÁË ÐÒÁ×ÉÌÏ, ÐÒÏÉÚ×ÏÄÉÔÅÌØÎÏÓÔØ ÚÄÅÓØ ÎÉÖÅ, ÞÅÍ × ÓÌÕÞÁÅ
-          ZIP-ÕÓÔÒÏÊÓÔ× Ó ÉÎÔÅÒÆÅÊÓÁÍÉ SCSI ÉÌÉ IDE, ÔÁË ËÁË ÏÎÁ ÏÇÒÁÎÉÞÅÎÁ
-          ÓËÏÒÏÓÔØÀ ÐÁÒÁÌÌÅÌØÎÏÇÏ ÐÏÒÔÁ.  ðÒÏÐÕÓËÎÁÑ ÓÐÏÓÏÂÎÏÓÔØ ÐÁÒÁÌÌÅÌØÎÏÇÏ
-          ÐÏÒÔÁ ÚÎÁÞÉÔÅÌØÎÏ ÒÁÚÌÉÞÁÅÔÓÑ ÍÅÖÄÕ ÒÁÚÎÙÍÉ ËÏÍÐØÀÔÅÒÁÍÉ, É ÚÁÞÁÓÔÕÀ
-          ÍÏÖÅÔ ÎÁÓÔÒÁÉ×ÁÔØÓÑ × BIOS ËÏÍÐØÀÔÅÒÁ.  îÅËÏÔÏÒÙÍ ÍÁÛÉÎÁÍ ÔÁËÖÅ ÍÏÖÅÔ
-          ÐÏÎÁÄÏÂÉÔØÓÑ ÎÁÓÔÒÏÉÔØ BIOS ÎÁ ÒÁÂÏÔÕ ÐÁÒÁÌÌÅÌØÎÏÇÏ ÐÏÒÔÁ ×
-          Ä×ÕÎÁÐÒÁ×ÌÅÎÎÏÍ ÒÅÖÉÍÅ.  (ðÁÒÁÌÌÅÌØÎÙÅ ÐÏÒÔÙ ÉÚÎÁÞÁÌØÎÏ ÂÙÌÉ
-          ÐÒÅÄÎÁÚÎÁÞÅÎÙ ÔÏÌØËÏ ÄÌÑ ×Ù×ÏÄÁ ÎÁ ÐÒÉÎÔÅÒÙ)</para>
-      </listitem>
-    </orderedlist>
-  </sect1>
-
-  <sect1>
-    <title>õÓÔÒÏÊÓÔ×Ï ZIP ÄÌÑ ÐÁÒÁÌÌÅÌØÎÏÇÏ ÐÏÒÔÁ: äÒÁÊ×ÅÒ ÕÓÔÒÏÊÓÔ×Á
-      <devicename>vpo</devicename></title>
-
-    <para>äÌÑ ÉÓÐÏÌØÚÏ×ÁÎÉÑ ZIP-ÕÓÔÒÏÊÓÔ×Á Ó ÉÎÔÅÒÆÅÊÓÏÍ ÐÁÒÁÌÌÅÌØÎÏÇÏ ÐÏÒÔÁ
-      ×Ï FreeBSD × ÑÄÒÅ ÄÏÌÖÎÏ ÂÙÔØ ÐÒÉÓÕÔÓÔ×Ï×ÁÔØ ÕÓÔÒÏÊÓÔ×Ï.  õÓÔÒÏÊÓÔ×Á ZIP
-      ÄÌÑ ÐÁÒÁÌÌÅÌØÎÏÇÏ ÐÏÒÔÁ ÉÍÅÀÔ ×ÓÔÒÏÅÎÎÙÊ ËÏÎÔÒÏÌÌÅÒ SCSI.  äÒÁÊ×ÅÒ vpo
-      ÐÏÚ×ÏÌÑÅÔ ÑÄÒÕ FreeBSD ÒÁÂÏÔÁÔØ ÓÏ SCSI-ËÏÎÔÒÏÌÌÅÒÏÍ ZIP-ÕÓÔÒÏÊÓÔ×Á ÞÅÒÅÚ
-      ÐÁÒÁÌÌÅÌØÎÙÊ ÐÏÒÔ.</para>
-
-    <para>ôÁË ËÁË ÄÒÁÊ×ÅÒ vpo ÎÅ ×ÈÏÄÉÔ × ÓÔÁÎÄÁÒÔÎÏÅ ÑÄÒÏ (ÎÁÞÉÎÁÑ Ó FreeBSD
-      3.2), ÔÏ ÄÌÑ ÉÓÐÏÌØÚÏ×ÁÎÉÑ ÕÓÔÒÏÊÓÔ×Á ×ÁÍ ÎÅÏÂÈÏÄÉÍÏ ÐÅÒÅÓÔÒÏÉÔØ ÑÄÒÏ.
-      ðÒÏÃÅÓÓ ÐÏÓÔÒÏÅÎÉÑ ÑÄÒÁ ÐÏÄÒÏÂÎÏ ÏÐÉÓÁÎ × <ulink url="&url.books.handbook;/kernelconfig.html">òÕËÏ×ÏÄÓÔ×Å
-      &os;</ulink>.  îÉÖÅ ÐÒÉ×ÅÄÅÎÁ ËÒÁÔËÁÑ ÐÏÓÌÅÄÏ×ÁÔÅÌØÎÏÓÔØ ÛÁÇÏ× ÄÌÑ ×ËÌÀÞÅÎÉÑ ÄÒÁÊ×ÅÒÁ vpo:</para>
-
-    <orderedlist>
-      <listitem>
-	<para>úÁÐÕÓÔÉÔÅ <command>/stand/sysinstall</command> É ÕÓÔÁÎÏ×ÉÔÅ ×
-          ×ÁÛÅÊ ÓÉÓÔÅÍÅ ÉÓÈÏÄÎÙÊ ËÏÄ ÑÄÒÁ.</para>
-      </listitem>
-
-      <listitem>
-        <para>óÏÂÅÒÉÔÅ ËÏÎÆÉÇÕÒÁÃÉÏÎÎÙÊ ÆÁÊÌ ÑÄÒÁ Ó ÐÏÄÄÅÒÖËÏÊ ÄÒÁÊ×ÅÒÁ
-          ÄÌÑ ÕÓÔÒÏÊÓÔ×Á vpo:</para>
-
-	<screen>
-&prompt.root; <userinput>cd /sys/i386/conf</userinput>
-&prompt.root; <userinput>cp GENERIC MYKERNEL</userinput>
-        </screen>
-
-	<para>ïÔÒÅÄÁËÔÉÒÕÊÔÅ ÆÁÊÌ <filename>MYKERNEL</filename>, ÉÚÍÅÎÉ× ÓÔÒÏËÕ
-	  <literal>ident</literal> ÎÁ <literal>MYKERNEL</literal> É
-          ÒÁÓËÏÍÍÅÎÔÉÒÕÊÔÅ ÓÔÒÏÞËÕ, ÏÐÉÓÙ×ÁÀÝÕÀ ÄÒÁÊ×ÅÒ vpo.</para>
-
-	<para>åÓÌÉ Õ ×ÁÓ ÉÍÅÅÔÓÑ ×ÔÏÒÏÊ ÐÁÒÁÌÌÅÌØÎÙÊ ÐÏÒÔ, ×ÁÍ ÍÏÖÅÔ
-          ÐÏÔÒÅÂÏ×ÁÔØÓÑ ÓËÏÐÉÒÏ×ÁÔØ ÒÁÚÄÅÌ ÄÌÑ <literal>ppc0</literal>, ÞÔÏÂÙ
-          ÓÏÚÄÁÔØ ÕÓÔÒÏÊÓÔ×Ï <literal>ppc1</literal>.  ÷ÔÏÒÏÊ ÐÁÒÁÌÌÅÌØÎÙÊ
-          ÐÏÒÔ, ËÁË ÐÒÁ×ÉÌÏ, ÉÓÐÏÌØÚÕÅÔ IRQ 5 É ÁÄÒÅÓ 378.  ÷ ËÏÎÆÉÇÕÒÁÃÉÏÎÎÏÍ
-          ÆÁÊÌÅ ÔÒÅÂÕÅÔÓÑ ÕËÁÚÁÔØ ÔÏÌØËÏ IRQ.</para>
-
-	<para>åÓÌÉ ÄÉÓË Ó ËÏÒÎÅ×ÏÊ ÆÁÊÌÏ×ÏÊ ÓÉÓÔÅÍÏÊ Ñ×ÌÑÅÔÓÑ ÄÉÓËÏÍ Ó
-          ÉÎÔÅÒÆÅÊÓÏÍ SCSI, ÔÏ ×Ù ÍÏÖÅÔÅ ÓÔÏÌËÎÕÔØÓÑ Ó ÐÒÏÂÌÅÍÏÊ ×
-          ÐÏÓÌÅÄÏ×ÁÔÅÌØÎÏÓÔÉ ÏÂÎÁÒÕÖÅÎÉÑ ÕÓÔÒÏÊÓÔ×, ÞÔÏ ÍÏÖÅÔ ÐÒÉ×ÅÓÔÉ Ë
-          ÐÏÐÙÔËÅ ÉÓÐÏÌØÚÏ×ÁÎÉÑ ZIP-ÕÓÔÒÏÊÓÔ×Á × ËÁÞÅÓÔ×Å ÄÉÓËÁ Ó ËÏÒÎÅ×ÏÊ
-          ÆÁÊÌÏ×ÏÊ ÓÉÓÔÅÍÏÊ.  üÔÏ ÂÕÄÅÔ ÐÒÉ×ÏÄÉÔØ Ë ÏÛÉÂËÅ ÚÁÇÒÕÚËÉ, ÐÏËÁ ×Ù ÎÅ
-          ÐÏÍÅÓÔÉÔÅ ËÏÒÎÅ×ÕÀ ÆÁÊÌÏ×ÕÀ ÓÉÓÔÅÍÕ FreeBSD ÎÁ ×ÁÛ ZIP-ÄÉÓË!  äÌÑ
-          ÜÔÏÇÏ ×ÁÍ ÎÕÖÎÏ <quote>ÚÁÆÉËÓÉÒÏ×ÁÔØ</quote> ËÏÒÎÅ×ÏÊ ÄÉÓË, Á ÉÍÅÎÎÏ
-          ÚÁÓÔÁ×ÉÔØ ÑÄÒÏ ÁÓÓÏÃÉÉÒÏ×ÁÔØ ×ÙÂÒÁÎÎÏÅ ÕÓÔÒÏÊÓÔ×Ï Ó ÕÓÔÒÏÊÓÔ×ÏÍ
-          <filename>/dev/da0</filename>, ÔÏ ÅÓÔØ Ó ËÏÒÎÅ×ÙÍ SCSI-ÄÉÓËÏÍ.  úÁÔÅÍ
-          ZIP-ÄÉÓË ÂÕÄÅÔ Ó×ÑÚÁÎ ÓÏ ÓÌÅÄÕÀÝÉÍ ÄÏÓÔÕÐÎÙÍ SCSI-ÄÉÓËÏÍ, ÎÁÐÒÉÍÅÒ, Ó
-	  <literal>/dev/da1</literal>.  äÌÑ ÔÏÇÏ, ÞÔÏÂÙ ÐÒÉ×ÑÚÁÔØ ×ÁÛ SCSI-ÄÉÓË
-	  Ë ÕÓÔÒÏÊÓÔ×Õ <literal>da0</literal>, ÉÚÍÅÎÉÔÅ ÓÔÒÏÞËÕ
-
-	  <programlisting>device  da0</programlisting>
-
-	  ÎÁ
-
-	  <programlisting>disk da0 at scbus0 target 0 unit 0</programlisting>
-        </para>
-
-	<para>÷ÁÍ ÍÏÖÅÔ ÐÏÔÒÅÂÏ×ÁÔØÓÑ ÓÍÅÎÉÔØ ÎÏÍÅÒ ÕÓÔÒÏÊÓÔ×Á (target) ×ÙÛÅ ÎÁ
-          SCSI ID ×ÁÛÅÇÏ ÄÉÓËÁ.  ôÁËÖÅ ×ÁÍ ÎÕÖÎÏ ÐÒÉ×ÑÚÁÔØ scbus0 Ë ×ÁÛÅÍÕ
-          ËÏÎÔÒÏÌÌÅÒÕ.  îÁÐÒÉÍÅÒ, ÅÓÌÉ Õ ×ÁÓ ÕÓÔÁÎÏ×ÌÅÎ ËÏÎÔÒÏÌÌÅÒ &adaptec;
-          15xx, ×ÁÍ ÎÕÖÎÏ ÓÍÅÎÉÔØ
-
-	  <programlisting>controller scbus0</programlisting>
-
-	  ÎÁ
-
-	  <programlisting>controller scbus0 at aha0</programlisting>
-        </para>
-
-	<para>é ÎÁËÏÎÅÃ, ÒÁÚ ×Ù ÒÅÄÁËÔÉÒÕÅÔÅ ËÏÎÆÉÇÕÒÁÃÉÏÎÎÙÊ ÆÁÊÌ ÑÄÒÁ, ×Ù
-          ÍÏÖÅÔÅ ÚÁÏÄÎÏ ÕÄÁÌÉÔØ ×ÓÅ ÎÅÎÕÖÎÙÅ ÄÒÁÊ×ÅÒÙ.  üÔÏ ÎÕÖÎÏ ÄÅÌÁÔØ Ó
-          ÂÏÌØÛÏÊ ÏÓÔÏÒÏÖÎÏÓÔØÀ, É ÔÏÌØËÏ ÅÓÌÉ ×Ù Õ×ÅÒÅÎÙ ×Ï ×ÎÏÓÉÍÙÈ
-          ÉÚÍÅÎÅÎÉÑÈ.  õÄÁÌÅÎÉÅ ÎÅÎÕÖÎÙÈ ÄÒÁÊ×ÅÒÏ× ÕÍÅÎØÛÉÔ ÒÁÚÍÅÒ ÑÄÒÁ, ÞÔÏ
-          ÄÁÓÔ ÂÏÌØÛÅ ÐÁÍÑÔÉ ÄÌÑ ×ÁÛÉÈ ÐÒÉÌÏÖÅÎÉÊ.  äÌÑ ÏÐÒÅÄÅÌÅÎÉÑ ÔÏÇÏ,
-          ËÁËÉÅ ÄÒÁÊ×ÅÒÙ ÎÅ ÎÕÖÎÙ, ÐÅÒÅÊÄÉÔÅ × ËÏÎÅà ÆÁÊÌÁ
-          <filename>/var/log/messages</filename>, É ÐÏÉÝÉÔÅ ÓÔÒÏÞËÉ Ó
-          ÄÉÁÇÎÏÓÔÉËÏÊ "not found".  úÁÔÅÍ ÚÁËÏÍÍÅÎÔÉÒÕÊÔÅ ÜÔÉ ÕÓÔÒÏÊÓÔ×Á ×
-          ËÏÎÆÉÇÕÒÁÃÉÏÎÎÏÍ ÆÁÊÌÅ ×ÁÛÅÇÏ ÑÄÒÁ.  ÷Ù ÍÏÖÅÔÅ ÔÁËÖÅ ÉÚÍÅÎÉÔØ ÄÒÕÇÉÅ
-          ÐÁÒÁÍÅÔÒÙ ÄÌÑ ÕÍÅÎØÛÅÎÉÑ ÒÁÚÍÅÒÁ É ÕÓËÏÒÅÎÉÑ ÒÁÂÏÔÙ ×ÁÛÅÇÏ ÑÄÒÁ.
-          ðÒÏÞÔÉÔÅ ÒÁÚÄÅÌ Ï ÐÅÒÅËÏÍÐÉÌÑÃÉÉ ×ÁÛÅÇÏ ÑÄÒÁ ÄÌÑ ÐÏÌÕÞÅÎÉÑ ÂÏÌÅÅ
-          ÐÏÌÎÏÊ ÉÎÆÏÒÍÁÃÉÉ.</para>
-      </listitem>
-
-      <listitem>
-	<para>ôÅÐÅÒØ ÐÒÉÛÌÏ ×ÒÅÍÑ ËÏÍÐÉÌÑÃÉÉ ÑÄÒÁ:</para>
-
-	<screen>
-&prompt.root; <userinput>/usr/sbin/config MYKERNEL</userinput>
-&prompt.root; <userinput>cd ../../compile/MYKERNEL</userinput>
-&prompt.root; <userinput>make clean depend &amp;&amp; make all install</userinput>
-        </screen>
-      </listitem>
-    </orderedlist>
-
-    <para>ðÏÓÌÅ ÔÏÇÏ, ËÁË ÑÄÒÏ ÂÕÄÅÔ ÐÅÒÅÓÔÒÏÅÎÏ, ×ÁÍ ÎÕÖÎÏ ×ÙÐÏÌÎÉÔØ
-      ÐÅÒÅÚÁÇÒÕÚËÕ.  ðÅÒÅÄ ÔÅÍ, ËÁË ÜÔÏ ÓÄÅÌÁÔØ, ÕÄÏÓÔÏ×ÅÒØÔÅÓØ, ÞÔÏ
-      ZIP-ÕÓÔÒÏÊÓÔ×Ï ÐÏÄËÌÀÞÅÎÏ Ë ÐÁÒÁÌÌÅÌØÎÏÍÕ ÐÏÒÔÕ.  ÷Ù ÄÏÌÖÎÙ Õ×ÉÄÅÔØ
-      ZIP-ÕÓÔÒÏÊÓÔ×Ï ÓÒÅÄÉ ÓÏÏÂÝÅÎÉÊ, ×ÙÄÁ×ÁÅÍÙÈ ÐÒÉ ÚÁÇÒÕÚËÅ, ËÁË ÕÓÔÒÏÊÓÔ×Ï
-      vpo0 ÉÌÉ vpo1, × ÚÁ×ÉÓÉÍÏÓÔÉ ÏÔ ÔÏÇÏ, Ë ËÁËÏÍÕ ÐÁÒÁÌÌÅÌØÎÏÍÕ ÐÏÒÔÕ
-      ÏÎÏ ÐÏÄËÌÀÞÅÎÏ.  ëÒÏÍÅ ÔÏÇÏ, ÂÕÄÅÔ ÕËÁÚÁÎÏ, Ë ËÁËÏÍÕ ÆÁÊÌÕ ÕÓÔÒÏÊÓÔ×Á
-      ÂÙÌ ÐÒÉ×ÑÚÁÎ ZIP-ÄÉÓË.  üÔÏ ÂÕÄÅÔ <filename>/dev/da0</filename>, ÅÓÌÉ
-      × ÓÉÓÔÅÍÅ ÎÅÔ ÄÒÕÇÉÈ SCSI-ÄÉÓËÏ×, ÉÌÉ <filename>/dev/da1</filename> ×
-      ÓÌÕÞÁÅ, ÅÓÌÉ ×ÁÛ SCSI-ÄÉÓË ÚÁÆÉËÓÉÒÏ×ÁÎ × ËÁÞÅÓÔ×Å ËÏÒÎÅ×ÏÇÏ
-      ÕÓÔÒÏÊÓÔ×Á.</para>
-  </sect1>
-
-  <sect1>
-    <title>íÏÎÔÉÒÏ×ÁÎÉÅ ÄÉÓËÏ× ZIP</title>
-
-    <para>äÌÑ ÒÁÂÏÔÙ Ó ZIP-ÄÉÓËÏÍ ×Ù ÄÏÌÖÎÙ ÅÇÏ ÓÍÏÎÔÉÒÏ×ÁÔØ, ÔÏÞÎÏ ÔÁË ÖÅ, ËÁË
-      É ÌÀÂÏÅ ÄÒÕÇÏÅ ÄÉÓËÏ×ÏÅ ÕÓÔÒÏÊÓÔ×Ï.  æÁÊÌÏ×ÁÑ ÓÉÓÔÅÍÁ ÎÁ ÕÓÔÒÏÊÓÔ×Å
-      ÐÒÅÄÓÔÁ×ÌÅÎÁ ËÁË ÓÌÁÊÓ 4, ÐÏÜÔÏÍÕ ÄÌÑ ÕÓÔÒÏÊÓÔ× Ó ÐÁÒÁÌÌÅÌØÎÙÍ ÉÌÉ
-      SCSI-ÉÎÔÅÒÆÅÊÓÏÍ ×ÁÍ ÎÕÖÎÏ ÓÄÅÌÁÔØ ÓÌÅÄÕÀÝÅÅ:</para>
-
-    <screen>
-&prompt.root; <userinput>mount_msdos /dev/da1s4 /mnt</userinput>
-    </screen>
-
-    <para>äÌÑ ÕÓÔÒÏÊÓÔ× ZIP Ó ÉÎÔÅÒÆÅÊÓÏÍ IDE ÉÓÐÏÌØÚÕÊÔÅ ×ÏÔ ÞÔÏ:</para>
-
-    <screen>
-&prompt.root; <userinput>mount_msdos /dev/ad1s4 /mnt</userinput>
-    </screen>
-
-    <para>äÌÑ ÏÂÌÅÇÞÅÎÉÑ ÍÏÎÔÉÒÏ×ÁÎÉÑ ÂÕÄÅÔ ÐÏÌÅÚÎÏ ÔÁËÖÅ ÏÂÎÏ×ÉÔØ ÆÁÊÌ
-      <filename>/etc/fstab</filename>.  äÏÂÁ×ØÔÅ ÓÔÒÏËÕ, ÓÏÏÔ×ÅÔÓÔ×ÕÀÝÕÀ
-      ×ÁÛÅÊ ÓÉÓÔÅÍÅ, ÎÁÐÏÄÏÂÉÅ ÓÌÅÄÕÀÝÅÊ:
-
-      <programlisting>/dev/da1s4  /zip msdos rw,noauto  0 0</programlisting>
-
-      É ÓÏÚÄÁÊÔÅ ËÁÔÁÌÏÇ <filename>/zip</filename>.
-    </para>
-
-    <para>ôÅÐÅÒØ ×Ù ÍÏÖÅÔÅ ÍÏÎÔÉÒÏ×ÁÔØ ÄÉÓË ÐÒÏÓÔÏ ÐÏ ËÏÍÁÎÄÅ
-
-      <screen>&prompt.root; <userinput>mount /zip</userinput></screen>
-
-      É ×ÙÐÏÌÎÑÔØ ÒÁÚÍÏÎÔÉÒÏ×ÁÎÉÅ ÐÏ ËÏÍÁÎÄÅ
-
-      <screen>&prompt.root; <userinput>umount /zip</userinput></screen>
-    </para>
-
-    <para>âÏÌÅÅ ÐÏÄÒÏÂÎÁÑ ÉÎÆÏÒÍÁÃÉÑ Ï ÆÏÒÍÁÔÅ ÆÁÊÌÁ
-      <filename>/etc/fstab</filename> ÎÁÈÏÄÉÔÓÑ × &man.fstab.5;.</para>
-
-    <para>÷Ù ÍÏÖÅÔÅ ÔÁËÖÅ ÓÏÚÄÁÔØ ÆÁÊÌÏ×ÕÀ ÓÉÓÔÅÍÕ FreeBSD ÎÁ ZIP-ÄÉÓËÅ ÐÒÉ
-      ÐÏÍÏÝÉ &man.newfs.8;.  ïÄÎÁËÏ ÄÉÓË ÍÏÖÎÏ ÂÕÄÅÔ ÉÓÐÏÌØÚÏ×ÁÔØ ÔÏÌØËÏ ×
-      ÓÉÓÔÅÍÅ FreeBSD É, ÍÏÖÅÔ ÂÙÔØ, Ó ÅÝÅ ÎÅÓËÏÌØËÉÍÉ ËÌÏÎÁÍÉ &unix;, ËÏÔÏÒÙÅ
-      ÒÁÓÐÏÚÎÁÀÔ ÆÁÊÌÏ×ÙÅ ÓÉÓÔÅÍÙ FreeBSD.  (ïÐÒÅÄÅÌÅÎÎÏ ÜÔÏÇÏ ÎÅ ÍÏÇÕÔ ÄÅÌÁÔØ ÎÉ
-      &ms-dos; ÎÉ &windows;.)</para>
-  </sect1>
-</article>
diff --git a/ru_RU.KOI8-R/books/faq/book.sgml b/ru_RU.KOI8-R/books/faq/book.sgml
index 1809a0e828..11960db1a9 100644
--- a/ru_RU.KOI8-R/books/faq/book.sgml
+++ b/ru_RU.KOI8-R/books/faq/book.sgml
@@ -1326,19 +1326,6 @@
       </qandaentry>
 
       <qandaentry>
-	<question id="multiboot">
-	  <para>íÏÇÕ ÌÉ Ñ ÉÍÅÔØ ÂÏÌÅÅ ÞÅÍ ÏÄÎÕ ÏÐÅÒÁÃÉÏÎÎÕÀ ÓÉÓÔÅÍÕ ÎÁ ÍÏ£Í
-	    ðë?</para>
-	</question>
-
-	<answer>
-	  <para>÷ÚÇÌÑÎÉÔÅ ÎÁ ÜÔÏ <ulink
-	    url="&url.articles.multi-os;/index.html">
-	    ÒÕËÏ×ÏÄÓÔ×Ï</ulink>.</para>
-	</answer>
-      </qandaentry>
-
-      <qandaentry>
 	<question id="windows-coexist">
 	  <para>íÏÖÅÔ ÌÉ &windows; ÓÏÓÕÝÅÓÔ×Ï×ÁÔØ Ó &os;?</para>
 	</question>
@@ -4905,10 +4892,7 @@ kern.sched.name: 4BSD</screen>
 	    &man.disklabel.8;.  ÷Ù ÔÁËÖÅ ÄÏÌÖÎÙ ÕÓÔÁÎÏ×ÉÔØ ÎÁ ÏÂÁ ÄÉÓËÁ
 	    ÐÒÏÇÒÁÍÍÕ booteasy Ó ÐÏÍÏÝØÀ &man.boot0cfg.8;, ÞÔÏÂÙ ÉÍÅÔØ
 	    ×ÏÚÍÏÖÎÏÓÔØ ×ÙÐÏÌÎÑÔØ ÚÁÇÒÕÚËÕ ËÁË ÓÔÁÒÏÊ, ÔÁË É ÎÏ×ÏÊ ÓÉÓÔÅÍÙ
-	    ÐÏÓÌÅ ×ÙÐÏÌÎÅÎÉÑ ËÏÐÉÒÏ×ÁÎÉÑ.  ïÂÒÁÔÉÔÅÓØ Ë <ulink
-	    url="&url.articles.formatting-media;/index.html">
-	    ÒÕËÏ×ÏÄÓÔ×Õ ÐÏ ÆÏÒÍÁÔÉÒÏ×ÁÎÉÀ ÎÏÓÉÔÅÌÅÊ</ulink> ÚÁ ÐÏÄÒÏÂÎÙÍ
-	    ÏÐÉÓÁÎÉÅÍ ÜÔÏÇÏ ÐÒÏÃÅÓÓÁ.</para>
+	    ÐÏÓÌÅ ×ÙÐÏÌÎÅÎÉÑ ËÏÐÉÒÏ×ÁÎÉÑ.</para>
 
 	  <para>éÔÁË, ÐÏÓÌÅ ÐÏÄÇÏÔÏ×ËÉ ÄÉÓËÁ ×Ù ÍÏÖÅÔÅ ÐÅÒÅÎÏÓÉÔØ ÄÁÎÎÙÅ.  ë
 	    ÓÏÖÁÌÅÎÉÀ, ×Ù ÎÅ ÍÏÖÅÔÅ ÐÒÏÓÔÏ ÓËÏÐÉÒÏ×ÁÔØ ÄÁÎÎÙÅ.  ôÁËÉÅ ×ÅÝÉ, ËÁË
diff --git a/ru_RU.KOI8-R/htdocs/docproj/translations.sgml b/ru_RU.KOI8-R/htdocs/docproj/translations.sgml
index 1e4291462b..1b1e53a156 100644
--- a/ru_RU.KOI8-R/htdocs/docproj/translations.sgml
+++ b/ru_RU.KOI8-R/htdocs/docproj/translations.sgml
@@ -114,9 +114,6 @@
       <dd><a href="http://www.cybershade.us/freebsd/bg/fdp/split/">õÞÅÂÎÉË ÐÏ
 	ðÒÏÅËÔÕ ÄÏËÕÍÅÎÔÉÒÏ×ÁÎÉÑ FreeBSD ÄÌÑ ÎÏ×ÙÈ ÕÞÁÓÔÎÉËÏ×</a></dd>
 
-      <dd><a href="http://www.cybershade.us/freebsd/bg/multi-os/">õÓÔÁÎÏ×ËÁ É
-        ÉÓÐÏÌØÚÏ×ÁÎÉÅ FreeBSD Ó ÄÒÕÇÉÍÉ ÏÐÅÒÁÃÉÏÎÎÙÍÉ ÓÉÓÔÅÍÁÍÉ</a></dd>
-
       <dt><i>äÏËÕÍÅÎÔÙ, ÎÁÈÏÄÑÝÉÅÓÑ × ÒÁÂÏÔÅ</i></dt>
 
       <dd>òÕËÏ×ÏÄÓÔ×Ï FreeBSD</dd>
diff --git a/ru_RU.KOI8-R/htdocs/docs/books.sgml b/ru_RU.KOI8-R/htdocs/docs/books.sgml
index 0786e19d22..777360b3fb 100644
--- a/ru_RU.KOI8-R/htdocs/docs/books.sgml
+++ b/ru_RU.KOI8-R/htdocs/docs/books.sgml
@@ -100,12 +100,6 @@
 
 	<!-- óÔÁÔØÉ ÏÔÓÏÒÔÉÒÏ×ÁÎÙ ÐÏ ÉÍÅÎÉ ËÁÔÁÌÏÇÏ× -->
 
-	    <p><a href="&url.ru.articles;/5-roadmap/index.html">
-	      äÏÒÏÇÁ Ë 5-STABLE</a> (5-roadmap)<br/>
-	      ïÐÉÓÙ×ÁÅÔ ÓÒÅÄÎÅÓÒÏÞÎÙÅ ÐÌÁÎÙ ÒÁÚÒÁÂÏÔËÉ É ×ÙÐÕÓËÁ
-	      ÒÅÌÉÚÏ×, ×ÅÄÕÝÉÅ Ë ×ÅÔËÅ 5-STABLE.  üÔÁ ÓÔÁÔØÑ ÐÒÅÄÓÔÁ×ÌÑÅÔ ×
-	      ÏÓÎÏ×ÎÏÍ ÉÓÔÏÒÉÞÅÓËÉÊ ÉÎÔÅÒÅÓ.</p>
-
 	    <p><a href="&url.articles;/bsdl-gpl/index.html">ðÏÞÅÍÕ ÎÕÖÎÏ
 	      ÉÓÐÏÌØÚÏ×ÁÔØ ÌÉÃÅÎÚÉÀ BSD ÄÌÑ ÐÒÏÅËÔÏ× Ó ÏÔËÒÙÔÙÍ ÉÓÈÏÄÎÙÍ
 	      ÔÅËÓÔÏÍ</a> (bsdl-gpl)<br/>
@@ -120,12 +114,6 @@
 	      : A Case Study</a> (casestudy-argentina.com)<br/>
               ëÁË FreeBSD ÂÙÌ ÐÏÌÅÚÅÎ ÂÏÌØÛÏÍÕ ISP × ìÁÔÉÎÓËÏÊ áÍÅÒÉËÅ.</p>
 
-	    <p><a href="&url.ru.articles;/checkpoint/index.html">
-	      éÎÔÅÇÒÁÃÉÑ Checkpoint VPN-1/Firewall-1 É FreeBSD IPsec</a>
-	      (checkpoint)<br/>
-	      ëÁË ÎÁÓÔÒÏÉÔØ Checkpoint VPN-1/Firewall-1 É FreeBSD
-	      IPsec.</p>
-
 	    <p><a href="&url.ru.articles;/committers-guide/index.html">
 	      óÐÒÁ×ÏÞÎÉË ËÏÍÍÉÔÔÅÒÁ</a> (committers-guide)<br/>
 	      îÁÞÁÌØÎÁÑ ÉÎÆÏÒÍÁÃÉÑ ÄÌÑ ËÏÍÍÉÔÔÅÒÏ× FreeBSD.</p>
@@ -160,22 +148,6 @@
 	      ×ÏÐÒÏÓÙ ÒÁÂÏÔÙ CVSup</a> (cvsup-advanced)<br/>
 	      óÔÁÔØÑ Ó ÎÅËÏÔÏÒÙÍÉ ÓÏ×ÅÔÁÍÉ Ï ÔÏÎËÏÓÔÑÈ ÒÁÂÏÔÙ CVSup.</p>
 
-	    <p><a href="&url.ru.articles;/dialup-firewall/index.html">
-	      éÓÐÏÌØÚÏ×ÁÎÉÅ ÍÅÖÓÅÔÅ×ÏÇÏ ÜËÒÁÎÁ ×Ï FreeBSD ÐÒÉ ÒÁÂÏÔÅ ÐÏ ËÏÍÍÕÔÉÒÕÅÍÏÊ
-	      ÌÉÎÉÉ Ó×ÑÚÉ</a> (dialup-firewall)<br/>
-	      ï ÔÏÍ, ËÁË ÎÁÓÔÒÏÉÔØ ÍÅÖÓÅÔÅ×ÏÊ ÜËÒÁÎ ÐÒÉ ÐÏÍÏÝÉ PPP É ipfw ×
-	      ÓÌÕÞÁÅ ÒÁÂÏÔÙ ÐÏ ËÏÍÍÕÔÉÒÕÅÍÏÍÕ ËÁÎÁÌÕ Ó×ÑÚÉ Ó ÄÉÎÁÍÉÞÅÓËÉ ÎÁÚÎÁÞÁÅÍÙÍÉ
-	      IP-ÁÄÒÅÓÁÍÉ.</p>
-
-	    <p><a href="&url.ru.articles;/diskless-x/index.html">óÏÚÄÁÎÉÅ
-	      ÂÅÚÄÉÓËÏ×ÏÇÏ X ÓÅÒ×ÅÒÁ</a> (diskless-x)<br/>
-	      ï ÔÏÍ, ËÁË ÓÏÚÄÁÔØ ÂÅÚÄÉÓËÏ×ÙÊ X ÓÅÒ×ÅÒ.</p>
-
-	    <p><a href="&url.ru.articles;/euro/article.html">óÉÍ×ÏÌ å×ÒÏ
-	      ×Ï FreeBSD</a> (euro)<br/>
-	      ëÁË ÎÁÓÔÒÏÉÔØ FreeBSD É ÓÏÏÔ×ÅÔÓÔ×ÕÀÝÉÅ ÐÒÉÌÏÖÅÎÉÑ ÄÌÑ
-	      ×Ù×ÏÄÁ ÓÉÍ×ÏÌÁ å×ÒÏ.</p>
-
 	    <p><a href="&url.ru.articles;/explaining-bsd/index.html">
 	      ïÂßÑÓÎÅÎÉÅ BSD</a> (explaining-bsd)<br/>
 	      ïÔ×ÅÔ ÎÁ ×ÏÐÒÏÓ ``þÔÏ ÔÁËÏÅ BSD?''</p>
@@ -196,22 +168,12 @@
 	      ïÐÉÓÁÎÉÅ ÒÁÚÌÉÞÎÙÈ ÔÅÈÎÏÌÏÇÉÊ ÒÁÂÏÔÙ ÓÏ ÛÒÉÆÔÁÍÉ ×Ï FreeBSD, É Ï
 	      ÔÏÍ, ËÁË ÉÓÐÏÌØÚÏ×ÁÔØ ÉÈ × ÒÁÚÌÉÞÎÙÈ ÐÒÏÇÒÁÍÍÁÈ.</p>
 
-	    <p><a href="&url.ru.articles;/formatting-media/index.html">
-	      æÏÒÍÁÔÉÒÏ×ÁÎÉÅ ÎÏÓÉÔÅÌÅÊ ×Ï FreeBSD</a> (formatting-media)<br/>
-	      ëÁË ÒÁÚÂÉÔØ ÎÁ ÓÌÁÊÓÙ, ÒÁÚÄÅÌÙ É ÏÔÆÏÒÍÁÔÉÒÏ×ÁÔØ ÎÅÓßÅÍÎÙÅ É
-	      ÓßÅÍÎÙÅ ÎÏÓÉÔÅÌÉ ×Ï FreeBSD.</p>
-
 	    <p><a href="&url.ru.articles;/freebsd-questions/index.html">
 	      ëÁË ÒÁÂÏÔÁÔØ ÓÏ ÓÐÉÓËÏÍ ÒÁÓÓÙÌËÉ FreeBSD-questions c ÍÁËÓÉÍÁÌØÎÏÊ
 	      ÏÔÄÁÞÅÊ</a> (freebsd-questions)<br/>
 	      óÏ×ÅÔÙ É ÒÅËÏÍÅÎÄÁÃÉÉ, ËÏÔÏÒÙÅ ÐÏÍÏÇÕÔ ×ÁÍ Õ×ÅÌÉÞÉÔØ ÛÁÎÓ ÎÁ
 	      ÐÏÌÕÞÅÎÉÅ ÐÏÌÅÚÎÏÊ ÉÎÆÏÒÍÁÃÉÉ ÉÚ ÓÐÉÓËÁ ÒÁÓÓÙÌËÉ -questions.</p>
 
-	    <p><a href="&url.ru.articles;/hats/index.html">òÁÂÏÔÁ Ó
-	      Hats</a> (hats)<br/>
-	      òÕËÏ×ÏÄÓÔ×Ï ÄÌÑ ËÏÍÍÉÔÔÅÒÏ× ÐÏ ÒÁÂÏÔÅ Ó ``hats'' (ÄÒÕÇÉÍÉ
-	      ËÏÍÍÉÔÔÅÒÁÍÉ, ×ÏÚÇÌÁ×ÌÑÀÝÉÍÉ ÏÔÄÅÌØÎÙÅ ÏÂÌÁÓÔÉ FreeBSD).</p>
-
 	    <p><a href="&url.ru.articles;/hubs/index.html">úÅÒËÁÌÉÒÏ×ÁÎÉÅ FreeBSD</a>
 	      (hubs)<br/>
 	      (÷ÓÅ Ï ÚÅÒËÁÌÉÒÏ×ÁÎÉÉ Web-ÓÁÊÔÁ FreeBSD, ÓÅÒ×ÅÒÏ×
@@ -240,11 +202,6 @@
 	      ÷×ÏÄÎÏÅ ÒÕËÏ×ÏÄÓÔ×Ï ÐÏ ÉÓÐÏÌØÚÏ×ÁÎÉÀ ÐÏÞÔÏ×ÏÇÏ ËÌÉÅÎÔÁ MH
 	      ×Ï FreeBSD.</p>
 
-	    <p><a href="&url.ru.articles;/multi-os/index.html">
-	      éÓÐÏÌØÚÏ×ÁÎÉÅ FreeBSD Ó ÄÒÕÇÉÍÉ ÏÐÅÒÁÃÉÏÎÎÙÍÉ ÓÉÓÔÅÍÁÍÉ</a> (multi-os)<br/>
-	      ëÁË ÕÓÔÁÎÏ×ÉÔØ FreeBSD ×ÍÅÓÔÅ Ó ÏÄÎÏÊ ÉÌÉ ÎÅÓËÏÌØËÉÍÉ ÒÁÚÌÉÞÎÙÍÉ
-	      ÏÐÅÒÁÃÉÏÎÎÙÍÉ ÓÉÓÔÅÍÁÍÉ ÎÁ ÏÄÉÎ É ÔÏÔ ÖÅ ËÏÍÐØÀÔÅÒ.</p>
-
 	    <p><a href="&url.articles;/nanobsd/index.html">NanoBSD</a><br/>
 	      éÎÆÏÒÍÁÃÉÑ Ï ÉÎÓÔÒÕÍÅÎÔÁÈ NanoBSD, ËÏÔÏÒÙÅ ÍÏÇÕÔ ÂÙÔØ ÉÓÐÏÌØÚÏ×ÁÎÙ
 	      ÐÒÉ ÓÏÚÄÁÎÉÉ ÏÂÒÁÚÏ× ÓÉÓÔÅÍÙ FreeBSD ÄÌÑ ×ÓÔÒÏÅÎÎÙÈ ÐÒÉÌÏÖÅÎÉÊ,
@@ -330,33 +287,11 @@
 	      éÓÐÏÌØÚÏ×ÁÎÉÅ Ô×ÅÒÄÏÔÅÌØÎÙÈ ÄÉÓËÏ×ÙÈ ÕÓÔÒÏÊÓÔ× ×Ï
 	      FreeBSD.</p>
 
-	    <p><a href="&url.articles;/storage-devices/index.html">
-	      õÓÔÒÏÊÓÔ×Á ÈÒÁÎÅÎÉÑ ÉÎÆÏÒÍÁÃÉÉ</a> (storage-devices)<br/>
-	      ðÏÄÒÏÂÎÁÑ ÉÎÆÏÒÍÁÃÉÑ Ï ÉÓÐÏÌØÚÏ×ÁÎÉÉ ÕÓÔÒÏÊÓÔ× ÈÒÁÎÅÎÉÑ
- 	      ×Ï FreeBSD, ×ËÌÀÞÁÑ ÄÉÓËÉ ESDI, SCSI, ÓÔÒÉÍÅÒÙ É ÐÒÉ×ÏÄÙ
-	      ËÏÍÐÁËÔ-ÄÉÓËÏ×.</p>
-
-	    <p><a href="&url.ru.articles;/version-guide/index.html">÷ÙÂÏÒ ÐÏÄÈÏÄÑÝÅÊ
-	      ÄÌÑ ×ÁÓ ×ÅÒÓÉÉ FreeBSD</a> (version-guide)<br/>
-	      ëÁË ×ÙÂÒÁÔØ, ËÁËÁÑ ÉÚ ×ÅÒÓÉÊ FreeBSD ÐÏÄÈÏÄÉÔ ×ÁÍ ÂÏÌÅÅ ×ÓÅÇÏ?
-	      òÁÓÓÍÁÔÒÉ×ÁÅÍÙÅ ÔÅÍÙ ×ËÌÀÞÁÀÔ × ÓÅÂÑ ÒÅÌÉÚÙ, ×ÅÔ×É, ÒÁÚÌÉÞÉÑ ÍÅÖÄÕ -CURRENT É
-	      -STABLE, Á ÔÁËÖÅ ÔÅËÕÝÉÅ ÃÅÌÉ × ÐÌÁÎÉÒÏ×ÁÎÉÉ ÒÅÌÉÚÏ×.</p>
-
-	    <p><a href="&url.articles;/vinum/index.html">îÁÞÁÌØÎÙÊ ÚÁÐÕÓË
-	      vinum: ïÓÎÏ×Á ÎÁÄ£ÖÎÙÈ ÓÅÒ×ÅÒÏ×</a> (vinum)<br/>
-	      íÑÇËÏÅ ××ÅÄÅÎÉÅ × ÓÐÅÃÉÆÉËÕ ÒÁÂÏÔÙ ÓÅÒ×ÅÒÏ×, ÕÓÔÏÊÞÉ×ÙÈ Ë ÓÂÏÑÍ É
-	      ÐÏÛÁÇÏ×ÙÅ ÉÎÓÔÒÕËÃÉÉ ÐÏ ÉÈ ÐÏÓÔÒÏÅÎÉÀ ÐÒÉ ÐÏÍÏÝÉ Vinum.</p>
-
 	    <p><a href="&url.ru.articles;/vm-design/index.html">üÌÅÍÅÎÔÙ
 	      ÁÒÈÉÔÅËÔÕÒÙ ÓÉÓÔÅÍÙ ×ÉÒÔÕÁÌØÎÏÊ ÐÁÍÑÔÉ ×Ï FreeBSD</a> (vm-design)<br/>
 	      ðÏÎÑÔÎÏÅ É ÐÒÏÓÔÏÅ ÏÐÉÓÁÎÉÅ ÁÒÈÉÔÅËÔÕÒÙ ÐÏÄÓÉÓÔÅÍÙ ÕÐÒÁ×ÌÅÎÉÑ
 	      ×ÉÒÔÕÁÌØÎÏÊ ÐÁÍÑÔØÀ FreeBSD.</p>
 
-	    <p><a href="&url.ru.articles;/zip-drive/index.html">õÓÔÒÏÊÓÔ×Á
-	      Zip É FreeBSD</a> (zip-drive)<br/>
-	      ëÁË ÏÔÆÏÒÍÁÔÉÒÏ×ÁÔØ, ÓÍÏÎÔÉÒÏ×ÁÔØ É ÒÁÂÏÔÁÔØ Ó ÕÓÔÒÏÊÓÔ×ÁÍÉ
-	      Iomega Zip (SCSI, IDE É ÎÁ ÐÁÒÁÌÌÅÌØÎÏÍ ÐÏÒÔÕ) ×Ï FreeBSD.</p>
-
   <h2>îÁ ÄÒÕÇÉÈ ÓÁÊÔÁÈ</h2>
 
   <p>÷ ÒÅÚÕÌØÔÁÔÅ ÎÅÚÁ×ÉÓÉÍÙÈ ÕÓÉÌÉÊ ÂÙÌÏ ÓÏÚÄÁÎÏ ÍÎÏÇÏ ÚÁÓÌÕÖÉ×ÁÀÝÉÈ ×ÎÉÍÁÎÉÑ
diff --git a/ru_RU.KOI8-R/htdocs/news/2000/index.sgml b/ru_RU.KOI8-R/htdocs/news/2000/index.sgml
index 8f14edcabf..c0bed9edb5 100644
--- a/ru_RU.KOI8-R/htdocs/news/2000/index.sgml
+++ b/ru_RU.KOI8-R/htdocs/news/2000/index.sgml
@@ -273,7 +273,7 @@
       href="http://www.jp.FreeBSD.org/">http://www.jp.FreeBSD.org/</a>.</p>
 
       <p>ðÏÑ×ÉÌÁÓØ ÎÏ×ÁÑ ÓÔÁÔØÑ, ÏÐÉÓÙ×ÁÀÝÁÑ <a
-      href="&base;/../tutorials/dialup-firewall/index.html">ÉÓÐÏÌØÚÏ×ÁÎÉÅ PPP,
+      href="http://docs.freebsd.org/doc/9.0-RELEASE/usr/share/doc/freebsd/en_US.ISO8859-1/articles/dialup-firewall/index.html">ÉÓÐÏÌØÚÏ×ÁÎÉÅ PPP,
       natd É ipfw</a> ÄÌÑ ÒÅÁÌÉÚÁÃÉÉ ÍÅÖÓÅÔÅ×ÏÇÏ ÜËÒÁÎÁ ÞÅÒÅÚ ËÏÍÍÕÔÉÒÕÅÍÏÅ
       ÓÏÅÄÉÎÅÎÉÅ ÐÏ ÐÒÏÔÏËÏÌÕ PPP.</p>
 
diff --git a/ru_RU.KOI8-R/htdocs/news/2001/news.xml b/ru_RU.KOI8-R/htdocs/news/2001/news.xml
index f0ec6805ef..cb0eef058f 100644
--- a/ru_RU.KOI8-R/htdocs/news/2001/news.xml
+++ b/ru_RU.KOI8-R/htdocs/news/2001/news.xml
@@ -299,7 +299,7 @@
 
 	  <p><a href="mailto:Bob@BGPBook.Com">Bob Van Valzah</a> ÐÒÅÄÏÓÔÁ×ÉÌ
 	    ÓÔÁÔØÀ ÐÒÅÄÓÔÁ×ÌÑÀÝÕÀ <a
-	    href="$base/doc/en_US.ISO8859-1/articles/vinum/index.html">
+	    href="http://docs.freebsd.org/doc/9.0-RELEASE/usr/share/doc/freebsd/en_US.ISO8859-1/articles/vinum/index.html">
 	    ÏÛÉÂËÏ-ÚÁÝÉÝÅÎÎÙÈ ÓÅÒ×ÅÒÁ É ÐÏÛÁÇÏ×ÙÅ ÉÎÓÔÒÕËÃÉÉ ÄÌÑ
             ÓÏÚÄÁÎÉÑ ÔÁËÏ×ÏÇÏ Ó ÉÓÐÏÌØÚÏ×ÁÎÉÅÍ Vinum</a>.</p>
 	</event>
diff --git a/ru_RU.KOI8-R/htdocs/news/2002/news.xml b/ru_RU.KOI8-R/htdocs/news/2002/news.xml
index 11758fe9c2..3214f7a94c 100644
--- a/ru_RU.KOI8-R/htdocs/news/2002/news.xml
+++ b/ru_RU.KOI8-R/htdocs/news/2002/news.xml
@@ -817,7 +817,7 @@
 
           <p>Aaron Kaplan ÐÒÅÄÏÓÔÁ×ÉÌ ÎÏ×ÕÀ ÓÔÁÔØÀ, ÏÐÉÓÙ×ÁÀÝÕÀ, ËÁË ÉÚÍÅÎÉÔØ
             ËÏÎÆÉÇÕÒÁÃÉÀ ×ÁÛÅÊ ÓÉÓÔÅÍÙ ÄÌÑ ÉÓÐÏÌØÚÏ×ÁÎÉÑ ÎÏ×ÏÇÏ <a
-            href="../../doc/ru_RU.KOI8-R/articles/euro/article.html">
+            href="http://docs.freebsd.org/doc/9.0-RELEASE/usr/share/doc/freebsd/ru_RU.KOI8-R/articles/euro/index.html">
             ÓÉÍ×ÏÌÁ å×ÒÏ ×Ï FreeBSD</a>.</p>
         </event>
       </day>
diff --git a/ru_RU.KOI8-R/htdocs/releng/index.sgml b/ru_RU.KOI8-R/htdocs/releng/index.sgml
index 1732828827..0f9fd7e054 100644
--- a/ru_RU.KOI8-R/htdocs/releng/index.sgml
+++ b/ru_RU.KOI8-R/htdocs/releng/index.sgml
@@ -436,24 +436,6 @@
 	    FreeBSD.org, ËÁË ÓËÏÎÆÉÇÕÒÉÒÏ×ÁÔØ ÌÀÂÏÊ ÎÁÂÏÒ ÍÁÛÉÎ ÐÏÄ ËÌÁÓÔÅÒ
 	    ÐÏÒÔÏ×, ËÁË ÒÁÚÂÉÔØ ÐÁËÅÔÙ ÎÁ ÎÏÓÉÔÅÌÉ ÄÌÑ ÒÅÌÉÚÁ É ËÁË
 	    ÐÒÏ×ÅÒÉÔØ ÃÅÌÏÓÔÎÏÓÔØ ÎÁÂÏÒÁ ÐÁËÅÔÏ×.</small></p></li>
-
-    <li><p><a
-	  href="&enbase;/doc/ru_RU.KOI8-R/articles/5-roadmap/index.html">
-	  îÁÐÒÁ×ÌÅÎÉÑ ÒÁÂÏÔ × FreeBSD 5-STABLE</a><br/>
-
-	  <small>ïÐÉÓÙ×ÁÅÔ ÎÁÐÒÁ×ÌÅÎÉÅ ÒÁÚ×ÉÔÉÑ ÐÒÏÅËÔÁ ÄÌÑ ÄÏÓÔÉÖÅÎÉÑ ×ÅÔËÉ
-	    RELENG_5.  ÷ËÌÀÞÁÅÔ ÏÂÝÅÅ ÓÏÓÔÏÑÎÉÅ 5.x, ÞÔÏ ÏÓÔÁÌÏÓØ ÓÄÅÌÁÔØ É
-	    ÐÒÉÍÅÒÎÙÊ ÐÌÁÎ ÒÁÂÏÔ.  éÍÅÊÔÅ × ×ÉÄÕ, ÞÔÏ ÎÁ ÔÅËÕÝÉÊ ÍÏÍÅÎÔ
-	    ÄÁÎÎÙÊ ÄÏËÕÍÅÎÔ ÐÒÅÄÓÔÁ×ÌÑÅÔ ÐÏ ÂÏÌØÛÅÊ ÞÁÓÔÉ ÉÓÔÏÒÉÞÅÓËÕÀ
-	    ÃÅÎÎÏÓÔØ.</small></p></li>
-    <li><p><a
-	  href="&enbase;/doc/ru_RU.KOI8-R/articles/version-guide/index.html">
-	  ÷ÙÂÏÒ ÐÏÄÈÏÄÑÝÅÊ ÄÌÑ ×ÁÓ ×ÅÒÓÉÉ FreeBSD</a><br/>
-
-	  <small>ëÁË ÒÅÛÉÔØ, ËÁËÁÑ ×ÅÒÓÉÑ FreeBSD ÂÏÌØÛÅ ×ÓÅÇÏ ÐÏÄÈÏÄÉÔ
-	    ÄÌÑ ×ÁÛÉÈ ÎÕÖÄ.  ôÅÍÙ ×ËÌÀÞÁÀÔ × ÓÅÂÑ ÒÅÌÉÚÙ, ×ÅÔËÉ, ÒÁÚÌÉÞÉÅ
-	    ÍÅÖÄÕ -CURRENT É -STABLE É ÔÅËÕÝÉÅ ÐÌÁÎÉÒÕÅÍÙÅ ÃÅÌÉ
-	    ÐÒÏÅËÔÁ.</small></p></li>
   </ul>
 
   <h2><a name="team" id="team">ëÏÍÁÎÄÁ ÐÏÄÇÏÔÏ×ËÉ ÒÅÌÉÚÏ×</a></h2>
diff --git a/ru_RU.KOI8-R/share/sgml/urls.ent b/ru_RU.KOI8-R/share/sgml/urls.ent
index 24013c98dc..1b8de516d6 100644
--- a/ru_RU.KOI8-R/share/sgml/urls.ent
+++ b/ru_RU.KOI8-R/share/sgml/urls.ent
@@ -22,5 +22,3 @@
 <!ENTITY url.articles.contributors	"&url.articles.contributors.en;">
 <!ENTITY url.articles.filtering-bridges	"&url.articles.filtering-bridges.en;">
 <!ENTITY url.articles.serial-uart	"&url.articles.serial-uart.en;">
-<!ENTITY url.articles.storage-devices	"&url.articles.storage-devices.en;">
-<!ENTITY url.articles.vinum		"&url.articles.vinum.en;">
diff --git a/share/images/articles/checkpoint/networks.pic b/share/images/articles/checkpoint/networks.pic
deleted file mode 100644
index a8de40066a..0000000000
--- a/share/images/articles/checkpoint/networks.pic
+++ /dev/null
@@ -1,30 +0,0 @@
-.\" $FreeBSD$
-.\"
-.PS
-
-A: box "Firewall-1" right;
-B: line 1.4;
-C: box "Internet" dashed;
-D: line 1.4;
-E: box "FreeBSD  GW" wid 1.0;
-
-F: line down at A.s;
-G: box ht .04 wid 1.8 fill \
-   with .nw at F.s - (.4,0);
-
-H: line down at E.s;
-I: box ht .04 wid 1.8 fill \
-   with .ne at H.s + (.4,0);
-
-box ht .2 invis "\fC\s-2 208.229.100.6\s+2\fP" \
-    with .sw at B.nw + (.06,0);
-box ht .2 invis "\fC\s-2 216.218.197.2\s+2\fP" \
-    with .se at D.e - (.12,0);
-box wid 1.2 invis \
-    "\fC\s-2199.208.192.0/24\s+2\fP" "FW-1 protected nets" \
-    with .nw at G.w;
-box wid 1.2 invis \
-    "\fC\s-2192.168.10.0/24\s+2\fP" "internal nets" \
-    with .ne at I.e;
-
-.PE
diff --git a/share/images/articles/vinum/ad0b4aft.eps b/share/images/articles/vinum/ad0b4aft.eps
deleted file mode 100644
index c7cb4cc979..0000000000
--- a/share/images/articles/vinum/ad0b4aft.eps
+++ /dev/null
@@ -1,626 +0,0 @@
-%!PS-Adobe-2.0 EPSF-2.0
-%%Title: Untitled-2
-%%Creator: Dia v0.88.1
-%%CreationDate: Fri Oct 12 17:22:15 2001
-%%For: murray
-%%Magnification: 1.0000
-%%Orientation: Portrait
-%%BoundingBox: 0 0 311 173
-%%Pages: 1
-%%BeginSetup
-%%EndSetup
-%%EndComments
-%%BeginProlog
-[ /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef
-/.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef
-/.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef
-/.notdef /.notdef /space /exclam /quotedbl /numbersign /dollar /percent /ampersand /quoteright
-/parenleft /parenright /asterisk /plus /comma /hyphen /period /slash /zero /one
-/two /three /four /five /six /seven /eight /nine /colon /semicolon
-/less /equal /greater /question /at /A /B /C /D /E
-/F /G /H /I /J /K /L /M /N /O
-/P /Q /R /S /T /U /V /W /X /Y
-/Z /bracketleft /backslash /bracketright /asciicircum /underscore /quoteleft /a /b /c
-/d /e /f /g /h /i /j /k /l /m
-/n /o /p /q /r /s /t /u /v /w
-/x /y /z /braceleft /bar /braceright /asciitilde /.notdef /.notdef /.notdef
-/.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef
-/.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef
-/.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef
-/space /exclamdown /cent /sterling /currency /yen /brokenbar /section /dieresis /copyright
-/ordfeminine /guillemotleft /logicalnot /hyphen /registered /macron /degree /plusminus /twosuperior /threesuperior
-/acute /mu /paragraph /periodcentered /cedilla /onesuperior /ordmasculine /guillemotright /onequarter /onehalf
-/threequarters /questiondown /Agrave /Aacute /Acircumflex /Atilde /Adieresis /Aring /AE /Ccedilla
-/Egrave /Eacute /Ecircumflex /Edieresis /Igrave /Iacute /Icircumflex /Idieresis /Eth /Ntilde
-/Ograve /Oacute /Ocircumflex /Otilde /Odieresis /multiply /Oslash /Ugrave /Uacute /Ucircumflex
-/Udieresis /Yacute /Thorn /germandbls /agrave /aacute /acircumflex /atilde /adieresis /aring
-/ae /ccedilla /egrave /eacute /ecircumflex /edieresis /igrave /iacute /icircumflex /idieresis
-/eth /ntilde /ograve /oacute /ocircumflex /otilde /odieresis /divide /oslash /ugrave
-/uacute /ucircumflex /udieresis /yacute /thorn /ydieresis] /isolatin1encoding exch def
-/Times-Roman-latin1
-    /Times-Roman findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Times-Italic-latin1
-    /Times-Italic findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Times-Bold-latin1
-    /Times-Bold findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Times-BoldItalic-latin1
-    /Times-BoldItalic findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/AvantGarde-Book-latin1
-    /AvantGarde-Book findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/AvantGarde-BookOblique-latin1
-    /AvantGarde-BookOblique findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/AvantGarde-Demi-latin1
-    /AvantGarde-Demi findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/AvantGarde-DemiOblique-latin1
-    /AvantGarde-DemiOblique findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Bookman-Light-latin1
-    /Bookman-Light findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Bookman-LightItalic-latin1
-    /Bookman-LightItalic findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Bookman-Demi-latin1
-    /Bookman-Demi findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Bookman-DemiItalic-latin1
-    /Bookman-DemiItalic findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Courier-latin1
-    /Courier findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Courier-Oblique-latin1
-    /Courier-Oblique findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Courier-Bold-latin1
-    /Courier-Bold findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Courier-BoldOblique-latin1
-    /Courier-BoldOblique findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Helvetica-latin1
-    /Helvetica findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Helvetica-Oblique-latin1
-    /Helvetica-Oblique findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Helvetica-Bold-latin1
-    /Helvetica-Bold findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Helvetica-BoldOblique-latin1
-    /Helvetica-BoldOblique findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Helvetica-Narrow-latin1
-    /Helvetica-Narrow findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Helvetica-Narrow-Oblique-latin1
-    /Helvetica-Narrow-Oblique findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Helvetica-Narrow-Bold-latin1
-    /Helvetica-Narrow-Bold findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Helvetica-Narrow-BoldOblique-latin1
-    /Helvetica-Narrow-BoldOblique findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/NewCenturySchoolbook-Roman-latin1
-    /NewCenturySchoolbook-Roman findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/NewCenturySchoolbook-Italic-latin1
-    /NewCenturySchoolbook-Italic findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/NewCenturySchoolbook-Bold-latin1
-    /NewCenturySchoolbook-Bold findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/NewCenturySchoolbook-BoldItalic-latin1
-    /NewCenturySchoolbook-BoldItalic findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Palatino-Roman-latin1
-    /Palatino-Roman findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Palatino-Italic-latin1
-    /Palatino-Italic findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Palatino-Bold-latin1
-    /Palatino-Bold findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Palatino-BoldItalic-latin1
-    /Palatino-BoldItalic findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Symbol-latin1
-    /Symbol findfont
-definefont pop
-/ZapfChancery-MediumItalic-latin1
-    /ZapfChancery-MediumItalic findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/ZapfDingbats-latin1
-    /ZapfDingbats findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/cp {closepath} bind def
-/c {curveto} bind def
-/f {fill} bind def
-/a {arc} bind def
-/ef {eofill} bind def
-/ex {exch} bind def
-/gr {grestore} bind def
-/gs {gsave} bind def
-/sa {save} bind def
-/rs {restore} bind def
-/l {lineto} bind def
-/m {moveto} bind def
-/rm {rmoveto} bind def
-/n {newpath} bind def
-/s {stroke} bind def
-/sh {show} bind def
-/slc {setlinecap} bind def
-/slj {setlinejoin} bind def
-/slw {setlinewidth} bind def
-/srgb {setrgbcolor} bind def
-/rot {rotate} bind def
-/sc {scale} bind def
-/sd {setdash} bind def
-/ff {findfont} bind def
-/sf {setfont} bind def
-/scf {scalefont} bind def
-/sw {stringwidth pop} bind def
-/tr {translate} bind def
-
-/ellipsedict 8 dict def
-ellipsedict /mtrx matrix put
-/ellipse
-{ ellipsedict begin
-   /endangle exch def
-   /startangle exch def
-   /yrad exch def
-   /xrad exch def
-   /y exch def
-   /x exch def   /savematrix mtrx currentmatrix def
-   x y tr xrad yrad sc
-   0 0 1 startangle endangle arc
-   savematrix setmatrix
-   end
-} def
-
-/mergeprocs {
-dup length
-3 -1 roll
-dup
-length
-dup
-5 1 roll
-3 -1 roll
-add
-array cvx
-dup
-3 -1 roll
-0 exch
-putinterval
-dup
-4 2 roll
-putinterval
-} bind def
-28.346000 -28.346000 scale
--2.500000 -8.079412 translate
-%%EndProlog
-
-
-1.000000 1.000000 1.000000 srgb
-n 2.627195 2.617647 m 2.627195 7.617647 l 6.427195 7.617647 l 6.427195 2.617647 l f
-0.050000 slw
-[] 0 sd
-[] 0 sd
-0 slj
-0.000000 0.000000 0.000000 srgb
-n 2.627195 2.617647 m 2.627195 7.617647 l 6.427195 7.617647 l 6.427195 2.617647 l cp s
-1.000000 1.000000 1.000000 srgb
-n 9.627195 2.617647 m 9.627195 7.617647 l 13.427195 7.617647 l 13.427195 2.617647 l f
-0.050000 slw
-[] 0 sd
-[] 0 sd
-0 slj
-0.000000 0.000000 0.000000 srgb
-n 9.627195 2.617647 m 9.627195 7.617647 l 13.427195 7.617647 l 13.427195 2.617647 l cp s
-0.050000 slw
-[] 0 sd
-[] 0 sd
-0 slc
-n 13.427195 3.617647 m 9.627195 3.617647 l s
-0.050000 slw
-[] 0 sd
-[] 0 sd
-0 slc
-n 13.427195 4.617647 m 9.627195 4.617647 l s
-/Times-Bold-latin1 ff 0.400000 scf sf
-(ad0 Before Vinum) dup sw 2 div 4.527195 ex sub 2.317647 m gs 1 -1 sc sh gr
-/Times-Bold-latin1 ff 0.400000 scf sf
-(ad0 After Vinum) dup sw 2 div 11.527195 ex sub 2.317647 m gs 1 -1 sc sh gr
-/Times-Roman-latin1 ff 0.400000 scf sf
-(root) dup sw 2 div 11.602195 ex sub 2.942647 m gs 1 -1 sc sh gr
-/Times-Roman-latin1 ff 0.400000 scf sf
-(swap) dup sw 2 div 11.527195 ex sub 4.017647 m gs 1 -1 sc sh gr
-/Times-Roman-latin1 ff 0.350000 scf sf
-(Vinum drive YouCrazy) dup sw 2 div 11.527195 ex sub 5.017647 m gs 1 -1 sc sh gr
-/Times-Roman-latin1 ff 0.400000 scf sf
-(root) dup sw 2 div 4.527195 ex sub 3.017647 m gs 1 -1 sc sh gr
-/Times-Roman-latin1 ff 0.400000 scf sf
-(swap) dup sw 2 div 4.527195 ex sub 4.017647 m gs 1 -1 sc sh gr
-/Times-Roman-latin1 ff 0.400000 scf sf
-(/home) dup sw 2 div 4.527195 ex sub 6.017647 m gs 1 -1 sc sh gr
-/Times-Bold-latin1 ff 0.400000 scf sf
-(Offset \(blocks\)) dup sw 2 div 8.127195 ex sub 2.317647 m gs 1 -1 sc sh gr
-/Times-Roman-latin1 ff 0.300000 scf sf
-(\(not to scale\)) dup sw 2 div 3.427195 ex sub 8.017647 m gs 1 -1 sc sh gr
-/Courier-Bold-latin1 ff 0.400000 scf sf
-(/dev/ad0s1a) dup sw 2 div 11.527195 ex sub 3.417647 m gs 1 -1 sc sh gr
-/Courier-Bold-latin1 ff 0.400000 scf sf
-(/dev/ad0s1b) dup sw 2 div 11.527195 ex sub 4.417647 m gs 1 -1 sc sh gr
-/Courier-Bold-latin1 ff 0.400000 scf sf
-(/dev/ad0s1h) dup sw 2 div 11.527195 ex sub 5.417647 m gs 1 -1 sc sh gr
-/Courier-Bold-latin1 ff 0.400000 scf sf
-(/dev/ad0s1a) dup sw 2 div 4.527195 ex sub 3.417647 m gs 1 -1 sc sh gr
-/Courier-Bold-latin1 ff 0.400000 scf sf
-(/dev/ad0s1b) dup sw 2 div 4.527195 ex sub 4.417647 m gs 1 -1 sc sh gr
-/Courier-Bold-latin1 ff 0.400000 scf sf
-(/dev/ad0s1e) dup sw 2 div 4.527195 ex sub 6.417647 m gs 1 -1 sc sh gr
-/Courier-Bold-latin1 ff 0.400000 scf sf
-() dup sw 2 div 11.927195 ex sub 7.817647 m gs 1 -1 sc sh gr
-1.000000 1.000000 1.000000 srgb
-n 9.627195 5.617647 m 9.627195 6.617647 l 12.227195 6.617647 l 12.227195 5.617647 l f
-0.050000 slw
-[] 0 sd
-[] 0 sd
-0 slj
-0.000000 0.000000 0.000000 srgb
-n 9.627195 5.617647 m 9.627195 6.617647 l 12.227195 6.617647 l 12.227195 5.617647 l cp s
-1.000000 1.000000 1.000000 srgb
-n 9.627195 6.617647 m 9.627195 7.617647 l 12.227195 7.617647 l 12.227195 6.617647 l f
-0.050000 slw
-[] 0 sd
-[] 0 sd
-0 slj
-0.000000 0.000000 0.000000 srgb
-n 9.627195 6.617647 m 9.627195 7.617647 l 12.227195 7.617647 l 12.227195 6.617647 l cp s
-/Courier-Bold-latin1 ff 0.400000 scf sf
-(usr.p0.s0) dup sw 2 div 10.927195 ex sub 7.417647 m gs 1 -1 sc sh gr
-/Times-Roman-latin1 ff 0.400000 scf sf
-(Vinum sd) dup sw 2 div 10.927195 ex sub 7.017647 m gs 1 -1 sc sh gr
-/Courier-Bold-latin1 ff 0.400000 scf sf
-(home.p0.s0) dup sw 2 div 10.927195 ex sub 6.417647 m gs 1 -1 sc sh gr
-/Times-Roman-latin1 ff 0.400000 scf sf
-(Vinum sd) dup sw 2 div 10.927195 ex sub 6.017647 m gs 1 -1 sc sh gr
-0.020000 slw
-[] 0 sd
-[] 0 sd
-0 slc
-n 9.027195 7.617647 m 9.427195 7.617647 l s
-0 slj
-1.000000 1.000000 1.000000 srgb
-n 9.227195 7.717647 m 9.427195 7.617647 l 9.227195 7.517647 l f
-0.020000 slw
-[] 0 sd
-0 slj
-0.000000 0.000000 0.000000 srgb
-n 9.227195 7.717647 m 9.427195 7.617647 l 9.227195 7.517647 l cp s
-0.020000 slw
-[] 0 sd
-[] 0 sd
-0 slc
-n 9.027195 6.617647 m 9.427195 6.617647 l s
-0 slj
-1.000000 1.000000 1.000000 srgb
-n 9.227195 6.717647 m 9.427195 6.617647 l 9.227195 6.517647 l f
-0.020000 slw
-[] 0 sd
-0 slj
-0.000000 0.000000 0.000000 srgb
-n 9.227195 6.717647 m 9.427195 6.617647 l 9.227195 6.517647 l cp s
-0.020000 slw
-[] 0 sd
-[] 0 sd
-0 slc
-n 9.027195 5.617647 m 9.427195 5.617647 l s
-0 slj
-1.000000 1.000000 1.000000 srgb
-n 9.227195 5.717647 m 9.427195 5.617647 l 9.227195 5.517647 l f
-0.020000 slw
-[] 0 sd
-0 slj
-0.000000 0.000000 0.000000 srgb
-n 9.227195 5.717647 m 9.427195 5.617647 l 9.227195 5.517647 l cp s
-0.020000 slw
-[] 0 sd
-[] 0 sd
-0 slc
-n 9.027195 4.617647 m 9.427195 4.617647 l s
-0 slj
-1.000000 1.000000 1.000000 srgb
-n 9.227195 4.717647 m 9.427195 4.617647 l 9.227195 4.517647 l f
-0.020000 slw
-[] 0 sd
-0 slj
-0.000000 0.000000 0.000000 srgb
-n 9.227195 4.717647 m 9.427195 4.617647 l 9.227195 4.517647 l cp s
-0.020000 slw
-[] 0 sd
-[] 0 sd
-0 slc
-n 9.027195 3.617647 m 9.427195 3.617647 l s
-0 slj
-1.000000 1.000000 1.000000 srgb
-n 9.227195 3.717647 m 9.427195 3.617647 l 9.227195 3.517647 l f
-0.020000 slw
-[] 0 sd
-0 slj
-0.000000 0.000000 0.000000 srgb
-n 9.227195 3.717647 m 9.427195 3.617647 l 9.227195 3.517647 l cp s
-0.020000 slw
-[] 0 sd
-[] 0 sd
-0 slc
-n 9.027195 2.617647 m 9.427195 2.617647 l s
-0 slj
-1.000000 1.000000 1.000000 srgb
-n 9.227195 2.717647 m 9.427195 2.617647 l 9.227195 2.517647 l f
-0.020000 slw
-[] 0 sd
-0 slj
-0.000000 0.000000 0.000000 srgb
-n 9.227195 2.717647 m 9.427195 2.617647 l 9.227195 2.517647 l cp s
-0.020000 slw
-[] 0 sd
-[] 0 sd
-0 slc
-n 6.627195 2.617647 m 7.027195 2.617647 l s
-0 slj
-1.000000 1.000000 1.000000 srgb
-n 6.827195 2.517647 m 6.627195 2.617647 l 6.827195 2.717647 l f
-0.020000 slw
-[] 0 sd
-0 slj
-0.000000 0.000000 0.000000 srgb
-n 6.827195 2.517647 m 6.627195 2.617647 l 6.827195 2.717647 l cp s
-0.020000 slw
-[] 0 sd
-[] 0 sd
-0 slc
-n 6.627195 3.617647 m 7.027195 3.617647 l s
-0 slj
-1.000000 1.000000 1.000000 srgb
-n 6.827195 3.517647 m 6.627195 3.617647 l 6.827195 3.717647 l f
-0.020000 slw
-[] 0 sd
-0 slj
-0.000000 0.000000 0.000000 srgb
-n 6.827195 3.517647 m 6.627195 3.617647 l 6.827195 3.717647 l cp s
-0.020000 slw
-[] 0 sd
-[] 0 sd
-0 slc
-n 6.627195 4.617647 m 7.027195 4.617647 l s
-0 slj
-1.000000 1.000000 1.000000 srgb
-n 6.827195 4.517647 m 6.627195 4.617647 l 6.827195 4.717647 l f
-0.020000 slw
-[] 0 sd
-0 slj
-0.000000 0.000000 0.000000 srgb
-n 6.827195 4.517647 m 6.627195 4.617647 l 6.827195 4.717647 l cp s
-0.020000 slw
-[] 0 sd
-[] 0 sd
-0 slc
-n 6.627195 5.617647 m 7.027195 5.617647 l s
-0 slj
-1.000000 1.000000 1.000000 srgb
-n 6.827195 5.517647 m 6.627195 5.617647 l 6.827195 5.717647 l f
-0.020000 slw
-[] 0 sd
-0 slj
-0.000000 0.000000 0.000000 srgb
-n 6.827195 5.517647 m 6.627195 5.617647 l 6.827195 5.717647 l cp s
-0.020000 slw
-[] 0 sd
-[] 0 sd
-0 slc
-n 6.627195 6.617647 m 7.027195 6.617647 l s
-0 slj
-1.000000 1.000000 1.000000 srgb
-n 6.827195 6.517647 m 6.627195 6.617647 l 6.827195 6.717647 l f
-0.020000 slw
-[] 0 sd
-0 slj
-0.000000 0.000000 0.000000 srgb
-n 6.827195 6.517647 m 6.627195 6.617647 l 6.827195 6.717647 l cp s
-0.020000 slw
-[] 0 sd
-[] 0 sd
-0 slc
-n 6.627195 7.617647 m 7.027195 7.617647 l s
-0 slj
-1.000000 1.000000 1.000000 srgb
-n 6.827195 7.517647 m 6.627195 7.617647 l 6.827195 7.717647 l f
-0.020000 slw
-[] 0 sd
-0 slj
-0.000000 0.000000 0.000000 srgb
-n 6.827195 7.517647 m 6.627195 7.617647 l 6.827195 7.717647 l cp s
-/Courier-Bold-latin1 ff 0.400000 scf sf
-(0) dup sw 8.827195 ex sub 2.717647 m gs 1 -1 sc sh gr
-/Courier-Bold-latin1 ff 0.400000 scf sf
-(200000) dup sw 8.827195 ex sub 3.717647 m gs 1 -1 sc sh gr
-/Courier-Bold-latin1 ff 0.400000 scf sf
-(400000) dup sw 8.827195 ex sub 4.717647 m gs 1 -1 sc sh gr
-/Courier-Bold-latin1 ff 0.400000 scf sf
-(400265) dup sw 8.827195 ex sub 5.717647 m gs 1 -1 sc sh gr
-/Courier-Bold-latin1 ff 0.400000 scf sf
-(1400265) dup sw 8.827195 ex sub 6.717647 m gs 1 -1 sc sh gr
-/Courier-Bold-latin1 ff 0.400000 scf sf
-(4124673) dup sw 8.827195 ex sub 7.717647 m gs 1 -1 sc sh gr
-/Courier-Bold-latin1 ff 0.400000 scf sf
-() dup sw 2 div 8.427195 ex sub 2.617647 m gs 1 -1 sc sh gr
-/Courier-Bold-latin1 ff 0.400000 scf sf
-() dup sw 2 div 7.927195 ex sub 2.617647 m gs 1 -1 sc sh gr
-/Courier-Bold-latin1 ff 0.400000 scf sf
-() dup sw 2 div 7.927195 ex sub 2.617647 m gs 1 -1 sc sh gr
-0.050000 slw
-[] 0 sd
-[] 0 sd
-0 slc
-n 6.427195 3.617647 m 2.627195 3.617647 l s
-0.050000 slw
-[] 0 sd
-[] 0 sd
-0 slc
-n 6.427195 5.617647 m 2.627195 5.617647 l s
-/Courier-Bold-latin1 ff 0.400000 scf sf
-(/dev/ad0s1f) dup sw 2 div 4.527195 ex sub 7.417647 m gs 1 -1 sc sh gr
-/Times-Roman-latin1 ff 0.400000 scf sf
-(/usr) dup sw 2 div 4.527195 ex sub 7.017647 m gs 1 -1 sc sh gr
-0.050000 slw
-[] 0 sd
-[] 0 sd
-0 slc
-n 6.427195 6.617647 m 2.627195 6.617647 l s
-showpage
diff --git a/share/images/articles/vinum/ad2b4aft.eps b/share/images/articles/vinum/ad2b4aft.eps
deleted file mode 100644
index b118e90ac0..0000000000
--- a/share/images/articles/vinum/ad2b4aft.eps
+++ /dev/null
@@ -1,657 +0,0 @@
-%!PS-Adobe-2.0 EPSF-2.0
-%%Title: Untitled-3
-%%Creator: Dia v0.88.1
-%%CreationDate: Fri Oct 12 17:25:35 2001
-%%For: murray
-%%Magnification: 1.0000
-%%Orientation: Portrait
-%%BoundingBox: 0 0 311 201
-%%Pages: 1
-%%BeginSetup
-%%EndSetup
-%%EndComments
-%%BeginProlog
-[ /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef
-/.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef
-/.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef
-/.notdef /.notdef /space /exclam /quotedbl /numbersign /dollar /percent /ampersand /quoteright
-/parenleft /parenright /asterisk /plus /comma /hyphen /period /slash /zero /one
-/two /three /four /five /six /seven /eight /nine /colon /semicolon
-/less /equal /greater /question /at /A /B /C /D /E
-/F /G /H /I /J /K /L /M /N /O
-/P /Q /R /S /T /U /V /W /X /Y
-/Z /bracketleft /backslash /bracketright /asciicircum /underscore /quoteleft /a /b /c
-/d /e /f /g /h /i /j /k /l /m
-/n /o /p /q /r /s /t /u /v /w
-/x /y /z /braceleft /bar /braceright /asciitilde /.notdef /.notdef /.notdef
-/.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef
-/.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef
-/.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef
-/space /exclamdown /cent /sterling /currency /yen /brokenbar /section /dieresis /copyright
-/ordfeminine /guillemotleft /logicalnot /hyphen /registered /macron /degree /plusminus /twosuperior /threesuperior
-/acute /mu /paragraph /periodcentered /cedilla /onesuperior /ordmasculine /guillemotright /onequarter /onehalf
-/threequarters /questiondown /Agrave /Aacute /Acircumflex /Atilde /Adieresis /Aring /AE /Ccedilla
-/Egrave /Eacute /Ecircumflex /Edieresis /Igrave /Iacute /Icircumflex /Idieresis /Eth /Ntilde
-/Ograve /Oacute /Ocircumflex /Otilde /Odieresis /multiply /Oslash /Ugrave /Uacute /Ucircumflex
-/Udieresis /Yacute /Thorn /germandbls /agrave /aacute /acircumflex /atilde /adieresis /aring
-/ae /ccedilla /egrave /eacute /ecircumflex /edieresis /igrave /iacute /icircumflex /idieresis
-/eth /ntilde /ograve /oacute /ocircumflex /otilde /odieresis /divide /oslash /ugrave
-/uacute /ucircumflex /udieresis /yacute /thorn /ydieresis] /isolatin1encoding exch def
-/Times-Roman-latin1
-    /Times-Roman findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Times-Italic-latin1
-    /Times-Italic findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Times-Bold-latin1
-    /Times-Bold findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Times-BoldItalic-latin1
-    /Times-BoldItalic findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/AvantGarde-Book-latin1
-    /AvantGarde-Book findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/AvantGarde-BookOblique-latin1
-    /AvantGarde-BookOblique findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/AvantGarde-Demi-latin1
-    /AvantGarde-Demi findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/AvantGarde-DemiOblique-latin1
-    /AvantGarde-DemiOblique findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Bookman-Light-latin1
-    /Bookman-Light findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Bookman-LightItalic-latin1
-    /Bookman-LightItalic findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Bookman-Demi-latin1
-    /Bookman-Demi findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Bookman-DemiItalic-latin1
-    /Bookman-DemiItalic findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Courier-latin1
-    /Courier findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Courier-Oblique-latin1
-    /Courier-Oblique findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Courier-Bold-latin1
-    /Courier-Bold findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Courier-BoldOblique-latin1
-    /Courier-BoldOblique findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Helvetica-latin1
-    /Helvetica findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Helvetica-Oblique-latin1
-    /Helvetica-Oblique findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Helvetica-Bold-latin1
-    /Helvetica-Bold findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Helvetica-BoldOblique-latin1
-    /Helvetica-BoldOblique findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Helvetica-Narrow-latin1
-    /Helvetica-Narrow findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Helvetica-Narrow-Oblique-latin1
-    /Helvetica-Narrow-Oblique findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Helvetica-Narrow-Bold-latin1
-    /Helvetica-Narrow-Bold findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Helvetica-Narrow-BoldOblique-latin1
-    /Helvetica-Narrow-BoldOblique findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/NewCenturySchoolbook-Roman-latin1
-    /NewCenturySchoolbook-Roman findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/NewCenturySchoolbook-Italic-latin1
-    /NewCenturySchoolbook-Italic findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/NewCenturySchoolbook-Bold-latin1
-    /NewCenturySchoolbook-Bold findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/NewCenturySchoolbook-BoldItalic-latin1
-    /NewCenturySchoolbook-BoldItalic findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Palatino-Roman-latin1
-    /Palatino-Roman findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Palatino-Italic-latin1
-    /Palatino-Italic findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Palatino-Bold-latin1
-    /Palatino-Bold findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Palatino-BoldItalic-latin1
-    /Palatino-BoldItalic findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Symbol-latin1
-    /Symbol findfont
-definefont pop
-/ZapfChancery-MediumItalic-latin1
-    /ZapfChancery-MediumItalic findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/ZapfDingbats-latin1
-    /ZapfDingbats findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/cp {closepath} bind def
-/c {curveto} bind def
-/f {fill} bind def
-/a {arc} bind def
-/ef {eofill} bind def
-/ex {exch} bind def
-/gr {grestore} bind def
-/gs {gsave} bind def
-/sa {save} bind def
-/rs {restore} bind def
-/l {lineto} bind def
-/m {moveto} bind def
-/rm {rmoveto} bind def
-/n {newpath} bind def
-/s {stroke} bind def
-/sh {show} bind def
-/slc {setlinecap} bind def
-/slj {setlinejoin} bind def
-/slw {setlinewidth} bind def
-/srgb {setrgbcolor} bind def
-/rot {rotate} bind def
-/sc {scale} bind def
-/sd {setdash} bind def
-/ff {findfont} bind def
-/sf {setfont} bind def
-/scf {scalefont} bind def
-/sw {stringwidth pop} bind def
-/tr {translate} bind def
-
-/ellipsedict 8 dict def
-ellipsedict /mtrx matrix put
-/ellipse
-{ ellipsedict begin
-   /endangle exch def
-   /startangle exch def
-   /yrad exch def
-   /xrad exch def
-   /y exch def
-   /x exch def   /savematrix mtrx currentmatrix def
-   x y tr xrad yrad sc
-   0 0 1 startangle endangle arc
-   savematrix setmatrix
-   end
-} def
-
-/mergeprocs {
-dup length
-3 -1 roll
-dup
-length
-dup
-5 1 roll
-3 -1 roll
-add
-array cvx
-dup
-3 -1 roll
-0 exch
-putinterval
-dup
-4 2 roll
-putinterval
-} bind def
-28.346000 -28.346000 scale
--2.500000 -9.079412 translate
-%%EndProlog
-
-
-1.000000 1.000000 1.000000 srgb
-n 2.627195 2.617647 m 2.627195 8.617647 l 6.427195 8.617647 l 6.427195 2.617647 l f
-0.050000 slw
-[] 0 sd
-[] 0 sd
-0 slj
-0.000000 0.000000 0.000000 srgb
-n 2.627195 2.617647 m 2.627195 8.617647 l 6.427195 8.617647 l 6.427195 2.617647 l cp s
-1.000000 1.000000 1.000000 srgb
-n 9.627195 2.617647 m 9.627195 8.617647 l 13.427195 8.617647 l 13.427195 2.617647 l f
-0.050000 slw
-[] 0 sd
-[] 0 sd
-0 slj
-0.000000 0.000000 0.000000 srgb
-n 9.627195 2.617647 m 9.627195 8.617647 l 13.427195 8.617647 l 13.427195 2.617647 l cp s
-1.000000 1.000000 1.000000 srgb
-n 9.627195 7.617647 m 9.627195 8.617647 l 12.227195 8.617647 l 12.227195 7.617647 l f
-0.050000 slw
-[] 0 sd
-[] 0 sd
-0 slj
-0.000000 0.000000 0.000000 srgb
-n 9.627195 7.617647 m 9.627195 8.617647 l 12.227195 8.617647 l 12.227195 7.617647 l cp s
-0.050000 slw
-[] 0 sd
-[] 0 sd
-0 slc
-n 13.427195 3.617647 m 9.627195 3.617647 l s
-0.050000 slw
-[] 0 sd
-[] 0 sd
-0 slc
-n 13.427195 4.617647 m 9.627195 4.617647 l s
-/Times-Bold-latin1 ff 0.400000 scf sf
-(ad2 Before Vinum) dup sw 2 div 4.527195 ex sub 2.317647 m gs 1 -1 sc sh gr
-/Times-Bold-latin1 ff 0.400000 scf sf
-(ad2 After Vinum) dup sw 2 div 11.527195 ex sub 2.317647 m gs 1 -1 sc sh gr
-/Times-Roman-latin1 ff 0.400000 scf sf
-(/rootback) dup sw 2 div 11.527195 ex sub 3.017647 m gs 1 -1 sc sh gr
-/Times-Roman-latin1 ff 0.400000 scf sf
-(swap) dup sw 2 div 11.527195 ex sub 4.017647 m gs 1 -1 sc sh gr
-/Times-Roman-latin1 ff 0.350000 scf sf
-(Vinum drive UpWindow) dup sw 2 div 11.527195 ex sub 5.017647 m gs 1 -1 sc sh gr
-/Times-Roman-latin1 ff 0.400000 scf sf
-(Vinum sd) dup sw 2 div 10.927195 ex sub 8.017647 m gs 1 -1 sc sh gr
-/Times-Roman-latin1 ff 0.400000 scf sf
-(/rootback) dup sw 2 div 4.527195 ex sub 3.017647 m gs 1 -1 sc sh gr
-/Times-Roman-latin1 ff 0.400000 scf sf
-(swap) dup sw 2 div 4.527195 ex sub 4.017647 m gs 1 -1 sc sh gr
-/Times-Roman-latin1 ff 0.400000 scf sf
-(/NOFUTURE) dup sw 2 div 4.527195 ex sub 6.017647 m gs 1 -1 sc sh gr
-/Times-Bold-latin1 ff 0.400000 scf sf
-(Offset \(blocks\)) dup sw 2 div 8.127195 ex sub 2.317647 m gs 1 -1 sc sh gr
-/Times-Roman-latin1 ff 0.300000 scf sf
-(\(not to scale\)) dup sw 2 div 3.427195 ex sub 9.017647 m gs 1 -1 sc sh gr
-/Courier-Bold-latin1 ff 0.400000 scf sf
-(/dev/ad2s1a) dup sw 2 div 11.527195 ex sub 3.417647 m gs 1 -1 sc sh gr
-/Courier-Bold-latin1 ff 0.400000 scf sf
-(/dev/ad2s1b) dup sw 2 div 11.527195 ex sub 4.417647 m gs 1 -1 sc sh gr
-/Courier-Bold-latin1 ff 0.400000 scf sf
-(/dev/ad2s1h) dup sw 2 div 11.527195 ex sub 5.417647 m gs 1 -1 sc sh gr
-/Courier-Bold-latin1 ff 0.400000 scf sf
-(hope.p0.s0) dup sw 2 div 10.927195 ex sub 8.417647 m gs 1 -1 sc sh gr
-/Courier-Bold-latin1 ff 0.400000 scf sf
-(/dev/ad2s1e) dup sw 2 div 4.527195 ex sub 3.417647 m gs 1 -1 sc sh gr
-/Courier-Bold-latin1 ff 0.400000 scf sf
-(/dev/ad2s1b) dup sw 2 div 4.527195 ex sub 4.417647 m gs 1 -1 sc sh gr
-/Courier-Bold-latin1 ff 0.400000 scf sf
-(/dev/ad2s1f) dup sw 2 div 4.527195 ex sub 6.417647 m gs 1 -1 sc sh gr
-/Courier-Bold-latin1 ff 0.400000 scf sf
-() dup sw 2 div 11.927195 ex sub 7.817647 m gs 1 -1 sc sh gr
-1.000000 1.000000 1.000000 srgb
-n 9.627195 5.617647 m 9.627195 6.617647 l 12.227195 6.617647 l 12.227195 5.617647 l f
-0.050000 slw
-[] 0 sd
-[] 0 sd
-0 slj
-0.000000 0.000000 0.000000 srgb
-n 9.627195 5.617647 m 9.627195 6.617647 l 12.227195 6.617647 l 12.227195 5.617647 l cp s
-1.000000 1.000000 1.000000 srgb
-n 9.627195 6.617647 m 9.627195 7.617647 l 12.227195 7.617647 l 12.227195 6.617647 l f
-0.050000 slw
-[] 0 sd
-[] 0 sd
-0 slj
-0.000000 0.000000 0.000000 srgb
-n 9.627195 6.617647 m 9.627195 7.617647 l 12.227195 7.617647 l 12.227195 6.617647 l cp s
-/Courier-Bold-latin1 ff 0.400000 scf sf
-(usr.p1.s0) dup sw 2 div 10.927195 ex sub 7.417647 m gs 1 -1 sc sh gr
-/Times-Roman-latin1 ff 0.400000 scf sf
-(Vinum sd) dup sw 2 div 10.927195 ex sub 7.017647 m gs 1 -1 sc sh gr
-/Courier-Bold-latin1 ff 0.400000 scf sf
-(home.p1.s0) dup sw 2 div 10.927195 ex sub 6.417647 m gs 1 -1 sc sh gr
-/Times-Roman-latin1 ff 0.400000 scf sf
-(Vinum sd) dup sw 2 div 10.927195 ex sub 6.017647 m gs 1 -1 sc sh gr
-/Courier-Bold-latin1 ff 0.400000 scf sf
-(8420769) dup sw 8.827195 ex sub 8.717647 m gs 1 -1 sc sh gr
-0.020000 slw
-[] 0 sd
-[] 0 sd
-0 slc
-n 9.027195 7.617647 m 9.427195 7.617647 l s
-0 slj
-1.000000 1.000000 1.000000 srgb
-n 9.227195 7.717647 m 9.427195 7.617647 l 9.227195 7.517647 l f
-0.020000 slw
-[] 0 sd
-0 slj
-0.000000 0.000000 0.000000 srgb
-n 9.227195 7.717647 m 9.427195 7.617647 l 9.227195 7.517647 l cp s
-0.020000 slw
-[] 0 sd
-[] 0 sd
-0 slc
-n 9.027195 6.617647 m 9.427195 6.617647 l s
-0 slj
-1.000000 1.000000 1.000000 srgb
-n 9.227195 6.717647 m 9.427195 6.617647 l 9.227195 6.517647 l f
-0.020000 slw
-[] 0 sd
-0 slj
-0.000000 0.000000 0.000000 srgb
-n 9.227195 6.717647 m 9.427195 6.617647 l 9.227195 6.517647 l cp s
-0.020000 slw
-[] 0 sd
-[] 0 sd
-0 slc
-n 9.027195 5.617647 m 9.427195 5.617647 l s
-0 slj
-1.000000 1.000000 1.000000 srgb
-n 9.227195 5.717647 m 9.427195 5.617647 l 9.227195 5.517647 l f
-0.020000 slw
-[] 0 sd
-0 slj
-0.000000 0.000000 0.000000 srgb
-n 9.227195 5.717647 m 9.427195 5.617647 l 9.227195 5.517647 l cp s
-0.020000 slw
-[] 0 sd
-[] 0 sd
-0 slc
-n 9.027195 4.617647 m 9.427195 4.617647 l s
-0 slj
-1.000000 1.000000 1.000000 srgb
-n 9.227195 4.717647 m 9.427195 4.617647 l 9.227195 4.517647 l f
-0.020000 slw
-[] 0 sd
-0 slj
-0.000000 0.000000 0.000000 srgb
-n 9.227195 4.717647 m 9.427195 4.617647 l 9.227195 4.517647 l cp s
-0.020000 slw
-[] 0 sd
-[] 0 sd
-0 slc
-n 9.027195 3.617647 m 9.427195 3.617647 l s
-0 slj
-1.000000 1.000000 1.000000 srgb
-n 9.227195 3.717647 m 9.427195 3.617647 l 9.227195 3.517647 l f
-0.020000 slw
-[] 0 sd
-0 slj
-0.000000 0.000000 0.000000 srgb
-n 9.227195 3.717647 m 9.427195 3.617647 l 9.227195 3.517647 l cp s
-0.020000 slw
-[] 0 sd
-[] 0 sd
-0 slc
-n 9.027195 2.617647 m 9.427195 2.617647 l s
-0 slj
-1.000000 1.000000 1.000000 srgb
-n 9.227195 2.717647 m 9.427195 2.617647 l 9.227195 2.517647 l f
-0.020000 slw
-[] 0 sd
-0 slj
-0.000000 0.000000 0.000000 srgb
-n 9.227195 2.717647 m 9.427195 2.617647 l 9.227195 2.517647 l cp s
-0.020000 slw
-[] 0 sd
-[] 0 sd
-0 slc
-n 9.027195 8.617647 m 9.427195 8.617647 l s
-0 slj
-1.000000 1.000000 1.000000 srgb
-n 9.227195 8.717647 m 9.427195 8.617647 l 9.227195 8.517647 l f
-0.020000 slw
-[] 0 sd
-0 slj
-0.000000 0.000000 0.000000 srgb
-n 9.227195 8.717647 m 9.427195 8.617647 l 9.227195 8.517647 l cp s
-0.020000 slw
-[] 0 sd
-[] 0 sd
-0 slc
-n 6.627195 8.617647 m 7.027195 8.617647 l s
-0 slj
-1.000000 1.000000 1.000000 srgb
-n 6.827195 8.517647 m 6.627195 8.617647 l 6.827195 8.717647 l f
-0.020000 slw
-[] 0 sd
-0 slj
-0.000000 0.000000 0.000000 srgb
-n 6.827195 8.517647 m 6.627195 8.617647 l 6.827195 8.717647 l cp s
-0.020000 slw
-[] 0 sd
-[] 0 sd
-0 slc
-n 6.627195 2.617647 m 7.027195 2.617647 l s
-0 slj
-1.000000 1.000000 1.000000 srgb
-n 6.827195 2.517647 m 6.627195 2.617647 l 6.827195 2.717647 l f
-0.020000 slw
-[] 0 sd
-0 slj
-0.000000 0.000000 0.000000 srgb
-n 6.827195 2.517647 m 6.627195 2.617647 l 6.827195 2.717647 l cp s
-0.020000 slw
-[] 0 sd
-[] 0 sd
-0 slc
-n 6.627195 3.617647 m 7.027195 3.617647 l s
-0 slj
-1.000000 1.000000 1.000000 srgb
-n 6.827195 3.517647 m 6.627195 3.617647 l 6.827195 3.717647 l f
-0.020000 slw
-[] 0 sd
-0 slj
-0.000000 0.000000 0.000000 srgb
-n 6.827195 3.517647 m 6.627195 3.617647 l 6.827195 3.717647 l cp s
-0.020000 slw
-[] 0 sd
-[] 0 sd
-0 slc
-n 6.627195 4.617647 m 7.027195 4.617647 l s
-0 slj
-1.000000 1.000000 1.000000 srgb
-n 6.827195 4.517647 m 6.627195 4.617647 l 6.827195 4.717647 l f
-0.020000 slw
-[] 0 sd
-0 slj
-0.000000 0.000000 0.000000 srgb
-n 6.827195 4.517647 m 6.627195 4.617647 l 6.827195 4.717647 l cp s
-0.020000 slw
-[] 0 sd
-[] 0 sd
-0 slc
-n 6.627195 5.617647 m 7.027195 5.617647 l s
-0 slj
-1.000000 1.000000 1.000000 srgb
-n 6.827195 5.517647 m 6.627195 5.617647 l 6.827195 5.717647 l f
-0.020000 slw
-[] 0 sd
-0 slj
-0.000000 0.000000 0.000000 srgb
-n 6.827195 5.517647 m 6.627195 5.617647 l 6.827195 5.717647 l cp s
-0.020000 slw
-[] 0 sd
-[] 0 sd
-0 slc
-n 6.627195 6.617647 m 7.027195 6.617647 l s
-0 slj
-1.000000 1.000000 1.000000 srgb
-n 6.827195 6.517647 m 6.627195 6.617647 l 6.827195 6.717647 l f
-0.020000 slw
-[] 0 sd
-0 slj
-0.000000 0.000000 0.000000 srgb
-n 6.827195 6.517647 m 6.627195 6.617647 l 6.827195 6.717647 l cp s
-0.020000 slw
-[] 0 sd
-[] 0 sd
-0 slc
-n 6.627195 7.617647 m 7.027195 7.617647 l s
-0 slj
-1.000000 1.000000 1.000000 srgb
-n 6.827195 7.517647 m 6.627195 7.617647 l 6.827195 7.717647 l f
-0.020000 slw
-[] 0 sd
-0 slj
-0.000000 0.000000 0.000000 srgb
-n 6.827195 7.517647 m 6.627195 7.617647 l 6.827195 7.717647 l cp s
-/Courier-Bold-latin1 ff 0.400000 scf sf
-(0) dup sw 8.827195 ex sub 2.717647 m gs 1 -1 sc sh gr
-/Courier-Bold-latin1 ff 0.400000 scf sf
-(200000) dup sw 8.827195 ex sub 3.717647 m gs 1 -1 sc sh gr
-/Courier-Bold-latin1 ff 0.400000 scf sf
-(400000) dup sw 8.827195 ex sub 4.717647 m gs 1 -1 sc sh gr
-/Courier-Bold-latin1 ff 0.400000 scf sf
-(400265) dup sw 8.827195 ex sub 5.717647 m gs 1 -1 sc sh gr
-/Courier-Bold-latin1 ff 0.400000 scf sf
-(1400265) dup sw 8.827195 ex sub 6.717647 m gs 1 -1 sc sh gr
-/Courier-Bold-latin1 ff 0.400000 scf sf
-(4124673) dup sw 8.827195 ex sub 7.717647 m gs 1 -1 sc sh gr
-/Courier-Bold-latin1 ff 0.400000 scf sf
-() dup sw 2 div 8.427195 ex sub 2.617647 m gs 1 -1 sc sh gr
-/Courier-Bold-latin1 ff 0.400000 scf sf
-() dup sw 2 div 7.927195 ex sub 2.617647 m gs 1 -1 sc sh gr
-/Courier-Bold-latin1 ff 0.400000 scf sf
-() dup sw 2 div 7.927195 ex sub 2.617647 m gs 1 -1 sc sh gr
-0.050000 slw
-[] 0 sd
-[] 0 sd
-0 slc
-n 6.427195 3.617647 m 2.627195 3.617647 l s
-0.050000 slw
-[] 0 sd
-[] 0 sd
-0 slc
-n 6.427195 5.617647 m 2.627195 5.617647 l s
-showpage
diff --git a/share/images/articles/vinum/arch.eps b/share/images/articles/vinum/arch.eps
deleted file mode 100644
index 2d4e34519d..0000000000
--- a/share/images/articles/vinum/arch.eps
+++ /dev/null
@@ -1,410 +0,0 @@
-%!PS-Adobe-2.0 EPSF-2.0
-%%Title: Untitled-4
-%%Creator: Dia v0.88.1
-%%CreationDate: Fri Oct 12 17:26:03 2001
-%%For: murray
-%%Magnification: 1.0000
-%%Orientation: Portrait
-%%BoundingBox: 0 0 104 138
-%%Pages: 1
-%%BeginSetup
-%%EndSetup
-%%EndComments
-%%BeginProlog
-[ /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef
-/.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef
-/.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef
-/.notdef /.notdef /space /exclam /quotedbl /numbersign /dollar /percent /ampersand /quoteright
-/parenleft /parenright /asterisk /plus /comma /hyphen /period /slash /zero /one
-/two /three /four /five /six /seven /eight /nine /colon /semicolon
-/less /equal /greater /question /at /A /B /C /D /E
-/F /G /H /I /J /K /L /M /N /O
-/P /Q /R /S /T /U /V /W /X /Y
-/Z /bracketleft /backslash /bracketright /asciicircum /underscore /quoteleft /a /b /c
-/d /e /f /g /h /i /j /k /l /m
-/n /o /p /q /r /s /t /u /v /w
-/x /y /z /braceleft /bar /braceright /asciitilde /.notdef /.notdef /.notdef
-/.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef
-/.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef
-/.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef /.notdef
-/space /exclamdown /cent /sterling /currency /yen /brokenbar /section /dieresis /copyright
-/ordfeminine /guillemotleft /logicalnot /hyphen /registered /macron /degree /plusminus /twosuperior /threesuperior
-/acute /mu /paragraph /periodcentered /cedilla /onesuperior /ordmasculine /guillemotright /onequarter /onehalf
-/threequarters /questiondown /Agrave /Aacute /Acircumflex /Atilde /Adieresis /Aring /AE /Ccedilla
-/Egrave /Eacute /Ecircumflex /Edieresis /Igrave /Iacute /Icircumflex /Idieresis /Eth /Ntilde
-/Ograve /Oacute /Ocircumflex /Otilde /Odieresis /multiply /Oslash /Ugrave /Uacute /Ucircumflex
-/Udieresis /Yacute /Thorn /germandbls /agrave /aacute /acircumflex /atilde /adieresis /aring
-/ae /ccedilla /egrave /eacute /ecircumflex /edieresis /igrave /iacute /icircumflex /idieresis
-/eth /ntilde /ograve /oacute /ocircumflex /otilde /odieresis /divide /oslash /ugrave
-/uacute /ucircumflex /udieresis /yacute /thorn /ydieresis] /isolatin1encoding exch def
-/Times-Roman-latin1
-    /Times-Roman findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Times-Italic-latin1
-    /Times-Italic findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Times-Bold-latin1
-    /Times-Bold findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Times-BoldItalic-latin1
-    /Times-BoldItalic findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/AvantGarde-Book-latin1
-    /AvantGarde-Book findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/AvantGarde-BookOblique-latin1
-    /AvantGarde-BookOblique findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/AvantGarde-Demi-latin1
-    /AvantGarde-Demi findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/AvantGarde-DemiOblique-latin1
-    /AvantGarde-DemiOblique findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Bookman-Light-latin1
-    /Bookman-Light findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Bookman-LightItalic-latin1
-    /Bookman-LightItalic findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Bookman-Demi-latin1
-    /Bookman-Demi findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Bookman-DemiItalic-latin1
-    /Bookman-DemiItalic findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Courier-latin1
-    /Courier findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Courier-Oblique-latin1
-    /Courier-Oblique findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Courier-Bold-latin1
-    /Courier-Bold findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Courier-BoldOblique-latin1
-    /Courier-BoldOblique findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Helvetica-latin1
-    /Helvetica findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Helvetica-Oblique-latin1
-    /Helvetica-Oblique findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Helvetica-Bold-latin1
-    /Helvetica-Bold findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Helvetica-BoldOblique-latin1
-    /Helvetica-BoldOblique findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Helvetica-Narrow-latin1
-    /Helvetica-Narrow findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Helvetica-Narrow-Oblique-latin1
-    /Helvetica-Narrow-Oblique findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Helvetica-Narrow-Bold-latin1
-    /Helvetica-Narrow-Bold findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Helvetica-Narrow-BoldOblique-latin1
-    /Helvetica-Narrow-BoldOblique findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/NewCenturySchoolbook-Roman-latin1
-    /NewCenturySchoolbook-Roman findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/NewCenturySchoolbook-Italic-latin1
-    /NewCenturySchoolbook-Italic findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/NewCenturySchoolbook-Bold-latin1
-    /NewCenturySchoolbook-Bold findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/NewCenturySchoolbook-BoldItalic-latin1
-    /NewCenturySchoolbook-BoldItalic findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Palatino-Roman-latin1
-    /Palatino-Roman findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Palatino-Italic-latin1
-    /Palatino-Italic findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Palatino-Bold-latin1
-    /Palatino-Bold findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Palatino-BoldItalic-latin1
-    /Palatino-BoldItalic findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/Symbol-latin1
-    /Symbol findfont
-definefont pop
-/ZapfChancery-MediumItalic-latin1
-    /ZapfChancery-MediumItalic findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/ZapfDingbats-latin1
-    /ZapfDingbats findfont
-    dup length dict begin
-	{1 index /FID ne {def} {pop pop} ifelse} forall
-	/Encoding isolatin1encoding def
-    currentdict end
-definefont pop
-/cp {closepath} bind def
-/c {curveto} bind def
-/f {fill} bind def
-/a {arc} bind def
-/ef {eofill} bind def
-/ex {exch} bind def
-/gr {grestore} bind def
-/gs {gsave} bind def
-/sa {save} bind def
-/rs {restore} bind def
-/l {lineto} bind def
-/m {moveto} bind def
-/rm {rmoveto} bind def
-/n {newpath} bind def
-/s {stroke} bind def
-/sh {show} bind def
-/slc {setlinecap} bind def
-/slj {setlinejoin} bind def
-/slw {setlinewidth} bind def
-/srgb {setrgbcolor} bind def
-/rot {rotate} bind def
-/sc {scale} bind def
-/sd {setdash} bind def
-/ff {findfont} bind def
-/sf {setfont} bind def
-/scf {scalefont} bind def
-/sw {stringwidth pop} bind def
-/tr {translate} bind def
-
-/ellipsedict 8 dict def
-ellipsedict /mtrx matrix put
-/ellipse
-{ ellipsedict begin
-   /endangle exch def
-   /startangle exch def
-   /yrad exch def
-   /xrad exch def
-   /y exch def
-   /x exch def   /savematrix mtrx currentmatrix def
-   x y tr xrad yrad sc
-   0 0 1 startangle endangle arc
-   savematrix setmatrix
-   end
-} def
-
-/mergeprocs {
-dup length
-3 -1 roll
-dup
-length
-dup
-5 1 roll
-3 -1 roll
-add
-array cvx
-dup
-3 -1 roll
-0 exch
-putinterval
-dup
-4 2 roll
-putinterval
-} bind def
-28.346000 -28.346000 scale
--2.500000 -6.850000 translate
-%%EndProlog
-
-
-1.000000 1.000000 1.000000 srgb
-n 2.525000 2.025000 m 2.525000 6.825000 l 6.125000 6.825000 l 6.125000 2.025000 l f
-0.050000 slw
-[] 0 sd
-[] 0 sd
-0 slj
-0.000000 0.000000 0.000000 srgb
-n 2.525000 2.025000 m 2.525000 6.825000 l 6.125000 6.825000 l 6.125000 2.025000 l cp s
-1.000000 1.000000 1.000000 srgb
-n 2.525000 2.825000 m 2.525000 6.025000 l 5.725000 6.025000 l 5.725000 2.825000 l f
-0.050000 slw
-[] 0 sd
-[] 0 sd
-0 slj
-0.000000 0.000000 0.000000 srgb
-n 2.525000 2.825000 m 2.525000 6.025000 l 5.725000 6.025000 l 5.725000 2.825000 l cp s
-1.000000 1.000000 1.000000 srgb
-n 3.725000 2.025000 m 3.725000 2.825000 l 4.925000 2.825000 l 4.925000 2.025000 l f
-0.050000 slw
-[] 0 sd
-[] 0 sd
-0 slj
-0.000000 0.000000 0.000000 srgb
-n 3.725000 2.025000 m 3.725000 2.825000 l 4.925000 2.825000 l 4.925000 2.025000 l cp s
-/Times-Roman-latin1 ff 0.400000 scf sf
-(UFS) dup sw 2 div 3.125000 ex sub 2.525000 m gs 1 -1 sc sh gr
-/Times-Roman-latin1 ff 0.400000 scf sf
-(swap) dup sw 2 div 4.325000 ex sub 2.525000 m gs 1 -1 sc sh gr
-/Times-Roman-latin1 ff 0.400000 scf sf
-(volume) dup sw 2 div 4.525000 ex sub 3.325000 m gs 1 -1 sc sh gr
-/Times-Roman-latin1 ff 0.400000 scf sf
-(plex) dup sw 2 div 4.525000 ex sub 4.125000 m gs 1 -1 sc sh gr
-/Times-Roman-latin1 ff 0.400000 scf sf
-(subdisk) dup sw 2 div 4.625000 ex sub 4.925000 m gs 1 -1 sc sh gr
-/Times-Roman-latin1 ff 0.400000 scf sf
-(drive) dup sw 2 div 4.525000 ex sub 5.725000 m gs 1 -1 sc sh gr
-/Times-Roman-latin1 ff 0.400000 scf sf
-(Block I/O devices) dup sw 2 div 4.325000 ex sub 6.525000 m gs 1 -1 sc sh gr
-/Times-Roman-latin1 ff 0.400000 scf sf
-(V) dup sw 2 div 3.025000 ex sub 3.725000 m gs 1 -1 sc sh gr
-(i) dup sw 2 div 3.025000 ex sub 4.125000 m gs 1 -1 sc sh gr
-(n) dup sw 2 div 3.025000 ex sub 4.525000 m gs 1 -1 sc sh gr
-(u) dup sw 2 div 3.025000 ex sub 4.925000 m gs 1 -1 sc sh gr
-(m) dup sw 2 div 3.025000 ex sub 5.325000 m gs 1 -1 sc sh gr
-/Times-Roman-latin1 ff 0.400000 scf sf
-(Etc.) dup sw 2 div 5.625000 ex sub 2.525000 m gs 1 -1 sc sh gr
-0.050000 slw
-[] 0 sd
-[] 0 sd
-0 slc
-n 5.725000 3.625000 m 3.525000 3.625000 l s
-0.050000 slw
-[] 0 sd
-[] 0 sd
-0 slc
-n 5.725000 5.225000 m 3.525000 5.225000 l s
-0.050000 slw
-[] 0 sd
-[] 0 sd
-0 slc
-n 5.725000 4.425000 m 3.525000 4.425000 l s
-showpage
diff --git a/share/sgml/urls.ent b/share/sgml/urls.ent
index e0a1557be7..0e309e2890 100644
--- a/share/sgml/urls.ent
+++ b/share/sgml/urls.ent
@@ -80,16 +80,12 @@
 
 <!-- for doc//langcode//articles -->
 
-<!ENTITY url.articles.5-roadmap		"&url.doc.langbase;/articles/5-roadmap">
-<!ENTITY url.articles.5-roadmap.en	"&url.doc.langbase.en;/articles/5-roadmap">
 <!ENTITY url.articles.bsdl-gpl		"&url.doc.langbase;/articles/bsdl-gpl">
 <!ENTITY url.articles.bsdl-gpl.en	"&url.doc.langbase.en;/articles/bsdl-gpl">
 <!ENTITY url.articles.building-products	"&url.doc.langbase;/articles/building-products">
 <!ENTITY url.articles.building-products.en	"&url.doc.langbase.en;/articles/building-products">
 <!ENTITY url.articles.casestudy-argentina.com	"&url.doc.langbase;/articles/casestudy-argentina.com">
 <!ENTITY url.articles.casestudy-argentina.com.en.en	"&url.doc.langbase.en;/articles/casestudy-argentina.com">
-<!ENTITY url.articles.checkpoint	"&url.doc.langbase;/articles/checkpoint">
-<!ENTITY url.articles.checkpoint.en	"&url.doc.langbase.en;/articles/checkpoint">
 <!ENTITY url.articles.committers-guide	"&url.doc.langbase;/articles/committers-guide">
 <!ENTITY url.articles.committers-guide.en	"&url.doc.langbase.en;/articles/committers-guide">
 <!ENTITY url.articles.compiz-fusion	"&url.doc.langbase;/articles/compiz-fusion">
@@ -108,12 +104,6 @@
 <!ENTITY url.articles.cvs-freebsd.en	"&url.doc.langbase.en;/articles/cvs-freebsd">
 <!ENTITY url.articles.cvsup-advanced	"&url.doc.langbase;/articles/cvsup-advanced">
 <!ENTITY url.articles.cvsup-advanced.en	"&url.doc.langbase.en;/articles/cvsup-advanced">
-<!ENTITY url.articles.dialup-firewall	"&url.doc.langbase;/articles/dialup-firewall">
-<!ENTITY url.articles.dialup-firewall.en	"&url.doc.langbase.en;/articles/dialup-firewall">
-<!ENTITY url.articles.diskless-x	"&url.doc.langbase;/articles/diskless-x">
-<!ENTITY url.articles.diskless-x.en	"&url.doc.langbase.en;/articles/diskless-x">
-<!ENTITY url.articles.euro		"&url.doc.langbase;/articles/euro">
-<!ENTITY url.articles.euro.en		"&url.doc.langbase.en;/articles/euro">
 <!ENTITY url.articles.explaining-bsd	"&url.doc.langbase;/articles/explaining-bsd">
 <!ENTITY url.articles.explaining-bsd.en	"&url.doc.langbase.en;/articles/explaining-bsd">
 <!ENTITY url.articles.fbsd-from-scratch	"&url.doc.langbase;/articles/fbsd-from-scratch">
@@ -122,16 +112,12 @@
 <!ENTITY url.articles.filtering-bridges.en	"&url.doc.langbase.en;/articles/filtering-bridges">
 <!ENTITY url.articles.fonts		"&url.doc.langbase;/articles/fonts">
 <!ENTITY url.articles.fonts.en		"&url.doc.langbase.en;/articles/fonts">
-<!ENTITY url.articles.formatting-media	"&url.doc.langbase;/articles/formatting-media">
-<!ENTITY url.articles.formatting-media.en	"&url.doc.langbase.en;/articles/formatting-media">
 <!ENTITY url.articles.freebsd-questions	"&url.doc.langbase;/articles/freebsd-questions">
 <!ENTITY url.articles.freebsd-questions.en	"&url.doc.langbase.en;/articles/freebsd-questions">
 <!ENTITY url.articles.geom-class	"&url.doc.langbase;/articles/geom-class">
 <!ENTITY url.articles.geom-class.en	"&url.doc.langbase.en;/articles/geom-class">
 <!ENTITY url.articles.gjournal-desktop	"&url.doc.langbase;/articles/gjournal-desktop">
 <!ENTITY url.articles.gjournal-desktop.en	"&url.doc.langbase.en;/articles/gjournal-desktop">
-<!ENTITY url.articles.hats		"&url.doc.langbase;/articles/hats">
-<!ENTITY url.articles.hats.en		"&url.doc.langbase.en;/articles/hats">
 <!ENTITY url.articles.hubs		"&url.doc.langbase;/articles/hubs">
 <!ENTITY url.articles.hubs.en		"&url.doc.langbase.en;/articles/hubs">
 <!ENTITY url.articles.ipsec-must	"&url.doc.langbase;/articles/ipsec-must">
@@ -150,8 +136,6 @@
 <!ENTITY url.articles.mailing-list-faq.en	"&url.doc.langbase.en;/articles/mailing-list-faq">
 <!ENTITY url.articles.mh		"&url.doc.langbase;/articles/mh">
 <!ENTITY url.articles.mh.en		"&url.doc.langbase.en;/articles/mh">
-<!ENTITY url.articles.multi-os		"&url.doc.langbase;/articles/multi-os">
-<!ENTITY url.articles.multi-os.en	"&url.doc.langbase.en;/articles/multi-os">
 <!ENTITY url.articles.nanobsd		"&url.doc.langbase;/articles/nanobsd">
 <!ENTITY url.articles.nanobsd.en	"&url.doc.langbase.en;/articles/nanobsd">
 <!ENTITY url.articles.new-users		"&url.doc.langbase;/articles/new-users">
@@ -182,15 +166,7 @@
 <!ENTITY url.articles.serial-uart.en	"&url.doc.langbase.en;/articles/serial-uart">
 <!ENTITY url.articles.solid-state	"&url.doc.langbase;/articles/solid-state">
 <!ENTITY url.articles.solid-state.en	"&url.doc.langbase.en;/articles/solid-state">
-<!ENTITY url.articles.storage-devices	"&url.doc.langbase;/articles/storage-devices">
-<!ENTITY url.articles.storage-devices.en	"&url.doc.langbase.en;/articles/storage-devices">
-<!ENTITY url.articles.version-guide		"&url.doc.langbase;/articles/version-guide">
-<!ENTITY url.articles.version-guide.en		"&url.doc.langbase.en;/articles/version-guide">
-<!ENTITY url.articles.vinum		"&url.doc.langbase;/articles/vinum">
-<!ENTITY url.articles.vinum.en		"&url.doc.langbase.en;/articles/vinum">
 <!ENTITY url.articles.vm-design		"&url.doc.langbase;/articles/vm-design">
 <!ENTITY url.articles.vm-design.en	"&url.doc.langbase.en;/articles/vm-design">
 <!ENTITY url.articles.wp-toolbox	"&url.doc.langbase;/articles/wp-toolbox">
 <!ENTITY url.articles.wp-toolbox.en	"&url.doc.langbase.en;/articles/wp-toolbox">
-<!ENTITY url.articles.zip-drive		"&url.doc.langbase;/articles/zip-drive">
-<!ENTITY url.articles.zip-drive.en	"&url.doc.langbase.en;/articles/zip-drive">
diff --git a/sr_YU.ISO8859-2/articles/Makefile b/sr_YU.ISO8859-2/articles/Makefile
index 59a30ec0af..a45b8a47c1 100644
--- a/sr_YU.ISO8859-2/articles/Makefile
+++ b/sr_YU.ISO8859-2/articles/Makefile
@@ -1,18 +1,13 @@
 # $FreeBSD$
 
 #SUBDIR = committers-guide
-SUBDIR+= dialup-firewall
-SUBDIR+= diskless-x
 #SUBDIR+= explaining-bsd
 #SUBDIR+= freebsd-questions
 #SUBDIR+= fonts
-#SUBDIR+= formatting-media
 #SUBDIR+= ipsec-must
 #SUBDIR+= mh
-#SUBDIR+= multi-os
 #SUBDIR+= new-users
 #SUBDIR+= programming-tools
-#SUBDIR+= zip-drive
 
 # ROOT_SYMLINKS+= new-users
 
diff --git a/sr_YU.ISO8859-2/articles/dialup-firewall/Makefile b/sr_YU.ISO8859-2/articles/dialup-firewall/Makefile
deleted file mode 100644
index 886e21cc9d..0000000000
--- a/sr_YU.ISO8859-2/articles/dialup-firewall/Makefile
+++ /dev/null
@@ -1,14 +0,0 @@
-# $FreeBSD$
-
-DOC?= article
-
-FORMATS?= html
-
-INSTALL_COMPRESSED?=gz
-INSTALL_ONLY_COMPRESSED?=
-
-SRCS= article.sgml
-
-DOC_PREFIX?= ${.CURDIR}/../../..
-
-.include "${DOC_PREFIX}/share/mk/doc.project.mk"
diff --git a/sr_YU.ISO8859-2/articles/dialup-firewall/article.sgml b/sr_YU.ISO8859-2/articles/dialup-firewall/article.sgml
deleted file mode 100644
index a549fc8048..0000000000
--- a/sr_YU.ISO8859-2/articles/dialup-firewall/article.sgml
+++ /dev/null
@@ -1,359 +0,0 @@
-
-<?xml version="1.0" encoding="ISO-8859-2" standalone="no"?>
-<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V4.2-Based Extension//EN"
-	"../../../share/sgml/freebsd42.dtd" [
-<!ENTITY % entities PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Entity Set//SR" "../../share/sgml/entities.ent">
-%entities;
-]>
-
-<!--
-     The FreeBSD Documentation Project
-
-     $FreeBSD$
-     Original revision: 1.7
--->
-
-<article lang='sr'>
-  <articleinfo>
-    <title>Dialup-firewalling sa FreeBSD-om</title>
-
-    <authorgroup>
-      <author>
-        <firstname>Marc</firstname>
-        <surname>Silver</surname>
-
-        <affiliation>
-          <address><email>marcs@draenor.org</email></address>
-        </affiliation>
-      </author>
-    </authorgroup>
-
-    <pubdate>$FreeBSD$</pubdate>
-
-    <releaseinfo>$FreeBSD$</releaseinfo>
-
-    <abstract>
-      <para>Ovaj èlanak dokumentuje kako podesiti firewall koristeæi PPP dialup
-sa FreeBSD-om i IPFW-om, kao i posebno pode¹avanje firewall-a na
-dialup sa dinamièki dodeljenim IP adresama. Ovaj dokument ne pokriva
-pode¹avanje same PPP konekcije.</para>
-    </abstract>
-  </articleinfo>
-
-  <sect1 id="preface">
-    <title>Uvod</title>
-
-    <para>Dialup-firewalling sa FreeBSD-om</para>
-
-    <para>Ovaj dokument poku¹ava da objasni postupak koji je potreban da bi se
-	podesio firewall na FreeBSD-u u sluèaju kada imate dinamièki
-	dodeljenu IP adresu. Mnogo truda je bilo ulo¾eno u to da ovaj
-	dokument bude¹ ¹to informativniji i taèniji, svaki va¹
-	komentar/sugestija <ulink url="mailto:marcs@draenor.org">autoru</ulink> je
-	dobrodo¹la.</para>
-   </sect1>
-
-  <sect1 id="kernel">
-    <title>Opcije pri konfigurisanju kernela</title>
-
-    <para>Prva stvar koju morate da uradite jeste da rekompajlirate kernel
-	FreeBSD-a. Ako vam je potrebno vi¹e informacija o tome kako da
-	rekompajlirate kernel, onda je svakako najbolje mesto da poènete poglavlje
-	o konfigurisanju kernela u <ulink
-    url="http://www.freebsd.org/handbook/kernelconfig.html">Pririèniku</ulink>.
-	Morate iskompajlirati kernel sa sledeæim opcijama:</para>
-
-    <variablelist>
-      <varlistentry>
-        <term><literal>options IPFIREWALL</literal></term>
-
-        <listitem>
-          <para>Ukljucuje firewall kod u kernel.</para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><literal>options IPFIREWALL_VERBOSE</literal></term>
-
-        <listitem>
-          <para>©alje logovane pakete system logger-u.</para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><literal>options
-            IPFIREWALL_VERBOSE_LIMIT=<replaceable>100</replaceable></literal></term>
-
-        <listitem>
-          <para>Limitira broj ekvivalentnih unosa u log. Ovo spreèava da se va¹ log prepuni
-		  sa mnogo jednakih unosa. <replaceable>100</replaceable> je razuman broj, ali mo¾ete
-		  promeniti ovaj podatak prema va¹im potrebama.</para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><literal>options IPDIVERT</literal></term>
-
-        <listitem>
-          <para>Omoguæava <emphasis>preusmeravanje</emphasis> socket-a, o èemu æe kasnije
-		  biti reèi.</para>
-        </listitem>
-      </varlistentry>
-    </variablelist>
-
-    <para>Postoje jos neke opcije koje nisu obavezne, a koje mo¾ete ukompajlirati u va¹ kernel
-	kako bi ste pobolj¹ali bezbednost va¹eg sistema. Ove opcije nisu neophodne, ali æe neki
-	paranoidniji korisnici svakako ¾eleti da ih upotrebe.</para>
-
-    <variablelist>
-      <varlistentry>
-        <term><literal>options TCP_RESTRICT_RST</literal></term>
-
-        <listitem>
-          <para>Ova opcija blokira sve TCP RST pakete. Ovo je najbolje koristiti za sisteme
-		  koji bi mogli biti izlo¾eni SYN flooding-u (IRC serveri su dobar primer), ili sisteme
-		  za koje je po¾eljno da im se ne mogu lako skenirati portovi.</para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><literal>options TCP_DROP_SYNFIN</literal></term>
-
-        <listitem>
-          <para>Ako ukljuèite ovu opciju u kernel, biæe ignorisani sci SYN i FIN paketi. Ovo
-		  onemoguæava alate kao sto je nmap, itd. da odrede TCP/IP stek masine, ali onemoguæava
-		  podr¹ku za RFC1644 ekstenzije. Ovo NIJE preporuèljivo ako æe ma¹ina raditi kao web
-		  server.</para>
-        </listitem>
-      </varlistentry>
-     </variablelist>
-
-    <para>Nemojte odmah da restartujete ma¹inu po¹to rekompajlirate kernel. Uz malo sreæe moraæete
-	samo jednom da uradite restartovanje da bi ste zavrsili instalaciju firewall-a.</para>
-  </sect1>
-
-  <sect1 id="rcconf">
-    <title>Izmene <filename>/etc/rc.conf</filename> fajla potrebne za podizanje
-      firewall-a</title>
-
-    <para>Sada je potrebno da uradimo odredjene izmene na
-      <filename>/etc/rc.conf</filename> fajlu kako bi smo omoguæili podizanje firewall-a.
-	  Jednostavno dodajte sledeæe linije:</para>
-
-    <programlisting>firewall_enable="YES"
-firewall_script="/etc/firewall/fwrules"
-natd_enable="YES"
-natd_interface="tun0"
-natd_flags="-dynamic"</programlisting>
-
-    <para>Za vi¹e informacija o tome pogledajte u
-      <filename>/etc/defaults/rc.conf</filename> i procitajte
-      &man.rc.conf.5;</para>
-  </sect1>
-
-  <sect1>
-    <title>Iskljcivanje PPP prevodjenja adresa</title>
-
-    <para>Moguæe je da veæ koristite prevodjenje adresa (network address translation-NAT)
-	koji je ugraðen u PPP. U tom sluèaju moraæete da ga iskljuèite, kao sto sledeæi primeri
-	koriste &man.natd.8; da bi uradili istu stvar.</para>
-
-    <para>Ako veæ imate pode¹en ppp, verovatno imate blok instrukcija za automatsko podizanje
-	PPP-a i to verovatno izgleda otprilike ovako:</para>
-
-    <programlisting>ppp_enable="YES"
-ppp_mode="auto"
-ppp_nat="YES"
-ppp_profile="<replaceable>profile</replaceable>"</programlisting>
-
-    <para>Ako je tako, obri¹ite <literal>ppp_nat="YES"</literal> line. Takodje æete morati
-	da uklonite <literal>nat enable yes</literal> ili <literal>alias enable yes</literal>
-	u <filename>/etc/ppp/ppp.conf</filename> fajlu.</para>
-  </sect1>
-
-  <sect1 id="rules">
-    <title>Pode¹avanje firewall-a</title>
-
-    <para>Sada smo veæ pri kraju. Sve ¹to je preostalo jeste da defini¹emo pravila po kojim
-	æe se firewall pona¹ati i posle toga mo¾ete da restartujete ma¹inu i firewall bi trebao
-	da bude podignut i aktivan. Svakako razumem da æe svako ¾eleti ne¹to drugaèija pravila za
-	njihov firewall, tako da sam poku¹ao da napi¹em pravila koja æe odgovarati veæini
-	korisnika dialup konekcije. Mo¾ete lako modifikovati veæ postojeæa pravila kao osnovu za
-	va¹ set pravila. Krenimo prvo sa osnovama zatvorenog firewall-inga. Ono ¹to bi trebalo da
-	uradite jeste da u osnovnoj konfiguraciji sve zatvorite i onda po potrebi otvorite samo ono
-	¹to vam je potrebno. Pravila se pi¹u tako da se prvo pi¹u pravila dozvole (allow), a onda
-	pravila zabrane (deny). Pretpostavka je da æete prvo dodati pravila dozvole, a zatim sve
-	ostalo zabraniti. :)</para>
-
-    <para>Napravimo sada direktorijum /etc/firewall. Udjite u taj direktorijum i potom napravite
-	file fwrules koji smo naznaèili u rc.conf fajlu i editujte ga prema va¹im potrebama. Molim
-	vas da obratite pa¾nju na to da mo¾ete da promenite ime ovog fajla kako vama odgovara. Ovo
-	uputsvo samo daje ovo ime kao primer. </para>
-
-    <para>Pogledajmo sada primer konfiguracionog fajla, gde æete videti i detalje pode¹avanja:.
-	</para>
-
-    <programlisting># Pravila za konfigurisanje firewall-a
-# Written by Marc Silver (marcs@draenor.org)
-# http://draenor.org/ipfw
-# Slobodna distribucija
-
-
-# Defini¹ite firewall komadu (kao u /etc/rc.firewall) radi
-# lak¹eg referenciranja. Omoguæava lak¹e èitanje istog .
-fwcmd="/sbin/ipfw"
-
-# Prisiljava preuzimanje novih pravila prilikom restartovanja.
-$fwcmd -f flush
-
-# Preusmerava sve pakete kroz tunnel interfejs.
-$fwcmd add divert natd all from any to any via tun0
-
-# Dozvoljava protok svih podataka kroz mre¾ne karte i localhost.
-# Proverite da li ste promenili identifikaciju mre¾ne karte pre
-# nego ¹to restartujete ma¹inu (moja je bila fxp0) :)
-$fwcmd add allow ip from any to any via lo0
-$fwcmd add allow ip from any to any via fxp0
-
-# Dozvoli sve konekcije koje ja iniciram
-$fwcmd add allow tcp from any to any out xmit tun0 setup
-
-# Po¹to su konekcije napravljene, dozvoli im da ostanu otvorene
-$fwcmd add allow tcp from any to any via tun0 established
-
-# Svima na internetu je dozvoljeno da se konektuju na sledeæe
-# servise na ovoj ma¹ini. U ovom primeru ljudi mogu da se
-# konektuju na ssh i apache (ili neki drugi web server koji
-# slu¹a na portu 80)
-$fwcmd add allow tcp from any to any 80 setup
-$fwcmd add allow tcp from any to any 22 setup
-
-# Ova linija ¹alje RESET svim ident paketima.
-$fwcmd add reset log tcp from any to any 113 in recv tun0
-
-# Omoguæi izlazne DNS upite SAMO ka odreðenim serverima.
-$fwcmd add allow udp from any to <replaceable>x.x.x.x</replaceable> 53 out xmit tun0
-
-# Dozvoli im da daju povratnu infomaciju.... :)
-$fwcmd add allow udp from <replaceable>x.x.x.x</replaceable> 53 to any in recv tun0
-
-# Dozvoli ICMP (potreban za ping i traceroute). Mo¾da æete
-# ¾eleti da ovo onemoguæite, ali to mojim potrebama odgovara
-$fwcmd add 65435 allow icmp from any to any
-
-# Zabrani sve ostalo.
-$fwcmd add 65435 deny log ip from any to any</programlisting>
-
-    <para>Sada imate potpuno funkcionalan firewall koji ce dozvoliti konekcije
-	na portove 80 i 22, i koji æe prijaviti poku¹aj konekcije na bilo koji
-	drugi port. Sada bi trebalo da mo¾ete bezbedno da restartujete ma¹inu i
-	posle restarta bi va¹ firewall trebao fino da radi. Ako pronadjete neku
-	gre¹ku ili natrèite na neki problem, ili imate bilo koju sugestiju kako bi
-	unapredio ovu dokumentaciju, molim vas da mi napi¹ete email.</para>
-  </sect1>
-
-  <sect1>
-    <title>Pitanja</title>
-
-    <qandaset>
-      <qandaentry>
-        <question>
-          <para>Za¹to koristite natd i ipfw kada bi mogli da koristite
-		  ugraðene ppp filtre?</para>
-        </question>
-
-        <answer>
-          <para>Moraæu da budem iskren na ovom mestu i da ka¾em da nemam
-		  odreðen razlog za¹to zaista koristim natd i ipfw umesto ugradjenih
-		  ppp filtera. Posle razgovora koje sam imao sa raznim ljudima, do¹li
-		  smo do konsezusa da je ipwf definitivno moæniji kao i konfigurabilniji
-		  od ppp filtera sto mu daje poen vi¹e za funkcionalnost, kao i poen
-		  manje za lakoæu kori¹æenja. Jedan od razloga zbog kojeg vi¹e volim
-		  ipwf jeste ¹to preferiram da se firewalling radi na nivou kernela a
-		  ne na nivou korisnièkog programa.</para>
-        </answer>
-      </qandaentry>
-
-      <qandaentry>
-        <question>
-          <para>Ako interno koristim privatnu adresu, kao npr. u 192.168.0.0
-		  opsegu, mogu li dodati komandu kao npr. $fwcmd add deny all from
-		  any to 192.168.0.0:255.255.0.0 via tun0 u pravila kako bih spreèio
-		  poku¹aj konekcija sa udaljene ma¹ine na internu ma¹inu?</para>
-        </question>
-
-        <answer>
-          <para>Jednostavan odgovor je ne. Razlog je to sto natd radi prevodjenje
-		  adresa za <emphasis>sve</emphasis> sto je preusmereno kroz tun0. Sto se
-		  natd-a tièe, dolazeæi paketi æe govoriti samo o dinamièki dodeljenoj
-		  IP adresi a NE o internoj mre¾i. Primetimo ipak da firewall-u mo¾ete
-		  dodati pravilo nalik na <literal>$fwcmd add deny all from any to
-		  192.168.0.0:255.255.0.0 via tun0</literal> koje bi ogranièilo host
-		  u va¹oj internoj mre¾i da izaðe uz pomoæ firewall-a.</para>
-        </answer>
-      </qandaentry>
-
-      <qandaentry>
-        <question>
-          <para>Mora da je ne¹to pogre¹no. Pratio sam va¹a uputstva od reèi do reèi
-		  i sada sam potpuno zatvoren.</para>
-        </question>
-
-        <answer>
-          <para>Ovaj tutorial pretpostavlja da koristite
-            <emphasis>userland-ppp</emphasis>, i iz tog razloga dati set
-            pravila radi na <devicename>tun0</devicename> interfejsu, to odgovara
-			prvoj konekciji ostvarenoj sa &man.ppp.8; (odn.
-            <emphasis>user-ppp</emphasis>).  Dodatne konekcije bi koristile
-            <devicename>tun1</devicename>, <devicename>tun2</devicename>
-			itd.</para>
-
-          <para>Takoðe bi trebalo da primetite da &man.pppd.8; koristi ppp0
-            <devicename>ppp0</devicename> interfejs, tako da ako zelite
-            da ostvarite konekciju pomocu &man.pppd.8;-a morate zameniti
-            <devicename>tun0</devicename> sa <devicename>ppp0</devicename>.
-            Brz naèin da podesite firewall u tom sluèaju je prikazan dole.
-			Originalni set pravila je saèuvan
-            <filename>fwrules_tun0</filename>.</para>
-
-          <screen>
-            &prompt.user; <userinput>cd /etc/firewall</userinput>
-            /etc/firewall&prompt.user; <userinput>su</userinput>
-            <prompt>Password:</prompt>
-            /etc/firewall&prompt.root; <userinput>mv fwrules fwrules_tun0</userinput>
-            /etc/firewall&prompt.root; <userinput>cat fwrules_tun0 | sed s/tun0/ppp0/g > fwrules</userinput>
-          </screen>
-
-          <para>Da bi ste saznali da li trenutno koristite &man.ppp.8; ili
-            &man.pppd.8; mozete pogledati izlaz &man.ifconfig.8;-a kada uspostavite vezu.
-			Pod uslovom da uspostavite konekciju sa &man.pppd.8;-om videæete ne¹to kao
-			(prikazane su samo relevatne linije):</para>
-
-          <screen>
-            &prompt.user; <userinput>ifconfig</userinput>
-            <emphasis>(skipped...)</emphasis>
-            ppp0: flags=<replaceable>8051&lt;UP,POINTOPOINT,RUNNING,MULTICAST&gt; mtu 1524</replaceable>
-                    inet <replaceable>xxx.xxx.xxx.xxx</replaceable> --&gt; <replaceable>xxx.xxx.xxx.xxx</replaceable> netmask <replaceable>0xff000000</replaceable>
-            <emphasis>(preskoèeno...)</emphasis>
-            </screen>
-
-          <para>OPod uslovom da je konekcija uspostavljena sa &man.ppp.8;-om
-            (<emphasis>user-ppp</emphasis>) trebalo bi da dobijete nesto nalik
-			na slede'e linije:</para>
-
-          <screen>
-            &prompt.user; <userinput>ifconfig</userinput>
-            <emphasis>(skipped...)</emphasis>
-            ppp0: flags=<replaceable>8010&lt;POINTOPOINT,MULTICAST&gt; mtu 1500</replaceable>
-            <emphasis>(skipped...)</emphasis>
-            tun0: flags=<replaceable>8051&lt;UP,POINTOPOINT,RUNNING,MULTICAST&gt; mtu 1524</replaceable>
-                    <emphasis>(IPv6 stuff skipped...)</emphasis>
-                    inet <replaceable>xxx.xxx.xxx.xxx</replaceable> --&gt; <replaceable>xxx.xxx.xxx.xxx</replaceable> netmask <replaceable>0xffffff00</replaceable>
-                    Opened by PID <replaceable>xxxxx</replaceable>
-            <emphasis>(preskoèeno...)</emphasis>
-            </screen>
-        </answer>
-      </qandaentry>
-    </qandaset>
-  </sect1>
-</article>
diff --git a/sr_YU.ISO8859-2/articles/diskless-x/Makefile b/sr_YU.ISO8859-2/articles/diskless-x/Makefile
deleted file mode 100644
index 886e21cc9d..0000000000
--- a/sr_YU.ISO8859-2/articles/diskless-x/Makefile
+++ /dev/null
@@ -1,14 +0,0 @@
-# $FreeBSD$
-
-DOC?= article
-
-FORMATS?= html
-
-INSTALL_COMPRESSED?=gz
-INSTALL_ONLY_COMPRESSED?=
-
-SRCS= article.sgml
-
-DOC_PREFIX?= ${.CURDIR}/../../..
-
-.include "${DOC_PREFIX}/share/mk/doc.project.mk"
diff --git a/sr_YU.ISO8859-2/articles/diskless-x/article.sgml b/sr_YU.ISO8859-2/articles/diskless-x/article.sgml
deleted file mode 100644
index 04154c15b5..0000000000
--- a/sr_YU.ISO8859-2/articles/diskless-x/article.sgml
+++ /dev/null
@@ -1,344 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-2" standalone="no"?>
-<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V4.2-Based Extension//EN"
-	"../../../share/sgml/freebsd42.dtd" [
-<!ENTITY % entities PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Entity Set//SR" "../../share/sgml/entities.ent">
-%entities;
-]>
-
-<!--
-     The FreeBSD Documentation Project
-
-     $FreeBSD$
--->
-
-<article lang="sr">
-  <articleinfo>
-    <title>Diskless X Server: "how to" vodiè</title>
-
-    <authorgroup>
-      <author>
-	<firstname> Jerry</firstname>
-	<surname>Kendall</surname>
-	<affiliation>
-	  <address>
-	    <email>jerry@kcis.com</email>
-	  </address>
-	</affiliation>
-      </author></authorgroup>
-
-    <pubdate>28. decembar 1996.</pubdate>
-
-    <copyright>
-      <year>1996</year>
-      <holder>Jerry Kendall</holder>
-    </copyright>
-
-    <releaseinfo>$FreeBSD$</releaseinfo>
-
-    <abstract>
-      <para>Uz pomoæ nekih prijatelja sa FreeBSD-hackers liste, napravio
-        sam diskless X terminal. Pravljenje X terminala je prvo zahtevalo
-	da se napravi sistem bez diska sa minimalnim skupom alata koji se
-	mountuje preko NFSa. Isti postupak je kori¹æen da se naprave 2
-	odvojena diskless sistema. Prvi je <hostid role="fqdn">
-	altair.kcis.com</hostid>, X terminal bez diska koji radi na mom
-	starom 386DX-40 raèunaru. Ima hard disk od 340 megabajta, ali
-	nisam ¾eleo da ga menjam. Tako da se ma¹ina bootuje sa <hostid
-	  role="fqdn">antares.kcis.com</hostid> ma¹ine, preko Etherneta.
-	Drugi sistem je 486DX2-66. Napravio sam diskless FreeBSD instalaciju
-	(kompletnu) koja ne koristi lokalni disk. U ovom sluèaju server je
-	Sun 670MP pod SunOSom 4.1.3. Ista konfiguracija je kori¹æena za
-	obe ma¹ine.</para>
-
-      <para>Siguran sam da ima dosta stvari koje treba dodati ovom dokumentu.
-        Molim vas, po¹aljite mi sve komentare.</para>
-    </abstract>
-  </articleinfo>
-
-  <sect1>
-    <title>Kreiranje boot diskete (na diskless sistemu)</title>
-
-    <para>Po¹to mre¾ni boot loaderi neæe da rade sa nekim TSR MS-DOS
-      programima, najbolje je napraviti posebnu boot disketu, ili,
-      ako mo¾ete, napraviti MS-DOS meni koji æe (pomoæu
-      <filename>config.sys</filename>/<filename>autoexec.bat</filename>
-      datoteka) upitati koju konfiguraciju ¾elimo da uèitamo pri startu
-      sistema. Ovo potonje je metod koji ja koristim i radi sjajno.
-      Evo mog MS-DOS (6.x) menija.</para>
-
-    <example>
-      <title><filename>config.sys</filename></title>
-
-      <programlisting>[menu]
-menuitem=normal, normal
-menuitem=unix, unix
-[normal]
-....
-normal config.sys stuff
-...
-[unix]</programlisting>
-    </example>
-
-    <example>
-      <title><filename>autoexec.bat</filename></title>
-
-      <programlisting>@ECHO OFF
-goto %config%
-
-:normal
-...
-normal autoexec.bat stuff
-...
-goto end
-
-:unix
-cd \netboot
-nb8390.com
-
-:end</programlisting>
-    </example>
-  </sect1>
-
-  <sect1>
-    <title>Instalacija programa za boot preko mre¾e (na serveru)</title>
-
-    <para>Prevedite 'net-boot' programe koji se nalaze u
-      <filename>/usr/src/sys/i386/boot/netboot</filename>.  Trebalo bi da
-      proèitate komentare na poèetku <filename>Makefile</filename> fajla.
-      Podesite po potrebi. Napravite rezervnu kopiju originala za svaki
-      sluèaj. Kad se prevoðenje zavr¹i, trebalo bi da imate 2 MS-DOS
-      izvr¹na fajla, <filename>nb8390.com</filename> i <filename>nb3c509.com</filename>.
-      Jedan od ova dva programa je ono ¹to æete pokrenuti na diskless ma¹ini.
-      Slu¾iæe da uèita kernel sa boot servera. Sada stavite oba programa na
-      MS-DOS boot disketu koju ste ranije napravili.</para>
-  </sect1>
-
-  <sect1>
-    <title>Koji program pokrenuti? (na diskless ma¹ini)</title>
-
-    <para>Ako znate koji set èipova va¹a Ethernet kartica koristi, ovaj
-      korak je lak. Ako imate NS8390 set èipova, ili neki baziran na NS8390
-      èipu, uzmite <filename>nb8390.com</filename>. Ako imate karticu baziranu
-      na 3Com 509 èipu, uzmite <filename>nb3C509.com</filename> boot program.
-      Ako niste sigurni kakvu karticu imate, poku¹ajte sa jednim, ako prijavi
-      <errorname>No adapter found</errorname>, poku¹ajte sa onim drugim. Ako
-      ovo ne upali, moraæete sami da se snaðete.</para>
-  </sect1>
-
-  <sect1>
-    <title>Podizanje sistema preko mre¾e</title>
-
-    <para>Podignite diskless sistem bez config.sys/autoexec.bat fajlova.
-      Poku¹ajte da pokrenete boot program za va¹u mre¾nu karticu.</para>
-
-    <para>Moja mre¾na kartica radi u WD8013 16bitnom modu, pa ja koristim
-      <filename>nb8390.com</filename>.</para>
-
-    <screen><prompt>C:&gt;</prompt> <userinput>cd \netboot</userinput>
-<prompt>C:&gt;</prompt> <userinput>nb8390</userinput>
-
-<prompt>Boot from Network (Y/N) ?</prompt>  <userinput>Y</userinput>
-
-BOOTP/TFTP/NFS bootstrap loader     ESC for menu
-
-Searching for adapter..
-WD8013EBT base 0x0300, memory 0x000D8000, addr 00:40:01:43:26:66
-
-Searching for server...</screen>
-
-    <para>U ovom trenutku, moj diskless sistem poku¹ava da naðe ma¹inu koja
-      æe slu¾iti kao boot server. Prepi¹ite <literal>addr</literal> liniju
-      u gornjem listingu, trebaæe vam taj broj kasnije. Resetujte diskless
-      ma¹inu i podesite <filename>config.sys</filename> i
-      <filename>autoexec.bat</filename> da rade ovaj posao automatski. Na primer
-      pomoæu menija. Ako koristite <command>nb3c509.com</command> umesto
-      <command>nb8390.com</command>, listing æe biti isti kao gornji. Ako ste
-      dobili poruku <errorname>No adapter found</errorname> kod
-      <literal>Searching for adapter...</literal> poruke, proverite da li ste
-      dobro podesili opcije u <filename>Makefile</filename>-u.</para>
-  </sect1>
-
-  <sect1>
-    <title>Omoguæite sistemima da se podignu preko mre¾e (na serveru)</title>
-
-    <para>Proverite da li su tftp i bootps pode¹eni u <filename>/etc/inetd.conf</filename>
-      fajlu. Evo mog pode¹avanja:</para>
-
-    <programlisting>tftp	dgram	udp	wait	nobody	/usr/libexec/tftpd	tftpd /tftpboot
-#
-# Additions by who ever you are
-bootps  dgram  udp  wait  root  /usr/libexec/bootpd bootpd /etc/bootptab</programlisting>
-
-    <para>Ako promenite ne¹to u <filename>/etc/inetd.conf</filename> fajlu,
-      po¹aljite <literal>HUP</literal> signal inetd demonu. Da bi ovo uèinili,
-      naðite ID procesa inetd sa <command>ps -ax | grep inetd | grep -v
-	grep</command>.  Zatim mu po¹aljite HUP signal sa
-	<command>kill -HUP &lt;pid&gt;</command>.  Ovo æe naterati inetd
-	da ponovo proèita svoj konfiguracioni fajl.</para>
-
-    <para>Da li ste zabele¾ili <literal>addr</literal> liniju iz ispisa
-      boot loadera na ma¹ini bez diska? Sada æe vam biti potrebna.</para>
-
-    <para>Dodajte sledeæe u <literal>/etc/bootptab</literal> (mo¾da æete morati
-      da kreirate fajl).</para>
-
-    <programlisting>altair:\
-        :ht=ether:\
-        :ha=004001432666:\
-        :sm=255.255.255.0:\
-        :hn:\
-        :ds=199.246.76.1:\
-        :ip=199.246.76.2:\
-        :gw=199.246.76.1:\
-        :vm=rfc1048:</programlisting>
-
-    <para>Evo znaèenja ovih redova:</para>
-
-    <informaltable frame="none">
-      <tgroup cols="2">
-	<tbody>
-	  <row>
-	    <entry><literal>altair</literal></entry>
-	    <entry>ime sistema bez diska, bez imena domena.</entry>
-	  </row>
-
-	  <row>
-	    <entry><literal>ht=ether</literal></entry>
-	    <entry>tip hardvera, u ovom sluèaju 'ethernet'.</entry>
-	  </row>
-
-	  <row>
-	    <entry><literal>ha=004001432666</literal></entry>
-	    <entry>hardverska adresa (broj koji ste zabele¾ili).</entry>
-	  </row>
-
-	  <row>
-	    <entry><literal>sm=255.255.255.0</literal></entry>
-	    <entry>subnet maska.</entry>
-	  </row>
-
-	  <row>
-	    <entry><literal>hn</literal></entry>
-	    <entry>govori serveru da treba klijentu da po¹alje
-	      njegov hostname.</entry>
-	  </row>
-
-	  <row>
-	    <entry><literal>ds=199.246.76.1</literal></entry>
-	    <entry>govori klijentu gde je domain server.</entry>
-	  </row>
-
-	  <row>
-	    <entry><literal>ip=199.246.76.2</literal></entry>
-	    <entry>govori klijentu koja mu je IP adresa.</entry>
-	  </row>
-
-	  <row>
-	    <entry><literal>gw=199.246.76.1</literal></entry>
-	    <entry>govori klijentu koji je podrazumevani gateway.</entry>
-	  </row>
-
-	  <row>
-	    <entry><literal>vm=...</literal></entry>
-	    <entry>samo ostavite ovo kako jeste.</entry>
-	  </row>
-	</tbody>
-      </tgroup>
-    </informaltable>
-
-    <note>
-      <para>Vodite raèuna da upi¹ete IP adrese ispravno, gornji primer je
-	moja konfiguracija.</para>
-    </note>
-
-    <para>Kreirajte direktorijum '/tftpboot' na serveru, koji æe sadr¾ati
-      konfiguracione fajlove za sisteme bez diska koje æe server opslu¾ivati.
-      Ovi fajlovi æe nositi ime 'cfg.&lt;ip&gt;' gde je &lt;ip&gt; IP adresa
-      diskless sistema. Konfiguracioni fajl za 'altair' je
-      /tftpboot/cfg.199.246.76.2.  Njegov sadr¾aj je:</para>
-
-    <programlisting>rootfs 199.246.76.1:/DiskLess/rootfs/altair
-hostname altair.kcis.com</programlisting>
-
-    <para>Red <literal>hostname altair.kcis.com</literal> govori raèunaru
-      bez diska njegovo puno ime domena.</para>
-
-    <para>Red <literal>rootfs
-	199.246.76.1:/DiskLess/rootfs/altair</literal> govori raèunaru bez
-	diska gde mu se nalazi root fajlsistem koji æe mountovati preko NFSa.
-    </para>
-
-    <note>
-      <para>NFS root fajlsistem æe biti mountovan kao <emphasis>read
-	  only</emphasis>.</para>
-    </note>
-
-    <para>Hijerarhija za sistem bez diska mo¾e biti re-mountovana
-      da bi se dozvolilo pisanje po fajl sistemu, ukoliko je to potrebno.
-    </para>
-
-    <para>Ja koristim moj stari 386DX-40 kao posveæeni X terminal.</para>
-
-    <para>Hijerarhija za 'altair' izgleda ovako:</para>
-
-    <literallayout>/
-/bin
-/etc
-/tmp
-/sbin
-/dev
-/dev/fd
-/usr
-/var
-/var/run</literallayout>
-
-    <para>Evo i liste samih fajlova:</para>
-
-    <screen>-r-xr-xr-x  1 root  wheel  779984 Dec 11 23:44 ./kernel
--r-xr-xr-x  1 root    bin  299008 Dec 12 00:22 ./bin/sh
--rw-r--r--  1 root  wheel     499 Dec 15 15:54 ./etc/rc
--rw-r--r--  1 root  wheel    1411 Dec 11 23:19 ./etc/ttys
--rw-r--r--  1 root  wheel     157 Dec 15 15:42 ./etc/hosts
--rw-r--r--  1 root    bin    1569 Dec 15 15:26 ./etc/XF86Config.altair
--r-x------  1 bin     bin  151552 Jun 10  1995 ./sbin/init
--r-xr-xr-x  1 bin     bin  176128 Jun 10  1995 ./sbin/ifconfig
--r-xr-xr-x  1 bin     bin  110592 Jun 10  1995 ./sbin/mount_nfs
--r-xr-xr-x  1 bin     bin  135168 Jun 10  1995 ./sbin/reboot
--r-xr-xr-x  1 root    bin   73728 Dec 13 22:38 ./sbin/mount
--r-xr-xr-x  1 root  wheel    1992 Jun 10  1995 ./dev/MAKEDEV.local
--r-xr-xr-x  1 root  wheel   24419 Jun 10  1995 ./dev/MAKEDEV</screen>
-
-    <para>Ne zaboravite da pokrenete <command>MAKEDEV all</command> u
-      <filename>dev</filename> direktorijumu.</para>
-
-    <para>Moj <filename>/etc/rc</filename> za <hostid>altair</hostid>
-      izgleda ovako:</para>
-
-<programlisting>#!/bin/sh
-#
-PATH=/bin:/
-export PATH
-#
-# configure the localhost
-/sbin/ifconfig lo0 127.0.0.1
-#
-# configure the ethernet card
-/sbin/ifconfig ed0 199.246.76.2 netmask 0xffffff00
-#
-# mount the root filesystem via NFS
-/sbin/mount antares:/DiskLess/rootfs/altair /
-#
-# mount the /usr filesystem via NFS
-/sbin/mount antares:/DiskLess/usr /usr
-#
-/usr/X11R6/bin/XF86_SVGA -query antares -xf86config /etc/XF86Config.altair >/dev/null 2&gt;&amp;1
-#
-# Reboot after X exits
-/sbin/reboot
-#
-# We blew up....
-exit 1</programlisting>
-
-    <para>Svi komentari su dobrodo¹li, kao i sva pitanja.</para>
-  </sect1>
-</article>
diff --git a/tr_TR.ISO8859-9/htdocs/docs.sgml b/tr_TR.ISO8859-9/htdocs/docs.sgml
index ad954cd900..4f86efb042 100644
--- a/tr_TR.ISO8859-9/htdocs/docs.sgml
+++ b/tr_TR.ISO8859-9/htdocs/docs.sgml
@@ -122,24 +122,6 @@
 <!-- Articles are sorted by pathname -->
 
     <p><a
-      href="&enbase;/doc/en_US.ISO8859-1/articles/5-roadmap/index.html">
-      5-STABLE için yol haritasý</a>
-      (<tt>5-roadmap</tt>)<br>
-      <small>5-Stable sýnýfýnýn
-	oluþturulabilmesi için orta vadeli geliþtirim
-	planý ve sürüm mühendisli&eth;i
-	planlarý anlatýlmaktadýr.</small></p>
-
-    <p><a
-      href="&enbase;/doc/en_US.ISO8859-1/articles/checkpoint/index.html">
-      Checkpoint VPN-1/Firewall-1 ve FreeBSD IPsec entegrasyonu</a>
-      (<tt>checkpoint</tt>)<br>
-      <small>Checkpoint VPN-1/Firewall-1 ve FreeBSD IPsec 'in berbaber
-	çalýþmasý için nasýl
-	konfigüre edilmesi gerekti&eth;i
-	anlatýlmaktadýr.</small></p>
-
-    <p><a
       href="&enbase;/doc/en_US.ISO8859-1/articles/committers-guide/index.html">
       Committer Klavuzu</a> (<tt>committers-guide</tt>)<br>
       <small>FreeBSD committer 'larý için gerekli
@@ -179,28 +161,6 @@
       <small>CVSup sisteminin inceli&eth;i.</small></p>
 
     <p><a
-      href="&enbase;/doc/en_US.ISO8859-1/articles/dialup-firewall/index.html">
-      FreeBSD ile Çevirimli Firewall Kurulumu</a>
-      (<tt>dialup-firewall</tt>)<br>
-      <small>PPP ve ipfw kullanarak çevirimli a&eth;
-	üzerinden atanmýþ; de&eth;iþken bir IP
-	üzerinde firewall kurulumu.</small></p>
-
-    <p><a
-      href="&enbase;/doc/en_US.ISO8859-1/articles/diskless-x/index.html">
-      Disksiz bir X sunucusu kurmak</a> (<tt>diskless-x</tt>)<br>
-      <small>Disksiz bir X sunucusu kurulumu
-	anlatýlmaktadýr.</small></p>
-
-    <p><a
-      href="&enbase;/doc/en_US.ISO8859-1/articles/euro/article.html">
-      FreeBSD 'de Euro Sembölü</a> (<tt>euro</tt>)<br>
-      <small>FreeBSD ve alakalý
-	yazýlýmlarýn Euro sembolünü
-	nasýl gösterebilece&eth;i
-	anlatýlýr.</small></p>
-
-    <p><a
       href="&enbase;/doc/en_US.ISO8859-1/articles/explaining-bsd/index.html">
       BSD 'i Açýklanýyor</a>
       (<tt>explaining-bsd</tt>)<br>
@@ -232,14 +192,6 @@
 	kullanýldý&eth;ý.</small></p>
 
     <p><a
-      href="&enbase;/doc/en_US.ISO8859-1/articles/formatting-media/index.html">
-      FreeBSD 'de Formatlama</a> (<tt>formatting-media</tt>)<br>
-      <small>FreeBSD 'de taþýnabilir ve sabit
-	cihazlarýn nasýl dilimleme, bölmeleme ve
-	formatlama yapýlaca&eth;ý
-	anlatýlýr.</small></p>
-
-    <p><a
       href="&enbase;/doc/en_US.ISO8859-1/articles/freebsd-questions/index.html">
       FreeBSD-questions mail listesinden en iyi sonucu nasýl
       alýrsýnýz</a> (<tt>freebsd-questions</tt>)<br>
@@ -248,14 +200,6 @@
       anlatýlýr.</small></p>
 
     <p><a
-      href="&enbase;/doc/en_US.ISO8859-1/articles/hats/index.html">
-      Hats 'lerle çalýþmak</a> (<tt>hats</tt>)<br>
-      <small>``hat'' (FreeBSD 'nin de&eth;iþik
-	noktalarýndan sorumlu kiþiler) ile birlikte
-	nasýl çalýþýlaca&eth;ý
-	anlatýlmaktadýr.</small></p>
-
-    <p><a
       href="&enbase;/doc/en_US.ISO8859-1/articles/hubs/index.html">FreeBSD
       'yi Yansýlamak</a> (<tt>hubs</tt>)<br>
       <small>FreeBSD web sitesinin, CVSup sunucusunun, FTP sunucusunun
@@ -289,15 +233,6 @@
 	nasýl kullanýlaca&eth;ý.</small></p>
 
     <p><a
-      href="&enbase;/doc/en_US.ISO8859-1/articles/multi-os/index.html">
-      FreeBSD 'nin di&eth;er iþletim sistemleri ile
-      nasýl kullanýlaca&eth;ý?</a>
-      (<tt>multi-os</tt>)<br>
-      <small>Ayný bilgisayar üzerinde de&eth;iþik
-	iþletim sistemlerinin FreeBSD ile nasýl
-	kurulabilece&eth;i.</small></p>
-
-    <p><a
       href="&enbase;/doc/en_US.ISO8859-1/articles/new-users/index.html">FreeBSD
       'de ilk adýmlar </a> (<tt>new-users</tt>)<br>
       <small>FreeBSD ve &unix; sistemini ilk kez kullanacaklar
@@ -380,39 +315,12 @@
       anlatýlýr.</small></p>
 
     <p><a
-      href="&enbase;/doc/en_US.ISO8859-1/articles/storage-devices/index.html">Yedekleme
-      Cihazlarý</a> (<tt>storage-devices</tt>)<br>
-      <small>FreeBSD'de ESDI disklerin, SCSI disklerin,
-      teyplerin, ve CDROM sürücülerinin
-      nasýl kullanýldý&eth;ý
-      anlatýlýr.</small></p>
-
-    <p><a
-      href="&enbase;/doc/en_US.ISO8859-1/articles/vinum/index.html">
-      Vinum: Güvenli sunucular için temel
-      yapýtaþý</a> (<tt>vinum</tt>)<br>
-      <small>FreeBSD 'de hata duyarlý sunucularýn
-      kurulumu ve bunun Vinum ile nasýl
-      gerçellendi&eth;inin adým adým
-      gösterimi.</small></p>
-
-    <p><a
       href="&enbase;/doc/en_US.ISO8859-1/articles/vm-design/index.html">
       FreeBSD VM sisteminin tasarým parçalarý</a>
       (<tt>vm-design</tt>)<br> <small>FreeBSD sanal hafýza
       sisteminin nasýl gerçellendi&eth;inin
       anlatýlýr.</small></p>
 
-    <p><a
-      href="&enbase;/doc/en_US.ISO8859-1/articles/zip-drive/index.html">Zip
-      sürücüler ve FreeBSD</a>
-      (<tt>zip-drive</tt>)<br> <small>Iomega Zip (SCSI, IDE, ya da
-      paralel) sürücülerinin nasýl
-      formatlandý&eth;ý,
-      ba&eth;landý&eth;ý ve
-      kullanýldý&eth;ý
-      anlatýlmaktadýr.</small></p>
-
     <h3><a name="man">Klavuz Sayfalarý</a></h3>
 
     <dl>
diff --git a/zh_CN.GB2312/articles/linux-users/article.sgml b/zh_CN.GB2312/articles/linux-users/article.sgml
index e02ea00c47..602b6879af 100644
--- a/zh_CN.GB2312/articles/linux-users/article.sgml
+++ b/zh_CN.GB2312/articles/linux-users/article.sgml
@@ -138,11 +138,6 @@ in your /etc/rc.conf. Extra options can be found in startup script.</screen>
           ÀýÈ磬°Ñ <envar>PACHAGESITE</envar> ÉèÖóÉ
           <ulink url="ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-6-stable/Latest/"></ulink>
           À´ÏÂÔØ 6.X ϵÁÐ×îеİü¡£</para>
-
-        <para>Äã¿ÉÒÔÔĶÁÕâƪÎÄÕÂ
-	  <ulink url="&url.base;/doc/en_US.ISO8859-1/articles/version-guide/">
-            Ñ¡Ôñ×îÊʺÏ×Ô¼ºµÄ &os; °æ±¾ºÅ</ulink> À´»ñÈ¡¸ü¶à¹ØÓÚ &os;
-          °æ±¾ºÅµÄ¶«Î÷¡£</para>
       </note>
 
       <para>ÏëÁ˽â¸ü¶àµÄ packages ÐÅÏ¢Çë²éÔÄ &os;
diff --git a/zh_TW.Big5/books/faq/book.sgml b/zh_TW.Big5/books/faq/book.sgml
index fb3d6169dd..49a895c659 100644
--- a/zh_TW.Big5/books/faq/book.sgml
+++ b/zh_TW.Big5/books/faq/book.sgml
@@ -1241,18 +1241,6 @@ File: +DESC (ignored)</screen>
       </qandaentry>
 
       <qandaentry>
-        <question id="multiboot">
-          <para>§Ú¹q¸£¤W¥i¥H¦³¦h­«§@·~¨t²Î¶Ü¡H</para>
-        </question>
-
-        <answer>
-          <para>¥i¥H§r¡A½Ð°Ñ¾\
-            <ulink url="&url.articles.multi-os;/index.html">
-            ¦h­«§@·~¨t²Î</ulink> ³o½g¤å³¹¡C</para>
-        </answer>
-      </qandaentry>
-
-      <qandaentry>
         <question id="windows-coexist">
           <para>&windows; ¥i¥H»P FreeBSD ¦@¦s©ó¹q¸£¤W¶Ü¡H</para>
         </question>
@@ -4501,18 +4489,6 @@ device sio5 at isa? port 0x2b8 tty flags 0x501 vector siointr</programlisting>
 
     <qandaset>
       <qandaentry>
-        <question id="adding-disks">
-          <para>¦p¦ó¦b FreeBSD ¤º§â·sµwºÐ±¾¤W¥h¥Î©O¡H</para>
-        </question>
-
-        <answer>
-          <para>½Ð°Ñ¾\<ulink
-            url="&url.articles.formatting-media;/index.html">
-            ºÏºÐ®æ¦¡¤Æ±Ð¾Ç</ulink>¡C</para>
-        </answer>
-      </qandaentry>
-
-      <qandaentry>
         <question id="new-huge-disk">
           <para>§Ú­n«ç»ò§â§Úªº¨t²Î·h¨ì·sµwºÐ¤W­±¥h¡H</para>
         </question>
@@ -4534,10 +4510,7 @@ device sio5 at isa? port 0x2b8 tty flags 0x501 vector siointr</programlisting>
             and &man.disklabel.8;.  You should also install booteasy
             on both disks with &man.boot0cfg.8;, so that you can
             dual boot to the old or new system after the copying
-            is done.  See the <ulink
-            url="&url.articles.formatting-media;/index.html">
-            formatting-media article</ulink> for details on this
-            process.</para>
+            is done.</para>
 
           <para>Now you have the new disk set up, and are ready
             to move the data.  Unfortunately, you cannot just blindly
diff --git a/zh_TW.Big5/htdocs/docs/books.sgml b/zh_TW.Big5/htdocs/docs/books.sgml
index 4796dbd8dc..6f52a3f54d 100644
--- a/zh_TW.Big5/htdocs/docs/books.sgml
+++ b/zh_TW.Big5/htdocs/docs/books.sgml
@@ -94,11 +94,6 @@
 
 	<!-- ¤å³¹ªº³¡¥÷¬O¥H¥Ø¿ý¦WºÙ§@¬°±Æ§Ç¤§¨Ì¾Ú -->
 
-	    <p><a href="&url.en.articles;/5-roadmap/index.html">The
-	      Roadmap for 5-STABLE</a> (5-roadmap)<br/>
-	      ´y­z 5-STABLE ¤À¤äªº¤¤µ{¶}µo¥H¤Î release engineering ¾úµ{¡C
-	      ¥»¤å¥D­n¬Oµ¹¦³¦Ò¥j°g°Ñ¦Ò¡C</p>
-
 	    <p><a href="&url.en.articles;/bsdl-gpl/index.html">Why you should use
               a BSD style license for your Open Source Project</a> (bsdl-gpl)
 	      <br/> ¤¶²Ð¨Ï¥Î BSD license §@¬°ÄÀ¥X­ì©l½Xªº¦n³B¡C</p>
@@ -110,11 +105,6 @@
 	    <p><a href="&url.en.articles;/casestudy-argentina.com/index.html">®×¨Ò¬ã¨s¡GArgentina.com</a> (casestudy-argentina.com)<br/>
 	      ¦p¦ó¹B¥Î FreeBSD ¦¨¬°©Ô¤B¬ü¬wªº¤j«¬ ISP¡C</p>
 
-	    <p><a href="&url.en.articles;/checkpoint/index.html">Checkpoint VPN-1/Firewall-1 »P FreeBSD IPsec ªº¾ã¦X</a>
-	      (checkpoint)<br/>
-	      ¦p¦ó½Õ¾ã Checkpoint ªº VPN-1/Firewall-1 ²£«~»P FreeBSD ªº IPsec
-	      ¡C</p>
-
 	    <p><a href="&url.en.articles;/committers-guide/index.html">The
 	      Committer's Guide</a> (committers-guide)<br/>
 	      Ãö©ó FreeBSD committer ªº¶·ª¾¨Æ©y¡C</p>
@@ -145,18 +135,6 @@
 	      Advanced Points</a> (cvsup-advanced)<br/>
 	      ¤¶²Ð CVSup ªº©_§Þ²]¥©¡C</p>
 
-	    <p><a href="&url.en.articles;/dialup-firewall/index.html">Dialup
-	      firewalling with FreeBSD</a> (dialup-firewall)<br/>
-	      ¦p¦ó¥H ipfw ¨Ó«Ø¥ß¹ï PPP ¼·±µ³s½u¡B°ÊºA¤À°t IP ªº¨¾¤õÀð¡C</p>
-
-	    <p><a href="&url.en.articles;/diskless-x/index.html">Creating
-	      a diskless X server</a> (diskless-x)<br/>
-	      ¦p¦ó«Ø¥ßµLºÏºÐªº X server¡C</p>
-
-	    <p><a href="&url.en.articles;/euro/article.html">The Euro symbol
-	      on FreeBSD</a> (euro)<br/>
-	      ³]©wÅý FreeBSD ¤Î¬ÛÃö³nÅé¯à¥¿½TÅã¥Ü¼Ú¤¸³f¹ô²Å¸¹¡C</p>
-
 	    <p><a href="&url.en.articles;/explaining-bsd/index.html">Explaining
 	      BSD</a> (explaining-bsd)<br/>
 	      ¸ÑÄÀ ``What is BSD? (¦ó¬° BSD¡H)''</p>
@@ -174,10 +152,6 @@
 	      FreeBSD</a> (fonts)<br/>
 	      ¤¶²Ð FreeBSD ªº¦UºØ¦r«¬§Þ³N¡A¥H¤Î¦b¦UºØµ{¦¡¤W¦p¦ó¹B¥Î¤§¡C</p>
 
-	    <p><a href="&url.en.articles;/formatting-media/index.html">Formatting
-	      media on FreeBSD</a> (formatting-media)<br/>
-	      ¦p¦ó¦b FreeBSD ¤W¤À³Î¡B®æ¦¡¤ÆµwºÐ¡BÀH¨­ºÐ¡B¥úºÐµ¥¡C</p>
-
 	    <p><a href="&url.articles;/freebsd-questions/index.html">How to get
 	      the best results from the FreeBSD-questions mailing list</a>
 	      (freebsd-questions)<br/>
@@ -187,11 +161,6 @@
 	      a GEOM Class</a>(geom-class)<br/>
 	      ¤¶²Ð GEOM ¤º³¡²Ó¸`¡A¨Ã¦p¦ó¼¶¼g class¡C</p>
 
-	    <p><a href="&url.en.articles;/hats/index.html">Working with Hats</a>
-	      (hats)<br/>
-	      A committer's guide to working with ``hats'' (¦b FreeBSD
-	      ªº¯S©w»â°ì³Q±ÂÅvªº committer)¡C</p>
-
 	    <p><a href="&url.articles;/hubs/index.html">Mirroring FreeBSD</a>
 	      (hubs)
 	      <br/>¦p¦ó¦¨¬° FreeBSD ºô¯¸¡BCVSup server¡BFTP ¯¸µ¥ªº mirror ¯¸
@@ -219,10 +188,6 @@
 	      (mh)<br/>
 	      ¤¶²Ð¦p¦ó¦b FreeBSD ¤W¨Ï¥Î MH µ{¦¡¨Ó¦¬µo«H¡C</p>
 
-	    <p><a href="&url.en.articles;/multi-os/index.html">Using
-	      FreeBSD with other operating systems</a> (multi-os)<br/>
-	      ¦p¦ó¦b¦P¤@¥x¹q¸£¤W¦w¸Ë FreeBSD ¥H¤Î¨ä¥L§@·~¨t²Î¡C</p>
-
 	    <p><a href="&url.articles;/nanobsd/index.html">Introduction
               to NanoBSD</a> (nanobsd)<br/>
 	      ¤¶²Ð NanoBSD ¬ÛÃö¤u¨ã¡A¹³¬O«Ø¥ß FreeBSD ¨t²Î image¡A¨Ã¸Ë¨ì
@@ -297,31 +262,10 @@
 	      and Solid State Devices</a> (solid-state)<br/>
 	      ¦b FreeBSD ¤W¨Ï¥Î SSD(Solid State Disk¡A©TºAµwºÐ)¡C</p>
 
-	    <p><a href="&url.en.articles;/storage-devices/index.html">Storage Devices</a>
-	      (storage-devices)<br/>
-	      ¤¶²Ð¦p¦ó¦b FreeBSD ¨Ï¥ÎÀx¦s³]³Æªº²Ó¸`¸ê°T¡A¥]¬A ESDI µwºÐ¡B
-	      SCSI µwºÐ¡BºÏ±a¾÷¥H¤Î¥úºÐ¾÷¡C</p>
-
-	    <p><a href="&url.en.articles;/version-guide/index.html">Choosing the
-	      FreeBSD Version That Is Right For You</a> (version-guide)<br/>
-	      ¦p¦ó¿ï¾Ü©Ò»Ýªº FreeBSD ª©¥»¡C  °Q½×¥DÃD¥]¬A release¡B¤À¤ä¡B
-	      -CURRENT ¤Î -STABLE ªº®t²§¡A¥H¤Î¥Ø«e FreeBSD ­p¹º©Ò³W¹ºªº¥Ø¼Ð
-	      ¡C</p>
-
-	    <p><a href="&url.en.articles;/vinum/index.html">Bootstrapping
-	      Vinum: A Foundation for Reliable Servers</a> (vinum)<br/>
-	      ¤¶²Ð¨ã¦³®e¿ù¾÷¨î(failure-resilient)ªº server
-	      ¡A¥H¤Î³v¨B»¡©ú¦p¦ó¥H Vinum ¨Ó«Ø¥ß¤§¡C</p>
-
 	    <p><a href="&url.en.articles;/vm-design/index.html">Design
 	      elements of the FreeBSD VM system</a> (vm-design)<br/>
 	      ¥Ñ²L¤J²`¤¶²Ð FreeBSD µêÀÀ°O¾ÐÅé(Virtual Memory)¾÷¨îªº³]­p¡C</p>
 
-	    <p><a href="&url.en.articles;/zip-drive/index.html">Zip-drives
-	      and FreeBSD</a> (zip-drive)<br/>
-	      ¦p¦ó¦b FreeBSD ¤W®æ¦¡¤Æ¡B±¾¸ü¡B¹B¥Î Iomega Zip (SCSI¡BIDE¡B
-	      parallel ¬É­±)ºÏºÐ¾÷¡C</p>
-
 
     <h2>¥¦¤s¤§¥Û</h2>
 
diff --git a/zh_TW.Big5/share/sgml/news.xml b/zh_TW.Big5/share/sgml/news.xml
index ab035320c6..4f786f1a80 100644
--- a/zh_TW.Big5/share/sgml/news.xml
+++ b/zh_TW.Big5/share/sgml/news.xml
@@ -1326,7 +1326,7 @@ href="http://wikitest.freebsd.org/moin.cgi/SummerOfCode2006">Summer of Code wiki
 	  <title>·s¼W¤å³¹¡G ¦p¦ó¿ï¾Ü FreeBSD ª©¥»</title>
 
 	  <p>·s¼Wªº¤@½g¤å³¹¡A<a
-	    href="&enbase;/doc/en_US.ISO8859-1/articles/version-guide/">
+	    href="http://docs.freebsd.org/doc/9.0-RELEASE/usr/share/doc/freebsd/en_US.ISO8859-1/articles/version-guide/index.html">
 	    ¿ï¾Ü¾A¦X±zªº FreeBSD ª©¥»</a>¡A
 	    °Q½×¤F¿ï¾Ü³Ì¾A¦X¨ãÅéÀ³¥Îªº FreeBSD ª©¥»®É©Ò»Ý­n¦Ò¼{ªº°ÝÃD¡C
 	    ¨ä¤¤¥]¬Aµo¦æª©»P¤À¤ä¡A¥H¤Î FreeBSD-STABLE ©M
diff --git a/zh_TW.Big5/share/sgml/urls.ent b/zh_TW.Big5/share/sgml/urls.ent
index 4f3bfb2ed0..29e8b5eff2 100644
--- a/zh_TW.Big5/share/sgml/urls.ent
+++ b/zh_TW.Big5/share/sgml/urls.ent
@@ -84,14 +84,10 @@
 
 <!-- for doc//langcode//articles -->
 
-<!ENTITY url.articles.5-roadmap		"&url.doc.langbase;/articles/5-roadmap">
-<!ENTITY url.articles.5-roadmap.en	"&url.doc.langbase.en;/articles/5-roadmap">
 <!ENTITY url.articles.bsdl-gpl		"&url.doc.langbase;/articles/bsdl-gpl">
 <!ENTITY url.articles.bsdl-gpl.en	"&url.doc.langbase.en;/articles/bsdl-gpl">
 <!ENTITY url.articles.building-products	"&url.doc.langbase;/articles/building-products">
 <!ENTITY url.articles.building-products.en	"&url.doc.langbase.en;/articles/building-products">
-<!ENTITY url.articles.checkpoint	"&url.doc.langbase;/articles/checkpoint">
-<!ENTITY url.articles.checkpoint.en	"&url.doc.langbase.en;/articles/checkpoint">
 <!ENTITY url.articles.committers-guide	"&url.doc.langbase;/articles/committers-guide">
 <!ENTITY url.articles.committers-guide.en	"&url.doc.langbase.en;/articles/committers-guide">
 <!ENTITY url.articles.console-server	"&url.doc.langbase;/articles/console-server">
@@ -106,12 +102,6 @@
 <!ENTITY url.articles.cvs-freebsd.en	"&url.doc.langbase.en;/articles/cvs-freebsd">
 <!ENTITY url.articles.cvsup-advanced	"&url.doc.langbase;/articles/cvsup-advanced">
 <!ENTITY url.articles.cvsup-advanced.en	"&url.doc.langbase.en;/articles/cvsup-advanced">
-<!ENTITY url.articles.dialup-firewall	"&url.doc.langbase;/articles/dialup-firewall">
-<!ENTITY url.articles.dialup-firewall.en	"&url.doc.langbase.en;/articles/dialup-firewall">
-<!ENTITY url.articles.diskless-x	"&url.doc.langbase;/articles/diskless-x">
-<!ENTITY url.articles.diskless-x.en	"&url.doc.langbase.en;/articles/diskless-x">
-<!ENTITY url.articles.euro		"&url.doc.langbase;/articles/euro">
-<!ENTITY url.articles.euro.en		"&url.doc.langbase.en;/articles/euro">
 <!ENTITY url.articles.explaining-bsd	"&url.doc.langbase;/articles/explaining-bsd">
 <!ENTITY url.articles.explaining-bsd.en	"&url.doc.langbase.en;/articles/explaining-bsd">
 <!ENTITY url.articles.fbsd-from-scratch	"&url.doc.langbase;/articles/fbsd-from-scratch">
@@ -120,12 +110,8 @@
 <!ENTITY url.articles.filtering-bridges.en	"&url.doc.langbase.en;/articles/filtering-bridges">
 <!ENTITY url.articles.fonts		"&url.doc.langbase;/articles/fonts">
 <!ENTITY url.articles.fonts.en		"&url.doc.langbase.en;/articles/fonts">
-<!ENTITY url.articles.formatting-media	"&url.doc.langbase;/articles/formatting-media">
-<!ENTITY url.articles.formatting-media.en	"&url.doc.langbase.en;/articles/formatting-media">
 <!ENTITY url.articles.freebsd-questions	"&url.doc.langbase;/articles/freebsd-questions">
 <!ENTITY url.articles.freebsd-questions.en	"&url.doc.langbase.en;/articles/freebsd-questions">
-<!ENTITY url.articles.hats		"&url.doc.langbase;/articles/hats">
-<!ENTITY url.articles.hats.en		"&url.doc.langbase.en;/articles/hats">
 <!ENTITY url.articles.hubs		"&url.doc.langbase;/articles/hubs">
 <!ENTITY url.articles.hubs.en		"&url.doc.langbase.en;/articles/hubs">
 <!ENTITY url.articles.ipsec-must	"&url.doc.langbase;/articles/ipsec-must">
@@ -138,8 +124,6 @@
 <!ENTITY url.articles.mailing-list-faq.en	"&url.doc.langbase.en;/articles/mailing-list-faq">
 <!ENTITY url.articles.mh		"&url.doc.langbase;/articles/mh">
 <!ENTITY url.articles.mh.en		"&url.doc.langbase.en;/articles/mh">
-<!ENTITY url.articles.multi-os		"&url.doc.langbase;/articles/multi-os">
-<!ENTITY url.articles.multi-os.en	"&url.doc.langbase.en;/articles/multi-os">
 <!ENTITY url.articles.nanobsd		"&url.doc.langbase;/articles/nanobsd">
 <!ENTITY url.articles.nanobsd.en	"&url.doc.langbase.en;/articles/nanobsd">
 <!ENTITY url.articles.new-users		"&url.doc.langbase;/articles/new-users">
@@ -166,13 +150,5 @@
 <!ENTITY url.articles.serial-uart.en	"&url.doc.langbase.en;/articles/serial-uart">
 <!ENTITY url.articles.solid-state	"&url.doc.langbase;/articles/solid-state">
 <!ENTITY url.articles.solid-state.en	"&url.doc.langbase.en;/articles/solid-state">
-<!ENTITY url.articles.storage-devices	"&url.doc.langbase;/articles/storage-devices">
-<!ENTITY url.articles.storage-devices.en	"&url.doc.langbase.en;/articles/storage-devices">
-<!ENTITY url.articles.version-guide		"&url.doc.langbase;/articles/version-guide">
-<!ENTITY url.articles.version-guide.en		"&url.doc.langbase.en;/articles/version-guide">
-<!ENTITY url.articles.vinum		"&url.doc.langbase;/articles/vinum">
-<!ENTITY url.articles.vinum.en		"&url.doc.langbase.en;/articles/vinum">
 <!ENTITY url.articles.vm-design		"&url.doc.langbase;/articles/vm-design">
 <!ENTITY url.articles.vm-design.en	"&url.doc.langbase.en;/articles/vm-design">
-<!ENTITY url.articles.zip-drive		"&url.doc.langbase;/articles/zip-drive">
-<!ENTITY url.articles.zip-drive.en	"&url.doc.langbase.en;/articles/zip-drive">