Re: GPL issues

Stefan Smietanowski
2006-04-12T09:13:29Z

[-- Attachment #1: Type: text/plain, Size: 2811 bytes --]

David Weinehall wrote:
> On Tue, Apr 11, 2006 at 10:45:55PM -0700, jdow wrote:
>
>>>On Tue, 2006-04-11 at 23:18 -0400, Mark Lord wrote:
>>>
>>>>Joshua Hudson wrote:
>>>>
>>>>>On 4/11/06, David Weinehall <tao@acc.umu.se> wrote:
>>>>>
>>>>>>OK, simplified rules; if you follow them you should generally be OK:
>>>>
>>>>..
>>>>
>>>>>>3. Userspace code that uses interfaces that was not exposed to
>>>>
>>>>userspace
>>>>
>>>>>>before you change the kernel --> GPL (but don't do it; there's almost
>>>>>>always a reason why an interface is not exported to userspace)
>>>>>>
>>>>>>4. Userspace code that only uses existing interfaces --> choose
>>>>>>license yourself (but of course, GPL would be nice...)
>>>>
>>>>Err.. there is ZERO difference between situations 3 and 4.
>>>>Userspace code can be any license one wants, regardless of where
>>>>or when or how the syscalls are added to the kernel.
>>>
>>>that is not so clear if the syscalls were added exclusively for this
>>>application by the authors of the application....
>>
>>Consider a book. The book is GPLed. I do not have to GPL my brain when
>>I read the book.
>>
>>I add some margin notes to the GPLed book. I still do not have to GPL
>>my brain when I read the book.
>
>
> This is possibly the worst comparison I've read in a long long time...
>
> It's rather a case of:
>
> Consider a book. The book is GPLed. You take add one chapter to the
> book. The resulting book needs to be GPLed.
>
> Now, instead of adding to that book, you "export" parts of the book by
> copying them into your book. Your new book wouldn't work without the
> copied parts. Your resulting book needs to be GPLed.
>
> Your "read the book"-case is only comparable to the case of building
> a userspace binary for local use that only uses existing interfaces,
> vs building one that uses exported private interfaces. In both cases,
> since you're not distributing your modified version, you're free to
> do whatever you like.
>
>
> Regards: David

IANAL But I don't think that makes any difference at all.

The INTERACTION between syscalls and userspace is not a topic for
discussion really. Otherwise we'd have to put the boundary at
"syscalls that the Linux Gurus added" vs "syscalls someone else added
cause they thought they were neat".

NONE of the ones in the "neat" category are ever to be used ever by
ANY non-GPL program.

That is what it boils down to. I add a syscall to the kernel, you don't
like it? Tough, it's GPL so I can distribute it, etc etc.

A program emerges that uses that syscall? You don't like that ?
Equally tough. It doesn't matter if I wrote both parts or just one,
we're not looking at INTENT here. Either programs can be non-GPL
or they can't.

Btw, no I'm not jumping at anyone here, I am just trying to show
a point.

// Stefan

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 253 bytes --]