updatinator status, issues

[Alexander Larsson]

I've updated autoupdatinator (the peer-to-peer mDNS version of the
updatinator downloader) to work with the new repository layout where
manifests are stored as blobs. I've tested it by publishing an apache
http server with a static avahi server file, and it works well.

I also updated the server-release tool that lets you publish the olpc:s
current image via avahi, but when testing this on my XOs I immediately
ran into an issue. When trying to download a blob I got a 404 error. It
turns out this was due to the manifest listing /var/lib/rpm/__db.001,
which gets removed from the root filesystem at boot.

In general I think there are problems with trying to do updates like
this if we don't have a pristine version of the current image (even when
using e.g. rsync and not updatinator), and we're currently modifying the
image all over the place (writing logs, removing rpm db files etc). What
is the current status of the vserver work? Perhaps we need to start
thinking about that stuff now so we can get robust updates...

Anyway, the updatinator stuff is in git for people who'd like to play
with the code.