[nobrainer]

Update:
Upon fighting with it s’more, I found the problem is that I’m expecting an encrypted PW to go through, as I read in several locations that it’s required, but the kickstart command is actually passing the PW as clear text. When I put in the first 8 characters of the encrypted PW, I was able to sign in just fine.

I’m uncomfortable with passing clear text as a PW via script – but if that’s the way it is, that’s the way it is…

[nobrainer]

[QUOTE][u]Quote by: dead2sin[/u][p]This is in rough form, but here is a basic guide for customizing a Firstboot.pkg:

[url]http://www.osxdeployment.info/wiki/Firstboot_Package_Guide[/url]

Nate[/p][/QUOTE]

Thank you for the info! I’ve been trying to download the PackageMaker thing all flippin morning, download keeps bombing out @ 2gig… i’ve tried from machines here at our office, our Chicago branch and our NY branch, all of them bomb out. (Mac’s and PCs). Finally flipped over to our ‘guest’ network and lo and behold it’s past the 2 gig mark… but it’s going @ around 200k / second…. soooo slooowwww….

While I wait for that to download, I’m gonna post another question re: kickstart and VNC 🙂

Thank you again for all your help!

[nobrainer]

[QUOTE][u]Quote by: dead2sin[/u][p]That is a good resource that Allister linked there. I use Greg Negle’s blog for reference a lot due to his great documentation on the various issues that we all run into eventually. That Packagemaker template will work quite well if you can get the postflights figured out. I’ll write up a Composer Guide for the firstboot package when I have time (Beginning of the semester rush right now, so things are rather hectic).

I prefer Composer personally, but as Allister said PackagerMaker has become more then capable with the last couple of updates and Packages looks very promising as well. InstallEASE also has a free packaing app if I am not mistaken. The only reason I chose to mention Composer in that guide was because its my main go-to Packaging App simply because I’ve used it for the past 2 years and don’t feel like learning PackageMaker 😀

Let us know if you get the firstboot package working or if you have issues getting it going.

Nate[/p][/QUOTE]

I don’t think it worked… well, it sort of worked…. it didn’t do teh firstboot.sh or the launchd…. here’s the info from where it failed from the instadmg debug log.

PHASE:Writing files…
%8.398202
PackageKit: Shoving /private/tmp/InstaDMG_temp_folder.0ytAaf/mount_point.f8eT5k/.PKInstallSandbox-tmp/Root (1 items) to /tmp/InstaDMG_temp_folder.0ytAaf/mount_point.f8eT5k
PackageKit: Executing script “./postflight” in /Users/macadmin/instadmg/InstallerFiles/InstaUp2DatePackages/payload-free.pkg/Contents/Resources
./postflight: cp: firstboot.sh: No such file or directory
./postflight: cp: com.shc.firstboot.plist: No such file or directory
Installed “payload-free” ()
PackageKit: —– End install —–

I modified the pkg’s postflight.sh script with the following…

cp firstboot.sh $3/Library/Scripts/Admin-Added
cp com.shc.firstboot.plist $3/Library/LaunchDaemons

my understanding was that if I copy the stuff to the folder, it would launch automatically the next time the system booted.

[nobrainer]

[QUOTE][u]Quote by: Allister[/u][p]Hey nobrainer,

Mr. Kevin White has to gloss over a few details in his Peachpit Deployment book, but he doesn’t skimp on the instructions for using Apple’s Packagemaker, and it really has become more capable over the years(and is free). I can’t speak to Iceberg even though the dev is very helpful and has an ancillary project “Packages” which may be of interest to you as well. The new Composer is pretty slick, but I wish they solved all my Adobe problems for me! Got to give them a break since its so inexpensive though, and I think, although I’ve only used the newest version for a couple minutes, is very straightforward and friendly.

Having said all that, you probably want to punt and just use a pre-made payload free package from Mr. Greg Neagle:

Payload-free package template

Zooming back in on your specific questions, /Library/LaunchAgents are considered better practice for repeating admin-created scripts, but I use a LaunchDaemon for my first-boot since I want it to be root and it self-removes so it doesn’t cause trouble. My payload-free package has a postflight script, which runs while instadmg installs the package, and cp’s the launchd.plist and firstboot.sh files from the resources folder of the package to $3/Library/Scripts/Admin-Added and $3/Library/LaunchDaemons, which automatically gets the plist loaded into launchctl on boot.

