[1394] in NetBSD-Development
sipb-athena source issues for ringworld
daemon@ATHENA.MIT.EDU (Greg Hudson)
Thu Oct 24 03:15:17 1996
Date: Thu, 24 Oct 1996 03:14:49 -0400
From: Greg Hudson <ghudson@MIT.EDU>
To: pc-dialup@MIT.EDU, ops@MIT.EDU
Cc: sipb-athena@MIT.EDU
I'm thinking about how to handle the NetBSD 1.2 upgrade on ringworld.
It will require upgrading some Athena programs (attach and login, at
least), and it would seem like a good idea to get in all the
improvements that were made to sipb-athena between then and now.
My recollection is that there are only a few changes to the athena
sources for ringworld--the telnetd banner, mainly. So it would make
the most sense to do a wholesale upgrade and then merge in the local
changes. But with the current organization (a separate RCS tree),
there's no way to identify precisely what changes were made for
ringworld, which is a real pain for me right now.
Does anyone have any problems with me creating an ops branch of the
sipb-athena repository and making /mit/opssrc/dialup/netbsd/athena-src
a working directory on that branch? It assumes a few things about
tree administration (changes can't be checked in on the ops branch
without write access to the sipb-athena repository; changes could
still be made locally and never checked in, of course), but in the
long run I see PC dialup service using code from IS rather than SIPB,
so I think the short term simplification is worth the assumptions.
