April 3, 201214 yr I created a folder in a user share from a Windows machine. In that folder I can create folders copy files into it, everything ok. But when I copy some folders in it with Midnight Commander running on the unraid server, I can access these folders and the files in it, but I can't change them from within Windows. I can't even change the name! When I do a ls -l on such a folder I see root:root on that folder. The folders I created myself show nobody:user. How to get Midnight Commander behave different? Should I login differently and not as root? When I login under a different name will Midnight Commander then create folders as nobody:user?
April 3, 201214 yr I created a folder in a user share from a Windows machine. In that folder I can create folders copy files into it, everything ok. But when I copy some folders in it with Midnight Commander running on the unraid server, I can access these folders and the files in it, but I can't change them from within Windows. I can't even change the name! When I do a ls -l on such a folder I see root:root on that folder. The folders I created myself show nobody:user. How to get Midnight Commander behave different? Should I login differently and not as root? When I login under a different name will Midnight Commander then create folders as nobody:user? don't use midnight commander unless you are going to change the permissions manually. root is the only user that has access to telnet in.
April 3, 201214 yr Author Correct, I tried a different username but can't login. So I should chow/chmod manually? Or use the cp or mv command, or copy it with help of another PC? Gives Midnight Commander rather limited use. Would running the new permissions script work too? I use 5.0b12a atm.
April 3, 201214 yr I also MC to transfer some files. No W in Windows. So I tired manually chown nobody:users and chmod og=rw and nothing still cannot delete or change files in Win7. ls -l clearly showed nobody:users. There is something in 5B14 which messed permissions. I guess the answer is not to use MC for me. According to Joe L. the files transferred by MC were owned by root so if you use chown nobody:users directory or files then the files would be owned by nobody:users and permissions for RW will be granted when using Windows. I tried that and have reported that it did not work for me for some reason. Really annoying.
April 3, 201214 yr Author Running the new permissions script did the trick for me. Basically this is also a chmod and chown.
Archived
This topic is now archived and is closed to further replies.