  -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
  =                     Parlor House BBS for Linux                      = 
  =                             Version 3.0                             =
  =                       By Asu Pala and Loreen Lacy                   =
  =                            Copyright 1995                           =
  -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

The following is a summary of some of the included files for the BBS. 
Some of the files can be easily modified to your own preferences. 
However, do not change the files as noted below or the BBS will not find
them during its operation.  
-  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  - 
		Summary of directory structure and files

DATA: where the BBS searches for data relevant to its functions

Files which can be safely changed:
choice.info -	shows leave or stay options to new accounts
help.topics -	the numbers beside each topic shows the lowest level which can
		view that help topic.  If you wanted to limit access to 
		certain help topics, change the number to 1 number higher than 
		that level.
home.place -	this line of text shows on the line for BBS time that 
		shows every 15 minutes.
hosts.create.deny - where the results of /ban create commands reside
hosts.login.deny - where the results of /ban login commands reside
login.info -	shows to users after the intro screen and before they 
		type their name
login.screen -	shows to users after they type their password or finish the
		new account creation process
logout.screen -	shows to users after typing /quit
reserved.names - a list of names and user reservations. No other user can 
		 use the /n newname command for that name.
systemkick.scr - if systemkicks are enabled, this is the message and test
		 users would see if system kicked.
-  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  
EXTPROFILES: 	the directory where the extended profile files are 
		stored. 

Files which can be safely changed:
Files must have the .ext extention to be recognized by the BBS.  Any 
ascii file can be used.
-  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  
FONTS: the binary fonts for use in the Zoom command.

Files which can be safely changed:
none can be changed
-  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  
HELP: where the BBS looks for help files.

Files which can be safely changed:
Files must have the .help extention to be recognized by the BBS.  
If you add a file, for it to show on the BBS, you must also edit 
the DATA/help.topics file.  You must add the name of the file 
(without the .help extention) and the level of access.

Subdirectory LOCAL
Where the BBS looks for the rules.login to display to new accounts. This 
file can be changed to reflect whatever rules or guidelines you decide 
for your BBS.  Note: you may want to copy the file as a help file for your 
users to refer to later.  (see above).
-  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  
HINTS: where the BBS looks for the file with the hints that display 
during BBS operation.

Files which can be safely changed:
You can modify or recreate the hints.list file, but you must have a file
of 100 lines and each hint must be on one line.  The BBS will randomly
select a line to display.  If you want to increase the chances or
frequency of a line displaying, add it multiple times throughout the file. 
-  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  
LOGS: where the BBS stores the system logs

Files which can be safely changed:
bbslogs - you will have to routinely delete or archive this file or when
	  the /journal command is issued, the output will be outdated.
systemlogs - this file shows BBS status information during operation.
-  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  
MESSAGES: where the BBS searches for messages to display to users after 
	  login. 
Files which can be safely changed:
The files must have username.mesg format.
-  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  
TMP: the BBS uses this directory for writing temporary information

Files which can be safely changed:
none can be changed but the files can be deleted.  The BBS will recreate 
them as needed.
-  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  
USERS: where the BBS stores the datafiles for the new users.

Files which can be safely changed:
allusers - can change the order of usernames if new user# assignments are 
	   desired.
passwd - changes to this file have no effect on users, but you can check 
	 original passwords if needed.

If you have to delete a user manually - 
1. delete the line with their username in allusers
2. delete the line with their username in passwd
3. delete their binary file in userdata
-  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  
USERDATA: where the binary files for users are stored.

Files which can be safely changed:
none but you may want to make a backup of this directory in case these 
files are somehow corrupted or lost.

