BusyBox

BusyBox provides many common UNIX utilities in a single small executable for embedded systems. The community package includes runit; see runit for more information.

Note: Do not expect full drop-in replacement and compatibility. Certain utilities may not exist, and for those that do, there may be missing options.

Installation

Install the busybox package.

Busybox commands are symbolic links to /usr/bin/busybox and thus take very little space. This is especially interesting for low-footprint systems.

Usage

init

Init scripts can be used together with busybox-init, for example minirc-gitAUR. See init for details.

getty

The gettys are defined in the file /etc/inittab. By default, getty is started on ttys 1 through 4.

In order to enable/disable gettys, you just put this line in /etc/inittab.

tty2::respawn:/sbin/agetty -8 -s 38400 tty2 linux

Just replace tty2 with the tty you want getty to start on. If you want init to ask you before starting the gettty, then replace respawn with .

mdev

See Gentoo:mdev.

runit

See runit.

gollark: No.
gollark: Do I now.
gollark: They *have firmware for* a specific task. They are general purpose computers.
gollark: Well, they can all independently execute code.
gollark: - actual CPU- power management microcontroller on CPU- Intel Management Engine- Intel GuC on CPU (graphics microcontroller)- Intel *H*uC (HEVC microcontroller)- WiFi card microcontroller- Ethernet chip probably has a processor in it- dedicated GPU onboard microcontroller- display panel probably has a processor too, definitely at least an EEPROM- laptop embedded controller for general purpose things- camera microcontroller for debayering and USB- keyboard USB controller

See also

This article is issued from Archlinux. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.