BusyBox
BusyBox is a single compact executable that bundles many common UNIX command-line utilities into one tiny binary.
Platform availability
Available on 0 of 10 platforms
- Unraid (not listed)
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm (not listed)
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
40/100 Fair
- Maintained
- 0last commit 860 days ago
- Popular
- 672,192 GitHub stars
- Easy to install
- 250 install platforms, install notes, Docker image
- Light to run
- 100128 MB minimum RAM
- Security check
- 59no serious findings, tests, OpenSSF Scorecard 1.9/10
- GitHub stars
- 2,192
- Open issues
- 94
- Last commit
- 2024-07-13
- Activity
- stale
Checked 18 days ago - source: GitHub (mirror/busybox)
Resources & Compatibility
Minimum requirements: 128 MB RAM. ARM (e.g. Raspberry Pi) is not supported.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Set up mdev so devices appear If you're using BusyBox on a minimal Linux system, mount /proc and /sys, tell the kernel to use /sbin/mdev when new hardware appears, and run mdev -s to scan existing devices. Without this, /dev can stay empty, so consoles, disks, and other devices won't work. source
- Prepare /dev and /dev/pts first If you're booting from flash, mount a small tmpfs (a temporary RAM filesystem) on /dev, create /dev/pts, and mount devpts before basic mdev setup. This gives device nodes room in RAM and terminal programs the /dev/pts entries they need. source
- Set device permissions in mdev.conf In /etc/mdev.conf, add a rule such as hd[a-z][0-9]* 0:3 660 so disk devices like hda/hdb get the owner/group and permissions you want. If these are wrong, users or apps may get access denied when opening disk devices. source
Fetched 53 days ago - each note links to its source
Variants
Alternatives (2)
Checked 54 days ago - source: AlternativeTo
Common questions
How do I get device nodes populated on a minimal BusyBox Linux system?
Mount /proc and /sys, configure the kernel to run /sbin/mdev when new hardware appears, and run mdev -s to scan existing devices. Without this, /dev can remain empty and disks or consoles may not work.
How can I recover an Ubuntu system that drops into the BusyBox initramfs prompt?
Run a file system check on the root partition with fsck. This can fix boot failures without reinstalling the system.
Where should I submit a detailed BusyBox configuration problem?
Post the problem description to the BusyBox mailing list.
Why is BusyBox used on resource-constrained systems?
BusyBox is a compact single executable that provides many common utilities with a small footprint. This makes it suitable for systems with limited resources.
Answers sourced from github.com, medium.com, www.busybox.net, www.reddit.com
Community
- What is the difference between Busybox/Linux and GNU/Linux? - Reddit (reddit)
- ELI5:What is bussybox ? : r/explainlikeimfive - Reddit (reddit)
Collected 48 days ago - public community threads