NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Manohar
Apr 04, 2019Initiate
is possible to set user permission as read and write but not delete files and folders Readynas 3312
I want create a user with the permissions as read and write but not delete required folder or file. is it possible in ReadyNAS 3312. if there is no way, how to raise the request to organisation. plea...
StephenB
Apr 05, 2019Guru - Experienced User
Retired_Member wrote:
That concept as you are describing it is inconsistent. ... Just because we accepted your described concept for decades since Linus implemented it in Linux does not make it more consistent. ...
Retired_Member: Our opinions on this really don't matter. Linux file permissions are what they are - we don't have the ability to change the framework, and neither does Netgear. They certainly aren't going to switch to a different OS either.
I think we need to wind this down, as it can't go anywhere useful here. If you want to pursue it, then maybe try https://forum.linuxfoundation.org/
Hopchen
Apr 05, 2019Prodigy
Pretty much what StephenB said.
Retired_Member
But will sticky bit (t-bit) not do it for you? It does exactly what you want right? That is even an option in the GUI (under file access)...
On a side note, your interpritation of how it should work is not considerate of several things. For example, you can't hide executables rights as a subsidary to read permissions. Yes, it is true that you need to read a file in order to excute it. But that is only because your interpreter needs to have those right (bash, python, curl, perl, etc.). However, in Linux many binary files can be executed without read permissions. You cannot just bundle the two :)
Anyway, Linux works in this way and probably for a reason.
- Retired_MemberApr 05, 2019
Hi Hopchen , thanks for mentioning the "Sticky-bit", which seems to be a great workaround for certain circumstances in the absence of a true delete right. Will explore that a little bit for better understanding. Kind regards
- SandsharkApr 06, 2019Sensei - Experienced User
For those who wonder "why", here it is: To prevent accidental deletions. In the workplace, one needs to assume that the authorized users will not attempt to sabotage the server. But accidents happen. On a share I used to administer at work, a user accidently dragged one folder into another, causing several automated processes to start failing. Fortunately, I figured it out and restored the folder to it's rightful place. But had he accidently deleted it, I would have had to rely on snapshots to restore it, and work performed after the snapshot was taken would have been lost.
Windows users often don't pay strict attention to the pop-up warning when deleting files. And they are spoiled by the Recycle Bin, as they can recover from most oopses. There being no recycle bin on a ReadyNAS (which there used to be in OS4.x and should optionally still be), there is less oops protection.
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!