> > If this ext2fs check-w/-failure is happening at the "root on XXXX"
> > point AND it's actually figuring out that the partition's an
> > ffs partition, DON'T WORRY ABOUT IT! The kernel's just being chatty. 
> > If either it doesn't figure out the filesystem on that partition is an
> > ffs partition (or the ext2fs code chokes when it actually is an ext2fs
> > filesystem) (set accent=NewYork) _then_ you got problems.
> 
> Mm hmm.  Well, here's the exact message where it's choking...
> 
>   boot device: sd0
>   root on sd0a dumps on sd0b
>   PRAM: 0x35c6d762, macos_boottime: 0x35c6d756.
>   root file system type: ext2fs
>   bad directory entry: directory entry across blocks
>   offset=0, inode=167772160, rec_len=3072, name_len=256
>   panic: ext2fs_dirbadentry
>   Stopped at _Debugger+0x6:  unlk  a6
> 
> ...and debugger prompt, at which all I know to do right now is reboot.
> So whattaya think, sirs?

I'd say post a message (with this message chunk) to current-users.
I think you're more likely to get in touch w/ the ext2fs keepers
there, and someone else might be able to help.

> I'll try cleaning up my libraries tonight, to see if that clears up the 
> vi problem under the 1.3.2 kernel.  But the above problem when trying 
> newer kernels, looks to be kernel-specific since it's not accessing the
> the file system correctly, much less the proper libraries or binaries.

Good luck!

Take care,

Bill