On Jul 23, 2014, at 2:57 PM, Lee Duncan <lduncan@suse.com> wrote:
I have several questions:
- Why does my system have a newer 3.0.101 kernel and the build service have an older one? The build service is only enabling the SLES11-SP3-Pool repo (the complete repo as of the time SP3 shipped, and a superset of the DVD), not SLES11-SP3-Updates. There have of course been several kernel updates since the release of SP3.
Perhaps someone else can explain how to enable the SP3-Updates repo for your build, or if it is even possible to do so with OBS. I myself don't know, but would also like to learn...
- Can I specify 3.0.101, or should I just patch against 3.0.76? If you can get the updates repo enabled, then you can build against the latest version, but if you can patch against the older version (and the kernel ABI hasn't changed since [1]), that might be preferable, since you'd have one package that would work with all kernel versions for a given OS/SP release. Of course, getting your patch mainlined might be the better option...
- How do I know what kernel a particular OS flavor will use in general? Look at the kernel packages in the SLES-SPn-Pool repo, or the oss repo for opensuse (or a DVD ISO for either). Without update repos this is what will be used.
-Andrew [1] See https://www.novell.com/developer/Kmpm-code11.pdf -- kernel packages have RPM provides/requires for some driver symbols. This is why some kmp RPMs get updated with some kernel updates, but not all.-- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org