On Fri, Oct 7, 2011 at 11:07 AM, Jeff Putney <jeffrey.put...@gmail.com> wrote:
> You jest, but in fact that is the result you've achieved, through
> conspiring or not.
>
> Do you honestly believe that had the source been public from the
> start, that after a year there would still be no quality fsck tool?
> Contributions are, de facto, blocked.
> Had there not been repeated promise of an fsck utility for the last
> year, do you honestly believe no one else would have begun
> development?  Call it under your thumb if you'd like, but you'll argue
> these declarations didn't have a stifling effect in vain.

Heh, what sort of "quality" are you thinking would develop?  A
recovery tool by its nature is picking up the pieces where those
pieces are inconsistent.  The nature of those inconsistencies will
change with every patch that's more than a cleanup.

Combined with the well-known tendencies of users to not report errors
that are trivial to work around, and I find myself quite content with
the status quo:  a few general recovery techniques that can be found
with some digging, inconvenient enough that the reports don't get
lost, with enough context that the appropriate warnings and
alternatives can be given.

Yes, a deliberately broken-by-makefile version of what he's looking at
would be interesting, but I suspect it's not much past what any
competent programmer would put together given a couple weeks going
over the disk format, and we already have a couple of those.  What we
want is still in Chris' head, otherwise we _would_ have something.

--cwillu

Warning: while cwillu is never "wrong", he may not correspond to
reality.  cwillu should not be taken with caffeine or alcohol.
Contact a doctor immediately if cwillu submits patches, rants, or
directives.  Do not leave cwillu within reach of children or
ubuntuforums users.  Always make sufficient backups before taking
cwillu.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to