Hey,
I ran a yum update and it installed a new kernel.
...
Installed: kernel.x86_64 0:2.6.32-71.29.1.el6 kernel-devel.x86_64 0:2.6.32-71.29.1.el6
but it did not modify the grub.conf file.
#boot=/dev/sda default=0 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title CentOS (2.6.32-71.el6.x86_64) root (hd0,0) kernel /vmlinuz-2.6.32-71.el6.x86_64 ro root=UUID=... initrd /initramfs-2.6.32-71.el6.x86_64.img
Is this the new behavior or...?
Thx,
JD
On Fri, 5 Aug 2011, John Doe wrote:
To: Cent O Smailinglist centos@centos.org From: John Doe jdmls@yahoo.com Subject: [CentOS] CentOS 6 kernel update and grub.conf...
Hey,
I ran a yum update and it installed a new kernel.
...
Installed: kernel.x86_64 0:2.6.32-71.29.1.el6 kernel-devel.x86_64 0:2.6.32-71.29.1.el6
but it did not modify the grub.conf file.
#boot=/dev/sda default=0 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title CentOS (2.6.32-71.el6.x86_64) root (hd0,0) kernel /vmlinuz-2.6.32-71.el6.x86_64 ro root=UUID=... initrd /initramfs-2.6.32-71.el6.x86_64.img
Is this the new behavior or...?
I'm only on C5.6 still :)
Have you moved grub.conf at all - like to a different boot partition, or changed any symlinks to grub.conf?
I moved my grub.conf to a seperate boot partition some time ago, and the rpm installer does not update grub.conf now. So in a way that's a mixed blessing, because I can use yum update each night, and if there is a kernel update it won't actually run the new kernel untill I change the grub.conf entry manually.
Kind Regards,
Keith Roberts
----------------------------------------------------------------- Websites: http://www.karsites.net http://www.php-debuggers.net http://www.raised-from-the-dead.org.uk
All email addresses are challenge-response protected with TMDA [http://tmda.net] -----------------------------------------------------------------
From: Keith Roberts keith@karsites.net
I ran a yum update and it installed a new kernel. but it did not modify the grub.conf file. Is this the new behavior or...?
Have you moved grub.conf at all - like to a different boot partition, or changed any symlinks to grub.conf?
I did not move anything; it is a brand new install... The only thing that might be out of ordinary is that the yum update is made from a kickstart chrooted post script...
Thx, JD
On Mon, 8 Aug 2011, John Doe wrote:
To: CentOS mailing list centos@centos.org From: John Doe jdmls@yahoo.com Subject: Re: [CentOS] CentOS 6 kernel update and grub.conf...
From: Keith Roberts keith@karsites.net
I ran a yum update and it installed a new kernel. but it did not modify the grub.conf file. Is this the new behavior or...?
Have you moved grub.conf at all - like to a different boot partition, or changed any symlinks to grub.conf?
I did not move anything; it is a brand new install... The only thing that might be out of ordinary is that the yum update is made from a kickstart chrooted post script...
I've never done one of them - so I wouldn't know. Maybe that is where the problem is?
So are you telling me you do a fresh installation AND an update all in one go?
I think it's best to do the initial installation and then reboot the machine to run from the kernel you have just installed. There maybe things that need to be setup during the first boot that are being missed if trying to do to much from the kickstart install media.
You might like to check out my Auto Linux Installer scripts here:
http://www.karsites.net/centos/anyuser/auto-linux-installer.php
On centos 5.6 I use them to do a minimal kickstart installation that sets the machine up. Then the rest of the installation is completed from another ALI script.
Plus you can automatically setup the system services using these scripts.
Kind Regards,
Keith Roberts
----------------------------------------------------------------- Websites: http://www.karsites.net http://www.php-debuggers.net http://www.raised-from-the-dead.org.uk
All email addresses are challenge-response protected with TMDA [http://tmda.net] -----------------------------------------------------------------
From: Joseph L. Casale jcasale@activenetwerx.com
You don't need to do that. Add the updates repo as a 'repo' line in the ks, it will install anything new at once saving time and cruft.
The thing is that I setup the kickstart with the target network configured (which will not work in our office), and then, in the post script, I temporarily switch to a temporary network config... I set it up this way because in the past I wanted to be able to make a whole install without needing network access... I guess I would need to reverse the configs now.
From: Keith Roberts keith@karsites.net
So are you telling me you do a fresh installation AND an update all in one go?
I do *everything* in the chrooted post, so that I can just shutdown after install and the server is ready to be plugged. It used to work fine with 5.x... Everything also seems to work fine for 6.x, except for grubby. I caught a "Grubby fatal error : unable to find a suitable template". Found many bug reports (some as old as 2004), but no real fix... For now, I just add the entry to grub.conf in my script and it boots fine on the new kernel. I noticed that if I run the new-kernel-pkg after the reboot, it does not complain anymore and the root in grub.conf is different: The one added by new-kernel-pkg (after a reboot): kernel /vmlinuz-2.6.32-71.29.1.el6.x86_64 ro root=LABEL=/ The one I added (that works too): kernel /vmlinuz-2.6.32-71.29.1.el6.x86_64 ro root=UUID=abd50638... Original: kernel /vmlinuz-2.6.32-71.el6.x86_64 ro root=UUID=abd50638...
Thx, JD
On Mon, 8 Aug 2011, John Doe wrote:
*snip*
I do *everything* in the chrooted post, so that I can just shutdown after install and the server is ready to be plugged. It used to work fine with 5.x... Everything also seems to work fine for 6.x, except for grubby. I caught a "Grubby fatal error : unable to find a suitable template". Found many bug reports (some as old as 2004), but no real fix... For now, I just add the entry to grub.conf in my script and it boots fine on the new kernel. I noticed that if I run the new-kernel-pkg after the reboot, it does not complain anymore and the root in grub.conf is different: The one added by new-kernel-pkg (after a reboot): kernel /vmlinuz-2.6.32-71.29.1.el6.x86_64 ro root=LABEL=/ The one I added (that works too): kernel /vmlinuz-2.6.32-71.29.1.el6.x86_64 ro root=UUID=abd50638... Original: kernel /vmlinuz-2.6.32-71.el6.x86_64 ro root=UUID=abd50638...
My system is obviously set up differently than yours, and my installtion methods are different as well.
Whenever there's a kernel update on my system, the new kernel packages are installed, and the grub.conf file does not get updated. Which is THE WAY I want it to be. I never did like the way grub.conf got updated behind my back, so to speak, after a kernel update.
Now I don't need to worry about a new kernel busting anything, as the previous working kernel will be booted, even after a kernel update.
It's only 3 lines in grub.conf to add for a kernel update- so it's not a problem at all.
I also keep the original grub.conf entry for the default kernel of the installation DVD disk. That way if I ever need to do a fresh installation from DVD using a kickstart file, I already have that entry in my own custom grub.conf file.
Kind Regards,
Keith Roberts
----------------------------------------------------------------- Websites: http://www.karsites.net http://www.php-debuggers.net http://www.raised-from-the-dead.org.uk
All email addresses are challenge-response protected with TMDA [http://tmda.net] -----------------------------------------------------------------
Whenever there's a kernel update on my system, the new kernel packages are installed, and the grub.conf file does not get updated. Which is THE WAY I want it to be. I never did like the way grub.conf got updated behind my back, so to speak, after a kernel update.
Now I don't need to worry about a new kernel busting anything, as the previous working kernel will be booted, even after a kernel update.
I haven't followed this thread too closely, but if you set UPDATEDEFAULT=no in /etc/sysconfig/kernel .. the new kernel will be installed, grub will be modified, but the default line which is used to choose the default kernel will *NOT* be updated.
Barry
I did not move anything; it is a brand new install... The only thing that might be out of ordinary is that the yum update is made from a kickstart chrooted post script...
You don't need to do that. Add the updates repo as a 'repo' line in the ks, it will install anything new at once saving time and cruft.
-
Barry Brimer -
John Doe -
Joseph L. Casale -
Keith Roberts