[OpenAFS] Re: Linking GPL3 code with IPL? (Was: afs_syscall (Samba as a client of OpenAFS))

[Derrick Brashear]

The GPL module won't help you as it's the kernel and not the userland. =20=

Doing ioctls on a proc file isn't really proprietary; You don't need =20
to link our code.

Derrick


On Oct 6, 2008, at 15:25, G=C3=A9mes G=C3=A9za <geza@kzsdabas.hu> wrote:

> Volker Lendecke =C3=ADrta:
>> On Sun, Oct 05, 2008 at 10:41:06PM +0200, G=C3=A9mes G=C3=A9za wrote:
>>
>>> I've built up a patch (attachment 3658 to bug 5799 on samba =20
>>> bugzilla)
>>> which makes fake-kaserver and vfs-afsacl work again.
>>> But the patched configure makes smbd, net and maybe other binaries =20=

>>> link
>>> with libsys.a in order to communicate with the openafs kernel =20
>>> code. The
>>> question is what are the legal consequences, are the binaries
>>> distributable et all?
>>>
>>
>> At the time I wrote the fake kaserver stuff I had the same
>> concerns and thus did a fresh implementation of the ticket
>> generation and syscall wrappers. Can't you do the same with
>> the proc_afs_syscall thing? This can't be much code.
>>
>> Volker
>>
> Unfortunately this time it seems to be a lot harder, the main change
> being at least to my understanding, the fact that the openafs kernel
> module doesn't advertise its services as a system call, and thus we
> cannot link with just libc code which calls into the kernel, but =20
> need to
> explicitly use openafs calls for the same propose resulting in a =20
> need to
> link to their code.
> Hope is not lost totally yet as I've read about some work of =20
> developing
> a GPL licensed kernel module, and then we could use some glue code =20
> from
> there.
>
> Geza
> _______________________________________________
> OpenAFS-info mailing list
> OpenAFS-info@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-info