Gitiles
Code Review Sign In
gerrit.openfyde.cn / chromium.googlesource.com / chromiumos / platform / initramfs / 946b09a9e6554986da8c24d6ad9766ff03671126
commit946b09a9e6554986da8c24d6ad9766ff03671126[log] [tgz]
authorVyshu <vyshu@google.com>Mon May 10 12:25:03 2021 -0400
committerCommit Bot <commit-bot@chromium.org>Tue May 11 19:33:47 2021 +0000
tree3db7cf3cd13b4502735de21cfec0f78f0d2cb284
parent7e7421f23847992dd28cbeaa1e5312d00d50ff1b [diff]
initrmafs: Add user confirmation string to minios

Add text asking for user confirmation to localized text.

BUG=b:181248366
TEST=build and run minios, test user permission screen.

Change-Id: I91cd854ba17113dbba7d3c7cf73fe3574d211459
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/initramfs/+/2884618
Tested-by: Vyshu Khota <vyshu@google.com>
Reviewed-by: Ting Shen <phoenixshen@chromium.org>
Commit-Queue: Vyshu Khota <vyshu@google.com>
2 files changed
tree: 3db7cf3cd13b4502735de21cfec0f78f0d2cb284
  1. common/
  2. factory_netboot/
  3. factory_shim/
  4. hypervisor/
  5. minios/
  6. recovery/
  7. test/
  8. .gitignore
  9. LICENSE
  10. Makefile
  11. OWNERS
  12. 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 over SSH:

  1. mkdir /usr/local/test/; cd /usr/local/test
  2. xzcat /tmp/XXXXXX_ramfs.cpio.xz | toybox cpio -iv
  3. stop ui; kill $(pidof frecon)
  4. bind mount /dev, /proc, /sys and /tmp in /usr/local/test:
for d in dev proc sys tmp; do
   mount --bind /${d} /usr/local/test/${d}
done
  1. chroot /usr/local/test /init
  2. Iterate.