PERFORCE change 185706 for review

[Rene Ladan]

http://p4web.freebsd.org/@@185706?ac=10

Change 185706 by rene at rene_acer on 2010/11/12 20:49:17

	Cleanup of the vinum chapter.

Affected files ...

.. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/vinum/chapter.sgml#5 edit

Differences ...

==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/vinum/chapter.sgml#5 (text+ko) ====

@@ -766,16 +766,6 @@
 
     <itemizedlist>
       <listitem>
-        <note><para>This only applies to the historic Vinum
-	implemenation.</para></note>
-
-	<para>The control devices
-	  <filename class="devicefile">/dev/vinum/control</filename> and
-	  <filename class="devicefile">/dev/vinum/controld</filename>, which are used
-	  by &man.gvinum.8; and the Vinum daemon respectively.</para>
-      </listitem>
-
-      <listitem>
 	<para>Device entries for each volume.
 	  These are the main devices used by Vinum.  Thus the configuration
 	  above would include the devices
@@ -787,15 +777,6 @@
       </listitem>
 
       <listitem>
-        <note><para>This only applies to the historic Vinum
-	implemenation.</para></note>
-
-	<para>A directory <filename class="directory">/dev/vinum/drive</filename>
-	  with entries for each drive.  These entries are in fact
-	  symbolic links to the corresponding disk nodes.</para>
-      </listitem>
-
-      <listitem>
 	<para>All volumes get direct entries under
 	  <filename class="directory">/dev/gvinum/</filename>.</para>
       </listitem>
@@ -877,13 +858,6 @@
 	  &man.newfs.8;:</para>
 
 	<screen>&prompt.root; <userinput>newfs /dev/gvinum/concat</userinput></screen>
-
-	<note><para>On &os; versions prior to 5.0 &man.newfs.8; requires
-	    an additional <option>-v</option> flag and the old device naming
-	    scheme:</para>
-
-	<screen>&prompt.root; <userinput>newfs -v /dev/vinum/concat</userinput></screen></note>
-
     </sect2>
   </sect1>
   
@@ -943,29 +917,15 @@
       <sect3 id="vinum-rc-startup">
 	<title>Automatic Startup</title>
 
-	<note><para>This information only relates to the historic
-	Vinum implementation.  <emphasis>Gvinum</emphasis> always
+	<para>
+	<emphasis>Gvinum</emphasis> always
 	features an automatic startup once the kernel module is
 	loaded, via &man.loader.conf.5;.  To load the
 	<emphasis>Gvinum</emphasis> module at boot time, add
 	<literal>geom_vinum_load="YES"</literal> to
-	<filename>/boot/loader.conf</filename>.</para></note>
+	<filename>/boot/loader.conf</filename>.</para>
 
-        <para>In order to start Vinum automatically when you boot the
-	  system, ensure that you have the following line in your
-	  <filename>/etc/rc.conf</filename>:</para>
-
-	<programlisting>start_vinum="YES"		# set to YES to start vinum</programlisting>
-
-	<para>If you do not have a file
-	  <filename>/etc/rc.conf</filename>, create one with this
-	  content.  This will cause the system to load the Vinum
-	  <acronym>kld</acronym> at startup, and to start any objects
-	  mentioned in the configuration.  This is done before
-	  mounting file systems, so it is possible to automatically
-	  &man.fsck.8; and mount file systems on Vinum volumes.</para>
-
-	<para>When you start Vinum with the <command>vinum
+	<para>When you start Vinum with the <command>gvinum
 	  start</command> command, Vinum reads the configuration
 	  database from one of the Vinum drives.  Under normal
 	  circumstances, each drive contains an identical copy of the
@@ -1040,39 +1000,10 @@
 	</listitem>
 
 	<listitem>
-	  <note><para>For <emphasis>Gvinum</emphasis>, all startup
+	  <para>For <emphasis>Gvinum</emphasis>, all startup
 	  is done automatically once the kernel module has been
 	  loaded, so the procedure described above is all that is
-	  needed.  The following text documents the behaviour of
-	  the historic Vinum system, for the sake of older
-	  setups.</para></note>
-
-	  <para>Vinum must be initialized early since it needs to
-	    supply the volume for the root filesystem.	By default,
-	    the Vinum kernel part is not looking for drives that might
-	    contain Vinum volume information until the administrator
-	    (or one of the startup scripts) issues a <command>vinum
-	    start</command> command.</para>
-
-	  <note><para>The following paragraphs are outlining the steps
-	    needed for &os;.</para></note>
-
-	  <para>By placing the line:</para>
-
-	  <programlisting>vinum.autostart="YES"</programlisting>
-
-	  <para>into <filename>/boot/loader.conf</filename>, Vinum is
-	    instructed to automatically scan all drives for Vinum
-	    information as part of the kernel startup.</para>
-
-	  <para>Note that it is not necessary to instruct the kernel
-	    where to look for the root filesystem.
-	    <filename>/boot/loader</filename> looks up the name of the
-	    root device in <filename>/etc/fstab</filename>, and passes
-	    this information on to the kernel.	When it comes to mount
-	    the root filesystem, the kernel figures out from the
-	    device name provided which driver to ask to translate this
-	    into the internal device ID (major/minor number).</para>
+	  needed.</para>
 	</listitem>
       </itemizedlist>
     </sect2>