site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com Thanks for the reply. I just came across an article on it. http://dom.neopoleon.com/permalink.aspx/4e48d9dd-4c28-4b89-a8e5-8cb158da44c3 S+E -- 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 (Darwin-kernel@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.a... At 22:11 -0400 2/5/05, Bijoy Thomas wrote: Learning how system calls work is all well and good for curiosity's sake, but I have a couple of warnings about using this information in a product. o Apple does not support binary compatibility for statically linked executables. That is, if you do as the above article suggests and write your own glue to make system calls from a user space program, we won't make any effort not to break you. For binary compatibility, you must make system calls by dynamically linking to libSystem. o Monkeying with the in-kernel system call dispatch mechanism is definitely not supported. Many folks have discovered this as they've trying to port their code to Tiger. System call patching is not supported on Tiger. If you can explain what you're trying to achieve, we might be able to suggest a better alternative. This email sent to site_archiver@lists.apple.com