Re: Obtaining non-exported symbol from kernel on runtime (without the debug symbols)
Re: Obtaining non-exported symbol from kernel on runtime (without the debug symbols)
- Subject: Re: Obtaining non-exported symbol from kernel on runtime (without the debug symbols)
- From: Amanda Walker <email@hidden>
- Date: Mon, 15 Dec 2008 08:56:02 -0500
On Dec 15, 2008, at 12:02 AM, John D. wrote:
Excuse me, but monkey business is taking FreeBSD and Mach, creating a
hybrid kernel, and crippling the API in a manner that doesn't let
third-party developers exercise the best of both systems. Is that
common sense?
To some of us, yes. Try maintaining binary compatibility for a Linux
or FreeBSD kernel module across major kernel versions. At least in
Darwin, if you use supported KPIs, it's *possible*.
It sounds like you've fallen into a common error--thinking "I did X
under Linux or FreeBSD, so I'll just tweak it a little bit for Mac OS
X", and then discovering that it's not that simple. This is not a
bug, though.
--Amanda
_______________________________________________
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