On Mon, 2005-01-24 at 16:20 +1100, david smethurst wrote: > hiall, again > im at a loss as to what all this means: > > [root@localhost qtparted]# rpm -ivh libuuid*.rpm > 1:libuuid warning: user cs does not exist - using root > warning: group cs does not exist - using root > ########################################### [100%] > warning: user cs does not exist - using root > warning: group cs does not exist - using root > warning: user cs does not exist - using root > warning: group cs does not exist - using root > [root@localhost qtparted]# > > > im trying to get some of the dependencies to get qtparted installed on > my 64bit because im too stupid to be able to figger-out how to access my > original drive which still has fc2 on it and cant be mounted because of > the same mount point names, > but now i just cant solve all the dependencies required. > i might attach it as a usb and see what that does> > or just ghost this new fc3 installation across and lose all the data ive > been trying to keep thats on fc2 disk. > thanks easy solution for the problem with identical disk labels -- don't use them in fstab. to fix that do the following. # mount will give you something like this that (mostly) maps labels to partitions [root@goliath ~]# mount /dev/hda2 on / type ext3 (rw) /dev/hda1 on /boot type ext3 (rw) /dev/hda3 on /home type ext3 (rw) /dev/hda5 on /opt type ext3 (rw) now look in /etc/fstab to find out which filesystems are mounted by label. Usually you will see LABEL=/ and LABEL=/boot and maybe more. replace only that part of the line with the device equivalent. With mine that means replacing LABEL=/ with /dev/hda2 and similar for /boot and /dev/hda1 Finally you edit /boot/grub/grub.conf and replace the root=LABEL=/ with root=/dev/hda2. Now you can attach the other drive and reboot without getting the label conflicts that prevent booting. HTH > david >
