From: Christopher Bachner <hello@chrisbox.org>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: RHEL8 package install or build fail
Date: Fri, 28 Jun 2019 14:05:55 +0200 [thread overview]
Message-ID: <CAKJniYQ-YcFrYm8hz2Q8aWaJf2jLTsa_g2VGy_UaqfEx2yBUtQ@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9qi6eb+YCKx8NdtN85ouTszDBrCsrshT1sYFTUXw8K_zQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 660 bytes --]
Hi Jason,
You can get free developer access to RHEL.
https://developers.redhat.com/blog/2018/01/19/command-line-heros-podcast/
Greetings,
Christopher
On Fri, 28 Jun 2019 at 14:03 Jason A. Donenfeld <Jason@zx2c4.com> wrote:
> Hi Mike,
>
> While RHEL8 is out, it looks like CentOS 8 is not yet, so I don't have
> much of a way to make sure our compat layer works well for RHEL8. Do
> you have any suggestions on how I could obtain access to a running
> RHEL8 box and its kernel sources?
>
> Jason
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
>
[-- Attachment #1.2: Type: text/html, Size: 1441 bytes --]
[-- Attachment #2: Type: text/plain, Size: 148 bytes --]
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2019-07-17 20:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-26 13:18 RHEL8 package install or build fail Michael
2019-06-28 12:03 ` Jason A. Donenfeld
2019-06-28 12:05 ` Christopher Bachner [this message]
2019-06-28 12:07 ` Jason A. Donenfeld
2019-06-28 12:32 ` Jason A. Donenfeld
2019-06-28 14:41 ` Michael
2019-06-28 14:52 ` Jason A. Donenfeld
2019-07-02 19:51 ` Joe Doss
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=CAKJniYQ-YcFrYm8hz2Q8aWaJf2jLTsa_g2VGy_UaqfEx2yBUtQ@mail.gmail.com \
--to=hello@chrisbox.org \
--cc=Jason@zx2c4.com \
--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).