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

Replace UNIX™' combination with the &unix;' entity.

Browse source 
Approved by:	des (mentor)
This commit is contained in:
Hiten Pandya 2003-06-12 21:35:02 +00:00
parent dd93911fd5
commit eba5eae438
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=17272
1 changed files with 9 additions and 9 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

18
en_US.ISO8859-1/books/handbook/vinum/chapter.sgml
View file

@ -275,7 +275,7 @@
<listitem> <listitem>
<para>The most visible object is the virtual disk, called a <para>The most visible object is the virtual disk, called a
<emphasis>volume</emphasis>. Volumes have essentially the same <emphasis>volume</emphasis>. Volumes have essentially the same
properties as a UNIX&trade; disk drive, though there are some minor properties as a &unix; disk drive, though there are some minor
differences. They have no size limitations.</para> differences. They have no size limitations.</para>
</listitem> </listitem>
@ -288,13 +288,13 @@
</listitem> </listitem>
<listitem> <listitem>
<para>Since Vinum exists within the UNIX&trade; disk storage <para>Since Vinum exists within the &unix; disk storage
framework, it would be possible to use UNIX&trade; framework, it would be possible to use &unix;
partitions as the building block for multi-disk plexes, partitions as the building block for multi-disk plexes,
but in fact this turns out to be too inflexible: but in fact this turns out to be too inflexible:
UNIX&trade; disks can have only a limited number of &unix; disks can have only a limited number of
partitions. Instead, Vinum subdivides a single partitions. Instead, Vinum subdivides a single
UNIX&trade; partition (the <emphasis>drive</emphasis>) &unix; partition (the <emphasis>drive</emphasis>)
into contiguous areas called into contiguous areas called
<emphasis>subdisks</emphasis>, which it uses as building <emphasis>subdisks</emphasis>, which it uses as building
blocks for plexes.</para> blocks for plexes.</para>
@ -302,7 +302,7 @@
<listitem> <listitem>
<para>Subdisks reside on Vinum <emphasis>drives</emphasis>, <para>Subdisks reside on Vinum <emphasis>drives</emphasis>,
currently UNIX&trade; partitions. Vinum drives can currently &unix; partitions. Vinum drives can
contain any number of subdisks. With the exception of a contain any number of subdisks. With the exception of a
small area at the beginning of the drive, which is used small area at the beginning of the drive, which is used
for storing configuration and state information, the for storing configuration and state information, the
@ -677,7 +677,7 @@
<para><anchor id="vinum-resilience">With sufficient hardware, it <para><anchor id="vinum-resilience">With sufficient hardware, it
is possible to build volumes which show both increased is possible to build volumes which show both increased
resilience and increased performance compared to standard resilience and increased performance compared to standard
UNIX&trade; partitions. A typical configuration file might &unix; partitions. A typical configuration file might
be:</para> be:</para>
<programlisting> <programlisting>
@ -875,7 +875,7 @@
<title>Creating File Systems</title> <title>Creating File Systems</title>
<para>Volumes appear to the system to be identical to disks, <para>Volumes appear to the system to be identical to disks,
with one exception. Unlike UNIX&trade; drives, Vinum does with one exception. Unlike &unix; drives, Vinum does
not partition volumes, which thus do not contain a partition not partition volumes, which thus do not contain a partition
table. This has required modification to some disk table. This has required modification to some disk
utilities, notably &man.newfs.8;, which previously tried to utilities, notably &man.newfs.8;, which previously tried to
@ -958,7 +958,7 @@ sd name bigraid.p0.s4 drive e plex bigraid.p0 state initializing len 4194304b dr
configuration information: it finds the drives by scanning configuration information: it finds the drives by scanning
the configured disk drives for partitions with a Vinum the configured disk drives for partitions with a Vinum
label. This enables Vinum to identify drives correctly even label. This enables Vinum to identify drives correctly even
if they have been assigned different UNIX&trade; drive if they have been assigned different &unix; drive
IDs.</para> IDs.</para>
<sect3 id="vinum-rc-startup"> <sect3 id="vinum-rc-startup">