New translations

9 files changed, 1454 insertions, 3 deletions

diff --git a/release/doc/fr_FR.ISO8859-1/installation/Makefile b/release/doc/fr_FR.ISO8859-1/installation/Makefile
index 8591f7d..81b8b63 100644
--- a/release/doc/fr_FR.ISO8859-1/installation/Makefile
+++ b/release/doc/fr_FR.ISO8859-1/installation/Makefile
@@ -4,12 +4,14 @@
 #
 #      $Id$
 #      $FreeBSD$
-#      Original revision: 1.2
+#      Original revision: 1.4
 
 RELN_ROOT?= ${.CURDIR}/../..
 
 SUBDIR = alpha
 SUBDIR+= i386
+SUBDIR+= pc98
+SUBDIR+= sparc64
 
 .include "${RELN_ROOT}/share/mk/doc.relnotes.mk"
 .include "${DOC_PREFIX}/share/mk/doc.project.mk"
diff --git a/release/doc/fr_FR.ISO8859-1/installation/common/install.sgml b/release/doc/fr_FR.ISO8859-1/installation/common/install.sgml
index 310f63a..f18a434 100644
--- a/release/doc/fr_FR.ISO8859-1/installation/common/install.sgml
+++ b/release/doc/fr_FR.ISO8859-1/installation/common/install.sgml
@@ -12,7 +12,7 @@ from {alpha,i386}/INSTALL.TXT.
 -->
 
 <sect1>
-  <title>Installation de &os;</title>
+  <title>***En cours de traduction***Installation de &os;</title>
 
   <para>Cette sections documente le processus pour l'installation 
   d'une nouvelle version de &os;. Ces instructions mettent un accent
@@ -96,7 +96,7 @@ from {alpha,i386}/INSTALL.TXT.
 
     <para arch="alpha">Vous devez disposer le micro-code de console
     SRM pour cette plateforme. Dans certains cas, il est possible
-    de changer les micro-code AlphaBIOS (ou ARC) et SRM. Dans les
+    de changer les micro-codes AlphaBIOS (ou ARC) et SRM. Dans les
     autres cas il est n&eacute;cessaire de t&eacute;l&eacute;charger le nouveau
     micro-code depuis le site Web du constructeur.</para>
 
