June 30th, 2024, will bring the End of Life (EOL) of CentOS Linux (2023)
201–210 of 228 posts
Re: June 30th, 2024, will bring the End of Life (EOL) of CentOS Linux (2023)
#202Earlier quoted context omitted.
Prior to CentOS Stream, couldn't you file the bug in the upstream project's bug tracker instead, and then still do all of the other stuff you said?
You'd still have to wait for someone at Red Hat to backport the fix themselves. There wasn't really a way to actually participate in the engineering of CentOS itself.
Re: June 30th, 2024, will bring the End of Life (EOL) of CentOS Linux (2023)
#203Earlier quoted context omitted.
I am always baffled by people using ubuntu because "free". I get the desire if you want the paid stream. EG, an alternative to Redhat or SuSE as a paid stream. But if you're going to use Ubuntu, why put up with the snaps, the commercialism, the app store, when you can just use debian? Every time I hear a reason why, it makes little sense to me. Even though 95% of Ubuntu is Debian, and Ubuntu wouldn't exist without De…
If I'm not running a desktop, why would I consider running Ubuntu at all? I feel the same about people offering a kneejerk suggestion of Ubuntu as when I'm told to use Docker without actually knowing anything about my needs. Just because I'm wanting to use Linux does not mean I need Ubuntu. Just because I'm deploying code doesn't mean Docker is the solution. But 99% of the time I talk to people, it's all Docker this…
For polygot/hybrid cases where you have a smattering of different languages and supporting technologies/services, docker makes a lot of sense.
If you're all in (for example) on nodejs with a monorepo, it probably doesn't - you're just an "npm install" away from deployment.
Whenever I really dig into the docker passion, I usually find devs who are frustrated by having to manage a million little details to get the dev environment going.
If the language/stack takes that pain away, docker loses most of its value.
Re: June 30th, 2024, will bring the End of Life (EOL) of CentOS Linux (2023)
#204Earlier quoted context omitted.
You'd still have to wait for someone at Red Hat to backport the fix themselves. There wasn't really a way to actually participate in the engineering of CentOS itself.
Won't you still have to wait for someone at Red Hat to move the change from Stream into RHEL?
With CentOS you would have the same problem, except that there's no way to make the engineering part happen any faster than Red Hat's staffing and priorities allowed.
Re: June 30th, 2024, will bring the End of Life (EOL) of CentOS Linux (2023)
#205Earlier quoted context omitted.
> Additionally, Red Hat support is so bad these days. It almost reminds me of Microsoft Technet forums of the past. Random 'techs' offering copy-paste solutions and the same bad information. Yeah, that's been my experience. We had a bad driver package from them completely hose one of our prod systems. It took 3 days and multiple calls from our CTO to get anyone to seriously look at the issue despite being on the top…
The SLA is to respond within X hours, not resolve. So when the SE sends an email that says: "I'm the owner of the case and will reach out after looking at the notes." They have complied with the SLA.
Re: June 30th, 2024, will bring the End of Life (EOL) of CentOS Linux (2023)
#206Earlier quoted context omitted.
My understanding is that since Red Hat restricted the source availability for RHEL, Rocky is using the following loopholes to gain binary compatibility with RHEL: 1. Using OCI images of RHEL (i.e. on Docker Hub) 2. Using cloud server images of RHEL They outlined their plans for this in June of 2023[0]. Red Hat’s official stance is that downstream distros like Rocky or AlmaLinux should be basing off of CentOS Stream —…
IBM's official route results in a distro that is not bug-for-bug compatible with RHEL, at least not without a lot of unnecessary work. The route Rocky is taking results in a distro that is bug-for-bug compatible.
Point taken.
From my perspective, it seems like a short-sighted approach to rely on loopholes to obtain bug-for-bug compatibility. I know I wouldn't be comfortable running anything production-grade on Rocky Linux with their current approach.
Re: June 30th, 2024, will bring the End of Life (EOL) of CentOS Linux (2023)
#207Earlier quoted context omitted.
My understanding is that since Red Hat restricted the source availability for RHEL, Rocky is using the following loopholes to gain binary compatibility with RHEL: 1. Using OCI images of RHEL (i.e. on Docker Hub) 2. Using cloud server images of RHEL They outlined their plans for this in June of 2023[0]. Red Hat’s official stance is that downstream distros like Rocky or AlmaLinux should be basing off of CentOS Stream —…
So what? Doesn't matter how convoluted the "loophole" is. There will always be a loophole because Red Hat must leave one open, because this is open-source software and it's impossible for them to truly close all avenues to using your RIGHTS under the license. We should he celebrating people working around DRM, not being fearful of it.
(I'd be happy if the Rocky Linux folks prove me wrong -- the more variety there is with Linux, the better!)
Re: June 30th, 2024, will bring the End of Life (EOL) of CentOS Linux (2023)
#208Earlier quoted context omitted.
I'm not claiming that either, so what's your point. I'm just saying that the way Rocky presents it is mostly marketing. The cleverness is to save themselves effort, not to do something they weren't being allowed to do previously.
I'm not sure why you weighed in on the subject then, other than to advance your own personal preference. At least, I mistook it as an objection to Rocky Linux's very existence. As long as what they're doing is legal, then let them be. Each distribution will rise and fall based on the value it provides.