Does that clarify these three moving parts a little more? Nate’s guide is great, but if you have feedback you should definitely let us know so we can all benefit from your learning process. Thanks,

Allister [/p][/QUOTE]

Thank you for getting back to me so quickly!

I tried to get PackageMaker – but I don’t have a developer account handy and I heard iceberg was as good or better – and more importantly I could acquire it 🙂

I checked out the template, that seemed to be what i needed- I didn’t see anything about the firstboot script or plist – so i just added the cp command to copy to the postflight script sending the files to the folders you mentioned. guess I will see if that works. Theoretically – if I push the pkg to a system, it should run it, just to see if it works before it gets bundled.

[nobrainer]

svn checkout http://instadmg.googlecode.com/svn/trunk/ instadmg-read-only

Is the correct command… however, the part after /trunk/ is just a destination folder – it can be named anything you want.

There is apparently a bug in the 334 release that puts spaces into the catalog file instead of tabs, but that’s easily fixed if you don’t have time to wait for the corrected script (modify the catalog file and remove the spaces (replace with a single tab) under apple updates and system settings)

The other thing I ran into was when building 10.5.x machines the scripts will often bomb out because it can’t find the temp folder… another post here, in the forums, found that by commenting out Lines 573 –> 575 and then adding HOST_MOUNT_FOLDER=”/private/tmp” would correct it…
—
Lines 573 – 575 below to make it easier to search…just put a # in front of the line to comment it out

HOST_MOUNT_FOLDER=`/usr/bin/mktemp -d “$TEMPORARY_FOLDER/$MOUNT_FOLDER_TEMPLATE”`
/bin/chmod og+x “$HOST_MOUNT_FOLDER” 2>&1 | (while read INPUT; do log “$INPUT ” detail; done) # allow the installer user through
log “Host mount folder: $HOST_MOUNT_FOLDER” detail
—

However, this seemed to not work anymore with r334 – now I find it bombs out when it’s making the image, it goes through all the Apple updates, it errors out with something about the temp folder not being found – but it puts “/private/tmp/private/tmp”, so your mileage may vary.

[nobrainer]

To get around it, I just modified the catalog file and backspaced the “spaces” and hit tab. That seemed to correct it.

Now I’ve got a different problem where it goes through, but it’s double entering the temp path… for example “/private/tmp/private/tmp” and won’t let me create a 10.5.8 image. course, I also discovered my current 10.5.8 image is fine, so I don’t really need to at this point.

[nobrainer]

[QUOTE][u]Quote by: jazzace[/u][p]I’ve had this happen twice to me now and I am wondering what I might do to stop it. Here are the specs:

[i]10.5.8 client (not server) build machine (Mac mini Late 2009, server model)
Building a 10.5.8 image
instadmg.bash r318
latest version of createUser (1.0.3?)
no use of InstaUp2Date
[/i]

First question: can anyone remind me of the trick (that I heard at Macworld 2008 IT track) that would let me bring up the user/password dialogue text boxes so that I could try to type in my admin username and password?
[/p][/QUOTE]

If you go to system preferences –> Accounts –> Login Options –> Authenticate via the Padlock –> Change Display login window as Name and password

[nobrainer]

[QUOTE][u]Quote by: Chris+George[/u][p]Curiouser and curiouser. It worked.

I commented out lines 573-575 and inserted the following on line 576:
HOST_MOUNT_FOLDER=”/tmp”

I now need to go back and try and revert to /private/tmp (see my last post) and see if the changes hold. If so, it’s an issue with $MOUNT_FOLDER_TEMPLATE. If you’re working within /private/tmp you’re fine, but if you’re working within /private/tmp/InstaDMG_temp_folder.XXXXXXX, not so much.

Edit: Confirmed. Solution as noted above works; the only change required to resolve the issue is to comment out 573-575, and insert on 576:
HOST_MOUNT_FOLDER=”/private/tmp”

The build process is continuing at this time on my machine; I’ll let it finish and do my normal checks on the result, but I’m highly confident that it will be fine.[/p][/QUOTE]

