Talk:Repair permissions

Skip to table of contents

This is the talk page for discussing improvements to the Repair permissions article.
This is not a forum for general discussion of the article's subject.

Put new text under old text. Click here to start a new topic.
New to Wikipedia? Welcome! Learn to edit; get help.

Article policies

Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL

This article was nominated for deletion on 21 April 2009 (UTC). The result of the discussion was keep.

Computing: Software

	This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing articles
???	This article has not yet received a rating on the project's importance scale.
	This article is supported by WikiProject Software.

Apple Inc. Mid‑importance

	This article is within the scope of WikiProject Apple Inc., a collaborative effort to improve the coverage of Apple, Mac, iOS and related topics on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.Apple Inc.Wikipedia:WikiProject Apple Inc.Template:WikiProject Apple Inc.Apple Inc. articles
Mid	This article has been rated as Mid-importance on the project's importance scale.

Untitled

Wasn't this a separate utility in Mac OS X 10.1? I believe it was called "Repair Privileges". I think this article could mention that as a historical fact and perhaps link to OS X 10.1. 58.107.191.210 08:32, 16 November 2007 (UTC)[reply]

Embed as inline citations

The following external links look more suitable to be embedded as inline citations. WLU (t) (c) Wikipedia's rules:^simple/_complex 11:09, 5 May 2009 (UTC)[reply]

Repairing permissions: What you need to know Macworld's Dan Frakes attempts to provide a thorough, balanced look at repairing permissions
Repairing Permissions is Useless Unsanity's Rosyna tries to educate mac users about repairing permissions.
‘Repair Permissions’ Is Not a Recommended Step When Applying System Updates John Gruber questions the practise of repairing permissions.
Seriously, ‘Repair Permissions’ Is Voodoo Repairing permissions is declared to be voodoo.
Troubleshooting permissions issues in Mac OS X Apple document on troubleshooting permissions issues
About Disk Utility's Repair Disk Permissions feature Apple document on Disk Utility's repair disk permissions feature
Care and Feeding of Jaguar: OS X Drive Maintenance Arguments for repairing permissions regularly

External links modified

Hello fellow Wikipedians,

I have just added archive links to one external link on Repair permissions. Please take a moment to review my edit. If necessary, add {{cbignore}} after the link to keep me from modifying it. Alternatively, you can add {{nobots|deny=InternetArchiveBot}} to keep me off the page altogether. I made the following changes:

Added archive https://web.archive.org/20040626052051/http://developer.apple.com:80/documentation/Security/Conceptual/Security_Overview/Concepts/chapter_3_section_9.html to https://developer.apple.com/documentation/Security/Conceptual/Security_Overview/Concepts/chapter_3_section_9.html

When you have finished reviewing my changes, please set the checked parameter below to true to let others know.

This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template {{source check}} (last update: 5 June 2024).

If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—^{cyberbot II}_{Talk to my owner:Online} 09:06, 12 January 2016 (UTC)[reply]

Permissions repair in El Capitan

There is no real reference to how permission repairs are conducted in El Capitan. There remain a number of situations in which it is appropriate to command a permission repair, even with the system integrity protection running.

The syntax for a repair (as before, there is no real point to running a 'verify' alone in any Mac OS X permissions-repair utility) is as follows: From a Terminal window, enter

sudo /usr/libexec/repair_packages --repair --standard-pkgs /

to perform permissions repair on the root. Instead of the last backslash, you can specify

-- volume PATH

(where you specify the full path to the volume involved) if you want to repair permissions on a particular device that has a bootable copy of OD X installed on it. e.g. if you are troubleshooting a system on a remote machine or you've booted from a recovery partition or device such as a USB stick.

The current description in the article itself appears to follow Apple propaganda in that 'no permissions repair is needed' and that the system will maintain itself properly with the designed-in utilities. That appears to be far from the truth in an interestingly large range of circumstances, and I think it is appropriate to describe the method that users can employ to run the permissions repair correctly. (Someone knowledgeable can compare the usual manpage for this, describe what the individual arguments do and why they are constructed as they are, etc.)

This particular syntax is reported from an article in MacObserver, but there are multiple places on the Web that provide it or a similar version. 2602:306:36CF:2950:589B:5D82:7002:1526 (talk) 02:14, 25 January 2016 (UTC)[reply]