[2083] in SIPB-AFS-requests
3.3a/3.4 for rt_aos4
daemon@ATHENA.MIT.EDU (John Hawkinson)
Thu Aug 3 17:36:15 1995
Date: Thu, 3 Aug 1995 17:34:13 -0400
To: sipb-afsreq@MIT.EDU
Cc: yandros@MIT.EDU (Devoted lover of RTs)
From: John Hawkinson <jhawk@MIT.EDU>
Per his note to info-afs yesterday, I asked db74+ if he planned to
port 3.4 to rt_aos4 when it became stable; his response is attached
(yccch, he used pine).
--jhawk
Date: Thu, 3 Aug 1995 17:21:49 -0400 (EDT)
From: Derrick J Brashear <shadow@DEMENTIA.ORG>
X-Sender: shadow@johnstown.andrew.cmu.edu
To: John Hawkinson <jhawk@MIT.EDU>
Subject: Re: 3.3a under RT AOS?
In-Reply-To: <199508032116.RAA17978@lola-granola.MIT.EDU>
Message-Id: <Pine.SUN.3.90c1.950803171924.14063A-100000@johnstown.andrew.cmu.edu
>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
On Thu, 3 Aug 1995, John Hawkinson wrote:
>
> Hullo!
>
> D'you intend to get support for the RT working in AFS 3.4 at some
> point? The SIPB's got a few RTs that we might like to work in that
> environment at some point in the future, and if you'd be actually
> getting that done, having the diffs'd sure be nice :-)
When 3.4 is release-level and stable I intend to start on the work; I'm
not real confident in 3.4 beta...
When I get it working I'd be happy to let you have diffs. My main problem
with diffs right now is I had to make a kernel mod to get m_cpytoc (I
think that's what it was) compiled into the AOS kernel even when AFS
wasn't defined at config time. (otherwise the AFS that comes with AFS
would conflict with the libafs from 3.3a)
Other than that it was straightforward.
Heck, if you want 3.3a you can have that too.
-D
