As tb@ pointed out, /usr/man/man6 also doesn't exist. Let's remove
the whole "Installation" section.
OK?
Index: games/hunt//README
===
RCS file: /cvs/src/games/hunt/README,v
retrieving revision 1.1.1.1
diff -u -p -r1.1.1.1 README
--- games/hunt//README 21 Jan 1999 05:33:37 - 1.1.1.1
+++ games/hunt//README 13 Jun 2017 16:27:43 -
@@ -43,59 +43,6 @@ Words of Warning:
hunt abusers. Hunt may also be addictive, and the
withdrawal symptoms are not pretty :-)
-Installation:
-
- 1. Edit file "Makefile" and make sure the options selected are
- reasonable. There are four "make" variables that you
- should check: GAME_PARAM, SYSCFLAGS, SYSLDFLAGS, and DEFS.
- GAME_PARAM controls what features of the game will be
- compiled in (e.g. reflecting walls). The optional features
- are listed in comments above where GAME_PARAM is defined.
- If you want to try them, just add the ones you want to the
- GAME_PARAM definition.
-
- DEFS is where most system configuration is described.
- If your system is 4.3BSD, Sun, Ultrix, Convex, HPUX
- v6.0.1, or SGI, you're in luck. We provide the
- appropriate definitions for these systems and you just
- need to select one of them (e.g. if you have an Ultrix
- system, just change the line
- DEFS= $(GAME_PARAM) $(DEFS_43)
- to
- DEFS= $(GAME_PARAM) $(DEFS_ULTRIX)
- ). If your system is *not* listed above, then you may
- need to do some experiments. All of the options are
- documented in the Makefile, be brave.
-
- SYSCFLAGS and SYSLDFLAGS are used for "unusual" systems
- and you probably won't need to deal with it. An
- example of an unusual system is the Silicon Graphics
- IRIS, which keeps the network socket code in a BSD
- emulation library that is in -lbsd. Edit these only if
- you *know* your system is "different."
-
- 2. Edit file "Makefile" and look at the "install:" target. By
- default, files are installed in /usr/games,
- /usr/games/lib, and /usr/man/man6, which are "standard"
- locations for games. If your system has a local games
- directory, you'll need to change these.
- 3. Edit file "pathname.c" and make sure the file names and port
- numbers are reasonable. You can ignore the first set
- of variables as they are used only for debugging
- purposes. The second set is used in the installed
- version of hunt. The important variables are "Driver"
- (where the server is kept), "Test_port" (the Internet
- UDP port number that new players should use to contact
- the server), and "Stat_file" (where scoring statistics
- and body counts are written). The only tricky variable
- here is "Test_port". The default value is chosen so
- that it is unlikely to conflict with other service port
- numbers, but you can change it if you want to.
- 4. Type "make install", which will compile and install the
- programs and manual pages. Now you're almost ready to
- go (see next section). There may be some warnings during
- compilation. Ignore them.
-
Setting up the network:
Hunt may be set up in one of three modes: standalone, inetd, or
@@ -121,12 +68,12 @@ Setting up the network:
server machine. THERE SHOULD ONLY BE ONE SERVER MACHINE!
# start up the hunt daemon if present
- if [ -f /usr/games/lib/huntd ]; then
- /usr/games/lib/huntd -s & (echo -n ' huntd')>/dev/console
+ if [ -f /usr/games/huntd ]; then
+ /usr/games/huntd -s & (echo -n ' huntd')>/dev/console
fi
Also, you should start one up (on the off chance that you will
- want to test this mess :-) by typing "/usr/games/lib/hunt -s".
+ want to test this mess :-) by typing "/usr/games/hunt -s".
-
@@ -140,7 +87,7 @@ Setting up the network:
that variable, then you should put whatever value you used here
as well. In /etc/inetd.conf, add the line
- huntdgram udp waitnobody /usr/games/lib/huntdhuntd
+ huntdgram udp waitnobody /usr/games/huntdhuntd
This works for 4.3BSD. I don't remember the configuration file
format for 4.2BSD inetd.
--
Michal Mazurek
