From owner-freebsd-doc@FreeBSD.ORG Thu Jan 10 12:30:03 2008 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DD5E116A4C1 for ; Thu, 10 Jan 2008 12:30:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id A1D1F13C442 for ; Thu, 10 Jan 2008 12:30:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m0ACU32L023546 for ; Thu, 10 Jan 2008 12:30:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m0ACU396023543; Thu, 10 Jan 2008 12:30:03 GMT (envelope-from gnats) Date: Thu, 10 Jan 2008 12:30:03 GMT Message-Id: <200801101230.m0ACU396023543@freefall.freebsd.org> To: freebsd-doc@FreeBSD.org From: Marc Silver Cc: Subject: Re: docs/113695: handbook suggests different lockfile than gbde(8) manpage X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Marc Silver List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Jan 2008 12:30:04 -0000 The following reply was made to PR docs/113695; it has been noted by GNATS. From: Marc Silver To: bug-followup@FreeBSD.org, billf@mu.org Cc: Subject: Re: docs/113695: handbook suggests different lockfile than gbde(8) manpage Date: Thu, 10 Jan 2008 14:22:19 +0200 --V88s5gaDVPzZ0KCq Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi there, I double checked this and /etc/rc.d/gbde does indeed look for a file that ends in ".lock". Furthermore, the rc.d script explicitly looks in /etc for a lockfile unless gbde_lockdir is explicitly set in /etc/rc.conf. Included is a patch that corrects the article as well as adding notes regarding the fact that GBDE lock files must end in .lock and adding mention of the gbde_lockdir override. With regards to the 'c' partition vs. the 'real' partition, I was able to set this up with the 'c' partition without any error, but since the guide states that the disk output should be used as a guideline I don't think this is too much of a trainsmash. Cheers, Marc --V88s5gaDVPzZ0KCq Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="gbde.patch" --- chapter.sgml.orig 2008-01-10 13:59:53.000000000 +0200 +++ chapter.sgml 2008-01-10 14:06:04.000000000 +0200 @@ -3566,7 +3566,7 @@ initialized before it can be used. This initialization needs to be performed only once: - &prompt.root; gbde init /dev/ad4s1c -i -L /etc/gbde/ad4s1c + &prompt.root; gbde init /dev/ad4s1c -i -L /etc/gbde/ad4s1c.lock &man.gbde.8; will open your editor, permitting you to set various configuration options in a template. For use with UFS1 @@ -3598,7 +3598,14 @@ The gbde init command creates a lock file for your gbde partition that in this example is stored as - /etc/gbde/ad4s1c. + /etc/gbde/ad4s1c.lock. + + + gbde lock files must end in + .lock in order to be correctly detected + by the gbde rc.d + script. + gbde lock files @@ -3616,7 +3623,7 @@ Attach the Encrypted Partition to the Kernel - &prompt.root; gbde attach /dev/ad4s1c -l /etc/gbde/ad4s1c + &prompt.root; gbde attach /dev/ad4s1c -l /etc/gbde/ad4s1c.lock You will be asked to provide the passphrase that you selected during the initialization of the encrypted partition. @@ -3693,7 +3700,7 @@ Attach the gbde Partition to the Kernel - &prompt.root; gbde attach /dev/ad4s1c -l /etc/gbde/ad4s1c + &prompt.root; gbde attach /dev/ad4s1c -l /etc/gbde/ad4s1c.lock You will be asked to provide the passphrase that you selected during initialization of the encrypted @@ -3734,7 +3741,8 @@ &man.rc.conf.5;, for example: gbde_autoattach_all="YES" -gbde_devices="ad4s1c" +gbde_devices="ad4s1c" +gbde_lockdir="/etc/gbde" This will require that the gbde passphrase be entered at boot time. After typing the correct --V88s5gaDVPzZ0KCq--