From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: Baptiste Jonglez <baptiste@bitsofnetworks.org>,
"Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Installation instructions for Debian
Date: Sun, 14 May 2017 08:52:12 -0400 [thread overview]
Message-ID: <87wp9jfvnn.fsf@fifthhorseman.net> (raw)
In-Reply-To: <20170514084456.GA7227@tuxmachine.polynome.dn42>
[-- Attachment #1: Type: text/plain, Size: 878 bytes --]
On Sun 2017-05-14 10:44:56 +0200, Baptiste Jonglez wrote:
> Note that the previous installation instructions (basically, just "sudo
> apt install wireguard-tools wireguard-dkms") were valid for Debian sid.
>
> The new installation instructions are only valid for Debian jessie and
> Debian stretch (admittedly, probably the largest fraction of Debian
> users). But I still think you should reflect this in the instructions.
>
> Debian wheezy is not supported (with its old 3.2 kernel), although it
> could be possible to use wireguard with the wheezy-backports kernel
> (3.16). I don't think it's worth mentioning it anyway, Wheezy is
> old-stable and will soon be old-old-stable.
As the debian maintainer for wireguard, I agree with Baptiste on all
these points, and on his earlier recommendations. Thanks, Baptiste, for
the clear and concise documentation.
--dkg
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2017-05-14 12:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-13 7:05 Baptiste Jonglez
2017-05-13 22:58 ` Jason A. Donenfeld
2017-05-14 8:44 ` Baptiste Jonglez
2017-05-14 12:52 ` Daniel Kahn Gillmor [this message]
2017-07-08 14:14 ` Baptiste Jonglez
2017-07-10 0:50 ` Jason A. Donenfeld
2017-07-11 23:36 ` Daniel Kahn Gillmor
2017-07-12 0:00 ` Bzzzz
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=87wp9jfvnn.fsf@fifthhorseman.net \
--to=dkg@fifthhorseman.net \
--cc=Jason@zx2c4.com \
--cc=baptiste@bitsofnetworks.org \
--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).