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
Long term (when we are compiling the xkb) package, we should put this
change in that package. For now, we create a symlink from /var/lib/xkb
to /var/tmp in customize_rootfs.sh
tedbo@ found the solution. I just did the CL
Review URL: http://chromereview.prom.corp.google.com/1181006
git-svn-id: svn://chrome-svn/chromeos/trunk@124 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
We are using the same sources as what is in the tarball. Just that they
are now in git. Copying the kernel tree over to the build dir for now.
Will eventually modify it so that we build from the src directory into
the build directory.
Review URL: http://chromereview.prom.corp.google.com/1177012
git-svn-id: svn://chrome-svn/chromeos/trunk@81 06c00378-0e64-4dae-be16-12b19f9950a1
Mark the wlan0 interface down on suspend and back up on resume to
prod connman into action. The result isn't exactly what we want
as connman won't return to the previous ap if another, previously
visited ap, is found with higher signal strength. Also this is
very heavyweight, the better behaviour is to simulate a beacon miss
on resume and try to reassociate to the same ap; then roam if that
fails--but getting that behaviour will take more work so add this
for now.
Review URL: http://chromereview.prom.corp.google.com/1175077
git-svn-id: svn://chrome-svn/chromeos/trunk@57 06c00378-0e64-4dae-be16-12b19f9950a1
