reorganised

1 files changed, 0 insertions, 49 deletions

diff --git a/s6/base/scripts/rc.init b/s6/base/scripts/rc.init
deleted file mode 100755
index 56c3e7b..0000000
--- a/s6/base/scripts/rc.init
+++ /dev/null
@@ -1,49 +0,0 @@
-#!/bin/sh -e
-
-rl="$1"
-shift
-
-### argv now contains the arguments of the kernel command line that are
-### not of the form key=value. (The key=value arguments were stored by
-### s6-linux-init into an envdir, if instructed so via the -s option.)
-### Normally this argv remains unused because programs that need the
-### kernel command line usually read it later on from /proc/cmdline -
-### but just in case, it's available here.
-
-
-### 1. Early preparation
-### This is done only once at boot time.
-### Ideally, this phase should just initialize the service manager.
-
-### If your services are managed by sysv-rc:
-# /etc/init.d/rcS
-
-### If your services are managed by OpenRC:
-# /sbin/openrc sysinit
-# /sbin/openrc boot
-
-### If your services are managed by s6-rc:
-### (replace /run/service with your scandir)
-s6-rc-init -c /etc/s6/db/current /run/service
-
-
-### 2. Starting the wanted set of services
-### This is also called every time you change runlevels with telinit.
-### (edit the location to suit your installation)
-### By default, $rl is the string "default", unless you changed it
-### via the -D option to s6-linux-init-maker.
-### Numeric arguments from 1 to 5 on the kernel command line will
-### override the default.
-
-exec /etc/s6/base/scripts/runlevel "$rl"
-
-
-### If this script is run in a container, then 1. and 2. above do not
-### apply and you should just call your CMD, if any, or let your
-### services run.
-### Something like this:
-
-# if test -z "$*" ; then return 0 ; fi
-# $@
-# echo $? > /run/s6-linux-init-container-results/exitcode
-# halt