3 ms·
Exactly. ZFS was deliberately released with a license designed to keep it out of the kernel. It's unavailable to the Linux community, so people use what they
by ajross 14y ago
Exactly. ZFS was deliberately released with a license designed to keep it out of the kernel. It's unavailable to the Linux community, so people use what they have and work on replacements. The controversy isn't technical, it's legal. And it's not resolvable by feature lists and fanboi flaming.
ZFS is great, I'm sure. But btrfs is great too and rapidly improving. I don't think the Linux world has much to worry about.
- petsos 14y ago> Exactly. ZFS was deliberately released with a license designed to keep it out of the kernel. Right, it's a big conspiracy.
- ajross 14y agoNo, this is mostly inarguable, and multiple Sun employees attested to it at the time (I remember a bunch of discussions on freenode specifically, but I'm sure someone can find a web link for a better cite). The fear with the Open Solaris release among the executives was that any code released would instantly be imported into Linux and destroy the perceived competetive advantage Sun had in the enterprise space. So the CDDL was crafted to be almost entirely identical to the LGPLv2 from a practical perspective (the only major distinction being whether "files" are considered independently for protection vs. the work as a whole) yet still be GPL-incompatible. Obviously this also insulated Solaris from any of the drivers in the Linux tree, so 4.5 years later it still doesn't run on anything but custom designed hardware and a handful of vanilla x86 server configurations. The CDDL was a great harm to the broader community. Like I said I don't see that there's much argument to be made there. (edit rather than response to avoid prolonging a discussion: obviously Bryan was there and I wasn't, but it should be pointed out that not everyone who was there agrees with that take, nor are our points exclusive. The wikipedia page on the CDDL has a reference ([6]) which jives with my understanding at the time: http://en.wikipedia.org/wiki/Common_Development_and_Distribution_License http://en.wikipedia.org/wiki/Common_Development_and_Distribu... )
- bcantrill 14y agoIt's frustrating that this idea persists. Yes, the GPL was explicitly rejected, but no, it wasn't because of fear of Linux compatibility. It is true that we refused to dual-license (we didn't want to create a license-based fork), but the reason the GPLv2 was rejected is actually very simple: the strong copy-left left way too much ambiguity for our IHV partners. In particular, we wanted to allow proprietary, closed-source drivers to be shipped for OpenSolaris without a Linux-esque "taint" of the system. We also wanted distros to be created that had entirely proprietary components -- including the binaries that constituted elements of the system that we could not ourselves open source due to third party restrictions. So yes, we rejected GPLv2 -- but it was not because we were afraid of becoming an organ donor to Linux, but rather because it would have overly restricted the freedoms of our community. In this regard, we were forward looking: it is now broadly accepted that the GPLv2 is an anti-collaborative license[1], explaining its acute decline for new work. [1] http://dtrace.org/blogs/bmc/2012/08/01/post-revolutionary-open-source/ http://dtrace.org/blogs/bmc/2012/08/01/post-revolutionary-op...
- jsight 14y agoIf those were the concerns, it could have been dual licensed.
- rbanffy 14y agoOr used an Apache-style license.
- stock_toaster 14y agoDo you recall why other popular licenses at the time (apache-2.0, MIT, BSD(new), etc) were rejected?
- tedunangst 14y agoNone of those are copyleft.
- nodata 14y ago> Right, it's a big conspiracy. It's not a conspiracy, it was deliberately released with a license designed to keep it out of the Linux kernel.