okay.. i'm fairly new to the linux environment, and have had some joy and lots of headache learning it..

the problem i am currently having is that at my work, we have a new linux server set up as file server... we are transferring all the files/folders from the windows server to linux server...

transferring files is easy, and setting it up is easy.. however, permissions have been killing me..

in windows it was easy to give a certain user in AD permissions to read, write, access files..

what i have done is created groups on the AD side, and grant group permission access full access to the windows users on the linux system. .. so it would be chmod -R 770 (whatever folder).. this is great and all, however, while the linux side clearly shows that group has read write and execute access.. i can't get any users to actually open the folder or create anything in the folder .. it doesnt seem like it's picking up something.. can anyone help ME?!?!?! this happens when i try to add a user into the group on AD or when I create a new group on AD, and give that group a read write execute access ...


help someone... thanks!

I'm not sure exactly what is your problem. Nevertheless, the
commands for manipulating user permission are:

chmod
chgrp (change group)
chown (change ownership)

With these commands, you show be able to do everything.
Do a man and/or info on these commands.
If you want GUI, try the "Control Center".
Btw, you didn't mention which distribution you're using - might help others.

Sheng-Chieh

Ok, so setting rwx permissions for the group on a folder will allow those users to read the contents of that folder, navigate to it, and create files. However, all of those abilities are broken if there is any directory in the path that does not allow both read and execute permissions for the users. An example might illustrate what I'm saying. Suppose you have this directory:
owner=root,group=AD, 770: /system/backup/windows

So now root and users in group AD should be able to do anything their hearts desire in that directory. However, throw this into the mix:
owner=root,group=admin, 770: /system/backup

All of a sudden the chain is broken, and AD users are left in the cold. For the /system/backup directory, users in the AD group fall into the "others" category regarding permissions. And those permissions are 0 (no read, no write, no execute). It no longer matters what permissions are on /system/backup/windows, because the AD users can't get through /system/backup. To access /system/backup/windows, the users in group AD need read and execute permissions on every directory in the path. So /system needs to give them rx and /system/backup needs to give them rx.

Double check those permissions and see if you're falling into that trap.