Upgrade XO to Build 703

I upgraded my XO to Build 703 this week. It was a little difficult at first, but I like it now. It's so cool that it now suspends when you close the lid. This is the first Linux laptop that I've had that does that so smoothly.

Disk space is at a premium on this little machine. I actually couldn't get Sugar to start after the upgrade until I did a ctrl-alt-f1 over to a virtual console and removed some files from my home directory. One utility that is nice for adding and, maybe more importantly, removing Activities is xo-get.py. Once installed you can just ./xo-get.py remove ActivityName to free up more disk space. Nice.

Removing activities wasn't nearly enough though. I was still really full on disk space and after poking around with du I found the /versions directory that seems to contain the complete set of files for the previous version of the OLPC software (after an update you can boot the previous version by holding down tho 'o' gamepad key). That takes up a lot of disk space. I searched and searched to see if there was a recommended safe way to get rid of stuff in /versions, and all I found was a mailing list post saying that you *should* be able to delete stuff in the versions directory. I didn't feel safe deleting stuff that seemed to be the currently running OS (I checked /versions/run/BIGLONGHASHEDVALUE/etc/issue to be sure), but I deleted the old version and everything seems to be running OK still. A little faster even.

We are going on a long road trip and the XO is the only laptop I'm going to bring. Wish me luck.

Comments

Post a Comment

Popular posts from this blog

SystemVerilog Fork Disable "Gotchas"

This is a long post with a lot of SystemVerilog code. The purpose of this entry is to hopefully save you from beating your head against the wall trying to figure out some of the subtleties of SystemVerilog processes (basically, threads). Subtleties like these are commonly referred to in the industry as "Gotchas" which makes them sound so playful and fun, but they really aren't either. I encourage you to run these examples with your simulator (if you have access to one) so that a) you can see the results first hand and better internalize what's going on, and b) you can tell me in the comments if this code works fine for you and I'll know I should go complain to my simulator vendor. OK, I'll start with a warm-up that everyone who writes any Verilog or SystemVerilog at all should be aware of, tasks are static by default. If you do this: module top; task do_stuff ( int wait_time); #wait_time $display ( "waited %0d, then did stuff" , wa
Read more

'git revert' Is Not Equivalent To 'svn revert'

I just learned that if you have some changes in your working tree that you want to get rid of, you don't type 'git revert' like you might guess. No, that's what cvs, subversion, mercurial, and bazaar (to name a few) use revert to mean, but not git. With git, revert is used to undo actual commits. Thankfully, you can undo your revert with another 'git revert', I just learned. So let me repeat to be clear, if you have changes to your working files that you want to abandon, DO NOT do this: git revert HEAD That will undo your last commit. Do this instead: git reset --hard HEAD I'm glad I have that straightened out now. I'm wondering if /etc was really a good place for me to start out playing with git. UPDATE: Nearly two years later and I'm still getting comments on this. I'm glad I've been able to help people out this way. The discussion in the comments is good, and one thing I'd like to point out is that I now always use
Read more

Git Rebase Explained

Image
Introduction Rebase is a helpful git command that can be used to turn a branchy two-headed version history into an easy to follow linear one. A linear history is much easier for a human eye to follow and a human brain to understand. Rebase is a very safe command to use, despite some fear that people have about it. This post should explain how rebase works and clear up any misunderstandings about it. Rebase Basics The short summary of rebase is that it cuts commits out of the git history and reconnects them somewhere else. Let's say the common scenario comes up: you commit a change to the main branch of a repository, you then run  git fetch , and in come a couple changes that other people made on the main branch. If your commit is version 46f and the others that just came in on the fetch are versions ef9 and 4a2, your version history might look like this: The main branch now has two heads, 46f and 4a2. You can run  git rebase  to disconnect your commit from version d88 and connect i
Read more