xfs
[Top] [All Lists]

[PATCH] mkfs.xfs: clarify ftype defaults in manpage

To: xfs-oss <xfs@xxxxxxxxxxx>, linux-xfs@xxxxxxxxxxxxxxx
Subject: [PATCH] mkfs.xfs: clarify ftype defaults in manpage
From: Eric Sandeen <sandeen@xxxxxxxxxx>
Date: Fri, 16 Sep 2016 15:48:14 -0500
Cc: Chris Murphy <chris@xxxxxxxxx>
Delivered-to: xfs@xxxxxxxxxxx
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.3.0
When CRCs were made default, a few leftovers related to its
prior non-default status remained in the manpage, in the ftype
section.  Clean those up.

Reported-by: Chris Murphy <chris@xxxxxxxxx>
Signed-off-by: Eric Sandeen <sandeen@xxxxxxxxxx>
---

diff --git a/man/man8/mkfs.xfs.8 b/man/man8/mkfs.xfs.8
index 9578c4d..033bc36 100644
--- a/man/man8/mkfs.xfs.8
+++ b/man/man8/mkfs.xfs.8
@@ -636,13 +636,13 @@ do not need to look up the inode to determine the inode 
type.
 
 The
 .I value
-is either 0 or 1, with 1 signifiying that filetype information
-will be stored in the directory structure. The default value is 0.
+is either 0 or 1, with 1 signifying that filetype information
+will be stored in the directory structure.
 
-When CRCs are enabled via
-.B \-m crc=1,
-the ftype functionality is always enabled. This feature can not be turned
-off for such filesystem configurations.
+When CRCs are enabled (the default), the ftype functionality is always
+enabled, and cannot be turned off. If CRCs are disabled with
+.B \-m crc=0,
+the ftype functionality is disabled by default.
 .IP
 .RE
 .TP


<Prev in Thread] Current Thread [Next in Thread>