Ah. An mkext is a multi-kext. You can actually build one using the
mkextcache tool. It contains all the kexts you need to boot stuffed into
Well, yes, you can build one, and as you hint, /etc/rc does so at each bootup, which I learned to my chagrin a little before I got your note. It doesn't appear that mkextcache can produce a working Extensions.mkext for my system. It boots fine if I delete that file before I start up, so the extensions present are apparently OK (well, the ones I need, anyway). I do get one ``Error: Can't get bundle identifier.'' message when I run it; maybe that means something... It does report Compressing /System/Library/Extensions/AppleCore99PE.kext/Contents/Info.plist 2220 => 811 Compressing /System/Library/Extensions/AppleCore99PE.kext/Contents/MacOS/AppleCore99PE 89968 => 30842 which looks promising, but doesn't seem to work. I did move all extensions which appeared not to have been installed with 10.1, but that still didn't help. For me, the workaround is just to delete Extensions.mkext, and to comment out the bit in /etc/rc that generates it. The difference in boot time is fairly miniscule, and I don't reboot stable operating systems terribly often ;) Again, I think a lot of people are having this problem (check the message boards), so it might be a good idea to get something about this into the troubleshooting section online. If I find out which extension is causing trouble, I'll let everybody know... Thanks ---- Chris J. Bednar <http://optics.tamu.edu/~bednar/> Director, Distributed Computing Product Group http://AdvancedDataSolutions.com/