debian always seems to be forgotten outside of its server use

Nah, not even for servers. SLSA and ISO27002. Validation in the other distros is better, and that’s night-and-day for server sector.

I worked Unix in 99-06 and there’s a reason their Linux offering wasn’t debian: that validation hole.

I like cinnamon. Haven’t run desktop Linux since slackware, so it was a breath of fresh air on Nobara.

Nobara for fun, rocky for work.

I worked on United Linux, with suse. Never again.

That’s not really systemd’s fault though.

Oh, but it is. Upstart and sysV will both assassinate everything after a point. This bullshit is entirely new, either by Systemd sucking, or Systemd allowing this shit (thus, sucking), where neither thing happened beforehand.

I admit I rage when it’s starting or stopping and can’t win for all the losing – especially because “startup time” was the the main (unfounded) feature on the banner they waved around.

I work with sysV and Systemd and shut each down on a regular basis, via tooling, for stuff like patching, so it’s often a horse-race to offline. The difference is often negligible, for new machines or established boxes with apps, and the main difference is sometimes Systemd fails its YOU HAD ONE job from time to intermittent time.

I work in a team where Unix and Linux is ~15 very experienced admins, so don’t fret over the skills and experience question or the scale question.

Yes. I’m doing that with a 7040mff right now.

since endeavour is very close to arch I hope I’ll find some solutions in that realm.

Smart thinking. I don’t use arch (btw) either, so I’m merely a cheerleader at this point. Yes, I’d downgrade the kernel for the sake of Science. Find a popular stable kernel, jump to that and see if it behaves better.

(That may be my bias: I only really do enterprise linux, so after 28 years since I moved from slackware I’m really risk-averse!)

Yeah so grub can see the disk but then the kernel can’t. Efi and other tricks aren’t involved.

I think your route is to find out why the kernel hates your ass. Probably an upd pulled a driver … But who removes the SATA or nvme stuff?

Either way, it’s in the kernel and not the boot or the core apps. I don’t use endeavour, where I could provide better help, but I think the kernel is your best suspect for this crime.

That’s the joy of open source though: you can stop it. You are free to use another init system, fork projects

That and a big company looking to manufacture a perceived advantage by aggreasively pushing their shit into the mainstream - good fit to be taken over by IBM - who can bankroll the slapdash dev and bully ISVs, and you’re set.

your favorite thing is being ruined and you can’t stop it,

Hardly a ‘favourite thing’; it’s like making a water slide out of a river : Wantonly wrecking something simple, effective and usable for this mishmash isn’t ruining something sacred as much as it is destroying something for no reason to dramatically create something lesser the world didn’t need. Except with more hype, payola, ageism, strong-arm adoption and cult worship.

the virulently anti-systemd crowd are among the ones that baffle me the most.

Tell me you need to learn more about scope creep, Unix and system design using different words.

Mature software doesn’t need hourly updates. All the shit that leverages the library repos in horribly unsafe ways - ohai npm - that stuff needs constant updates.

Slackware -> rhl(4) -> rhel -> centos -> rocky

High SLSA, high iso27002.

Flatpak addressed one problem, but at tremendous cost.

The server part seems to be container-only. That’s a shame if you’re aware of iso27002 or SLSA.

and its clear you have negligible programming experience, or creative experience for that matter, to be coming after the concept of sharing code like-so.

As someone with several years of experience as a programmer: fuck off with this elitist nonsense

Well said. Bit of a Straw Man, there.

After that it’ll be roughly TEN rounds of interviews, the final one being with Mark Shuttleworth himself who may very well be a dick and decide he simply doesn’t like you.

A dear friend of mine went through this hiring process for a very senior spot. She’s been out of high-school for 35 years, has obtained 2 degrees since, and has run a hemisphere for a very nerdy storage-adjacent pro-serve company for a decade; but still needed to talk about her English marks in secondary school. I met her when we started our own company in '97.

She suffered 14 interviews, with the prep, interview - panel, group, or solo - taking a lot of her daytime. It was grueling. She met Mark, and it went very well. Her new boss and reports were making all kinds of positive noises about starting work soon.

A sub-stellar response from some French guy from Interview #3 torpedoed it. The rejection after all the essays, questions, prepared interviews and research was absolutely crushing and almost derailed the MBA programme she was on.

Thankfully Systemd is chatty like a kid talking about dinosaurs and so there’s lots of ASCII spooge on the screen, usually vomited to console. It’s half simplistically beautiful and half utter professional embarrassment.

The canonical method was with a kickstart, and if it looks like too complex, remember you should have one stashed in /root already that you just need to mod.

Normally a kickstart is a bit much, otherwise, though. I use a suite of tools but the best one I used was a simple virtual package to bring in the others, drop configs in and start daemons. We did this in like 2001 to great effect.

I ditched slackware in 98 after the validation issue became starkly problematic.

SLSA.dev .

Fedora is corporate? I nearly spat my coffee ;-)

I’m flashing back to working with suse on unitedlinux and the challenges we had. If you want a very Corporate distro, it’s right there.

Never again.