[lkml]   [2002]   [Apr]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: The tainted message
On Mon, 29 Apr 2002, Ian Molton wrote:

> tomas szepe Awoke this dragon, who will now respond:
> > > Warning: The module (%s) does not seem to have a compatible license.
> > > Please contact the supplier of this module regarding any
> > > problems, or reproduce the problem after rebooting without
> > > ever loading this module.
> > >
> > > shorter?
> >
> > I don't think you can strip the part about open-ness of the code --
> > it's an essential part of the explanation. And "any problems" might
> > be too broad.
> Moreover, I think the 'compatible license thing doesnt fly.
> the argument against CLOSE modules is that they make the _whole_package_
> undebuggable.
> if the source is available, no matter HOW crippling its license, the
> package _IS_ debuggable.
> thie warning should be:
> Warning: Module %s is not open source, and as such, loading it will make
> your kernel un-debuggable. Please do not submit bug reports from a kernel
> with this module loaded, as they will be useless, and likely ignored.

well, that's not the truth: the kernel itself is debuggable, but we don't
know about the module, and how the module interacts with the

why not simply state that "the source to this module doesn't seem to be
available..." ?

in some way i do, and in some way i don't.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:22    [W:0.125 / U:1.144 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site