Rather than pull the initial set from /lib/udev/devices, we
move them to /lib/chromiumos/devices.
We also whitelist the udev maintainer script since we don't need
to have it create devices in /lib/udev/devices and we also do not
need it to create the persistent rules files.
Review URL: http://codereview.chromium.org/552056
A few weeks ago, dbus-uuidgen command was removed from the platform/init/dbus.conf script, but after the "upgrade-everything-to-Karmic" change, I think generating the uuid has become mandatorty again.
Without the uuid file (/var/lib/dbus/machine-id), ibus-daemon which uses D-Bus as its IPC channel does not work at all. I'm not sure but possibly the same is true for dbus-daemon?
chronos@localhost:/home/chronos$ ibus-daemon
process 2254: D-Bus library appears to be incorrectly set up; failed to read machine uuid: Failed to open "/var/lib/dbus/machine-id": No such file or directory
See the manual page for dbus-uuidgen to correct this issue.
BUG=1127
TEST=On xterm, run /usr/bin/ibus-setup and verify the command does not show an error like "ibus-daemon is not working."
Review URL: http://codereview.chromium.org/508018
running maintainer scripts.
This is a work-in-progress. If you build_image like:
EXPERIMENTAL_NO_DEBOOTSTRAP=1 ./build_image.sh
it will skip debootstrap and install the base required packages
without running maintainer scripts. This is about 68 packages that
have lots of interleaved dependencies so it is nasty to trim down.
If you build like:
EXPERIMENTAL_NO_MAINTAINER_SCRIPTS=1 ./build_image.sh
it will install all packages skipping maintainer scripts.
Using these we can try and get things in a state where we can
create an image built of cross-compiled packages.
This is obviously not finished but in this case I prefer to commit
early so others can poke at it.
Review URL: http://codereview.chromium.org/527015
Given this we need to explicitly install xterm and lsof, but
otherwise it is a net reduction of about 45 packages, which is nice.
Review URL: http://codereview.chromium.org/515009
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
their own init script in /etc/init.
This changes the chromeos-init package to install our
init scripts in /etc/init.chromeos. In the customize_rootfs
stage we remove /etc/init and replace with our init scripts.
Review URL: http://chromereview.prom.corp.google.com/1187069
git-svn-id: svn://chrome-svn/chromeos/trunk@264 06c00378-0e64-4dae-be16-12b19f9950a1
should depend on the installer package.
Move postinst out of customize_rootfs and into the installer
package (at least for now).
Review URL: http://chromereview.prom.corp.google.com/1187059
git-svn-id: svn://chrome-svn/chromeos/trunk@252 06c00378-0e64-4dae-be16-12b19f9950a1
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
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
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
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
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
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
