Re: Notification of fork()
Re: Notification of fork()
- Subject: Re: Notification of fork()
- From: Michael Smith <email@hidden>
- Date: Tue, 26 Dec 2006 11:39:34 -0800
On Dec 26, 2006, at 10:55 AM, Josh Rodatus wrote:
That is very interesting. I'm looking at it right now. Certainly
it is
more invasive than what I had in mind, but I'm not really in a
position to be picky if it works.
I noticed in the documentation that he intends to one day add
"mach_unoverride" support. So, what does this mean when my kext
unloads?
When you override, you are copying your custom function into the
kernel's permanent memory. Your custom function will *not* be
erased along with your kext (during unload).
The kernel's "permanent memory" is completely full of bits of the
kernel, so wherever it might go that ain't it.
= Mike
_______________________________________________
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