Download your favorite Linux distribution at LQ ISO.
Go Back > Blogs > zeebra
User Name


Rate this Entry

SystemFree (aka sysf), the systemd replacement

Posted 08-25-2019 at 05:25 AM by zeebra

So I went ahead an "sinned" in the eyes of some crowds by "talking about" a hush hush issue and/or "the impossible". A new init system. (THERE ARE ALREADY ALTERNATIVE INIT SYSTEMS!!!!!!!!!!!!!!!!!!!). Roger that mr negative.

What is SystemFree? It's a project to replace systemd. In it's full scope it is "systemd done right", in it's minimal form it is just a modular init. SystemFree what a stupid name! Yes indeed, it's not THE name, it's just a working title to reference (1) freeing the system, from systemd, which is the whole point in the first place. Another point is to (2) make a bridge between sysvinit and systemd and a third point is to (3) make a modular init which can replace (SysV or) systemd in systemd systems in a relatively easy way (from source) by non-newbie users, replace and remove. And to host a repository of pre-configured packages for various distroes where any user can replace systemd with SystemFree.

Just for clarification, I don't hate systemd, I think it has some points, it works well in many ways and I think it has some use. However I find it repulsive in so many ways. That's mostly ideological, and in the way it thus has been implemented. I'm not going to explain that now. But SystemFree is very much anti-systemd, it disagrees with the way systemd has done things and "solved" things and it aims to correct those.

SystemFree in reality is:
SysF init (sys6 init??)
sysfd (main module, working title "pid 101")
sysecd (system security daemon, cgroups etc)
sysd (systemd emulation daemon, for where that is needed)

The main problem is that an init itself no matter how big (big is bad), can replace systemd. Systemd has taken over various projects and made so many dependencies in the system core that it's pointless to view it at an init system. Thus to replace systemd, one also has to fork all the relevant software and make those software projects independent, in the spirit of doing it right. Do deblob systemd and split it into pieces. Several of these forks already exist, and it is the intention of SystemFree to make life easier for them, and to contribute (or in the case of start-stop-daemon, to integrate if possible).

SystemFree as a project is not going to be controlling and doing all that itself and keeping them as a SystemFree project, but it will do everything possible to support all those projects as independent projects and to contribute to them if possible. Those projects are the essential bridge between sysvinit and systemd. In a way SystemFree hopes to contribute to ALL existing init systems and all relevant projects and distroes. And to encourage the relevant parts of the community to do the same and also contribute and partake in those projects to make them thrive.

Sysfd is the core of systemfree, but can in reality be used by any init if the init itself makes it possible, it is part of SysFinit, but not integrated into it. It's a daemon and a "module" of SysF. Sysfd is where the majority of work is, while SysFinit is pretty much just a dumb minimal init, but slightly smarter. Stage1+? It can be configured to work as just an init or it can be configured to work with sysfd, but the "standard mode" is that it would be minimal and stable and pass everything on to sysfd. It would listen for sysfd, but could in practice listen to any replacement for sysfd as well.

In any case, I'm looking for intellectual and practical input on this topic.

We need (1) a plan and to come up with a plan we need to (2) map out the situation and reality and (3) analyse everything and (4) shape the main idea(s), only then can we start to (5) organise everything and actually make things happen. First and foremost we need to do the ground work first, we can't just skip right to coding without a proper plan. The situation and the needs are way too complex for that.
Posted in sysfd
Views 898 Comments 2
« Prev     Main     Next »
Total Comments 2


  1. Old Comment
    Sounds like a good idea. Maybe your init will do to systemd what systemd did to sysV: just appear out of nowhere and take over without anyone knowing why. Works for me.
    Posted 08-28-2019 at 09:15 PM by jr_bob_dobbs jr_bob_dobbs is offline
  2. Old Comment
    I do not have the programming knowledge, nor experience, in giving you intellectual or practical input on how to program a replacement for Systemd with a SystemFree init system. But, I see the need for a SystemFree init system of some form to replace Systemd. So, I am behind the concept and will try and keep abreast of the work by you and others. Keep us informed by your blog or through threads here on LQ.
    Posted 08-31-2019 at 05:01 AM by greencedar greencedar is offline


All times are GMT -5. The time now is 01:28 AM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration