Need to test it a bit first (i.e. at least compile it)...
> > I know a bit about LILO, so I should be able to get the "root=LABEL=" to
> > work there as well.
>
> There were no problems with the original patch with LILO.
> You just must use append="root=xxxxx" instead of simply
> root=xxx , because LILO tries to be "smart" .... at least the
> version I used then did.
Actually, there are 2 ways to go about this: LILO could do the UUID/LABEL
resolution at the time lilo is run (to store root dev into kernel), and
_also_ append "root=LABEL=X" to kernel options, so that if the kernel
can't resolve the UUID/LABEL (i.e. no support for this option) we can fall
back to the root dev from when LILO was run.
> > One reason why this may NOT ever make it into the kernel is that I know
> > "kernel poking at devices" is really frowned upon.
>
> This an ugly hack , if you ask me. The identificators ( be it labels ,
> UUIDs or whatever ) should be outside the partitions. Otherwise cases with
> swap partitions , <any FS that doesn't support labels/UUIDs> unformatted
> partitions etc. can not be handled.
LVM now has UUID-like identifiers for all "partitions" (Logical Volumes),
although they are not really accessible by any tools right now. The "LABEL"
is actually the LV name, so it is used directly all the time:
/dev/vgroot/lvroot / ext3 defaults 1 1
/dev/vgroot/lvswap none swap sw,pri=100 0 0
This obviates most of the reason for the UUID/LABEL support, but not
everyone runs LVM (yet ;-) and ext2 UUID/LABELs are still useful.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbert
-
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/