diff --git a/release/doc/fr_FR.ISO8859-1/installation/common/trouble.sgml b/release/doc/fr_FR.ISO8859-1/installation/common/trouble.sgml
new file mode 100644
index 0000000..96abb76
--- /dev/null
+++ b/release/doc/fr_FR.ISO8859-1/installation/common/trouble.sgml
@@ -0,0 +1,535 @@
+<!--
+     The FreeBSD Documentation Project
+     The FreeBSD French Documentation Project
+
+     $Id$
+     $FreeBSD$
+     Original revision: 1.5
+
+	This file contains the comments of the old TROUBLE.TXT file.
+-->
+<sect1 id="trouble">
+  <title>***Non traduit***Troubleshooting</title>
+
+  <sect2 id="repairing">
+    <title>Repairing an Existing &os; Installation</title>
+
+    <para>&os; features a
+    <quote>Fixit</quote> option in the top menu of the boot floppy.
+    To use it, you will also need either a
+    <filename>fixit.flp</filename> image floppy, generated in the same
+    fashion as the boot floppy, or the <quote>live filesystem</quote>
+    CDROM; typically the second CDROM in a multi-disc &os; 
+    distribution.</para>
+
+    <para>To invoke fixit, simply boot the
+    <filename>kern.flp</filename> floppy, choose the
+    <quote>Fixit</quote> item and insert the fixit floppy or CDROM
+    when asked.  You will then be placed into a shell with a wide
+    variety of commands available (in the <filename>/stand</filename>
+    and <filename>/mnt2/stand</filename> directories) for checking,
+    repairing and examining filesystems and their contents.  Some
+    UNIX administration experience <emphasis>is</emphasis> required to
+    use the fixit option.</para>
+  </sect2>
+
+  <sect2>
+    <title>Common Installation Problems, Q&amp;A</title>
+
+    <qandaset>
+      <qandaentry>
+        <question>
+          <para>I go to boot from the hard disk for the first time
+          after installing &os;, the kernel loads and probes my
+          hardware, but stops with messages like:</para>
+
+          <screen>changing root device to wd1s1a panic: cannot mount root</screen>
+          <para>What is wrong?  What can I do?</para>
+
+          <para>What is this
+          <literal>bios_drive:interface(unit,partition)kernel_name</literal>
+          thing that is displayed with the boot help?</para>
+        </question>
+        <answer>
+          <para>There is a longstanding problem in the case where the
+          boot disk is not the first disk in the system.  The BIOS
+          uses a different numbering scheme to &os;, and working
+          out which numbers correspond to which is difficult to get
+          right.</para>
+
+          <para>In the case where the boot disk is not the first disk
+          in the system, &os; can need some help finding it.  There
+          are two common situations here, and in both of these cases,
+          you need to tell &os; where the root filesystem is.  You
+          do this by specifying the BIOS disk number, the disk type
+          and the &os; disk number for that type.</para>
+
+          <para>The first situation is where you have two IDE disks,
+          each configured as the master on their respective IDE
+          busses, and wish to boot &os; from the second disk.  The
+          BIOS sees these as disk 0 and disk 1, while &os; sees
+          them as <devicename>wd0</devicename> and
+          <devicename>wd2</devicename>.</para>
+
+          <para>&os; is on BIOS disk 1, of type
+          <literal>wd</literal> and the &os; disk number is 2, so
+          you would say:</para>
+
+          <screen><userinput>1:wd(2,a)kernel</userinput></screen>
+
+          <para>Note that if you have a slave on the primary bus, the
+          above is not necessary (and is effectively wrong).</para>
+
+          <para>The second situation involves booting from a SCSI disk
+          when you have one or more IDE disks in the system.  In this
+          case, the &os; disk number is lower than the BIOS disk
+          number.  If you have two IDE disks as well as the SCSI disk,
+          the SCSI disk is BIOS disk 2, type <literal>da</literal> and
+          &os; disk number 0, so you would say:</para>
+
+          <screen><userinput>2:da(0,a)kernel</userinput></screen>
+
+          <para>To tell &os; that you want to boot from BIOS disk
+          2, which is the first SCSI disk in the system.  If you only
+          had one IDE disk, you would use '1:' instead.</para>
+
+          <para>Once you have determined the correct values to use,
+          you can put the command exactly as you would have typed it
+          in the <filename>/boot.config</filename> file using a
+          standard text editor.  Unless instructed otherwise, &os;
+          will use the contents of this file as the default response
+          to the <literal>boot:</literal> prompt.</para>
+        </answer>
+      </qandaentry>
+      <qandaentry>
+        <question>
+	  <para>I go to boot from the hard disk for the first time
+          after installing &os;, but the Boot Manager prompt just
+          prints <literal>F?</literal> at the boot menu each time but
+          the boot won't go any further.</para>
+	</question>
+	<answer>
+          <para>The hard disk geometry was set incorrectly in the
+          Partition editor when you installed &os;.  Go back into
+          the partition editor and specify the actual geometry of your
+          hard disk.  You must reinstall &os; again from the
+          beginning with the correct geometry.</para>
+
+          <para>If you are failing entirely in figuring out the
+	  correct geometry for your machine, here's a tip: Install a
+	  small DOS partition at the beginning of the disk and install
+	  &os; after that.  The install program will see the DOS
+	  partition and try to infer the correct geometry from it,
+	  which usually works.</para>
+
+	  <para>The following tip is no longer recommended, but is left here
+	  for reference:</para>
+
+	  <blockquote>
+            <para>If you are setting up a truly dedicated &os;
+	    server or workstation where you don't care for (future)
+	    compatibility with DOS, Linux or another operating system,
+	    you've also got the option to use the entire disk (`A' in
+	    the partition editor), selecting the non-standard option
+	    where &os; occupies the entire disk from the very first
+	    to the very last sector.  This will leave all geometry
+	    considerations aside, but is somewhat limiting unless
+	    you're never going to run anything other than &os; on a
+	    disk.</para>
+	  </blockquote>
+ 	</answer>
+      </qandaentry>
+    </qandaset>
+  </sect2>
+  <sect2>
+    <title>Known Hardware Problems, Q&amp;A</title>
+
+    <note>
+      <para>Please send hardware tips for this section to &a.jkh;.</para>
+    </note>
+
+    <qandaset>
+      <qandaentry>
+        <question>
+	  <para>The &man.mcd.4; driver keeps thinking that it has
+	  found a device and this stops my Intel EtherExpress card
+	  from working.</para>
+	</question>
+	<answer>
+	  <para>Use the UserConfig utility (see
+          <filename>HARDWARE.TXT</filename>) and disable the probing
+          of the <devicename>mcd0</devicename> and
+          <devicename>mcd1</devicename> devices.  Generally speaking,
+          you should only leave the devices that you will be using
+          enabled in your kernel.</para>
+	</answer>
+      </qandaentry>
+      <qandaentry>
+        <question>
+	  <para>&os; claims to support the 3Com PCMCIA card, but my
+	  card isn't recognized when it's plugged into my
+	  laptop.</para>
+	</question>
+	<answer>
+	  <para>There are a couple of possible problems.  First of
+	  all, &os; does not support multi-function cards, so if
+	  you have a combo Ethernet/modem card (such as the 3C562), it
+	  won't work.  The default driver for the 3C589 card was
+	  written just like all of the other drivers in &os;, and
+	  depend on the card's own configuration data stored in NVRAM
+	  to work.  You must correctly configure &os;'s driver to
+	  match the IRQ, port, and IOMEM stored in NVRAM.</para>
+
+	  <para>Unfortunately, the only program capable of reading
+	  them is the 3COM supplied DOS program.  This program must be
+	  run on a absolutely clean system (no other drivers must be
+	  running), and the program will whine about CARD-Services not
+	  being found, but it will continue.  This is necessary to
+	  read the NVRAM values.  You want to know the IRQ, port, and
+	  IOMEM values (the latter is called the CIS tuple by 3COM).
+	  The first two can be set in the program, the third is
+	  un-settable, and can only be read.  Once you have these
+	  values, set them in UserConfig and your card will be
+	  recognized.</para>
+	</answer>
+      </qandaentry>
+      <qandaentry>
+        <question>
+	  <para>&os; finds my PCMCIA network card, but no packets
+	  appear to be sent even though it claims to be working.</para>
+	</question>
+	<answer>
+	  <para>Many PCMCIA cards have the ability to use either the
+	  10-Base2 (BNC) or 10-BaseT connectors for connecting to the
+	  network.  The driver is unable to <quote>auto-select</quote>
+	  the correct connector, so you must tell it which connector
+	  to use. In order to switch between the two connectors, the
+	  link flags must be set.  Depending on the model of the card,
+	  <option>-link0 link1</option> or <option>-link0
+	  -link1</option> will choose the correct network connector.
+	  You can set these in &man.sysinstall.8; by using the
+	  <literal>Extra options to ifconfig:</literal> field in the
+	  network setup screen.</para>
+	</answer>
+      </qandaentry>
+      <qandaentry>
+        <question>
+	  <para>The system finds my &man.ed.4; network card, but I
+          keep getting device timeout errors.</para>
+	</question>
+	<answer>
+	  <para>Your card is probably on a different IRQ from what is
+	  specified in the kernel configuration.  The ed driver does
+	  not use the `soft' configuration by default (values entered
+	  using EZSETUP in DOS), but it will use the software
+	  configuration if you specify <literal>?</literal> in the IRQ field of your
+	  kernel config file.</para>
+
+	  <para>Either move the jumper on the card to a hard
+          configuration setting (altering the kernel settings if
+          necessary), or specify the IRQ as <literal>-1</literal> in UserConfig or <literal>?</literal> 
+          in your kernel config file.  This will tell the kernel to
+          use the soft configuration.</para>
+
+          <para>Another possibility is that your card is at IRQ 9,
+          which is shared by IRQ 2 and frequently a cause of problems
+          (especially when you have a VGA card using IRQ 2!).  You
+          should not use IRQ 2 or 9 if at all possible.</para>
+	</answer>
+      </qandaentry>
+      <qandaentry>
+        <question>
+	  <para>I have a Matsushita/Panasonic drive but it isn't
+	  recognized by the system.</para>
+	</question>
+	<answer>
+	  <para>Make certain that the I/O port that the &man.matcd.4; driver
+          is set to is correct for the host interface card you have.
+          (Some SoundBlaster DOS drivers report a hardware I/O port
+          address for the CD-ROM interface that is 0x10 lower than it
+          really is.)</para>
+
+          <para>If you are unable to determine the settings for the
+          card by examining the board or documentation, you can use
+          UserConfig to change the 'port' address (I/O port) to -1 and
+          start the system.  This setting causes the driver to look at
+          a number of I/O ports that various manufacturers use for
+          their Matsushita/Panasonic/Creative CD-ROM interfaces.  Once
+          the driver locates the address, you should run UserConfig
+          again and specify the correct address.  Leaving the 'port'
+          parameter set to -1 increases the amount of time that it
+          takes the system to boot, and this could interfere with
+          other devices.</para>
+
+          <para>The double-speed Matsushita CR-562 and CR-563 are the
+          only drives that are supported.</para>
+	</answer>
+      </qandaentry>
+      <qandaentry>
+        <question>
+	  <para>I booted the install floppy on my IBM ThinkPad (tm)
+          laptop, and the keyboard is all messed up.</para>
+	</question>
+	<answer>
+          <para>Older IBM laptops use a non-standard keyboard
+          controller, so you must tell the keyboard driver (atkbd0) to
+          go into a special mode which works on the ThinkPads.  Change
+          the atkbd0 'Flags' to 0x4 in UserConfig and it should work
+          fine.  (Look in the Input Menu for 'Keyboard'.)</para>
+	</answer>
+      </qandaentry>
+      <qandaentry>
+        <question>
+	  <para>When I try to boot the install floppy, I see the
+          following message and nothing seems to be happening.  I
+          cannot enter anything from the keyboard either.</para>
+
+          <screen>Keyboard: no</screen>
+	</question>
+	<answer>
+          <para>Due to lack of space, full support for old XT/AT
+	  (84-key) keyboards is no longer available in the bootblocks.
+	  Some notebook computers may also have this type of keyboard.
+	  If you are still using this kind of hardware, you will see
+	  the above message appears when you boot from the CD-ROM or
+	  an install floppy.</para>
+
+          <para>As soon as you see this message, hit the space bar,
+	  and you will see the prompt:</para>
+
+<screen>>> FreeBSD/i386 BOOT
+Default: x:xx(x,x)/boot/loader 
+boot:</screen>
+
+          <para>Then enter <userinput>-Dh</userinput>, and things
+          should proceed normally.</para>
+	</answer>
+      </qandaentry>
+      <qandaentry>
+        <question>
+	  <para>I have a Matsushita/Panasonic CR-522, a
+	  Matsushita/Panasonic CR-523 or a TEAC CD55a drive, but it is
+	  not recognized even when the correct I/O port is set.</para>
+	</question>
+	<answer>
+	<para>These CD-ROM drives are currently not supported by
+	&os;.  The command sets for these drives are not compatible
+	with the double-speed CR-562 and CR-563 drives.</para>
+   
+        <para>The single-speed CR-522 and CR-523 drives can be
+	identified by their use of a CD-caddy. </para>
+	</answer>
+      </qandaentry>
+      <qandaentry>
+        <question>
+	  <para>I'm trying to install from a tape drive but all I get
+	  is something like this on the screen:</para>
+
+	  <screen>sa0(aha0:1:0) NOT READY csi 40,0,0,0</screen>
+	</question>
+	<answer>
+	  <para>There's a limitation in the current &man.sysinstall.8;
+          that the tape <emphasis>must</emphasis> be in the drive
+          while &man.sysinstall.8; is started or it won't be detected.
+          Try again with the tape in the drive the whole time.</para>
+	</answer>
+      </qandaentry>
+      <qandaentry>
+        <question>
+	  <para>I've installed &os; onto my system, but it hangs
+	  when booting from the hard drive with the message:</para>
+
+          <screen>Changing root to /dev/da0a</screen>
+        </question>
+	<answer>
+	  <para>his problem may occur in a system with a 3com 3c509
+          Ethernet adapter.  The &man.ep.4; device driver appears to
+          be sensitive to probes for other devices that also use
+          address 0x300.  Boot your &os; system by power cycling
+          the machine (turn off and on).  At the
+          <literal>Boot:</literal> prompt specify the
+          <option>-c</option>.  This will invoke UserConfig (see
+          <xref linkend="repairing"> above).
+	  Use the <literal>disable</literal>
+          command to disable the device probes for all devices at
+          address 0x300 except the ep0 driver.  On exit, your machine
+          should successfully boot &os;.</para>
+	</answer>
+      </qandaentry>
+      <qandaentry>
+        <question>
+	  <para>My system can not find my Intel EtherExpress 16 card.</para>
+        </question>
+	<answer>
+	  <para>You must set your Intel EtherExpress 16 card to be
+          memory mapped at address 0xD0000, and set the amount of
+          mapped memory to 32K using the Intel supplied
+          <filename>softset.exe</filename> program.</para>
+	</answer>
+      </qandaentry>
+      <qandaentry>
+        <question>
+	  <para>When installing on an EISA HP Netserver, my on-board
+	  AIC-7xxx SCSI controller isn't detected.</para>
+        </question>
+	<answer>
+	  <para>This is a known problem, and will hopefully be fixed
+	  in the future.  In order to get your system installed at
+	  all, boot with the <option>-c</option> option into
+	  UserConfig, but <emphasis>don't</emphasis> use the pretty
+	  visual mode but the plain old CLI mode.  Type:</para>
+
+          <screen><userinput>eisa 12</userinput>
+<userinput>quit</userinput></screen>
+
+          <para>at the prompt.  (Instead of `quit', you might also
+          type `visual', and continue the rest of the configuration
+          session in visual mode.)  While it's recommended to compile
+          a custom kernel, dset now also understands to save
+          this value.</para>
+
+          <para>Refer to the FAQ topic 3.16 for an explanation of the
+          problem, and for how to continue.  Remember that you can
+          find the FAQ on your local system in /usr/share/doc/FAQ,
+          provided you have installed the `doc' distribution.</para>
+	</answer>
+      </qandaentry>
+      <qandaentry>
+        <question>
+	  <para>I have a Panasonic AL-N1 or Rios Chandler Pentium
+          machine and I find that the system hangs before ever getting
+          into the installation now.</para>
+        </question>
+	<answer>
+	  <para>Your machine doesn't like the new
+          <literal>i586_copyout</literal> and
+          <literal>i586_copyin</literal> code for some reason.  To
+          disable this, boot the installation boot floppy and when it
+          comes to the very first menu (the choice to drop into kernel
+          UserConfig mode or not) choose the command-line interface
+          (<quote>expert mode</quote>) version and type the following
+          at it:</para>
+
+          <screen><userinput>flags npx0 1</userinput></screen>
+
+          <para>Then proceed normally to boot.  This will be saved
+          into your kernel, so you only need to do it once.</para>
+	</answer>
+      </qandaentry>
+      <qandaentry>
+        <question>
+	  <para>I have this CMD640 IDE controller that is said to be
+	  broken.</para>
+        </question>
+	<answer>
+	  <para>Yes, it is.  &os; does not support this controller
+          except through the legacy wdc driver.</para>
+	</answer>
+      </qandaentry>
+      <qandaentry>
+        <question>
+	  <para>On a Compaq Aero notebook, I get the message <quote>No
+          floppy devices found!  Please check ...</quote> when trying to
+          install from floppy.</para>
+        </question>
+	<answer>
+	  <para>With Compaq being always a little different from other
+          systems, they do not announce their floppy drive in the CMOS
+          RAM of an Aero notebook.  Therefore, the floppy disk driver
+          assumes there is no drive configured.  Go to the UserConfig
+          screen, and set the Flags value of the fdc0 device to 0x1.
+          This pretends the existence of the first floppy drive (as a
+          1.44 MB drive) to the driver without asking the CMOS at
+          all.</para>
+	</answer>
+      </qandaentry>
+      <qandaentry>
+        <question>
+	  <para>When I go to boot my Intel AL440LX
+          (<quote>Atlanta</quote>) -based system from the hard disk the
+          first time, it stops with a <literal>Read Error</literal>
+          message.</para>
+        </question>
+	<answer>
+	  <para>There appears to be a bug in the BIOS on at least some
+          of these boards, this bug results in the &os; bootloader
+          thinking that it is booting from a floppy disk.  This is
+          only a problem if you are not using the BootEasy boot
+          manager.  Slice the disk in <quote>compatible</quote>mode
+          and install BootEasy during the &os; installation to
+          avoid the bug, or upgrade the BIOS (see Intel's web site for
+          details).</para>
+	</answer>
+      </qandaentry>
+      <qandaentry>
+        <question>
+	  <para>When installing on an Dell Poweredge XE, Dell
+          proprietary RAID controller DSA (Dell SCSI Array) isn't
+          recognized.</para>
+        </question>
+	<answer>
+	  <para>Configure the DSA to use AHA-1540 emulation using EISA
+          configuration utility.  After that &os; detects the DSA
+          as an Adaptec AHA-1540 SCSI controller, with irq 11 and port
+          340. Under emulation mode system will use DSA RAID disks,
+          but you cannot use DSA-specific features such as watching
+          RAID health.</para>
+	</answer>
+      </qandaentry>
+      <qandaentry>
+        <question>
+	  <para>My Ethernet adapter is detected as an AMD PCnet-FAST
+          (or similar) but it doesn't work.  (Eg. onboard Ethernet on
+          IBM Netfinity 5xxx or 7xxx)</para>
+        </question>
+	<answer>
+	  <para>The &man.lnc.4; driver is currently faulty, and will
+          often not work correctly with the PCnet-FAST and
+          PCnet-FAST+.  You need to install a different Ethernet
+          adapter.</para>
+	</answer>
+      </qandaentry>
+      <qandaentry>
+        <question>
+	  <para>I have an IBM EtherJet PCI card, it is detected by the
+          &man.fxp.4; driver correctly, but the lights on the card don't
+          come on and it doesn't connect to the network.</para>
+        </question>
+	<answer>
+	  <para>We don't understand why this happens.  Neither do IBM
+          (we asked them).  The card is a standard Intel EtherExpress
+          Pro/100 with an IBM label on it, and these cards normally
+          work just fine.  You may see these symptoms only in some IBM
+          Netfinity servers.  The only solution is to install a
+          different Ethernet adapter.</para>
+	</answer>
+      </qandaentry>
+      <qandaentry>
+        <question>
+	  <para>When I configure the network during installation on an
+          IBM Netfinity 3500, the system freezes.</para>
+        </question>
+	<answer>
+	  <para>There is a problem with the onboard Ethernet in the
+          Netfinity 3500 which we have not been able to identify at
+          this time.  It may be related to the SMP features of the
+          system being misconfigured.  You will have to install
+          another Ethernet adapter and avoid attempting to configure
+          the onboard adapter at any time.</para>
+	</answer>
+      </qandaentry>
+      <qandaentry>
+        <question>
+	  <para>When I install onto a drive managed by a Mylex PCI
+          RAID controller, the system fails to boot (eg. with a
+          <literal>read error</literal> message).</para>
+        </question>
+	<answer>
+	  <para>There is a bug in the Mylex driver which results in it
+          ignoring the <quote>8GB</quote> geometry mode setting in the
+          BIOS.  Use the 2GB mode instead.</para>
+	</answer>
+      </qandaentry>
+    </qandaset>
+  </sect2>
+</sect1>
diff --git a/release/doc/fr_FR.ISO8859-1/installation/common/upgrade.sgml b/release/doc/fr_FR.ISO8859-1/installation/common/upgrade.sgml
new file mode 100644
index 0000000..b523cce
--- /dev/null
+++ b/release/doc/fr_FR.ISO8859-1/installation/common/upgrade.sgml
@@ -0,0 +1,216 @@
+<!--
+     The FreeBSD Documentation Project
+     The FreeBSD French Documentation Project
+
+     $Id$
+     $FreeBSD$
+     Original revision: 1.7
+	This section contains the contents of the old UPGRADE.TXT
+	file.
+-->
+<sect1 id="upgrading">
+  <title>***Non traduit ***Upgrading &os;</title>
+
+  <para>These instructions describe a procedure for doing a binary
+  upgrade from an older version of &os;.</para>
+
+  <warning>
+    <para>While the &os; upgrade procedure does its best to
+    safeguard against accidental loss of data, it is still more than
+    possible to <emphasis>wipe out your entire disk</emphasis> with
+    this installation!  Please do not accept the final confirmation
+    request unless you have adequately backed up any important data
+    files.</para>
+  </warning>
+
+  <important>
+    <para>These notes assume that you are using the version of
+    &man.sysinstall.8; supplied with the version of &os; to which you
+    intend to upgrade.  Using a mismatched version of &man.sysinstall.8; is
+    almost guaranteed to cause problems and has been known to leave
+    systems in an unusable state.  The most commonly made mistake in
+    this regard is the use of an old copy of &man.sysinstall.8; from
+    an existing installation to upgrade to a newer version of
+    &os;.  This is <emphasis>not</emphasis> recommended.</para>
+  </important>
+
+  <sect2>
+    <title>Introduction</title>
+
+    <para>The upgrade procedure replaces distributions selected by the
+    user with those corresponding to the new &os; release.  It
+    preserves standard system configuration data, as well as user
+    data, installed packages and other software.</para>
+
+    <para>Administrators contemplating an upgrade are encouraged to
+    study this section in its entirety before commencing an upgrade.
+    Failure to do so may result in a failed upgrade or loss of data.</para>
+
+    <sect3>
+      <title>Upgrade Overview</title>
+
+      <para>Upgrading of a distribution is performed by extracting the
+      new version of the component over the top of the previous
+      version.  Files belonging to the old distribution are not
+      deleted.</para>
+
+      <para>System configuration is preserved by retaining and
+      restoring the previous version of the following files:</para>
+
+      <para><filename>Xaccel.ini</filename>,
+<filename>XF86Config</filename>,
+<filename>adduser.conf</filename>,
+<filename>aliases</filename>,
+<filename>aliases.db</filename>,
+<filename>amd.map</filename>,
+<filename>crontab</filename>,
+<filename>csh.cshrc</filename>,
+<filename>csh.login</filename>,
+<filename>csh.logout</filename>,
+<filename>cvsupfile</filename>,
+<filename>dhclient.conf</filename>,
+<filename>disktab</filename>,
+<filename>dm.conf</filename>,
+<filename>dumpdates</filename>,
+<filename>exports</filename>,
+<filename>fbtab</filename>,
+<filename>fstab</filename>,
+<filename>ftpusers</filename>,
+<filename>gettytab</filename>,
+<filename>gnats</filename>,
+<filename>group</filename>,
+<filename>hosts</filename>,
+<filename>hosts.allow</filename>,
+<filename>hosts.equiv</filename>,
+<filename>hosts.lpd</filename>,
+<filename>inetd.conf</filename>,
+<filename>kerberosIV</filename>,
+<filename>localtime</filename>,
+<filename>login.access</filename>,
+<filename>login.conf</filename>,
+<filename>mail</filename>,
+<filename>mail.rc</filename>,
+<filename>make.conf</filename>,
+<filename>manpath.config</filename>,
+<filename>master.passwd</filename>,
+<filename>modems</filename>,
+<filename>motd</filename>,
+<filename>namedb</filename>,
+<filename>networks</filename>,
+<filename>newsyslog.conf</filename>,
+<filename>nsmb.conf</filename>,
+<filename>nsswitch.conf</filename>,
+<filename>pam.conf</filename>,
+<filename>passwd</filename>,
+<filename>periodic</filename>,
+<filename>ppp</filename>,
+<filename>printcap</filename>,
+<filename>profile</filename>,
+<filename>pwd.db</filename>,
+<filename>rc.conf</filename>,
+<filename>rc.conf.local</filename>,
+<filename>rc.firewall</filename>,
+<filename>rc.local</filename>,
+<filename>remote</filename>,
+<filename>resolv.conf</filename>,
+<filename>rmt</filename>,
+<filename>sendmail.cf</filename>,
+<filename>sendmail.cw</filename>,
+<filename>services</filename>,
+<filename>shells</filename>,
+<filename>skeykeys</filename>,
+<filename>spwd.db</filename>,
+<filename>ssh</filename>,
+<filename>syslog.conf</filename>,
+<filename>ttys</filename>,
+<filename>uucp</filename>
+</para>
+
+      <para>The versions of these files which correspond to the new
+      version are moved to <filename>/etc/upgrade/</filename>.  The
+      system administrator may peruse these new versions and merge
+      components as desired.  Note that many of these files are
+      interdependent, and the best merge procedure is to copy all
+      site-specific data from the current files into the new.</para>
+
+      <para>During the upgrade procedure, the administrator is
+      prompted for a location into which all files from
+      <filename>/etc/</filename> are saved.  In the event that local
+      modifications have been made to other files, they may be
+      subsequently retrieved from this location.</para>
+
+    </sect3>
+  </sect2>
+
+  <sect2>
+    <title>Procedure</title>
+
+    <para>This section details the upgrade procedure.  Particular
+    attention is given to items which substantially differ from a
+    normal installation.</para>
+
+    <sect3>
+      <title>Backup</title>
+
+      <para>User data and system configuration should be backed up
+      before upgrading.  While the upgrade procedure does its best
+      to prevent accidental mistakes, it is possible to partially or
+      completely destroy data and configuration information.</para>
+    </sect3>
+
+    <sect3>
+      <title>Mount Filesystems</title>
+
+      <para>The disklabel editor is entered with the nominated disk's
+      filesystem devices listed.  Prior to commencing the upgrade, the
+      administrator should make a note of the device names and
+      corresponding mountpoints.  These mountpoints should be entered
+      here.  <emphasis>Do not</emphasis>set the <quote>newfs
+      flag</quote> for any filesystems, as this will cause data
+      loss.</para>
+    </sect3>
+
+    <sect3>
+      <title>Select Distributions</title>
+
+      <para>When selecting distributions, there are no constraints
+      on which must be selected.  As a general rule, the <literal>bin</literal>
+      distribution should be selected for an update, and the <literal>man</literal>
+      distribution if manpages are already installed.  Other
+      distributions may be selected beyond those originally
+      installed if the administrator wishes to add additional
+      functionality.</para>
+    </sect3>
+
+    <sect3 id="fstab">
+      <title>After Installation</title>
+
+      <para>Once the installation procedure has completed, the
+      administrator is prompted to examine the new configuration
+      files.  At this point, checks should be made to ensure that the
+      system configuration is valid.  In particular, the
+      <filename>/etc/rc.conf</filename> and
+      <filename>/etc/fstab</filename> files should be checked.</para>
+    </sect3>
+  </sect2>
+
+  <sect2>
+    <title>Upgrading from Source Code</title>
+
+    <para>Those interested in an upgrade method that allows more
+    flexibility and sophistication should take a look at
+    <ulink
+    url="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/cutting-edge.html">The
+    Cutting Edge</ulink> in the &os; Handbook.  This procedure involves
+    rebuilding all of &os; from source code.  It requires reliable
+    network connectivity, extra disk space, and time, but has
+    advantages for networks and other more complex
+    installations.  This is roughly the same procedure as is used for
+    track the -STABLE or -CURRENT development branches.</para>
+
+    <para><filename>/usr/src/UPDATING</filename> contains important
+    information on updating a &os; system from source code.  It lists
+    various issues resulting from changes in &os; that may affect an
+    upgrade.<para>
+  </sect2>
+</sect1>  
diff --git a/release/doc/fr_FR.ISO8859-1/installation/pc98/Makefile b/release/doc/fr_FR.ISO8859-1/installation/pc98/Makefile
new file mode 100644
index 0000000..6ff53b6
--- /dev/null
+++ b/release/doc/fr_FR.ISO8859-1/installation/pc98/Makefile
@@ -0,0 +1,28 @@
+#
+#     The FreeBSD Documentation Project
+#     The FreeBSD French Documentation Project
+#     $Id$
+#
+#     $FreeBSD$
+#     Original revision: 1.1
+#
+
+
+RELN_ROOT?= ${.CURDIR}/../../..
+
+DOC?= article
+FORMATS?= html
+INSTALL_COMPRESSED?= gz
+INSTALL_ONLY_COMPRESSED?=
+
+# SGML content
+SRCS+=	article.sgml
+SRCS+=	../common/artheader.sgml
+SRCS+=	../common/abstract.sgml
+SRCS+=	../common/install.sgml
+SRCS+=	../common/layout.sgml
+SRCS+=	../common/trouble.sgml
+SRCS+=	../common/upgrade.sgml
+
+.include "${RELN_ROOT}/share/mk/doc.relnotes.mk"
+.include "${DOC_PREFIX}/share/mk/doc.project.mk"
diff --git a/release/doc/fr_FR.ISO8859-1/installation/pc98/article.sgml b/release/doc/fr_FR.ISO8859-1/installation/pc98/article.sgml
new file mode 100644
index 0000000..5e68d6e
--- /dev/null
+++ b/release/doc/fr_FR.ISO8859-1/installation/pc98/article.sgml
@@ -0,0 +1,35 @@
+<!--
+     The FreeBSD Documentation Project
+     The FreeBSD French Documentation Project
+
+     $Id$
+     $FreeBSD$
+     Original revision: 1.1
+-->
+
+<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
+<!ENTITY % man PUBLIC "-//FreeBSD//ENTITIES DocBook Manual Page Entities//EN">
+%man;
+<!ENTITY % authors PUBLIC  "-//FreeBSD//ENTITIES DocBook Author Entities//EN">
+%authors;
+<!ENTITY % mlists PUBLIC "-//FreeBSD//ENTITIES DocBook Mailing List Entities//FR">
+%mlists;
+<!ENTITY % release PUBLIC "-//FreeBSD//ENTITIES Release Specification//EN">
+%release;
+<!ENTITY % sections SYSTEM "../common/install.ent"> %sections;
+
+<!-- Architecture-specific customization -->
+
+<!ENTITY arch "pc98">
+<!ENTITY arch.print "NEC PC-98x1">
+
+]>
+
+<article>
+&artheader;
+&abstract;
+&sect.install;
+&sect.layout;
+&sect.upgrade;
+&sect.trouble;
+</article>
diff --git a/release/doc/fr_FR.ISO8859-1/installation/sparc64/Makefile b/release/doc/fr_FR.ISO8859-1/installation/sparc64/Makefile
new file mode 100644
index 0000000..c3e7481
--- /dev/null
+++ b/release/doc/fr_FR.ISO8859-1/installation/sparc64/Makefile
@@ -0,0 +1,26 @@
+#
+#     The FreeBSD Documentation Project
+#     The FreeBSD French Documentation Project
+#     $Id$
+#
+#     $FreeBSD$
+#     Original revision: 1.1
+#
+
+
+RELN_ROOT?= ${.CURDIR}/../../..
+
+DOC?= article
+FORMATS?= html
+INSTALL_COMPRESSED?= gz
+INSTALL_ONLY_COMPRESSED?=
+
+# SGML content
+SRCS+=	article.sgml
+SRCS+=	install.sgml
+SRCS+=	../common/artheader.sgml
+SRCS+=	../common/install.sgml
+SRCS+=	../common/layout.sgml
+
+.include "${RELN_ROOT}/share/mk/doc.relnotes.mk"
+.include "${DOC_PREFIX}/share/mk/doc.project.mk"
diff --git a/release/doc/fr_FR.ISO8859-1/installation/sparc64/article.sgml b/release/doc/fr_FR.ISO8859-1/installation/sparc64/article.sgml
new file mode 100644
index 0000000..cdbbc68
--- /dev/null
+++ b/release/doc/fr_FR.ISO8859-1/installation/sparc64/article.sgml
@@ -0,0 +1,41 @@
+<!--
+     The FreeBSD Documentation Project
+     The FreeBSD French Documentation Project
+
+     $Id$
+     $FreeBSD$
+     Original revision: 1.3
+-->
+
+<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
+
+<!ENTITY release.url "ftp://ftp.FreeBSD.org/pub/FreeBSD/development/sparc64/">
+
+<!ENTITY % man PUBLIC "-//FreeBSD//ENTITIES DocBook Manual Page Entities//EN">
+%man;
+<!ENTITY % authors PUBLIC  "-//FreeBSD//ENTITIES DocBook Author Entities//EN">
+%authors;
+<!ENTITY % mlists PUBLIC "-//FreeBSD//ENTITIES DocBook Mailing List Entities//FR">
+%mlists;
+<!ENTITY % release PUBLIC "-//FreeBSD//ENTITIES Release Specification//EN">
+%release;
+<!ENTITY % sections SYSTEM "../common/install.ent"> %sections;
+
+<!-- Architecture-specific customization -->
+
+<!ENTITY arch "sparc64">
+<!ENTITY arch.print "UltraSPARC">
+<!ENTITY sect.sparc64.install SYSTEM "./install.sgml">
+]>
+
+<article>
+&artheader;
+<abstract>
+  <para>Ce document donne de brèves instructions sur l'installation
+  de &os;/&arch; &release.current;. Gardez bien à l'esprit que ce
+  portage est en cours, et que en conséquence, la procédure
+  d'installation demande beaucoup plus de travail que pour &os;/i386
+  ou &os;/alpha.</para>
+</abstract>
+&sect.sparc64.install;
+</article>
diff --git a/release/doc/fr_FR.ISO8859-1/installation/sparc64/install.sgml b/release/doc/fr_FR.ISO8859-1/installation/sparc64/install.sgml
new file mode 100644
index 0000000..56270ec
--- /dev/null
+++ b/release/doc/fr_FR.ISO8859-1/installation/sparc64/install.sgml
@@ -0,0 +1,568 @@
+<!--
+     The FreeBSD Documentation Project
+     The FreeBSD French Documentation Project
+
+     $Id$
+     $FreeBSD$
+     Original revision: 1.12
+     Ce fichier contient les instructions pour l'installation
+     specifique aux systemes sparc64.
+
+-->
+
+<sect1>
+  <title>***Non traduit***Installing &os;</title>
+
+  <para>This text describes how to install and boot the &arch; port.
+    Users of this port are encouraged to subscribe to the
+    &a.sparc;.</para>
+
+  <warning>
+    <para>The kernel and userland binaries mentioned below are highly
+      experimental (for example, the kernel contains some ATA changes
+      and EEPROM handling code which could potentially be dangerous).
+      Unless you know what you are doing and are willing to cope with
+      any damage that might arise, you should probably not be trying
+      this.</para>
+  </warning>
+
+  <para>Unlike &os;/i386 or &os;/alpha, there is no version of
+    &man.sysinstall.8; for &os;/&arch;.  The installation procedure
+    consists of loading a kernel (either from CDROM or the network)
+    onto the &arch; machine, with a root filesystem on CDROM or
+    exported via NFS.  The utilities on the root filesystem can then
+    be used to partition the local disk on the &arch; machine and
+    optionally to copy the &os; distribution to the local disk to make
+    a stand-alone machine.</para>
+
+  <para>Currently, there are two ways to install &os;/&arch; on a new
+    machine.  By far the easier of the two is to install from CDROM;
+    this method allows you to install &os; without any dependencies on
+    any other computers.</para>
+
+  <para>If installing from CDROM is impossible or undesirable, the
+    alternative is to install over the network.  This requires another
+    machine, suitably configured, to serve the boot loader, kernel,
+    and root filesystem to the new machine, via a combination of
+    RARP, TFTP, and either BOOTP or DHCP.  This netboot server can be
+    another &os; machine, but is not required to be.</para>
+
+  <para>You will need to decide which of these methods you want to use
+    for installation, as this will determine the set of files you need
+    to download (if any), as well as the steps required to do the
+    installation.</para>
+
+<!-- this should read "in this document" after the re-structure -->
+
+  <important>
+    <para>The URLs in this section are provisional and subject to
+      change.  Please see the archives of the &a.sparc; for the most
+      recent locations of files.  This notice will be removed when
+      more permanent URLs have been determined.</para>
+  </important>
+
+  <sect2 id="getting-to-prom-prompt">
+    <title>Getting to the PROM Prompt</title>
+
+    <para>Most &arch; systems are set up to boot automatically from
+      disk.  To install &os;, you need to boot over the network or
+      from a CDROM, which requires you to break into the PROM
+      (OpenFirmware).</para>
+
+    <para>To do this, reboot the system, and wait until the boot
+      message appears.  It depends on the model, but should look about
+      like:</para>
+
+    <screen>Sun Blade 100 (UltraSPARC-IIe), Keyboard Present
+Copyright 1998-2001 Sun Microsystems, Inc.  All rights reserved.
+OpenBoot 4.2, 128 MB memory installed, Serial #51090132.
+Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4.</screen>
+
+    <para>If your system proceeds to boot from disk at this point, you
+      need to press <keycombo
+      action="simul"><keycap>L1</keycap><keycap>A</keycap></keycombo>
+      or <keycombo
+      action="simul"><keycap>Stop</keycap><keycap>A</keycap></keycombo>
+      on the keyboard, or send a <command>BREAK</command> over the
+      serial console (using for example <command>~#</command> in
+      &man.tip.1; or &man.cu.1;) to get to the PROM prompt.  It looks
+      like this:</para>
+
+    <screenco>
+      <areaspec>
+	<area id="prompt-single" coords="1 5">
+	<area id="prompt-smp" coords="2 5">
+      </areaspec>
+
+      <screen><prompt>ok     </prompt>
+<prompt>ok {0} </prompt></screen>
+
+      <calloutlist>
+	<callout arearefs="prompt-single">
+	  <para>This is the prompt used on systems with just one
+	    CPU.</para>
+	</callout>
+
+	<callout arearefs="prompt-smp">
+	  <para>This is the prompt used on SMP systems, the digit
+	    indicates the number of the active CPU.</para>
+	</callout>
+      </calloutlist>
+    </screenco>
+  </sect2>
+
+  <sect2 id="prepare-cd">
+    <title>Preparing for a CDROM Installation</title>
+
+    <para>If you want to do a CDROM installation, an ISO image with a
+      snapshot of &os;/&arch; can be found at <ulink
+      url="&release.url;"></ulink>.  This file can be used to create a
+      bootable CDROM which contains everything necessary to boot and
+      load at least a minimal &os; installation.</para>
+
+<!-- XXX ISO location?-->
+    <para>Place the CDROM into your drive, and break into the PROM as
+      described above.  On the PROM prompt, type <command>boot
+      cdrom</command>.  The system should boot into single-user mode
+      now, and you can create the disk label and install the base
+      system archive as described in <xref
+      linkend="creating-disk-label"> and <xref
+      linkend="creating-root-filesystem">.</para>
+  </sect2>
+
+  <sect2 id="prepare-network">
+    <title>Preparing for a Network Installation</title>
+
+    <para>A &os;/&arch; kernel is booted by having the firmware
+      retrieve and execute a <application>loader</application>, which
+      in turn fetches and executes the actual kernel.  For this boot
+      process, you need to set up &man.rarpd.8; and &man.tftpd.8; (for
+      the firmware) and &man.bootpd.8; (for the
+      <application>loader</application>) on another networked system.
+      The loader can fetch a kernel using TFTP or NFS.  All of this is
+      covered in detail below.</para>
+
+    <sect3 id="downloading">
+      <title>Getting the Required Files</title>
+
+      <para>For a network installation, you will need several files.
+	First, you will need to download a &os;/&arch; loader for
+	&man.tftpd.8; to serve to your &arch; client.  The loader will
+	use either TFTP or NFS to retrieve the &os; kernel from the
+	netboot server.  There is a separate loader for each of these
+	methods (i.e. a loader for TFTP and a loader for NFS).  You
+	should download one of the following files, as
+	appropriate:</para>
+
+      <itemizedlist>
+	<listitem>
+	  <para><ulink
+	    url="&release.url;loader-tftp.gz"></ulink></para>
+	</listitem>
+
+	<listitem>
+	  <para><ulink
+	    url="&release.url;loader-nfs.gz"></ulink></para>
+	</listitem>
+      </itemizedlist>
+
+      <para>A network installation also requires a kernel to be served
+	to the netboot client.  A suitable kernel can be found at
+	<ulink url="&release.url;"></ulink>.</para>
+<!-- XXX kernel filename?-->
+
+      <para>Finally, you will need a &man.tar.1; archive which
+	contains the binaries and configuration files from the base
+	system.  This file is available from <ulink
+	url="&release.url;distrib.tar.gz"></ulink>.</para>
+    </sect3>
+
+<!-- put the words "netboot server" in here -->
+    <sect3>
+      <title>rarpd</title>
+
+      <para>You need to add the Ethernet address of your &os;/&arch;
+	system to <filename>/etc/ethers</filename> on the netboot
+	server.  An entry looks like:</para>
+
+      <programlisting>0:3:ba:b:92:d4 your.host.name</programlisting>
+
+      <para>The Ethernet address is usually displayed in the boot
+	message.</para>
+
+      <para>Make sure <hostid>your.host.name</hostid> is in
+	<filename>/etc/hosts</filename> or has a valid DNS entry (or
+	use an IP address).  Then, start &man.rarpd.8; on a network
+	interface that is on the same subnet as the &os;/&arch;
+	system.</para>
+    </sect3>
+
+<!-- put the words "netboot server" in here -->
+    <sect3>
+      <title>tftpd</title>
+
+      <para>Activate &man.tftpd.8; in your &man.inetd.8;
+	configuration by uncommenting the following line in
+	<filename>/etc/inetd.conf</filename>:</para>
+
+      <programlisting>tftp dgram udp  wait nobody /usr/libexec/tftpd tftpd /tftpboot</programlisting>
+
+      <para>Copy the unpacked loader to your
+	<filename>/tftpboot</filename> directory, and name it with the
+	&os;/&arch; host's IP address in upper-case hexadecimal
+	notation without dots (or use appropriately-named symbolic
+	links).  For example, your setup may look like this, for an IP
+	address of <hostid>192.168.0.16</hostid>:</para>
+
+      <screen>  lrwx------  1 tmm users       9 Jul 24 17:05 /tftpboot/C0A80010 -> boot/loader
+  -rw-r--r--  1 tmm users 1643021 Oct 20 18:04 /tftpboot/boot/loader</screen>
+
+      <para>If you have trouble booting, it is very helpful to use
+	&man.tcpdump.1; to monitor the TFTP requests.  This will allow
+	you to see the file name you need to use for the loader.
+	Error replies by the TFTP server are most often due to
+	incorrect file permissions.</para>
+    </sect3>
+
+<!-- put the words "netboot server" in here -->
+    <sect3>
+      <title>Setting up bootpd/dhcpd</title>
+
+      <para>You can use either BOOTP or DHCP (both not both) to
+	provide some parameters to the boot loader, such as a
+	machine's IP address.  If you are using another &os; machine
+	as a netboot server, the BOOTP functionality is provided by
+	&man.bootpd.8;, which is a part of the &os; base system.
+	Several DHCP servers are provided in the &os; Ports
+	Collection.</para>
+
+      <para>If you are going to use &man.bootpd.8;, create entries for
+	your &os;/&arch; system in the server's
+	<filename>/etc/bootptab</filename> (see &man.bootptab.5; for
+	more details):</para>
+
+      <programlisting>.default:\
+  :bf="kernel":dn=local:ds=<replaceable>name-server-ip-address</replaceable>:\
+  :gw=<replaceable>gateway-ip-address</replaceable>:ht=ether:hd="/tftpboot/boot/kernel":hn:\
+  :sa="<replaceable>tftp-server-ip-address</replaceable>":\
+  :rp="<replaceable>tftp-server-ip-address</replaceable>:<replaceable>nfs-root-directory</replaceable>":\
+  :sm=<replaceable>ip-netmask</replaceable>
+
+<replaceable>name-of-the-entry</replaceable>:\
+  ha=<replaceable>sparc64-ethernet-address</replaceable>:ip=<replaceable>sparc64-ip-address</replaceable>:tc=.default</programlisting>
+
+      <para>The Ethernet address must be the same as the one in the
+	TFTP example above, but it is specified hexadecimal notation
+	without colons (for the example above, this would be
+	<literal>0003ba0b92d4</literal>).  NFS/TFTP specific entries
+	can be omitted if the given method is not used.  The strings
+	given in the <literal>hd</literal> and <literal>bf</literal>
+	properties are concatenated to give the boot file name.  If
+	your kernel is named differently or you use another directory,
+	change these values as required.  If you are booting using
+	NFS, remove the <literal>bf</literal> and
+	<literal>hd</literal> settings (or change them to specify the
+	directory and file inside the NFS root hierarchy in which the
+	kernel will reside).  The name of the host entry is
+	conventionally the host name without the domain
+	appended.</para>
+
+      <para>For a DHCP server, add an entry similar to the following
+	to your <filename>dhcpd.conf</filename> file.  An example
+	entry for <application>ISC DHCP</application> version 2
+	(available in the &os; Ports Collection as <filename
+	role="package">net/isc-dhcp2</filename>) is shown
+	below:</para>
+
+      <programlisting>host <replaceable>name-of-entry</replaceable> {
+  hardware ethernet <replaceable>sparc64-ethernet-address</replaceable>;
+  option host-name "<replaceable>sparc64-fully-qualified-domain-name</replaceable>";
+  fixed-address <replaceable>sparc64-ip-address</replaceable>;
+  always-reply-rfc1048 on;
+  filename "kernel";
+  option root-path "<replaceable>tftp-server-ip-address</replaceable>:<replaceable>nfs-root-directory</replaceable>";
+}</programlisting>
+
+      <para>The <literal>filename</literal> option corresponds to the
+	concatenation of <literal>hd</literal> and
+	<literal>bf</literal> in <filename>/etc/bootptab</filename>.
+	The Ethernet address is specified in hexadecimal with colons,
+	just like in the &man.rarpd.8; example above.
+	<literal>options root-path</literal> corresponds to
+	<literal>rp</literal> in <filename>/etc/bootptab</filename>.
+	If the name given in <literal>option host-name</literal> is
+	resolvable, i.e. has a DNS entry or is associated with an
+	address in <filename>/etc/hosts</filename>, the
+	<literal>fixed-address</literal> specification can be
+	omitted.</para>
+    </sect3>
+
+    <sect3>
+      <title>Loading the Kernel</title>
+
+      <para>With the daemons on the netboot server configured, the
+	next step is to copy the kernel (obtained during the steps of
+	<xref linkend="downloading">) to an appropriate directory.
+	There are two ways of retrieving a kernel over the network:
+	TFTP and NFS.  (You specified one of these two alternatives by
+	picking a loader.)</para>
+
+      <para>For both TFTP and NFS, the loader will use the parameters
+	that it obtained via BOOTP or DHCP to find the kernel.</para>
+
+      <sect4>
+	<title>Loading the Kernel over TFTP</title>
+
+	<para>Place the kernel in the directory you specified using
+	  <literal>bf</literal> and <literal>hd</literal> in the
+	  <filename>/etc/bootptab</filename> or the
+	  <literal>filename</literal> parameter to
+	  <filename>dhcpd.conf</filename>.</para>
+      </sect4>
+
+      <sect4>
+	<title>Loading the Kernel over NFS</title>
+
+	<para>Export the directory that was specified by the
+	  <literal>rp</literal> property in
+	  <filename>/etc/bootptab</filename> or the
+	  <literal>root-path</literal> parameter in
+	  <filename>dhcpd.conf</filename> (see &man.exports.5;).  Copy
+	  the kernel to the directory you specified using
+	  <literal>bf</literal> and <literal>hd</literal> in the
+	  <filename>/etc/bootptab</filename> or the
+	  <literal>filename</literal> parameter to
+	  <filename>dhcpd.conf</filename>.</para>
+      </sect4>
+    </sect3>
+
+    <sect3>
+      <title>Loading the Base System to the Netboot Server</title>
+
+      <para>You must extract the base system distribution image to the
+	NFS root directory specified either by the
+	<literal>rp</literal> option in
+	<filename>/etc/bootptab</filename> or the
+	<literal>root-path</literal> option in
+	<filename>dhcpd.conf</filename>.  This directory tree will
+	become the &arch;'s root filesystem once the kernel is booted.
+	Besides providing a normal userland environment, it also
+	contains all of the necessary utilities for you to install the
+	distribution on the &arch; client's local disk.</para>
+
+      <para>Using whatever editing tools you have on the netboot
+	server, you probably will want to edit the &arch;'s
+	<filename>/etc/fstab</filename> and
+	<filename>/etc/rc.conf</filename> and set a
+	<username>root</username> password.</para>
+    </sect3>
+
+    <sect3>
+      <title>Booting</title>
+
+      <para>If all goes well, you can now boot the &os; on your &arch;
+	machine by dropping into the PROM prompt as described in <xref
+	linkend="getting-to-prom-prompt">.  Now, just type
+	<command>boot net</command> and the system should boot.
+	Specifically, the loader is retrieved via TFTP, it then does a
+	BOOTP request and will proceed to load the kernel (either
+	using TFTP or NFS, depending on your choice of loader).  Then,
+	it should wait 10 seconds for user input and proceed to
+	execute the kernel.</para>
+
+      <para>If something does not work in between, and you suspect
+	TFTP/NFS/BOOTP problems, <application>Ethereal</application>
+	(available in the &os; Ports Collection as <filename
+	role="package"> net/ethereal</filename>) is usually helpful.
+	The most common problems are related to bad file permissions.
+	Also note that &man.rarpd.8; will not answer to packets under
+	some circumstances, refer to the manual page for
+	details.</para>
+    </sect3>
+  </sect2>
+
+  <sect2 id="creating-disk-label">
+    <title>Creating a Disk Label</title>
+
+    <para>The kernel supports the Sun disk label format, so you can
+      label the disks you want to use with &os; from Solaris.</para>
+
+    <para>&os; disk labels must currently be created by hand, as
+      &man.sysinstall.8; is not yet available on &os;/&arch;.  Please
+      refer to the <ulink
+      url="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/">FreeBSD
+      Handbook</ulink> for more information about labels and special
+      partitions.</para>
+
+    <para>On &os;/&arch;, a Sun compatibility label is embedded in the
+      &os; label; this is needed for the PROM to boot from disk.  This
+      imposes an additional restriction on the disk label format:
+      partitions are required to start on a cylinder boundary.</para>
+
+    <para>To create a disk label, the following procedure is the
+      easiest:</para>
+
+    <procedure>
+      <step>
+	<para>Run <command>disklabel -w -r
+	  <replaceable>device</replaceable> auto</command> to create a
+	  basic disk label.  The third argument you need specify here
+	  is just the name of the device, not the complete path to the
+	  device node (e.g. <devicename>ad0</devicename> for the first
+	  ATA disk).</para>
+      </step>
+
+      <step>
+	<para> Use <command>disklabel -e
+	  <replaceable>device</replaceable></command> to open an
+	  editor in which you can edit the disk label.  The
+	  information presented to you should look like:</para>
+
+	<screen># /dev/ad6c:
+type: unknown
+disk: amnesiac
+label:
+flags:
+bytes/sector: 512
+sectors/track: 63
+tracks/cylinder: 16
+sectors/cylinder: 1008
+cylinders: 79780
+sectors/unit: 80418240
+rpm: 3600
+interleave: 1
+trackskew: 0
+cylinderskew: 0
+headswitch: 0           # milliseconds
+track-to-track seek: 0  # milliseconds
+drivedata: 0
+
+8 partitions:
+#        size   offset    fstype   [fsize bsize bps/cpg]
+  c: 80418240        0    unused        0     0         # (Cyl.    0 - 79779)</screen>
+
+	<para>You can now add new partitions in the same format as the
+	  already present line.  Using <literal>*</literal> in the
+	  offset field makes the procedure easier; please refer to the
+	  &man.disklabel.8; manual page for more information.</para>
+
+	<para>To make sure the restriction mentioned above is met, the
+	  size of each partition must be a multiple of the number of
+	  sectors per cylinder as shown in the information that is
+	  presented in the editor (1008 in the example above).</para>
+
+	<para>When you are done, save your changes and quit the
+	  editor.i This will cause the disk label to be
+	  written.</para>
+
+	<warning>
+	  <para>This procedure will overwrite any disk label that may
+	    be already present on the disk.  Any existing filesystems
+	    on this disk must have their respective partition entries
+	    in the old and new label match
+	    <emphasis>exactly</emphasis>, or they will be
+	    lost.</para>
+	</warning>
+
+	<para>If you want to double-check that your partitions end on
+	  cylinder boundaries, run <command>disklabel -e
+	  <replaceable>device</replaceable></command> again.  The
+	  editor will display the cylinders used by a particular
+	  partition on the right hand side of the output.  If any of
+	  the partitions you defined (i.e. anything except partition
+	  <literal>c</literal>) shows an <literal>*</literal> next to
+	  it, the partition does <emphasis>NOT</emphasis> start or end
+	  on a cylinder boundary.  You <emphasis>MUST</emphasis> fix
+	  these or your system will not work.</para>
+      </step>
+
+      <step>
+	<para>Use <command>disklabel -B</command> if you want to make
+	  the disk bootable for &os;/&arch;.</para>
+
+	<warning>
+	  <para>Using <command>disklabel -B</command> on a disk will
+	    overwrite any preexisting boot block, so it will likely
+	    render any other operating system installed on the same
+	    disk unbootable.</para>
+	</warning>
+
+	<para>If you do not want to overwrite the boot block, it is
+	  possible to load the <application>loader</application> via
+	  TFTP as described above, but have it boot the kernel from
+	  disk.  This requires a special loader binary, which is
+	  available at <ulink
+	  url="ftp://ftp.FreeBSD.org/pub/FreeBSD/development/sparc64/loader-ufs.gz"></ulink></para>
+      </step>
+    </procedure>
+  </sect2>
+
+  <sect2 id="creating-root-filesystem">
+    <title>Creating the Root Fileystem</title>
+
+    <para>If you want to boot from a local disk, you will need to
+      create a root filesystem to hold the base system binaries and
+      configuration files (and optionally other filesystems mounted
+      in places such as <filename>/usr</filename> and
+      <filename>/var</filename>).</para>
+
+    <para>The kernel contains support for Sun disklabels, so you can
+      use Solaris disks, which may even be prepared using
+      <application>newfs</application> under Solaris.  NetBSD disk
+      labels and filesystems are also usable from &os;.</para>
+
+    <warning>
+      <para>Do <emphasis>not</emphasis> run Solaris
+	<application>fsck</application> on filesystems modified by
+	&os;.  Doing so will damage the file permissions.</para>
+    </warning>
+
+    <para>To create filesystems and to install the base system, boot
+      from CDROM or via NFS and create a disk label as described in
+      <xref linkend="creating-disk-label">.</para>
+
+    <para>When booting the first time and you have not entered your
+      root partition into <filename>/etc/fstab</filename> yet, you may
+      need to specify your root partition on the mountroot prompt when
+      booting (use a format like
+      <command>ufs:<replaceable>disk</replaceable><replaceable>partition</replaceable></command>,
+      i.e. leave the slice specification out).  If the kernel does
+      automatically attempt to boot from another filesystem, press a
+      key other than <keycap>Enter</keycap> on the
+      <application>loader</application> prompt:</para>
+
+    <screen>Hit [Enter] to boot immediately, or any other key for command prompt.</screen>
+
+    <para>Then, boot the kernel using <command>boot -a -s</command>,
+      which will cause the kernel to ask you for the root partition
+      and then boot into single-user mode.  Once the root filesystem
+      has been entered into <filename>/etc/fstab</filename>, it should
+      be automatically mounted as <filename>/</filename> on the next
+      boot.</para>
+
+    <para>If you are booting over the network (via NFS), the above
+      BOOTP entries should suffice to have the kernel find and mount
+      the root filesystem via NFS.</para>
+  </sect2>
+
+  <sect2 id="installing-base-system">
+    <title>Installing the Base System</title>
+
+    <para>If you booted the kernel from the network, you downloaded a
+      &man.tar.1; archive with the base system and exported it from
+      the netboot server via NFS.  You can unpack this same archive to
+      your local disk to create a stand-alone system (remember to copy
+      the kernel over as well).</para>
+
+    <para>If you booted from CDROM, the same archive is available in
+      <filename>/root/</filename> on the CDROM.</para>
+
+    <para>Before booting the system stand-alone, you will want to edit
+      <filename>/etc/fstab</filename> and
+      <filename>/etc/rc.conf</filename> and set a
+      <username>root</username> password.</para>
+
+    <para>Note that some programs from the base system may not be
+      present in the archive, or may not work properly yet.</para>
+  </sect2>
+</sect1>