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

Made <indexterm>'s more specific by adding <filename>, <command>,

Browse source 
and <application> entities.

Submitted by:	Valentino Vaschetto <valentino.vaschetto@windriver.com>
Reviewed by:	murray
This commit is contained in:
Chern Lee 2001-07-19 01:11:52 +00:00
parent 9bb625166b
commit 4df284c246
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=9960
8 changed files with 279 additions and 103 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
en_US.ISO8859-1/articles/contributing/article.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/contrib/chapter.sgml,v 1.452 2001/07/15 19:57:41 tobez Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/contrib/chapter.sgml,v 1.453 2001/07/17 01:09:39 mike Exp $
-->
<chapter id="contrib">
@ -501,7 +501,9 @@
command, with the <quote>context diff</quote> form
being preferred. For example:</para>
<indexterm><primary>diff</primary></indexterm>
<indexterm>
<primary><command>diff</command></primary>
</indexterm>
<para>
<screen>&prompt.user; <userinput>diff -c oldfile newfile</userinput></screen>
@ -523,7 +525,9 @@
address it immediately, but it will remain in the pr database until we
do.</para>
<indexterm><primary>uuencode</primary></indexterm>
<indexterm>
<primary><command>uuencode</command></primary>
</indexterm>
<para>If you feel it appropriate (e.g. you have added, deleted, or
renamed files), bundle your changes into a <command>tar</command> file
and run the &man.uuencode.1; program on it. Shar archives are also

