From: Jeffrey Hundstad <jeffrey.hundstad@mnsu.edu>
To: xfs@oss.sgi.com
Subject: [humor] Re: XFS...Windows?
Date: Mon, 9 Dec 2013 14:33:54 -0600 [thread overview]
Message-ID: <52A62932.6000605@mnsu.edu> (raw)
In-Reply-To: <52A5F249.1060505@sandeen.net>
On 12/09/2013 10:39 AM, Eric Sandeen wrote:
> 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. :)
<humor>
To keep it standards compliant with your new OS, you'd want to change it
just a tiny bit to make it incompatible with the normal XFS, patent that
bit and claim it's an industry standard.
</humor>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2013-12-09 20:34 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 ` XFS...Windows? Eric Sandeen
2013-12-09 20:33 ` Jeffrey Hundstad [this message]
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=52A62932.6000605@mnsu.edu \
--to=jeffrey.hundstad@mnsu.edu \
--cc=xfs@oss.sgi.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 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.