• 4 Posts
  • 3.07K 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.











  • Long-term support and distro-branched tool chains are a boon to the workstation too. And all of lennarts cancer has been in support of dynamic networking changes and wifi devices; no overlap with a server, but they include that shit at every turn. So obviously they’re primarily geared for laptops and servers are a target of opportunity – and their decline in stability over 3-4 distro versions just backs that up.


  • So old code is now suddenly bad?

    Yes. It must go stale without some kind of needless churn; right?

    I loved solving a problem that redhat cant fix (because the smart people left) on their theForeman clone with a workaround that I learned from the days of NIS+. A 30-year-old workaround for last year’s shitty install.

    But fear of established, known-good code will certainly change that in the long run: ifconfig, netstat, ifup, fstab, xinet, service; the more we can churn out the working tools for neu dreck coded by dunning-kruger lost-boys kids who had no mentoring to prevent dumb patterns, the less the working solutions for known-good tools will work. And that’s, some how, “progress”.