aboutsummaryrefslogtreecommitdiff
path: root/scripts/inittab
diff options
context:
space:
mode:
Diffstat (limited to 'scripts/inittab')
-rw-r--r--scripts/inittab86
1 files changed, 0 insertions, 86 deletions
diff --git a/scripts/inittab b/scripts/inittab
deleted file mode 100644
index 8e7e945b3..000000000
--- a/scripts/inittab
+++ /dev/null
@@ -1,86 +0,0 @@
1# /etc/inittab init(8) configuration for BusyBox
2#
3# Copyright (C) 1999 by Lineo, inc. Written by Erik Andersen
4# <andersen@lineo.com>, <andersee@debian.org>
5#
6#
7# Note, BusyBox init doesn't support runlevels. The runlevels field is
8# completely ignored by BusyBox init. If you want runlevels, use sysvinit.
9#
10#
11# Format for each entry: <id>:<runlevels>:<action>:<process>
12#
13# <id>: WARNING: This field has a non-traditional meaning for BusyBox init!
14#
15# The id field is used by BusyBox init to specify the controlling tty for
16# the specified process to run on. The contents of this field are
17# appended to "/dev/" and used as-is. There is no need for this field to
18# be unique, although if it isn't you may have strange results. If this
19# field is left blank, it is completely ignored. Also note that if
20# BusyBox detects that a serial console is in use, then all entries
21# containing non-empty id fields will _not_ be run. BusyBox init does
22# nothing with utmp. We don't need no stinkin' utmp.
23#
24# <runlevels>: The runlevels field is completely ignored.
25#
26# <action>: Valid actions include: sysinit, respawn, askfirst, wait, once,
27# ctrlaltdel, and shutdown.
28#
29# Note: askfirst acts just like respawn, but before running the specified
30# process it displays the line "Please press Enter to activate this
31# console." and then waits for the user to press enter before starting
32# the specified process.
33#
34# Note: unrecognised actions (like initdefault) will cause init to emit
35# an error message, and then go along with its business.
36#
37# <process>: Specifies the process to be executed and it's command line.
38#
39# Note: BusyBox init works just fine without an inittab. If no inittab is
40# found, it has the following default behavior:
41# ::sysinit:/etc/init.d/rcS
42# ::askfirst:/bin/sh
43# ::ctrlaltdel:/sbin/reboot
44# ::shutdown:/sbin/swapoff -a
45# ::shutdown:/bin/umount -a -r
46# if it detects that /dev/console is _not_ a serial console, it will
47# also run:
48# tty2::askfirst:/bin/sh
49# tty3::askfirst:/bin/sh
50# tty4::askfirst:/bin/sh
51#
52# Boot-time system configuration/initialization script.
53# This is run first except when booting in single-user mode.
54#
55::sysinit:/etc/init.d/rcS
56
57# /bin/sh invocations on selected ttys
58#
59# Note below that we prefix the shell commands with a "-" to indicate to the
60# shell that it is supposed to be a login shell. Normally this is handled by
61# login, but since we are bypassing login in this case, BusyBox lets you do
62# this yourself...
63#
64# Start an "askfirst" shell on the console (whatever that may be)
65::askfirst:-/bin/sh
66# Start an "askfirst" shell on /dev/tty2-4
67tty2::askfirst:-/bin/sh
68tty3::askfirst:-/bin/sh
69tty4::askfirst:-/bin/sh
70
71# /sbin/getty invocations for selected ttys
72tty4::respawn:/sbin/getty 38400 tty5
73tty5::respawn:/sbin/getty 38400 tty6
74
75# Example of how to put a getty on a serial line (for a terminal)
76#::respawn:/sbin/getty -L ttyS0 9600 vt100
77#::respawn:/sbin/getty -L ttyS1 9600 vt100
78#
79# Example how to put a getty on a modem line.
80#::respawn:/sbin/getty 57600 ttyS2
81
82# Stuff to do before rebooting
83::ctrlaltdel:/sbin/reboot
84::shutdown:/bin/umount -a -r
85::shutdown:/sbin/swapoff -a
86