Annoying permissions problem

[acme]

Quote: Originally Posted by agentx No idea how it came to be but mor ethan lily th inheritance bit is set on the ~/Documents ACE which it should not be.....i think. Does it all work now ? ls -alOe ~ ls -alOe ~/Documents Post back

LionRs-MacBook-Pro:~ lionr$ ls -alOe ~
total 1808
drwxr-xr-x+ 17 lionr staff - 578 Apr 13 12:58 .
0: group:everyone deny delete
drwxr-xr-x 6 root admin - 204 Apr 15 10:05 ..
-rw------- 1 lionr staff compressed 3 Apr 7 13:09 .CFUserTextEncoding
-rw-r--r--@ 1 lionr staff - 15364 Apr 16 11:03 .DS_Store
drwx------ 5 lionr staff - 170 Apr 16 11:43 .Trash
drwxr-x--x 3 lionr staff - 102 Apr 7 15:52 .adobe
-rw------- 1 lionr staff - 334 Apr 16 11:26 .bash_history
drwx------ 2 lionr staff - 68 Apr 7 16:03 Applications
drwx------+ 7 lionr staff - 238 Apr 16 11:23 Desktop
0: group:everyone deny delete
drwx------+ 12 lionr staff - 408 Apr 14 20:13 Documents
0: group:everyone deny delete
drwx------+ 5 lionr staff - 170 Apr 7 13:15 Downloads
0: group:everyone deny delete
drwx------@ 45 lionr staff hidden 1530 Apr 16 11:24 Library
0: group:everyone deny delete
-rw-r--r--@ 1 lionr staff - 300304 Apr 7 17:27 Library alias
drwx------+ 3 lionr staff - 102 Apr 7 13:09 Movies
0: group:everyone deny delete
drwx------+ 4 lionr staff - 136 Apr 9 14:29 Music
0: group:everyone deny delete
drwx------+ 4 lionr staff - 136 Apr 7 13:09 Pictures
0: group:everyone deny delete
drwxr-xr-x+ 7 lionr staff - 238 Apr 14 20:15 Public
0: group:everyone deny delete
LionRs-MacBook-Pro:~ lionr$


and



LionRs-MacBook-Pro:~ lionr$ ls -alOe ~/Documents
total 80296
drwx------+ 12 lionr staff - 408 Apr 14 20:13 .
0: group:everyone deny delete
drwxr-xr-x+ 17 lionr staff - 578 Apr 13 12:58 ..
0: group:everyone deny delete
-rw-------@ 1 lionr staff - 24580 Apr 14 20:13 .DS_Store
-rw------- 1 lionr staff - 0 Apr 7 13:09 .localized
drwx------ 23 lionr staff - 782 Apr 14 21:20 Art
drwx------ 3 lionr staff - 102 Mar 24 20:22 ArtRage Paintings
drwx------@ 48 lionr staff - 1632 Apr 14 20:09 Downs|RC
-rw-------@ 1 lionr staff - 41082880 Mar 15 11:26 SecureInfoHeManB_Day.dmg
drwx------@ 26 lionr staff - 884 Mar 9 16:09 Type Master|RC
drwx------@ 44 lionr staff - 1496 Mar 11 20:35 resources
drwx------ 4 lionr staff - 136 Apr 3 15:17 tunes from Greg
drwx------@ 57 lionr staff - 1938 Apr 14 20:03 ••Info RC••
LionRs-MacBook-Pro:~ lionr$

[acme]

I just had to reboot and when I got in, I accidentally discovered that I again can not re-name files on the Desktop!

Files in Documents seem to be free of this.

do I have to do the commands as before but with "Desktop" the last item in the command?

thank you,

a

[zo219]

People, download batchmod and do what you will. It's your machine.

http://www.lagentesoft.com/batchmod/index.html

[acme]

wasn't one of the lessons here that users can hose their own machines by tinkering with permissions?

[trevor]

I would hate for that to be the lesson. The lesson that I would prefer is that educating oneself about ownership and permissions will allow YOU control over them, instead of them controlling you. Education is key. Once you understand how things work, then you can and should control them and make changes to them--it is your machine, as zo219 says.

I'm not a fan of recommending utilities that allow people who don't understand what it is that they're doing to do things that can lose control of their own computer. Tools exist to make life easier, and there's no problem with the tools in themselves. But you have to pick the right tool for it's user. I don't give my four-year-old access to my power tools, and I don't recommend that my grandmother use BatChmod.

Trevor

[acme]

heh..fair enough...you are a good dad!

in terms of education, is there a place where one can learn what the permissions should be for various things...like the desktop for a Standard user?

[trevor]

I'd start by digging into unix permissions and how they work. This will entail some playing in the Terminal. One good resource from our very own hayne is the Unix FAQ. Here's the part on permissions:
http://hayne.net/MacDev/Notes/unixFAQ.html#permissions

Trevor

[acme]

thank you for that link!

a

[ganbustein]

Quote: Originally Posted by acme now, have any of you ever gotten into this situation and/or know how or why it could happen?

It probably happened from a careless click on "Apply to enclosed items" in Finder's Get Info box. (You can find it in the "gear" menu at the bottom of the window.) Terminal.app gets a bad rap as a tool that can mess you up if misused, but Finder can be just as dangerous when it comes to permissions. Worse, in some respects, because Finder won't give you a clear picture of what you're doing or about to do or just did. Terminal may sometimes be cryptic, but at least it's always precise.

[acme]

Quote: Originally Posted by ganbustein It probably happened from a careless click on "Apply to enclosed items" in Finder's Get Info box.

I will own doing that, but my problem existed prior to my clicking "Apply to enclosed items."


so I still don't have a clue what originally caused the problem.