-Last update 21-Jan-2002
+Last update 16-Feb-2002
Unix Distributions.
@@ -25,12 +25,7 @@ disadvantages for bbs use. Which distribution to pick is very personal.
Since late 2001 a port to FreeBSD is available, from version 0.33.19 this
port is ready to use.
Since januari 2002 a port to NetBSD is available, this version is not ready for
-use.
-You should also consider the fact if the bbs machine is the same machine on
-which you do your daily work on or if you use a seperate system for the bbs.
-I will describe the distributions below for use on dedicated bbs computers,
-that means you don't do daily work on them and don't use them to play games.
-Most important is that this is my personal view.
+use.
Slackware
@@ -67,8 +62,7 @@ How to build an optimized Debian system is not tested by me.
FreeBSD
-I test on a FreeBSD 3.2 stable release. Newer releases will not run on the
-hardware I have available. (Don't ask me why, they crash during install).
+I test on FreeBSD 3.2 and 4.4 stable releases.
The setup is quite simple, do a small setup (average user), and add some needed packages
from the ports collection such as gcc, mgetty, infozip etc. The test machine
has a 500 MB harddisk, about 250 MB is still free. Note that the older
diff --git a/html/gwnews.html b/html/gwnews.html
index 4bde57e5..ec51bc8c 100755
--- a/html/gwnews.html
+++ b/html/gwnews.html
@@ -1,4 +1,5 @@
+
diff --git a/html/invoking.html b/html/invoking.html
index 2c74479c..ab825996 100644
--- a/html/invoking.html
+++ b/html/invoking.html
@@ -1,4 +1,5 @@
+
@@ -34,16 +35,19 @@ Login as user mbse and check the logfiles if everything looks
good. If something is wrong, reread the previous documentation and check if
you did everything right.
-Next logon to your BBS locally using the account "bbs". You will then create
-the first user of your BBS, this will be you, the sysop of course.
+Next logon to your BBS locally using the account "bbs".
+You can do that by typing su - bbs or if you already have installed
+mblogin as login replacement for telnet, then type telnet
+localhost.
+You will then create the first user of your BBS, this will be you, the sysop of course.
After you logout the BBS start as user
mbse the program mbsetup and edit your user record
to set your level to that of the sysop. One more thing, the unix account you
must create when you logon as new BBS user may not be mbse
as this is the normal Admin account the BBS and its utilities use.
-Now login with your unix account and see if everything still works. After all
-this and if you have setup mgetty you may want to test if
+Now login with your unix account and see if everything still works.
+If you have setup mgetty you may want to test if
users really can login with a modem. Also check a mailer session, can you
dialout, ie. poll other nodes and can they call you. There is a lot that can
go wrong with unix permissions if you are not precise in wat you are doing.
@@ -51,10 +55,9 @@ go wrong with unix permissions if you are not precise in wat you are doing.
If everything is working it is time to create poll events, and adjust other
scripts to your local needs to get your BBS full up and running.
-To do this you must install a crontab for user mbse As user
-mbse go to the directory ~/mbsebbs-0.33.xx.
-In that directory type
-sh ./CRON.sh and a default crontab will be installed.
+To do this you must install a crontab for user mbse.
+As user mbse go to the directory ~/mbsebbs-0.33.xx.
+In that directory type sh ./CRON.sh and a default crontab will be installed.
To add poll events, edit the crontab with the command crontab -e
At the bottom of that file there is an example of how to do that.
@@ -63,7 +66,7 @@ dialout, scanning and tossing mail etc. In other words, the bbs is up and
running.
-
Go Back
+Go Back
diff --git a/html/mgetty.html b/html/mgetty.html
index d37a103e..11116f0b 100644
--- a/html/mgetty.html
+++ b/html/mgetty.html
@@ -1,4 +1,5 @@
+
-Last update 21-Jan-2002
+Last update 16-Feb-2002
MBSE BBS Setup - Mail Setup -> Mail Areas.
@@ -40,29 +40,27 @@ change netmail reply board and delete message area.
Area Name The description of the area.
Area Tag The echomail area tag.
+Group The name of the echomail group.
Newsgroup The newsgroup name if you are gating this area.
-Moderator Leave this blank for now!
JAM base The path and name of the JAM message base without extension.
Origin The origin line to add to echomail messages.
Fido Aka The Fidonet aka for this area.
QWK name The name of the area for OffLine Readers.
-Group The name of the echomail group.
Distrib. Leave this blank for now!
Area Type Local, Netmail, Echomail or News.
Msg Kinds Private/Public, Private, Public, Read Only, FTN moderated, Usenet Moderated
FTN chars FTN characterset, not in use yet, defaults to IBMPC 2
RFC chars RFC characterset, not in use yet, defaults tp LATIN-1 2
+Active If this area is active.
Days Old The maximum age of the messages before purging.
Max. Msgs The maximum messages in this area.
Articles The maximum news headers to fetch.
Netreply Netmail reply area if this is echomail.
-Active If this area is active.
-User Del. Users may delete their own messages.
Read Sec. The security level to read messages.
Write Sec. The security level to write messages.
Sysop Sec. The security level to do sysop actions.
+User Del. Users may delete their own messages.
Aliases Allow the use of an Alias.
-Random org Create random origin lines (Oneliner database).
Quotes Add a random quote under new messages (Oneliner database).
Mandatory If this area is mandatory for downlinks.
UnSecure Don't check link address during toss (Dangerous!).
@@ -124,38 +122,8 @@ harm is done. The file mbsetup.log shows all affected areas.
Automatic area creation.
-If you want to use the automatic area creation you have to define a fictitious
-area tagged 'DEFAULT' with the options you want for new areas like this:
-
- 1. Area Name Area autocreada:
- 2. FTN area DEFAULT
- 3. Newsgroup
- 4. Moderator
- 5. JAM base /var/spool/mbse/mail/
- 6. Origin Parolas BBX. Por fin.
- 7. Fido Aka 0:0/0@ 22. Sysop Sec. 100
- 8. QWK name 15. Days Old 40 23. Aliases No
- 9. Group AUTOCREADAS 16. Max. Msgs 1000 24. Quotes No
- 10. Distrib. 17. Netreply 0 25. Mandatory No
- 11. Area Type Echomail 18. Active Yes 26. UnSecure No
- 12. Msg Kinds Public 19. User Del. Yes 27. OLR Default No
- 13. FTN chars IBMPC 2 20. Read Sec. 5 28. OLR Forced No
- 14. RFC chars LATIN-1 2 21. Write Sec. 5 29. Connections
-
-The FTN area's Tag must be 'DEFAULT' exactly. Connections will be left blank. Fill
-the remaining options with your defaults for the new areas.
-If Fido AKA has not been filled in, the best fitting AKA according to the origin of
-the message will be used from the configuration.
-
-Areas will be created as is laid out in this template, the tag of a new area
-will be added to the name and base path, the new tag will be placed in the tag
-and qwk name (truncating it if needed).
-Only the node from which the new area is received will be added in connections.
-
-You will need to change the setup, menu 18, item 2, to change the command
-'mbfido tic toss'. Add the -a parameter if you want the automatic
-creation of areas to work when importing received mail.
-So the commandline would be like /opt/mbse/bin/mbfido tic toss web -a -quiet.
+If you want to use the automatic area creation you have to define this in the
+message area groups. This has been changed since MBSE BBS version 0.33.19.
Back to Mail Setup
diff --git a/html/setup/emgroup.html b/html/setup/emgroup.html
index e405d77a..3f94d2f8 100644
--- a/html/setup/emgroup.html
+++ b/html/setup/emgroup.html
@@ -1,4 +1,5 @@
+
diff --git a/html/ups.html b/html/ups.html
index 9e0b1157..caaa4fe9 100644
--- a/html/ups.html
+++ b/html/ups.html
@@ -1,4 +1,5 @@
+