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-01-22 20:38:29 +00:00
parent 5879543058
commit b39503d9aa
8 changed files with 45 additions and 32 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

BIN
html/images/nodelist.gif
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 12 KiB

After

Width:  |  Height:  |  Size: 12 KiB

BIN
html/images/nodelist1.gif
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 11 KiB

After

Width:  |  Height:  |  Size: 11 KiB

BIN
html/images/nodelist2.gif
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 8.8 KiB

After

Width:  |  Height:  |  Size: 8.5 KiB

BIN
html/images/nodelist3.gif
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 9.4 KiB

After

Width:  |  Height:  |  Size: 9.3 KiB

BIN
html/images/nodelist4.gif
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 11 KiB

After

Width:  |  Height:  |  Size: 11 KiB

BIN
html/images/nodelist5.gif
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 8.2 KiB

After

Width:  |  Height:  |  Size: 8.2 KiB

26
html/intergate.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">
@ -11,7 +12,7 @@
</HEAD> </HEAD>
<BODY> <BODY>
<BLOCKQUOTE> <BLOCKQUOTE>
<h5>Last update 26-Apr-2001</h5> <h5>Last update 22-Jan-2002</h5>
<P>&nbsp;<P> <P>&nbsp;<P>
<H1 ALIGN="CENTER">MBSE BBS - Internet Gateway.</H1> <H1 ALIGN="CENTER">MBSE BBS - Internet Gateway.</H1>
@ -45,10 +46,14 @@ description for the whole setup.
<P> <P>
If you only want to gate internet news to your bbs users and not want to If you only want to gate internet news to your bbs users and not want to
make echomail available as news, and you have a permament internet connection make echomail available as news, and you have a permament internet connection
then you don't need your own news server. Just configure MBSE BBS to use the then you don't need your own news server. This will also work on dialup links,
newsserver of your ISP in screen 1.14 with mbsetup. All other users need once the internet connection is up, make sure that <b>mbfido news -quiet</b> is
to run a newsserver on the bbs machine or another networked machine. You started as user mbse.
could use <A HREF="http://www.isc.org">inn news</A> for a newsserver. To do this configure MBSE BBS to use the newsserver of your ISP in screen 1.15
with mbsetup.
If you don't want to use the newsserver of your ISP or want to make echomail
available as news for your local users you must install your own newsserver.
You could use <A HREF="http://www.isc.org">inn news</A> for a newsserver.
To connect a small feed with your ISP you could use <strong>suck</strong>. To connect a small feed with your ISP you could use <strong>suck</strong>.
<P> <P>
In each echomail area you want to gate you need to fill in the newsgroup In each echomail area you want to gate you need to fill in the newsgroup
@ -61,12 +66,17 @@ that, you may get a lot of old articles that will be gated. Just run that
command once after you have set this up. Later when you receive fresh articles command once after you have set this up. Later when you receive fresh articles
the command <strong>mbfido news</strong> will only gate new arrived articles. the command <strong>mbfido news</strong> will only gate new arrived articles.
See the configuration of <A HREF="gwnews.html">INN news configuration</A>. See the configuration of <A HREF="gwnews.html">INN news configuration</A>.
In each mail area you can set the number of articles to get in one run. If you
set this too high, mbfido will scan all headers on the newsserver for new
articles. This can cost a lot of time. The best thing to do is to set this value
about four times higher then the average number of messages per day in that
group. If you set it too low, warning messages will appear in the logfile.
<P>&nbsp;<P> <P>&nbsp;<P>
<H3>Setup a newsgate with rnews.</H3> <H3>Setup a newsgate with rnews.</H3>
<P> <P>
This is the setup if you don't want an NNTP newsserver like inn, but a simple This is the setup if you don't want an NNTP newsserver like inn, but a simple
cnews setup for UUCP links only. In <strong>mbsetup</strong> menu 1.14 you need cnews setup for UUCP links only. In <strong>mbsetup</strong> menu 1.15 you need
to set this up. You need to fill in the path to the rnews program so that to set this up. You need to fill in the path to the rnews program so that
<strong>mbfido</strong> can post articles to cnews. MORE INFO NEEDED. <strong>mbfido</strong> can post articles to cnews. MORE INFO NEEDED.
<P> <P>
@ -79,7 +89,7 @@ posted to that newsgroup.
<P> <P>
With this setup you don't run a local newsserver, only your bbs users and With this setup you don't run a local newsserver, only your bbs users and
Fidonet links can then use news. You need to install <strong>uucp</strong> Fidonet links can then use news. You need to install <strong>uucp</strong>
on your system. With <strong>mbsetup</strong> menu 1.14 you need to set this on your system. With <strong>mbsetup</strong> menu 1.15 you need to set this
up. Suppose your ISP's nodename is xs4all the you probably need to set the up. Suppose your ISP's nodename is xs4all the you probably need to set the
UUCP path to <code>/var/spool/uucp/xs4all</code> and the UUCP node to UUCP path to <code>/var/spool/uucp/xs4all</code> and the UUCP node to
<code>xs4all</code>. Your own nodename will be your system's hostname without <code>xs4all</code>. Your own nodename will be your system's hostname without
@ -95,7 +105,7 @@ posted to that newsgroup.
See <A HREF="postfix.html">Postfix (email) configuration</A> See <A HREF="postfix.html">Postfix (email) configuration</A>
<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>

