After about three years of development Published The initialization system release FAST INIT, developed as a simple alternative to SYSV INIT and SYSTEMD. The project is based on the operations created by foaming the Fastinit initialization system used in the EEEPC netbook Linux-firmware and a remarkable very fast loading process. The system is primarily aimed at ensuring the download of compact and embedded systems, but can also be used for conventional desktop and server environments. Examples of scripts for embedding prepared for Void Linux, Alpine Linux and Debian GNU / Linux. The project code is written in the Si language and extends under the MIT license.
Finit supports execution levels ( RunLevel ) in the SYSV Init style, tracking background process performance (for automatic restart in case of failure ), Perform disposable handlers, launching services, taking into account dependencies and arbitrary conditions, attaching additional handlers to start before or after the service is executed. For example, you can configure the start of service only after accessing the network or after some other service is running, such as syslogd. CGroups v2 is used to specify restrictions.
To expand functionality and adaptation, plugins for which the Hooks system are provided can be used to attach the handler to various downloads and executing services, as well as to tie to external events. For example, plugins to support D-BUS, ALSA, NETLINK, RESOLVCONF, hot device connection, availability checks and download the kernel modules, processing PID files and settings for the X server.
Supports the use of typical scripts to start the services created for SYSV Init (/etc/rc.d and /etc/init.d are not used, but support / etc / inittab can be implemented via plugin), as well as RC scenarios. Local, files with environment variables and network settings / etc / network / interfaces, as in Debian and BusyBox. Settings can be defined in one /etc/finit.conf configuration file, and distributed over multiple files in the /etc/finit.d directory.
Control is carried out through the Typical InitTL and Run-Parts toolkit, allowing you to activate and deactivate services in binding to launch levels, as well as selectively run part of the services. The FINIT also includes built-in GETTY implementation (Terminal and user input), Watchdog to track performance and recovery mode After a failure with built-in Sulogin to start an isolated command shell.
