One of the less-recognised benefits of SIP was that it effectively prevented this from happening, although improvements in system installers undoubtedly played their part as well. Disk Utility’s command took its time to fix the problems, and sometimes only a reinstallation sufficed. In those days, repairing permissions required going back and checking installation records for the correct permissions for each system folder and file, which wasn’t something the user could do. It also appeared sufficiently common a problem that it merited its own command in Disk Utility. The effects could be subtle and puzzling, or bring sudden disaster, depending on what exactly broke as a result. This article looks at what we used to do, and wonders how we cope without it now.īefore the advent of SIP (System Integrity Protection), anything that had root access to the files in the system could change their permissions. If you’ve been using macOS for even longer, you’ll remember having to repair permissions on the system (Mark 1). That in itself was repairing permissions Mark 2 anyway. When’s the last time that you repaired permissions on your Mac? Just a few years ago, it had become something of a universal panacea, which Apple recommended as a solution to a long and varied list of problems.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |