Hi again !
Only to be sure:
In our company we only use the old minix format. Under Linux you must
use the option `-n14' to have this old style format using mkfs.minix.
I don't know, if GRUB can handle any other minix file system than the
old classic one. So 0x80 can be used as 'protection' not to use GRUB
on non-classic minix partitions, created with mkfs.minix without
`-n14' option (which should have code 0x81 !)
With friendly regards
Christoph P.
Alessandro Rubini wrote:
>
> [...]
>
> > The `0x81' code repesenst (so I think)
> > an enhanced minix file system with name length > 14 chars, etc.
> > I don't know, if the minix implementation in GRUB is able to
> > handle this !!!!
>
> Once again, the partiotion types are not authoritative (with the exception
> of DOS that relies). Grub correctly tells the different filesystems apart
> using the minix magic number stored in the super block. The magic number
> is different for the different minix implementations.
>
> Applying my patch has been the only way I had to access my minix
> partition on an old linux-2.0 disk I mounted on my 386-SX. Sure I
> could change the partition types (after finding some other way to
> boot, though), but I'm pretty sure every minix fs created under GNU/Linux
> will have 0x81 in the partition table and a 30-chars filesystem.
>
> Note, this is not the minix version 2 filesystem, which is not supported
> by GRUB (and identified by means of the magic number, not the partition table.
> It is the default of mkfs.minix under Linux, grub dealt fine with it
> as stored two years ago on my disk.
>
> Regards
> /alessandro
--
-------------------------------------------------------------------------
private: [EMAIL PROTECTED]
company: [EMAIL PROTECTED]
