Hi,
Thanks to all of you for your replies and insight.
I'm already disallowing kernel-updates via zypper, so already
installed systems are not causing any problem - only newly deployed.
I have sovled this, not in a good way, by removing the kernel-packages
that does not work from my installation repository. As a few of you
suggested as a solution.
It solves the problem, and I believe it's better than reinstalling the
kernel using init-script or similar (at least a lot less hacking ;)),
although I hoped I could solve this directly in autoyast :)
Again, thanks for your reply and valuable insight!
Have a nice weekend!
/ Alexander
On Fri, Oct 21, 2011 at 11:33 PM, Mike Marion
On Fri, Oct 21, 2011 at 07:01:49PM +0100, Magyari, Miklos wrote:
If you use your own repo, you may try to remove kernels newer than the one you need, so 2.6.32.45 will be installed.
That would be my suggestion. This is one reason we don't do auto updates via smt into our install repo. With a lot of the EDA tools we support being very touchy with updates, we have smt repos that we copy in the updated stuff when/if needed and tested, into our own updates path.
-- Mike Marion-Unix SysAdmin/Staff IT Engineer-http://www.qualcomm.com Peter: "Oh my God! Brian, there's a message in my Alphabits.. it says, 'oooooo'" Brian: "Peter, those are Cheerios!" -- Family Guy.
-- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner@opensuse.org