| Erik Andersen | 3695052 | 2000-01-06 01:16:59 +0000 | [diff] [blame] | 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, and once. |
| 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 |
| 39 | # is found, it has the following default behavior: |
| 40 | # ::sysinit:/etc/init.d/rcS |
| 41 | # ::askfirst:/bin/sh |
| 42 | # if it detects that /dev/console is _not_ a serial console, it will also run: |
| 43 | # tty2::askfirst:/bin/sh |
| 44 | # |
| 45 | |
| 46 | |
| 47 | # 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 | # |
| 54 | # Start an "askfirst" shell on the console (whatever that may be) |
| 55 | ::askfirst:/bin/sh |
| 56 | # Start an "askfirst" shell on /dev/tty2 |
| 57 | tty2::askfirst:/bin/sh |
| 58 | |
| 59 | # /sbin/getty invocations for selected ttys |
| 60 | # |
| 61 | tty4::respawn:/sbin/getty 38400 tty4 |
| 62 | tty5::respawn:/sbin/getty 38400 tty5 |
| 63 | |
| 64 | |
| 65 | # Example of how to put a getty on a serial line (for a terminal) |
| 66 | # |
| 67 | #ttyS0::respawn:/sbin/getty -L ttyS0 9600 vt100 |
| 68 | #ttyS1::respawn:/sbin/getty -L ttyS1 9600 vt100 |
| 69 | # |
| 70 | # Example how to put a getty on a modem line. |
| 71 | #ttyS2::respawn:/sbin/getty -x0 -s 57600 ttyS2 |
| 72 | |
| 73 | # Not currently supported, but may be sometime in the future... |
| 74 | #::ctrlaltdel:/sbin/reboot |
| 75 | |