From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.9-ac6
Date: 4 Sep 2001 22:52:03 -0700 [thread overview]
Message-ID: <9n4ei3$gn6$1@cesium.transmeta.com> (raw)
In-Reply-To: <17870.999661846@kao2.melbourne.sgi.com> <NOEJJDACGOHCKNCOGFOMOEBEDLAA.davids@webmaster.com>
Followup to: <NOEJJDACGOHCKNCOGFOMOEBEDLAA.davids@webmaster.com>
By author: "David Schwartz" <davids@webmaster.com>
In newsgroup: linux.dev.kernel
>
> Yes, but even if the module is GPL'd, the module could still cost $1,000
> and you're not entitled to the source if you didn't buy the module. If what
> you want is "source code is available to the general public", then that can
> be true or false for both GPL'd and non-GPL'd modules.
>
True enough, but if it's GPLd you are allowed to redistribute it free
of charge once you've bought it.
The main case of "unavailable GPL" code is probably modified GPL code
used within a company -- since only employees would have accessed to
the modified code, it simply would never get distributed.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt <amsp@zytor.com>
next prev parent reply other threads:[~2001-09-05 5:52 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-03 1:50 Linux 2.4.9-ac6 Alan Cox
2001-09-03 2:51 ` Keith Owens
2001-09-03 3:08 ` Dave Jones
2001-09-03 13:05 ` Andrea Arcangeli
2001-09-03 13:21 ` Alan Cox
2001-09-05 1:51 ` Keith Owens
2001-09-05 3:30 ` David Schwartz
2001-09-05 3:50 ` Keith Owens
2001-09-05 5:16 ` David Schwartz
2001-09-05 5:39 ` Alan Shutko
2001-09-05 18:46 ` David Schwartz
2001-09-05 5:52 ` H. Peter Anvin [this message]
2001-09-05 5:56 ` Aaron Lehmann
2001-09-05 7:03 ` David Schwartz
2001-09-05 7:09 ` David Schwartz
2001-09-05 9:50 ` Alex Bligh - linux-kernel
2001-09-05 9:57 ` David Schwartz
2001-09-05 12:50 ` christophe barbé
2001-09-05 13:06 ` Alan Cox
2001-09-05 13:14 ` Alex Bligh - linux-kernel
2001-09-05 13:23 ` christophe barbé
2001-09-05 14:05 ` Henning P. Schmiedehausen
2001-09-05 7:18 ` Aaron Lehmann
2001-09-05 7:19 ` David Schwartz
2001-09-05 9:41 ` Justin Guyett
2001-09-05 9:53 ` David Schwartz
2001-09-05 10:21 ` Justin Guyett
2001-09-05 11:55 ` Alan Cox
2001-09-05 18:46 ` David Schwartz
2001-09-05 18:54 ` Alan Cox
2001-09-05 22:09 ` Linux 2.4.9-ac6 (really about tainting) David Schwartz
2001-09-05 12:07 ` Linux 2.4.9-ac6 Alan Cox
2001-09-05 12:16 ` Arjan van de Ven
2001-09-05 12:23 ` Jan-Benedict Glaw
-- strict thread matches above, loose matches on Subject: below --
2001-09-05 14:36 Thomas Foerster
2001-09-06 19:23 ` Camiel Vanderhoeven
2001-09-06 20:14 ` Alan Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='9n4ei3$gn6$1@cesium.transmeta.com' \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox