Date: Wed, 20 Feb 2019 10:32:45 -0800 From: Enji Cooper <yaneurabeya@gmail.com> To: rgrimes@freebsd.org Cc: Alexey Dokuchaev <danfe@freebsd.org>, Shawn Webb <shawn.webb@hardenedbsd.org>, Pawel Jakub Dawidek <pjd@freebsd.org>, svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org Subject: Re: svn commit: r344316 - head/sys/cddl/contrib/opensolaris/uts/common/fs/zfs Message-ID: <2E31FED5-0E0B-4624-AF11-2178C7E84308@gmail.com> In-Reply-To: <201902201711.x1KHBeiQ016158@pdx.rh.CN85.dnsmgr.net> References: <201902201711.x1KHBeiQ016158@pdx.rh.CN85.dnsmgr.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Feb 20, 2019, at 09:11, Rodney W. Grimes <freebsd@pdx.rh.cn85.dnsmgr.net>= wrote: > One can personally link ZoL into your own kernel, and a company/corporate > can even do this and run it on 1000's of servers, you just can not > distribute it to anyone else, which in the end is not really a big > deal, unless your in the Linux distribution business. Very little organizations roll their own Linux kernels in the grand scheme o= f things (run of the mill sysadmins aren=E2=80=99t hackers), and making Linu= x VFS work with ZFS is a nontrivial job (ZoL might work with a kernel versio= n, but it won=E2=80=99t work with all target kernel versions). Groups like Fa= cebook, Google, Oracle, etc, do it because they have the developer manpower a= nd it=E2=80=99s in their vested interest to run a custom kernel config/kerne= l with backports/enhancements. Plus, they don=E2=80=99t need to release thei= r changes, as their server platforms won=E2=80=99t be productized (thus skat= ing around the GPLv2). I couldn=E2=80=99t find gregkh@=E2=80=98s diatribe about Linux kernel compat= ibility, but it was basically (put nicely), =E2=80=9Cput your code in the ke= rnel tree, cause we won=E2=80=99t necessarily provide backwards compatibilit= y, as we need to break interfaces from time to time.=E2=80=9D Given that zfs is licensed under the CDDL (a viral license to Linux), that c= ode will never, ever, hit the mainline tree. This is one of the code reasons why, over time, btrfs has evolved into the f= ile system that it is: it fills a niche that ext4 couldn=E2=80=99t and zfs d= id, while being licensed under an acceptable kernel license (GPLv2). -Enji=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2E31FED5-0E0B-4624-AF11-2178C7E84308>