but you obviously don’t want 14 year olds to get drunk.
Which is totally legal here as long as the 14 year old is under supervision of a legal guardian.
but you obviously don’t want 14 year olds to get drunk.
Which is totally legal here as long as the 14 year old is under supervision of a legal guardian.
German here with similar laws to yours, though wine and beer legal with 16: legal age of 21 is in line with experts’ recommendations regarding brain development, however it’s questionable if this approach achieves the goal. If you want to discourage teenage drinking, make it unappealing, not illegal; but then we might have to acknowledge that we have an industry that heavily profits from a risky substance that puts a huge burden on society (several billion in damages each year) and we might have to regulate some aspects instead of just blaming the unfortunate people who got screwed over.
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.
Ich als solidarischer Westdeutscher habe meinen Teil getan und alle meine Immobilien in Leipzig für gemeinnützige Zwecke zur Verfügung gestellt
The base game is free, the price is for DLC.
Is it though? Normally it’s ironic: https://knowyourmeme.com/memes/stop-doing-math
You don’t subtract from 10, but from 10x0.999… I mean your statement is also true but it just proves the point further.
Hence the comment about “bias automation”
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 by 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.