From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: linux-xfs <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH 3/2] mkfs: manpage fixups in config file section
Date: Thu, 14 Jun 2018 09:43:25 -0700 [thread overview]
Message-ID: <20180614164325.GA8128@magnolia> (raw)
In-Reply-To: <bc2a4277-cbe2-c3e7-ad92-e2a67f9102cf@sandeen.net>
On Thu, Jun 14, 2018 at 10:43:37AM -0500, Eric Sandeen wrote:
> A bit more clarification in the CONFIGURATION FILE FORMAT
> section of the mkfs.xfs manpage.
>
> Primarily, map the commandline switches to the section names
> explicitly.
>
> "optional default" sounds pretty weird, so call it the
> "defaults" configuration file instead.
>
> Document the comment format by example.
>
> Fix the sparse inode default setting in the example.
>
> Change the .BI tags to .B (there is no bold/italic switching).
>
> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
> ---
>
> diff --git a/man/man8/mkfs.xfs.8.in b/man/man8/mkfs.xfs.8.in
> index cf4bdf8..9c0c1a8 100644
> --- a/man/man8/mkfs.xfs.8.in
> +++ b/man/man8/mkfs.xfs.8.in
> @@ -957,53 +957,61 @@ Do not attempt to discard blocks at mkfs time.
> .B \-V
> Prints the version number and exits.
> .SH CONFIGURATION FILE FORMAT
> -The optional default configuration file in
> +The optional defaults configuration file in
> .B @sysconfdir@/xfs/mkfs/default
> as well as any alternate configuration file specified via the
> .B \-c
> -option follow a simple ini-style format as shown below.
> -Available options consist of a small subset of the parameters available
> -via the
> -.BR mkfs.xfs (8)
> -command line.
> -Currently all default parameters can only be either enabled or disabled,
> +option follow a simple ini-style format as shown below, with section names
> +corresponding to command-line options as follows:
> +.BR "\-d [data]" ,
> +.BR "\-i [inode]" ,
> +.BR "\-l [log]" ,
> +.BR "\-m [metadata]" ,
> +.BR "\-n [naming]" ,
> +.BR "\-r [rtdev]" .
> +.br
> +In each of these sections, a subset of the command-line suboptions may be
> +specified to override built-in default settings.
> +Currently all parameters can only be either enabled or disabled,
> with a value of 1 to enable or 0 to disable.
> See below for a list of all supported configuration parameters and their
> current built-in default settings.
> .PP
> -.BI [data]
> +.B # Comments and blank lines are allowed
> +.br
> +.B [data]
> .br
> -.BI noalign=0
> +.B noalign=0
> .PP
> -.BI [inode]
> +.B [inode]
> .br
> -.BI align=1
> +.B align=1
> .br
> -.BI projid32bit=1
> +.B projid32bit=1
> .br
> -.BI sparse=0
> +.B sparse=1
> .PP
> -.BI [log]
> +.B [log]
> .br
> -.BI lazy-count=1
> +.B lazy-count=1
> .PP
> -.BI [metadata]
> +.B [metadata]
> .br
> -.BI crc=1
> +.B crc=1
> .br
> -.BI finobt=1
> +.B finobt=1
> .br
> -.BI rmapbt=0
> +.B rmapbt=0
> .br
> -.BI reflink=0
> +.B reflink=0
> .PP
> -.BI [naming]
> +.B [naming]
> .br
> -.BI ftype=1
> +.B ftype=1
> .PP
> -.BI [rtdev]
> +.B [rtdev]
> .br
> -.BI noalign=0
> +.B noalign=0
I would add a note that configuration files are still considered an
experimental feature. With that,
Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com>
--D
> .PP
> .SH SEE ALSO
> .BR xfs (5),
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2018-06-14 16:43 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-13 19:33 [PATCH 0/2] mkfs: 2 more fixes Eric Sandeen
2018-06-13 19:34 ` [PATCH 1/2] mkfs: initialize return value of parse_config_stream to success Eric Sandeen
2018-06-14 8:48 ` Carlos Maiolino
2018-06-14 16:20 ` Luis R. Rodriguez
2018-06-14 16:41 ` Darrick J. Wong
2018-06-13 19:37 ` [PATCH 2/2] mkfs: remove notion of config "type" Eric Sandeen
2018-06-14 9:46 ` Carlos Maiolino
2018-06-14 16:19 ` Luis R. Rodriguez
2018-06-14 16:40 ` Eric Sandeen
2018-06-14 16:41 ` Darrick J. Wong
2018-06-14 23:42 ` Dave Chinner
[not found] ` <CAB=NE6V7JmsPpkCB1zp0CuY5YTJvMonG7UJPjScKYVJZLWb3xg@mail.gmail.com>
2018-06-15 2:33 ` Dave Chinner
2018-06-15 2:45 ` Eric Sandeen
2018-06-16 0:17 ` Dave Chinner
2018-06-16 0:55 ` Eric Sandeen
2018-06-16 2:44 ` Dave Chinner
2018-06-16 4:35 ` cfg file versioning (was: [PATCH 2/2] mkfs: remove notion of config "type") Eric Sandeen
2018-06-14 15:43 ` [PATCH 3/2] mkfs: manpage fixups in config file section Eric Sandeen
2018-06-14 16:43 ` Darrick J. Wong [this message]
2018-06-14 16:20 ` [PATCH 4/2] mkfs: add -c option to the --help screen Darrick J. Wong
2018-06-14 16:34 ` Eric Sandeen
2018-06-14 16:49 ` Luis R. Rodriguez
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180614164325.GA8128@magnolia \
--to=darrick.wong@oracle.com \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@sandeen.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.