- Fix bug under SunOS, in check_speed.c the line speed checking causes a segmetation fault and really messes up the program, this can be fixed with more line speed checking or another method of doing this, I need to look at some real code.

- Move the msdos directory to the src/config/ tree, I don;t like to look at it.

- Initialize all pointers and strings.

- For each user that logs in, set up a tmp file that keeps track of this
information.  Write the users loginname, and info, in a file.  When the 
users does a ''who'' within the BBS program this will tell them.
	This information can be written to .plan in the home directory of bbs, 
	then when someone fingers the BBS they get a list of all bbs users online
	and some other information.  Editing the /etc/utmp would be best, because
if you finger bbs you will get an instance for each bbs user.

- 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. (this will
probably be done after the anonymous logins are set up and enabled)

- 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. (this will probably be done after the
program becomes a finite state program.)

- Add compressed menu text files, headers, and screens. (is this really
necessary, things are really small already)

- Get the users information from /etc/utmp, and check the terminal speed
through the actual device and connect rate, instead of "stty speed" (this
is a lot more portable for a Unix system, not all ''stty'' programs have
the 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 filter that grabs the user names from the bbs
	config file and sorts the mail messages accordingly.  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.

- 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.

##
# 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 dropped 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.
