From owner-p4-projects@FreeBSD.ORG Fri Nov 12 20:49:20 2010 Return-Path: Delivered-To: p4-projects@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 32767) id C48AF1065672; Fri, 12 Nov 2010 20:49:19 +0000 (UTC) Delivered-To: perforce@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 868AC106564A for ; Fri, 12 Nov 2010 20:49:19 +0000 (UTC) (envelope-from rene@FreeBSD.org) Received: from skunkworks.freebsd.org (skunkworks.freebsd.org [IPv6:2001:4f8:fff6::2d]) by mx1.freebsd.org (Postfix) with ESMTP id 69D668FC08 for ; Fri, 12 Nov 2010 20:49:19 +0000 (UTC) Received: from skunkworks.freebsd.org (localhost [127.0.0.1]) by skunkworks.freebsd.org (8.14.4/8.14.4) with ESMTP id oACKnJ5Y043152 for ; Fri, 12 Nov 2010 20:49:19 GMT (envelope-from rene@FreeBSD.org) Received: (from perforce@localhost) by skunkworks.freebsd.org (8.14.4/8.14.4/Submit) id oACKnJpw043149 for perforce@freebsd.org; Fri, 12 Nov 2010 20:49:19 GMT (envelope-from rene@FreeBSD.org) Date: Fri, 12 Nov 2010 20:49:19 GMT Message-Id: <201011122049.oACKnJpw043149@skunkworks.freebsd.org> X-Authentication-Warning: skunkworks.freebsd.org: perforce set sender to rene@FreeBSD.org using -f From: Rene Ladan To: Perforce Change Reviews Precedence: bulk Cc: Subject: PERFORCE change 185706 for review X-BeenThere: p4-projects@freebsd.org X-Mailman-Version: 2.1.5 List-Id: p4 projects tree changes List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Nov 2010 20:49:20 -0000 http://p4web.freebsd.org/@@185706?ac=10 Change 185706 by rene@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 @@ - This only applies to the historic Vinum - implemenation. - - The control devices - /dev/vinum/control and - /dev/vinum/controld, which are used - by &man.gvinum.8; and the Vinum daemon respectively. - - - 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 @@ - This only applies to the historic Vinum - implemenation. - - A directory /dev/vinum/drive - with entries for each drive. These entries are in fact - symbolic links to the corresponding disk nodes. - - - All volumes get direct entries under /dev/gvinum/. @@ -877,13 +858,6 @@ &man.newfs.8;: &prompt.root; newfs /dev/gvinum/concat - - On &os; versions prior to 5.0 &man.newfs.8; requires - an additional flag and the old device naming - scheme: - - &prompt.root; newfs -v /dev/vinum/concat - @@ -943,29 +917,15 @@ Automatic Startup - This information only relates to the historic - Vinum implementation. Gvinum always + + Gvinum always features an automatic startup once the kernel module is loaded, via &man.loader.conf.5;. To load the Gvinum module at boot time, add geom_vinum_load="YES" to - /boot/loader.conf. + /boot/loader.conf. - In order to start Vinum automatically when you boot the - system, ensure that you have the following line in your - /etc/rc.conf: - - start_vinum="YES" # set to YES to start vinum - - If you do not have a file - /etc/rc.conf, create one with this - content. This will cause the system to load the Vinum - kld 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. - - When you start Vinum with the vinum + When you start Vinum with the gvinum start 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 @@ - For Gvinum, all startup + For Gvinum, 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. - - 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 vinum - start command. - - The following paragraphs are outlining the steps - needed for &os;. - - By placing the line: - - vinum.autostart="YES" - - into /boot/loader.conf, Vinum is - instructed to automatically scan all drives for Vinum - information as part of the kernel startup. - - Note that it is not necessary to instruct the kernel - where to look for the root filesystem. - /boot/loader looks up the name of the - root device in /etc/fstab, 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). + needed.