aterm will be going back into every build for now, so we can revert these dev-mode only changes
BUG=chromium-os:3884
TEST=none yet
Review URL: http://codereview.chromium.org/2669004
- add shell script to populate payload partition of a recovery image
(i.e. copying partition A of a pristine Chrome OS image to partition B
of a recovery image)
Review URL: http://codereview.chromium.org/2568003
This prevents the machine from suspending while it is being tested.
TEST=Modified an image for test and verified that powerd did not suspend.
BUG=chromium-os:3694
Review URL: http://codereview.chromium.org/2620008
The signing work is being tested and developed on x86, and ARM isn't ready
to use it. Signing the ARM kernel is disruptive. We'll enable it for ARM
later.
Review URL: http://codereview.chromium.org/2599001
- add recovery installer config file (which invokes chromeos-install with
--recovery flag)
- update build_image to install recovery_installer pkg and changed base image
name to recovery_image.bin
Review URL: http://codereview.chromium.org/2081018
BUG=3283
TEST=Tested by running mod_image_for_test and checking the stateful partiton
on the resulting image and verifying that these files exist in the correct
locations.
Review URL: http://codereview.chromium.org/2107013
BUG=3356
TEST=Run memento_updater.sh and update from chrome about page successfully from developer builds.
Review URL: http://codereview.chromium.org/2114007
Modify build_image to use the create_blob utility and the inline bootloader
to generate a bootable (but still unsigned) kernel partition.
Review URL: http://codereview.chromium.org/2112013
TEST=Tested this by running it locally on my workstation and calling both stateful_update and memento_updater on a ToT build of chromiumOS on an eee1008HA.
Review URL: http://codereview.chromium.org/2283003
I've updated the CL to remove the space in the "] ;". I'm not sure I understand your "size != 0" comment as if the device is just attached for charging, it won't go through the trouble of becoming a USB storage device. Will chat in person.
Review URL: http://codereview.chromium.org/2269003
Added chrome_root_mount option to specify the mount point to work around a permissions issue.
BUG=3464
TEST=none
Review URL: http://codereview.chromium.org/2126011
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
