[58] in Layered Athena
Re: new way of doing Layered Athena
daemon@ATHENA.MIT.EDU (brlewis@MIT.EDU)
Thu May 19 11:48:48 1994
From: brlewis@MIT.EDU
Date: Thu, 19 May 94 11:47:15 -0400
To: kcunning@MIT.EDU
Cc: layered-athena@MIT.EDU
In-Reply-To: <9405181340.AA24217@slingshot.MIT.EDU> (kcunning@MIT.EDU)
I'm afraid I chose my subject line rather poorly. I should have
written, "new way DCNS allocates human resources to Layered Athena".
It's not a change to the goals and overall concept.
The work involved in getting Layered Athena working on any Unix platform
has more to do with the platform than with Layered Athena. It only
makes sense that LA work for Solaris should be done as a part of the
Solaris project. As the Layered Athena developer, I shouldn't have to
learn the quirks of every operating system.
I can't take credit for the idea. While I was scrambling to get
Kerberized telnet clients, servers and man pages ready for release 7.7,
Tim was thinking about Layered Athena, and told me about this idea. In
the process of bouncing his idea off a number of people, he got the
sense that there's a lot of sentiment that Layered Athena should really
move forward, and he did his part. (Tim can correct me if any part of
this is wrong).
When I cc'ed layered-athena on my message to developers, I somehow
spaced by using the phrase "doing Layered Athena" when talking about
something that doesn't affect documentation, support, licensing, etc.
A Layered Athena team meeting would be a good thing. I've been lame
about getting CSS set up with a test layered machine, but I'm going over
today. How about giving them 3 weeks of testing, and then meeting on
June 16, 10-11:30?
