Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror

Comment Re:RTFGPL (Score 1) 126

What would happen is you as an end user would loose your subscription rights to RHEL as per your contract with Red Hat, but at the same time Red Hat could loose their rights to redistribute software covered under the GPL if the upstream project enforces those rights under the GPL. Also as is explicit in the GPL, even though Red Hat could loose their right to redistribute, you as a downstream recipient of RHEL would not.

So the short answer, everybody looses in some capacity.

Comment Re:RTFGPL (Score 1) 126

I disagree that there is any difference between cancelling a current contract and refusing to renew one that is or will soon become expired. Either action, if taken as a punitive measure in retaliation for you exercising your rights under the GPL is against at least the spirit of the GPL and likely, though not tested yet in court, a violation of the GPL as well. My take is that it comes down to the reason for the cancellation or refusal to renew and this reasoning may be the difficult thing to prove in court, although statements made by Red Hat and actions that they did or did not take against others who did not redistribute the sources would go a long ways towards convincing a court.

Basically put, Red Hat has the right (under the GPL) to do business with whom they choose so long as it's not done in an attempt to do an end-run around the rights given in the GPL to downstream recipients of the software. One way to look at it is that it's perfectly legal for a restaurant to refuse service to anyone they want, so long as it isn't discrimination against race, religion, sexual orientation, etc. The moment that restaurant puts up a sign that says, "Whites Only" they are in violation of Federal law.

Comment Re:RTFGPL (Score 1) 126

This is why the statement from the FSF is so important, they actually own the copyrights to a very large portion of software that is redistributed by Red Hat, including, but not limited to:

* The bash shell.
* glibc.
* the gcc and g++ compilers.
* emacs
* Gnome ...this list just goes on and on. The FSF *has* standing to bring litigation against Red Hat for this, and as such their opinion on what Red Hat is doing is *very* relevant.

Now whether they can win in court is, as you say, not a given, but they certainly have standing to bring the lawsuit.

Also consider that if they *really* want to they can update the GPL again (GPLv4 anyone?) and start distributing their software under that, so when they say that what Red Hat is doing violates the spirit of the GPL they do have the power to bring the actual GPL into alignment with the "spirit" for which they refer. Now updating the GPL to a new version is a lot of work and certainly there would be consequences related to acceptance and adoption by the community at large so it's not a simple ask, and I really doubt they would do this just to gain leverage over Red Hat in this particular case, but they can if they really want to and it would be game over for Red Hat if they do, there is very little chance that Red Hat can release a quality product without including at least some GNU software in it.

Comment Re:RTFGPL (Score 1) 126

Generally speaking I would agree with you up until a refusal to distribute is taken as a penalizing action against someone who chooses to exercise their rights under the GPL. As soon as that happens then this changes from Red Hat choosing who they do business with to Red Hat violating the provisions of their own right to redistribute certain software under the GPL and they can loose that right if they persist.

Comment Re:RTFGPL (Score 1) 126

This is more than just what RMS had in mind when he created the GPL a long time ago. The FSF owns the copyright of a not-insignificant amount of software that is redistributed by Red Hat in their RHEL distribution. They intentionally license their software under the GPL which they themselves maintain and are fully aware of the intent of what that license is supposed to mean. When the FSF says that what Red Hat is doing goes against the spirit of the GPL that is a very strong statement from them and they do have the means to back that up with litigation if they so choose.

My takeaway from this is that they are basically saying that they are not aware of anyone having actually had their subscription revoked or refused to be renewed as a consequence of redistributing the sources provided under the GPL and other copyleft licenses from Red Hat, but if they are made aware of such a case they would be willing to at least consider taking some form of action. They are putting Red Hat on notice and without saying as much drawing a line in the sand saying, "this is how far we are willing to let you go with this, don't cross this line".

Now I may be taking some liberties and reading things into their response that I shouldn't be, but to me it is regardless a powerful statement coming from the FSF.

