White space fix only. Translators can ignore.
Sponsored by: iXsystems
This commit is contained in:
parent
80e5917c7a
commit
97db393348
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=44890
1 changed files with 330 additions and 331 deletions
|
@ -80,22 +80,21 @@
|
|||
program used by &os; 8.x, is covered in <xref
|
||||
linkend="install"/>.</para>
|
||||
|
||||
<para>In general, the installation instructions in this chapter are written
|
||||
for the &i386; and <acronym>AMD64</acronym> architectures.
|
||||
Where applicable, instructions specific to other
|
||||
platforms will be listed. There may be minor differences
|
||||
between the installer and what is shown here, so use this
|
||||
chapter as a general guide rather than as a set of literal
|
||||
instructions.</para>
|
||||
<para>In general, the installation instructions in this chapter
|
||||
are written for the &i386; and <acronym>AMD64</acronym>
|
||||
architectures. Where applicable, instructions specific to other
|
||||
platforms will be listed. There may be minor differences
|
||||
between the installer and what is shown here, so use this
|
||||
chapter as a general guide rather than as a set of literal
|
||||
instructions.</para>
|
||||
|
||||
<note>
|
||||
<para>Users who prefer to install &os; using a graphical
|
||||
installer may be interested in
|
||||
installer may be interested in
|
||||
<application>pc-sysinstall</application>, the installer used
|
||||
by the
|
||||
PC-BSD Project. It can be used to install either a graphical
|
||||
desktop (PC-BSD) or a command line version of &os;. Refer to
|
||||
the PC-BSD Users Handbook for details (<link
|
||||
by the PC-BSD Project. It can be used to install either a
|
||||
graphical desktop (PC-BSD) or a command line version of &os;.
|
||||
Refer to the PC-BSD Users Handbook for details (<link
|
||||
xlink:href="http://wiki.pcbsd.org/index.php/PC-BSD%C2%AE_Users_Handbook/10.1">http://wiki.pcbsd.org/index.php/PC-BSD%C2%AE_Users_Handbook/10.1</link>).</para>
|
||||
</note>
|
||||
|
||||
|
@ -141,135 +140,136 @@
|
|||
<sect1 xml:id="bsdinstall-hardware">
|
||||
<title>Minimum Hardware Requirements</title>
|
||||
|
||||
<para>The hardware requirements to install &os; vary by the
|
||||
&os; version and the hardware architecture. Hardware
|
||||
architectures and devices supported by a &os;
|
||||
release are listed in the Hardware Notes file. Usually named
|
||||
<filename>HARDWARE.TXT</filename>, the file is located in the
|
||||
root directory of the release media. Copies of the supported
|
||||
hardware list are also available on the Release Information
|
||||
page of the &os; web site (<link
|
||||
xlink:href="&url.base;/releases/index.html">http://www.FreeBSD.org/releases/index.html</link>).</para>
|
||||
<para>The hardware requirements to install &os; vary by the &os;
|
||||
version and the hardware architecture. Hardware architectures
|
||||
and devices supported by a &os; release are listed in the
|
||||
Hardware Notes file. Usually named
|
||||
<filename>HARDWARE.TXT</filename>, the file is located in the
|
||||
root directory of the release media. Copies of the supported
|
||||
hardware list are also available on the Release Information page
|
||||
of the &os; web site (<link
|
||||
xlink:href="&url.base;/releases/index.html">http://www.FreeBSD.org/releases/index.html</link>).</para>
|
||||
|
||||
<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. 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.</para>
|
||||
<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. 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.</para>
|
||||
|
||||
<para>The processor requirements for
|
||||
each architecture can be summarized as follows:</para>
|
||||
<para>The processor requirements for each architecture can be
|
||||
summarized as follows:</para>
|
||||
|
||||
<variablelist>
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term>&arch.amd64;</term>
|
||||
<listitem>
|
||||
<para>There are two classes of processors capable of running
|
||||
&arch.amd64;. The first are <acronym>AMD64</acronym> processors,
|
||||
including the &amd.athlon;64 and
|
||||
&amd.opteron; processors.</para>
|
||||
<para>There are two classes of processors capable of running
|
||||
&arch.amd64;. The first are <acronym>AMD64</acronym>
|
||||
processors, including the &amd.athlon;64 and &amd.opteron;
|
||||
processors.</para>
|
||||
|
||||
<para>The second class of processors includes those using the
|
||||
&intel; EM64T architecture. Examples of these
|
||||
processors include all multi-core &intel; &xeon;
|
||||
processors except Sossaman, the single-core
|
||||
&intel; &xeon; processors Nocona, Irwindale, Potomac,
|
||||
and Cranford, the &intel; &core; 2 (not Core Duo)
|
||||
and later processors, all &intel; &pentium; D processors, the
|
||||
&intel; &pentium; 4s and Celeron Ds using the Cedar
|
||||
Mill core, and some &intel; &pentium; 4s and Celeron Ds
|
||||
using the Prescott core.</para>
|
||||
<para>The second class of processors includes those using
|
||||
the &intel; EM64T architecture. Examples of these
|
||||
processors include all multi-core &intel; &xeon;
|
||||
processors except Sossaman, the single-core
|
||||
&intel; &xeon; processors Nocona, Irwindale, Potomac,
|
||||
and Cranford, the &intel; &core; 2 (not Core
|
||||
Duo) and later processors, all &intel; &pentium; D
|
||||
processors, the &intel; &pentium; 4s and Celeron Ds
|
||||
using the Cedar Mill core, and some &intel; &pentium;
|
||||
4s and Celeron Ds using the Prescott core.</para>
|
||||
|
||||
<para>Both Uniprocessor (<acronym>UP</acronym>) and Symmetric
|
||||
Multi-processor (<acronym>SMP</acronym>) configurations are
|
||||
supported.</para>
|
||||
</listitem>
|
||||
<para>Both Uniprocessor (<acronym>UP</acronym>) and
|
||||
Symmetric Multi-processor (<acronym>SMP</acronym>)
|
||||
configurations are supported.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>&arch.i386;</term>
|
||||
<listitem>
|
||||
<para>Almost all i386-compatible processors with a floating
|
||||
point unit are supported. All &intel; processors
|
||||
486 or higher are supported.</para>
|
||||
|
||||
<para>&os; will take advantage of Physical Address Extensions
|
||||
(<acronym>PAE</acronym>) support on <acronym>CPU</acronym>s
|
||||
that support this feature. A kernel with the
|
||||
<acronym>PAE</acronym> feature enabled will detect memory
|
||||
above 4 GB and allow it to be used by the system.
|
||||
This feature places constraints on the device drivers and
|
||||
other features of &os; which may be used; refer to
|
||||
&man.pae.4; for details.</para>
|
||||
<varlistentry>
|
||||
<term>&arch.i386;</term>
|
||||
<listitem>
|
||||
<para>Almost all i386-compatible processors with a floating
|
||||
point unit are supported. All &intel; processors 486 or
|
||||
higher are supported.</para>
|
||||
|
||||
<para>&os; will take advantage of Physical Address
|
||||
Extensions (<acronym>PAE</acronym>) support on
|
||||
<acronym>CPU</acronym>s that support this feature. A
|
||||
kernel with the <acronym>PAE</acronym> feature enabled
|
||||
will detect memory above 4 GB and allow it to be used
|
||||
by the system. This feature places constraints on the
|
||||
device drivers and other features of &os; which may be
|
||||
used; refer to &man.pae.4; for details.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>ia64</term>
|
||||
<listitem>
|
||||
<para>Currently supported processors are the &itanium; and the
|
||||
&itanium; 2. Supported chipsets include the HP zx1, &intel;
|
||||
460GX, and &intel; E8870. Both Uniprocessor
|
||||
(<acronym>UP</acronym>) and Symmetric Multi-processor
|
||||
(<acronym>SMP</acronym>) configurations are supported.</para>
|
||||
</listitem>
|
||||
<para>Currently supported processors are the &itanium; and
|
||||
the &itanium; 2. Supported chipsets include the HP zx1,
|
||||
&intel; 460GX, and &intel; E8870. Both Uniprocessor
|
||||
(<acronym>UP</acronym>) and Symmetric Multi-processor
|
||||
(<acronym>SMP</acronym>) configurations are
|
||||
supported.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>pc98</term>
|
||||
<listitem>
|
||||
<para>NEC PC-9801/9821 series with almost all i386-compatible
|
||||
processors, including 80486, &pentium;, &pentium; Pro, and
|
||||
&pentium; II, are all supported. All i386-compatible processors
|
||||
by AMD, Cyrix, IBM, and IDT are also supported. EPSON
|
||||
PC-386/486/586 series, which are compatible with NEC PC-9801
|
||||
series, are supported. The NEC FC-9801/9821 and NEC SV-98
|
||||
series should be supported.</para>
|
||||
<para>NEC PC-9801/9821 series with almost all
|
||||
i386-compatible processors, including 80486, &pentium;,
|
||||
&pentium; Pro, and &pentium; II, are all supported. All
|
||||
i386-compatible processors by AMD, Cyrix, IBM, and IDT are
|
||||
also supported. EPSON PC-386/486/586 series, which are
|
||||
compatible with NEC PC-9801 series, are supported. The
|
||||
NEC FC-9801/9821 and NEC SV-98 series should be
|
||||
supported.</para>
|
||||
|
||||
<para>High-resolution mode is not supported. NEC
|
||||
PC-98XA/XL/RL/XL^2, and NEC PC-H98 series are supported in
|
||||
normal (PC-9801 compatible) mode only. The
|
||||
<acronym>SMP</acronym>-related features of &os; are not
|
||||
supported. The New Extend Standard Architecture
|
||||
(<acronym>NESA</acronym>) bus used in the PC-H98, SV-H98,
|
||||
and FC-H98 series, is not supported. </para>
|
||||
</listitem>
|
||||
<para>High-resolution mode is not supported. NEC
|
||||
PC-98XA/XL/RL/XL^2, and NEC PC-H98 series are supported in
|
||||
normal (PC-9801 compatible) mode only. The
|
||||
<acronym>SMP</acronym>-related features of &os; are not
|
||||
supported. The New Extend Standard Architecture
|
||||
(<acronym>NESA</acronym>) bus used in the PC-H98, SV-H98,
|
||||
and FC-H98 series, is not supported.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>&arch.powerpc;</term>
|
||||
<listitem>
|
||||
<para>All New World <acronym>ROM</acronym> &apple; &macintosh; systems with built-in
|
||||
<acronym>USB</acronym> are supported.
|
||||
<acronym>SMP</acronym> is supported on machines with
|
||||
multiple <acronym>CPU</acronym>s.</para>
|
||||
<para>All New World <acronym>ROM</acronym> &apple;
|
||||
&macintosh; systems with built-in <acronym>USB</acronym>
|
||||
are supported. <acronym>SMP</acronym> is supported on
|
||||
machines with multiple <acronym>CPU</acronym>s.</para>
|
||||
|
||||
<para>A 32-bit kernel can only use the first 2 GB of
|
||||
<acronym>RAM</acronym>.</para>
|
||||
</listitem>
|
||||
<para>A 32-bit kernel can only use the first 2 GB of
|
||||
<acronym>RAM</acronym>.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<varlistentry>
|
||||
<term>&arch.sparc64;</term>
|
||||
<listitem>
|
||||
<para>Systems supported by &os;/&arch.sparc64; are listed at
|
||||
the FreeBSD/sparc64 Project (<link
|
||||
xlink:href="&url.base;/platforms/sparc.html">http://www.freebsd.org/platforms/sparc.html</link>).</para>
|
||||
<para>Systems supported by &os;/&arch.sparc64; are listed at
|
||||
the FreeBSD/sparc64 Project (<link
|
||||
xlink:href="&url.base;/platforms/sparc.html">http://www.freebsd.org/platforms/sparc.html</link>).</para>
|
||||
|
||||
<para><acronym>SMP</acronym> is supported on all systems with
|
||||
more than 1 processor. A dedicated disk is required as
|
||||
it is not possible to share a disk with another operating
|
||||
system at this time.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
<para><acronym>SMP</acronym> is supported on all systems
|
||||
with more than 1 processor. A dedicated disk is required
|
||||
as it is not possible to share a disk with another
|
||||
operating system at this time.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</sect1>
|
||||
|
||||
<sect1 xml:id="bsdinstall-pre">
|
||||
|
@ -283,38 +283,40 @@
|
|||
checklist:</para>
|
||||
|
||||
<procedure>
|
||||
<step>
|
||||
<title>Back Up Important Data</title>
|
||||
<step>
|
||||
<title>Back Up Important Data</title>
|
||||
|
||||
<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>
|
||||
<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>
|
||||
|
||||
<step>
|
||||
<title>Decide Where to Install &os;</title>
|
||||
<step>
|
||||
<title>Decide Where to Install &os;</title>
|
||||
|
||||
<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>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 these primary partitions
|
||||
<firstterm>slices</firstterm>. One of these
|
||||
primary partitions can be made into an <firstterm>extended
|
||||
partition</firstterm> containing multiple <firstterm>logical
|
||||
partitions</firstterm>. The <firstterm>GUID Partition Table</firstterm>
|
||||
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 these primary partition
|
||||
<firstterm>slices</firstterm>. One of these primary
|
||||
partitions can be made into an <firstterm>extended
|
||||
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. Common <acronym>GPT</acronym>
|
||||
implementations allow up to 128 partitions per disk,
|
||||
|
@ -344,84 +346,86 @@
|
|||
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 <acronym>CD</acronym> distributions.</para>
|
||||
many other Linux live <acronym>CD</acronym>
|
||||
distributions.</para>
|
||||
|
||||
<warning>
|
||||
<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>
|
||||
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>Disk partitions containing different operating systems
|
||||
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>
|
||||
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>
|
||||
|
||||
<step>
|
||||
<title>Collect Network Information</title>
|
||||
<step>
|
||||
<title>Collect Network Information</title>
|
||||
|
||||
<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>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>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, the follwoing network information for the system must be obtained
|
||||
from the local network administrator or Internet service
|
||||
provider:</para>
|
||||
<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, the follwoing
|
||||
network information for the system must be obtained from the
|
||||
local network administrator or Internet service
|
||||
provider:</para>
|
||||
|
||||
<orderedlist xml:id="bsdinstall-collect-network-information">
|
||||
<title>Required Network Information</title>
|
||||
<orderedlist xml:id="bsdinstall-collect-network-information">
|
||||
<title>Required Network Information</title>
|
||||
|
||||
<listitem>
|
||||
<para><acronym>IP</acronym>
|
||||
address</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para><acronym>IP</acronym> address</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Subnet mask</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Subnet mask</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para><acronym>IP</acronym> address of default
|
||||
gateway</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para><acronym>IP</acronym> address of default
|
||||
gateway</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Domain name of the network</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Domain name of the network</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para><acronym>IP</acronym> addresses of the network's
|
||||
<acronym>DNS</acronym> servers</para>
|
||||
</listitem>
|
||||
</orderedlist>
|
||||
</step>
|
||||
<listitem>
|
||||
<para><acronym>IP</acronym> addresses of the network's
|
||||
<acronym>DNS</acronym> servers</para>
|
||||
</listitem>
|
||||
</orderedlist>
|
||||
</step>
|
||||
|
||||
<step>
|
||||
<title>Check for &os; Errata</title>
|
||||
<step>
|
||||
<title>Check for &os; Errata</title>
|
||||
|
||||
<para>Although the &os; Project strives to ensure that each
|
||||
release of &os; is as stable as possible, bugs occasionally
|
||||
creep into the process. On very rare occasions those bugs
|
||||
affect the installation process. As these problems are
|
||||
discovered and fixed, they are noted in the &os; Errata (<link
|
||||
xlink:href="&url.base;/releases/&rel.current;R/errata.html">http://www.freebsd.org/releases/&rel.current;R/errata.html</link>)
|
||||
on the &os; web site. Check the errata before installing to
|
||||
make sure that there are no problems that might affect the
|
||||
installation.</para>
|
||||
<para>Although the &os; Project strives to ensure that
|
||||
each release of &os; is as stable as possible, bugs
|
||||
occasionally creep into the process. On very rare occasions
|
||||
those bugs affect the installation process. As these
|
||||
problems are discovered and fixed, they are noted in the
|
||||
&os; Errata (<link
|
||||
xlink:href="&url.base;/releases/&rel.current;R/errata.html">http://www.freebsd.org/releases/&rel.current;R/errata.html</link>)
|
||||
on the &os; web site. Check the errata before installing to
|
||||
make sure that there are no problems that might affect the
|
||||
installation.</para>
|
||||
|
||||
<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>
|
||||
</step>
|
||||
<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>
|
||||
</step>
|
||||
</procedure>
|
||||
|
||||
<sect2 xml:id="bsdinstall-installation-media">
|
||||
|
@ -620,131 +624,125 @@ commit your changes?</programlisting>
|
|||
configure the system to boot from the inserted media depends
|
||||
upon the architecture.</para>
|
||||
|
||||
<sect2 xml:id="bsdinstall-starting-i386">
|
||||
<title>Booting on &i386; and &arch.amd64;</title>
|
||||
<sect2 xml:id="bsdinstall-starting-i386">
|
||||
<title>Booting on &i386; and &arch.amd64;</title>
|
||||
|
||||
<para>These architectures provide a
|
||||
<acronym>BIOS</acronym> menu for selecting the
|
||||
boot device. Depending upon the installation media
|
||||
being used, select the
|
||||
<acronym>CD</acronym>/<acronym>DVD</acronym> or
|
||||
<acronym>USB</acronym> device as the first boot device.
|
||||
Most systems also
|
||||
provide a key for selecting the boot device during
|
||||
startup without having to enter the <acronym>BIOS</acronym>.
|
||||
Typically, the key is either <keycap>F10</keycap>,
|
||||
<keycap>F11</keycap>, <keycap>F12</keycap>, or
|
||||
<keycap>Escape</keycap>.</para>
|
||||
<para>These architectures provide a <acronym>BIOS</acronym>
|
||||
menu for selecting the boot device. Depending upon the
|
||||
installation media being used, select the
|
||||
<acronym>CD</acronym>/<acronym>DVD</acronym> or
|
||||
<acronym>USB</acronym> device as the first boot device. Most
|
||||
systems also provide a key for selecting the boot device
|
||||
during startup without having to enter the
|
||||
<acronym>BIOS</acronym>. Typically, the key is either
|
||||
<keycap>F10</keycap>, <keycap>F11</keycap>,
|
||||
<keycap>F12</keycap>, or <keycap>Escape</keycap>.</para>
|
||||
|
||||
<para>If the computer loads the
|
||||
existing operating system instead of the &os; installer, then either:</para>
|
||||
<para>If the computer loads the existing operating system
|
||||
instead of the &os; installer, then either:</para>
|
||||
|
||||
<orderedlist>
|
||||
<listitem>
|
||||
<para>The installation media was not inserted early enough in the
|
||||
boot process. Leave the media inserted and try restarting the
|
||||
computer.</para>
|
||||
</listitem>
|
||||
<orderedlist>
|
||||
<listitem>
|
||||
<para>The installation media was not inserted early enough
|
||||
in the boot process. Leave the media inserted and try
|
||||
restarting the computer.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>The <acronym>BIOS</acronym> changes were incorrect or not saved.
|
||||
Double-check that the right boot device
|
||||
is selected as the first boot device.</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>The <acronym>BIOS</acronym> changes were incorrect or
|
||||
not saved. Double-check that the right boot device is
|
||||
selected as the first boot device.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>This system is too old to
|
||||
support booting from the chosen media. In this case, the
|
||||
<application>Plop Boot Manager</application> (<link
|
||||
xlink:href="http://www.plop.at/en/bootmanager.html">http://www.plop.at/en/bootmanager.html</link>)
|
||||
can be used to boot the system from the selected
|
||||
media.</para>
|
||||
</listitem>
|
||||
</orderedlist>
|
||||
</sect2>
|
||||
<listitem>
|
||||
<para>This system is too old to support booting from the
|
||||
chosen media. In this case, the <application>Plop Boot
|
||||
Manager</application> (<link
|
||||
xlink:href="http://www.plop.at/en/bootmanager.html">http://www.plop.at/en/bootmanager.html</link>)
|
||||
can be used to boot the system from the selected
|
||||
media.</para>
|
||||
</listitem>
|
||||
</orderedlist>
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Booting on &powerpc;</title>
|
||||
<sect2>
|
||||
<title>Booting on &powerpc;</title>
|
||||
|
||||
<para>On most machines, holding <keycap>C</keycap> on the
|
||||
keyboard during boot will boot from the
|
||||
<acronym>CD</acronym>. Otherwise, hold
|
||||
<keycombo action="simul">
|
||||
<keycap>Command</keycap>
|
||||
<keycap>Option</keycap>
|
||||
<keycap>O</keycap>
|
||||
<keycap>F</keycap>
|
||||
</keycombo>,
|
||||
or
|
||||
<keycombo action="simul">
|
||||
<keycap>Windows</keycap>
|
||||
<keycap>Alt</keycap>
|
||||
<keycap>O</keycap>
|
||||
<keycap>F</keycap>
|
||||
</keycombo>
|
||||
on non-&apple; keyboards. At the <prompt>0 ></prompt>
|
||||
prompt, enter</para>
|
||||
<para>On most machines, holding <keycap>C</keycap> on the
|
||||
keyboard during boot will boot from the <acronym>CD</acronym>.
|
||||
Otherwise, hold <keycombo action="simul">
|
||||
<keycap>Command</keycap>
|
||||
<keycap>Option</keycap>
|
||||
<keycap>O</keycap>
|
||||
<keycap>F</keycap>
|
||||
</keycombo>, or
|
||||
<keycombo action="simul">
|
||||
<keycap>Windows</keycap>
|
||||
<keycap>Alt</keycap>
|
||||
<keycap>O</keycap>
|
||||
<keycap>F</keycap>
|
||||
</keycombo> on non-&apple; keyboards. At the
|
||||
<prompt>0 ></prompt> prompt, enter</para>
|
||||
|
||||
<screen><userinput>boot cd:,\ppc\loader cd:0</userinput></screen>
|
||||
</sect2>
|
||||
<screen><userinput>boot cd:,\ppc\loader cd:0</userinput></screen>
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Booting on &sparc64;</title>
|
||||
<sect2>
|
||||
<title>Booting on &sparc64;</title>
|
||||
|
||||
<para>Most &sparc64; systems are set up to boot automatically
|
||||
from disk. To install &os;
|
||||
from a <acronym>CD</acronym> requires a break into the
|
||||
<acronym>PROM</acronym>.</para>
|
||||
<para>Most &sparc64; systems are set up to boot automatically
|
||||
from disk. To install &os; from a <acronym>CD</acronym>
|
||||
requires a break into the <acronym>PROM</acronym>.</para>
|
||||
|
||||
<para>To do this, reboot the system and wait until the boot
|
||||
message appears. The message depends on the model, but should look
|
||||
something like this:</para>
|
||||
<para>To do this, reboot the system and wait until the boot
|
||||
message appears. The message depends on the model, but should
|
||||
look something like this:</para>
|
||||
|
||||
<screen>Sun Blade 100 (UltraSPARC-IIe), Keyboard Present
|
||||
<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 the system proceeds to boot from disk at this point,
|
||||
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. When using <application>tip</application>
|
||||
or <application>cu</application>, <command>~#</command> will
|
||||
issue a BREAK. The <acronym>PROM</acronym> prompt will be
|
||||
<prompt>ok</prompt> on systems with one
|
||||
<acronym>CPU</acronym> and <prompt>ok {0} </prompt> on <acronym>SMP</acronym>
|
||||
systems, where the digit indicates the number of the active
|
||||
<acronym>CPU</acronym>.</para>
|
||||
<para>If the system proceeds to boot from disk at this point,
|
||||
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. When using <application>tip</application> or
|
||||
<application>cu</application>, <command>~#</command> will
|
||||
issue a BREAK. The <acronym>PROM</acronym> prompt will be
|
||||
<prompt>ok</prompt> on systems with one
|
||||
<acronym>CPU</acronym> and <prompt>ok {0} </prompt> on
|
||||
<acronym>SMP</acronym> systems, where the digit indicates the
|
||||
number of the active <acronym>CPU</acronym>.</para>
|
||||
|
||||
<para>At this point, place the <acronym>CD</acronym> into the
|
||||
drive and type <command>boot cdrom</command> from the
|
||||
<acronym>PROM</acronym> prompt.</para>
|
||||
<para>At this point, place the <acronym>CD</acronym> into the
|
||||
drive and type <command>boot cdrom</command> from the
|
||||
<acronym>PROM</acronym> prompt.</para>
|
||||
</sect2>
|
||||
|
||||
<sect2 xml:id="bsdinstall-view-probe">
|
||||
<title>&os; Boot Menu</title>
|
||||
|
||||
<para>Once the system boots from the installation media,
|
||||
a menu similar to the following will be displayed:</para>
|
||||
<para>Once the system boots from the installation media, a menu
|
||||
similar to the following will be displayed:</para>
|
||||
|
||||
<figure xml:id="bsdinstall-newboot-loader-menu">
|
||||
<title>&os; Boot Loader Menu</title>
|
||||
<figure xml:id="bsdinstall-newboot-loader-menu">
|
||||
<title>&os; Boot Loader Menu</title>
|
||||
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata
|
||||
fileref="bsdinstall/bsdinstall-newboot-loader-menu"/>
|
||||
</imageobject>
|
||||
</mediaobject>
|
||||
</figure>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata
|
||||
fileref="bsdinstall/bsdinstall-newboot-loader-menu"/>
|
||||
</imageobject>
|
||||
</mediaobject>
|
||||
</figure>
|
||||
|
||||
<para>By default, the menu will wait ten seconds for user
|
||||
input before booting into the &os; installer or, if &os; is
|
||||
already installed, before booting into &os;. To pause the
|
||||
boot timer in order to review the selections, press
|
||||
<para>By default, the menu will wait ten seconds for user input
|
||||
before booting into the &os; installer or, if &os; is already
|
||||
installed, before booting into &os;. To pause the boot timer
|
||||
in order to review the selections, press
|
||||
<keycap>Space</keycap>. To select an option, press its
|
||||
highlighted number, character, or key. The following options
|
||||
are available.</para>
|
||||
|
@ -784,18 +782,18 @@ Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4.</screen>
|
|||
menu shown in, and described under, <xref
|
||||
linkend="bsdinstall-boot-options-menu"/>.</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
</itemizedlist>
|
||||
|
||||
<figure xml:id="bsdinstall-boot-options-menu">
|
||||
<title>&os; Boot Options Menu</title>
|
||||
<figure xml:id="bsdinstall-boot-options-menu">
|
||||
<title>&os; Boot Options Menu</title>
|
||||
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata
|
||||
fileref="bsdinstall/bsdinstall-boot-options-menu"/>
|
||||
</imageobject>
|
||||
</mediaobject>
|
||||
</figure>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata
|
||||
fileref="bsdinstall/bsdinstall-boot-options-menu"/>
|
||||
</imageobject>
|
||||
</mediaobject>
|
||||
</figure>
|
||||
|
||||
<para>The boot options menu is divided into two sections. The
|
||||
first section can be used to either return to the main boot
|
||||
|
@ -834,19 +832,19 @@ Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4.</screen>
|
|||
<listitem>
|
||||
<para><literal>Verbose</literal>: Toggle this option to
|
||||
<literal>On</literal> to see more detailed messages during
|
||||
the boot process. This can be useful when troubleshooting
|
||||
the boot process. This can be useful when troubleshooting
|
||||
a piece of hardware.</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
</itemizedlist>
|
||||
|
||||
<para>After making the needed selections, press
|
||||
<keycap>1</keycap> or <keycap>Backspace</keycap> to return to
|
||||
the main boot menu, then press <keycap>Enter</keycap> to
|
||||
continue booting into &os;. A series of boot messages will
|
||||
appear as &os; carries out its hardware device probes and
|
||||
loads the installation program. Once the boot is complete,
|
||||
the welcome menu shown in
|
||||
<xref linkend="bsdinstall-choose-mode"/> will be displayed.</para>
|
||||
the main boot menu, then press <keycap>Enter</keycap> to
|
||||
continue booting into &os;. A series of boot messages will
|
||||
appear as &os; carries out its hardware device probes and
|
||||
loads the installation program. Once the boot is complete,
|
||||
the welcome menu shown in <xref
|
||||
linkend="bsdinstall-choose-mode"/> will be displayed.</para>
|
||||
|
||||
<figure xml:id="bsdinstall-choose-mode">
|
||||
<title>Welcome Menu</title>
|
||||
|
@ -859,10 +857,10 @@ Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4.</screen>
|
|||
</figure>
|
||||
|
||||
<para>Press <keycap>Enter</keycap> to select the default of
|
||||
<guibutton>[ Install ]</guibutton> to
|
||||
enter the installer. The rest of this chapter describes how
|
||||
to use this installer. Otherwise, use the right or left arrows
|
||||
or the colorized letter to select the desired menu item. The
|
||||
<guibutton>[ Install ]</guibutton> to enter the
|
||||
installer. The rest of this chapter describes how to use this
|
||||
installer. Otherwise, use the right or left arrows or the
|
||||
colorized letter to select the desired menu item. The
|
||||
<guibutton>[ Shell ]</guibutton> can be used to
|
||||
access a &os; shell in order to use command line utilities to
|
||||
prepare the disks before installation. The
|
||||
|
@ -871,13 +869,14 @@ Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4.</screen>
|
|||
is described in <xref linkend="using-live-cd"/>.</para>
|
||||
|
||||
<tip>
|
||||
<para>To review the boot messages, including the hardware device
|
||||
probe, press the upper- or lower-case <keycap>S</keycap> and
|
||||
then <keycap>Enter</keycap> to access a shell. At the shell
|
||||
prompt, type <command>more /var/run/dmesg.boot</command> and
|
||||
use the space bar to scroll through the messages. When
|
||||
finished, type <command>exit</command> to return to the
|
||||
welcome menu.</para>
|
||||
<para>To review the boot messages, including the hardware
|
||||
device probe, press the upper- or lower-case
|
||||
<keycap>S</keycap> and then <keycap>Enter</keycap> to access
|
||||
a shell. At the shell prompt, type <command>more
|
||||
/var/run/dmesg.boot</command> and use the space bar to
|
||||
scroll through the messages. When finished, type
|
||||
<command>exit</command> to return to the welcome
|
||||
menu.</para>
|
||||
</tip>
|
||||
</sect2>
|
||||
</sect1>
|
||||
|
@ -889,9 +888,9 @@ Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4.</screen>
|
|||
<application>bsdinstall</application> menus and the type of
|
||||
information that will be asked before the system is installed.
|
||||
Use the up and down arrows to highlight a menu option, then the
|
||||
<keycap>Space</keycap> key to select or deselect a
|
||||
menu item. Then, use <keycap>Enter</keycap> to save the selection
|
||||
and move onto the next screen.</para>
|
||||
<keycap>Space</keycap> key to select or deselect a menu item.
|
||||
Then, use <keycap>Enter</keycap> to save the selection and move
|
||||
onto the next screen.</para>
|
||||
|
||||
<sect2 xml:id="bsdinstall-keymap">
|
||||
<title>Selecting the Keymap Menu</title>
|
||||
|
@ -979,8 +978,8 @@ Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4.</screen>
|
|||
</mediaobject>
|
||||
</figure>
|
||||
|
||||
<para>Type in a hostname that is unique for the network. It should be a fully-qualified hostname,
|
||||
such as <systemitem
|
||||
<para>Type in a hostname that is unique for the network. It
|
||||
should be a fully-qualified hostname, such as <systemitem
|
||||
class="fqdomainname">machine3.example.com</systemitem>.</para>
|
||||
</sect2>
|
||||
|
||||
|
@ -1004,15 +1003,15 @@ Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4.</screen>
|
|||
<para>Deciding which components to install will depend largely
|
||||
on the intended use of the system and the amount of disk space
|
||||
available. The &os; kernel and userland, collectively known
|
||||
as the <quote>base system</quote>, are always
|
||||
installed. Depending on the architecture, some of these
|
||||
components may not appear:</para>
|
||||
as the <quote>base system</quote>, are always installed.
|
||||
Depending on the architecture, some of these components may
|
||||
not appear:</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para><literal>doc</literal> - Additional documentation,
|
||||
mostly of historical interest, to install into
|
||||
<filename>/usr/share/doc</filename>. The documentation
|
||||
<filename>/usr/share/doc</filename>. The documentation
|
||||
provided by the FreeBSD Documentation Project may be
|
||||
installed later using the instructions in <xref
|
||||
linkend="updating-upgrading-documentation"/>.</para>
|
||||
|
|
Loading…
Reference in a new issue