When we reboot the ubuntu talos boxes we lose the following settings: - vnc - correct settings for random/urandom - correct cpufreq settings - possibly apache needs to be restarted - buildbot slave does not auto restart

These machines also need to auto-login after reboot.

- added the following to rc.local: #set up vnc x11vnc -display :0 -shared -forever -rfbauth /home/mozqa/.vnc/passwd -auth /var/lib/gdm/:0.Xauth -bg #replace random with urandom rm /dev/random mknod /dev/random c 1 9 #set up throttling cpufreq-set -g userspace cpufreq-set -c 1 -g userspace cpufreq-set -f 1000 cpufreq-set -c 1 -f 1000 - /usr/share/hal/fdi/policy/10osvendor remove 10-cpufreq.fdi (disables hald-addon-cpufreq to allow rc.local settings to take effect) - sudo gksu /usr/sbin/gdmsetup (to have mozqa autologin) - Preferences -> Sessions -> gnome-terminal -x buildbot start talos-slave (for auto starting talos slave, also ensure that gnome-terminal is configured to stay open after command completion)

I can add these settings to the talos linux image, but we'll need a plan to roll out the changes to currently up machines. If all the changes are applied you can cleanly reboot a linux talos slave - there will no longer be requirements to set additional configuration options after reboot.

Installation instructions: - System -> Administration -> Login Window -> Security -> Enable Automatic Login - Terminal -> Edit -> Profiles -> Select 'Default', click Edit -> Title and Command -> 'When command exits' -> 'Hold the terminal open' - System -> Preferences -> Sessions -> Startup Programs -> Add -> name: 'start talos slave', command: 'gnome-terminal -x buildbot start talos-slave' - grab rebootUbuntu.zip - unzip in home directory - sudo ./reboot.sh - test reboot * is the cpu frequency correct? * has random been replaced with urandom? * did buildbot auto start? - remove rebootUbuntu.zip and reboot.sh