John Summerfield wrote:
Andrew Farris wrote:
John Summerfield wrote:
See my earlier posts for details; this still persists.
I've not noticed that anyone's asking for information.
Photo at http://js.id.au/img2038.jpeg
It's a bit blurry, I think the camera doesn't handle the contrast
well, but it is legible.
I've had this on some kernels and not on others, but what is more
interesting is it can go away depending on what kernel you installed
them from. There was talk of a mkinitrd error when installing from
2.6.24 kernels, but I get that problem for some kernels when I install
from 2.6.23-1 and not for others, and sometimes they install fine from
the latest.
My advice.. keep lots of prior kernels, I've currently got
installonlyn=10, and I've locked the oldest kernel to not get removed as
I was wondering about this:
installonly_limit=8
installonlypkgs=kernel*
I then did a
yum install kernel
and there was only one left.
Sorry I for the delay. What I have setup is this:
/etc/yum/pluginconf.d/versionlock.conf
[main]
enabled = 1
locklist = /etc/yum/pluginconf.d/versionlock.list
/etc/yum/pluginconf.d/versionlock.list
0:kernel-2.6.24.1-28.fc9.i686
0:kernel-2.6.25-0.40.rc1.git2.fc9.i686
0:kernel-2.6.25-0.82.rc3.git2.fc9.i686
You need to have fixed yum-versionlock which is broken, see bz:
https://bugzilla.redhat.com/show_bug.cgi?id=433581
By default the kernel is included in installonlypkgs, so you don't really need
to set that (and there may be others included in default you're not now including).
The newer kernels are installing fine for me from 2.6.24.1-28 (which is why I
still have it).
--
Andrew Farris <lordmorgul@xxxxxxxxx> www.lordmorgul.net
gpg 0xC99B1DF3 fingerprint CDEC 6FAD BA27 40DF 707E A2E0 F0F6 E622 C99B 1DF3
No one now has, and no one will ever again get, the big picture. - Daniel Geer
---- ----
--
fedora-test-list mailing list
fedora-test-list@xxxxxxxxxx
To unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-test-list
