If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
If you're using Linux, chances are that you're running software with practically every license on that page. So what's the problem? "If it's not GPL, it's not relevant" we've had the argument often enough that I won't repeat it in all its glory, but the simple version goes like this:
Linux can, and does, use BSD licensed software in its kernel.
Is there a rewrite under GPL planned ? If it is not going to GPL, it does not matter.
The original copyright belongs to Oracle now, they are definitely not going to change it, and if by some miracle they did I'd hope they would be smart enough to use a license that the current users of ZFS can actually tolerate, like the BSD2.
What is the status of the various ZFS pool versions? Is there only a split now between Oracle Solaris and the rest of the open implementations (FreeBSD, Linux, Illumos, etc.)? Or are all the open implementations fragmented as well?
It is split between Oracle and the rest of the world. After backwards incompatible things were added starting to be added to the open source zfs v28, it was decided to adopt an approach that would ensure ZFS would remain compatible between the different distributions, like FreeBSD, IllumOS and ZOL. The version number was changed to v5000 (to ensure there would never be confusion with Oracle and the v34 etc) and instead would adopt 'feature flags', a set of flags stored in the metadata that describe what features the zpool supports (like asynchronous destruction (read-only compatible) and lz4 compression). These flags also contain a marker that describes if they are 'read-only compatible'. For example, if the async_destroy feature is enabled on a pool and you are using an older version of ZFS that does not understand that feature, it is possible to mount the zpool read-only and still read the data. However lz4 is obviously not read-only compatible, you cannot read the files if you cannot decompress them.
This is one of the main goals of the OpenZFS project, to ensure that the various open source implementations remain compatible. The ultimate goal is to reduce the code differences between the various implementations to ensure updates are easily shared between the various vendors.