Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!uunet!ingr!b11!dwig
From: dwig@b11.ingr.com (David Wiggins)
Newsgroups: comp.windows.x
Subject: XDMCP questions
Keywords: XDMCP, xdm, display manager
Message-ID: <7663@b11.ingr.com>
Date: 8 Mar 90 18:23:14 GMT
Organization: Intergraph Corp. Huntsville, AL
Lines: 28


I'm trying to get xdm running on System 5 with BSD extensions.

Our BSDisms are extensive enough that we can compile the entire os/4.2bsd
directory almost without modification - the minor exception being changing
"MIN" to "min" in xdmcp.c.  (This info provided in case it affects the
anwer to my first question.)

Questions:

Why is the call to WaitForSomething ifdef'ed out for SYSV in the R4 xdm?
Is their some fundamental problem with supporting XDMCP on System 5 that
I should be aware of?

There appears to be no code to perform byte-swapping for XDMCP in the server
or xdm.  (Our machines are little-endian, and XDMCP requires big-endian.)
Should I take the time to add it, or is someone else doing this?

Is there any reason why the execute() function was not used in place of
execve() in xdm/session.c?  The ExecableScripts configuration parameter
might be useful here.

By the way, who should one contact regarding problems with the xstuff server?

Thanks for any response!

David P. Wiggins	dwig@ingr.com  or  uunet!ingr!dwig	(205)730-6365
Intergraph Corporation, One Madison Industrial Park, Huntsville, AL 35807