From: Evgeniy Ivanov <lolkaantimat@gmail.com>
To: linux-ext4@vger.kernel.org
Subject: Re: Using parts of ext2_fs.h in BSD licensed code
Date: Mon, 15 Mar 2010 20:26:16 +0300 [thread overview]
Message-ID: <e1e08eb01003151026q1352c02btf12d7cd6d84c3f21@mail.gmail.com> (raw)
In-Reply-To: <e1e08eb01003150942s6350c04fn6b3d696fed8b7fc1@mail.gmail.com>
Just found, that recently FreeBSD got this:
http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/fs/ext2fs/ext2fs.h
It looks like I can easily include it to the BSD-licensed project and
no GPL violation. But I dunno how did they wrote ext2fs.h, since it
still must be based on ext2_fs.h
On Mon, Mar 15, 2010 at 7:42 PM, Evgeniy Ivanov <lolkaantimat@gmail.com> wrote:
> Hello,
>
> I'm working on ext2 implementation for Minix3, where BSD license is
> desirable (AFAIK folks from *BSD are interested too). Most things are
> already implemented, while working I looked through linux and hurd
> implementations, but didn't use anything from there (I just learned
> some internals of ext2) and read http://nongnu.org/ext2-doc/ (thus my
> implementation mostly based on ext2-doc).
> Flags, constants, data structures are available in ext2-doc and
> ext2_fs.h. As I understand GPL license I can't just take it from
> ext2_fs.h and use in BSD licensed code, since it violates GPL (it was
> confirmed on #gnu). Is it correct? From another hand code based on
> ext2-doc can't be called derivative work. Is there any other header
> similar to ext2_fs.h (or any documentation except
> nongnu.org/ext2-doc/)?
>
> Do you think I can ask copyright owners for permission to use
> constants(data structures) from ext2_fs.h? Can somebody please send me
> Remy Card's email (in sources it's incorrect)?
>
> --
> Evgeniy Ivanov
>
--
Evgeniy Ivanov
next prev parent reply other threads:[~2010-03-15 17:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-15 16:42 Using parts of ext2_fs.h in BSD licensed code Evgeniy Ivanov
2010-03-15 17:26 ` Evgeniy Ivanov [this message]
2010-03-15 18:23 ` tytso
2010-03-16 12:34 ` Evgeniy Ivanov
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=e1e08eb01003151026q1352c02btf12d7cd6d84c3f21@mail.gmail.com \
--to=lolkaantimat@gmail.com \
--cc=linux-ext4@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).