Submission + - Free Software Foundation Speaks up Against Red Hat Source Code Announcement

PAjamian writes: Two years ago Red Hat announced an end to its public source code availability. This caused a great deal of outcry from the Enterprise Linux community at large. Since then many have waited for a statement from the Free Software Foundation concerning their stance on the matter. Now, nearly two years later the FSF has finally responded to questions regarding their stance on the issue with the following statement:

Generally, we don't agree with what Red Hat is doing. Whether it constitutes a violation of the GPL would require legal analysis and the FSF does not give legal advice. However, as the stewards of the GNU GPL we can speak how it is intended to be applied and Red Hat's approach is certainly contrary to the spirit of the GPL. This is unfortunate, because we would expect such flagship organizations to drive the movement forward.

When asked if the FSF would be willing to intervene on behalf of the community they had this to say:

As of today, we are not aware of any issue with Red Hat's new policy that we could pursue on legal grounds. However, if you do find a violation, please follow these instructions and send a report to license-violation@gnu.org.

Following is the full text of my original email to them and their response:

Subject: Statement about recent changes in source code distribution for Red Hat Enterprise Linux
Date: 2023-07-16 00:39:51

> Hi,
>
> I'm a user of Red Hat Enterprise Linux, Rocky Linux and other Linux
> distributions in the RHEL ecosystem. I am also involved in the EL
> (Enterprise Linux) community which is being affected by the statements
> and changes in policy made by Red Hat at
> https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fwww.redhat.com%2Fen%2Fblog%2Ffurthering-evolution-centos-stream and
> https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fwww.redhat.com%2Fen%2Fblog%2Fred-hats-commitment-open-source-
> response-gitcentosorg-changes
> (note there are many many more links and posts about this issue which
> I
> believe you are likely already aware of). While a few of these
> questions are answered more directly by the license FAQ some of them
> are
> not and there are a not insignificant number of people who would very
> much appreciate a public statement from the FSF that answers these
> questions directly.
>
> Can you please comment or release a statement about the Free Software
> Foundation's position on this issue? Specifically:
>

Thank you for writing in with your questions. My apologies for the delay, but we are a small team with limited resources and can be challenging keeping up with all the emails we receive.

Generally, we don't agree with what Red Hat is doing. Whether it constitutes a violation of the GPL would require legal analysis and the FSF does not give legal advice. However, as the stewards of the GNU GPL we can speak how it is intended to be applied and Red Hat's approach is certainly contrary to the spirit of the GPL. This is unfortunate, because we would expect such flagship organizations to drive the movement forward.

> Is Red Hat's removal of sources from git.centos.org a violation of the
> GPL and various other Free Software licenses for the various programs
> distributed under RHEL?
>
> Is Red Hat's distribution of source RPMs to their customers under
> their
> subscriber agreement sufficient to satisfy the above mentioned
> licenses?
>
> Is it a violation if Red Hat terminates a subscription early because
> their customer exercised their rights under the GPL and other Free
> Software licenses to redistribute the RHEL sources or create
> derivative
> works from them?
>
> Is it a violation if Red Hat refuses to renew a subscription that has
> expired because a customer exercised their rights to redistribute or
> create derivative works?
>
> A number of the programs distributed with RHEL are copyrighted by the
> FSF, some examples being bash, emacs, GNU core utilities, gcc, gnupg
> and
> glibc. Given that the FSF has standing to act in this matter would
> the
> FSF be willing to intervene on behalf of the community in order to get
> Red Hat to correct any of the above issues?
>

As of today, we are not aware of any issue with Red Hat's new policy that we could pursue on legal grounds. However, if you do find a violation, please [follow these instructions][0] and send a report to <license-violation@gnu.org>.

[0]: https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fwww.gnu.org%2Flicenses%2Fgpl-violation.html

If you are interested in something more specific on this, the Software Freedom Conservancy [published an article about the RHEL][1] situation and hosted a [panel at their conference in 2023][2]. These cover the situation fairly thoroughly.

