lkml.org 
[lkml]   [2001]   [Nov]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Changed message for GPLONLY symbols

On Tue, Nov 13, 2001 at 01:50:09PM +1100, 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. This is probably due to a
coding or configuration problem. Contact the module supplier
for assistance.

Since the attempt by an non-GPL module to use GPLONLY sysbols is a
coding error IMHO, this message is clearer and avoids the confusion we
have been seeing.

> 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?
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:13    [from the cache]
©2003-2011 Jasper Spaans