I wonder how IBM / RedHat might react to that, were it to happen.
SUSE is forking RHEL
41–50 of 307 posts
Re: SUSE is forking RHEL
#42I'm continually baffled that so many companies follow RHEL compatibility to this day. I've been using Linux for nearly 30 years. Admining as a profession for at least a quarter of that. 20 years ago, it made a ton of sense. Today, less so. The 'stable version but we backport patches' mantra doesn't make any sense today. I can't even describe how many things that have broken that you can't even find an answer for beca…
The time (some years back now, it was a 5.10 patch and a 5.8 rpm) they mis-backported a perl patch to work around a bug in a deprecated CPAN module for one of their enterprise customers and in the process caused a 2x-30x slowdown of lots of other newer code (including the library that had replaced it in the majority of production environments by that point) was 'fun'. Took me a couple years to get together a coalitio…
Re: SUSE is forking RHEL
#431. If SUSE wants to preserve choice, it should offer a systemd-free distribution. 2. Agree with silisili's bafflement at how corporations are sticking to RHEL.
Re: SUSE is forking RHEL
#44I wonder how this will affect openSUSE, will they announce a new product based on this RHEL fork from SUSE?
Re: SUSE is forking RHEL
#45I'm continually baffled that so many companies follow RHEL compatibility to this day. I've been using Linux for nearly 30 years. Admining as a profession for at least a quarter of that. 20 years ago, it made a ton of sense. Today, less so. The 'stable version but we backport patches' mantra doesn't make any sense today. I can't even describe how many things that have broken that you can't even find an answer for beca…
Re: SUSE is forking RHEL
#46Earlier quoted context omitted.
Well, nobody's stopping IBM from retaliating by offering a SUSE clone :)
Funny but how does that help the community or businesses adopt Linux really?
Re: SUSE is forking RHEL
#47I'm continually baffled that so many companies follow RHEL compatibility to this day. I've been using Linux for nearly 30 years. Admining as a profession for at least a quarter of that. 20 years ago, it made a ton of sense. Today, less so. The 'stable version but we backport patches' mantra doesn't make any sense today. I can't even describe how many things that have broken that you can't even find an answer for beca…
When you're a part of an international research infrastructure which works on the same stack for a decade and half, being supported by RH for free (because of CERN) and creating tons of software at every layer of this research stack over that time period is one of the bigger reasons, but it's not the only one.
I personally use Debian for my personal computers and small servers elsewhere for 15+ years, but when it comes to infrastructure homogenization amongst high thousands of nodes, it's a different story.
Re: SUSE is forking RHEL
#48I wonder how this will affect openSUSE, will they announce a new product based on this RHEL fork from SUSE?
As a long term Leap and Tumbleweed user, I trust the openSUSE community to keep producing a nice distro.
Re: SUSE is forking RHEL
#49Could Alma, Rocky, SUSE and Oracle team up, coordinate with each other, pool their resources? (The announcement mentions Rocky and SUSE working together, but not Alma or Oracle.) I wonder how IBM / RedHat might react to that, were it to happen.
Re: SUSE is forking RHEL
#50I'm continually baffled that so many companies follow RHEL compatibility to this day. I've been using Linux for nearly 30 years. Admining as a profession for at least a quarter of that. 20 years ago, it made a ton of sense. Today, less so. The 'stable version but we backport patches' mantra doesn't make any sense today. I can't even describe how many things that have broken that you can't even find an answer for beca…
Some software vendors - e.g. major engineering applications - only support their products on RHEL.
If you open a support ticket and say "Hi I'm using Debian/Arch/Nix" they will just laugh and close the ticket.