Skip to contentSkip to conversation

ZFS with Linux: An Open Plea

DISCUSSION David R. Litwin 20 participants 37 messages Apr 17, 2007 – Apr 18, 2007

lore
Share & tools
lore
#0 lore raw

On 15/04/07, Jesper Juhl <[email protected]> wrote:

Quoted 5 lines · David R. Litwin

Before I go on, let me appologise. I don't really know what I hope to accomplish, beyond trying to garner thoughts (and support?) for the topic.

Essentially: I want to use Linux and ZFS. I don't particularly care about licences or any of the rest of that nonsense.

The license that protects the code we write is far from nonsense.

I know. In the end, this is the reason this topic is being discussed.

I suggest the first thing you do is contact the ZFS developers and convince them to release their code under a license that's GPL compatible, then we can start looking at a Linux port.

I began by contacting them. One of the devs there told me to contact the Linux devs.

Quoted 2 lines

FUSE is nice for trying out new and interresting ideas in userspace - it has its uses.

Yes, but it is not really for the end-user. To paraphrase another, it is mostly academic.

Quoted 3 lines

What are the thoughts of the Linux community?

Can't tell you that, all I can tell you is my own oppinion.

You make up a member of the Linux community.

Quoted 3 lines

I believe
ZFS for Linux would be interresting, if not for any other reason then for compatibility.

For the greater glory of Linux? :-)

Quoted 2 lines

I'd personally like to see it - but, settle the
license issue first.

And we've come full circle: The liconsinc issue.

--
Jesper Juhl <[email protected]>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html

--
—A watched bread-crumb never boils.
—My hover-craft is full of eels.
—[...]and that's the he and the she of it.

#1 lore raw
Quoted 5 lines
Quoted 2 lines

FUSE is nice for trying out new and interresting ideas in userspace - it has its uses.

Yes, but it is not really for the end-user. To paraphrase another, it is mostly academic.

Oh? I thought those ~10,000 downloads of SSHFS and ~200,000 downloads of NTFS-3G were end users.(*)

Maybe I was wrong though. Thanks for the clarification.

Miklos

(*) Numbers obviously don't include packaged installations

#2 lore raw
In reply to David R. Litwin
Quoted 10 lines · David R. Litwin
Quoted 1 line

The license that protects the code we write is far from nonsense.

I know. In the end, this is the reason this topic is being discussed.

I suggest the first thing you do is contact the ZFS developers and convince them to release their code under a license that's GPL compatible, then we can start looking at a Linux port.

I began by contacting them. One of the devs there told me to contact the Linux devs.

Well, that was totally useless answer from the ZFS developers. What he should have told you is to contact Sun management, since they are the only ones who can decide whether or not to release ZFS under a GPL license, and more importantly, to give a patent license for any patents they may have filed in the course of developing ZFS. This is not anything Linux developers can help you with.

- Ted

#3 lore raw

On Tue, 17 Apr 2007, Theodore Tso wrote:
[..]

Quoted 6 lines

Well, that was totally useless answer from the ZFS developers. What he should have told you is to contact Sun management, since they are the only ones who can decide whether or not to release ZFS under a GPL license, and more importantly, to give a patent license for any patents they may have filed in the course of developing ZFS. This is not anything Linux developers can help you with.

Realy can't or don't want (?)
So who is responsible for potential changing Linux code licensing for allow if not incorporate CDDL code correct interraction without breaking some law ?
And/or what Linux can loose on follow this king changes ?
And/or why Linux code licensing can't evolve ? Seems when Linux code was licensed noone was thinking about case like interraction with code under license like CDDL so why now it can be corrected and still many people try to think like "anything arond Linux must evolve .. but not Linux" (?) Why this can't be fixes ?

If in this ponit in Linux "evniroment" can't be chaged .. sorry but is it not kind of hipocritics ?

kloczek

Signature · 4 lines
-----------------------------------------------------------
*Ludzie nie mają problemów, tylko sobie sami je stwarzają*
-----------------------------------------------------------
Tomasz Kłoczko, sys adm @zie.pg.gda.pl|*e-mail: [email protected]*
#4 lore raw
Quoted 4 lines · Tomasz Kłoczko

Realy can't or don't want (?)
So who is responsible for potential changing Linux code licensing for allow if not incorporate CDDL code correct interraction without breaking some law ?

Everyone who holds any copyright over any of the code in Linux, which is several thousand people. You'd probably need permission from all of them. Good luck!

Signature · 1 line
Matthew Garrett | [email protected]
#5 lore raw
Quoted 9 lines · Matthew Garrett
Quoted 4 lines · Tomasz Kłoczko

Realy can't or don't want (?)
So who is responsible for potential changing Linux code licensing for allow if not incorporate CDDL code correct interraction without breaking some law ?

Everyone who holds any copyright over any of the code in Linux, which is several thousand people. You'd probably need permission from all of them. Good luck!

Why on discussion about switching to GPL v3 Linux code this argument was allways taken as "piece of cake". Why in case switching to another license which will allow use CDDL code just it is most importand contr argument ?

kloczek

