[Rusty Myers]

[QUOTE][u]Quote by: mgb123[/u][p]Rusty, actually, in the end I just used Composer to snapshot it.

[/p][/QUOTE]

What version of Composer were you using? I tried with version 5.1 but keep getting “An exception of class NilObjectException was not handled. The application must shut down”

[Rusty Myers]

Thanks for the update!

Here’s what I’m seeing, using InstaUp2Date:

**Just the first few updates shown, but each package that gets installed shows the same things.**

16:29:44 ######InstaDMG build initiated######
16:29:44 ######Mounting Mac OS X installer image######
Mounting the shadow file (/tmp/D6E519D1-5083-479E-9F4E-257C7FBB5BD0.dmg) onto the image.
Mac OS X installer image mounted
Running from cached image (./Caches/BaseImageCache/226663A2:76393a32d3ca132914acd4e16543f4a71561f650.dmg)
16:30:43 ######Beginning Installation from ######
Using Cached image, so skipping OS installation
16:30:43 ######Beginning Update Installs from ./InstallerFiles/BaseUpdates######
Installing MacOSXUpdCombo10.5.7.pkg from ../../Caches/InstaUp2DateCache/MacOSXUpdCombo10.5.7.dmg (1) using a chroot environment
mount_hfs: No such file or directory
Installing MacOSXUpdCombo10.5.7…..
Installing QuickTime76_Leopard.pkg from ../../Caches/InstaUp2DateCache/QuickTime76_Leopard.dmg (2) using a chroot environment
2009-05-19 13:57:57.702 installer[66315:3e03] *** -[IFRunnerProxy requestKeyForRights:askUser:]: unrecognized selector sent to instance 0x57525a0
2009-05-19 13:57:57.704 installer[66315:3e03] *** Terminating app due to uncaught exception ‘NSInvalidArgumentException’, reason: ‘*** -[IFRunnerProxy requestKeyForRights:askUser:]: unrecognized selector sent to instance 0x57525a0’
2009-05-19 13:57:57.705 installer[66315:3e03] Stack: (
12086672,
9860332,
12115800,
12109140,
12109800,
1279280,
1300308,
1285300,
3808624,
7811272
)
Installing AirPortUtility.pkg from ../../Caches/InstaUp2DateCache/AirPortUtility.dmg (3) using a chroot environment
2009-05-19 13:58:07.376 installer[66369:3e03] *** -[IFRunnerProxy requestKeyForRights:askUser:]: unrecognized selector sent to instance 0x57519f0
2009-05-19 13:58:07.378 installer[66369:3e03] *** Terminating app due to uncaught exception ‘NSInvalidArgumentException’, reason: ‘*** -[IFRunnerProxy requestKeyForRights:askUser:]: unrecognized selector sent to instance 0x57519f0’
2009-05-19 13:58:07.379 installer[66369:3e03] Stack: (
12086672,
9860332,
12115800,
12109140,
12109800,
1279280,
1300308,
1285300,
3808624,
7811272
)
Installing AirPortClientUpdate2009001.pkg from ../../Caches/InstaUp2DateCache/AirPortClientUpdate2009001.dmg (4) using a chroot environment
2009-05-19 13:58:30.663 installer[66421:3e03] *** -[IFRunnerProxy requestKeyForRights:askUser:]: unrecognized selector sent to instance 0x5794fe0
2009-05-19 13:58:30.665 installer[66421:3e03] *** Terminating app due to uncaught exception ‘NSInvalidArgumentException’, reason: ‘*** -[IFRunnerProxy requestKeyForRights:askUser:]: unrecognized selector sent to instance 0x5794fe0’
2009-05-19 13:58:30.667 installer[66421:3e03] Stack: (
12086672,
9860332,
12115800,
12109140,
12109800,
1279280,
1300308,
1285300,
3808624,
7811272
)

Don’t know if the image works, or if those are errors, but it’s different from what i expected so I posted it.
Rusty

[Rusty Myers]

Good question.

I think that if you call all the scripts from the launchd, it will run them at the same time. This may be perfect in your situation.

I run three scripts that I have the computer reboot between each. The first one sets the date/time and some other minor changes. Then it sets the launchd item for the second script and reboots. The second script names the computer, using Bombich’s set-names script, then installs the launchd item for the third script and reboots. The third script then binds the computer to AD/OD and reboots. So, In my case, I want to reboot between scripts and putting them all together wouldn’t work in the way I have them built.

