Lemmy Shitpost
Welcome to Lemmy Shitpost. Here you can shitpost to your hearts content.
Anything and everything goes. Memes, Jokes, Vents and Banter. Though we still have to comply with lemmy.world instance rules. So behave!
Rules:
1. Be Respectful
Refrain from using harmful language pertaining to a protected characteristic: e.g. race, gender, sexuality, disability or religion.
Refrain from being argumentative when responding or commenting to posts/replies. Personal attacks are not welcome here.
...
2. No Illegal Content
Content that violates the law. Any post/comment found to be in breach of common law will be removed and given to the authorities if required.
That means:
-No promoting violence/threats against any individuals
-No CSA content or Revenge Porn
-No sharing private/personal information (Doxxing)
...
3. No Spam
Posting the same post, no matter the intent is against the rules.
-If you have posted content, please refrain from re-posting said content within this community.
-Do not spam posts with intent to harass, annoy, bully, advertise, scam or harm this community.
-No posting Scams/Advertisements/Phishing Links/IP Grabbers
-No Bots, Bots will be banned from the community.
...
4. No Porn/Explicit
Content
-Do not post explicit content. Lemmy.World is not the instance for NSFW content.
-Do not post Gore or Shock Content.
...
5. No Enciting Harassment,
Brigading, Doxxing or Witch Hunts
-Do not Brigade other Communities
-No calls to action against other communities/users within Lemmy or outside of Lemmy.
-No Witch Hunts against users/communities.
-No content that harasses members within or outside of the community.
...
6. NSFW should be behind NSFW tags.
-Content that is NSFW should be behind NSFW tags.
-Content that might be distressing should be kept behind NSFW tags.
...
If you see content that is a breach of the rules, please flag and report the comment and a moderator will take action where they can.
Also check out:
Partnered Communities:
1.Memes
10.LinuxMemes (Linux themed memes)
Reach out to
All communities included on the sidebar are to be made in compliance with the instance rules. Striker
view the rest of the comments
Mastering file permissions is a big part of becoming Linux capable. And it essential to the "everything is a file" ethos. Wanna lock down an important file or program? chmod is a powerful ally.
Microslop has tried to adopt a half-ass elevated permissions scheme, but with lame-ass UAC and users who've no idea why Explorer doesn't have administrator rights on their administrator account.
Windows' 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 do that.
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.
OP meant ACLs.
Which arent exactly straight forward in CLI in either Windows nor Linux.
But it is pretty straightforward in the Windows GUI.
More or less.
Until you get into nested and inherited permissions ;) Then it get's really fun.
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".
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.
setfacl can do.
It's just that some *NIX users want the stupid POSIX model and authenticating with user-ids (+ private keys) instead of proper usernames and password (and private keys).
Go figure /shrug