Sharing & Permissions question

[kirkbross]

I was messing around with folder permissions trying to make some folder available to some users and not others on my Mac Pro running Lion.

In the list with Name and Privilege, I ended up with two "everyone" Read & Writes and can't delete either one because the minus sign is grayed out. How do I delete one or reset it to it's original defaults and start again?

Question 2: do I need the 'everyone' user in this area?

 

[Alameda]

First step would be to run Disk Utility and Repair Permissions.

 

[Bear]

I was messing around with folder permissions trying to make some folder available to some users and not others on my Mac Pro running Lion.

In the list with Name and Privilege, I ended up with two "everyone" Read & Writes and can't delete either one because the minus sign is grayed out. How do I delete one or reset it to it's original defaults and start again?

Question 2: do I need the 'everyone' user in this area?

I did some poking around in my files and found the all add Everyone entries, some were read only and some were no access. It all depends on what you want for access permissions.

 

[GGJstudios]

First step would be to run Disk Utility and Repair Permissions.

Some people repair, or recommend repairing permissions for situations where it isn't appropriate. Repairing permissions only addresses very specific issues. It is not a "cure all" or a general performance enhancer, and doesn't need to be done on a regular basis. It also doesn't address permissions problems with your files or 3rd party apps.

Five Mac maintenance myths

Repairing permissions: What you need to know
About Disk Utility's Repair Disk Permissions feature​

Disk Utility repairs the permissions for files installed by the Mac OS X Installer, Software Update, or an Apple software installer. It doesn’t repair permissions for your documents, your home folder, and third-party applications.

You can verify or repair permissions only on a disk with Mac OS X installed.

Does Disk Utility check permissions on all files?

Files that aren't installed as part of an Apple-originated installer package are not listed in a receipt and therefore are not checked. For example, if you install an application using a non-Apple installer application, or by copying it from a disk image, network volume, or other disk instead of installing it via Installer, a receipt file isn't created. This is expected. Some applications are designed to be installed in one of those ways.

Also, certain files whose permissions can be changed during normal usage without affecting their function are intentionally not checked.

There are times when repairing permissions is appropriate. To do so, here are the instructions:

Repairing Disk Permissions​

If repairing permissions results in error messages, some of these messages can be ignored and should be no cause for concern.

Mac OS X: Disk Utility's Repair Disk Permissions messages that you can safely ignore​

 

[kirkbross]

@GGJstudios Thanks. It's odd... I'm running Lion and have the old, jam-packed, messy, Leopard drive still in the MP so I (and the other 2 users) can access old stuff from that drive while in Lion. All three Lion users are Admins btw, and all three user accounts are on a separate drive from Lion so as not to bloat the SSD with music and pictures.

So... for one of the new user accounts in Lion I tried creating an alias of his old Leopard Desktop folder so I could place it on his Lion desktop for quick access (rather than copy 200GB of data from his old desktop to his new desktop... and don't get me started on messy, hoarder-users).

The problem?

While logged in as him, I am able browse and access the contents of his old Leopard desktop folder with no problem, but when I create an alias of that old desktop folder and try to access it through the alias, it says I don't have permission. Whu-huh?

So... I tried selecting the old desktop folder > Get Info > and select his user name (which already says Read & Write) and then 'Apply to enclosed items' -- but after the changes are applied, I still can't access it from the alias.

I know, worst-case he has to navigate to his old desktop manually, but I don't understand why the alias doesn't work.

Drives:

240 - SSD w/ Lion
1TB - USERS DRIVE
1TB - OLD LEOPARD DRIVE
2TB - DATA
2TB - DATA
2TB - TIME MACHINE