blob: 13a04afdccbb3c6ef3de4706cd1c6a504a84d860 [file] [log] [blame]
Erik Andersen36950522000-01-06 01:16:59 +00001# /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#
Erik Andersend7ce5e782000-02-09 04:40:25 +000026# <action>: Valid actions include: sysinit, respawn, askfirst, wait, once,
27# and ctrlaltdel.
Erik Andersen36950522000-01-06 01:16:59 +000028#
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
40# is found, it has the following default behavior:
41# ::sysinit:/etc/init.d/rcS
42# ::askfirst:/bin/sh
43# if it detects that /dev/console is _not_ a serial console, it will also run:
44# tty2::askfirst:/bin/sh
45#
46
Erik Andersen36950522000-01-06 01:16:59 +000047# Boot-time system configuration/initialization script.
48# This is run first except when booting in single-user mode.
49#
50::sysinit:/etc/init.d/rcS
51
52# /bin/sh invocations on selected ttys
53#
Eric Andersen7e3bf6e2000-09-14 22:01:31 +000054# Note below that we prefix the shell commands with a "-" to indicate to the
55# shell that it is supposed to be a login shell. Normally this is handled by
56# login, but since we are bypassing login in this case, BusyBox lets you do
57# this yourself...
58#
59# Start an "askfirst" shell on the console (whatever that may be).
60::askfirst:-/bin/sh
61#
62# Start an "askfirst" shell on /dev/tty2-4
63tty2::askfirst:-/bin/sh
64tty3::askfirst:-/bin/sh
65tty4::askfirst:-/bin/sh
Erik Andersen36950522000-01-06 01:16:59 +000066
67# /sbin/getty invocations for selected ttys
68#
Erik Andersen36950522000-01-06 01:16:59 +000069tty5::respawn:/sbin/getty 38400 tty5
Eric Andersen7e3bf6e2000-09-14 22:01:31 +000070tty6::respawn:/sbin/getty 38400 tty6
Erik Andersen36950522000-01-06 01:16:59 +000071
72# Example of how to put a getty on a serial line (for a terminal)
73#
74#ttyS0::respawn:/sbin/getty -L ttyS0 9600 vt100
75#ttyS1::respawn:/sbin/getty -L ttyS1 9600 vt100
76#
77# Example how to put a getty on a modem line.
78#ttyS2::respawn:/sbin/getty -x0 -s 57600 ttyS2
79
Erik Andersend7ce5e782000-02-09 04:40:25 +000080# Stuff to do before rebooting
Pavel Roskinf5cf8c62000-09-15 01:34:17 +000081::ctrlaltdel:/bin/umount -a -r
82::ctrlaltdel:/sbin/swapoff -a
Erik Andersen36950522000-01-06 01:16:59 +000083