Common Development and Distribution License - Wikipedia

The Unix Way Episode 17. DTrace was designed at Sun in 2003 by Bryan Cantrill, Mike Shapiro and Adam Leventhal, shipped in Solaris 10 in January 2005, ported to FreeBSD by John Birrell and landed in 7.1-RELEASE on 6 January 2009; the script language was deliberately Turing-incomplete so the compiler could prove safety before loading. Linux could not adopt DTrace upstream because the GPL absorbs every licence it touches; the CDDL accepts coexistence, the GPL does not. The rebuild started from a substrate that had existed since 1992: McCanne and Jacobson's Berkeley Packet Filter. Alexei Starovoitov and Daniel Borkmann generalised it into eBPF, merged in Linux 3.18 on 7 December 2014; BCC arrived in 2015; Brendan Gregg announced bpftrace as DTrace 2.0 for Linux in October 2018, fifteen years after the original. The shape was always the same; the journey was a great deal longer.

Torvalds doesn't want to be hounded by Oracle's legal team for merging ZFS filesystem code into the Linux kernel.

If brtfs interested you, start your next-gen trip with a step-by-step guide to ZFS. Read the whole story

The personal website of Jack Neely

Stratis is a new local storage-management solution for Linux. It can be compared to ZFS, Btrfs [...]

I have a Server in my living room that runs Arch Linux. I originally set up this server to provide a NAS. The NAS serves as a backup solution for the clients in my network, and also stores my media collection. When I initially set it up, I had just one (Desktop!) HDD: A Seagate Barracuda with 8TB of storage. For the filesystem, I chose Btrfs at the time because I heard some good things about it, and looking through the features it seemed to do what I wanted. But the longer I used it, the more problems creeped up. It doesn’t have native filesystem encryption, so I had to use LUKS. It supports Quotas, but doesn’t have a good way of displaying how much storage a specific subvolume/snapshot actually uses. It supports snapshots, but not too many of them. I also thought that subvolumes were very neat, so I created a lot of them to give each “application” a unique path that I tried to cram into the FHS-Philosophy. This caused more trouble than it solved though, because now I had a lot of different paths that I had to write down. I also made a bash script to mount all of these different subvolumes, and had to frequently look inside this script to keep all of the paths and subvolumes together. And with every Service I added, I needed to update this mounting script. This wasn’t really hard or complicated, but very annoying.

The Free Software Foundation has decided they'd rather hang out with a sex pest than have an ounce of credibility, so fuck em. Let's look at the copyleft licenses they didn't write and see how they're used.