Re: Placing Kext at custom location instead of /System/Library/Extensions
Re: Placing Kext at custom location instead of /System/Library/Extensions
- Subject: Re: Placing Kext at custom location instead of /System/Library/Extensions
- From: Rick Macklem <email@hidden>
- Date: Fri, 7 Dec 2007 10:59:05 -0500 (EST)
On Fri, 7 Dec 2007, JanakiRam wrote:
Hi All,
I've developed a kext for my product . To have more control on
loading the kext (after login) , i'm planning to place it at custom location
( /opt/myproductfolder) instead of /System/Library/Extensions.
Can any one point out the pros & cons for the location change ?
This is more a related question than an answer to your question, but...
does putting the kext somewhere other than /System/Library/Extensions
affect how it gets cached (in the kernel extensions cache)? I have mine
in /System/Library/Extensions and I do have to remember to
sudo touch /System/Library/Extensions
after I replace the binary. (It's loaded by a daemon of mine that is
started by Launchd. Oh, and I wasn't bothering to bump up the version#
for each build.)
Thanks in advance for any info, rick
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden