| |||||||||||||
Proprietary loadable kernel modulesProprietary loadable kernel modulesPosted Mar 21, 2011 9:56 UTC (Mon) by FlorianMueller (guest, #32048)In reply to: Proprietary loadable kernel modules by foom Parent article: Has Bionic stepped over the GPL line?
The differences are quite fundamental. glibc uses the "sanitized" headers provided by the kernel maintainers for the purpose of creating libraries. Google reprocesses and repurposes the "raw" (original, non-sanitized) kernel headers.
(Log in to post comments)
Proprietary loadable kernel modules Posted Mar 21, 2011 11:01 UTC (Mon) by nix (subscriber, #2304) [Link]
So... what magic does the headers_install script perform to strip out copyright that the (very similar) script that Google provides omits to do? It would be trivial for Google to use the output of headers_install, and then all your doom-mongering would be for nothing (except to spread FUD, but that *of course* isn't your intention, oh no).
Proprietary loadable kernel modules Posted Mar 21, 2011 11:05 UTC (Mon) by FlorianMueller (guest, #32048) [Link]
One of the differences is that the output of headers_install is provided by the kernel maintainer for the purpose of integration into C libraries. That's different than just repurposing something else.
Your thinly-veiled FUD accusation is unwarranted. If it's (according to you) trivial for Google to use the output of headers_install, and if they do that in the future, everything's fine from my point of view. I'd love to see exactly that happen, and the sooner, the better. So the easier it is for them to do it, the better. Still I believe this must be done.
Proprietary loadable kernel modules Posted Mar 21, 2011 12:44 UTC (Mon) by sorpigal (subscriber, #36106) [Link] You're talking lawyer-magic here, not reality. Only in lawyer-magic-land does it matter whether they use the "raw" headers and then create their stripped version or use the headers_install version and then create their stripped version. Lawyers may think that there's a difference, but there isn't.
|
|||||||||||||