- I have installed no proprietary driver, all loaded drivers declare to be
"GPL" or "Dual BSD/GPL".  I dicovered that I could "echo 0 >
/proc/sys/kernel/tainted"
 => is this reasonable ?
- I can't see in my logs any mention of the kernel becoming tainted (I
remember that on another machine, loading the e1000 driver triggered a
warning message - here I have no clue)
 => isn't there a mechanism that triggers a kernel log when "tainted" is set ?  
    Any reason for not having one ?
- In 2.4.18 I can't find any information about the modules licencing issues
in Documentation/modules.txt (nor in Documentation/kmod.txt, but I don't
feel this one would be the place for this, correct me if I'm wrong)
- Documentation/modules.txt still documents KERNELD, which AFAIK is not
supported any more in 2.4 kernels (and possibly since 2.2 IIRC).
 => does anyone who knows have the time to update this ?
 
-- 
Yann Dirson    <ydirson@altern.org> |    Why make M$-Bill richer & richer ?
Debian-related: <dirson@debian.org> |   Support Debian GNU/Linux:
Pro:    <yann.dirson@fr.alcove.com> |  Freedom, Power, Stability, Gratuity
     http://ydirson.free.fr/        | Check <http://www.debian.org/>
-
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/