[comp.protocols.appletalk] Updated ru-cap2 available.

rapatel@khnphwzhn.njin.net ( Rakesh Patel) (11/20/90)

There is an updated version of ru-cap2 avialable via anonymous from 
rutgers.edu (src/ru-cap2.tar.Z). There have been a few more bug fixes
added in and it should now work on networks that do not have any
Appletalk routers on them when you specify the zone and network number
in atalk.local (I tested it this time :-). This is when using the
ethertalk support on Suns using the Berkeley enet driver. There were
various patches to some of the cap applications as well.

Anyone using any prior version of CAP (Rutgers, Columbia, etc.) should
upgrade to this version. There have been many bug fixes that
improve reliability. In addition to fixes to dozens of bugs, there are
many enhancements as well. People are strongly encouraged to upgrade.
The Rutgers version is 100% backwards compatible with the Columbia
CAP 5.0 release when configured for IPTalk, so it shouldn't cause
any pain to convert to it. Even if you got the initial ru-cap2
release, you'll want to get this version.

NOTE: The Rutgers CAP version has contained the NeXT patches (from
Edward Moy at Berkeley) for a while, however, it has not yet been
tested on the NeXT. If any other patches are necessary, please let me
know.

Possible changes in later releases:

	Support for the use of System V shared memory as an
	alternative to Sun's mmap() function. This is likely to
	be only on the Pyramid initially. This should aid portability
	for the ethertalk support. All one would need to do is to
	port the enet driver as long as either System V shared memory
	or Suns mmap() call exists on the machine in question.

	Phase II support. Probably a few months away due to time contraints.

	System V support (likely to be from someone outside Rutgers).
	I haven't had much time to help the person working on it
	unfortunately.

	PC Aufs support.

I make no guarantee on these, but if time is found, the some of the above are
likely to be included in the future.

Thanks to those that have reported and helped fix the problems that
existed. I'm awaiting more of those fixes. :-)

Rakesh Patel.