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

- Use a more fine-grained markup

Browse source 
PR:		docs/123948, docs/123974
Submitted by:	pgj
This commit is contained in:
Gabor Kovesdan 2008-05-25 14:37:05 +00:00
parent 17ca8361e0
commit 9994ce961f
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=32043
1 changed files with 10 additions and 10 deletions
Download patch file Download diff file Expand all files Collapse all files

20
en_US.ISO8859-1/books/faq/book.sgml
View file

@ -1689,9 +1689,9 @@ File: +DESC (ignored)</screen>
<para>If it <emphasis>is</emphasis> turned on (it is often
supplied this way to get around certain limitations in
&ms-dos;) and the disk capacity is more than 1GB, use M
&ms-dos;) and the disk capacity is more than 1GB, use <replaceable>M</replaceable>
cylinders, 63 sectors per track (<emphasis>not</emphasis>
64), and 255 heads, where <literal>M</literal> is the disk capacity in MB
64), and 255 heads, where <replaceable>M</replaceable> is the disk capacity in MB
divided by 7.844238 (!). So our example 2GB drive would
have 261 cylinders, 63 sectors per track and 255
heads.</para>
@ -1900,11 +1900,11 @@ File: +DESC (ignored)</screen>
systems, with the hard disks arranged as the master or
single device on separate IDE controllers, with FreeBSD
installed on the secondary IDE controller. The boot blocks
think the system is installed on ad0 (the second BIOS
think the system is installed on <devicename>ad0</devicename> (the second BIOS
disk) while the kernel assigns the first disk on the
secondary controller device, ad2. After the device
secondary controller device, <devicename>ad2</devicename>. After the device
probing, the kernel tries to mount what the boot blocks
think is the boot disk, ad0, while it is really ad2, and
think is the boot disk, <devicename>ad0</devicename>, while it is really <devicename>ad2</devicename>, and
fails.</para>
<para>To fix the problem, do one of the following:</para>
@ -1917,10 +1917,10 @@ File: +DESC (ignored)</screen>
drop you into the boot loader.</para>
<para>Then type
<literal>
<userinput>
set
root_disk_unit="<replaceable>disk_number</replaceable>"
</literal>. <replaceable>disk_number</replaceable>
</userinput>. <replaceable>disk_number</replaceable>
will be <literal>0</literal> if FreeBSD is installed
on the master drive on the first IDE controller,
<literal>1</literal> if it is installed on the slave
@ -1930,13 +1930,13 @@ File: +DESC (ignored)</screen>
installed on the slave of the second IDE
controller.</para>
<para>Then type <literal>boot</literal>, and your
<para>Then type <userinput>boot</userinput>, and your
system should boot correctly.</para>
<para>To make this change permanent (i.e, so you do not
have to do this every time you reboot or turn on
your FreeBSD machine), put the line <literal>
root_disk_unit="<replaceable>disk_number</replaceable>"</literal>
your FreeBSD machine), put the line <userinput>
root_disk_unit="<replaceable>disk_number</replaceable>"</userinput>
in <filename>/boot/loader.conf.local
</filename>.</para>
</listitem>