Mac OS X | Desktop Enhancements | Themes | SafariNoBrush | Permissions Problems

SafariNoBrush

Removes brushed metal style from Safari

Version: 1.22

[ Views: 805 ]

Permissions Problems

Feedback Type: Review

Contributed by: FredericoR Tuesday, June 24 2003 @ 07:25 PM PDT

Product Platform: MacOSX

Used Product For: Have Not Tried

Recommend Product: YES

For those of you seeing the 'can't copy 'xxx' file' error, it is due to a permissions problem with the application; i.e., if the Safari installation is owned by 'system', and not the current user (admin or otherwise), SafariNoBrush will return the aforementioned error. The solution is to login as root and rerun the application, or, or, simply duplicate the Safari Application and run SFNB on it, or, not as safe, change the permissions using Get Info for the folder Safari->Contents->English.lproj and its entire enclosed contents. I do not advise the latter. The difference in experience for those who are successful, and not logged in as root appears to be the difference between dowloading the standalone installer and using Software Update; SU sets ownershipt to root (system), while the standalone seems to set ownership to the user (or at least allows others to Read & Write). HTH -- Frederico

Overall Rating:

Ease of Use:

Support:

Features:

Quality / Stability:

Price:

1 of 1 users found this helpful.

Rate this Review

Was this Review helpful? Yes | No

Comments

Permissions Problems - RAngol

There isn't exactly a permissions "problem." Safari 1.0 is owned by root as is I.E. All you do is use 'sudo' for the geek gifted and change owner to your admin or use XRay if you're a non-geek to do the same. Presto. You can do whatever you want. Save a copy of the "original Safari" with your other important saved installers/updaters. Solves this non-problem rather quickly should a future updater prefer the original spread.

Reply to This

Thursday, June 26 2003 @ 08:10 PM PDT

Permissions Problems - FredericoR

I didn't meant to imply that the permissions problems were with Safari, but with SafariNoBrush's inability to apply changes due to its lack of authorization, or, rather, its apparent oversight in predicting it as a problem.

Thanks for the comment and opportunity to clarify.

Reply to This

Thursday, June 26 2003 @ 10:49 PM PDT