Re: Update to 10.5.5

2008-09-16 Thread Peter Fowler



Hello Peter,

In general, run Repair Permissions after installing or upgrading  
software.


To be accurate, it doesn’t actually repair permissions. Rather, it  
simply resets permissions.
Permissions stay the way they are set until someone or something comes  
along and sets them another way.


Extract from 'Take Control of Maintaining your Mac':

In Mac OS X, each file contains information specifying which users(or  
parts of the system) can read it, modify it, or execute it.
This information is collectively known as permissions. If a file has  
incorrect permissions, it can cause applications to misbehave in  
various ways,such as crashing or failing to launch.
Ordinarily, installers set the correct permissions for the files they  
install, and the permissions stay that way permanently.
However, a poorly written installer can mess up permissions—even for  
files it did not install—and if you use Unix commands such as chown  
and chmod,
you can accidentally set files’ permissions incorrectly. These sorts  
of problems occur infrequently, but they do occur.


The Repair Permissions feature looks for certain software installed  
using Apple’s installer, which leaves behind files called receipts  
that list the locations and initial permissions of all the files in a  
given package. Repair Permissions compares the current permissions to  
those listed in the receipts and, if it finds any differences, changes  
the files back.
The command ignores software installed in other ways (using a  
different installer or drag-and-drop installation, for instance) and  
knows nothing about legitimate permission changes you may have made  
deliberately.


Cheers,
Ronni



Cheers Ronnie, Thanks for that ... I will make sure that I do that  
after this next update.


Have I got this right,

Go to utilities, select Macintosh HD, click  Repair Dick Permissions

regards

Peter


-- The WA Macintosh User Group Mailing List --
Archives - http://www.wamug.org.au/mailinglist/archives.shtml
Guidelines - http://www.wamug.org.au/mailinglist/guidelines.shtml
Unsubscribe - mailto:[EMAIL PROTECTED]

-- The WA Macintosh User Group Mailing List --
Archives - http://www.wamug.org.au/mailinglist/archives.shtml
Guidelines - http://www.wamug.org.au/mailinglist/guidelines.shtml
Unsubscribe - mailto:[EMAIL PROTECTED]


Re: Update to 10.5.5

2008-09-16 Thread Robert Howells


On 16/09/2008, at 10:24 PM, Peter Fowler wrote:




Hello Peter,

In general, run Repair Permissions after installing or upgrading  
software.


To be accurate, it doesn’t actually repair permissions. Rather, it  
simply resets permissions.
Permissions stay the way they are set until someone or something  
comes along and sets them another way.


Extract from 'Take Control of Maintaining your Mac':

In Mac OS X, each file contains information specifying which  
users(or parts of the system) can read it, modify it, or execute it.
This information is collectively known as permissions. If a file has  
incorrect permissions, it can cause applications to misbehave in  
various ways,such as crashing or failing to launch.
Ordinarily, installers set the correct permissions for the files  
they install, and the permissions stay that way permanently.
However, a poorly written installer can mess up permissions—even for  
files it did not install—and if you use Unix commands such as chown  
and chmod,
you can accidentally set files’ permissions incorrectly. These sorts  
of problems occur infrequently, but they do occur.


The Repair Permissions feature looks for certain software installed  
using Apple’s installer, which leaves behind files called receipts  
that list the locations and initial permissions of all the files in  
a given package. Repair Permissions compares the current permissions  
to those listed in the receipts and, if it finds any differences,  
changes the files back.
The command ignores software installed in other ways (using a  
different installer or drag-and-drop installation, for instance) and  
knows nothing about legitimate permission changes you may have made  
deliberately.


Cheers,
Ronni



Cheers Ronnie, Thanks for that ... I will make sure that I do that  
after this next update.


Have I got this right,

Go to Applications - utilities - Disk Utility


and start it ,

when it has found the hard drives

 select Macintosh HD,clickRepair Disk Permissions




regards

Peter


-- The WA Macintosh User Group Mailing List --
Archives - http://www.wamug.org.au/mailinglist/archives.shtml
Guidelines - http://www.wamug.org.au/mailinglist/guidelines.shtml
Unsubscribe - mailto:[EMAIL PROTECTED]

-- The WA Macintosh User Group Mailing List --
Archives - http://www.wamug.org.au/mailinglist/archives.shtml
Guidelines - http://www.wamug.org.au/mailinglist/guidelines.shtml
Unsubscribe - mailto:[EMAIL PROTECTED]



-- The WA Macintosh User Group Mailing List --
Archives - http://www.wamug.org.au/mailinglist/archives.shtml
Guidelines - http://www.wamug.org.au/mailinglist/guidelines.shtml
Unsubscribe - mailto:[EMAIL PROTECTED]


Re: Update to 10.5.5

2008-09-16 Thread Mervyn Giuliana Bond

