this post was submitted on 01 Apr 2024
313 points (93.1% liked)

linuxmemes

21025 readers
518 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!

    founded 1 year ago
    MODERATORS
    poopsmith@lemmy.world
    zephyr@lemmy.world
    rtxn@lemmy.world
    313
    People who use distros without systemd, why do you do this? (lemmy.world)
    submitted 6 months ago by Waffelson@lemmy.world to c/linuxmemes@lemmy.world
    101 comments fedilink hide all child comments
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] linearchaos@lemmy.world 3 points 6 months ago

    It's a give and take honestly.

    System-d has better logging. Until you have something that needs to really really log. You can argue that if you have something that's that dependent on logging it shouldn't be logging through the console but it's worked fine for decades. Auto pruning of logs isn't necessarily ideal. Getting console logs and assist logs as a pain in the ass.

    Same goes for service dependencies we had this sorted it was answered via run levels and naming. It wasn't necessarily the most elegant solution but it was simple and there was very little to go wrong.

    The tools to manage the services and logs are needlessly complicated. Service start, service stop, service status, service log, service enable, service disable. And I shouldn't have to reload the Daemon every time I make a change.

    This isn't to say that it's all bad. It's flexible, and for most workflows, it's very automated and very light touch. The other pruning on the log file says probably saved a lot of downtime, a whole lot of downtime.

    It's really well suited to desktop.

    Service creation is somewhat easier.

    Dependencies are more flexible than run levels.

    To be honest I wouldn't go out of my way to run in a non-system distro but I would feel a little sigh of relief if something I was screwing with was still init.d