From: Sven L. <sve...@wa...> - 2003-09-18 06:19:26
|
On Thu, Sep 18, 2003 at 03:28:35AM +0200, Geert Uytterhoeven wrote: > On Wed, 17 Sep 2003, Sven Luther wrote: > > Finally, i have a question concerning the partition DosType of > > partitions of the following filesystems : > > > > - ext3 (i used LNX\1) > > - fat16 > > - fat32 > > - hfs (MAC\0 ?) > > - jfs > > - ntfs > > - reiserfs > > - sun-ufs > > - hp-ufs > > - xfs > > > > Or maybe i could use one of the UNI\x for some of them, or some kind of > > RSV\0 (for reserved) dostype. > > > > What is currently in use for these ? > > Since AmigaOS doesn't care[*], you can use whatever you want. E.g. 0x45585433 > (EXT3 in HEX ASCII) for ext3. But then, why not use ext2 instead of lnx0 for ext2 ? > BTW, most of these file systems use some 32-bit magic value in their > superblock, don't they? You may want to use that one. That is a good idea, i will be going hunting for them. That said, i am sure at lest for fat16 or fat32 there are values that are already used, which would be best to be reused. I will investigate more about this. > I think cfdisk determines the type of the partition from the superblock, since > all my Linux partitions (on ia32) have type 0x82 in the partition table, while > cfdisk identifies them as `Linux ext2' or `Linux ext3' depending on the actual > file system. Mmm, parted also don't care, since it uses exclusively the information found in the filesystem to detect the filesystem type and fully ignores the filesystem type found in the partition table. > [*] AFAIK the only exception is that AmigaOS refuses to boot from a partition > if it has a DosType for which it has no file system driver (either in ROM > or in the RDB) and it has an `unknown' type (not 100% sure about that one, > probably it can boot from UNI\x). So if you want to put the Lilo boot block > on an ext2 partition, you need to use a fake DosType, or have put an > AmigaOS ext2 driver in the RDB. Ok, that makes sense. Do you know of a link to such an ext2 driver ? That said, the pegasos OF is able to boot from affs, ext2 and bsdish filesystems, so it is not so much of a problem for me. Well the next incarnation of the OF, the current one only knows about affs, which is why i will nextly implement the creation of affs empty filesystems in parted. BTW, do you think it is worth to implement affs and co awareness in mkfs/fsck ? Friendly, Sven Luther |