Chris,

There still seem to be numerous problems on the Cats with 2.0 beta.

- Booting a non-standard kernel (eg at the firmware prompt typing boot 
wd0:/testnetbsd.aout) seems to lead to the console being dead once 
bootstrap is complete (you can type in the name of the root file system 
and init program, but you can't login afterwards).

- Kernels built with LOCKDEBUG will panic very quickly once booted.

- (maybe related to the above):  I've just had a kernel lock up with huge 
numbers of processes stuck in vnlock.

Do you have any clues about the above?  It really doesn't look as though 
the cats port is in good shape at this time.

(All this is with a Cyclone firmware, but I don't know if that's relevant 
or not -- I'm disinclined to go to ABLE since there seems to be no easy 
route back again afterwards).

R.