docs/149482: [patch][handbook] Chapter 12 The FreeBSD Booting Process: Replace "FreeBSD" with "&os; "
Glen Barber
glen.j.barber at gmail.com
Tue Aug 10 00:10:06 UTC 2010
>Number: 149482
>Category: docs
>Synopsis: [patch][handbook] Chapter 12 The FreeBSD Booting Process: Replace "FreeBSD" with "&os;"
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-doc
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: doc-bug
>Submitter-Id: current-users
>Arrival-Date: Tue Aug 10 00:10:05 UTC 2010
>Closed-Date:
>Last-Modified:
>Originator: Glen Barber
>Release: 8.1-PRERELEASE
>Organization:
>Environment:
FreeBSD orion 8.1-PRERELEASE FreeBSD 8.1-PRERELEASE #3 r210428: Sat Jul 24 13:37:37 EDT 2010 root at orion:/usr/obj/usr/src/sys/ORION amd64
>Description:
The attached patch replaces instances of "FreeBSD" with "&os;" where appropriate.
>How-To-Repeat:
>Fix:
Patch attached with submission follows:
--- boot/chapter.sgml.orig 2009-02-16 11:47:13.000000000 -0500
+++ boot/chapter.sgml 2010-08-09 19:27:20.000000000 -0400
@@ -5,7 +5,7 @@
-->
<chapter id="boot">
- <title>The FreeBSD Booting Process</title>
+ <title>The &os; Booting Process</title>
<sect1 id="boot-synopsis">
<title>Synopsis</title>
@@ -14,15 +14,15 @@
<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
+ <quote>booting</quote>. &os;'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
+ to customize the &os; boot process. This includes everything that
+ happens until the &os; 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>
@@ -30,12 +30,12 @@
<itemizedlist>
<listitem>
- <para>What the components of the FreeBSD bootstrap system are, and how
+ <para>What the components of the &os; bootstrap system are, and how
they interact.</para>
</listitem>
<listitem>
- <para>The options you can give to the components in the FreeBSD
+ <para>The options you can give to the components in the &os;
bootstrap to control the boot process.</para>
</listitem>
@@ -47,7 +47,7 @@
<note>
<title>x86 Only</title>
- <para>This chapter only describes the boot process for FreeBSD running
+ <para>This chapter only describes the boot process for &os; running
on Intel x86 systems.</para>
</note>
</sect1>
@@ -94,7 +94,7 @@
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
+ but &os; 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
@@ -113,14 +113,14 @@
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
+ <para>The remainder of the &os; 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
+ two. Chaining the tasks together allows &os; to provide a more
flexible loader.</para>
<indexterm><primary>kernel</primary></indexterm>
@@ -133,7 +133,7 @@
&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>
+ are run on a &os; system at startup.</para>
</sect1>
<sect1 id="boot-blocks">
@@ -151,7 +151,7 @@
<application>boot0</application> and <application>LILO</application>.</para>
<formalpara><title>The <application>boot0</application> Boot Manager:</title>
- <para>The MBR installed by FreeBSD's installer or &man.boot0cfg.8;, by
+ <para>The MBR installed by &os;'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
@@ -164,7 +164,7 @@
<title><filename>boot0</filename> Screenshot</title>
<screen>F1 DOS
-F2 FreeBSD
+F2 &os;
F3 Linux
F4 ??
F5 Drive 1
@@ -174,7 +174,7 @@
<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
+ or you want to replace your existing MBR with the &os; MBR then use
the following command:</para>
<screen>&prompt.root; <userinput>fdisk -B -b /boot/boot0 <replaceable>device</replaceable></userinput></screen>
@@ -188,16 +188,16 @@
<formalpara><title>The LILO Boot Manager:</title>
- <para>To install this boot manager so it will also boot FreeBSD, first
+ <para>To install this boot manager so it will also boot &os;, 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>
+label=&os;</programlisting>
- <para>In the above, specify FreeBSD's primary partition and drive using
+ <para>In the above, specify &os;'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
@@ -229,12 +229,12 @@
<para><filename>boot1</filename> is very simple, since it
can only be 512 bytes
- in size, and knows just enough about the FreeBSD
+ in size, and knows just enough about the &os;
<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
+ the &os; file system enough to find files on it, and can
provide a simple interface to choose the kernel or loader to
run.</para>
@@ -247,7 +247,7 @@
<example id="boot-boot2-example">
<title><filename>boot2</filename> Screenshot</title>
- <screen>>> FreeBSD/i386 BOOT
+ <screen>>> &os;/i386 BOOT
Default: 0:ad(0,a)/boot/loader
boot:</screen>
</example>
@@ -788,7 +788,7 @@
</indexterm>
<title>Device Hints</title>
- <note><para>This is a FreeBSD 5.0 and later feature which does not
+ <note><para>This is a &os; 5.0 and later feature which does not
exist in earlier versions.</para></note>
<para>During initial system startup, the boot &man.loader.8; will read the
@@ -972,10 +972,10 @@
the <literal>KILL</literal> signal to any that do not terminate
timely.</para>
- <para>To power down a FreeBSD machine on architectures and systems
+ <para>To power down a &os; machine on architectures and systems
that support power management, simply use the command
<command>shutdown -p now</command> to turn the power off
- immediately. To just reboot a FreeBSD system, just use
+ immediately. To just reboot a &os; system, just use
<command>shutdown -r now</command>. You need to be
<username>root</username> or a member of
<groupname>operator</groupname> group to run &man.shutdown.8;.
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the freebsd-doc
mailing list