diff options
| author | Tom Cherry <tomcherry@google.com> | 2018-11-06 10:32:53 -0800 |
|---|---|---|
| committer | Tom Cherry <tomcherry@google.com> | 2018-11-08 15:47:36 -0800 |
| commit | 56999b41af9c553787a2436ce4067aca04aa2dc6 (patch) | |
| tree | 812e53da488b3c765f203de7ecf671d239a439d7 /libunwindstack/tests/MemoryCacheTest.cpp | |
| parent | 166ae693d4d0cce2a8b094ac31aeac43c8f64093 (diff) | |
init: chroot from recovery to /first_stage_ramdisk
When using the recovery image as a trampoline to boot the system,
first chroot from the recovery image to /first_stage_ramdisk, to
minimize differences between these two boot paths.
Primary motivation is due to the fact that the basename of each mount
point is used by device-manager to name its nodes, and the previous
code that created used /system_recovery_mount as the mount point for
system.img broke AVB. Instead of hacking around that issue, this
change unified mounting for the recovery trampoline and true first
stage ramdisk paths.
Bug: 114062208
Test: AVB works with blueline_mainline
Change-Id: Iffb154962b6e160150917e068f1e7d0bf7cb84e7
Diffstat (limited to 'libunwindstack/tests/MemoryCacheTest.cpp')
0 files changed, 0 insertions, 0 deletions