BusyBox combines tiny versions of many common UNIX utilities into a single small executable. It provides minimalist replacements for most of the utilities you usually find in GNU fileutils, shellutils, etc. The utilities in BusyBox generally have fewer options than their full-featured GNU cousins; however, the options that are included provide the expected functionality and behave very much like their GNU counterparts. BusyBox provides a fairly complete POSIX environment for any small or embedded system.
TinyLogin is a suite of tiny UNIX utilities for handling logins, user authentication, changing passwords, and otherwise maintaining users and groups on an embedded system. It also provides shadow password support to enhance system security. TinyLogin is, as the name implies, very small, and makes an excellent addition to an embedded system.
Re: Problem with busybox as init
> I've been making my own
> bootdisk/minilinux. I use busybox, and I
> dont have initd, so the kernel is
> started with "init=/bin/sh" where sh is
> a link to busybox (yes, i compiled sh
> into bb). But when the system boots,
> busybox prints out its list of functions
> and quits! This results to "kernel
> panic: tried to kill init"
> help would be appreciated :)
This is the result of a kernel bug where the kernel fails to properly set the value of argv for init to /bin/sh. I got a patch into 2.4.23, and 2.6.0-preX fixing this bug, so this will now work properly with the latest Linux kernels.