Re: syscall implementation
Re: syscall implementation
- Subject: Re: syscall implementation
- From: Quinn <email@hidden>
- Date: Wed, 11 May 2005 10:32:27 +0100
At 19:02 -0400 10/5/05, Bijoy Thomas wrote:
I was just curious about how they worked on the ppc.
Cool.
By system call patching, do you mean that the syscall table is no
longer exported and replacing system calls with your own functions
or trying to add a new syscall is no longer possible?
Exactly.
I remember the Linux kernel developers got tired of people hijacking
syscalls and decided not to export it any more with version 2.6. But
ofcourse, people have found ways around it.
Of course. Mac OS X is an open source kernel, after all, so we can't
stop folks from hacking it. However, as we draw a sharp line between
what's supported (the KPIs) and what's not (everything else), we feel
a lot less worried about changing the unsupported stuff and breaking
the developers that rely on it.
The flip side of this coin is that we're serious about extending the
KPIs to cover serious developer requirements. So, if you're building
a product that requires you to patch the system call dispatch table,
we'd like to know about it. This happened a number of times during
the Tiger pre-release cycle, and I expect it to happen again as we
(Apple and our third party developers) get more experience developing
software for Tiger.
Share and Enjoy
--
Quinn "The Eskimo!" <http://www.apple.com/developer/>
Apple Developer Technical Support * Networking, Communications, Hardware
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden