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
@@ -1448,19 +1448,6 @@ $FreeBSDde$
         </answer>
       </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>
@@ -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
@@ -1348,18 +1348,6 @@ File: +DESC (ignored)</screen>
 	</answer>
       </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>
@@ -5195,18 +5183,6 @@ kern.sched.name: 4BSD</screen>
     <title>������, ��������� ������� ��� �������� ���������</title>
 
     <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>
@@ -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
@@ -1309,19 +1309,6 @@
 	</answer>
       </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>
@@ -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/>
@@ -141,13 +133,6 @@
 	  Comment FreeBSD a aid� un important FAI en
 	  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/>
@@ -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/>
@@ -234,13 +202,6 @@
 	  sous FreeBSD et comment les utiliser avec diff�rents
 	  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
@@ -249,13 +210,6 @@
 	  chances d'obtenir des informations utiles sur la liste de
 	  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/>
@@ -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>
@@ -405,31 +351,6 @@
 	  L'utilisation des p�riph�riques disques
 	  &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>
@@ -437,12 +358,6 @@
 	  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
@@ -1651,22 +1651,6 @@
 	</answer>
       </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�
@@ -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
@@ -145,12 +145,6 @@
       Hogyan seg�tett a &os; egy nagy latin-amerikai
       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/>
@@ -219,27 +213,6 @@
       N�h�ny tipp, hogyan haszn�ljuk ki a CVSup
       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/>
@@ -271,14 +244,6 @@
       tartoz� technol�gi�kr�l �s azok
       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/>
@@ -301,13 +266,6 @@
       part�ci�k l�trehoz�s�t otthoni
       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/>
@@ -367,13 +325,6 @@
       Bevezet�s az MH e-mail olvas� szoftver
       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/>
@@ -507,33 +458,6 @@
       Solid state lemezeszk�z�k haszn�lata a
       &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/>
@@ -541,13 +465,6 @@
       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; ���ɤ�Dz�������</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"/> ���ɤ�Dz�������
-      �������Υϡ��ɥǥ������� 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)
-          �ϺǤ��®�������dz�ĥ����⤯��
-          �����ƺǤ����ʥ��󥿥ե������Ǥ���
-          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
@@ -1534,19 +1534,6 @@ File: +DESC (ignored)</screen>
         </answer>
       </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>
@@ -6316,17 +6303,6 @@ device sio5 at isa? port 0x2b8 tty flags 0x501 vector siointr</programlisting>
         </answer>
       </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>
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">
 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">
 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
@@ -1563,16 +1563,6 @@ File: +DESC (ignored)</screen>
 	</answer>
       </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>
@@ -6595,20 +6585,6 @@ device sio5 at isa? port 0x2b8 tty flags 0x501 vector siointr</programlisting>
 	Loaders</foreignphrase>)</title>
 
     <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
@@ -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
@@ -1325,19 +1325,6 @@
 	</answer>
       </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>
@@ -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
@@ -121,24 +121,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>
@@ -178,28 +160,6 @@
       Detaylar�</a> (<tt>cvsup-advanced</tt>)<br>
       <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>
@@ -231,14 +191,6 @@
 	bunlar�n de&eth;i�ik programlar ile nas�l
 	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
@@ -247,14 +199,6 @@
       nas�l al�nabilece&eth;i
       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>
@@ -288,15 +232,6 @@
       <small>MH mail okuma program�n�n FreeBSD 'de
 	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>
@@ -379,23 +314,6 @@
       kullan�ld�&eth;�
       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>
@@ -403,16 +321,6 @@
       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
@@ -1240,18 +1240,6 @@ File: +DESC (ignored)</screen>
         </answer>
       </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>
@@ -4500,18 +4488,6 @@ device sio5 at isa? port 0x2b8 tty flags 0x501 vector siointr</programlisting>
     <title>�w�СB�ɮרt�ΡBBoot Loader</title>
 
     <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>
@@ -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">