検索
"Rocky Linux from CIQ meets the needs of organizations who want to run community Rocky Linux within their IT infrastructure but need contractual guarantees and mitigation to liabilities that the open source community cannot provide."
So, Rocky Linux is going full Oracle Enterprise Linux. I'm not entirely surprised, but I am disappointed.
I suggest AlmaLinux, RHEL, CentOS, or SLES instead. Any one of those.
https://www.theregister.com/2024/10/09/rocky_linux_from_ciq/
#Linux #RockyLinux #RHEL
You read that right folks, EPEL 10 things are happening. Will be talking about this more at Flock next week.
#EPEL #Fedora #CentOS #RHEL #FlockToFedora
https://fosstodon.org/@adamw/112883887150801180
The Case Against Rocky Linux
https://hackernoon.com/the-case-against-rocky-linux
#RockyLinux #RedHat #RedHatEnterpriseLinux #AlmaLinux #RHEL
🤷
🤷
Attention #AlmaLinux users!! Other #CentOS, #RHEL, etc. users might want to tune into this one as well.
https://jonathanspw.com/posts/2024-03-31-dealing-with-cve-2024-1086/
#Linux #InfoSec
While everyone has been talking about #xz's backdoor I've been working on a patch for an AlmaLinux kernel vulnerability (CVE-2024-1086) that #rhel has yet to release a fix for (though #centos stream is patched). It's quite a nasty privilege escalation vulnerability so I suggest updating ASAP.
https://jonathanspw.com/posts/2024-03-31-dealing-with-cve-2024-1086/
Full production kernel builds provided within, as well as live kpatches (with no warranty/guarantee of course).
Kernel updates expected to hit #AlmaLinux repositories on Monday.
@[email protected] will be hosting an event at SCaLE called CentOS Classroom - a neat opportunity to learn more about the project from contributors. Happening Mar 14 from 2-5pm local time!
At the end there will be a packaging workshop for Fedora EPEL! Check it out if you've wanted to get into packaging but weren't sure how. @[email protected]'s got your back. 👍
Learn more: https://blog.centos.org/2024/03/centos-at-scale/
#CentOS #EPEL #FedoraEPEL #EnterpriseLinux #AlmaLinux #RockyLinux #RHEL
As much flack as I've given #RedHat over #RHEL source shenanigans, they've kept #Ansible AWX #opensource and available to the public, very much to their credit. Tower was proprietary when they bought it and they opened it and kept it open.
返信元:
@[email protected] I've actually found interesting how much more active the matrix side is than the IRC side. I suppose it all depends on channels/rooms/communities.
@[email protected] That's fair. Channels like #RHEL are far more IRC weighted.
返信元:
How did I get on the #Canonical #Ubuntu marketing email list?
@[email protected] somebody with a sense of humour?
If you get #rhel ads too, it wasn't me :-)
返信元:
We're about 2 years into discovering what kind of community can exist here and what conditions are necessary to make it worth everybody's while. Fedora has an 18 year head start. We're making mistakes, like in the same sense that "Core" was a mistake. In life we all try things, and often they don't work the way we think they will. If we're lucky, we learn, we try again, and we do better.
So far, we've replumbed how #RHEL development works, created a public upstream from which all RHEL minor releases are derived, and invited people to join in and contribute. I think many of us were hoping it would be open in ways analogous to Fedora. In practice, we're discovering where we aren't able to get rid of Core, as it were... at least not yet, and that's meant contributions have been hard. e're trying here, and I appreciate it must be hard to work with us as we lumber clumsily forward.
返信元:
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.
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.
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