←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.27s | source
Show context
Xeamek ◴[30 Apr 24 21:06 UTC] No.40216342[source]▶
2 weeks ago I didn't understood the systemd hate. But I tried to run udev-requiring program on non-systemd based distro.

And now I don't like systemd anymore.

replies(3): >>40216750 #>>40216857 #>>40217077 #
suprjami ◴[30 Apr 24 21:44 UTC] No.40216750[source]▶
So, you don't like a component because you ran software which requires that component, and you intentionally ran it in an environment without that component.

That does not make sense to me?

replies(3): >>40216780 #>>40216814 #>>40217775 #
Xeamek ◴[30 Apr 24 23:36 UTC] No.40217775[source]▶
No.

I don't like a framework that promotes using components that are arbitrary dependent on it.

To use udev, I need systemd-init, and to use systemd-init I need systemd boot.

I really don't believe it MUST be this way, and those requirements aren't at least partially arbitral.

Why systemd refuses to run in chroot?

replies(1): >>40219446 #
1. BenjiWiebe ◴[01 May 24 04:15 UTC] No.40219446[source]▶
You don't actually need to use systems-boot to use systemd-init. They're two separate things.