updatinator status, issues

[Alexander Larsson]

On Thu, 2007-07-26 at 11:55 -0400, Dan Williams wrote:
> On Thu, 2007-07-26 at 17:00 +0200, Alexander Larsson wrote:
> > 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.
> 
> I did an update from 530 -> 535 yesterday and it worked perfectly,
> preserving all my user data.  Nice job.

That was a centralized update though (i.e. from the olpc1 http server).
Thats won't get the same problem as a peer-to-peer update if the local
image has been modified.