On Wed, 11 Jun 1997, Dave McGuire wrote:
> I just picked up a '3500.  As soon as I get it checked out & cleaned
> up, I think I'll be doing just that.  Anyone else?

I'm working on getting my very own notorious MicroVAX II up and running,
but I'm still desperately seeking an RD54 before I'll probably get
anywhere with it.

Beyond that I've got plenty of spare CPU cycles to contribute from my
happily running pair of VS3100's.  And I'm also one of those sick
individuals who likes to keep compiling the most current versions of an OS
just because I can. :-)

--

Still, Tim Shoppa did make a very good point in his message.  Even if it's
only with the VAX specific pieces of NetBSD -- there really should be some
simple documentation explaining what code is being changed.  I don't
see why we couldn't just add another directory under /usr/src/sys/arch/vax, 
maybe named "doc", which would contain VAX specific notes.  Then everytime
a group of changes are made and applied to the VAX specific code, a text
file summarizing the changes made could be incorporated along with the
patch.  Just a thought.

Since the NetBSD/vax community is so small (we only have a couple of
people actively developing the kernel), we really need to be smarter about
how we keep track of problems.  Be it with kernel bugs, or in installation
setups.

It's a shame to see so much frustration with a machine architecture so
closely tied to the history of BSD.

-brian.
---------------------------------------------------------------------------
Brian D. Chase         Systems Coordinator        brian.chase@carpediem.com
-- Compression, Inc. - 13765 Alton Pkwy, Suite B - Irvine, CA 92618, USA --