[dead2sin]

Also, I noticed using 1.5 RC1 that I get crazy dyld shared cache errors when making images. The system log shows that this is playing into the fontd issue. Here is an example:

[code]
ov 9 11:03:57 localhost com.apple.fontd[102]: dyld: shared cached file was build against a different libSystem.dylib, ignoring cache
Nov 9 11:04:23 localhost com.apple.fontd[102]: dyld: shared cached file was build against a different libSystem.dylib, ignoring cache
Nov 9 11:04:24 localhost /System/Library/Frameworks/ApplicationServices.framework/Frameworks/ATS.framework/Support/fontd[102]: ATS is unable to switch to Read/Write database – ATS will run off of a read-only database. Only System Fonts will be available.
Nov 9 14:07:16 netboot003 com.apple.fontd[208]: dyld: shared cached file was build against a different libSystem.dylib, ignoring cache
Nov 9 14:07:16 netboot003 /System/Library/Frameworks/ApplicationServices.framework/Frameworks/ATS.framework/Support/fontd[208]: ATS is unable to switch to Read/Write database – ATS will run off of a read-only database. Only System Fonts will be available.
Nov 9 14:07:52 netboot003 com.apple.fontd[251]: dyld: shared cached file was build against a different libSystem.dylib, ignoring cache
Nov 9 14:07:52 netboot003 com.apple.fontd[251]: dyld: shared cached file was build against a different libSystem.dylib, ignoring cache
Nov 9 14:07:52 netboot003 /System/Library/Frameworks/ApplicationServices.framework/Frameworks/ATS.framework/Support/fontd[251]: ATS is unable to switch to Read/Write database – ATS will run off of a read-only database. Only System Fonts will be available.
Nov 9 14:09:46 netboot003 com.apple.fontd[355]: dyld: shared cached file was build against a different libSystem.dylib, ignoring cache
Nov 9 14:09:48 netboot003 com.apple.fontd[355]: dyld: shared cached file was build against a different libSystem.dylib, ignoring cache
Nov 9 14:09:49 netboot003 /System/Library/Frameworks/ApplicationServices.framework/Frameworks/ATS.framework/Support/fontd[355]: ATS is unable to switch to Read/Write database – ATS will run off of a read-only database. Only System Fonts will be available.
[/code]

Why is there a dyld cache in place if its never been booted? And if it is created, should it not be deleted before the image is finished?

Thanks,

Nate

[dead2sin]

I talked to Akinspe and he said it works with 10.6. My issue was most likely due to the USERDATA file (I reused the USERDATA file from the previous version). I’ll post here if that fixes it for me.

[dead2sin]

Should createUser be working with Snow Leopard now? I just did a 10.6 build and it didn’t make the user account at all =(

Thanks,

Nate

[dead2sin]

[QUOTE][u]Quote by: knowmad[/u][p]well, and this is only a small item, it should work if your building 10.6 on 10.6
I … in a fit of stupidity, am trying 10.6 build with the build machine running 10.5
so… I changed only one of the two items to 10.6
the other I left as 10.5
course I COULD just do away with the check completely and tell it that its running leopard and let it go from there….. that would work too…. and its cleaner.
[/p][/QUOTE]

So should 1.5RC1 work so long as you are building 10.6 images on a 10.6 machine? Or whats the deal?

[dead2sin]

Alright, that command didn’t totally fix the issue. Looking into this some more…

[dead2sin]

I had this issue as well and I have resolved it on my build train.

I am now adding the printers on first boot (first boot script) instead of copying the whole /etc/cups/blah stuff over to the image via a package. This has resolved the issue where it would say I wasn’t in the _lpadmin group and it also resolved an issue I had been having printing in photoshop.

Here is the example I put into my wiki so I wouldn’t forget 😀

[code] lpadmin -p “HiddenSystemName” -L “Location” -D “Display Name”-E -v lpd://olorin/queuename -P “/Library/Printers/PPDs/Contents/Resources/en.lproj/correctppd.ppd.gz”[/code]

Rules for using this command:

-p “HiddenSystemName” cannot have any spaces or symbols in the name. (Underscore _ is acceptable).

-L “Location” Should be a human readable description of the location such as “Computer Lab” or “Pharos Station”

-D “Display Name” Should also be human readable and it can contain spaces. This is what OS X Displays in Printers and Faxes within System Preferences.

-E Enables the printer

-v Specifies the queue name. For our printers, they are all on lpd://olorin/printername.

-P Specifies the print driver. This can be a*.ppd, *.gz or any unix compatible format. Most commonly found in /usr/share/cups/model and /Library/Printers/PPDs/Contents/Resources/en.lproj/

Hope this helps someone else out as well!

Nate

[dead2sin]

Sorry it isn’t working for you guys. I’ll try to help you out in a bit (really busy atm).

Are you using Composer 7?

Nate

[dead2sin]

I’ve sucessfully Packaged CS4 using Composer 7 as well. Here are my directions straight from our Wiki on the topic:

[quote]Packaging Adobe CS4 for InstaDMG

These are directions for packaging Adobe CS4 for use with InstaDMG Only. You cannot use this method if other adobe products are already installed, it will totally pooch them.

Acrobat 9 Pro Articles found on Google and modified for our purposes.
[edit] Make Package using Composer 7

The first step is to make the install package using Composer 7. You will want to mount all the DMGs of the software you want to install and have the serial #s ready. (Photoshop, InDesign, Illustrator, Dreamweaver, Flash and Acrobat 9 Pro).

In Composer 7, you will click follow these steps:

1. Open Composer 7, authenticate, and select “New Package”
2. Chose the “New & Modified Snapshot” method for creating the package.
3. Composer will make a snapshot of all the current files and modified dates. This will take a few minutes.
4. After it finishes the SnapShot, install all the applications you would like to have in the package.
5. Open both Acrobat 9 Pro and Distiller so they self-heal. (You might need to open the 2x for this to work correctly).
6. Click “Build Package” in Composer and it will create another snapshot, compare them and put the files that were changed into the package.
7. Take the file from”/Users/currentuser/Library/Preferences/com.adobe.acrobat.90.sh.plist and add it to /System/Library/User Template/English.lproj/Library/Preferences/
8. Add the registration files into the same User Template directory as the previous step (I normally get these by building the CS4 package and then making another Composer Package to capture the registration files).
9. Look through the files that are in the package and remove the kruft (unnecessary files). Common examples are samba logs, apple remote desktop related things, etc.
10. Now that you have the install done and have cleaned up the files that it installs, you must follow the rest of the steps in this wiki article.

[edit] Suppressing Self-heal – Acrobat 9 Pro and Distiller

Found here:

itmac.wordpress.com/2008/12/09/adobe-acrobat-admin-password-self-heal-problems/

NOTE: This can only be used if you are packaging this with Composer or something similar. This will only work in the situation mentioned at the top of this article.

Adobe CS and Acrobat Pro/Reader are unfortunately not the easiest applications to deploy in IT, on either the Mac or PC. A common problem is having general users receive a query for administrator credentials when they open Acrobat after installation. This is caused by Adobe Acrobat running through a “Self Heal” procedure when it’s opened. Many times it’s caused by Acrobat wanting to become the default PDF reader for Safari.

You can minimize the chance of this happening by modifying the Self Heal XML file that is created after installing Acrobat. Please note that this IS NOT RECOMMENDED by Adobe, but seems to be the a common modification amongst IT departments rolling out Acrobat. The file to edit is /Library/Application Support/Adobe/Acrobat/AcroEFGPro90SelfHeal.xml (for Adobe Acrobat Pro – Reader may have a slightly different name/location. A quick summary of changes made to the XML file:

Change the string of “YES” to “NO“
Change the string of “REQUIRED” to “NO“

Depending on the flavor of Acrobat, you may also see a “FIRST RUN” value as well. This value should also be changed to “NO“. These changes are case sensitive. Also note you will see the “required” key in lower case letters many times in the XML file. These should not be changed. Only the strings previously mentioned should be changed, and they are always capitalized.

Sometimes you will continue to receive the admin username/password request even after modifying the self heal XML file. To remedy this, I’ve found that logging in under a clean admin account, configuring the Adobe Acrobat Pro/Reader preferences as desired, will result in the following .plist files being modified in ~/Library/Preferences.

com.adobe.acrobat.90.sh.plist
com.adobe.acrobat.pdfviewer.plist
com.apple.LaunchServices.plist

If you’re in the image creation process when doing these configurations/testing, you can copy these preference files to the /System/Library/User Template/English.lproj/Library/Preferences directory, and once your image is complete, new users who login to the system will receive these modified prefrence files by default. You could also deploy these changes in .pkg file, and have a script copy these preferences to the User Template and existing user home directories. The Casper Suite allows you to build specialized packages that can deploy these changes to both the User Template and existing user directories, if needed. Although I haven’t tried, I would guess these preferences could also be managed by MCX/Workgroup Manager if you have your Macs bound to an Open Directory server and are managing them in that manner.

Click here for a .pdf of the Self Heal XML file. Feel free to try it out, modify, and use if needed. This is the self heal file for Adobe Acrobat Pro 9. Those for Reader and version 8 of Acrobat Pro are different, so don’t try and use this one. Instead, compare the changes made on this file and apply to yours as needed. Good luck.

This must also be done for the Distiller Self-heal file. It should be called AcroENUDist90SelfHeal.xml.[/quote]

On my Packages, I choose to disable all self healing since I capture what the self heal does anything by opening both acrobat and Distiller before building the package.

Hope that Helps!

Nate

[dead2sin]

Hrmmm, that definitely sucks. Perhaps you could pull a Woz and convince them that its worthless to them like he did with HP? 😀

Who else works on this project besides you? Perhaps we could get a post going asking for people to help contribute (preferably people that are good at scripting). I would like to help, but I am a scripting noob. I look at your scripts and it takes me a while to figure out whats going on. I’d love to help design an interface for it though, that is something I believe I could help with. I would be willing to learn how to script better as well, but I’m simply not good at it right now.

Either way, I think that you/we should figure out a way to keep this going. I REALLY like InstaDMG and I would HATE to have to move to a product that is inferior and also costs $500+.

Just a few thoughts,

Nate

[dead2sin]

I’ve always had speed issues with the office updates (specific parts would hang) so I’ve started repackaging Office 2008 with all the updates. This makes my images build faster and I *know* its updating correctly. I use Composer 7 for it.

Hope that helps,

Nate

[dead2sin]

Is InstaDMG GPL’d? If it is, shouldn’t that protect it from the company regardless? They can’t claim ownership of something thats already been GPL’d.

I’m sad to see this happen because I love using InstaDMG. I’m using 1.4b4 for my leopard images and its been working great. I tried using Casper Imaging Suite and didn’t care for it (not very straight forward). I hope someone can take the reigns of this and keep it going. InstaDMG is an invaluable tool.

Thanks for all the work you’ve put into your project!

Nate

[dead2sin]

I had the same issue.

It turns out the issue has to do with generating the shadow hash. If you have any symbols in your password, you MUST escape the symbols when you generate the hash.

Example:

p@ssword

needs to be

p\@ssword

If you don’t escape the ! it will stop at the T and the hash won’t match what you want the password to be.

So a backslash before each symbol within the password: p\@ssword\!

Hope that helps!

Nate

[dead2sin]

btw, I noticed that with ilife support 9.0.3, if you install iLife 09 AFTER you install the support 9.0.3 package, it overwrites it with iLife Support 9.0.0. I fixed this by adding the 9.0.3 package to the end of my DeployStudio Workflow and it worked fine.

If I install iLife08 after install the support 9.0.3 package, it works fine.

As for iLife08 and iLife09 themselves, I always use composer with the new and modified snapshot in order to make a fully updated package.

Nate

[dead2sin]

The easiest solution I found for this issue is this:

I installed a fresh copy of 10.5 on my machine and installed only one update (10.5.7). Everything else I ignored. In fact, I turned off auto download for software updates so it wouldn’t bug me. Also, I deleted the receipts for anything that had caused me issues in the past.

As a result, I’ve been able to install iLife 9.0.3 Support as well as Safari within my workflow.

A note about the 9.0.3 update, if you install 9.0.3 support before iLife 09, iLife 09 will blow away the update and you’ll need to reapply it. Kind of a pain, so I just threw the 9.0.3 update at the end of my DeployStudio workflow and it works like a charm.

Hope that helps =)

Nate

[dead2sin]

[QUOTE][u]Quote by: larkost[/u][p]It looks like your base image is read/write. The second line in your log is it failing to checksum the base image (and then not mounting it). At this point the image must be read-only (a safety precaution). You did find a bug in that the process should have stopped cold at that point. I have just checked in a bug-fix for that (rev210).[/p][/QUOTE]

Sounds good. My Mac OS X Install DVD image is a DVD/CD Master, which as far as I know is read only. I used the same exact image with version 1.4b4. Is it a change in the newer code where it checks for read-only before proceeding?

Thanks,

Nate

[Author]

Posts