Re: The .nke check in Jaguar is NOT a good idea
Re: The .nke check in Jaguar is NOT a good idea
- Subject: Re: The .nke check in Jaguar is NOT a good idea
- From: Stéphane Sudre <email@hidden>
- Date: Thu, 25 Jul 2002 16:02:10 +0200
On Thursday, July 25, 2002, at 03:56 PM, Andrew Pinski wrote:
Actually having the ability to load in kext/kne after the
startup script is a good thing because when you install the
kext/kne you can actually not make the user reboot the machine.
In fact in Darwin 5.0(1.4) and even in 1.0 you can load in kext/kne
after the startup script and even unload them and install a new
version without rebooting.
In fact when Mac OS X 10.1.2 came out, the SharedIP kext was busted,
it would kernel panic when you connect to a local ip address (same
machine).
The problem was fixed in the Darwin's cvs, so downloaded the source and
made
the kext, unload the old one and loaded the new one up. It worked after
that.
I'm not saying it's useless to be able to load/unload a kext/nke at
will. This is super useful when you're coding your kext/nke.
I'm saying it's wrong that the System considers it can load a nke after
its startup scripts. Because the nke can be working fine, the
application too but the communication tunnel between them is not
established and so the application may not work as it should.
_______________________________________________
darwin-kernel mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/darwin-kernel
Do not post admin requests to the list. They will be ignored.