From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: noloader@gmail.com, Silvan Nagl <mail@53c70r.de>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Wireguard not available for CentOS Stream
Date: Tue, 05 Jan 2021 15:58:30 +0100 [thread overview]
Message-ID: <87sg7fa0rt.fsf@toke.dk> (raw)
In-Reply-To: <CAH8yC8kwtW5qMM=vZxLe1VTKwtqy76u4SP8Vtib_nhpdpBWJag@mail.gmail.com>
Jeffrey Walton <noloader@gmail.com> writes:
> On Tue, Jan 5, 2021 at 8:06 AM Silvan Nagl <mail@53c70r.de> wrote:
>>
>> Thank you for this information.
>> Since Stream is more or less like a very old Fedora version now I am
>> convinced using Fedora Server wont be that bad at all.
>>
>> Gonna test it soon.
>
> Yeah, I think you'll like it.
>
> I got tired of dicking around with all the breaks and workarounds
> caused by Red Hat and CentOS antique software. I also did not feel
> comfortable with abandoned kernels.
>
> I don't understand how Red Hat or CentOS can provide a 2.6 or 3.10
> kernel in good conscience. Even the kernel folks tell you to use a
> modern kernel, because those old kernels get no attention. The new
> kernels get the bug fixes and security updates (and include the bug
> fixes of the old kernels).
The version number for RHEL kernels is completely fictional. IIRC we
backport 1/3 of all patches in each new kernel release, but keep the
version number fixed and do an insane amount of engineering to keep the
internal kernel ABI stable in spite of the backports.
We can argue about whether this is a reasonable thing to do in the first
place (and I'm not sure I'll actually argue that it is), but it's wrong
to think of RHEL kernels as "ancient with no security updates"... :)
-Toke
next prev parent reply other threads:[~2021-01-05 14:58 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
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 [this message]
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=87sg7fa0rt.fsf@toke.dk \
--to=toke@toke.dk \
--cc=mail@53c70r.de \
--cc=noloader@gmail.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).