Linked by Thom Holwerda on Wed 30th Apr 2008 12:55 UTC, submitted by diegocg
Linux The (unstable and development-oriented only) filesystem Btrfs version 0.14 has been released. "Btrfs is a new copy on write filesystem for Linux aimed at implementing advanced features while focusing on fault tolerance, repair and easy administration. Initially developed by Oracle, Btrfs is licensed under the GPL and open for contribution from anyone."
Thread beginning with comment 312154
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: excited
by Wes Felter on Wed 30th Apr 2008 16:31 UTC in reply to "RE: excited"
Wes Felter
Member since:
2005-11-15

Licensing is political. NIH is also a political issue.

Reply Parent Bookmark Score: 3

RE[3]: excited
by Kakihara on Wed 30th Apr 2008 16:34 in reply to "RE[2]: excited"
Kakihara Member since:
2007-06-09

But the problem is that GPL is too restrictive. Thus ZFS couldn't be included in Linux kernel and Btrfs(also GPL) won't be easily included in other operating systems. If I understand correctly...

Reply Parent Bookmark Score: 1

RE[4]: excited
by Luminair on Wed 30th Apr 2008 22:23 in reply to "RE[3]: excited"
Luminair Member since:
2007-03-30

sun could make zfs gpl. there was talk about it as a trade for linux kernel drivers.

but they chose not to because they are launching new products that use it, and it is a big differentiating feature between them and linux.

Reply Parent Bookmark Score: 2

RE[4]: excited
by sbergman27 on Wed 30th Apr 2008 22:48 in reply to "RE[3]: excited"
sbergman27 Member since:
2005-07-24

Thus ZFS couldn't be included in Linux kernel and Btrfs(also GPL) won't be easily included in other operating systems.

That's life. Seriously. Choices have consequences, and some of them are beneficial and some of them are not. It is unlikely that ZFS will see inclusion in the Linux kernel, and it is unlikely that btrfs will see inclusion in the *Solaris kernel. (Should that be plural or not?) Sometimes those kinds of barriers are significant, and sometimes they are not. I am not convinced that the sharing of filesystem code has much benefit over cross-pollenation of *ideas* in this particular case, for reasons which I have outlined elsewhere in this thread.

I find that discussions on licensing often end up doing nothing more than generating bad blood and resentment between the various parties, without yielding any meaningful benefits.

Reply Parent Bookmark Score: 2

RE[3]: excited
by sbergman27 on Wed 30th Apr 2008 16:43 in reply to "RE[2]: excited"
sbergman27 Member since:
2005-07-24

NIH is also a political issue.

An impedance mismatch between the ZFS architecture and Linux kernel architecture is *not* political, however. Sun's goals for ZFS, apparently, are for it the be the Solaris filesystem. And there is absolutely nothing wrong with that. That strategy has its strengths. And in that case, putting the layering of logical levels into ZFS itself makes perfect sense. However, supporting a broad range of filesystems is a strategy which also has its strengths, and that is what Linux does. In that case, having all the layering of raid, volume manager, fs, etc. in ZFS itself makes no sense at all.

No NIH is required to see that ZFS, while a good fit for Solaris, is a poor fit for Linux.

As to licensing... that does have a political aspect. But the problem is primarily a practical one from the Linux kernel devs standpoint. Although an argument could be made that Sun's choice of license might have been motivated by political (or perhaps "strategic" would be a better word) factors.

Edited 2008-04-30 16:44 UTC

Reply Parent Bookmark Score: 5

RE[4]: excited
by Wes Felter on Wed 30th Apr 2008 17:38 in reply to "RE[3]: excited"
Wes Felter Member since:
2005-11-15

I don't think that argument holds, since Btrfs is busy copying all the "layer violation" features from ZFS such as RAID.

Reply Parent Bookmark Score: 7