search for: updatedefault

.. in that expected way where newly installed kernel is set to boot as default. would you suggest where to look, what to check? many thanks.

Just updated another machine to 5.3, everything fine, but grub.conf wasn't updated to the 128 kernel. It got a new modified date and the kernel is there, but the content wasn't changed. /etc/sysconfig/kernel contains the correct UPDATEDEFAULT=yes No errors in logs or during the update. No problem to boot with this kernel once added. This is the first time I ever see this happen. Any clues? Kai -- Kai Sch?tzl, Berlin, Germany Get your web at Conactive Internet Services: http://www.conactive.com

Le 26/01/2016 12:53, lejeczek a ?crit : > .. in that expected way where newly installed kernel is set to boot as > default. > > would you suggest where to look, what to check? In /etc/sysconfig/kernel : # UPDATEDEFAULT specifies if new-kernel-pkg should make # new kernels the default UPDATEDEFAULT=yes -- Philippe BOURDEU d'AGUERRE AIME - Campus de l'INSA http://www.aime-toulouse.fr/ 135 av. de Rangueil T?l +33 561 559 885 31077 TOULOUSE Cedex 4 - FRANCE Fax +33 561 559 870

It appears that if I do anything to grub.conf, say, take out the rhgb quiet, after every succeding kernel update, I have to manually edit grub.conf, because the kernel update - maybe the post install script? - will set the default to be the previous kernel. Has anyone got a solution to this, so that a kernel update will give the new kernel as the default? mark

...ndex=0 options snd-hda-intel index=0 remove snd-hda-intel { /usr/sbin/alsactl store 0 >/dev/null 2>&1 || : ; }; /sbin/modprobe -r --ignore-remove snd-hda-intel [root@server ~]# [root@server ~]# [root@server ~]# [root@server ~]# [root@server ~]# [root@server ~]# cat /etc/sysconfig/kernel # UPDATEDEFAULT specifies if new-kernel-pkg should make # new kernels the default UPDATEDEFAULT=yes # DEFAULTKERNEL specifies the default kernel package type DEFAULTKERNEL=kernel alias scsi_hostadapter0 aacraid [root@server ~]# [root@server ~]# [root@server ~]# Please advise what to do to get rid of this...

Hello, we run approximately 400 Centos servers at our company. We use cfengine for configuration management. I am looking for some documentation to do patching including kernel patches. I was thinking of just having each host run yum update via cfengine but not sure if there are any gotchas there? Should I just do yum update? or should i exclude the kernel and be more careful with those? how

Trying to get Xen going on Fedora 9. Xen was installed from the distro RPMs. Xen version is 3.2.0 and the linux-xen version is 2.6.25.3. Xen seems to come up fine, but the system just hangs at the point where booting of Dom0 should start. There is absolutely no output from Dom0. I configured Xen to log to a serial port and captured the output below. Any suggestions on how to continue