From: Jordan Glover <Golden_Miller83@protonmail.ch>
To: John <graysky@archlinux.us>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>,
Christian Hesse <mail@eworm.de>
Subject: Re: binary module for arch?
Date: Tue, 01 Jan 2019 12:44:51 +0000 [thread overview]
Message-ID: <lPQ5GurSKCXMO-VZWTLlzPNWWOS6oi7Q35asuQZSP6MQzEHDY_XGp0p9_XGkeA3tfX_DQiZyfJqvDel5ncCbKD5doM83U6yUHbh2sv-4ibA=@protonmail.ch> (raw)
In-Reply-To: <CAO_nJAYw_zbNBsxtaKbR=kxp-+E4d2VkzUfrWtnSn26ZVkuEMw@mail.gmail.com>
On Monday, December 31, 2018 5:11 PM, John <graysky@archlinux.us> wrote:
> My recommendation is to change the wording under the command on your
> install page to something like: "Users of the distro provided kernels
> (linux and linux-lts) may download the requisite corresponding
> precompiled wireguard module. Users of custom kernels will require the
> wireguard-dkms package and corresponding kernel headers to compile the
> module."
>
This isn't strictly true as there are distro provided kernels
(linux-hardened and linux-zen) which don't have wireguard binary modules
available. Below would be more appropriate:
"Users of linux and linux-lts kernels may download the requisite
corresponding precompiled wireguard module. Users of other kernels will
require the wireguard-dkms package and corresponding kernel headers to
compile the module."
Jordan
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2019-01-01 12:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-31 0:58 binary module for arch? Jason A. Donenfeld
2018-12-31 1:48 ` Davide Depau
2018-12-31 16:11 ` John
2019-01-01 12:44 ` Jordan Glover [this message]
2019-01-01 20:54 ` Christian Hesse
2019-01-01 20:50 ` Christian Hesse
2019-01-02 0:22 ` Jason A. Donenfeld
2019-01-02 7:57 ` Christian Hesse
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='lPQ5GurSKCXMO-VZWTLlzPNWWOS6oi7Q35asuQZSP6MQzEHDY_XGp0p9_XGkeA3tfX_DQiZyfJqvDel5ncCbKD5doM83U6yUHbh2sv-4ibA=@protonmail.ch' \
--to=golden_miller83@protonmail.ch \
--cc=graysky@archlinux.us \
--cc=mail@eworm.de \
--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).