From: "David Schwartz" <davids@webmaster.com>
To: "Andre Hedrick" <andre@linux-ide.org>,
"Roman Zippel" <zippel@linux-m68k.org>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: RE: Promise SATA driver GPL'd
Date: Wed, 23 Jul 2003 17:21:19 -0700 [thread overview]
Message-ID: <MDEHLPKNGKAHNMBLJOLKMEHPEJAA.davids@webmaster.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10307231516580.14556-100000@master.linux-ide.org>
> Freedom comes from keeping all of it free.
All code released publically is free. The more code you release, the more
freedom.
You seem to think that how much freedom you have is based upon what
percentage of code is free as opposed to how much free code there is. Nobody
can reduce the amount of free code, so nobody can reduce your freedom.
No matter how much code I write for which I don't give you the source, the
amount of code for which you do have the source is not reduced. The more
free code there is, the freer you are. The only thing that threatens your
freedom is if someone makes free code unfree. How do they do that?
If I add something and don't make it free, that doesn't reduce your
freedom. It only fails to increase it.
> Litigation is a means to prevent the blanket theift of today.
> You cleary do not get it.
The only thing a person can steal is what they themselves added. So no
theft takes any of your freedom away. You are still free, no matter how many
things that I produce I fail to give you.
> How do you plan to stop people from making changes to the kernel,
> packaging a binary kernel and selling it?
Would I be any better off if they didn't make the changes in the first
place? How can someone not giving me access to something they produced make
me any less free than if those things didn't exist at all?
Nobody can take your freedom away just by denying you something that they
produced.
DS
next prev parent reply other threads:[~2003-07-24 0:06 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-23 5:12 Adam J. Richter
2003-07-23 5:28 ` Andre Hedrick
2003-07-23 9:08 ` Adrian Bunk
2003-07-23 10:12 ` Matthias Andree
2003-07-23 10:21 ` Wichert Akkerman
2003-07-23 11:47 ` Alan Cox
2003-07-23 11:54 ` Wichert Akkerman
2003-07-23 22:22 ` On "any later version" in GPL [Was: Re: Promise SATA driver GPL'd] Horst von Brand
2003-07-23 10:37 ` Promise SATA driver GPL'd Adrian Bunk
2003-07-23 10:29 ` Alan Cox
2003-07-23 10:51 ` Adrian Bunk
2003-07-23 11:43 ` Alan Cox
2003-07-23 12:17 ` Adrian Bunk
2003-07-23 12:32 ` Martin Diehl
2003-07-23 12:57 ` Alan Cox
2003-07-23 19:08 ` Andre Hedrick
2003-07-23 19:19 ` Alan Cox
2003-07-23 19:33 ` Andre Hedrick
2003-07-23 19:46 ` Andre Hedrick
2003-07-23 20:59 ` Roman Zippel
2003-07-23 22:22 ` Andre Hedrick
2003-07-23 22:40 ` Roman Zippel
2003-07-23 22:35 ` Andre Hedrick
2003-07-23 23:02 ` Roman Zippel
2003-07-23 23:08 ` Andre Hedrick
2003-07-23 23:33 ` Roman Zippel
2003-07-23 23:45 ` Andre Hedrick
2003-07-24 0:14 ` dacin
2003-07-24 0:23 ` Andre Hedrick
2003-07-24 0:21 ` David Schwartz [this message]
2003-07-24 0:21 ` Andre Hedrick
2003-07-24 13:23 ` Jesse Pollard
2003-07-24 14:01 ` Richard B. Johnson
2003-07-24 18:37 ` David Schwartz
2003-07-23 22:32 ` Andre Hedrick
2003-07-23 22:46 ` Larry McVoy
2003-07-23 23:13 ` Roman Zippel
2003-07-23 10:40 ` Adam Sampson
-- strict thread matches above, loose matches on Subject: below --
2003-07-22 18:45 Erik Andersen
2003-07-22 18:54 ` Jeff Garzik
2003-07-22 19:07 ` Erik Andersen
2003-07-22 19:39 ` Samuel Flory
2003-07-22 20:56 ` Jeff Garzik
2003-07-22 21:39 ` Erik Andersen
2003-07-22 23:25 ` Jeff Garzik
2003-08-27 3:01 ` Nick Urbanik
2003-08-27 3:14 ` Jeff Garzik
2003-08-27 9:00 ` Matthias Andree
2003-08-27 11:51 ` Jeff Garzik
2003-07-22 20:57 ` Jeff Garzik
2003-07-23 13:20 ` Mark Watts
2003-07-23 1:59 ` Andre Hedrick
2003-07-23 2:38 ` Shawn
2003-07-23 10:32 ` Alan Cox
2003-07-23 18:58 ` Andre Hedrick
2003-07-24 11:22 ` Matthias Andree
2003-08-13 13:34 ` Vojtech Pavlik
2003-08-13 14:24 ` Jeff Garzik
2003-08-15 10:17 ` Andre Hedrick
2003-07-25 3:44 ` Milan Roubal
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=MDEHLPKNGKAHNMBLJOLKMEHPEJAA.davids@webmaster.com \
--to=davids@webmaster.com \
--cc=andre@linux-ide.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zippel@linux-m68k.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
all inboxes | Powered by JetHome®