From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Jonathon Fernyhough <jonathon.fernyhough@york.ac.uk>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Advising in packages to load new module or reboot
Date: Wed, 9 Aug 2017 01:30:50 +0200 [thread overview]
Message-ID: <CAHmME9q50iu1h+Wxi1CGji0MbD2dYtiCyGhPT3cvihsC0MsJNw@mail.gmail.com> (raw)
In-Reply-To: <daea6ec7-4f6e-b23d-6ae7-3cc5ae49e90c@york.ac.uk>
On Wed, Aug 9, 2017 at 1:27 AM, Jonathon Fernyhough
<jonathon.fernyhough@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
obvious.
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
compiled-module-version.
next prev parent reply other threads:[~2017-08-08 23:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-08 23:16 Jason A. Donenfeld
2017-08-08 23:27 ` Jonathon Fernyhough
2017-08-08 23:30 ` Jason A. Donenfeld [this message]
2017-08-08 23:37 ` Bzzzz
2017-08-08 23:46 ` Jonathon Fernyhough
2017-08-09 11:16 ` Egbert Verhage
2017-08-09 17:05 ` Daniel Kahn Gillmor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAHmME9q50iu1h+Wxi1CGji0MbD2dYtiCyGhPT3cvihsC0MsJNw@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=jonathon.fernyhough@york.ac.uk \
--cc=wireguard@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).