Re: ext3 corruption
From: Molle Bestefich
Date: Sun Aug 13 2006 - 15:18:56 EST
Theodore Tso wrote:
Well, the e2fsck man page isn't intended to be a tutorial. If someone
wants to volunteer to write an extended introduction to how e2fsck
works and what all of the messages mean, I'd certainly be willing to
work with that person... So if you're willing to volunteer
I'd love to help others with the same problem that I have. I know
basically nothing of e2fsck though, and I don't have time to research
and write a whole tutorial. Maybe there's a wiki somewhere where I
can start something out with a structure and some information
regarding the stuff I've seen?
or willing to chip in to pay for a technical writer, let me know....
What kind of economic scale where you thinking about?
(This is open source, which means if people who have the bad manners
to kvetch that volunteers have done all of this free work for them
haven't done $FOO will be gently reminded that patches to implement
$FOO are always welcome. :-)
OTOH, the open source community rigorously PR Linux as an alternative
While the above attitude is fine by me, you're going to have to expect
to see some sad faces from Windows users when they create a filesystem
on a loop device and don't realize that the loop driver destroys
journaling expectancies and results in all their photos and home
videos going down the drain, all because nobody implemented a simple
"warning!" message in the software.
(Or whatever. Lots of similar examples exist to show you that the "no
warranty: you use our software, you learn to hack it to do what you
want yourself or it's your own fault" argument is fallacious.)
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/