• 2 Posts
  • 926 Comments
Joined 3 years ago
cake
Cake day: June 12th, 2023

help-circle

  • 2 weeks to set everything up (lamp stack, K3S, crowdsec, openappsec, wireguard, etc)

    If you’re pushing kubes onto a normie or a noob, the fault’s partially yours. Single-box apache, maybe samba xor git, depending on the workflow, and some audio hints in /etc/profile.d to remind them how to restart various pieces if they can putty in.

    echo 'yum clean ; yum upgrade --skip-broken --no-best ; needs-rebooting && reboot||:' > /etc/cron.weekly/do-eet
    

    … and walk away.

    (--no-best and --skip-broken because RH can’t even do releng now. ‘You had one job’ meets ‘Dead Sea Effect’)





  • BSD isn’t Unix. It’s fairest to say it is a Unix. Unix was built in Murray Hill and maintained by a succession of corporations and now sits locked in a safe at a company where they will never have the clue or interest to maintain or distribute it, thanks to IBM. Everything else is just sparkling multics.

    (Source: was on the periphery, know the people who know where the bodies are)

    And it’s neat to see how well IBM killed the competition who dared to cry code-rape.



  • corsicanguppy@lemmy.catoSelfhosted@lemmy.worldTonight 😬
    link
    fedilink
    English
    arrow-up
    10
    ·
    edit-2
    1 day 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?