Proposed downtime 3/22, 3/23

I am looking at upgrading from FreeBSD 6 to FreeBSD 7. Unfortunately this means downtime. Additionally, as I'll be moving to a 64 bit OS, I can't just build the "next" gigo.com at home without buying a 64 bit capable spare machine that's only gonna be needed for a few days.

What this means is, I need to actually bring gigo.com down in a big way to do this upgrade. I expect it to take a weekend.

What I'm proposing is 3/22 to 3/23 being declared as "maintenance". I'll obviously try and limit how long mail and web are down, but .. this upgrade is unfortunately going to take time. If this time does not work for you, please let me know. I expect 1 day of major impact, 1 day of minor impact.

The priority order on what I'd get back up and running would be:

• firewalls, dns, ssh (then work from a hotel)
• mailing lists (delayed, until brought back up)
• greylisting,spamd,regular mail,imap (delayed, until brought back up)
• mysql, web,webmail (flat out offline until brought back up - sorry)
• irc, jabber
• bitlbee, rsync
• nagios

I apologize that this is so soon after last August's update - unfortunately, FreeBSD 7 was only just now released. Minor upgrades are not nearly as big of a deal (usually just a minor install and a reboot). But a major upgrade, those are a bit more painful (especially changing from 32 bit to 64 bit at the same time).

Before anyone asks: Yes, in theory, I could move *everything* to another site, somewhere else, maybe even volunteered space, but the overhead in doing so is too much, for the amount of stuff here. Given my limited free time, that's not an option. But, thanks in advance for thinking about it.