Trashed a UFS2 file system from 4.8-Release

Ok, I'm a big loser, and for some reason I thought that I should be able
to fsck and mount a 5.0-Current UFS2 file system from 4.8-Release. Now I
know you can't do that. :)

So, the question is, if RELENG_4 fsck doesn't grok UFS2 file systems, why
did it try to fsck it? Shouldn't it just give up when it realizes that
it's not a UFS1 fs?

Doug

-- 

    This .signature sanitized for your protection