o Fix mdoc formatting for the '.Fx' macro. [1]

o Add information about APM scheme and fix typos. [2]

Submitted by:	gjb [1], nwhitehorn [2]
Approved by:	re (kib)
MFC after:	1 week
This commit is contained in:
Andrey V. Elsukov 2011-08-20 08:20:10 +00:00
parent bda13729a4
commit 25b233372d
Notes: svn2git 2020-12-20 02:59:44 +00:00
svn path=/head/; revision=225023

View File

@ -709,7 +709,8 @@ The scheme-specific attributes for PC98:
.It Cm bootable
.El
.Sh BOOTSTRAPPING
.Fx supports several partitioning schemes and each scheme uses different
.Fx
supports several partitioning schemes and each scheme uses different
bootstrap code.
The bootstrap code is located in the specific disk area for each partitioning
scheme and also it might have different size.
@ -770,7 +771,7 @@ and
The first one is used to boot from UFS.
It searches in the GPT partition with type
.Cm freebsd-ufs ,
and it runs the thrid bootstrap stage (
and it runs the third bootstrap stage (
.Pa /boot/loader )
if it is found.
The
@ -785,7 +786,7 @@ from it.
The VTOC8 scheme does not support embedding bootstrap code.
Instead, the 8 KBytes bootstrap code image
.Pa /boot/boot1
could be written with
should be written with
.Cm gpart bootcode
command with
.Fl p Ar bootcode
@ -793,6 +794,15 @@ option to all sufficiently large VTOC8 partitions.
To do this the
.Fl i Ar index
option could be ommited.
.Pp
The APM scheme also does not support embedding bootstrap code.
Instead, the 800 KBytes bootstrap code image
.Pa /boot/boot1.hfs
should be written with
.Cm gpart bootcode
command to a partition of type
.Cm freebsd-boot ,
which should also be 800 KB in size.
.Sh OPERATIONAL FLAGS
Actions other than the
.Cm commit