On Fri, 2006-05-05 at 15:31 -0500, Aaron Konstam wrote: > > > > It should be noted that this is only a problem when you move disks from > > one system to another. > Of course people do that. Move disk that is. Interestingly - I have a disk that has a partition with LABEL=/ and it isn't a problem when attached via USB after a system with LABEL=/ has booted. It's only a problem when fstab is mounting a mount point with the specified label - IE the disk is there when the system boots. The fix in that case is to edit /etc/fstab and change LABEL=/ to /dev/whatever (you should be able to boot into maintenance mode to do that) > > > > When you already have disks with those labels, anaconda sees them - and > > does not use them. > I am not sure I believe that but I cna't prove it. One of my system always has at least two installs - FC4 and devel, and sometimes an additional. root on the second is LABEL=/2 or something like that. Well, now I use LVM which does things a little differently, but it too detects existing volume groups and their name. But yes - anaconda reads disk labels that exist, and if a disk label exists that it wants to use for creating a partition - it uses a different label. > > > I can't remeber that hte label can be specified separate from the mount > point. But maybe it can be in FC5. I will be installing FC5 again next > week so I will check that. I'm pretty sure it can in the manual partitioning mode. Almost positive it can.
