But, we still explictly require bootchart-java, to create the pretty picture.
Without explicitly adding bootchart-java, it removes these packages:
bootchart-java
ca-certificates-java
default-jre-headless
gcj-4.4-base
gcj-4.4-jre
gcj-4.4-jre-headless
gcj-4.4-jre-lib
gcj-jre
gcj-jre-headless
icedtea-6-jre-cacao
java-common
libcommons-cli-java
libcommons-compress-java
libcommons-lang-java
libgcj-common
libgcj10
libgcj10-awt
libjline-java
liblcms1
openjdk-6-jre-headless
openjdk-6-jre-lib
python-central
rhino
tzdata-java
By explicitly adding bootchart-java it removes only these packages:
gcj-4.4-jre-lib
icedtea-6-jre-cacao
Either way, bootchart still collects the data so it is possible to generate
the pictures remotely.
Review URL: http://chromereview.prom.corp.google.com/1188035
git-svn-id: svn://chrome-svn/chromeos/trunk@225 06c00378-0e64-4dae-be16-12b19f9950a1
This removes the acpi stuff from customize_rootfs and should make it easier
to do more acpi stuff in the future as needed. We still need to figure out
how to handle acpi across different devices.
Review URL: http://chromereview.prom.corp.google.com/1186038
git-svn-id: svn://chrome-svn/chromeos/trunk@220 06c00378-0e64-4dae-be16-12b19f9950a1
Fixes the following error:
rm: cannot remove `/home/chrome-bot/trunk/src/build/x86/local_packages/linux-image-*.deb': No such file or directory
Review URL: http://chromereview.prom.corp.google.com/1186034
git-svn-id: svn://chrome-svn/chromeos/trunk@215 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
stuff that parses a bunch of files in favor of just starting
our session script under a console-kit session. We don't need
any of the typical Xsession start stuff and this is simpler to
understand. Since we don't use Xsession.d, we no longer need
to delete certain files from that directory.
The CL also has the login_manager package install our own slim.conf
so that we don't need to be modifying the default one using sed
from customize_rootfs and the login_manager maintainer scripts.
Review URL: http://chromereview.prom.corp.google.com/1188025
git-svn-id: svn://chrome-svn/chromeos/trunk@209 06c00378-0e64-4dae-be16-12b19f9950a1
A few changes here.
1. A simple webui for building packages in the source tree.
2. A shell script that you can run on your netbook to kick of a build of a given package, download the result, and install it.
3. Refactored update/build functionality into classes so that the build env paths can be shared.
4. devkit.sh downloads an upsatart task that starts ssh at boot time.
More info in the dev server manual -
https://docs.google.com/a/google.com/Doc?docid=0AT6qlIKi36JQY2M1Y3B2bWNfMTZkems5eGducg&hl=en
Review URL: http://chromereview.prom.corp.google.com/1187017
git-svn-id: svn://chrome-svn/chromeos/trunk@207 06c00378-0e64-4dae-be16-12b19f9950a1
We should no longer try to connect to googleguest or another open network at boot time. First time users will need to connect via ethernet to log into the machine. Once a user has logged in for the first time they will be able to login without network connectivty. Also, Connman will automatically connect to any available networks that the user has connected to in the past.
The long term solution for first time usage is to put the network picker in the login UI.
Review URL: http://chromereview.prom.corp.google.com/1187008
git-svn-id: svn://chrome-svn/chromeos/trunk@191 06c00378-0e64-4dae-be16-12b19f9950a1
We had a bug where we were unable to boot a device where the usb
drive appeared as sdc. This is because it was using our fixed set
of devices needed to start X rather than re-using the devices
that are created in the initrd. This fixes that to re-use the
devices created by udev if we have an initramfs.
This CL also fixes a reboot bug.
Review URL: http://chromereview.prom.corp.google.com/1183002
git-svn-id: svn://chrome-svn/chromeos/trunk@174 06c00378-0e64-4dae-be16-12b19f9950a1
This CL changes the shutdown sequence to be more upstartified.
We switch from using the stock shutdown scripts to a custom
sequence that basically terminates chrome cleanly and then kills
all processes that hold open files on our stateful partition and
crypto-home so that we can unmount them cleanly and shutdown.
The change adds a ui.conf upstart job that lets upstart track
the login manager. Starting the ui will start the login manager
and enable a graphical session; stopping the ui will cleanly
kill chrome and then tear down the graphical session.
Review URL: http://chromereview.prom.corp.google.com/1180066
git-svn-id: svn://chrome-svn/chromeos/trunk@169 06c00378-0e64-4dae-be16-12b19f9950a1
This changes many of our upstart jobs to use upstart
properly rather than just running the corresponding
scripts in /etc/init.d. The init.d scripts all pull in
helper functions, etc that are mostly unused. These
changes typically go from using many subshells to start
a daemon to a single exec of the daemon with proper
tracking by upstart. Most of these jobs are not in
the critical boot path, but we should still keep them
as optimized as possible.
Review URL: http://chromereview.prom.corp.google.com/1181042
git-svn-id: svn://chrome-svn/chromeos/trunk@164 06c00378-0e64-4dae-be16-12b19f9950a1
namespaces, minor build speed up using -j option for more scons.
Review URL: http://chromereview.prom.corp.google.com/1180018
git-svn-id: svn://chrome-svn/chromeos/trunk@160 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
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
