Firstboot

[bango]

in the process of building an image. i use the following command to build : sudo ..path/to/instaUp2Date.py –process catalogfile.catalog
now in one of the catalog files, ive included a firstboot script – at the end of the script it destroys itself – using the srm command
in the build process, why does this script run, i dont get it, the mac reboots during the build process (cause in the script ive put that in there). how can i stop this script or any others from running when im trying to create an image.
thanks in advance

[Allister Banks]

Hey bango,

You need to let image creation finish, so that firstboot should be set to be called by a launchd job. osxdeployment.com has a rather thorough guide if you hadn’t taken a look already. Please pardon me if I’m not getting your issue properly, and ask more questions/post links to pastie’s of your scripts/catalog so we can see what you’re working with. Thanks,

Allister

[bango]

hi Allister
thanks for your reply.
i have read the firstboot article on the osxdeployment site – thats where i got the pdmoc sample from.

in my postflight script, i configure a few OS settings (that cant be done in WGM), bind to AD, assign a computer name….
here is a little snippet of code (that ive put at the end) in my postflight.sh file:

[i]#!/bin/sh
#############
###
sudo diskutil repairPermissions /
#
reboot 10
# Destroy this script!
srm “$0″[/i]

when the image is being created, and gets to the firstboot pkg file (found in one of the catalog files), it installs/configures what i tell it too and it when it gets to the reboot line, it does that.. When the mac rebooted, i didnt know if i had to re-run the image process again?
do i need to take out the “reboot 10” command from the script?
hope im making sense?? 🙂

[Allister Banks]

Hey bango,

You probably don’t want these functions performed before the computer boots- you’d be binding all the computers to AD with the same computer name if its built into the image. You cannot interrupt the build process and re-start it later, there is no mechanism to do so, and its last step is making a read-only optimized asr-restorable image. It also will run repairPermissions for you as one of its cleanup steps.

Please split out your directory and binding tasks into script(s) called by a LaunchDaemon. It will be the most reliable way to ensure these customizations happen, or use the actions provided in a deployment/imaging tool like DeployStudio to automate and manage these tasks.

Allister

[bango]

understand that. thank you so much! 🙂

[Author]

Posts