this post was submitted on 04 Oct 2023
725 points (95.3% liked)

linuxmemes

21282 readers
386 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
  •  

    Please report posts and comments that break these rules!


    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't fork-bomb your computer.

    founded 1 year ago
    MODERATORS
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] gunpachi@lemmings.world 14 points 1 year ago (1 children)

    I don't have anything against systemd that is until I tried void linux for the first time. The working of runit seemed very simple and efficient compared to the complexity of systemd.

    I still don't hate systemd, but I just wish it was simpler.

    [–] MeanEYE@lemmy.world 15 points 1 year ago (1 children)

    To be honest systemd is much simpler to me. Create a unit file, define what it depends on, accesses, etc. And you are done.

    [–] taladar@sh.itjust.works 12 points 1 year ago (1 children)

    And most importantly you don't have to deal with things like environment variables or other session state leaking into your startup scripts as you had with all the init script based init systems.

    I seriously do not miss services that worked when starting them from an ssh session but did not work on startup (because e.g. PATH had fewer directories).

    [–] MeanEYE@lemmy.world 4 points 1 year ago

    That too. I completely forgot about that.