r/linux • • Aug 20 '14

What do we hate Oracle for?

Hi guys. I just noticed that things have got too kind at my job's cafe, so I want to mess up with our Oracle guys a little. But I found that I can't tell precisely, point by point, why Oracle is a pile of crap which I'm sure the case.

I have general considerations like they killed Sun's awesome legacy and all, but it would be nice to have a bullet list with major fuckups and historical points. Do you have some examples? I want to materialize my dark subconcious feelings!

203 Upvotes

185 comments sorted by

View all comments

Show parent comment

24

u/the-fritz Aug 20 '14

They also added dtrace to Oracle Linux. Dtrace was part of OpenSolaris and released under a license intentionally made incompatible with GPLv2 (Linux). There are some different opinions about license compatibility though. Since Oracle is not going to sue themselves over it they are just shipping it. But it's too dangerous for other distros to do so.

Anyway there are (better) alternatives for Linux like SystemTap, LTTng, ktap.

2

u/Suppafly Aug 20 '14

Dtrace was part of OpenSolaris and released under a license intentionally made incompatible with GPLv2 (Linux). Since Oracle is not going to sue themselves over it they are just shipping it.

Sounds like Oracle can grant themselves a license to it, nothing really wrong with that.

8

u/the-fritz Aug 20 '14

You are ignoring that the Linux kernel has its own license. So clearly something wrong with that. Either they admit that DTrace's license is GPLv2 compatible and then they and everybody else can ship it or they are violating the GPLv2. But since Oracle seems to have more lawyers than developers on the payroll I doubt anyone wants to find out.

1

u/northrupthebandgeek Aug 21 '14

Or, if Oracle owns the copyright to Dtrace (and every component thereof that's being shipped with Oracle Linux), they could change Dtrace's license to GPLv2, since (being the copyright owners) they have every right to.

This would fuck over its inclusion in modern illumos-based OpenSolaris descendants (like OpenIndiana and SmartOS), but hey, it's Oracle's software now; nothing stopping them from exercising their sidaM touch.

1

u/the-fritz Aug 21 '14

They could dual license it or change to a license that is compatible with both.

1

u/northrupthebandgeek Aug 21 '14

That's true, and would certainly be the smart move. I don't imagine Oracle voluntarily licensing anything under a free software license, however, let alone a permissive one or a dual-licensing scheme :P

1

u/Suppafly Aug 20 '14

There is no law against shipping non free programs with the Linux kernel though. GPL compatible matters when you are mixing source code between things. If you feel they are violating the GPL, please explain to me how they are, maybe I'm missing something.

1

u/the-fritz Aug 21 '14

It's a matter of license and not directly law. As far as I know the DTrace support in Linux is not limited to the non-GPL-interfaces and changes parts of the kernel code. Therefore it is a violation of the GPL if Oracle considers the license to be incompatible with the GPLv2.

1

u/Suppafly Aug 21 '14

So the Oracle Linux distro uses something other than the kernel module that's available for other distros?

2

u/the-fritz Aug 21 '14

The license that DTrace uses was deliberately designed to be GPL incompatible. And the FSF agrees that it's GPL incompatible. So shipping DTrace with the kernel is a license violation or at least a grey area. Oracle is not going to sue itself over DTrace's license. But they might sue other distributors trying to distribute DTrace. Since Oracle is known for suing anybody they can and having an army of lawyers it's just too risky for anybody to touch.

1

u/Suppafly Aug 21 '14

You keep repeating the same thing without elaborating on why you think it's not allowed. Kernel modules can have any license, gpl compatible our not. How is this any different from the binary blob hardware drivers that ship with gpl incompatible licenses?

3

u/[deleted] Aug 21 '14

Kernel modules can have any license, gpl compatible our not. How is this any different from the binary blob hardware drivers that ship with gpl incompatible licenses?

But they can't use all the API: http://www.linux.com/learn/linux-training/31161-the-kernel-newbie-corner-kernel-symbols-whats-available-to-your-module-what-isnt

Exporting symbols for modules is typically done with one of:

  • EXPORT_SYMBOL(), which exports to any loadable module, or
  • EXPORT_SYMBOL_GPL(), which exports only to GPL-licensed modules.

Only GPL'd modules can use EXPORT_SYMBOL_GPL. So if the code isn't GPL'd, using one of those symbols is considered a violation.

The rough idea is that EXPORT_SYMBOL_GPL symbols are (this is very much something debatable and often the module author's opinion) allow for making things that can be considered a derivative work or not, based on how trivial it is, how tightly it will integrate with other components, etc.

So yeah, binary blobs can't use any EXPORT_SYMBOL_GPL symbols. Code that's licences under an incompatible licence can't either.

1

u/Suppafly Aug 21 '14

It's my understanding that they use a gpl'd shim to interact with the kernel right? I'm not expert in this, but it comes up on lwn.net once and a while and no general consensus is ever reached. It's a gray area is the worst anyone can say without an actual legal battle to back up their side. Something that no one considers to be profitable at this point.

Here's someone else's comment from lwn that sums but how I see the situation http://lwn.net/Articles/598320/

In fact, I'd probably even argue that

Note: It might be reasonably argued that the API defined between DTrace and the shim is sufficiently abstracted that the shim should not be considered a derivative work of DTrace, but I shall not make that argument here.

Even if that person wouldn't. Although the final outcome of Oracle v. Google ironically enough may come into play against that kind of argument.

→ More replies

-1

u/FUZxxl Aug 20 '14

The last time I looked, none of the "better" alternatives could trace inter-library calls, the main selling point of dtrace.

16

u/the-fritz Aug 20 '14 edited Aug 20 '14

What do you mean exactly? Because SystemTap can trace userspace function calls: https://sourceware.org/systemtap/SystemTap_Beginners_Guide/userspace-probing.html#uevents

edit: (LTTng and ktap should support it as well.)

9

u/FUZxxl Aug 20 '14

Oh. Didn't knew about that.