[nobrainer]

[QUOTE][u]Quote by: MichaelR[/u][p]@nobrainer Have you tried the SVN version? That did the job for me. I didn’t use any parameters and used 10.5.4 as mine image.[/p][/QUOTE]

I tried a couple different, including the latest and greatest one from today.

when you say SVN, do you mean instadmg script or the whole kitten caboodle?

[nobrainer]

[QUOTE][u]Quote by: Allister[/u][p]Hey Michael,
You are doing nothing wrong. There have been recent revisions that we cannot confirm symptoms of failure in 10.5 on, so for now the ‘voodoo'(not sure if its true you HAVE to do this to make it work) is:

1. Use an Intel machine patched to 10.5.8(as far as I recall it will build Leopard as a universal image, so should be no concern)
2. Make sure you’ve cleanly booted the system you’re building on
3. Best practice is to use the most recent retail disc, so try to find a 10.5.6 build

Beyond that, it’s my conjecture that you shouldn’t jail the installer daemon AND put the entire process in a chroot jail, so use the -s flag in addition to the -f. Mr. Bernstein also found that not using 3-digit folders worked better for him, I had no issue besides with some custom packages. Here’s his reporting on the subject:
https://www.afp548.com/forum/viewtopic.php?showtopic=27149&lastpost=true

hope that helps, Allister[/p][/QUOTE]

Allister,

I’m having a similar problem with my 10.5.8 build…

I did #1 and #2. I used the latest (10.5.5) disk we had.

I tried modifying the instadmg.bash file and set DISABLE_INSTALLD_CHROOT=true

Output disk name: Macintosh HD
09:10:36 ###### Finding main MacOS X installer disk ######
Found primary OS installer disk: ./InstallerFiles/BaseOS/Mac OS X Install DVD.dmg
09:10:36 ###### Looking for a Cached Image ######
Mounting the shadow file (/private/tmp/InstaDMG_temp_folder.90g87N/B6D2F972-E20B-43CD-9DF6-21DB157A0F29.shadowfile) onto the cached image (./Caches/BaseImageCache/2E725137.dmg)
2010-07-22 09:10:41.605 defaults[2894:10b]
The domain/default pair of (/private/tmp/InstaDMG_temp_folder.90g87N/mount_point.tOJXi8/System/Library/CoreServices/SystemVersion, ProductVersion) does not exist
2010-07-22 09:10:41.616 defaults[2896:10b]
The domain/default pair of (/private/tmp/InstaDMG_temp_folder.90g87N/mount_point.tOJXi8/System/Library/CoreServices/SystemVersion, ProductVersion) does not exist
2010-07-22 09:10:41.626 defaults[2898:10b]
The domain/default pair of (/private/tmp/InstaDMG_temp_folder.90g87N/mount_point.tOJXi8/System/Library/CoreServices/SystemVersion, ProductBuildVersion) does not exist
2010-07-22 09:10:41.636 defaults[2899:10b]
The domain/default pair of (/private/tmp/InstaDMG_temp_folder.90g87N/mount_point.tOJXi8/System/Library/CoreServices/SystemVersion, ProductName) does not exist
/Users/macadmin/instadmg/instadmg.bash: line 700: [: 5: unary operator expected
Target OS: ()
09:10:41 ###### Beginning Update Installs from /tmp/InstaUp2DateFolder-W85fU8 ######
Working on folder 01 Mac OS X 10.5.8 Combo Update (09:10:41)
Mounting the package dmg: MacOSXUpdCombo10.5.8 sha1-0a88c9ecfbe08faf1a2307929c67f38b4822dfcb.dmg (/tmp/InstaUp2DateFolder-W85fU8/01 Mac OS X 10.5.8 Combo Update) at: /private/tmp/InstaDMG_temp_folder.90g87N/mount_point.tOJXi8/private/tmp/mount_point.GfBL8W
###### There were no items to install in: /private/tmp/InstaDMG_temp_folder.90g87N/mount_point.tOJXi8/private/tmp/mount_point.GfBL8W ######

I tried finding in the instadmg file where to put the -s but couldn’t find it… and when i put it in the terminal line for instaupd2date.py -s -10.5 vanilla (or whatever it is)… i just got an error message.

I tried to set DISABLE_CHROOT=true and I got teh same “does not exist” errors, but it appears to continue to process the patches.

Am I doing something wrong?

[nobrainer]

Doh. Apparently it didn’t do any of the updates. oh well, back tot eh drawing board.

[nobrainer]

[QUOTE][u]Quote by: larkost[/u][p]Maybe a silly note, but you are creating your 10.5 image while booted into 10.5, yes? Otherwise I know things are going to go wonky.[/p][/QUOTE]

Lo and behold. The reboot seems to work properly!

Thank you again!

[nobrainer]

😳

Err, no, I originally built it on a 10.6 platform.
Last night though, I rebuilt on a 10.5 platform, giving a whirl now..

Thanks for the heads up! (seems like an odd bug though).

[nobrainer]

OoooOOH

Thank you!
You’re the bestest!

[nobrainer]

so doing some digging around, i found that it’s missing the

http://appldnld.apple.com.edgesuite.net/content.info.apple.com/iTunes9/061-8440.20100616.Tnzs2/iTunes9.2.dmg but for 9.2.1…

any idea how I can go about getting the updated one? Or do I need to just wait for the script update?

I’m assuming anytime a new patch rolls out, I will need to wait for the script update?

[nobrainer]

I think I figured out the AV problem, there is a users folder that had info in it – I just opened the file back in composer and deleted it. Trying on a couple lab systems.

[nobrainer]

Seems to be a problem with Symantec AV 10.2.3.pkg file. After I install that both accounts appear on the list.

But we’ve been using 10.2.3 since January and on our old method of builds it wasn’t an issue – it’s just since we started using instaDMG / CreateUser.

[nobrainer]

nope, I used the createuser.pkg files to create 2 local admin accounts that are hidden.

I’ve tested some apps to see what causes it – seems like our applications cd unhides the casper account (it was created with a before / after snapshot), but leaves the other local admin hidden.

Office 2008, AdmitMac, and Acrobat Reader seem to be fine (leaves both accounts hidden). All were packaged with Casper…

I’m still testing the remainder of the packages/dmg for our base build

[nobrainer]

I actually just ended up packaging with casper. Now when I deploy it and run off our local (hidden) admin account – all the apps except iPhoto work – which gives an error about no permissions. I assume it’s because of the admin account is hidden?

[nobrainer]

I wasn’t really looking to build it into the main image, I was looking to patch to the latest and greatest then make a deployable image that I could add to our deployment ‘build’.

Instadmg seemed to do a good job for making the touchless but updated image for the OS and I saw some stuff about iLife – wasn’t sure if I could use that to do kind of the same thing for just iLife..

[nobrainer]

I was having problems with the special characters as well….

I just did a test image and finally got them accepted.

for the password hash I had to use escape characters – w/o quotes

example:
./shadowhash p\@\$\$w0rd>password_hash

Maybe this can be added to the documentation? I would imagine anybody doing this for a company (or paranoid people) would be using “special” characters. It could save people a TON of time (in my case days).

[nobrainer]

Trying these changes – is there a way to do a faster build of the image? It’s taking about an hour+ or so between attempts… the –process part, or is that something that just needs to happen?

[nobrainer]

Yeah, You’re right, it’s gotta be the password i’m trying to use.

I will have to work on it more next week.

Thank you for ALL your help!

[Author]

Posts