##
# Mips 5.01
- BUG - schaefer@alphanet.ch - Segmentation fault on is_bbs_running.c, this 
happens for the same reason it happens under OSF1.  I need to figure out a 
way to fix it though, if the variable BBS is predefined BEFORE the program 
is executed there will not be a problem.  Maybe checking for a NULL.

- BUG - schaefer@alphanet.ch - Program hangs and prints \377, after the 
first header display and before the first menu display.  Need to find a 
Mips machine for testing.

##
# Other
- Initialize all pointers and strings.

- Add user security levels.  Limit certain menu items, don't even display
them on the screen if the user has no rights to see them.

- Add anonymous logins, if user = bbs prompt for a user name, check the
password file for the bbs system then check the password file for the host
system, before letting the user on.

- Add compressed menu text files, headers, and screens.

- Get the users information from /etc/utmp, and check the terminal speed
through the actual device and connect rate, instead of "stty speed"

- Add mail access via /usr/lib/smail/forcepaths. . .

	.bbs						bbs
	.bbs.fhilx2.outpost23.org	bbs

Then the bbs user gets the mail and parses it into
$BBS_home/usr/spool/mail/$USER_name.

	problems: writing a mail fhilter that grabs the usernames from the bbs
	config file and sorts the mail messages accoringly.  This program will
	have to be able to handle a John.Doe type format.

- Security problem: search for '`' shells before executing an inquiry
otherwise people can get some nasty shells.

- Get users name only once then pass the argument around, instead of
calling the getlogin() function, this would be a bit faster.  I will
probally do this after I get anonymous users.

- Add the command line option 'bbs -V' to get the current version.  This
would help in the set up of a auto bug reporter.

- Set up PATH variable so when a user manages to shell out they have a
path.

- Fix the make depends on the program, it is a little annoying.

- Menu_edit: allow listing and compiling multiple files on the command
line, and allow for a ''menu_edit -V'' to get the version.

- Menu_edit: change the running dots to something else, it is a little
crapy, maybe a spinning line.

##
# Makefile
- Look into methods of changing one thing in the Makefile to switch between
machine types (especially the development machines).  Some work has been 
done on this with the sys_config file.

- Add a better baseliner for cutting a baseline of code (TOOL)

 	co -l RCS/*,v ; ci -f$(BASELINE) -m"Baseline $(BASELINE): My Truck" RCS/*,v

 	the above works pretty good, but I just need to implement it.


##
# file areas - CDrom support
- Set up tools for installing cdroms and using the items as a file area and
downloads.  This can be set up in a menu module, write up program and all
to add to a menu.  Then menu gets droped into the $BBS_home/menu, and then
compiled with the menu_edit.  Subdirectorys off of $BBS_home/menu/$MOD_name 
will contain any executables for the module, it will get config info out of
a configuration file. (fa-walk.sh)

- Set up configuration tables for the download protocols.
