READ_ME 4.2 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283848586878889909192939495
  1. $NetBSD: READ_ME,v 1.2 1995/03/23 08:29:12 cgd Exp $
  2. Hack is a display oriented dungeons & dragons - like game.
  3. Both display and command structure resemble rogue.
  4. (For a game with the same structure but entirely different display -
  5. a real cave instead of dull rectangles - try Quest)
  6. Hack was originally written by Jay Fenlason (at lincolnsudbury:
  7. 29 East St., Sudbury Mass., 01776) with help from
  8. Kenny Woodland, Mike Thome and Jon Payne.
  9. Basically it was an implementation of Rogue, however, with 52+ instead of 26
  10. monster types.
  11. The current version is more than thrice as large (with such new features as
  12. the dog, the long worms, the shops, etc.) and almost entirely rewritten
  13. (only the display routines are the original ones - I must rewrite these
  14. too one day; especially when you are blind strange things still happen).
  15. Files for hack:
  16. hack The actual game
  17. record Top 100 list (just start with an empty file)
  18. news Tells about recent changes in hack, or bugs found ...
  19. (Just start with no news file.)
  20. data Auxiliary file used by hack to give you the names
  21. and sometimes some more information on the
  22. objects and monsters.
  23. help Introductory information (no doubt outdated).
  24. hh Compactified version of help.
  25. perm An empty file used for locking purposes.
  26. rumors Texts for fortune cookies.
  27. (Some of these contain information on the game,
  28. others are just plain stupid. Additional rumors
  29. are appreciated.)
  30. hack.sh A shell script.
  31. (We have hack.sh in /usr/games/hack and
  32. hack in /usr/games/lib/hackdir/hack and all the other
  33. hack stuff in /usr/games/lib/hackdir - perhaps this
  34. will make the script clear.
  35. There is no need for you to use it.)
  36. READ_ME This file.
  37. Original_READ_ME Jay Fenlason's READ_ME
  38. System files used:
  39. /etc/termcap Used in conjunction with the environment variable
  40. $TERM.
  41. /bin/cat
  42. /usr/ucb/more
  43. /bin/sh Used when $SHELL is undefined.
  44. How to install hack:
  45. 0. Compile the sources. Perhaps you should first look at the file config.h
  46. and define BSD if you are on a BSDtype system,
  47. define STUPID if your C-compiler chokes on complicated expressions.
  48. Make sure schar and uchar represent signed and unsigned types.
  49. If your C compiler doesnt allow initialization of bit fields
  50. change Bitfield. When config.h looks reasonable, say 'make'.
  51. (Perhaps you have to change TERMLIB in the makefile.)
  52. 1. If it didnt exist already, introduce a loginname `play' .
  53. 2. The program hack resides in a directory so that it is executable
  54. for everybody and is suid play:
  55. ---s--s--x 1 play 206848 Apr 3 00:17 hack
  56. Perhaps you wish to restrict playing to certain hours, or have games
  57. running under nice; in that case you might write a program play.c
  58. such that the program play is suid play and executable for everybody
  59. while all the games in /usr/games are readable or executable for
  60. play only; all the program play does is asking for the name of a game,
  61. checking that time-of-day and system load do not forbid playing,
  62. and then executing the game. Thus:
  63. -r-sr-sr-x 1 play 13312 May 24 12:52 play
  64. ---x------ 1 play 206848 Apr 3 00:17 hack
  65. If you are worried about security you might let play do
  66. chroot("/usr/games") so that no player can get access to the rest
  67. of the system via shell escapes and the likes.
  68. If you #define SECURE in config.h then hack will not setuid(getuid())
  69. before executing a chdir(). Hack will always do setuid(getuid()) with
  70. a fork. If you do not define UNIX then hack will not fork.
  71. 3. The rest of the stuff belonging to hack sits in a subdirectory hackdir
  72. (on our system /usr/games/lib/hackdir) with modes
  73. drwx------ 3 play 1024 Aug 9 09:03 hackdir
  74. Here all the temporary files will be created (with names like xlock.17
  75. or user.5).
  76. 4. If you are not really short on file space, creating a subdirectory
  77. hackdir/save (modes again drwx------) will enable users to save their
  78. unfinished games.
  79. The program hack is called
  80. $ hack [-d hackdir] [maxnrofplayers]
  81. (for playing) or
  82. $ hack [-d hackdir] -s [listofusers | limit | all]
  83. (for seeing part of the scorelist).
  84. The shell file hack (in this kit called hack.sh) takes care of
  85. calling hack with the right arguments.
  86. Send complaints, bug reports, suggestions for improvements to
  87. mcvax!aeb - in real life Andries Brouwer.