I understand that macOS has its own policies about how various standard Unix directories are used, and that these are (or at least have in the past been) documented in the "File System Programming Guide". I'm about to update to High Sierra (from Sierra) and wonder:
- have these policies changed in any way between 10.12 and 10.13; and
- does the update process force changes (e.g. by enforcing new policies or reimposing old ones that have been customized) in organization or existing permissions.
For example I see that it is no longer possible under 10.13 to chown /usr/local/, and wonder what other changes the update will make to these standard Unix directories in (a) structure, (b) permissions, or (c) my ability to change permissions or organize the directories.
Best Answer
No super big changes on directories is my feeling / opinion.
High Sierra changes very little with respect to SIP protection and you can easily use
lsto read ACL and restricted status protecting from root / super user modification of files.Everything that was changed materially was versions before. High Sierra does introduce APFS and the concept of snapshots and radically more efficient storage and access speeds - but on the UNIX directory level - this is a snoozer of an upgrade.
Your
/usr/localchange is the only one that's notable - you can't get rid of it* but you're free to roam within it and change things to suit your needs.Apple provides additional details about SIP Protected directories.
——
* Of course, you can still get rid of SIP protected files / folders / directories by disabling SIP by doing the hokey-pokey of reboot, disable, reboot, change, reboot, re-enable, reboot (Assuming you want SIP in general but not for this one thing). But then, the next time an OS update comes, your work customizing the OS could (and eventually will) fail since the installer will then put the file back where Apple intended it to be - existing and protected by SIP.