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

Replace 'FreeBSD' with &os; in the install chapter of the Handbook.

Browse source 
Approved by:	remko (mentor)
This commit is contained in:
Giorgos Keramidas 2013-03-11 21:08:54 +00:00
parent f9e97bc875
commit 8eb0f8af1d
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=41166
1 changed files with 138 additions and 138 deletions

276
en_US.ISO8859-1/books/handbook/install/chapter.xml
View file

@ -176,14 +176,14 @@
<sect2 id="install-inventory">
<title>Inventory Your Computer</title>
<para>Before installing FreeBSD you should attempt to inventory the
components in your computer. The FreeBSD installation routines will
<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. FreeBSD will also
so forth) 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 FreeBSD's determination of
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
@ -195,7 +195,7 @@
hexadecimal numbers, such as 0x330.</para>
<para>We recommend you print or write down this information before
installing FreeBSD. It may help to use a table, like this:</para>
installing &os;. It may help to use a table, like this:</para>
<table pgwide="1" frame="none">
<title>Sample Device Inventory</title>
@ -293,22 +293,22 @@
<sect2>
<title>Backup Your Data</title>
<para>If the computer you will be installing FreeBSD on contains
<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 FreeBSD. The FreeBSD
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
undone.</para>
</sect2>
<sect2 id="install-where">
<title>Decide Where to Install FreeBSD</title>
<title>Decide Where to Install &os;</title>
<para>If you want FreeBSD to use your entire hard disk, then there is nothing
<para>If you want &os; to use your entire hard disk, then there is nothing
more to concern yourself with at this point &mdash; you can skip this
section.</para>
<para>However, if you need FreeBSD to co-exist with other operating
<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>
@ -320,7 +320,7 @@
&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 FreeBSD utility
in &os; itself. For example, the &os; utility
<command>fdisk</command> which operates on the PC disk partitions,
refers to slices instead of partitions. By design, the PC only
supports four partitions per disk. These partitions are called
@ -332,7 +332,7 @@
extended partition.</para>
<para>Each partition has a <firstterm>partition ID</firstterm>, which is
a number used to identify the type of data on the partition. FreeBSD
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
@ -341,16 +341,16 @@
<firstterm>drive letter</firstterm>, starting with
<devicename>C:</devicename>.</para>
<para>FreeBSD must be installed into a primary partition. FreeBSD can
<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
FreeBSD partition on all, or some, of them. When you install FreeBSD,
&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 FreeBSD using the tools
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>
@ -358,7 +358,7 @@
may need to shrink one or more of your existing partitions
first.</para>
<para>A minimal installation of FreeBSD takes as little as 100&nbsp;MB
<para>A minimal installation of &os; takes as little as 100&nbsp;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
@ -404,7 +404,7 @@
<para>This means that your disk has two partitions on it, one per
drive letter. You can copy all your existing data from
<devicename>D:</devicename> to <devicename>C:</devicename>, which
will free up the second partition, ready for FreeBSD.</para>
will free up the second partition, ready for &os;.</para>
</example>
<example>
@ -414,10 +414,10 @@
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&nbsp;GB in size. You are
currently using 1.5&nbsp;GB of space, and want FreeBSD to have 2&nbsp;GB
currently using 1.5&nbsp;GB of space, and want &os; to have 2&nbsp;GB
of space.</para>
<para>In order to install FreeBSD you will need to either:</para>
<para>In order to install &os; you will need to either:</para>
<orderedlist>
<listitem>
@ -439,12 +439,12 @@
<sect2>
<title>Collect Your Network Configuration Details</title>
<para>If you intend to connect to a network as part of your FreeBSD
<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
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
FreeBSD can connect to the network to complete the install.</para>
&os; can connect to the network to complete the install.</para>
<sect3>
<title>Connecting to an Ethernet Network or Cable/DSL Modem</title>
@ -485,7 +485,7 @@
<title>Connecting Using a Modem</title>
<para>If you dial up to an ISP using a regular modem then you can
still install FreeBSD over the Internet, it will just take a very
still install &os; over the Internet, it will just take a very
long time.</para>
<para>You will need to know:</para>
@ -506,14 +506,14 @@
</sect3>
</sect2>
<sect2>
<title>Check for FreeBSD Errata</title>
<title>Check for &os; Errata</title>
<para>Although the FreeBSD project strives to ensure that each release
of FreeBSD is as stable as possible, bugs do occasionally creep into
<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
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">FreeBSD Errata</ulink>,
which is found on the FreeBSD web site. You
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>
@ -523,13 +523,13 @@
url="&url.base;/releases/index.html">release
information</ulink> section of the
<ulink
url="&url.base;/index.html">FreeBSD web site</ulink>.</para>
url="&url.base;/index.html">&os; web site</ulink>.</para>
</sect2>
<sect2>
<title>Obtain the FreeBSD Installation Files</title>
<title>Obtain the &os; Installation Files</title>
<para>The FreeBSD installation process can install FreeBSD from files
<para>The &os; installation process can install &os; from files
located in any of the following places:</para>
<itemizedlist>
@ -573,13 +573,13 @@
</listitem>
</itemizedlist>
<para>If you have purchased FreeBSD on CD or DVD then you already have
<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 you have not obtained the FreeBSD installation files you should
<para>If you have not obtained the &os; installation files you should
skip ahead to <xref linkend="install-diff-media"/> which explains how
to prepare to install FreeBSD from any of the above. After reading
to prepare to install &os; from any of the above. After reading
that section, you should come back here, and read on to
<xref linkend="install-boot-media"/>.</para>
</sect2>
@ -587,20 +587,20 @@
<sect2 id="install-boot-media">
<title>Prepare the Boot Media</title>
<para>The FreeBSD installation process is started by booting the
computer into the FreeBSD installer&mdash;it is not a program you run
<para>The &os; installation process is started by booting the
computer into the &os; installer&mdash;it is not a program you 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 FreeBSD on CDROM or DVD (either one you purchased
<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
FreeBSD CDROM and DVD images are bootable and can be used to install
FreeBSD without any other special preparation.</para>
&os; CDROM and DVD images are bootable and can be used to install
&os; without any other special preparation.</para>
</tip>
<para>To create a bootable memory stick, follow these
@ -649,7 +649,7 @@
<title>Write The Image File to the Memory Stick</title>
<procedure>
<title>Using FreeBSD To Write the Image</title>
<title>Using &os; To Write the Image</title>
<warning>
<para>The example below
@ -761,7 +761,7 @@
floppies if choosing this installation route.</para>
<important>
<para>If you try to install FreeBSD and the installation
<para>If you try to install &os; and the installation
program 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
@ -799,16 +799,16 @@
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 FreeBSD FTP site.</para>
directory</ulink> on the &os; FTP site.</para>
<para>If you are writing the floppies on a &unix; system (such as
another FreeBSD system) you can use the &man.dd.1; command to
write the image files directly to disk. On FreeBSD, you would
another &os; system) you can use the &man.dd.1; command to
write the image files directly to disk. On &os;, you would
run:</para>
<screen>&prompt.root; <userinput>dd if=boot.flp of=/dev/fd0</userinput></screen>
<para>On FreeBSD, <filename>/dev/fd0</filename> refers to the
<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;
@ -818,7 +818,7 @@
</step>
</procedure>
<para>You are now ready to start installing FreeBSD.</para>
<para>You are now ready to start installing &os;.</para>
</sect2>
</sect1>
@ -927,7 +927,7 @@ We can take no responsibility for lost disk contents!</literallayout>
</step>
<step>
<para>FreeBSD will start to boot. If you are booting from CDROM you
<para>&os; will start to boot. If you are booting from CDROM you
will see a display similar to this (version information
omitted):</para>
@ -1140,7 +1140,7 @@ Mounting root from ufs:/dev/md0c
/stand/sysinstall running as init on vty0</screen>
</figure>
<para>Check the probe results carefully to make sure that FreeBSD found
<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. A <link linkend="kernelconfig">custom kernel</link>
allows you to add in support for devices which are not in the
@ -1187,7 +1187,7 @@ Mounting root from ufs:/dev/md0c
<title>Introducing Sysinstall</title>
<para>The <application>sysinstall</application> utility is the installation
application provided by the FreeBSD Project. It is console based and is
application provided by the &os; Project. It is console based and is
divided into a number of menus and screens that you can use to
configure and control the installation process.</para>
@ -1344,7 +1344,7 @@ Mounting root from ufs:/dev/md0c
<title>Begin a Standard Installation</title>
<para>The <guimenuitem>Standard</guimenuitem> installation is the
option recommended for those new to &unix; or FreeBSD. Use the arrow
option recommended for those new to &unix; or &os;. Use the arrow
keys to select <guimenuitem>Standard</guimenuitem> and
then press <keycap>Enter</keycap> to start the installation.</para>
@ -1363,15 +1363,15 @@ Mounting root from ufs:/dev/md0c
<sect1 id="install-steps">
<title>Allocating Disk Space</title>
<para>Your first task is to allocate disk space for FreeBSD, and label
<para>Your first task is to allocate disk space for &os;, and label
that space so that <application>sysinstall</application> can prepare
it. In order to do this you need to know how FreeBSD expects to find
it. In order to do this you need to know how &os; expects to find
information on the disk.</para>
<sect2 id="install-drive-bios-numbering">
<title>BIOS Drive Numbering</title>
<para>Before you install and configure FreeBSD on your system, there is an
<para>Before you install and configure &os; on your system, there is an
important subject that you should be aware of, especially if you have
multiple hard drives.</para>
@ -1400,14 +1400,14 @@ Mounting root from ufs:/dev/md0c
fashion for up to seven drives.</para>
<para>A user who is accustomed to taking advantage of these features may
become surprised when the results with FreeBSD are not as expected.
FreeBSD does not use the BIOS, and does not know the <quote>logical BIOS
become surprised when the results with &os; are not as expected.
&os; does not use the BIOS, and does not know the <quote>logical BIOS
drive mapping</quote>. This can lead to very perplexing situations,
especially when drives are physically identical in geometry, and have
also been made as data clones of one another.</para>
<para>When using FreeBSD, always restore the BIOS to natural drive
numbering before installing FreeBSD, and then leave it that way. If you
<para>When using &os;, always restore the BIOS to natural drive
numbering before installing &os;, and then leave it that way. If you
need to switch drives around, then do so, but do it the hard way, and
open the case and move the jumpers and cables.</para>
@ -1415,9 +1415,9 @@ Mounting root from ufs:/dev/md0c
<title>An Illustration from the Files of Bill and Fred's Exceptional
Adventures:</title>
<para>Bill breaks-down an older Wintel box to make another FreeBSD box
<para>Bill breaks-down an older Wintel box to make another &os; box
for Fred. Bill installs a single SCSI drive as SCSI unit zero and
installs FreeBSD on it.</para>
installs &os; on it.</para>
<para>Fred begins using the system, but after several days notices that
the older SCSI drive is reporting numerous soft errors and reports
@ -1432,21 +1432,21 @@ Mounting root from ufs:/dev/md0c
that the new drive is installed and functioning nicely, Bill decides
that it is a good idea to start using it, so he uses features in the
SCSI BIOS to re-order the disk drives so that the system boots from
SCSI unit four. FreeBSD boots and runs just fine.</para>
SCSI unit four. &os; boots and runs just fine.</para>
<para>Fred continues his work for several days, and soon Bill and Fred
decide that it is time for a new adventure &mdash; time to upgrade
to a
newer version of FreeBSD. Bill removes SCSI unit zero because it was
newer version of &os;. Bill removes SCSI unit zero because it was
a bit flaky and replaces it with another identical disk drive from
the <quote>archive</quote>. Bill then installs the new version of
FreeBSD onto the new SCSI unit zero using Fred's magic Internet FTP
&os; onto the new SCSI unit zero using Fred's magic Internet FTP
floppies. The installation goes well.</para>
<para>Fred uses the new version of FreeBSD for a few days, and certifies
<para>Fred uses the new version of &os; for a few days, and certifies
that it is good enough for use in the engineering department. It is
time to copy all of his work from the old version. So Fred mounts
SCSI unit four (the latest copy of the older FreeBSD version). Fred
SCSI unit four (the latest copy of the older &os; version). Fred
is dismayed to find that none of his precious work is present on SCSI
unit four.</para>
@ -1456,11 +1456,11 @@ Mounting root from ufs:/dev/md0c
SCSI unit four, unit four became the <quote>new clone</quote>.
When Bill re-ordered the SCSI BIOS so that he could boot from
SCSI unit four, he was only fooling himself.
FreeBSD was still running on SCSI unit zero.
&os; was still running on SCSI unit zero.
Making this kind of BIOS change will cause some or all of the Boot and
Loader code to be fetched from the selected BIOS drive, but when the
FreeBSD kernel drivers take-over, the BIOS drive numbering will be
ignored, and FreeBSD will transition back to normal drive numbering.
&os; kernel drivers take-over, the BIOS drive numbering will be
ignored, and &os; will transition back to normal drive numbering.
In the illustration at hand, the system continued to operate on the
original SCSI unit zero, and all of Fred's data was there, not on SCSI
unit four. The fact that the system appeared to be running on SCSI
@ -1528,7 +1528,7 @@ Mounting root from ufs:/dev/md0c
<para>Consider what would happen if you had two IDE hard disks, one
as the master on the first IDE controller, and one as the master on
the second IDE controller. If FreeBSD numbered these as it found
the second IDE controller. If &os; numbered these as it found
them, as <devicename>ad0</devicename> and
<devicename>ad1</devicename> then everything would work.</para>
@ -1538,7 +1538,7 @@ Mounting root from ufs:/dev/md0c
<devicename>ad2</devicename>. Because device names (such as
<devicename>ad1s1a</devicename>) are used to find filesystems, you
may suddenly discover that some of your filesystems no longer
appear correctly, and you would need to change your FreeBSD
appear correctly, and you would need to change your &os;
configuration.</para>
<para>To work around this, the kernel can be configured to name IDE
@ -1549,13 +1549,13 @@ Mounting root from ufs:/dev/md0c
<devicename>ad0</devicename> or <devicename>ad1</devicename>
devices.</para>
<para>This configuration is the default for the FreeBSD kernel, which
<para>This configuration is the default for the &os; kernel, which
is why this display shows <devicename>ad0</devicename> and
<devicename>ad2</devicename>. The machine on which this screenshot
was taken had IDE disks on both master channels of the IDE
controllers, and no disks on the slave channels.</para>
<para>You should select the disk on which you want to install FreeBSD,
<para>You should select the disk on which you want to install &os;,
and then press &gui.ok;.
<application>FDisk</application> will start, with a display similar to
that shown in <xref linkend="sysinstall-fdisk1"/>.</para>
@ -1564,11 +1564,11 @@ Mounting root from ufs:/dev/md0c
sections.</para>
<para>The first section, covering the first two lines of the display,
shows details about the currently selected disk, including its FreeBSD
shows details about the currently selected disk, including its &os;
name, the disk geometry, and the total size of the disk.</para>
<para>The second section shows the slices that are currently on the
disk, where they start and end, how large they are, the name FreeBSD
disk, where they start and end, how large they are, the name &os;
gives them, and their description and sub-type. This example shows two
small unused slices, which are artifacts of disk layout schemes on the
PC. It also shows one large <acronym>FAT</acronym> slice, which
@ -1592,15 +1592,15 @@ Mounting root from ufs:/dev/md0c
<para>What you do now will depend on how you want to slice up your
disk.</para>
<para>If you want to use FreeBSD for the entire disk (which will delete
<para>If you want to use &os; for the entire disk (which will delete
all the other data on this disk when you confirm that you want
<application>sysinstall</application> to continue later in the
installation process) then you can press <keycap>A</keycap>, which
corresponds to the <guimenuitem>Use Entire Disk</guimenuitem> option.
The existing slices will be removed, and replaced with a small area
flagged as <literal>unused</literal> (again, an artifact of PC disk
layout), and then one large slice for FreeBSD. If you do this, then
you should select the newly created FreeBSD slice using the arrow
layout), and then one large slice for &os;. If you do this, then
you should select the newly created &os; slice using the arrow
keys, and press <keycap>S</keycap> to mark the slice as being
bootable. The screen will then look very similar to
<xref linkend="sysinstall-fdisk2"/>. Note the
@ -1609,7 +1609,7 @@ Mounting root from ufs:/dev/md0c
booted from.</para>
<para>If you will be deleting an existing slice to make space for
FreeBSD then you should select the slice using the arrow keys, and
&os; then you should select the slice using the arrow keys, and
then press <keycap>D</keycap>. You can then press <keycap>C</keycap>,
and be prompted for size of slice you want to create. Enter the
appropriate figure and press <keycap>Enter</keycap>. The default
@ -1617,7 +1617,7 @@ Mounting root from ufs:/dev/md0c
make, which could be the largest contiguous block of unallocated
space or the size of the entire hard disk.</para>
<para>If you have already made space for FreeBSD (perhaps by using a
<para>If you have already made space for &os; (perhaps by using a
tool such as <application>&partitionmagic;</application>) then you can
press <keycap>C</keycap> to create a new slice. Again, you will be
prompted for the size of slice you would like to create.</para>
@ -1641,26 +1641,26 @@ Mounting root from ufs:/dev/md0c
<title>Install a Boot Manager</title>
<para>You now have the option to install a boot manager. In general,
you should choose to install the FreeBSD boot manager if:</para>
you should choose to install the &os; boot manager if:</para>
<itemizedlist>
<listitem>
<para>You have more than one drive, and have installed FreeBSD onto
<para>You have more than one drive, and have installed &os; onto
a drive other than the first one.</para>
</listitem>
<listitem>
<para>You have installed FreeBSD alongside another operating system
on the same disk, and you want to choose whether to start FreeBSD
<para>You have installed &os; alongside another operating system
on the same disk, and you want to choose whether to start &os;
or the other operating system when you start the computer.</para>
</listitem>
</itemizedlist>
<para>If FreeBSD is going to be the only operating system on
<para>If &os; is going to be the only operating system on
this machine, installed on the first hard disk, then the
<guimenuitem>Standard</guimenuitem> boot manager will suffice.
Choose <guimenuitem>None</guimenuitem> if you are using a
third-party boot manager capable of booting FreeBSD.</para>
third-party boot manager capable of booting &os;.</para>
<para>Make your choice and press <keycap>Enter</keycap>.</para>
@ -1684,13 +1684,13 @@ Mounting root from ufs:/dev/md0c
<para>If there is more than one drive, it will return to the
Select Drives screen after the boot manager selection. If you wish to
install FreeBSD on to more than one disk, then you can select another
install &os; on to more than one disk, then you can select another
disk here and repeat the slice process using
<application>FDisk</application>.</para>
<important>
<para>If you are installing FreeBSD on a drive other than your
first, then the FreeBSD boot manager needs to be installed on
<para>If you are installing &os; on a drive other than your
first, then the &os; boot manager needs to be installed on
both drives.</para>
</important>
@ -1727,10 +1727,10 @@ Mounting root from ufs:/dev/md0c
<para>Certain applications can benefit from particular partition
schemes, especially if you are laying out partitions across more than
one disk. However, for this, your first FreeBSD installation, you do
one disk. However, for this, your first &os; installation, you do
not need to give too much thought to how you partition the disk. It
is more important that you install FreeBSD and start learning how to
use it. You can always re-install FreeBSD to change your partition
is more important that you install &os; and start learning how to
use it. You can always re-install &os; to change your partition
scheme when you are more familiar with the operating system.</para>
<para>This scheme features four partitions&mdash;one for swap space, and
@ -1768,11 +1768,11 @@ Mounting root from ufs:/dev/md0c
<entry>This is the root filesystem. Every other filesystem
will be mounted somewhere under this one. 1&nbsp;GB is a
reasonable size for this filesystem. You will not be storing
too much data on it, as a regular FreeBSD install will put
too much data on it, as a regular &os; install will put
about 128&nbsp;MB of data here. The remaining space is for
temporary data, and also leaves expansion space if future
versions of
FreeBSD need more space in <filename>/</filename>.</entry>
&os; need more space in <filename>/</filename>.</entry>
</row>
<row>
@ -1792,7 +1792,7 @@ Mounting root from ufs:/dev/md0c
the swap amount to 64&nbsp;MB.</para><para>
If you have more than one disk then you can put swap
space on each disk. FreeBSD will then use each disk for
space on each disk. &os; will then use each disk for
swap, which effectively speeds up the act of swapping. In
this case, calculate the total amount of swap you need
(e.g., 128&nbsp;MB), and then divide this by the number of
@ -1812,8 +1812,8 @@ Mounting root from ufs:/dev/md0c
files that are constantly varying;
log files, and other administrative files. Many
of these files are read-from or written-to extensively during
FreeBSD's day-to-day running. Putting these files on another
filesystem allows FreeBSD to optimize the access of these
&os;'s day-to-day running. Putting these files on another
filesystem allows &os; to optimize the access of these
files without affecting other files in other directories that
do not have the same access pattern.</entry>
</row>
@ -1839,7 +1839,7 @@ Mounting root from ufs:/dev/md0c
Defaults</literal> by the &os; partition editor.</para>
</warning>
<para>If you will be installing FreeBSD on to more than one disk then
<para>If you will be installing &os; on to more than one disk then
you must also create partitions in the other slices that you
configured. The easiest way to do this is to create two partitions on
each disk, one for the swap space, and one for a filesystem.</para>
@ -2068,7 +2068,7 @@ Mounting root from ufs:/dev/md0c
<filename>/usr</filename>, you can leave the suggested size as is, to
use the rest of the slice.</para>
<para>Your final FreeBSD DiskLabel Editor screen will appear similar to
<para>Your final &os; DiskLabel Editor screen will appear similar to
<xref linkend="sysinstall-label4"/>, although your values chosen may
be different. Press <keycap>Q</keycap> to finish.</para>
@ -2094,7 +2094,7 @@ Mounting root from ufs:/dev/md0c
on the intended use of the system and the amount of disk space
available. The predefined options range from installing the
smallest possible configuration to everything. Those who are
new to &unix; and/or FreeBSD should almost certainly select one
new to &unix; and/or &os; should almost certainly select one
of these canned options. Customizing a distribution set is
typically for the more experienced user.</para>
@ -2139,7 +2139,7 @@ Mounting root from ufs:/dev/md0c
<title>Installing the Ports Collection</title>
<para>After selecting the desired distribution, an opportunity to
install the FreeBSD Ports Collection is presented. The ports
install the &os; Ports Collection is presented. The ports
collection is an easy and convenient way to install software.
The Ports Collection does not contain the source code necessary
to compile the software. Instead, it is a collection of files which
@ -2150,10 +2150,10 @@ Mounting root from ufs:/dev/md0c
<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 FreeBSD &rel.current;, the FreeBSD
adequate hard disk space. As of &os; &rel.current;, the &os;
Ports Collection takes up about &ports.size; of disk space.
You can safely assume a larger value for more recent versions
of FreeBSD.</para>
of &os;.</para>
<screen> User Confirmation Requested
Would you like to install the FreeBSD ports collection?
@ -2382,7 +2382,7 @@ installation menus to retry whichever operations have failed.
<para>Configuration of various options follows the successful
installation. An option can be configured by re-entering the
configuration options before booting the new FreeBSD
configuration options before booting the new &os;
system or after installation using
<command>sysinstall</command>
and selecting
@ -2396,7 +2396,7 @@ installation menus to retry whichever operations have failed.
above.</para>
<para>For detailed information on Local Area Networks and
configuring FreeBSD as a gateway/router refer to the
configuring &os; as a gateway/router refer to the
<link linkend="advanced-networking">Advanced Networking</link>
chapter.</para>
@ -3926,7 +3926,7 @@ Password:</screen>
</sect2>
<sect2 id="shutdown">
<title>FreeBSD Shutdown</title>
<title>&os; Shutdown</title>
<para>It is important to properly shutdown the operating
system. Do not just turn off power. First, become a superuser by
@ -3966,7 +3966,7 @@ Please press any key to reboot.</screen>
</indexterm>
<para>The following section covers basic installation troubleshooting,
such as common problems people have reported. There are also a few
questions and answers for people wishing to dual-boot FreeBSD with
questions and answers for people wishing to dual-boot &os; with
&ms-dos; or &windows;.</para>
<sect2>
@ -4283,11 +4283,11 @@ Please press any key to reboot.</screen>
<title>Advanced Installation Guide</title>
<para>This section describes how to install FreeBSD in exceptional
<para>This section describes how to install &os; in exceptional
cases.</para>
<sect2 id="headless-install">
<title>Installing FreeBSD on a System without a Monitor or
<title>Installing &os; on a System without a Monitor or
Keyboard</title>
<indexterm>
@ -4297,7 +4297,7 @@ Please press any key to reboot.</screen>
<indexterm><primary>serial console</primary></indexterm>
<para>This type of installation is called a <quote>headless
install</quote>, because the machine that you are trying to install
FreeBSD on either does not have a monitor attached to it, or does not
&os; on either does not have a monitor attached to it, or does not
even have a VGA output. How is this possible you ask? Using a
serial console. A serial console is basically using another
machine to act as the main display and keyboard for a
@ -4320,8 +4320,8 @@ Please press any key to reboot.</screen>
<primary><command>mount</command></primary>
</indexterm>
<para>If you were to boot into the USB stick that you just
made, FreeBSD would boot into its normal install mode. We
want FreeBSD to boot into a serial console for our
made, &os; would boot into its normal install mode. We
want &os; to boot into a serial console for our
install. To do this, you have to mount the
USB disk onto your &os;
system using the &man.mount.8; command.</para>
@ -4438,7 +4438,7 @@ Please press any key to reboot.</screen>
through your <command>cu</command> session. It will load the kernel
and then it will come up
with a selection of what kind of terminal to use. Select the
FreeBSD color console and proceed with your install!</para>
&os; color console and proceed with your install!</para>
</sect2>
</sect1>
@ -4447,13 +4447,13 @@ Please press any key to reboot.</screen>
<title>Preparing Your Own Installation Media</title>
<note>
<para>To prevent repetition, <quote>FreeBSD disc</quote> in this context
means a FreeBSD CDROM or DVD that you have purchased or produced
<para>To prevent repetition, <quote>&os; disc</quote> in this context
means a &os; CDROM or DVD that you have purchased or produced
yourself.</para>
</note>
<para>There may be some situations in which you need to create your own
FreeBSD installation media and/or source. This might be physical media,
&os; installation media and/or source. This might be physical media,
such as a tape, or a source that <application>sysinstall</application>
can use to retrieve the files, such as a local FTP site, or an &ms-dos;
partition.</para>
@ -4463,16 +4463,16 @@ Please press any key to reboot.</screen>
<itemizedlist>
<listitem>
<para>You have many machines connected to your local network, and one
FreeBSD disc. You want to create a local FTP site using the
contents of the FreeBSD disc, and then have your machines use this
&os; disc. You want to create a local FTP site using the
contents of the &os; disc, and then have your machines use this
local FTP site instead of needing to connect to the Internet.</para>
</listitem>
<listitem>
<para>You have a FreeBSD disc, and FreeBSD does not recognize your
<para>You have a &os; disc, and &os; does not recognize your
CD/DVD drive, but &ms-dos; / &windows; does. You want to copy the
FreeBSD installation files to a &ms-dos; partition on the same
computer, and then install FreeBSD using those files.</para>
&os; installation files to a &ms-dos; partition on the same
computer, and then install &os; using those files.</para>
</listitem>
<listitem>
@ -4484,19 +4484,19 @@ Please press any key to reboot.</screen>
<listitem>
<para>You want to create a tape that can be used to install
FreeBSD.</para>
&os;.</para>
</listitem>
</itemizedlist>
<sect2 id="install-cdrom">
<title>Creating an Installation CDROM</title>
<para>As part of each release, the FreeBSD project makes available at
<para>As part of each release, the &os; project makes available at
least two CDROM images (<quote>ISO images</quote>) per supported
architecture. These images can be written
(<quote>burned</quote>) to CDs if you have a CD writer, and then used
to install FreeBSD. If you have a CD writer, and bandwidth is cheap,
then this is the easiest way to install FreeBSD.</para>
to install &os;. If you have a CD writer, and bandwidth is cheap,
then this is the easiest way to install &os;.</para>
<procedure>
<step>
@ -4536,7 +4536,7 @@ Please press any key to reboot.</screen>
<entry><filename>&os;-<replaceable>version</replaceable>-RELEASE-<replaceable>arch</replaceable>-dvd1.iso.gz</filename></entry>
<entry>This DVD image contains everything necessary to
install the base FreeBSD operating system, a
install the base &os; operating system, a
collection of pre-built packages, and the
documentation. It also supports booting into a
<quote>livefs</quote> based rescue mode.</entry>
@ -4622,7 +4622,7 @@ Please press any key to reboot.</screen>
<title>Write the CDs</title>
<para>You must then write the CD images to disc. If you will be
doing this on another FreeBSD system then see
doing this on another &os; system then see
<xref linkend="creating-cds"/> for more information (in
particular, <xref linkend="burncd"/> and
<xref linkend="cdrecord"/>).</para>
@ -4635,14 +4635,14 @@ Please press any key to reboot.</screen>
</procedure>
<note><para>If you are interested in building a customized
release of FreeBSD, please see the <ulink
release of &os;, please see the <ulink
url="&url.articles.releng;">Release Engineering
Article</ulink>.</para></note>
</sect2>
<sect2 id="install-ftp">
<title>Creating a Local FTP Site with a FreeBSD Disc</title>
<title>Creating a Local FTP Site with a &os; Disc</title>
<indexterm>
<primary>installation</primary>
@ -4650,13 +4650,13 @@ Please press any key to reboot.</screen>
<tertiary>FTP</tertiary>
</indexterm>
<para>FreeBSD discs are laid out in the same way as the FTP site. This
<para>&os; discs are laid out in the same way as the FTP site. This
makes it very easy for you to create a local FTP site that can be used
by other machines on your network when installing FreeBSD.</para>
by other machines on your network when installing &os;.</para>
<procedure>
<step>
<para>On the FreeBSD computer that will host the FTP site, ensure
<para>On the &os; computer that will host the FTP site, ensure
that the CDROM is in the drive, and mounted on
<filename>/cdrom</filename>.</para>
@ -4734,7 +4734,7 @@ Please press any key to reboot.</screen>
the use of improperly formatted media, which is why we are
making a point of it now.</para>
<para>If you are creating the floppies on another FreeBSD machine,
<para>If you are creating the floppies on another &os; machine,
a format is still not a bad idea, though you do not need to put
a &ms-dos; filesystem on each floppy. You can use the
<command>bsdlabel</command> and <command>newfs</command>
@ -4787,7 +4787,7 @@ Please press any key to reboot.</screen>
reproduced within this directory, so we suggest using the &ms-dos;
<command>xcopy</command> command if you are copying it from a CD.
For example, to prepare for a minimal installation of
FreeBSD:</para>
&os;:</para>
<screen><prompt>C:\&gt;</prompt> <userinput>md c:\freebsd</userinput>
<prompt>C:\&gt;</prompt> <userinput>xcopy e:\bin c:\freebsd\bin\ /s</userinput>
@ -4866,12 +4866,12 @@ Please press any key to reboot.</screen>
Parallel port (PLIP (laplink cable)).</para>
<para>For the fastest possible network installation, an
Ethernet adapter is always a good choice! FreeBSD supports most
Ethernet adapter is always a good choice! &os; supports most
common PC Ethernet cards; a table of supported cards (and their
required settings) is provided in the Hardware Notes for each
release of FreeBSD. If you are using one of the supported PCMCIA
release of &os;. If you are using one of the supported PCMCIA
Ethernet cards, also be sure that it is plugged in
<emphasis>before</emphasis> the laptop is powered on! FreeBSD does
<emphasis>before</emphasis> the laptop is powered on! &os; does
not, unfortunately, currently support hot insertion of PCMCIA cards
during installation.</para>
@ -4909,7 +4909,7 @@ Please press any key to reboot.</screen>
If you have problems, logging can be directed to the screen using
the command <command>set log local ...</command>.</para>
<para>If a hard-wired connection to another FreeBSD
<para>If a hard-wired connection to another &os;
machine is available, you might also consider installing
over a <quote>laplink</quote> parallel port cable. The data rate
over the parallel port is much higher than what is typically
@ -4925,7 +4925,7 @@ Please press any key to reboot.</screen>
<tertiary>NFS</tertiary>
</indexterm>
<para>The NFS installation is fairly straight-forward. Simply
copy the FreeBSD distribution files you want onto an NFS server
copy the &os; distribution files you want onto an NFS server
and then point the NFS media selection at it.</para>
<para>If this server supports only <quote>privileged port</quote>
@ -4940,14 +4940,14 @@ Please press any key to reboot.</screen>
<para>In order for NFS installation to work, the server must
support subdir mounts, for example, if your
FreeBSD&nbsp;&rel.current; distribution directory lives on:
&os;&nbsp;&rel.current; distribution directory lives on:
<filename>ziggy:/usr/archive/stuff/FreeBSD</filename>, then
<hostid>ziggy</hostid> will have to allow the direct mounting
of <filename>/usr/archive/stuff/FreeBSD</filename>, not just
<filename>/usr</filename> or
<filename>/usr/archive/stuff</filename>.</para>
<para>In FreeBSD's <filename>/etc/exports</filename> file, this
<para>In &os;'s <filename>/etc/exports</filename> file, this
is controlled by the <option>-alldirs</option> options. Other NFS
servers may have different conventions. If you are getting
<errorname>permission denied</errorname> messages from the