Description of problem:
I had 2 up kernels and 4 smp kernels installed. I wanted to free some
few disk space so i invoked "rpm -e kernel-fooversion ; rpm -e
kernel-smp-fooversion kernel-smp-barversion". Once those commands
returned, the default kernel in grub.conf was set to the only UP
kernel I kept. The previous 'default' was the kernel i'm currently
running. The default should have been either my current kernel or the
newer smp kernel still installed as i'm on a dual athlon system.
Maybe a grubby problem ? (i have mkinitrd-3.5.22-1)
Packages i had: kernel-2.6.5-1.353 kernel-2.6.5-1.356
kernel-smp-2.6.5-1.327 kernel-smp-2.6.5-1.349 kernel-smp-2.6.5-1.353
Current kernel: 2.6.5-1.349smp
Packages i removed: kernel-2.6.5-1.353 kernel-smp-2.6.5-1.353
Default kernel after removal: kernel-2.6.5-1.356
grubby doesn't really have any logic to handle this, instead all of
the "magic" is in higher-level tools such as up2date, yum and apt. If
you remove your current default then it falls back to the first (or
might be last, don't remember off the top of my head) image with the
same rootdev in your boot loader config.
wth is that.. I didnt install any new kernels and "something" keeps
reseting the default kernel to the uni-processor instead of the smp
one in the grub.conf. I've just upgraded some packages today, nothign
What tool did you use to update? I suspect this may be an apt problem
with Panu's more recent kernel handling lua scripts. Panu?
yeah it was apt-0.5.15cnc6-0.fdr.11.2...
Please open a new bug in fedora.us Bugzilla against the apt component.
The luas could possibly be refined to avoid causing this type of
situation upon package remove.
Hmm, yeah, I think someone mentioned seeing some odd behavior with
default kernel getting changed but the information wasn't sufficient
for me to reproduce. I'll have a better look at it this time but lets
close this bug here, not RH's headache.