On 16/09/2008, at 6:48 PM, Mervyn  Giuliana Bond wrote:


I have completed an update to 10.5.5. on an intel iMac.
This was followed by running Disk Utility and repair permissions.
The permissions report read as follows:

Repairing permissions for Macintosh HD
Reading permissions database.
Reading the permissions database can take several minutes.

Permissions differ on 
System/Library/LaunchDaemons/com.apple.usbmuxd.plist, should be 
-rw-r--r-- , they are -rwxr-xr-x .
Warning: SUID file 
System/Library/CoreServices/Finder.app/Contents/Resources/OwnerGroupTool 
has been modified and will not be repaired.
Warning: SUID file usr/bin/lppasswd has been modified and will 
not be repaired.

Group differs on private/etc/cups, should be 0, group is 26.
Permissions differ on private/var/spool/cups/cache/rss, should be 
drwxr-xr-x , they are drwxrwxr-x .


Permissions repair complete

Should I be concerned about the two statements commencing with the 
word Warning?


Hello Merv,

These errors can be safely ignored. See this kb article:

http://support.apple.com/kb/TS1448

Nothing is wrong with your system. Apple has changed (again) the 
way Disk Utility behaves. It seems to go through phases: tells us 
things we don't need to know, and can't do anything about, gets 
fixed, then gets all chatty again. It's in an excessively chatty 
phase with Leopard.


You could download the Combo update and run that over the top, it 
normally gets rid of these SUID warnings.

http://www.apple.com/support/downloads/macosx1055comboupdate.html

Cheers,
Ronni


Ronni
I did the combo update as you suggested and then ran Disk Utility.
This time the report read

Repairing permissions for Macintosh HD
Reading permissions database.
Reading the permissions database can take several minutes.

Group differs on private/etc/cups, should be 0, group is 26.

Permissions repair complete

Thank you for your advice.  Truly appreciated.
Merv


-- The WA Macintosh User Group Mailing List --
Archives - http://www.wamug.org.au/mailinglist/archives.shtml
Guidelines - http://www.wamug.org.au/mailinglist/guidelines.shtml
Unsubscribe - mailto:[EMAIL PROTECTED]



--
Science teaches that we must see in order to believe, but we must 
also believe in order to see.


-- The WA Macintosh User Group Mailing List --
Archives - http://www.wamug.org.au/mailinglist/archives.shtml
Guidelines - http://www.wamug.org.au/mailinglist/guidelines.shtml
Unsubscribe - mailto:[EMAIL PROTECTED]


Re: Update to 10.5.5

2008-09-16 Thread Shay Telfer

Ronda Brown wrote:


 On 16/09/2008, at 7:37 PM, Peter Fowler wrote:

 Hi all


 This may sound like a dumb question, but I am new to this game, is 
it normal to run repair permissions after a software update, and 
why?


 regards

 Peter

 Hello Peter,

 In general, run Repair Permissions after installing or upgrading software.

 To be accurate, it doesn't actually repair permissions. Rather, it 
simply resets permissions.
 Permissions stay the way they are set until someone or something 
comes along and sets them another way.

[...deletia...]


IMHO (and that of others) if repair permissions were required after 
the update, Apple's installer would do it anyway...


http://www.tuaw.com/2008/02/25/new-ebook-explains-leopards-permissions/

Have fun,
Shay
--
=== Shay  Telfer 
 Perth, Western Australia   Technomancer  The love of liberty is the love
 Opinions for hire  [POQ] of others; the love of power is
 http://newtonslore.com/fnord the love of ourselves - Hazlitt

-- The WA Macintosh User Group Mailing List --
Archives - http://www.wamug.org.au/mailinglist/archives.shtml
Guidelines - http://www.wamug.org.au/mailinglist/guidelines.shtml
Unsubscribe - mailto:[EMAIL PROTECTED]


Re: Update to 10.5.5

2008-09-16 Thread Paul Kitchener

Shay Telfer wrote:

IMHO (and that of others) if repair permissions were required after the 
update, Apple's installer would do it anyway...


http://www.tuaw.com/2008/02/25/new-ebook-explains-leopards-permissions/

Have fun,
Shay


I had the impression that I should repair permissions, back up, perform 
rites with chickens etc *before* I upgrade.
Happy to be corrected, it's just that I've hardly ever bothered, or been 
required, before or after so I'm unsure of the right way to go.


Also, I'd be interested to know if anyone has comments one way or the 
other on using Combo Updates. People often see these as a better way to 
go. As Rove would say; discuss... :-p


Cheers
Paul

-- The WA Macintosh User Group Mailing List --
Archives - http://www.wamug.org.au/mailinglist/archives.shtml
Guidelines - http://www.wamug.org.au/mailinglist/guidelines.shtml
Unsubscribe - mailto:[EMAIL PROTECTED]