Linked by Thom Holwerda on Mon 21st Sep 2009 08:44 UTC, submitted by Cytor
There are several options out there if you wan to run Mac OS X on your non-Apple labelled computer, but one of them appears to be in serious trouble. It has been uncovered that the EFI-X module is nothing more than a USB stick with a DRM chip, with code from the hackintosh community on it - without attribution. On top of that, its firmware update utility uses LGPL code - again, without attribution.
Thread beginning with comment 385405
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: "Disagreeing with the GPL"
by lemur2 on Tue 22nd Sep 2009 05:21
in reply to "RE: "Disagreeing with the GPL""
Member since:2007-02-17
As you are so eager to educate us about GPL, please mention also the requirements of GPL regarding those permissions mentioned in the license. Because, you know, those are the real gist of GPL.
The GPL cannot impose a "requirement" on anyone, because the GPL is not law, and it is not a contract. It is a license. It gives you permissions, some permissions it gives you unconditionally, and one permission it gives you only if you meet certain conditions. If you don't meet the conditions, the only "penalty" is that you don't get that last permission.
I listed the permissions given by the GPL in my last post, the one to which you replied. Of the five permissions you get, the first four are given to you unconditionally, and the last one is given to you if you meet the condition, which I also stated.
Here it is again, in summary:
OK, so the GPL is a license to do the following things with the covered code:
(1) copy the code on to as many of one's own machines as one wishes,
(2) run the code on as many of one's own machines as one wishes,
(3) study the source code,
(4) modify the source code for use on as many of one's own machines as one wishes, and
(5) give the code out again (or sell it) to other recipients (either with or without one's own modifications) provided one gives the forward recipient the exact same permissions as listed here.
(1) copy the code on to as many of one's own machines as one wishes,
(2) run the code on as many of one's own machines as one wishes,
(3) study the source code,
(4) modify the source code for use on as many of one's own machines as one wishes, and
(5) give the code out again (or sell it) to other recipients (either with or without one's own modifications) provided one gives the forward recipient the exact same permissions as listed here.
For those of you who suffer unfrotunate reading comprehension problems, the "condition" is the phrase that comes after the word "provided" above.
Edited 2009-09-22 05:30 UTC
Member since:
2009-05-20
As you are so eager to educate us about GPL, please mention also the requirements of GPL regarding those permissions mentioned in the license. Because, you know, those are the real gist of GPL.