From: Edward Ned Harvey <kernel@nedharvey.com>
To: "'ivo welch'" <ivowel@gmail.com>, <linux-btrfs@vger.kernel.org>
Subject: RE: licenses (for apple OSX and others)?
Date: Sun, 14 Aug 2011 22:00:37 -0400 [thread overview]
Message-ID: <003201cc5aef$23baccb0$6b306610$@nedharvey.com> (raw)
In-Reply-To: <CAPr7RtVfNtNno=7KTJvyvNFnkumHd3PiJSo8eoswBZT-0vwFQA@mail.gmail.com>
> From: linux-btrfs-owner@vger.kernel.org [mailto:linux-btrfs-
> owner@vger.kernel.org] On Behalf Of ivo welch
>
> curiosity question---could btrfs be licensed in multiple ways to allow
> Apple and other vendors to adopt it?
No. The source code is copyrighted by many different entities, and the only
way to release it under any other license would require all of the
contributors to mutually agree. It'll never happen. Likewise, perhaps
Apple could release their code under a license that's compatible with GPL,
but I seriously doubt that would ever happen.
> as end users, having one good
> file system that works everywhere as a main root system would be
> heaven...
Agreed. But the various producers of filesystems are generally commercial
entities interested in making a profit. For various reasons, many of them
intentionally don't go this direction. They're all trying to differentiate
themselves.
Generally speaking, the problem is the requirement to integrate some other
FS into a kernel or other component that requires license compatibility for
booting. Generally speaking you can circumvent this problem by using things
like Fuse to mount a filesystem in user space, thus not requiring it to be
built into the kernel, thus eliminating any license compatibility problems.
next prev parent reply other threads:[~2011-08-15 2:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-15 0:34 licenses (for apple OSX and others)? ivo welch
2011-08-15 2:00 ` Edward Ned Harvey [this message]
2011-08-15 2:27 ` ivo welch
2011-08-15 2:53 ` Billy Crook
2011-08-15 5:54 ` C Anthony Risinger
2011-08-15 7:40 ` Roman Mamedov
2011-08-15 15:15 ` Chris Mason
2011-08-15 17:39 ` Billy Crook
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='003201cc5aef$23baccb0$6b306610$@nedharvey.com' \
--to=kernel@nedharvey.com \
--cc=ivowel@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.