On Tue, 11 Jun 2002, Trevin Beattie wrote:

> I just happened to have a MO disk lying around that I had created using
> NeXTSTEP 3.0/68k, so I decided to dump the first few sectors and see what
> it looks like.  The first thing I found is that NeXT's disk label is at the
> beginning of the disk (sector 0 byte 0), and the super-block starts at
> sector 3 (byte offset 0x1800).  I've confirmed that NeXTSTEP sets
> fs_fsbtodb and fs_nspf in terms of physical sector size / fragment size, so
> my recent patches do the right thing in that respect.
>
> One thing that concerns me is that NetBSD's ffs expects the super-block to
> be at byte offset 0x2000, and I can't figure out where or if we look
> differently when reading a NeXT file system.  Has anybody been able to
> mount a NeXT/68k disk under NetBSD?  Also, if anyone has a 512-byte/sector
> disk formatted by NeXT/68k, I'd like to know whether the super-block in
> that case is also on sector 3 or at byte offset 0x1800.

I think we'll need NeXT file systems to be a little different. Well, we
will probably need a different mount option, which will change some
initial parameters.

Someone on macppc was looking into this since MacOS X's UFS is very
next-based.

Take care,

Bill