minix images + minix FS

[df]

v2 FS has 'zones' in the superblock.. what are they? afaik they are contiguous blocks.. but Ive no info on how to read them in, is it a bitmap or what??

there are also bits set in the i_mode of inodes that I cant tell what they are. I think its to do with link files, devices, etc... anyone got proper info on this? I have dir attrib + the standard rwxrwxrwx bit masks)...

there dont seem to be any documents on the internet explaining the minix fs (and my andy t book is back in australia.... sigh..)

i'm writing some 'minix tools' just for the heck of it. think mtools for dos, but for minix. anyway.

also, anyone got a v2 30char name disk image?? i have images of v1+14, v1+30, v2+14 but not v2+30...

so far all is ok except for minix203.img... which bochs distributes.. that seems corrupt to me.. but afaik i think bochs can boot it ok....

based on my image, its inode list should start at 0x2800
(1 block bootsector, 1block superblock. 2+6 blocks for inode+zone images)..

at 0x2800 there looks like a inode.. but is only 1 inode on its own!!
the disk shows all the inodes starting at 0x3400...

yet they look like 64byte inodes instead of 32byte inodes.
the magic definatly describes a v1+30 FS.

in the bitmap zones is a load of crap.
2200 - copy of boot sector block
2400 - copy of boot sector block
2600 - init script? (rootdev=c0d0p0s0 rammagedev=c0d0p0s0 ramsize=1024)

between 0x2800 - 0x3200 is a load of guff...

2800 - single inode entry
2C00 - looks like inode bitmap
3000 - looks like anoter bitmap
3400 - 64byte inode entries?

AC00 - root directory entries
(equates to block 0x2B)

I cant figure this disk image out...

all my other imags work fine... just this one image that does not conform!

can someone check for me that bochs can boot minix203.img??? still laptop-less.. ugh..

[df]

you know when you look at something so hard and for so long you blind yourself to it???

aaaaaaaaaaaargh. its sooo DAMN SIMPLE!! i was looking at a hard disk image with an MBR!!!

minix has its own formats and things... and unlike everything else that usualy doesnt use the entire first track, minix starts off with other bits on the next sector so I had a valid boot sector but that pointed to a bunch of minix subpartitions that are not compatible with anything else!!

doh!

sweet. back on track now anyway