On 16 May 2001 15:28:03 +0200, Helge Hafting wrote:
> Oystein Viggen wrote:
> >
> > Quoth Helge Hafting:
> >
> > > 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.
> >
> > What happens if I insert a hard drive from another computer which also
> > has partitions named "home", "usr", and soforth?
>
> This is the problem with all sorts of ID-based naming. In this case
> the kernel could simply change the conflicting names a bit,
> and leave the cleanup to the administrator. (Who probably
> is around as he just inserted those disks....)
>
> The current scheme have problems if you move a disk
> from one controller to another, or in some cases
> if you merely add a new one. So the question becomes -
> what is most likely to go wrong? And you can be
> smart and name your partitions /usr21042001, /home03042001
> and so on in order to minimize the risk of conflicts.
Well, a usermode solution might be to add support for having the
filesystem utilities generate and detect partition IDs. Then the disks
could be moved from one controller to another, but mount could scan
partition IDs and associate mount points on matching IDs rather than on
/dev/hdX or /dev/sdX.
Or is this a ridiculous idea?
Miles
-
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:17 EST