52
en_US.ISO8859-1/books/handbook/backups/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/backups/chapter.sgml,v 1.33 2001/06/26 15:40:08 phantom Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/backups/chapter.sgml,v 1.34 2001/06/26 20:10:23 murray Exp $
-->
<chapter id="backups">
@ -246,8 +246,8 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
<primary>backup software</primary>
<secondary>dump / restore</secondary>
</indexterm>
<indexterm><primary>dump</primary></indexterm>
<indexterm><primary>restore</primary></indexterm>
<indexterm><primary><command>dump</command></primary></indexterm>
<indexterm><primary><command>restore</command></primary></indexterm>
<para>&man.dump.8; and &man.restore.8; are the traditional Unix backup
programs. They operate on the drive as a collection of disk blocks,
@ -264,7 +264,7 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
These defaults must be overridden on the command line to utilize the
capacity of current tape drives.</para>
<indexterm><primary>rhosts</primary></indexterm>
<indexterm><primary><filename>rhosts</filename></primary></indexterm>
<para>&man.rdump.8; and &man.rrestore.8; backup data across the network
to a tape drive attached to another computer. Both programs rely upon
&man.rcmd.3; and &man.ruserok.3; to access the remote tape drive.
@ -283,7 +283,7 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
<title>Tar</title>
<indexterm>
<primary>backup software</primary>
<secondary>tar</secondary>
<secondary><command>tar</command></secondary>
</indexterm>
<para>&man.tar.1; also dates back to Version 6 of ATT Unix (circa 1975).
@ -293,7 +293,7 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
&man.tar.1; does not require the unusual command pipeline that
&man.cpio.1; uses.</para>
<indexterm><primary>tar</primary></indexterm>
<indexterm><primary><command>tar</command></primary></indexterm>
<para>Most versions of &man.tar.1; do not support backups across the
network. The GNU version of &man.tar.1;, which FreeBSD utilizes,
supports remote devices using the same syntax as &man.rdump.8;. To
@ -313,7 +313,7 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
<title>Cpio</title>
<indexterm>
<primary>backup software</primary>
<secondary>cpio</secondary>
<secondary><command>cpio</command></secondary>
</indexterm>
<para>&man.cpio.1; is the original Unix file interchange tape program
@ -323,7 +323,7 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
&man.cpio.1; and excellent choice for installation media.
&man.cpio.1; does not know how to walk the directory tree and a list
of files must be provided through <filename>stdin</filename>.</para>
<indexterm><primary>cpio</primary></indexterm>
<indexterm><primary><command>cpio</command></primary></indexterm>
<para>&man.cpio.1; does not support backups across the network. You can
use a pipeline and &man.rsh.1; to send the data to a remote tape
@ -346,9 +346,9 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
<title>Pax</title>
<indexterm>
<primary>backup software</primary>
<secondary>pax</secondary>
<secondary><command>pax</command></secondary>
</indexterm>
<indexterm><primary>pax</primary></indexterm>
<indexterm><primary><command>pax</command></primary></indexterm>
<indexterm><primary>POSIX</primary></indexterm>
<indexterm><primary>IEEE</primary></indexterm>
@ -365,9 +365,9 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
<title>Amanda</title>
<indexterm>
<primary>backup software</primary>
<secondary>amanda</secondary>
<secondary><command>amanda</command></secondary>
</indexterm>
<indexterm><primary>amanda</primary></indexterm>
<indexterm><primary><command>amanda</command></primary></indexterm>
<para><ulink url="/ports/misc.html#amanda-2.4.0">Amanda</ulink>
(Advanced Maryland Network Disk Archiver) is a client/server backup
@ -416,7 +416,9 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
<sect2>
<title>Which Backup Program is Best?</title>
<indexterm><primary>LISA</primary></indexterm>
<indexterm>
<primary>LISA</primary>
</indexterm>
<para>&man.dump.8; <emphasis>Period.</emphasis> Elizabeth D. Zwicky
torture tested all the backup programs discussed here. The clear
@ -442,7 +444,9 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
<para>There are only four steps that you need to perform in
preparation for any disaster that may occur.</para>
<indexterm><primary>disklabel</primary></indexterm>
<indexterm>
<primary><command>disklabel</command></primary>
</indexterm>
<para>First, print the disklabel from each of your disks
(<command>e.g. disklabel da0 | lpr</command>), your filesystem table
@ -670,10 +674,16 @@ echo "The floppy has been unmounted and is now ready."]]></programlisting>
<para>Recover each filesystem separately.</para>
<indexterm><primary>mount</primary></indexterm>
<indexterm>
<primary><command>mount</command></primary>
</indexterm>
<indexterm><primary>root partition</primary></indexterm>
<indexterm><primary>disklabel</primary></indexterm>
<indexterm><primary>newfs</primary></indexterm>
<indexterm>
<primary><command>disklabel</command></primary>
</indexterm>
<indexterm>
<primary><command>newfs</command></primary>
</indexterm>
<para>Try to &man.mount.8; (e.g. <command>mount /dev/da0a
/mnt</command>) the root partition of your first disk. If the
disklabel was damaged, use &man.disklabel.8; to re-partition and
@ -764,8 +774,12 @@ echo "The floppy has been unmounted and is now ready."]]></programlisting>
<sect2 id="floppies-compress">
<title>Can I compress my backups?</title>
<indexterm><primary>tar</primary></indexterm>
<indexterm><primary>gzip</primary></indexterm>
<indexterm>
<primary><command>tar</command></primary>
</indexterm>
<indexterm>
<primary><command>gzip</command></primary>
</indexterm>
<indexterm><primary>compression</primary></indexterm>
<para>Unfortunately, &man.tar.1; will not allow the

30
en_US.ISO8859-1/books/handbook/basics/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/basics/chapter.sgml,v 1.28 2001/07/17 00:11:18 chern Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/basics/chapter.sgml,v 1.29 2001/07/17 02:31:55 murray Exp $
-->
<chapter id="basics">
@ -115,7 +115,9 @@
</tbody>
</tgroup>
</informaltable>
<indexterm><primary>ls</primary></indexterm>
<indexterm>
<primary><command>ls</command></primary>
</indexterm>
<indexterm><primary>directories</primary></indexterm>
<para>For the long directory listing by <command>ls -l</command>, a
@ -407,7 +409,9 @@
with a text editor. FreeBSD comes with a few as part of the base
system, and many more are available in the ports collection.</para>
<indexterm><primary>ee</primary></indexterm>
<indexterm>
<primary><command>ee</command></primary>
</indexterm>
<para>The easiest and simplest editor to learn is an editor called
<application>ee</application>, which stands for easy editor. To
start <application>ee</application>, one would type at the command
@ -423,24 +427,28 @@
editor. The editor will prompt you to save any changes if the file
has been modified.</para>
<indexterm><primary>vi</primary></indexterm>
<indexterm>
<primary>editors</primary>
<secondary>vi</secondary>
<primary><command>vi</command></primary>
</indexterm>
<indexterm><primary>emacs</primary></indexterm>
<indexterm>
<primary>editors</primary>
<secondary>emacs</secondary>
<secondary><command>vi</command></secondary>
</indexterm>
<indexterm>
<primary><command>emacs</command></primary>
</indexterm>
<indexterm>
<primary>editors</primary>
<secondary><command>emacs</command></secondary>
</indexterm>
<para>FreeBSD also comes with more powerful text editors such as
<application>vi</application> as part of the base system, and
<application>emacs</application> and <application>vim</application>
<command>vi</command> as part of the base system, and
<command>emacs</command> and <command>vim</command>
as part of the FreeBSD ports collection. These editors offer much
more functionality and power at the expense of being a little more
complicated to learn. However if you plan on doing a lot of text
editing, learning a more powerful editor such as
<application>vim</application> or <application>emacs</application>
<command>vim</command> or <command>emacs</command>
will save you much more time in the long run.</para>
</sect1>

