aboutsummaryrefslogtreecommitdiff
path: root/src/wiki/init/switching-to-sinit.md
blob: 180b736e706cffe37f11e7f411cf166fc3fe7778 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
Title: Switching to Sinit

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.