os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Replace "you"usage in 9.x Install chapter.

Browse source 
Sponsored by:	iXsystems
This commit is contained in:
Dru Lavigne 2014-04-24 20:50:14 +00:00
parent cf57d4979f
commit a8293d13cb
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=44651
1 changed files with 69 additions and 72 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

141
en_US.ISO8859-1/books/handbook/bsdinstall/chapter.xml
View file

@ -101,7 +101,7 @@
<listitem>
<para>The questions <application>bsdinstall</application> will
ask you, what they mean, and how to answer them.</para>
ask, what they mean, and how to answer them.</para>
</listitem>
</itemizedlist>
@ -110,7 +110,7 @@
<itemizedlist>
<listitem>
<para>Read the supported hardware list that shipped with the
version of &os; you are installing, and verify that your
version of &os; to be installed and verify that the system's
hardware is supported.</para>
</listitem>
</itemizedlist>
@ -136,9 +136,9 @@
&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 supported CDROM drive, and in some cases a
network adapter. This will be covered by
sections. Depending upon the method chosen to install &os;,
a supported CDROM drive and, in some cases, a
network adapter may be needed. This will be covered by
<xref linkend="bsdinstall-installation-media"/>.</para>
<sect3>
@ -174,12 +174,10 @@
&intel;&nbsp;&xeon; E3, E5 and E7 processors, and the
&intel;&nbsp;&core; i3, i5 and i7 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 for which we have not yet
found a workaround.</para>
<para>If the system is based on an nVidia nForce3
Pro-150, the IO APIC <emphasis>must</emphasis> be disabled
in the BIOS setup. If this BIOS option does not exist,
disable ACPI instead.</para>
</sect3>
<sect3>
@ -225,7 +223,7 @@
<title>Pre-Installation Tasks</title>
<sect2>
<title>Back Up Your Data</title>
<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
@ -348,7 +346,7 @@
<orderedlist>
<listitem>
<para>Back up your &windows; data. Then reinstall
<para>Back up any &windows; data. Then reinstall
&windows;, creating a 20&nbsp;GB partition during the
install.</para>
</listitem>
@ -462,14 +460,14 @@
corrupt and should be discarded.</para>
<tip>
<para>If you already have a copy of &os; on CDROM, DVD, or USB
<para>If a copy of &os; already exists on CDROM, DVD, or USB
memory stick, this section can be skipped.</para>
</tip>
<para>&os; CD and DVD images are bootable ISO files. Only one
CD or DVD is needed for an install. Burn the ISO image to a
bootable CD or DVD using the CD recording applications
available with your current operating system. On &os;,
available with the current operating system. On &os;,
recording is provided by &man.cdrecord.1; from
<filename>sysutils/cdrtools</filename>, installed
from the Ports Collection.</para>
@ -488,7 +486,7 @@
<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 which you want to
architecture and the version number to
install, respectively. For example, the memory stick
images for &os;/&arch.i386;&nbsp;9.0-RELEASE are
available from <uri
@ -525,8 +523,8 @@
<para>The example below shows
<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, or
you may destroy existing data.</para>
the correct device is used as the output target, as this command will
destroy existing data.</para>
</warning>
<step>
@ -549,8 +547,8 @@
<warning>
<para>Be sure to give the correct drive letter as the
output target, or you may overwrite and destroy
existing data.</para>
output target, as existing data will be overwritten
and destroyed.</para>
</warning>
<step>
@ -600,7 +598,7 @@
<important>
<para>By default, the installation will not make any changes to
your disk(s) until you see the following message:</para>
the disk(s) before the following message:</para>
<literallayout class="monospaced">Your changes will now be written to disk. If you
have chosen to overwrite existing data, it will
@ -609,8 +607,8 @@ commit your changes?</literallayout>
<para>The install can be exited at any time prior to this
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
there is a concern that something is
incorrectly configured, just turn the computer off before this
point, and no damage will be done.</para>
</important>
@ -622,19 +620,19 @@ commit your changes?</literallayout>
<procedure>
<step>
<para>If you prepared a <quote>bootable</quote> USB stick,
<para>When using a prepared <quote>bootable</quote> USB stick,
as described in
<xref linkend="bsdinstall-installation-media"/>, then
plug in your USB stick before turning on the
<xref linkend="bsdinstall-installation-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>When booting from CDROM,
turn on the computer and insert the CDROM at the first
opportunity.</para>
</step>
<step>
<para>Configure your machine to boot from either the CDROM
<para>Configure the system to boot from either the CDROM
or from USB, depending on the media being used for the
installation. <acronym>BIOS</acronym> configurations
allow the selection of a specific boot device. Most
@ -645,24 +643,24 @@ commit your changes?</literallayout>
</step>
<step>
<para>If your computer starts up as normal and loads your
<para>If the computer starts up as normal and loads an
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 computer.</para>
the computer.</para>
</listitem>
<listitem>
<para>The <acronym>BIOS</acronym> changes earlier did
not work correctly. You should redo that step until
you get the right option.</para>
not work correctly. Redo that step until
the right option is selected.</para>
</listitem>
<listitem>
<para>Your particular <acronym>BIOS</acronym> does not
<para>This particular <acronym>BIOS</acronym> does not
support booting from the desired media. The <link
xlink:href="http://www.plop.at/en/bootmanager.html">Plop
Boot Manager</link> can be used to boot older
@ -672,8 +670,8 @@ commit your changes?</literallayout>
</step>
<step>
<para>&os; will start to boot. If you are booting from
CDROM you will see a display similar to this (version
<para>&os; will start to boot. When booting from
CDROM, messages similar to this will be displayed (version
information omitted):</para>
<screen>Booting from CD-ROM...
@ -752,8 +750,8 @@ Loading /boot/defaults/loader.conf
<title>Booting for &sparc64;</title>
<para>Most &sparc64; systems are set up to boot automatically
from disk. To install &os;, you need to boot over the
network or from a CDROM, which requires you to break into
from disk. To install &os;, booting over the
network or from a CDROM requires a break into
the
<acronym>PROM</acronym>
(OpenFirmware).</para>
@ -767,8 +765,8 @@ 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 your system proceeds to boot from disk at this point,
you need to press
<para>If the system proceeds to boot from disk at this point,
press
<keycombo
action="simul"><keycap>L1</keycap><keycap>A</keycap></keycombo>
or
@ -795,7 +793,7 @@ Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4.</screen>
</callout>
</calloutlist>
<para>At this point, place the CDROM into your drive, and from
<para>At this point, place the CDROM into the drive, and from
the <acronym>PROM</acronym> prompt, type
<command>boot cdrom</command>.</para>
</sect3>
@ -808,17 +806,17 @@ Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4.</screen>
screen are stored and can be reviewed.</para>
<para>To review the buffer, press <keycap>Scroll Lock</keycap>.
This turns on scrolling in the display. You can then use the
This turns on scrolling in the display. Use the
arrow keys, or <keycap>PageUp</keycap> and
<keycap>PageDown</keycap> to view the results. Press
<keycap>PageDown</keycap>, to view the results. Press
<keycap>Scroll Lock</keycap> again to stop scrolling.</para>
<para>Do this now, to review the text that scrolled off the
screen when the kernel was carrying out the device probes.
You will see text similar to
<xref linkend="bsdinstall-dev-probe"/>, although the precise
text will differ depending on the devices that you have in
your computer.</para>
Text similar to
<xref linkend="bsdinstall-dev-probe"/> will be displayed, although the precise
text will differ depending on the devices in
the computer.</para>
<figure xml:id="bsdinstall-dev-probe">
<title>Typical Device Probe Results</title>
@ -973,15 +971,15 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
</figure>
<para>Check the probe results carefully to make sure that &os;
found all the devices you expected. If a device was not
found, then it will not be listed.
found all the devices. If a device was not
found, it will not be listed. Refer to
<link linkend="kernelconfig-custom-kernel">Kernel
modules</link> allows you to add in support for devices
modules</link> for instructions on how to add in support for devices
which are not in the <filename>GENERIC</filename>
kernel.</para>
<para>After the procedure of device probing, you will see
<xref linkend="bsdinstall-choose-mode"/>. The install media
<para>After the procedure of device probing,
<xref linkend="bsdinstall-choose-mode"/> will be displayed. The install media
can be used in three ways: to install &os;, as a
<link linkend="using-live-cd">live CD</link>, or
to simply access a &os; shell. Use the arrow keys to choose
@ -1170,12 +1168,11 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
to use the ports collection.</para>
<warning>
<para>The installation program does not check to see if
you have adequate space. Select this option only if you
have adequate hard disk space. As of &os;&nbsp;9.0, the
<para>The installation program does not check for
adequate disk space. Select this option only if
sufficient hard disk space is available. The
&os; Ports Collection takes up about &ports.size; of
disk space. You can safely assume a larger value for
more recent versions of &os;.</para>
disk space.</para>
</warning>
</listitem>
@ -1803,7 +1800,7 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
<guibutton>- Rescan Devices</guibutton> to repopulate the list
of available disks. To ensure that the correct disk is
selected, so as not to accidently destroy the wrong disks, the
<guibutton>- Disk Info</guibutton> menu allows you to inspect
<guibutton>- Disk Info</guibutton> menu can be used to inspect
each disk, including its partition table, and various other
information, including the device model number and serial
number, if available.</para>
@ -2310,13 +2307,13 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
<sect2 xml:id="bsdinstall-timezone">
<title>Setting the Time Zone</title>
<para>Setting the time zone for your machine will allow it to
<para>Setting the time zone for the machine will allow it to
automatically correct for any regional time changes and
perform other time zone related functions properly.</para>
<para>The example shown is for a machine located in the Eastern
time zone of the United States. Your selections will vary
according to your geographical location.</para>
time zone of the United States. The selections will vary
according to the geographical location.</para>
<figure xml:id="bsdinstall-local-utc">
<title>Select Local or UTC Clock</title>
@ -2332,7 +2329,7 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
<para>Select <guibutton>[&nbsp;Yes&nbsp;]</guibutton>
or <guibutton>[&nbsp;No&nbsp;]</guibutton> according to how
the machine's clock is configured and press
<keycap>Enter</keycap>. If you do not know whether the system
<keycap>Enter</keycap>. If it is not known whether the system
uses UTC or local time, select
<guibutton>[&nbsp;No&nbsp;]</guibutton> to choose the more
commonly-used local time.</para>
@ -2661,7 +2658,7 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
<listitem>
<para><literal>Handbook</literal> - Download and install the
&os; Handbook (which is what you are reading now).</para>
&os; Handbook.</para>
</listitem>
</itemizedlist>
@ -2957,23 +2954,23 @@ login:</screen>
<para>Due to various limitations of the PC architecture, it is
impossible for probing to be 100% reliable, however, there are
a few things you can do if it fails.</para>
a few things to try if it fails.</para>
<para>Check the <link
xlink:href="http://www.FreeBSD.org/releases/index.html">Hardware
Notes</link> document for your version of &os; to make sure
Notes</link> document for the version of &os; to make sure
your hardware is supported.</para>
<para>If your hardware is supported and you still experience
lock-ups or other problems, you will need to build a
<link linkend="kernelconfig">custom kernel</link>. This will
allow you to add in support for devices which are not present
<para>If the hardware is supported and
lock-ups or other problems occur, build a
<link linkend="kernelconfig">custom kernel</link> which
adds support for devices which are not present
in the <filename>GENERIC</filename> kernel. The kernel on the
boot disks is configured assuming that most hardware devices
are in their factory default configuration in terms of IRQs,
IO addresses, and DMA channels. If your hardware has been
reconfigured, you will most likely need to edit the kernel
configuration and recompile to tell &os; where to find
IO addresses, and DMA channels. If the hardware has been
reconfigured, a custom kernel
configuration file can tell &os; where to find
things.</para>
<para>It is also possible that a probe for a device not present