| commit | 5b9b3a35dbd91dbd3b2ceb7e20656016e416fa62 | [log] [tgz] |
|---|---|---|
| author | Hung-Te Lin <hungte@chromium.org> | Fri Nov 25 08:09:03 2016 |
| committer | chrome-bot <chrome-bot@chromium.org> | Fri Nov 25 12:16:37 2016 |
| tree | 20fe911995166fa1419ffe2aa61d90eb387c5ac7 | |
| parent | 43b239fde88cfe8590996369295bbb449ee9845a [diff] |
factory_netboot: Add modprobe into bin dependency. The modprobe in busybox does not work in netboot environment so we have to add the real one from system tree. This fixes the "permission denied" error message during network_bringup. BUG=None TEST=USE=factory_netboot_ramfs emerge-link chromeos-initramfs Change-Id: If2f75967d505339fb50e7a5916b41a39da406be7 Reviewed-on: https://chromium-review.googlesource.com/414668 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.