export syscalls
A message that is not in the archive (sent off-list or not yet received): [email protected]
* frm [email protected] "10/25/2001 05:25:40 PM +0000" | sed '1,$s/^/* /' *
* Hi Linus,
*
* the appended patch exports the syscalls (GPL-limited), this is needed
* for the Linux-ABI modules so they can use the syscalls in their
* syscall tables for non-Linux personalities.
What is the rationale for marking these as GPL-exclusive symbols ?
I thought system calls were a public interface.
* Christoph
*
* --
* Of course it doesn't work. We've performed a software upgrade.
[snip]
* +EXPORT_SYMBOL_GPL(sys_ioctl);
* +EXPORT_SYMBOL_GPL(sys_gettimeofday);
[snip]
richard.
Signature · 4 lines
----------------------------------------------------------------------- Richard Offer Technical Lead, Trust Technology, SGI "Specialization is for insects" ___________________________________________On sabatical Nov 8 -> Nov 30
Quoted 9 lines · In article <[email protected]> you wrote:
* frm [email protected] "10/25/2001 05:25:40 PM +0000" | sed '1,$s/^/* /' *
* Hi Linus,
*
* the appended patch exports the syscalls (GPL-limited), this is needed
* for the Linux-ABI modules so they can use the syscalls in their
* syscall tables for non-Linux personalities.
Quoted 3 lines
What is the rationale for marking these as GPL-exclusive symbols ?
I thought system calls were a public interface.
That won't change, but the syscalls are exported GPL-only for _inkernel_ users. My first version of the patch didn't do that, but people think that they can cause to much pain when used incorrectly, and that is checkable only with non-binary-only modules.
Christoph
Signature · 1 line
Of course it doesn't work. We've performed a software upgrade.
Quoted 10 lines · Christoph Hellwig
Quoted 9 lines · In article <[email protected]> you wrote:
* frm [email protected] "10/25/2001 05:25:40 PM +0000" | sed '1,$s/^/* /' *
* Hi Linus,
*
* the appended patch exports the syscalls (GPL-limited), this is needed
* for the Linux-ABI modules so they can use the syscalls in their
* syscall tables for non-Linux personalities.
Quoted 8 lines
Quoted 3 lines
What is the rationale for marking these as GPL-exclusive symbols ?
I thought system calls were a public interface.
That won't change, but the syscalls are exported GPL-only for _inkernel_ users. My first version of the patch didn't do that, but people think that they can cause to much pain when used incorrectly, and that is checkable only with non-binary-only modules.
So since some people can't do something we should punish everyone? If binary-only module crashes and burns, other people aren't going to fix it anyhow.
Signature · 2 lines
Tom Rini (TR1265) http://gate.crashing.org/~trini/