From owner-svn-doc-head@FreeBSD.ORG Tue Feb 12 03:20:48 2013 Return-Path: Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id DC8A99B7; Tue, 12 Feb 2013 03:20:48 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-2.mit.edu (DMZ-MAILSEC-SCANNER-2.MIT.EDU [18.9.25.13]) by mx1.freebsd.org (Postfix) with ESMTP id 53C9EF3D; Tue, 12 Feb 2013 03:20:48 +0000 (UTC) X-AuditID: 1209190d-b7fa66d0000008f6-10-5119b3dd060c Received: from mailhub-auth-4.mit.edu ( [18.7.62.39]) by dmz-mailsec-scanner-2.mit.edu (Symantec Messaging Gateway) with SMTP id 38.48.02294.DD3B9115; Mon, 11 Feb 2013 22:15:41 -0500 (EST) Received: from outgoing.mit.edu (OUTGOING-AUTH-1.MIT.EDU [18.9.28.11]) by mailhub-auth-4.mit.edu (8.13.8/8.9.2) with ESMTP id r1C3Fej9002655; Mon, 11 Feb 2013 22:15:40 -0500 Received: from multics.mit.edu (SYSTEM-LOW-SIPB.MIT.EDU [18.187.2.37]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id r1C3FcRP004571 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 11 Feb 2013 22:15:40 -0500 Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id r1C3FcrH029599; Mon, 11 Feb 2013 22:15:38 -0500 (EST) Date: Mon, 11 Feb 2013 22:15:38 -0500 (EST) From: Benjamin Kaduk To: Dru Lavigne Subject: Re: svn commit: r40946 - head/en_US.ISO8859-1/books/handbook/geom In-Reply-To: <201302111450.r1BEoXIR033682@svn.freebsd.org> Message-ID: References: <201302111450.r1BEoXIR033682@svn.freebsd.org> User-Agent: Alpine 1.10 (GSO 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrAIsWRmVeSWpSXmKPExsUixG6nrnt3s2SgQdNNFosfHw8xWXQ1qVrc WLSfyWJ3fy+zA4vHjE/zWQIYo7hsUlJzMstSi/TtErgyrkxsZCx4bFmx/sw25gbGS7pdjJwc EgImEvuuf2OGsMUkLtxbz9bFyMUhJLCPUWL5ky9gCSGBjYwSt/+UQCQOMUm8W9TCDuE0MEpM 6n7F0sXIwcEioC1x8qcUSAObgIrEzDcb2UBsEQFFiadf9zKC2MwCURJ7ljaygtjCAl4Sv95O YwGxOQWsJP7dXQ0W5xVwkLiyZDsLxGJLiQsXdoH1igroSKzeP4UFokZQ4uTMJywQMy0l/q39 xTqBUXAWktQsJKkFjEyrGGVTcqt0cxMzc4pTk3WLkxPz8lKLdI30cjNL9FJTSjcxggKWU5J3 B+O7g0qHGAU4GJV4eBtEJQOFWBPLiitzDzFKcjApifJe3ggU4kvKT6nMSCzOiC8qzUktPsQo wcGsJMK77KNEoBBvSmJlVWpRPkxKmoNFSZz3SspNfyGB9MSS1OzU1ILUIpisDAeHkgTvtE1A QwWLUtNTK9Iyc0oQ0kwcnCDDeYCGPwWp4S0uSMwtzkyHyJ9iVJQS590MkhAASWSU5sH1whLK K0ZxoFeEeT+DVPEAkxFc9yugwUxAgzlzxEEGlyQipKQaGFdwmG/cNHPz3neZ32P2dW4wn6ao JVh6ser7Qd3T87TNzdMtLA3euO8tYPS/EnTsxrSrvJdfyMXvaOBOTK7SUJqerdvK21L2WatW 13jmnLRa3saDJotns82PnSD53K01rvhOtcUi0dLZAn6Bp9fNifo7t01v3/F5mZoM/yxF7bcW Lyn+mnC6VomlOCPRUIu5qDgRAMHIhG8DAwAA Cc: svn-doc-head@freebsd.org, svn-doc-all@freebsd.org, doc-committers@freebsd.org X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Feb 2013 03:20:48 -0000 On Mon, 11 Feb 2013, Dru Lavigne wrote: > Author: dru > Date: Mon Feb 11 14:50:33 2013 > New Revision: 40946 > URL: http://svnweb.freebsd.org/changeset/doc/40946 > > Log: > This patch addresses the following: > > - fixes xref tags > > - some tightening and removing of redundancy > > - fixed some confusion in glabel section > > Approved by gjb (mentor) > > Modified: > head/en_US.ISO8859-1/books/handbook/geom/chapter.xml > > Modified: head/en_US.ISO8859-1/books/handbook/geom/chapter.xml > ============================================================================== > --- head/en_US.ISO8859-1/books/handbook/geom/chapter.xml Mon Feb 11 13:47:43 2013 (r40945) > +++ head/en_US.ISO8859-1/books/handbook/geom/chapter.xml Mon Feb 11 14:50:33 2013 (r40946) > @@ -35,11 +35,11 @@ > control utilities which use the framework for configuration. > This chapter will not go into in depth discussion on how GEOM > handles or controls I/O, the underlying subsystem, or code. > - This information is provided through the &man.geom.4; manual > - page and its various SEE ALSO references. This chapter is also > - not a definitive guide to RAID > - configurations. Only GEOM-supported RAID > - classifications will be discussed. > + This information is provided in &man.geom.4; and its various If memory serves, we are using (all over the place, not just here) man page entities to refer to both the man page and the program itself. That is potentially a source of confusion, though not necessarily something to tackle here. > + SEE ALSO references. This chapter is also > + not a definitive guide to RAID configurations > + and only GEOM-supported RAID classifications > + will be discussed. > > After reading this chapter, you will know: > > @@ -317,28 +316,28 @@ Done. > used to replace the old single disk. > > &man.gmirror.8; requires a kernel module, > - geom_mirror.ko, either built into the > - kernel or loaded at boot- or run-time. Manually load the > - kernel module now: > + geom_mirror.ko, either compiled into a > + custom kernel or loaded at boot- or run-time. To manually > + load the kernel module now: > > &prompt.root; gmirror load > > - Create the mirror with the two new drives. > + To create the mirror with the two new drives. This should end with a colon, not a full stop? > @@ -384,8 +383,8 @@ Done. > &prompt.root; newfs -U /dev/mirror/gm0s1e > &prompt.root; newfs -U /dev/mirror/gm0s1f > > - Filesystems from the original disk > - (ada0) can now be copied onto the > + Filesystems from the original I'm pretty sure Kirk and Bruce et all prefer "File systems" with a space, but it seems the NFSv4 guys are not having any of it (http://www.ietf.org/mail-archive/web/nfsv4/current/msg11661.html). > + ada0 disk can now be copied onto the > mirror with &man.dump.8; and &man.restore.8;. > > &prompt.root; mount /dev/mirror/gm0s1a /mnt > @@ -527,8 +526,8 @@ BSD 8 > 6 freebsd-ufs 130023424 838860800 > 7 freebsd-ufs 968884224 984640881 > > - If the whole disk was used in the output of &man.gpart.8; > - show, the capacity in these partition > + If the whole disk shows as used in the output of > + gpart show, the capacity in these partition (Warren's suggestion seems fine.) > tables must be reduced by one sector. Edit the two files, > reducing the size of both the slice and last partition by one. > These are the last numbers in each listing. > @@ -1010,8 +1000,8 @@ Done. > > 192.168.1.0/24 RW /dev/da0s4d > > - It will allow all hosts inside the private network access > - the file system on the da0s4d > + This allows all hosts inside the specified private network > + access to the file system on the da0s4d I think it would be "gives X access to" or "allows X to access", not "allows X access to" > partition. > > To export this device, ensure it is not currently mounted, > @@ -1258,9 +1236,9 @@ ufsid/486b6fc16926168e N/A ad4s1f /dev/ufsid/486b6fc16926168e /usr ufs rw 2 2 > > Any partitions with ufsid labels can be > - mounted in this way, eliminating the need to create permanent > - labels for them manually, while still enjoying the benefits of > - device-name independent mounting. > + mounted in this way, eliminating the need to manually create > + permanent labels, while still enjoying the benefits of device > + name independent mounting. I would put hyphens in here, but I tend to overuse hyphens in such cases. > > > > @@ -1332,12 +1309,11 @@ ufsid/486b6fc16926168e N/A ad4s1f > &prompt.root; newfs -O 2 -J /dev/da4.journal > > - The previously issued command will create a > - UFS2 file system on the journaled > - device. > + This command will creates a UFS2 file > + system on the journaled device. > > - Effectively mount the device at the > - desired point with: > + mount the device at the desired point Should this be "desired point" or "desired mount point"? > + with: > > &prompt.root; mount /dev/da4.journal /mnt > > @@ -1351,21 +1327,21 @@ ufsid/486b6fc16926168e N/A ad4s1f + For better performance, the journal may be kept on another > + disk. In this configuration, the journal provider or storage > + device should be listed after the device to enable journaling > + on. Journaling may also be enabled on current file systems by This sentence is pretty confusing. Perhaps "the provider or storage device dedicated to holding the journal itself should be listed after the device whose transactions will be logged in the journal."? Still a bit unwieldly, it seems.... > + using tunefs. However, I'm not sure what "current file systems" are. Are they ones that are mounted, or just an already extant filesystem? Thanks for all the updates. -Ben > + always make a backup before attempting to > + alter a file system. In most cases, gjournal > + will fail if it is unable to create the journal, but this does > + not protect against data loss incurred as a result of misusing > tunefs.