Anyway, here are some notes on getting VNC to work.
Try running vncserver manually first and verify that you can connect to it. If you can't do this, launching via inetd probably isn't going to work, either. If you have trouble see the documentation page for VNC. Also of use is Andre Moreira's page on iXvnc. Ignore the parts about patching vnc since this feature is now part of the standard VNC (and has been for some time). Just jump down to the "Installing/Using" part.
The thing that mattered for me was making /tmp/.X11-unix world-writeable.
After that, vncserver worked by both methods. Note that if the host
is restarted, you'll probably need to reset the rights on that directory
again, as /tmp is often cleared by reboots. I had to do this once
after just killing and restarting the X-server on the host.
vnc-800x600x16 5950/tcp # VNC server
This tells the vncserver to run at 800x600 resolution with 16-bit color, and that the client should use display :50 when attaching.
Add this to /etc/inetd.conf:
vnc-800x600x16 stream tcp nowait nobody /usr/local/bin/Xvnc Xvnc -inetd -query gromit -once -geometry 800x600 -depth 16
(Note that the above should all be on one line.)
After adding the above, do a 'kill -1 ' to the PID of inetd. In the above line, 'gromit' is the name of the host that is running the VNC server. In the example on Andre's page he uses -broadcast instead. This caused a problem for me in that a SCO box on our network responded to this XDMCP request more quickly than did my Sun workstation, and so I was always getting a login screen for the SCO box, which I didn't want. So I specified the host instead. I believe there is a way to have it query all the hosts on the network that have an XDM running, such that you could then pick the host you wanted from a list, but I don't know the particulars on that.