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

Add more devices to the sample inventory.

Browse source 
Be more accurate in explaining PC primary, extended, and logical partitions.
I'm learning more about this stuff than I ever wanted to.

Add a "collect your network configuration" section to the pre-installation
tasks.

Add a link to the errata information.

Note that the 'c' partition refers to the enclosing slice, not the whole
disk, as I have always thought for the past seven years.  Also note that
the 'd' partition is no longer special, but that lots of software,
including sysinstall, believes that it still is.  Update the ASCII art
disk layout diagram to reflect this, comment out the EPS version until I
can fix it.

Fix some typos.

Some of this is my own work, the rest is based on comments from
William Roth <RothW@SEC.GOV>, and Annelise Anderson
<andrsn@andrsn.stanford.edu>
This commit is contained in:
Nik Clayton 2001-08-28 23:33:07 +00:00
parent ff37f1f3bb
commit 84bd9dbf6c
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=10488
1 changed files with 169 additions and 75 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

244
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.98 2001/08/24 13:39:00 rpratt Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/install/chapter.sgml,v 1.99 2001/08/26 20:41:27 rpratt Exp $
-->
<chapter id="install">
@ -156,6 +156,26 @@
<entry></entry>
</row>
<row>
<entry>Network card</entry>
<entry>N/A</entry>
<entry>N/A</entry>
<entry>Intel 10/100</entry>
</row>
<row>
<entry>Modem</entry>
<entry>N/A</entry>
<entry>N/A</entry>
<entry>3Com 56K faxmodem, on COM1:</entry>
</row>
<row>
<entry>&hellip;</entry>
</row>
@ -186,27 +206,33 @@
systems then you need to have a rough understanding of how data is
laid out on the disk, and how this affects you.</para>
<para>A PC disk can be divided in to up to four discrete chunks. These
chunks are called <firstterm>partitions</firstterm>. One partition on
each disk will be the primary partition, the others are extended
partitions. A disk does not need to be configured with all four
partitions. You might only have one partition on your disk at the
moment, and that partition is taking up the whole space of the
disk. Each partition has a <firstterm>partition ID</firstterm>, which
is a number, used to identify the type of data on the partition.
FreeBSD partitions have the partition ID
<literal>165</literal>.</para>
<para>A PC disk can be divided in to discrete chunks. These chunks are
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
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 partiton has a <firstterm>partition ID</firstterm>, which is
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
partitions in a particular way. For example, DOS, and its
descendants, like Windows, assign each partition a <firstterm>drive
letter</firstterm>, starting with
descendants, like Windows, assign each primary and logical partition a
<firstterm>drive letter</firstterm>, starting with
<devicename>C:</devicename>.</para>
<para>FreeBSD keeps all your data in one partition, so you need to have
one partition available when you install FreeBSD. 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>FreeBSD must be installed in to 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
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
@ -217,7 +243,7 @@
may need to shrink one or more of your existing partitions
first.</para>
<para>A minimal installation of FreeBSD takes as little as 35MB of disk
<para>A minimal installation of FreeBSD takes as little as 100MB of disk
space. However, that is a <emphasis>very</emphasis> minimal install,
leaving almost no space for your own files. A more realistic minimum
is 250MB without a graphical environment, and 350MB or more if you
@ -281,6 +307,70 @@
</example>
</sect2>
<sect2>
<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
will be prompted for this information during the installation so that
FreeBSD can connect to the network to complete the install.</para>
<sect3>
<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
information:</para>
<orderedlist>
<listitem>
<para>IP address.</para>
</listitem>
<listitem>
<para>IP address of the default gateway.</para>
</listitem>
<listitem>
<para>Hostname.</para>
</listitem>
<listitem>
<para>DNS server IP addresses.</para>
</listitem>
</orderedlist>
<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>
</sect3>
<sect3>
<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
long time.</para>
<para>You will need to know:</para>
<orderedlist>
<listitem>
<para>The phone number to dial for your ISP.</para>
</listitem>
<listitem>
<para>The COM: port your modem is connected to.</para>
</listitem>
<listitem>
<para>The username and password for your ISP account.</para>
</listitem>
</orderedlist>
</sect3>
</sect2>
<sect2>
<title>Check for FreeBSD Errata</title>
@ -291,6 +381,10 @@
are noted in the FreeBSD Errata, posted on the FreeBSD 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>
<para>Information about all the releases, including the errata for each
release, can be found at
<ulink url="http://www.freebsd.org/releases/index.html">http://www.FreeBSD.org/releases/index.html</ulink>.</para>
</sect2>
<sect2 id="install-floppies">
@ -314,12 +408,14 @@
from 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
or DVD then you are probably preparing your own installation media
(e.g., FTP, or an MS-DOS partition), which must be prepared before you
install FreeBSD. This is a slightly more advanced, and infrequent
activity, and is documented in <xref
linkend="install-diff-media">.</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
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>
<procedure>
<step>
@ -338,6 +434,14 @@
<filename>mfsroot.flp</filename>, but check
<filename>README.TXT</filename> in the same directory to be
sure.</para>
<important>
<para>Your FTP program must use <emphasis>binary mode</emphasis>
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>
</important>
</step>
<step>
@ -601,8 +705,8 @@ Booting [kernel] in 9 seconds... _</screen>
<para>Unfortunately, the default IRQs and memory ports used by some
drivers clash. This is because some ISA devices are shipped with IRQs
or memory ports that clash. The defaults in FreeBSD's drivers are
deliberately set to mirror this so that, out of the box, as many
devices as possible will work.</para>
deliberately set to mirror the manufacturer's defaults, so that, out
of the box, as many devices as possible will work.</para>
<para>This is almost never an issue when running FreeBSD day-to-day.
Your computer will not normally contain two pieces of hardware that
@ -1351,20 +1455,22 @@ Mounting root from ufs:/dev/md0c
<row>
<entry><literal>c</literal></entry>
<entry>Normally the same size as the entire disk. This allows
utilities that need to work on the entire disk (for example, a
bad disk block scanner) to work on the <literal>c</literal>
partition. You would not normally create a filesystem on this
partition.</entry>
<entry>Normally the same size as the enclosing slice. This
allows utilities that need to work on the entire slice (for
example, a bad block scanner) to work on the
<literal>c</literal> partition. You would not normally create
a filesystem on this partition.</entry>
</row>
<row>
<entry><literal>d</literal></entry>
<entry>Normally the same size as the enclosing slice. This
allows utilities that must operate on the whole FreeBSD slice
to work on the <literal>d</literal> partition. You would not
normally create a filesystem on this partition.</entry>
<entry>Partition <literal>d</literal> used to have a special
meaning associated with it, although that is now gone. To
this day, some tools may operate oddly if told to work on
partition <literal>d</literal>, so
<application>Sysinstall</application> will not normally create
partition <literal>d</literal>.</entry>
</row>
</tbody>
</tgroup>
@ -1493,44 +1599,32 @@ Mounting root from ufs:/dev/md0c
hierarchy, and <literal>f</literal> for the
<filename>/usr</filename> directory hierarchy.</para>
<mediaobject>
<imageobject>
<imagedata fileref="install/disk-layout" format="EPS">
</imageobject>
<textobject>
<literallayout class="monospaced">.-----------------. --. --.
| | | |
| DOS / Windows | | | Partition c, no
: : > First slice, ad0s1 > filesystem, all
: : | | of disk, ad0s1c
| | | |
:=================: ==: | --.
| | | Partition a, mounted as / | |
| | > referred to as ad0s2a | |
| | | | |
:-----------------: ==: | |
| | | Partition b, used as swap | |
| | > referred to as ad0s2b | |
| | | | |
:-----------------: ==: | | Partition d, no
| | | Partition e, used as /var | > filesystem, all
| | > referred to as ad0s2e | | of FreeBSD slice,
| | | | | ad0s2d
:-----------------: ==: | |
| | | | |
: : | Partition f, used as /usr | |
: : > referred to as ad0s2f |
: : | | |
| | | | |
| | --' | |
`-----------------' --' --'</literallayout>
</textobject>
<textobject>
<phrase>Conceptual model of a disk</phrase>
</textobject>
</mediaobject>
<literallayout class="monospaced">.-----------------. --.
| | |
| DOS / Windows | |
: : > First slice, ad0s1
: : |
| | |
:=================: ==: --.
| | | Partition a, mounted as / |
| | > referred to as ad0s2a |
| | | |
:-----------------: ==: |
| | | Partition b, used as swap |
| | > referred to as ad0s2b |
| | | |
:-----------------: ==: | Partition c, no
| | | Partition e, used as /var > filesystem, all
| | > referred to as ad0s2e | of FreeBSD slice,
| | | | ad0s2c
:-----------------: ==: |
| | | |
: : | Partition f, used as /usr |
: : > referred to as ad0s2f |
: : | |
| | | |
| | --' |
`-----------------' --'</literallayout>
</example>
</sect2>
@ -1625,7 +1719,7 @@ Mounting root from ufs:/dev/md0c
<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
gives the, and their description and sub-type. This example shows two
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 FAT slice, which almost certainly appears
as <devicename>C:</devicename> in DOS / Windows, and an extended
@ -1653,7 +1747,7 @@ Mounting root from ufs:/dev/md0c
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 artefact of PC disk
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 then select the newly created FreeBSD slice using the arrow
keys, and press <keycap>S</keycap> to mark the slice as being