From: "D. ShadowWolf" <dhazelton@enter.net>
To: linux-kernel@vger.kernel.org
Subject: Re: inter_module_get and __symbol_get
Date: Sun, 31 Jul 2005 00:27:18 -0400 [thread overview]
Message-ID: <200507310027.18484.dhazelton@enter.net> (raw)
On this topic I have to weigh in that I just subscribed to the kernel list
because I have had to undo a modification made to the kernel around version
2.6.10 that stopped the export of 'inter_module_get'. To me it appears that
some kernel developers forget that there are those of us out there who do not
have broadband connections and are shafted with low-end hardware. In this
case I am currently stuck using a Lucent Winmodem to connect to the internet.
The need to undo that patch arose when I upgraded to 2.6.12.3 and found that
the drivers provided by the linmodem project were dependant on that function.
If the new system has been targeted at only GPL symbols, then I am certain it
is definately not something good for the kernel.
I enjoy GPL'd software as much as the next guy, but forgetting that there are
people in the world dependant on third-party drivers that may or may not have
a non-GPL license attached to them shows short-sightedness on the part of the
people involved.
I have my own issues with the modem I'm currently using, and with the fact
that Lucent sits behind a wall of NDA's and other legal documents and refuses
to release the entire source of the driver, instead making us rely on a
driver that has a precompiled binary as part of it's source. I'm certain
there are people that could reverse engineer the binary (I could do it
myself), but with the current state of the law in the US and abroad doing so
could cause major legal troubles.
Well... enough rambling. I've used too much bandwidth as it is.
DRH
next reply other threads:[~2005-07-31 4:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-31 4:27 D. ShadowWolf [this message]
2005-08-01 1:04 ` inter_module_get and __symbol_get Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2005-01-06 21:32 Terence Ripperda
2005-01-06 21:57 ` Brian Gerst
2005-01-06 22:51 ` Terence Ripperda
2005-01-08 4:00 ` Jon Smirl
2005-01-12 19:37 ` Terence Ripperda
2005-01-12 22:21 ` Brian Gerst
2005-01-08 3:10 ` Keith Owens
2005-01-24 22:36 ` David Mosberger
2005-01-24 22:44 ` Keith Owens
2005-01-24 22:52 ` David Mosberger
2005-01-24 22:54 ` Keith Owens
2005-01-24 22:58 ` David Mosberger
2005-01-24 23:03 ` Keith Owens
2005-01-25 1:01 ` Jon Smirl
2005-01-24 23:19 ` Jon Smirl
2005-01-24 23:23 ` David Mosberger
2005-01-25 5:31 ` Terence Ripperda
2005-01-25 5:59 ` Chris Wedgwood
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=200507310027.18484.dhazelton@enter.net \
--to=dhazelton@enter.net \
--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