From: "Lukáš Czerner" <lczerner@redhat.com>
To: Phillip Susi <psusi@ubuntu.com>
Cc: Andreas Dilger <adilger@dilger.ca>, linux-ext4@vger.kernel.org
Subject: Re: [PATCH] mke2fs: don't interact with a non tty
Date: Wed, 19 Mar 2014 18:05:20 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.00.1403191758160.14658@localhost.localdomain> (raw)
In-Reply-To: <5329BFFA.1030308@ubuntu.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 2523 bytes --]
On Wed, 19 Mar 2014, Phillip Susi wrote:
> Date: Wed, 19 Mar 2014 12:04:10 -0400
> From: Phillip Susi <psusi@ubuntu.com>
> To: Lukáš Czerner <lczerner@redhat.com>
> Cc: Andreas Dilger <adilger@dilger.ca>, linux-ext4@vger.kernel.org
> Subject: Re: [PATCH] mke2fs: don't interact with a non tty
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 3/19/2014 11:16 AM, Lukáš Czerner wrote:
> > There was a discussion between me and Dave Chinner a while ago
> > about exactly this topic and he made some very good points. You as
> > a guy working with file system, or file system utilities, testing
> > them and so on will probably see a ton of the warning like that.
> > But like it, or not you're *not* the typical user - you're a
> > developer and there is a huge difference.
>
> Whether I'm a typical user or a developer does not matter. This is
> unix, and commands are expected to do what they are told. If you must
> do such silly things, at the very least you need to not break scripts
> when doing it, which means if stdin is not a tty, don't assume you are
> being run by an idiot who needs hand holding and do what you've been
> told to.
>
> Scripts and other tools like say, gparted, should not have to figure
> out every silly thing you might complain about and add a stupid
> - --yes-i-really-meant-it flag to every invocation.
You're wrong. It does matter, because the usage habits of those two
groups are entirely different and certainly mke2fs is not a tool
designed for developers.
It is a safety net for already overwhelmed sysadmins. And I do not
understand how this is breaking scripts - it has been like that for
a long time.
I agree that it is a bug that we're still asking question even though
there is not a tty attached, but as I said the right thing to do in
that case is to fail rather than blindly continue despite the checks.
If you want the latter, you can use the 'force' Luke :)
Thanks!
-Lukas
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.17 (MingW32)
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQEcBAEBAgAGBQJTKb/6AAoJEI5FoCIzSKrwefcIAIHJtyiquS/Zrs4LbCSW1Zoe
> 5QoLx1ROxqP/Y5CP9mMCcRfsOTXMtZWqf116/Hg5SgIbJ76FGn7peChfPAKw477W
> HFPWsUmWgdkdVRFJdqny/5MVaOHGd/bD9mt7/8suEwSXX3eAp/gDegKR9Srm+etY
> n7V/G/uHWQgUQDbs8GAAcpIMA4Y1zcARB19fdNMr1evhDORdN7PAFqxqbixz3gU6
> //ZnztB7mkDB+cDq9aEYIFR0NnUT8d1SlPR0K/S42Ygy/byP96PjFV+Fkcs7kUA3
> DlWUgJxC7hr5VnF/PxU11ydiU90NT6NmhRSz/0++tlgGQzNXnHuGMyTtvvHJj30=
> =BX1H
> -----END PGP SIGNATURE-----
>
next prev parent reply other threads:[~2014-03-19 17:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-18 17:11 [PATCH] mke2fs: don't interact with a non tty Phillip Susi
2014-03-18 18:31 ` Andreas Dilger
2014-03-18 18:47 ` Phillip Susi
2014-03-19 11:26 ` Lukáš Czerner
2014-03-19 13:35 ` Phillip Susi
2014-03-19 15:16 ` Lukáš Czerner
2014-03-19 16:04 ` Phillip Susi
2014-03-19 17:05 ` Lukáš Czerner [this message]
2014-03-19 17:37 ` Phillip Susi
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=alpine.LFD.2.00.1403191758160.14658@localhost.localdomain \
--to=lczerner@redhat.com \
--cc=adilger@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=psusi@ubuntu.com \
/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