I recently have been using a EL 2.1ASDEV server and noticed that I had an application that needed an upgraded kernel. I registered the installation to enable up2date to pull down any updates, but it said there were none. I noticed however that the updates.redhat.com under the enterprise/2.1AS section did show some updates to the kernel, however everything there were src.rpms rather than normal rpms. I did some research and found that very easily you can compile and create rpms via the "rpm -ba <src.rpm>". I did this on a few packages and sure enough, out popped my rpms to install. I did this for the kernel, and after about 10 minutes of compiling, making, and make testing, it finally popped out 4 rpms to install. Here is the issue, the rpms I got were the following: i386/kernel-BOOT-2.4.9-e.30.i386.rpm i386/kernel-headers-2.4.9-e.30.i386.rpm i386/kernel-doc-2.4.9-e.30.i386.rpm i386/kernel-source-2.4.9-e.30.i386.rpm Now, I noticed that there is no kernel-2.4.9-e.30.i386.rpm. There were no other rpms stuck back anywhere in the i686, etc. directories either. I figured, ok, lets see what happens and installed them (rpm -Uvvh kerne*), and sure enough there are there. On reboot I noticed that I had to select the kernel-BOOT-2.4.9e-30 option but it boots, and seems to run ok. I'm not so sure I'm comfortable running the BOOT disk kernel, and I was wondering if anyone knew maybe where I went wrong or if I am missing something to which made it so a kernel-2.4.9-e.30 wasn't created? Another step or something? Thanks in advance -Brian -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
