Skip to content

Comment on Google's Android faces a serious Linux copyright issueparent

Comments

Edward Naughton, a prominent IP litigator, said in his Huffington Post article on this that he's skeptical of Google's approach because he believes the header material they copied is likely copyrightable. If it's copyrightable, it can't just be relicensed by third parties.

During all those years that Linux has been around, no one other than Google has tried to take this kind of material from the original kernel headers and publish it under any license other than the GPL. And no one has tried to do an alternative glibc. I guess what someone would do is take glibc and fork it on LGPL terms.

Eh wha? No-one has tried to do an alternative glibc? Wrong:

http://www.fefe.de/dietlibc/

http://www.uclibc.org/

http://sourceware.org/newlib/

Does any of those libraries gut the original Linux kernel headers the way Bionic does? Not as far as I can see.

You can build libraries if you like, but you can't just put header code under a different license unless you're the original right holder or have the original right holder's consent.

You said that no-one has tried to do an alternative to glibc. I proved you wrong. I never made any statements on anything else you said, so really I am not sure what you are arguing for or against...

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.