also from my totally surface level understanding both sudo and doas “elevate your privileges” which is supposedly unnecessary attack surface. run0 does it in a better way which I do not understand.

sudo and doasare setuid binaries, a special privileged bit to tell the kernel that this binary is not run as the user starting it, but as the owner. A lot of care has to be incorporated into these to make sure you don’t escalate your privileges as the default interface is very limited, being a single bit.

Another issue with this approach is that since you’re running this from your shell, the process will by default inherit all environment variables, which can be convenient, but also annoying (since a privileged process might write into your $HOME) or upright dangerous.

run0doesn’t use that mechanism. systemd is, being a service manager at its core, something launching binaries in specialized environments, e.g. it will start an nginx process under the nginx user with a private tmp, protecting the system from writes by that service, maybe restrict it to a given address family etc. So the infrastructure to launch processes – even for users via systemd-run– is already there. run0 just goes one step further and implements an interface to request to start elevated (or rather with permissions different from their own) processes from a user’s shell.

Classic solutions do it like this:

1. user starts binary with setuid (let’s say sudo) that runs with root (because that’s the owner of the binary) privileges in their shell. Since this is a child process of their shell, it inherits all environment variables by default.
2. sudochecks /etc/sudoers if that user is authorized to perform the requested action and either denies the request, performs it or asks for authentication.
3. a new process is spawned from it, again inheriting the environment variables that were not cleaned, as you can’t get rid of variables by forking (this is often an issue if you have services that have their secrets configured via environment variables)

With run0:

1. user starts run0 binary as a user process. This process inherits the environment variables.
2. run0 forwards the user’s request via interface to the running systemd process (pid 1 I guess). That process however does not inherit any variables by default, since it was started outside the user’s shell.
3. systemd checks if the user who started the run0 binary is allowed to perform the requested operation and again, either denies the request, performs it or asks for authentication.
4. a new process is spawned from it, but it will only receive the environment variables that were explicitly requested as there’s no inheritance.

At least that’s my understanding, I haven’t looked too much into it or used it yet.

I mean it was a bit like a USB stick. Just nobody made the comparison back then because USB didn’t exist. But yes it is removable storage that is read/writable.

GameCube though…

Which is exactly what I’d use this for, were it not for the fact that I switched to the windows version of SV anyways. It wants an old system OpenSSL lib that’s insecure and I don’t have it. So wine with Windows version it is.

BASIC aus Büchern sind halt auch eher 30+ Jahre als 20 😉 die das von dir beschriebene Gefühl würde ich sagen hat man heute sogar mehr Möglichkeiten, installiert man sich eben ein(e) BSD, ein exotisches Linux oder Haiku OS. Oder Inferno…

Mainstream ist das natürlich alles nicht, aber das galt ja früher für die komplette IT.

Ich als solidarischer Westdeutscher habe meinen Teil getan und alle meine Immobilien in Leipzig für gemeinnützige Zwecke zur Verfügung gestellt

So Bürschchen jetzt reichts

Ich bin noch nicht so lange mit Computern dabei (irgendwelche DOS Kisten für die ich zu jung war, zu verstehen, was wirklich drin ist) aber immer wenn ich heute von Leuten höre, wie toll Computer früher waren (wir reden hier von Windows XP Zeit), denke ich nur NEIN, DIE WAREN DAMALS SCHEIẞE. Ich will den alten Ranz nicht zurück. Ich will nicht mehr sperrige IDE-Kabel verlegen. Ich will nicht mehr Master / Slave daran konfigurieren. Und nur weil du dich nicht 5 Minuten in die Thematik einlesen willst, heißt das auch nicht, dass BIOS MBR (primäre / sekundäre Partitionen irgendwer?) besser als das komplizierte UEFI mit Secure Boot ist. Nur weil dir Windows 11 und nervige Apps auf die Nüsse gehen, heißt das nicht, dass die Technik an sich heute nicht 100000 mal besser (und damit meine ich nicht nur schneller) ist als damals.

Davon abgesehen finde ich so GANZ alte Hardware mit ihren Beschränkungen (ähnlich wie auch Microcontroller) schon interessant. Aber da ist man ja schon fast näher an der Elektrotechnik als an der Informatik… aber das Geraffel von vor 20 Jahren kann mir komplett gestohlen bleiben.

Und ja das darf jetzt jemand anderes nach Zangendeutsch übersetzen

The base game is free, the price is for DLC.

Is it though? Normally it’s ironic: https://knowyourmeme.com/memes/stop-doing-math

I guess that’s where the advantages come into play the most. I only use it for a handful of machines (2 notebooks, one workstation, an SBC and 2 VPSs) and it’s still a great solution, though there is quite the overhead for the first setup.

Anyhow, that doesn’t mean that it’s more work in total than other distributions. The module system catches a lot of configuration errors for you which means you basically never and up with a “broken” configuration, and even if you did, you could select an older generation (more correct way to say rolling back on NixOS). Sure, the configuration might not do want you intended, but it will most likely be functional.

This even goes so far that some modules detect common configuration pitfalls for applications, like headers not being inherited because they got redefined.