Apple

On 7-Feb-06, at 2:35 PM, Alain Birtz wrote:

<snip>

If that's the case, why don't you put your KEXT in /System/Library/
Extensions? There are a couple circumstances where is makes sense to
not put your kernel extension in /S/L/E, but to me this doesn't seem
to be one of them

Note that simply placing your kext in /S/L/E doesn't mean it will be
loaded automatically at boot.

Not sure to understand: do you mean that simply placing the kext in /S/L/E
wil force the kext to load automatically at boot and this without the script holding the kextload instruction ?

IOKit matching can cause it to do so,
but it's not the default behaviour.

Sam

------------------------------

Message: 2
Date: Mon, 6 Feb 2006 21:08:52 -0800
From: Cliff Russell <email@hidden>
Subject: Re: Kern ext. message "An item in the Startup Items
folder...Fix"
To: John Davidorff Pell <email@hidden>
Cc: Darwin Kernel List <email@hidden>
Message-ID: <email@hidden">email@hidden>
Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed

John,

I don't think it's that simple.

I think you'll find that a lot of third party drivers, especially
authors of kernel extensions that need to participate in the boot
process or driver matching will install their kernel extension in /
System/Library/Extensions.

In fact, in "I/O Kit Device Driver Design Guidlines" under "Packaging
Drivers for Installation" you'll see a note talking about using
creating a package to install your kernel extension in /System/
Library/Extensions (see <http://developer.apple.com/documentation/
DeviceDrivers/Conceptual/WritingDeviceDriver/index.html>)

I can't find any Apple documentation indicating that third parties
should not install their kernel extensions in /System/Library/
Extensions.

Yes, /System is Apple owned, but I think this is an exception to that
rule. As well Startup Items are deprecated on 10.4. (see <http://
developer.apple.com/technotes/tn2005/tn2083.html>)

Alain needs to decide where his extensions needs to be installed. I
think if his extension needs to run everytime the machine boots and
he sets up the appropriate matching information
then /System/Library/Extensions is reasonable, but perhaps there is
some other requirement to his extension that I don't know about and
loading from somewhere else makes sense.

Yes, MyKext need to be load every time the computer start.

<snip>