All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ryusuke Konishi <ryusuke-sG5X7nlA6pw@public.gmane.org>
To: jir-hfpbi5WX9J54Eiagz67IpQ@public.gmane.org
Cc: athena-/JWCw35jmeM@public.gmane.org,
	linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: resizing file system
Date: Tue, 28 Sep 2010 01:01:38 +0900 (JST)	[thread overview]
Message-ID: <20100928.010138.179946334.ryusuke@osrg.net> (raw)
In-Reply-To: <87fwwvo3it.wl%jir-27yqGEOhnJbQT0dZR+AlfA@public.gmane.org>

Hi,
On Mon, 27 Sep 2010 19:59:54 +0900, Jiro SEKIBA wrote:
> Hi,
> 
> At Sat, 18 Sep 2010 01:20:00 +0900 (JST),
> Ryusuke Konishi wrote:
> > 
> > Hi,
> > On Fri, 17 Sep 2010 18:15:59 +0900, Jiro SEKIBA wrote:
> > > Hi,
> > > 
> > > I think it would be good to have a generic libraries for other user land tools,
> > > like parted, for the purpose to modify/tweek file system off line.
> > > At least, resize/fsck/mkfs are the generic functionalities that parted
> > > can handle.  So it's good if there is a library that can perform
> > > those things to avoid implementing same thing all over the place.
> > > 
> > > One big problem for parted is that parted is GPL3 and libnilfs2 is GPL2 X).
> > > Still, contributers of libnilfs2 are countable, so maybe we can get agreements
> > > from all contributers to change licence to LGPL2, isn't it?
> > 
> > Definitely yes.  I think we should migrate the licence of the library
> > to LGPL2.
> > 
> > One practical problem is that some of the source files derive the
> > kernel code, and they are licensed under GPLv2.
> > 
> > For example, nilfs2_fs.h and crc32.c are just such ones.
> > 
> > Do you think we need replacement for these?
> 
> We could choose to change the licence as LGPL like mqueue.h (*1).
> However, we may be able to think that license of nilfs2_fs.h won't affect
> license of user land tools.

> At least, Linus stated that "There's a
> clarification that user-space programs that use the standard system call
> interfaces aren't considered derived works, ..." (*2). 
>
> *1) http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob_plain;f=include/linux/mqueue.h;hb=HEAD
> *2) http://kerneltrap.org/node/1735

"unistd.h" is distributed under LGPL.  So, the above Linus' statement
sounds like saying just fundamental charateristics of LGPL.

The point of "nilfs2_fs.h" issue differs from that.  A copy of
nilfs2_fs.h is actually included in nilfs-utils, and the nilfs library
is depending on the copy.

The "mqueue.h" solution seems to be an approved manner (sigh).

Another solution is extracting requisites from "nilfs2_fs.h" and
rewriting them under LGPL for the library and userland programs.

Or, do you know any examples of GPL header file whose library is
licensed under LGPL?

> While, crc32.c must be replaced other implementation :(.
> I'll search lgpled implementation.

OK, let's replace it with a compatible one if we change the library
license to LGPL.

Thanks,
Ryusuke Konishi
--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2010-09-27 16:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-07 16:57 [SPAM] resizing file system Munro, Fred
     [not found] ` <BAEFA5609CC3AB4BAE1625CAD4C27E5C02986E1D-qPLjlnsG5hmCmmEZ8mJCX5vx1ZQ4fP860E9HWUfgJXw@public.gmane.org>
2009-04-07 17:30   ` Ryusuke Konishi
     [not found]     ` <20090408.023005.48479195.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-04-07 17:40       ` Munro, Fred
2010-09-11  9:46     ` Matteo Frigo
     [not found]       ` <87iq2cr4sq.fsf_-_-/JWCw35jmeM@public.gmane.org>
2010-09-11 18:34         ` Ryusuke Konishi
2010-09-11 19:40           ` [PATCH] Compare device number rather than device name for mount check Matteo Frigo
     [not found]             ` <87d3skgjc3.fsf_-_-/JWCw35jmeM@public.gmane.org>
2010-09-12  3:35               ` Ryusuke Konishi
2010-09-11 23:31           ` resizing file system Matteo Frigo
     [not found]             ` <87zkvnoo1l.fsf-/JWCw35jmeM@public.gmane.org>
2010-09-12  2:26               ` Ryusuke Konishi
     [not found]                 ` <20100912.112650.179928857.ryusuke-sG5X7nlA6pw@public.gmane.org>
2010-09-17  9:15                   ` Jiro SEKIBA
     [not found]                     ` <87tylo7msw.wl%jir-27yqGEOhnJbQT0dZR+AlfA@public.gmane.org>
2010-09-17 16:20                       ` Ryusuke Konishi
     [not found]                         ` <20100918.012000.159151572.ryusuke-sG5X7nlA6pw@public.gmane.org>
2010-09-27 10:59                           ` Jiro SEKIBA
     [not found]                             ` <87fwwvo3it.wl%jir-27yqGEOhnJbQT0dZR+AlfA@public.gmane.org>
2010-09-27 16:01                               ` Ryusuke Konishi [this message]
     [not found]                                 ` <20100928.010138.179946334.ryusuke-sG5X7nlA6pw@public.gmane.org>
2010-10-01  4:21                                   ` Jiro SEKIBA
     [not found]                                     ` <87wrq2tufd.wl%jir-27yqGEOhnJbQT0dZR+AlfA@public.gmane.org>
2010-10-03 10:34                                       ` Ryusuke Konishi

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=20100928.010138.179946334.ryusuke@osrg.net \
    --to=ryusuke-sg5x7nla6pw@public.gmane.org \
    --cc=athena-/JWCw35jmeM@public.gmane.org \
    --cc=jir-hfpbi5WX9J54Eiagz67IpQ@public.gmane.org \
    --cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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.