doc-el commit 1017:6898cd12c671 - Replaced english text of 'vinu...

[freebsd-doc-el at lists.hellug.gr]

changeset: 1017:6898cd12c671
user:      Manolis Kiagias <sonicy at otenet.gr>
date:      2008-11-06 16:44 +0200
details:   http://hg.hellug.gr/freebsd/doc-el/?cmd=changeset;node=6898cd12c671

description:
	Replaced english text of 'vinum' chapter with rev. 1.45 (no changes in synopsis)

diffstat:

1 file changed, 2 insertions(+), 73 deletions(-)
el_GR.ISO8859-7/books/handbook/vinum/chapter.sgml |   75 ---------------------

diffs (99 lines):

diff -r 0b3f811345fb -r 6898cd12c671 el_GR.ISO8859-7/books/handbook/vinum/chapter.sgml
--- a/el_GR.ISO8859-7/books/handbook/vinum/chapter.sgml	Thu Nov 06 16:38:54 2008 +0200
+++ b/el_GR.ISO8859-7/books/handbook/vinum/chapter.sgml	Thu Nov 06 16:44:24 2008 +0200
@@ -12,7 +12,7 @@
   $FreeBSD: doc/el_GR.ISO8859-7/books/handbook/vinum/chapter.sgml,v 1.2 2008/01/14 14:19:47 keramida Exp $
 
   %SOURCE%	en_US.ISO8859-1/books/handbook/vinum/chapter.sgml
-  %SRCID%	1.1
+  %SRCID%	1.45
 
 -->
 
@@ -1059,9 +1059,7 @@
 	    start</command> command.</para>
 
 	  <note><para>The following paragraphs are outlining the steps
-	    needed for FreeBSD 5.X and above.  The setup required for
-	    FreeBSD 4.X differs, and is described below in <xref
-	    linkend="vinum-root-4x">.</para></note>
+	    needed for FreeBSD.</para></note>
 
 	  <para>By placing the line:</para>
 
@@ -1372,75 +1370,6 @@
 	  bootstrap no longer collide.</para>
       </sect3>
     </sect2>
-
-    <sect2 id="vinum-root-4x">
-      <title>Differences for FreeBSD 4.X</title>
-
-      <para>Under FreeBSD 4.X, some internal functions required to
-	make Vinum automatically scan all disks are missing, and the
-	code that figures out the internal ID of the root device is
-	not smart enough to handle a name like
-	<filename>/dev/vinum/root</filename> automatically.
-	Therefore, things are a little different here.</para>
-
-      <para>Vinum must explicitly be told which disks to scan, using a
-	line like the following one in
-	<filename>/boot/loader.conf</filename>:</para>
-
-      <programlisting>vinum.drives="/dev/<replaceable>da0</replaceable> /dev/<replaceable>da1</replaceable>"</programlisting>
-
-      <para>It is important that all drives are mentioned that could
-	possibly contain Vinum data.  It does not harm if
-	<emphasis>more</emphasis> drives are listed, nor is it
-	necessary to add each slice and/or partition explicitly, since
-	Vinum will scan all slices and partitions of the named drives
-	for valid Vinum headers.</para>
-
-      <para>Since the routines used to parse the name of the root
-	filesystem, and derive the device ID (major/minor number) are
-	only prepared to handle <quote>classical</quote> device names
-	like <filename>/dev/ad0s1a</filename>, they cannot make
-	any sense out of a root volume name like
-	<filename>/dev/vinum/root</filename>.  For that reason,
-	Vinum itself needs to pre-setup the internal kernel parameter
-	that holds the ID of the root device during its own
-	initialization.	 This is requested by passing the name of the
-	root volume in the loader variable
-	<literal>vinum.root</literal>.	The entry in
-	<filename>/boot/loader.conf</filename> to accomplish this
-	looks like:</para>
-
-      <programlisting>vinum.root="root"</programlisting>
-
-      <para>Now, when the kernel initialization tries to find out the
-	root device to mount, it sees whether some kernel module has
-	already pre-initialized the kernel parameter for it.  If that
-	is the case, <emphasis>and</emphasis> the device claiming the
-	root device matches the major number of the driver as figured
-	out from the name of the root device string being passed (that
-	is, <literal>"vinum"</literal> in our case), it will use the
-	pre-allocated device ID, instead of trying to figure out one
-	itself.	 That way, during the usual automatic startup, it can
-	continue to mount the Vinum root volume for the root
-	filesystem.</para>
-
-      <para>However, when <command>boot -a</command> has been
-	requesting to ask for entering the name of the root device
-	manually, it must be noted that this routine still cannot
-	actually parse a name entered there that refers to a Vinum
-	volume.  If any device name is entered that does not refer to
-	a Vinum device, the mismatch between the major numbers of the
-	pre-allocated root parameter and the driver as figured out
-	from the given name will make this routine enter its normal
-	parser, so entering a string like
-	<literal>ufs:da0d</literal> will work as expected. Note
-	that if this fails, it is however no longer possible to
-	re-enter a string like <literal>ufs:vinum/root</literal>
-	again, since it cannot be parsed.  The only way out is to
-	reboot again, and start over then.  (At the
-	<quote>askroot</quote> prompt, the initial
-	<filename>/dev/</filename> can always be omitted.)</para>
-    </sect2>
   </sect1>
 </chapter>