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
Download Patch File Download Diff File Expand all files Collapse all files

51
html/nodelist.html
View File

@@ -1,4 +1,5 @@
<HTML>
<!-- $Id$ -->
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO 8859-1">
<META http-equiv="Content-Style-Type" content="text/css">
@@ -11,7 +12,7 @@
</HEAD>
<BODY>
<BLOCKQUOTE>
<h5>Last update 07-Jun-2001</h5>
<h5>Last update 22-Jan-2002</h5>
<P>&nbsp;<P>
<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
goes wrong, you still have a working system. The three directories are:<br>
<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
compressed nodelists for download.
<li><strong>/opt/mbse/tmp/nlwork</strong>, this is the working directory
to apply diffs to the previous nodelist. This directory should allways
contain the latest <strong>uncompressed</strong> nodelist.
<li><strong>/var/spool/mbse/nodelist</strong>, this is the systems nodelist
directory defined in mbsetup, menu 1.3.4
<li><strong>/opt/mbse/var/nodelist</strong>, this is the systems nodelist
directory defined in mbsetup, menu 1.4.4
</ol>
In short the steps to process the nodediff's is as follows:
<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
are send from here. Below is the example of my system.
<P>
<IMG SRC="images/nodelist.gif" Border="0">
<IMG SRC="images/nodelist.gif" Border="0" Alt="BBS download area 20">
<P>&nbsp;</P>
<H3>The NODEDIFF tic area</H3>
<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
in the download directory, older ones are removed. Now you can receive
nodediff files, store them for download, and send them to other nodes.
<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>
<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
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
as uppercase names. As I receive the diff files as arc, the filemask on
my system is <strong>nodediff.a##</strong>.
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 <strong>nodediff.z##</strong>.
This means that the file with the name nodediff.z14 in the area NODEDIZZ
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>nodediff.a14</strong>.<br>The mbdiff program applies
<strong>nodediff.a14</strong> against <strong>NODELIST.007</strong> in the
<strong>mbdiff /opt/mbse/tmp/nlwork/NODELIST /var/spool/mbse/ftp/pub/fido/nodelist/nodediff.z14 -quiet</strong>
if the received nodediff is
<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
new <strong>NODELIST.014</strong> is created there, a compressed <strong>
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
uncompressed nodelist in the directory <strong>/opt/mbse/tmp/nlwork</strong>.
<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>
<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
is shown below. The hatch manager runs automatic with the comand
<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
hatch setup for this area.
tic area <strong>NODELIST</strong> The two screens below show the hatch and
tic setup for this area.
<P>
<IMG SRC="images/nodelist4.gif" Border="0" width="591" height="344">
<IMG SRC="images/nodelist3.gif" Border="0" width="591" height="344">
<IMG SRC="images/nodelist3.gif" Border="0" Alt="Hatch new nodelist">
<IMG SRC="images/nodelist4.gif" Border="0" Alt="TIC area for new nodelist">
<P>
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 <strong>magic</strong> command to do
that. In this case we unpack the nodelist in <strong>/var/spool/mbse/nodelist</strong>
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 <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
</strong> will compile the new nodelist. Don't be afraid that the unpacked
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>
mbtask</strong>.
<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>
<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>
</BODY>
</HTML>