Google Git
Sign in
chromium / chromiumos / platform / initramfs / refs/heads/stabilize-12121.B
commitf8e0478e9409837815e2a53099c6817feef773dd[log] [tgz]
authorchuntsen <chuntsen@google.com>Thu Jan 10 09:22:39 2019
committerchrome-bot <chrome-bot@chromium.org>Thu Apr 11 01:07:06 2019
treedc715afb377abbc9f3bfa8a33ea602262630e79f
parente043793ce4968d66e0abfc27e4be9c976ba2ccb6 [diff]
factory_shim: Change the size of ram disk

The 400M ram disk is not enough when installing. This CL should be a
temporary solution.

BUG=b:122348657, b:129663373
TEST=Manually test on my local device

Change-Id: I457ffb35de767267fc7398bd0b94239730913a88
Reviewed-on: https://chromium-review.googlesource.com/1404612
Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com>
Tested-by: Chun-Tsen Kuo <chuntsen@chromium.org>
Reviewed-by: Hung-Te Lin <hungte@chromium.org>
1 file changed
tree: dc715afb377abbc9f3bfa8a33ea602262630e79f
  1. common/
  2. factory_netboot/
  3. factory_shim/
  4. recovery/
  5. test/
  6. .gitignore
  7. LICENSE
  8. Makefile
  9. OWNERS
  10. README.md
README.md

Chromium OS initramfs

Build logic for creating standalone initramfs environments.

See the README files in the respective subdirs for more details.

To Use

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).

To Make

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.

To Debug

It is possible to debug few of the initramfs targets in QEMU. Read test/README.md for more information.

Also, here is a shortcut for developing/debugging graphical bits in initramfs, without having to create a full image for every iteration.

After emerge-$BOARD, find your initramfs package from chroot /build/$BOARD/var/lib/initramfs and copy to a running DUT, for example /tmp/recovery_ramfs.cpio.xz, then do followings on DUT:

  1. mount -o remount,exec /mnt/stateful_partition
  2. mkdir /mnt/stateful_partition/test; cd /mnt/stateful_partition/test
  3. xzcat /tmp/XXXXXX_ramfs.cpio.xz | cpio -iv
  4. stop ui; kill $(pidof frecon)
  5. bind mount /dev, /proc, /sys and /tmp in /mnt/stateful_partition/test
  6. chroot /mnt/stateful_partition/test/init
  7. Iterate.