Which Server

Thanks drunken monkey. The differences compared to Environment Indicator (which I've also used) are:

• Environment indicator is for the same site in different environments (e.g. test versus staging versus live), while my module is for multiple sites (live or test or staging) installed on a range of different servers.
• My module is to assist site administrators with installing and updating modules, where the administrator has Drupal sites installed on several servers. It is not a testing/live environment indicator, it's a module maintenance tool to improve the core Update manager module.
• My module requires no configuration, you just enable it and it does its work. I host many Drupal sites on several servers, and this module is very useful to me :) Perhaps not so useful for people who only have one server, or only one or two sites.

I'll have a look at possibly submitting patches for Drupal core's Update manager module. That seems to me to be a better place than the Environment Indicator module, which is intended for something quite different. The only thing is that my additions aren't needed for most people, so probably don't need to live in core either...

I used a theme override as that seemed to be a quick way to add to the updates table, but then found that this didn't work in Drupal 6, so resorted to hook_help() instead. Should have used hook_help() instead, I'll re-write that. I'll also add t() to the untranslated string, well spotted :)

I've modified the code as suggested by drunken monkey, so it uses hook_help() instead of modifying the themeing of the updates list, and to add the missing t().

Set back to "needs review" as I personally find this module provides useful functionality that isn't likely to be available elsewhere (it's not really relevant for core, and solves a different need to the environment indicator module).