I like the idea of nixOS and will definitely try it in the future to see how portable I can make the setup be (hopefully a couple of files that can configure the entire machine).

But the only thing in my mind that is stopping it not being the absolute almost perfection of a tech-savy distro is the reliance of systemd, which has software that I as a user will never going to touch which adds unnecessary bloat to the init (also more unnecessary attack vectors). And if I really needed to have some of the systemd programs, there are replacements out there that do the job that can be later installed when needed, like having log files and stuff.

What do you think of some day seeing a fork of nixOS that uses other init systems and works well? Or is it just me that likes this idea? Like a voidish nixOS 🤔

  • BlanK0@lemmy.mlOP
    link
    fedilink
    arrow-up
    2
    arrow-down
    9
    ·
    11 months ago

    I am not saying this proves single-handedly that systemd has vulnerabilities but it is one of probably many out there. I am not saying enterprise is stupid but I could definitely see some sacrifice being possibly made to spend less time setting up utilities on every systemd machine for enterprise work.

    • atzanteol@sh.itjust.works
      link
      fedilink
      arrow-up
      7
      ·
      11 months ago

      I could definitely see some sacrifice being possibly made to spend less time setting up utilities on every systemd machine for enterprise work.

      I’m not sure how much time do you think anyone spends setting up systemd utilities… but as a home admin systemd has saved me a ton of time over the ragtag collection of shell scripts we had in the past. And a lot of that is because of its vastly improved logging.

      I suppose if you consider logs to be “bloat” you won’t understand though. I consider them to be essential services.

      • yianiris@kafeneio.social
        link
        fedilink
        arrow-up
        3
        ·
        11 months ago

        s6/66 simplifies dependency of running/starting, automatically enables an s6-log for each service/daemon/bundle it is much faster and smaller than systemd (by a factor of 10 maybe), and once it is up and running it is virtually impossible to bring down without its own routine. Servers have run consistenly for a decade with s6, including skarnet.org

        @atzanteol @BlanK0

      • BlanK0@lemmy.mlOP
        link
        fedilink
        arrow-up
        2
        arrow-down
        2
        ·
        11 months ago

        I was saying that you do spend less time cause it is already there. Also you can have logs on other init systems, what I said on the post is that if later I wanted logs I could just setup instead of being already there (and the other utilities, not just the logs of course).