From: "Justin Hibbits <jrh29@po.cwru.edu>"@opus.INS.cwru.edu
To: linux-kernel@vger.kernel.org
Cc: torvalds@transmeta.com
Subject: Exporting GPLONLY symbols (Please CC to my email address)
Date: Mon, 10 Dec 2001 22:41:56 -0500 [thread overview]
Message-ID: <20011210224156.E14022@po.cwru.edu> (raw)
Umm....I'm a new poster here to the list, but, nonetheless, I have a
small complaint about the track the kernel is taking with respect to
kernel modules, specifically the exporting of symbols as GPLONLY. I
understand that several hackers are pushing to export many symbols as
GPLONLY, which I feel is a very bad idea. The NVidia drivers will no
longer work, and any other module which depends on symbols which will
eventually be exported as GPLONLY will also no longer work. Do you guys
really want to restrict everyone to using modules licensed under the
GPL? I've read and understand the GPL all too well, and came to the
conclusion that it's a horrible license to begin with, given the simple
fact that Stallman's communist views are in it, forcing everything
licensed under it to be under every future license....with one change to
the license, he can claim all source licensed under the GPL.
I agree with Cox that something has to be done to warn the average user
that inserting closed source modules might cause something bad, and you
guys can't do anything about it, but FORCING all modules to become GPL
is the stupidest idea yet! Linux is starting to take the road of M$,
forcing a one-licensed approach. Not cool guys.
Those are my thoughts.
Justin Hibbits
next reply other threads:[~2001-12-11 3:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-11 3:41 Justin Hibbits <jrh29@po.cwru.edu> [this message]
[not found] ` <jrh29@po.cwru.edu>
2001-12-11 6:55 ` David Weinehall
2001-12-11 7:47 ` Richard Gooch
2001-12-11 12:46 ` Alan Cox
2001-12-11 4:27 jrh29
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=20011210224156.E14022@po.cwru.edu \
--to="justin hibbits <jrh29@po.cwru.edu>"@opus.ins.cwru.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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®