Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!apple!apple.com!falken
From: falken@apple.com (Dave Falkenburg)
Newsgroups: comp.protocols.appletalk
Subject: Re: CAP on Apollo Domain
Message-ID: <2138@internal.Apple.COM>
Date: 31 May 89 17:53:18 GMT
References: <2996@cayman.COM>
Sender: usenet@Apple.COM
Organization: Apple Computer, Inc.
Lines: 30

In article <2996@cayman.COM> chris@cayman.COM (Chris North, Technical 
Support) writes:
> Has anyone installed it?  I tried but the C libs on an Apollo are not
> archived as CAP expects them to be so I am not sure what to do.  Any
> ideas?
> 
> -chris

At university of michigan we did a port of cap to the apollo.  Basically, 
because the libraries are not "just like real unix" because of the neat 
file system, nm doesn't work.   What you should do is start with a generic 
BSD build, then define the NOSENDMSG and NORECVMSG (or something like 
that) so that the cap library can be built.  (Basically sendmsg() et. al. 
never made it into apollo's tcp libraries)  Do a build & everything should 
work-- EXCEPT aufs

Basically because of apollos distrbuted file system's root level called 
"//" instead of "/", aufs will blow up when it tries to assign unique 
directory IDs to all the paths below.  If i can recall, a few simple 
changes to "afpdid.c" did the trick, but i'm not quite sure if that was 
all (we did this over a year ago & we havent looked at it since-- CAP 
seems to have memory leaks or other errors which seems to leave nasty, 
un-killable processes around so we didn't officially support it)


-dave falkenburg
  falken@apple.com

Disclaimer: I did this stuff while at UMich, so Apple has nothing to do 
with it..