Unless you are very confident of your security and the implications of 1777 permissions, I'd avoid them. If something is misconfigured and you end up with a malicious file written there, it can be executed by any user or process. Step 2: Select ‘File Explorer’ from the list and select. Step 1: Right-click on the Windows key and select Task Manager. Incidentally, setting 1777 permissions is not considered a great idea, as it grants much greater permission than required, and allows the folder to be globally written to and executed from. You can force close the app and try creating new folders again. (This is a very common configuration for shared media folders.) The uid and gid options will work in your `/etc/fstab/ file as well, since you say the partition is mounted permanently, this is most likely where you've done it. If that's the case, then you will need 775 or 774 permissions to allow group members to write, and you'll also need to set chmod g+s (or chmod 1774 will do the same) to ensure all group members can access newly created files in future. In both these examples, the group will almost certainly be your username, unless you have a special group so that multiple users can interact with the mounted drive. So changing your mount command to this might help in future: mount device mount-point -o uid= -o gid= This can happen with mounted filesystems that you use sudo to mount. That can be fixed with this: sudo chown -R username:group directory If you don't own it, that would explain the behaviour you described. Try checking the user and group ownership of the directory (and its contents) using ls -l.
0 kommentar(er)
