From: Jamie Lokier <jamie@shareable.org>
To: James Morris <jmorris@redhat.com>
Cc: 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 14:30:43 +0000 [thread overview]
Message-ID: <20031221143043.GJ3438@mail.shareable.org> (raw)
In-Reply-To: <Xine.LNX.4.44.0312210833030.3044-100000@thoron.boston.redhat.com>
James Morris wrote:
> This approach would turn Linux into proprietary software.
You're saying a Linux kernel with _more_ capabilities that I and
everyone else outside the USA can use, learn from, modify and
distribute freely is proprietary, whereas denying me access to those
capabilities is more free?
I guess it is more free for people living within the patented economic
zones, and less free for people outside them.
To put it into perspective: I'd love for Mandrake or SuSE or Polish or
Red Flag Linux to come with a full suite of modem, DSL and wireless
drivers, and support for VFAT and Longhorn filesystems.
There's two ways to go about it:
1. First way is we develop a common Linux kernel which everyone in
the USA may use, even if it contains things like encryption
which are not so legal in some other parts of the world.
This is obviously how it's done right now.
Mandrake, SuSE, Polish, Red Flag and everyone else outside the
USA must apply the Big Linux Patch to build kernels which
support all the extra devices and filesystems.
2. Second way is to include all those extra wireless drivers
etc. in the common kernel, but disable them somehow for USA
users. Note that the USA users have not lost anything.
Distributing the code in disabled form _may_ not be legal in
practice, I simply do not know, so maybe the second way is not
permissible. But if there is a chance it is permissible, don't
you think it should be explored?
-- Jamie
next prev parent reply other threads:[~2003-12-21 14:31 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 [this message]
2003-12-21 16:03 ` Xavier Bestel
2003-12-21 14:56 ` Arjan van de Ven
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=20031221143043.GJ3438@mail.shareable.org \
--to=jamie@shareable.org \
--cc=albert@users.sourceforge.net \
--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;
as well as URLs for NNTP newsgroup(s).