From: "Helge Hafting" <helgehaf@idb.hist.no>
> Partition id's seems more interesting than disk id's - we normally
> mount partitions not whole disks.
>
> RAID do this well - the raid autodetect partition stores an ID in the
> last block,
> the remaining N-1 blocks are available for a fs.
>
> This could be extended to non-raid use - i.e. use the "raid autodetect"
> partition type for non-raid as well. The autodetect routine could
> then create /dev/partitions/home, /dev/partitions/usr or
> /dev/partitions/name_of_my_choice
> for autodetect partitions not participating in a RAID.
Raid can do this easily because they install the raid on fresh partitions so
they can easily "steal" the last sector, and the filesystem goes in the
"shrinked" raid-device. Normal partitions that already have a filesystem on
them (maybe another OS formatted them) occupy space including the last
sector - no place left on these partitions to baptize them. - how should
that work with existing fs'es???
> This is better than volume labels, as it will work for all fs'es
> (including those who don't support mount-by-ID) and also raw
> partitions with no fs.
Thomas Kotzian
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed May 23 2001 - 21:00:16 EST