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

help-circle

  • 33 years with Linux (kernel 1.2.13, slackware). Worked at a distro. Worked in OS security – Unix and enterprise Linux. I helped build United Linux out of the dismembered corpse suse kicked over the fence as ‘collaboration’.

    Because of the validation issue in the .deb package format and others, I’m on a mixture of Rocky and Nobara.

    I’m subscribed to cloudLinux’s tuxcare enterprise updates for some older stuff, and I can’t recommend it enough. It’s excellent; and if almalinux releases their sLTS distro release and actually covers it for 25 years, that will be such a coup.

    I’m worried at the direction Linux has been taken by IBM and I hope it can be unfucked one day. I miss the reliable, fast boots and uncomplicated tooling before this systemd shitshow.












  • I can’t think of any case where a routine update caused trouble for me.

    I second this.

    Since about 2002, I’ve had a growing number of machines (ent Linux, similar to fedora) who simply patch nightly via cron. I get mail on the changes. In 24 years of yum-cron I’ve seen one error (busted deps on cobbler) and caused one error (too-old smb.conf during an update) and that’s it.

    So, my fuck-up aside, the only issue I’ve seen with a yum-cron patching setup (in dev/test and homelab) in ~25 years is exactly one issue on boxes running a mainstream but not prevalent piece of software due to a packaging glitch. That’s it.




  • Consider PCLinuxOS: they’re an RPM-based mandriva (mandrake/conectiva) derivative with really great and wide compatibility in stacks without the ‘modules’ shitfest RH started after no one remembered what ‘alternatives’ was for.

    They don’t use systemd, but their installation is a bit shite as it’s a “live CD” installer – they pruned out the proper templatey install that mandriva has. But so far that’s the biggest issue. If they can get off networkManager we’ll be even better off, though.