検索

返信元:

@[email protected] @[email protected] Well, #Rancher now owned by #SUSE, so that tracks! But I've ran #k3s on #CentOSStream and #AlmaLinux successfully as well. I think I've only deployed #RKE2 on SUSE variants (SLE Micro, Elemental OS, OpenSUSE Leap Transactional Server).
返信 1 · Renote 0

返信元:

For me, the coolest thing to come out of RHEL was the recognition that we needed #Fedora. It didn't start out as cool as it is now: There was Fedora Core, which Red Hat controlled, and Fedora Extras, where community could directly contribute to. This was an entirely new kind of community, we hadn't done this before. It felt... unsafe to the business. Yet this user / developer / distro community experiment worked. It took a while, but all that is left of Core is the "c" in the "fc" dist tag.
返信 1 · Renote 0
Which leads me to the last few years. Every 3 years, we make a new #RHEL major release, primarily from a subset of #Fedora content, plus a few other upstreams. From that point forward, each update to that RHEL release isn't necessarily from Fedora, it's from upstream, where Fedora's sources come from. This meant that we couldn't have the kind of community that Fedora formed for RHEL. That's why we created #CentOSStream.
返信 1 · Renote 0
Status update on the whole RHEL iperf3 saga... The patch by @[email protected] from @[email protected] has been merged into @[email protected] Stream 8! The c9s patch state is a bit different as the maintainer would rather backport than rebase. This comes after Red Hat's Product Security team rated CVE-2023-38403 as Important, the second highest rating. https://access.redhat.com/security/cve/cve-2023-38403 #redhat #rhel #centos #centosstream #community #cve #vulnerability #alma #almalinux #contribution #contribute #contributing
返信 0 · Renote 1

返信元:

I have to admit that whenever I have weird server problems on #CentOS Stream, there's always a question of whether or not it's Stream or something else and that lack of certainty usually is just enough that I often might not file an issue for Stream, but also just enough that I second guess running CentOS Stream over #AlmaLinux in cases where I don't want/need full on #RHEL. When stuff breaks on AlmaLinux, I'm less likely to question the distro (even though bugs happen everywhere).
返信 2 · Renote 0
@[email protected] Here's the thing. When using @[email protected], the main point of value creation is when you participate in the project. Whether that's filing bugs/submitting fixes to #CentOSStream or contributing/supporting SIGs like the Hyperscale and Kmods SIGs, you are taking some *ownership* of the project to help make it sustainable. This is also true in @[email protected], it's just new to community users of the Enterprise Linux ecosystem.
返信 1 · Renote 0
Let me reiterate some points from my FOSDEM22 talk: https://archive.fosdem.org/2022/schedule/event/centos_stream_stable_and_continuous/ Q: Does CentOS Stream replace Fedora? No. CentOS Stream development starts where Fedora development stops Q: Is CentOS Stream a Fedora LTS? No. During bootstrap many changes are applied to the content, which makes CentOS Stream separate distribution. Q: Is CentOS Stream like Debian Testing? No. The closest concept in Debian is probably "Debian Stable Proposed Updates" https://wiki.debian.org/StableProposedUpdates #CentOS #CentOSStream
返信 0 · Renote 0