From owner-doc-jp@jp.freebsd.org  Thu Jan 13 02:15:04 2000
Received: (from daemon@localhost)
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) id CAA70998;
	Thu, 13 Jan 2000 02:15:04 +0900 (JST)
	(envelope-from owner-doc-jp@jp.FreeBSD.org)
Received: from sv01.geocities.co.jp (sv01.geocities.co.jp [210.153.89.155])
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) with ESMTP id CAA70992
	for <doc-jp@jp.freebsd.org>; Thu, 13 Jan 2000 02:15:03 +0900 (JST)
	(envelope-from hrs@geocities.co.jp)
Received: from mail.geocities.co.jp (mail.geocities.co.jp [210.153.89.137]) by sv01.geocities.co.jp (8.9.3+3.2W/3.7W) with ESMTP id CAA07369 for <doc-jp@jp.freebsd.org>; Thu, 13 Jan 2000 02:15:01 +0900 (JST)
Received: from mail.hrs.jp (sutkmax2-ppp16.ed.kagu.sut.ac.jp [133.31.177.82]) by mail.geocities.co.jp (1.3G-GeocitiesJ-3.3) with ESMTP id CAA10785 for <doc-jp@jp.freebsd.org>; Thu, 13 Jan 2000 02:14:55 +0900 (JST)
Message-Id: <200001121714.CAA10785@mail.geocities.co.jp>
Received: from localhost (alph.hrs.jp [192.168.0.10])
	by mail.hrs.jp (8.9.3/3.7W/DomainMaster) with ESMTP id BAA10437
	for <doc-jp@jp.freebsd.org>; Thu, 13 Jan 2000 01:22:27 +0900 (JST)
	(envelope-from hrs@hrs.jp)
To: doc-jp@jp.freebsd.org
Content-Type: Multipart/Mixed;
 boundary="--Next_Part(Thu_Jan_13_01:15:40_2000_518)--"
Content-Transfer-Encoding: 7bit
X-Mailer: Mew version 1.94 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA)
Mime-Version: 1.0
Date: Thu, 13 Jan 2000 01:20:29 +0900
From: Hiroki Sato <hrs@geocities.co.jp>
X-Dispatcher: imput version 990905(IM130)
Lines: 794
Reply-To: doc-jp@jp.freebsd.org
Precedence: list
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+990727
X-Sequence: doc-jp 6960
Subject: [doc-jp 6960] <handbook> install/chapter.sgml 1.30
Errors-To: owner-doc-jp@jp.freebsd.org
Sender: owner-doc-jp@jp.freebsd.org
X-Originator: hrs@geocities.co.jp

----Next_Part(Thu_Jan_13_01:15:40_2000_518)--
Content-Type: Text/Plain; charset=iso-2022-jp
Content-Transfer-Encoding: 7bit

