Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!udel!haven.umd.edu!ni.umd.edu!sayshell.umd.edu!louie
From: louie@sayshell.umd.edu (Louis A. Mamakos)
Newsgroups: comp.sys.next
Subject: Re: Postscript
Message-ID: <1991Apr29.201739.16532@ni.umd.edu>
Date: 29 Apr 91 20:17:39 GMT
References: <47941@ut-emx.uucp> <1991Apr26.044349.5265@ni.umd.edu> <1991Apr29.132216.1@capd.jhuapl.edu>
Sender: usenet@ni.umd.edu (USENET News System)
Organization: University of Maryland, College Park
Lines: 24
Nntp-Posting-Host: sayshell.umd.edu

In article <1991Apr29.132216.1@capd.jhuapl.edu> waltrip@capd.jhuapl.edu writes:

>> Wow, funny you should mention this.  We will most likely be using
>> Kerberos authenticated AFS on our NeXTs anyway.
>	I, for one, will be very interested in how you accomplish this.  I
>	would be very interested in NeXT accomplishing it FOR us all (2.2?).

The short answer is: we are going to license the NeXT sources and
ruthlessly hack as much as we need to get the job done.  Personally,
I'm hoping that we can rebuild the shared C library to catch a good
bit of this.

As far as AFS is concerned, you can just buy it from Transarc.  We
have yet to work out who (Transarc or NeXT) is going to supply a
modified loginwindow program which does the kerberos authentication
necessary.  Once again, we are licensing the AFS sources as well so
that we won't be at the mercy of a vendor to get this stuff done for
us.

And some vendors wonder why we are so adament about being able to license
source code for their products.  Its to make their products usable in our
environment, and not the one perceived by their marketeers.

louie