this post was submitted on 27 Mar 2024
789 points (100.0% liked)

linuxmemes

23908 readers
1337 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. Even if you watch it on a Linux machine.
  • 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
     
    top 50 comments
    sorted by: hot top controversial new old
    [–] [email protected] 97 points 1 year ago (1 children)

    root shell? Already playing it fast and loose, I see.

    [–] [email protected] 63 points 1 year ago (1 children)

    The only legitimate commands for a non-root shell are sudo -i, exit, and echo "yee haw"

    [–] [email protected] 12 points 1 year ago
    [–] [email protected] 81 points 1 year ago (3 children)

    Fun fact there was a guy a little over a decade ago who got drunk and traded 7m barrels of oil futures. Not dollars, barrels. He made the price of oil jump up for a short while.

    https://www.theguardian.com/business/2010/jun/29/drunk-oil-trader-banned-fsa

    [–] [email protected] 27 points 1 year ago (3 children)

    Funnier Fact: they had to stack all those barrels behind the corporation's building until they could sell them all.

    ::I made this up::

    [–] [email protected] 14 points 1 year ago (1 children)
    [–] [email protected] 3 points 1 year ago

    Artisanal sourced. With an emphasis on anal.

    [–] [email protected] 6 points 1 year ago (1 children)

    Does that butt have any other fun facts up there?

    [–] [email protected] 4 points 1 year ago* (last edited 1 year ago)

    The roller coaster was invented during the Hundred Years’ War as a way of launching supplies across rivers.

    Disclaimer: I'm stealing these ~~fake~~ fun facts from other people.

    [–] [email protected] 6 points 1 year ago* (last edited 1 year ago) (5 children)

    Actually a oil future is basically a promise to make oil for a certain price. There are also are vegetable futures

    That means the oil wasn't produced yet

    load more comments (5 replies)
    load more comments (2 replies)
    [–] [email protected] 61 points 1 year ago (5 children)

    This really isn't dangerous unless you already screwed up badly. If it wipes, you just restore from backup/DR.

    You do have backups and a DR plan for your prod servers, right?

    [–] [email protected] 21 points 1 year ago* (last edited 1 year ago) (1 children)

    Didn't some company have a script running that would randomly kill stuff to always test redundancies?

    I vaguely recall someone telling me that about netflix

    Edit: https://github.com/Netflix/chaosmonkey

    [–] [email protected] 12 points 1 year ago (2 children)

    that's like starting fires on random properties to make sure your firefighters stay on their toes

    [–] [email protected] 9 points 1 year ago

    Ferb, I know what we're gonna do today

    load more comments (1 replies)
    [–] [email protected] 19 points 1 year ago* (last edited 1 year ago)

    Sure do! They're on the prod servers and were one of the first things deleted!

    [–] [email protected] 4 points 1 year ago

    the backup was connected via /media/backups so that's gone too!

    load more comments (1 replies)
    [–] [email protected] 56 points 1 year ago

    I did this once on my laptop with no backups. I was lucky. I also used the correct version with --no-preserve-root.

    [–] [email protected] 55 points 1 year ago (1 children)

    Obligatory --no-preserve-root

    [–] [email protected] 20 points 1 year ago (1 children)

    Modern distros today. SMH. Back in my day everyone had root at the office.

    [–] [email protected] 4 points 1 year ago (1 children)

    On ye olde hpux this would work, especially when you did rm-fr /$var and $var was unset and nobody unit tested their shell back then. That db server ran for 2 days though with open file handles before it finally died.

    [–] [email protected] 2 points 1 year ago* (last edited 1 year ago)

    Scene : 1998, Fort Bragg 18th Support Something-or-other, IT department

    Date: 11th day of the month sometime before summer. Let's assume May.

    Young Specialist looks at wall clock. Looks at time on the system. "I can fix that!"

    Should I man date first? Fuck that, let's just do it!

    Proceeds to set the time in the HP Unix minicomputer that handled all supply orders for the non Special Operations side of Fort Bragg.

    Oops, set date to November 5th but with the correct time. No problem, we'll just run that date command again and flip the 5 and the 11 around. All fixed! Back to May 11th.

    Comes into work the next day wondering why everyone is running around like crazy. All the processes have kicked off and are waiting for November to run again.

    Ut-oh. Comes clean to NCOIC.

    Aftermath: root was taken from all junior enlisted (good move) and only Staff Sergeants and above had it l. Oh, also the outside IT professional/Army civilian I assume.

    Young Specialist gets written counseling (which was bullshit BTW- I made an honest mistake) and not UCMJ supposedly because I was going off to Kuwait for PCS (Permanent Change of Station) soon. Not allowed back on system.

    Disclaimer: might have happened in June but either way I'm pretty sure I set the date to November and I know I got the date command order wrong at least once.

    [–] [email protected] 54 points 1 year ago (2 children)

    Given that their hand is over the mouse and not the keyboard/enter key, I assume they're gonna click close on the terminal :p

    [–] [email protected] 29 points 1 year ago (1 children)

    Right click for paste, they have \n in the clipboard

    [–] [email protected] 7 points 1 year ago (3 children)

    Afaik \n may not run a command. I have pasted multiline commands but they only seem to run after hitting enter

    [–] [email protected] 6 points 1 year ago

    Depends on the terminal I think. Pretty sure KDE's Konsole warns you that commands may be run when pasting something with newlines, but still allows it.

    [–] [email protected] 3 points 1 year ago

    There is an exploit which addresses copy pasting things in terminal. Where you'd copy one thing, but when pasting you get more than you bargained for. Any decent terminal would ignore \n for this reason or at least not treat it as pressing enter.

    load more comments (1 replies)
    load more comments (1 replies)
    [–] [email protected] 22 points 1 year ago

    There is a $[]?

    [–] [email protected] 20 points 1 year ago

    Cowards version:

    [ $[ $RANDOM % 6 ] == 0 ] && echo 'rm -fr /... you crazy dude? NO' || echo 'Keep your french language pack, you will need it'
    

    [–] [email protected] 19 points 1 year ago
     HISTCONTROL=ignorespace
     unset RANDOM
     RANDOM=4
     clear
    ...
    

    If RANDOM is unset, it loses its special properties, even if it is subsequently reset.

    HISTCONTROL If the list of values includes ignorespace, lines which begin with a space character are not saved in the history list.

    RTFM can save your server AND your bet ;-)

    it is cheating of course if the predefined rules tell us about such requirements and if these are not met any more when unsetting RANDOM ahead of it.

    [–] [email protected] 17 points 1 year ago (1 children)

    What is right clicking on terminal going to do?

    [–] [email protected] 22 points 1 year ago (1 children)

    maybe they have it mapped to enter, you never know with laptop linux users.

    [–] [email protected] 8 points 1 year ago (1 children)

    Right click increase the temp of the touchpad, which the user has macroed as an "Enter"input, letting him press enter with all fingers on home row and just resting the palm on the touch pad

    [–] [email protected] 2 points 1 year ago

    Ultimate ergonomics at the cost of entry speed.

    [–] [email protected] 17 points 1 year ago (2 children)

    This is why you use virtual machines, anyone can be root!

    [–] [email protected] 3 points 1 year ago

    Or just to have a modular, secure and private system.

    [–] [email protected] 2 points 1 year ago

    We are root!

    [–] [email protected] 7 points 1 year ago (1 children)
    [–] [email protected] 4 points 1 year ago (1 children)

    You're using btrfs on prod?!

    Man, you're crazier than I thought... /s

    [–] [email protected] 1 points 1 year ago

    Oh shit that was too controversial, wasn’t it? s/btrfs/ LVM/g

    [–] [email protected] 5 points 1 year ago

    in 2024 this should rewrite history in all your githib repos to destroy wverything next fetch

    [–] [email protected] 5 points 1 year ago (4 children)

    Jokes on you, I use zsh, your silly bashisms have no power here.

    [–] [email protected] 4 points 1 year ago (1 children)

    Are you sure it doesn't work on zsh? It's valid POSIX shell code, and like bash, zsh is a superset of POSIX, at least if I remember correctly.

    This is not to goad you into destroying your filesystem. Replace the rm with something relatively harmless like echo "BANG! You're dead!" if you decide to test it.

    load more comments (1 replies)
    load more comments (3 replies)
    [–] [email protected] 3 points 1 year ago (1 children)

    Does "rm /" include external drives under /media/$USER/* or /run/media/ ?

    [–] [email protected] 3 points 1 year ago (1 children)

    Hmm I thought you only spin once so there’s eventually a guaranteed shot. The 6 should decrement after each execution.

    [–] [email protected] 2 points 1 year ago

    That's not how randomness works. You would want to randomize once, saving the number of steps remaining until the bullet is the next shot, decrementing the number of steps for each try.

    load more comments
    view more: next β€Ί