Re: OSX 10.5.6 questions

Michael H. Phillips <mhp@xxxxxxxxxxxxx> wrote:

Having got Sheepshaver to work, I've gone from 10.4.11 to 10.5.6 using
Archive & Install.

First question: all applications seem to be working as they should,
preferences intact, so can I safely erase 'Previous Systems' or might there
be essential invisible items hiding there?

I usually delete most of a Previous System straight away. You can
certainly toss the applications (all older version of Apple standard
apps) unless you had done something to patch one of the older versions
which you want to keep.

If I'm bored I go through the rest of it to see if there is anything
else I might have done which I want to keep.

The only non-Apple stuff that might be usefl would be third party kernel
extensions, and some third party stuff in Library which might not have
been transferred to the new system. It is generally better to install
these sorts of things afresh (and preferably a later version known to be
compatible with the new OS version) rather than trying to manually
transfer them from the old system, so your Previous System is more of a
guide to what might be missing.

(I'm assuming you chose to preserve the user accounts in the Archive &
Install. If not, they will be in Previous Systems and you probably don't
want to delete them!)

Second question: I repaired permissions before and after the installation,
but Disk Utility continues to report a host of damaged permissions ("ACL
found but not expected...").

They aren't "damaged permissions". It is a warning message and is a well
known issue with the permission repair reporting spurious things it
can't deal with. Ignore it. Hopefully Apple will fix it at some point to
get rid of the warnings.

I see from articles in Apple Support and Forums that this is benign and
should be ignored, but Disk Utility is taking about 45 minutes to verify
permissions!

Also normal, but partly due to it having to waste time printing the
spurious warnings.

Leopard's Repair Permissions is known to take a lot longer than earlier
systems, due to the additional checks required for access control lists.

I wonder if these ACL violations refer to applications lingering in
Previous Systems and erasing this folder might speed up the verification.

No. Repair Permissions only looks at things referenced by the files in
/Library/Receipts, which refer to installed system software and
applications (in /System, /Library, /Applications and a few hidden
Unix-level folders). It doesn't have anything to do with other top-level
folders (including /Previous Systems and /Users).

If not, is there a method of persuading Disk utility to ignore ACL
warnings?

No.

--
David Empson
dempson@xxxxxxxxxxxxx
.

Relevant Pages

  • Re: Avoid HAL on Ubuntu 10.04?
    ... but is still used for other applications. ... I've yet to figure out the source/meanings of the warnings (I get them ... Maybe you are thinking of the "apt-cache rdepends" command. ... install HAL on the test system, that removed the warning some time, ...
    (Ubuntu)
  • Re: Help with mini mac program instalation.
    ... But it's not in the applications folder and it refuses to ... might have been with a fresh install). ... allow you to modify the permissions. ...
    (comp.sys.mac.advocacy)
  • Re: More before-the-fact advice for 2K and XP?
    ... neither ActiveX nor BHO require Admin permissions to ... given that non-admins have a significant amount of control over ... "Would you like to install the ... With executable white listing, the app doesn't just ...
    (microsoft.public.security)
  • Re: Creating a Restore Disk Image
    ... told me that I needed to run the Disk Utility by booting from the OS X ... That is true if you are repairing the disk, but repairing permissions is ... supposed to be done while booted from the hard drive, not the install ... anything explaining how to use Repair Permissions. ...
    (comp.sys.mac.system)
  • Re: New install of XP
    ... you can set XP Home permissions in Safe Mode. ... Open Explorer, go to Tools and Folder Options, on the view tab, scroll to ... >>Was this a clean install or did you install over a> previous setup? ...
    (microsoft.public.windowsxp.basics)