bob's tech ramblings

where i ramble about technical things

Entries tagged "openguides".

7th April 2007

Things I have learnt this week.

  • Backups are good.
    • If for instance your colo box breaks.
  • Tested backups are better.
    • Best to test them before your box breaks.
  • Automated backups are better still.
    • Humans forget to do things. Machines rarely do. So your backup may not be as recent as yo u think.
  • How to backup svn
    • svnadmin dump $repo | bzip2 > svndump.bz2
  • Checking which disk you are replacing in a degraded mirrored pair is a good thing
    • Your filesystem dieing or going back in time is not fun. See previous points

Having learnt these things I have made my backup regime better and have made sure its croned and does backup the stuff I need. I s hould also start putting more stuff in my svn repo.

This clusterfuck did annoyingly lead to losing about a weeks worth of data on the Randomness Guide to London which was particularly galling since one of the reason for doing it was I trusted myself more with the data. bah

14th April 2007

So recently Kake and I have been adding Public Domain Geodata to our Guide to London using a Garmin Etrex she has been borrowing from a friend. However, it possibly has one of the one most annoying interfaces i've used for a while and we only have one.

So, I succumbed and bought the Nokia LD-3W which works with my phone. I can get location data with applications which came as standard and indeed save landmarks which I can then export as an xml file. I cant get any routes though. However, I did find an application from nokia research which almost gives me what i want. It can export trip data as kml. So for your viewing pleasure My trip to the butchers this morning. It jumps around quite a bit.

One problem is that I can only get Lat/Long out when we are using OSGB for the guide. Thankfully, the windows program the Ordnance Survey provide to convert between them can run under Wine. This will make mass conversions easier.

10th August 2009

The first perl 5.10.1 release candidate was released the other day. As mst says if you don't test it now and it breaks for you when its released its your fault. As a good cpan tester I've added it to my testing setup.

Since I care about OpenGuides for the Randomness Guide to London I made sure to submit a test report for it.

While I was doing this I also added perl 5.8.9 to my setup. I also changed my setup slightly by pre-installing Moose and Catalyst since thats what all the cool perl programmers are using these days. Since installing and testing their dependency chains was burning a lot of cpu, time and bandwidth every time a new module based on them was updated or added to CPAN