This puts all package installation for the rootfs in one place. It
also makes it so that you can run install_packages.sh --root="foo"
outside of the build_image.sh script if you want to test something
without going through the full image build. With this change
build_image basically:
- Sets up a loopback mounted rootfs
- Calls install_packages.sh on rootfs
- Calls customize_rootfs on rootfs
- Makes the rootfs bootable
Review URL: http://codereview.chromium.org/520004
and install debs into the target rootfs.
This will still run the maintainer scripts, but it is a step in
the right direction to being able to create a cross-compiled image.
This will allow us to experiment with disabling the maintainer
scripts and attempt to get that working. It also makes it easier
to modify the install_packages script since it now has access to
shflags and the source tree properly.
This CL also cleans up stuff doing in build_image.sh to bind mount
the trunk into the target rootfs, set up packages for install there,
etc.
The next step is to experiment with disabling maintainer scripts.
One possible way to do that would be to put a shim in place of dpkg
so that when apt calls dpkg it install a package we call dpkg-deb
with a simple unpack instead. This would allow us to continue to
use the good nice features that apt provides.
Review URL: http://codereview.chromium.org/517003
only host-based tools. This is a requirement in order to be able to build
a cross-compiled image where the target rootfs is a different arch than
the host.
Review URL: http://codereview.chromium.org/500014
This fixes monospace fonts in Chrome. This change also
moves some static files out of customize_rootfs.sh.
BUG=237
Review URL: http://codereview.chromium.org/424011
git-svn-id: svn://chrome-svn/chromeos/trunk@303 06c00378-0e64-4dae-be16-12b19f9950a1
The build_image script now calls install_packages.sh followed
by customize_rootfs.sh.
The current system installs packages and performs customization
fixups from within the rootfs it is building. In order to
cross-build properly we'll need to do these steps from outside
of the root. Splitting package installation and rootfs customization
will make it easier to do this. A follow-on change will modify
customize_rootfs to run from outside of the rootfs.
Review URL: http://codereview.chromium.org/414051
git-svn-id: svn://chrome-svn/chromeos/trunk@300 06c00378-0e64-4dae-be16-12b19f9950a1
Already moved config into the kernel git repo. This change fixes the
build to use the config which is in the kernel and removes the configs
in the chromeos repo.
Also removed a lot of the kernel version hard-coding that is in the build.
Review URL: http://chromereview.prom.corp.google.com/1188031
git-svn-id: svn://chrome-svn/chromeos/trunk@214 06c00378-0e64-4dae-be16-12b19f9950a1
I think read-only is the default, but this makes it explicit.
Review URL: http://chromereview.prom.corp.google.com/1181041
git-svn-id: svn://chrome-svn/chromeos/trunk@159 06c00378-0e64-4dae-be16-12b19f9950a1
from git); to enable set KERNEL_VERSION in your environment to the
directory name (e.g. 2.6.31-chromeos-intel-menlow) otherwise default to
the existing kernel build mechanism
Review URL: http://chromereview.prom.corp.google.com/1180034
git-svn-id: svn://chrome-svn/chromeos/trunk@142 06c00378-0e64-4dae-be16-12b19f9950a1
image_to_usb.sh didn't handle the case where the devices were being
automounted.
build_image.sh didn't handle the case where the version string > ~14
characters.
Review URL: http://chromereview.prom.corp.google.com/1173161
git-svn-id: svn://chrome-svn/chromeos/trunk@108 06c00378-0e64-4dae-be16-12b19f9950a1
I've been getting frustrated by juggling usb sticks to constantly update my netbook so I wrote a simple
server that can run in a developer's source tree and serve updates to a netbook. I also added an upstart
task that will download a script from the dev server and run it. I use this to install sshfs, gdb, and vim.
Here's a quick heads up about what has changed.
1. /etc/lsb-release
I added two new fields to the release file. One is the URL that should be pinged for updates. The other is the URL that can be used to download a developer setup script.
2. chromeos_version.sh
The functionality for the release build is unchanged, however, developer builds now have a monotonically increasing version number.
3. software-update.conf
Autoupdate is disabled when the DEV_SERVER field in /etc/lsb-release is initialized. This field won't be set on the build server, but will be set everywhere else.
4. ping_omaha.sh
The omaha server is now configured by /etc/lsb-release
Review URL: http://chromereview.prom.corp.google.com/1175098
git-svn-id: svn://chrome-svn/chromeos/trunk@92 06c00378-0e64-4dae-be16-12b19f9950a1
USB image:
- have a stateful partition
- use a read-only system partition
Installer:
- copy read-only system partition from USB to hard drive, skip fsck check
- make stateful partition empty
System:
- Change to tolerate empty stateful partition on bootup
- Don't keep so much of /var on stateful partition (var/lib should be in system
image)
Autoupdate:
- Fix a couple checks to allow partitions 3 and 4 to be system partitions
- Fix a misnomer in mk_memento_images.sh
Review URL: http://chromereview.prom.corp.google.com/1175102
git-svn-id: svn://chrome-svn/chromeos/trunk@87 06c00378-0e64-4dae-be16-12b19f9950a1
