Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Running a Red-Hat 9 Distro using the Red Hat Notification Alert Tool for Updating. Seems to work flawlessly as far as dowloading and installing the updates. I have one 'Critical Information Alert' that states my rig is using the Kernal -2.4.20-8 and that the latest Kernel is 2.4.20-20-9 and that I should reboot to "Test' this new Kernal. Reboot does not clear out. Im using a boot disk that I made when I orginally loaded up Linux in a dual boot config with windows. Not using a boot loader as the boot CD fires the Linux up perfectly. Im Toatally guessing here, but im assuming(bad thing I know), the the boot disk is the cause? Anyhow, any body know how to fire up the latest Kernel, I would appreciate it.
Create a new bootable floppy... The command should be "mkbootdisk --device /dev/fd0 2.4.20-20-9". You might have to play with the kernel version number a bit.
Be sure to use a new floppy, not your original. That way, you can get into the system if the new one doesn't work, for some reason.
I personally would tell you to use GRUB as your boot loader, since it does a very good job when dual booting a computer, not to mention that it can fool windows to think that it is installed on the first primary partition even it was installed on an extended partition. Anyhow, you may want to look under your /boot directory, there you should have lots of information regarding your kernel version. The actual kernel is the file called vmiluz-2.4.20-xxx (where xxx is the Red Hat subpatch version), you should also have an initrd-2.4.20-xxx.img and a System.map symlink to the current System.map-2.4.20-xxx. If you left the up2date utility to upgrade the kernel it surely left your previous version there (2.4.20-8), letting you boot whichever kernel you would like.
[edit]
Changed the phrase since it can does a very good job... to since it does a very good job
Thanks for your responses, im not using a boot loader at all. I just made a boot disk when I installed and transfered that to a bootable CD. I have my bios set for CD rom as first boot device. If I put the linux boot CD in the drive the rig will boot to Linux. If I leave out the CD it boots to Windows XP. Kinda Nice acutally. Im gonna try to make a new boot disk using the first Post response. I Kinda figured the boot disk im using is booting the original Kernel. Il let you know how I make out.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.