On Thu, Feb 12, 2004 at 10:05:33AM -0800, Rob Braun wrote: > > Apple has gotten really draconian about how kexts can be installed > on the system. I believe the kext actually has to be in /S/L/E, and > can't be a symlink. I'll need to test, but I'm pretty sure a symlink > won't suffice. I'll also go ask the kext folks how they would like > to see such a situation handled.
After talking with some of the people that actually know something about kexts, I'm completely wrong here. kexts can be loaded from anywhere. They only need to be in /S/L/E if they are going to be "hot plugged", or automatically loaded when a device is inserted or some such. If this is not the case, it is recommended that kexts NOT be placed in /S/L/E. A case in point is the filesystem kexts. These are in /S/L/CoreServices/... So, we can install kexts in /sw/<somewhere>, and everything should be fine. The only other things that would need addressing would be 1) a startup item to load the kext, 2) if the kext supports unloading, unload it on package removal. And that seems like about it. If the kext is going into /sw, and not touching anything outside of there anymore, how much do we need the big flashy warnings about the package installation? Should there be a warning on package removal if the kext doesn't support unloading? Something saying "warning, the kext is still loaded and will be until you reboot"? Rob ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
