R-R-R Revisited
Olaf Olson
oolson at hadleyconnection.com
Thu Oct 7 15:02:21 MDT 2004
I received an answer to my question, via the yum mail list. The answer
is simple - mostly. Remove the kernel upgrade! Since it isn't really
being used, remove it and yum update kernel and voila! Pardon my French.
So... how to do that:
rpm -e kernel-2.4.22-2g
and then yum update kernel
That's according to Seth Vidal, Mr. YUM, himself. I also got advice to:
rpm -e --justdb --nodeps packagename
but I had a little trouble understanding that packagename wasn't kernel,
but was kernel-2.4.22-2g
The second form would just remove the single package and not touch the
dependencies. justdb means only the database, not the filesystem, which
should mean that it would force yum to believe that an update or install
hadn't taken place and would, therefore, redo it. The latter is helpful
when something's not working right, but you don't want it to stop
working completely before you reinstall it.
Anyway, I'm now fully restored and happily running.
Olaf
Olaf Olson wrote:
> OK. Mostly I am working after the reinstall, except...
>
> The current kernel is 2.4.22a - that's the one from the CD. I had once
> upgraded to 2.4.22g, using yum update. Sadly, because I didn't wipe
> all partitions and reinstall, yum still thinks I have 2.4.22g, so yum
> update sees nothing to update. Yet, my 2.4.22g kernel isn't there.
>
> How do I tell yum that?
>
> Olaf
> _______________________________________________
> yellowdog-general mailing list
> yellowdog-general at lists.terrasoftsolutions.com
> http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-general
> HINT: to Google archives, try '<keywords> site:terrasoftsolutions.com'
>
More information about the yellowdog-general
mailing list