svn commit: r187069 - stable/7/sbin/fsck_ffs

[David O'Brien]

On Mon, Jan 12, 2009 at 12:39:22AM +0000, Xin LI wrote:
> Author: delphij
> Date: Mon Jan 12 00:39:22 2009
> New Revision: 187069
> URL: http://svn.freebsd.org/changeset/base/187069
> 
> Log:
>   MFC revisions 178088 and 179656: Catastrophic recovery mode.

Hi Xin,
I guess you missed my email to you about this.  I was hoping to get an
answer to this before it was MFC'ed.
The use of 'C' conflicts with a Juniper Networks change Juniper wants to
push back to FreeBSD.  

For Juniper the -C flag is the "clean" flag.  Meaning don't do anything
if the FS is clean, other wise do as full a fsck as possible (vs. just
a "preen" fsck).  It is useful as 'fsck -C -y /var' (for instance).

Do you think your functionality could live under the "-D" (damaged)
option?  fsck_ffs already had a "-c" option, or Juniper would have
used that letter.

-- 
-- David  (obrien at FreeBSD.org)
Q: Because it reverses the logical flow of conversation.
A: Why is top-posting (putting a reply at the top of the message) frowned upon?
Let's not play "Jeopardy-style quoting"