• michaelmrose@lemmy.worldEnglish
      0·
      20 days ago

      Have you considered that just “reaping old process IDs” wasn’t enough responsibility for an init daemon on a secure, robust system? That maybe it should be protecting other parts of the system and tracking the liveness of a desired service?

      What is the benefit of specifically doing that in init?

      If I see an argument like this then I can only assume the interlocutor doesn’t do software engineering.

      Its more likely that the user simply has simple needs like running stuff at startup which any init system can do and doesn’t see as much benefits as poster.

      Also who loves systemd-resolved?

      • azertyfun@sh.itjust.works
        0·
        20 days ago

        Being able to assign a nameserver per interface with a domain wildcard is a fucking godsend. I use it every day with a hook script because my job uses some private domains but I don’t want to send my entire DNS history through the VPN. Now ~job.com goes to tun0 and that’s the end of it.

        systemd-resolved is not perfect but with libnss’s overly rigid nature the only alternative for my use-case would be to recreate similar functionality to resolved with dnsmasq – which is just objectively worse especially when you want to use DHCP sometimes but not always. Why reinvent the wheel? resolved does its job and does it well. I had some issues with it a few years ago but have been using it for the past couple years without complaint.

      • anyhow2503@lemmy.world
        0·
        20 days ago

        What is the benefit of specifically doing that in init?

        What’s the alternative?

        Also who loves systemd-resolved?

        I don’t think I will ever love anything DNS-related, but it’s still the best solution I’ve used for name resolution on a system with many interfaces.

    • Wildmimic@anarchist.nexusEnglish
      0·
      20 days ago

      I fully agree. I am a user with a bit of technical background, but not a lot of detailled knowledge about the inner workings of an operating system (i know boolean logic and basic programming structures - in Pascal lol - from the 90’s, what a transistor does and stuff, how to build my own PCs and handle filesystems and troubleshooting).

      With init scripts, i hit a wall pretty fast.

      With Systemd i know how to start, stop and configure services, and the suite built around it uses the same conventions everywhere, making the everyday life with Linux for someone like me so much easier and more transparent than ever before.

  • zalgotext@sh.itjust.works
    0·
    20 days ago

    I’ve only ever used systemd, and I’m not really aware of what else is out there, since I think systemd has been the default on all the distros I’ve tried. Anyone have some good resources on other alternatives and how to start playing around with them?

    • anyhow2503@lemmy.world
      0·
      20 days ago

      Most non-systemd users are either contrarians or people who don’t want to switch their workflow from some other system that they already know perfectly.

      I will always welcome alternative systems on principle alone, but at this point there is not much need for linux “consumers” to consider anything else (unless their distro doesn’t ship with systemd of course).

  • Auli@lemmy.caEnglish
    0·
    20 days ago

    Yes I like it and it is loads better then what came before it.

  • ronflex@lemmy.world
    0·
    19 days ago

    Systemd has simplified my life on a few occasions, and it seems to be reliable from what I can tell. At the end of the day if I can get the OS to do what I want in a relatively simple matter, that’s all I care about.

    • Lettuce eat lettuce@lemmy.ml
      0·
      15 days ago

      In all seriousness, I’ve yet to encounter a situation where Systemd made any meaningful negative difference in my Linux experience.

      I’ve never had problems with any init system, Systemd or otherwise.

  • floquant@lemmy.dbzer0.com
    0·
    19 days ago

    Systemd is fine.

    Journald is fine.

    But someone pass me a mace I can beat systemd-resolved and systemd-logind to death with

    EDIT: Oh come on

    • Trainguyrom@reddthat.comEnglish
      0·
      21 days ago

      Since I started actually doing system administration and actually interacting directly with SystemD all of the hate for it I’d soaked up from enthusiast forums melted away. I’ve never used any of the other init systems so maybe I’m missing out, but I do appreciate SystemD for what it does

  • whoisearth@lemmy.ca
    0·
    20 days ago

    My biggest complaint with systemd…

    Service xxx stop/start/restart is so much easier than

    Systemctl stop/start/restart xxx

    It fucking annoys me

    • Petter1@discuss.tchncs.de
      0·
      17 days ago

      I neaver bothered me too much, can you not alias stop to sudo sytemctl stop xxx

      Like that you can write “stop wpa_supplicant” instead od “Sudo systemctl stop wpa_supplicant. “

  • Marn@lemmy.dbzer0.com
    0·
    21 days ago

    I would replace grub in a heartbeat with systemd if it a feature like grub-btrfs (boot time snapshots for btrfs all in the GUI)