simple-init

A set of init binaries for linux
git clone git://depsterr.com/git/simple-init
Log | Files | Refs | README | LICENSE

commit 6acff7521d213bdc0ae8a440444659ebc6925587
parent 1d939f932dd54693a4e4e50f4411d6020d3cf87b
Author: depsterr <depsterr@protonmail.com>
Date:   Sun, 31 May 2020 19:26:02 +0200

updated readme

Diffstat:
MREADME.md | 16+++++++++++++---
1 file changed, 13 insertions(+), 3 deletions(-)

diff --git a/README.md b/README.md @@ -1,18 +1,20 @@ # simple init -These are some linux init "scripts" written in C. The scripts are heavily inspired by [the kisslinux init scripts](https://github.com/kisslinux/init). However, unlike the kiss init scripts, my init script doesn't: +These are some Linux init "scripts" written in C. The scripts are heavily inspired by [the kisslinux init scripts](https://github.com/kisslinux/init). However, unlike the kiss init scripts, my init script doesn't: * support mdev, if you want/need this, then edit the source. * use any hooks, config files etc, if you want/need this, then edit the source. +I recommend using this in conjunction with [sinit](https://git.suckless.org/sinit) for a truly minimal init experience. + ## Adding services or hooks Just add them in `init.c` with a call to `spawn_process`, though beware of the following: -* Any process called by `spawn_process` which does not exit sucessfully (with an error code of 0) will cause `wait_for_children` to drop the user into a shell. +* Any process called by `spawn_process` which does not exit successfully (with an error code of 0) will cause `wait_for_children` to drop the user into a shell. -* If your process doesn't exit into the background `wait_for_children` will halt init. To work around this, create a shellscript which starts and disowns processes that you wish to start and then exits with code 0. Then execute this file instead. +* If your process doesn't exit into the background `wait_for_children` will halt init. To work around this, either create a shell script which starts and disowns processes that you wish to start and then exits with code 0 or mess around with the source. ## Installation @@ -21,3 +23,11 @@ If you can't figure this out on your own, then you should not try to install any ## WARNING USE THIS PROGRAM AT YOUR OWN RISK. IF YOU DO NOT KNOW WHAT YOU ARE DOING YOU RISK "BRICKING" YOUR LINUX INSTALL. + +## why? + +Systemd is bloated beyond repair + +Openrc, while better is needlessly large + +The kiss init scripts, while great, are shell scripts which limits speed as well as customizability.