Advising in packages to load new module or reboot
Jason A. Donenfeld
Jason at zx2c4.com
Wed Aug 9 01:30:50 CEST 2017
On Wed, Aug 9, 2017 at 1:27 AM, Jonathon Fernyhough
<jonathon.fernyhough at york.ac.uk> wrote:
> On 09/08/17 00:16, Jason A. Donenfeld wrote:
>> 3) not having any headers installed
>> Any thoughts on this pattern?
> I suspect this would be a packaging issue - packages that build modules
> should depend on whatever headers (etc.) that are necessary for building
> the module. I can't think of any distro where that isn't the norm, and
> it's not normally up to the upstream developers to check those things
> (they provide the software source, packagers provide something that
> works specifically with the distro).
Right. So this is all item (3) stuff. I agree with you there --
packages need to express the dependencies in whatever way they can.
That might mean printing nice messages if the correct dependency isn't
For (1) and (2), though, what do you think of the warning I've added
to Gentoo? That's what I meant by asking for thoughts on "this
pattern" -- the whole thing with comparing running kernel and
compiled-for-kernel and comparing loaded-module-version and
More information about the WireGuard