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
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 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?
[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?
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?
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?
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 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 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 (configkernel, initrdkernel, module-infokernel, System.mapkernel , Vmlinuxkernel, Vmlinuzkernel ) 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
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 (configkernel, initrdkernel, module-infokernel, System.mapkernel , Vmlinuxkernel, Vmlinuzkernel ) 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
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 (configkernel, initrdkernel, module-infokernel, System.mapkernel , Vmlinuxkernel, Vmlinuzkernel ) 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
-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
-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
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
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 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
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
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
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
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
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
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 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
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: 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 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
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 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
** 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
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: 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
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
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 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.
