Locking Down The Current Kernel

Hello all, I'm hoping someone may be able to answer this question.
I am currently running Susu 10.1 and want to permenantly keep the kernel I am currently running (2.6.16.13-4-smp)
and do not want to update to newer kernels via the online updater.
Keeping the older kernel may be odd, but I am developing a template that will be used by 100 or so people, and since I have experienced odd behaviours when I update to a newer kernel, I would like to make sure the 100 or so people will have a stable
environment, as I have now under 2.6.16.13-4.
I pretty sure out of the number of people getting this template there will be many that will click the updater globe and take the kernel updates, therefore getting a system that will exhibit odd behaviour.
It seems as though all the settings I try from with YAST - Software Management/ and Online Updates only stay valid for that session.

I hope I explained this well enough, as it may seem like an odd request.

Does anybody know how I can permamenty mark the kernel as do not upgrade or modify?


Darrylc1

I think that if you lock a component in the YaST software management area or mark is as taboo, the zen updater respects that - although I'm not 100% sure.

Next time an update for something appears, lock that component in yast, then see if the zen updater ignores it or updates it anyway.

Eds

EDS, thanks for your quick reply. I do believe the "taboo" marking is only valid for that session, however I will take you advice and try it again. I hope you are correct, as that would help with my problem.

--darrylc1

Okay, I tried the taboo and Do not modify option but it seemed to only lock them down for the current session. Darn..
Hopefully I'm not doing something overly wrong here..

So any peeps out there that may have any other suggestions?

Eds thanks for you quick reply again and it was muchly appreciated and hopefully someone has more suggestions?

--darryl

Have you tried Smart? If that correctly locks could you force the use of Smart over Yast for updates?

you can remove your kernel from your rpm-database, so NONE of the package-managers will ever touch your kernel. But you won't receive any message for a kernel-update and have to check this manually.

rpm -e --justdb kernel-default or
rpm -e --justdb kernel-smp
will do the trick. If you're using some kernel-modules you have to remove this modules also from the database, otherwise you will receive messages that a kernel-package is missing.

The kernel-files are still in place, only the database entry is gone

to reinstall the kernel-information in your rpm-database you need the kerenl-package!
this is done with the command:
rpm -i --justdb /path-to/kernel-package

oc2pus, that seems to work fine, as the kernel upgrade notifications are gone.
Again, thamks so much for taking the time to answer this question.

Cheers

Darryl

oc2pus, that seems to work fine, [/b]

I thought it was nice, simple, sensible response. I was quite impressed.