Signature · 4 lines
-----------------------------------------------------------
*Ludzie nie mają problemów, tylko sobie sami je stwarzają*
-----------------------------------------------------------
Tomasz Kłoczko, sys adm @zie.pg.gda.pl|*e-mail: [email protected]*
#6 lore raw
Quoted 2 lines

Why on discussion about switching to GPL v3 Linux code this argument was allways taken as "piece of cake". Why in case switching to another license

What planet do you come from I wonder ?

On Earth (where most of us usually reside) the consensus of the kernel developers and the legal people they talked to was that GPLv2 to GPLv3 would be very very hard to do if not impossible for the kernel.

Alan

#7 lore raw
In reply to Tomasz Kłoczko
Quoted 11 lines · On Tuesday 17 April 2007 11:46:38 Tomasz Kłoczko wrote:
Quoted 9 lines · Matthew Garrett
Quoted 4 lines · Tomasz Kłoczko

Realy can't or don't want (?)
So who is responsible for potential changing Linux code licensing for allow if not incorporate CDDL code correct interraction without breaking some law ?

Everyone who holds any copyright over any of the code in Linux, which is several thousand people. You'd probably need permission from all of them. Good luck!

Quoted 5 lines

Why on discussion about switching to GPL v3 Linux code this argument was allways taken as "piece of cake". Why in case switching to another license which will allow use CDDL code just it is most importand contr argument ?

kloczek

Because *EVERY* version of the GPL contains the "or any later version of this license" clause (except, now, the version being used with the Linux kernel)

DRH

#8 lore raw

On Tue, 17 Apr 2007, Daniel Hazelton wrote:
[..]

Quoted 8 lines
Quoted 5 lines

Why on discussion about switching to GPL v3 Linux code this argument was allways taken as "piece of cake". Why in case switching to another license which will allow use CDDL code just it is most importand contr argument ?

kloczek

Because *EVERY* version of the GPL contains the "or any later version of this license" clause (except, now, the version being used with the Linux kernel)

So after around commented swiching to GPL v3 it will be possible to start work on GLP v3.5 which will allow easy reuse CDDL code under Linux .. good to know :o)
How many years it will take ? two, three ? more ? (it will be good to know how long we must wait on ZFS under Linux .. I don't belive in rewriting ZFS code time and make it so useable on production as *now* it is possible under Solaris/*BSD/MOX and passing all pointless arguing will take shorter time) .. or maybe never because some people says something like "Linux is in GPL cage".

Hmm .. transforming KProbes/systemtap to someting useable as DTrace was started more than two years ago and I don't see end of base work (sill on start). Make ALSA so useable as OSS it was next three trashed years (because some developers stays on position "mixing audio in kernel space is dangerous") and also not finished in many points. LVM still isnt't Veritas. I don't see OpenVZ to tries be so useable and easy for managa as Solaris zoning (why OpenVZ people can't use the same commands syntax for manage zones as under Solaris .. command syntax is not patented :). Also .. moment .. moment .. for what I'm waiting if I can install and use Solaris/*BSD/MOX *NOW* ??? Why still contribute any code to project which seems must die ? (Is is realy true that some beeings which can't evolve in changeing enviroment will not survive .. ?)

EOT .. sorry

kloczek

Signature · 4 lines
-----------------------------------------------------------
*Ludzie nie mają problemów, tylko sobie sami je stwarzają*
-----------------------------------------------------------
Tomasz Kłoczko, sys adm @zie.pg.gda.pl|*e-mail: [email protected]*
#9 lore raw
Quoted 10 lines · On Tuesday 17 April 2007 15:58:09 Tomasz Kłoczko wrote:

On Tue, 17 Apr 2007, Daniel Hazelton wrote:
[..]

Quoted 7 lines
Quoted 6 lines

Why on discussion about switching to GPL v3 Linux code this argument was allways taken as "piece of cake". Why in case switching to another license which will allow use CDDL code just it is most importand contr argument ?

kloczek

Quoted 7 lines
Quoted 3 lines

Because *EVERY* version of the GPL contains the "or any later version of this license" clause (except, now, the version being used with the Linux kernel)

So after around commented swiching to GPL v3 it will be possible to start work on GLP v3.5 which will allow easy reuse CDDL code under Linux .. good to know :o)

Nope. Note that I said "Except the Linux Kernel".

After the discussions that took place back around the time of the release of the first draft of GPLv3 it was decided to lock Linux to *ONLY* GPLv2

So the Linux kernel will *never* be able to have a version of the GPL other than the current one applied. This change might have occurred without the knowledge or agreement of the FSF, who maintain the GPL, but since it was done with the complete agreement of all the current developers - and assumed agreement of any who contributed and are no longer able to consent (since their code was originally released under GPLv2) - it should stand. After all, the form of the license that applies to the kernel is shipped with the kernels sources.

In fact, from the copy in the latest Git:
NOTE! This copyright does *not* cover user programs that use kernel services by normal system calls - this is merely considered normal use of the kernel, and does *not* fall under the heading of "derived work". Also note that the GPL below is copyrighted by the Free Software Foundation, but the instance of code that it refers to (the Linux kernel) is copyrighted by me and others who actually wrote it.

Also note that the only valid version of the GPL as far as the kernel is concerned is _this_ particular version of the license (ie v2, not v2.2 or v3.x or whatever), unless explicitly otherwise stated.

