Home opinion-and-analysis Open Sauce Third time lucky? Naughton raises Google GPL claims again

Author's Opinion

The views in this column are those of the author and do not necessarily reflect the views of iTWire.

Have your say and comment below.

Edward Naughton is at it again. The lawyer from Brown Rudnick has for the third time alleged that Google is violating the terms of the GPLv2 under which the Linux kernel is distributed.


Naughton made the same claim in March and again in August. It looks like nobody is listening to his dog whistling else he wouldn't be at it for the third time in a calendar year.

His charges are the same: a key component of Android, the Bionic library which is used to access the core features of the Linux kernel code, was developed by Google stripping the kernel headers and then declaring those files free of the copyright restrictions placed on it by the GPL.

Naughton's third bid for attention attempts to analyse his earlier allegations in light of the summary judgement in the case between Google and Oracle; the case revolves around Dalvik, the VM created by Google. Oracle claims this is in violation of its Java APIs and code.

Linux expert Brian Proffitt has done an excellent analysis of the charges in Naughton chapter 3 (PDF). Read it, is my advice. There are a lot of general issues that present themselves, though, and which Proffitt has not touched on.

Exactly why Naughton should be so agitated about this issue - which is a hypothesis, remember - is unclear.

One reason could be that he is touting for business. Despite the fact that Android has been late on the handheld scene, it is slowly becoming the dominant operating system for handheld devices by a big margin.

Manufacturers love it because it is free. They love the flexibility that the Linux kernel offers. They love even more the fact that Google's own additions to it are under an Apache licence which has none of the strictures of the GPL.

Hence if there is something that could get in the way of Android being distributed and a competitor could prove that in court with the aid of our good friend Naughton, why it would be payday for the lawyer. And not an ordinary payday either.

FREE WHITEPAPER - RISKS OF MOVING DATABASES TO VMWARE

VMware changed the rules about the server resources required to keep a database responding

It's now more difficult for DBAs to see interaction between the database and server resources

This whitepaper highlights the key differences between performance management between physical and virtual servers, and maps out the five most common trouble spots when moving production databases to VMware

1. Innacurate metrics
2. Dynamic resource allocation
3. No control over Host Resources
4. Limited DBA visibility
5. Mutual ignorance

Don't move your database to VMware before learning about these potential risks, download this FREE Whitepaper now!

DOWNLOAD!

Sam Varghese

website statistics

A professional journalist with decades of experience, Sam for nine years used DOS and then Windows, which led him to start experimenting with GNU/Linux in 1998. Since then he has written widely about the use of both free and open source software, and the people behind the code. His personal blog is titled Irregular Expression.

Connect