| commit | a8ce70b9f726125b7c54618e612cd889c3395825 | [log] [tgz] |
|---|---|---|
| author | Shelley Chen <shchen@chromium.org> | Thu Mar 30 22:41:19 2017 |
| committer | chrome-bot <chrome-bot@chromium.org> | Mon Apr 03 22:41:50 2017 |
| tree | 66f6ed632ab503af8fe81774fb2ba3c55f61a0af | |
| parent | a0f0b6ba3da4e4bcf9ffd277e903b19c75501fca [diff] |
recovery: fix vt3 debug output
The redirect to vt3 was being done prior to the vts
being set up by frecon. Moving frecon call earlier
in the init process so that the /run/frecon/vt# links
are created earlier in the recovery flow.
BUG=chromium:703991
BRANCH=None
TEST=Build recovery image, go through recovery flow
and make sure that recovery.log output to vt2
in realtime.
Change-Id: I40ffc3f326a4394e471106b97ce44c0f510d873f
Signed-off-by: Shelley Chen <shchen@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/464067
Reviewed-by: Randall Spangler <rspangler@chromium.org>
Build logic for creating standalone initramfs environments.
See the README files in the respective subdirs for more details.
Normally you wouldn't build in this directory directly. Instead, you would build the chromeos-initramfs package with the right USE flags. e.g.:
$ USE=recovery_ramfs emerge-$BOARD chromeos-initramfs
That will install the cpio initramfs files into the sysroot for you to build into a kernel directly. The various build scripts would then be used to make the right kernel/image using those (e.g. mod_image_for_recovery.sh).
You could build these by hand for quick testing. Inside the chroot:
$ make SYSROOT=/build/$BOARD BOARD=$BOARD <target>
That will create the cpio archives for you.