> Yuck.  but I guess thats what happens since the fscks are individual
> programs written by people who don't care to maintain a common API.  Even
> the yes|fsck is not guaranteed to work on everything in that case.
>
> When this is actually an issue for anyone, we should probably have the fsck
> code look at what the filesystem type is and explicitly call the correct fs
> specific fsck with the appropriate options.

Yup, if we can't work out a common method, we can absolutely do that.
_______________________________________________
Autotest mailing list
[email protected]
http://test.kernel.org/cgi-bin/mailman/listinfo/autotest

Reply via email to