• neidu3@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      0
      ·
      edit-2
      1 day ago

      STORY TIME!

      Once upon a time, I worked an offshore rotation. So while I was home, I didn’t have much better to do than to hang out with my friend and his coworkers. They all worked for the local branch of a huge international corporation that shall remain anonymous, so I will only refer to the corporation by their initials: IBM.

      This local branch dealt with banking systems, handling large clients in Europe, ensuring that their systems ran the way they should. And to make sure said banks could have their stuff sorted when a problem arose, there was always someone on call.

      Well, it sucks being the guy on call when the one who’s the perfect guy to fix it is off, and in the spirit of solidarity, they did the only thing reasonable: Went to a local pub, and placed the on-call phone on the table, so if it rang, the expertise to get it sorted quickly was present.

      I usually joined them, and more than once did I go for a piss, passing someone with their phone on their shoulder with a laptop in a bathroom sink, trying to sort out banking issues after having had waaay too many drinks.

      • Skullgrid@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        15 minutes ago

        They all worked for the local branch of a huge international corporation that shall remain anonymous, so I will only refer to the corporation by their initials: IBM.

        Some kind of corporation that works internationally, supplying businesses with machines?

  • corsicanguppy@lemmy.ca
    link
    fedilink
    English
    arrow-up
    0
    arrow-down
    1
    ·
    edit-2
    23 hours ago

    What’s the big deal? For 20 years in the enterprise space it’s been yum upgrade -y && reboot into cron and no issues. At the day job I even had satellite (5 and that shitball 6) cronned up to do my promotion automatically (even when 6 had shit for scheduling and I had to cron-parallel-xargs a better one). All cron.

    Hell, I barely pay attention to the email reports now. It’s been that long. Okay, prod updates on Friday night only; but that’s our only nod to risk. Because even after the metastatic fatberg that is Systemd, it’s still barely reliable.

    What’s the added risk for Debian packages? Imperfect replacement? No signed manifest to compare against? What?