I’d like to get away from these scripts and move to Puppet for management. It seems like it will be easier to set machines up once the Puppet system is configured.

Rusty

[Rusty Myers]

I agree with blake. Here’s what I do.

Install script, lets call it “startup.sh” in /Library/Scripts/”myOrganization”/

I use a very simple launchd item that starts the script as root at first boot (I made my first few launchd items with Lingon). It’s called myOrganization.startup.sh and put into /Library/LaunchDaemons with these contents:

[code]

Disabled

Label
myOrganization.startup
ProgramArguments

sh
/Library/Scripts/myOrganization/startup.sh

RunAtLoad
[/code]

Make sure the launchd item is owned by root and the group is wheel. The permissions MUST be owner: read+write, group: read only, other: read only.
Lingon makes this very easy, but package maker has bit me a few times when packaging.

Post your results!
Rusty

(Edited by Patrick Fergus, 2:52 p.m. 5/18/09. Forum was eating your XML tags–I put it inside code tags)

[Rusty Myers]

Those darn html tags!
[url]http://instadmg.googlecode.com/svn/trunk/AddOns/InstaUp2Date/CatalogFiles/vanilla.catalog[/url]

[Rusty Myers]

Try the date command:

http://www.ss64.com/osx/date.html

[Rusty Myers]

Thanks Hannes,

I’m just now getting into Puppet. This script will help out. I may deconstruct it, since some of my packages are from other programs than packagemaker.

Rusty

[Rusty Myers]

Puppet may help to maintain the correct favorites.
http://reductivelabs.com/

[Rusty Myers]

You can install it into the UserTemplate directory so that when a new user is created, it will already be in the new user’s home folder.

/System/Library/UserTemplate/English.lproj/Library/Favorites/

Or create a script to copy it to the home folder.
Rusty

[Rusty Myers]

I’ve partitioned my drive in three, one for package creation, one for package testing, one images. I start by making an image of the first partition, then I clone that to the other two partitions. Finally, I copy the disk images to the third partition. So I can build images on partition 1, test on partition 2, then boot into partition 3 to image partition one and two. Works, but a pain in the rear. I would really, really, really like to be able to virtualize the OS. Would make it so much simpler!
Rusty

[Rusty Myers]

Did you use Packagemaker?
Rusty

[Rusty Myers]

I’ve seen this too. I haven’t taken the time to care, yet.

The createUser package, I don’t think, creates a home folder. I don’t see it in the code.

I have the some of the same files missing as you. So I’m thinking that one of the packages is creating the home folder from a package. My accounts are the same that I make with createUser and I package apps with. I have used composer, pkgdiff, and packagmaker packages. I’m guessing that within one of the packages there is a home folder created with that account name.

The system needs the Library folder, so it creates that, if nothing else has. I’d be willing to bet the Desktop folder is the same. Not sure about Downloads, maybe it’s needed?

Do you have any packages that could install something to that “users” folder?

Rusty

[Rusty Myers]

I don’t know about during the build, but after the build, I set this:

#Set hostname
hostName=InstaDMG
/usr/sbin/scutil –set ComputerName $hostName
/usr/sbin/scutil –set LocalHostName $hostName

Perhaps adding $3 somewhere will help?

[Rusty Myers]

What needs repaired?

I’m here thinking that when the packages get installed, they set the permissions they need and place a receipt with those permissions. Then if you run repair permissions, it looks at those receipts and set the permissions according to them. If the instadmg image has never been run, then the permissions would have to be the same as the receipts permissions, right?

Rusty

[Rusty Myers]

Ok, so I removed all the base updates and custom packages and built an image, that worked. So I decided to add in all the base updates, that worked. I was sure it was a custom package at that point, so I was expecting the image creation to fail after I added all my custom packages back. Nope, it worked fine.

I am now really stumped, but I don’t care. As long as I’m building images, I’m content. So, if anyone else has this issue, please let me know what you think the problem was, or how you fixed it. Thanks!

Rusty

UPDATE

Well, It looks like the disc image created is not bootable? I restored it to my internal hard drive partition and it wouldn’t show as a boot option in system prefs. So I’m back to removing the updates and testing the base image boot-ability.

[Author]

Posts