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

* Revise comma usage

Browse source 
* Minor wording/technical inconsistencies
* Remove contractions
* Moved Slice description into Disk Organization to compliment the
  existing description
* Remove redundancy in earlier disks naming commit
* Moved complete list of disk device names back into Storage chapter
* Fixed initial boot-up/probe/login text--missing FreeBSD banner
This commit is contained in:
Chern Lee 2001-10-08 22:35:07 +00:00
parent 0dbffb2e8f
commit 2f8c248c27
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=10896
1 changed files with 125 additions and 215 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

340
en_US.ISO8859-1/books/handbook/install/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/install/chapter.sgml,v 1.123 2001/10/08 12:52:54 tom Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/install/chapter.sgml,v 1.124 2001/10/08 20:30:47 chern Exp $
-->
<chapter id="install">
@ -97,15 +97,15 @@
your configuration.</para>
<para>If you already have another operating system installed, such as
Windows, or Linux, it is a good idea to use the facilities provided
Windows or Linux, it is a good idea to use the facilities provided
by those operating systems to see how your hardware is already
configured. If you are really not sure what settings an expansion
card is using you may find it printed on the card itself. Popular IRQ
card is using, you may find it printed on the card itself. Popular IRQ
numbers are 3, 5, and 7, and IO port addresses are normally written as
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 FreeBSD. It may help to use a table, like this:</para>
<table pgwide="1" frame="none">
<title>Sample Device Inventory</title>
@ -199,16 +199,16 @@
valuable data then ensure you have it backed up, and that you have
tested the backups before installing FreeBSD. The FreeBSD
installation routine will prompt you several times before writing any
data to your disk, but once that process has started it can not be
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>
<para>If you want FreeBSD to use all your disk then there is nothing
more to concern yourself with at this point, and you can skip to the
next section..</para>
<para>If you want FreeBSD to use all your disk, then there is nothing
more to concern yourself with at this point &mdash; you can skip to the
next section.</para>
<para>However, if you need FreeBSD to co-exist with other operating
systems then you need to have a rough understanding of how data is
@ -221,14 +221,14 @@
called <firstterm>partitions</firstterm>. By design, the PC only
supports four partitions per disk. These partitions are called
<firstterm>primary partitions</firstterm>. To work around this
limitation, and allow more than four partitions, a new partition type
limitation and allow more than four partitions, a new partition type
was created, the <firstterm>extended partition</firstterm>. A disk
may contain only one extended partition. Special partitions, called
<firstterm>logical partitions</firstterm>, can be created inside this
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. FreeBSD
partitions have the partition ID <literal>165</literal>.</para>
<para>In general, each operating system that you use will identify
@ -237,16 +237,16 @@
<firstterm>drive letter</firstterm>, starting with
<devicename>C:</devicename>.</para>
<para>FreeBSD must be installed in to a primary partition. FreeBSD can
<para>FreeBSD must be installed into a primary partition. FreeBSD 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
partition. However, if you have multiple disks, then you can create a
FreeBSD partition on all, or some, of them. When you install FreeBSD,
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 to use, using the tools
<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
provided by the other operating systems you use (e.g.,
<command>fdisk</command> on DOS or Windows).</para>
@ -259,7 +259,7 @@
leaving almost no space for your own files. A more realistic minimum
is 250MB without a graphical environment, and 350MB or more if you
want a graphical user interface. If you intend to install a lot of
third party software as well then you will need more space.</para>
third party software as well, then you will need more space.</para>
<para>You can use a commercial tool such as <application>Partition
Magic</application> to resize your partitions to make space for
@ -278,7 +278,7 @@
<example>
<title>Using an existing partition unchanged</title>
<para>Suppose that you have a computer with a single 4GB disk, that
<para>Suppose that you have a computer with a single 4GB disk that
already has a version of Windows installed, and you have split the
disk in to two drive letters, <devicename>C:</devicename> and
<devicename>D:</devicename>, each of which is 2GB in size. You have
@ -305,7 +305,7 @@
<orderedlist>
<listitem>
<para>Back up your Windows data, and then reinstall Windows,
<para>Backup your Windows data, and then reinstall Windows,
asking for a 2GB partition at install time.</para>
</listitem>
@ -361,12 +361,13 @@ pqb0.0.1.4.0 PQB0 PCI EIDE</screen>
refers to a SCSI with SCSI target ID 1 on the first SCSI bus (A),
whereas <devicename>DKC300</devicename> refers to a SCSI disk
with SCSI ID 3 on the third SCSI bus (C). Devicename <devicename>
PKx</devicename>refers to the SCSI host bus adapter. As
PKx</devicename> refers to the SCSI host bus adapter. As
seen in the <literal>SHOW DEVICE</literal> output SCSI
CDROM drives are treated as any other SCSI hard disk drive.</para>
<para>IDE disks have names like <devicename>DQx</devicename>,
<devicename>PQx</devicename> is the associated IDE controller.</para>
<para>IDE disks have names similar to <devicename>DQx</devicename>,
while <devicename>PQx</devicename> is the associated IDE
controller.</para>
</sect3>
</sect2>
@ -375,8 +376,9 @@ pqb0.0.1.4.0 PQB0 PCI EIDE</screen>
<title>Collect Your Network Configuration Details</title>
<para>If you intend to connect to a network as part of your FreeBSD
installation (e.g., if you will be installing from an FTP site, or an
NFS server) then you need to know your network configuration. You
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>
@ -384,7 +386,7 @@ pqb0.0.1.4.0 PQB0 PCI EIDE</screen>
<title>Connecting to an Ethernet Network, or Cable/DSL Modem</title>
<para>If you connect to an Ethernet network, or you have an Internet
connection via cable or DSL then you will need the following
connection via cable or DSL, then you will need the following
information:</para>
<orderedlist>
@ -405,7 +407,7 @@ pqb0.0.1.4.0 PQB0 PCI EIDE</screen>
</listitem>
</orderedlist>
<para>If you do not know this information then ask your system
<para>If you do not know this information, then ask your system
administrator or service provider. They may say that this
information is assigned automatically, using
<firstterm>DHCP</firstterm>. If so, make a note of this.</para>
@ -466,30 +468,34 @@ pqb0.0.1.4.0 PQB0 PCI EIDE</screen>
<para>If you have FreeBSD on CDROM or DVD, 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
section. The FreeBSD CDROM and DVD images are bootable and can be
used to install FreeBSD without any other special
preparation.</para>
</tip>
<para>The FreeBSD installation process is started by booting your
computer in to the FreeBSD installer&mdash;it is not a program you run
from within another operating system. To do this you must create some
computer into the FreeBSD installer&mdash;it is not a program you run
within another operating system. To do this, you must create some
floppy disks that can be booted from, and then boot from them.</para>
<para>If you are <emphasis>not</emphasis> installing directly from
CDROM, DVD, or FTP then you are probably preparing your own
installation media (e.g., an MS-DOS partition), which must be prepared
before you install FreeBSD. This is a slightly more advanced, and
before you install FreeBSD. This is a slightly more advanced,
infrequent activity, and is documented in <xref
linkend="install-diff-media">. This includes the scenario where you
want to create your own FTP site on your own network so that other
computers can use your site as a FreeBSD FTP installation site.</para>
<para>In general, to create boot floppy images, follow these
steps:</para>
<procedure>
<step>
<title>Acquire the Boot Floppy Images</title>
<para>The boot discs are available on your installation media, and
<para>The boot discs are available on your installation media
in the floppies directory, and
can also be downloaded from the <ulink
url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel.current;-RELEASE/floppies/">
floppies directory</ulink>.</para>
@ -509,7 +515,7 @@ pqb0.0.1.4.0 PQB0 PCI EIDE</screen>
to download these disk images. Some web browsers have been
known to use <emphasis>text</emphasis> (or
<emphasis>ASCII</emphasis>) mode, which will be apparent if you
can not boot from the disks.</para>
cannot boot from the disks.</para>
</important>
</step>
@ -523,9 +529,9 @@ pqb0.0.1.4.0 PQB0 PCI EIDE</screen>
<important>
<para>If you try to install FreeBSD and the installation
program crashes, freezes, or otherwise misbehaves one of
program crashes, freezes, or otherwise misbehaves, one of
the first things to suspect is the floppies. Try writing
the floppy image files to some other disks, and try
the floppy image files to some other disks and try
again.</para>
</important>
</step>
@ -536,38 +542,38 @@ pqb0.0.1.4.0 PQB0 PCI EIDE</screen>
<para>The <filename>.flp</filename> files are
<emphasis>not</emphasis> regular files you copy to the disk.
Instead, they are images of the complete contents of the
disk. This means that you can <emphasis>not</emphasis> use
disk. This means that you <emphasis>cannot</emphasis> use
commands like DOS' <command>copy</command> to write the
files. Instead, you must use specific tools to write the
images directly to the disk.</para>
<indexterm><primary>DOS</primary></indexterm>
<para>If you are creating the floppies on a computer running
DOS/Windows then we provide a tool to do
DOS/Windows, then we provide a tool to do
this called <command>fdimage</command>.</para>
<para>If you are using the floppies from the CDROM, and your
CDROM is the <devicename>E:</devicename> drive then you would
CDROM is the <devicename>E:</devicename> drive, then you would
run this:</para>
<screen><prompt>E:\&gt;</prompt> <userinput>tools\fdimage floppies\kern.flp A:</userinput></screen>
<para>Repeat this command for each <filename>.flp</filename>
file, replacing the floppy disk each time, and being sure to label
file, replacing the floppy disk each time, being sure to label
the disks with the name of the file that you copied to them.
Adjust the command line as necessary, depending on where you have
placed the <filename>.flp</filename> files. If you do not have
the CDROM then <command>fdimage</command> can be downloaded from
the CDROM, then <command>fdimage</command> can be downloaded from
the <ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/tools/"><filename>tools</filename> directory</ulink> on the FreeBSD 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
write the image files directly to disk. On FreeBSD, you would
run:</para>
<screen>&prompt.root; <userinput>dd if=kern.flp of=/dev/fd0</userinput></screen>
<para>On FreeBSD <filename>/dev/fd0</filename> refers to the
<para>On FreeBSD, <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
@ -633,13 +639,13 @@ We can take no responsibility for lost disk contents!</literallayout>
<literal>Floppy</literal>, <literal>CDROM</literal>,
<literal>First Hard Disk</literal>, and so on.</para>
<para>If you needed to prepare boot floppies then make sure that the
<para>If you needed to prepare boot floppies, then make sure that the
floppy disk is selected. If you are booting from the CDROM then
make sure that that is selected instead. In case of doubt you
make sure that that is selected instead. In case of doubt, you
should consult the manual that came with your computer, and/or its
motherboard.</para>
<para>Make the change, then save, and exit. The computer should now
<para>Make the change, then save and exit. The computer should now
restart.</para>
</step>
@ -650,7 +656,7 @@ We can take no responsibility for lost disk contents!</literallayout>
<filename>kern.flp</filename>. Put this disc in your floppy
drive.</para>
<para>If you are booting from CDROM then you will need to turn on
<para>If you are booting from CDROM, then you will need to turn on
the computer, and insert the CDROM at the first
opportunity.</para>
@ -693,7 +699,7 @@ FreeBSD/i386 bootstrap loader, Revision 0.8
Hit [Enter] to boot immediately, or any other key for command prompt.
Booting [kernel] in 9 seconds... _</screen>
<para>If you are booting from floppy disc you will see a display
<para>If you are booting from floppy disc, you will see a display
similar to this:</para>
<screen>Verifying DMI Pool Data ........
@ -801,23 +807,23 @@ Booting [kernel] in 9 seconds... _</screen>
the FreeBSD kernel has a driver associated with it. Each driver has a
two or three letter name, such as <devicename>sa</devicename> for the
SCSI sequential access driver, or <devicename>sio</devicename> for the
Serial I/O driver (which manages com ports).</para>
Serial I/O driver (which manages COM ports).</para>
<para>When the kernel starts each driver checks the system to see
<para>When the kernel starts, each driver checks the system to see
whether or not the hardware it supports exists on your system. If it
does then the driver configures the hardware, and makes it available
does, then the driver configures the hardware and makes it available
to the rest of the kernel.</para>
<para>This checking is commonly referred to as <firstterm>device
probing</firstterm>. Unfortunately, it is not always possible to do
this in a safe way. Some hardware drivers do not co-exist well
together, and probing for one piece of hardware can sometimes leave
another piece of hardware in an inconsistent state. This is a basic
another in an inconsistent state. This is a basic
limitation of the design of the PC.</para>
<para>Many older devices are what is called ISA devices&mdash;as opposed
<para>Many older devices are called ISA devices&mdash;as opposed
to PCI devices. The ISA specification requires each device to have
some information hard coded in to it, typically the Interrupt Request
some information hard coded into it, typically the Interrupt Request
Line number (IRQ) and IO port address that the driver uses. This
information is commonly set by using physical
<firstterm>jumpers</firstterm> on the card, or by using a DOS based
@ -834,7 +840,7 @@ Booting [kernel] in 9 seconds... _</screen>
driver for that device will need to be configured with the IRQ and
port address that you have set the card to. This is why carrying out
an inventory of your hardware (see <xref
linkend="install-inventory">) can be so useful.</para>
linkend="install-inventory">) can be useful.</para>
<para>Unfortunately, the default IRQs and memory ports used by some
drivers clash. This is because some ISA devices are shipped with IRQs
@ -844,17 +850,17 @@ Booting [kernel] in 9 seconds... _</screen>
<para>This is almost never an issue when running FreeBSD day-to-day.
Your computer will not normally contain two pieces of hardware that
clash, because then one of them would not work (irrespective of the
clash, because tone of them would not work (irrespective of the
operating system you are using).</para>
<para>It becomes an issue when you are installing FreeBSD for the first
time because the kernel used to carry out the install has to contain
as many drivers as possible, so that as many different hardware
configurations can be supported as possible. This means that some of
as many drivers as possible, so that many different hardware
configurations can be supported. This means that some of
those drivers will have conflicting configurations. The devices are
probed in a strict order, and if you own a device that is probed late
in the process, but that an earlier probe conflicted with, then your
hardware might not function, or be probed correctly when you install
in the process, but conflicted with an earlier probe, then your
hardware might not function or be probed correctly when you install
FreeBSD.</para>
<para>Because of this, the first thing you have the opportunity to do
@ -864,7 +870,7 @@ Booting [kernel] in 9 seconds... _</screen>
configuration if you do own the device but the defaults are
wrong.</para>
<para>That probably sounds much more complicated than it actually
<para>This probably sounds much more complicated than it actually
is.</para>
<para><xref linkend="kernel-config"> shows the first kernel
@ -884,7 +890,7 @@ Booting [kernel] in 9 seconds... _</screen>
</figure>
<para>The kernel configuration screen (<xref linkend="fig-userconfig">)
is then divided in to four sections.</para>
is then divided into four sections.</para>
<orderedlist>
<listitem>
@ -1042,7 +1048,7 @@ Booting [kernel] in 9 seconds... _</screen>
<para>Answer <keycap>Y</keycap> to save the parameters and the
probing will start. After displaying the probe results in white
on black text <application>Sysinstall</application> will start,
on black text <application>Sysinstall</application> will start
and display its main menu
(<xref linkend="sysinstall-main">).</para>
@ -1063,7 +1069,7 @@ Booting [kernel] in 9 seconds... _</screen>
<title>Reviewing the Device Probe Results</title>
<para>The last few hundred lines that have been displayed on screen are
stored, and can be reviewed.</para>
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 arrow keys, or
@ -1127,8 +1133,8 @@ Mounting root from ufs:/dev/md0c
</figure>
<para>Check the probe results carefully to make sure that FreeBSD found
all the devices you expected. If a device was not found then it will
be listed as missing. If the device's driver required configuring
all the devices you expected. If a device was not found, then it will
not be listed. If the device's driver required configuring
with the IRQ and port address then you should check that you entered
them correctly.</para>
@ -1171,14 +1177,15 @@ Mounting root from ufs:/dev/md0c
<title>Introducing Sysinstall</title>
<para><application>Sysinstall</application> is the installation
application provided by the FreeBSD Project. It is text based, and is
divided in to a number of menus and screens that you can use to
application provided by the FreeBSD 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>
<para>The <application>Sysinstall</application> menu system is controlled
by the arrow keys, <keycap>Enter</keycap>, <keycap>Space</keycap>. and
other keys. A detailed description of these keys, and what they do, is
contained in sysinstall's usage information.</para>
contained in <application>Sysinstall's</application> usage
information.</para>
<para>To review this information, ensure that the
<guimenuitem>Usage</guimenuitem> entry is highlighted and that the
@ -1341,130 +1348,13 @@ Mounting root from ufs:/dev/md0c
</sect2>
</sect1>
<sect1 id="install-drive">
<title>Installation Destination</title>
<sect1 id="install-steps">
<title>Allocating Disk Space</title>
<sect2 id="disks-naming">
<title>Disk Naming</title>
<indexterm><primary>IDE</primary></indexterm>
<indexterm><primary>SCSI</primary></indexterm>
<indexterm><primary>RAID</primary></indexterm>
<indexterm><primary>flash memory</primary></indexterm>
<para>Physical drives come in two main flavors,
<acronym>IDE</acronym>, or <acronym>SCSI</acronym>; but there
are also drives backed by RAID controllers, flash memory, and so
forth. Since these behave quite differently, they have their
own drivers and devices.</para>
<table id="disk-naming-physical-table">
<title>Physical Disk Naming Conventions</title>
<tgroup cols="2">
<thead>
<row>
<entry>Drive type</entry>
<entry>Drive device name</entry>
</row>
</thead>
<tbody>
<row>
<entry>IDE hard drives</entry>
<entry><literal>ad</literal> in 4.0-RELEASE,
<literal>wd</literal> before 4.0-RELEASE.</entry>
</row>
<row>
<entry>IDE CDROM drives</entry>
<entry><literal>acd</literal> from 4.0-RELEASE,
<literal>wcd</literal> before 4.0-RELEASE.</entry>
</row>
<row>
<entry>SCSI hard drives and USB Mass storage devices</entry>
<entry><literal>da</literal> from 3.0-RELEASE,
<literal>sd</literal> before 3.0-RELEASE.</entry>
</row>
<row>
<entry>SCSI CDROM drives</entry>
<entry><literal>cd</literal></entry>
</row>
<row>
<entry>Assorted non-standard CDROM drives</entry>
<entry><literal>mcd</literal> for Mitsumi CD-ROM,
<literal>scd</literal> for Sony CD-ROM,
<literal>matcd</literal> for Matsushita/Panasonic CD-ROM
</entry>
</row>
<row>
<entry>Floppy drives</entry>
<entry><literal>fd</literal></entry>
</row>
<row>
<entry>SCSI tape drives</entry>
<entry><literal>sa</literal> from 3.0-RELEASE,
<literal>st</literal> before 3.0-RELEASE.</entry>
</row>
<row>
<entry>IDE tape drives</entry>
<entry><literal>ast</literal> from 4.0-RELEASE,
<literal>wst</literal> before 4.0-RELEASE.</entry>
</row>
<row>
<entry>Flash drives</entry>
<entry><literal>fla</literal> for DiskOnChip Flash device
from 3.3-RELEASE.</entry>
</row>
<row>
<entry>RAID drives</entry>
<entry><literal>myxd</literal> for Mylex, and
<literal>amrd</literal> for AMI MegaRAID,
<literal>idad</literal> for Compaq Smart RAID.
from 4.0-RELEASE. <literal>id</literal> between
3.2-RELEASE and 4.0-RELEASE.</entry>
</row>
</tbody>
</tgroup>
</table>
<para>All the drives attached through a specific driver are
numbered starting at 0. So the first IDE drive would be
<quote>ad<emphasis>0</emphasis></quote>. You seldom need to use
these devices.</para>
<sect3 id="slicesandpartitions">
<title>Slices and Partitions</title>
<indexterm><primary>slices</primary></indexterm>
<indexterm><primary>partitions</primary></indexterm>
<indexterm><primary>dangerously dedicated</primary></indexterm>
<para>Physical disks usually contain
<firstterm>slices</firstterm>, unless they are
<quote>dangerously dedicated</quote>. Slice numbers follow
the device name, prefixed with an <literal>s</literal>,
starting at 1. So <quote>da0<emphasis>s1</emphasis></quote>
is the first slice on the first SCSI drive. There can only be
four physical slices on a disk, but you can have logical
slices inside physical slices of the appropriate type. These
extended slices are numbered starting at 5, so
<quote>ad0<emphasis>s5</emphasis></quote> is the first
extended slice on a disk. These devices are used by file
systems that expect to occupy a slice.</para>
<para>Slices, <quote>dangerously dedicated</quote> physical
drives, and other drives contain
<firstterm>partitions</firstterm>, which are represented as
letters from <literal>a</literal> to <literal>h</literal>.
This letter is appended to the device name, so
<quote>da0<emphasis>a</emphasis></quote> is the a partition on
the first da drive, which is <quote>dangerously dedicated</quote>.
<quote>ad1s3<emphasis>e</emphasis></quote> is the fifth partition
in the third slice of the second IDE disk drive.</para>
<para>The boot code expects partition <literal>a</literal> to be
the root partition. Partition <literal>b</literal> is normally
reserved for swap partitions, and <literal>c</literal> is an
unused partition the size of the entire slice or drive. This
is explained in <xref linkend="disks-adding">.</para>
</sect3>
</sect2>
<para>Your first task is to allocate disk space for FreeBSD, 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
information on the disk.</para>
<sect2 id="install-drive-bios-numbering">
<title>BIOS Drive Numbering</title>
@ -1573,15 +1463,6 @@ Mounting root from ufs:/dev/md0c
apply equally to IDE drives.</para>
</sidebar>
</sect2>
</sect1>
<sect1 id="install-steps">
<title>Allocating Disk Space</title>
<para>Your first task is to allocate disk space for FreeBSD, 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
information on the disk.</para>
<sect2>
<title>Disk Organization</title>
@ -1856,6 +1737,31 @@ Mounting root from ufs:/dev/md0c
FreeBSD's Unix background. Slices are numbered, starting at 1,
through to 4.</para>
<indexterm><primary>slices</primary></indexterm>
<indexterm><primary>partitions</primary></indexterm>
<indexterm><primary>dangerously dedicated</primary></indexterm>
<para>Slice numbers follow
the device name, prefixed with an <literal>s</literal>,
starting at 1. So <quote>da0<emphasis>s1</emphasis></quote>
is the first slice on the first SCSI drive. There can only be
four physical slices on a disk, but you can have logical
slices inside physical slices of the appropriate type. These
extended slices are numbered starting at 5, so
<quote>ad0<emphasis>s5</emphasis></quote> is the first
extended slice on a disk. These devices are used by file
systems that expect to occupy a slice.</para>
<para>Slices, <quote>dangerously dedicated</quote> physical
drives, and other drives contain
<firstterm>partitions</firstterm>, which are represented as
letters from <literal>a</literal> to <literal>h</literal>.
This letter is appended to the device name, so
<quote>da0<emphasis>a</emphasis></quote> is the a partition on
the first da drive, which is <quote>dangerously dedicated</quote>.
<quote>ad1s3<emphasis>e</emphasis></quote> is the fifth partition
in the third slice of the second IDE disk drive.</para>
<para>Finally, each disk on the system is identified. A disk name
starts with a code that indicates the type of disk, and then a number,
indicating which disk it is. Unlike slices, disk numbering starts at
@ -2173,7 +2079,7 @@ Mounting root from ufs:/dev/md0c
<itemizedlist>
<listitem>
<para>You have more than one drive, and have installed FreeBSD on to
<para>You have more than one drive, and have installed FreeBSD onto
a drive other than the first one.</para>
</listitem>
@ -2206,8 +2112,8 @@ 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 than you can select another
disk here, and repeat the slice process using
install FreeBSD on to more than one disk, then you can select another
disk here and repeat the slice process using
<application>FDisk</application>,</para>
<figure id="sysinstall-fdisk-drive2">
@ -2448,7 +2354,7 @@ Mounting root from ufs:/dev/md0c
</figure>
<para><application>Disklabel</application> can automatically create
partitions for you, and assign them default sizes. Try this now, by
partitions for you and assign them default sizes. Try this now, by
Pressing <keycap>A</keycap>. You will see a display similar to that
shown in <xref linkend="sysinstall-label2">. Depending on the size of
the disk you are using the defaults may or may not be appropriate.
@ -2492,7 +2398,7 @@ Mounting root from ufs:/dev/md0c
<para>The default size shown will create a partition that takes up the
rest of the slice. If you are using the partition sizes described
earlier then delete the existing figure using
earlier, then delete the existing figure using
<keycap>Backspace</keycap>, and then type in
<userinput>64M</userinput>, as shown in
<xref linkend="sysinstall-label-add2">. Then press
@ -2684,7 +2590,7 @@ Mounting root from ufs:/dev/md0c
<title>Choosing Your Installation Media</title>
<para>If Installing from a CDROM, use the arrow keys to highlight
<guimenuitem>Install from a FreeBSD CDROM</guimenuitem>. Ensure
<guimenuitem>Install from a FreeBSD CD/DVD</guimenuitem>. Ensure
that <guibutton>[ OK ]</guibutton> is highlighted, then press
<keycap>Enter</keycap> to proceed with the installation.</para>
@ -2817,7 +2723,8 @@ Mounting root from ufs:/dev/md0c
<keycap>Enter</keycap> to proceed.</para>
<para>The installation time will vary according to the distribution
chosen and installation media used. There will be a series of
chosen, installation media used, and the speed of the computer.
There will be a series of
messages displayed indicating the status.</para>
<para>The installation is complete when the following message is
@ -2914,7 +2821,7 @@ installation menus to try and retry whichever operations have failed.
<para>If you want to try the new Internet protocol (IPv6), choose
<guibutton>[ Yes ]</guibutton> and press <keycap>Enter</keycap>.
It will take several seconds for scanning RA servers.</para>
It will take several seconds to scan for RA servers.</para>
<screen> User Confirmation Requested
Do you want to try DHCP configuration of the interface?
@ -3540,7 +3447,7 @@ To change any of these settings later, edit /etc/rc.conf
<sect2 id="mouse">
<title>Mouse Settings</title>
<para>This option will allow you to cut and past text in the
<para>This option will allow you to cut and paste text in the
console and user programs with a 3-button mouse. If using a 2-button
mouse, refer to manual page, &man.moused.8;, after installation for
details on emulating the 3-button style. This example depicts a
@ -3701,7 +3608,7 @@ To change any of these settings later, edit /etc/rc.conf
[ Press enter to continue ]</screen>
<para>The indicates that the mouse daemon previously configured has been
<para>This indicates that the mouse daemon previously configured has been
detected. Press <keycap>Enter</keycap> to continue.</para>
<screen> Press [Enter] to switch to graphics mode.
@ -3830,8 +3737,8 @@ To change any of these settings later, edit /etc/rc.conf
<step>
<title><guimenuitem>Other</guimenuitem></title>
<para>There default settings are reasonable values so you
probably won't need to change anything here.</para>
<para>The default settings are reasonable values, so you
probably will not need to change anything here.</para>
<para>The default setting which allows the server to be killed
with the hotkey sequence <keycombo action='simul'>
@ -3868,14 +3775,15 @@ when you've finished.</screen>
<para>After selecting <guibutton>Okay</guibutton>, some messages
will briefly appear advising to wait and attempting to start
the x-server. This process takes a few moments, so be
the X-server. This process takes a few moments, so be
patient.</para>
<para>The screen will go blank for a short period of time and
then a screen will appear with the message
<quote>Congratulations, you've got a running server!</quote></para>
<para>If nothing appears or is distorted, kill the x-server using
<para>If nothing appears or the display is distorted,
kill the X-server using
<keycombo action='simul'>
<keycap>Ctrl</keycap>
<keycap>Alt</keycap>
@ -3894,11 +3802,11 @@ when you've finished.</screen>
damage your equipment. Heed them. If in doubt, do not do
it. Instead, use the monitor controls to adjust the display for
x-windows. There may be some display differences when switching
back to text mode, but it is better than damaging equipment. The
back to text mode, but it is better than damaging equipment.
<application>xvidtune</application> can be ran later using
<command>/stand/sysinstall</command>.</para>
<para>Read the <application>xvidtune</application> before making
<para>Read the &man.xvidtune.1; man page before making
any adjustments.</para>
</step>
@ -4219,7 +4127,7 @@ when you've finished.</screen>
</sect2>
<sect2 id="rootpass">
<title>Set Root Password</title>
<title>Set <username>root</username> Password</title>
<screen> Message
Now you must set the system manager's password.
@ -4429,6 +4337,8 @@ Additional ABI support: linux.
Local package initilization:.
Additional TCP options:.
FreeBSD/i386 (k6-2.weeble.com) (ttyv0)
login: rpratt
Password:</screen>