16
en_US.ISO8859-1/books/handbook/boot/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/boot/chapter.sgml,v 1.13 2001/07/06 13:03:00 dd Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/boot/chapter.sgml,v 1.14 2001/07/17 20:51:52 chern Exp $
-->
<chapter id="boot">
@ -160,7 +160,7 @@ boot:</screen>
the interpreter is started, and the easy-to-use commands are
explained to it.</para>
<indexterm><primary>loader</primary></indexterm>
<indexterm><primary>loader configuration</primary</indexterm>
<indexterm><primary>loader configuration</primary></indexterm>
<para>loader will then read
<filename>/boot/loader.rc</filename>, which by default reads
@ -340,7 +340,9 @@ boot:</screen>
<listitem>
<para>To unload your usual kernel and modules, and then
load just your old (or another) kernel:</para>
<indexterm><primary>kernel.old</primary></indexterm>
<indexterm>
<primary><filename>kernel.old</filename></primary>
</indexterm>
<screen><userinput>unload</userinput>
<userinput>load <replaceable>kernel.old</replaceable></userinput></screen>
@ -453,7 +455,9 @@ boot:</screen>
</sect1>
<sect1 id="boot-init">
<indexterm><primary>init</primary></indexterm>
<indexterm>
<primary><command>init</command></primary>
</indexterm>
<title>Init: Process Control Initialization</title>
<para>Once the kernel has finished booting, it passes control to
@ -552,7 +556,9 @@ console none unknown off insecure</programlisting>
<sect1 id="boot-shutdown">
<title>Shutdown Sequence</title>
<indexterm><primary>shutdown</primary></indexterm>
<indexterm>
<primary><command>shutdown</command></primary>
</indexterm>
<para>Upon controlled shutdown, via <command>shutdown</command>,
<command>init</command> will attempt to run the script

14
en_US.ISO8859-1/books/handbook/config/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/config/chapter.sgml,v 1.4 2001/07/16 20:49:02 nik Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/config/chapter.sgml,v 1.5 2001/07/17 00:11:18 chern Exp $
-->
<chapter id="config-tuning">
@ -34,9 +34,15 @@
<title>Partition layout</title>
<indexterm><primary>Partition layout</primary></indexterm>
<indexterm><primary>/etc</primary></indexterm>
<indexterm><primary>/var</primary></indexterm>
<indexterm><primary>/usr</primary></indexterm>
<indexterm>
<primary><filename>/etc</filename></primary>
</indexterm>
<indexterm>
<primary><filename>/var</filename></primary>
</indexterm>
<indexterm>
<primary><filename>/usr</filename></primary>
</indexterm>
<sect3>
<title>Base Partitions</title>

