From: Davin McCall <davmac@davmac.org>
Date: Wed, 3 Jul 2019 09:50:08 +0000 (+1000)
Subject: Minor updates to Linux Dinit-as-init guidelines.
X-Git-Tag: v0.6.0~17
X-Git-Url: https://git.librecmc.org/?a=commitdiff_plain;h=6ef81d60e8bc8d9600348c23063d1118c6813e4d;p=oweals%2Fdinit.git

Minor updates to Linux Dinit-as-init guidelines.
---

diff --git a/doc/linux/DINIT-AS-INIT.md b/doc/linux/DINIT-AS-INIT.md
index c825fc4..6c6529b 100644
--- a/doc/linux/DINIT-AS-INIT.md
+++ b/doc/linux/DINIT-AS-INIT.md
@@ -66,7 +66,7 @@ functionality, although at the cost of the losing automated integration.
 
 Some packages may rely on the "logind" functionality of Systemd for
 session/seat management. This same functionality is also provided by
-Elogind and ConsoleKit2, though I'm not to what degree nor level of
+Elogind and ConsoleKit2, though I'm not sure to what degree nor level of
 compatibility.
 
 In general I've found it quite possible to run a desktop system with Dinit
@@ -85,6 +85,8 @@ The basic procedure for boot (to be implemented by services) is as follows:
 - run root filesystem check
 - remount root filesystem read-write
 - start syslog deamon
+- various miscellaneous tasks: seed the random number generator, configure the
+  loopback interface, cleanup files in /tmp, /var/run and /var/lock
 - start other daemons as appropriate (dhcpcd, any networking daemons)
 - start getty instances virtual terminals