Also, folks are realizing that Red Hat's subscription agreement allows it to terminate the subscription (and access to future source code) if someone redistributes code (including GPL'ed code) in a way that Red Hat doesn't like.
People who misunderstand the GPL are accusing Red Hat of violating it by not widely distributing RHEL source to everyone.
People who sort-of understand the GPL (or willfully misrepresent it) are accusing Red Hat of violating the GPL by "restricting" the ability to redistribute sources. IMO it is not, because customers have all their rights to the code they receive under the subscription prior to termination - they simply are blocked from later releases.
Red Hat has basically acknowledged that it "sees no value" in a free RHEL clone, and is under no obligation to make it easy for clones to exist - so it's not going to anymore. It prefers you use Stream or pay for RHEL or do something else.
I've been writing about this a lot on my blog, starting here: https://dissociatedpress.net/2023/06/24/red-hat-and-the-clon...
(Disclaimer: I'm a former employee of Red Hat, so I am potentially biased one way or another.)
The situation is actually (c) - IBM RedHat is distributing the patches (and sources) as required by the GPL, but only to people who pay for their license. Re-distributing said patches or sources automatically invalidates your license, so if you exercise your GPL rights to re-distribute the GPL code you bought from IBM, you immediately lose both your support contract with them and any access to any future patches.
This has meant that many companies and projects who were historically using CentOS for free have found that they either have to pay IBM to move to RHEL, or to switch to another distro. Projects like Rocky and Alma which were trying to replace CentOS are now on rather shaky grounds (though they are trying to find additional ways of surviving).
> the patches themselves should be released downstream as part of the GPL.
The GPL only says you must provide the source to your customers. Not to anyone else. It does not compel you to offer them the world, gratis, no, not if you don't want.
From what I've read, what's actually making people grumpy is that signing in to download the sources, and later giving these sources to anyone else, could risk losing your RHEL account.
If I download everything and advertise a rebuild based on those sources? I'd expect that my subscription will be going away soon. There's probably a line somewhere in between where Red Hat would take notice and care.
But I would wager a good bottle of Scotch[1] that line is much closer to "everything" than a maintainer grabbing Red Hat's changes to their work via a sign-in to the no-cost account and incorporating those changes or something like that.
[1] Say, Auchentoshan Three Wood or something good but not like 30-year-old Speyside. I'm not made of money...
Because if they distribute a copy to an individual, RHEL account access banned or not, distribution of binaries puts them on the hook for providing sources. Unless there's no way to buy a single copy as a random stranger, this all seems incredibly impractical to enforce.
In any case: Red Hat giving you a copy of RHEL only entitles you to source for that version and not future (or past) versions.
So if you somehow receive RHEL 8.5.1 from Red Hat on media independent of a subscription, you have the right to receive the sources for GPL'ed software present in that release.
Not RHEL 8.5, not RHEL 8.5.2, etc. And, technically, you only have the right to source to GPL'ed software, so they don't have to give you source for Apache HTTPD or other permissively licensed software in RHEL.
An interesting wrinkle that I haven't seen addressed yet is whether Red Hat has to find a way to convey source to you after the subscription if you had access to download source during the subscription but didn't exercise it. It was there, you just didn't take it. If you want it later, do they have to ship you a DVD or something? I have no idea.
Ultimately, the issue is RedHat thinks people should be using centOS stream if they don't need enterprise support and a significant part of the community just want RHEL but free.
> What's now changed is that these patches are either (a) not distributed as required by the GPL, or (b) the patches are distributed, but in a way that is intentionally less useful, e.g. by having to get them via the Red Hat portal.
My understanding is a bit different:
Red Hat submits patches upstream and also back-ports those patches into existing RHEL releases that have long-term support.
The upstream patches are still as open as ever, nothing has changed.
The back-ports into existing RHEL releases are what Red Hat is trying to make harder for people to consume outside of a Red Hat subscription (the free developer subscription and the paid support contracts).
I'm not making a judgement either way in this comment, just trying to help clarify my understanding.
That’s an interesting detail. Thanks!
[1]Has Rakuten made a Rocky-er road for Red Hat?
https://www.mobileeurope.co.uk/has-rakuten-made-a-rocky-er-r...
I've always been a user of the Debian and Arch worlds. The RHEL/Fedora/etc world has been this "other" part of Linux that I frankly haven't touched much, and haven't yet found a reason to.
One thing I'm not totally clear on is what specifically Red Hat offers that people pay for, i.e. what are the details of the "+ stability + patches" of what GP mentioned. Are there paid applications as well? Is paid support a large part of the business model? And so on and so on. I'm still just a little mystified by the RHEL business model, and every time I hear someone talk about it, it's literally vague one-word answers such as "stability," "patches," "support," "enterprise stuff," etc. Even the RHEL FAQ offers essentially just that.
I'm still not quite informed enough to be able to confidently lean one way or the other, but I have to say that I can't shake the feeling that RHEL's business model ultimately relies on exploiting their customers' desire to change their systems as little as possible, even if it means the customers eschew more modern systems that make obsolete the need for the kind of products and services RHEL provides. Or to put it another way, RHEL enables their customers to live with "the devil they know," and not adopt more modern best practices. Which isn't necessarily a bad thing, I get it, but also if that is indeed the case, it seems like a rickety foundation upon the already rickety foundation of trying to sell open source software that easily be unseated by, say, the nix model of doing things.
I don't know, I could be dead wrong, but starting from what I've seen most other tech companies do and mixing it with a dash of "the idea of paying for Linux seems insane to me"...in lieu of better information, I can't dismiss the above out of hand.
Very, very generally, updates tend to play better with or expect that the software it's working with is also updated; and so, while yes it can be stable to stick with a particular version for 10+ years, the value of that stability drops as time goes on, as the software/OS in question has more and more trouble operating in the context of/with other/newer software, and so 5+ years into that 10+ year timespan, that stability you're supposedly paying for doesn't feel very stable at all -- and that doesn't even begin to touch what happens once those 10+ years run out and you need to get with the times.
Which is all to say: this is why rolling releases exist. Better to get used to surfing the wave all the time, rather than sitting on the beach for years and then having to swim an Olympic race after you're out of shape. I'm mixing metaphors here but you get the idea.
What's more, obviously riding the wave can be a little tiring, and thus more and more best practices are borne out of that problem -- which is why I mentioned nix in my last comment. I'm not even a nix user, have never done more than read about it, lest one think that I'm yet another nix zealot on HN, but I do think that it or something like it is a very very good solution to the pains that can be had by constantly staying up to date. I for one will always be more interested in that kind of route, rather than agreeing to the golden handcuffs of long-term support. While not in a RHEL-like setting, I've been bitten by the "I just want this old thing to keep going and never change" problem too many times before.
Like, I was listening to the most recent episode of Linux Unplugged, and they had a member of the RHEL team on, and when asked about the value proposition of RHEL, he said something to the effect of that it's not just the software, but being able to offer the specific versions with the specific patches in particular combinations of other software with whatever patches. And I couldn't help but think -- isn't he basically just describing nix? Nix's whole thing is to super easily enable declaring specific versions of software in specific combinations, and to be able to recall it with a config file -- Matthew Croughan's talk at SCALE this year was essentially...that, and doing it super easily. And perhaps if we aren't keeping so much old software alive, it wouldn't all need so many patches to allow all the various combinations required.
I don't know. It all seems like a very heavy-handed, people-y solution to a problem that we've mostly solved, and perhaps even eliminated the conditions for to exist in the first place.
Anyways, this is all mostly hypothetical pontification, and I'm sure that those who actually work with RHEL on a daily basis could poke tons of holes in my point of view. Would love that actually, as like I said I feel very much like an outsider looking in. But it just seems like a goal that is fundamentally flawed.
For those enterprises, the value of the stability RHEL provides goes UP as time goes on, because the longer you wait, the more risky and costly it is to migrate to the new version/solution/etc.
My understanding is that Red Hat Enterprise Linux can be thought of as Fedora + stability + patches, and that the patches themselves should be released downstream as part of the GPL.
What's now changed is that these patches are either (a) not distributed as required by the GPL, or (b) the patches are distributed, but in a way that is intentionally less useful, e.g. by having to get them via the Red Hat portal. This has made it more difficult for "repackagers" like CentOS, Rocky and Alma to keep their disros up to date.
Assuming I have the above correct (and I may not), my suspicion is that Red Hat is looking at cloud providers who also have been repackaging, for example, Amazon Web Services' Amazon Linux has historically been RHEL repackaged and bundled with some aws tools. I'm not aware of AWS distributing their changes either. From this perspective, it looks like the AWS benefits from the stability + patches without paying RedHat for their development. (I'm also not aware of whether aws distributes the Amazon Linux sources and if so those are done in a way that is useful for the community... I'll do some further research on my own. edit: It looks like the Amazon Linux sources are here: https://github.com/amazonlinux/linux)