Hi, Jean-Eric!
Jean-Eric Cuendet (Jean-Eric.Cuendet@linkvest.com) wrote 1 lines:
> > > The tainted flag is set because the
> > > vfat module I think. Kernel says: no license, will taint the kernel (or
> > > similar to this).
> > Aha, I'd heard there were a few of those :-(
> Could you please explain in more details what are those license things
> and taint things?
There are modules for which there is no source code available.
While it's OK to use these modules[1] it is absolutely
impossible to debug kernels with these modules inserted.
(And there's no reason for the open source community to
debug closed source which uses the open source in that rather
intimate way.)
Thus the kernel gains a 'tainted' flag and any oops report
will show that fact, saving the developers a heap of time
'cause they won't have to chase e.g. vmware bugs.
As some modules have no or misleading license information,
they get tainted as well, until the information has been added.
-Wolfgang
[1] vmware comes to mind, but several graphics cards etc. do
the same dance