I tried your suggestions, and it worked flawlessly! Thank you!

[nobrainer]

[QUOTE][u]Quote by: Gary+Bernstein[/u][p]I have just tried to use my 10.5 image that I thought was updated to 10.5.8 by using the combo updater. It appears to have ran but not installed the updates.

I must be missing something stupid, as this should not be this hard.

Any thoughts?[/p][/QUOTE]

Gary, that’s EXACTLY what I ran into a couple times that I was “successful” the DMG would finish, but when I would try and test deploy it, there would be no updates on it… I would go back through the logs and see that they all failed and I would still be on the original version of the OS 10.5.5

One thing to note – you can load the log files up in the console and watch them in real time to see if they fail… if they do fail you can abort the image and save yourself the time (a little trick I learned at the very end).

[nobrainer]

[QUOTE][u]Quote by: larkost[/u][p]The 10.5.8 updater will not work with the ‘-r’ flag. The chroot’ed installer code was put in place to handle the 10.5.7 and 10.5.8 updaters.

I have not been able to replicate any problems with the latest InstaDMG/InstaUp2Date running on 10.5.8 on Intel.[/p][/QUOTE]

I’m no where near considering myself an expert, I can only share what I found worked for me.

I do think there is a problem somewhere with instaDMG/InstaUp2Date. Maybe something your revision has or doesn’t have that others do/don’t. There looked to be several people with trouble with it (though you rarely hear about the ones that don’t have trouble).

I spent 4 full working days last week of between 9-11hrs each trying to get the instaDMG/InstaUp2Date working, different revisions, different hardware platforms, etc, and the above cmd line was the only way I got a working dmg file.

I’m more than willing to work with someone to narrow down the problems, so the next person can have a smoother experience. This is a GREAT treasure to find and the support community is top notch. I just wish I had the expertise to narrow down the trouble spot myself and constructively share 🙁

[nobrainer]

While using instadmg r261, I built a 10.5.8 using instadmg.bash -r -s -n “Macintosh HD” -m Mac1058_vanilla

I put all the updates in the installerfiles/baseupdates folder and renamed them as 01update, 02update, 03update

What did not appear to work was the CustomPKG files, so no clearreg, or admin account(s) created.

Soo…. anybody got any ideas for how to get the clearreg and admin account working?

[nobrainer]

[QUOTE][u]Quote by: Gary+Bernstein[/u][p]I made a little progress yesterday and I thought I should share it.

In instadmg/InstallerFiles/BaseUpdates I was placing all of the updates in individually numbered folders. For instance: BaseUpdates/001/MacOSX10.5.8.ComboUpdate.dmg or BaseUpdates/002/QuickTime7.6.6.dmg, and etc. When I did this I was getting the errors mentioned above. I did this because it was hinted at in the instadmg docs that this was a good way to go and to provide an order to the updates.

I found last night that if I move the files up one level and rename them that instadmg works. For instance: BaseUpdates/001MacOSX10.5.8.ComboUpdate.dmg or BaseUpdates/002QuickTime7.6.6.dmg, and etc.

I was then able to successfully run:

sudo ./instadmg.bash -r -n KCPA-1058 -m KCPA-1058

I am still unable to get InstaUp2Date to run on 10.5.8 and create a 10.5.8 disk image. I get an error about There were no items to install in /private/tmp/InstaDMG_temp_folder.4pYx6b/mount_point.jTh1nO/private/tmp/mount_point.mBDYKi

Thoughts?

Thanks
-Gary[/p][/QUOTE]

I’m kind of at the same point, I renamed my update files and put them all in the base updates folder.. and I was able to run the instadmg.bash -r -n -m and the instadmg script ran through but none of the updates applied, I still have a 10.5.5 OS (instead of 10.5.8)

Checked the debug log, and while it continued on through the whole process… the actual logs showed every addon failed the install…

Install failed: The Installer could not install some files in “/private/tmp/InstaDMG_temp_folder.LWia2J/mount_point.VzhoKv”. Contact the software manufacturer for assistance.
The install failed (The Installer could not install some files in “/private/tmp/InstaDMG_temp_folder.LWia2J/mount_point.VzhoKv”. Contact the software manufacturer for assistance.)

