svn commit: r44888 - head/en_US.ISO8859-1/books/handbook/bsdinstall
Dru Lavigne
dru at FreeBSD.org
Tue May 20 19:36:04 UTC 2014
Author: dru
Date: Tue May 20 19:36:04 2014
New Revision: 44888
URL: http://svnweb.freebsd.org/changeset/doc/44888
Log:
Editorial review of Pre-installation tasks.
Format these tasks as a procedure.
Move disk size recommendations to similar paragraph in minimum
hardware section.
Sponsored by: iXsystems
Modified:
head/en_US.ISO8859-1/books/handbook/bsdinstall/chapter.xml
Modified: head/en_US.ISO8859-1/books/handbook/bsdinstall/chapter.xml
==============================================================================
--- head/en_US.ISO8859-1/books/handbook/bsdinstall/chapter.xml Tue May 20 19:25:43 2014 (r44887)
+++ head/en_US.ISO8859-1/books/handbook/bsdinstall/chapter.xml Tue May 20 19:36:04 2014 (r44888)
@@ -153,10 +153,17 @@
<para>A &os; installation will require at least 64 MB of
<acronym>RAM</acronym> and 1.1 GB of free hard drive
- space for the most minimal installation. It is recommended to
+ space for the most minimal installation. However, that is a
+ <emphasis>very</emphasis> minimal install, leaving almost no
+ free space. A more realistic minimum is 3 GB without a
+ graphical environment, and 5 GB or more if a graphical
+ user interface will be used. Third-party application
+ software requires more space. It is recommended to
increase <acronym>RAM</acronym> and hard drive space to meet
the needs of the applications that will be used and the amount
- of data that will be stored. The processor requirements for
+ of data that will be stored.</para>
+
+ <para>The processor requirements for
each architecture can be summarized as follows:</para>
<variablelist>
@@ -268,53 +275,50 @@
<sect1 xml:id="bsdinstall-pre">
<title>Pre-Installation Tasks</title>
- <sect2>
+ <para>Once it has been determined that the system meets the
+ minimum hardware requirements for installing &os;, the
+ installation file should be downloaded and the installation
+ media prepared. Before doing this, check that the system is
+ ready for an installation by verifying the items in this
+ checklist:</para>
+
+ <procedure>
+ <step>
<title>Back Up Important Data</title>
- <para>Back up all important data on the target computer where
- &os; will be installed. Test the backups before continuing.
- The &os; installer will ask before making changes to the disk,
- but once the process has started it cannot be undone.</para>
- </sect2>
+ <para>Before installing any operating system,
+ <emphasis>always</emphasis> backup all important data first.
+ Do not store the backup on the system being installed.
+ Instead, save the data to a removable disk such as a
+ <acronym>USB</acronym> drive, another system on the network,
+ or an online backup service. Test the backup before
+ starting the installation to make sure it contains all of the
+ needed files. Once the installer formats the system's disk,
+ all data stored on that disk will be lost.</para>
+ </step>
- <sect2 xml:id="bsdinstall-where">
+ <step>
<title>Decide Where to Install &os;</title>
- <para>If &os; will be the only operating system installed, and
- will be allowed to use the entire hard disk, the rest of this
- section can be skipped. But if &os; will share the disk with
- other operating systems, an understanding of disk layout is
- useful during the installation.</para>
-
- <sect3 xml:id="bsdinstall-where-i386">
- <title>Disk Layouts for &os;/&arch.i386; and
- &os;/&arch.amd64;</title>
-
- <para>Hard disks can be divided into multiple sections. These
- sections are called
- <firstterm>partitions</firstterm>.</para>
-
- <para>There are two ways of dividing a disk into partitions.
- A traditional <firstterm>Master Boot Record</firstterm>
+ <para>If &os; will be the only operating system installed, this
+ step can be skipped. But if &os; will share the disk with
+ another operating system, decide which disk or partition will
+ be used for &os;.</para>
+
+ <para>In the &arch.i386; and &arch.amd64; architectures, disks
+ can be divided into multiple partitions using one of two
+ partitioning schemes. A traditional <firstterm>Master Boot Record</firstterm>
(<acronym>MBR</acronym>) holds a partition table defining up
to four <firstterm>primary partitions</firstterm>. For
- historical reasons, &os; calls primary partitions
- <firstterm>slices</firstterm>. A limit of only four
- partitions is restrictive for large disks, so one of these
+ historical reasons, &os; calls these primary partitions
+ <firstterm>slices</firstterm>. One of these
primary partitions can be made into an <firstterm>extended
- partition</firstterm>. Multiple <firstterm>logical
- partitions</firstterm> may then be created inside the
- extended partition. This may sound a little unwieldy, and
- it is.</para>
-
- <para>The <firstterm>GUID Partition Table</firstterm>
+ partition</firstterm> containing multiple <firstterm>logical
+ partitions</firstterm>. The <firstterm>GUID Partition Table</firstterm>
(<acronym>GPT</acronym>) is a newer and simpler method of
- partitioning a disk. <acronym>GPT</acronym> is far more
- versatile than the traditional <acronym>MBR</acronym>
- partition table. Common <acronym>GPT</acronym>
+ partitioning a disk. Common <acronym>GPT</acronym>
implementations allow up to 128 partitions per disk,
- eliminating the need for inconvenient workarounds like
- logical partitions.</para>
+ eliminating the need for logical partitions.</para>
<warning>
<para>Some older operating systems, like &windows; XP,
@@ -324,111 +328,57 @@
partitioning is required.</para>
</warning>
- <para>&os;'s standard boot loader requires either a primary or
- <acronym>GPT</acronym> partition. Refer to <xref
- linkend="boot"/> for more information about the &os;
- booting process. If all of the primary or
+ <para>The &os; boot loader requires either a primary or
+ <acronym>GPT</acronym> partition. If all of the primary or
<acronym>GPT</acronym> partitions are already in use, one
- must be freed for &os;.</para>
-
- <para>A minimal installation of &os; takes as little as
- 1 GB of disk space. However, that is a
- <emphasis>very</emphasis> minimal install, leaving almost no
- free space. A more realistic minimum is 3 GB without a
- graphical environment, and 5 GB or more if a graphical
- user interface will be used. Third-party application
- software requires more space.</para>
+ must be freed for &os;. To create a partition without
+ deleting existing data, use a partition resizing tool to
+ shrink an existing partition and create a new partition
+ using the freed space.</para>
<para>A variety of free and commercial partition resizing
tools are listed at <link
xlink:href="http://en.wikipedia.org/wiki/List_of_disk_partitioning_software">http://en.wikipedia.org/wiki/List_of_disk_partitioning_software</link>.
<application>GParted Live</application> (<link
xlink:href="http://gparted.sourceforge.net/livecd.php">http://gparted.sourceforge.net/livecd.php</link>)
- is a free Live CD which includes the
+ is a free live <acronym>CD</acronym> which includes the
<application>GParted</application> partition editor.
<application>GParted</application> is also included with
- many other Linux Live CD distributions.</para>
+ many other Linux live <acronym>CD</acronym> distributions.</para>
<warning>
- <para>Disk partition applications can destroy data. Make a
- full backup and verify its integrity before modifying disk
+ <para>When used properly, disk shrinking utilities can
+ safely create space for creating a new partition.
+ Since the possibility of selecting the wrong partition
+ exists, always backup any important data
+ and verify the integrity of the backup before modifying disk
partitions.</para>
</warning>
- <para>Resizing µsoft; Vista partitions can be
- difficult. A Vista installation <acronym>CD</acronym> can
- be useful when attempting such an operation.</para>
-
- <example>
- <title>Using an Existing Partition</title>
-
- <para>A &windows; computer has a single 40 GB disk that
- has been split into two 20 GB partitions. &windows;
- calls them <filename>C:</filename> and
- <filename>D:</filename>. The <filename>C:</filename>
- partition contains 10 GB of data, and the
- <filename>D:</filename> partition contains 5 GB of
- data.</para>
-
- <para>Moving the data from <filename>D:</filename> to
- <filename>C:</filename> frees up the second partition to
- be used for &os;.</para>
- </example>
-
- <example>
- <title>Shrinking an Existing Partition</title>
-
- <para>A &windows; computer has a single 40 GB disk and
- one large partition using the whole disk. &windows; shows
- this 40 GB partition as a single
- <filename>C:</filename>. 15 GB of space is being
- used. The goal is to end up with &windows; in a
- 20 GB partition, and have another 20 GB
- partition for &os;.</para>
-
- <para>There are two ways to do this:</para>
-
- <orderedlist>
- <listitem>
- <para>Back up any &windows; data. Then reinstall
- &windows;, creating a 20 GB partition during the
- install.</para>
- </listitem>
-
- <listitem>
- <para>Use a partition resizing tool like
- <application>GParted</application> to shrink the
- &windows; partition and create a new partition in the
- freed space for &os;.</para>
- </listitem>
- </orderedlist>
- </example>
-
<para>Disk partitions containing different operating systems
- make it possible to run any one of those operating systems
- at a time. An alternative method that allows running
- multiple operating systems at the same time is covered in
- <xref linkend="virtualization"/>.</para>
- </sect3>
- </sect2>
+ make it possible to install multiple operating systems on one computer.
+ An alternative is to use virtualization (<xref
+ linkend="virtualization"/>) which allows
+ multiple operating systems to run at the same time without
+ modifying any disk partitions.</para>
+ </step>
- <sect2 xml:id="bsdinstall-collect-network-information">
+ <step>
<title>Collect Network Information</title>
- <para>Some &os; installation methods need a network connection
- to download files. To connect to an Ethernet network (or
- cable or <acronym>DSL</acronym> modem with an Ethernet
- interface), the installer will request some information about
- the network.</para>
+ <para>Some &os; installation methods require a network connection
+ in order to download the installation files. After any
+ installation, the installer will offer to setup the system's
+ network interfaces.</para>
- <para><acronym>DHCP</acronym> is commonly used to provide
+ <para>If the network has a <acronym>DHCP</acronym> server, it can be used to provide
automatic network configuration. If <acronym>DHCP</acronym>
- is not available, this network information must be obtained
- from the local network administrator or service
+ is not available, the follwoing network information for the system must be obtained
+ from the local network administrator or Internet service
provider:</para>
- <orderedlist>
- <title>Network Information</title>
+ <orderedlist xml:id="bsdinstall-collect-network-information">
+ <title>Required Network Information</title>
<listitem>
<para><acronym>IP</acronym>
@@ -440,21 +390,22 @@
</listitem>
<listitem>
- <para>Default router <acronym>IP</acronym> address</para>
+ <para><acronym>IP</acronym> address of default
+ gateway</para>
</listitem>
<listitem>
- <para>Domain name of the local network</para>
+ <para>Domain name of the network</para>
</listitem>
<listitem>
- <para><acronym>DNS</acronym>
- server <acronym>IP</acronym> address(es)</para>
+ <para><acronym>IP</acronym> addresses of the network's
+ <acronym>DNS</acronym> servers</para>
</listitem>
</orderedlist>
- </sect2>
+ </step>
- <sect2>
+ <step>
<title>Check for &os; Errata</title>
<para>Although the &os; Project strives to ensure that each
@@ -470,7 +421,8 @@
<para>Information and errata for all the releases can be found
on the release information section of the &os; web site (<link
xlink:href="&url.base;/releases/index.html">http://www.freebsd.org/releases/index.html</link>).</para>
- </sect2>
+ </step>
+ </procedure>
<sect2 xml:id="bsdinstall-installation-media">
<title>Prepare the Installation Media</title>
More information about the svn-doc-head
mailing list