The big switch to systemd was always a mistake and this announcement just proves it.
Run0, a systemd based alternative to sudo, announced
471–480 of 902 posts
Re: Run0, a systemd based alternative to sudo, announced
#472I'm not a fan of sudo. It's does so much it needs BNF to describe it's configuration format. Who knows, maybe replacing the configuration with polkit is a good idea. Still it's a stand alone binary with one clear job to do, simple enough that one person has no trouble getting their head around it so it's not surprising it hasn't had too many problems over it's long life time. This made me smile: > sudo has serious pr…
Regarding your first point: some people agree, most notably the OpenBSD people who did something about it and wrote “doas” as a replacement; which fits the most common use-cases of sudo without fanfare.
Re: Run0, a systemd based alternative to sudo, announced
#473I'm not a fan of sudo. It's does so much it needs BNF to describe it's configuration format. Who knows, maybe replacing the configuration with polkit is a good idea. Still it's a stand alone binary with one clear job to do, simple enough that one person has no trouble getting their head around it so it's not surprising it hasn't had too many problems over it's long life time. This made me smile: > sudo has serious pr…
Isn't that link showing the opposite? That sudo is really large and systemd isn't? They even compare systemd with wpa_supplicant and it turns out they are the same size.
Re: Run0, a systemd based alternative to sudo, announced
#474I'm not a fan of sudo. It's does so much it needs BNF to describe it's configuration format. Who knows, maybe replacing the configuration with polkit is a good idea. Still it's a stand alone binary with one clear job to do, simple enough that one person has no trouble getting their head around it so it's not surprising it hasn't had too many problems over it's long life time. This made me smile: > sudo has serious pr…
The article you linked seems to be in support that systemd is in fact simpler than sudo.
Sudo, which only does privilege escalations, is only 1/3 the amount of code of the entirety of systemd.
Systemd-run has been around for many years now, this is simply an expansion of capabilities of features already exposed.
Re: Run0, a systemd based alternative to sudo, announced
#475Earlier quoted context omitted.
I can think of a number of things this tinting would break.
It violates the principle of Least Surprise; if I'm invoking run0 I'm expecting it to run my program with a different UID and return the same stdout I'd have gotten if I had just run the program in my shell. Not inject a whole bunch of color control bytes in there. Which hopefully my terminal will handle. Unless it doesn't. I'll give them the benefit of the doubt and assume they only do this if $TERM supports color.…
But sudo already doesn’t do that either. Eg sudo may ask for a password, and output some control sequences which hide the text so your password is not visible.
This feels like much ado about nothing.
Edit: Also don’t forget the “with great power comes great responsibility” blurb that sudo likes to output. I know that doesn’t happen in scripts when output is redirected, but I’m sure run0 will figure that out too.
Re: Run0, a systemd based alternative to sudo, announced
#476I'm not a fan of sudo. It's does so much it needs BNF to describe it's configuration format. Who knows, maybe replacing the configuration with polkit is a good idea. Still it's a stand alone binary with one clear job to do, simple enough that one person has no trouble getting their head around it so it's not surprising it hasn't had too many problems over it's long life time. This made me smile: > sudo has serious pr…
Ian Jackson (former Debian project leader) has been on this train for about 25 years now: https://www.gnu.org/software/userv/
Re: Run0, a systemd based alternative to sudo, announced
#477Earlier quoted context omitted.
IIRC, xz was used by a systemd library, and that systemd library got added to sshd so it could tell systemd when it had started or something like that. SSH itself doesn't use xz.
xz is a compression library.
I'm aware? It's a compression library that is used by systemd, including in a systemd library that got added to sshd in some distros.
Re: Run0, a systemd based alternative to sudo, announced
#478I'm not a fan of sudo. It's does so much it needs BNF to describe it's configuration format. Who knows, maybe replacing the configuration with polkit is a good idea. Still it's a stand alone binary with one clear job to do, simple enough that one person has no trouble getting their head around it so it's not surprising it hasn't had too many problems over it's long life time. This made me smile: > sudo has serious pr…
Isn't that link showing the opposite? That sudo is really large and systemd isn't? They even compare systemd with wpa_supplicant and it turns out they are the same size.
Not really. I'm not going the effort of breaking it down like he did, so just looking at total lines in the source calculated with "wc -l $(find . -type f)":
sudo: 284,103 systemd: 1,981,535
Re: Run0, a systemd based alternative to sudo, announced
#479Re: Run0, a systemd based alternative to sudo, announced
#480Earlier quoted context omitted.
Oh you do: this work completely differently from sudo, there is no suid binary involved, instead it does IPC to the systemd pid 1 and asks it to spawn you process, attached to your current terminal. So if you don't have systeme as pid 1, it'll have noone to talk to. Whether you like that or not is for you to decide.
IPC will likely be over d-bus. The new process will fork off a systemd which is almost always pid 1, but it might not have to be.
are there any non-systemd DBus options anymore? I had a hard time a year ago setting up Gentoo because there were no maintained options at that time.