| commit | 0398aa2c9925df7b024dc974f68364c074e7fc5e | [log] [tgz] |
|---|---|---|
| author | Mattias Nissler <mnissler@chromium.org> | Tue Sep 12 10:49:57 2017 |
| committer | chrome-bot <chrome-bot@chromium.org> | Wed Sep 13 22:12:06 2017 |
| tree | cc7f9c467d9087c7ada37e011690e40cc2356098 | |
| parent | fb9ba210f4a9e9bfc38bdf9caa0beb15994a5b5b [diff] |
recovery: Don't clobber logs on recovery retry. Allow multiple instances of recovery logs to be stored on the recovery media. This helps avoid clobbering important information that will be helpful for post-mortem debugging after multiple recovery attempts. BUG=chromium:764261 TEST=Manual Change-Id: I2a126dd818bc38bc7edc5ce5ca7e7c3e65eb5037 Reviewed-on: https://chromium-review.googlesource.com/663638 Commit-Ready: Mattias Nissler <mnissler@chromium.org> Tested-by: Mattias Nissler <mnissler@chromium.org> Reviewed-by: Mike Frysinger <vapier@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.