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

Typo and markup fixes.

Browse source 
PR:		docs/28777
Submitted by:	Giorgos Keramidas <keramida@ceid.upatras.gr>
This commit is contained in:
Nik Clayton 2001-07-11 13:07:38 +00:00
parent dc6cbd9351
commit 4cf92970df
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=9837
1 changed files with 12 additions and 14 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

26
en_US.ISO8859-1/articles/formatting-media/article.sgml
View file

@ -2,7 +2,7 @@
<!ENTITY % man PUBLIC "-//FreeBSD//ENTITIES DocBook Manual Page Entities//EN">
%man;
]>
<!-- $FreeBSD: doc/en_US.ISO8859-1/articles/formatting-media/article.sgml,v 1.16 2001/06/04 03:04:38 grog Exp $ -->
<!-- $FreeBSD: doc/en_US.ISO8859-1/articles/formatting-media/article.sgml,v 1.17 2001/07/11 13:05:44 nik Exp $ -->
<article>
<articleinfo>
<title>Formatting Media For Use With FreeBSD</title>
@ -128,7 +128,7 @@ now. -->
composed of contiguous sectors. Slices are recorded in a
<quote>slice table</quote> used by the system BIOS to
locate bootable partitions. The slice table is usually
called the Partition Table in DOS parlance. Maintained by
called the <quote>partition table</quote> in DOS parlance. Maintained by
the fdisk utility.</para>
</listitem>
@ -256,7 +256,7 @@ drive(s)?</screen>
</step>
<step>
<para>When warned about Writing on installed systems, answer
<para>When warned about writing on installed systems, answer
<command>Yes</command>.</para>
</step>
@ -280,7 +280,7 @@ drive(s)?</screen>
<step>
<para>Enter <command>W</command> when done and confirm to
continue. The filesystem will be newfs'd for you, unless
you select otherwise (for news partitions you'll want to
you select otherwise (for new partitions you'll want to
do this!). You'll get the error:
<informalexample>
@ -300,7 +300,7 @@ drive(s)?</screen>
<sect2>
<title>Making Dedicated Mode Disks Using the Command Line</title>
<para>Execute the following commands, replacing ad2 with the
<para>Execute the following commands, replacing <devicename>ad2</devicename> with the
disk name.</para>
<informalexample>
@ -334,7 +334,7 @@ drive(s)?</screen>
<para>The command line is the easiest way to make dedicated
disks, and the worst way to make compatibility disks. The
command-line fdisk utility requires higher math skills and an
command-line <command>fdisk</command> utility requires higher math skills and an
in-depth understanding of the slice table, which is more than
most people want to deal with. Use sysinstall for
compatibility disks, as described below.</para>
@ -416,7 +416,7 @@ drive(s)?</screen>
<step>
<para>The filesystem will be newfs'd for you, unless you
select otherwise (for news partitions you'll want to do
select otherwise (for new partitions you'll want to do
this!). You'll get the error:
<informalexample>
@ -472,7 +472,7 @@ drive(s)?</screen>
</programlisting>
</informalexample>
<para>Change /dev/ad0b to the device of the newly added
<para>Change <filename>/dev/ad0b</filename> to the device of the newly added
space.</para>
</step>
@ -577,13 +577,11 @@ swapon: added /dev/da0b as swap space</screen>
be at least 128 kB, and it should not be not be a power of 2.</para>
<para>Now you can mount and use your CCD by referencing device
/dev/ccd0c.</para>
<para>
A more powerful and flexible alternative to CCD is Vinum. See the <ulink
URL="http://www.vinumvm.org/">Vinum Project home page</ulink> for further
details
</para>
<filename>/dev/ccd0c</filename>.</para>
<para>A more powerful and flexible alternative to CCD is Vinum. See the
<ulink URL="http://www.vinumvm.org/">Vinum Project home page</ulink>
for further details.</para>
</sect2>
</sect1>