| 1 | Frequently asked questions about the PennMUSH Server, post-pl10 |
|---|
| 2 | |
|---|
| 3 | Updated: January 15, 1996 |
|---|
| 4 | |
|---|
| 5 | 0. What's the release history since pl10? |
|---|
| 6 | 1. How do I ask for help with a problem? |
|---|
| 7 | 2. How do I report a bug? |
|---|
| 8 | 3. How do I request a new feature? |
|---|
| 9 | 4. Where can I get more information about admin'ing and hacking MUSH? |
|---|
| 10 | 5. Where can I hear about new releases? |
|---|
| 11 | |
|---|
| 12 | ----------------------------- |
|---|
| 13 | |
|---|
| 14 | 0. What's the release history since pl10? |
|---|
| 15 | |
|---|
| 16 | PennMUSH pl10 is the last patchlevel of PennMUSH developed by Amberyl. |
|---|
| 17 | Amberyl handed over the maintenance, development, and support of |
|---|
| 18 | PennMUSH to Javelin/Paul (Alan Schwartz) after pl10. |
|---|
| 19 | |
|---|
| 20 | The first two post-pl10 releases were termed the "dune-1" and "dune-2" |
|---|
| 21 | releases (in honor of DuneMUSH, where Alan did most of his development |
|---|
| 22 | work). Amberyl and Javelin agreed that it was silly to start a whole |
|---|
| 23 | new numbering scheme, so the next patchlevel released was pl11. |
|---|
| 24 | |
|---|
| 25 | Javelin, along with the other two PennMUSH developers, T. Alexander |
|---|
| 26 | Popiel and Ralph Melton, made so many internal changes that it was |
|---|
| 27 | time for a new numbering scheme, and PennMUSH was advanced to 1.6.0. |
|---|
| 28 | |
|---|
| 29 | |
|---|
| 30 | 1. How do I ask for help with a problem? |
|---|
| 31 | |
|---|
| 32 | Email to dunemush@mellers1.psych.berkeley.edu |
|---|
| 33 | When asking for help, please be as specific as you can about the |
|---|
| 34 | problem. Include at least the following: |
|---|
| 35 | - Version of PennMUSH including any official patches you've applied |
|---|
| 36 | - Host machine brand (Sun, Dec, etc.), model (Sparcstation, etc.) |
|---|
| 37 | - Operating system version (e.g., Ultrix 4.4) |
|---|
| 38 | - Compiler used to compile (if a compilation problem) |
|---|
| 39 | - A description of the problem: what you think it should be doing that |
|---|
| 40 | it isn't. |
|---|
| 41 | - If things were working, and you recently changed something and they're |
|---|
| 42 | not working now, what did you change? |
|---|
| 43 | |
|---|
| 44 | 2. How do I report a bug? |
|---|
| 45 | |
|---|
| 46 | Email to pennmush-bugs@mellers1.psych.berkeley.edu |
|---|
| 47 | Include specific information as described in #3 above. If you know |
|---|
| 48 | what's causing the bug, or how to fix it, or if you have a patch for |
|---|
| 49 | the bug, send it along. If you don't, and the bug caused a crash with |
|---|
| 50 | a core dump, you can send along a stack trace (see #6 if you don't know |
|---|
| 51 | how to do this). |
|---|
| 52 | |
|---|
| 53 | Bugs are patched as quickly as possible. Patches for bugs are emailed |
|---|
| 54 | to the pennmush@mellers1.psych.berkeley.edu mailing list (to subscribe, |
|---|
| 55 | email to listproc@mellers1.psych.berkeley.edu, and have the message say |
|---|
| 56 | "subscribe pennmush YourNameHere") and are put on the mellers1 ftp |
|---|
| 57 | site, in the /pub/DuneMUSH/Source directory. |
|---|
| 58 | |
|---|
| 59 | 3. How do I request a new feature? |
|---|
| 60 | |
|---|
| 61 | Email to dunemush@mellers1.psych.berkeley.edu |
|---|
| 62 | No promises, but I try to put things onto my to-do list and get to |
|---|
| 63 | them w/in the next revision or two. I'll email you back either way. :) |
|---|
| 64 | |
|---|
| 65 | 4. Where can I get more information about admin'ing and hacking MUSH? |
|---|
| 66 | |
|---|
| 67 | Read Javelin's God for PennMUSH Gods, loads of info about setting up |
|---|
| 68 | a MUSH, hacking source code, daily maintenance, and many tips from |
|---|
| 69 | other Gods! |
|---|
| 70 | |
|---|
| 71 | By WWW: http://mellers1.psych.berkeley.edu/~alansz/guide.html |
|---|
| 72 | By ftp: mellers1.psych.berkeley.edu, /pub/DuneMUSH/Guide |
|---|
| 73 | |
|---|
| 74 | 5. Where can I hear about new releases? |
|---|
| 75 | |
|---|
| 76 | New releases of the PennMUSH code are announced on the PennMUSH |
|---|
| 77 | mailing list (see above) and rec.games.mud.{tiny,admin,announce} |
|---|
| 78 | |
|---|
| 79 | Patches are only announced on the PennMUSH mailing list, and are put |
|---|
| 80 | on the ftp site. |
|---|
