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 09:00:27 -0500
On Dec 15, 2008, at 12:15 AM, John D. wrote:
On Mon, Dec 15, 2008 at 5:33 AM, Dean Reece <email@hidden>
wrote:
It isn't a hassle for legitimate developers because they loose that
status
as soon as they step outside our KPI space. Thus far, we have not
introduced strong protections to prevent developers getting at
things we
don't export, but that may change if we see customer problems
resulting from
such practice.
Correct me if I'm interpreting your words wrongly, buy did you just
say that anyone who steps out of the limited KPI interfaces is
illegitimate?
In the sense of "can expect support", yes. I mean, you can hack on
anything you want, but KPIs and APIs exist specifically to be a
contract with developers about what won't change (at least without
warning). Going outside of them means you're at your own risk.
That sounds naive. It's not their fault if you have
crippled the FreeBSD kernel API. I'm not saying you don't have any
legit reasons to do so, but it's a fact that you've done it.
No, they have not. Darwin has never used the "FreeBSD kernel API".
Darwin shares some code with NetBSD and FreeBSD, but it is in no sense
a "crippled" FreeBSD. Believing that it is will probably just cause
you ongoing frustration.
--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