Feeding the Penguins

Ubuntu Server: Versioning /etc with etckeeper rocks!

2009-05-13T19:43:12Z

Deploying a new server at work – a dedicated server hosted at Hetzner. Fortunately Jaunty (Ubuntu 9.04) was released before we had anything hosted on the machine, so I took the decision to upgrade it before we do serious deployment.

One of the shiny new features of Ubuntu Server 9.04 is etckeeper, documented here by Thierry Carrez. In particular, on 9.04 etckeeper plays well with bzr and shows the real user who typed “sudo etckeeper commit” in the bzr log, not just “root”.

As we have a (small but distributed) team adminning the server, this will help a great deal to keep track of who did what when.

Surviving an Ubuntu Release Day

2009-04-23T18:46:54Z

Some observations on the last n releases:

Throughout the Ubuntu development cycle, there are daily “snapshot” CD images produced. If you’re fortunate to live in a country where most of the “broadband” online population are not capped at 1GB per month (and a presidential hopeful who doesn’t keep singing “bring me my machine gun“) then you can download these during the development cycle to boot (daily-live) or install (perhaps in a virtual machine) to check on the progress or help with testing. These culminate in the actual “gold” release image.

Therefore, if you have one of these images from near the end of the development cycle, such as the release candidate, you can rsync to the latest image available on release day, and that will download the differences between the iso you have, and the final daily image – which will be identical to the release image, even though the daily image will be named something like jaunty-desktop-i386.iso and the corresponding release image named ubuntu-9.04-desktop-i386.iso. Rename it, and you’re done!

(Check the MD5SUMS after the release is announced, to be 100% sure you have it. There is always a small chance of a change to the ISOs on release day if some major “ate all my data” bug is found – so if you do have problems, remember that it comes with no warranty…)

Now, for kicks, go and lurk on IRC in #ubuntu-release-party and watch the masses rocking up to ask “Is it out yet?” Note Alan Pope’s list of Things Not To Say, and don’t go gloating that you have it already – you’ll only be kicked from the channel by the ironically named partybot.

Instead, burn write it to a USB stick (CDs are so early 2008) and get installing!

OLPC discontinues “Change the World”

2009-02-18T19:09:17Z

In a stunning moment of irony, OLPC has discontinued “Change the World”.

In an email that leaked out onto the grassroots mailing list, OLPC quietly announced the end of the “Change the World” program previously known as “Give Many”, where you could buy 100 or 1000 XOs for the school of your choice.

Here’s the relevant excerpt:

> Unfortunately, as some of you might have heard "Change the World" aka "Give
> a School" aka "Give 100, Give 1000" will cease to exist. We are just waiting
> for the info to be taken off the main website (any second now).
>
> We are doing this in an effort to refocus back to large-scale deployments
> that create change in a major way. We WILL honor all requests that we have
> received prior to the info being taken off the website. So if you know
> anyone who is interested, tell them time is of the essence!!

Indeed, the ways to give page no longer lists “give a school” as an option. That option used to read (courtesy of Google cache):

Give 100 or more laptops with this special program that allows donors to choose the country where the laptops go. This geo-targeted program can impact a village, a region, or even a country, with large group donations.

The page it linked to is still live, but the link is gone.

I’m speculating that the minimum deployment is back up to 10,000 XOs, which was a previous category of deployment.

This is a blow to future small deployments in South Africa, as we have over 600 XOs deployed in South Africa through this program with more that were planned. Marco Rosa has been setting up a local non-profit organisation to raise funds and coordinate deployments – now to no effect unless we use laptops from other vendors.

Now I’ll get back to making Sugar, the learning platform originally developed for the OLPC XO, work on other hardware via Ubuntu…

[Image remixed from Ploum, CC-BY]

Status of Sugar on Ubuntu

2009-02-05T20:58:23Z

Here’s the status of Sugar on Ubuntu:

[ Help wanted sign ]

Sugar 0.82 on Intrepid (8.10)

There are various bugs and issues with Sugar 0.82 on Intrepid.