$B:4F#!wEl5~M}2JBg3X$G$9!#(B

 +1318/-1023 $B$HBgJ*$N(B
 books/handbook $B$N(B install/chapter.sgml 1.30 $B$NJ,3d$r9T$J$$$^$7$?!#(B

 $BJ8=q7A<0$N%j%9%H%i$,F~$C$F$$$k4X78$G!"(Bdiff $B$,(B
 $B0UL#$N$"$k$b$N$K$J$C$F$$$^$;$s!#(B

 $B$9$G$KLu$5$l$F$$$kItJ,$G>l=j$@$1JQ99$K$J$C$?$b$N$b$$$/$D$+(B
 $BG'$a$i$l$^$7$?$,!"K\Ev$K$=$N$^$^$J$N$+%A%'%C%/$,HK;($@$C$?$N$G(B
 $B7A<0E*$K$P$i$7$^$7$?!#(Brelease notes $B$H=EJ#$9$kItJ,$b(B
 $B$$$/$D$+$"$k$H;W$$$^$9!#(B

 $B:n6H$5$l$kJ}$O!"(Brelease notes $B$HF|K\8lHG(B 1.29 $B$r;29M$K$7$F!"(B
 $BJ,3d$5$l$?86J8$NItJ,$rK]Lu$7$F2<$5$$!#(B
 $B@.2LJ*$O(B doc-jp $B$NJ}$X$*4j$$$7$^$9!#(B

 # $B<B<AE*$J?75,K]LuNL$O$=$l$[$I$"$j$^$;$s$N$G!"(B
 # $B%A%'%C%/$K6a$$:n6H$K$J$k$H;W$$$^$9!#(B

--
| $B:4F#(B $B9-@8!wEl5~M}2JBg3X(B <hrs@geocities.co.jp>
|
|                                  j7397067@ed.noda.sut.ac.jp(univ)
|                        hrs@jp.FreeBSD.org(FreeBSD doc-jp Project)

----Next_Part(Thu_Jan_13_01:15:40_2000_518)--
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="chapter.diff.1"

+  <sect1>
+    <title>Synopsis</title>
 
+    <para>The following chapter will attempt to guide you through the
+      install of FreeBSD on your system.  It can be installed through a
+      variety of methods including anonymous FTP (assuming you have
+      network connectivity), CDROM, floppy disk, tape, an MS-DOS
+      partition, or even NFS.</para>
+
+    <para>No matter which method you choose, you will need to get started
+      by creating the <emphasis>installation disks</emphasis> as described
+      in the <link linkend="install-floppies">next section</link>.  By
+      booting into the FreeBSD installer, even if you are not planning on
+      installing FreeBSD right away, will provide important information
+      about compatibility with your hardware.  This information may
+      dictate which installation options are even possible for you.  It
+      can also provide clues early-on in the process to potential problems
+      you may come across later.</para>
+
+    <para>If you plan on installing FreeBSD via anonymous FTP, the only
+      thing you will need are the <link
+      linkend="install-floppies">installation floppies</link>.  The
+      install program itself will handle anything else that is
+      required.</para>
+
+    <para>For more information on obtaining FreeBSD, see the <link
+      linkend="mirrors">Obtaining FreeBSD</link> section of the
+      Appendix.</para>
 
+    <para>By now, you are probably wondering what exactly it is you need
+      to do.  Continue on to the installation guide.</para>
+  </sect1>

----Next_Part(Thu_Jan_13_01:15:40_2000_518)--
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="chapter.diff.2"

+
+  <sect1 id="install-guide">
+    <title>Installation Guide</title>
+
+    <para>The following sections will guide you through preparing for and
+      actually installing FreeBSD.  If you find something missing, please
+      let us know about it by sending email to the &a.doc;</para>
+
+    <sect2 id="install-prepare">
+      <title>Preparing for the Installation</title>
+
+      <para>There are various things you should do in preparation for the
+        install.  The following describes what needs to be done prior to
+	each type of installation.</para>
+
+      <para>The first thing you should do is make sure your hardware is
+	supported by FreeBSD.  The list of <link
+	linkend="install-hw">supported hardware</link> should
+	come in handy here. ;-)  It would also be a good idea to make a
+	list of any &ldquo;special&rdquo; cards you have installed,
+	such as SCSI controllers, ethernet cards, sound cards, etc..
+	The list should include their IRQs and IO port addresses.</para>
+
+      <sect3 id="install-floppies">
+	<title>Creating the Boot Floppies</title>
+
+        <para>Please read the <ulink
+	  url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel.current;-RELEASE/floppies/README.TXT">installation
+	  boot image information</ulink> before proceeding.  To make the
+	  installation boot disks from the image files, do the
+	  following:</para>
+
+	<itemizedlist>
+	  <listitem>
+	    <para>If you are installing from an MS-DOS partition,
+	      download the <ulink
+	      url="ftp://ftp.FreeBSD.org/pub/FreeBSD/tools/fdimage.exe">fdimage.exe</ulink>
+	      program or get it from <filename>tools\fdimage.exe</filename>
+	      on the CDROM and then run it like so:</para>
+
+	    <screen><prompt>E:\&gt;</prompt> <userinput>tools\fdimage floppies\kern.flp a:</userinput></screen>
+
+	    <para>The <emphasis>fdimage</emphasis> program will format
+	      the <devicename>A:</devicename> drive and then copy
+	      <filename>kern.flp</filename> to it (assuming that you are
+	      at the top level of a FreeBSD distribution and the floppy
+	      images live in a <filename>floppies</filename>
+	      subdirectory, which is typically the case).</para>
+	  </listitem>
+
+	  <listitem>
+	    <para>If you are using a UNIX-based system to create the
+	      boot floppies, do the following:</para>
+
+	    <screen>&prompt.root; <userinput>dd if=kern.flp of=<replaceable>disk_device</replaceable></userinput></screen>
+
+	    <para><replaceable>disk_device</replaceable> is the
+	      <filename>/dev</filename> entry for the floppy drive.  On
+	      FreeBSD, this is <filename>/dev/rfd0</filename> for the
+	      <devicename>A:</devicename> drive and
+	      <filename>/dev/rfd1</filename> for the
+	      <devicename>B:</devicename> drive.</para>
+	  </listitem>
+	</itemizedlist>
+
+        <para>With the <filename>kern.flp</filename> disk in your floppy
+	  drive, reboot your computer.  You will be prompted to insert
+	  the <filename>mfsroot.flp</filename>, after which the
+	  installation will proceed normally.</para>
+      </sect3>

----Next_Part(Thu_Jan_13_01:15:40_2000_518)--
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="chapter.diff.3"

+
+      <sect3 id="install-cdrom">
+        <title>Before Installing from CDROM</title>
+	
+	<para>If your CDROM is of an unsupported type, please skip ahead
+	  to the <link linkend="install-msdos">MS-DOS Preparation</link>
+	  section.</para>
+	
+	<para>There is not a whole lot of preparation needed if you are
+	  installing from one of <ulink
+	  url="http://www.wccdrom.com/">Walnut Creek CDROM's</ulink>
+	  FreeBSD CDROMs (other CDROM distributions may work as well,
+	  though we cannot say for certain as we have no hand or say in
+	  how they created).  You can either boot into the CD installation
+	  directly from DOS using the <filename>install.bat</filename> or
+	  you can make floppies with the <filename>makeflp.bat</filename>
+	  command.</para>
+
+	<para>If the CD has El Torrito boot support and your system
+	  supports booting directly from the CDROM drive (many older
+	  systems do <emphasis>NOT</emphasis>), simply insert the first
+	  FreeBSD of the set into the drive and reboot your system.  You
+	  will be put into the install menu directly from the CD.</para>
+
+	<para>If you are installing from an MS-DOS partition and have
+	  the proper drivers to access your cd, run the install.bat
+	  script provided on the CDROM.  This will attempt to boot
+	  the FreeBSD installation directly from DOS.</para>
+
+	<note>
+	  <para>You must do this from actual DOS (i.e., boot in DOS
+	    mode) and not from a DOS window under Windows.</para>
+	</note>
+
+	<para>For the easiest interface of the all (from DOS), type
+	  <command>view</command>.  This will bring up a DOS menu utility
+	  that leads you through all of the available options.</para>
+
+	<para>If you are creating the boot floppies from a UNIX machine,
+	  see the <link linkend="install-floppies">Creating the Boot
+	  Floppies</link> section of this guide for examples.</para>
+	
+	<para>Once you have booted from DOS or floppy, you should then be
+	  able to select CDROM as the media type during the install
+	  process and load the entire distribution from CDROM.  No other
+	  types of installation media should be required.</para>
+
+	<para>After your system is fully installed and you have rebooted
+	  (from the hard disk), you can mount the CDROM at any time by
+	  typing:</para>
+
+	<screen>&prompt.root; <userinput>mount /cdrom</userinput></screen>
+
+	<para>Before removing the CD from the drive again, you must first
+	  unmount it.  This is done with the following command:</para>
+
+	<screen>&prompt.root; <userinput>umount /cdrom</userinput></screen>
+
+	<para>Do not just remove it from the drive!</para>
+
+	<note>
+	  <para>Before invoking the installation, be sure that the CDROM
+	    is in the drive so that the install probe can find it.  This
+	    is also true if you wish the CDROM to be added to the default
+	    system configuration automatically during the install (whether
+	    or not you actually use it as the installation media).</para>
+	</note>
+
+	<para>Finally, if you would like people to be able to FTP install
+	  FreeBSD directly from the CDROM in your machine, you will find
+	  it quite easy.  After the machine is fully installed, you simply
+	  need to add the following line to the password file (using the
+	  <command>vipw</command> command):</para>
+
+	<programlisting>
+ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent</programlisting>
+
+	<para>Anyone with network connectivity to your machine (and
+	  permission to log into it) can now chose a media type of FTP and
+	  type in <userinput>ftp://<replaceable>your
+	  machine</replaceable></userinput> after picking
+	  &ldquo;Other&rdquo; in the FTP sites menu during the
+	  install.</para>
+      </sect3>
+
+      <sect3>
+        <title>Before installing from Floppies</title>
+
+	<para>If you must install from floppy disk (which we suggest you
+	  do not do), either do unsupported hardware or simply because you
+	  insist on doing things the hard way, you must first prepare some
+	  floppies for the install.</para>
+
+	<para>At a minimum, you will need as many 1.44MB or 1.2MB floppies
+	  as it takes to hold all the files in the
+	  <filename>bin</filename> (binary distribution) directory.  If
+	  you are preparing the floppies from DOS, then they
+	  <emphasis>MUST</emphasis> be formatted using the MS-DOS
+	  <command>FORMAT</command> command.  If you are using Windows,
+	  use the Windows File Manager format command.</para>
+
+	<para>Do <emphasis>NOT</emphasis> trust factory pre-formatted
+	  floppies!  Format them again yourself, just to be sure.  Many
+	  problems reported by our users in the past have resulted from
+	  the use of improperly formatted media, which is why we are
+	  making a point of it now.</para>
+
+	<para>If you are creating the floppies on another FreeBSD machine,
+	  a format is still not a bad idea, though you do not need to put
+	  a DOS filesystem on each floppy.  You can use the
+	  <command>disklabel</command> and <command>newfs</command>
+	  commands to put a UFS filesystem on them instead, as the
+	  following sequence of commands (for a 3.5" 1.44MB floppy)
+	  illustrate:</para>
+
+	<screen>&prompt.root; <userinput>fdformat -f 1440 fd0.1440</userinput>
+&prompt.root; <userinput>disklabel -w -r fd0.1440 floppy3</userinput>
+&prompt.root; <userinput>newfs -t 2 -u 18 -l 1 -i 65536 /dev/rfd0</userinput></screen>
+
+	<note>
+	  <para>Use <literal>fd0.1200</literal> and
+	    <literal>floppy5</literal> for 5.25" 1.2MB disks.</para>
+	</note>
+
+	<para>Then you can mount and write to them like any other
+	  filesystem.</para>
+
+	<para>After you have formatted the floppies, you will need to copy
+	  the files to them.  The distribution files are split into chunks
+	  conveniently sized so that 5 of them will fit on a conventional
+	  1.44MB floppy.  Go through all your floppies, packing as many
+	  files as will fit on each one, until you have all of the
+	  distributions you want packed up in this fashion.  Each
+	  distribution should go into a subdirectory on the floppy, e.g.:
+	  <filename>a:\bin\bin.aa</filename>,
+	  <filename>a:\bin\bin.ab</filename>, and so on.</para>
+
+	<para>Once you come to the Media screen during the install
+	  process, select &ldquo;Floppy&rdquo; and you will be prompted
+	  for the rest.</para>
+      </sect3>

----Next_Part(Thu_Jan_13_01:15:40_2000_518)--
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="chapter.diff.4"

+
+      <sect3 id="install-msdos">
+        <title>Before Installing from MS-DOS</title>
+
+	<para>To prepare for an installation from an MS-DOS partition,
+	  copy the files from the distribution into a directory named
+	  <filename>c:\FreeBSD</filename>.  The directory structure of the
+	  CDROM or FTP site must be partially reproduced within this
+	  directory, so we suggest using the DOS <command>xcopy</command>
+	  command if you are copying it from a CD.  For example, to
+	  prepare for a minimal installation of FreeBSD:</para>
+
+	<screen><prompt>C:\&gt;</prompt> <userinput>md c:\FreeBSD</userinput>
+<prompt>C:\&gt;</prompt> <userinput>xcopy /s e:\bin c:\FreeBSD\bin\</userinput>
+<prompt>C:\&gt;</prompt> <userinput>xcopy /s e:\manpages c:\FreeBSD\manpages\</userinput></screen>
+
+	<para>Assuming that <devicename>C:</devicename> is where you have
+	  free space and <devicename>E:</devicename> is where your CDROM
+	  is mounted.</para>
+
+	<para>For as many distributions you wish to install from an MS-DOS
+	  partition (and you have the free space for), install each one
+	  under <filename>c:\FreeBSD</filename> &mdash; the
+	  <literal>BIN</literal> distribution is the only one required for
+	  a minimum installation.</para>
+      </sect3>
+
+      <sect3>
+        <title>Before Installing from QIC/SCSI Tape</title>
+
+	<para>Installing from tape is probably the easiest method, short
+	  of an online FTP install or CDROM install.  The installation
+	  program expects the files to be simply tar'ed onto the tape, so
+	  after getting all of the distribution files you are interested
+	  in, simply tar them onto the tape like so:</para>
+
+	<screen>&prompt.root; <userinput>cd /freebsd/distdir</userinput>
+&prompt.root; <userinput>tar cvf /dev/rwt0 dist1 ... dist2</userinput></screen>
+
+	<para>When you go to do the installation, you should also make
+	  sure that you leave enough room in some temporary directory
+	  (which you will be allowed to choose) to accommodate the
+	  <emphasis>full</emphasis> contents of the tape you have created.
+	  Due to the non-random access nature of tapes, this method of
+	  installation requires quite a bit of temporary storage.  You
+	  should expect to require as much temporary storage as you have
+	  stuff written on tape.</para>
+
+	<note>
+	  <para>When going to do the installation, the tape must be in the
+	    drive <emphasis>before</emphasis> booting from the boot
+	    floppy.  The installation probe may otherwise fail to find
+	    it.</para>
+	</note>
+      </sect3>

----Next_Part(Thu_Jan_13_01:15:40_2000_518)--
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="chapter.diff.5"

+
+      <sect3>
+        <title>Before Installing over a Network</title>
 
+	<para>There are three types of network installations you can do.
+	  Serial port (SLIP or PPP), Parallel port (PLIP (laplink cable)),
+	  or Ethernet (a standard ethernet controller (includes some
+	  PCMCIA)).</para>
+
+	<para>The SLIP support is rather primitive, and limited primarily
+	  to hard-wired links, such as a serial cable running between a
+	  laptop computer and another computer.  The link should be
+	  hard-wired as the SLIP installation does not currently offer a
+	  dialing capability; that facility is provided with the PPP
+	  utility, which should be used in preference to SLIP whenever
+	  possible.</para>
+
+	<para>If you are using a modem, then PPP is almost certainly
+	  your only choice.  Make sure that you have your service
+	  provider's information handy as you will need to know it fairly
+	  soon in the installation process.  You will also need to know
+	  how to dial your ISP using the &ldquo;AT commands&rdquo;
+	  specific to your modem, as the PPP dialer provides only a very
+	  simple terminal emulator.  If you are using PAP or CHAP, you
+	  will need to type the necessary <command>set authname</command>
+	  and <command>set authkey</command> commands before typing
+	  <command>term</command>.  Refer to the user-ppp <link
+	  linkend="userppp">handbook</link> and <ulink
+	  url="../FAQ/ppp.html">FAQ</ulink> entries for further
+	  information.  If you have problems, logging can be directed to
+	  the screen using the command <command>set log local
+	  ...</command>.</para>
+
+	<para>If a hard-wired connection to another FreeBSD (2.0-R or
+	  later) machine is available, you might also consider installing
+	  over a &ldquo;laplink&rdquo; parallel port cable.  The data rate
+	  over the parallel port is much higher than what is typically
+	  possible over a serial line (up to 50k/sec), thus resulting in a
+	  quicker installation.</para>
+
+	<para>Finally, for the fastest possible network installation, an
+	  ethernet adapter is always a good choice!  FreeBSD supports most
+	  common PC ethernet cards, a table of supported cards (and their
+	  required settings) is provided in the <link
+	  linkend="install-hw">Supported Hardware</link> list.  If you are
+	  using one of the supported PCMCIA ethernet cards, also be sure
+	  that it is plugged in <emphasis>before</emphasis> the laptop is
+	  powered on!  FreeBSD does not, unfortunately, currently support
+	  hot insertion of PCMCIA cards during installation.</para>
+
+	<para>You will also need to know your IP address on the network,
+	  the netmask value for your address class, and the name of your
+	  machine.  Your system administrator can tell you which values to
+	  use for your particular network setup.  If you will be referring
+	  to other hosts by name rather than IP address, you will also
+	  need a name server and possibly the address of a gateway (if you
+	  are using PPP, it is your provider's IP address) to use in
+	  talking to it.  If you do not know the answers to all or most of
+	  these questions, then you should really probably talk to your
+	  system administrator <emphasis>before</emphasis> trying this
+	  type of installation.</para>
+
+	<sect4>
+	  <title>Before Installing via NFS</title>
+
+	  <para>The NFS installation is fairly straight-forward.  Simply
+	    copy the FreeBSD distribution files you want onto a server
+	    somewhere and then point the NFS media selection at it.</para>
+
+	  <para>If this server supports only &ldquo;privileged port&rdquo;
+	    (as is generally the default for Sun workstations), you will
+	    need to set this option in the Options menu before
+	    installation can proceed.</para>
+
+	  <para>If you have a poor quality ethernet card which suffers
+	    from very slow transfer rates, you may also wish to toggle the
+	    appropriate Options flag.</para>
+
+	  <para>In order for NFS installation to work, the server must
+	    support subdir mounts, e.g., if your FreeBSD 3.4 distribution
+	    directory lives
+	    on:<filename>ziggy:/usr/archive/stuff/FreeBSD</filename>, then
+	    <hostid>ziggy</hostid> will have to allow the direct mounting
+	    of <filename>/usr/archive/stuff/FreeBSD</filename>, not just
+	    <filename>/usr</filename> or
+	    <filename>/usr/archive/stuff</filename>.</para>
+
+	  <para>In FreeBSD's <filename>/etc/exports</filename> file, this
+	    is controlled by the <option>-alldirs</option>.  Other NFS
+	    servers may have different conventions.  If you are getting
+	    &ldquo;permission denied&rdquo; messages from the server, then
+	    it is likely that you do not have this enabled
+	    properly.</para>
+	</sect4>

----Next_Part(Thu_Jan_13_01:15:40_2000_518)--
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="chapter.diff.6"

+
+	<sect4>
+	  <title>Before Installing via FTP</title>
+
+	  <para>FTP installation may be done from any FreeBSD mirror site
+	    containing a reasonably up-to-date version of FreeBSD
+	    &rel.current;.  A full list of FTP mirrors located all over
+	    the world is provided during the install process.</para>
+
+	  <para>If you are installing from an FTP site not listed in this
+	    menu, or are having trouble getting your name server
+	    configured properly, you can also specify a URL to use by
+	    selecting the choice labeled &ldquo;Other&rdquo; in that menu.
+	    You can also use the IP address of a machine you wish to
+	    install from, so the following would work in the absence of a
+	    name server:</para>
+
+	  <screen><userinput>ftp://165.113.121.81/pub/FreeBSD/&rel.current;-RELEASE</userinput></screen>
+
+	  <para>There are two FTP installation modes you can choose from,
+	    active or passive FTP.</para>
+
+	  <variablelist>
+	    <varlistentry>
+	      <term>FTP Active</term>
+
+	      <listitem>
+	        <para>For all FTP transfers, use &ldquo;Active&rdquo;
+		  mode.  This will not work through firewalls, byt will
+		  often work with older FTP servers that do not support
+		  passive mode.  If your connection hangs with passive
+		  mode (the default), try active!</para>
+	      </listitem>
+	    </varlistentry>
+
+	    <varlistentry>
+	      <term>FTP Passive</term>
+
+	      <listitem>
+	        <para>For all FTP transfers, use &ldquo;Passive&rdquo;
+		  mode.  This allows the user to pass through firewalls
+		  that do not allow incoming connections on random port
+		  addresses.</para>
+	      </listitem>
+	    </varlistentry>
+	  </variablelist>
+
 	  <note>
+	    <para>Active and passive modes are not the same as a
+	      &ldquo;proxy&rdquo; connection, where a proxy FTP server is
+	      listening and forwarding FTP requests!</para>
 	  </note>
+
+	  <para>For a proxy FTP server, you should usually give the name
+	    of the server you really want as a part of the username, after
+	    an &ldquo;@&rdquo; sign.  The proxy server then
+	    &ldquo;fakes&rdquo; the real server.  For example, assuming
+	    you want to install from <hostid
+	    role="fqdn">ftp.FreeBSD.org</hostid>, using the proxy FTP
+	    server <hostid role="fqdn">foo.bar.com</hostid>, listening on
+	    port 1024.</para>
+
+	  <para>In this case, you go to the options menu, set the FTP
+	    username to ftp@ftp.FreeBSD.org, and the password to your
+	    email address.  As your installation media, you specify FTP
+	    (or passive FTP, if the proxy supports it), and the URL
+	    <literal>ftp://foo.bar.com:1234/pub/FreeBSD</literal>.</para>
+
+	  <para>Since <filename>/pub/FreeBSD</filename> from <hostid
+	    role="fqdn">ftp.FreeBSD.org</hostid> is proxied under <hostid
+	    role="fqdn">foo.bar.com</hostid>, you are able to install from
+	    <emphasis>that</emphasis> machine (which will fetch the files
+	    from <hostid role="fqdn">ftp.FreeBSD.org</hostid> as your
+	    installation requests them.</para>
+	</sect4>
+      </sect3>
+    </sect2>

----Next_Part(Thu_Jan_13_01:15:40_2000_518)--
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="chapter.diff.7"

 
+    <sect2 id="install-freebsd">
+      <title>Installing FreeBSD</title>
+
+      <para>Once you have completed the pre-installation step relevant to
+        your situation, you are ready to install FreeBSD!</para>
+
+      <para>Although you should not experience any difficulties, there is
+        always the chance you might, no matter how slight it is.  If this
+	is the case in your situation, then you may wish to go back and
+	re-read the relevant preparation section or sections.  Perhaps you
+	will come across something you missed the first time.  If you are
+	having hardware problems, or FreeBSD refuses to boot at all, read
+	the Hardware Guide on the boot floppy for a list of possible
+	solutions.</para>
+
+      <para>The FreeBSD boot floppies contain all of the online
+        documentation you should need to be able to navigate through an
+	installation.  If it does not, please let us know what you found
+	to be the most confusing or most lacking.  Send your comments to
+	the &a.doc;.  It is the objective of the installation program
+	(sysinstall) to be self-documenting enough that painful
+	&ldquo;step-by-step&rdquo; guides are no longer necessary.  It may
+	take us a little while to reach that objective, but nonetheless,
+	it is still our objective :-)</para>
+
+      <para>Meanwhile, you may also find the following &ldquo;typical
+        installation sequence&rdquo; to be helpful:</para>
+
+      <orderedlist>
+        <listitem>
+	  <para>Boot the <filename>kern.flp</filename> floppy and when
+	    asked, remove it and insert the
+	    <filename>mfsroot.flp</filename> and hit return.  After a
+	    boot sequence which can take anywhere from 30 seconds to 3
+	    minutes, depending on your hardware, you should be presented
+	    with a menu of initial choices.  If the
+	    <filename>kern.flp</filename> floppy does not boot at all or
+	    the boot hangs at some stage, read the Q&amp;A section of the
+	    Hardware Guide on the floppy for possible causes.</para>
 	</listitem>
 
 	<listitem>
+	  <para>Press F1.  You should see some basic usage instructions on
+	    the menu screen and general navigation.  If you have not used
+	    this menu system before then <emphasis>please</emphasis> read
+	    this thoroughly.</para>
 	</listitem>
 
 	<listitem>
+	  <para>Select the Options item and set any special preferences
+	    you may have.</para>
 	</listitem>
 
 	<listitem>
+	  <para>Select a Novice, Custom, or Express install, depending on
+	    whether or not you would like the installation to help you
+	    through a typical installation, give you a high degree of
+	    control over each step, or simply whizz through it (using
+	    reasonable defaults when possible) as fast as possible.  If
+	    you have never used FreeBSD before, the Novice installation
+	    method is most recommended.</para>
 	</listitem>
 
+	<listitem>
+	  <para>The final configuration menu choice allows you to further
+	    configure your FreeBSD installation by giving you menu-driven
+	    access to various system defaults.  Some items, like
+	    networking, may be especially important if you did a CDROM,
+	    tape, or floppy install and have not yet configured your
+	    network interfaces (assuming you have any).  Properly
+	    configuring such interfaces here will allow FreeBSD to come up
+	    on the network when you first reboot from the hard
+	    disk.</para>
+	</listitem>
+      </orderedlist>
+    </sect2>
+  </sect1>

----Next_Part(Thu_Jan_13_01:15:40_2000_518)--
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="chapter.diff.8"

 
   <sect1 id="install-hw">
+    <title>Supported Hardware</title>
 
+    <para>FreeBSD currently runs on a wide variety of ISA, VLB, EISA, and
+      PCI bus based PCs, ranging from the 386SX to Pentium class machines
+      (though the 386SX is not recommended).  Support for generic IDE or
+      ESDI drive configurations, various SCSI controllers, and network and
+      serial cards is also provided.</para>
+
+    <para>In order to run FreeBSD, a recommmended minimum of eight
+      megabytes of RAM is suggested.  Sixteen megabytes is the preferred
+      amount of RAM as you may have some trouble with anything less than
+      sixteen depending on your hardware.</para>
+
+    <para>What follows is a list of hardware currently known to work with
+      FreeBSD.  There may be other hardware that works as well, but we
+      have simply not received any confirmation of it.</para>
 
+  <sect1 id="install-trouble">
+    <title>Troubleshooting</title>
 
+    <para>The following section covers basic installation troubleshooting,
+      such as common problems people have reported.  There are also a few
+      questions and answers for people wishing to dual-boot FreeBSD with
+      MS-DOS.</para>
 
+    <sect2>
+      <title>What to do if something goes wrong...</title>
 
+      <para>Due to various limitations of the PC architecture, it is
+        impossible for probing to be 100% reliable, however, there are a
+        few things you can do if it fails.</para>
+
+      <para>Check the <link linkend="install-hw">supported
+        hardware</link> list to make sure your hardware is
+        supported.</para>
+
+      <para>If your hardware is supported and you still experience
+        lock-ups or other problems, reset your computer, and when the
+        visual kernel configuration option is given, choose it.  This will
+        allow you to go through your hardware and supply information to the
+        system about it.  The kernel on the boot disks is configured
+        assuming that most hardware devices are in their factory default
+        configuration in terms of IRQs, IO addresses, and DMA channels.  If
+        your hardware has been reconfigured, you will most likely need to
+        use the configuration editor to tell FreeBSD where to find
+        things.</para>
+
+      <para>It is also possible that a probe for a device not present will
+        cause a later probe for another device that is present to fail.  In
+        that case, the probes for the conflicting driver(s) should be
+        disabled.</para>
+
+      <warning>
+        <para>Do not disable any drivers you will need during the
+          installation, such as your screen (<devicename>sc0</devicename>).
+	  If the installation wedges or fails mysertiously after leaving
+	  the configuration editor, you have probably removed or changed
+	  something you should not have.  Reboot and try again.</para>
+      </warning>
+      
+      <para>In configuration mode, you can:</para>
+
+      <itemizedlist>
+        <listitem>
+          <para>List the device drivers installed in the kernel.</para>
+        </listitem>
 
+        <listitem>
+          <para>Change device drivers for hardware that is not present in
+	    your system.</para>
+        </listitem>
+
+        <listitem>
+          <para>Change IRQs, DRQs, and IO port addresses used by a device
+	    driver.</para>
+        </listitem>
+      </itemizedlist>
+
+      <para>After adjusting the kernel to match your hardware
+        configuration, type <command>Q</command> to boot with the new
+        settings.  Once the installation has completed, any changes you
+        made in the configuration mode will be permanent so you do not have
+        to reconfigure every time you boot.  It is still highly likely that
+        you will eventually want to build a <link
+        linkend="kernelconfig">custom kernel</link>.</para>
+    </sect2>
+
+    <sect2>
+      <title>MS-DOS User's Questions and Answers</title>
+
+      <para>Many users wish to install FreeBSD on PCs inhabited by MS-DOS.
+        Here are some commonly asked questions about installing FreeBSD on
+        such systems.</para>
+
+      <qandaset>
+        <qandaentry>
+	  <question>
+	    <para>Help, I have no space!  Do I need to delete everything 
+	      first?</para>
+	  </question>
+
+	  <answer>
+	    <para>If your machine is already running MS-DOS and has little
+	      or no free space available for the FreeBSD installation, all
+	      hope is not lost!  You may find the FIPS utility, provided
+	      in the <filename>tools</filename> directory on the FreeBSD
+	      CDROM or various FreeBSD FTP sites to be quite
+	      useful.</para>
+
+	    <para>FIPS allows you to split an existing MS-DOS parition
+	      into two pieces, preserving the original partition and
+	      allowing you to install onto the second free piece.  You
+	      first defragment your MS-DOS partition using the DOS 6.XX
+	      DEFRAG utility or the Norton Disk Tools, then run FIPS.  It
+	      will prompt you for the rest of the information it needs.
+	      Afterwards, you can reboot and install FreeBSD on the new
+	      free slice.  See the <emphasis>Distributions</emphasis> menu
+	      for an estimate of how much free space you will need for the
+	      kind of installation you want.</para>
+	  </answer>
+	</qandaentry>
+
+	<qandaentry>
+	  <question>
+	    <para>Can I use compressed MS-DOS filesystems from
+	      FreeBSD?</para>
+	  </question>
+
+	  <answer>
+	    <para>No.  If you are using a utility such as Stacker(tm) or
+	      DoubleSpace(tm), FreeBSD will only be able to use whatever
+	      portion of the filesystem you leave uncompressed.  The rest
+	      of the filesystem will show up as one large file (the
+	      stacked/double spaced file!).  <emphasis>Do not remove that
+	      file or you will probably regret it
+	      greatly!</emphasis></para>
+
+	    <para>It is probably better to create another uncompressed
+	      primary MS-DOS partition and use this for communications
+	      between MS-DOS and FreeBSD.</para>
+	  </answer>
+	</qandaentry>
+
+	<qandaentry>
+	  <question>
+	    <para>Can I mount my extended MS-DOS parition?</para>
+	  </question>
+          
+	  <answer>
+	    <para>Yes.  DOS extended partitions are mapped in at the end
+	      of the other &ldquo;slices&rdquo; in FreeBSD, e.g., your
+	      <devicename>D:</devicename> drive might be
+	      <filename>/dev/da0s5</filename>, your
+	      <devicename>E:</devicename> drive,
+	      <filename>/dev/da0s6</filename>, and so on.  This example
+	      assumes, of course, that your extended parition is on SCSI
+	      drive 0.  For IDE drives, substitute <filename>wd</filename>
+	      for <filename>da</filename> appropriately.  You otherwise
+	      mount extended paritions exactly like you would any other
+	      DOS drive, for example:</para>
+
+	    <screen>&prompt.root; <userinput>mount -t msdos /dev/da0s5 /dos_d</userinput></screen>
+	  </answer>
+	</qandaentry>
+      </qandaset>
+    </sect2>

----Next_Part(Thu_Jan_13_01:15:40_2000_518)----
