Re: Unloading a KEXT with Client still connected
Re: Unloading a KEXT with Client still connected
- Subject: Re: Unloading a KEXT with Client still connected
- From: Stephane Sudre <email@hidden>
- Date: Wed, 13 Jul 2005 22:36:34 +0200
On mercredi, juillet 13, 2005, at 10:25 PM, Allan Hoeltje wrote:
Thank you all for coping with my continuous stream of newbie questions,
hopefully including this one:
I have a client application that connects to my KEXT and I am currently
testing the KEXT by using kextload and kextunload. I noticed the hard
way
that if I kextunload the KEXT while my client is running and connected
I get
the scary "gray curtain of death" - which I guess is the kernel panic
everybody refers to.
Eventually my KEXT will be put in the startup folder. If the user
shuts
down with the client still running and connected to the KEXT will I
get a
kernel panic?
Can it be possible to rethink the issue and wonder if instead, you
could not just prevent the kext from being unloaded when the client is
connected?
_______________________________________________
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