• DAMunzy@lemmy.dbzer0.com
      link
      fedilink
      arrow-up
      27
      arrow-down
      1
      ·
      8 months ago

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

      ::I made this up::

        • DAMunzy@lemmy.dbzer0.com
          link
          fedilink
          arrow-up
          4
          ·
          edit-2
          8 months 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.

      • Possibly linux@lemmy.zip
        link
        fedilink
        English
        arrow-up
        6
        arrow-down
        1
        ·
        edit-2
        8 months ago

        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

          • milicent_bystandr@lemm.ee
            link
            fedilink
            arrow-up
            1
            ·
            8 months ago

            But I do remember a story (on daily wtf) where a lady bought coal futures and somehow forgot or didn’t manage to sell, and a coal barge turned up in the river behind her office!

        • FiniteBanjo
          link
          fedilink
          arrow-up
          1
          arrow-down
          1
          ·
          8 months ago

          Also, Crude Barrels have a shelf life so you definitely wouldn’t store them like that for any extended period of time.

          • Possibly linux@lemmy.zip
            link
            fedilink
            English
            arrow-up
            1
            ·
            8 months ago

            A future means that they will be created at some point in the future. Basically its an agreement to buy for a certain price in the future regardless of what the markets are doing.

            • FiniteBanjo
              link
              fedilink
              arrow-up
              1
              arrow-down
              1
              ·
              8 months ago

              Yes you said exactly that in the comment I replied to, I never argued against it I was just adding onto it. We both were talking about how unrealistic the comment further above yours was.

  • Nollij@sopuli.xyz
    link
    fedilink
    English
    arrow-up
    61
    ·
    8 months ago

    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?

  • Rikudou_Sage@lemmings.world
    link
    fedilink
    arrow-up
    58
    arrow-down
    1
    ·
    8 months ago

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

      • mitchty@lemmy.sdf.org
        link
        fedilink
        arrow-up
        4
        ·
        8 months ago

        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.

        • DAMunzy@lemmy.dbzer0.com
          link
          fedilink
          arrow-up
          2
          ·
          edit-2
          8 months 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.

  • librecat@lemmy.basedcount.com
    link
    fedilink
    arrow-up
    55
    ·
    8 months ago

    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

        • Ghoelian@lemmy.dbzer0.com
          link
          fedilink
          arrow-up
          7
          ·
          8 months 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.

        • LostXOR@fedia.io
          link
          fedilink
          arrow-up
          1
          ·
          8 months ago

          It definitely runs the command for me in GNOME Terminal. Pasting multiple commands at once runs everything but the last command.

    • nebula42
      link
      fedilink
      arrow-up
      1
      ·
      8 months ago

      Well they did have the type the command, and to do that they would first have to navigate to the terminal (assuming the machine isn’t running just a plain tty) first.

  • GravelPieceOfSword@lemmy.ca
    link
    fedilink
    arrow-up
    20
    ·
    8 months ago

    Cowards version:

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

  • smb@lemmy.ml
    link
    fedilink
    English
    arrow-up
    19
    ·
    8 months 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.

      • Droechai@lemm.ee
        link
        fedilink
        arrow-up
        8
        ·
        8 months ago

        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

  • mvirts@lemmy.world
    link
    fedilink
    arrow-up
    5
    ·
    8 months ago

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

    • palordrolap@kbin.social
      link
      fedilink
      arrow-up
      4
      ·
      8 months ago

      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.

      • mitchty@lemmy.sdf.org
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        8 months ago

        Key here is the outer [] and interaction of $[], test doesn’t have == by default in standard posix, so no this isn’t posix shell or bourne compatible. Tis but another bashism. I could probably force zsh into a more bourne mode to try it but its definitely not portable bourne shell its bash.

        $ [ $[ $RANDOM % 6 ] == 0 ] && echo rm || echo ok
        zsh: = not found
        $ zsh --version
        zsh 5.9 (x86_64-pc-linux-gnu)
        

        == should be -eq for this to be posix/bourne portable, you could use = but -eq is for numeric comparisons so not quite right.