Subject: Re: Alright, damnit, this is getting annoying.
To: Rick Copeland <rickgc@calweb.COM>
From: Tim Shoppa <>
List: port-vax
Date: 06/11/1997 13:08:16
> I understand what you are saying, I have spent almost 5 months trying to get
> a workable system on my VAX's with no real success. THIS PORT HAS MAJOR

Part of the problem is that when changes are made (i.e. between 1.1 and
1.2) there is apparently no place to go and figure out who broke what
and when.  Or is there?  Is there some list somewhere, where we can
track down the changes made to various drivers that cause them to no
longer work, and figure out what can be done to fix it?

IMHO, the right approach to take is what Steven Schultz does with
his patches to 2.11BSD for the PDP-11.  Each patch has a little
info file telling what's being modified, why (with examples if
something broken is being fixed), which source modules are modified,
and which exectubles are being modified.  This makes it incredibly easy
to track all the changes.  For examples of how Steven does it right,
look at some of his patches:

I realize that this procedure may not be fully realizable for NetBSD,
as there are so many changes being made from other platforms.  But it
seems to me that most of the problems I've seen introduced from release to
release is VAX-specific, and I think the world would benefit greatly
if some order was imposed such that common folks (like me) could
figure out who was breaking what.

Tim. (