51
html/nodelist.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">
@ -11,7 +12,7 @@
</HEAD> </HEAD>
<BODY> <BODY>
<BLOCKQUOTE> <BLOCKQUOTE>
<h5>Last update 07-Jun-2001</h5> <h5>Last update 22-Jan-2002</h5>
<P>&nbsp;<P> <P>&nbsp;<P>
<H1>Nodelist and Nodediff processing</H1> <H1>Nodelist and Nodediff processing</H1>
@ -26,14 +27,14 @@ use three separate directories to do the nodelist processing. This is to
make sure that all stages are independent of each other, and if something make sure that all stages are independent of each other, and if something
goes wrong, you still have a working system. The three directories are:<br> goes wrong, you still have a working system. The three directories are:<br>
<ol> <ol>
<li><strong>/var/spool/mbse/ftp/pub/fido/nodelist</strong>, this is the public <li><strong>/opt/mbse/ftp/pub/fido/nodelist</strong>, this is the public
download area, the received diff's are stored here as well as the final download area, the received diff's are stored here as well as the final
compressed nodelists for download. compressed nodelists for download.
<li><strong>/opt/mbse/tmp/nlwork</strong>, this is the working directory <li><strong>/opt/mbse/tmp/nlwork</strong>, this is the working directory
to apply diffs to the previous nodelist. This directory should allways to apply diffs to the previous nodelist. This directory should allways
contain the latest <strong>uncompressed</strong> nodelist. contain the latest <strong>uncompressed</strong> nodelist.
<li><strong>/var/spool/mbse/nodelist</strong>, this is the systems nodelist <li><strong>/opt/mbse/var/nodelist</strong>, this is the systems nodelist
directory defined in mbsetup, menu 1.3.4 directory defined in mbsetup, menu 1.4.4
</ol> </ol>
In short the steps to process the nodediff's is as follows: In short the steps to process the nodediff's is as follows:
<ol> <ol>
@ -54,17 +55,17 @@ First define the download area for the bbs. In my case, this is area 20. From
here users can download the nodelists and nodediffs, files to the downlinks here users can download the nodelists and nodediffs, files to the downlinks
are send from here. Below is the example of my system. are send from here. Below is the example of my system.
<P> <P>
<IMG SRC="images/nodelist.gif" Border="0"> <IMG SRC="images/nodelist.gif" Border="0" Alt="BBS download area 20">
<P>&nbsp;</P> <P>&nbsp;</P>
<H3>The NODEDIFF tic area</H3> <H3>The NODEDIFF tic area</H3>
<P> <P>
From your uplinks you usually receive NODEDIFF files. Create a tic area for From your uplinks you usually receive NODEDIFF or NODEDIZZ files. Create a tic area for
that purpose. I have keep# set to 5, this means the last 5 diff's are stored that purpose. I have keep# set to 5, this means the last 5 diff's are stored
in the download directory, older ones are removed. Now you can receive in the download directory, older ones are removed. Now you can receive
nodediff files, store them for download, and send them to other nodes. nodediff files, store them for download, and send them to other nodes.
<P> <P>
<IMG SRC="images/nodelist1.gif" Border="0" width="591" height="344"> <IMG SRC="images/nodelist1.gif" Border="0" Alt="NODEDIZZ tic area">
<P>&nbsp;</P> <P>&nbsp;</P>
<H3>Apply the diff</H3> <H3>Apply the diff</H3>
@ -72,13 +73,14 @@ nodediff files, store them for download, and send them to other nodes.
We do this with the tic <strong>magic</strong> processor. In this example We do this with the tic <strong>magic</strong> processor. In this example
I have NODELIST.007 in the <strong>/opt/mbse/tmp/nlwork</strong> directory. I have NODELIST.007 in the <strong>/opt/mbse/tmp/nlwork</strong> directory.
Note that this filename is uppercase, they are usually stored and distributed Note that this filename is uppercase, they are usually stored and distributed
as uppercase names. As I receive the diff files as arc, the filemask on as uppercase names. As I receive the diff files as zip, the filemask on
my system is <strong>nodediff.a##</strong>. my system is <strong>nodediff.z##</strong>.
This means that the file with the name nodediff.a14 in the area NODEDIFF This means that the file with the name nodediff.z14 in the area NODEDIZZ
is a match. The command that is executed expands to is a match. The command that is executed expands to
<strong>mbdiff /opt/mbse/tmp/nlwork/NODELIST /var/spool/mbse/ftp/pub/fido/nodelist/nodediff.a14 -quiet</strong> if the received nodediff is <strong>mbdiff /opt/mbse/tmp/nlwork/NODELIST /var/spool/mbse/ftp/pub/fido/nodelist/nodediff.z14 -quiet</strong>
<strong>nodediff.a14</strong>.<br>The mbdiff program applies if the received nodediff is
<strong>nodediff.a14</strong> against <strong>NODELIST.007</strong> in the <strong>nodediff.z14</strong>.<br>The mbdiff program applies
<strong>nodediff.z14</strong> against <strong>NODELIST.007</strong> in the
<strong>/opt/mbse/tmp/nlwork</strong> directory. If this is successfull, a <strong>/opt/mbse/tmp/nlwork</strong> directory. If this is successfull, a
new <strong>NODELIST.014</strong> is created there, a compressed <strong> new <strong>NODELIST.014</strong> is created there, a compressed <strong>
nodelist.z14</strong> is created there and <strong>NODELIST.007</strong> is nodelist.z14</strong> is created there and <strong>NODELIST.007</strong> is
@ -94,7 +96,7 @@ you get it and manually give the <strong>mbdiff</strong> commands as user
<strong>mbse</strong> until you are up to date. Or, place the latest <strong>mbse</strong> until you are up to date. Or, place the latest
uncompressed nodelist in the directory <strong>/opt/mbse/tmp/nlwork</strong>. uncompressed nodelist in the directory <strong>/opt/mbse/tmp/nlwork</strong>.
<P> <P>
<IMG SRC="images/nodelist2.gif" Border="0" width="591" height="344"> <IMG SRC="images/nodelist2.gif" Border="0" Alt="Magic to apply the nodelist diff file">
<P>&nbsp;</P> <P>&nbsp;</P>
<H3>Processing the new nodelist</H3> <H3>Processing the new nodelist</H3>
@ -104,16 +106,17 @@ The file <strong>nodelist.z14</strong> is in the directory
<strong>/opt/mbse/tmp/nlwork</strong>. The example for the hatch manager <strong>/opt/mbse/tmp/nlwork</strong>. The example for the hatch manager
is shown below. The hatch manager runs automatic with the comand is shown below. The hatch manager runs automatic with the comand
<strong>mbfido tic</strong>. This setup will hatch the new nodelist in the <strong>mbfido tic</strong>. This setup will hatch the new nodelist in the
tic area <strong>NODELIST</strong> The two screens below show the tic and tic area <strong>NODELIST</strong> The two screens below show the hatch and
hatch setup for this area. tic setup for this area.
<P> <P>
<IMG SRC="images/nodelist4.gif" Border="0" width="591" height="344"> <IMG SRC="images/nodelist3.gif" Border="0" Alt="Hatch new nodelist">
<IMG SRC="images/nodelist3.gif" Border="0" width="591" height="344"> <IMG SRC="images/nodelist4.gif" Border="0" Alt="TIC area for new nodelist">
<P> <P>
Now that we have hatched the new nodelist and stored in in the download area, Now that we have hatched the new nodelist and processed it the new nodelist
and maybe send some copies to downlinks, we have to feed it to the nodelist is stored in in the download area, and maybe send some copies to downlinks.
compiler for our own system. We use a tic <strong>magic</strong> command to do We now have to feed it to the nodelist compiler for our own system.
that. In this case we unpack the nodelist in <strong>/var/spool/mbse/nodelist</strong> We use a tic <strong>magic</strong> command to do
that. In this case we unpack the nodelist in <strong>/opt/mbse/var/nodelist</strong>
and set the <strong>compile</strong> semafore so that the <strong>mbindex and set the <strong>compile</strong> semafore so that the <strong>mbindex
</strong> will compile the new nodelist. Don't be afraid that the unpacked </strong> will compile the new nodelist. Don't be afraid that the unpacked
nodelists will acumulate in the nodelist directory, <strong>mbindex</strong> nodelists will acumulate in the nodelist directory, <strong>mbindex</strong>
@ -121,10 +124,10 @@ will handle that, only the latest two nodelists are kept there. The
<strong>mbindex</strong> program is started by the taskmanager <strong> <strong>mbindex</strong> program is started by the taskmanager <strong>
mbtask</strong>. mbtask</strong>.
<P> <P>
<IMG SRC="images/nodelist5.gif" Border="0" width="591" height="344"> <IMG SRC="images/nodelist5.gif" Border="0" Alt="Magic copy nodelist and trigger compiler">
<P>&nbsp;</P> <P>&nbsp;</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>