Post Install Scripts

Question

Post Install Scripts

I am creating an image with System Utility. One module i can add is called "Add Packages and Post-Install Scripts".

I put one of my scripts in it:

#!bin/sh
defaults write /Library/Preferences/com.apple.loginwindow LoginwindowText "Hello"

But I get an error when trying to image saying "install setup failed: run postinstall script"

I know the script works because i tested it.

Any ideas?

intel, Mac OS X (10.5.8)

Posted on Oct 2, 2009 7:04 AM

Reply

Answer 1

Oct 2, 2009 9:12 AM in response to NeedSomeAnswer

You get the error where? When creating the image or when installing it?

If it's during creation (and I think that's what you're saying) then set the logging level to debug in SIU. This will produce a lot of information, but will give you a better idea of what's going on.

Reply

Answer 2

Oct 2, 2009 9:28 AM in response to Brian Nesse

No, I get the message when installing it. The image creates just fine. I go to deploy it, it installs the OS, then when it gest to the postimage script, it gives the error message.

In System Image Utility, I have the following:
"Define Image Source" (I use the DVD image)
"Add Packages and Post-Install Scripts"
"Create Images"

It runs through fine. It installs fine...until the post install script fails.

Reply

Answer 3

foilpan

Level 4

1,385 points

Oct 2, 2009 11:36 AM in response to NeedSomeAnswer

it could be the specific path. try the defaults command with no path to the pref, so it should apply globally. you might try the -currentHost option. there's also a shell variable that pertains to the installed image, though i forget what it is ($1 or something).

why not manage this loginwindow setting with mcx — is this just a test?

Reply

Answer 4

Oct 2, 2009 11:40 AM in response to foilpan

Well, the script works by itself. I can run the script after I image a machine and it does great. It's also not just that command. I can just put in the post install script to make a folder. It still fails.

Would you think it could be the shell I'm using? #!/bin/bash?

Reply

Answer 5

foilpan

Level 4

1,385 points

Oct 2, 2009 4:43 PM in response to NeedSomeAnswer

probably not…

try using the defined installer variables instead of a specific path. there's a quick rundown here, though there's probably better documentation of it elsewhere: http://tinyurl.com/yejppmm

basically, you probably want $3:

$1: Full Path to Package
$2: Full Path to target installation directory: /Applications
$3: Mountpoint of installation disk: / or /Volumes/External_Drive
$4: Root directory of currently booted system

your script may be failing because the installer is trying to run it on the booted volume, which won't work. you want it to apply to the restored/newly installed volume.

Reply

Answer 6

Oct 5, 2009 8:46 AM in response to foilpan

You might check the install log for more information. In the installer, Cmd-L to bring up the log, Cmd-3 to display all logs.

In addition to foilpan's suggestions... another possibility is that you are trying to use a tool which does not exist in the install environment (remember this is a slimmed down system.)

Reply

Answer 7

Oct 6, 2009 10:29 AM in response to Brian Nesse

Boy, this one is giving me a headache 🙂

foilplan, I don't really know what it is you are suggesting. I can't seem to understand it.

Brian, I checked the install logs. I changed the command to:
#!/bin/bash
/usr/bin/touch /var/hello

The logs say "/var/hello" Read-only file system.

Do you know if I have to put "sudo" before commands that alter the file system?

Reply

Answer 8

foilpan

Level 4

1,385 points

Oct 6, 2009 11:37 AM in response to NeedSomeAnswer

your last example was trying to create a file on the image netboot/install uses to perform the install, so it's read only.

use one of the variables i listed earlier, and you'll probably be fine.

try changing the one-liner to "/usr/bin/touch $3/var/hello" and see what happens.

the $3 variable is expanded to /Volumes/name of_your_targetdisk.

Reply

Answer 9

Oct 6, 2009 11:38 AM in response to NeedSomeAnswer

I tried this command:

"/usr/bin/touch /var/db/.AppleSetupDone"

The error is:

"touch: /var/db/.AppleSetupDone: Read-only file system"

Reply

Answer 10

Oct 6, 2009 11:41 AM in response to NeedSomeAnswer

Thanks foil...i'll give that a try.

Reply

Answer 11

Oct 6, 2009 1:07 PM in response to NeedSomeAnswer

I think that worked. I'll have to do some more testing.

So trying to understand the "$3" variable a little more, you are saying that you have to have that typed in the script in order for it to install on the remote machine?

Reply

Answer 12

foilpan

Level 4

1,385 points

Oct 6, 2009 1:47 PM in response to NeedSomeAnswer

i wish i had more readily accessible details on it, but refer to the man page for installer for some hints. it hints at the device variables.

take a look at the instadmg source ( http://code.google.com/p/instadmg/source/browse/trunk/instadmg.bash) for some other details. i'm not aware of any "official" documentation on the environment variables at play here.

Reply

Answer 13

Oct 7, 2009 6:35 AM in response to foilpan

Awesome foilpan! That worked wonderfully!

THANK YOU!

Reply

Answer 14

Oct 12, 2009 10:33 AM in response to NeedSomeAnswer

If anyone is still there, I seem to hit another big brick wall on the moduler image.

The post install script works. You have to put the $3\ in front of the path.

The problem lies whenever I add OS updates as well. I am using a 10.5.2 OS Disk to capture the image from. Therefore I add the following packages in the "Add Packages and Post-Insatll Scirpts" section:

MacOSXUpdCombo10.5.4.pkg
MacOSXUpdCombo10.5.6.pkg
MacOSXUpdCombo10.5.8.pkg

My image fails whenever it loads the 10.5.8 package. It will load 10.5.4 and 10.5.6 just fine.

Reply

Answer 15

Oct 13, 2009 9:14 AM in response to NeedSomeAnswer

The Combo update package will update any version of the OS. Try just using the 10.5.2 OS disk and the 10.5.8 Combo updater.

Reply