> Check out /usr/src/etc/etc.svr4 ... there you should find a
> SVR4_MAKEDEV and an example netconfig file...I'm pretty sure that
> running SVR4_MAKEDEV in /emul/svr4/dev and placing the netconfig
> file in /emul/svr4/etc will DTRT...

Now it can open /dev/ticotsord fine, but complains after failing a
TIOCGETP (old) ioctl:

   339 xterm    NAMI  "/emul/svr4/dev/ticotsord"
   339 xterm    NAMI  "/emul/svr4"
   339 xterm    NAMI  "/emul/svr4/dev/ticotsord"
   339 xterm    RET   svr4_open 3
   339 xterm    CALL  svr4_ioctl(0x3,0x530b ,0x41ada04)
   339 xterm    RET   svr4_ioctl 1
   339 xterm    CALL  svr4_ioctl(0x3,0x5320 ,0xf7ffed3c)
   339 xterm    RET   svr4_ioctl 0
   339 xterm    CALL  svr4_ioctl(0x3,0x5313 ,0x2)
   339 xterm    RET   svr4_ioctl 0
   339 xterm    CALL  svr4_sigpending(0x2,0x42b8480)
   339 xterm    RET   svr4_sigpending 0
   339 xterm    CALL  svr4_sigprocmask(0x3,0xf7ffed2c,0xf7ffed1c)
   339 xterm    RET   svr4_sigprocmask 0
   339 xterm    CALL  svr4_ioctl(0x3,0x5308 ,0xf7ffeb90)
   339 xterm    RET   svr4_ioctl -1 errno 22 Invalid argument
   339 xterm    CALL  close(0x3)
   339 xterm    RET   close 0

Also bothersome is that 0x530b, 0x5320, and 0x5313 should be
unrecognized ioctls as far as I can tell (which would explain the
return value of 0, but which isn't very encouraging).

If I set my DISPLAY to machinename:0.0 to force a TCP connection,
Solaris xterm gets a bus error just after closing netconfig.