1. 27
  1. 10

    There’s still more BOFH that isn’t on here.

    A while ago I wanted to make a proper archive but it’d just be most likely adding to the problem eventually and I don’t think I have the rights to redistribute. But who knows…

    1. 8

      Be bold

      1. 25

        There’s still more BOFH that isn’t on here.

        A while ago I wanted to make a proper archive but it’d just be most likely adding to the problem eventually and I don’t think I have the rights to redistribute. But who knows…

    2. 8

      Ah, memories. I read those while working at a commercial ISP, and I was insanely jealous of the BOFH. I wanted to be more like him :)

      1. 3

        When I was 18 I was the assistant sysadmin at a mom’n’pop ISP (this was 1998 when small independent ISPs were still a thing). The head guy called himself the BOFH and I was his PFY. By 1999 he had moved on and I became the new BOFH.

      2. 4

        Excellent memories! I have the BOFH excuse generator by Jeff Ballard running on a host of mine:

        % nc ols.wtf 666
        Stale file handle (next time use Tupperware(tm)!)
        
        1. 3

          BOFH 3 used to be funny. Not anymore

          1. 1

            I read the 3rd entry in the linked list - it wasn’t funny then, either.

          2. 3

            Back when I was in support business, some my friends and I formulated the laws of support technician evolution:

            1. Given enough time, any support technician will almost surely turn into a BOFH.
            2. The transition is irreversible.
            3. Therefore, it’s important to make sure all people leave those positions before going BOFH.
            1. 2

              Ah. The times when we could afford being distanced from the real world implications of our actions. Things looked simpler than.

              But was it?