> [Venkatesh Ramamurthy] Dont you think that mounting and booting
> based on disk label names is better, then relying on device nodes which can
> change when a new card is added?. The existing patch for 2.2.xx is quite
> small and it does not bloat the kernel too much either. I think we can port
> it for 2.4.XX with ease.In my words it is worth the effort
Of course that would be better. The only complaint I have with such a
system is that of backwards compatibility...as long as the legacy device
names are still supported i would have no problem with it at all.
however, this brings up an interesting question: what happens if two disks
(presumably from two different machines) have the same disk label? what
happens then? for instance, i have several linux machines both at my
workplace and my home. if for some reason one of these machines dies due
to hardware failure and i want to get stuff off the drives, i put the disk
containing the /home partition on the failed machine into a working
machine and reboot. What /home gets mounted then? the original /home or
the new one from the dead machine? (and don't say end users wouldn't
possibly do that... if they are adding hardware into their systems this is
by no means beyond their capabilities)
at least with physical device nodes i can say 'computer, you will mount
this partition on this mountpoint!' and be done with it.
so tell me then, how would one discern between two partitions with the
same label?
just a thought....
Kelsey Hudson khudson@ctica.com
Software Engineer
Compendium Technologies, Inc (619) 725-0771
---------------------------------------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/