So I'm sure you can imagine my excitement when I stumbled across an archive containing XENIX ports of a bunch of Unix games, including vtrek. (Thank you, Vince!) I'm not even sure how I managed to find that. Nowadays, Google only returns two search results for vtrek, the XENIX game port archive and a munged version of the original release to net.sources.games, and that's only if you know to include the "duncel" insult the game uses in the search terms. Google Groups searches of net.sources.games will lead you to a series of posts from the fall of 1985, but how would anyone other than an old fuddy duddy like me even know to look there? (Also, Google Groups doesn't have the original Usenet posts, so formatting is all screwed up. It's a vexing problem for the modern programmer archeologist.) Now imagine, if you will, an eager and not inexperienced nerd trying to compile a System V-era game on Linux and FreeBSD circa 2005. This Star Trek quote seems appropriate:
PAIN!
I mean, even the Real Hackers back in 1985 had problems getting it to compile, so I don't know why I thought my experience would be anything other than worse. The termios code in glibc just didn't work. At all. Neither did the sgtty code, which had been broken since at least 4.4BSD. After a good long while beating my head against vtrek, even going so far as to trying to build it on OpenStep 4.2 (from 1997) and FreeBSD 2.0 (from 1994), I gave up. Maybe it's time to give it another go for nostalgia's sake.
The 1985 release per Google Groups:
https://groups.google.com/g/net.sources.games/search?q=vtrek
For an example of how Google Groups screws up posts, here's a patch to vtrek:
https://usenet.trashworldnews.com/?thread=241631
And here's Google's version:
https://groups.google.com/g/net.sources.games/c/Rx_u0q5V5iE/...
The XENIX port (thanks again, Vince!):
https://svn.so-much-stuff.com/svn/trunk/cvs/trunk/games.d/vt...
Hints at how I might get vtrek to work:
https://comp.unix.programmer.narkive.com/KP4z3Ge2/problem-wi...
God bless Thomas Dickey, who's been maintaining vttest this whole time!