1. 24
  1.  

  2. 4

    Are Adelie, Devuan, and Obarun aware of the existence of dinit? If so what do they have to say about it?

    Having looked into init systems a few years ago (my knowledge may be out of date), it seems that the systemd detractors also don’t like the status quo. So what are they settling on? Last I heard, Alpine uses openrc, which not everyone is entirely happy with.

    1. 4

      I’ve assumed that they are aware of it at least to some degree, because I’ve been blogging about it for a while and I’ve occasionally seen reference to it crop up elsewhere, but i’ve never tried actually approaching these distributions to ask whether they would consider using Dinit. Partly this was because I didn’t want to be seen as pushing it on people, I had this idea that it would be good enough that it would be recognized for what it was worth and perhaps adopted for that reason.

      Some of them would no doubt prefer OpenRC or S6-RC to Dinit because those are simpler, and the complexity of Systemd is one of the things that people don’t like about it. There’s an idea that init should be as simple as possible, and if that’s what you want then Dinit isn’t a good match for you. Personally I believe there’s an ideal middle ground somewhere between Systemd and the others, and that’s what I’ve been aiming for.

      Maybe not pushing Dinit harder was the wrong call. I’ve considered talking to the Devuan people (mostly because I’m more familiar with Debian than I am these other distributions) to see what it would take to add Dinit as an option (I believe they currently offer Sys V init and OpenRC as options). I’m still having debating internally whether to do this (and whether to do it now, or once I’ve gotten it a llittle closer to what I’m planning to call version 1.0).

      1. 10

        I had this idea that it would be good enough that it would be recognized for what it was worth and perhaps adopted for that reason.

        There’s an old quote I heard once: “Don’t worry about people stealing your ideas, if your ideas are any good you’ll have to force them down people’s throats”.

        I think systemd is awesome, like C++ is awesome, for all the new capabilities it brings. However, I’m really looking forward to the generation of init systems after systemd, that learn from it and tame it, in the same way that Java, C#, Go, and Rust have all learned from C++ without copying it wholesale. I hope Dinit is one of those systems, but to get there you’re going to need an amazing feature (like Rust) or a lot of advertising (like Java, Go and C#) to win mindshare.

        1. 1

          Oof! Is there much uptake on s6? I’ve only seen it at one job, and, uh, it’s only in use on legacy systems there.

        2. 2

          Void uses runit. Devuan seemed to prefer the Sys V status quo. If anybody here ever comes across a thorough comparison between the new-ish non-systemd init systems, I hope they post a link. It’s something I’m mildly curious about, but not enough to do the research myself.

          1. 2

            I have a comparison of various inits/service managers in the Dinit repository, it’s not exhaustive but it tries to go into the differences in a meaningful way.

        3. 3

          System D

          oh boy better be careful they don’t hunt you down for the improper typesetting of “systemd”

          1. 5

            Haha! Yes, it upsets people when it’s not written as “systemd”, but in the title it’s actually meant to be an allusion to old science fiction films, think “Escape from planet X”. I always capitalise proper nouns though, and so I’ve (otherwise) called it Systemd (as I call my own system Dinit, though the executable is called “dinit”). As far as I’m concerned you can spell it however you like :)

            1. 5

              In my experience, people who insist on calling it SystemD are the pettiest of detractors.

              1. 2

                Also they’d insist on systemd, all lowercase, lol

                Yeah, agreed, it’s incredibly petty and stupid.

                1. 1

                  I mean, this is a community that still uses “Micro$oft” as a moniker, so…

                2. 1

                  Elasticsearch vs. ElasticSearch is also a fun one :)

                  1. 1

                    I remember SystemD being the right way to typeset it. At least, that’s what everyone seemed to be using at the start. Given I have had zero interest in the project since then (except using it on arch linux and finding it… inadequate for my purposes), I haven’t been updated with the systemd-official way of calling it. I do dislike systemd, but I think it’s silly to call everyone who hasn’t kept up to date with the name “detractors”.

                    Edit: Elsewhere in the thread there’s an implicit comparison between using SystemD and using Micro$oft. But I don’t see how you can compare those things. The first is a reasonably proper name for it (System Daemon, or whatever), the other is a jab at the FUD and EEE tactics of the corporation.

                3. 2

                  These kinds of things make me sad. I don’t know much about dinit and my experience actually using systemd is quite minimal. I’m by no means an administrator at work.

                  With that said though I’m not convinced that systemd was the best init out there, just the squeekiest wheel, if you know what I mean.

                  1. 1

                    I’ve always thought the most exciting thing about AI would be making robots that can cover the work needed so all human beings get to focus on what’s meaningful for them.

                    Do you mean squeaky as in squeaky-clean, or squeaky as in not-right?

                  2. 1

                    Oops, I just interpreted the number of the episode as the name of an editor.

                    1. 1

                      The catchprase:

                      What it needs more than anything is more users.