Linus Torvalds
-----------------

So the Linux kernel, unless things change some years in the future, will never have a license completely compatible with the CDDL. (and the CDDL isn't really a "Free Software" license in the GPL vein because it makes demands such as retention of the header blocks and reserves Sun (or whoever is releasing code under the CDDL) the right to revoke the implicit patent grant the license offers.)

Quoted 6 lines

How many years it will take ? two, three ? more ? (it will be good to know how long we must wait on ZFS under Linux .. I don't belive in rewriting ZFS code time and make it so useable on production as *now* it is possible under Solaris/*BSD/MOX and passing all pointless arguing will take shorter time) .. or maybe never because some people says something like "Linux is in GPL cage".

Linux is not in any cage - Solaris and ZFS, because of the CDDL, sit inside the cage. I, personally, will *NEVER* release code meant to be "open source" under a license that makes demands like those of the user.

DRH

#10 lore raw
Quoted 2 lines

After the discussions that took place back around the time of the release of the first draft of GPLv3 it was decided to lock Linux to *ONLY* GPLv2

This is not accurate. As far back as I can easily check, the kernel's COPYING file has said:

Also note that the only valid version of the GPL as far as the kernel is concerned is _this_ particular version of the license (ie v2, not v2.2 or v3.x or whatever), unless explicitly otherwise stated.

To be really precise, there was a trivial rewording of this sometime around Feb 2002 to make it clearer, but the point is that the kernel has been GPL v2 only long before the GPL v3 process started.

- R.

#11 lore raw
In reply to Daniel Hazelton
Quoted 16 lines · Daniel Hazelton
Quoted 14 lines · On Tuesday 17 April 2007 15:58:09 Tomasz Kłoczko wrote:

On Tue, 17 Apr 2007, Daniel Hazelton wrote:
[..]

Quoted 10 lines
Quoted 6 lines

Why on discussion about switching to GPL v3 Linux code this argument was allways taken as "piece of cake". Why in case switching to another license which will allow use CDDL code just it is most importand contr argument ?

kloczek

Because *EVERY* version of the GPL contains the "or any later version of this license" clause (except, now, the version being used with the Linux kernel)

Quoted 8 lines
Quoted 3 lines

So after around commented swiching to GPL v3 it will be possible to start work on GLP v3.5 which will allow easy reuse CDDL code under Linux .. good to know :o)

Nope. Note that I said "Except the Linux Kernel".

After the discussions that took place back around the time of the release of the first draft of GPLv3 it was decided to lock Linux to *ONLY* GPLv2

actually the GPLv2 only predates the GPLv3 draft by several years

there are quite a few other projects that are also GPLv2 only

Quoted 8 lines

So the Linux kernel will *never* be able to have a version of the GPL other than the current one applied. This change might have occurred without the knowledge or agreement of the FSF, who maintain the GPL, but since it was done with the complete agreement of all the current developers - and assumed agreement of any who contributed and are no longer able to consent (since their code was originally released under GPLv2) - it should stand. After all, the form of the license that applies to the kernel is shipped with the kernels sources.

the 'or later' version is not part of the GPLv2 license itself, it's a burb that the FSF suggests that people use so that they (the FSF) can retroactivly change the license of the code that other people create.

The dispute over the GPLv3 is if these retroactive chagnes aer to the benifit or detriment of the people who created the code.

Quoted 8 lines

In fact, from the copy in the latest Git:
NOTE! This copyright does *not* cover user programs that use kernel services by normal system calls - this is merely considered normal use of the kernel, and does *not* fall under the heading of "derived work". Also note that the GPL below is copyrighted by the Free Software Foundation, but the instance of code that it refers to (the Linux kernel) is copyrighted by me and others who actually wrote it.

Quoted 6 lines

Also note that the only valid version of the GPL as far as the kernel is concerned is _this_ particular version of the license (ie v2, not v2.2 or v3.x or whatever), unless explicitly otherwise stated.

Linus Torvalds
-----------------

take a look at the date that this went into the kernel

Quoted 10 lines
Quoted 6 lines

How many years it will take ? two, three ? more ? (it will be good to know how long we must wait on ZFS under Linux .. I don't belive in rewriting ZFS code time and make it so useable on production as *now* it is possible under Solaris/*BSD/MOX and passing all pointless arguing will take shorter time) .. or maybe never because some people says something like "Linux is in GPL cage".

Linux is not in any cage - Solaris and ZFS, because of the CDDL, sit inside the cage. I, personally, will *NEVER* release code meant to be "open source" under a license that makes demands like those of the user.

and similarly, many people will not release code under a license that lets other people change the terms years later.

David Lang

#12 lore raw
Quoted 53 lines · On Tuesday 17 April 2007 18:12:17 David Lang wrote:
Quoted 15 lines · Daniel Hazelton
Quoted 14 lines · On Tuesday 17 April 2007 15:58:09 Tomasz Kłoczko wrote:

On Tue, 17 Apr 2007, Daniel Hazelton wrote:
[..]

Quoted 10 lines
Quoted 6 lines

Why on discussion about switching to GPL v3 Linux code this argument was allways taken as "piece of cake". Why in case switching to another license which will allow use CDDL code just it is most importand contr argument ?

kloczek

Because *EVERY* version of the GPL contains the "or any later version of this license" clause (except, now, the version being used with the Linux kernel)

Quoted 8 lines
Quoted 3 lines

So after around commented swiching to GPL v3 it will be possible to start work on GLP v3.5 which will allow easy reuse CDDL code under Linux .. good to know :o)

Nope. Note that I said "Except the Linux Kernel".

After the discussions that took place back around the time of the release of the first draft of GPLv3 it was decided to lock Linux to *ONLY* GPLv2

actually the GPLv2 only predates the GPLv3 draft by several years

there are quite a few other projects that are also GPLv2 only

Quoted 8 lines

So the Linux kernel will *never* be able to have a version of the GPL other than the current one applied. This change might have occurred without the knowledge or agreement of the FSF, who maintain the GPL, but since it was done with the complete agreement of all the current developers - and assumed agreement of any who contributed and are no longer able to consent (since their code was originally released under GPLv2) - it should stand. After all, the form of the license that applies to the kernel is shipped with the kernels sources.

the 'or later' version is not part of the GPLv2 license itself, it's a burb that the FSF suggests that people use so that they (the FSF) can retroactivly change the license of the code that other people create.

The dispute over the GPLv3 is if these retroactive chagnes aer to the benifit or detriment of the people who created the code.

Quoted 8 lines

In fact, from the copy in the latest Git:
NOTE! This copyright does *not* cover user programs that use kernel services by normal system calls - this is merely considered normal use of the kernel, and does *not* fall under the heading of "derived work". Also note that the GPL below is copyrighted by the Free Software Foundation, but the instance of code that it refers to (the Linux kernel) is copyrighted by me and others who actually wrote it.

Quoted 8 lines
Quoted 6 lines

Also note that the only valid version of the GPL as far as the kernel is concerned is _this_ particular version of the license (ie v2, not v2.2 or v3.x or whatever), unless explicitly otherwise stated.

Linus Torvalds
-----------------

take a look at the date that this went into the kernel

Yeah, I did afterwards. Perhaps it was because of the discussion that occurred then that I remember it.

Quoted 7 lines
Quoted 7 lines
Quoted 6 lines

How many years it will take ? two, three ? more ? (it will be good to know how long we must wait on ZFS under Linux .. I don't belive in rewriting ZFS code time and make it so useable on production as *now* it is possible under Solaris/*BSD/MOX and passing all pointless arguing will take shorter time) .. or maybe never because some people says something like "Linux is in GPL cage".

Quoted 6 lines
Quoted 3 lines

Linux is not in any cage - Solaris and ZFS, because of the CDDL, sit inside the cage. I, personally, will *NEVER* release code meant to be "open source" under a license that makes demands like those of the user.

and similarly, many people will not release code under a license that lets other people change the terms years later.

Agreed. This is something that I would never do.

DRH

Quoted 2 lines

David Lang

#13 lore raw
In reply to Tomasz Kłoczko
Quoted 9 lines · Tomasz K?oczko

On Tue, 17 Apr 2007, Theodore Tso wrote:
[..]

Quoted 6 lines

Well, that was totally useless answer from the ZFS developers. What he should have told you is to contact Sun management, since they are the only ones who can decide whether or not to release ZFS under a GPL license, and more importantly, to give a patent license for any patents they may have filed in the course of developing ZFS. This is not anything Linux developers can help you with.

Quoted 4 lines

Realy can't or don't want (?)
So who is responsible for potential changing Linux code licensing for allow if not incorporate CDDL code correct interraction without breaking some law ?

All Linux contributors (i.e: copyright owners) are. If you want to change the kernel license, you have all contributors to agree. Like somebody else in this thread already said: some of them can't be reached anymore, some of them are even dead.

For Sun it would be much easier: there might be many contributors to ZFS, but all of them are employed by Sun and hence Sun owns the copyright and has the choice of license.

Quoted 1 line

And/or what Linux can loose on follow this king changes ?

A lot. Like an even playing field for all contributors.

Quoted 4 lines

And/or why Linux code licensing can't evolve ? Seems when Linux code was licensed noone was thinking about case like interraction with code under license like CDDL so why now it can be corrected and still many people try to think like "anything arond Linux must evolve .. but not Linux" (?)

The Linux kernel was licensed under GPLv2 way before Sun even thought about CDDL. You can't blame Linus for choosing a license that was incompatible with to be written future licenses.

Quoted 1 line

Why this can't be fixes ?

Because so far we haven't found a way to ask dead copyright owners to think about relicensing their code. And even if we had, that still doesn't mean they would actually agree with relicensing their code.

Quoted 2 lines

If in this ponit in Linux "evniroment" can't be chaged .. sorry but is it not kind of hipocritics ?

Nothing hypocritical about it, just undoable.

Erik

Signature · 2 lines
They're all fools. Don't worry. Darwin may be slow, but he'll
eventually get them. -- Matthew Lammers in alt.sysadmin.recovery
#14 lore raw
In reply to Tomasz Kłoczko
Quoted 5 lines

And/or why Linux code licensing can't evolve ? Seems when Linux code was licensed noone was thinking about case like interraction with code under license like CDDL so why now it can be corrected and still many people try to think like "anything arond Linux must evolve .. but not Linux" (?) Why this can't be fixes ?

That's not evolution; it's de-evolution. Linux morphing to some sort of mentally-damaged pseudo-proprietary licence would be like switching back to a feudal society where 50 was considered unbelievably ancient.

I'm sure Linus did think very closely about the interaction of his code with proprietary licences. He thought about it, snickered for a few moments, and made the right decision.

#15 lore raw
Quoted 9 lines · John Anthony Kazos Jr.
Quoted 5 lines

And/or why Linux code licensing can't evolve ? Seems when Linux code was licensed noone was thinking about case like interraction with code under license like CDDL so why now it can be corrected and still many people try to think like "anything arond Linux must evolve .. but not Linux" (?) Why this can't be fixes ?

That's not evolution; it's de-evolution. Linux morphing to some sort of mentally-damaged pseudo-proprietary licence would be like switching back to a feudal society where 50 was considered unbelievably ancient.

CDDL is OSI aproved. Did you realy want to say by above something like "CDDL is pseudo-proprietary licence" ? Are you still taking about (and only) CDDL ?

Quoted 3 lines

I'm sure Linus did think very closely about the interaction of his code with proprietary licences. He thought about it, snickered for a few moments, and made the right decision.

I don't want see problmes on border with propretary licenses at all but I see (and still want to talk only about) problem on on some class licenses which provides more oppened (and not closed) code.

kloczek

Signature · 4 lines
-----------------------------------------------------------
*Ludzie nie mają problemów, tylko sobie sami je stwarzają*
-----------------------------------------------------------
Tomasz Kłoczko, sys adm @zie.pg.gda.pl|*e-mail: [email protected]*
#16 lore raw
Quoted 8 lines
Quoted 3 lines

That's not evolution; it's de-evolution. Linux morphing to some sort of mentally-damaged pseudo-proprietary licence would be like switching back to a feudal society where 50 was considered unbelievably ancient.

CDDL is OSI aproved. Did you realy want to say by above something like "CDDL is pseudo-proprietary licence" ? Are you still taking about (and only) CDDL ?

From what I have read, CDDL is treading the veeeerrrrrry thin line between

an actual Free license and an actual proprietary licence. Just look at the nonsense Mozilla Co. has gotten itself worked up about (and judging by how much Firefox/Iceweasel crashes on me, being like IE is quite appropriate in licencing too). And (if I have not been misinformed), CDDL is inspired by Mozilla's licence.

The FSF has something to say.
http://www.gnu.org/licenses/license-list.html#SoftwareLicenses
So yes, CDDL is, to me, "pseudo-"proprietary, and it would be very easy for them to slip up and whoops! Didn't we tell you? You can do everything but -that-. But of course it's still free...yeah...

Quoted 7 lines
Quoted 3 lines

I'm sure Linus did think very closely about the interaction of his code with proprietary licences. He thought about it, snickered for a few moments, and made the right decision.

I don't want see problmes on border with propretary licenses at all but I see (and still want to talk only about) problem on on some class licenses which provides more oppened (and not closed) code.

The GPL is more about protection than openness. Someone can write code, throw it on the internet with no licence at all, and it's exactly as "open" as it is under the GPL. You can do anything you want with it in any way, just like under the GPL. What the GPL does is protect the code and its writer from being snapped up by somebody else, and in any way
restricted: It makes sure the code STAYS open, and makes sure you are always free to do as you like with it.

#17 lore raw
In reply to Tomasz Kłoczko
Quoted 1 line · Tomasz Kłoczko

Realy can't or don't want (?)

Relicensing the whole kernel under the CDDL just to be able to get ZFS is not going to happen (I bet that rewriting ZFS is easier than relicensing a large piece of software with thousand of different copyrigth owners ;)

Either Sun relicenses Solaris under a GPL-compatible license (which may happen, as Sun's CEO has said they may relicense it under the GPL3), or Linux won't get ZFS except using the FUSE backend. If you miss ZFS, you always can use solaris.

#18 lore raw
In reply to Tomasz Kłoczko
Quoted 3 lines

So who is responsible for potential changing Linux code licensing for allow if not incorporate CDDL code correct interraction without breaking some law ?

Every single contributor, individually. Which won't happen.

The real test of whether Sun were serious about ZFS being anywhere but Solaris is what they do to license it - they've patented everything they can, and made the code available only under licenses incompatible with other OS products. Their intent is quite clear, and quite sad.

Compare it to what the old Sun company did with NFS, which is now a standard used everywhere.

If Sun want ZFS to get used all over the place in free software then I'd have expected at the very least to see them throw out a copy of the code, docs and patent grant in a form that could be used, even if it came with no other assistance of any kind. Now would be a great time to do that, but I can't see it happening, instead they'll miss the boat just as microsoft did with Office XML (three years ago they'd have sailed it through ISO to the sound of fanfairs)

Alan

#19 lore raw
Quoted 4 lines · Alan Cox

The real test of whether Sun were serious about ZFS being anywhere but Solaris is what they do to license it - they've patented everything they can, and made the code available only under licenses incompatible with other OS products. Their intent is quite clear, and quite sad.

That is not quite true. They made ZFS available under the CDDL, which is an OSI-approved open-source license that is *less* restrictive than the GPL. The CDDL doesn't prevent anyone from using the ZFS code in combination with code under other licenses.

The proof of that is that ZFS has already been ported to FreeBSD and it's being ported to the Mac OS X kernel.

The main problem with ZFS on Linux is that most people consider that the GPL doesn't allow non-GPL kernel modules.

#20 lore raw
Quoted 10 lines · Ricardo Correia
Quoted 4 lines · Alan Cox

The real test of whether Sun were serious about ZFS being anywhere but Solaris is what they do to license it - they've patented everything they can, and made the code available only under licenses incompatible with other OS products. Their intent is quite clear, and quite sad.

That is not quite true. They made ZFS available under the CDDL, which is an OSI-approved open-source license that is *less* restrictive than the GPL. The CDDL doesn't prevent anyone from using the ZFS code in combination with code under other licenses.

You are wrong. Please read e.g.
<http://www.gnu.org/licenses/license-list.html#GPLIncompatibleLicenses>
(maybe there are better analysis somewhere, but I don't know where).

Xav

#21 lore raw
Quoted 8 lines · Xavier Bestel
Quoted 4 lines

That is not quite true. They made ZFS available under the CDDL, which is an OSI-approved open-source license that is *less* restrictive than the GPL. The CDDL doesn't prevent anyone from using the ZFS code in combination with code under other licenses.

You are wrong. Please read e.g.
<http://www.gnu.org/licenses/license-list.html#GPLIncompatibleLicenses>
(maybe there are better analysis somewhere, but I don't know where).

What I meant in saying the CDDL is less restrictive than the GPL is that the CDDL can be freely used in conjunction with code under other licenses, as long as the files licensed under CDDL keep the license notice, whereas the GPL requires that derived works also have to be licensed under the GPL, which is not possible in many cases (such as this one).

#22 lore raw
Quoted 2 lines

What I meant in saying the CDDL is less restrictive than the GPL is that the CDDL can be freely used in conjunction with code under other

The CDDL is more restrictive in numerous ways, and in the Solaris case has an obnoxious requirement to use the US joke courts for any legal decisions (which means the license is I'm pretty sure not even valid in some parts of the world).

#23 lore raw
In reply to Alan Cox
Quoted 14 lines · Alan Cox
Quoted 3 lines

So who is responsible for potential changing Linux code licensing for allow if not incorporate CDDL code correct interraction without breaking some law ?

Every single contributor, individually. Which won't happen.

The real test of whether Sun were serious about ZFS being anywhere but Solaris is what they do to license it - they've patented everything they can, and made the code available only under licenses incompatible with other OS products. Their intent is quite clear, and quite sad.

Compare it to what the old Sun company did with NFS, which is now a standard used everywhere.

Quoted 7 lines

If Sun want ZFS to get used all over the place in free software then I'd have expected at the very least to see them throw out a copy of the code, docs and patent grant in a form that could be used, even if it came with no other assistance of any kind. Now would be a great time to do that, but I can't see it happening, instead they'll miss the boat just as microsoft did with Office XML (three years ago they'd have sailed it through ISO to the sound of fanfairs)

Maybe Ian Murdock could weigh in on this given his new position at Sun. Ian?

BTW, congrats on the new gig...

#24 lore raw
In reply to Alan Cox
Quoted 10 lines · Alan Cox
Quoted 3 lines

So who is responsible for potential changing Linux code licensing for allow if not incorporate CDDL code correct interraction without breaking some law ?

Every single contributor, individually. Which won't happen.

The real test of whether Sun were serious about ZFS being anywhere but Solaris is what they do to license it - they've patented everything they can, and made the code available only under licenses incompatible with other OS products. Their intent is quite clear, and quite sad.

This isn't universally true. Look at Java, for example, which Sun recently released parts of under an open source license -- not the CDDL, not a CDDL/xxx dual license, the GPL proper.

Indeed, Sun already have products that are dual licensed CDDL/GPL, for example the J2EE product.

Quoted 4 lines

If Sun want ZFS to get used all over the place in free software then I'd have expected at the very least to see them throw out a copy of the code, docs and patent grant in a form that could be used, even if it came with no other assistance of any kind.

I couldn't speculate on the rationale, but it does seem that Sun's choice to use _only_ the CDDL with certain software (like ZFS) is deliberate.

Signature · 5 lines
Cheers,
Alistair.

Final year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.
#25 lore raw
In reply to Alan Cox
Quoted 4 lines · Alan Cox

The real test of whether Sun were serious about ZFS being anywhere but Solaris is what they do to license it - they've patented everything they can, and made the code available only under licenses incompatible with other OS products. Their intent is quite clear, and quite sad.

Please do see:
http://www.opensolaris.org/os/about/faq/licensing_faq/#patents

ZFS has been ported to some of those 'other OS products'. :)

My two cents...

-Manoj

#27 lore raw
Quoted 8 lines · Alan Cox
Quoted 2 lines

Please do see:
http://www.opensolaris.org/os/about/faq/licensing_faq/#patents

Which appears to agree with everything I said not what you are claiming.

The patent license is strictly tied to their implementation and its derivatives under the CDDL, so specifically acts to exclude Linux.

I thought you said "incompatible with other OS products". I believe there are other OS products it is quite compatible with. The ports of ZFS seem to confirm this.

That it is compatible with the Linux kernel was not what I was arguing. :)

-Manoj

#28 lore raw
In reply to Tomasz Kłoczko
Quoted 11 lines · On Tuesday 17 April 2007 09:47:32 Tomasz Kłoczko wrote:

On Tue, 17 Apr 2007, Theodore Tso wrote:
[..]

Quoted 6 lines

Well, that was totally useless answer from the ZFS developers. What he should have told you is to contact Sun management, since they are the only ones who can decide whether or not to release ZFS under a GPL license, and more importantly, to give a patent license for any patents they may have filed in the course of developing ZFS. This is not anything Linux developers can help you with.

Realy can't or don't want (?)

As it has been explained to you before it is "can't"

Quoted 3 lines

So who is responsible for potential changing Linux code licensing for allow if not incorporate CDDL code correct interraction without breaking some law ?

If I've parsed this query correctly the answer is: Linux is licensed under the GPL and because a number of people that have contributed code to it can no longer agree to a change in the license because they have died this cannot be changed. That was explained quite clearly in several mails as well.

Quoted 5 lines

And/or what Linux can loose on follow this king changes ? And/or why Linux code licensing can't evolve ? Seems when Linux code was licensed noone was thinking about case like interraction with code under license like CDDL so why now it can be corrected and still many people try to think like "anything arond Linux must evolve .. but not Linux" (?)

When Linux was licensed under the GPL there was only *ONE* real choice for licensing it. Linus released the code under the GPL and there it has remained, with Linus leading development. If Linux had *NOT* been released under the GPL it would not be as popular or as powerful as it is - and that is not an opinion but a statement of fact.

Quoted 1 line

Why this can't be fixes ?

See the previous statement and several previous mails in this thread. Linux is licensed under the GPL, it is the *only* license agreed to by everyone that has contributed code. If I remember the statistics, there have been something like 10,000 different people that have contributed code. Since each contributor holds the copyright on their code they are the *ONLY* people that could change the license on it. Anyone attempting to change the license without agreement from *everyone* that has contributed code to the kernel they are in violation of US and international copyright laws.

Quoted 2 lines

If in this ponit in Linux "evniroment" can't be chaged .. sorry but is it not kind of hipocritics ?

Nope. You've just ignored it when it was explained *why* the existing ZFS code cannot be simply be ported to Linux. If you really need ZFS on linux, might I suggest that you port the code on your own and maintain whatever patches are needed to use it? As it stands ZFS *might* show up in Linux as a from-scratch implementation, although I stress the "might" because there are patents involved.

DRH

(Now please, drop the subject - IMNSHO it is never going to happen)

#29 lore raw
Quoted 6 lines · Daniel Hazelton

Nope. You've just ignored it when it was explained *why* the existing ZFS code cannot be simply be ported to Linux. If you really need ZFS on linux, might I suggest that you port the code on your own and maintain whatever patches are needed to use it? As it stands ZFS *might* show up in Linux as a from-scratch implementation, although I stress the "might" because there are patents involved.

Given that Sun has reportedly filed a huge number of patents covering ZFS and has refused to make them available for anything other than Solaris --- and there are senior Sun programmers who have on record stated that one of the reasons why Sun picked the CDDL was precisely because it was incompatible with GPL and Sun fears Linux ---- I wouldn't bet on Sun being willing to making a patent license available to a hypothetical alternate implementation of the ZFS format for Linux.

Again, this is is Sun's fault, and it's because they fear Linux, and it may have something to do with the fact that the vast majority of their Opteron boxes get Linux installed instead of Solaris. The bottom line is that people who would like ZFS need to understand that the code is Copyright by Sun, and there are almost certainly patents owned by Sun, and if they choose licenses that are explicitly designed to be incompatible with Linux, we should respect Sun's deep-seated fear of Linux, and we can continue trying to innovate around better filesystem and LVM storage technologies, as opposed to trying to chase the ZFS tail lights.

Of course, this is all open source. If someone wants to work on reimplementing ZFS from scratch, either in userspace or in the kernel, certainly the Linux community won't stop them. Given the patent issues Linus might not feel comfortable including it in the mainline sources without a promise from Sun that they won't sue the pants off of him and The Linux Foundation, but again, that's Sun's decision, and no one else can help you there.

- Ted

#30 lore raw

* Theodore Tso:

Quoted 3 lines

we can continue trying to innovate around better filesystem and LVM storage technologies, as opposed to trying to chase the ZFS tail lights.

Indeed. Here's a gem from the official ZFS FAQ:

| What can I do if ZFS panics on every boot?
| 
|     ZFS is designed to survive arbitrary hardware failures through the
|     use of redundancy (mirroring or RAID-Z). Unfortunately, certain
|     failures in non-replicated configurations can cause ZFS to panic
|     when trying to load the pool. This is a bug, and will be fixed in
|     the near future (along with several other nifty features like
|     background scrubbing and the ability to see a list of corrupted
|     files). In the meantime, if you find yourself in the situation
|     where you cannot boot due to a corrupt pool, do the followng:
| 
|        1. boot using '-m milestone=none'
|        2. # mount -o remount /
|        3. # rm /etc/zfs/zpool.cache
|        4. # reboot
| 
|     This will remove all knowledge of pools from your system. You will
|     have to re-create your pool and restore from backup.

<http://opensolaris.org/os/community/zfs/faq/#zfspanic>

I keep hoping that this FAQ entry is outdated, but the date on that page is rather current. 8-/

#31 lore raw
Quoted 4 lines · Florian Weimer

<http://opensolaris.org/os/community/zfs/faq/#zfspanic>

I keep hoping that this FAQ entry is outdated, but the date on that page is rather current. 8-/

That FAQ entry is outdated, ZFS can recover from metadata corruption on non-replicated pools for a long time already.

Background scrubbing and the ability to see a list of corrupted files has also been available for a long time (even longer than the above).

#32 lore raw
Quoted 2 lines · Ricardo Correia

That FAQ entry is outdated, ZFS can recover from metadata corruption on non-replicated pools for a long time already.

Just a clarification, ZFS not only detects metadata corruption through the use of checksums but, since it keeps 2-3 copies of each metadata block on-disk (even on non-replicated pools), it also rewrites the corrupted blocks, effectively repairing the corruption.

All of this is done transparently to the user but, of course, it's possible to see a report of checksum failures.

#33 lore raw
In reply to Theodore Tso
Quoted 12 lines · Theodore Tso
Quoted 10 lines · David R. Litwin
Quoted 1 line

The license that protects the code we write is far from nonsense.

I know. In the end, this is the reason this topic is being discussed.

I suggest the first thing you do is contact the ZFS developers and convince them to release their code under a license that's GPL compatible, then we can start looking at a Linux port.

I began by contacting them. One of the devs there told me to contact the Linux devs.

Quoted 8 lines

Well, that was totally useless answer from the ZFS developers. What he should have told you is to contact Sun management, since they are the only ones who can decide whether or not to release ZFS under a GPL license, and more importantly, to give a patent license for any patents they may have filed in the course of developing ZFS. This is not anything Linux developers can help you with.

- Ted

Copyright law protects an implementation, not a specification. If there is a specification for a particular file-system, then certainly one can create a compatible one without violating any copyrights. Patents protect algorithms and other implementation details. Certainly, there are at least a hundred ways of performing the same function using a programming language, and if you never look at somebody else's' implementation details, you certainly should not be violating a patent.

So, what needs to be done is simply find out the specifications of the file-system. From the specifications, one writes compatible code. To protect "IP," you might have to give it a different name than "ZFS," but you certain should be able to write code that handles ZFS format files. The patent (pending) seems to work around the little/big endian issue. So, there is probably something in a header somewhere that resolves this --big deal, machines that are incompatible will have to suffer byte-swapping overhead. There are also 64-bit checksums for some reason. I guess they have bad hardware and needed a work-around. The 128-bit file-size follows the, "if a little is good, more must be better..." logic that became prevalent in industry once sales persons and accountants took over engineering.

Cheers,
Dick Johnson
Penguin : Linux version 2.6.16.24 on an i686 machine (5592.59 BogoMips). New book: http://www.AbominableFirebug.com/
_


****************************************************************
The information transmitted in this message is confidential and may be privileged. Any review, retransmission, dissemination, or other use of this information by persons or entities other than the intended recipient is prohibited. If you are not the intended recipient, please notify Analogic Corporation immediately - by replying to this message or by sending an email to [email protected] - and destroy all copies of this information, including any attachments, without reading or disclosing them.

Thank you.

#34 lore raw
Quoted 2 lines · linux-os (Dick Johnson)

So, what needs to be done is simply find out the specifications of the file-system.

I didn't know that was that simple, great !
So, what do we wait ? (I love that abusive "we")

Xav

#35 lore raw
Quoted 8 lines · Xavier Bestel
Quoted 2 lines · linux-os (Dick Johnson)

So, what needs to be done is simply find out the specifications of the file-system.

I didn't know that was that simple, great !
So, what do we wait ? (I love that abusive "we")

Xav

Well BSD already announced that they ported the file-system. "We" is not meant to be abusive, simply instructive as in "we the people."

Cheers,
Dick Johnson
Penguin : Linux version 2.6.16.24 on an i686 machine (5592.59 BogoMips). New book: http://www.AbominableFirebug.com/
_


****************************************************************
The information transmitted in this message is confidential and may be privileged. Any review, retransmission, dissemination, or other use of this information by persons or entities other than the intended recipient is prohibited. If you are not the intended recipient, please notify Analogic Corporation immediately - by replying to this message or by sending an email to [email protected] - and destroy all copies of this information, including any attachments, without reading or disclosing them.

Thank you.

#36 lore raw
In reply to linux-os (Dick Johnson)

linux-os (Dick Johnson) skrev:

Quoted 2 lines

if you never look at somebody else's'
implementation details, you certainly should not be violating a patent.

Oh, it would be a beautiful world in which this was true!

Michal