Either I don’t understand your comment, or you don’t understand chmod. What you describe ins’t beyond chmod; it’s the basic functionality of chmod.
Comment on When your computer says "You don't have permission to edit this file":
Viceversa@lemmy.world 14 hours agoWindows’ way is more convenient for me, than chmod: windows allows you to regulate file access more granularly, more flexible - per any particular user , particular group. Chmod can’t.
yesman@lemmy.world 13 hours ago
Viceversa@lemmy.world 12 hours ago
Via chmod you can’t configure access to some arbitrary group or user. You have only the owner user, owner group and everything else is crowded into one lump “other”.
Appoxo@lemmy.dbzer0.com 11 hours ago
OP meant ACLs.
Which arent exactly straight forward in CLI in either Windows nor Linux.
Appoxo@lemmy.dbzer0.com 11 hours ago
setfacl can do.
It’s just that *NIX users want the stupid POSIX model and authenticating with user-ids (private keys) instead of proper usernames +password and private keys.
Go figure /shrug
Limonene@lemmy.world 4 hours ago
chmod can do 95% of everything I’ve ever needed, just with the “user” and “other” category. Private files, public-readable files, public read-write files, programs I compile but anyone can run… all that is just in the “user” and “other” category of chmod.
It gets 99% if you add the sticky bit (used on /tmp) and the “group” category. Serial ports are owned by root:dialout, and mode 660. To get serial port access, just add the user to the dialout group. For group assignments in college, each partner pairing had their own group they could use. Group work files were mode 660 so groups could edit each others’ work, but other groups couldn’t peek.
For the last 1%, use setfacl. It does everything that explorer.exe’s security tab can do.