I’ve finally got a fix released for the problem of Browse not starting – it breaks every time we get a Firefox security update and we need to go through the process of getting hulahop rebuilt against the newer xulrunner path and uploaded to -proposed, tested and pushed out to -updates.

Other issues in Intrepid include needing support for Network Manager 0.7, and the Journal appearing not to store any entries (which is a xapian corruption thing fixed in Debian which we need to apply to sugar-datastore). We need to get these fixed, and there are patches available, so it takes people to do the packaging, sponsor the uploads, test the results, and keep testing and giving feedback.

Sugar 0.84 on Jaunty (9.04)

I’ve been working on packaging Sugar (sucrose) 0.83.x for jaunty. At this stage, the packages are uploaded to a PPA:
https://launchpad.net/~morgan/+archive/ppa. Don’t expect them to work yet, but if you have a troubleshooting mindset, please do help test.

I’ve got tickets open for uploads to jaunty, ready for sponsoring. In the mean time, jaunty still has 0.82.x.

(Please note that PPAs now have signing keys, so you need to add the GPG key to your apt config. Instructions are on the PPA page.)

I’ve packaged glucose and Browse and Chat for now. I could use help packaging the rest of the activities that we have in the archive.

Also, we need to get Read and Write working for Jaunty, which means evince and libabiword. I know Tomeu’s working on the former, and Luke on the latter. Please give feedback to the Ubuntu Sugar Team if you are stuck, or if you have been in contact with the Ubuntu packagers for these.

Logging bugs

If you have problems with Sugar on Ubuntu, please report bugs per the instructions on http://sugarlabs.org/go/Community/Distributions/Ubuntu. If you don’t report a bug, please at least let us know by mailing the Ubuntu Sugar Team (ubuntu-sugarteam@lists.ubuntu.com).

Sugar bugs a-twitter

2009-01-22T11:51:52Z

Inspired by how Launchpad posts bugs to twitter via an atom feed using TwitterFeed, I set up a twitter account for the Sugar Labs trac instance: Follow https://twitter.com/sugarbugs to see new bugs posted.

Due to rate limiting of a maximum of five updates in 30 minutes, it won’t show every bug logged during a busy period, but it gives a nice real-time notification of new bugs on trac.

Now I see TwitterFeed supports identi.ca too, so I’ve added the feed to http://identi.ca/sugarbugs as well.

The status of Sugar, post-OLPC

2009-01-21T11:57:45Z

[The following was largely written by members of the Sugar Labs marketing team.]

[UPDATE: Collabora also provide engineering resources.]

The recent layoffs of almost the entire OLPC software development team have been widely circulated, but not the implications for Sugar, the learning platform originally developed specifically for the OLPC XO but now available on various GNU/Linux distributions including Ubuntu, Debian and Fedora.

Here’s where the Sugar project stands:

Sugar’s development infrastructure is now mostly independent of OLPC, thanks to many generous partners (Ivan Krstic, OSU Open Source Lab, Free Software Foundation, prgmr.com, MIT Media Lab, Solution Grove, Collabora and Develer).
For about 3 months now, Sugar Labs has already been taking care of Sugar development with almost no support from OLPC (other than contracting the core development team until recently).
Sugar has not lost any of its full-time core developers as a consequence of OLPC’s layoffs: All of the core team will stay around as unpaid volunteers while we’re looking for new ways to finance their full-time contribution.
Today, development of Sugar and activities relies upon 20 active contributors.
Over the past few months, we have grown our community with new contributors, new partners and new distributors.
The rate of development seems to be increasing steadily as we consolidate our new community driven development model (we can obtain some support evidence from git).
Through the Software Freedom Conservancy, Sugar Labs is receiving some very generous support (although we’re not yet able to credit individual donors).
While we do not plan to hire a development team within Sugar Labs, we’re working to get some of our full-time volunteer contributors sponsored by external organizations.
Red Hat, Collabora and Solution Grove are contributing with engineering resources and covering traveling expenses for some of our members.
The development cycle is proceeding steadily and Sucrose 0.84 will be released as planned in March.
We’ve been working to establish Local Labs, grassroots organizations which, in our mind, will fill up the gap left by OLPC in deployments.

