fsck: exits 0 with no output (just version) when it doesn't find a type-specific fsck

I'm sure it ain't news to you that this is upstream's behaviour.
IIRC done/necessary for compatibility reasons.


If you care enough, please report upstream and see if they want to
change it.

I consider this not a bug for the reasons above.

Reply via email to