- Joined
- Sep 7, 2019
The Linux Thread - The Autist's OS of Choice
- Thread starter tehpope
- Start date
-
🐕 I am attempting to get the site runnning as fast as possible. If you are experiencing slow page load times, please report it.
- Joined
- Nov 21, 2020
Apparently RedHat has finally gotten tired of other companies compiling their publically provided source code and giving people the ability to run a "RHEL"like OS without paying.
CentOS switched to not be RHEL compatible a while back and now they've pulled their public RHEL repos that Oracle, Rocky, etc were all recompiling from.
I'm surprised it lasted this long.
CentOS switched to not be RHEL compatible a while back and now they've pulled their public RHEL repos that Oracle, Rocky, etc were all recompiling from.
I'm surprised it lasted this long.
- Joined
- Mar 4, 2019
Based on what they've said in their blog, this seems like a breach of the GPL. They make it clear that CentOS Stream and RHEL are sufficiently different to warrant separate source distributions, so they can't restrict the distribution of the RHEL sources to just paying customers without falling foul of section 3 of GPLv2, or section 6 of GPLv3.
- Joined
- Mar 30, 2023
Isn't RHEL under the Apache license or something? GPLv3 is VERY restrictive and most businesses would consider it a liability.
- Joined
- Mar 4, 2019
Apart from a few proprietary bits (logos/trademarks and a few bits of proprietary software), it's all derived from GPL code, so it's all under the GPL. The kernel is under V2 and almost everything else would be under v3. GPL doesn't allow arbitrary re-licensing by licensees.
- Joined
- Mar 30, 2023
Last I recall GPL 3 was a parasitic license where using any gplv3 code forced you to convert the rest of your code to gplv3, did they change that?
- Joined
- Mar 4, 2019
It's not parasitic, but meant to prevent parasitic behaviour. The entire purpose of the GPL is to stop people or commercial entities enclosing the hard work of other developers in their own products. If you want to use GPL licensed code in your software (as in you mingle or link the code in your code), you have to follow the license terms, same as any other software license.
Most of the core linux ecosystem is licensed under a version of the GPL, or under some compatible license, which means that, if you distribute a compiled version of the code, you are also required to provide access to the source. There's a specific carve-out for commercial entities that requires they make the source publicly available to anyone who asks, not just paying customers, in order to prevent exactly what Red Hat are apparently doing with RHEL right now.
- Joined
- Jul 4, 2022
More specifically, you can do whatever you want to your own copy of the code, run it, modify it or whatever.
The GPL only comes into effect when distributing code, you must provide the source code to whoever legally acquired the GPL licensed software from you. None of it implies you are giving everything away for free, you can sell your software at a price and include the source code, thus complying with the license. Charging for the cost of distribution is allowed. Redhat and friends used to sell support contracts and charge for the physical installer CDs.
Strictly speaking, there is no requirement to give the source code away to anyone who did not get the GPL software from you, after all, you never distributed the software to them, and GPL will not apply. This also implies that downstream paying customers can give it away for free if they like, since whatever transpires is between them and whoever getting their copy of the software, completely unrelated to the first party.
The GPL does not allow terms and conditions to be modified or appended, it is what makes the software protected from being locked away. This pisses off a lot of BSD or corporate evangelist types, they are recalcitrant at ignoring the reason GPL exists in the first place. You can't apply conditions that will prevent your own downstream from giving it away.
std::string
kiwifarms.net
- Joined
- May 17, 2018
Red Hat appears to be doing that though, since part of the licensing agreement to access the RHEL source prohibits you from using it to distribute a clone.
I suppose it would still be possible to use CentOS Stream going forwards to create a clone though, just pinning the versions of packages to what's currently in RHEL.
- Joined
- Mar 30, 2023
Ugh, I'm trying to configure pin unlock on kubuntu but it's a pita because the instructions are for Ubuntu and Arch linux and i think I mostly got it figured out but it for some reason refuses to work. if I want to add a module to the KDE login-unlock screen i just put it at the top of common-auth in etc/pam.d, right?
- Joined
- Apr 1, 2022
If the marketing team at IBM had any brain cells left, they'd do this for the larger community-focused REHL clones (Alma, Rocky, etc) free-of-charge, with a specific licensing agreement for them.
Negrate
kiwifarms.net
- Joined
- Apr 26, 2023
ibm are the anglos of software they had an empire but their retarded ways made them lose that empire and they manage to ruin everything they touch
- Joined
- Jul 4, 2022
IBM software is horrifyingly enterprisey. Their Clearcase version control system makes git look like it was designed by Steve Jobs for ease of use.
Pretty sure they only make money off consultation fees and training today.
Negrate
kiwifarms.net
- Joined
- Apr 26, 2023
and they manage to ruin every product they buy for example ustream what was once a streaming giant they bought and turned into some kind of corparate streaming nonesense i don't understand what their goal is they knew this move with redhat would turn everyone against them
- Joined
- Mar 30, 2023
Things they spin off to abandon sometimes become even bigger successes then them. Thinkpads are still amazing computers. Except there's no driver for my fingerprint reader except for a half assed hack that doesn't let you program in fingerprints
Negrate
kiwifarms.net
- Joined
- Apr 26, 2023
thinkpads are great i use one also just use your password ive never had a computer with a fingerprint reader and never needed one spacebar password is instinct for me
GNU Abyss
kiwifarms.net
- Joined
- May 30, 2023
I haven't done this On My Machine
, so this is guesswork. I'm gonna assume you're trying to configure PIN unlocking via libpam-pwdfile that lets you use a simpler PIN instead of the original user password just for the system's login screen. Is what you're doing similar to the instructions in this Arch Forums thread?Distro choice doesn't matter, what makes one major desktop environment different from another is its choice of Display Manager. Arch Linux and Ubuntu instructions probably assume a different DE, so it has a different DM. KDE's is SDDM. I've found these instructions for unlocking via fingerprint for it, which should help, config location is /etc/pam.d/sddm.
In case you want to confirm which DM your system is using, run ps aux | grep sddm. If it returns only your grep process, try other default ones like lightdm, gdm, etc. and look up instructions to those instead.
std::string
kiwifarms.net
- Joined
- May 17, 2018
Considering this is what they're actively trying to kill off, I don't think they would be interested.
Anyway after talking to the Alma devs last night it looks like pulling sources from CentOS Stream and patching them to RHEL equivalents through looking at git commits would be possible but not really feasible since it requires manual intervention for every single package.
- Joined
- Jan 5, 2015
What would be the best case scenario out of this whole situation? Would everyone involved in RHEL clones go rogue and switch over to Debian or SUSE? Could Debian restructure to appeal to the RHEL workflow, or would that not be feasible/redundant to scope?
- Joined
- Mar 30, 2023
Thank you, I figured that the problem Iwwas having was that I didn't know which file was the correct one for my display manager login. I didn't think that the sddm file would be it. I'll try that tonight.I haven't done this On My Machine
Distro choice doesn't matter, what makes one major desktop environment different from another is its choice of Display Manager. Arch Linux and Ubuntu instructions probably assume a different DE, so it has a different DM. KDE's is SDDM. I've found these instructions for unlocking via fingerprint for it, which should help, config location is /etc/pam.d/sddm.
In case you want to confirm which DM your system is using, run ps aux | grep sddm. If it returns only your grep process, try other default ones like lightdm, gdm, etc. and look up instructions to those instead.