[mandebooks]

I figured out the problem with my post install script, but it still doesn’t explain the package errors I get everytime I try using the chroot jail (see previous posts). I build my installers using Iceberg 1.2.4. I have 53 custom packages that handle all the aspects of customizing the image (there are so many because I modularized the entire process so each change (or group of related changes) is a single package.

[mandebooks]

So if a package has a preflight script it it that calls for a rm command then that command is going to fail since it can’t run the command from within the sparse-image? This sounds like an in credibly annoying item that needs a seperate implementation item (second folder for packages that you want run within a chroot jail) that way its easy to take advatage of when needed, but also easily avoided.

[mandebooks]

Ok, so thats the command, but how about its implementation within the InstaDMG process? If it changes the root why do the files have to be copied into a temp directory on the new disk image? I am trying to understand its implementation and why that would be causing my packages to fail with the new chroot option – even though they work just fine if I turn off the chroot jail.

[mandebooks]

Ok, got some more information.

I tried it with all my .pkg files in subfolders – no luck. Tried it running as root and still no luck.

I also found an additional log file and got this data out:

Copying folder ./InstallerFiles/CustomPKG/27 into the target at /private/tmp/package.qL2V46
Installing EasyFind.pkg from ./InstallerFiles/CustomPKG/27 (27) inside a chroot jail
installer: Error verifying EasyFind package contents: *** -[NSCFString substringFromIndex:]: Range or index out of bounds
Removing the copied folder: ./tmp/mount_folder.ZemiTx/mount_point.xTdMgF/private/tmp/package.qL2V46

As you can see there is a clear error in “verifying the package” I get this same error for all but a few of my .pkg files. Even the ones that don’t give me this error are not installing properly – I think something is causing the installer.app to go a bit nuts earlier on, but I don’t know.

[size=18]So – I wanted to pose my original question – HOW DOES THE CHROOT JAIL WORK? Can someone please post a document on the process and the methodology used for the CHROOT JAIL?[/size]

Sorry for being so forceful, but my original question was never answered or addressed.

[mandebooks]

So your saying you put each of your individual packages inside a dmg file? I suppose that would work – but that means I have to create 61 individual dmg files…

Randy R.

[mandebooks]

I have been running the script with sudo everytime – even with older versions before the chroot jail.

[Author]

Posts