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: Tue, 18 Mar 2008 11:04:29 +0100
On Mar 15, 2008, at 22:59, Duane Murphy wrote:
--- At Sat, 15 Mar 2008 20:18:54 +0100, Stephane Sudre wrote:
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.
This is in fact how the kext is installed. Following the installation,
the postflight script changes perms, etc and touches /S/L/E.
I don't understand why the postflight script would need to change the
permissions, owners or groups. If they are correctly set in the
pax/cpio archive, why would they need to be changed?
There used to be a bug in Installer.app on Mac OS X 10.2 where owners
and groups were not correctly set if you needed to have root:wheel. And
yes, in this case, you had to fix the owner and group settings in the
postflight script. But this has been fixed since.
If you need to do some post actions to install something in /S/L/E when
you conform to the recommended permissions and groups, it should be
considered a bug in Installer.app, in the documentation or in the OS.
_______________________________________________
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