Mailing Lists: Apple Mailing Lists
Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: KEXT ownership settings

My PB executes a script to create an installation package (.pkg) which
copies the kext into the right directory. Since this requires special
authorization the package asks a password. You can make the pkg run a script
(as root) with the right chowns and chmods in it too.

BTW: I use a separate machine for testing.

Jo Dotremont

chuck remes <email@hidden> wrote:
> This makes doing ProjectBuilder builds really tough when running the
> build as a regular user and not root. Yep, PB complains that it can't
> overwrite the kext because of ownership.
>
> It's a real pain to go in and "sudo rm -rf my.kext" every time I want
> to build it and then "sudo chown -R root:wheel my.kext" afterwards.
>
> Anyone have a slick way of setting up PB so it can get around this?

Hmm. It never would have occurred to me to build directly into
/System/Library/Extensions. I've always copied it in there manually
with sudo.

It never would have occurred to me either. I build the kext in my
project dir and kextload it from that location (it's unnecessary to
copy to /System/Library/Extensions). kextload complains if the
owner:group are not set to root:wheel. If I'm building the kext as my
regular user (cremes), it can't overwrite something owned by root EVEN
IF it is in a directory owned by cremes.

Am I missing something simple?
_______________________________________________
darwin-drivers mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/darwin-drivers
Do not post admin requests to the list. They will be ignored.


Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.