From: Karel Zak <kzak@redhat.com>
To: kerolasa@gmail.com
Cc: "Dale R. Worley" <worley@alum.mit.edu>,
"Theodore Ts'o" <tytso@mit.edu>,
util-linux <util-linux@vger.kernel.org>
Subject: Re: Typo in mkfs man-page
Date: Tue, 11 Feb 2014 10:22:19 +0100 [thread overview]
Message-ID: <20140211092219.GT8506@x2.net.home> (raw)
In-Reply-To: <CAG27Bk09kBXQ3B1Vtm6oDxw2iyqvsYbj9uYyGTdBgfLnLAvtsg@mail.gmail.com>
On Tue, Feb 11, 2014 at 09:05:32AM +0000, Sami Kerola wrote:
> On 10 February 2014 20:55, Dale R. Worley <worley@alum.mit.edu> wrote:
> >> From: "Theodore Ts'o" <tytso@mit.edu>
> >
> >> 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".
> >
> > This makes sense to me.
> >
> > More exactly, mkfs is generally run "manually".
> >
> > And while having fsck "do what I mean" is largely safe, creating a
> > file system is not the time that you want the user to be unclear on
> > the exact implications of each option he has specified.
>
> Would it make sense to add banner 'you probably should not run this
> utility, consider using file system specific mkfs' to mkfs?
And mark it deprecated and one day kill it at all.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2014-02-11 9:22 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
2014-02-10 20:55 ` Dale R. Worley
2014-02-11 9:05 ` Sami Kerola
2014-02-11 9:22 ` Karel Zak [this message]
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=20140211092219.GT8506@x2.net.home \
--to=kzak@redhat.com \
--cc=kerolasa@gmail.com \
--cc=tytso@mit.edu \
--cc=util-linux@vger.kernel.org \
--cc=worley@alum.mit.edu \
/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