]> 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>
Fri, 23 Sep 2016 14:25:49 +0000 (15:25 +0100)
commit3c5097574e24a3923b093d8ef92506411dc8df08
treec70835cbc69cc496e3ff7c7cfbf366cd2d17feef
parenta2d9d36818bbc7773ed4295c286fc53fe7c31345
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."

(From OE-Core rev: a53393082f331a613cb3eb973a07bab22cefcde8)

Signed-off-by: Stefan Agner <stefan@agner.ch>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Armin Kuster <akuster808@gmail.com>
meta/recipes-core/busybox/busybox.inc