From: Skip Ford <skip.ford@verizon.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Changed message for GPLONLY symbols
Date: Tue, 13 Nov 2001 06:19:23 -0500 [thread overview]
Message-ID: <200111131114.fADBEC805094@smtp010pub.verizon.net> (raw)
In-Reply-To: <10444.1005619809@kao2.melbourne.sgi.com>
In-Reply-To: <10444.1005619809@kao2.melbourne.sgi.com>; from kaos@ocs.com.au on Tue, Nov 13, 2001 at 01:50:09PM +1100
[-- Attachment #1: Type: text/plain, Size: 966 bytes --]
Keith Owens wrote:
> When insmod detects a non-GPL module with unresolved symbols it
> currently says:
>
> Note: modules without a GPL compatible license cannot use GPLONLY_ symbols
>
> I thought that hint was self-explanatory, obviously it was not clear.
> Never underestimate the ability of lusers to misread a message. insmod
> 2.4.12 will say
>
> Hint: You are trying to load a module without a GPL compatible license
> and it has unresolved symbols. The module may be trying to access
> GPLONLY symbols but the problem is more likely to be a coding or
> user error. Contact the module supplier for assistance.
>
> Does anyone think that this message can be misunderstood by anybody
> with the "intelligence" of the normal Windoze user?
How about 'Error: unresolved symbols (incorrect module/kernel version?)'
It's pointless to state the license type if all symbols can't be resolved.
--
Skip ID: 0x7EDDDB0A
[-- Attachment #2: Type: application/pgp-signature, Size: 163 bytes --]
next prev parent reply other threads:[~2001-11-13 11:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-13 2:50 Keith Owens
2001-11-13 3:01 ` Richard Gooch
2001-11-13 3:20 ` Keith Owens
2001-11-13 20:54 ` Riley Williams
2001-11-13 6:12 ` andrew may
2001-11-13 6:39 ` Anthony DeRobertis
2001-11-14 1:40 ` Mike Fedyk
2001-11-28 23:02 ` Dr. Kelsey Hudson
2001-11-13 11:19 ` Skip Ford [this message]
2001-11-13 17:10 ` Alex Bligh - linux-kernel
2001-11-13 17:34 ` Tommy Reynolds
2001-11-13 18:04 ` Alex Bligh - linux-kernel
2001-11-13 18:22 ` Sascha Andres
2001-11-13 20:50 ` Riley Williams
2001-11-15 18:11 ` Brian Beattie
2001-11-27 2:20 Michael T. Babcock
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=200111131114.fADBEC805094@smtp010pub.verizon.net \
--to=skip.ford@verizon.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
all inboxes | Powered by JetHome®