this post was submitted on 25 Apr 2025
626 points (98.0% liked)

linuxmemes

24652 readers
1654 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

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 sudo in Windows.
  • No porn, no politics, no trolling or ragebaiting.
  • 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 figuresWe 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
     
    (page 2) 50 comments
    sorted by: hot top controversial new old
    [–] Valmond@lemmy.world 2 points 1 day ago

    What happened with frog_brawler?

    [–] LainTrain@lemmy.dbzer0.com 11 points 2 days ago

    :w !sudo tee %

    [–] Katzimir@lemmy.dbzer0.com 11 points 2 days ago

    now i feel shame. I used to love breaking my xorg.conf in nano

    [–] jumponboard@lemmy.world 9 points 2 days ago (1 children)

    Why does it have to be transcribed into numbers anyway?

    load more comments (1 replies)
    [–] SleepyPie@lemmy.world 6 points 2 days ago (2 children)

    If it’s all my system should I really care about chown and chmod? Is the point that automatic processes with user names like www-data have to make edits, and need permission to do so, and that’s it?

    Newish Linux user btw

    [–] palordrolap@fedia.io 9 points 2 days ago (1 children)

    In addition to corsicanguppy's comment, some β€” often important β€” programs actually expect the system to be secured in a particular way and will refuse to function if things don't look right.

    Now, you'd be right to expect that closing down permissions too tightly could break a system, but people have actually broken their systems by setting permissions too openly on the wrong things as well.

    That said, for general, everyday use, those commands don't need to be used much, and there might even be a way to do what they do from your chosen GUI. Even so, it nice to know they're there and what they do for those rare occasions when they might be needed.

    load more comments (1 replies)
    [–] corsicanguppy@lemmy.ca 9 points 2 days ago* (last edited 21 hours ago) (1 children)

    Short answer: yes.

    One of the tenets of security is that a user or process should have only enough access to do what it needs, and then no more. So your web server, your user account, to your mail server, should have exactly what they need, and usually that's been intricately planned by the distro.

    If you subvert it you could be writing files as root that www-data now can't read or write. This kind of error is sometimes obvious and sometimes very subtle.

    Especially if you're new to this different access model, tread carefully.

    Great news! If you mess it up, many distros are really great at allowing you to compare permissions and reset them. The bad news is that maybe you're not on one of those. But you could be okay.

    load more comments (1 replies)
    [–] juipeltje@lemmy.world 6 points 2 days ago (2 children)

    I'm not sure if that's the joke and it flew over my head but isn't editing with sudo what you should be doing anyway if it's a system level file? You shouldn't change permissions unless the file is actually supposed to be owned by your user.

    load more comments (2 replies)
    load more comments
    view more: β€Ή prev next β€Ί