http://bugzilla.opensuse.org/show_bug.cgi?id=1194723 http://bugzilla.opensuse.org/show_bug.cgi?id=1194723#c15
Martin Wilck martin.wilck@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |m.schenker@posteo.de Flags| |needinfo?(m.schenker@posteo | |.de)
--- Comment #15 from Martin Wilck martin.wilck@suse.com --- (In reply to Michal Suchanek from comment #14)
It would be nice to build them in advance but even on Debian (the d in dkms stands for Debian IIRC) this is best effort.
I think it's _D_ell. They invented it, AFAIR. It pre-dates KMPs.
There is also the question what is specifically passed to the kernel.d scripts.
If we want it to be generic, we should pass all parameters from the kernel scriptlet. But...
Does it get just called once when something with kernels changes, or is it called for each kernel added/removed with some specific arguments that describe the event?
If we just care about dkms, we could take weak_modules2 as example. It's run like this:
%post (or %posttrans): weak-modules2 --add-kernel "$kernelrelease"-"$flavor" %postun: weak-modules2 --remove-kernel "$kernelrelease"-"$flavor"
These arguments should be sufficient for the DKMS script, too. Or not?