Forum Replies Created
-
AuthorPosts
-
August 27, 2009 at 9:12 pm in reply to: Anyone else having issues with iTunes 8.2.1 in InstaDMG? #376986
blake
ParticipantInstalling the iTunes components individually didn’t resolve the issue. I just pulled the iTunes 8.2.1 update from our build. Sounds like iTunes 9 will be showing up in the next few weeks. Hopefully that installer will just work.
Blake
August 26, 2009 at 11:34 pm in reply to: Anyone else having issues with iTunes 8.2.1 in InstaDMG? #376983blake
ParticipantI decided to go for the nuke and pave approach here..
Started with a completely different system to build the image and updated it all the way to 10.5.8 Server + all available updates. Downloaded the latest instadmg r211 from svn. Re-downloaded all the updater pkgs fresh from apple and populated the intsadmg updates tree. Copied in a known good retail 10.5.4 installer dmg. When I build this I get a workable image with all the updates installed!I also have the _usbmuxd errors spewing all over the system.log. Fixing this after the restore is not an option for us. I’m now attempting a build by installing the individual .pkg’s inside the iTunes.mpkg. If that doesn’t work I’m pulling iTunes out of our image for now.
Blake
August 24, 2009 at 9:36 pm in reply to: Anyone else having issues with iTunes 8.2.1 in InstaDMG? #376948blake
ParticipantI’m also seeing iTunes 8.2.1, Quicktime 7 & AirPort Utility fail to install with these errors.
[code]
installer[82217]: Install failed: The following install step failed: run preflight script for AirPort Utility. Contact the software manufacturer for assistance.
installer: The install failed (The following install step failed: run preflight script for AirPort Utility. Contact the software manufacturer for assistance.)
installer[82424]: Install failed: The following install step failed: run preflight script for QuickTime 7. Contact the software manufacturer for assistance.
installer: The install failed (The following install step failed: run preflight script for QuickTime 7. Contact the software manufacturer for assistance.)
installer[83355]: Install failed: The following install step failed: run preflight script for Apple Mobile Device Support. Contact the software manufacturer for assistance.
installer: The install failed (The following install step failed: run preflight script for Apple Mobile Device Support. Contact the software manufacturer for assistance.)
[/code]Host OS is 10.5.7 Server and Instadmg 1.5rc r210
blake
ParticipantAnybody have problems with Console.app not being the current version (10.5.6) after building an image? We are using retail 10.5.4 + 10.5.8 combo updater and the result image has Console.app 10.5.0 which is the version that comes with 10.5.4.
I’m working through the usual process for double checking our build. However can anybody with a image built from 10.5.4 or older intall dmg check their 10.5.8 image for the Console.app version?
Thanks,
Blakeblake
ParticipantI’m fairly sure that changing the volume name after the image is created requires you to convert it to a read-write image first. Changing it at creation time is as simple as using the -n argument with the desired volume name.
blake
blake
ParticipantOne of my test build stations uses a 3 disk raid 0 for the builds. I’m not convinced that using a raid 0 is all that useful. Now that using the -t option for redirecting temp files is working again I plan on testing with 2 disks. Splitting the temp files and rest of the data between separate disks. If speed is a real concern get one of those 15K rpm 300GB SAS disks. I highly recommend getting applecare on the system. We have seen a high rate of failure with those on Xserve systems. Looks like you also need the raid card option for the mac pro as well.
Blake
blake
ParticipantI’m working on Snow Leopard. We gotta nail down our image building process before the WWDC build comes out. Looks like I’m sticking with 1.4b4 and some clean up scripting on boot to get that image done. Hopefully next week we can sort out a way to report InstaDMG issues with Snow Leopard and maintain the required NDA.
Also I would say that r200 is working well with Leopard. I reviewed the debug.log and my custom packages are being installed properly using the chroot jail.
Blake
blake
ParticipantOk so the issue is resolved by using 10.5.7 as the host OS and using a 10.5.4 installer DVD image. The 1.4b4 version however works as expected.
blake
ParticipantGot a different error this time after deleting the cached dmg.
[code]
15:52:41 ###### Beginning Update Installs from ./InstallerFiles/CustomPKG ######
Working on folder 01 (15:52:41)
Copying folder ./InstallerFiles/CustomPKG/01 into the target at /private/tmp/package.KKF79q
Installing firstboot0.8.pkg from ./InstallerFiles/CustomPKG/01 (01) inside a chroot jail
/Volumes/files/instadmg/instadmg.bash: line 786: 37143 Bad system call /usr/sbin/chroot . /usr/sbin/installer -verbose -dumplog -pkg “$CHROOT_TARGET/$TARGET_FILE_NAME” -target /
Removing the copied folder: /private/tmp/mount_folder.aLtWjV/mount_point.0JTCWs/private/tmp/package.KKF79q
Folder 01 done (15:52:47)
[/code]blake
ParticipantI put our scripts into the /Library/Scripts directory and start them with a launchd plist that’s appropriate for the task. These are easily collected into a .pkg that can be added to your InstaDMG process.
If you are not familiar with lanchd plists grab a copy of lingon http://tuppis.com/lingon/ to make the plist.
blake
blake
ParticipantYou want to avoid DHCPv6 in my opinion. The stateless auto-configuration is done by the client and router discovering each other using neighbor discovery. You router will provide your prefix and the computer will generate the last part of your IPv6 address. This works well and doesn’t require DHCP or any other parts besides the router and the host.
You should go get as current of firmware as you can get your hands on for the cisco router and see what options it provides. As for DNS over IPv6, you need to make sure you DNS server can actually deliver dns requests via IPv6. Don’t assume things automatically work with IPv6. I recommend you focus on getting basic IPv6 routing up and running then start looking at the DNS parts.
I would look at the “Well-know anycast address approach” listed in the RFC. Ideally OS X will attempt to use these addresses for DNS automatically. I haven’t tested this yet myself tho. Otherwise you may need to manually enter the IPv6 address of your DNS server into the control panel. I’m just letting all my DNS queries go over IPv4 while the rest of the traffic uses IPv6 when it can.
Blake
blake
Participanthttp://www.theonion.com/content/video/apple_introduces_revolutionary
You will need to use the included custom build of 10.5.6 of course…
🙂
blake
ParticipantThat’s totally what’s happening here. A second script we use has already created the folder first and stuck a launch agent in it..
Without knowing when the home directory is created during the boot process it would be fairly difficult to know exactly when you can change any files in it. I may re-work this script to let OS X create the home directory if I can sort out the timing, configuring localization & if it correctly sets up the dock on OS X server..
Thanks for the info Patrick!
blake
ParticipantAt the root of the home these directories are missing…
Documents
Movies
Music
Pictures
Public
SitesA good number of files from the ~/Library folder are also missing. Doesn’t look like anything very critical but OS X doesn’t clone out the files from /System/Library/User Template/Language.lproj for you.
blake
ParticipantDid a quick test skipping the creation of the home directory. When you login it does create a home directory and populates some of the files but not the full set you see normally.
-
AuthorPosts
Recent Comments