[951] in Kerberos
Porting Kerberos to an SYSV Platform
daemon@ATHENA.MIT.EDU (Riddick@DOCKMASTER.NCSC.MIL)
Fri May 18 19:01:40 1990
Date: Fri, 18 May 90 16:03 EDT
From: Riddick@DOCKMASTER.NCSC.MIL
To: kerberos@ATHENA.MIT.EDU
Cc: Riddick@DOCKMASTER.NCSC.MIL
We are trying to port Kerberos over to a System V 3.2 platform and we
are having trouble getting past the makefiles. We haven't had a chance
to attack the BSD -vs- SYSV differences because of the platform we are
porting to. Specifically, we are using an Intel-386 machine with SCO
UNIX.
We have two specific questions, but can use any advice that you can
give:
1. In each "conf" file in /mit/kerberos/src/include, there are several
defines that describe the platform on which kerberos is installed. It
is not clear where or how thesedefines are used in the kerberos source
code (i.e., for conditional compilation, etc.). Could someone explain
the purpose of thesedefines (particularly CROSSMSDOS, BIG, and IBMPC),
and the set from which they are selected?
2. To port kerberos to a System V Unix on an Intel 80386 host, a new
conf file in /mit/kerberos/src/include must be created and a newifdef
condition added to the 'osconf.h' file. This file assumes that 'vax',
or 'sun', or 'tahoe' have been defined somewhere. These constant
identifiers don't appear to be manifest defines. Who defines one of
them and where?
I would appreciate any advice you can give.
Thanks in advance,
Chris Riddick
