diff --git a/html/images/nodelist.gif b/html/images/nodelist.gif index 361fb05d..58a42c23 100644 Binary files a/html/images/nodelist.gif and b/html/images/nodelist.gif differ diff --git a/html/images/nodelist1.gif b/html/images/nodelist1.gif index 7d2bc179..fe0e10cb 100644 Binary files a/html/images/nodelist1.gif and b/html/images/nodelist1.gif differ diff --git a/html/images/nodelist2.gif b/html/images/nodelist2.gif index ecdce8d1..d9fe58c3 100644 Binary files a/html/images/nodelist2.gif and b/html/images/nodelist2.gif differ diff --git a/html/images/nodelist3.gif b/html/images/nodelist3.gif index b064d659..948fa83b 100644 Binary files a/html/images/nodelist3.gif and b/html/images/nodelist3.gif differ diff --git a/html/images/nodelist4.gif b/html/images/nodelist4.gif index b722e8f4..5642c742 100644 Binary files a/html/images/nodelist4.gif and b/html/images/nodelist4.gif differ diff --git a/html/images/nodelist5.gif b/html/images/nodelist5.gif index ea5b7195..4d2dc03d 100644 Binary files a/html/images/nodelist5.gif and b/html/images/nodelist5.gif differ diff --git a/html/intergate.html b/html/intergate.html index 9588140c..c663b40b 100644 --- a/html/intergate.html +++ b/html/intergate.html @@ -1,4 +1,5 @@ + @@ -11,7 +12,7 @@
-
Last update 26-Apr-2001
+
Last update 22-Jan-2002

 

MBSE BBS - Internet Gateway.

@@ -45,10 +46,14 @@ description for the whole setup.

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 -then you don't need your own news server. Just configure MBSE BBS to use the -newsserver of your ISP in screen 1.14 with mbsetup. All other users need -to run a newsserver on the bbs machine or another networked machine. You -could use inn news for a newsserver. +then you don't need your own news server. This will also work on dialup links, +once the internet connection is up, make sure that mbfido news -quiet is +started as user mbse. +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 inn news for a newsserver. To connect a small feed with your ISP you could use suck.

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 the command mbfido news will only gate new arrived articles. See the configuration of INN news configuration. +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.

 

Setup a newsgate with rnews.

This is the setup if you don't want an NNTP newsserver like inn, but a simple -cnews setup for UUCP links only. In mbsetup menu 1.14 you need +cnews setup for UUCP links only. In mbsetup menu 1.15 you need to set this up. You need to fill in the path to the rnews program so that mbfido can post articles to cnews. MORE INFO NEEDED.

@@ -79,7 +89,7 @@ posted to that newsgroup.

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 uucp -on your system. With mbsetup menu 1.14 you need to set this +on your system. With mbsetup menu 1.15 you need to set this up. Suppose your ISP's nodename is xs4all the you probably need to set the UUCP path to /var/spool/uucp/xs4all and the UUCP node to xs4all. Your own nodename will be your system's hostname without @@ -95,7 +105,7 @@ posted to that newsgroup. See Postfix (email) configuration

-Back Go Back +BackGo Back

diff --git a/html/nodelist.html b/html/nodelist.html index bda77168..c462c4d6 100644 --- a/html/nodelist.html +++ b/html/nodelist.html @@ -1,4 +1,5 @@ + @@ -11,7 +12,7 @@
-
Last update 07-Jun-2001
+
Last update 22-Jan-2002

 

Nodelist and Nodediff processing

@@ -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 goes wrong, you still have a working system. The three directories are:
    -
  1. /var/spool/mbse/ftp/pub/fido/nodelist, this is the public +
  2. /opt/mbse/ftp/pub/fido/nodelist, this is the public download area, the received diff's are stored here as well as the final compressed nodelists for download.
  3. /opt/mbse/tmp/nlwork, this is the working directory to apply diffs to the previous nodelist. This directory should allways contain the latest uncompressed nodelist. -
  4. /var/spool/mbse/nodelist, this is the systems nodelist -directory defined in mbsetup, menu 1.3.4 +
  5. /opt/mbse/var/nodelist, this is the systems nodelist +directory defined in mbsetup, menu 1.4.4
In short the steps to process the nodediff's is as follows:
    @@ -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 are send from here. Below is the example of my system.

    - +BBS download area 20

     

    The NODEDIFF tic area

    -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 in the download directory, older ones are removed. Now you can receive nodediff files, store them for download, and send them to other nodes.

    - +NODEDIZZ tic area

     

    Apply the diff

    @@ -72,13 +73,14 @@ nodediff files, store them for download, and send them to other nodes. We do this with the tic magic processor. In this example I have NODELIST.007 in the /opt/mbse/tmp/nlwork directory. 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 -my system is nodediff.a##. -This means that the file with the name nodediff.a14 in the area NODEDIFF +as uppercase names. As I receive the diff files as zip, the filemask on +my system is nodediff.z##. +This means that the file with the name nodediff.z14 in the area NODEDIZZ is a match. The command that is executed expands to -mbdiff /opt/mbse/tmp/nlwork/NODELIST /var/spool/mbse/ftp/pub/fido/nodelist/nodediff.a14 -quiet if the received nodediff is -nodediff.a14.
    The mbdiff program applies -nodediff.a14 against NODELIST.007 in the +mbdiff /opt/mbse/tmp/nlwork/NODELIST /var/spool/mbse/ftp/pub/fido/nodelist/nodediff.z14 -quiet +if the received nodediff is +nodediff.z14.
    The mbdiff program applies +nodediff.z14 against NODELIST.007 in the /opt/mbse/tmp/nlwork directory. If this is successfull, a new NODELIST.014 is created there, a compressed nodelist.z14 is created there and NODELIST.007 is @@ -94,7 +96,7 @@ you get it and manually give the mbdiff commands as user mbse until you are up to date. Or, place the latest uncompressed nodelist in the directory /opt/mbse/tmp/nlwork.

    - +Magic to apply the nodelist diff file

     

    Processing the new nodelist

    @@ -104,16 +106,17 @@ The file nodelist.z14 is in the directory /opt/mbse/tmp/nlwork. The example for the hatch manager is shown below. The hatch manager runs automatic with the comand mbfido tic. This setup will hatch the new nodelist in the -tic area NODELIST The two screens below show the tic and -hatch setup for this area. +tic area NODELIST The two screens below show the hatch and +tic setup for this area.

    - - +Hatch new nodelist +TIC area for new nodelist

    -Now that we have hatched the new nodelist and stored in in the download area, -and maybe send some copies to downlinks, we have to feed it to the nodelist -compiler for our own system. We use a tic magic command to do -that. In this case we unpack the nodelist in /var/spool/mbse/nodelist +Now that we have hatched the new nodelist and processed it the new nodelist +is stored in in the download area, and maybe send some copies to downlinks. +We now have to feed it to the nodelist compiler for our own system. +We use a tic magic command to do +that. In this case we unpack the nodelist in /opt/mbse/var/nodelist and set the compile semafore so that the mbindex will compile the new nodelist. Don't be afraid that the unpacked nodelists will acumulate in the nodelist directory, mbindex @@ -121,10 +124,10 @@ will handle that, only the latest two nodelists are kept there. The mbindex program is started by the taskmanager mbtask.

    - +Magic copy nodelist and trigger compiler

     

    -Back Go Back +BackGo Back