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

Fix up the grammar in a few places.

Browse source 
Submitted by:	Josh Bello <josh@pike.cdrom.com>
This commit is contained in:
Jim Mock 2000-04-07 21:26:56 +00:00
parent 9e3b2b0844
commit dc328a6b88
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=7027
2 changed files with 24 additions and 24 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -1,7 +1,7 @@
<!-- <!--
The FreeBSD Documentation Project The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/boot/chapter.sgml,v 1.5 2000/03/25 14:18:24 nbm Exp $ $FreeBSD: doc/en_US.ISO_8859-1/books/handbook/boot/chapter.sgml,v 1.6 2000/04/03 02:15:35 chris Exp $
--> -->
<chapter id="boot"> <chapter id="boot">
@ -12,14 +12,14 @@
<para>FreeBSD uses a three-stage bootstrap by default, which <para>FreeBSD uses a three-stage bootstrap by default, which
basically entails three programs which call each basically entails three programs which call each
other in order (the two <link linkend="boot-blocks">boot other in order (two <link linkend="boot-blocks">boot
blocks</link>, and the <link blocks</link>, and the <link
linkend="boot-loader">loader</link>). Each of these three build on the linkend="boot-loader">loader</link>). Each of these three build on the
previous program's understanding and provide increasing amounts previous program's understanding and provide increasing amounts
of sophistication.</para> of sophistication.</para>
<para>The kernel is then started, at which time devices are <para>The kernel is then started, which will then probe for devices
probed for and initialized for use. Once the kernel boot and initialize them for use. Once the kernel boot
process is finished, the kernel passes control to the user process 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;, which then makes sure the disks are in a usable state.
&man.init.8; then starts the user-level resource configuration which &man.init.8; then starts the user-level resource configuration which
@ -42,14 +42,14 @@
programs to determine what configuration details were programs to determine what configuration details were
determined.</para> determined.</para>
<para>In standard personal computers, this involves the BIOS, <para>In standard personal computers, this involves the BIOS
which oversees the bootstrap, and CMOS, which stores (which oversees the bootstrap), and CMOS (which stores
configuration; and these understand disks, and they also configuration). BIOS and CMOS understand disks, and also
understand where on the disk to find a program that will know understand where on the disk to find a program that will know
how to load up an operating system.</para> how to load up an operating system.</para>
<para>This chapter will not deal with this first part of the <para>This chapter will not deal with this first part of the
bootstrap process, and focuses on what happens after control bootstrap process. Instead it will focus on what happens after control
is passed to the program on the disk.</para> is passed to the program on the disk.</para>
<para>The boot blocks are responsible for finding (usually) the <para>The boot blocks are responsible for finding (usually) the
@ -67,7 +67,7 @@
list of possible slices to boot from.</para> list of possible slices to boot from.</para>
<para>boot0 is very simple, since the program in the <para>boot0 is very simple, since the program in the
<abbrev>MBR</abbrev> can only be 512 bytes large.</para> <abbrev>MBR</abbrev> can only be 512 bytes in size.</para>
<para>It displays something like this:</para> <para>It displays something like this:</para>
@ -94,7 +94,7 @@ Default: F2</screen>
find the program to run to continue the boot process.</para> find the program to run to continue the boot process.</para>
<para>boot1 is very simple, since it too can only be 512 bytes <para>boot1 is very simple, since it too can only be 512 bytes
large, and knows just enough about the FreeBSD in size, and knows just enough about the FreeBSD
<firstterm>disklabel</firstterm>, which stores information <firstterm>disklabel</firstterm>, which stores information
about the slice, to find and execute <link about the slice, to find and execute <link
linkend="boot-boot2">boot2</link>.</para> linkend="boot-boot2">boot2</link>.</para>
@ -116,7 +116,7 @@ Default: F2</screen>
<example id="boot-boot2-example"> <example id="boot-boot2-example">
<title>boot2 screenshot</title> <title>boot2 screenshot</title>
<screen>>> FreeBSD/i386 BOOT <screen>&gt;&gt; FreeBSD/i386 BOOT
Default: 0:wd(0,a)/kernel Default: 0:wd(0,a)/kernel
boot:</screen> boot:</screen>
</example> </example>
@ -367,7 +367,7 @@ boot:</screen>
<para>Once the kernel is loaded by either <link <para>Once the kernel is loaded by either <link
linkend="boot-loader">loader</link> (as usual) or <link linkend="boot-loader">loader</link> (as usual) or <link
linkend="boot-boot2">boot2</link> (bypassing the loader), it linkend="boot-boot2">boot2</link> (bypassing the loader), it
examines its boot flags, if any, and adjusts its behaviour as examines its boot flags, if any, and adjusts its behavior as
necessary.</para> necessary.</para>
<sect2 id="boot-kernel-bootflags"> <sect2 id="boot-kernel-bootflags">

