Rails-CMDB release 0.4.3

I’ve released a new version of Rails-CMDB with some reports. Details behind the cut, it can be downloaded from here.

Continue reading


Rails-CMDB release 0.4.1

It’s been a while since I’ve managed to do a release of Rails-CMDB. This is mainly because I got stuck working parts of the test suite and I’ve been doing things that have kept me away from a computer.

However over the last few days I’ve managed to get an import integration story working, which seems to be working. I’ve also taken the chance to migrate to Ruby on Rails 1.2.5, but there are some DEPRECATION warnings still to dealt with.

Behind the cut is the changelog. Continue reading

Cool things in Leopard (and sorting keyboard issues)

I’ve finally upgraded to Leopard and so far I’m loving the following:

  • Built in ssh-agent support.
  • The iCal and Mail integration.
  • Spaces.
  • New look Finder.
  • Profiles in the terminal.
  • Being able to map network shares from the dock.

The things that have not improved.

  • Using a real UK PC keyword is still not handled correctly (I’m had a ergonomic keyboard for years).
  • There seems to be no way to change to size of unread counts in the dock (annoying for netnewswire).

I’ve also just spent what seems like an age getting my keyboard back to functioning correctly, after MacOS refused to do anything to change the keyboard type with the following error (also sometimes the change keyboard type button disappeared from the keyboard and mouse section of system preferences):

No unknown keyboard connected - terminating

The only way to fix it was to remove the following file and then reboot.


Then when re-detecting the keyboard type and selecting the map from the following page, it worked correctly with the keyboard type of ISO European.

It’s been a while…

It’s been a while since I posted and this is mainly because I’ve been very busy with work and also trying to cut back on computer use for the last month.
Currently I’m managing to hold back on the upgrade to Leopard, however this is because some really important software is missing support and thus preventing me upgrading :-(. I’m hoping that early December will give me the new shiny.

A couple of weeks ago I went to a talk at ScotRUG about StaticMatic and I’ve now ported my web site over to it from Website Meta Language. Now all that’s left is working round HAMLs handling of content within pre tags and updating the site so it looks like something created the in latter half of this decade instead of the late 90’s.

ITIL Foundation v3 Certificate

I got some very good news in the post this morning (well it turned up for a start). After weeks of waiting  I got the letter informing me that I had passed the ITIL Foundation v3 exam, which I sat on 27th September.

Really happy about this as I started reading about ITIL some time in May this year, just before I learned about version 3. All in all I think it’s a good improvement over version 2 and well worth doing.

Testing import of CSV imports in Ruby on Rails

It’s been a few weeks since I did any work on Rails-CMDB. This is mainly down me being busy and getting stuck on how to test the import of data. I’ve come to the conclusion that it really is an integration story, so now the problem is how to do the file uploads.

It’ll not be hard to generate a complete set of CSV files and place them on disk, but my issue would be how to upload them. Does anyone have any useful suggestions ?

Correct system time is a security issue

There’s a story that hit Slashdot today about Debian (see bug #433869) not using the security.debian.org system to send out an update to the timezone data for a change in New Zealand daylight savings time.

The update in question is not a security fix, however having the correct time on a system is very important for security. Without the correct local time across all of your different systems (and thus having the correct timestamp on log messages) you will not be able to collate messages between different systems (e.g. routers, firewalls, other unix/linux systems) during an incident. This has already been released by Microsoft, Red Hat and, I expect, other vendors.

To me this seems just to be another reason that an commercial company should not run Debian GNU/Linux as you’re at the whims of a bunch of volunteers who are unlikely to understand the security concerns of your business (e.g. PCI/DSS or Sarbanes-Oxley). However it’s still a good OS if you’re running a personal system or if you can have a team of Debian sysadmins/developers at your call to backport important package changes.