weston-init: start weston on a new VT

Weston 1.3 needs to run on a VT, which is typically handled by weston-launch.
Currently weston-init doesn't use weston-launch as that depends on the
(non-default) pam DISTRO_FEATURE, so depend on kbd and use openvt directly.

This also fixes problems caused by the init script blocking until Weston exits,
which meant that later init scripts were not actually running.

(From OE-Core master rev: 3726eb29cfa79a4a1fbdbcaa96f770063c482858)

(From OE-Core rev: d79f7846f5d538f6f835f52686fd2c749cb1b70f)

Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Ross Burton 2013-11-07 11:55:35 +00:00 committed by Richard Purdie
parent 6894ee1baf
commit b4d22bb10f
2 changed files with 3 additions and 1 deletions

View File

@ -13,5 +13,7 @@ do_install() {
inherit allarch update-rc.d
RDEPENDS_${PN} = "weston kbd"
INITSCRIPT_NAME = "weston"
INITSCRIPT_PARAMS = "start 9 5 2 . stop 20 0 1 6 ."

View File

@ -34,7 +34,7 @@ case "$1" in
chmod 0700 $XDG_RUNTIME_DIR
fi
weston
openvt -s weston
;;
stop)