]> code.ossystems Code Review - openembedded-core.git/commit
busybox: Fix busybox-init on non-tty consoles
authorStefan Agner <stefan@agner.ch>
Mon, 8 Aug 2016 05:47:28 +0000 (22:47 -0700)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Wed, 10 Aug 2016 09:45:33 +0000 (10:45 +0100)
commita53393082f331a613cb3eb973a07bab22cefcde8
tree7f4a9b908b4a7e3c448375666e3c5425a7f386f5
parent6dca3dee34b587157d0d49c590a177ff1dabb374
busybox: Fix busybox-init on non-tty consoles

When using non-tty consoles (e.g. VirtIO console /dev/hvc0) the
current init system fails with:
process '/sbin/getty 115200 hvc0' (pid 545) exited. Scheduling for restart.
can't open /dev/ttyhvc0: No such file or directory

The first field needs to be a valid device. The BusyBox inittab example
explains as follows:
"<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 "/dev/" and used as-is."

Signed-off-by: Stefan Agner <stefan@agner.ch>
Signed-off-by: Ross Burton <ross.burton@intel.com>
meta/recipes-core/busybox/busybox.inc