Ulf wrote:

Hi,

...

What are you heading for?

many management tools, like vmware tools or hp ilo driver have their own modules. These module have to fit to the running kernel. # modinfo hp_ilo.ko | grep vermagic vermagic: 2.6.16.54-0.2.5-smp SMP gcc-4.1

My intention is to put the hp-ilo.spec file into the build service and get a valid rpm for all kernel versions. Or should I force the newer kernel to load an "older" module?

You just have to build for each SP kernel and use that same kernel module on all the update kernels for that SP. I.e., kernel modules built for SLES 10 will load on all kernel updates until SLES 10 SP1. Kernel modules built for SLES 10 SP1 will load on all kernel updates until SLES 10 SP2. Etc. This is because on SLES, the kABI is held stable between SPs and the SLES kernel update process automatically "reuses" kernel mods if the kABI has not changed. There is no need to force the install of the kernel mods. openSUSE is different because the kABI is not stable. See http://www.novell.com/communities/node/5684/developing-software-products-sus... Make sure to look at the referenced docs that discuss kABI stability in SLES, etc. Hope this helps, Ann Ann

Regards, Ulf

--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org