24
en_US.ISO_8859-1/books/handbook/boot/chapter.sgml
View file

@ -1,7 +1,7 @@
<!-- <!--
The FreeBSD Documentation Project The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/boot/chapter.sgml,v 1.5 2000/03/25 14:18:24 nbm Exp $ $FreeBSD: doc/en_US.ISO_8859-1/books/handbook/boot/chapter.sgml,v 1.6 2000/04/03 02:15:35 chris Exp $
--> -->
<chapter id="boot"> <chapter id="boot">
@ -12,14 +12,14 @@
<para>FreeBSD uses a three-stage bootstrap by default, which <para>FreeBSD uses a three-stage bootstrap by default, which
basically entails three programs which call each basically entails three programs which call each
other in order (the two <link linkend="boot-blocks">boot other in order (two <link linkend="boot-blocks">boot
blocks</link>, and the <link blocks</link>, and the <link
linkend="boot-loader">loader</link>). Each of these three build on the linkend="boot-loader">loader</link>). Each of these three build on the
previous program's understanding and provide increasing amounts previous program's understanding and provide increasing amounts
of sophistication.</para> of sophistication.</para>
<para>The kernel is then started, at which time devices are <para>The kernel is then started, which will then probe for devices
probed for and initialized for use. Once the kernel boot and initialize them for use. Once the kernel boot
process is finished, the kernel passes control to the user process 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;, which then makes sure the disks are in a usable state.
&man.init.8; then starts the user-level resource configuration which &man.init.8; then starts the user-level resource configuration which
@ -42,14 +42,14 @@
programs to determine what configuration details were programs to determine what configuration details were
determined.</para> determined.</para>
<para>In standard personal computers, this involves the BIOS, <para>In standard personal computers, this involves the BIOS
which oversees the bootstrap, and CMOS, which stores (which oversees the bootstrap), and CMOS (which stores
configuration; and these understand disks, and they also configuration). BIOS and CMOS understand disks, and also
understand where on the disk to find a program that will know understand where on the disk to find a program that will know
how to load up an operating system.</para> how to load up an operating system.</para>
<para>This chapter will not deal with this first part of the <para>This chapter will not deal with this first part of the
bootstrap process, and focuses on what happens after control bootstrap process. Instead it will focus on what happens after control
is passed to the program on the disk.</para> is passed to the program on the disk.</para>
<para>The boot blocks are responsible for finding (usually) the <para>The boot blocks are responsible for finding (usually) the
@ -67,7 +67,7 @@
list of possible slices to boot from.</para> list of possible slices to boot from.</para>
<para>boot0 is very simple, since the program in the <para>boot0 is very simple, since the program in the
<abbrev>MBR</abbrev> can only be 512 bytes large.</para> <abbrev>MBR</abbrev> can only be 512 bytes in size.</para>
<para>It displays something like this:</para> <para>It displays something like this:</para>
@ -94,7 +94,7 @@ Default: F2</screen>
find the program to run to continue the boot process.</para> find the program to run to continue the boot process.</para>
<para>boot1 is very simple, since it too can only be 512 bytes <para>boot1 is very simple, since it too can only be 512 bytes
large, and knows just enough about the FreeBSD in size, and knows just enough about the FreeBSD
<firstterm>disklabel</firstterm>, which stores information <firstterm>disklabel</firstterm>, which stores information
about the slice, to find and execute <link about the slice, to find and execute <link
linkend="boot-boot2">boot2</link>.</para> linkend="boot-boot2">boot2</link>.</para>
@ -116,7 +116,7 @@ Default: F2</screen>
<example id="boot-boot2-example"> <example id="boot-boot2-example">
<title>boot2 screenshot</title> <title>boot2 screenshot</title>
<screen>>> FreeBSD/i386 BOOT <screen>&gt;&gt; FreeBSD/i386 BOOT
Default: 0:wd(0,a)/kernel Default: 0:wd(0,a)/kernel
boot:</screen> boot:</screen>
</example> </example>
@ -367,7 +367,7 @@ boot:</screen>
<para>Once the kernel is loaded by either <link <para>Once the kernel is loaded by either <link
linkend="boot-loader">loader</link> (as usual) or <link linkend="boot-loader">loader</link> (as usual) or <link
linkend="boot-boot2">boot2</link> (bypassing the loader), it linkend="boot-boot2">boot2</link> (bypassing the loader), it
examines its boot flags, if any, and adjusts its behaviour as examines its boot flags, if any, and adjusts its behavior as
necessary.</para> necessary.</para>
<sect2 id="boot-kernel-bootflags"> <sect2 id="boot-kernel-bootflags">