| commit | a878c6922db5fc5c2565b4058f1f4713ee5115aa | [log] [tgz] |
|---|---|---|
| author | Hung-Te Lin <hungte@chromium.org> | Thu May 11 02:46:47 2017 |
| committer | chrome-bot <chrome-bot@chromium.org> | Fri May 12 05:27:46 2017 |
| tree | fe6f6a82668bfb4cd157db8e92cfb7f7070fbaa8 | |
| parent | b85c6992c6e3b182fa9d632587332999e9ec25a5 [diff] |
factory_netboot: Add pigz and lbzip2. The factory netboot installer needs to download and extract files in gz or bzip2 format. Adding pigz and lbzip2 so we can utilize CPU cores for better imaging speed. BUG=chromium:711615 TEST=src/scripts/make_netboot.sh --board eve Change-Id: Icafbfe10a009f4dd84edcd675e9b2482c7cc5dc9 Reviewed-on: https://chromium-review.googlesource.com/502767 Commit-Ready: Hung-Te Lin <hungte@chromium.org> Tested-by: Hung-Te Lin <hungte@chromium.org> Reviewed-by: Hung-Te Lin <hungte@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.