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…
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…
I always find this a little funny… Like I always hear complaints how the FDA is overbearing and stuff
It’s big corpos who’d love to continue using these additives that launch these claims via proxy into the public. Similar to how McDonald’s made sure people think the US is a country of frivolous lawsuits because they were ordered to cover a woman’s medical costs after a jury found them guilty. Purposeful misrepresentation of facts
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.
sudo
anddoas
are 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.
run0
doesn’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 viasystemd-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:
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.sudo
checks/etc/sudoers
if that user is authorized to perform the requested action and either denies the request, performs it or asks for authentication.With
run0
:run0
binary as a user process. This process inherits the environment variables.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.run0
binary is allowed to perform the requested operation and again, either denies the request, performs it or asks for authentication.At least that’s my understanding, I haven’t looked too much into it or used it yet.