> I think, perhaps, the logic should be that a module
> shouldn't taint the kernel if:
>
> 1) The user built the module from source on that machine, OR
>
> 2) The module source is freely available without restriction
I just realized two things. One, there's a strong argument that this should
be an AND, not an OR. Second, even if the code is freely available, it might
have been locally modified and the local modifications may not be easily
available (this can happen even if the code is GPL'd since source
distribution is only required if the compiled code is distributed). So the
stamping of the module source as freely available would have to have a
checksum or something like that. (Unless this is officially deemed to be No
Big Deal.)
DS
-
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/
This archive was generated by hypermail 2b29 : Fri Sep 07 2001 - 21:00:29 EST