From 979a10c2a68746565f330e871da2a0a112fa1604 Mon Sep 17 00:00:00 2001
From: Cem Keylan <cem@ckyln.com>
Date: Mon, 6 Apr 2020 12:06:20 +0300
Subject: initial commit

---
 docs/wiki/init/switching-to-sinit.txt | 51 +++++++++++++++++++++++++++++++++++
 1 file changed, 51 insertions(+)
 create mode 100644 docs/wiki/init/switching-to-sinit.txt

(limited to 'docs/wiki/init/switching-to-sinit.txt')

diff --git a/docs/wiki/init/switching-to-sinit.txt b/docs/wiki/init/switching-to-sinit.txt
new file mode 100644
index 0000000..3bee312
--- /dev/null
+++ b/docs/wiki/init/switching-to-sinit.txt
@@ -0,0 +1,51 @@
+
+Switching to Sinit
+==================
+
+Carbs Linux runs `busybox-init` by default. You can switch to
+anything else you desire, but only busybox-init and sinit are
+officially supported. Switching to sinit is extremely easy, you
+can be up and running within minutes. The only "hard" requirement
+is an environment you will be chrooting in. So, let's begin!
+
+
+Preparing your environment
+--------------------------
+
+From your other environment, download the kiss-chroot utility 
+and make it executable.
+
+    $ wget https://dl.getkiss.org/kiss-chroot
+    $ chmod +x kiss-chroot
+    
+    # From your environment start the chroot
+    $ kiss-chroot /mnt
+
+Removing busybox-init
+---------------------
+
+Now that we are in chroot environment, let's remove busybox-init.
+
+    $ kiss r busybox-init
+
+
+Installing and configuring sinit
+--------------------------------
+
+Build and install sinit
+
+    $ kiss b sinit
+    $ kiss i sinit
+
+Open up your `/etc/init/rc.conf` now and uncomment
+the variables regarding SINIT. You are ready now.
+
+If you edited your inittab, make sure you reflect your changes
+on the `/etc/init/sinit-launch-services.boot` file.
+
+
+Finishing up
+------------
+
+If all of the above is done, simply exit the chroot and reboot.
+Sinit should be functioning without any issues.
-- 
cgit v1.2.3