Earlier quoted context omitted.
OpenSUSE Leap is just that, it uses binaries directly from SLES https://www.zdnet.com/article/suse-bridges-the-gap-between-o...
It's not just binary compatible - it uses the SLES binaries directly
SUSE is forking RHEL
161–170 of 307 posts
Re: SUSE is forking RHEL
#162Earlier quoted context omitted.
Oracle and almalinux would probably base on Stream with their own patches. The maintenance burden will be much smaller than a full fork, as red hat will still be the main contributor.
But if you base on Stream, you are no longer bug-for-bug compatible with the current stable release of RHEL. Not that I care personally, but this point seems to be very important for a lot of people.
Oracles and Almalinuxes announcements both state clearly that they aim to be compatible so long its possible, so no 1:1 binary compatibility promises.
Re: SUSE is forking RHEL
#163Wow, that's pretty rich from a company that has made good money from vendor lock-in. I'm still bitter when they drastically increased our SLES-prices for academic institutions, that was probably around 2010/11, and I've never touched SUSE since. That they now fork RHEL is pretty funny, since I vividly remember talking to a SUSE sales rep at that time, and I said we would now switch away from SLES to Scientific Linux, and he called it a "parasite project". Of course, you are allowed to make money off FLOSS software, but please, get off your high horse when others do the same.
Re: SUSE is forking RHEL
#164Earlier quoted context omitted.
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…
> 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'. That ONE time might have been fun, but with Arc…
Re: SUSE is forking RHEL
#165Re: SUSE is forking RHEL
#166Re: SUSE is forking RHEL
#167Did SUSE coordinate this announcement With Oracle? Because they also announced similar thing yesterday https://www.oracle.com/news/announcement/blog/keep-linux-ope...
Oracle talking about "open and free". Didn't think I would live to see that happening...
Whatever benefits their bottom line.
Re: SUSE is forking RHEL
#168Earlier quoted context omitted.
The US market is primarily RHEL. Historically the EU market and SAP shops were SLES. I admit I’m far enough removed today that I’m not sure if that still holds true.
My feeling is that most engineers outside of Germany prefer RHEL to SLES.
Re: SUSE is forking RHEL
#169I'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…
> I can't figure out why RHEL compat is so desirable. Hey, here’s a comprehensive guide complete with commands, expected outcomes, and side effects of each command for setting up a Windows Domain using an RHEL domain controller: https://access.redhat.com/documentation/en-us/red_hat_single... Oh, that’s for 7.5? One that’s 15 years old and no longer under standard support? It still works! Wait, but you’re a new custom…
I really like Nix so far (just started using it), but damn is the documentation ever shit tier.
Re: SUSE is forking RHEL
#170Earlier quoted context omitted.
> mostly independent from IBM (who didn't participate in this decision). Right, they only pressured them to make more money, didn't tell them how exactly.
Even if that was the intended meaning, it's quite an extrapolation that Red Hat is "growing hostile towards open source as a whole", especially since people say that of Red Hat roughly every two years.
This is being hostile towards open source. And as someone else pointed out, the reason we're mad at Red Hat is because they were built because of the open source community, but now they've shown that since their acquisition by IBM, their goals have profoundly changed - they are now seeking to be more profitable, if it's by IBM's orders or not, we can only speculate, but there is a correlation here and it's not just a coincidence.