Why do pkg’s install on / instead of $CURRENT_IMAGE_MOUNT

[[email protected]]

Hi all,
i’ve found that pkg’s from the ‘CustomPKG’ folder, are targeted to / instead of $CURRENT_IMAGE_MOUNT.

anyone seen this behavior before?

[knowmad]

can you give us more details?
InstaDMG is supposed to re-point all installs to the current image mount…. do you have an unusual installerchoices file? have you altered your instadmg script drastically?
The more details you can give the more likely we (read: larkost) are to have a quick and/or useful answer.

[[email protected]]

hi all,
i’ve made 2 changes to the instadmg script:
[code]ASR_FILESYSTEM_NAME=”Macintosh HD”[/code] for the name of the resulting dmg when mounted and
[code]if [ “$IMAGE_FILE” == “$INSTALLER_FOLDER/Mac OS X Install Disc 1.dmg” ] || [ “$IMAGE_FILE” == “$INSTALLER_FOLDER/Mac OS X Upgrade DVD.dmg” ][/code]
so that a ‘drop in dvd’ can be used as base os.

one of the scripts i run (as postinstall on a empty pkg) is for setting the energy saver
the contents of the script are:
[code]
pmset -c sleep 0
pmset -c displaysleep 60
pmset -c disksleep 0
pmset -c lessbright 0
pmset -c halfdim 0
pmset -b sleep 5
pmset -b displaysleep 3
pmset -b disksleep 5
pmset -b lessbright 1
pmset -b halfdim 1
[/code]
instead of applying these settings to the dmg, they are applied to the system where i run the instadmg.bash script. the packagemaker project and the pkg are on my .mac public folder (my .mac login is tuke)

when i place system updates in the correct folder, they are applied as they should to the resulting dmg

i haven’t used installerchoices yet (still on my todo list…)

[knowmad]

I am really confused (a constant state of being but in this case it applies to somethings you said)
the upshot of your reply seems to be that if you put the updates where they belong then it works and if you put them where they don’t belong than it does not work…… am I missing something?

also, in your zero-payload installer package, the script you are running… does it reference the instadmg image by name or by $3 ?
what is the name of your boot drive?
Are you certain that pmset will work on a non-booted volume? I have a vauge recollection of it being a boot volume only option…
Have you looked into setting this stuff via mcx record? that I know works (I have done it myself) and it also lets you set it permanently, if you don’t want users playing with it.
Otherwise you might make your pmset script into a boot script, run it the first time or every time …. whatever you need.
Knowmad

[larkost]

I think that knowmad has hit upon the problem: pmset does not work on the filesystem, rather it works on the information that is stored in the power management unit. That has its own little bit of battery-backed RAM, and has nothing to do with the files on the virtual disk that InstaDMG builds (nor anything to do with the files on the boot drive). Using MCX would be a much better way of creating these settings. Alternately you could create something that was run once the computer first booted from the image, but that is a little more work.

Is there another reason you think that things are getting run against your booted drive?

[[email protected]]

ok,sure, makes sense…

the reason i wanted to set things this way, is because it’s easy ‘recyclable’ and easy to change in other deployment scenarios.

to reply on knowmad,
[quote] the upshot of your reply seems to be that if you put the updates where they belong then it works and if you put them where they don’t belong than it does not work…… am I missing something? [/quote]
what i mean, it did work with updates from apple but it didn’t with pkg’s i had created. now i understand it has nothing to do with how i made those pkg’s. (was not sure about that)

i’ll try the suggestions and see what works best for me

[Author]

Posts