examples/inittab - busybox - Git at Google

 # /etc/inittab init(8) configuration for BusyBox
 #
 # Copyright (C) 1999 by Lineo, inc.  Written by Erik Andersen
 # <andersen@lineo.com>, <andersee@debian.org>
 #
 #
 # Note, BusyBox init doesn't support runlevels.  The runlevels field is
 # completely ignored by BusyBox init. If you want runlevels, use sysvinit.
 #
 #
 # Format for each entry: <id>:<runlevels>:<action>:<process>
 #
 # <id>: WARNING: This field has a non-traditional meaning for BusyBox init!
 #
 #	The id field is used by BusyBox init to specify the controlling tty for
 #	the specified process to run on.  The contents of this field are
 #	appended to "/dev/" and used as-is.  There is no need for this field to
 #	be unique, although if it isn't you may have strange results.  If this
 #	field is left blank, it is completely ignored.  Also note that if
 #	BusyBox detects that a serial console is in use, then all entries
 #	containing non-empty id fields will _not_ be run.  BusyBox init does
 #	nothing with utmp.  We don't need no stinkin' utmp.
 #
 # <runlevels>: The runlevels field is completely ignored.
 #
 # <action>: Valid actions include: sysinit, respawn, askfirst, wait, once,
 #                                  and ctrlaltdel.
 #
 #       Note: askfirst acts just like respawn, but before running the specified
 #       process it displays the line "Please press Enter to activate this
 #       console." and then waits for the user to press enter before starting
 #       the specified process.
 #
 #       Note: unrecognised actions (like initdefault) will cause init to emit
 #       an error message, and then go along with its business.
 #
 # <process>: Specifies the process to be executed and it's command line.
 #
 # Note: BusyBox init works just fine without an inittab.  If no inittab
 # is found, it has the following default behavior:
 #	::sysinit:/etc/init.d/rcS
 #	::askfirst:/bin/sh
 # if it detects that /dev/console is _not_ a serial console, it will also run:
 #	tty2::askfirst:/bin/sh
 #


 # Boot-time system configuration/initialization script.
 # This is run first except when booting in single-user mode.
 #
 ::sysinit:/etc/init.d/rcS

 # /bin/sh invocations on selected ttys
 #
 # Start an "askfirst" shell on the console (whatever that may be)
 ::askfirst:/bin/sh
 # Start an "askfirst" shell on /dev/tty2
 tty2::askfirst:/bin/sh

 # /sbin/getty invocations for selected ttys
 #
 tty4::respawn:/sbin/getty 38400 tty4
 tty5::respawn:/sbin/getty 38400 tty5


 # Example of how to put a getty on a serial line (for a terminal)
 #
 #ttyS0::respawn:/sbin/getty -L ttyS0 9600 vt100
 #ttyS1::respawn:/sbin/getty -L ttyS1 9600 vt100
 #
 # Example how to put a getty on a modem line.
 #ttyS2::respawn:/sbin/getty -x0 -s 57600 ttyS2

 # Stuff to do before rebooting
 ::ctrlaltdel:/bin/umount -a -r > /dev/null 2>&1
 ::ctrlaltdel:/sbin/swapoff -a > /dev/null 2>&1
	# /etc/inittab init(8) configuration for BusyBox
	#
	# Copyright (C) 1999 by Lineo, inc. Written by Erik Andersen
	# <andersen@lineo.com>, <andersee@debian.org>
	#
	#
	# Note, BusyBox init doesn't support runlevels. The runlevels field is
	# completely ignored by BusyBox init. If you want runlevels, use sysvinit.
	#
	#
	# Format for each entry: <id>:<runlevels>:<action>:<process>
	#
	# <id>: WARNING: This field has a non-traditional meaning for BusyBox init!
	#
	# The id field is used by BusyBox init to specify the controlling tty for
	# the specified process to run on. The contents of this field are
	# appended to "/dev/" and used as-is. There is no need for this field to
	# be unique, although if it isn't you may have strange results. If this
	# field is left blank, it is completely ignored. Also note that if
	# BusyBox detects that a serial console is in use, then all entries
	# containing non-empty id fields will _not_ be run. BusyBox init does
	# nothing with utmp. We don't need no stinkin' utmp.
	#
	# <runlevels>: The runlevels field is completely ignored.
	#
	# <action>: Valid actions include: sysinit, respawn, askfirst, wait, once,
	# and ctrlaltdel.
	#
	# Note: askfirst acts just like respawn, but before running the specified
	# process it displays the line "Please press Enter to activate this
	# console." and then waits for the user to press enter before starting
	# the specified process.
	#
	# Note: unrecognised actions (like initdefault) will cause init to emit
	# an error message, and then go along with its business.
	#
	# <process>: Specifies the process to be executed and it's command line.
	#
	# Note: BusyBox init works just fine without an inittab. If no inittab
	# is found, it has the following default behavior:
	# ::sysinit:/etc/init.d/rcS
	# ::askfirst:/bin/sh
	# if it detects that /dev/console is _not_ a serial console, it will also run:
	# tty2::askfirst:/bin/sh
	#


	# Boot-time system configuration/initialization script.
	# This is run first except when booting in single-user mode.
	#
	::sysinit:/etc/init.d/rcS

	# /bin/sh invocations on selected ttys
	#
	# Start an "askfirst" shell on the console (whatever that may be)
	::askfirst:/bin/sh
	# Start an "askfirst" shell on /dev/tty2
	tty2::askfirst:/bin/sh

	# /sbin/getty invocations for selected ttys
	#
	tty4::respawn:/sbin/getty 38400 tty4
	tty5::respawn:/sbin/getty 38400 tty5


	# Example of how to put a getty on a serial line (for a terminal)
	#
	#ttyS0::respawn:/sbin/getty -L ttyS0 9600 vt100
	#ttyS1::respawn:/sbin/getty -L ttyS1 9600 vt100
	#
	# Example how to put a getty on a modem line.
	#ttyS2::respawn:/sbin/getty -x0 -s 57600 ttyS2

	# Stuff to do before rebooting
	::ctrlaltdel:/bin/umount -a -r > /dev/null 2>&1
	::ctrlaltdel:/sbin/swapoff -a > /dev/null 2>&1