Google Git
Sign in
chromium / chromiumos / platform / initramfs / c748ebdb82cf1495e31a8dea6191340dd3530a83
commitc748ebdb82cf1495e31a8dea6191340dd3530a83[log] [tgz]
authorAmin Hassani <ahassani@chromium.org>Thu Nov 01 20:01:07 2018
committerchrome-bot <chrome-bot@chromium.org>Tue Dec 04 04:32:15 2018
tree9bd20ce588b4a6a3156ea306dc5076105d27a26b
parent9cf462923fbfa414101d05ca62e45bd1f58cf4c1 [diff]
initramfs: recovery: init: Enable oobe config

Enable oobe_config in the for recovery installer.

Also move selecting the locale before displaying any messages (like the ones for
oobe config).

BUG=chromium:901068
TEST=build a recovery image and use cros_oobe_autoconfig to populate it with
config file. Then did a recovery with that image and it worked fine. Also
worked for other laguages like french.

Change-Id: I02773b325dbf4a386f817012cdff5583da98bf4e
Reviewed-on: https://chromium-review.googlesource.com/1316470
Commit-Ready: Amin Hassani <ahassani@chromium.org>
Tested-by: Amin Hassani <ahassani@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
2 files changed
tree: 9bd20ce588b4a6a3156ea306dc5076105d27a26b
  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.