RE: Kernel Update - if it's not broke do I fix it?
On Thu, 25 Sep 2003, Billy wrote: snip... > > Then on the other hand, if I install the newkernel.rpm and something isn't > working right could reboot into the old kernel and run rpm -e newkernel.rpm? > Is there a chance that after the kernel has been updated that the machine > will not boot at all, or as long as I have the old kernel I can always boot > with that? And finally *if* I go ahead with this am I crazy to do this > remotely over SSH? > > Thanks a million!! > > Billy Actually, you don't do an "rpm -e newkernel.rpm". That doesn't work (putting the .rpm on the end). Try an "rpm -q kernel" to find out which kernel rpm's you have installed. Once you decide which ones you want to remove do an "rpm -e kernel-2.4.20-19.9" for example. That will remove kernel-2.4.20-19.9. It takes it out of grub as well as from the disk. -- Gerry "The lyfe so short, the craft so long to learne" Chaucer -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
Re: Kernel Update - if it's not broke do I fix it?
On Thu, 25 Sep 2003 15:36:58 -0400 "Billy" <[EMAIL PROTECTED]> wrote: > Thanks for the advice Sean...I am going to research the kernel updates > some more and evaluate the upgrade. I do have a question about the > kernel and being able to retreat. If I install the newkernel.rpm with > rpm -ivh it will install, and running in conjunction with the old > kernel? So once I reboot by default it will load the newest kernel? > Then once I let it run for a couple days and everything seems fine I > could safely run rpm -e oldkernel.rpm to remove the old? Then on the > other hand, if I install the newkernel.rpm and something isn't working > right could reboot into the old kernel and run rpm -e newkernel.rpm? Yes, it will work as you describe. When the grub menu is shown to you at boot up time you'll be able to select which kernel to use but the new one should be the default if you select nothing. > Is there a chance that after the kernel has been updated that the > machine will not boot at all, or as long as I have the old kernel I can > always boot with that? Installing a new kernel _should_ do nothing to stop you from rebooting and using the previous kernel. Still that's no excuse not to have proper backups ;o) > And finally *if* I go ahead with this am I crazy to do this remotely > over SSH? If for some reason the new kernel hangs on reboot, you'll have to be in front of the console to reset it. I've upgraded kernels remotely for years, but on occasion have had to get in the car and go to the server or call someone for a reset. Good Luck, Sean -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
Re: Kernel Update - if it's not broke do I fix it?
On Thursday 25 September 2003 03:36 pm, Billy wrote: > > > will installing the mew kernel with rpm -ivh kernel_new_zzz.rpm > > > (a) add the new kernel image to my boot loader (in this case GRUB) > > > (b) keep the entry for the old kernel in my boot loader > > > > > > I don't know of any other way to be able to "retreat" if for some > > > reason the new kernel does not boot... > > > > Hi Jason > > > > Yes to both questions. > > Thanks for the advice Sean...I am going to research the kernel updates some > more and evaluate the upgrade. I do have a question about the kernel and > being able to retreat. If I install the newkernel.rpm with rpm -ivh it will > install, and running in conjunction with the old kernel? You can only run 1 kernel at a time, but if you I guess what you meant correctly, then yes, your old kernel won't be gone. It will still show up in LILO or Grup (mine shows up as Linux Bak, Linux Bak1, etc in LILO) > So once I reboot > by default it will load the newest kernel? Yes > Then once I let it run for a > couple days and everything seems fine I could safely run rpm -e > oldkernel.rpm to remove the old? Yes > Then on the other hand, if I install the newkernel.rpm and something isn't > working right could reboot into the old kernel and run rpm -e > newkernel.rpm? Yes >Is there a chance that after the kernel has been updated > that the machine will not boot at all, or as long as I have the old kernel > I can always boot with that? You can always revert back to old kernel > And finally *if* I go ahead with this am I > crazy to do this remotely over SSH? The only thing you need to worry is that if you fail to boot, than you have no way to tell the machine to use the old kernel without the machine physically in front of you. But if there's someone you can call that has physical access to the machine, you can always tell him/her "Hey, watch the LILO (or GRUB) and choose the old kernel when booting! " :) FWIW, I have always upgraded my kernel when newer version available using Redhat up2date, and never had any problems. I also run Apache, MySql, PostgreSQL, Oracle (no, not all on the same machine), PHP, and a bunch of other stuffs. But, as always the disclaimer, YMMV. RDB -- Reuben D. Budiardja Department of Physics and Astronomy The University of Tennessee, Knoxville, TN - -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
RE: Kernel Update - if it's not broke do I fix it?
> > will installing the mew kernel with rpm -ivh kernel_new_zzz.rpm > > (a) add the new kernel image to my boot loader (in this case GRUB) > > (b) keep the entry for the old kernel in my boot loader > > > > I don't know of any other way to be able to "retreat" if for some reason > > the new kernel does not boot... > > > > Hi Jason > > Yes to both questions. Thanks for the advice Sean...I am going to research the kernel updates some more and evaluate the upgrade. I do have a question about the kernel and being able to retreat. If I install the newkernel.rpm with rpm -ivh it will install, and running in conjunction with the old kernel? So once I reboot by default it will load the newest kernel? Then once I let it run for a couple days and everything seems fine I could safely run rpm -e oldkernel.rpm to remove the old? Then on the other hand, if I install the newkernel.rpm and something isn't working right could reboot into the old kernel and run rpm -e newkernel.rpm? Is there a chance that after the kernel has been updated that the machine will not boot at all, or as long as I have the old kernel I can always boot with that? And finally *if* I go ahead with this am I crazy to do this remotely over SSH? Thanks a million!! Billy --- [This E-mail was scanned for viruses by QuestNet.net (http://www.QuestNet.net)] -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
RE: Kernel Update - if it's not broke do I fix it?
[EMAIL PROTECTED] wrote: > I have the same problem, but my further questions are: > > will installing the mew kernel with rpm -ivh kernel_new_zzz.rpm > (a) add the new kernel image to my boot loader (in this case GRUB) > (b) keep the entry for the old kernel in my boot loader Installing the new kernel will ADD the new kernel to your boot process and to grub. If it doesn't allow you to boot just select the old kernel from grub when the machine reboots and you can go in under the old kernel and find out what's up. If you want to then go back and always boot from the old kernel just change the grub configuration file to reflect your default kernel for booting. Good luck. stew > I don't know of any other way to be able to "retreat" if for some > reason the new kernel does not boot... > > Thanks, > Jason > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Sean Estabrooks > Sent: Thursday, September 25, 2003 2:06 PM > To: [EMAIL PROTECTED] > Subject: Re: Kernel Update - if it's not broke do I fix it? > > > On Thu, 25 Sep 2003 12:18:46 -0400 > "Billy" <[EMAIL PROTECTED]> wrote: > >> I have a 7.3 server running Apache, PHP, MySQL, and WU-FTP. I of >> course keep all of those packages updated since I have to have most >> of the ports open in the firewall to use them. However, I have not >> upgrade the kernel since the install about a year ago. It is version >> 2.4.18-3. I have three questions, #1 How important is it to keep the >> kernel updated, I could imagine maybe I have just gotten lucky but >> the machine has been wonderful up to date. #2 How big of risk do I >> run upgrading the kernel, is there a good chance that I could hose >> the machine, or is it as easy as running rpm-Fvh kernel.rpm? #3 When >> I run rpm -qa | grep kernel it only returns kernel-2.4.18-3, when I >> look at the available kernel updates I find >> kernel-BOOT-2.4.20-20.7.i386.rpm and >> kernel-source-2.4.20-20.7.i386.rpm as well...my practice in the past >> has always been to only install updated packages for what I already >> have on the machine...excuse my ignorance but I am extremely new to >> the linux world, and have heard so many horror stories about kernel >> updates...any input would be greatly appreciated!! >> > > Hey Bill, > > It is quite probable that there have been security related updates to > the kernel that would be relevant to your environment. You have to > decide for yourself how important that makes it for you to upgrade. > Obviously there is no other reason to upgrade as you're content with > the way the system is operating. > > If you do choose to upgrade your kernel i'd suggest _adding_ the new > kernel but not removing your existing kernel: > > rpm -ivh kernel_new_zzz.rpm > > This will give you a way to retreat if there are any problems with > the new kernel. You _dont_ want to use the BOOT kernel, that's > pretty much just for installation media like CD's. And you probably > don't have any reason to install the kernel-source package. > > HTH, > Sean. > > > -- > redhat-list mailing list > unsubscribe mailto:[EMAIL PROTECTED] > https://www.redhat.com/mailman/listinfo/redhat-list --- Outgoing SofTEC USA email is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.518 / Virus Database: 316 - Release Date: 9/11/2003 -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
Re: Kernel Update - if it's not broke do I fix it?
On Thu, 25 Sep 2003 14:38:10 -0400 "Jason Murray" <[EMAIL PROTECTED]> wrote: > I have the same problem, but my further questions are: > > will installing the mew kernel with rpm -ivh kernel_new_zzz.rpm > (a) add the new kernel image to my boot loader (in this case GRUB) > (b) keep the entry for the old kernel in my boot loader > > I don't know of any other way to be able to "retreat" if for some reason > the new kernel does not boot... > Hi Jason Yes to both questions. Cheers, Sean -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
RE: Kernel Update - if it's not broke do I fix it?
I have the same problem, but my further questions are: will installing the mew kernel with rpm -ivh kernel_new_zzz.rpm (a) add the new kernel image to my boot loader (in this case GRUB) (b) keep the entry for the old kernel in my boot loader I don't know of any other way to be able to "retreat" if for some reason the new kernel does not boot... Thanks, Jason -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Sean Estabrooks Sent: Thursday, September 25, 2003 2:06 PM To: [EMAIL PROTECTED] Subject: Re: Kernel Update - if it's not broke do I fix it? On Thu, 25 Sep 2003 12:18:46 -0400 "Billy" <[EMAIL PROTECTED]> wrote: > I have a 7.3 server running Apache, PHP, MySQL, and WU-FTP. I of > course keep all of those packages updated since I have to have most of > the ports open in the firewall to use them. However, I have not upgrade > the kernel since the install about a year ago. It is version 2.4.18-3. I > have three questions, #1 How important is it to keep the kernel updated, > I could imagine maybe I have just gotten lucky but the machine has been > wonderful up to date. #2 How big of risk do I run upgrading the kernel, > is there a good chance that I could hose the machine, or is it as easy > as running rpm-Fvh kernel.rpm? #3 When I run rpm -qa | grep kernel it > only returns kernel-2.4.18-3, when I look at the available kernel > updates I find kernel-BOOT-2.4.20-20.7.i386.rpm and > kernel-source-2.4.20-20.7.i386.rpm as well...my practice in the past has > always been to only install updated packages for what I already have on > the machine...excuse my ignorance but I am extremely new to the linux > world, and have heard so many horror stories about kernel updates...any > input would be greatly appreciated!! > Hey Bill, It is quite probable that there have been security related updates to the kernel that would be relevant to your environment. You have to decide for yourself how important that makes it for you to upgrade. Obviously there is no other reason to upgrade as you're content with the way the system is operating. If you do choose to upgrade your kernel i'd suggest _adding_ the new kernel but not removing your existing kernel: rpm -ivh kernel_new_zzz.rpm This will give you a way to retreat if there are any problems with the new kernel. You _dont_ want to use the BOOT kernel, that's pretty much just for installation media like CD's. And you probably don't have any reason to install the kernel-source package. HTH, Sean. -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
Re: Kernel Update - if it's not broke do I fix it?
On Thu, 25 Sep 2003 12:18:46 -0400 "Billy" <[EMAIL PROTECTED]> wrote: > I have a 7.3 server running Apache, PHP, MySQL, and WU-FTP. I of > course keep all of those packages updated since I have to have most of > the ports open in the firewall to use them. However, I have not upgrade > the kernel since the install about a year ago. It is version 2.4.18-3. I > have three questions, #1 How important is it to keep the kernel updated, > I could imagine maybe I have just gotten lucky but the machine has been > wonderful up to date. #2 How big of risk do I run upgrading the kernel, > is there a good chance that I could hose the machine, or is it as easy > as running rpm-Fvh kernel.rpm? #3 When I run rpm -qa | grep kernel it > only returns kernel-2.4.18-3, when I look at the available kernel > updates I find kernel-BOOT-2.4.20-20.7.i386.rpm and > kernel-source-2.4.20-20.7.i386.rpm as well...my practice in the past has > always been to only install updated packages for what I already have on > the machine...excuse my ignorance but I am extremely new to the linux > world, and have heard so many horror stories about kernel updates...any > input would be greatly appreciated!! > Hey Bill, It is quite probable that there have been security related updates to the kernel that would be relevant to your environment. You have to decide for yourself how important that makes it for you to upgrade. Obviously there is no other reason to upgrade as you're content with the way the system is operating. If you do choose to upgrade your kernel i'd suggest _adding_ the new kernel but not removing your existing kernel: rpm -ivh kernel_new_zzz.rpm This will give you a way to retreat if there are any problems with the new kernel. You _dont_ want to use the BOOT kernel, that's pretty much just for installation media like CD's. And you probably don't have any reason to install the kernel-source package. HTH, Sean. -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
Kernel Update - if it's not broke do I fix it?
Howdy, I have a 7.3 server running Apache, PHP, MySQL, and WU-FTP. I of course keep all of those packages updated since I have to have most of the ports open in the firewall to use them. However, I have not upgrade the kernel since the install about a year ago. It is version 2.4.18-3. I have three questions, #1 How important is it to keep the kernel updated, I could imagine maybe I have just gotten lucky but the machine has been wonderful up to date. #2 How big of risk do I run upgrading the kernel, is there a good chance that I could hose the machine, or is it as easy as running rpm -Fvh kernel.rpm? #3 When I run rpm -qa | grep kernel it only returns kernel-2.4.18-3, when I look at the available kernel updates I find kernel-BOOT-2.4.20-20.7.i386.rpm and kernel-source-2.4.20-20.7.i386.rpm as well...my practice in the past has always been to only install updated packages for what I already have on the machine...excuse my ignorance but I am extremely new to the linux world, and have heard so many horror stories about kernel updates...any input would be greatly appreciated!! Thanks! Billy K. --- [This E-mail was scanned for viruses by QuestNet.net (http://www.QuestNet.net)] -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
Re: rebooting after kernel update
I am running 7.2 but I think this version uses GRUB. The new kernel shows up when I list the kernels but for some reason it is now hanging if I don't have the keyboard/mouse hooked up. It didn't do that before. It does run fine after I remove the keyboard and mouse. Any ideas? Mark On Saturday, August 23, 2003, at 10:04 AM, Stuart Sears wrote: On Saturday 23 August 2003 17:33, I thought I heard [EMAIL PROTECTED] say Sorry, I'm new to linux and command line. What is lilo.conf and what does running lilo do and how do I run it? which version of RH are you running? RH8/9 use GRUB as a bootloader and installing a new kernel rpm should add lines to its config file in /boot/grub/grub.conf Prior to this the boot manager was LILO, which does not read a config file on boot, but converts the information into a binary form which is loaded at boot time. if your boot manager is LILO you need to run /sbin/lilo -v after updating your kernel in order to accomplish this - you can then reboot and it should list an extra/new kernel in the list. the config file it reads is /etc/lilo.conf a sample entry would be: image = /boot/vmlinuz-2.4.18-14 label ="redhat 8.0" root=/dev/hdb2 read-only this will of course vary for you, depending on the kernel version and root partition. -- Stuart Sears RHCE (Registered Linux User #284465. LFS user #6416) -- "When you are in it up to your ears, keep your mouth shut." -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
Re: rebooting after kernel update
On Saturday 23 August 2003 17:33, I thought I heard [EMAIL PROTECTED] say > Sorry, I'm new to linux and command line. What is lilo.conf and what > does running lilo do and how do I run it? which version of RH are you running? RH8/9 use GRUB as a bootloader and installing a new kernel rpm should add lines to its config file in /boot/grub/grub.conf Prior to this the boot manager was LILO, which does not read a config file on boot, but converts the information into a binary form which is loaded at boot time. if your boot manager is LILO you need to run /sbin/lilo -v after updating your kernel in order to accomplish this - you can then reboot and it should list an extra/new kernel in the list. the config file it reads is /etc/lilo.conf a sample entry would be: image = /boot/vmlinuz-2.4.18-14 label ="redhat 8.0" root=/dev/hdb2 read-only this will of course vary for you, depending on the kernel version and root partition. -- Stuart Sears RHCE (Registered Linux User #284465. LFS user #6416) -- "When you are in it up to your ears, keep your mouth shut." -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
Re: rebooting after kernel update
Sorry, I'm new to linux and command line. What is lilo.conf and what does running lilo do and how do I run it? On Friday, August 22, 2003, at 09:54 PM, Res wrote: On Fri, 22 Aug 2003, [EMAIL PROTECTED] wrote: Everytime I reboot after I update the kernel using "up2date -u -f" the machine won't restart, or I should say it hangs on restart. When I tell it to reboot I do "shutdown -r now". you are checking lilo.conf and runing lilo first arent you? -- Res - Network Solutions: clueless f'wits who dont care whos business they damage through their incompetance, which is the ONLY thing they excel at. -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
Re: rebooting after kernel update
On Fri, 22 Aug 2003, [EMAIL PROTECTED] wrote: > Everytime I reboot after I update the kernel using "up2date -u -f" the > machine won't restart, or I should say it hangs on restart. When I tell > it to reboot I do "shutdown -r now". you are checking lilo.conf and runing lilo first arent you? -- Res - Network Solutions: clueless f'wits who dont care whos business they damage through their incompetance, which is the ONLY thing they excel at. -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
rebooting after kernel update
Everytime I reboot after I update the kernel using "up2date -u -f" the machine won't restart, or I should say it hangs on restart. When I tell it to reboot I do "shutdown -r now". It's a pain when I do this remotely and then have to drive 30 miles to fix it. When I see it at its location it looks like it partially rebooted and then froze but then when I restart it from there it boots up just fine. So, am I doing anything wrong? Does anyone know what's going on? Thanks Mark -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
RE: kernel update and grub
I have never had a kernel source to be deleted by a new install. If that is so then why have you sent this email. You should not have a space problem in that case. Look at the directories I referred and see if the old source is there. If it is not then you don't have a problem. > -Original Message- > From: [EMAIL PROTECTED] [mailto:redhat-list- > [EMAIL PROTECTED] On Behalf Of Robert C. Paulsen Jr. > Sent: Thursday, August 21, 2003 9:28 AM > To: [EMAIL PROTECTED] > Subject: Re: kernel update and grub > > On Thu, Aug 21, 2003 at 08:54:09AM -0500, Otto Haliburton wrote: > > > > > > > -Original Message- > > > From: [EMAIL PROTECTED] [mailto:redhat-list- > > > [EMAIL PROTECTED] On Behalf Of Asbjorn Hoiland Aarrestad > > > Sent: Thursday, August 21, 2003 4:18 AM > > > To: [EMAIL PROTECTED] > > > Subject: kernel update and grub > > > > > > hi! > > > > > > Just got word about the new kernel update, but when looking in my > logs > > > for the update, I just see an errormessage about "not enough space > on > > > /boot". This most probably because I have been installing a couple > of > > > kernel updates automatically using up2date, and never deleted > > > anything. > > > > > > I have redhat 7.3 and grub installed > > > > > > > > > How do I (commandline) delete the old kernels from grub? > > > > > > > > > - asbj?rn > > > > > > > > > -- > > > redhat-list mailing list > > > unsubscribe mailto:redhat-list- > [EMAIL PROTECTED] > > > https://www.redhat.com/mailman/listinfo/redhat-list > > > > You need to delete the old kernels from /boot. You can also delete > them > > from /usr/src. > > 1) Look at the grub.conf file in /etc. The directory is in /boot > (you > > can go there) also. The symbolic link to the file is in /etc. > > Determine which kernels you want to delete. Delete them from > grub.conf > > and from /boot. Remember to look at the default pointer and update > it > > to the new default in grub.conf. You can also go to /usr/src and > delete > > the old kernel directories. Be sure and make yourself a boot floppy > in > > case you make a mistake. Good luck > > A safer method is to delete the old kernels via rpm. For example my > system shows: > > rpm -qa | grep kernel > kernel-pcmcia-cs-3.1.31-13 > kernel-source-2.4.20-20.9 > kernel-2.4.20-19.9 > kernel-2.4.20-20.9 > > There is one old kernel still installed: kernel-2.4.20-19.9. To delete > it I would run: > > rpm -e kernel-2.4.20-19.9 > > I generally keep one back-level kernel "just in case"; thus the output > above. It appears that when kernel source is installed the older > version > is removed. I am not sure why, but although I have never deleted any > only the latest one ever shows up. > > -- > Robert C. Paulsen, Jr. > [EMAIL PROTECTED] > > > -- > redhat-list mailing list > unsubscribe mailto:[EMAIL PROTECTED] > https://www.redhat.com/mailman/listinfo/redhat-list -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
Re: kernel update and grub
On Thu, Aug 21, 2003 at 08:54:09AM -0500, Otto Haliburton wrote: > > > > -Original Message- > > From: [EMAIL PROTECTED] [mailto:redhat-list- > > [EMAIL PROTECTED] On Behalf Of Asbjorn Hoiland Aarrestad > > Sent: Thursday, August 21, 2003 4:18 AM > > To: [EMAIL PROTECTED] > > Subject: kernel update and grub > > > > hi! > > > > Just got word about the new kernel update, but when looking in my logs > > for the update, I just see an errormessage about "not enough space on > > /boot". This most probably because I have been installing a couple of > > kernel updates automatically using up2date, and never deleted > > anything. > > > > I have redhat 7.3 and grub installed > > > > > > How do I (commandline) delete the old kernels from grub? > > > > > > - asbj?rn > > > > > > -- > > redhat-list mailing list > > unsubscribe mailto:[EMAIL PROTECTED] > > https://www.redhat.com/mailman/listinfo/redhat-list > > You need to delete the old kernels from /boot. You can also delete them > from /usr/src. > 1) Look at the grub.conf file in /etc. The directory is in /boot (you > can go there) also. The symbolic link to the file is in /etc. > Determine which kernels you want to delete. Delete them from grub.conf > and from /boot. Remember to look at the default pointer and update it > to the new default in grub.conf. You can also go to /usr/src and delete > the old kernel directories. Be sure and make yourself a boot floppy in > case you make a mistake. Good luck A safer method is to delete the old kernels via rpm. For example my system shows: rpm -qa | grep kernel kernel-pcmcia-cs-3.1.31-13 kernel-source-2.4.20-20.9 kernel-2.4.20-19.9 kernel-2.4.20-20.9 There is one old kernel still installed: kernel-2.4.20-19.9. To delete it I would run: rpm -e kernel-2.4.20-19.9 I generally keep one back-level kernel "just in case"; thus the output above. It appears that when kernel source is installed the older version is removed. I am not sure why, but although I have never deleted any only the latest one ever shows up. -- Robert C. Paulsen, Jr. [EMAIL PROTECTED] -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
RE: kernel update and grub
> -Original Message- > From: [EMAIL PROTECTED] [mailto:redhat-list- > [EMAIL PROTECTED] On Behalf Of Asbjorn Hoiland Aarrestad > Sent: Thursday, August 21, 2003 4:18 AM > To: [EMAIL PROTECTED] > Subject: kernel update and grub > > hi! > > Just got word about the new kernel update, but when looking in my logs > for the update, I just see an errormessage about "not enough space on > /boot". This most probably because I have been installing a couple of > kernel updates automatically using up2date, and never deleted > anything. > > I have redhat 7.3 and grub installed > > > How do I (commandline) delete the old kernels from grub? > > > - asbjørn > > > -- > redhat-list mailing list > unsubscribe mailto:[EMAIL PROTECTED] > https://www.redhat.com/mailman/listinfo/redhat-list You need to delete the old kernels from /boot. You can also delete them from /usr/src. 1) Look at the grub.conf file in /etc. The directory is in /boot (you can go there) also. The symbolic link to the file is in /etc. Determine which kernels you want to delete. Delete them from grub.conf and from /boot. Remember to look at the default pointer and update it to the new default in grub.conf. You can also go to /usr/src and delete the old kernel directories. Be sure and make yourself a boot floppy in case you make a mistake. Good luck -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
Re: kernel update and grub
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 21 Aug 2003 11:17:48 +0200, Asbjorn Hoiland Aarrestad wrote: > Just got word about the new kernel update, but when looking in my logs > for the update, I just see an errormessage about "not enough space on > /boot". This most probably because I have been installing a couple of > kernel updates automatically using up2date, and never deleted anything. > > I have redhat 7.3 and grub installed > > > How do I (commandline) delete the old kernels from grub? rpm --query 'kernel*' to list installed kernel packages. cat /proc/version to list the running kernel version. rpm --erase kernel-2.4.20-18.9 to uninstall an old kernel package including its GRUB entry. - -- -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/RLxS0iMVcrivHFQRAhxXAJ0Trf14Z4sGUcNp7kzyoKFaamaWCQCeIuHo /L+TNwiFx0bRQ4CSwK6Q9eI= =kCn+ -END PGP SIGNATURE- -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
Re: kernel update and grub
> >>Just got word about the new kernel update, but when looking in my logs > >>for the update, I just see an errormessage about "not enough space on > >>/boot". This most probably because I have been installing a couple of > >>kernel updates automatically using up2date, and never deleted anything. > >> > >>I have redhat 7.3 and grub installed > >>How do I (commandline) delete the old kernels from grub? > >> > >> > >First I used "rpm -e" to remove the old kernel(s) but that caused some > >problems. So yust quick and dirty, I've removed all files (config, > >initrd, module-info, System.map , Vmlinux, > >Vmlinuz ) related to a specific kernel from /boot and removed the > >kernel entries from /boot/grub/grub.conf . > > > > > > after editing grub.conf, is there any command needed to be fun in order > to make grub understand that the config file is changed? Not to my knowledge (after editing lilo.conf you need to run lilo thats for sure), but do check the "default" (0 is the first entry, 1 the second and so on) key in grub.conf is pointing to the kernel you want to use. > I'm admining the rh box remotely and can't afford it to hang during boot. Check for self compiled kernel modules (RAID controller or NIC modules etc). Good luck. Cheers, Andre -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
Re: kernel update and grub
Andre ten Bohmer wrote: Hello, Just got word about the new kernel update, but when looking in my logs for the update, I just see an errormessage about "not enough space on /boot". This most probably because I have been installing a couple of kernel updates automatically using up2date, and never deleted anything. I have redhat 7.3 and grub installed How do I (commandline) delete the old kernels from grub? First I used "rpm -e" to remove the old kernel(s) but that caused some problems. So yust quick and dirty, I've removed all files (config, initrd, module-info, System.map , Vmlinux, Vmlinuz ) related to a specific kernel from /boot and removed the kernel entries from /boot/grub/grub.conf . after editing grub.conf, is there any command needed to be fun in order to make grub understand that the config file is changed? I'm admining the rh box remotely and can't afford it to hang during boot. - asbjørn -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
Re: kernel update and grub
Hello, > Just got word about the new kernel update, but when looking in my logs > for the update, I just see an errormessage about "not enough space on > /boot". This most probably because I have been installing a couple of > kernel updates automatically using up2date, and never deleted anything. > > I have redhat 7.3 and grub installed > How do I (commandline) delete the old kernels from grub? First I used "rpm -e" to remove the old kernel(s) but that caused some problems. So yust quick and dirty, I've removed all files (config, initrd, module-info, System.map , Vmlinux, Vmlinuz ) related to a specific kernel from /boot and removed the kernel entries from /boot/grub/grub.conf . Cheers, Andre -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
kernel update and grub
hi! Just got word about the new kernel update, but when looking in my logs for the update, I just see an errormessage about "not enough space on /boot". This most probably because I have been installing a couple of kernel updates automatically using up2date, and never deleted anything. I have redhat 7.3 and grub installed How do I (commandline) delete the old kernels from grub? - asbjørn -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
kernel update (2.4.20-13 & 18) missing files (binfmt_coff.o)
When I updated the kernel to 2.4.20-13.8 and then to 2.4.20-18.8, the file /lib/modules/2.4.20*/kernel/fs/binfmt_coff.o is missing. I tried copying the one from the previous version that had it, but it's not compatible. How do I get this file? -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
Audio Problem with latest Kernel Update
Hi all, I am absolutely not sure where to post this maybe the sound-list will be a better option. If that is the case somebody please correct me so that I may redirect my query there. I have recently installed RH 9 and was merrily using the RHN update without any problems till now. Recently about a few days back RH released the kernel update linux-2.4.20-18.9 which I dutifully applied and as warned rebooted the PC to test the latest update. But using this kernel I am unable to play any sound. Initially I thought that the problem was with the sound settings and tried playing with the settings but to no avail. Thankfully I remembered that I had updated my kernel and voila on rebooting sound plays beautifully. The system is RedHat 9.0 with all the updates applied or at least the RHN icon in the panel claims so. There is a huge blue tick so I think all the updates are applied. This is an i845 and I am using the onboard sound card. [EMAIL PROTECTED] root]# lsmod Module Size Used byNot tainted ide-cd 35708 0 (autoclean) cdrom 33728 0 (autoclean) [ide-cd] i810_audio 27720 0 (autoclean) ac97_codec 13640 0 (autoclean) [i810_audio] soundcore 6404 2 (autoclean) [i810_audio] parport_pc 19076 1 (autoclean) lp 8996 0 (autoclean) parport37056 1 (autoclean) [parport_pc lp] nfsd 80176 8 (autoclean) lockd 58704 1 (autoclean) [nfsd] sunrpc 81564 1 (autoclean) [nfsd lockd] autofs 13268 0 (autoclean) (unused) tulip 43840 1 8139too18088 1 mii 3976 0 [8139too] ipt_REJECT 3928 2 (autoclean) iptable_filter 2412 1 (autoclean) ip_tables 15096 2 [ipt_REJECT iptable_filter] microcode 4668 0 (autoclean) keybdev 2944 0 (unused) mousedev5492 1 hid22148 0 (unused) input 5856 0 [keybdev mousedev hid] usb-uhci 26348 0 (unused) usbcore78784 1 [hid usb-uhci] ext3 70784 5 jbd51892 5 [ext3] The same modules are loaded in both the cases I saved the lsmod output and compared both of them. Any other information if required please tell me I do not know what else to include. signature.asc Description: This is a digitally signed message part
Re: Trying again: kernel update for 7.3 is 2.4.20*, not 2.4.18*
> From: MKlinke <[EMAIL PROTECTED]> > Date: Sat, 7 Jun 2003 16:48:03 +0100 > On Saturday 07 June 2003 16:01, mark wrote: > > Asking again: RH 7.3 kernel updates have all been 2.4.18-*. The new > > kernel update, announced several days ago, is 2.4.20, which I have > > associated with RH8. Does anyone know if this is the correct updated > > kernel for 7.3? > You may have missed a kernel update (errata dated last month) when they > all; 7.1, 7.1, 7.3, 8.0, made the switch from 2.4.18... to 2.4.20 > > https://rhn.redhat.com/errata/RHSA-2003-172.html I had. Also, going to that page, it makes no mention of that action. But I guess we're just (l)users, and should have read the kernel list to find out Stuph (tm) Thanks! mark -- "Liberalism isn't assaulting anyone these days. It's barely alive. It's a bubble boy on life support in the coma ward. Liberalism a threat? To whom, Bambi?" --Knute Berger, Conservative Crybabies -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
Re: Trying again: kernel update for 7.3 is 2.4.20*, not 2.4.18*
On Saturday 07 June 2003 16:01, mark wrote: > Asking again: RH 7.3 kernel updates have all been 2.4.18-*. The new > kernel update, announced several days ago, is 2.4.20, which I have > associated with RH8. Does anyone know if this is the correct updated > kernel for 7.3? > > mark The errata sheets indicate this is correct. https://rhn.redhat.com/errata/RHSA-2003-187.html You may have missed a kernel update (errata dated last month) when they all; 7.1, 7.1, 7.3, 8.0, made the switch from 2.4.18... to 2.4.20 https://rhn.redhat.com/errata/RHSA-2003-172.html Regards, Mike Klinke -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
Trying again: kernel update for 7.3 is 2.4.20*, not 2.4.18*
Asking again: RH 7.3 kernel updates have all been 2.4.18-*. The new kernel update, announced several days ago, is 2.4.20, which I have associated with RH8. Does anyone know if this is the correct updated kernel for 7.3? mark -- "One of the penalties for refusing to participate in politics is that you end up being governed by your inferiors." -- Plato -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
RE: Latest Kernel update hosed me....
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 >On Fri, Mar 28, 2003 at 08:11:51AM -0800, Burke, Thomas G. wrote: >> Well, now I know. I always assumed the fileutils were statically >> linked, as there's so many situations where you need them & the >> libs may not be available. I'll bet there's static-linked ones >> out there, somewhere... Oh well, now I know. > >If memory serves me right, the ash shell consists of statically >linked binaries. It's designed for things like rescue disks. kewl, thanks. > >> I'm kind of curious why NMB is failing... Isn't that part of the >> SAMBA package? > >Yup, it's part of Samba. It may be failing because isn't your >network basically all hosed? I wouldn't worry about Samba until >after you've got functioning IP functionality. Thanks... Didin't think of that. Wasn't really worried about it yet - - like you said, gotta get everything else working, first. -BEGIN PGP SIGNATURE- Version: PGP Personal Privacy 6.5.3 iQA/AwUBPoSJLNPjBkUEZx5AEQIjmwCcCuu6cTY8I+2xESLWWDJUf1zlBL8An0pe XKzLi8bWusEkKE1dgw7qyi3a =rCKh -END PGP SIGNATURE- -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Latest Kernel update hosed me....
On Fri, Mar 28, 2003 at 08:11:51AM -0800, Burke, Thomas G. wrote: > Well, now I know. I always assumed the fileutils were statically > linked, as there's so many situations where you need them & the libs > may not be available. I'll bet there's static-linked ones out there, > somewhere... Oh well, now I know. If memory serves me right, the ash shell consists of statically linked binaries. It's designed for things like rescue disks. > I'm kind of curious why NMB is failing... Isn't that part of the > SAMBA package? Yup, it's part of Samba. It may be failing because isn't your network basically all hosed? I wouldn't worry about Samba until after you've got functioning IP functionality. .../Ed -- Ed Wilts, Mounds View, MN, USA mailto:[EMAIL PROTECTED] Member #1, Red Hat Community Ambassador Program -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Latest Kernel update hosed me....
On Fri, Mar 28, 2003 at 05:24:43AM -0800, Burke, Thomas G. wrote: > Installed the latest kernel & (I think glibc) updates for 6.2. > Rebooted machine. Kernel starts to load: beepbeepbeepbeepbeep (ad > nauseum)... > > "well shit," I think. I'll just R^2 the kernel & glibc stuff & > reinstall the older versions. > > Reboot with boot disk (unfortunately it's an old kernel, as well)... > rpm -e --force kernel (and related) and glibc (and related). Oops. The --force is there for people who only know what they're doing. rpm does lots of checking to make sure you don't shoot yourself in the foot. You told it to override those checks and hurt yourself... For kernels, you always install new ones. The old ones are available to boot from. You should have tested that first. Never, ever, remove glibc. Boy does that hurt! > Now many of the normal commands don't work (ls, more, and so on)... > Didn't realize they were somehow related to those packages. That's why rpm does the checking for you. ls is in the fileutils package: [EMAIL PROTECTED] ewilts]$ rpm -q --requires fileutils /sbin/install-info /bin/sh /bin/sh rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(CompressedFileNames) <= 3.0.4-1 libc.so.6 libc.so.6(GLIBC_2.0) libc.so.6(GLIBC_2.1) libc.so.6(GLIBC_2.1.3) libc.so.6(GLIBC_2.2) libc.so.6(GLIBC_2.2.3) libtermcap.so.2 This tells you that you can't remove glibc because fileutils requires it. > So, what the heck... Make sure I've got recent backups of /etc & > /root (don't want to lose those configs!). Reinstall 6.2 from CD, > tell it to format the appropriate patitions & go to bed. > > Get up this morning, apply all the updates (which I have on disk) > except the latest, which is what seems to have hosed my system. > > Copy my /etc directory back into /etc. Did you also get the subdirectories of /etc? That's where things like your network is (/etc/sysconfig). Did you double-check the lilo config to make sure it's pointing to the right kernel? Did you re-run lilo? > Reboot machine. > > Error - can't (write or find) /var/lib/ > - - sorry, it goes by too quickly to catch what it says (Didn't think > to hit the pause key), but it seems to be pointing to a file that has > an older set of numbers than my kernel. cat /var/log/messages dmesg You're hopefully not too far away from getting things going again... -- Ed Wilts, Mounds View, MN, USA mailto:[EMAIL PROTECTED] Member #1, Red Hat Community Ambassador Program -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
Latest Kernel update hosed me....
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Well, the subject says it all... Installed the latest kernel & (I think glibc) updates for 6.2. Rebooted machine. Kernel starts to load: beepbeepbeepbeepbeep (ad nauseum)... "well shit," I think. I'll just R^2 the kernel & glibc stuff & reinstall the older versions. Reboot with boot disk (unfortunately it's an old kernel, as well)... rpm -e --force kernel (and related) and glibc (and related). Now many of the normal commands don't work (ls, more, and so on)... Didn't realize they were somehow related to those packages. So, what the heck... Make sure I've got recent backups of /etc & /root (don't want to lose those configs!). Reinstall 6.2 from CD, tell it to format the appropriate patitions & go to bed. Get up this morning, apply all the updates (which I have on disk) except the latest, which is what seems to have hosed my system. Copy my /etc directory back into /etc. Reboot machine. Error - can't (write or find) /var/lib/ - - sorry, it goes by too quickly to catch what it says (Didn't think to hit the pause key), but it seems to be pointing to a file that has an older set of numbers than my kernel. Ethernet & NMB stuff not loading. I imagine that the ethernet stuff isn't loading because of this thing looking for the wrong version of something, but I can't imagine why, as I've douplechecked kernel versions & so on. Any clues? -BEGIN PGP SIGNATURE- Version: PGP Personal Privacy 6.5.3 iQA/AwUBPoRNFNPjBkUEZx5AEQIEWACgqt1rACLm3SfE5UM+3XpXj9GpFKYAoKQX fNUQqiwrAQeQa8hI02EJ6brk =k9IF -END PGP SIGNATURE- -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Out of Disk PSace to Insatll Kernel Update
Robert Love wrote: Thank you! Ben and Irwin I used RPM to remove some of the previous kernals then was able to run up2date -u to get the latest kernal :-) Did not want to remove anything to do with the kernal, if I did not know it was going to be safe. In general it's safe to uninstall all kernels that you aren't currently booted with. You should always keep the current kernel for 2 reasons. 1)That new kernel might not boot;-) 2)You might want to load a new module for your current kernel before you reboot. For example might want to mount a cdrom which requires the iso filesystem module. -- There is no such thing as obsolete hardware. Merely hardware that other people don't want. (The Second Rule of Hardware Acquisition) Sam Flory <[EMAIL PROTECTED]> -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Out of Disk PSace to Insatll Kernel Update
Thank you! Ben and Irwin I used RPM to remove some of the previous kernals then was able to run up2date -u to get the latest kernal :-) Did not want to remove anything to do with the kernal, if I did not know it was going to be safe. Thanks Again Robert Love - Original Message - From: "Ben Russo" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, March 21, 2003 4:18 PM Subject: Re: Out of Disk PSace to Insatll Kernel Update > Same here, I rpm -e all kernel-* rpms except the most recent two. > I've never had a problem with it. > > -Ben. > > irwin wrote: > > >I only keep one plus the current. So far no problems. > > > >Irwin > > > > > >On Friday 21 March 2003 02:40 pm, you wrote: > > > > > >>I am currently running Red Hat Linux 7.1 i386 as a web/mail server for our > >>local users group. > >> > >>I currently have the following Kernel-* Packages installed. > >> > >> kernel-2.4.18-17.7.x > >> kernel-2.4.18-18.7.x > >> kernel-2.4.18-19.7.x > >> kernel-2.4.2-2 > >> kernel-2.4.9-21 > >> kernel-2.4.9-31 > >> kernel-2.4.9-34 > >> kernel-headers-2.4.9-34 > >> > >>Up2date has another Kernel Package that is available. > >> > >> kernel-2.4.18-27.7.x > >> > >>However, I do not have enough Disk Space to install packages on the / > >>partition. > >> > >>Filesystem 1k-blocks Used Available Use% Mounted on > >>/dev/hda8 256667230189 13226 95% / > >>/dev/hda154416 21291 30316 42% /boot > >>/dev/hda6 8499136187092 7880300 3% /home > >>/dev/hda5 8499136952048 7115344 12% /usr > >>/dev/hda7 256667 92396151019 38% /var > >>none 30920 0 30920 0% /dev/shm > >> > >>Is it safe to remove the previous kernels? > >>Such as these: > >> kernel-2.4.2-2 > >> kernel-2.4.9-21 > >> kernel-2.4.9-31 > >> kernel-2.4.9-34 > >>It makes sense to keep a couple of the previous versions just in case > >>something goes wrong. > >> > >>If so is it recommended to do this through RPM or Up2Date? > >> > >>If it is not safe to remove the previous kernels does anyone have any > >>ideas on how to resolve this problem? > >> > >>Note: I have all of the other up2date upgrade/patch packages installed. > >>So I am current with the exception of this Kernel Update. > >> > >>Thank You > >>Robert Love > >> > >> > > > > > > > > > > > > -- > redhat-list mailing list > unsubscribe mailto:[EMAIL PROTECTED] > https://listman.redhat.com/mailman/listinfo/redhat-list -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Out of Disk PSace to Insatll Kernel Update
Same here, I rpm -e all kernel-* rpms except the most recent two. I've never had a problem with it. -Ben. irwin wrote: I only keep one plus the current. So far no problems. Irwin On Friday 21 March 2003 02:40 pm, you wrote: I am currently running Red Hat Linux 7.1 i386 as a web/mail server for our local users group. I currently have the following Kernel-* Packages installed. kernel-2.4.18-17.7.x kernel-2.4.18-18.7.x kernel-2.4.18-19.7.x kernel-2.4.2-2 kernel-2.4.9-21 kernel-2.4.9-31 kernel-2.4.9-34 kernel-headers-2.4.9-34 Up2date has another Kernel Package that is available. kernel-2.4.18-27.7.x However, I do not have enough Disk Space to install packages on the / partition. Filesystem 1k-blocks Used Available Use% Mounted on /dev/hda8 256667230189 13226 95% / /dev/hda154416 21291 30316 42% /boot /dev/hda6 8499136187092 7880300 3% /home /dev/hda5 8499136952048 7115344 12% /usr /dev/hda7 256667 92396151019 38% /var none 30920 0 30920 0% /dev/shm Is it safe to remove the previous kernels? Such as these: kernel-2.4.2-2 kernel-2.4.9-21 kernel-2.4.9-31 kernel-2.4.9-34 It makes sense to keep a couple of the previous versions just in case something goes wrong. If so is it recommended to do this through RPM or Up2Date? If it is not safe to remove the previous kernels does anyone have any ideas on how to resolve this problem? Note: I have all of the other up2date upgrade/patch packages installed. So I am current with the exception of this Kernel Update. Thank You Robert Love -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Out of Disk PSace to Insatll Kernel Update
I only keep one plus the current. So far no problems. Irwin On Friday 21 March 2003 02:40 pm, you wrote: > I am currently running Red Hat Linux 7.1 i386 as a web/mail server for our > local users group. > > I currently have the following Kernel-* Packages installed. > >kernel-2.4.18-17.7.x >kernel-2.4.18-18.7.x >kernel-2.4.18-19.7.x >kernel-2.4.2-2 >kernel-2.4.9-21 >kernel-2.4.9-31 >kernel-2.4.9-34 >kernel-headers-2.4.9-34 > > Up2date has another Kernel Package that is available. > >kernel-2.4.18-27.7.x > > However, I do not have enough Disk Space to install packages on the / > partition. > > Filesystem 1k-blocks Used Available Use% Mounted on > /dev/hda8 256667230189 13226 95% / > /dev/hda154416 21291 30316 42% /boot > /dev/hda6 8499136187092 7880300 3% /home > /dev/hda5 8499136952048 7115344 12% /usr > /dev/hda7 256667 92396151019 38% /var > none 30920 0 30920 0% /dev/shm > > Is it safe to remove the previous kernels? > Such as these: >kernel-2.4.2-2 >kernel-2.4.9-21 >kernel-2.4.9-31 >kernel-2.4.9-34 > It makes sense to keep a couple of the previous versions just in case > something goes wrong. > > If so is it recommended to do this through RPM or Up2Date? > > If it is not safe to remove the previous kernels does anyone have any > ideas on how to resolve this problem? > > Note: I have all of the other up2date upgrade/patch packages installed. > So I am current with the exception of this Kernel Update. > > Thank You > Robert Love -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
Out of Disk PSace to Insatll Kernel Update
I am currently running Red Hat Linux 7.1 i386 as a web/mail server for ourlocal users group. I currently have the following Kernel-* Packages installed. kernel-2.4.18-17.7.x kernel-2.4.18-18.7.x kernel-2.4.18-19.7.x kernel-2.4.2-2 kernel-2.4.9-21 kernel-2.4.9-31 kernel-2.4.9-34 kernel-headers-2.4.9-34 Up2date has another Kernel Package that is available. kernel-2.4.18-27.7.x However, I do not have enough Disk Space to install packages on the / partition. Filesystem 1k-blocks Used Available Use% Mounted on/dev/hda8 256667 230189 13226 95% //dev/hda1 54416 21291 30316 42% /boot/dev/hda6 8499136 187092 7880300 3% /home/dev/hda5 8499136 952048 7115344 12% /usr/dev/hda7 256667 92396 151019 38% /varnone 30920 0 30920 0% /dev/shm Is it safe to remove the previous kernels?Such as these: kernel-2.4.2-2 kernel-2.4.9-21 kernel-2.4.9-31 kernel-2.4.9-34 It makes sense to keep a couple of the previous versions just in case something goes wrong. If so is it recommended to do this through RPM or Up2Date? If it is not safe to remove the previous kernels does anyone have any ideas on how to resolve this problem? Note: I have all of the other up2date upgrade/patch packages installed.So I am current with the exception of this Kernel Update. Thank You Robert Love
Re: Kernel update question
On Wed, Jan 22, 2003 at 11:50:26AM -0600, John H. Clark, III wrote: > > What is the right way to remove old kernel image and configuration files > from the boot partition? rpm -q kernel will list all the kernels that are currently installed. You can then remove all but the one you are running. That should free up enough space to allow you to install a new kernel via up2date. Emmanuel -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Kernel update question
The up2date automatic update agent has filled up my boot partition. What is the right way to remove old kernel image and configuration files from the boot partition? Thanks for your help, John Clark
missing .IMG file after kernel update via up2date
Title: missing .IMG file after kernel update via up2date Hello, My system is using an ATA133 controller for the sole drive in the box and after I ran up2date and upgraded the kernel, I get a kernel panic error on reboot. I booted up with the previous kernel and looked at the lilo.conf file and there is no image file referenced in the new linux section (2.4.18-18.8.0). I can add the missing line to the lilo.conf file, but there is no related image file in the /boot folder. Should I re-run up2date or is there a way I can create the missing image file from a command? Thanks! Stuart
Re: Kernel Update: puzzling ls
At 11:48 22.10.2002, Emmanuel Seyman and Nick Lindsell said: [snip] >You don't. >You have a vmlinux-2.4.18-17.7.xsmp file and a vmlinuz-2.4.18-17.7.xsmp >one (same as the previous one but compressed). >You can't have two files with the same name in the same directory. > >One is vmlinuX, the other is vmlinuZ - the Z denoting compression > [snip] Thx guys - think I should buy me new glasses ;-) or simply attend a reading school. >You can't have two files with the same name in the same directory. That's what I thought I knew - so I got bit of nervous instead of just _looking_. RTFLS ;-) >O Ernest E. Vogelsinger (\)ICQ# 13394035 ^ -- redhat-list mailing list unsubscribe mailto:redhat-list-request@;redhat.com?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Kernel Update: puzzling ls
At 11:33 22/10/2002 +0200, you wrote: Hmm - I failed to visit /etc/grub.conf... sorry for the noise before, of course grub.conf points to the correct images. One question remains though - how come that I have 2 (!) vmlinuz-2.4.18-17.7.xsmp files in /boot? One is vmlinuX, the other is vmlinuZ - the Z denoting compression Thx, >O Ernest E. Vogelsinger (\)ICQ# 13394035 ^ -- redhat-list mailing list unsubscribe mailto:redhat-list-request@;redhat.com?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list -- redhat-list mailing list unsubscribe mailto:redhat-list-request@;redhat.com?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Kernel Update: puzzling ls
On Tue, Oct 22, 2002 at 11:33:31AM +0200, Ernest E Vogelsinger wrote: > > One question remains though - how come that I have 2 (!) > vmlinuz-2.4.18-17.7.xsmp files in /boot? You don't. You have a vmlinux-2.4.18-17.7.xsmp file and a vmlinuz-2.4.18-17.7.xsmp one (same as the previous one but compressed). You can't have two files with the same name in the same directory. Emmanuel -- redhat-list mailing list unsubscribe mailto:redhat-list-request@;redhat.com?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Kernel Update: puzzling ls
Hmm - I failed to visit /etc/grub.conf... sorry for the noise before, of course grub.conf points to the correct images. One question remains though - how come that I have 2 (!) vmlinuz-2.4.18-17.7.xsmp files in /boot? Thx, >O Ernest E. Vogelsinger (\)ICQ# 13394035 ^ -- redhat-list mailing list unsubscribe mailto:redhat-list-request@;redhat.com?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Kernel Update: puzzling ls
Hi list, maybe some kernel guru can shed a light on this. Yesterday night I ran up2date for the new kernel patch on our dual processor machine. Now, the System.map points to the new kernel map, I have 2 (!) entries for vmlinuz-2.4.18-17.7.xsmp, and module-info and vmlinuz are still linked to 2.4.9.34. ls -al /boot (edited for brevity sake) is included: lrwxrwxrwx1 27 Oct 21 23:54 System.map -> System.map-2.4.18-17.7.xsmp -rw-r--r--1 517959 Oct 8 19:02 System.map-2.4.18-17.7.xsmp -rw-r--r--1 438900 Jun 1 12:31 System.map-2.4.9-34 -rw-r--r--1 459650 Jun 1 12:22 System.map-2.4.9-34smp -rw-r--r--1 42266 Oct 8 19:02 config-2.4.18-17.7.xsmp -rw-r--r--1 261785 Oct 21 23:47 initrd-2.4.18-17.7.xsmp.img -rw-r--r--1 472190 Jun 7 12:11 initrd-2.4.9-34.img -rw-r--r--1 473325 Jun 7 12:11 initrd-2.4.9-34smp.img lrwxrwxrwx1 14 Jun 7 12:11 kernel.h -> kernel.h-2.4.9 -rw-r--r--1 409 Jun 7 12:11 kernel.h-2.4.9 lrwxrwxrwx1 20 Jun 7 12:11 module-info -> module-info-2.4.9-34 -rw-r--r--1 15436 Oct 8 19:02 module-info-2.4.18-17.7.xsmp -rw-r--r--1 13599 Jun 1 12:31 module-info-2.4.9-34 -rw-r--r--1 13599 Jun 1 12:22 module-info-2.4.9-34smp -rwxr-xr-x1 3376633 Oct 8 19:02 vmlinux-2.4.18-17.7.xsmp lrwxrwxrwx1 16 Jun 7 12:11 vmlinuz -> vmlinuz-2.4.9-34 -rw-r--r--1 1154028 Oct 8 19:02 vmlinuz-2.4.18-17.7.xsmp -rw-r--r--1 976110 Jun 1 12:31 vmlinuz-2.4.9-34 -rw-r--r--1 1050074 Jun 1 12:22 vmlinuz-2.4.9-34smp I have some burning questions: a) why is module-info still linked to 2.4.9.34? b) why is vmlinuz still linked to 2.4.9.34? c) why are both module-info and vmlinuz linked to the non-smp version of the kernel, when up2date _knows_ that it is a dual processor machine? d) why are there 2 (!!) versions for vmlinuz-2.4.18-17.7.xsmp? e) why does /proc/version say Linux version 2.4.18-17.7.xsmp ([EMAIL PROTECTED]) (gcc version 2.96 2731 (Red Hat Linux 7.3 2.96-112)) #1 SMP Tue Oct 8 12:37:04 EDT 2002 f) should I relink module-info and vmlinuz to 2.4.18-17.7.xsmp and reboot to get a "real" 2.4.18-17.7 SMP kernel? Thx 4 insights, >O Ernest E. Vogelsinger (\)ICQ# 13394035 ^ -- redhat-list mailing list unsubscribe mailto:redhat-list-request@;redhat.com?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
RE: Kernel update
The source, if you installed it, will be in /usr/src/linux-2.4 (actually a symlink to 2.4.18-3 :^) >From there: make mrproper # cleans up any old stuff laying about cp configs/kernel-2.4.18-i686-smp.config .config# Copy one of redhats configs as a starting point make menuconfig/xconfig # xconfig if your running x, menuconfig from a console -- Run through whatever changes you need to make; remember, RH builds a REALLY generic kernel :^) make dep make bzImage make modules make modules_install make install Now, before you reboot, edit lilo.conf. I like: prompt timeout=200 # give yourself more time to catch it default=linux boot=/dev/sda map=/boot/map install=/boot/boot.b message=/boot/message linear # clone these 5 lines from the existing setup image=/boot/vmlinuz # This is the main thing to change, "make install" links this to the latest kernel label=linux initrd=/boot/initrd-2.4.18-3smp.img read-only root=/dev/sda4 # This is my root, might not be yours image=/boot/vmlinuz-2.4.18-3smp label=redhat-smp # Changed from "linux", lets you boot stock redhat if needed initrd=/boot/initrd-2.4.18-3smp.img read-only root=/dev/sda4 image=/boot/vmlinuz-2.4.18-3 label=redhat-up # Also changed to match above initrd=/boot/initrd-2.4.18-3.img read-only root=/dev/sda4 Once thats done, run lilo to update the MBR and reboot. A bit quick and dirty, but thats the framework -Original Message- From: Christian Fredrickson [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 30, 2002 12:03 PM To: RedHat Subject: Kernel update I am running RedHat 7.3 on a VA Linux FullOn 2250 server. It has a Mylex DAC960 A150 RAID controller. Now RedHat ships with a driver, but my system hangs when loading the driver. I have booted into "rescue" mode from the CD and I want to install the updated driver and patch for the Mylex card, however when I follow the directions for installation, I cannot find my source tree under /usr/src (e.g. I cannot find the specified folders or files under that directory). Can someone please help me with the steps needed to find the kernel source tree, recompile the kernel, and modify LILO? Thank you, Chris -- redhat-list mailing list Unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Kernel update
I am running RedHat 7.3 on a VA Linux FullOn 2250 server. It has a Mylex DAC960 A150 RAID controller. Now RedHat ships with a driver, but my system hangs when loading the driver. I have booted into "rescue" mode from the CD and I want to install the updated driver and patch for the Mylex card, however when I follow the directions for installation, I cannot find my source tree under /usr/src (e.g. I cannot find the specified folders or files under that directory). Can someone please help me with the steps needed to find the kernel source tree, recompile the kernel, and modify LILO? Thank you, Chris -- redhat-list mailing list Unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Kernel update using up2date
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 18 June 2002 02:11 pm, Tomás García Ferrari wrote: > Did you have to manually config lilo? This is what I'm having now (on a > machine running RH 7.3 and doing the first kernel upgrade since > install): > > [root@server root]# rpm -qa | grep kernel > kernel-2.4.18-3 > kernel-2.4.18-4 > [root@server root]# rpm -q lilo > lilo-21.4.4-14 > [root@server root]# ls /etc/lilo.conf > ls: /etc/lilo.conf: No such file or directory > > Should I manually config lilo before restarting the machine? OK, it's a silly question, but I have to ask... Are you certain that you are using lilo rather than grub as your boot loader? - -- - -Michael pgp key: http://www.tuxfan.homeip.net:8080/gpgkey.txt Red Hat Linux 7.2 in 8M of RAM: http://www.rule-project.org/ - -- -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAj0P9lsACgkQn/07WoAb/Ssm4wCfaRPKRBmG6bS1A7oLG0q5umfZ qDwAn04grMDlDwI5doF1CBE6bnFFSEvU =fxNK -END PGP SIGNATURE- ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Kernel update using up2date
Did you have to manually config lilo? This is what I'm having now (on a machine running RH 7.3 and doing the first kernel upgrade since install): [root@server root]# rpm -qa | grep kernel kernel-2.4.18-3 kernel-2.4.18-4 [root@server root]# rpm -q lilo lilo-21.4.4-14 [root@server root]# ls /etc/lilo.conf ls: /etc/lilo.conf: No such file or directory Should I manually config lilo before restarting the machine? Thanks for your help! Tomás > I did the update you are talking about, and it worked fine with me. > > Regards, > > Joost Cogels +----+ Tomás García Ferrari Bigital http://bigital.com/ +----+ ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
Re: kernel update
On Wed, 2002-03-13 at 10:15, Jack Bowling wrote: > ** Reply to message from Bret Hughes <[EMAIL PROTECTED]> on Wed, 13 Mar > 2002 09:50:39 -0600 > > Can be done from the keyboard when the boot listing comes up on the next boot. > Otherwise, just go into grub.conf and change the "default" line. > Bummer. I have a remote unattended install/upgrade setup that uses the lilo -R so that if the install pukes early enough it will reboot back to the orig. Oh well lilo still works :) Bret ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
Re: kernel update
** Reply to message from Bret Hughes <[EMAIL PROTECTED]> on Wed, 13 Mar 2002 09:50:39 -0600 > On Wed, 2002-03-13 at 01:54, Jack Bowling wrote: > > ** Reply to message from "Maynard B. Fernando" <[EMAIL PROTECTED]> on Wed, 13 >Mar 2002 15:39:51 +0800 > > > > > > > to all, > > > > > > i upgraded kernel to its latest version then i found out > > > that GRUB is present instead of LILO... i'm not familiar > > > with it... in LILO, i just edit /etc/lilo.conf and run lilo... > > > what will i do? im sure i'll get error when the machine > > > gets started!!! > > > > Actually, Maynard, you will be presently surprised. There is a lot > of intelligence built into the GRUB code. Reboot and you will find > out that the kernel has already been added to the /boot/grub/grub.conf > file and everything is ready to go. > > Please wrap your outgoing messages. Oops, sorry. > > Is this grup that is smart or the fact that RedHat rpms make the > addition to grub.conf? I do like the fact that you don't have to run a > program but then you don't get a chance to test whther or not the > changes made to grub.conf were correct. I sort of got used to the lilo > -v warm and fuzzy that the kernel was going to be seen at next boot. The RPMs do all the heavy lifting of setting up grub.conf, making the intird, etc. Of course, RH in their benevolence assumes that you would like the new kernel to be the one you just installed so if you want to rearrange this, just go into grub.conf and edit away. Note that grub will scan /boot on the next reboot and list every boot image it finds, so you don't have to really go in and monkey with it if you don't want to. > While I am thinking about it and not reading the docs :O is there a grub > equivilent to lilo -R kernelname that will reboot kernelname the next > time only regardless of the default? Can be done from the keyboard when the boot listing comes up on the next boot. Otherwise, just go into grub.conf and change the "default" line. jb -- Jack Bowling mailto: [EMAIL PROTECTED] ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
Re: kernel update
On Wed, 2002-03-13 at 01:54, Jack Bowling wrote: > ** Reply to message from "Maynard B. Fernando" <[EMAIL PROTECTED]> on Wed, 13 Mar >2002 15:39:51 +0800 > > > > to all, > > > > i upgraded kernel to its latest version then i found out > > that GRUB is present instead of LILO... i'm not familiar > > with it... in LILO, i just edit /etc/lilo.conf and run lilo... > > what will i do? im sure i'll get error when the machine > > gets started!!! > > Actually, Maynard, you will be presently surprised. There is a lot of intelligence built into the GRUB code. Reboot and you will find out that the kernel has already been added to the /boot/grub/grub.conf file and everything is ready to go. Please wrap your outgoing messages. Is this grup that is smart or the fact that RedHat rpms make the addition to grub.conf? I do like the fact that you don't have to run a program but then you don't get a chance to test whther or not the changes made to grub.conf were correct. I sort of got used to the lilo -v warm and fuzzy that the kernel was going to be seen at next boot. While I am thinking about it and not reading the docs :O is there a grub equivilent to lilo -R kernelname that will reboot kernelname the next time only regardless of the default? Bret ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
Re: Re: kernel update
i have just read about GRUB in redhat's website :-) anyway, thanks for the reply! yeah, you're right sir! i was surprised what i've read about GRUB he he he i thought its like LILO :-) - Original Message From: Jack Bowling <[EMAIL PROTECTED]> Sent: Wednesday, March 13, 2002 3:54:49 PM To: <[EMAIL PROTECTED]> Subject: Re: kernel update > ** Reply to message from "Maynard B. Fernando" <[EMAIL PROTECTED]> on Wed, 13 Mar 2002 15:39:51 +0800 > > > > to all, > > > > i upgraded kernel to its latest version then i found out > > that GRUB is present instead of LILO... i'm not familiar > > with it... in LILO, i just edit /etc/lilo.conf and run lilo... > > what will i do? im sure i'll get error when the machine > > gets started!!! > > Actually, Maynard, you will be presently surprised. There is a lot of intelligence built into the GRUB code. Reboot and you will find out that the kernel has already been added to the /boot/grub/grub.conf file and everything is ready to go. > > jb > > -- > Jack Bowling > mailto: [EMAIL PROTECTED] > > > > ___ > Redhat-list mailing list > [EMAIL PROTECTED] > https://listman.redhat.com/mailman/listinfo/redhat-list ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
Re: kernel update
On Wed, 2002-03-13 at 17:24, Jack Bowling wrote: > ** Reply to message from "Maynard B. Fernando" <[EMAIL PROTECTED]> on Wed, 13 Mar >2002 15:39:51 +0800 > > > > to all, > > > > i upgraded kernel to its latest version then i found out > > that GRUB is present instead of LILO... i'm not familiar > > with it... in LILO, i just edit /etc/lilo.conf and run lilo... > > what will i do? im sure i'll get error when the machine > > gets started!!! > > Actually, Maynard, you will be presently surprised. There is a lot of intelligence >built into the GRUB code. Reboot and you will find out that the kernel has already >been added to the /boot/grub/grub.conf file and everything is ready to go. > > jb > > -- > Jack Bowling > mailto: [EMAIL PROTECTED] > > > > ___ > Redhat-list mailing list > [EMAIL PROTECTED] > https://listman.redhat.com/mailman/listinfo/redhat-list > Excepo that if he was running lilo he may need to run sbin/grub-install so that the MBR is up dated ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
Re: kernel update
** Reply to message from "Maynard B. Fernando" <[EMAIL PROTECTED]> on Wed, 13 Mar 2002 15:39:51 +0800 > to all, > > i upgraded kernel to its latest version then i found out > that GRUB is present instead of LILO... i'm not familiar > with it... in LILO, i just edit /etc/lilo.conf and run lilo... > what will i do? im sure i'll get error when the machine > gets started!!! Actually, Maynard, you will be presently surprised. There is a lot of intelligence built into the GRUB code. Reboot and you will find out that the kernel has already been added to the /boot/grub/grub.conf file and everything is ready to go. jb -- Jack Bowling mailto: [EMAIL PROTECTED] ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
kernel update
to all, i upgraded kernel to its latest version then i found out that GRUB is present instead of LILO... i'm not familiar with it... in LILO, i just edit /etc/lilo.conf and run lilo... what will i do? im sure i'll get error when the machine gets started!!! tia Maynard B. Fernando Tel. Nos.: 632.840.0881 / 632.840.0882 http://www.broline.com "Men of genius are admired, men of wealth are envied, men of power are feared, but only men of character are trusted!" ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
Re: kernel update solved
i solved this already (yesterday).. i re-install RH7.2 and repeat the same steps in updating the kernel then it worked fine! WEIRD :-) - Original Message - From: "Mike Burger" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, March 12, 2002 4:26 PM Subject: Re: kernel update > Wen you updated the lilo.conf file, did you remember to run lilo, to apply > the changes to the boot sector? > > On Tue, 12 Mar 2002, Maynard B. Fernando wrote: > > > to all, > > > > i update my kernel version to 2.4.9-31 but when i > > got the 'CRC error' when i reboot the machine... > > > > note: the update was successful and i changed the > > lilo.conf to its new version > > > > where/what was my fault? TIA :-) > > > > Maynard B. Fernando > > Tel. Nos.: 632.840.0881 / 632.840.0882 > > http://www.broline.com > > > > "Men of genius are admired, men of wealth > > are envied, men of power are feared, but > > only men of character are trusted!" > > > > > > > > ___ > > Redhat-list mailing list > > [EMAIL PROTECTED] > > https://listman.redhat.com/mailman/listinfo/redhat-list > > > > > > ___ > Redhat-list mailing list > [EMAIL PROTECTED] > https://listman.redhat.com/mailman/listinfo/redhat-list ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
Re: kernel update
Wen you updated the lilo.conf file, did you remember to run lilo, to apply the changes to the boot sector? On Tue, 12 Mar 2002, Maynard B. Fernando wrote: > to all, > > i update my kernel version to 2.4.9-31 but when i > got the 'CRC error' when i reboot the machine... > > note: the update was successful and i changed the > lilo.conf to its new version > > where/what was my fault? TIA :-) > > Maynard B. Fernando > Tel. Nos.: 632.840.0881 / 632.840.0882 > http://www.broline.com > > "Men of genius are admired, men of wealth > are envied, men of power are feared, but > only men of character are trusted!" > > > > ___ > Redhat-list mailing list > [EMAIL PROTECTED] > https://listman.redhat.com/mailman/listinfo/redhat-list > ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
Re: kernel update
what version of kernel you recommended most? - Original Message - From: "Statux" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, March 12, 2002 1:17 PM Subject: Re: kernel update > CRC errors happen a lot now adays. I usually either reset the system or > write BIOS settings out (depending on where the CRC error is occuring). > > On Tue, 12 Mar 2002, Maynard B. Fernando wrote: > > > to all, > > > > i update my kernel version to 2.4.9-31 but when i > > got the 'CRC error' when i reboot the machine... > > > > note: the update was successful and i changed the > > lilo.conf to its new version > > > > where/what was my fault? TIA :-) > > > > Maynard B. Fernando > > Tel. Nos.: 632.840.0881 / 632.840.0882 > > http://www.broline.com > > > > "Men of genius are admired, men of wealth > > are envied, men of power are feared, but > > only men of character are trusted!" > > > > > > > > ___ > > Redhat-list mailing list > > [EMAIL PROTECTED] > > https://listman.redhat.com/mailman/listinfo/redhat-list > > > > -- > -Statux > > > > ___ > Redhat-list mailing list > [EMAIL PROTECTED] > https://listman.redhat.com/mailman/listinfo/redhat-list ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
Re: kernel update
CRC errors happen a lot now adays. I usually either reset the system or write BIOS settings out (depending on where the CRC error is occuring). On Tue, 12 Mar 2002, Maynard B. Fernando wrote: > to all, > > i update my kernel version to 2.4.9-31 but when i > got the 'CRC error' when i reboot the machine... > > note: the update was successful and i changed the > lilo.conf to its new version > > where/what was my fault? TIA :-) > > Maynard B. Fernando > Tel. Nos.: 632.840.0881 / 632.840.0882 > http://www.broline.com > > "Men of genius are admired, men of wealth > are envied, men of power are feared, but > only men of character are trusted!" > > > > ___ > Redhat-list mailing list > [EMAIL PROTECTED] > https://listman.redhat.com/mailman/listinfo/redhat-list > -- -Statux ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
kernel update
to all, i update my kernel version to 2.4.9-31 but when i got the 'CRC error' when i reboot the machine... note: the update was successful and i changed the lilo.conf to its new version where/what was my fault? TIA :-) Maynard B. Fernando Tel. Nos.: 632.840.0881 / 632.840.0882 http://www.broline.com "Men of genius are admired, men of wealth are envied, men of power are feared, but only men of character are trusted!" ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
Kernel update questions
Hi all, A couple of questions about moving to 2.4.0-1 Current config: RH 7 with all updates and errata: 1. I have kernel-headers and kernel source downloaded. 2. I have bin86 downloaded 3. Upon trying to install with gnorpm I find kernel-headers-2.4.0-0.43 already on the machine. This has multiple dependencies and I am not sure if I can uninstall these headers without totally crapping up the machine. I tried to select 'upgrade' but received a large number of unmet dependencies. 4. Do I need to install bin86? Dev86 is installed, I just don't know if a new kernel will see it when I try to build the new kernel. All suggestions appreciated. -- Bob Hartung www.radiologygrouppc.com ___ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
Re: kernel update RPM
On Wed, 26 Jul 2000 18:47:52 -0700, you wrote: >I downloaded the source RPM, and I can build it fine, but the kernel >version is 2.2.16, ie. it does not have the -3. I noticed a number of >patch files in the redhat/SOURCES directory, do these need to be >applied, and if so which? I tried applying all of them, and some of the Look at SPECS/kernel-2.2.spec for how redhat builds its kernel. If you want to make a custom kernel you have 3 choices: 1) download stock 2.2.16 and do it on your own. 2) Use redhat srpm: take the patches you like from SOURCES (look at the spec file for the order in which they are applied) and do it on your own 3) Use redhat srpm and follow their method: a) rpm -bp SPEC/... b) go in BUILD/linux and make menuconfig, personalize c) copy .config to SOURCES/kernel-2.2.16-i586.config or the appropriate config file d) edit SPECS/... and change release from 3 to 3.mine e) rpm -ba SPECS/... you'll end up with all the custom kernel rpms, the kernel will be: 2.2.16-3.mine -- [EMAIL PROTECTED] -- To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe" as the Subject.
Re: kernel update RPM
In general, the naming scheme is as follows: packagename-version.release.build-identifier Or something like that... everything in the -identifier field is for the compiler's information, to distinguish one compile from another (maybe to indicate the patch version?). Most people don't use that -identifier field unless it's being distributed. So, don't worry about the -3 not appearing. As for needing/wanting/using the RedHat patches... that's another issue. Lee Howard At 06:47 PM 7/26/00 -0700, you wrote: >A newbe question, I have just updated to the kernel-2.2.16-3 using the >RPM, and that went fine, so I thought I would build a custom kernel, so >I downloaded the source RPM, and I can build it fine, but the kernel >version is 2.2.16, ie. it does not have the -3. I noticed a number of >patch files in the redhat/SOURCES directory, do these need to be >applied, and if so which? I tried applying all of them, and some of the >applys failed. > >Any advice? > >Thanks > >Rich Gibbs > > >-- >To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe" >as the Subject. > -- To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe" as the Subject.
kernel update RPM
A newbe question, I have just updated to the kernel-2.2.16-3 using the RPM, and that went fine, so I thought I would build a custom kernel, so I downloaded the source RPM, and I can build it fine, but the kernel version is 2.2.16, ie. it does not have the -3. I noticed a number of patch files in the redhat/SOURCES directory, do these need to be applied, and if so which? I tried applying all of them, and some of the applys failed. Any advice? Thanks Rich Gibbs -- To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe" as the Subject.
kernel update
I saw the updates for the kernel packages. So I updated---though I do not know why since the errata does not mention the kernel packages. In any case, the new kernel would not boot: it was looking for modules.dep in /lib/modules/2.0.34. I also realized that the new kernel package does not install modules.dep at all. So I did a quite forbidding thing: ln -s ../2.0.34-1 /lib/modules/2.0.34 cp -a /lib/modules/2.0.34-0.6/modules.dep /lib/modules/2.0.34 How does modules.dep get created? Thx --- Mate Wierdl | Dept. of Math. Sciences | University of Memphis -- PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES! http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips /mailing-lists To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe" as the Subject.
