Just mailing this for notice:

With help of rick's snapshots I got netbsd to install on
our uvax2/630.

Somehow it seems to have lots of problems with the 2nd drive
installed though (I don't know if this has anything to do
with the stuff on Ragge's todo-list).

the vax has dua0 which is a Maxtor XT2190 and a dua1 which is a
dec rd53.
racopy thinks dua0 is also a rd53, which is not the end of the
world, just inconvenient; I'd have to relabel the disk manually
(the kernel does recognize the actual size in sectors though
when booting).
Unfortunately, relabeling cannot be done while the device is
mounted =).
Fortunately, I have a second drive, which is a rd53.
Unfortunately, newfs-ing this drive results in a bunch of
hard- and softerrors. I know that this drive has a few
bad blocks, but not where the first superblock is stored.
Shouldn't newfs map out the bad blocks ? If it does,
it may be something else since the kernel sometimes even panics
during access of this drive. Both drives are on the uda controller.

Then, it seems the kernel doesn't like 'vi'. Whenever vi is
fired up (either manually or by 'disklabel -e') the kernel
dumps, syncs and breaks out. Is this a known feature and a 
quest to ban the usage of vi ? =)

Michel.