this post was submitted on 04 May 2026
904 points (99.2% liked)
linuxmemes
31413 readers
2012 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
- Don't get baited into back-and-forth insults. We are not animals.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudoin Windows. - No porn, no politics, no trolling or ragebaiting.
- Don't come looking for advice, this is not the right community.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
5. π¬π§ Language/ΡΠ·ΡΠΊ/Sprache
- This is primarily an English-speaking community. π¬π§π¦πΊπΊπΈ
- Comments written in other languages are allowed.
- The substance of a post should be comprehensible for people who only speak English.
- Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
6. (NEW!) Regarding public figures
We all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations. - Keep discussions polite and free of disparagement.
- We are never in possession of all of the facts. Defamatory comments will not be tolerated.
- Discussions that get too heated will be locked and offending comments removed. Β
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Cool, but to be fair Linux is made to not make you root.
In most cases a sysadmin somewhere is root, and you may only pledge to him by email and wait weeks for when he decides you waited long enough for a reply.
User permissions are quite strict in Linux.
I'm still pissed there is no way for a user to decide to open a shared folder to other users which enforces base permissions without root doing that.
can't you?
you can assign a preexisting group to a folder as a secondary owner. or you can do it per-user with ACLs
Tried ACL, it kind of works. However users first respect the creation umask, which is generally 022. Which means they can create files in my directory but I can not delete them.
You can force everyone working with you to set their umask to 000, which clearly is not a really nice solution. However, even this does not solve the problem, since if they copy anything over which does not have 666 permissions then you can not edit it or delete it.
Then you're stuck with a bunch of files by someone else who left you their things that you can not delete.
I still have 1 TB of stuff somewhere from a user which has long been deleted from the system, I have no other way to delete that stuff than contact the system administrator.
You can assign a group and then set permissions to 660 and do some ACL magic which hopefully works to enforce a umask of 0 on group; however you can not create a group without being root, which does not really solve the problem.
To be fair, I would appreciate if users were allowed to create their own groups.
did you try setting the default ACL on the shared directory?
section "OBJECT CREATION AND DEFAULT ACLs" here: https://linux.die.net/man/5/acl
I'm not quite sure about how does the inheritance of the default work though. but initially you will need to set the default ACL recursively, so that all existing directories will have the proper default ACL
Mind you, on my own Linux machine I can become root while on Windows all I can be is someone with admin rights (but subordinate to SYSTEM).
Yea, it's a completely different security model, due to coming from Unix (a multi-user system) while Windows started as a single-user system.
Windows is user-centric security, Linux is file/process-centric.
Linux is arguably better, but it also requires more management.
Unless IT has blocked it you should have share options for your Public Folder. At least that's how it was when we ran it at a company. Every user had access to their own public share to share as needed. It was part of the Unix Model.
Never have I seen a public folder on a Linux system, neither personal nor the ones I use for work.
Either way, it would not solve the problem of me myself deciding to share a folder with a set of selected people who can write files in the folder which I then can modify or delete.
I can get to the point of them reading, modifying and creating new files; but the fact that I can not delete files by someone else in my own folders really pisses me off.
All the Linux installs I've done have a public folder in the user home directory as default.
And for example in Gnome settings you turn on the sharing option/password.
I realize that doesn't give you samba sharing with user name access though.