From: Eric Sandeen <sandeen@redhat.com>
To: Ric Wheeler <rwheeler@redhat.com>
Cc: Theodore Tso <tytso@mit.edu>,
ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: e2fsck -y says "yes" to "Abort?"
Date: Mon, 20 Apr 2009 13:33:31 -0500 [thread overview]
Message-ID: <49ECBFFB.2050004@redhat.com> (raw)
In-Reply-To: <49ECBF08.6030806@redhat.com>
Ric Wheeler wrote:
> The only down side is when you try to automate this (say in an
> appliance) and you don't have a human reading the output. In this case,
> you might just want to invert the logic but in general, it does seem
> dangerous to invert the logic for a long standing option,
>
> Ric
>
Maybe make something like "-yy" automatically answer "n" to anything
that would stop the fsck, and answer "y" to anything that it proposes
fixing?
-Eric
next prev parent reply other threads:[~2009-04-20 18:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-18 14:10 e2fsck -y says "yes" to "Abort?" Eric Sandeen
2009-04-18 16:17 ` Theodore Tso
2009-04-20 18:29 ` Ric Wheeler
2009-04-20 18:33 ` Eric Sandeen [this message]
2009-04-20 18:38 ` Ric Wheeler
2009-04-20 20:47 ` Andreas Dilger
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=49ECBFFB.2050004@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=rwheeler@redhat.com \
--cc=tytso@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;
as well as URLs for NNTP newsgroup(s).