.sp
version: [$Id: document.txt,v 5.123 1995/01/18 01:30:03 hitman Exp $]
.sp
[1][19-08-93 Menus]
Have a basic menu structure, yet it will print out very cryptic.
.sp
[2][20-08-93 Edit while you use it!]
I have programed in menus so you can edit parts of the program without
any trouble.  This is great for testing and debugging.
.sp
[3][20-08-93 I didn't want to do that!]
If you enter a character that is not a choice it finds it in the rest of
the text in menu file then executes the relative command.  I need to
make the search grep more specific.  This would fix up that error.
.sp
[4][20-08-93 Online Menu Editing.]
It is not very wise to edit the bbs.script program while it is running.
This may come up with some annoying results.
.sp
[5][23-08-93 Organization]
A bit of organization has taken place in organizing files.  All menus,
screens, and helps are in sub-directory off of the main.
.sp
[6][23-08-93 As result of...]
As a result of organization of the directory the menus got deeper and
deeper.  I am now going to implement a hidden quick command "go [menu
name]", this should speed things up for farmilar users.
.sp
[7][07-09-93 As result of the above...]
I need to give each menu a title, so I know what to call it on a 'go
menu', command.
.sp
[8][15-10-93 Needs some looks.]
Adding a function to display notes and messages to the users.  Plus a function to have nicer menu titles.
.sp
[9][31-10-93 What menu am I on?]
Added a header display for menus.  It displays little header file for the user
to tell what menu they are on.  Since these are cats they can be color with ANSI.
.sp
[10][31-10-93 More than one?]
Need to add a check to prevent more than one running of the shell per session.
I will have the bbs.script look for a variable in the environment and if found it 
returns "type exit to return to BBS".  This should fix any of that.
.sp
[11][31-10-93 No mail]
I deleted my mail serves on my machine so I need to reinstall this to clean things
up.  I will reinstall the whole system after I get my 105meg drive back from 
Seagate.  Until then look for online games...
.sp
[12][31-10-93 Patched Mail]
I really like Linux, in 10 minutes I was able to patch the mail back onto the 
system with a sysinstall.  We are back in business.  All I need to do is spread
the word.
.sp
[13][31-10-93 Send Mail Option]
Added a send mail option to the menu file.  The menu file line will look like:
S:#:title:options user
This is used for sending mail for predefined users or groups.  This is good for
corispondence to the SysAdmin.
.sp
[14][31-10-93 Add some color!]
Black and White is okay but I need to add color.  This will have to be done for 
now through ANSI.
.sp
[15][31-10-93 For looks!]
For looks and easy reading, I am going to start to use troff for the documentations
since I will not be the only person ever looking at them.  The troff will help
in the formating and making documents more portable.
.sp
[16][31-10-93 Specifications]
Starting specification files, the menu file format will be defined first.
.sp
[17][2-11-93 Headings or more]
Headings can be only used at the start of a menu for now.  I need to work 
in some type of menu format.  I don't mind the archaic menus but some users 
may get confused or even distracted.  But this doesn't matter for now.
.sp
[18][2-11-93 Ready to go online]
This system is about to go online.  The next release version will have all
the file transfer things installed.  For right now it will just have the
suggestion boxes all over.
.sp
[19][2-11-93 Missing Option]
Be careful with menus that you don't leave any blank space in them.  The 
blank gets read as an option.  Of course it is a null option, it just looks
bad.
.sp
[20][3-11-93 Added a few]
Added a news reader and a few other function to the bbs, advertisements
go out today...
.sp
[21][4-11-93 Added some Color]
Added a little ANSI color to the bbs.  Mainly little suddle things.  These make
things look a little better.  A little question, will the ANSI colors make this 
bbs un-portable to other versions of unix?  I do remember that ESIX could run
ANSI and so could the RS/6000 AIX 3.2.  These other system could run it but
they were very sensitive.  All screens had to reset after a ANSI run.
.sp
[22][6-11-93 Fixes]
Had to go into menus and remove the spaces in the subject lines for replies to 
the SysAdmin. It seem that the spaces will cause messages not to go through.
I also need to put in a questionnaire function.  This would allow me to set up 
surveys, and sign ups for the bbs.
.sp
[23][6-11-93 Bugs...]
Major bug in the mail sender.  Need to use an underscore as a space in the 
subject line of auto senders to SysAdmin.
.sp
[24][6-11-93 Added more color]
Well since no one calls the board I have better make it look good.  Adding
headers to make things look nice.  The go function works great if you know a 
menu name, I should put key words available for users or a function to view
the names of menus to go to.  That should be in the next release.
.sp
[25][7-11-93 Users New Accounts]
Making mention for the users to get a real account with their own name and 
personal mail etc...  Maybe someone will read and follow directions.
.sp
[26][13-11-93 Is this a set user prog?]
I need to keep in mind that this program can become or be a setuid.  So I am going
to make a fake-login called bbs that will own these files.  It will automaticly use
the bbs.script program for its shell.
.sp
[27][13-11-93 Setup Note]
This bbs has a fake login called bbs.  The following attribute apply to this
account:
.sp
Login:		bbs
.sp
.ti 5
o	This is pretty generic.  If each user wants their own personal account
and access to the bbs they can link the bbs to their root.  
ex. ln -sd /usr/local/bbs ~/.bbs
Then at the prompt the just need to type 'bbs' and the program 
/usr/bin/bbs will take care of the rest.
.sp
Passwd:		<anything>
.sp
.ti 5
o	This is dependent on the security for your system.  Some private boards
have separate account for public and private boards.  Later I will 
install a security checker that only displays what the user has permission
to see.
.sp
Shell:		/usr/local/bbs/bbs.script
.sp
.ti 5
o	This program is not real specific where the main parts of the program
are located but everything below ./bbs must be in the specified 
directories.  This is all hard coded into the programs for speed and 
ease of upgrading.
.sp
Home:		/home/BBSuser
.sp
.ti 5
o	This is based on where your personal bbs is.  You must at least look
at the configuration file and specify the directory used.
.sp
Comment:	Public BBS Account
.sp
.ti 5
o	This doesn't matter but will be shown to the user in the bbs prompt.
.sp
The set up of this fake-login prevents a lot of trouble with pirate and inquisit
users making this board indirectly trouble.
.sp
[28][13-11-93 File list?]
Yes, I have included a file list that will help me keep track of where all the 
files are.  This will be good for distribution.
.sp
[29][14-11-93 Bugs]
I am having trouble cat'ing out a file from within my script.  It has a very
direct filename, it must just be late.  I am not sure. I will try again to fix
it.  This bug is in the welcome display for the bbs.
.sp
[30][14-11-93 Bug Fix]
I fixed it, I fixed it...Now I can go to sleep.  I now know that the file wouldn't
cat because the name sent to it was ad.12\b.screen which looks like ad.1.screen
due to the backspace.  I am now reading the number as a character and only
displaying column one.
.sp
[31][14-11-93 Adding some variety!]
For the amount of time it takes to transmit text across a modem, I can have my
bbs picking random or pseudo-random header screens for individual file menus.
This will make the different menus different most of the time.  If the users
see's a new screen every so often they may like it better than the same old
thing.
.sp
[32][15-11-93 Bugs...Fixes]
If the SysAdmin uses the passwd -S user for extra user information this program
comes up with a bunch of information for the user-name.  I need to go in and make
this very specific.  Also the main menu clears out the intro message and new mail
intro.
.sp
[33][15-11-93 Hum...]
Users if they wish can write their own personal menus if they read this document
they will find this out.  Of Course I am not going to tell them how, they would
have to have specific menu definition.  I will leave this to a later release.
Another note about menus the go:menu option will go to any available menu in
the bbs.menu directory, so I could have special menus for "hidden" jobs, or
is this a good Idea.  Users could get in and do bad things.
.sp
[34][15-11-93 In regards]
In regards to the above comments, I need to put some kind of menu permissions
on the menus.  This would prevent dweebs from reading normal users menus.
.sp
[35][26-11-93 Upload Functions]
Set up a few upload functions so I can get a report from one of my classmates.
If you use a Header menu option you can put subtitles in the menus.  This is
not a 100% proven fact but it works for now.
.sp
[36]27-11-93 Users]
Trying to be more user friendly.  The users are the one that will be using 
this (duuu) I should get a few games for them.  Menus need to be organized
and cleaned up.  No more than ten entries per menu.
.sp
[37][28-11-93 Applic to Appli]
I need to change the name Applic to Appli, I may need to set a limitation on
the length of header names.  The extension must be complete for the display
of headers.
.sp
[38][30-11-93 Get public release?]
Some users say I should get a public release of a bbs program, one that
everyone is farmilar with.  Hey all this is a menu system so users can
buffer their way to unix, a real operating system.  I will work out the
bugs, what do you expect this is written in a script language (for DOS
users that batch language! for unix...)
.sp
[39][30-11-93 Development changed]
Development will go a little faster now that I have a DOS based terminal 
to test the down-load and DOS interfaces.  This will allow me to simulate
the effects the items have on DOS users.
.sp
[40][30-11-93 Error: List]
The list command needs fixed up.  Lists out /home/BBS/bbs for users of 
bbs account.  Need to fix this.  Add a pause at the end to keep from 
scrolling off the screen.
.sp
[41][30-11-93 Fixed list]
Fixed the list problem.  It seems someone with an incompatible modem is trying
to connect to my system.  I hope it is K.B., I will ask her tomorrow.  If that
is not the case I may need to write a program or use tout to hang up idle 
lines.  Someone did get knocked off and never reset the modem.
.sp
[42][4-12-93 Application Down-load]
Application down-load and up load sheets are giving a little trouble in the
upload process.  Also there is no exit out of the SIGN UP menu.  Lets fix 
both of these.  A instruction screen may be needed for the sign up menu.
.sp
[43][4-12-93 help file]
Updated the help file to be a little easier to understand, I might want to spell
check it because I don't spell to well.  I really enjoy having a DOS dial-in
emulation set up in my computer room.  I can test all the down-load things and
any thing else I notice at direct link 9600 baud or Telnet in at 38400 on 
another terminal to test structural things.
.sp
[44][3-1-94 Putting BBS program up for all]
I am putting the bbs program up for all to use with out a question.  Never
put numbers in any part of the menu file.
.sp
[45][5-1-94 Looks]
I have found some professional ansi that I am working into the random menu
headers.  I have of course leaving credits at the bottom of each screen,
saying leeched from: filename.  This at least lets the people get the
information from online again.
.sp
[46][8-1-94 Friendly as possible]
In the hopes to make this board as friendly as possible, I am makeing
everything colorful and simular to DOS based bbs systems.
Of course I will throw a few unix only things here and there because Unix
is so much better than DOS, it's got the power and the fame.
.sp
[47][9-1-94 Clean up mem.]
I changed the batch for running the bbs program.  Now all sysadmin needs to
do is link all users .profile scripts to /etc/skel and put the bbs script
within it.  This way only the bbs script is running for the login users.
Otherwise other users can just type bbs.
.sp
[48][12-1-94 User configurations]
Setup some user configurations so users can change their passwords and
things like that.  Also added a few new menus and cleaned some things up.
.sp
[49][19-1-94 A few changes needed]
A couple of menu clearifications are needed to prevent the old phantom
messages from confused users.  I also need to add the who command for those
multi-user systems.  At the end othe the help file I need to tell users to
hit return to continue, big menu pause causes some users to think things
are locked up.  A suggestion box also will be added.  This next release
will be jam packed with stuff.  I will also set up a lockout for baud rates
less than 2400 to keep users from having to sit throught luxurous Ansi's
and encourage faster modems.  This lockout will just put them in the normal
unix shell, all line oriented in the depths of unix!!
.sp
[50][19-1-94: Speed and optimization is the key]
I increased the speed of the help file by turning the groff into a ascii
file before the user ever sees it, at the installation.
.sp
[51][29-1-94: Added a lockout for lower speeds]
I am thinking of makeing the system more graphical, so I want to limit all
slow modem users [2400 and below] to shell accounts, while all other users
allow them to use the ansi and other graphics in my menus.  This is for the
better of the users.  Personally I would rather look at nice pictures than
the old character based, but if I am going to look at pictures I at least
want to look at the speed by.
.sp
[52][29-1-94: Cleaned unneed menus]
I removed the menus that are not being used.  Mainly old editor menus for
editing menus and documentation.  These dated back to version 5.5.5a and
that was a while ago.
.sp
[53][2-2-94: Optimization]
For the users name I am going to use a predefined enviroment variable to
save time and resourses.  The predefined variable is also more acurate then
the algorythm I had set up.
.sp
[54][2-2-94: Online Application]
I need a online appication service.  This would allow users to know their
login and password before I have the account set up.  This would increase
the user call back ratio.
.sp
[55][6-2-94: User Friendly]
I tried to make things a little more user friendly by includeing an editor
off of the mail sending, feedbacks etc..
.sp
[56][6-2-94: BUG: After help you send mail!]
After a user sends for help the mail editor jumps in, and when you abort
that you get logged out.
.sp
[57][6-2-94: FIX: Specific Searches are the best]
I revamped most of the searches and make them as specific as possible.
This will help on those accidental menu choices.  I feel the above bug is
fixed.
.sp
[58][8-2-94: Public system is for public]
Need to not allow the public access account to shell out unless they are
300, 1200 baud then put them in a shell.  Let them use slow modems they are
guests.
.sp
[59][20-02-94: Iron the shirts.]
When users shell to the users account they ended up in a directory they
could not write in.  Now that was fixed, I was just wondering, with all the
symbolic links to users directorys, isn't that taking up extra inodes and
things like that.  Yes it is, so I re-wrote the bbs launcher program to
bbs.sh, this program moves to the public copy of the BBS program.  This
allows users to just run and read from the files there.  Cuts down on links
to users directorys...
.sp
[60]-20-02-94: Get a faster modem!]
Some users don't like the 2400 and below lockout.  I might need to do a
monochrome interface for those people that don't like colors or that might
hang up on the sytem.
.sp
[61]20-02-94: BUG: Ctrl-C to shell]
When a user hits ctrl-c they get put in a unix shell account.  This needs
to be fixed to prevent a user that has no account access from getting out
of the program, some users can't handle that.
.sp
This may be fixed my editing the .profile to exec the launch program.
.sp
[62][24-02-94: BUG: Two Fours!]
There were two fours on the applications menu.  This has been fixed!
.sp
[63][24-02-94: FIX: Ctrl-C was fixed by exec!]
I needed to exec the to exit the system after someone breaks out of the
program.  I think this may interfere with the shell procedures.  I am not
sure.
.sp
[64][24-02-94: Need to keep very specific]
On trixie (SUN OS) had to edit the bbs.script program to borne shell.
.sp
[65]02-03-94: Patch: Produced and applied a patch to bbs/bbs.script, from the code
used on SunOS 4.1.3.  This code is strictly bourne shell, for
compatability.  It seems that the SunOS 4.1.3 doen't have the Korne Shell.
.sp
[66]02-03-94: Added the utility diff_dir.sh, it can tell the difference
between to remote directorys.  I don't know how helpful this will be on a
bbs but it is there.
.sp
[67]06-03-94: I started converting the script bbs to C, problem will be the
working with the enviormental variables.  I can still use most of the unix
command, but I think I will have to code parts to organize.
.sp
[68]06-03-94: I must move away from enviroment variables.  All seems to be
pretty go theroy wise.  I just need to do a bit more coding, then break
everything up into modular sections.
.sp
[69]07-03-94: Working on small sections at a time will bring my best
results, I have to convert sections and remove all the enviroment
variables.  I will have to leave most of that stuff up to the current path.
.sp
[70]07-03-94: After things get running I will break everything apart and
put it into a finite state machine.  But this will be later.  More
functions to clean things up.
.sp
[71]08-03-94: I have most of the basics up and running, now for the menu
interpretations and things like that.  I can only display one opening
screen that has been hard coded into the program.  I need to fix that.
.sp
[72]09-03-94: After programming most of this program in the standard
straight forward C/C++, I am really starting to like finite state
programming.  It is a lot easier to debug and test.  It also comiles
faster.  After I get this program working I will release it then convert it
to a finite machine.  That will speed up the program and make things run a
lot faster.
.sp
[73]13-03-94: I am working on a menu editor that will convert the text
based menu files to binary menufiles for the bbs to read.  This will make
the bbs menus a little faster and easier to get up on the screen.  I want
to be able to edit the menus with just about any editor but I don't want to
have to wait for days for a menu to come up on the screen.
.sp
[74]13-03-94: All header files will have to be shared between both of these
programs, the bbs and the menu editor.  This shouldn't be a problem, but it
will help with keeping the control consitent.
.sp
[75]17-05-94: Added a clean function in the makefile.  This will make
cleaning a little better, get rid of those object files.  I think if I take
the outpost23 program and tack this program on as a header we may have a
BBS system going.  O'Well.  At least a shell program.
.sp
[76]20-05-94: Sometimes slashes may have to be added when talking about
directories, this program may need to run on multiple operating systems.
Maybe later I can add in a statement that figures out the operating system
then sets up the slash accordingly.
.sp
[77]21-05-94: menu_edit: So far the program reads in the menu file and
interprets it.  After I get all the debug statements in, I can figure out
why the program doesn't write the binary output file.  I may not have put
in that code yet.
.sp
[78]21-05-94: menu_edit: I may have to do some changeing to the variable
that holds information about the menus.  I think that the menus may have to 
be limited to a certain number of lines to allow for scrolling.
.sp
[79]22-05-94: All menu files must have all five columns full.  If a column
is not going to be used you must put null in them.  Or a short comment of
some sort.  This is to prevent the menu reader from spitting binary garbage
on the screen.
.sp
[80]22-05-94: The menu reads and write work pretty good.  I still need to
initiailize each variable for the read and the write to keep out any extra
characters.  If I initilize with a \0 I should be able to keep things clean
when printed out.
.sp
[81]22-05-94: Initilizing the variables to the end of string character
keeps the variables clean and organized.
.sp
[82]23-05-94: read_menu_main.c, v1.6.1: Has an error causeing a
segmentation fault when returning from the function read_menu.  The
function read_menu works, becuase if you exit instead of returning, all
works out fine.  It is getting the variable back that is the problem.
.sp
[83]23-05-94: read_menu: Working on getting the data to pass back to the
main function.  I have had things work like this before, now it is just a
matter of coping the code.
.sp
[84]24-05-94: bbs_script: It compiles, runs, prints the intro, prints
header, prints the main menu, then sits there.  So far so good, just keep
adding to it and cleaning out the old script code.  This program is many
times faster than its script brother.
.sp
[85]25-05-94: bbs_script: So far so good, need to remember to recompile the
menu datafiles everytime I edit the menu text files.
.sp
[86]25-05-94: Baseline 3.0: I am going to cut a baseline and test from
there for a little while.  Hopefully things will work out pretty good and
the bugs will be few.
.sp
[87]26-05-94: Baseline 3.0, BUG: Mail functions don't work.  Runs throught
the header for the mail (feed back function, etc...), but most of it just
garbles up in a mess.
.sp
[88]26-05-94: Baseline 3.0, BUG: Menu seperators don't work correctly, the
signup menu comes up with:
.sp
.nf
(1)	Menu Option
(ASCIInull)     null
(2)	Another Menu Option
.sp
This can be fixed by reading their indexes as they get printed and act
accordingly.
.sp
[89]26-05-94: Baseline 3.0, BUG: Need more debuging with the spawning of
commands.  I need to know the error codes and act accordingly to them.
Some programs fail and the user doesn't really know what happened.
.sp
[90]26-05-94: Baseline 3.0, BUG:  Logouts from any menu do not work.  I
need to fix this by adding a logout index, or something of the such.
.sp
[91]26-05-94: Baseline 3.0, BUG:  A null user option just carrys a return
down the screen.  Maybe if it returned another prompt or something, it
would be more useful.
.sp
[92]26-05-94: Baseline 3.0, BUG:  Option 2 from the file menu spawns a
bunch of zombie processes and really hangs up the terminal.  This must be
fixed, if I will be programming over a modem, if things hangup I can't come
in on another port to fix it.
.sp
[93]31-05-94: Baseline 3.0, FIX:  Option 2 from the file menu has been
fixed.  I removed the jump option in the menu files and from the code.  I
also edited all the menus and menu_struct.txt to reflect this change.  If
you want to jump into a directory you must write a script to do change 
directory and jump.
.sp
[94]31-05-94: Baseline 3.0, FIX: Logout menu options have been fixed.  This
was done by adding a function X in the menu.  If the menu uses the function
X then the program exits.  The menu_spec.txt has been updated.
.sp
[95]11-06-94: I am real proud of this program, after these minor bugs in
Baseline 3.5, I will cut to a new baseline and send this out for general
use.
.sp
[96]11-06-94: Baseline 3.5, FIX: The mail function has been fixed and works
properly for the feed back menus and other things like that.  I should be
about ready for a release soon!  I need to fill out all the paper work and 
come up with an announcement.
.sp
[97]11-06-94: Baseline 3.5, FIX: The menu seperator in the sign menu has
been fixed.  The menus when edited must leave the reference column open to
get the headers within the menu to print right.
.sp
[98]11-06-94: Things are looking really nice, I need to clean things up and
get ready for another public release.  In the real world a few things will
have to be added for bug control.  I will only release this program at
first to the members of BBS development groups.  This way they can do a
quick rip over and see what is going on.  Then I will as the user able
options for bugging and user levels.
.sp
[99]02-07-94: Baseline 5.6: Cut a new baseline working on some HP porting
and things look pretty good.
.sp
[100]19-07-94: HP_UX:
The menu data files MUST be recreated for the HP system or the menus will
not work.  The HP 750 has a differenct integer size than a Linux and Alpha
machine, this causes a little trouble so rebuild the menus.
.sp
[101]20-07-94: SunOS:
Save yourself a lot of trouble and find a ANSI C compiler before trying to
install this program.  The K&R compilers die and die quick.
.sp
[102]23-07-94: Baseline 5.12: Cut a new baseline added the HP_UX and SunOS
ports.  Things have cleaned up a bit and a new release will be soon.
.sp
[103]23-07-94: In the makefile you must use the full pathname from root for
the DIR variable.  If you fail to do so you will not get a clean install.
.sp
[104]23-07-94: The HP_UX and SunOS ports when pretty good, I just need to
make sure all code stays ANSI C.  This makes thing so much easier.
.sp
[105]25-07-94: Had an error in the src/ver file but I fixed it.  That is
all I need, to screw up the version control.  Where is a good CM person
when you need them!
.sp
[106]26-07-94: Baseline 5.12: FIX: Added a ''make all'' to grap all binaries
and make them up.
.sp
[107]28-07-94: BASELINE 5.22: More fixes from b5.12 added and everything
looks pretty good.  Starting testing only, no new anything.  this next
baseline will get tested on Alpha...
.sp
.in 4
Linux - aprox b5.20
.br
Dec Alpha - aprox. b5.30
.br
HP HP-UX - aprox. b5.40
.br
Sun SunOS - aprox. b5.50
.br
Public Release - aprox b6.0
.in 0
.sp
[108]19-08-94: Many hours of testing and many fixes and fine tunings, I am
working more on the installation and configuration for the new sysadmin.  I
would like to make this project very easy to install.
.sp
[109]19-08-94: I moved the all system specific configurations to a file
called src/sys_config.  This way everything is in one realitive position.
This file is then inturn included in each Makefile.
.sp
[110]19-08-94:
The __DATE__ doesn't exist in the standard ULTRIX compiler, and the
code parser is very specific to the format of the code.
.sp
[111]19-08-94:
The compiler here seems to be a little before ANSI standards, and may need
or cause a few changes, but the changes seem to be still within the
standards, just not including any short cuts.
.sp
[112]06-09-94: fixed one of the items in the TODO list.  The getlogin
function now assigns its value to a pointer and the pointer is accessed for
the information istead of recalling the function every time the prompt
comes up.
.sp
[113]14-09-94: After this next baseline I will convert this program to a
finite state type.  This will speed up things and make the program easier
to update.
.sp
[114]14-09-94: BASELINE 5.34: Now for the finite state.
.sp
[115]20-09-94: I need to merge the other version of this program together
and get a baseline 5.xx then fix bugs and move to version 6.0.  After this 
everything will be all finite state.
.sp
[116]23-09-94: Baseline 5.41: Clean up the final changes and work off all
the bugs before the 6.0 version.
.sp
[117]01-10-94: Baseline 5.22.10: Added in the MSDOS port.  Next add in the
ultrix port.
.sp
[118]20-09-94: Set up a script that will reset the terminal to its original
state after running the BBS program.  This will make sure things are left
the way I found them.
.sp
[119]20-09-94: I would like to implement:  If the users speed is locked out
exit and display the lockout.txt file.  This would allow systems to
specialize there lockout to be pretty ansi etc...
.sp
If the username is ''bbs'' then just hang up on them, those speeds are just
not worth the effort.  They should get shell accounts below 2400 baud.
.sp
Make sure the logout screen is NOT to long, it takes time to print that
stuff out and at less than 2400 it is annoying.
.sp
[120]01-10-94: Baseline 5.22.20:  I need to work on the makefile, It seems to
have a few problems.  This running two or three jobs at a time is causeing
trouble, for the make all.
.sp
[121]27-10-94: In the install_database, you must list directorys in the
order they will be seen from root.  For example: src/ will come before
src/another_directory/.
.sp
[122]07-11-94: Baseline 5.80: Added many enhancements from the Linux port.
The install works a lot better.  Still working in the Finite state stuff.
.sp
[123]09-11-94: Baseline 5.74-hpux: Removed many control characters.
.sp
[124]09-11-94: Baseline 5.74-hpux: Cleaned up the make for the finite sections
of the code.  This still needs some work, but the depends and all go
better.
.sp
[125]10-11-94: The HP systems don't like the traping I do in the 'bbs.sh'.  I set up
a conditional to make this not work.  SunOS seems to not care and this work fine.
.sp
[126]10-11-94: Baseline 5.83.1.6: menu_edit: Finally added the magic spining cursor!!
.sp
[127]10-11-94: UnOfficial Baseline 6.x: X/Motif Version: Major security error, that allow users to pop up there very own xwindow with a shell.  This may not be a problem for private
users, but for public users, this is a major security problem.  At least I don't setuid my programs.
.sp
.sp
[128]21-11-94: Baseline 5.88.2.0: The MSDOS port is pretty much the same as the
rest of the program, except the multi-users support.  This ends up being a
regular little menu system.  Maybe one day I can throw a little Novell support
in it, but until then...
.sp
[129]14-12-94: UnOfficial Baseline 5.83.1.16.1.3: Added a few shell programs to help with administration, and things like that.  This program really works real well, I haven't seen any problems lately and no bug reports.  Is this good or bad.
.sp
[130]14-12-94: UnOfficial Baseline 5.83.1.16.1.8: menu_edit: cleaned up the code and remoded the use.  This now will handle multiple files on the command line and a quiet option.  The quiet option makes the version information not print.
.sp
[131]26-12-94: UnOfficial Baseline 5.93: working on getting everything into
the finite state, so far many items have been merged and getting ready to
base line.  everything compiles, and now it runs, a few debugging and
testing versions will put this on the market.
.sp
[132]01-01-95: This works really good now, I just need to do few more fixes
under testing and get things a bit smoother.
.sp
[133]03-01-95: Baseline 5.115: Fixed up the Makefile so on installs the
installed README's get transfered to the new install directory.
.sp
[]06-01-95: Baseline 5.120.1.5: HP Testing and Developing, my home system's keyboard has a messed up 'm' key and it is really annoying me.  I moved all the source from src/bbs_fn-src to src/, I wanted to simpilfy the make and the compile.  This shouldn't make any difference in anything.
.sp
[]06-01-95: Baseline 5.120.1.10: More testing and more working, removed all headers from source that were not needed.  This program should run very smooth on any platform, as long as it supports ANSI C.
.sp
[]06-01-95: Baseline 5.120.1.12: Fixed the error with the program menu options telling you have an invalid command, after you have just executed it.
.sp
[]10-01-95: Baseline 5.120.1.15: Fixed up a few error messages, and added a suppport address for contacting the system administrator or who ever runs that bbs system.
.sp
[]12-01-95: Baseline 5.120.1.17: Produced a Configure program that replaces the sys_config file, and creates everything for you.
.sp
[]17-01-95: Baseline 5.120.1.31: The Following has happened:
.sp
Unoffical Baseline 1.31: Added the ChangedLog file to keep track of the baseline changes for me.
.br
Unoffical Baseline 1.29: SunOS compile, things work very good, but I need to get a newer ANSI C compiler on the Sun's
.br
Unoffical Baseline 1.27: Indented all code to make things standard across the board.
.br
Unoffical Baseline 1.24: New Install Program in the Makefile
.br
Unoffical Baseline 1.20: New Configure script that sets up sys_config
.br
Unoffical Baseline 1.17: Moved most of the global variables in main to local static variables.
.br
Unoffical Baseline 1.15: Fixed problem with the error messages, and added a support address.
.br
Unoffical Baseline 1.12: Fixed problem with the programs after they run a program menu option
.br
Unoffical Baseline 1.10: Hp testing and Development
.br
Unoffical Baseline 1.6: Hp testing and Development
.sp
