5 ms·

> 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 t

> 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. The systemd developers are tying it to systemd because they are systemd developers. If somebody else made something like this, it wouldn't be tied to systemd. But somebody else hasn't made something like this. Sudo isn't going to just go away (unfortunately). You can keep using your CVE-ridden setuid binary as much as you want.

constantcrying 2y ago
>The systemd developers are tying it to systemd because they are systemd developers. What? Literally every single other group of software developers has managed to create two projects. Even Microsoft can do it.
- SAI_Peregrinus 2y ago
  GNU didn't. Why should Systemd?
  - gkbrk 2y ago
    You can use almost any GNU project without depending on all the other GNU projects.
    - SAI_Peregrinus 2y ago
      This is different from Systemd how? You can't use any GNU project without depending on GNU libc (except glibc itself, trivially).
      - enriquto 2y ago
        That is not true. I use gnu tools compiled with musl libc.
      - gkbrk 2y ago
        > You can't use any GNU project without depending on GNU libc. Of course you can. Unless they're depending on non-standard parts of libc, you can use any GNU project with other libc implementations (musl, dietlibc, ulibc etc).
fanf2 2y ago
userv has been around for decades https://www.chiark.greenend.org.uk/~ian/userv/ https://www.chiark.greenend.org.uk/~ian/userv/
- throwaway7356 2y ago
  But userv requires code to be written specifically to work with userv, even for seemingly simple tasks as reading files. See 6.6 Error handling and input streams (eg stdin) on https://www.chiark.greenend.org.uk/~ian/userv/spec.html/ch-notes.html#s-stdinerr https://www.chiark.greenend.org.uk/~ian/userv/spec.html/ch-n... systemd's run0 on the other hand doesn't require code to be written specifically to work with it.
crashmat 2y ago
noting I have been recommended doas as a more lightweight version of sudo so other people are trying to do this kind of thing

constantcrying 2y ago

>The systemd developers are tying it to systemd because they are systemd developers. What? Literally every single other group of software developers has managed to create two projects. Even Microsoft can do it.

SAI_Peregrinus 2y ago
GNU didn't. Why should Systemd?
- gkbrk 2y ago
  You can use almost any GNU project without depending on all the other GNU projects.
  - SAI_Peregrinus 2y ago
    This is different from Systemd how? You can't use any GNU project without depending on GNU libc (except glibc itself, trivially).
    - enriquto 2y ago
      That is not true. I use gnu tools compiled with musl libc.
    - gkbrk 2y ago
      > You can't use any GNU project without depending on GNU libc. Of course you can. Unless they're depending on non-standard parts of libc, you can use any GNU project with other libc implementations (musl, dietlibc, ulibc etc).

fanf2 2y ago

userv has been around for decades https://www.chiark.greenend.org.uk/~ian/userv/ https://www.chiark.greenend.org.uk/~ian/userv/

throwaway7356 2y ago
But userv requires code to be written specifically to work with userv, even for seemingly simple tasks as reading files. See 6.6 Error handling and input streams (eg stdin) on https://www.chiark.greenend.org.uk/~ian/userv/spec.html/ch-notes.html#s-stdinerr https://www.chiark.greenend.org.uk/~ian/userv/spec.html/ch-n... systemd's run0 on the other hand doesn't require code to be written specifically to work with it.

crashmat 2y ago

noting I have been recommended doas as a more lightweight version of sudo so other people are trying to do this kind of thing