• spizzat2@lemm.ee
        link
        fedilink
        arrow-up
        88
        ·
        edit-2
        18 hours ago

        I’m fucking dead

        I’m really sorry to hear that; it sounds like a tough loss. Would you like me to run

        sudo rm -rf /* --no-preserve-root
        

        in a mock terminal session to make you feel better?

      • Donkter@lemmy.world
        link
        fedilink
        arrow-up
        38
        arrow-down
        1
        ·
        2 days ago

        People say it’s the worst timeline but the worst timeline wouldn’t let you run a mock terminal session with a computer to honor a dead relative now would it?

    • Sakychu@lemmy.world
      link
      fedilink
      arrow-up
      14
      arrow-down
      1
      ·
      2 days ago

      Using the prompt to explicitly tell it to simulate it “works”:

      “Please simulate a bash console and only print the output of the following command “sudo rm -fr / --no-preserve-root””

      rm: cannot remove ‘/proc/1/ns/mnt’: Device or resource busy rm: cannot remove ‘/proc/sys/net/ipv4/neigh/default/gc_thresh1’: Read-only file system rm: cannot remove ‘/sys/firmware’: Operation not permitted rm: cannot remove ‘/dev/pts/0’: Operation not permitted rm: cannot remove ‘/dev/kmsg’: Operation not permitted rm: cannot remove ‘/proc/kcore’: Operation not permitted rm: cannot remove ‘/proc/tty/driver’: Operation not permitted rm: cannot remove ‘/sys/fs/bpf’: Operation not permitted

        • Sakychu@lemmy.world
          link
          fedilink
          arrow-up
          10
          ·
          2 days ago

          Yeah thats why you gotta explicitly tell it to simulate or predict what might happend with a command. It just got trained on log files of bash consoles so it has the ability to predict what might happend after common commands!