10
en_US.ISO8859-1/books/handbook/contrib/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/contrib/chapter.sgml,v 1.452 2001/07/15 19:57:41 tobez Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/contrib/chapter.sgml,v 1.453 2001/07/17 01:09:39 mike Exp $
-->
<chapter id="contrib">
@ -501,7 +501,9 @@
command, with the <quote>context diff</quote> form
being preferred. For example:</para>
<indexterm><primary>diff</primary></indexterm>
<indexterm>
<primary><command>diff</command></primary>
</indexterm>
<para>
<screen>&prompt.user; <userinput>diff -c oldfile newfile</userinput></screen>
@ -523,7 +525,9 @@
address it immediately, but it will remain in the pr database until we
do.</para>
<indexterm><primary>uuencode</primary></indexterm>
<indexterm>
<primary><command>uuencode</command></primary>
</indexterm>
<para>If you feel it appropriate (e.g. you have added, deleted, or
renamed files), bundle your changes into a <command>tar</command> file
and run the &man.uuencode.1; program on it. Shar archives are also

116
en_US.ISO8859-1/books/handbook/disks/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/disks/chapter.sgml,v 1.36 2001/07/14 23:40:28 murray Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/disks/chapter.sgml,v 1.37 2001/07/16 15:02:50 nik Exp $
-->
<chapter id="disks">
@ -288,7 +288,10 @@
<sect2 id="disks-mount">
<title>The mount Command</title>
<indexterm><primary>filesystems</primary><secondary>mounting</secondary></indexterm>
<indexterm>
<primary>filesystems</primary>
<secondary>mounting</secondary>
</indexterm>
<para>The &man.mount.8; command is what is ultimately used to
mount filesystems.</para>
@ -414,7 +417,10 @@
<sect2 id="disks-umount">
<title>The umount Command</title>
<indexterm><primary>filesystems</primary><secondary>unmounting</secondary></indexterm>
<indexterm>
<primary>filesystems</primary>
<secondary>unmounting</secondary>
</indexterm>
<para>The umount command takes, as a parameter, one of a
mountpoint, a device name, or the <option>-a</option> or
@ -433,7 +439,10 @@
<sect1 id="disks-adding">
<title>Adding Disks</title>
<indexterm><primary>disks</primary><secondary>adding</secondary></indexterm>
<indexterm>
<primary>disks</primary>
<secondary>adding</secondary>
</indexterm>
<para><emphasis>Originally contributed by &a.obrien; 26 April
1998</emphasis></para>
@ -455,7 +464,9 @@
<indexterm><primary>partitions</primary></indexterm>
<indexterm><primary>slices</primary></indexterm>
<indexterm><primary>fdisk</primary></indexterm>
<indexterm>
<primary><command>fdisk</command></primary>
</indexterm>
<para>Because FreeBSD runs on IBM-PC compatible computers, it must
take into account the PC BIOS partitions. These are different
@ -480,7 +491,10 @@
<sect2>
<title>Using &man.sysinstall.8;</title>
<indexterm><primary>sysinstall</primary><secondary>adding disks</secondary></indexterm>
<indexterm>
<primary><application>sysinstall</application></primary>
<secondary>adding disks</secondary>
</indexterm>
<para>You may use <command>/stand/sysinstall</command> to
partition and label a new disk using its easy to use menus.
@ -603,7 +617,10 @@
<sect1 id="disks-virtual">
<title>Virtual Disks: Network, Memory, and File-Based Filesystems</title>
<indexterm><primary>virtual disks</primary></indexterm>
<indexterm><primary>disks</primary><secondary>virtual</secondary></indexterm>
<indexterm>
<primary>disks</primary>
<secondary>virtual</secondary>
</indexterm>
<para>Aside from the disks you physically insert into your computer:
floppies, CDs, hard drives, and so forth; other forms of disks
@ -612,7 +629,10 @@
<indexterm><primary>NFS</primary></indexterm>
<indexterm><primary>Coda</primary></indexterm>
<indexterm><primary>disks</primary><secondary>memory</secondary></indexterm>
<indexterm>
<primary>disks</primary>
<secondary>memory</secondary>
</indexterm>
<para>These include network filesystems such as the <link
linkend="nfs">Network Filesystem</link> and Coda, memory-based
filesystems such as <link linkend="disks-md">md</link> and
@ -621,7 +641,10 @@
<sect2 id="disks-vnconfig">
<title>vnconfig: file-backed filesystem</title>
<indexterm><primary>disks</primary><secondary>file-backed</secondary></indexterm>
<indexterm>
<primary>disks</primary>
<secondary>file-backed</secondary>
</indexterm>
<para>&man.vnconfig.8; configures and enables vnode pseudo disk
devices. A <firstterm>vnode</firstterm> is a representation
@ -665,7 +688,10 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
<sect2 id="disks-md">
<title>md: Memory Filesystem</title>
<indexterm><primary>disks</primary><secondary>memory</secondary></indexterm>
<indexterm>
<primary>disks</primary>
<secondary>memory filesystem</secondary>
</indexterm>
<para>md is a simple, efficient means to do memory
filesystems.</para>
@ -689,8 +715,10 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
<sect1 id="quotas">
<title>Disk Quotas</title>
<indexterm><primary>accounting</primary><secondary>disk
space</secondary></indexterm>
<indexterm>
<primary>accounting</primary>
<secondary>disk space</secondary>
</indexterm>
<indexterm><primary>disk quotas</primary></indexterm>
<para>Quotas are an optional feature of the operating system that
@ -723,7 +751,10 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
line:</para>
<programlisting>enable_quotas=<quote>YES</quote></programlisting>
<indexterm><primary>disk quotas</primary><secondary>checking</secondary></indexterm>
<indexterm>
<primary>disk quotas</primary>
<secondary>checking</secondary>
</indexterm>
<para>For finer control over your quota startup, there is an
additional configuration variable available. Normally on bootup,
the quota integrity of each file system is checked by the
@ -787,7 +818,10 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
<sect2>
<title>Setting Quota Limits</title>
<indexterm><primary>disk quotas</primary><secondary>limits</secondary></indexterm>
<indexterm>
<primary>disk quotas</primary>
<secondary>limits</secondary>
</indexterm>
<para>Once you have configured your system to enable quotas, verify
that they really are enabled. An easy way to do this is to
@ -875,7 +909,10 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
<sect2>
<title>Checking Quota Limits and Disk Usage</title>
<indexterm><primary>disk quotas</primary><secondary>checking</secondary></indexterm>
<indexterm>
<primary>disk quotas</primary>
<secondary>checking</secondary>
</indexterm>
<para>You can use either the <command>quota</command> or the
<command>repquota</command> commands to check quota limits and
@ -934,7 +971,10 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
<sect1 id="creating-cds">
<title>Creating CDs</title>
<indexterm><primary>CDROMs</primary><secondary>creating</secondary></indexterm>
<indexterm>
<primary>CDROMs</primary>
<secondary>creating</secondary>
</indexterm>
<para><emphasis>Contributed by Mike Meyer
<email>mwm@mired.org</email>, April 2001.</emphasis></para>
@ -956,21 +996,29 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
CD.</para>
<indexterm><primary>ISO 9660</primary></indexterm>
<indexterm><primary>filesystems</primary><secondary>ISO-9660</secondary></indexterm>
<indexterm>
<primary>filesystems</primary>
<secondary>ISO-9660</secondary>
</indexterm>
<para>The ISO 9660 file system was designed to deal with these
differences. It unfortunately codifies file system limits that were
common then. Fortunately, it provides an extension mechanism that
allows properly written CDs to exceed those limits while still
working with systems that do not support those extensions.</para>
<indexterm><primary>mkisofs</primary></indexterm>
<indexterm>
<primary><command>mkisofs</command></primary>
</indexterm>
<para>The <command><link linkend="mkisofs">mkisofs</link></command>
program is used to produce a data file containing an ISO 9660 file
system. It has options that support various extensions, and is
described below. You can install it with the <filename>
/usr/ports/sysutils/mkisofs</filename> port.</para>
<indexterm><primary>CD burner</primary><secondary>ATAPI</secondary></indexterm>
<indexterm>
<primary>CD burner</primary>
<secondary>ATAPI</secondary>
</indexterm>
<para>Which tool to use to burn the CD depends on whether your CD burner
is ATAPI or something else. ATAPI CD burners use the <command><link
linkend="burncd">burncd</link></command> program that is part of
@ -988,7 +1036,10 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
<screen>&prompt.root; <userinput>mkisofs <option>-o</option> <replaceable>imagefile.iso</replaceable> <replaceable>/path/to/tree</replaceable></userinput></screen>
<indexterm><primary>filesystems</primary><secondary>ISO-9660</secondary></indexterm>
<indexterm>
<primary>filesystems</primary>
<secondary>ISO-9660</secondary>
</indexterm>
<para>This command will create an <replaceable>imagefile</replaceable>
containing an ISO 9660 file system that is a copy of the tree at
<replaceable>/path/to/tree</replaceable>. In the process, it will
@ -998,8 +1049,14 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
for details of this process, and options that can be used to
control it.</para>
<indexterm><primary>filesystems</primary><secondary>HFS</secondary></indexterm>
<indexterm><primary>filesystems</primary><secondary>Joliet</secondary></indexterm>
<indexterm>
<primary>filesystems</primary>
<secondary>HFS</secondary>
</indexterm>
<indexterm>
<primary>filesystems</primary>
<secondary>Joliet</secondary>
</indexterm>
<para>A number of options are available to overcome those
restrictions. In particular, <option>-R</option> enables the
Rock Ridge extensions common to Unix systems, <option>-J</option>
@ -1015,7 +1072,10 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
from, though it may violate the ISO 9660 standard in a number of
ways.</para>
<indexterm><primary>CDROMs</primary><secondary>creating bootable</secondary></indexterm>
<indexterm>
<primary>CDROMs</primary>
<secondary>creating bootable</secondary>
</indexterm>
<para>The last option of general use is <option>-b</option>. This is
used to specify the location of the boot image for use in producing an
<quote>El Torito</quote> bootable CD. This option takes an
@ -1045,7 +1105,10 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
<sect2 id="burncd">
<title>burncd</title>
<indexterm><primary>CDROMs</primary><secondary>burning</secondary></indexterm>
<indexterm>
<primary>CDROMs</primary>
<secondary>burning</secondary>
</indexterm>
<para>If you have an ATAPI CD burner, you can use the
<command>burncd</command> command to burn an ISO image onto a
CD. <command>burncd</command> is part of the base system, installed
@ -1086,7 +1149,10 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
the <option>dev</option> to use. To find the proper setting, use
the <option>-scanbus</option> flag of <command>cdrecord</command>,
which might produce results like this:</para>
<indexterm><primary>CDROMs</primary><secondary>burning</secondary></indexterm>
<indexterm>
<primary>CDROMs</primary>
<secondary>burning</secondary>
</indexterm>
<screen>&prompt.root; <userinput>cdrecord <option>-scanbus</option></userinput>
Cdrecord 1.9 (i386-unknown-freebsd4.2) Copyright (C) 1995-2000 J&ouml;rg Schilling
Using libscg version 'schily-0.1'

