Clarification on a few points

Posted Jan 31, 2012 21:51 UTC (Tue) by dskoll (subscriber, #1630)
In reply to: Clarification on a few points by mjg59
Parent article: Garrett: The ongoing fight against GPL enforcement

But they'll still be using the kernel,

Assuming they're using the Linux kernel. Busybox can be used on a BSD kernel, no?

to post comments

Clarification on a few points

Posted Jan 31, 2012 21:56 UTC (Tue) by mjg59 (subscriber, #23239) [Link] (7 responses)

I'm not aware of any cases where people have been shipping devices with Busybox on non-Linux kernels. If you're using BSD then it's more common to just build the tools you need with crunchgen.

Clarification on a few points

Posted Feb 1, 2012 0:01 UTC (Wed) by landley (guest, #6789) [Link] (6 responses)

Busybox's include/platform.h was added on my watch to support the guy building against libgloss and the people who wanted to build against MacOS X and so on.

That said, board support packages usually provide kernel source because it's one package and you usually have to rebuild it to tailor it to the hardware. They don't necessarily rebuild the base userspace.

For example, at my day job the "bringup" department I'm working for has built kernels for three different new product boards since I got here. I build kernels every day. And each time they use a binary arago root filesystem tarball that hasn't been recompiled since I got here, with a toolchain they got from code sourcery in 2009. (The bringup department then hands said kernels off to the Android guys, who replace the root filesystem with Android stuff they get from Google, and layer their own stuff on top of it as android packages. Neither the kernels nor root filesystems actually _ship_, I'm just trying to make the hardware work and then they put android on it.)

Google's already excluding all GPL code from userspace, and android developers are happy to go along with it. I'm building a package the android guys might actually get to _use_. Busybox has existed since before android shipped, and doesn't get used on android, and isn't going to. Arguing whether or not it _should_, or how they'll come around if we wait for the sun to go out, has nothing to do with reality.

Linus Torvalds stopped waiting for the android developers to come around to his way of thinking, and started merging their code. I've usually considered Linus a good model. (Remember how he used a non-GPL license for Sparse because he was fed up with the FSF? I suspect git was only GPLv2 to quiet the "oh no bitkeeper"! hysteria, but haven't asked.)

I keep hearing people go "what, are they going to rewrite the kernel next if we make a big enough fuss about it"? And I keep going "MacOS X is BSD based became the most profitable company in the world using that; you think Google can't switch to that in a single development cycle if they really wanted to?"

Linux has stayed unified because of _LINUS_. Thinking that "oh it can't fork, it's GPL"... Android kernel anyone?

Red Hat almost standardized on Alan Cox's kernel back when Linus overloaded and spent months dropping patches (anybody remember my old "Patch Penguin" rant?), and Alan took a year off to go back to grad school to FORCE everybody to work with Linus (who took up bitkeeper to solve the scalability issue). The license has _helped_ keep Linux unified, but it's the community that's actually done it. The community of kernel developers who _REJECTED_ GPLv3, sidelined Richard Stallman, and never BOTHERED to launch widespread license enforcement lawsuits because they are a BAD IDEA. There's some saber rattling, but suing potential allies generally doesn't bring them closer to you. This isn't a defeat = friendship world.

Me, I reinvent the wheel a lot (hence working on busybox). I had to prove for myself that they're a bad idea. So I ran the experiment, and I reported the results, and whadaya know: It's a bad idea.

(I can't help it if other people want to repeat my mistakes and insist on finding out for themselves that fire is hot, but telling the guy with firsthand experience that you know more about it than he does gets old after a while.)

Clarification on a few points

Posted Feb 1, 2012 1:50 UTC (Wed) by Duncan (guest, #6647) [Link] (2 responses)

> Google's already excluding all GPL code from userspace, and android developers are happy to go along with it.

In practice, that remains to be determined in a court of law -- the Oracle case. What happens if Oracle wins? Google would have to pay penalties for past shipments, sure, but that doesn't resolve the future shipment problem.

What happens if they can't agree on a solution for future shipments? Google would have two alternatives, either quit shipping something they're doing 700K activations a day of, or suddenly reverse course on a GPLed userspace and keep shipping. Of course they /might/ have a third option lined up too, an independent replacement. But that would be a compatibility nightmare.

What I've been hoping for all along is pretty much just this scenario. There's a large enough Android ecosystem out there that any way this scenario plays out would set the whole tech world ringing with the implications. Would google and the rest of the ecosystem simply quit shipping? OUCH! Or would they bite the bullet and gamble that whatever the anti-GPL case was before, Android's too big to stop now just because it ends up being GPLed userspace? How much of the ecosystem would stay with them if they did?

Of course, that would put the ball back in Oracle's court as well, effectively calling their bluff on their GPLed Java. The risk is a toppling of the entire copyleft ecosystem and community, but imagine what a reputation the GPL would have if it survived THAT, regardless of how the rest of it plays out, Oracle trying to reverse course on Java's GPLing, OR challenging its patent provisions so that bit gets settled, OR folding and allowing Google to continue shipping, of course with rather zealous enforcement of the GPL provisions from someone with the money to do so, in an attempt to discourage everyone else from taking that same out.

That's still an unlikely scenario, but the first part of it, Google continuing to build Android shipments to the point where it /might/ be practical to force a GPLed userspace, and have people actually accept it, has certainly happened. Thus, the odds are far better than they were when that whole feud started.

And if Oracle /did/ choose the patent challenge route, it could very easily result in the whole tech world "going patent nuclear", thus very possibly settling the patent wars once and for all once all the dust settles, as well. Even if it didn't result in the patent world "going nuke", it should at least resolve the patent issues one way or another for the GPLv2, thus resolving all sorts of GPL community issues in that regard. If the GPLv2's patent provisions such as they are hold, it's solve a lot of Linux patent issues, and if they don't, well, the predictions leading to the GPLv3 would have been demonstrated to be true, and the GPLv2 licensed Linus kernel will end up being far closer license-wise to the BSDs than it is now, at least for anyone with patents.

So, yeah, while Google has to date taken a hard line on a GPLed Android userspace, that could yet change. I guess we'll see how this Oracle/Google case plays out at the trial court level at least, pretty quickly, now. There will certainly be appeals and it's likely to play out for years either way, just as SCO did, but the Android ecosystem and even the larger mobile computing ecosystem is I think way bigger already than the entire Linux ecosystem was when SCO started, and the waves could thus be MUCH MUCH bigger... either way!

Duncan

Clarification on a few points

Posted Feb 1, 2012 21:52 UTC (Wed) by Wol (subscriber, #4433) [Link]

Just to add to this - READ GROKLAW.

Firstly, Oracle launched this as a patent suit. Unfortunately for them, the patents have been comprehensively gutted.

Secondly, they threw in the copyright stuff as a side dish. Unfortunately, it seems to be all they've got left. And it's pretty irrelevant, because Google (a) never used the code in question, and (b) only distributed it by accident. It's a few lines of code (measured in hundreds of LOC if that), and it's part of the test suite that should NEVER get onto any shipping device.

Cheers,
Wol

Clarification on a few points

Posted Feb 1, 2012 21:57 UTC (Wed) by Wol (subscriber, #4433) [Link]

Whoops - I missed your comment about *if* Oracle choose the patent challenge route.

But, as you'll see from my other post, they DID choose the patent challenge route. And it seems the nuke detonated on launch ...

I can't remember all the figures, but they tried to sue over about 250 claims. The Judge said "that's too much, whittle it down to your best 15" or something like that. Google returned a major broadside and it seems out of those 250, Oracle is unlikely to find 15, or whatever it was the Judge said, to bring to trial! They might even get to trial only to find they don't have any valid patents to claim!

Cheers,
Wol

Clarification on a few points

Posted Feb 1, 2012 11:41 UTC (Wed) by mitchskin (subscriber, #32405) [Link] (1 responses)

Android does have some (L)GPL code in userspace: dbus, bluez, and webkit at least.

GPL in Android userspace

Posted Feb 2, 2012 12:58 UTC (Thu) by simonkelley (guest, #17525) [Link]

Android also has dnsmasq, which is GPLv2/GPLv3, in userspace. When they first started talking about removing GPL userspace I offered Google a license on pretty much any terms they wanted but covering use in Android only. They wouldn't take the "Android only" part, and dnsmasq is still in Ice Cream Sandwich under the GPL.

Clarification on a few points

Posted Feb 2, 2012 10:50 UTC (Thu) by paulj (subscriber, #341) [Link]

Google's already excluding all GPL code from userspace,

Hmm, Android's bluetooth support relies on Bluez, which is GPLv2+. Google stuck some IPC in between the Android stuff and the Bluez libraries, but I doubt that achieves the GPL-washing effect that Google are trying for, should BlueZ copyright holders ever care to do something.

So unless that's changed, your statement above appears to be incorrect.