Home › Forums › Software › InstaDMG › Can InstaDMG repairPermissions on the image?

Viewing 12 posts - 1 through 12 (of 12 total)
  • Author
    Posts
  • March 20, 2009 at 10:25 pm #375769
    AllanMarcus
    Participant

    File under feature request, but it would be nice if InstaDMG ran a repairPermissions on the image after install all the software. i don’t know if this is possible, but it would be helpful. When I restore the image I find that I need to run a repairPermissions. For now, I’ll jsut do this in my “onFirstBoot” procedure.

    -Allan

    March 21, 2009 at 12:35 am #375772
    Rusty Myers
    Participant

    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

    March 23, 2009 at 5:35 am #375775
    Patrick Fergus
    Participant

    [QUOTE][u]Quote by: AllanMarcus[/u][p][i]File under feature request, but it would be nice if InstaDMG ran a repairPermissions on the image after install all the software. i don’t know if this is possible, but it would be helpful. When I restore the image I find that I need to run a repairPermissions. For now, I’ll jsut do this in my “onFirstBoot” procedure.[/i][/p][/QUOTE]Whether repair permissions helps or not is discussion for another time (and has been beaten to death in the Tiger days). It [i]can[/i] help in the case of incredibly poorly written installers such as QuarkXPress 6.

    What you’d need is a payload-free CustomPKG that postflights the following:[code]#!/bin/bash

    “$3″/usr/sbin/diskutil repairPermissions “$3″[/code]Haven’t tried the above, but if it’s going to work that probably should do it.

    – Patrick

    P.S. I just re-read what I wrote and the first paragraph was [i]not[/i] written to pick on thespider–it was more meant to try to head off a thread from entering a discussion about the validity of repairing permissions.

    March 23, 2009 at 11:20 pm #375786
    AllanMarcus
    Participant

    Thanks for the idea. As it turns out, even repairing permission on the image once restored to a computer seems to report issues. After repairing permission I ran a verify permissions and I see what is below. Looks like a lof of symlinks where files should be. Any idea on how to resolve these or why they are there?

    Verify permissions for “InstaDMG”
    Reading permissions database.
    Reading the permissions database can take several minutes.

    Permissions differ on “System/Library/CoreServices/Front Row.app/Contents/CodeResources”, should be -rw-r–r– , they are lrw-r–r– .
    Permissions differ on “System/Library/CoreServices/Front Row.app/Contents/PlugIns/DVD.frappliance/Contents/CodeResources”, should be -rw-r–r– , they are lrw-r–r– .
    Permissions differ on “System/Library/CoreServices/Front Row.app/Contents/PlugIns/FRSettings.frappliance/Contents/CodeResources”, should be -rw-r–r– , they are lrw-r–r– .
    Permissions differ on “System/Library/CoreServices/Front Row.app/Contents/PlugIns/FRSources.frappliance/Contents/CodeResources”, should be -rw-r–r– , they are lrw-r–r– .
    Permissions differ on “System/Library/CoreServices/Front Row.app/Contents/PlugIns/Movies.frappliance/Contents/CodeResources”, should be -rw-r–r– , they are lrw-r–r– .
    Permissions differ on “System/Library/CoreServices/Front Row.app/Contents/PlugIns/Music.frappliance/Contents/CodeResources”, should be -rw-r–r– , they are lrw-r–r– .
    Permissions differ on “System/Library/CoreServices/Front Row.app/Contents/PlugIns/Photos.frappliance/Contents/CodeResources”, should be -rw-r–r– , they are lrw-r–r– .
    Permissions differ on “System/Library/CoreServices/Front Row.app/Contents/PlugIns/Podcasts.frappliance/Contents/CodeResources”, should be -rw-r–r– , they are lrw-r–r– .
    Permissions differ on “System/Library/CoreServices/Front Row.app/Contents/PlugIns/TV.frappliance/Contents/CodeResources”, should be -rw-r–r– , they are lrw-r–r– .
    Permissions differ on “System/Library/PrivateFrameworks/BackRow.framework/Versions/A/CodeResources”, should be -rw-r–r– , they are lrw-r–r– .
    Permissions differ on “System/Library/CoreServices/RawCamera.bundle/Contents/CodeResources”, should be -rw-r–r– , they are lrw-r–r– .
    Permissions differ on “Applications/iTunes.app/Contents/CodeResources”, should be -rw-rw-r– , they are lrw-rw-r– .
    Permissions differ on “Applications/iTunes.app/Contents/Frameworks/InternetUtilities.bundle/Contents/CodeResources”, should be -rw-rw-r– , they are lrw-rw-r– .
    Permissions differ on “Applications/iTunes.app/Contents/Resources/iTunesHelper.app/Contents/CodeResources”, should be -rw-rw-r– , they are lrw-rw-r– .
    Permissions differ on “System/Library/PrivateFrameworks/iLifeMediaBrowser.framework/Versions/A/CodeResources”, should be -rw-r–r– , they are lrw-r–r– .
    Permissions differ on “System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/CodeResources”, should be -rw-r–r– , they are lrw-r–r– .
    Permissions differ on “System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/Plugins/BlackAndWhiteEffect.IAPlugin/Contents/CodeResources”, should be -rw-r–r– , they are lrw-r–r– .
    Permissions differ on “System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/Plugins/CubeTransition.IAPlugin/Contents/CodeResources”, should be -rw-r–r– , they are lrw-r–r– .
    Permissions differ on “System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/Plugins/DissolveTransition.IAPlugin/Contents/CodeResources”, should be -rw-r–r– , they are lrw-r–r– .
    Permissions differ on “System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/Plugins/DropletTransition.IAPlugin/Contents/CodeResources”, should be -rw-r–r– , they are lrw-r–r– .
    Permissions differ on “System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/Plugins/FadeThroughBlackTransition.IAPlugin/Contents/CodeResources”, should be -rw-r–r– , they are lrw-r–r– .
    Permissions differ on “System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/Plugins/FlipTransition.IAPlugin/Contents/CodeResources”, should be -rw-r–r– , they are lrw-r–r– .
    Permissions differ on “System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/Plugins/MosaicFlipTransition.IAPlugin/Contents/CodeResources”, should be -rw-r–r– , they are lrw-r–r– .
    Permissions differ on “System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/Plugins/MosaicFlipTransitionSmall.IAPlugin/Contents/CodeResources”, should be -rw-r–r– , they are lrw-r–r– .
    Permissions differ on “System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/Plugins/PageFlipTransition.IAPlugin/Contents/CodeResources”, should be -rw-r–r– , they are lrw-r–r– .
    Permissions differ on “System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/Plugins/PushTransition.IAPlugin/Contents/CodeResources”, should be -rw-r–r– , they are lrw-r–r– .
    Permissions differ on “System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/Plugins/RevealTransition.IAPlugin/Contents/CodeResources”, should be -rw-r–r– , they are lrw-r–r– .
    Permissions differ on “System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/Plugins/SepiaEffect.IAPlugin/Contents/CodeResources”, should be -rw-r–r– , they are lrw-r–r– .
    Permissions differ on “System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/Plugins/TwirlTransition.IAPlugin/Contents/CodeResources”, should be -rw-r–r– , they are lrw-r–r– .
    Permissions differ on “System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/Plugins/WipeTransition.IAPlugin/Contents/CodeResources”, should be -rw-r–r– , they are lrw-r–r– .
    ACL found but not expected on “Applications”.

    Permissions verification complete

    March 24, 2009 at 3:29 pm #375791
    AllanMarcus
    Participant

    Yea, but these are just permissions. These are symlinks that should be files. I followed a few of the symlink and the files are there, but in off directories that begin with an underscore. I just wonder is something that will cause problems for these applications int he long run. I suppose I could write a script to verify permissions, follow each symlink in the resultant list, remove the symlink, then move the original file to the symlink’s position. I suppose someone has to do it.

    I did check a couple of machines not build through an InstaDMG image, and they do not have this symlink issue.

    March 24, 2009 at 6:22 pm #375796
    AllanMarcus
    Participant

    some are in applications. The full paths are in this thread.

    October 6, 2009 at 6:52 pm #377292
    mbezzo
    Participant

    Hi All,
    I’m having similar issues and my repair permissions output is about a mile long with all the changes it’s making. It’s looking like pretty much everything in /System/Library/ has incorrect permissions… This is a new build with 10.5.8 and previous builds didn’t have these permissions issues. Should I be worried?

    Thanks,
    Matt

    October 7, 2009 at 2:23 am #377297
    larkost
    Participant

    I just checked the files on my computers (installed by hand, not an image), and on all of the files at my samples of these locations have been links, just like the files are on your image. It seems to me that these files on the image are correct, but somehow what the “repair permissions” code is looking up is wrong. All of my systems have been the host system for InstaDMG at one point or another, so someone should check this on a clean 10.6.1 system.

    That is solidly worth looking into, but I don’t think that there is a significant problem here. It looks to me like we are missing the data from an update (probably 10.6.1) where things got moved. We have the actual moves, but not the records of them. Does anyone know what “repair permissions” is looking at nowadays? And does anyone want to bet that this data got written to the boot volume? (*sigh*…)

    Now on the subject of “is repair permissions worth running”, I come down solidly on the “no” side. With the exception of some bad behavior with printing a while ago (10.2?) that got fixed that way I have never seen repair permissions turn up, or fix, and valid problems. I have seen it prompt people to find problems where there are none.

    October 7, 2009 at 4:14 am #377298
    larkost
    Participant

    After a little testing, I am not seeing this issue on 10.6.1.

    Ok… I just realized that we could be talking at cross purposes, since in the limited time I have for InstaDMG I am working only on 10.6 (both as host and as target). So, when anyone reports anything, I am going to absolutely need them to give the following information:

    Host OS version
    Target OS version
    Revision number of InstaDMG

    And if you are on less than rev210, I am probably going to just ignore the post altogether (this means it does not get fixed if it is broken).

    October 7, 2009 at 4:14 pm #377301
    mbezzo
    Participant

    You know, I never even thought about the host OS I was buidling from… I’m on 10.6.1 building a 10.5.8 image… Will try on a 10.5 box and see if i get anything different. I bet that’s the issue!

    Thanks,
    Matt

    October 8, 2009 at 12:14 am #377307
    mbezzo
    Participant

    and yes, everything worked just fine once I moved instadmg to a 10.5 box…

    October 8, 2009 at 1:12 am #377308
    larkost
    Participant

    I would like to get back to the point where you can install an older os version from a newer one (specifically 10.5 while booted from 10.6), but the 10.6 installer is killing that at the moment, and I either have to hack my way though the darkness, or Apple has to fix the bugs.

  • Author
    Posts
Viewing 12 posts - 1 through 12 (of 12 total)
  • You must be logged in to reply to this topic.

Comments are closed

Copyright © 2025 AFP548. All Rights Reserved.