

Yeah, the arch installation on my desktop is about a decade old at this point. It was installed on a completely different computer. No issues.


Yeah, the arch installation on my desktop is about a decade old at this point. It was installed on a completely different computer. No issues.
My friend, a podman container file is a simple tiny ini text file. Behind the scenes it gets converted to a systemd service unit file, which is also an ini text file. The service file has a simple ExecStart command that just calls podman run. Meanwhile podman will just set up an environment and run the container with runc or crun. The whole thing is basically one step above a shell script. I could buildroot a system with this entire stack and it would fit on my wifi router.
You’re the one overcomplicating things.
That sounds heavy and complicated.
It’s neither. A systemd generator just transforms a simple 15 line container text file to a simple 20 line service text file, and then the container lifecycle and dependencies are managed by systemd like any other system or user service.
It’s not tightly coupled to anything. It just ships with a systemd generator allowing you to manage containers, pods or networks with systemd if you want. And lots of people are noticing the benefits of that arrangement.
And somehow more “independent” than arch, when it’s based on arch?
Not even, amd on both my laptop and desktop, but still lots of issues. None of them major, but it adds up.
while they happily stick to the X they know
Gnome forced me onto Wayland a few weeks ago and I’ve been dealing with issues ever since. Some issues even affecting the most basic level tasks like typing text, imagine dealing with that in 2025. Following your analogy, if the Uber with the fancy new transmission came to a halt every kilometre, you’d care too.
And xorg is older than it appears, as it was forked from the much older XFree86 over licensing disagreements. XFree86 started in 1991 according to Wikipedia.


More like:
No system package -> installing from user repos -> appimage -> flatpak -> creating your own package -> using a VM with a distro that has the package -> not installing package
If after that you still don’t have it, it wasn’t meant to be it’s probably just not very good software.


I’ve had it run on wine a few years back, but it’s hard to say if it would still run now as they change it all the time. Freecad is ok for simpler designs, but if you do complex cad work, you hit its limits (clunky and buggy). There’s always onshape though, works perfectly fine on Linux.


I use quadlets instead - it’s part of podman and lets you manage containers as systemd services. Supports automatic image updates and gives you all the benefits of systemd service management. There’s a tool out there that will convert a docker compose config into quadlet unit files giving you a quick start, but I just write them by hand.
Well, you have to own one of these things when you’re a king, you know.
The thing I’m supposed to be doing is on workspace 3…
I recently needed to build newer versions of some packages for Debian. Now, they’re go based so the official packaging is super complicated and eventually I decided to try and make my own from scratch. After a few more hours of messing with the official tooling I start thinking “there must be a better way.”
And sure enough, after a bit of searching I found makedeb which allows you to make debs from (almost) regular PKGFILEs. Made the task a million times simpler.
They’re going after the anger dollar, that’s a good dollar. We’ve done research.
That screen is from cloudflare. It means you’re blocking their JavaScript or iframe elements used to create the bot challenge. I get it quite often as I still use the old uMatrix extension. Temporarily unblocking and refreshing the page will let you through.