From: Lars Marowsky-Bree <lmb@suse.de>
To: "Richard B. Johnson" <linux-os@analogic.com>,
Michal Jaegermann <michal@harddata.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: A "new driver model" and EXPORT_SYMBOL_GPL question
Date: Tue, 5 Jul 2005 14:06:21 +0200 [thread overview]
Message-ID: <20050705120621.GM2879@marowsky-bree.de> (raw)
In-Reply-To: <Pine.LNX.4.61.0507050703220.20388@chaos.analogic.com>
On 2005-07-05T07:09:47, "Richard B. Johnson" <linux-os@analogic.com> wrote:
> This problem will continue. Eventually there will be no general
> exported symbols. The apparent idea is to prevent the use of the
> kernel in proprietary systems.
... with proprietary kernel extensions. There's a difference.
> Not to worry. The tools provided with a typical Linux distribution
> are capable of resolving those symbols. You can make a script
> that `greps` System.map for the correct offsets of those symbols.
> You can use those offsets in a linker script.
If it wasn't you, I'd be assuming you'd be joking when suggesting to
subvert the clear wishes of and licensing granted by the copyright
holders and authors.
Sincerely,
Lars Marowsky-Brée <lmb@suse.de>
--
High Availability & Clustering
SUSE Labs, Research and Development
SUSE LINUX Products GmbH - A Novell Business -- Charles Darwin
"Ignorance more frequently begets confidence than does knowledge"
prev parent reply other threads:[~2005-07-05 12:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-03 23:12 A "new driver model" and EXPORT_SYMBOL_GPL question Michal Jaegermann
2005-07-04 5:44 ` Greg KH
2005-07-04 16:00 ` Michal Jaegermann
2005-07-05 21:50 ` Zan Lynx
2005-07-05 21:57 ` Greg KH
2005-07-06 4:37 ` Michal Jaegermann
2005-07-06 5:26 ` Greg KH
2005-07-05 11:09 ` Richard B. Johnson
2005-07-05 12:06 ` Lars Marowsky-Bree [this message]
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=20050705120621.GM2879@marowsky-bree.de \
--to=lmb@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.com \
--cc=michal@harddata.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.