From: Eric Sandeen <sandeen@sandeen.net>
To: Yuji Saeki <yuji1@mail.com>, xfs@oss.sgi.com
Subject: Re: XFS...Windows?
Date: Mon, 09 Dec 2013 10:39:37 -0600 [thread overview]
Message-ID: <52A5F249.1060505@sandeen.net> (raw)
In-Reply-To: <000001cef46c$ab687cc0$02397640$@mail.com>
On 12/8/13, 5:24 PM, Yuji Saeki wrote:
> Congratulations on your file system, it’s quite nice. I’ve
> benchmarked it myself, it’s very impressive. I’m curious though, is
> there are thought to a Windows driver? If someone ported the most
> current-stable version to Windows (free) under the same license ‘GNU
> Lesser General Public License’ with entire credit to XFS
XFS isn't under the LGPL, it's GPL, as is the rest of the kernel code,
and the license terms should be quite clear.
> would SGI
> be okay with that? A ‘no-warranty implied’ (etc) kind of protection
> of course. Quite a few devs that I work with enjoy the XFS filesystem
> and we dev in both Linux and Windows. We’re very interested in making
> this happen with respect to the XFS project.
I'm not a lawyer, but it's not really an issue of opinion - it's a legal
matter. If you can port XFS to Windows while maintaining the terms
of the license agreements on both ends, you're free to do so.
The technical difficulty of such a task is another matter as well. :)
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-12-09 16:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-08 23:24 XFS...Windows? Yuji Saeki
2013-12-09 16:16 ` XFS...Windows? Shaun Gosse
2013-12-09 16:42 ` XFS...Windows? Jay Ashworth
2013-12-09 16:39 ` Eric Sandeen [this message]
2013-12-09 20:33 ` [humor] XFS...Windows? Jeffrey Hundstad
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=52A5F249.1060505@sandeen.net \
--to=sandeen@sandeen.net \
--cc=xfs@oss.sgi.com \
--cc=yuji1@mail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox