Re: Installing a kext on 10.5 (Leopard)
Re: Installing a kext on 10.5 (Leopard)
- Subject: Re: Installing a kext on 10.5 (Leopard)
- From: Stephane Sudre <email@hidden>
- Date: Sat, 15 Mar 2008 20:18:54 +0100
On Mar 15, 2008, at 6:59 PM, Dean Reece wrote:
On Mar 15, 2008, at 10:35 AM, Duane Murphy wrote:
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.
kextd is watching the extensions folder, so the final touch you do
should (re)trigger the cache rebuild.
If you are doing a touch after the kext install & perm dance, and
the cache is not being rebuilt correctly, you need to file a radar.
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?
Yes, it is the best thing to do on any version of OS X, since it
guarantees you won't end up with a partially installed or updated
kext if the system crashes at just the wrong time.
Is this also the procedure that should be followed when you install
your kext through a .pkg package? That would go against the idea
behind a .pkg.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden