- This topic has 2 replies, 2 voices, and was last updated 15 years, 2 months ago by
chrisb.
-
AuthorPosts
-
February 8, 2010 at 8:19 am #377957
chrisb
ParticipantHello,
I’ve been going through the process of creating an image using InstaDMG. I started out small with creating an image with just the OS X Snow Leopard install disk and a simple installerchoices.xml (popular print drivers, QT7, and rosetta) and that worked fine, than I moved onto doing it with 10.6.2, than a third time with the clearreg.pkg and createuser.pkg and was able to have a normal booting image both times.
My current issue is this:
Our image requires 2 default accounts, I read in one thread ([url]https://www.afp548.com/forum/viewtopic.php?forum=45&showtopic=26045&highlight=createuser[/url]) that renaming a second createuser.pkg along the lines of ‘createUser (nochroot).pkg’ works (I tried editing the bash file also as suggested in that thread but received errors when trying to run instadmg.bash). My 4th image I created consisted of the clearreg, and the 2 createusers in 3 folders in the customPKG folder, and the 10.6.2 combo update, the latest security updates, java update 1, along with the packages for the updates of iphoto, safari, itunes, and ARD client. (in that order)
Building this image presented a TON of permission issues that were “repaired” in the instadmg.bash process, however when I tried to boot to the newly deployed image, the computer (aluminum imac) just sat at the apple logo with the spinner until i restarted the computer (at one time i gave it over 30 minutes).
After this i narrowed the updates down to just 10.6.2, java, and the security updates. Again presented many permission issues that were “repaired” but still not bootable.
My last attempt I created an image with the same 3 packages in customPKG and only the 10.6.2 combo update. The only issue that was presented was the the “Library” had incorrect permissions that was “repaired.”
Now this image booted up each time I attempted it. However it sits at the apple logo and spinner for ~30 seconds before the login screen is presented after each reboot.
Basically what I am getting at, is anyone else having issues creating Snow Leopard images with the latest Updates and multiple accounts, or am I just doing something completely incorrect?
Thank You,
ChrisFebruary 10, 2010 at 4:32 am #377970larkost
ParticipantA big problem with the current createuser system is that you wind up reusing the same package id (CFBundleIdentifier) for each one you use. The installer can get a bit particular about this and will start deleting things from the first one when you install the second if you don’t change the package id of the second. Compounding that is how the packages don’t work under the chroot tricks I have to pull for 10.5 (and wish I could pull for 10.6). I have started and abandoned a few replacements, and will try again for something that works a bit better in this regard.
For the moment I would do two things:
1) In the second pacage open it back up and change the “CFBundleIdentifier” (in PlistEditor this will be the “Bundle identifier” line) to something other than “edu.uc.daap.createuser.pkg”. In the example below I use “edu.uc.daap.createuserNumberTwo.pkg”)
2) Change the line that looks like this:
[code]CHROOT_EXCLUDED_CODES=(“edu.uc.daap.createuser.pkg”)[/code]
to something like this:
[code]CHROOT_EXCLUDED_CODES=(“edu.uc.daap.createuser.pkg” “edu.uc.daap.createuserNumberTwo.pkg”)[/code]note that there is a space, and nothing else between those two entries.
Additionally, please always post the following information when asking for help:
1) The version of the OS you are running
2) The version of the OS that you are installing
3) The version (including revision) of instaDMG you are runningWithout those bits it can be difficult to figure things out that seem obvious to me.
February 11, 2010 at 6:25 pm #377973chrisb
ParticipantThank You for the reply.
I apologize for the lack of information. I am running 10.6.2 and building a 10.6.2 image. My InstaDMG version must have been a little old. I updated from google code and in a round about way I was able to eliminate all of those issues without any permission issues. As of now I have a booting/working 10.6.2 image with updated security, java, and 2 user accounts.
-
AuthorPosts
- You must be logged in to reply to this topic.
Comments are closed