All, I am totally bewildered at the behavior of setting basic file permissions and ownership on 15.4. I cannot change the group on files I own. (WTF?). I cannot set or unset setgid on directories on directories I own with octets (I can with the g+s syntax) Is this apparmor or some other security setting? It wasn't this way with 15.0. Take for example a directory I own and have full write capability to: 00:02 wizard:~/tmp> l -d ./ drwxr-xr-x 10 david david 4096 Jun 15 23:01 ./ Now let's create a new directory named "foo": $ md foo $ l -d ./foo/ drwxr-xr-x 2 david david 4096 Jun 16 00:03 ./foo/ So far so good. Let's change the group to "skyline" of which I'm the sole member, e.g. $ grep skyline /etc/group skyline:x:1000:david $ chown david:skyline foo chown: changing ownership of 'foo': Operation not permitted Huh?? What gives? Why can't I change directory ownership of "foo" to "skyline". That's really bad. Why would I have to be root to set group ownership on a directory I own? But I do: $ sudo chown david:skyline foo $ l -d ./foo drwxr-xr-x 2 david skyline 4096 Jun 16 00:03 ./foo Alright, can I at least set it setgid now so that the files created within it will have the proper permissions: $ chmod 2755 foo $ l -d ./foo drwxr-xr-x 2 david skyline 4096 Jun 16 00:03 ./foo What? Why didn't that work? Can I at least use 'g+s'? $ chmod g+s foo $ l -d ./foo drwxr-xr-x 2 david skyline 4096 Jun 16 00:03 ./foo What? Do I have to be root to do that? What gives? $ sudo chmod 2755 foo $ l -d ./foo drwxr-sr-x 2 david skyline 4096 Jun 16 00:03 ./foo Damnit! This is going to get old quick. I've never had to be root to set group ownership before. There are no ACL's set, so that's not it either. Is there an apparmor rule or something that is doing this? -- David C. Rankin, J.D.,P.E.