Slashdot Mirror

← Back to Stories (view on slashdot.org)

Fork of Systemd Leads To Lightweight Uselessd

Posted by timothy on from the not-big-and-fancy dept.

An anonymous reader writes A boycott of systemd and other backlash around systemd's feature-creep has led to the creation of Uselessd, a new init daemon. Uselessd is a fork of systemd 208 that strips away functionality considered irrelevant to an init system like the systemd journal and udev. Uselessd also adds in functionality not accepted in upstream systemd like support for alternative C libraries (namely uClibc and musl) and it's even being ported to BSD.

5 of 469 comments (clear)

  1. kill -1 by Spazmania · · Score: 5, Insightful

    If it still doesn't adequately support the "kill -1" functionality of initd (which kills and resets all processes init manages, especially the getty processes on the terminals), I still don't want it.

    --
    Moderating "-1, Disagree" is simple censorship. Have the guts to post your opinion.
    1. Re:kill -1 by arth1 · · Score: 5, Insightful

      The compatibility is a main reason. Being able to run and configure all startup/shutdown processes independently of the overseer is nice. As a sysadmin, I get to do easy manual corrections, additions and deletions without giving init a thought.
      i don't have to use the "service" command, and I spend far less time when seting up a new server or adding a service.

      i don't give a crap whether the system boots twice as fast - reboots are years between, and in scheduled windows. I want something that lets me admin my systems without relying on anything more than a dumb terminal - and if need be, not even that.

  2. Finally someone decides to do something by Skarjak · · Score: 5, Insightful

    That's how the free open source community works. If you don't like something, it's pointless to just spend a lot of time bitching about it (like many linux users have done about systemd). Just go out and make your own version. Everyone who's been complaining about systemd better contribute to this thing.

    1. Re:Finally someone decides to do something by Anonymous Coward · · Score: 5, Insightful

      Actually, that's a bad idea. They should go an support another init project that's already underway, like OpenRC. This is just protest software by a single guy.

  3. Re:Not a boycott but a confirmation by dskoll · · Score: 5, Insightful

    systemd does have some very good ideas when it comes to the init system. Socket-based activation and process supervision are Very Good Things.

    But when the systemd developers started trying to embrace, extend and extinguish other things like syslog, core dumps, etc. then systemd jumped the shark.