Mailing List Archive
tlug.jp Mailing List tlug archive tlug Mailing List Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: [tlug] linux in Japanese schools
- Date: Sat, 6 Jan 2007 14:53:13 +0100 (MET)
- From: Marcus Metzler <mocm@example.com>
- Subject: Re: [tlug] linux in Japanese schools
- References: <459645EB.7020606@example.com> <b4d277190612300408x7dc5f973m8c59d0ac51e6415d@example.com> <83a2a4180701060237g6960f029k66a79bfa14a75e19@example.com> <B247F759-EAC9-45BF-9D66-4F051BDFB5B9@example.com> <Pine.NEB.4.64.0701062148320.29071@example.com>
>>>>> "Curt" == Curt Sampson <cjs@example.com> writes: Curt> On Sat, 6 Jan 2007, Jean-Christophe Helary wrote: >> I totally agree with that but I think current practice is to >> use "ãããããã" instead of "èçããã". Or did I miss the >> places where "èçããã" is used intensively ? Curt> Actually, maybe someone can explain this to me, because I've Curt> been puzzling over it for years. Curt> So with something like BSD-licensed software, when you get Curt> hold of it, you can do what you like with it. You can change Curt> it, keep your changes to yourself, and sell compiled Curt> versions for money, if that's what you want to do. There are Curt> very few restrictions on your freedom to do what you want Curt> with that code, beyond clause three the four-clause versions Curt> of that license (which generally compell you to say that Curt> your product includes code from wherever). Curt> With GPL'd software, the situation seems to me exactly the Curt> opposite. You have many more restrictions on what you can Curt> do with this software; for example, you cannot change the Curt> source, keep your changes secret, and sell your new version, Curt> as you can with the BSD license. However, anybody who gets Curt> any version of a GPL'd program, under the license, is Curt> entitled to the source code at no charge. The main effect of Curt> this seems to be that it is highly unlikely you will ever Curt> have to pay money for a piece of GPL'd software if you don't Curt> want to, even if it's a version with substantial Curt> modifications that the developer would rather keep Curt> proprietary. Curt> Now, I (perhaps naively) interpret "free beer" as "you don't Curt> have to pay money for it," and "free speech" as "you can do Curt> what you want." But it seems to me that the GPL can be Curt> summarized as, "the software will always be free of charge, Curt> and we place restrictions on the receivers to make that so," Curt> and the BSD licence can be summarised as, "you can do what Curt> you want with it, even charge people for variants." So Curt> wouldn't that mean that the GPL is "free as in beer," and Curt> the BSD license is "free as in speech"? Curt> Why is it claimed that the GPL is "free as in speech" when Curt> it places more restrictions on the freedom of the users of Curt> the software than the BSD (or many other) open source Curt> licenses? Is this a trolling attempt? There are no restrictions on the user under the GPL, only on (re-) distribution. Marcus -- /--------------------------------------------------------------------\ | Dr. Marcus O.C. Metzler | | | mocm@example.com | http://www.metzlerbros.de/ | \--------------------------------------------------------------------/ |>>> Quis custodiet ipsos custodes <<<|
- References:
- Re: [tlug] linux in Japanese schools
- From: Marty Pauley
- Re: [tlug] linux in Japanese schools
- From: Jean-Christophe Helary
- Re: [tlug] linux in Japanese schools
- From: Curt Sampson
Home | Main Index | Thread Index
- Prev by Date: Re: [tlug] linux in Japanese schools
- Next by Date: Re: [tlug] linux in Japanese schools
- Previous by thread: Re: [tlug] linux in Japanese schools
- Next by thread: Re: [tlug] linux in Japanese schools
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links