[1967] in SIPB bug reports
Re: charon kerberos rlogin, hearts server
daemon@ATHENA.MIT.EDU (Marc Horowitz)
Wed Jul 10 22:38:39 1991
To: srz@charon.MIT.EDU (Stan Zanarotti)
Cc: jik@cats.UCSC.EDU, bug-sipb@MIT.EDU, sipb-staff@MIT.EDU
In-Reply-To: Your message of Wed, 10 Jul 91 20:11:35 -0400.
Reply-To: Marc Horowitz <marc@MIT.EDU>
Date: Wed, 10 Jul 91 20:56:52 EDT
From: Marc Horowitz <marc@ATHENA.MIT.EDU>
>> Any of these possibilities is better than getting pissed and showing how
>> you're such a better SIPB member than any of us are...
>>
>> Yelling at people, even electronically, doesn't produce results, Jon.
>> If you haven't learned this yet, I suggest you try.
Sorry, Stan, I have to agree with jik on this one. Since it's well
known that you don't always like to pay attention to jik, I'll make a
few comments. What passes for maintenance on charon is atrocious.
Very few people know the local hacks, since they're poorly documented.
This means that it's hard for people to learn about charon. I'm not
convinced updating charon would be as difficult as you you would make
us believe, but I have no evidence to support this.
Put it this way: Bugs in commercial software get fixed faster than
bugs on charon. (There. Now you should feel really insulted. ;-)
My feelings about charon is that we should make a decision about it.
It should be either a Unix machine which does timesharing, with some
athena stuff installed on it, an Athena server configuration with
local modifications (lots of people do this *and* follow releases), or
something else (such as a 4.3-Reno or Hurd testbed). Whatever it is,
it shouldn't be a half-baked combination.
Marc
