From: Joe Doss <joe@solidadmin.com>
To: wireguard@lists.zx2c4.com
Subject: Re: Wireguard not available for CentOS Stream
Date: Tue, 5 Jan 2021 12:35:27 -0600 [thread overview]
Message-ID: <0dc9aaac-d92f-fbaa-21e0-3a92c246480e@solidadmin.com> (raw)
In-Reply-To: <VE1PR08MB5837188C79F58A014916E123A0D10@VE1PR08MB5837.eurprd08.prod.outlook.com>
On 1/5/21 5:25 AM, Jonathan Aquilina wrote:
> Is Fedora a rolling release so to speak? I remember they used to call
> fedora the bleeding edge distro not really geared for production
> environments is that still accurate. I have only used it as a work
> station desktop with KDE installed.
It has a release about every 6 months [1], so I wouldn't call it a
rolling release. You can use DNF System Upgrade to move up to the next
release pretty easily with a bit of downtime.
I have used Fedora a lot in production and I find that it works great. I
don't consider it bleeding edge at all unless you run Fedora Rawhide
[2]. If you are looking for a rolling release Fedora, checkout Fedora
CoreOS [3], but that comes with some changes on how you use it since it
is a container-focused operating system.
The kernel that ships in Fedora has WireGuard included and the
wireguard-tools package is in the main repo. IMO if you want to use a
Red Hat variant of Linux with WireGuard, Fedora Server, Fedora Cloud
[4], or Fedora CoreOS are your best choices. I use Fedora Server at home
and Fedora CoreOS at work with WireGuard everyday.
Joe
[1] https://fedoraproject.org/wiki/Releases
[2] https://fedoraproject.org/wiki/Releases/Rawhide
[3] https://getfedora.org/en/coreos?stream=stable
[4] https://alt.fedoraproject.org/cloud/
--
Joe Doss
joe@solidadmin.com
next prev parent reply other threads:[~2021-01-05 18:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-03 20:17 Silvan Nagl
2021-01-03 21:31 ` Silvan Nagl
2021-01-04 1:24 ` Joe Doss
2021-01-04 12:47 ` Jason A. Donenfeld
[not found] ` <CAL0FmdWzknetT9raQcr_BhJwSWSBKPxXZocHSr2TT6bz2QihSA@mail.gmail.com>
2021-01-04 19:42 ` Joe Doss
2021-01-04 20:25 ` Bruno Wolff III
2021-01-04 21:55 ` Jeffrey Walton
2021-01-05 11:25 ` Jonathan Aquilina
2021-01-05 18:35 ` Joe Doss [this message]
2021-01-05 18:14 ` Joe Doss
[not found] ` <VE1PR08MB5837188C79F58A014916E123A0D10@53c70r.de>
2021-01-06 9:32 ` Silvan Nagl
[not found] ` <CAH8yC8n-fC8MJxR7cA+otkqRyDZwhR7wz2Ni+-YTAgiKz7CRHA@53c70r.de>
2021-01-05 13:06 ` Silvan Nagl
2021-01-05 13:56 ` Jeffrey Walton
2021-01-05 14:58 ` Toke Høiland-Jørgensen
2021-01-12 9:57 ` Christopher Ng
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=0dc9aaac-d92f-fbaa-21e0-3a92c246480e@solidadmin.com \
--to=joe@solidadmin.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).