kedardamle wrote:That's lame,
Well, that's a matter of opinion, if it was not a requirement, what you'd have is the BSD/MIT/X11 licenses.
kedardamle wrote:I can't give out free software to someone if I don't have the source code.
That is correct, and the reason is, if it was not this way, Apple could easily use GPLed code in Mac OS X, and their kernel sucks, so I can only imagine Steve Jobs wanting to use the Linux kernel. I mean seriously, this is a basic requirement of the GPL! Copyright law, by default says "all rights reserved buddy, hands off!", the GPL is the only channel for lessening that total lock-down. So if you violate the GPL, which terminates your permission to distribute the software, you obviously cannot distribute the software.
kedardamle wrote:Does this apply to me giving my friend the latest ubuntu disc ?
Technically, yes. This is a reason why GPLv3 is really sooooo much better a license for today's world, for which it is written. Remember GPLv2 was written in in 1991, this was before ANY average person in society had any sort of fast Internet. If you gave me an Ubuntu disc, and I asked you for the source code, it would technically be a GPLv2 violation for you to simply point to Ubuntu's servers and say "Go get it there", even if you're 100% sincere about it, although I doubt anybody in the world would sue you for it, unless it was preventing me from getting the source code. The reason is that GPLv2 requires every "node in the network" if you will, to provide source code, you can't simply point to a central point. The reason for this, is that back in the day, Internet accessibility and speed would be a technical barrier for people to get the source code. If I only had ASS-SLOW dial-up, and you only offered the source code on Internet, I did not get the four freedoms in reality, only in theory, and the purpose of the GPL in any revision, is to absolutely and completely safeguard the four freedoms, NOT to be a good development model as Linus Torvalds
seems to think.
kedardamle wrote:By the way should it be a problem even if I am pointing to the original project's website for the torrent?
Torrent files themselves, does not contain any data, it just contains file information and hashes etc. etc. so that is no problem. And torrents in general is not a problem, because it's not a central point.
kedardamle wrote:I already put up FreeBSD 5.5 Release CD torrent links, the links just point you to the FreeBSD BitTorrent Tracker page for the concerned disc image. Have a look and tell me if this is fine. I know, I know with FreeBSD there is not liability of the GPL, but as an example.
--
http://oldunixcd.8tt.org/blog
Actually there is, because FreeBSD does include, GCC etc. etc.
Anyway, the main thing you need to watch out for. Is if you start to distribute stuff like Red Hat 6.0. GPLv2 only requires people to provide source for three years:
GPLv2 wrote: b) Accompany it with a written offer, valid for at least three
years, to give any third party, for a charge no more than your
cost of physically performing source distribution, a complete
machine-readable copy of the corresponding source code, to be
distributed under the terms of Sections 1 and 2 above on a medium
customarily used for software interchange; or,
Unless you can dig up the source code for that stuff, you cannot distribute the binary. The reason is the same basic requirement to provide source code that prevents the likes of Apple, from (ab?)using GPLed code inside of the parts of Mac OS X that is not under GPL, because they must then provide source code for the entire program under the GPL. If you distribute a binary, you MUST provide the people you give it to, the source code, so that they can have the same four freedoms that you had. And if you don't have the source code, it's too bad, to put it frankly, but there just can't be any exceptions to this rule, otherwise, Apples would run amok!
