So, hdiutil is normally the tool that will mount a disk image, but its a userland tool, and we'll run something at the Boot-132 level(ie very low level) to mount the compressed diskimage. Rammjet leads me to believe that this function is already present in some form in boot-132...he did try it..
I'm betting this is akin to the feature that lets you load a ramdisk image with your custom kexts before really loading the os, by using syslinux/[GRUB?], but that loads stuff into memory, which is kinda bad for us. Let's get some feedback from him on how he did it with the install DVD...
Btw, i looked through that paper. and while it is definitely a good thing to be familiar with, I believe there is something more pressing to be understood:
please read this if you get a moment, we'll need to maximize our use of it.http://tgwbd.org/darwin/boot.html
This is from [user] himself:
25 seconds from Darwin boot prompt to Language selection dialog box.
Files placed outside the compressed image:
/test.dmg (the compressed image)
Place "-f -v rp=file:///test.dmg" in the Boot.plist.
The dot files/dirs can be deleted but they will be regenerated. That wouldn't happen on a DVD.
I modified the IOHDIXController.kext and built a new mkext. Because of the unique mkext, when the installer boots, I have full video and partial wireless.
The files are from an early 9A581 installation and the test.dmg is the 9A581 installer"
Let's try this. It turns out he exploits not a functionality of Boot-132, but of the darwin loader itself...Netbooting. This works great because the install disk is always read only, so booting has no problems...
I'm gonna try this soon. Once we've tried this we can progress to using a normal install image as opposed to an installer. That'll bring up the read-write issue, but i've got an idea for that.
gnite for now