On November 27, 2003 07:55 am, Brian Furey wrote: > Use the "ln" command to link the 2 directories. > For instance your system will look for the directory > module-info and your link will point from this directory to > module-info-2.4.20... > i think its > ln /dir/mod-info-2.4.3.45 module-info > Anthony Yulo <strikewing16th@xxxxxxxxxxx> wrote: > > ............ > ............ > .......... > > >Then make sure any sym links in /boot point to files for your current > >kernel: > >module-info -> module-info-2.4.20-20.8 > >System.map -> System.map-2.4.20-20.8 > >vmlinuz -> vmlinuz-2.4.20-20.8 > > ahmm.. how do i do that? i mean make sure the /boot point to files in my > current kernel? > sorry, i don't know what to do.. newbie..:) > > _________________________________________________________________ > Help STOP SPAM with the new MSN 8 and get 2 months FREE* > http://join.msn.com/?page=features/junkmail Hi, Actually, you want to make a symbolic link, not a hard link. They are similar to a shorcut in windows or an alias in mac. (A hard link is a difference reference to the same inode, a sym link is a inode pointing to another inode. use 'ln -s' for a symbolic link.) as root enter: cd /boot ls -lF (or to only see the sym links "ls -lF|grep lrwxrwxrwx") That will display a detailed file listing which will likely have 3 sym links such as: lrwxrwxrwx <snip...> module-info -> module-info-2.4.20-20.8 The "l" at the begining shows it is a symbolic link. The symbilic name is "module-info " which points to the real file "module-info-2.4.20-20.8" (You must have done this if you are booting a new kernel that you compiled, unless your kernel image in called vmlinuz or some thing) Anyway, you want to link the base name to the latest kernel and module info, so, if you have a new image called vmlinuz-2.4.20-20.8 (it should be in /boot already), and say your old kernel was vmlinuz-2.4.18-26.8.0, do this: Current: module-info -> module-info-2.4.18-26.8.0 System.map -> System.map-2.4.18-26.8.0 vmlinuz -> vmlinuz-2.4.18-26.8.0 do this to remove the old link (not the files) and replace it: (the -s is Symbolic, -f is Force overwrite onld link, see man) ln -sf vmlinuz-2.4.20-20.8 vmlinuz ln -sf System.map-2.4.20-20.8 System.map ln -sf module-info-2.4.20-20.8 module-info (any order, I put some space in for clearity) that will leave you with: module-info -> module-info-2.4.20-20.8 System.map -> System.map-2.4.20-20.8 vmlinuz -> vmlinuz-2.4.20-20.8 then in /boot/grub edit grub.conf Using the old kernel from above, it will contain a stanza like: title Red Hat Linux (2.4.18-18.8.0) root (hd0,0) kernel /vmlinuz-2.4.18-18.8.0 ro root=LABEL=/ initrd /initrd-2.4.18-18.8.0.img Add one right above like: title Red Hat Linux (2.4.20-20.8) root (hd0,0) kernel /vmlinuz-2.4.20-20.8 ro root=LABEL=/ initrd /initrd-2.4.20-20.8.img There is a line near the top with: default=0 That means the 1st listed kernel will be the default selected in the GRUB boot menu, and will boot by default. default=1 would select the 2nd kernel as the default selection. Hope that Helps. hmmm, after looking at my grub conf file it looks like grub may not need the sym links that lilo does. They won't hurt, but anybody know if thay are still required for GRUB? -- Pete Nesbitt, rhce -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
