site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com Hi Folks, I'm installing a kext in /System/Library/Extensions. On Leopard we are having trouble with the kext cache for a boot partition not getting updated properly when the kext is installed. Of course this results in the system becoming unbootable because the cache is out of sync (at least that's what the output at boot time says). We are following the usual guidelines, but I get the idea that the usual guidelines may not be appropriate for Leopard. The installer puts the kext folder into /System/Library/Extensions then we do the chmod, chown dance to set privileges correctly, then finally touch /S/L/E. I believe that on Leopard, kextcache is launched as a result of using the new FSEvents mechanism. This in turn causes kextcache to be kicked off when the folder is installed before the privilege dance can be finished causing the cache to get out of sync. It has been recommended to me previously to do the privilege dance outside of /S/L/E and then move the kext into /S/L/E. The question then becomes where is a good place to stage the kext? And is this the right thing to do? The target directory should be on the same volume as /S/L/E and support privileges (ie not have the "ignore privileges on this volume" switch turned on). Is just using /S/L appropriate? /tmp seems scary to me. Seems to easy (and to common) to remap to a different volume for expert users. Seems like this change to kext loading could affect lots of installations if I am correct. Thank you for your comments and recommendations. ...Duane _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... This email sent to site_archiver@lists.apple.com