caseyweederman

Cold dead god-damned hands

It’s like there’s an echo in here.

…I was on your side at the start but you really don’t need to keep poking the bear.

Oh, you’re not even the same person. All you’ve done here is poke bears that were already cowed.

You thought so, but there was a teleporter

My bad, I was just trying to meet you halfway and not suggest that you don’t actually know what you’re talking about, because that would be rude.

I don’t really care what dpkg is written in but I do know two things for a fact: Ubuntu’s coreutils upgrade broke Ubuntu because coreutils first gets removed, and Canonical’s official response was “apt maintainers will have to clean up our mess”: https://discourse.ubuntu.com/t/migration-to-rust-coreutils-in-25-10/59708
My memory was wrong on one point: dpkg is the workaround, apt is what the linked post blames.

Fair point. dpkg, being effectively some scripts, suddenly lose access to user-level utilities for managing files in the filesystem, like mv, mkdir, cp, ln, etc.

It’s not that they depend on coreutils, it’s that without coreutils, the operating system no longer has the tools to (for example) navigate and make changes to the file system.

They’re saying “dpkg needs to put in the work to make an exception for our specific use-case because why should we change it”

sudo-rs breaks Ansible. Imagine pushing this nightmare out to several hundred computers and then not being able to reverse it.

They’re very open about not being 1:1 on feature matching.
sudo-rs breaks Ansible privilege escalation. They blamed the Ansible team.
The Rust coreutils package upgrade removes coreutils from your system and then fails to install the new ones because there aren’t any coreutils installed. They blamed the dpkg team.

Remember Bitkeeper?

Yeah. OP got them laid was my first thought.

He’s actually a gojira but you were close

Fuck. We really need more variety in the web browser space too.

Well you Alexes seem a pretty cool bunch

Do I need to read Dark Alex 1 through 16 to have an appreciation of the plot or can I jump in here?

raises hand

The running kernel is not removed. Most (if not all?) distros will keep multiple previous kernels for fallback purposes. Some relatively recent projects will wait for system calls to complete and redirect new ones to the updated equivalent (see Live Kernel Patching).
The reason some things stop working is because the kernel modules directory is replaced. The running (old) kernel tries to access a module for a newer version and says nope.

Arch Linux has the package kernel-modules-hook which backs up the old modules and points the old kernel to them while it’s running. I’m not sure why it’s not installed by default.

ADHESIVE MEDICAL STRIP

but why