public inbox for util-linux@vger.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: Karel Zak <kzak@redhat.com>
Cc: Kenny Rachuonyo <krmboya@gmail.com>, util-linux@vger.kernel.org
Subject: Re: Typo in mkfs man-page
Date: Mon, 10 Feb 2014 13:57:41 -0500	[thread overview]
Message-ID: <20140210185741.GF4724@thunk.org> (raw)
In-Reply-To: <20140210173545.GK8506@x2.net.home>

On Mon, Feb 10, 2014 at 06:35:45PM +0100, Karel Zak wrote:
> On Wed, Jan 22, 2014 at 10:38:31AM +0300, Kenny Rachuonyo wrote:
> > The short form of the --verbose option should probably be -v instead of -V
> > 
> > This occurs both on the online man-page:
> > 
> > http://man7.org/linux/man-pages/man8/mkfs.8.html
> > 
> > and my local system (Ubuntu 12.04) man-page.
> 
>  I think this historical mess is well explained in the man page. 

I'll add that I've never been convinced that the mkfs front end is all
that useful.  It's probably better for people to explicitly run
/sbin/mkfs.xfs, /sbin/mkfs.ext4, etc.., so you don't have to worry
about which options get passed down to the file system specific mkfs
program, and which ones are interpreted by /sbin/mkfs --- and I don't
believe /sbin/mkfs adds enough (err, any?) value that using
"/sbin/mkfs -t xxx" vs "/sbin/mkfs.xxx" makes any sense whatsoever.

At least with /sbin/fsck it runs multiple fsck programs in parallel,
and it serves as a front-end program so you don't have to modify the
init scripts if you change your root file system from reiserfs to jfs,
while keeping some of your other file systems as minixfs.  So
/sbin/fsck adds value.

But /sbin/mkfs.xxx is generally run by system administrators, and IMHO
it's better to tell people to run the command "/sbin/mkfs.xxx" instead
of "/sbin/mkfs -t xxx".

Cheers,

					- Ted

  reply	other threads:[~2014-02-10 18:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-22  7:38 Typo in mkfs man-page Kenny Rachuonyo
2014-02-10 17:35 ` Karel Zak
2014-02-10 18:57   ` Theodore Ts'o [this message]
2014-02-10 20:55     ` Dale R. Worley
2014-02-11  9:05       ` Sami Kerola
2014-02-11  9:22         ` Karel Zak
2014-02-12 20:13         ` Dale R. Worley
2014-02-21 11:07     ` Karel Zak

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=20140210185741.GF4724@thunk.org \
    --to=tytso@mit.edu \
    --cc=krmboya@gmail.com \
    --cc=kzak@redhat.com \
    --cc=util-linux@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox