this post was submitted on 27 Jun 2025
365 points (96.4% liked)

linuxmemes

25876 readers
760 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
    365
    Dirty Talk (lemmy.zip)
    submitted 20 hours ago* (last edited 20 hours ago) by [email protected] to c/[email protected]
     

    Disclaimer: Do not run this command.

    you are viewing a single comment's thread
    view the rest of the comments
    [–] [email protected] 111 points 20 hours ago (10 children)

    Obligatory DO NOT RUN THIS ON YOUR COMPUTER (or anyone else's).

    You'd think with fully open permissions, everything would work better, but many programs, including important low level things, interpret it as a sign of system damage and will refuse to operate instead.

    If you do run it, you'd better have a backup or something like Timeshift to bail you out, and even if you do have that, it's not worth trying it just to see what will happen.

    It's not quite as bad as deleting everything because you can boot from external media and back up non-system files after the fact, but the system will almost certainly not work properly and need to be repaired.

    You have been warned.

    [–] [email protected] 50 points 19 hours ago (2 children)

    New guy at work ran this to try to fix permissions on his home folder, accidentally ran it on root (both would have been bad)

    Several highly paid and experienced Linux admins finally just gave up and deleted the server and built a new one from the backups.

    [–] [email protected] 2 points 6 hours ago

    Why does he have rights to use sudo in the first place?

    [–] CosmicTurtle0 24 points 18 hours ago (2 children)

    Which, honestly, is the better way to go. Treat your compute resources like cattle, not pets.

    [–] [email protected] 10 points 12 hours ago* (last edited 12 hours ago) (1 children)

    One of our servers is a rotting carcass being kept alive by our collective prayers. It runs Windows 7 and custom software whose developer is dead and the source is missing, nothing has been updated for over a decade, and it has its own independent UPS because once it goes down, it has an extremely slim chance of recovering, and we're afraid to test it. It controls the card entry system into the building, including the server room. Boss doesn't want to replace it because we'd have to replace all of the terminals and controllers too, and it hasn't catastrophically failed yet.

    You're right. It's not a pet. It's like one of the Saw movies: if it dies, we're all fucked.

    [–] [email protected] 2 points 4 hours ago

    So... the dead server controls who is even able to enter the building? Wow. That is one big juggernaut of a problem heading for you.

    [–] [email protected] 4 points 16 hours ago* (last edited 16 hours ago)

    I learned this relatively quickly running my own server with the intention of my family also using it. Data on a separate drive, backed up regularly and automatically. System on it's own drive, dd'd when it's in it's final state and backed up before I screw around any deeper than trying out a new container. I can bring my server back up in however long it takes to transfer data.

    load more comments (7 replies)