site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com Am 23.06.2006 um 22:52 schrieb David A Rowland: OK. I thought so but it might have been the problem ;-) You're welcome. Glad to hear you've got it working now. Mike -- Mike Fischer Softwareentwicklung, EDV-Beratung Schulung, Vertrieb Web: <http://homepage.mac.com/mike_fischer/index.html> Note: I read this list in digest mode! Send me a private copy for faster responses. _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.a... Am 23.06.2006 um 21:03 schrieb David A Rowland <rowlandd@sbcglobal.net>: StartupItems.plist Should be "StartupParameters.plist" I think. That's what I use. Right, my mistake in the email. So your kext bundle is actually installed inside the StartupItem? Why not in /System/Library/Extensions/ ? Apple strongly suggests the Library/StartupItems location for third party stuff. I'll follow the rules. Do you have any reference where this is documented? I'm not suggesting it's not a good idea but until now the only way I saw to get a kext loaded at boot time seemed to be to install it in /System/ Library/Extensions. It never occured to me that a StartupItem might be used to load a kext. Unless the kext is needed very early I guess it would work out fine that way though. Another thought is that StartupItems seem to be depreciated in favor of the launchd mechanism. As far as I understand launchd though, this particular way to use StartupItems is not easily converted into something launchd could work with. There was a long discussion about a similar topic on the Darwin-dev ML a couple of days ago. It turns out to have been a misspelling in my script, MyKext. With that fixed it does just what I want. Your comments here were very helpful. Thank you. This email sent to site_archiver@lists.apple.com