|
|
1.1 root 1: Rogue installation:
2:
3: In order to install your rogue game, you should read mach_dep.c,
4: wherein are located comments which tell you what tunable variables
5: there are. When you wish to create a rogue, type:
6:
7: cc -s <defines...> distmod.o mach_dep.c -lcurses -ltermlib
8:
9: This will create a stripped a.out for you to run. You should
10: initialize the score file by copying /dev/null to it. Rogue is set up
11: so that it can be run setuid; either the score file must be writeable
12: by anyone or rogue must be setuid and the score file must be owned by
13: that user.
14:
15: The file rogue.doc is can be nroffed thusly:
16:
17: tbl rogue.doc | nroff -me -h | col
18:
19: and the output should probably be saved somewhere, since everyone
20: will want to look at it. Also included in the archive is a file
21: ("rogue.new") which briefly explains the changes from 5.2 to create
22: 5.3. This will be useful for rogue hacks who don't want to read the
23: whole documentation, although I'd recommend that they do at first.
24: It is also recommended to play a few games in noterse mode at first.
25:
26: Enjoy,
27: Ken Arnold
28: Mike C. Toy, Esq.
29:
30:
31: ==== NOTE ===
32:
33: THIS VERSION OF ROGUE WILL NOT WORK UNLESS YOU HAVE THE FIXED VERSION
34: OF CURSES DISTRIBUTED IN "NET.SOURCES". If you don't have access to
35: this version, you will have to get it from somewhere. I can provide
36: copies, and it should be distributed with 4.2bsd UN*X.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.