I have been looking into the possibility of binary compatibility for *nux and possibly other programs on Mac OS X, as well as other interesting or potentially useful programs to play with OS interoperability. Invariably, I have been lead to the task emulation functions, and immediately dove into learning about them (task_set_emulation, task_set_emulation_vector, and task_get_emulation_vector). In browsing and searching the mailing lists, I've run across posts from other people trying to make use of the task emulation functions as well, only to be met with the news that these functions have been unhooked and are therefore rendered useless. My question is simply this: why remove the task_{s,g}et_emulation functionality from the Mach kernel? While Apple may not need these functions, there are many other independent developers, myself included, that could make use of task emulation, perhaps as open-source projects or otherwise. - ardent developer _______________________________________________ darwin-kernel mailing list | darwin-kernel@lists.apple.com Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/darwin-kernel Do not post admin requests to the list. They will be ignored.