[lkml]   [2002]   [Oct]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [Linux-streams] Re: [PATCH] Re: export of sys_call_tabl
"Brian F. G. Bidulock" wrote:
> On Fri, 11 Oct 2002, Christoph Hellwig wrote:
> > It is not. Sys_call_table was exported to allow iBCS/Linux-ABI
> I don't know if it matters, but these two calls putpmsg and getpmsg
> are the calls used by iBCS.

AFAIK, iBCS use these syscalls to emulate TLI, and iBCS
only has this emulation working for the IP protocol suite.

LiS is hooking the same syscalls, and is more protocol

In this way, iBCS and LiS are competing projects, even
if their base objectives are very different (iBCS aims
for user-level binary portability from SysV, while LiS
aims for kernel-level STREAMS code portability from SysV
to extend to Linux).

> No, I don't think anyone wants proprietary syscalls to be registered
> with this facility. If _GPL can allow an LGPL module to use the
> facility without problems, that will be the best way to go.

An LGPL module with proprietary code linked into it will
taint the kernel. LiS is often linked with proprietary
code, since it is under LGPL.

IMHO, A not-GPL-only export from the kernel is needed

That will not make these syscalls proprietary. Even with
proprietary drivers linked into LiS, it is impossible to
deviate from the SysV definition of putpmsg/getpmsg
unless the code of LiS itself is modified.

Best Regards,

Ole Husgaard.
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:29    [W:0.087 / U:3.928 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site