linux-ext4 - Re: [PATCH 3/5] e2fsck: print a notice when we've started suppressing a problem code

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <2A65740A-4C62-4817-8C96-728C5EB75FA3@dilger.ca>
Date:	Mon, 19 Mar 2012 16:43:10 -0600
From:	Andreas Dilger <adilger@...ger.ca>
To:	Ted Ts'o <tytso@....edu>
Cc:	Ext4 Developers List <linux-ext4@...r.kernel.org>
Subject: Re: [PATCH 3/5] e2fsck: print a notice when we've started suppressing a problem code

On 2012-03-18, at 6:25 PM, Ted Ts'o wrote:
> On Sun, Mar 18, 2012 at 05:17:20PM -0600, Andreas Dilger wrote:
>> 
>> Did a patch ever land to allow an interactive e2fsck run to set
>> a sticky answer (y/n) for a particular problem?  I know it has
>> been proposed several times.
> 
> It's been proposed but I don't think anyone has ever coded it.

There was the patch at: http://marc.info/?t=118597336000002&r=1&w=2
but I think the objection was that the "yes-to-all" and "no-to-all"
answers "A" and "O" were confusing for non-english speakers ("Oui",
for example).

However, I agree with the approach, and forcing a longer answer for
such a case like "yes-to-all" or "no-to-all" (or foreign equivalents)
is probably OK.

Cheers, Andreas





--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html