Look at /dev/disk/ and you will see several different ways a disk can be accessed: RAID-Server:/dev/disk# ll total 0 drwxr-xr-x 6 root root 120 2009-12-25 13:34 . drwxr-xr-x 14 root root 4200 2009-12-30 07:54 .. drwxr-xr-x 2 root root 820 2009-12-25 19:42 by-id drwxr-xr-x 2 root root 60 2009-12-25 13:34 by-label drwxr-xr-x 2 root root 420 2009-12-25 19:42 by-path drwxr-xr-x 2 root root 120 2009-12-25 13:34 by-uuid Look in the by-uuid directory, and you will see all the unique disk identifiers. Udev can and will move the assignments ( /dev/hda, /dev/sdb, etc ) around more or less at will, and will definitely do so whenever a disk is added or removed. This makes the old method of assigning boot drives (hd0, etc.) unreliable. The uuid, however, is specific to the drive, and will not change even if the drive is moved to another system. It's the only reasonable way, for example, to create a bootable USB drive or a bootable removable hard drive. > -----Original Message----- > From: linux-net-owner@xxxxxxxxxxxxxxx [mailto:linux-net- > owner@xxxxxxxxxxxxxxx] On Behalf Of clownix > Sent: Wednesday, December 30, 2009 4:12 PM > To: ranjith kumar > Cc: linux.kernel; linux-kernel; linux-net@xxxxxxxxxxxxxxx > Subject: Re: booting with linux kernel 2.6.32.2 > > If you do > > blkid > > you see all your UUID and the corresponding dev, UUID is a unique > identifier, this is why it is a long name. > > For the kernel config, try to take your own in the /boot/config-2.6... > Try: > > cp /boot/config-2.6... .config > make menuconfig > exit/save > make > make modules_install > make install > > > > > Le jeudi 31 décembre 2009 à 02:27 +0530, ranjith kumar a écrit : > > Hi, > > > > I am using fedora 10. > > I downloaded linux kernel 2.6.32.2 and run the follwing commands to > > build and install it. > > > > 1) make defconfig > > 2) make > > 4)make modules > > 5)make all > > 6)make modules_install > > 7)make install > > > > After that the contents of /boot/grub/menu.lst are: > > ------------------------------------------------------------------------ > > 1 # grub.conf generated by anaconda > > 2 # > > 3 # Note that you do not have to rerun grub after making changes > > to this file > > 4 # NOTICE: You have a /boot partition. This means that > > 5 # all kernel and initrd paths are relative to /boot/, > eg. > > 6 # root (hd0,2) > > 7 # kernel /vmlinuz-version ro > root=/dev/VolGroup00/LogVol00 > > 8 # initrd /initrd-version.img > > 9 #boot=/dev/sda > > 10 default=2 > > 11 timeout=5 > > 12 splashimage=(hd0,2)/grub/splash.xpm.gz > > 13 hiddenmenu > > 14 title Fedora (2.6.32.2) > > 15 root (hd0,2) > > 16 kernel /vmlinuz-2.6.32.2 ro > > root=UUID=80c4c9bd-8110-4f79-8bdc-dd69e38bf299 > > 17 initrd /initrd-2.6.32.2.img > > 18 title Fedora (2.6.27.5-117.fc10.i686) > > 19 root (hd0,2) > > 20 kernel /vmlinuz-2.6.27.5-117.fc10.i686 ro > > root=UUID=80c4c9bd-8110-4f79-8bdc-dd69e38bf299 > > 21 initrd /initrd-2.6.27.5-117.fc10.i686.img > > 22 title Windows Vista > > 23 rootnoverify (hd0,0) > > 24 chainloader +1 > > ------------------------------------------------------------------------ > --------------------------------- > > 1) When I rebooted the machine and selected "Fedora (2.6.32.2)" from > > grub's menu, > > why fedora(old fedora 10 which was there initially) is booting instead > > of linux kernel 2.6.32.2 ??? > > > > 2) what does "ro root=UUID=80c4c9bd-8110-4f79-8bdc-dd69e38bf299" means > > in /boot/grub/menu.lst ? > > > > Thanks in advance. > > -- > > To unsubscribe from this list: send the line "unsubscribe linux-net" in > > the body of a message to majordomo@xxxxxxxxxxxxxxx > > More majordomo info at http://vger.kernel.org/majordomo-info.html > > > -- > To unsubscribe from this list: send the line "unsubscribe linux-net" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-net" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
