From e58f84f3fbe211d5653d855a5741a66c9d9204ec Mon Sep 17 00:00:00 2001 From: Joachim Nilsson Date: Sun, 24 Sep 2017 20:54:27 +0200 Subject: [PATCH] Update introduction, much system config can be done using finit.d Signed-off-by: Joachim Nilsson --- README.md | 15 +++++++++------ 1 file changed, 9 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index 23a34edd..12ad7054 100644 --- a/README.md +++ b/README.md @@ -41,11 +41,14 @@ long boot times. Finit reduces context switches and forking of shell scripts to provide a swift [system bootstrap](doc/bootstrap.md) written entirely in C. -Configuration is read from [/etc/finit.conf](doc/config.md#etcfinitconf) -which details kernel modules to load, services and TTYs to start. When -the initial [bootstrap](doc/bootstrap.md) is done, including setting up -networking, all services in [/etc/finit.d/](doc/config.md#etcfinitd) and -the familiar [/etc/rc.local](#runparts--etcrclocal) are started. +The system configuration can be read from either the traditional single +file, [/etc/finit.conf](doc/config.md#etcfinitconf) and/or from small +per-service files in [/etc/finit.d/](doc/config.md#etcfinitd). These +files detail kernel modules to load, bootstrap tasks, services and TTYs +to start. When initial [bootstrap](doc/bootstrap.md) is done, including +setting up networking, all services the configured runlevel are started, +followed by running the familiar [/etc/rc.local](#runparts--etcrclocal) +script. **Example /etc/finit.conf:** @@ -53,7 +56,7 @@ the familiar [/etc/rc.local](#runparts--etcrclocal) are started. # Fallback if /etc/hostname is missing host default -# Runlevel to start after bootstrap, runlevel 'S' +# Runlevel to start after bootstrap, 'S', default: 2 runlevel 2 # Services to be monitored and respawned as needed