Review: Lindows 2.0 Dissected

Bob the Knob writes "Extremetech has done an in-depth review of Lindows. The guy who wrote it didn't think too much of Lindows before looking at it but he seemed to like it after doing a hands-on."

Comments

This could violate the GPL

[petard]

Those who have received from Lindows.com the binaries for any GPL'd software can also find the source code available for download in their my.lindows.com account.

Take the GPL Quiz. Lindows is required to distribute the source to anyone who has received the binaries and requests the source... not just "those who have received [binaries] from Linxows.com".

GPL and access to source (Re:Lindows Bashing)

[Hanno]

To clear up a common misunderstanding of the GPL. In brief, the GPL states that...

• if you use GPL'd source code as the code base of your product, you can still sell your product for any price you want and you are allowed to ship your product without source code

• you must, however, make the full source code available upon request to those who bought your product, and you are allowed to charge a reasonable fee for this service (which means, afaik, the copying and media cost, but not an added sales price)

• and - now HERE'S THE CATCH - you can't dictate those who have access to your source code (i.e. the buyers of your product) what they do with it.

  You can't stop your client from developing (and selling!) his own version of your original product, you can't stop your client from giving away the source for free, you can't stop your client from posting the source on a public internet server etc.

The philosophy of the GPL is NOT you must give out full free source code but you must allow access the full source code to your client AND you can't tell him what to do with it. This last part is the "free" in "free software".

Of course, as a result most GPL'd software isn't "sold" as a product, but as a service. I don't sell Apache to my clients, but they pay me for installing and maintaining their web servers, which is a service for them, not a software they buy.

E.g., when I modify a GPL'd software for a client (which I have done in the past), I charge my client by the hour for the service of modifying it, but I don't charge the client for, say, a license of "Hanno Mueller's version of XYZ version 0.1".

And since I have already been paid for the modification, I return the patch to the maintainers of the software, who may or may not use it.