From: Arjan van de Ven <arjanv@redhat.com>
To: James Morris <jmorris@redhat.com>
Cc: Jamie Lokier <jamie@shareable.org>,
Albert Cahalan <albert@users.sourceforge.net>,
linux-kernel mailing list <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@osdl.org>
Subject: Re: [OT] use of patented algorithms in the kernel ok or not?
Date: Sun, 21 Dec 2003 15:56:14 +0100 [thread overview]
Message-ID: <1072018574.5225.5.camel@laptop.fenrus.com> (raw)
In-Reply-To: <Xine.LNX.4.44.0312210833030.3044-100000@thoron.boston.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 970 bytes --]
> > I expect this was said in jest, but it would be delightful to see this
> > done for real. To the best of my knowlege it's uncharted territory,
> > so perhaps what you suggest _would_ be upheld in a court of law as
> > permissible?
> >
>
> This approach would turn Linux into proprietary software.
how so?
How is adding speed improvements to the code that may not be allowed in
ONE country make linux proprietary? We can't just rip out each and every
feature that ANY goverment or country in the world declares illegal/not
allowed to be used. CONFIG_USA and the like only provide a hint/helper
for those who want to use it in geographies where certain restrictions
are imposed by law on what software is allowed to do (without paying
third parties that is). Now of course it's a problem if the kernel
wouldn't function at all with CONFIG_USA is set (although perfectly ok
within the gpl afaics), but for additional performance improvements ?
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-12-21 14:56 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-21 1:12 [OT] use of patented algorithms in the kernel ok or not? Albert Cahalan
2003-12-21 10:53 ` Jamie Lokier
2003-12-21 13:35 ` James Morris
2003-12-21 14:30 ` Jamie Lokier
2003-12-21 16:03 ` Xavier Bestel
2003-12-21 14:56 ` Arjan van de Ven [this message]
2003-12-21 19:33 ` Stan Bubrouski
2003-12-21 23:25 ` Helge Hafting
2003-12-21 19:29 ` Stan Bubrouski
2003-12-21 19:55 ` Matthias Schniedermeyer
2003-12-21 20:11 ` Stan Bubrouski
2003-12-21 21:52 ` Francois Romieu
2003-12-21 21:57 ` Jamie Lokier
2003-12-22 9:50 ` John Bradford
2003-12-22 15:34 ` Adrian Cox
-- strict thread matches above, loose matches on Subject: below --
2003-12-22 1:43 James Lamanna
2003-12-22 11:32 ` Matti Aarnio
2003-12-18 23:11 Lennert Buytenhek
2003-12-19 6:10 ` Linus Torvalds
2003-12-19 7:38 ` Paul Jackson
2003-12-19 8:47 ` Arjan van de Ven
2003-12-19 11:38 ` Jan-Benedict Glaw
2003-12-20 17:28 ` Stefan Traby
2003-12-21 10:33 ` Jamie Lokier
2003-12-21 16:57 ` Pavel Machek
2004-01-13 15:35 ` Chuck Campbell
2004-01-13 19:35 ` Pavel Machek
2004-01-13 21:04 ` Richard B. Johnson
2003-12-22 0:37 ` jw schultz
2003-12-21 23:39 ` Lennert Buytenhek
2003-12-21 1:25 ` jw schultz
2003-12-21 19:40 ` Lennert Buytenhek
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=1072018574.5225.5.camel@laptop.fenrus.com \
--to=arjanv@redhat.com \
--cc=albert@users.sourceforge.net \
--cc=jamie@shareable.org \
--cc=jmorris@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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