11–20 of 555 posts
I am really interested to know why should anyone go with this when Debian or Ubuntu LTS exist. The two later have not changed their policies in the last decade, and they have a clear path for upgrading. CentOS was always a clear choice for device drivers support, but I never understood the stability claims.
What is the vision for Rocky Linux? A solid, stable, and transparent alternative for production environments, developed by the community for the community. Hence the name Rocky Linux, I suppose? Solid as a rock. Although I'll be inclined to think of it as series of movies. Perhaps even split wood before installing Rocky 5?
Edit: actually Rocky was the flying squirrel.
- The old CentOS had a brand value, which Rocky Linux has to earn back all over again.
- The old Red Hat was nice to CentOS or at least wasn't particularly hostile. That does not mean IBM will be nice too.
- It may be too short a notice for current CentOS users to wait for Rocky Linux to come through. They may already move away to other alternatives like Debian or Ubuntu or Amazon Linux or whatever fits their use case.
- If because of some miracle, Rocky Linux turns out to be just as successful as CentOS, there is a chance that either Red Hat or a competitor will end up taking control of it too. Corporate sponsorship is too lucrative to decline. So, it will end up with the same fate as CentOS.
I am really interested to know why should anyone go with this when Debian or Ubuntu LTS exist. The two later have not changed their policies in the last decade, and they have a clear path for upgrading. CentOS was always a clear choice for device drivers support, but I never understood the stability claims.
What is the vision for Rocky Linux? A solid, stable, and transparent alternative for production environments, developed by the community for the community. Hence the name Rocky Linux, I suppose? Solid as a rock. Although I'll be inclined to think of it as series of movies. Perhaps even split wood before installing Rocky 5?
"Thinking back to early CentOS days... My cofounder was Rocky McGaugh. He is no longer with us, so as a H/T to him, who never got to see the success that CentOS came to be, I introduce to you...Rocky Linux" — Gregory Kurtzer, Founder
I am really interested to know why should anyone go with this when Debian or Ubuntu LTS exist. The two later have not changed their policies in the last decade, and they have a clear path for upgrading. CentOS was always a clear choice for device drivers support, but I never understood the stability claims.
I am really interested to know why should anyone go with this when Debian or Ubuntu LTS exist. The two later have not changed their policies in the last decade, and they have a clear path for upgrading. CentOS was always a clear choice for device drivers support, but I never understood the stability claims.
Debian offers around three years of support. Ubuntu LTS around five. Both pale in comparison with Red Hat and, by proxy, CentOS.
CentOS 8 was released few days ago with kernel 4.18, which not even LTS is, and is older than the current Debian stable kernel(!).
If you need to install anything besides the base distro you need elrepo, epel, etc which I'm not sure can be counted as part of the support.
I am really interested to know why should anyone go with this when Debian or Ubuntu LTS exist. The two later have not changed their policies in the last decade, and they have a clear path for upgrading. CentOS was always a clear choice for device drivers support, but I never understood the stability claims.
Centos was the rational other free choice, not that Red Hat hasn't made other equally strange decisions.
Sometimes I think we'd be better off rolling our own, like Amazon does.
I am really interested to know why should anyone go with this when Debian or Ubuntu LTS exist. The two later have not changed their policies in the last decade, and they have a clear path for upgrading. CentOS was always a clear choice for device drivers support, but I never understood the stability claims.
Debian's package policies can be challenging for rapidly updating packages: https://lwn.net/Articles/835599/