News for hackers. Stuff that matters.
Re:An extensive ZFS setup on MacOS by jedberg on Saturday July 07, 2018 @12:37PM (#17479244)
ZFS was supposed to be the default file system on Mac OS X 10.5 (Leopard). I know this because I talked to some engineers at Apple, but the external evidence is that Time Machine clearly was built as a ZFS snapshot explorer and manager.

Sadly, they had to drop the whole thing because of the murky licensing on ZFS.

I sometimes dream of a world with a ZFS root partition on my MacBook Pro...

Re:An extensive ZFS setup on MacOS by omnibrain on Saturday July 07, 2018 @04:23PM (#17480367)
Seeing it was SUN who announced that ZFS was going to be OSX‘s default file system, I think that is more likely Apple/Steve himself changed plans in a fit of rage over this premature announcement.
Re:An extensive ZFS setup on MacOS by ascom on Saturday July 07, 2018 @01:50PM (#17479573)
https://openzfsonosx.org/wiki/ZFS_on_Boot

Not quite "it just works," but it's an option...

Re:An extensive ZFS setup on MacOS by cookiecaper on Saturday July 07, 2018 @04:33PM (#17480419)
Adam Leventhal doesn't seem to put much stock in the licensing theory, considering OS X's inclusion of DTrace, which was released under the same license. His discussion of the saga of ZFS on OS X is here: http://dtrace.org/blogs/ahl/2016/06/15/apple_and_zfs/ . Very interesting stuff.
Re:An extensive ZFS setup on MacOS by jedberg on Saturday July 07, 2018 @05:28PM (#17480701)
Right from that very article:

> When Apple included DTrace in Mac OS X a point in favor was that it could be yanked out should any sort of legal issue arise. Once user data hit ZFS it would take years to fully reverse the decision.

Re:An extensive ZFS setup on MacOS by cookiecaper on Saturday July 07, 2018 @09:20PM (#17481657)
Right, Leventhal mentions that such an eventuality was one in a group of several considerations, but clearly does not think it was the primary factor.

From the paragraph following your quote:

> Finally and perhaps most significantly, personal egos and NIH (not invented here) syndrome certainly played a part. [...] [C]ertain leads and managers preferred to build their own rather adopting external technology—even technology that was best of breed. They pitched their own project, an Apple project, that would bring modern filesystem technologies to Mac OS X.

and

> Licensing FUD was thrown into the mix; even today folks at Apple see the ZFS license as nefarious and toxic in some way whereas the DTrace license works just fine for them. Note that both use the same license with the same grants and same restrictions.

Leventhal's chronology continues to suggest that ZFS on OS X re-emerged even after this licensing argument had been advanced, and that the project was finally killed by Larry Ellison himself, in the interest of keeping his personal friendship with Steve Jobs unaffected by business considerations.

While it is of course possible that Apple is willing to accept any "murkiness" around the license as it pertains to DTrace but not willing to do so as it pertains to ZFS, it just doesn't seem like your original statement that "they had to drop the whole thing because of the murky licensing on ZFS" represents the situation clearly (at least not if we accept the version of events as told by Adam Leventhal; personally, I have no direct knowledge).

Re:An extensive ZFS setup on MacOS by hb3b on Saturday July 07, 2018 @02:52PM (#17479877)
This was one of Sun's last middle fingers to the FOSS community. They knew by licensing ZFS under the CDDL there was no way Linux users, specifically RHEL customers could benefit from it. Hopefully Apple won't follow suit with APFS.
Re:An extensive ZFS setup on MacOS by hultner on Saturday July 07, 2018 @04:33PM (#17480412)
This is a common misconception but in fact the incompatibility is purely accidental, in addition I wouldn’t call GNU/GPL the most pragmatic license family either.
Re:An extensive ZFS setup on MacOS by yjftsjthsd-h on Saturday July 07, 2018 @05:14PM (#17480618)
If it was an accident, then why does the CDDL even exist? What does it offer that MIT/BSD don't have, other than being incompatible with GPL?
Re:An extensive ZFS setup on MacOS by AndrewSnow on Saturday July 07, 2018 @06:33PM (#17481043)
Like Mozilla, per-file copyleft and clearer patent licensing, IIRC.

Some prominent former Sun folks have publicly claimed the GPL incompatibility was intentional, other equally prominent folks have disagreed.

Re:An extensive ZFS setup on MacOS by hultner on Saturday July 07, 2018 @05:19PM (#17480645)
This argument could be made for any license that’s similar to another, I don’t think it’s fair reasoning. Why does 2-Clause BSD exist? Why does Apache license exist?
Re:An extensive ZFS setup on MacOS by yjftsjthsd-h on Saturday July 07, 2018 @05:42PM (#17480768)
That's a good point, though honestly I never could understand why you would use anything but Apache (for permissive) or (A)GPL (for copyleft). Other options seem like oversights (BSD/MIT don't cover patents) or cutting off your nose to spite your face (WTFPL). I'm sure there's nuance, but I can't seem to see it.
Re:An extensive ZFS setup on MacOS by nine_k on Saturday July 07, 2018 @07:15PM (#17481209)
MIT license and BSD license seem to long predate Apache.

GPL and AGPL differ vastly in a few important aspects that make GPL pretty OK for commercial companies, and AGPL an absolute no-no.

Re:An extensive ZFS setup on MacOS by riobard on Saturday July 07, 2018 @02:18PM (#17479708)
Is there any hope that Time Machine might get reworked with APFS?
Re:An extensive ZFS setup on MacOS by dwaite on Saturday July 07, 2018 @02:47PM (#17479846)
portions of time machine already have been (local backup uses snapshots, and is ridiculously simpler as a result).

Proper Time Machine "v2" is a bit more complex (basically a rsync clone based on local and remote snapshots), but still way simpler than the current "v1" method, which builds its own change table from fsevents and has to cope with a lack of snapshots in HFS+.

They can't use APFS as a Time Machine "v1" store because the unique feature of HFS+ to support directory hard-links did not carry over to APFS. Migration of a v1 to v2 volume would be a fun exercise in translations (folder hierarchy collapsed to volume snapshots, and differing crypto approaches for encrypted backups).

I suspect they are trying to get APFS in an evolutionary "stable" place so they can publicly document it with the iOS 12/macOS Mojave/etc releases - the changes they are making to support HDDs and Fusion drives this year are likely a big internal evolution.

I also suspect Apple is just not in a rush to move time machine over - it already works, has a surprising amount of integration across the OS for backup/recovery, and people tend to value their backups working vs using the newest technology.

Eventually, my belief is they will roll out Time Machine v2 and leave v1 (on HFS+) only supported for restoration. Just like with v1 today, non-APFS volumes will get a sparse bundle disk image to hold the APFS data. But they will wait until they have a strategy to migrate the external volumes and disk images.

Re:An extensive ZFS setup on MacOS by cmurf on Saturday July 07, 2018 @05:25PM (#17480673)
There is definitely hope, it could turn out to be empty hope but... APFS has a lot to offer Time Machine as the hackery needed to get it to work on JHFS+/HFSX is tomfoolery at this point. At the least APFS has metadata checksums, and adding on an optional csum tree for data is not difficult for Apple to do. They already do COW with APFS so all that's needed is a separate tree for data csums. And then they have snapshots instead of hardlinks; or reflinks instead of hardlinks. I think it'll happen eventually as the deadweight of supporting HFS+ catches up with them.