TEST=From an already built image dir, ran archive_build with --notest_mod
set and verified the image had chromiumos_base_image.bin and chromiumos_image.bin.
Review URL: http://codereview.chromium.org/2111015
- add --recovery flag to chromeos-installer script to install a recovery
image from partition B onto a device's hard drive
- add temporary workaround to populate partition B to make installer work
- TODO(tgao): write a script to populate partition B and remove workaround
Review URL: http://codereview.chromium.org/2127010
TEST=Tested with building a new image, looking in the output directory, running
the image and running vi.
Review URL: http://codereview.chromium.org/2075019
I verified that if I whack /usr/lib/debug folder and run build_image, it works fine. This is important since I plan to check in this issue first and then the fix to add debug flags.
Review URL: http://codereview.chromium.org/2113007
- add back in RECOVERY variable since we can't specify value "0" in place
of boolean flag "--recovery"
- for recovery image, make ROOT-B 1GB, KERN-B 16MB and stateful partition 1GB
Review URL: http://codereview.chromium.org/2133006
- Don't run test image when building factory_image.
- Bump the size for factory_install image to 300MB, as the existing build_image
overfills the current size. The size does not really matter, as our SD card
copying time depends on the size of the contents, not the disk size.
Review URL: http://codereview.chromium.org/2113013
TEST=Tested build process. Tested dev image, test image and base image by booting all three and logging in.
Review URL: http://codereview.chromium.org/2106009
Temporary approach to using INSTALL_MASK to suppress some non-relevant paths.
It reduces the size from ~426MB to ~163MB. Eventually, will remove it and
create a clean and separated ebuild for chromeos-factoryinstall.
Review URL: http://codereview.chromium.org/2084001
TEST=Ran "gmergefs --remote my_device gmerge" resulted in having
gmerge installed into my /usr/local dir on my device
Review URL: http://codereview.chromium.org/2037006
In addition unifies changes in mount_gpt_image and one-offs in mod_image_for_test
to consolidate gpt / var mounting.
Review URL: http://codereview.chromium.org/2064001
Unfortunately, bind mounting /media inside the chroot did not allow us
to programmatically unmount automounted USB sticks from within the chroot.
Instead, I disable automounting on our corporate desktops when you enter the
chroot. Your normal setting is restored when you exit the chroot again.
TEST=run gconftool-2 -g /apps/nautilus/preferences/media_automount to print the current value of your automount pref; run this before entering the chroot, outside the chroot while you've got some other terminal that's inside the chroot, and then after exiting the chroot.
Review URL: http://codereview.chromium.org/2029009
Since we're using upstart, don't let packages drop startup scripts into
/etc/init.d.
BUG=none
TEST=Build image, inspect contents of /etc/init.d (or lack thereof, after this patch)
Review URL: http://codereview.chromium.org/2023006
Talked to kmixter, and we felt that bindmounting the directory in
which the host os creates mount points for automounted external
devices is the cleanest solution to the inside/outside the chroot problem.
By doing this, image_to_usb can be run from inside the chroot without concern.
That means that (as far as I understand) the factory install flow can all be
done inside the chroot, as well as modding images for test and everything else.
Review URL: http://codereview.chromium.org/1991006
BUG=1970
TEST=Running archive build with clean build and producing
a test image and normal image and zip file. Also running
with custom from and getting an error code with test_mod=true
This change is required because mod_image_for_test requires it
to be inside chroot. Since the buildbot is the main user
of this script, this deals with that use case. Other users
of this script will have to run mod_image_for_test manually
outside of archive_build
Review URL: http://codereview.chromium.org/2008001
The issue here is if an previous update succeeded but reboot not happen, for what ever unknown reason, this host lost the ability to update again.
I think some of the current update failure in the lab should be caused by this.
Review URL: http://codereview.chromium.org/2031002
Make standalone package for factory install, so it can be overlayed on top of an existing image.
Modify mod_image_for_test to do the overlay.
Review URL: http://codereview.chromium.org/1945004
A separate CL adds a test stanza to the metrics ebuild. More tests
(specifically, for the D-Bus MessageFilter) will also come in a
separate CL.
Review URL: http://codereview.chromium.org/1919005
Add restart_in_chroot_if_needed to common.sh, and modify the build scripts which referred to assert_inside_chroot to use it instead. The effect is that you don't ever have to explicitly enter_chroot.sh to build (still can, it work's fine).
Update mod_image_for_test.sh to use restart_in_chroot_if_needed
Review URL: http://codereview.chromium.org/1736025
TEST=Tested with image_to_live, memento_updater without image_to_live
This mimics the update process of the real image for the stateful partition.
By moving this the update into a separate script, I can add it to the gmerge
package such that developers will not have to use image_to_live. This change
also removes the dependency on tar.
Review URL: http://codereview.chromium.org/1774021
on the device under test and to use a not-normally-generated interface name, so that use of add-on ethernet devices is not affected in normal operation.
BUG=2962, 2941
(dup of 1810013, git goofiness)
Review URL: http://codereview.chromium.org/1826003
TEST=Tested by running image_to_live with correct formated images as well
as images that are missing either /var or dev_image directories.
Review URL: http://codereview.chromium.org/1705023
This allows appending extra kernel command line parameters to
the ARM kernel command line on the Voguev210 boards.
BUG=None
TEST=Built image
Review URL: http://codereview.chromium.org/1694021
* Leave ui.conf there, not run by default.
* dump autotest log into /dev/tty1
* Don't let tty1 eat keayboard events.
Review URL: http://codereview.chromium.org/1742018
