Several changes, fixed dependencies

This commit is contained in:
Michiel Broek
2002-06-15 14:09:15 +00:00
parent ef92dc3316
commit 9368fd32b0
9 changed files with 790 additions and 11 deletions

View File

@@ -12,7 +12,7 @@
</HEAD>
<BODY>
<BLOCKQUOTE>
<h5>Last update 29-Jan-2001</h5>
<h5>Last update 15-Jun-2002</h5>
<P>&nbsp;<P>
<H1>MBSE BBS Setup - archiver programs</H1>
@@ -36,6 +36,11 @@ your bbs. To make life a little more easy, during the first bbs setup the most
common archivers already configured. You only need to make sure that they are
really present on your system.
<p>
When you configured the sources and build mbse, the configure script searched
for excisting archivers. When mbsetup was run the first time, when mbtask was
started, the archivers found on your system are already configured with the
right paths and enabled.
<p>
<A HREF="./"><IMG SRC="../images/larrow.gif" ALT="Back" Border="0">Back to index</A>&nbsp;
<A HREF="../"><IMG SRC="../images/b_arrow.gif" ALT="Home" Border="0">Back to main index</A>

View File

@@ -12,7 +12,7 @@
</HEAD>
<BODY>
<BLOCKQUOTE>
<h5>Last update 11-Jun-2002</h5>
<h5>Last update 15-Jun-2002</h5>
<P>&nbsp;<P>
<H1>MBSE BBS Setup - Fidonet nodes.</H1>
@@ -73,7 +73,8 @@ you can setup the aka's, mail, files and session handshake.
<H3>Mail setup</H3>
<P>
<pre>
<strong>Session pwd </strong>The mailer session password.
<strong>Session pwd </strong>The mailer session handshake password.
<strong>PKT password </strong>The password to insert in .pkt files.
<strong>Check PKT pwd </strong>Check password in received .pkt files. If not,
errors or missing passwords are only logged.
If set, errors or missing password are refused

View File

@@ -12,7 +12,7 @@
</HEAD>
<BODY>
<BLOCKQUOTE>
<h5>Last update 29-Jan-2001</h5>
<h5>Last update 15-Jun-2002</h5>
<P>&nbsp;<P>
<H1>MBSE BBS Setup - BBS Setup - Transfer Protocols.</H1>
@@ -26,6 +26,11 @@ already had internal protocols and the precessor of the bbs package had external
protocols. Because my priority was make the bbs working it still is that way.
When time comes I will build some of the protocols internal, adding external
protocols will allways be possible.
<p>
When you configured the sources and build mbse, the configure script searched
for excisting transfer protocols. When mbsetup was run the first time, when mbtask was
started, the protocols found on your system are already configured with the
right paths and enabled.
<P>&nbsp;<p>
<H3>Transfer Protocols Setup.</H3>

View File

@@ -12,7 +12,7 @@
</HEAD>
<BODY>
<BLOCKQUOTE>
<h5>Last update 25-Oct-2001</h5>
<h5>Last update 15-Jun-2002</h5>
<P>&nbsp;<P>
<H1>MBSE BBS Setup - virus scanners</H1>
@@ -28,8 +28,13 @@ There are several scanners for Linux available. Default only two of them
are setup. You may consult <A HREF="http://www.openantivirus.org/">
http://www.openantivirus.org</A> for more scanners mentioned in a mini-FAQ
maintained by Rainer Link.
<p>
When you configured the sources and build mbse, the configure script searched
for excisting scanners. When mbsetup was run the first time, when mbtask was
started, the scanners found on your system are already configured with the
right paths and enabled.
<P>
The following scanners are default installed in the setup but disabled for use:
The following scanners are default installed in the setup:
<p>
<UL>
@@ -46,7 +51,7 @@ HREF="http://www.frisk.is">http://www.frisk.is</A>. For now the BETA releases ar
for personal use.
</UL>
<P>
As soon as you have made a scanner available in the setup and you receive files
As soon as you have made one scanner available in the setup and you receive files
in tic areas where the scan flag is set, then these files will be checked.
As soon as one of the scanners detects a virus the received file will not be imported.
Uploads from users will be checked with the installed virus scanners as well.