PERFORCE change 205476 for review
Rene Ladan
rene at FreeBSD.org
Tue Jan 31 17:10:48 UTC 2012
http://p4web.freebsd.org/@@205476?ac=10
Change 205476 by rene at rene_acer on 2012/01/31 17:09:47
IFC
Affected files ...
.. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml#36 integrate
.. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/boot/chapter.sgml#9 integrate
.. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/bsdinstall/chapter.sgml#10 integrate
.. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/config/chapter.sgml#19 integrate
.. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/filesystems/chapter.sgml#8 integrate
.. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/mac/chapter.sgml#10 integrate
.. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/security/chapter.sgml#21 integrate
.. //depot/projects/docproj_nl/en_US.ISO8859-1/books/porters-handbook/book.sgml#126 integrate
.. //depot/projects/docproj_nl/nl_NL.ISO8859-1/articles/contributing-ports/article.sgml#19 integrate
.. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/boot/chapter.sgml#11 integrate
.. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/security/chapter.sgml#28 integrate
.. //depot/projects/docproj_nl/share/mk/doc.common.mk#2 integrate
.. //depot/projects/docproj_nl/share/mk/doc.docbook.mk#3 integrate
.. //depot/projects/docproj_nl/share/mk/doc.html.mk#2 integrate
.. //depot/projects/docproj_nl/share/mk/doc.xml.mk#4 integrate
.. //depot/projects/docproj_nl/share/sgml/freebsd-html.dsl#9 integrate
.. //depot/projects/docproj_nl/share/sgml/mirrors.xml#33 integrate
.. //depot/projects/docproj_nl/www/en/developers.sgml#68 integrate
.. //depot/projects/docproj_nl/www/en/index.xsl#13 integrate
.. //depot/projects/docproj_nl/www/en/releng/index.sgml#47 integrate
.. //depot/projects/docproj_nl/www/nl/administration.sgml#38 integrate
.. //depot/projects/docproj_nl/www/share/mk/web.site.mk#6 integrate
.. //depot/projects/docproj_nl/www/share/sgml/common.ent#6 integrate
.. //depot/projects/docproj_nl/www/share/sgml/events2012.xml#4 integrate
.. //depot/projects/docproj_nl/www/share/sgml/header.ent#11 integrate
.. //depot/projects/docproj_nl/www/share/sgml/news.xml#129 integrate
Differences ...
==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml#36 (text+ko) ====
@@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
- $FreeBSD: doc/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml,v 1.444 2012/01/24 15:56:06 wblock Exp $
+ $FreeBSD: doc/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml,v 1.445 2012/01/31 05:11:07 wblock Exp $
-->
<chapter id="advanced-networking">
@@ -976,62 +976,60 @@
identifies the type of each network and the capabilities
of the stations operating there:</para>
- <variablelist>
- <varlistentry>
- <term><literal>E</literal></term>
+ <table frame="none" pgwide="0">
+ <title>Station Capability Codes</title>
- <listitem>
- <para>Extended Service Set (ESS). Indicates that the
- station is part of an infrastructure network (in
- contrast to an IBSS/ad-hoc network).</para>
- </listitem>
- </varlistentry>
+ <tgroup cols="2">
+ <thead>
+ <row>
+ <entry>Capability Code</entry>
+ <entry>Meaning</entry>
+ </row>
+ </thead>
- <varlistentry>
- <term><literal>I</literal></term>
+ <tbody>
+ <row>
+ <entry><literal>E</literal></entry>
+ <entry>Extended Service Set (ESS). Indicates that
+ the station is part of an infrastructure network
+ (in contrast to an IBSS/ad-hoc network).</entry>
+ </row>
- <listitem>
- <para>IBSS/ad-hoc network. Indicates that the station
- is part of an ad-hoc network (in contrast to an ESS
- network).</para>
- </listitem>
- </varlistentry>
+ <row>
+ <entry><literal>I</literal></entry>
+ <entry>IBSS/ad-hoc network. Indicates that the
+ station is part of an ad-hoc network (in contrast
+ to an ESS network).</entry>
+ </row>
- <varlistentry>
- <term><literal>P</literal></term>
+ <row>
+ <entry><literal>P</literal></entry>
+ <entry>Privacy. Data confidentiality is required
+ for all data frames exchanged within the BSS.
+ This means that this BSS requires the station to
+ use cryptographic means such as WEP, TKIP or
+ AES-CCMP to encrypt/decrypt data frames being
+ exchanged with others.</entry>
+ </row>
- <listitem>
- <para>Privacy. Data confidentiality is required for
- all data frames exchanged within the BSS. This means
- that this BSS requires the station to use
- cryptographic means such as WEP, TKIP or AES-CCMP to
- encrypt/decrypt data frames being exchanged with
- others.</para>
- </listitem>
- </varlistentry>
+ <row>
+ <entry><literal>S</literal></entry>
+ <entry>Short Preamble. Indicates that the network
+ is using short preambles (defined in 802.11b High
+ Rate/DSSS PHY, short preamble utilizes a 56 bit
+ sync field in contrast to a 128 bit field used in
+ long preamble mode).</entry>
+ </row>
- <varlistentry>
- <term><literal>S</literal></term>
-
- <listitem>
- <para>Short Preamble. Indicates that the network is
- using short preambles (defined in 802.11b High
- Rate/DSSS PHY, short preamble utilizes a 56 bit sync
- field in contrast to a 128 bit field used in long
- preamble mode).</para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><literal>s</literal></term>
-
- <listitem>
- <para>Short slot time. Indicates that the 802.11g
- network is using a short slot time because there are
- no legacy (802.11b) stations present.</para>
- </listitem>
- </varlistentry>
- </variablelist>
+ <row>
+ <entry><literal>s</literal></entry>
+ <entry>Short slot time. Indicates that the 802.11g
+ network is using a short slot time because there
+ are no legacy (802.11b) stations present.</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
<para>One can also display the current list of known
networks with:</para>
==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/boot/chapter.sgml#9 (text+ko) ====
@@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
- $FreeBSD: doc/en_US.ISO8859-1/books/handbook/boot/chapter.sgml,v 1.71 2010/12/01 20:37:03 rene Exp $
+ $FreeBSD: doc/en_US.ISO8859-1/books/handbook/boot/chapter.sgml,v 1.72 2012/01/29 02:33:32 wblock Exp $
-->
<chapter id="boot">
@@ -12,76 +12,80 @@
<indexterm><primary>booting</primary></indexterm>
<indexterm><primary>bootstrap</primary></indexterm>
- <para>The process of starting a computer and loading the operating system
- is referred to as <quote>the bootstrap process</quote>, or simply
- <quote>booting</quote>. FreeBSD's boot process provides a great deal of
- flexibility in customizing what happens when you start the system,
- allowing you to select from different operating systems installed on the
- same computer, or even different versions of the same operating system
- or installed kernel.</para>
+ <para>The process of starting a computer and loading the operating
+ system is referred to as <quote>the bootstrap process</quote>,
+ or simply <quote>booting</quote>. FreeBSD's boot process
+ provides a great deal of flexibility in customizing what happens
+ when you start the system, allowing you to select from different
+ operating systems installed on the same computer, or even
+ different versions of the same operating system or installed
+ kernel.</para>
- <para>This chapter details the configuration options you can set and how
- to customize the FreeBSD boot process. This includes everything that
- happens until the FreeBSD kernel has started, probed for devices, and
- started &man.init.8;. If you are not quite sure when this happens, it
- occurs when the text color changes from bright white to grey.</para>
+ <para>This chapter details the configuration options you can set
+ and how to customize the FreeBSD boot process. This includes
+ everything that happens until the FreeBSD kernel has started,
+ probed for devices, and started &man.init.8;. If you are not
+ quite sure when this happens, it occurs when the text color
+ changes from bright white to grey.</para>
<para>After reading this chapter, you will know:</para>
<itemizedlist>
<listitem>
- <para>What the components of the FreeBSD bootstrap system are, and how
- they interact.</para>
+ <para>What the components of the FreeBSD bootstrap system are,
+ and how they interact.</para>
</listitem>
<listitem>
- <para>The options you can give to the components in the FreeBSD
- bootstrap to control the boot process.</para>
+ <para>The options you can give to the components in the
+ FreeBSD bootstrap to control the boot process.</para>
</listitem>
-
+
<listitem>
- <para>The basics of &man.device.hints.5;.</para>
+ <para>The basics of &man.device.hints.5;.</para>
</listitem>
</itemizedlist>
<note>
<title>x86 Only</title>
- <para>This chapter only describes the boot process for FreeBSD running
- on Intel x86 systems.</para>
+ <para>This chapter only describes the boot process for FreeBSD
+ running on Intel x86 systems.</para>
</note>
</sect1>
<sect1 id="boot-introduction">
<title>The Booting Problem</title>
- <para>Turning on a computer and starting the operating system poses an
- interesting dilemma. By definition, the computer does not know how to
- do anything until the operating system is started. This includes
- running programs from the disk. So if the computer can not run a
- program from the disk without the operating system, and the operating
- system programs are on the disk, how is the operating system
- started?</para>
+ <para>Turning on a computer and starting the operating system
+ poses an interesting dilemma. By definition, the computer does
+ not know how to do anything until the operating system is
+ started. This includes running programs from the disk. So if
+ the computer can not run a program from the disk without the
+ operating system, and the operating system programs are on the
+ disk, how is the operating system started?</para>
- <para>This problem parallels one in the book <citetitle>The Adventures of
- Baron Munchausen</citetitle>. A character had fallen part way down a
- manhole, and pulled himself out by grabbing his bootstraps, and
- lifting. In the early days of computing the term
- <firstterm>bootstrap</firstterm> was applied to the mechanism used to
- load the operating system, which has become shortened to
- <quote>booting</quote>.</para>
+ <para>This problem parallels one in the book <citetitle>The
+ Adventures of Baron Munchausen</citetitle>. A character had
+ fallen part way down a manhole, and pulled himself out by
+ grabbing his bootstraps, and lifting. In the early days of
+ computing the term <firstterm>bootstrap</firstterm> was applied
+ to the mechanism used to load the operating system, which has
+ become shortened to <quote>booting</quote>.</para>
<indexterm><primary>BIOS</primary></indexterm>
- <indexterm><primary>Basic Input/Output System</primary><see>BIOS</see></indexterm>
+ <indexterm><primary>Basic Input/Output
+ System</primary><see>BIOS</see></indexterm>
- <para>On x86 hardware the Basic Input/Output System (BIOS) is responsible
- for loading the operating system. To do this, the BIOS looks on the
- hard disk for the Master Boot Record (MBR), which must be located on a
- specific place on the disk. The BIOS has enough knowledge to load and
- run the MBR, and assumes that the MBR can then carry out the rest of the
- tasks involved in loading the operating system,
- possibly with the help of the BIOS.</para>
+ <para>On x86 hardware the Basic Input/Output System (BIOS) is
+ responsible for loading the operating system. To do this, the
+ BIOS looks on the hard disk for the Master Boot Record (MBR),
+ which must be located on a specific place on the disk. The BIOS
+ has enough knowledge to load and run the MBR, and assumes that
+ the MBR can then carry out the rest of the tasks involved in
+ loading the operating system, possibly with the help of the
+ BIOS.</para>
<indexterm><primary>Master Boot Record (MBR)</primary></indexterm>
@@ -89,51 +93,57 @@
<indexterm><primary>Boot Loader</primary></indexterm>
- <para>The code within the MBR is usually referred to as a <emphasis>boot
- manager</emphasis>, especially when it interacts with the user. In this case
- the boot manager usually has more code in the first
- <emphasis>track</emphasis> of the disk or within some OS's file system. (A
- boot manager is sometimes also called a <emphasis>boot loader</emphasis>,
- but FreeBSD uses that term for a later stage of booting.) Popular boot
- managers include <application>boot0</application> (a.k.a. <application>Boot
- Easy</application>, the standard &os; boot manager),
- <application>Grub</application>, <application>GAG</application>, and
- <application>LILO</application>.
- (Only <application>boot0</application> fits within the MBR.)</para>
+ <para>The code within the MBR is usually referred to as a
+ <emphasis>boot manager</emphasis>, especially when it interacts
+ with the user. In this case the boot manager usually has more
+ code in the first <emphasis>track</emphasis> of the disk or
+ within some OS's file system. (A boot manager is sometimes also
+ called a <emphasis>boot loader</emphasis>, but FreeBSD uses that
+ term for a later stage of booting.) Popular boot managers
+ include <application>boot0</application> (a.k.a.
+ <application>Boot Easy</application>, the standard &os; boot
+ manager), <application>Grub</application>,
+ <application>GAG</application>, and
+ <application>LILO</application>. (Only
+ <application>boot0</application> fits within the MBR.)</para>
- <para>If you have only one operating system installed on your disks then
- a standard PC MBR will suffice. This MBR searches for the first bootable
- (a.k.a. active) slice on the disk, and then runs the code on that slice to
- load the remainder of the operating system. The MBR installed by
- &man.fdisk.8;, by default, is such an MBR. It is based on
+ <para>If you have only one operating system installed on your
+ disks then a standard PC MBR will suffice. This MBR searches
+ for the first bootable (a.k.a. active) slice on the disk, and
+ then runs the code on that slice to load the remainder of the
+ operating system. The MBR installed by &man.fdisk.8;, by
+ default, is such an MBR. It is based on
<filename>/boot/mbr</filename>.</para>
- <para>If you have installed multiple operating systems on your disks then
- you can install a different boot manager, one that can display a list of
- different operating systems, and allows you to choose the one to boot
- from. Two of these are discussed in the next subsection.</para>
+ <para>If you have installed multiple operating systems on your
+ disks then you can install a different boot manager, one that
+ can display a list of different operating systems, and allows
+ you to choose the one to boot from. Two of these are discussed
+ in the next subsection.</para>
- <para>The remainder of the FreeBSD bootstrap system is divided into three
- stages. The first stage is run by the MBR, which knows just enough to
- get the computer into a specific state and run the second stage. The
- second stage can do a little bit more, before running the third stage.
- The third stage finishes the task of loading the operating system. The
- work is split into these three stages because the PC standards put
- limits on the size of the programs that can be run at stages one and
- two. Chaining the tasks together allows FreeBSD to provide a more
+ <para>The remainder of the FreeBSD bootstrap system is divided
+ into three stages. The first stage is run by the MBR, which
+ knows just enough to get the computer into a specific state and
+ run the second stage. The second stage can do a little bit
+ more, before running the third stage. The third stage finishes
+ the task of loading the operating system. The work is split
+ into these three stages because the PC standards put limits on
+ the size of the programs that can be run at stages one and two.
+ Chaining the tasks together allows FreeBSD to provide a more
flexible loader.</para>
<indexterm><primary>kernel</primary></indexterm>
<indexterm><primary><command>init</command></primary></indexterm>
- <para>The kernel is then started and it begins to probe for devices
- and initialize them for use. Once the kernel boot
- process is finished, the kernel passes control to the user process
- &man.init.8;, which then makes sure the disks are in a usable state.
- &man.init.8; then starts the user-level resource configuration which
- mounts file systems, sets up network cards to communicate on the
- network, and generally starts all the processes that usually
- are run on a FreeBSD system at startup.</para>
+ <para>The kernel is then started and it begins to probe for
+ devices and initialize them for use. Once the kernel boot
+ process is finished, the kernel passes control to the user
+ process &man.init.8;, which then makes sure the disks are in a
+ usable state. &man.init.8; then starts the user-level resource
+ configuration which mounts file systems, sets up network cards
+ to communicate on the network, and generally starts all the
+ processes that usually are run on a FreeBSD system at
+ startup.</para>
</sect1>
<sect1 id="boot-blocks">
@@ -143,22 +153,31 @@
<sect2 id="boot-boot0">
<title>The Boot Manager</title>
- <indexterm><primary>Master Boot Record (MBR)</primary></indexterm>
+ <indexterm><primary>Master Boot Record
+ (MBR)</primary></indexterm>
+
+ <para>The code in the MBR or boot manager is sometimes referred
+ to as <emphasis>stage zero</emphasis> of the boot process.
+ This subsection discusses two of the boot managers previously
+ mentioned: <application>boot0</application> and
+ <application>LILO</application>.</para>
- <para>The code in the MBR or boot manager is sometimes referred to as
- <emphasis>stage zero</emphasis> of the boot process. This subsection
- discusses two of the boot managers previously mentioned:
- <application>boot0</application> and <application>LILO</application>.</para>
+ <formalpara>
+ <title>The <application>boot0</application> Boot
+ Manager:</title>
- <formalpara><title>The <application>boot0</application> Boot Manager:</title>
- <para>The MBR installed by FreeBSD's installer or &man.boot0cfg.8;, by
- default, is based on <filename>/boot/boot0</filename>.
- (The <application>boot0</application> program is very simple, since the
- program in the <abbrev>MBR</abbrev> can only be 446 bytes long because of the slice
- table and <literal>0x55AA</literal> identifier at the end of the MBR.)
- If you have installed <application>boot0</application> and
- multiple operating systems on your hard disks, then you will see a
- display similar to this one at boot time:</para></formalpara>
+ <para>The MBR installed by FreeBSD's installer or
+ &man.boot0cfg.8;, by default, is based on
+ <filename>/boot/boot0</filename>. (The
+ <application>boot0</application> program is very simple,
+ since the program in the <abbrev>MBR</abbrev> can only be
+ 446 bytes long because of the slice table and
+ <literal>0x55AA</literal> identifier at the end of the MBR.)
+ If you have installed <application>boot0</application> and
+ multiple operating systems on your hard disks, then you will
+ see a display similar to this one at boot
+ time:</para>
+ </formalpara>
<example id="boot-boot0-example">
<title><filename>boot0</filename> Screenshot</title>
@@ -172,71 +191,77 @@
Default: F2</screen>
</example>
- <para>Other operating systems, in particular &windows;, have been known
- to overwrite an existing MBR with their own. If this happens to you,
- or you want to replace your existing MBR with the FreeBSD MBR then use
- the following command:</para>
+ <para>Other operating systems, in particular &windows;, have
+ been known to overwrite an existing MBR with their own. If
+ this happens to you, or you want to replace your existing MBR
+ with the FreeBSD MBR then use the following command:</para>
<screen>&prompt.root; <userinput>fdisk -B -b /boot/boot0 <replaceable>device</replaceable></userinput></screen>
- <para>where <replaceable>device</replaceable> is the device that you
- boot from, such as <devicename>ad0</devicename> for the first IDE
- disk, <devicename>ad2</devicename> for the first IDE disk on a second
- IDE controller, <devicename>da0</devicename> for the first SCSI disk,
- and so on. Or, if you want a custom configuration of the MBR,
- use &man.boot0cfg.8;.</para>
+ <para>where <replaceable>device</replaceable> is the device that
+ you boot from, such as <devicename>ad0</devicename> for the
+ first IDE disk, <devicename>ad2</devicename> for the first IDE
+ disk on a second IDE controller, <devicename>da0</devicename>
+ for the first SCSI disk, and so on. Or, if you want a custom
+ configuration of the MBR, use &man.boot0cfg.8;.</para>
- <formalpara><title>The LILO Boot Manager:</title>
+ <formalpara>
+ <title>The LILO Boot Manager:</title>
- <para>To install this boot manager so it will also boot FreeBSD, first
- start Linux and add the following to your existing
- <filename>/etc/lilo.conf</filename> configuration file:</para></formalpara>
+ <para>To install this boot manager so it will also boot
+ FreeBSD, first start Linux and add the following to your
+ existing <filename>/etc/lilo.conf</filename> configuration
+ file:</para>
+ </formalpara>
<programlisting>other=/dev/hdXY
table=/dev/hdX
loader=/boot/chain.b
label=FreeBSD</programlisting>
- <para>In the above, specify FreeBSD's primary partition and drive using
- Linux specifiers, replacing <replaceable>X</replaceable> with the Linux
- drive letter and <replaceable>Y</replaceable> with the Linux primary
- partition number. If you are using a <acronym>SCSI</acronym> drive, you
- will need to change <replaceable>/dev/hd</replaceable> to read something
- similar to <replaceable>/dev/sd</replaceable>. The
- <option>loader=/boot/chain.b</option> line can be omitted if you have
- both operating systems on the same drive. Now run
- <command>/sbin/lilo -v</command> to commit your new changes to the
- system; this should be verified by checking its screen messages.</para>
+ <para>In the above, specify FreeBSD's primary partition and
+ drive using Linux specifiers, replacing
+ <replaceable>X</replaceable> with the Linux drive letter and
+ <replaceable>Y</replaceable> with the Linux primary partition
+ number. If you are using a <acronym>SCSI</acronym> drive, you
+ will need to change <replaceable>/dev/hd</replaceable> to read
+ something similar to <replaceable>/dev/sd</replaceable>. The
+ <option>loader=/boot/chain.b</option> line can be omitted if
+ you have both operating systems on the same drive. Now run
+ <command>/sbin/lilo -v</command> to commit your new
+ changes to the system; this should be verified by checking its
+ screen messages.</para>
</sect2>
-
+
<sect2 id="boot-boot1">
- <title>Stage One, <filename>/boot/boot1</filename>, and Stage Two,
- <filename>/boot/boot2</filename></title>
-
- <para>Conceptually the first and second stages are part of the same
- program, on the same area of the disk. Because of space constraints
- they have been split into two, but you would always install them
- together. They are copied from the combined file
- <filename>/boot/boot</filename> by the installer or
- <application>bsdlabel</application> (see below).</para>
+ <title>Stage One, <filename>/boot/boot1</filename>, and Stage
+ Two, <filename>/boot/boot2</filename></title>
+
+ <para>Conceptually the first and second stages are part of the
+ same program, on the same area of the disk. Because of space
+ constraints they have been split into two, but you would
+ always install them together. They are copied from the
+ combined file <filename>/boot/boot</filename> by the installer
+ or <application>bsdlabel</application> (see below).</para>
+
+ <para>They are located outside file systems, in the first track
+ of the boot slice, starting with the first sector. This is
+ where <link linkend="boot-boot0">boot0</link>, or any other
+ boot manager, expects to find a program to run which will
+ continue the boot process. The number of sectors used is
+ easily determined from the size of
+ <filename>/boot/boot</filename>.</para>
- <para>They are located outside file systems, in the first track of
- the boot slice, starting with the first sector. This is where <link
- linkend="boot-boot0">boot0</link>, or any other boot manager,
- expects to find a program to run which will
- continue the boot process. The number of sectors used is easily
- determined from the size of <filename>/boot/boot</filename>.</para>
+ <para><filename>boot1</filename> is very simple, since it can
+ only be 512 bytes in size, and knows just enough about the
+ FreeBSD <firstterm>bsdlabel</firstterm>, which stores
+ information about the slice, to find and execute
+ <filename>boot2</filename>.</para>
- <para><filename>boot1</filename> is very simple, since it
- can only be 512 bytes
- in size, and knows just enough about the FreeBSD
- <firstterm>bsdlabel</firstterm>, which stores information
- about the slice, to find and execute <filename>boot2</filename>.</para>
-
- <para><filename>boot2</filename> is slightly more sophisticated, and understands
- the FreeBSD file system enough to find files on it, and can
- provide a simple interface to choose the kernel or loader to
- run.</para>
+ <para><filename>boot2</filename> is slightly more sophisticated,
+ and understands the FreeBSD file system enough to find files
+ on it, and can provide a simple interface to choose the kernel
+ or loader to run.</para>
<para>Since the <link linkend="boot-loader">loader</link> is
much more sophisticated, and provides a nice easy-to-use
@@ -255,261 +280,270 @@
<para>If you ever need to replace the installed
<filename>boot1</filename> and <filename>boot2</filename> use
&man.bsdlabel.8;:</para>
-
+
<screen>&prompt.root; <userinput>bsdlabel -B <replaceable>diskslice</replaceable></userinput></screen>
- <para>where <replaceable>diskslice</replaceable> is the disk and slice
- you boot from, such as <devicename>ad0s1</devicename> for the first
- slice on the first IDE disk.</para>
+ <para>where <replaceable>diskslice</replaceable> is the disk and
+ slice you boot from, such as <devicename>ad0s1</devicename>
+ for the first slice on the first IDE disk.</para>
<warning>
<title>Dangerously Dedicated Mode</title>
<para>If you use just the disk name, such as
- <devicename>ad0</devicename>, in the &man.bsdlabel.8; command you
- will create a dangerously dedicated disk, without slices. This is
- almost certainly not what you want to do, so make sure you double
- check the &man.bsdlabel.8; command before you press
- <keycap>Return</keycap>.</para>
+ <devicename>ad0</devicename>, in the &man.bsdlabel.8;
+ command you will create a dangerously dedicated disk,
+ without slices. This is almost certainly not what you want
+ to do, so make sure you double check the &man.bsdlabel.8;
+ command before you press <keycap>Return</keycap>.</para>
</warning>
</sect2>
- <sect2 id="boot-loader">
- <title>Stage Three, <filename>/boot/loader</filename></title>
+ <sect2 id="boot-loader">
+ <title>Stage Three, <filename>/boot/loader</filename></title>
+
+ <indexterm><primary>boot-loader</primary></indexterm>
+
+ <para>The loader is the final stage of the three-stage
+ bootstrap, and is located on the file system, usually as
+ <filename>/boot/loader</filename>.</para>
+
+ <para>The loader is intended as a user-friendly method for
+ configuration, using an easy-to-use built-in command set,
+ backed up by a more powerful interpreter, with a more complex
+ command set.</para>
+
+ <sect3 id="boot-loader-flow">
+ <title>Loader Program Flow</title>
+
+ <para>During initialization, the loader will probe for a
+ console and for disks, and figure out what disk it is
+ booting from. It will set variables accordingly, and an
+ interpreter is started where user commands can be passed
+ from a script or interactively.</para>
+
+ <indexterm><primary>loader</primary></indexterm>
+ <indexterm><primary>loader configuration</primary></indexterm>
+
+ <para>The loader will then read
+ <filename>/boot/loader.rc</filename>, which by default reads
+ in <filename>/boot/defaults/loader.conf</filename> which
+ sets reasonable defaults for variables and reads
+ <filename>/boot/loader.conf</filename> for local changes to
+ those variables. <filename>loader.rc</filename> then acts
+ on these variables, loading whichever modules and kernel are
+ selected.</para>
+
+ <para>Finally, by default, the loader issues a 10 second wait
+ for key presses, and boots the kernel if it is not
+ interrupted. If interrupted, the user is presented with a
+ prompt which understands the easy-to-use command set, where
+ the user may adjust variables, unload all modules, load
+ modules, and then finally boot or reboot.</para>
+ </sect3>
+
+ <sect3 id="boot-loader-commands">
+ <title>Loader Built-In Commands</title>
+
+ <para>These are the most commonly used loader commands. For a
+ complete discussion of all available commands, please see
+ &man.loader.8;.</para>
- <indexterm><primary>boot-loader</primary></indexterm>
- <para>The loader is the final stage of the three-stage
- bootstrap, and is located on the file system, usually as
- <filename>/boot/loader</filename>.</para>
-
- <para>The loader is intended as a user-friendly method for
- configuration, using an easy-to-use built-in command set,
- backed up by a more powerful interpreter, with a more complex
- command set.</para>
+ <variablelist>
+ <varlistentry>
+ <term>autoboot <replaceable>seconds</replaceable></term>
- <sect3 id="boot-loader-flow">
- <title>Loader Program Flow</title>
-
- <para>During initialization, the loader will probe for a
- console and for disks, and figure out what disk it is
- booting from. It will set variables accordingly, and an
- interpreter is started where user commands can be passed from
- a script or interactively.</para>
- <indexterm><primary>loader</primary></indexterm>
- <indexterm><primary>loader configuration</primary></indexterm>
+ <listitem>
+ <para>Proceeds to boot the kernel if not interrupted
+ within the time span given, in seconds. It displays a
+ countdown, and the default time span is 10
+ seconds.</para>
+ </listitem>
+ </varlistentry>
- <para>The loader will then read
- <filename>/boot/loader.rc</filename>, which by default reads
- in <filename>/boot/defaults/loader.conf</filename> which
- sets reasonable defaults for variables and reads
- <filename>/boot/loader.conf</filename> for local changes to
- those variables. <filename>loader.rc</filename> then acts
- on these variables, loading whichever modules and kernel are
- selected.</para>
+ <varlistentry>
+ <term>boot
+ <optional><replaceable>-options</replaceable></optional>
+ <optional><replaceable>kernelname</replaceable></optional></term>
- <para>Finally, by default, the loader issues a 10 second wait
- for key presses, and boots the kernel if it is not interrupted.
- If interrupted, the user is presented with a prompt which
- understands the easy-to-use command set, where the user may
- adjust variables, unload all modules, load modules, and then
- finally boot or reboot.</para>
+ <listitem>
+ <para>Immediately proceeds to boot the kernel, with the
+ given options, if any, and with the kernel name given,
+ if it is. Providing a kernel name on the command-line
+ is only applicable after an
+ <emphasis>unload</emphasis> command has been issued,
+ otherwise the previously-loaded kernel will be
+ used.</para>
+ </listitem>
+ </varlistentry>
- </sect3>
-
- <sect3 id="boot-loader-commands">
- <title>Loader Built-In Commands</title>
-
- <para>These are the most commonly used loader commands. For a
- complete discussion of all available commands, please see
- &man.loader.8;.</para>
+ <varlistentry>
+ <term>boot-conf</term>
- <variablelist>
- <varlistentry>
- <term>autoboot <replaceable>seconds</replaceable></term>
+ <listitem>
+ <para>Goes through the same automatic configuration of
+ modules based on variables as what happens at boot.
+ This only makes sense if you use
+ <command>unload</command> first, and change some
+ variables, most commonly <envar>kernel</envar>.</para>
+ </listitem>
+ </varlistentry>
- <listitem>
- <para>Proceeds to boot the kernel if not interrupted
- within the time span given, in seconds. It displays a
- countdown, and the default time span is 10
- seconds.</para>
- </listitem>
- </varlistentry>
+ <varlistentry>
+ <term>help
+ <optional><replaceable>topic</replaceable></optional></term>
- <varlistentry>
- <term>boot
- <optional><replaceable>-options</replaceable></optional>
- <optional><replaceable>kernelname</replaceable></optional></term>
+ <listitem>
+ <para>Shows help messages read from
+ <filename>/boot/loader.help</filename>. If the topic
+ given is <literal>index</literal>, then the list of
+ available topics is given.</para>
+ </listitem>
+ </varlistentry>
- <listitem>
- <para>Immediately proceeds to boot the kernel, with the
- given options, if any, and with the kernel name given,
- if it is. Providing a kernel name on the command-line
- is only applicable after an <emphasis>unload</emphasis>
- command has been issued, otherwise the previously-loaded
- kernel will be used.</para>
- </listitem>
- </varlistentry>
+ <varlistentry>
+ <term>include <replaceable>filename</replaceable>
+ …</term>
- <varlistentry>
- <term>boot-conf</term>
+ <listitem>
+ <para>Processes the file with the given filename. The
+ file is read in, and interpreted line by line. An
+ error immediately stops the include command.</para>
+ </listitem>
+ </varlistentry>
- <listitem>
- <para>Goes through the same automatic configuration of
- modules based on variables as what happens at boot.
- This only makes sense if you use
- <command>unload</command> first, and change some
- variables, most commonly <envar>kernel</envar>.</para>
- </listitem>
- </varlistentry>
+ <varlistentry>
+ <term>load <optional><option>-t</option>
+ <replaceable>type</replaceable></optional>
+ <replaceable>filename</replaceable></term>
- <varlistentry>
- <term>help
- <optional><replaceable>topic</replaceable></optional></term>
+ <listitem>
+ <para>Loads the kernel, kernel module, or file of the
+ type given, with the filename given. Any arguments
+ after filename are passed to the file.</para>
+ </listitem>
+ </varlistentry>
- <listitem>
- <para>Shows help messages read from
- <filename>/boot/loader.help</filename>. If the topic
- given is <literal>index</literal>, then the list of
- available topics is given.</para>
- </listitem>
- </varlistentry>
+ <varlistentry>
+ <term>ls <optional><option>-l</option></optional>
+ <optional><replaceable>path</replaceable></optional></term>
- <varlistentry>
- <term>include <replaceable>filename</replaceable>
- …</term>
+ <listitem>
+ <para>Displays a listing of files in the given path, or
+ the root directory, if the path is not specified. If
+ <option>-l</option> is specified, file sizes will be
+ shown too.</para>
+ </listitem>
+ </varlistentry>
- <listitem>
- <para>Processes the file with the given filename. The
- file is read in, and interpreted line by line. An
- error immediately stops the include command.</para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>load <optional><option>-t</option>
- <replaceable>type</replaceable></optional>
- <replaceable>filename</replaceable></term>
+ <varlistentry>
+ <term>lsdev
+ <optional><option>-v</option></optional></term>
- <listitem>
- <para>Loads the kernel, kernel module, or file of the
- type given, with the filename given. Any arguments
- after filename are passed to the file.</para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>ls <optional><option>-l</option></optional>
- <optional><replaceable>path</replaceable></optional></term>
+ <listitem>
+ <para>Lists all of the devices from which it may be
+ possible to load modules. If <option>-v</option> is
+ specified, more details are printed.</para>
+ </listitem>
+ </varlistentry>
- <listitem>
- <para>Displays a listing of files in the given path, or
- the root directory, if the path is not specified. If
- <option>-l</option> is specified, file sizes will be
- shown too.</para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>lsdev <optional><option>-v</option></optional></term>
+ <varlistentry>
+ <term>lsmod
+ <optional><option>-v</option></optional></term>
- <listitem>
- <para>Lists all of the devices from which it may be
- possible to load modules. If <option>-v</option> is
- specified, more details are printed.</para>
- </listitem>
- </varlistentry>
+ <listitem>
+ <para>Displays loaded modules. If <option>-v</option>
+ is specified, more details are shown.</para>
+ </listitem>
+ </varlistentry>
- <varlistentry>
- <term>lsmod <optional><option>-v</option></optional></term>
+ <varlistentry>
+ <term>more <replaceable>filename</replaceable></term>
- <listitem>
- <para>Displays loaded modules. If <option>-v</option> is
- specified, more details are shown.</para>
- </listitem>
- </varlistentry>
+ <listitem>
+ <para>Displays the files specified, with a pause at each
+ <varname>LINES</varname> displayed.</para>
+ </listitem>
+ </varlistentry>
- <varlistentry>
- <term>more <replaceable>filename</replaceable></term>
+ <varlistentry>
+ <term>reboot</term>
- <listitem>
- <para>Displays the files specified, with a pause at each
- <varname>LINES</varname> displayed.</para>
- </listitem>
- </varlistentry>
+ <listitem>
+ <para>Immediately reboots the system.</para>
+ </listitem>
+ </varlistentry>
- <varlistentry>
- <term>reboot</term>
+ <varlistentry>
+ <term>set <replaceable>variable</replaceable></term>
+ <term>set
+ <replaceable>variable</replaceable>=<replaceable>value</replaceable></term>
- <listitem>
- <para>Immediately reboots the system.</para>
- </listitem>
- </varlistentry>
+ <listitem>
+ <para>Sets the loader's environment variables.</para>
+ </listitem>
+ </varlistentry>
- <varlistentry>
- <term>set <replaceable>variable</replaceable></term>
- <term>set
- <replaceable>variable</replaceable>=<replaceable>value</replaceable></term>
+ <varlistentry>
+ <term>unload</term>
- <listitem>
- <para>Sets the loader's environment variables.</para>
- </listitem>
- </varlistentry>
+ <listitem>
+ <para>Removes all loaded modules.</para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </sect3>
- <varlistentry>
- <term>unload</term>
+ <sect3 id="boot-loader-examples">
+ <title>Loader Examples</title>
- <listitem>
- <para>Removes all loaded modules.</para>
- </listitem>
- </varlistentry>
- </variablelist>
- </sect3>
+ <para>Here are some practical examples of loader usage:</para>
- <sect3 id="boot-loader-examples">
- <title>Loader Examples</title>
+ <itemizedlist>
+ <indexterm><primary>single-user mode</primary></indexterm>
- <para>Here are some practical examples of loader usage:</para>
+ <listitem>
+ <para>To simply boot your usual kernel, but in single-user
+ mode:</para>
- <itemizedlist>
- <indexterm><primary>single-user mode</primary></indexterm>
- <listitem>
- <para>To simply boot your usual kernel, but in single-user
- mode:</para>
+ <screen><userinput>boot -s</userinput></screen>
+ </listitem>
- <screen><userinput>boot -s</userinput></screen>
- </listitem>
+ <listitem>
+ <para>To unload your usual kernel and modules, and then
+ load just your old (or another) kernel:</para>
- <listitem>
- <para>To unload your usual kernel and modules, and then
- load just your old (or another) kernel:</para>
- <indexterm>
- <primary><filename>kernel.old</filename></primary>
- </indexterm>
+ <indexterm>
+ <primary><filename>kernel.old</filename></primary>
+ </indexterm>
- <screen><userinput>unload</userinput>
+ <screen><userinput>unload</userinput>
<userinput>load <replaceable>kernel.old</replaceable></userinput></screen>
- <para>You can use <filename>kernel.GENERIC</filename> to
- refer to the generic kernel that comes on the install
- disk, or <filename>kernel.old</filename> to refer to
- your previously installed kernel (when you have upgraded
- or configured your own kernel, for example).</para>
+ <para>You can use <filename>kernel.GENERIC</filename> to
+ refer to the generic kernel that comes on the install
+ disk, or <filename>kernel.old</filename> to refer to
+ your previously installed kernel (when you have upgraded
+ or configured your own kernel, for example).</para>
>>> TRUNCATED FOR MAIL (1000 lines) <<<
More information about the p4-projects
mailing list