• TipRing@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      ·
      19 hours ago

      At one of my prior positions they outsourced all the junior engineers to this firm that only had windows desktop support experience.

      Actual escalation I got:

      contractor: I am trying to remove this file that is filling the drive but it won’t let me

      me: show me what you are doing.

      contractor (screenshot): # rm -f /dev/hdc

      another one did rm -rf /var to clear a stuck log file, which at least did solve the problem he was having.

      After that I sent out an email stating that I would not help anyone who used he rm command unless they consulted with a senior first. I was later reprimanded for saying I wouldn’t help people.

      • B-TR3E@feddit.org
        link
        fedilink
        arrow-up
        1
        ·
        18 hours ago

        I was later reprimanded for saying I wouldn’t help people.

        I’ve heard that before. “No. I won’t close the circuit breaker while you’re holding the wires.” “Boss!..”

    • bitchkat@lemmy.world
      link
      fedilink
      English
      arrow-up
      8
      ·
      2 days ago

      Back in the olden days we used to nfs mount every other machines file system on every machine. I was root and ran “rm -rf /" instead of "./”.

      After I realized that it was taking too long, i realized my error.

      Now for the fun part. In those days nfs passed root privileges to the remote file system. I took out 2.5 machines before I killed it.

      • B-TR3E@feddit.org
        link
        fedilink
        arrow-up
        1
        ·
        1 day ago

        Back in the olden days we used to nfs mount every other machines file system on every machine. I was root and ran “rm -rf /” instead of “./”.

        I still do. With NFS4 even more than ever. Won’t let it go unless for a SAN.

        Now for the fun part. In those days nfs passed root privileges to the remote file system.

        no_root_squash
        

        much?

          • B-TR3E@feddit.org
            link
            fedilink
            arrow-up
            1
            ·
            18 hours ago

            Holy smokes. That must have been before 1989 (that’s when RFC1094 was released, explicitely prohibiting to map the root user to UID 0). I thought, I was old…

      • baines@lemmy.cafe
        link
        fedilink
        English
        arrow-up
        2
        ·
        2 days ago

        I did this in a cleanup script in a make file with an undefined path that turned the pointed dir to root after a hardware change

        thank rngesus I was in a user account with limited privileges