svn commit: r41554 - projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/install
Dru Lavigne
dru at FreeBSD.org
Mon May 6 11:53:23 UTC 2013
Author: dru
Date: Mon May 6 11:53:22 2013
New Revision: 41554
URL: http://svnweb.freebsd.org/changeset/doc/41554
Log:
First pass to cleanup this chapter:
- &os; and "you"
- dir tags and some (not all) acronyms
- fixes broken URLs, grammos, typos, outdated info
- removes 3.13.5 which assumes a boot floppy
- removes references to deprecated utilities partition magic,
xcopy, fdimage, doublespace
- removes unrecommended tip in Q&A
- removes 3.13.3 as floppies were covered earlier for pc98
Approved by: bcr (mentor)
Modified:
projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/install/chapter.xml
Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/install/chapter.xml
==============================================================================
--- projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/install/chapter.xml Mon May 6 11:34:28 2013 (r41553)
+++ projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/install/chapter.xml Mon May 6 11:53:22 2013 (r41554)
@@ -27,39 +27,40 @@
<!-- January 2000 -->
</chapterinfo>
- <title>Installing &os; 8.<replaceable>X</replaceable> and Earlier</title>
+ <title>Installing &os; 8.<replaceable>X</replaceable></title>
<sect1 id="install-synopsis">
<title>Synopsis</title>
<indexterm><primary>installation</primary></indexterm>
- <para>FreeBSD is provided with a text-based, easy to use installation
+ <para>&os; provides a text-based, easy to use installation
program. &os; 9.0-RELEASE and later use the installation program
- known as <application>bsdinstall</application>, with releases prior
- to 9.0-RELEASE using <application>sysinstall</application> for
- installation. This chapter describes the use of <application>sysinstall</application>
- to install &os;. The use of <application>bsdinstall</application>
+ known as &man.bsdinstall.8;
+ while &os; 8.<replaceable>X</replaceable> uses
+ &man.sysinstall.8;. This chapter describes
+ how to use &man.sysinstall.8;.
+ The use of &man.bsdinstall.8;
is covered in <xref linkend="bsdinstall"/>.</para>
<para>After reading this chapter, you will know:</para>
<itemizedlist>
<listitem>
- <para>How to create the FreeBSD installation disks.</para>
+ <para>How to create the &os; installation media.</para>
</listitem>
<listitem>
- <para>How FreeBSD refers to, and subdivides, your hard disks.</para>
+ <para>How &os; refers to and subdivides hard disks.</para>
</listitem>
<listitem>
- <para>How to start <application>sysinstall</application>.</para>
+ <para>How to start &man.sysinstall.8;.</para>
</listitem>
<listitem>
- <para>The questions <application>sysinstall</application> will ask
- you, what they mean, and how to answer them.</para>
+ <para>The questions &man.sysinstall.8; asks,
+ what they mean, and how to answer them.</para>
</listitem>
</itemizedlist>
@@ -68,19 +69,18 @@
<itemizedlist>
<listitem>
<para>Read the supported hardware list that shipped with the version
- of FreeBSD you are installing, and verify that your hardware is
+ of &os; to install, and verify that the system's hardware is
supported.</para>
</listitem>
</itemizedlist>
<note>
<para>In general, these installation instructions are written
- for &i386; (<quote>PC compatible</quote>) architecture
- computers. Where applicable, instructions specific to other
- platforms will be listed. Although this
- guide is kept as up to date as possible, you may find minor
- differences between the installer and what is shown here. It is
- suggested that you use this chapter as a general guide rather
+ for the &i386; and &os;/&arch.amd64; architectures.
+ Where applicable, instructions specific to other
+ platforms will be listed. There may be minor
+ differences between the installer and what is shown here.
+ This chapter should be used as a general guide rather
than a literal installation manual.</para>
</note>
@@ -96,23 +96,24 @@
&os; version and the hardware architecture.</para>
<para>A summary of this information is given in the following sections.
- Depending on the method you choose to install &os;, you may
- also need a floppy drive, a supported CDROM drive, and in some
- case a network adapter. This will be covered by the <xref
- linkend="install-boot-media"/>.</para>
+ Depending on the method chosen to install &os;,
+ a floppy drive, CDROM drive, or
+ network adapter may be needed. Instructions on how to
+ prepare the installation media can be found in
+ <xref linkend="install-boot-media"/>.</para>
<sect3>
<title>&os;/&arch.i386; and &os;/&arch.pc98;</title>
<para>Both &os;/&arch.i386; and &os;/&arch.pc98; require a 486 or
- better processor and at least 24 MB of RAM. You will
- need at least 150 MB of free hard drive space for the
+ better processor, at least 24 MB of RAM, and at
+ least 150 MB of free hard drive space for the
most minimal installation.</para>
<note>
- <para>In case of old configurations, most of time, getting
- more RAM and more hard drive space is more important than
- getting a faster processor.</para>
+ <para>In the case of older hardware, installing more RAM and
+ more hard drive space is often more important than
+ a faster processor.</para>
</note>
</sect3>
@@ -122,33 +123,32 @@
<para>There are two classes of processors capable of running
&os;/&arch.amd64;. The first are AMD64 processors,
including the &amd.athlon;64,
- &amd.athlon;64-FX, &amd.opteron; or better
+ &amd.athlon;64-FX, and &amd.opteron; or better
processors.</para>
- <para>The second class of processors that can use
- &os;/&arch.amd64; includes those using the &intel; EM64T
+ <para>The second class of processors
+ includes those using the &intel; EM64T
architecture. Examples of these processors include the
&intel; &core; 2 Duo, Quad, Extreme processor
families, and the &intel; &xeon; 3000, 5000, and 7000
sequences of processors.</para>
- <para>If you have a machine based on an nVidia nForce3
- Pro-150, you <emphasis>must</emphasis> use the BIOS setup to
- disable the IO APIC. If you do not have an option to do
- this, you will likely have to disable ACPI instead. There
- are bugs in the Pro-150 chipset that we have not found a
- workaround for yet.</para>
+ <para>If the machine is based on an nVidia nForce3
+ Pro-150, the BIOS setup <emphasis>must</emphasis> be used to
+ disable the IO APIC. If this option does not exist,
+ disable ACPI instead as there
+ are bugs in the Pro-150 chipset.</para>
</sect3>
<sect3>
<title>&os;/&arch.sparc64;</title>
- <para>To install &os;/&arch.sparc64;, you will need a supported
+ <para>To install &os;/&arch.sparc64;, use a supported
platform (see <xref
linkend="install-hardware-supported"/>).</para>
- <para>You will need a dedicated disk for &os;/&arch.sparc64;. It
- is not possible to share a disk with another operating
+ <para>A dedicated disk is needed for &os;/&arch.sparc64; as
+ it is not possible to share a disk with another operating
system at this time.</para>
</sect3>
</sect2>
@@ -159,14 +159,14 @@
<para>A list of supported hardware is provided with each &os;
release in the &os; Hardware Notes. This document can usually
be found in a file named <filename>HARDWARE.TXT</filename>, in
- the top-level directory of a CDROM or FTP distribution or in
- <application>sysinstall</application>'s documentation menu.
- It lists, for a given architecture, what hardware devices are
+ the top-level directory of a CDROM or FTP distribution, or in
+ &man.sysinstall.8;'s documentation menu.
+ It lists, for a given architecture, which hardware devices are
known to be supported by each release of &os;. Copies of the
supported hardware list for various releases and architectures
can also be found on the <ulink
url="http://www.FreeBSD.org/releases/index.html">Release
- Information</ulink> page of the &os; Web site.</para>
+ Information</ulink> page of the &os; website.</para>
</sect2>
</sect1>
@@ -174,28 +174,35 @@
<title>Pre-installation Tasks</title>
<sect2 id="install-inventory">
- <title>Inventory Your Computer</title>
+ <title>Inventory the Computer</title>
- <para>Before installing &os; you should attempt to inventory the
- components in your computer. The &os; installation routines will
- show you the components (hard disks, network cards, CDROM drives, and
- so forth) with their model number and manufacturer. &os; will also
+ <para>Before installing &os; it is recommended to inventory the
+ components in the computer. The &os; installation routines
+ will show components such as hard disks, network cards,
+ and CDROM drives with their model number and manufacturer.
+ &os; will also
attempt to determine the correct configuration for these devices,
- which includes information about IRQ and IO port usage. Due to the
- vagaries of PC hardware this process is not always completely
- successful, and you may need to correct &os;'s determination of
- your configuration.</para>
-
- <para>If you already have another operating system installed, such as
- &windows; or Linux, it is a good idea to use the facilities provided
- by those operating systems to see how your hardware is already
- configured. If you are not sure what settings an expansion
- card is using, you may find it printed on the card itself. Popular IRQ
- numbers are 3, 5, and 7, and IO port addresses are normally written as
- hexadecimal numbers, such as 0x330.</para>
+ including information about IRQ and I/O port usage. Due
+ to the
+ vagaries of computer hardware, this process is not always
+ completely
+ successful, and &os; may need some manual
+ configuration.</para>
- <para>We recommend you print or write down this information before
- installing &os;. It may help to use a table, like this:</para>
+ <para>If another operating system is already installed,
+ use the facilities provided
+ by that operating systems to view the hardware configuration.
+ If the settings of an expansion
+ card are not obvious, check if they are printed on the
+ card itself. Popular IRQ
+ numbers are 3, 5, and 7, and I/O port addresses are normally
+ written as
+ hexadecimal numbers, such as <literal>0x330</literal>.</para>
+
+ <para>It is recommended to print or write down this information
+ before
+ installing &os;. It may help to use a table, as seen in this
+ example:</para>
<table pgwide="1" frame="none">
<title>Sample Device Inventory</title>
@@ -211,7 +218,7 @@
<entry>IRQ</entry>
- <entry>IO port(s)</entry>
+ <entry>I/O port(s)</entry>
<entry>Notes</entry>
</row>
@@ -285,43 +292,44 @@
</tgroup>
</table>
- <para>Once the inventory of the components in your computer is
- done, you have to check if they match the hardware
- requirements of the &os; release you want to install.</para>
+ <para>Once the inventory of the components in the computer is
+ complete, check if it matches the hardware
+ requirements of the &os; release to install.</para>
</sect2>
<sect2>
- <title>Backup Your Data</title>
+ <title>Make a Backup</title>
- <para>If the computer you will be installing &os; on contains
- valuable data, then ensure you have it backed up, and that you have
- tested the backups before installing &os;. The &os;
- installation routine will prompt you before writing any
- data to your disk, but once that process has started it cannot be
+ <para>If the computer contains
+ valuable data, ensure it is backed up, and that the backup
+ has been
+ tested before installing &os;. The &os;
+ installer will prompt before writing any
+ data to disk, but once that process has started, it cannot be
undone.</para>
</sect2>
<sect2 id="install-where">
<title>Decide Where to Install &os;</title>
- <para>If you want &os; to use your entire hard disk, then there is nothing
- more to concern yourself with at this point — you can skip this
+ <para>If &os; is to be installed on the entire hard disk,
+ skip this
section.</para>
- <para>However, if you need &os; to co-exist with other operating
- systems then you need to have a rough understanding of how data is
- laid out on the disk, and how this affects you.</para>
+ <para>However, if &os; will co-exist with other operating
+ systems, a rough understanding of how data is
+ laid out on the disk is useful.</para>
<sect3 id="install-where-i386">
<title>Disk Layouts for &os;/&arch.i386;</title>
- <para>A PC disk can be divided into discrete chunks. These chunks are
- called <firstterm>partitions</firstterm>. Since
- &os; internally also has partitions, the naming
- can become confusing very quickly, therefore these
- disk chunks are referred to as disk slices or simply slices
- in &os; itself. For example, the &os; utility
- <command>fdisk</command> which operates on the PC disk partitions,
+ <para>A PC disk can be divided into discrete chunks known as
+ <firstterm>partitions</firstterm>. Since
+ &os; also has partitions, naming
+ can quickly become confusing. Therefore, these
+ disk chunks are referred to as slices
+ in &os;. For example, the &os; version of
+ &man.fdisk.8;
refers to slices instead of partitions. By design, the PC only
supports four partitions per disk. These partitions are called
<firstterm>primary partitions</firstterm>. To work around this
@@ -335,74 +343,71 @@
a number used to identify the type of data on the partition. &os;
partitions have the partition ID of <literal>165</literal>.</para>
- <para>In general, each operating system that you use will identify
- partitions in a particular way. For example, &ms-dos;, and its
- descendants, like &windows;, assign each primary and logical partition a
+ <para>In general, each operating system will identify
+ partitions in a particular way. For example,
+ &windows;, assigns each primary and logical partition a
<firstterm>drive letter</firstterm>, starting with
<devicename>C:</devicename>.</para>
- <para>&os; must be installed into a primary partition. &os; can
- keep all its data, including any files that you create, on this one
- partition. However, if you have multiple disks, then you can create a
- &os; partition on all, or some, of them. When you install &os;,
- you must have one partition available. This might be a blank
- partition that you have prepared, or it might be an existing partition
- that contains data that you no longer care about.</para>
-
- <para>If you are already using all the partitions on all your disks, then
- you will have to free one of them for &os; using the tools
- provided by the other operating systems you use (e.g.,
- <command>fdisk</command> on &ms-dos; or &windows;).</para>
-
- <para>If you have a spare partition then you can use that. However, you
- may need to shrink one or more of your existing partitions
- first.</para>
+ <para>&os; must be installed into a primary partition. If
+ there are multiple disks, a &os;
+ partition can be created
+ on all, or some, of them. When &os; is installed, at least
+ one partition must be available. This might be a blank
+ partition or it might be an existing partition whose
+ data can be overwritten.</para>
+
+ <para>If all the partitions on all the disks are in use,
+ free one of them for &os; using the tools
+ provided by an existing operating system, such as &windows;
+ <command>fdisk</command>.</para>
+
+ <para>If there is a spare partition, use that. If it is too
+ small,
+ shrink one or more existing partitions to create more
+ available space.</para>
<para>A minimal installation of &os; takes as little as 100 MB
of disk
space. However, that is a <emphasis>very</emphasis> minimal install,
- leaving almost no space for your own files. A more realistic minimum
+ leaving almost no space for files. A more realistic minimum
is 250 MB without a graphical environment, and 350 MB or
- more if you
- want a graphical user interface. If you intend to install a lot of
- third-party software as well, then you will need more space.</para>
-
- <para>You can use a commercial tool such as <application>&partitionmagic;</application>,
- or a free tool such as <application>GParted</application>,
- to resize your partitions and make space for
- &os;. Both
- <application>&partitionmagic;</application> and
- <application>GParted</application> are known to work on
- <acronym>NTFS</acronym>. <application>GParted</application>
- is available on a number of Live CD Linux distributions, such as
- <ulink url="http://www.sysresccd.org/">SystemRescueCD</ulink>.</para>
-
- <para>Problems have been reported resizing µsoft; Vista
- partitions. Having a Vista installation CDROM handy when
- attempting such an operation is recommended. As with all
- such disk maintenance tasks, a current set of backups is
- also strongly advised.</para>
+ more for
+ a graphical user interface. If other
+ third-party software will be installed,
+ even more space is needed.</para>
+
+ <para>Use a tool such as <ulink
+ url="http://gparted.sourceforge.net/">GParted</ulink>
+ to resize the partitions and make space for
+ &os;. When resizing µsoft; partitions, having a
+ &windows; installation disc handy is recommended. As with all
+ disk maintenance tasks, a current set of backups is also
+ strongly advised.</para>
<warning>
- <para>Incorrect use of these tools can delete the data on your disk.
- Be sure that you have recent, working backups before using
- them.</para>
+ <para>Incorrect use of a shrinking tool can delete the data
+ on the disk.
+ Always have a recent, working backup before using this
+ type of tool.</para>
</warning>
<example>
<title>Using an Existing Partition Unchanged</title>
- <para>Suppose that you have a computer with a single 4 GB disk
+ <para>Consider a computer with a single 4 GB disk
that
- already has a version of &windows; installed, and you have split the
- disk into two drive letters, <devicename>C:</devicename> and
+ already has a version of &windows; installed, where the
+ disk has been split into two drive letters,
+ <devicename>C:</devicename> and
<devicename>D:</devicename>, each of which is 2 GB in size.
- You have 1 GB of data on <devicename>C:</devicename>, and
+ There is 1 GB of data on <devicename>C:</devicename>,
+ and
0.5 GB of data on
<devicename>D:</devicename>.</para>
- <para>This means that your disk has two partitions on it, one per
- drive letter. You can copy all your existing data from
+ <para>This disk has two partitions, one per
+ drive letter. Copy all existing data from
<devicename>D:</devicename> to <devicename>C:</devicename>, which
will free up the second partition, ready for &os;.</para>
</example>
@@ -410,25 +415,28 @@
<example>
<title>Shrinking an Existing Partition</title>
- <para>Suppose that you have a computer with a single 4 GB disk
- that already has a version of &windows; installed. When you installed
- &windows; you created one large partition, giving you a
- <devicename>C:</devicename> drive that is 4 GB in size. You are
- currently using 1.5 GB of space, and want &os; to have 2 GB
+ <para>Consider a computer with a single 4 GB disk
+ that already has a version of &windows; installed. When
+ &windows; was installed, it created one large partition,
+ a
+ <devicename>C:</devicename> drive that is 4 GB in size.
+ Currently, 1.5 GB of space is used, and &os; should
+ have 2 GB
of space.</para>
- <para>In order to install &os; you will need to either:</para>
+ <para>In order to install &os;, either:</para>
<orderedlist>
<listitem>
- <para>Backup your &windows; data, and then reinstall &windows;,
+ <para>Backup the &windows; data and then reinstall
+ &windows;,
asking for a 2 GB partition at install time.</para>
</listitem>
<listitem>
- <para>Use one of the tools such as <application>&partitionmagic;</application>,
- described above, to shrink your &windows;
- partition.</para>
+ <para>Use a tool
+ to shrink the &windows;
+ partition.</para>
</listitem>
</orderedlist>
</example>
@@ -437,21 +445,24 @@
</sect2>
<sect2>
- <title>Collect Your Network Configuration Details</title>
+ <title>Collect the Network Configuration Details</title>
- <para>If you intend to connect to a network as part of your &os;
- installation (for example, if you will be installing from an FTP
+ <para>Before
+ installing from an FTP
site or an
- NFS server), then you need to know your network configuration. You
- will be prompted for this information during the installation so that
- &os; can connect to the network to complete the install.</para>
+ <acronym>NFS</acronym> server, make note of the network
+ configuration. The
+ installer
+ will prompt for this information so that
+ it can connect to the network to complete the
+ installation.</para>
<sect3>
<title>Connecting to an Ethernet Network or Cable/DSL Modem</title>
- <para>If you connect to an Ethernet network, or you have an Internet
- connection using an Ethernet adapter via cable or DSL, then you will
- need the following information:</para>
+ <para>If using an Ethernet network or an Internet
+ connection using an Ethernet adapter via cable or DSL, the
+ following information is needed:</para>
<orderedlist>
<listitem>
@@ -475,32 +486,35 @@
</listitem>
</orderedlist>
- <para>If you do not know this information, then ask your system
- administrator or service provider. They may say that this
- information is assigned automatically, using
- <firstterm>DHCP</firstterm>. If so, make a note of this.</para>
+ <para>If this information is unknown, ask the system
+ administrator or service provider. Make note if this
+ information is assigned automatically using
+ <firstterm>DHCP</firstterm>.</para>
</sect3>
<sect3>
<title>Connecting Using a Modem</title>
- <para>If you dial up to an ISP using a regular modem then you can
- still install &os; over the Internet, it will just take a very
+ <para>If using a dialup modem,
+ &os; can still be installed over the Internet, it will just
+ take a very
long time.</para>
<para>You will need to know:</para>
<orderedlist>
<listitem>
- <para>The phone number to dial for your ISP</para>
+ <para>The phone number to dial the Internet Service
+ Provider (<acronym>ISP</acronym>)</para>
</listitem>
<listitem>
- <para>The COM: port your modem is connected to</para>
+ <para>The COM: port the modem is connected to</para>
</listitem>
<listitem>
- <para>The username and password for your ISP account</para>
+ <para>The username and password for the
+ <acronym>ISP</acronym> account</para>
</listitem>
</orderedlist>
</sect3>
@@ -508,28 +522,30 @@
<sect2>
<title>Check for &os; Errata</title>
- <para>Although the &os; project strives to ensure that each release
+ <para>Although the &os; Project strives to ensure that each
+ release
of &os; is as stable as possible, bugs do occasionally creep into
- the process. On very rare occasions those bugs affect the
+ the process. On rare occasions those bugs affect the
installation process. As these problems are discovered and fixed, they
are noted in the <ulink url="http://www.FreeBSD.org/releases/&rel.current;R/errata.html">&os; Errata</ulink>,
- which is found on the &os; web site. You
- should check the errata before installing to make sure that there are
- no late-breaking problems which you should be aware of.</para>
+ which is found on the &os; website.
+ Check the errata before installing to make sure that there are
+ no late-breaking problems to be aware of.</para>
- <para>Information about all the releases, including the errata for each
+ <para>Information about all releases, including the errata for
+ each
release, can be found on the
<ulink
url="&url.base;/releases/index.html">release
information</ulink> section of the
<ulink
- url="&url.base;/index.html">&os; web site</ulink>.</para>
+ url="&url.base;/index.html">&os; website</ulink>.</para>
</sect2>
<sect2>
<title>Obtain the &os; Installation Files</title>
- <para>The &os; installation process can install &os; from files
+ <para>The &os; installer can install &os; from files
located in any of the following places:</para>
<itemizedlist>
@@ -548,11 +564,7 @@
</listitem>
<listitem>
- <para>A SCSI or QIC tape</para>
- </listitem>
-
- <listitem>
- <para>Floppy disks</para>
+ <para>Floppy disks (&os;/&arch.pc98; only)</para>
</listitem>
</itemizedlist>
@@ -560,8 +572,8 @@
<title>Network</title>
<listitem>
- <para>An FTP site, going through a firewall, or using an HTTP proxy,
- as necessary</para>
+ <para>An FTP site through a firewall or using an HTTP
+ proxy</para>
</listitem>
<listitem>
@@ -573,14 +585,14 @@
</listitem>
</itemizedlist>
- <para>If you have purchased &os; on CD or DVD then you already have
- everything you need, and should proceed to the next section
- (<xref linkend="install-boot-media"/>).</para>
+ <para>If installing from a purchased &os; CD/DVD,
+ skip ahead to
+ <xref linkend="install-boot-media"/>.</para>
- <para>If you have not obtained the &os; installation files you should
+ <para>To obtain the &os; installation files,
skip ahead to <xref linkend="install-diff-media"/> which explains how
- to prepare to install &os; from any of the above. After reading
- that section, you should come back here, and read on to
+ to prepare the installation media. After reading
+ that section, come back here and read on to
<xref linkend="install-boot-media"/>.</para>
</sect2>
@@ -588,18 +600,19 @@
<title>Prepare the Boot Media</title>
<para>The &os; installation process is started by booting the
- computer into the &os; installer—it is not a program you run
+ computer into the &os; installer. It is not a program that
+ can be run
within another operating system. The computer normally boots
using the operating system installed on the hard disk, but it
can also be configured to boot from a CDROM or from a USB
disk.</para>
<tip>
- <para>If you have &os; on CDROM or DVD (either one you purchased
- or you prepared yourself), and your computer allows you to boot from
- the CDROM or DVD (typically a BIOS option called <quote>Boot
- Order</quote> or similar), then you can skip this section. The
- &os; CDROM and DVD images are bootable and can be used to install
+ <para>If installing from a CD/DVD to a
+ computer whose BIOS supports booting from
+ the CD/DVD, skip this section. The
+ &os; CD/DVD images are bootable and can be used to
+ install
&os; without any other special preparation.</para>
</tip>
@@ -611,36 +624,38 @@
<title>Acquire the Memory Stick Image</title>
<para>Memory stick images for
- &os; 8.<replaceable>X</replaceable> and earlier can be downloaded from
+ &os; 8.<replaceable>X</replaceable> can be downloaded
+ from
the <filename class="directory">ISO-IMAGES/</filename>
directory at
<literal>ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/<replaceable>arch</replaceable>/ISO-IMAGES/<replaceable>version</replaceable>/&os;-<replaceable>version</replaceable>-RELEASE-<replaceable>arch</replaceable>-memstick.img</literal>.
Replace <replaceable>arch</replaceable> and
<replaceable>version</replaceable> with the
- architecture and the version number which you want to
- install, respectively. For example, the memory stick
+ architecture and the version number to
+ install. For example, the memory stick
images for &os;/&arch.i386; &rel2.current;-RELEASE are
available from <ulink
url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/&arch.i386;/ISO-IMAGES/&rel2.current;/&os;-&rel2.current;-RELEASE-&arch.i386;-memstick.img"></ulink>.</para>
<tip>
<para>A different directory path is used for
- &os; 9.0-RELEASE and later versions. Details of
- download and installation of &os; 9.0-RELEASE and
- later is covered in <xref linkend="bsdinstall"/>.</para>
+ &os; 9.0-RELEASE and later versions. How to
+ download and install
+ &os; 9.<replaceable>X</replaceable>
+ is covered in <xref linkend="bsdinstall"/>.</para>
</tip>
<para>The memory stick image has a <filename>.img</filename>
extension. The <filename
class="directory">ISO-IMAGES/</filename> directory
- contains a number of different images, and the one you
- will need to use will depend on the version of &os; you
- are installing, and in some cases, the hardware you are
- installing to.</para>
+ contains a number of different images and the one to
+ use depends on the version of &os; and the
+ type of media supported by the hardware being installed
+ to.</para>
<important>
<para>Before proceeding, <emphasis>back up</emphasis> the
- data you currently have on your USB stick, as this
+ data on the USB stick, as this
procedure will <emphasis>erase</emphasis> it.</para>
</important>
</step>
@@ -653,29 +668,32 @@
<warning>
<para>The example below
- lists <filename class="devicefile">/dev/da0</filename> as the
- target device where the image will be written. Be very careful
- that you have the correct device as the output target, or you
- may destroy your existing data.</para>
+ uses <filename class="devicefile">/dev/da0</filename>
+ as the
+ target device where the image will be written. Be
+ <emphasis>very</emphasis> careful
+ to use the correct device as the output target, as
+ the data on that device will be destroyed.</para>
</warning>
<step>
<title>Writing the Image with &man.dd.1;</title>
<para>The <filename>.img</filename> file
- is <emphasis>not</emphasis> a regular file you copy to the
+ is <emphasis>not</emphasis> a regular file that can
+ just be copied to the
memory stick. It is an image of the complete contents of the
- disk. This means that you <emphasis>cannot</emphasis> simply
- copy files from one disk to another. Instead, you must use
- &man.dd.1; to write the image directly to the disk:</para>
+ disk. This means that
+ &man.dd.1; must be used to write the image directly to
+ the disk:</para>
<screen>&prompt.root; <userinput>dd if=&os;-&rel2.current;-RELEASE-&arch.i386;-memstick.img of=/dev/<replaceable>da0</replaceable> bs=64k</userinput></screen>
<para>If an
<computeroutput>Operation not permitted</computeroutput>
error is displayed, make certain that the target device
- is not in use, mounted, or being automounted by some
- well-intentioned utility program. Then try
+ is not in use, mounted, or being automounted by
+ another program. Then try
again.</para>
</step>
</procedure>
@@ -684,8 +702,10 @@
<title>Using &windows; To Write the Image</title>
<warning>
- <para>Make sure you use the correct drive letter as the output
- target, or you may overwrite and destroy existing data.</para>
+ <para>Make sure to use the correct drive letter as the
+ output
+ target, as this command will overwrite and destroy
+ any existing data on the specified device.</para>
</warning>
<step>
@@ -740,29 +760,32 @@
<literal>kern*</literal>.</para>
<important>
- <para>Your FTP program must use <emphasis>binary mode</emphasis>
- to download these disk images. Some web browsers have been
- known to use <emphasis>text</emphasis> (or
- <emphasis>ASCII</emphasis>) mode, which will be apparent if you
- cannot boot from the disks.</para>
+ <para>The FTP program must use <emphasis>binary
+ mode</emphasis>
+ to download these disk images. Some web browsers
+ use <emphasis>text</emphasis> or
+ <emphasis>ASCII</emphasis> mode, which will be apparent
+ if
+ the disks are not bootable.</para>
</important>
</step>
<step>
<title>Prepare the Floppy Disks</title>
- <para>Prepare one floppy disk per image file you had to
- download. It is imperative that these disks are free from
- defects. The easiest way to test this is to format the disks
- for yourself. Do not trust pre-formatted floppies. The format
+ <para>Prepare one floppy disk per downloaded image file.
+ It is imperative that these disks are free from
+ defects. The easiest way to test this is to reformat the
+ disks.
+ Do not trust pre-formatted floppies. The format
utility in &windows; will not tell about the presence of
bad blocks, it simply marks them as <quote>bad</quote>
- and ignores them. It is advised that you use brand new
- floppies if choosing this installation route.</para>
+ and ignores them. It is advised to use brand new
+ floppies.</para>
<important>
- <para>If you try to install &os; and the installation
- program crashes, freezes, or otherwise misbehaves, one of
+ <para>If the installer
+ crashes, freezes, or otherwise misbehaves, one of
the first things to suspect is the floppies. Write
the floppy image files to new disks and try
again.</para>
@@ -773,47 +796,44 @@
<title>Write the Image Files to the Floppy Disks</title>
<para>The <filename>.flp</filename> files are
- <emphasis>not</emphasis> regular files you copy to the disk.
+ <emphasis>not</emphasis> regular files that can be copied
+ to the disk.
They are images of the complete contents of the
- disk. This means that you <emphasis>cannot</emphasis> simply
- copy files from one disk to another.
- Instead, you must use specific tools to write the
+ disk.
+ Specific tools must be used to write the
images directly to the disk.</para>
<indexterm><primary>DOS</primary></indexterm>
- <para>If you are creating the floppies on a computer running
- &ms-dos; / &windows;, then we provide a tool to do
- this called <command>fdimage</command>.</para>
-
- <para>If you are using the floppies from the CDROM, and your
- CDROM is the <devicename>E:</devicename> drive, then you would
- run this:</para>
+ <para>&os; provides a tool called
+ <command>rawrite</command> for creating the floppies on a
+ computer running
+ &windows;. This tool can be downloaded from
+ <literal>ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/pc98/<replaceable>
+ version</replaceable>-RELEASE/tools/</literal>
+ on the &os; FTP site. Download this tool, insert a
+ floppy, then specify the filename to write to the floppy
+ drive:</para>
- <screen><prompt>E:\></prompt> <userinput>tools\fdimage floppies\boot.flp A:</userinput></screen>
+ <screen><prompt>C:\></prompt> <userinput>rawrite boot.flp A:</userinput></screen>
<para>Repeat this command for each <filename>.flp</filename>
file, replacing the floppy disk each time, being sure to label
- the disks with the name of the file that you copied to them.
- Adjust the command line as necessary, depending on where you have
- placed the <filename>.flp</filename> files. If you do not have
- the CDROM, then <command>fdimage</command> can be downloaded from
- the <ulink
- url="ftp://ftp.FreeBSD.org/pub/FreeBSD/tools/"><filename class="directory">tools</filename>
- directory</ulink> on the &os; FTP site.</para>
-
- <para>If you are writing the floppies on a &unix; system (such as
- another &os; system) you can use the &man.dd.1; command to
- write the image files directly to disk. On &os;, you would
+ the disks with the name of the file.
+ Adjust the command line as necessary, depending on where
+ the <filename>.flp</filename> files are located.</para>
+
+ <para>When writing the floppies on a &unix;-like system,
+ such as
+ another &os; system, use &man.dd.1; to
+ write the image files directly to disk. On &os;,
run:</para>
<screen>&prompt.root; <userinput>dd if=boot.flp of=/dev/fd0</userinput></screen>
<para>On &os;, <filename>/dev/fd0</filename> refers to the
- first floppy disk (the <devicename>A:</devicename> drive).
- <filename>/dev/fd1</filename> would be the
- <devicename>B:</devicename> drive, and so on. Other &unix;
+ first floppy disk. Other &unix;
variants might have different names for the floppy disk
- devices, and you will need to check the documentation for the
+ device, so check the documentation for the
system as necessary.</para>
</step>
</procedure>
@@ -826,8 +846,9 @@
<title>Starting the Installation</title>
<important>
- <para>By default, the installation will not make any changes to your
- disk(s) until you see the following message:</para>
+ <para>By default, the installer will not make any changes to
+ the
+ disk(s) until after the following message:</para>
<literallayout class="monospaced">Last Chance: Are you SURE you want continue the installation?
@@ -836,10 +857,12 @@ STRONGLY ENCOURAGE YOU TO MAKE PROPER BA
We can take no responsibility for lost disk contents!</literallayout>
- <para>The install can be exited at any time prior to the final
- warning without changing the contents of the hard drive. If you are
- concerned that you have configured something incorrectly you can just
- turn the computer off before this point, and no damage will be
+ <para>The install can be exited at any time prior to this final
+ warning without changing the contents of the hard drive. If
+ there is a
+ concern that something is configured incorrectly,
+ turn the computer off before this point, and no damage
+ will be
done.</para>
</important>
@@ -851,10 +874,6 @@ We can take no responsibility for lost d
<procedure>
<step>
- <para>Start with your computer turned off.</para>
- </step>
-
- <step>
<para>Turn on the computer. As it starts it should display an
option to enter the system set up menu, or BIOS, commonly reached
by keys like <keycap>F2</keycap>, <keycap>F10</keycap>,
@@ -863,9 +882,10 @@ We can take no responsibility for lost d
<keycap>Alt</keycap>
<keycap>S</keycap>
</keycombo>. Use whichever keystroke is indicated on screen. In
- some cases your computer may display a graphic while it starts.
+ some cases the computer may display a graphic while it
+ starts.
Typically, pressing <keycap>Esc</keycap> will dismiss the graphic
- and allow you to see the necessary messages.</para>
+ and display the boot messages.</para>
</step>
<step>
@@ -875,11 +895,10 @@ We can take no responsibility for lost d
<literal>Floppy</literal>, <literal>CDROM</literal>,
<literal>First Hard Disk</literal>, and so on.</para>
- <para>If you are booting from the CDROM then make sure that
- the CDROM is selected. If you are booting from a USB disk or
- a floppy disk then
- make sure that is selected instead. In case of doubt, you
- should consult the manual that came with your computer, and/or its
+ <para>If booting from the CD/DVD, make sure that
+ the CDROM drive is selected. If booting from a USB disk,
+ make sure that it is selected instead. When in doubt,
+ consult the manual that came with the computer or its
motherboard.</para>
<para>Make the change, then save and exit. The computer should now
@@ -887,12 +906,13 @@ We can take no responsibility for lost d
</step>
<step>
- <para>If you prepared a <quote>bootable</quote> USB stick, as described in
- <xref linkend="install-boot-media"/>, then plug in your USB
+ <para>If using a prepared a <quote>bootable</quote> USB
+ stick, as described in
+ <xref linkend="install-boot-media"/>, plug in the USB
stick before turning on the computer.</para>
- <para>If you are booting from CDROM, then you will need to turn on
- the computer, and insert the CDROM at the first
+ <para>If booting from CD/DVD, turn on
+ the computer, and insert the CD/DVD at the first
opportunity.</para>
<note>
@@ -904,32 +924,33 @@ We can take no responsibility for lost d
installer.</para>
</note>
- <para>If your computer starts up as normal and loads your existing
+ <para>If the computer starts up as normal and loads the
+ existing
operating system, then either:</para>
<orderedlist>
<listitem>
<para>The disks were not inserted early enough in the boot
- process. Leave them in, and try restarting your
+ process. Leave them in, and try restarting the
computer.</para>
</listitem>
<listitem>
- <para>The BIOS changes earlier did not work correctly. You
- should redo that step until you get the right option.</para>
+ <para>The BIOS changes did not work correctly.
+ Redo that step until the right option is
+ selected.</para>
</listitem>
<listitem>
- <para>Your particular BIOS does not support booting from
+ <para>That particular BIOS does not support booting from
the desired media.</para>
</listitem>
</orderedlist>
</step>
*** DIFF OUTPUT TRUNCATED AT 1000 LINES ***
More information about the svn-doc-projects
mailing list