New kernel, should be the default

Panu Matilainen pmatilai at welho.com
Sat Oct 9 14:04:39 UTC 2004


On Sat, 2004-10-09 at 07:40, Matias Féliciano wrote:
> Le vendredi 08 octobre 2004 à 14:56 -0400, seth vidal a écrit :
> > On Fri, 2004-10-08 at 12:39, Matias Féliciano wrote:
> > > Editing /boog/grub/grub.conf should be require only if something goes
> > > wrong.
> > 
> > 
> > Okay here's how it is.
> > 
> > in yum 2.0.X if a new kernel was installed then after the transaction
> > completed yum would edit the grub.conf or the lilo.conf to make the new
> > kernel the default.
> > 
> 
> Just curious, why is this not done at rpm level ?

Whether to default to new kernel which can be unwanted in certain
situations or not is a policy question which doesn't belong to rpm
level. Doesn't belong to depsolvers either. All we really need is
something like /etc/sysconfig/kernel where you can put 
MAKEDEFAULT=yes|no
and make new-kernel-pkg honor that, eg:

--- new-kernel-pkg.orig	2004-10-09 16:35:56.000000000 +0300
+++ new-kernel-pkg	2004-10-09 16:43:37.403284208 +0300
@@ -22,6 +22,8 @@
     grubby=/sbin/grubby
 fi
 
+[ -f /etc/sysconfig/kernel ] && . /etc/sysconfig/kernel
+
 cfgGrub=""
 cfgLilo=""
 runLilo=""
@@ -87,6 +89,8 @@
 	return
     fi
     
+    [ "$MAKEDEFAULT" = "yes" ] && makedefault="--make-default"
+    
     INITRD=""
     if [ -f $initrdfile ]; then
 	[ -n "$verbose" ] && echo "found $initrdfile and using it with grubby"

	- Panu -




More information about the test mailing list