Things we definitely need to do:

1. ensure all disks are in use
2. ensure user data integrity

First, backup:

1. from mudge: rsync -a --progress --exclude '/tmp/*' --exclude '/proc/*' / root@tumbo.cs:/fsys2/ (I've already verified that /fsys2 on tumbo has sufficient room to hold "all" of mudge.) This is to both have a backup and to have a "live" copy of the data from /etc so I can duplicate the old setup. For instance, mudge uses softbase as a mail handler... Except this isn't working because for some reason tumbo's decided to hate mudge. And after trying different methods three or four times apiece, it suddenly started working again. This is rather distressing. Logged in as mpatters, ran screen, then suw. Once that is complete, run it again to catch any files that have been changed.

Simultaneously with this, shut down unneeded machines in the mudge region (gooch, quadra). First do "dpkg --get-selections > quadrapkgs" on quadra, just to get latest package selections. Those will be over on tumbo due to the backup, so we'll be able to get at them when we restore files.