summaryrefslogtreecommitdiffstats
path: root/meta/recipes-core/busybox/busybox
diff options
context:
space:
mode:
authorStefan Agner <stefan@agner.ch>2016-08-07 22:47:28 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2016-09-23 15:27:03 +0100
commitd9d046c28ab1c221313162c3f8115e608c480771 (patch)
treef54333f6553becde47e7acead3a1c9b59a34b626 /meta/recipes-core/busybox/busybox
parentb6bb27c4c9485949f476dd3881a5145c0aff7739 (diff)
downloadpoky-d9d046c28ab1c221313162c3f8115e608c480771.tar.gz
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) (From OE-Core rev: 3c5097574e24a3923b093d8ef92506411dc8df08) 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> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-core/busybox/busybox')
0 files changed, 0 insertions, 0 deletions