134
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.75 2001/07/17 02:31:55 murray Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/install/chapter.sgml,v 1.76 2001/07/17 22:20:48 chern Exp $
-->
<chapter id="install">
@ -39,9 +39,11 @@
can also provide clues early-on in the process to potential problems
you may come across later.</para>
<indexterm><primary>installation</primary>
<indexterm>
<primary>installation</primary>
<secondary>network</secondary>
<tertiary>anonymous FTP</tertiary></indexterm>
<tertiary>anonymous FTP</tertiary>
</indexterm>
<para>If you plan to install FreeBSD via anonymous FTP, the only
things you will need are the <link
linkend="install-floppies">installation floppies</link>. The
@ -81,10 +83,14 @@
<sect3 id="install-floppies">
<title>Creating the Installation Floppies</title>
<indexterm><primary>installation</primary>
<secondary>boot floppies</secondary></indexterm>
<indexterm><primary>installation</primary>
<secondary>CDROM</secondary></indexterm>
<indexterm>
<primary>installation</primary>
<secondary>boot floppies</secondary>
</indexterm>
<indexterm>
<primary>installation</primary>
<secondary>CDROM</secondary>
</indexterm>
<para>You may need to prepare some floppy disks. These disks will
be used to boot your computer in to the FreeBSD install process.
This step is not necessary <emphasis>if</emphasis> you are
@ -267,7 +273,11 @@
or not you actually use it as the installation media).</para>
</note>
<indexterm><primary>installation</primary><secondary>network</secondary><tertiary>FTP</tertiary></indexterm>
<indexterm>
<primary>installation</primary>
<secondary>network</secondary>
<tertiary>FTP</tertiary>
</indexterm>
<para>Finally, if you would like people to be able to FTP install
FreeBSD directly from the CDROM in your machine, you will find
it quite easy. After the machine is fully installed, you simply
@ -291,7 +301,10 @@
<sect3>
<title>Before installing from Floppies</title>
<indexterm><primary>installation</primary><secondary>floppies</secondary></indexterm>
<indexterm>
<primary>installation</primary>
<secondary>floppies</secondary>
</indexterm>
<para>If you must install from floppy disk (which we suggest you
do <emphasis>NOT</emphasis> do), either due to unsupported
hardware or simply because you insist on doing things the hard
@ -350,7 +363,10 @@
<sect3 id="install-msdos">
<title>Before Installing from MS-DOS</title>
<indexterm><primary>installation</primary><secondary>from MS-DOS</secondary></indexterm>
<indexterm>
<primary>installation</primary>
<secondary>from MS-DOS</secondary>
</indexterm>
<para>To prepare for an installation from an MS-DOS partition,
copy the files from the distribution into a directory named,
for example, <filename>c:\FreeBSD</filename>. The directory
@ -386,8 +402,10 @@
<sect3>
<title>Before Installing from QIC/SCSI Tape</title>
<indexterm><primary>installation</primary><secondary>from
QIC/SCSI Tape</secondary></indexterm>
<indexterm>
<primary>installation</primary>
<secondary>from QIC/SCSI Tape</secondary>
</indexterm>
<para>Installing from tape is probably the easiest method, short
of an online FTP install or CDROM install. The installation
program expects the files to be simply tarred onto the tape, so
@ -417,10 +435,21 @@
<sect3>
<title>Before Installing over a Network</title>
<indexterm><primary>installation</primary><secondary>network</secondary><tertiary>serial
(SLIP or PPP)</tertiary></indexterm>
<indexterm><primary>installation</primary><secondary>network</secondary><tertiary>parallel (PLIP)</tertiary></indexterm>
<indexterm><primary>installation</primary><secondary>network</secondary><tertiary>Ethernet</tertiary></indexterm>
<indexterm>
<primary>installation</primary>
<secondary>network</secondary>
<tertiary>serial (SLIP or PPP)</tertiary>
</indexterm>
<indexterm>
<primary>installation</primary>
<secondary>network</secondary>
<tertiary>parallel (PLIP)</tertiary>
</indexterm>
<indexterm>
<primary>installation</primary>
<secondary>network</secondary>
<tertiary>Ethernet</tertiary>
</indexterm>
<para>There are three types of network installations you can do.
Serial port (SLIP or PPP), Parallel port (PLIP (laplink cable)),
or Ethernet (a standard Ethernet controller (includes some
@ -489,7 +518,11 @@
<sect4>
<title>Before Installing via NFS</title>
<indexterm><primary>installation</primary><secondary>network</secondary><tertiary>NFS</tertiary></indexterm>
<indexterm>
<primary>installation</primary>
<secondary>network</secondary>
<tertiary>NFS</tertiary>
</indexterm>
<para>The NFS installation is fairly straight-forward. Simply
copy the FreeBSD distribution files you want onto a server
somewhere and then point the NFS media selection at it.</para>
@ -523,7 +556,11 @@
<sect4>
<title>Before Installing via FTP</title>
<indexterm><primary>installation</primary><secondary>network</secondary><tertiary>FTP</tertiary></indexterm>
<indexterm>
<primary>installation</primary>
<secondary>network</secondary>
<tertiary>FTP</tertiary>
</indexterm>
<para>FTP installation may be done from any FreeBSD mirror site
containing a reasonably up-to-date version of FreeBSD. A full
list of FTP mirrors located all over the world is provided
@ -560,7 +597,10 @@
<term>FTP Passive</term>
<listitem>
<indexterm><primary>FTP</primary><secondary>Passive mode</secondary></indexterm>
<indexterm>
<primary>FTP</primary>
<secondary>Passive mode</secondary>
</indexterm>
<para>This option instructs FreeBSD to use
<quote>Passive</quote> mode for all FTP operations.
This allows the user to pass through firewalls
@ -573,8 +613,10 @@
<term>FTP via a HTTP proxy</term>
<listitem>
<indexterm><primary>FTP</primary><secondary>via a HTTP
proxy</secondary></indexterm>
<indexterm>
<primary>FTP</primary>
<secondary>via a HTTP proxy</secondary>
</indexterm>
<para>This option instructs FreeBSD to use the HTTP
protocol (like a web browser) to connect to a proxy
for all FTP operations. The proxy will translate
@ -643,7 +685,9 @@
the <ulink url="../FAQ/hardware.html">Hardware Guide</ulink> for a
list of possible solutions.</para>
<indexterm><primary>sysinstall</primary></indexterm>
<indexterm>
<primary><application>sysinstall</application></primary>
</indexterm>
<para>The FreeBSD boot floppies contain all of the online
documentation you should need to be able to navigate through an
installation. If it does not, please let us know what you found
@ -683,9 +727,18 @@
you may have.</para>
</listitem>
<indexterm><primary>installation</primary><secondary>standard</secondary></indexterm>
<indexterm><primary>installation</primary><secondary>express</secondary></indexterm>
<indexterm><primary>installation</primary><secondary>custom</secondary></indexterm>
<indexterm>
<primary>installation</primary>
<secondary>standard</secondary>
</indexterm>
<indexterm>
<primary>installation</primary>
<secondary>express</secondary>
</indexterm>
<indexterm>
<primary>installation</primary>
<secondary>custom</secondary>
</indexterm>
<listitem>
<para>Select a Standard, Express, or Custom install, depending on
whether or not you would like the installation to help you
@ -1698,7 +1751,10 @@
<sect1 id="install-trouble">
<title>Troubleshooting</title>
<indexterm><primary>installation</primary><secondary>troubleshooting</secondary></indexterm>
<indexterm>
<primary>installation</primary>
<secondary>troubleshooting</secondary>
</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
@ -1789,7 +1845,9 @@
CDROM or various FreeBSD FTP sites to be quite
useful.</para>
<indexterm><primary>FIPS</primary></indexterm>
<indexterm>
<primary><command>FIPS</command></primary>
</indexterm>
<para>FIPS allows you to split an existing MS-DOS partition
into two pieces, preserving the original partition and
allowing you to install onto the second free piece. You
@ -1803,7 +1861,9 @@
for an estimate of how much free space you will need for the
kind of installation you want.</para>
<indexterm><primary>Partition Magic</primary></indexterm>
<indexterm>
<primary><application>Partition Magic</application></primary>
</indexterm>
<para>There is also a <emphasis>very</emphasis> useful
product from <ulink
url="http://www.powerquest.com/">PowerQuest</ulink>
@ -1879,8 +1939,10 @@
<title>Installing FreeBSD on a system without a monitor or
keyboard</title>
<indexterm><primary>installation</primary><secondary>headless
(serial console)</secondary></indexterm>
<indexterm>
<primary>installation</primary>
<secondary>headless (serial console)</secondary>
</indexterm>
<indexterm><primary>serial console</primary></indexterm>
<para>This type of installation is called a "headless install",
because the machine that you are trying to install FreeBSD on
@ -1923,7 +1985,9 @@
files. Instead, you must use specific tools to write the
images directly to the disk.</para>
<indexterm><primary>fdimage</primary></indexterm>
<indexterm>
<primary><command>fdimage</command></primary>
</indexterm>
<para>If you are creating the floppies on a computer running
DOS then we provide a tool to do this called
<command>fdimage</command>.</para>
@ -1968,7 +2032,9 @@
<para>Do not try to mount the floppy if it is write-protected</para>
</warning>
<indexterm><primary>mount</primary></indexterm>
<indexterm>
<primary><command>mount</command></primary>
</indexterm>
<para>If you were to boot into the floppies that you just
made, FreeBSD would boot into its normal install mode. We
want FreeBSD to boot into a serial console for our
@ -2025,7 +2091,9 @@
<step>
<title>Connecting to your headless machine</title>
<indexterm><primary>cu</primary></indexterm>
<indexterm>
<primary><command>cu</command></primary>
</indexterm>
<para>Now you have to connect to that machine with
&man.cu.1;:</para>