If you like BoxMatrix then please contribute Supportdata, Supportdata2, Firmware and/or Hardware (get in touch).
My metamonk@yahoo.com is not reachable by me since years. Please use hippie2000@webnmail.de instead.
Property:linuxrc
| BoxMatrix >> Shell-Commands >> linuxrc | @ BoxMatrix - IRC-Chat - Translate: de es fr it nl pl |
| News | Selectors | Models | Accessories | Components | Environment | Config | Commands | System | Webif | Software | Develop | Lexicon | Community | Project | Media |
| Startup-Scr | Hotplug-Scr | BusyBox-Cmds | Bash-Cmds | AVM-Cmds | Chipset-Cmds | Linux-Cmds | Shared-Libs | Kernel-Mods | Research |
BusyBox-Command
| Command: | linuxrc - type Link | Wiki | Freetz | IPPF | whmf | AVM | Web |
| Location: | Shell-Commands >> BusyBox-Commands - Origin: busybox | ||||||
| Path: | Release: /, /bin, <bb> Lab+Rel: /, /bin, <bb> | ||||||
| Properties: | Size: Link - Firmware: 1.63 - 7.60 | ||||||
| Function: | Init is the first process started during boot. It never exits. | ||||||
Goto: GPL-Browser - Dependencies - Model-Matrix - Symbols - SMW-Browser
Details
Excerpt from: BusyBox manual >> linuxrc command
No manual entry for this command.
Excerpt from: BusyBox source >> linuxrc command - Last update: 2024-04-24 03:56 GMT.
Usage:
linuxrc
Usage:
linuxrc
Init is the first process started during boot. It never exits.
This version of init is designed to be run only by the kernel.
BusyBox init doesn't support multiple runlevels. The runlevels field of
the /etc/inittab file is completely ignored by BusyBox init. If you want
runlevels, use sysvinit.
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
::ctrlaltdel:/sbin/reboot
::shutdown:/sbin/swapoff -a
::shutdown:/bin/umount -a -r
::restart:/sbin/init
tty2::askfirst:/bin/sh
tty3::askfirst:/bin/sh
tty4::askfirst:/bin/sh
If you choose to use an /etc/inittab file, the inittab entry format is as follows:
<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 be unique, although if it isn't you may have strange results. If this
field is left blank, then the init's stdin/out will be used.
<runlevels>:
The runlevels field is completely ignored.
<action>:
Valid actions include: sysinit, respawn, askfirst, wait,
once, restart, ctrlaltdel, and shutdown.
The available actions can be classified into two groups: actions
that are run only once, and actions that are re-run when the specified
process exits.
Run only-once actions:
'sysinit' is the first item run on boot. init waits until all
sysinit actions are completed before continuing. Following the
completion of all sysinit actions, all 'wait' actions are run.
'wait' actions, like 'sysinit' actions, cause init to wait until
the specified task completes. 'once' actions are asynchronous,
therefore, init does not wait for them to complete. 'restart' is
the action taken to restart the init process. By default this should
simply run /sbin/init, but can be a script which runs pivot_root or it
can do all sorts of other interesting things. The 'ctrlaltdel' init
actions are run when the system detects that someone on the system
console has pressed the CTRL-ALT-DEL key combination. Typically one
wants to run 'reboot' at this point to cause the system to reboot.
Finally the 'shutdown' action specifies the actions to taken when
init is told to reboot. Unmounting filesystems and disabling swap
is a very good here.
Run repeatedly actions:
'respawn' actions are run after the 'once' actions. When a process
started with a 'respawn' action exits, init automatically restarts
it. Unlike sysvinit, BusyBox init does not stop processes from
respawning out of control. The 'askfirst' actions acts just like
respawn, except that before running the specified process it
displays the line and then waits for the user to press enter before starting the
specified process.
Unrecognized actions (like initdefault) will cause init to emit an
error message, and then go along with its business. All actions are
run in the order they appear in /etc/inittab.
<process>:
Specifies the process to be executed and its command line.
Example /etc/inittab file:
# 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:-/bin/sh
# Start an tty2::askfirst:-/bin/sh
tty3::askfirst:-/bin/sh
tty4::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)
#
#::respawn:/sbin/getty -L ttyS0 9600 vt100
#::respawn:/sbin/getty -L ttyS1 9600 vt100
#
# Example how to put a getty on a modem line
#::respawn:/sbin/getty 57600 ttyS2
# Stuff to do when restarting the init process
::restart:/sbin/init
# Stuff to do before rebooting
::ctrlaltdel:/sbin/reboot
::shutdown:/bin/umount -a -r
::shutdown:/sbin/swapoff -a
Note that some options may not be compiled in. If Usage: is shown multiple times these are compile options.
GPL-Browser
Daily updated index of all linuxrc code findings on the GPL-Browser. Last update: 2024-04-24 04:14 GMT.
The Browse column points to the Path containing the respective source code on the gpl.boxmatrix.info service.
The SoC column lists the Chip-Codenames, the Model column lists the nicks of the Box-Models.
The Diff column links the comparison of the AVM Kernel to the pristine original from Kernel.org.
The Download column links the full tarball the respective directory content is extracted from.
The presence of the source does not mean it fits the respective model and architecture. See the Model-Matrix where it's used.
Excerpt from: BusyBox manual >> linuxrc command - Last update: 2009-10-02 09:23 GMT.
Dependencies
Daily updated index of all dependencies of this command. Last update: 2024-04-24 07:26 GMT.
A * in the Mod column marks info from Supportdata-Probes, which will always stay incomplete.
| Relation | Typ | Object | Mod | Firmware | Info | Origin |
|---|---|---|---|---|---|---|
| Symlink to | cmd | busybox (bbcmd) | 2 | 7.59 - 7.60 | The BusyBox executable itself. Contains the code for all applets. | BusyBox |
| 1 dependency for this command | ||||||
Model-Matrix
Daily updated index of the presence, path and size of this command for each model. Last update: 2024-04-24 05:11 GMT.
Showing all models using this command. Click any column header (click-wait-click) to sort the list by the respective data.
The (main/scrpn/boot/arm/prx/atom) label in the Model column shows which CPU is meant for models with multiple Linux instances.
Note that this list is merged from Firmware-Probes of all known AVM firmware for a model, including Recovery.exe and Labor-Files.
The path <bb> means the applet could be located in the busybox binary and could be called busybox linuxrc.
If a path is shown and no <bb> marker, then this is a dead link to a missing applet.
| Model | Firmware | Path | Size |
|---|---|---|---|
| FRITZ!Box SL | 1.63 | <bb> | |
| FRITZ!Box 5690 Pro (arm) | 7.59 - 7.60 | <bb> | |
| FRITZ!Box 5690 Pro (rtl) | 7.59 - 7.60 | / | Link |
| FRITZ!Box 6660 Cable (arm) | 7.14 | <bb> | |
| FRITZ!Box 6660 Cable (atom) | 7.14 | <bb> | |
| FRITZ!Box 7490 (main) | 7.19 | <bb> | |
| FRITZ!Box 7490 (scrpn) | 7.19 | <bb> | |
| FRITZ!Box 7520 v2 (arm) | /bin, <bb> | Link | |
| 8 models use this command | |||
Symbols
Daily updated index of all symbols of this command. Last update: 2024-04-24 07:26 GMT.
| Firmware | Symbol |
|---|---|
| 0 symbols for this command | |