It’s starting to become clear that 0.84 is where we’ll prove our credibility as a self-sufficient, community-driven project.

See our Getting Involved page!

OLPC in Limpopo

2009-01-14T13:27:11Z

I found a great video produced by One Here One There of their OLPC deployment in Limpopo province, South Africa:

Sugar development needs funding

2009-01-01T19:31:42Z

My contract with OLPC hasn’t been renewed due to financial reasons. I’ve added myself to the rather obscure Professional Services Sugar Labs page – look for more of us to appear there in the near future, as almost all the Sugar developers are in a similar position.

We either need funding, or a way to provide contract services developing and supporting Sugar.

Sugar git repository change

2008-12-15T15:16:21Z

There’s a shiny new instance of gitorious on git.sugarlabs.org, the new home of the upstream repositories for Sugar.

The following modules have moved over from dev.laptop.org:

sugar
sugar-base
sugar-toolkit
sugar-datastore
sugar-presence-service
sugar-jhbuild
read
chat

sugar-jhbuild has moved over as well, and updated to use the new repos. Some of the module names have been changed at the same time, for example presence-service is now sugar-presence-service, and chat-activity is now just chat.

If you’re using sugar-jhbuild, the old repo is up to date as of now with the new repos, but I recommend a completely clean build, cloned from the new repo, unless you have the git-fu to change it in place.

Anyone who could commit/push to the old sugar-* repos is welcome to ask for commit rights on the new repos – we can’t add you until you register on git.sugarlabs.org. In the mean time, it’s trivial to clone a personal repo in the git.sugarlabs.org web interface and push to that and request a merge.

Nvidia twinview and xrandr

2008-11-25T09:29:50Z

AJ, I agree that GUI tools for multihead are lacking. I recently got my nvidia twinview working much easier with some fiddling.

Inspired by smcv’s setup, I also have my external monitor above my laptop screen, and it’s only slightly wider than the laptop screen so I run them at the same width. Since my laptop has an Nvidia Geforce Go 6200, I’ve generally used nvidia-settings to set twinview mode on and off. Since that’s a GUI app, I’ve had to click several times to turn twinview on and off. Turning twinview off automatically moves all the windows to my laptop display, and turning twinview back on moves the ones which were on the external display back to it, so I can undock and redock from my CRT albeit with a whole lot of mouse clicking.

Now on Intrepid (not sure if this could have been done on Hardy, but anyway) I found a command line way to toggle twinview on and off. I had used nvidia-settings to write to my xorg.conf, which had produced the following:

Section “Screen”
Identifier    “Screen0″
Device        “Videocard0″
Monitor        “Monitor0″
Defaultdepth    24
Option        “TwinView”    “1″
Option        “TwinViewXineramaInfoOrder”    “CRT-0″
Option        “metamodes”    “CRT: 1280×1024_85 +0+0, DFP: nvidia-auto-select +0+1024″
EndSection

This at least allowed me to boot into twinview if the CRT was connected at the time.

I have added a metamode now, so that the line above reads:

Option “metamodes” “CRT: 1280×1024_85 +0+0, DFP: nvidia-auto-select +0+1024; CRT: null, DFP: nvidia-auto-select +0+0″

This lets me run “xrandr -s 0″ to select the twinview (CRT at 1280×1024 85 Hz and DFP below it) and “xrandr -s 1″ to turn off twinview.

I then discovered that my Fn+F7 combination automagically does the latter, so I only need to use xbindkeys to enable turning twinview on, so my .xbindkeysrc contains the following:

“exec xrandr -s 0″
Mod4 + F7

That binds it to the combination of Super_L (my Windows key) and F7, so I can undock with Fn+F7 and redock with Win+F7.

This is so much easier than using the nvidia-settings app! It’s going to save literally hours of my life to spend on other things… hope it helps someone else too.