I guess I will try an older instadmg script (this was 1.6rc1, rev: 318).

[nobrainer]

[QUOTE][u]Quote by: Allister[/u][p]Hey there,
Yes, 10.5 is broken with instaUp2Date and has been for some time(many revisions.) Please try your build train with the version in the downloads section of instadmg.googlecode.com(instaUp2Date 250 and instadmg.bash 261) and let us know if you’re still having an issue. One thing I haven’t gotten a chance to test ‘manually'(without instaUp2Date)is, if I disable the chrooted installd daemon with the appropriate flag, can I get it to work with createUser. 10.5 otherwise works with a manual build train as of r300. r303 came out last night/this morning, but does not seem to be related to the 10.5 issues(of which there are a few) and I haven’t gotten a chance to test. Please file a bug for each and every reproducible symptom you’re experiencing at the google code issue tracker. Thanks,

Allister[/p][/QUOTE]

I tried these 2 revisions by acquiring them individually (didn’t see a way to grab an entire rolled up release from those). The instaup2date seems to bomb out, first from the version check (which I then commented out) then from not being able to find updates..

Since I have the patch files downloaded, is there a way to use instadmg to install those manually w/o using instaup2date?

[nobrainer]

[QUOTE][u]Quote by: Gary+Bernstein[/u][p]I made a little progress yesterday and I thought I should share it.

In instadmg/InstallerFiles/BaseUpdates I was placing all of the updates in individually numbered folders. For instance: BaseUpdates/001/MacOSX10.5.8.ComboUpdate.dmg or BaseUpdates/002/QuickTime7.6.6.dmg, and etc. When I did this I was getting the errors mentioned above. I did this because it was hinted at in the instadmg docs that this was a good way to go and to provide an order to the updates.

I found last night that if I move the files up one level and rename them that instadmg works. For instance: BaseUpdates/001MacOSX10.5.8.ComboUpdate.dmg or BaseUpdates/002QuickTime7.6.6.dmg, and etc.

I was then able to successfully run:

sudo ./instadmg.bash -r -n KCPA-1058 -m KCPA-1058

I am still unable to get InstaUp2Date to run on 10.5.8 and create a 10.5.8 disk image. I get an error about There were no items to install in /private/tmp/InstaDMG_temp_folder.4pYx6b/mount_point.jTh1nO/private/tmp/mount_point.mBDYKi

Thoughts?

Thanks
-Gary[/p][/QUOTE]

I tried the sudo ./instadmg -r and I still get

010-07-22 10:54:41.847 defaults[18141:10b]
The domain/default pair of (/private/tmp/InstaDMG_temp_folder.I3oXw1/mount_point.tUFb0d/System/Library/CoreServices/SystemVersion, ProductVersion) does not exist
2010-07-22 10:54:41.857 defaults[18144:10b]
The domain/default pair of (/private/tmp/InstaDMG_temp_folder.I3oXw1/mount_point.tUFb0d/System/Library/CoreServices/SystemVersion, ProductVersion) does not exist
2010-07-22 10:54:41.866 defaults[18146:10b]
The domain/default pair of (/private/tmp/InstaDMG_temp_folder.I3oXw1/mount_point.tUFb0d/System/Library/CoreServices/SystemVersion, ProductBuildVersion) does not exist
2010-07-22 10:54:41.874 defaults[18147:10b]
The domain/default pair of (/private/tmp/InstaDMG_temp_folder.I3oXw1/mount_point.tUFb0d/System/Library/CoreServices/SystemVersion, ProductName) does not exist
./instadmg.bash: line 700: [: 5: unary operator expected
Target OS: ()
Encasing installer daemon in a chroot jail

cp: /private/tmp/InstaDMG_temp_folder.I3oXw1/mount_point.tUFb0d/private/var/log/InstaDMG_package.log: No such file or directory

and then dumps out.

[nobrainer]

[QUOTE][u]Quote by: MichaelR[/u][p]@nobrainer I just downloaded the whole thing. I used this command.

[code]svn checkout http://instadmg.googlecode.com/svn/trunk/ instadmg-read-only[/code][/p][/QUOTE]

I tried that one from this morning, and it’s having trouble with above log captures…

[Author]

Posts