bbs/deb-mbse
Archived
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Updated documentation

Browse Source
This commit is contained in:
Michiel Broek 2002-02-16 21:44:25 +00:00
parent 0aa608b565
commit 8bf1750cd9
9 changed files with 27 additions and 56 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
html/dist.html
View File

@ -12,7 +12,7 @@
</HEAD> </HEAD>
<BODY> <BODY>
<BLOCKQUOTE> <BLOCKQUOTE>
<h5>Last update 21-Jan-2002</h5> <h5>Last update 16-Feb-2002</h5>
<P>&nbsp;<P> <P>&nbsp;<P>
<H1>Unix Distributions.</H1> <H1>Unix Distributions.</H1>
@ -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 Since late 2001 a port to FreeBSD is available, from version 0.33.19 this
port is ready to use. port is ready to use.
Since januari 2002 a port to NetBSD is available, this version is not ready for Since januari 2002 a port to NetBSD is available, this version is not ready for
use.<br> 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.
<P>&nbsp;<P> <P>&nbsp;<P>
<H3>Slackware</H3> <H3>Slackware</H3>
@ -67,8 +62,7 @@ How to build an optimized Debian system is not tested by me.
<H3>FreeBSD</H3> <H3>FreeBSD</H3>
<P> <P>
I test on a FreeBSD 3.2 stable release. Newer releases will not run on the I test on FreeBSD 3.2 and 4.4 stable releases.
hardware I have available. (Don't ask me why, they crash during install).
The setup is quite simple, do a small setup (average user), and add some needed packages 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 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 has a 500 MB harddisk, about 250 MB is still free. Note that the older

1
html/gwnews.html
View File

@ -1,4 +1,5 @@
<HTML> <HTML>
<!-- $Id$ -->
<HEAD> <HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1"> <META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
<META http-equiv="Content-Style-Type" content="text/css"> <META http-equiv="Content-Style-Type" content="text/css">

21
html/invoking.html
View File

@ -1,4 +1,5 @@
<HTML> <HTML>
<!-- $Id$ -->
<HEAD> <HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1"> <META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
<META http-equiv="Content-Style-Type" content="text/css"> <META http-equiv="Content-Style-Type" content="text/css">
@ -34,16 +35,19 @@ Login as user <strong>mbse</strong> and check the logfiles if everything looks
good. If something is wrong, reread the previous documentation and check if good. If something is wrong, reread the previous documentation and check if
you did everything right.<p> you did everything right.<p>
Next logon to your BBS locally using the account "bbs". You will then create Next logon to your BBS locally using the account "bbs".
the first user of your BBS, this will be you, the sysop of course. You can do that by typing <b>su - bbs</b> or if you already have installed
<b>mblogin</b> as login replacement for telnet, then type <b>telnet
localhost</b>.
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 <strong> After you logout the BBS start as user <strong>
mbse</strong> the program <strong>mbsetup</strong> and edit your user record mbse</strong> the program <strong>mbsetup</strong> and edit your user record
to set your level to that of the sysop. One more thing, the unix account you 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 <strong>mbse</strong> must create when you logon as new BBS user may not be <strong>mbse</strong>
as this is the normal Admin account the BBS and its utilities use.<p> as this is the normal Admin account the BBS and its utilities use.<p>
Now login with your unix account and see if everything still works. After all Now login with your unix account and see if everything still works.
this and if you have setup <strong>mgetty</strong> you may want to test if If you have setup <strong>mgetty</strong> you may want to test if
users really can login with a modem. Also check a mailer session, can you 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 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.<P> go wrong with unix permissions if you are not precise in wat you are doing.<P>
@ -51,10 +55,9 @@ go wrong with unix permissions if you are not precise in wat you are doing.<P>
If everything is working it is time to create poll events, and adjust other 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.<P> scripts to your local needs to get your BBS full up and running.<P>
To do this you must install a crontab for user <strong>mbse</strong> As user To do this you must install a crontab for user <strong>mbse</strong>.
<strong>mbse</strong> go to the directory <strong>~/mbsebbs-0.33.xx</strong>. As user <strong>mbse</strong> go to the directory <strong>~/mbsebbs-0.33.xx</strong>.
In that directory type In that directory type <strong>sh ./CRON.sh</strong> and a default crontab will be installed.<p>
<strong>sh ./CRON.sh</strong> and a default crontab will be installed.<p>
To add poll events, edit the crontab with the command <strong>crontab -e To add poll events, edit the crontab with the command <strong>crontab -e
</strong> At the bottom of that file there is an example of how to do that. </strong> 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. running.
<p> <p>
<A HREF="index.htm"><IMG SRC="images/b_arrow.gif" ALT="Back" Border="0" width="33" height="35"> Go Back</A> <A HREF="index.htm"><IMG SRC="images/b_arrow.gif" ALT="Back" Border="0">Go Back</A>
</BLOCKQUOTE> </BLOCKQUOTE>
</BODY> </BODY>
</HTML> </HTML>

1
html/mgetty.html
View File

@ -1,4 +1,5 @@
<HTML> <HTML>
<!-- $Id$ -->
<HEAD> <HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1"> <META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
<META http-equiv="Content-Style-Type" content="text/css"> <META http-equiv="Content-Style-Type" content="text/css">

1
html/postfix.html
View File

@ -1,4 +1,5 @@
<HTML> <HTML>
<!-- $Id$ -->
<HEAD> <HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1"> <META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
<META http-equiv="Content-Style-Type" content="text/css"> <META http-equiv="Content-Style-Type" content="text/css">

1
html/routing.html
View File

@ -1,4 +1,5 @@
<HTML> <HTML>
<!-- $Id$ -->
<HEAD> <HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1"> <META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
<META http-equiv="Content-Style-Type" content="text/css"> <META http-equiv="Content-Style-Type" content="text/css">

44
html/setup/emareas.html
View File

@ -12,7 +12,7 @@
</HEAD> </HEAD>
<BODY> <BODY>
<BLOCKQUOTE> <BLOCKQUOTE>
<h5>Last update 21-Jan-2002</h5> <h5>Last update 16-Feb-2002</h5>
<P>&nbsp;<P> <P>&nbsp;<P>
<H1>MBSE BBS Setup - Mail Setup -> Mail Areas.</H1> <H1>MBSE BBS Setup - Mail Setup -> Mail Areas.</H1>
@ -40,29 +40,27 @@ change netmail reply board and delete message area.
<pre> <pre>
<strong>Area Name </strong>The description of the area. <strong>Area Name </strong>The description of the area.
<strong>Area Tag </strong>The echomail area tag. <strong>Area Tag </strong>The echomail area tag.
<strong>Group </strong>The name of the echomail group.
<strong>Newsgroup </strong>The newsgroup name if you are gating this area. <strong>Newsgroup </strong>The newsgroup name if you are gating this area.
<strong>Moderator </strong>Leave this blank for now!
<strong>JAM base </strong>The path and name of the JAM message base without extension. <strong>JAM base </strong>The path and name of the JAM message base without extension.
<strong>Origin </strong>The origin line to add to echomail messages. <strong>Origin </strong>The origin line to add to echomail messages.
<strong>Fido Aka </strong>The Fidonet aka for this area. <strong>Fido Aka </strong>The Fidonet aka for this area.
<strong>QWK name </strong>The name of the area for OffLine Readers. <strong>QWK name </strong>The name of the area for OffLine Readers.
<strong>Group </strong>The name of the echomail group.
<strong>Distrib. </strong>Leave this blank for now! <strong>Distrib. </strong>Leave this blank for now!
<strong>Area Type </strong>Local, Netmail, Echomail or News. <strong>Area Type </strong>Local, Netmail, Echomail or News.
<strong>Msg Kinds </strong>Private/Public, Private, Public, Read Only, FTN moderated, Usenet Moderated <strong>Msg Kinds </strong>Private/Public, Private, Public, Read Only, FTN moderated, Usenet Moderated
<strong>FTN chars </strong>FTN characterset, not in use yet, defaults to IBMPC 2 <strong>FTN chars </strong>FTN characterset, not in use yet, defaults to IBMPC 2
<strong>RFC chars </strong>RFC characterset, not in use yet, defaults tp LATIN-1 2 <strong>RFC chars </strong>RFC characterset, not in use yet, defaults tp LATIN-1 2
<strong>Active </strong>If this area is active.
<strong>Days Old </strong>The maximum age of the messages before purging. <strong>Days Old </strong>The maximum age of the messages before purging.
<strong>Max. Msgs </strong>The maximum messages in this area. <strong>Max. Msgs </strong>The maximum messages in this area.
<strong>Articles </strong>The maximum news headers to fetch. <strong>Articles </strong>The maximum news headers to fetch.
<strong>Netreply </strong>Netmail reply area if this is echomail. <strong>Netreply </strong>Netmail reply area if this is echomail.
<strong>Active </strong>If this area is active.
<strong>User Del. </strong>Users may delete their own messages.
<strong>Read Sec. </strong>The security level to read messages. <strong>Read Sec. </strong>The security level to read messages.
<strong>Write Sec. </strong>The security level to write messages. <strong>Write Sec. </strong>The security level to write messages.
<strong>Sysop Sec. </strong>The security level to do sysop actions. <strong>Sysop Sec. </strong>The security level to do sysop actions.
<strong>User Del. </strong>Users may delete their own messages.
<strong>Aliases </strong>Allow the use of an Alias. <strong>Aliases </strong>Allow the use of an Alias.
<strong>Random org </strong>Create random origin lines (Oneliner database).
<strong>Quotes </strong>Add a random quote under new messages (Oneliner database). <strong>Quotes </strong>Add a random quote under new messages (Oneliner database).
<strong>Mandatory </strong>If this area is mandatory for downlinks. <strong>Mandatory </strong>If this area is mandatory for downlinks.
<strong>UnSecure </strong>Don't check link address during toss (Dangerous!). <strong>UnSecure </strong>Don't check link address during toss (Dangerous!).
@ -124,38 +122,8 @@ harm is done. The file mbsetup.log shows all affected areas.
<H3>Automatic area creation.</H3> <H3>Automatic area creation.</H3>
<P> <P>
If you want to use the automatic area creation you have to define a fictitious If you want to use the automatic area creation you have to define this in the
area tagged 'DEFAULT' with the options you want for new areas like this: message area groups. This has been changed since MBSE BBS version 0.33.19.
<pre>
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
</pre>
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.<BR>
<P>
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.
<P>
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 <b>/opt/mbse/bin/mbfido tic toss web -a -quiet</b>.
<P> <P>
<A HREF="mail.html"><IMG SRC="../images/larrow.gif" ALT="Back" Border="0">Back to Mail Setup</A>&nbsp; <A HREF="mail.html"><IMG SRC="../images/larrow.gif" ALT="Back" Border="0">Back to Mail Setup</A>&nbsp;

1
html/setup/emgroup.html
View File

@ -1,4 +1,5 @@
<HTML> <HTML>
<!-- $Id$ -->
<HEAD> <HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1"> <META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
<META http-equiv="Content-Style-Type" content="text/css"> <META http-equiv="Content-Style-Type" content="text/css">

1
html/ups.html
View File

@ -1,4 +1,5 @@
<HTML> <HTML>
<!-- $Id$ -->
<HEAD> <HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1"> <META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
<META http-equiv="Content-Style-Type" content="text/css"> <META http-equiv="Content-Style-Type" content="text/css">