I highly doubt this would affect Fedora. Thankfully, it’s community driven and self-goverened so Red Hat execs can’t go and tell them what to do. (Though I don’t know how many ties the Fedora council had to Red Hat)
you'd be surprised how many comps use RHEL just for the "I'm completely fucked and I need corporate level support" or "we need a data center completely off the rack" or "we wanna throw money at this problem" or "we need somebody to sue or point our finger at if we get majorly fucked" or "we need an OS that meets compliance" use cases. many comps won't just use some random community built OS to run their shit regardless of the community support. at the end of the day, many corporations with very complex requirements don't have many legitimate data center OS options available.
Just checked their website and it seems like they’re using debian sid packages. What’s the difference between using siduction and plain debian sid, besides having a preconfigured desktop?
I never used siduction, im juat aware of its existence. I think they add some stability(=reliability) on top of sid and also keep updating packages during sid’s freezes. Dont quote me on this.
As @addie mentioned they are way out of date for gaming on AMD, especially if you purchase a new GPU at some point.
I switched from Ubuntu to Fedora when I got my 6900 XT because it would have taken another 2-3 months for Ubuntu to catch up to a kernel version where I could use it.
Mint is also based on Ubuntu LTS, so it is way behind Fedora by the time another release comes out. I like it as a distro but it doesn’t meet the request.
IBM: We poured money and resources into Linux before 99% of the business world had even heard of it. We helped make it great. Why shouldn't we require a return on that investment?
PLEASE UNDERSTAND, I think IBM/RH is bone-headed as heck and are now inexcusable violators of the GPL, and other licenses.
I knew they were going to break RH and make it something abominable.
But they were there at the very beginning of the 2000s, promoting Linux heavily. (Not altruistically, of course)
This is not a violation of the GPL. They are allowed to charge for access to the source. If you provide binaries/images to a customer, you also must provide source. However, anyone who doesn’t pay isn’t entitled to it.
I haven’t seen this in person so I can only speculate, but I bet they’ll only provide the sources as a tarball or something instead of a git repo, which will make it a PITA for anyone do actually do anything useful with it. I mean, you could potentially still build a full distro from it, but you wouldn’t be able to feasibly maintain it without the ability to do a sync and merge from upstream. So this way, Red Hat achieves their goal of being able to kill any spinoff distro, whilst still remaining compliant with the GPL.
It’s not a “they will.” Red Hat customers are able to download source rpms from the repository or the site, this has been the case for a very long time. It is possible to clone / sync the repository, this is how airgapped networks can still host their own.
The concern is that Red Hat terminates your account if you redistribute the source to another party. This feels like an additional restriction placed on the source code, which if it is, would indeed violate the GPL.
Terminating a support contract, in itself, is not a GPL violation. The restrictions only affects the ability to receive future updates.
Edit: Red Hat indeed claims that no GPL violation is happening, yet they inform their customers that sharing updates leads to contract termination, which clearly breaches the GPL at least in spirit: sfconservancy.org/blog/2023/…/rhel-gpl-analysis/
Context is important. It’s possible that the software is distributed without any warning like that and that the termination of the support contract is done without citing the redistribution of previous versions as a reason. OTOH if the customers could prove that there’s widespread knowledge of the retaliatory termination that could be equivalent to a (non-written) restriction that is indeed incompatible with the GPL
The warning is in the agreement every customer (and free developer account) signs to obtain access. They also mention they could sue you, although I think it is unrealistic they would do so just for redistribution.
I don't know about that. IBM is traditionally stupid, yeah, but they wanted Red Hat for a reason. The CentOS debacle altogether was Red Hat, not IBM, and I don't think they are doing too much day to day operational mandates for stuff like this. I would not be surprised if this was just a Red Hat thing. I know it's easy to blame IBM, but I don't think it's that simple.
They were dying and they needed a cash cow to milk. The only way that was gonna work is if they didn’t kick the cow and spoil that milk like they’ve kicked every cow before it. And they can’t stop, so they’re just kicking away.
. I would not be surprised if this was just a Red Hat thing.
It’s a tough one. We blame RedHat for a lot of its half-baked internal fridge art - systemd, network manager; and even, some days, yum in an apt-4-rpm world.
But this new one is QUITE the departure. It’s not ‘red hat’ stupid but a little further on the spectrum.
Not surprised. A for-profit corporation wanting more money. Especially as we enroach further into late stage capitalism where corporations struggle to find more territory to profiteer from and squeeze more profit out of us.
The era of free services being profitable is ending rapidly, and we see this across many areas in the world.
Add comment