[lkml]   [2003]   [Mar]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [BK PATCH] klibc for 2.5.64 - try 2
On Fri, 7 Mar 2003, H. Peter Anvin wrote:

> Roman Zippel wrote:
> >
> > You are avoiding my question. If something goes into the kernel, the
> > kernel license would be the obvious choice. Granting additional rights or
> > using a dual license is a relatively small problem. But you must certainly
> > have a reason to choose a completely different license?
> >
> I gave my reason. You chose not to accept it, but that's not my problem.

Correct me, IANAL, but my understanding is that klibc will be dual
GPL/<whatever it is now> by inclusion into the kernel tree, after all the
whole purpose is to provide an initramfs which will be linked into vmlinux
(Yes, linked not in the normal sense, but still).

So it'd rather be similar to some parts of the kernel which are already
dual licensed (parts of ACPI I think being the latest example), and
patches will be assumed to be contributed under that dual license, unless
explicitly stated otherwise.

Or not?


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:33    [W:0.064 / U:1.524 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site