mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Roman Zippel <zippel@linux-m68k.org>
To: David Lang <david.lang@digitalinsight.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
	Russell King <rmk@arm.linux.org.uk>,
	Linus Torvalds <torvalds@transmeta.com>, Greg KH <greg@kroah.com>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [BK PATCH] klibc for 2.5.64 - try 2
Date: Sat, 8 Mar 2003 17:55:15 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.44.0303081727460.5042-100000@serv> (raw)
In-Reply-To: <Pine.LNX.4.44.0303071753100.1933-100000@dlang.diginsite.com>

Hi,

On Fri, 7 Mar 2003, David Lang wrote:

> > There is still the possibility to support multiple libc implementation, if
> > you don't like dietlibc, you're still free to use klibc.
> 
> along the same lines if you don't like klibc you are free to use or
> implement dietlibc or anything else.

Ok, it seems this requires a larger explanation.
It doesn't matter what you or I like. As long as dietlibc or klibc and 
linux are separate projects, I don't care much about the license. I have 
little problems to contribute to a BSD project, if you look at the m68k 
fpu emulator you will find a dual license. I hope this makes it clear that 
I'm not against the BSD license.

The problem starts as soon as klibc becomes part of the linux kernel, as 
it would give a clear preference to similiar projects as dietlibc. It's 
hard to imagine, that this will not cause any problem. The easiest 
solution would be relicense klibc under a license which is closer to the 
kernel license, but on the other hand meets the requirements the current 
license was choosen for. AFAICS a libgcc like license would do this job, 
but Peter made it very clear, that he does not want a different license, 
although it's unfortunately unclear why, but I have to respect that.

This means now we have to come back to the original problem: what problems 
might occur, if klibc is integrated and distributed with the kernel? Will 
it be possible to use dietlibc? What does that mean for other early 
userspace code, has to be licensed under the klibc license? Can I take 
source from a GPL project and integrate that into klibc?
I think it's important to discuss such questions now, as long as still 
possible without a lawyer, is the module story not warning enough?
My opinion at this point is, as long as Peter avoids to dicuss these 
issues, we should also consider to avoid integrating klibc in the kernel.

bye, Roman


  parent reply	other threads:[~2003-03-08 16:45 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-07  0:16 Greg KH
2003-03-07  1:02 ` Roman Zippel
2003-03-07  1:05   ` H. Peter Anvin
2003-03-07  1:23     ` Roman Zippel
2003-03-07  1:35       ` H. Peter Anvin
2003-03-07  9:55         ` Roman Zippel
2003-03-07 13:43           ` H. Peter Anvin
2003-03-07 15:33             ` Kai Germaschewski
2003-03-07 19:42               ` H. Peter Anvin
2003-03-07 18:37             ` Roman Zippel
2003-03-07 18:52               ` Linus Torvalds
2003-03-07 21:55                 ` Roman Zippel
2003-03-07 23:05                   ` Linus Torvalds
2003-03-07 23:36                     ` Greg KH
2003-03-07 23:53                       ` Linus Torvalds
2003-03-07 23:55                         ` Greg KH
2003-03-08  0:47                           ` Linus Torvalds
2003-03-08  0:54                             ` Greg KH
2003-03-07 23:39                     ` Russell King
2003-03-07 23:44                       ` H. Peter Anvin
2003-03-08  0:00                         ` Russell King
2003-03-08  0:38                         ` Roman Zippel
2003-03-08  0:46                           ` H. Peter Anvin
2003-03-08  1:27                             ` Roman Zippel
2003-03-12 17:27                               ` Pavel Machek
2003-03-13  0:22                                 ` H. Peter Anvin
2003-03-08  0:46                           ` David Lang
2003-03-08  1:49                             ` Roman Zippel
2003-03-08  2:00                               ` David Lang
2003-03-08  2:26                                 ` Roman Zippel
2003-03-08 16:55                                 ` Roman Zippel [this message]
2003-03-08 17:06                                   ` Vlad@geekizoid.com
2003-03-08  2:06                       ` Eric W. Biederman
     [not found]                         ` <20030308100359.A27153@flint.arm.linux.org.uk>
2003-03-08 15:50                           ` Eric W. Biederman
2003-03-08 16:13                             ` Russell King
2003-03-08 17:28                               ` Eric W. Biederman
2003-03-08 21:08                                 ` H. Peter Anvin
2003-03-09  2:25                                   ` Eric W. Biederman
2003-03-09  2:30                                     ` Larry McVoy
2003-03-09 11:32                                 ` Daniel Egger
2003-03-09 11:46                                   ` Eric W. Biederman
2003-03-09 14:19                                     ` Daniel Egger
2003-03-10  0:49                                       ` H. Peter Anvin
2003-03-10  1:40                                         ` Daniel Egger
2003-03-10  6:01                                       ` Eric W. Biederman
2003-03-10 20:33                                       ` Hans-Peter Jansen
2003-03-10 22:02                                         ` Daniel Egger
2003-03-08 20:52                             ` H. Peter Anvin
2003-03-08 21:10                             ` H. Peter Anvin
2003-03-09  1:29                               ` Eric W. Biederman
2003-03-09  1:46                                 ` H. Peter Anvin
2003-03-09  2:37                                   ` Eric W. Biederman
2003-03-07 19:21 Matthew Wilcox
2003-03-07 21:04 ` Alan Cox
     [not found] <1047106664.22024.0.camel@rth.ninka.net>
2003-03-08 15:54 ` Linus Torvalds
2003-03-08 16:03   ` David S. Miller
2003-03-08 16:35     ` Linus Torvalds
2003-03-08 16:22       ` David S. Miller
2003-03-08 17:07       ` Larry McVoy
2003-03-08 20:22         ` Linus Torvalds
2003-03-08 21:02         ` H. Peter Anvin
2003-03-08 20:56       ` H. Peter Anvin
2003-03-09  1:24       ` Roman Zippel

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=Pine.LNX.4.44.0303081727460.5042-100000@serv \
    --to=zippel@linux-m68k.org \
    --cc=david.lang@digitalinsight.com \
    --cc=greg@kroah.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk@arm.linux.org.uk \
    --cc=torvalds@transmeta.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

all inboxes | Powered by JetHome®