[1446] in Kerberos
Re: Kerberos for AT&T?
daemon@ATHENA.MIT.EDU (Barr3y Jaspan)
Tue Jul 9 13:06:39 1991
Date: Tue, 9 Jul 91 12:30:02 -0400
From: "Barr3y Jaspan" <bjaspan@ATHENA.MIT.EDU>
To: Chris Riddick <cjr@simpact.COM>
Cc: kerberos@ATHENA.MIT.EDU
From: Chris Riddick <cjr@simpact.COM>
Date: Mon, 8 Jul 91 7:55:27 EDT
We have ported V5 to SCO V3.2. I haven't looked at SVR4,
but if SVR3.2 is any indication ny indication of effort
required the two principal areas you need to worry about
are porting the ISODE tools and file name length
restrictions.
Just fyi: I began to port Kerberos V to an Intel 486 box running
Intel's SVR4. Except for two or three yacc files, ISODE it built *on
the first try* (I was impresed); the yacc files merely required adding
a #include <stdlib.h> (there were declaration conflicts with malloc,
et al). I did not, however, proceede much further with the port
(other things arose).
Barry Jaspan, bjaspan@mit.edu
