←back to thread

Run0, a systemd based alternative to sudo, announced

(mastodon.social)
466 points CoolCold | 1 comments | 29 Apr 24 23:59 UTC | HN request time: 0.205s | source
Show context
constantcrying ◴[30 Apr 24 07:23 UTC] No.40208131[source]▶
Why do they have to do this? This is really, really stupid.

My issue isn't even that someone tries to replace sudo. That may or may not be a completely fine thing to do, depending on the state of sudo and what improvements can be made. But what makes me really upset is this completely unexplainable need to make everything part of one particular init system. There is absolutely no reason to tie your new sudo replacement to systemd. Absolutely none.

This is a completely insane way to develop software, instead of creating a new piece of software in a separate project they will force all their projects simultaneously onto all their users for absolutely no reason.

I am very glad to have jumped ship from systemd. It is particularly bad software created by a team of people who engage in very bad practices and a totally unhealthy view of software in general.

replies(15): >>40208192 #>>40208204 #>>40208221 #>>40208253 #>>40208266 #>>40208277 #>>40208280 #>>40208283 #>>40208314 #>>40208386 #>>40208516 #>>40209218 #>>40215207 #>>40215247 #>>40215377 #
dmm ◴[30 Apr 24 07:33 UTC] No.40208192[source]▶
> they will force all their projects simultaneously onto all their users for absolutely no reason.

That's just not true. Just because a system uses systemd the init system doesn't mean the it is forced to use the other components.

replies(2): >>40208527 #>>40214558 #
constantcrying ◴[30 Apr 24 08:29 UTC] No.40208527[source]▶
The single beat reason for doing this is to get a coherent complete system. This is what every other person here says.

You can not try to create a large coherent system and then tell people they shouldn't use that particular part. That is totally disingenuous. Systemd is DESIGNED to be an all or nothing deal.

replies(1): >>40209004 #
growse ◴[30 Apr 24 09:42 UTC] No.40209004[source]▶
> Systemd is DESIGNED to be an all or nothing deal.

^[Citation needed]

replies(1): >>40209285 #
constantcrying ◴[30 Apr 24 10:23 UTC] No.40209285[source]▶
Again and again people in this thread have told me that the great thing about systems is that it delivers integrated tools.
replies(2): >>40209768 #>>40215638 #
growse ◴[30 Apr 24 11:22 UTC] No.40209768[source]▶
And people are also telling you that tight integration is not a mandate. Having a bunch of stuff designed to work together does not mean that they're tightly coupled and can only work with their specific implementations.

We've all got confirmation bias, the trick is to be aware of it.

replies(1): >>40210009 #
constantcrying ◴[30 Apr 24 11:55 UTC] No.40210009[source]▶
This is such a bizarre statement. Of course any system with tight integration demands more precise specifications. Literally systems engineer 101.

This is such an absurd hill to die on.

replies(1): >>40212664 #
1. logicprog ◴[30 Apr 24 16:13 UTC] No.40212664[source]▶
You aren't making any sense. All of the components of system D are separate programs, and yes they are maintained by the same general project and designed to integrate well with each other, but just because components are designed to integrate well with other components from the same project if they are present, that doesn't remotely mean that all of the components are required. And I mean, the proof is in the pudding, there are plenty of distros that do not use all of the components of systemd. Also, doesn't Linux have a long history of creating integrated suites of programs designed to integrate well with each other and used together? Like GNU?