So, lately I’ve been doing checks on both ChrUbuntu AND crouton installations, and had to figure out how to have them both work together. So, here is the step-by-step, though I send you to some other locations to get the full installation instructions for those two.
1) Save anything you need to have backed up and set your Chromebook to the Developer mode. See here for how for your device: http://www.chromium.org/chromium-os/developer-information-for-chrome-os-devices — this is going to wipe your drive clean as a whistle, so back everything up that is in your Downloads folder that you may need to keep!!!
2) I recommend you switch to the Chrome Beta Channel for a saucy Unity installation and also currently for everything else. This is to obtain the more recent kernels for better video driver support, among other things. Go into Settings, click Help on the left sidebar, then click “More info” and then the “Change Channel” button. This performs a powerwash, which won’t matter on a unit freshly placed into developer mode. Note: Powerwashes clear out old Crouton chroots entirely.
3) Install ChrUbuntu first! Go to http://chromeos-cr48.blogspot.com/2013/05/chrubuntu-one-script-to-rule-them-all_31.html and follow all the instructions there, all the way to the end. (Lots of folks get it installed and forget to read the part at the end showing how to switch between the two systems from ChrUbuntu to Chromeos and back again.)
I used the following for a c710 which also works with any ARM units:
(See this page http://chromeos-cr48.blogspot.com/2013/10/chrubuntu-for-new-chromebooks-now-with.html for the script for the Chromebook Pixel and the newer Haswell-based Chromebooks like the Acer C720 and HP Chromebook 14. )
Go with the speedy XFCE environment in raring (stable in Chrome Beta channel):
or go with the beautiful Unity environment in saucy, assuming you used the Chrome Beta channel again:
I will tell you that if the physical security of your data is very important to you, that ChrUbuntu is the better way to go as your permanent installation. Even with a Powerwash or especially if someone hits your spacebar and exits developer mode, a ChrUbuntu installation with its data intact is still there on its partition waiting for you to return to Developer mode again. Crouton installs are totally and completely wiped. If you save everything to the cloud diligently, this will not matter to you perhaps. But I lost a 2 hour interview recording done in Audacity in a crouton installation due to someone hitting that spacebar!
4) Install Crouton Next! If you changed to the Chrome Dev channel earlier (but don’t till they fix the bugs – use the Beta channel!), change to the Chrome Beta Channel for Crouton installations. Don’t worry – the ChrUbuntu installation already took the cue from your channel setting earlier and installed its own copy of the kernel you selected. That doesn’t get changed by this move.
Follow the instructions here: https://github.com/dnschneid/crouton/blob/master/README.md
or see this article at my website: http://terrybritton.com/copy-and-paste-crouton-linux-on-chromebook-commands/
I highly recommend XFCE – Crouton FLIES with this. Otherwise, KDE or Unity both work with the Chrome Beta Channel kernel in raring and saucy.
sudo sh -e ~/Downloads/crouton -t chrome,xfce -r saucy -n saucy
That puts your chroot into a folder named saucy, so it doesn’t get the default name of precise, which would be confusing! Start with:
sudo startxfce4 -n saucy
5) So, now you have two installations, but the crouton installation turns off the developer mode needed to get back to your ChrUbuntu installation. So, use CTRL-ALT-F2 to get back into the Chronos shell, and type in WITHOUT logging in as chronos:
(that’s two dashes before mode)
Here are the switch codes to go between ChrUbuntu and ChromeOS again:
sudo cgpt add -i
sudo cgpt add -i
See the associated post,
to make life easier for yourself!