[1]: https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fsfconservancy.org%2Fblog%2F2023%2Fjun%2F23%2Frhel-gpl-analysis%2F
[2]: https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fsfconservancy.org%2Fblog%2F2023%2Fjul%2F19%2Frhel-panel-fossy-2023%2F

Comment This is a good thing (Score 1) 16

Alma Linux has switched to a slightly different strategy from the bug-for-bug compatibility one. Rocky Linux is staying bug-for-bug for now. This is good for Enterprise Linux as a whole and for both distros as having the two distros with different strategies adds robustness to EL as a whole.

I also tend to agree with the article and summary. The vast majority of people won't even be able to tell the difference.

Comment Re:Extrapolation is strong in this one... (Score 3, Insightful) 180

In NZ at least (and I would have assumed Australia to be the same) ATMs now dispense $20s and $50s, whereas they used to only dispense $20s, so I would assume that, combined with inflation, has made $50s much more common. In other words, the $50 note is the new $20 and should be much more common as a result.

Comment Re:GPL Loophole (Score 2) 118

That's not exactly the "loophole", what Red Hat is claiming is that if you pay to get the binaries, they will give you access to the sources as per the GPL, and you can, as per the GPL redistribute those sources, but if you do they will no longer give you access to future binaries (or sources). So they basically say you can exorcise your rights under the GPL but if you do they will cut you off.

Personally I think this is a violation of the GPL itself as they are punishing you for exorcising your GPL rights. Unfortunately as end users we don't have standing to sue, you have to be a copyright holder of one or more of the GPLed software that is included in RHEL. I think the most likely candidate for this is the Free Software Foundation, who own the copyright on all of the GNU software and utilities including bash, GNU coreutils, glibc, gcc, emacs ... the list goes on and on.

Comment Re:Lawsuit? (Score 1) 143

It may be up to a court to decide, but keep in mind that the GPL is written and maintained by the Free Software Foundation who have a vested interest in making sure that it is fully enforceable and very large portion of the software in RHEL is GNU software, so the FSF has standing to enforce against Red Hat. If a court decides that Red Hat did not violate the GPLv3 then the FSF always has the option to "fix" the GPL in a new GPLv4 version, then bump their software up to that version, so at the end of the day, if the FSF decides they don't like what Red Hat is doing they actually hold all the cards, they can make it so that Red Hat has to stop or end up crippling their product to such a degree as to make it very much unusable.

Comment GPL Issues (Score 1) 143

Red Hat is attempting to skirt the GPL by putting their subscription users under contract, basically saying that you can exorsize your rights to redistribute the source under the GPL, but if you do so they will terminate your subscription. I believe that this action of "punishing" a user violates at least the spirit, if not the letter of the GPL.

There is a lot of GNU software in RHEL (e.g. bash, GNU coreutils, gnupg, gcc, emacs ... the list goes on and on). If the Free Software Foundation were to lay down the law to Red Hat then it is almost certain that Red Hat would be in a bad place over this. Basically put Red Hat would loose their license to redistribute all of the GNU software which would effectively cripple their products. I understand that the FSF is already looking into it and if they determine that the GPLv3 doesn't currently block this kind of activity I would expect to see work start on a GPLv4 that does.

Red Hat likes to throw around the term "freeloaders" when referencing the clone distros, but they forget that nearly all of the software that goes into RHEL is software that they got for free from upstream projects. Red Hat is freeloading as much as any of the downstream clone distros are.

Comment Re:Usual question (Score 1) 206

Tracking by the retail store like that is done already. The only difference is that they will now be able to track the batch number of the product you buy which is actually helpful to the consumer, it means that if there is a recall on a product the retailer can know exactly who bought from that particular batch and contact them directly to let them know not to consume it. It could even be used to automatically credit the consumer for the product.

Slashdot Top Deals

Kill Ugly Processor Architectures - Karl Lehenbauer

Working...