XPost: alt.os.linux.mageia   
   From: Ar@127.0.0.1   
      
   On 05/02/13 20:32, Jim Beard wrote:   
   > You may note that grub thinks (0,0) is disk1 partition1, but grub2 will   
   > call disk1 partition1 (1,1).   
   >   
   > One way to deal with this is to go into mcc to manage local disks to   
   > advanced (I think) and label the partitions. This will allow both grub   
   > and grub2 to find the correct drive if in fstab you use LABEL=yourlabel   
   > rather thant he old /dev/sdax format. You can also use Label= format   
   > rather than UUIC= or /dev/sdax format in grub's menu.lst. I don't know   
   > what the grub2 menu.lst looks like (does it even have one?) so I don't   
   > know how far you can push this.   
      
   My entries for Windows partitions look like this:   
      
   UUID=00A609H8609 /media/win_a1 ntfs-3g silent,defaults,umask=000 0 0   
      
   or for Linux partitions:   
      
   UUID=36be3534-82b0-99f3-806z-26ea11h0c0v3 /home ext4 acl,relatime 1 2   
      
   I've had zero problems since I switched to using UUID to identify drives.   
      
   It's also so much easier to manage then Windows drive letters, which   
   assigns a partition the wrong letter then creates a whole load of mess   
   to try and get it sorted out.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)