An mkext should be created by kextcache in pd_setup

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Run pd_setup to create an ISO or VM

What is the expected output? 
An Extensions.mkext file is created to speed up the boot process

What do you see instead?
In the bootloader, I see that every kext is loaded individually

What version of the product are you using? On what operating system?
PD9

Please provide any additional information below.
DFE mentions
kextcache -m mach.macosx.kext /path/to/System/Library/Extensions
as the command to create the mkext on 
http://tgwbd.org/blog/2009/10/17/be-free-little-
pxes-be-free/

Original issue reported on code.google.com by appeng...@puredarwin.org on 2 Jan 2010 at 12:30

[GoogleCodeExporter]

This is when creating Nano

Original comment by appeng...@puredarwin.org on 2 Jan 2010 at 5:02

[GoogleCodeExporter]

I've noticed problems on read-only medium when the hardware where the 
Extensions.mkext has been generated 
on is different than the hardware which boots. 

Original comment by Aladin.Q...@gmail.com on 3 Jan 2010 at 12:15

[GoogleCodeExporter]

This is interesting. The DFE page mentions a switch to include more kexts in 
the mkext, maybe we need to use 
that.

Original comment by appeng...@puredarwin.org on 3 Jan 2010 at 12:27

[GoogleCodeExporter]

Switch added in revision 2b6333219b (enabled by default).

Original comment by Aladin.Q...@gmail.com on 5 Jan 2010 at 12:53

• Changed title: An mkext should be created by kextcache in pd_setup
• Changed state: Fixed