Editorial review of Prepare the Installation Media section.
Describe the available installation files. Sponsored by: iXsystems
This commit is contained in:
Dru Lavigne
parent
7cfcff7e6a
commit
70e133e25c
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=44900
1 changed files with 100 additions and 96 deletions
|
|
@ -431,116 +431,126 @@
|
|||
<sect2 xml:id="bsdinstall-installation-media">
|
||||
<title>Prepare the Installation Media</title>
|
||||
|
||||
<para>A &os; installation is started by booting the computer
|
||||
with a &os; installation <acronym>CD</acronym>,
|
||||
<acronym>DVD</acronym>, or <acronym>USB</acronym> memory
|
||||
stick. The installer is not a program that can be run from
|
||||
within another operating system.</para>
|
||||
<para>The &os; installer is not an application that can be run from
|
||||
within another operating system. Instead, download a &os;
|
||||
installation file, burn it to the media associated with its
|
||||
file type and size (<acronym>CD</acronym>,
|
||||
<acronym>DVD</acronym>, or <acronym>USB</acronym>), and boot
|
||||
the system to install from the inserted media.</para>
|
||||
|
||||
<para>In addition to the standard installation media which
|
||||
contains copies of all the &os; installation files, there is a
|
||||
<emphasis>bootonly</emphasis> variant. Bootonly install media
|
||||
does not have copies of the installation files, but downloads
|
||||
them from the network during an install. The bootonly install
|
||||
<acronym>CD</acronym> is consequently much smaller, and
|
||||
reduces bandwidth usage during the install by only downloading
|
||||
required files.</para>
|
||||
|
||||
<para>Copies of &os; installation media are available at <link
|
||||
<para>&os; installation files are available at <link
|
||||
xlink:href="&url.base;/where.html#download">www.freebsd.org/where.html#download</link>.
|
||||
Also download <filename>CHECKSUM.SHA256</filename> from the
|
||||
same directory as the image file, and use it to check the
|
||||
Each installation file's name includes the release version of
|
||||
&os;, the architecture, and the type of file. For example, to
|
||||
install &os; 10.0 on an &arch.amd64; system from a
|
||||
<acronym>DVD</acronym>, download
|
||||
<filename>FreeBSD-10.0-RELEASE-amd64-dvd1.iso</filename>,
|
||||
burn this file to a <acronym>DVD</acronym>, and boot the
|
||||
system with the <acronym>DVD</acronym> inserted.</para>
|
||||
|
||||
<para>Several file types are available, though not all file
|
||||
types are available for all architectures. The possible file
|
||||
types are:</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para><literal>-bootonly.iso</literal>: This is the smallest
|
||||
installation file as it only contains the installer. A
|
||||
working Internet connection is required during
|
||||
installation as the installer will download the files it
|
||||
needs to complete the &os; installation. This file should
|
||||
be burned to a <acronym>CD</acronym> using a
|
||||
<acronym>CD</acronym> burning application.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para><literal>-disc1.iso</literal>: This file contains all
|
||||
of the files needed to install &os;, its source, and the
|
||||
Ports Collection. It should be burned to a
|
||||
<acronym>CD</acronym> using a <acronym>CD</acronym>
|
||||
burning application.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para><literal>-dvd1.iso</literal>: This file contains all
|
||||
of the files needed to install &os;, its source, and the
|
||||
Ports Collection. It also contains a set of popular
|
||||
binary packages for installing a window manager and some
|
||||
applications so that a complete system can be installed
|
||||
from media without requiring a connection to the Internet.
|
||||
This file should be burned to a <acronym>DVD</acronym>
|
||||
using a <acronym>DVD</acronym> burning application.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para><literal>-memstick.img</literal>: This file contains
|
||||
all of the files needed to install &os;, its source, and
|
||||
the Ports Collection. It should be burned to a
|
||||
<acronym>USB</acronym> stick using the instructions
|
||||
below.</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<para>Also download <filename>CHECKSUM.SHA256</filename> from the
|
||||
same directory as the image file and use it to check the
|
||||
image file's integrity by calculating a
|
||||
<emphasis>checksum</emphasis>. &os; provides &man.sha256.1;
|
||||
<firstterm>checksum</firstterm>. &os; provides &man.sha256.1;
|
||||
for this, while other operating systems have similar programs.
|
||||
Compare the calculated checksum with the one shown in
|
||||
<filename>CHECKSUM.SHA256</filename>. The checksums must
|
||||
match exactly. If the checksums do not match, the file is
|
||||
corrupt and should be discarded.</para>
|
||||
corrupt and should be downloaded again.</para>
|
||||
|
||||
<tip>
|
||||
<para>If a copy of &os; already exists on
|
||||
<acronym>CD</acronym>, <acronym>DVD</acronym>, or
|
||||
<acronym>USB</acronym> memory stick, this section can be
|
||||
skipped.</para>
|
||||
</tip>
|
||||
<sect3>
|
||||
<title>Burning an Image File to <acronym>USB</acronym></title>
|
||||
|
||||
<para>&os; <acronym>CD</acronym> and <acronym>DVD</acronym>
|
||||
images are bootable <acronym>ISO</acronym> files. Only one
|
||||
<acronym>CD</acronym> or <acronym>DVD</acronym> is needed for
|
||||
an install. Burn the <acronym>ISO</acronym> image to a
|
||||
bootable <acronym>CD</acronym> or <acronym>DVD</acronym> using
|
||||
the burning applications available with the current operating
|
||||
system. On &os;, recording is provided by
|
||||
<command>cdrecord</command> from
|
||||
<package>sysutils/cdrtools</package>, installed from the Ports
|
||||
Collection.</para>
|
||||
|
||||
<para>To create a bootable memory stick, follow these
|
||||
steps:</para>
|
||||
|
||||
<procedure xml:id="bsdinstall-installation-media-memory-stick">
|
||||
<step>
|
||||
<title>Acquire the Memory Stick Image</title>
|
||||
|
||||
<para>Memory stick images for &os; 9.0-RELEASE and
|
||||
later can be downloaded from the
|
||||
<filename>ISO-IMAGES/</filename>
|
||||
directory at
|
||||
<literal>ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/<replaceable>arch</replaceable>/<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 to install, respectively. For
|
||||
example, the memory stick images for
|
||||
&os;/&arch.i386; 9.0-RELEASE are available from <uri
|
||||
xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/&arch.i386;/&arch.i386;/ISO-IMAGES/9.0/&os;-9.0-RELEASE-&arch.i386;-memstick.img">ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/&arch.i386;/&arch.i386;/ISO-IMAGES/9.0/&os;-9.0-RELEASE-&arch.i386;-memstick.img</uri>.</para>
|
||||
|
||||
<tip>
|
||||
<para>A different directory path is used for
|
||||
&os; 8.<replaceable>X</replaceable> and earlier
|
||||
versions. Details of download and installation of
|
||||
&os; 8.<replaceable>X</replaceable> and earlier is
|
||||
covered in <xref linkend="install"/>.</para>
|
||||
</tip>
|
||||
|
||||
<para>The memory stick image has a <filename>.img</filename>
|
||||
extension. The <filename>ISO-IMAGES/</filename> directory
|
||||
contains a number of different images, and the one needed
|
||||
depends on the version of &os; being installed, and in
|
||||
some cases, the target hardware.</para>
|
||||
<para>Since the <filename>*.img</filename> file is an
|
||||
<emphasis>image</emphasis> of the complete contents of a
|
||||
memory stick, it <emphasis>cannot</emphasis> just be copied
|
||||
to the target device. Several applications are available
|
||||
for burning the <filename>*.img</filename> to a
|
||||
<acronym>USB</acronym> stick. This section describes two
|
||||
of these utilities.</para>
|
||||
|
||||
<important>
|
||||
<para>Before proceeding, <emphasis>back up</emphasis> the
|
||||
data on the USB stick, as this procedure will
|
||||
<emphasis>erase</emphasis> it.</para>
|
||||
<para>Before proceeding, back up any important
|
||||
data on the <acronym>USB</acronym> stick as this procedure will
|
||||
erase the existing data on the stick.</para>
|
||||
</important>
|
||||
</step>
|
||||
|
||||
<step>
|
||||
<title>Write the Image File to the Memory Stick</title>
|
||||
|
||||
<procedure>
|
||||
<title>Using &os; to Write the Image</title>
|
||||
<title>Using <command>dd</command> to Write the
|
||||
Image</title>
|
||||
|
||||
<warning>
|
||||
<para>The example below shows
|
||||
<para>This example uses
|
||||
<filename>/dev/da0</filename> as the target device
|
||||
where the image will be written. Be very careful that
|
||||
the correct device is used as the output target, as
|
||||
this command will destroy existing data.</para>
|
||||
where the image will be written. Be <emphasis>very
|
||||
careful</emphasis> that the correct device is used as
|
||||
this command will destroy the existing data on the
|
||||
specified target device.</para>
|
||||
</warning>
|
||||
|
||||
<step>
|
||||
<title>Writing the Image with &man.dd.1;</title>
|
||||
<para>The <command>dd</command> command-line utility is
|
||||
included on BSD, Linux, and &macos; systems. To burn
|
||||
the image using <command>dd</command>, insert the
|
||||
<acronym>USB</acronym> stick and determine its device
|
||||
name. Then, specify the name of the downloaded
|
||||
installation file and the device name for the
|
||||
<acronym>USB</acronym> stick. This example burns the
|
||||
&arch.amd64; installation image to the first
|
||||
<acronym>USB</acronym> device on an existing &os;
|
||||
system.</para>
|
||||
|
||||
<para>The <filename>.img</filename> file is
|
||||
<emphasis>not</emphasis> a regular file. It is an
|
||||
<emphasis>image</emphasis> of the complete contents of
|
||||
the memory stick. It <emphasis>cannot</emphasis> be
|
||||
copied like a regular file, but must be written
|
||||
directly to the target device with &man.dd.1;:</para>
|
||||
<screen>&prompt.root; <userinput>dd if=<replaceable>FreeBSD-10.0-RELEASE-amd64-memstick.img</replaceable> of=/dev/<replaceable>da0</replaceable> bs=64k</userinput></screen>
|
||||
|
||||
<screen>&prompt.root; <userinput>dd if=&os;-9.0-RELEASE-&arch.i386;-memstick.img of=/dev/<replaceable>da0</replaceable> bs=64k</userinput></screen>
|
||||
<para>Should this command fail, verify that the
|
||||
<acronym>USB</acronym> stick is not mounted and that
|
||||
the device name is for the disk, not a partition.
|
||||
Depending upon the operating system, this command may
|
||||
need to be issued using
|
||||
<command>sudo</command>.</para>
|
||||
</step>
|
||||
</procedure>
|
||||
|
||||
|
|
@ -549,7 +559,7 @@
|
|||
|
||||
<warning>
|
||||
<para>Be sure to give the correct drive letter as the
|
||||
output target, as existing data will be overwritten
|
||||
existing data on the specified drive will be overwritten
|
||||
and destroyed.</para>
|
||||
</warning>
|
||||
|
||||
|
|
@ -583,15 +593,9 @@
|
|||
write the image file to the memory stick.</para>
|
||||
</step>
|
||||
</procedure>
|
||||
</step>
|
||||
</procedure>
|
||||
|
||||
<note>
|
||||
<para>Installation from floppy disks is no longer
|
||||
supported.</para>
|
||||
</note>
|
||||
|
||||
<para>You are now ready to start installing &os;.</para>
|
||||
</sect3>
|
||||
</sect2>
|
||||
</sect1>
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue