source: branches/2.2.2/mindi-busybox/examples/inittab @ 1247

Last change on this file since 1247 was 821, checked in by Bruno Cornec, 14 years ago

Addition of busybox 1.2.1 as a mindi-busybox new package
This should avoid delivering binary files in mindi not built there (Fedora and Debian are quite serious about that)

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