-----BEGIN PGP SIGNED MESSAGE-----
On 8/20/15 10:37 AM, Takashi Iwai wrote:
On Thu, 20 Aug 2015 16:01:30 +0200, Jeff Mahoney
On 8/19/15 6:42 AM, Jiri Slaby wrote:
On 08/19/2015, 12:29 PM, Michal Marek wrote:
> As maintainer of VirtualBox on openSUSE, I
would like to
> know how to prevent this in the future. My understanding of
> the build process is rather rudimentary.
The "proper" fix would be to reintroduce the ksym()
dependencies, i.e. make the KMPs depend on the kernel ABI
checksums rather than the kernel release string.
Which leads to another question: why do we still fight with
kabi in opensuse when we don't leverage from that?
Sidenote: if we don't use kabi, we can drop it and can update
to higher major kernel versions easier, if needed (e.g. once,
to the next longterm stable).
Isn't the major issue that widely-used third party modules like
nvidia and fglrx would also need to be rebuilt? That's the
biggest reason I always wanted to keep the kABI stable.
Yes, they need rebuilds, but I don't think there would be any kABI
checks. IIRC, they (both Nvidia and AMD) switched to a packaging
way to compile the module at the package installation time instead
of KMPs. But I myself haven't used them, so others can explain
Yeah, I'd appreciate an update on what the current state of those are.
I don't use either of those modules either, but wanted to make sure
we could present a path of least pain to users who do. If that's not
working, I'd consider that a bug.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
-----END PGP SIGNATURE-----
To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org