serveral updates for running DOS doors
This commit is contained in:
parent
71889fe67d
commit
6fcdb10f53
316
html/basic.html
316
html/basic.html
@ -1,158 +1,158 @@
|
|||||||
<HTML>
|
<HTML>
|
||||||
<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">
|
||||||
<META name="author" lang="en" "content="Michiel Broek">
|
<META name="author" lang="en" content="Michiel Broek">
|
||||||
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
||||||
<META name="description" lang="en" content="MBSE BBS Manual">
|
<META name="description" lang="en" content="MBSE BBS Manual">
|
||||||
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
||||||
<TITLE>MBSE BBS basic installation.</TITLE>
|
<TITLE>MBSE BBS basic installation.</TITLE>
|
||||||
<LINK rel=stylesheet HREF="manual.css">
|
<LINK rel=stylesheet HREF="manual.css">
|
||||||
</HEAD>
|
</HEAD>
|
||||||
<BODY>
|
<BODY>
|
||||||
<BLOCKQUOTE>
|
<BLOCKQUOTE>
|
||||||
<h5>Last update 07-Aug-2001</h5>
|
<h5>Last update 07-Aug-2001</h5>
|
||||||
<P> <P>
|
<P> <P>
|
||||||
|
|
||||||
<h1>MBSE BBS Basic Installation</h1>
|
<h1>MBSE BBS Basic Installation</h1>
|
||||||
|
|
||||||
<h3>Introduction.</h3>
|
<h3>Introduction.</h3>
|
||||||
<p>
|
<p>
|
||||||
Before you compile and install MBSE BBS you must first setup the basic
|
Before you compile and install MBSE BBS you must first setup the basic
|
||||||
environment. If you don't do this, things will fail.
|
environment. If you don't do this, things will fail.
|
||||||
<P> <p>
|
<P> <p>
|
||||||
|
|
||||||
<h3>Step 1: planning the filesystems.</h3>
|
<h3>Step 1: planning the filesystems.</h3>
|
||||||
<p>
|
<p>
|
||||||
MBSE BBS is default installed in <b>/opt/mbse</b>. The spoolfiles (in and
|
MBSE BBS is default installed in <b>/opt/mbse</b>. The spoolfiles (in and
|
||||||
outbound, message bases) go into <b>/var/spool/mbse</b>. In the <b>/opt/mbse</b>
|
outbound, message bases) go into <b>/var/spool/mbse</b>. In the <b>/opt/mbse</b>
|
||||||
path are several subdirectories, <b>bin</b> for the binaries, <b>etc</b> for the
|
path are several subdirectories, <b>bin</b> for the binaries, <b>etc</b> for the
|
||||||
configuration and some scripts, <b>english, spanish, italian</b> and <b>dutch</b> for the language
|
configuration and some scripts, <b>english, spanish, italian</b> and <b>dutch</b> for the language
|
||||||
files and menus, <b>home</b> for the users homedirectories, <b>log</b> for the
|
files and menus, <b>home</b> for the users homedirectories, <b>log</b> for the
|
||||||
logfiles, <b>magic</b> for the filerequest magicnames, <b>fdb</b> for the files
|
logfiles, <b>magic</b> for the filerequest magicnames, <b>fdb</b> for the files
|
||||||
database, <b>var</b> for some statistic files and <b>tmp</b> as temp directory.
|
database, <b>var</b> for some statistic files and <b>tmp</b> as temp directory.
|
||||||
<p>
|
<p>
|
||||||
Don't use UMSDOS or SAMBA filesystems for the bbs, stick by the standard Linux
|
Don't use UMSDOS or SAMBA filesystems for the bbs, stick by the standard Linux
|
||||||
filesystems (ext2 or reiserfs). If you intent to make your bbs also accessible
|
filesystems (ext2 or reiserfs). If you intent to make your bbs also accessible
|
||||||
by FTP and WWW you must create the directory structure under the ftp user
|
by FTP and WWW you must create the directory structure under the ftp user
|
||||||
behind the pub directory. Read <a href="misc/ftpserver.html">the
|
behind the pub directory. Read <a href="misc/ftpserver.html">the
|
||||||
ftp server</a> doc for details. If you don't follow these guidlines, you
|
ftp server</a> doc for details. If you don't follow these guidlines, you
|
||||||
will run into trouble later and have to spend a lot of time in correcting
|
will run into trouble later and have to spend a lot of time in correcting
|
||||||
this error.
|
this error.
|
||||||
<p>
|
<p>
|
||||||
The default setup will be as follows:<br>
|
The default setup will be as follows:<br>
|
||||||
<pre>
|
<pre>
|
||||||
/opt/mbse binaries, config and user home directories.
|
/opt/mbse binaries, config and user home directories.
|
||||||
/var/spool/mbse In/outbound, queues, download directories.
|
/var/spool/mbse In/outbound, queues, download directories.
|
||||||
</pre>
|
</pre>
|
||||||
<P> <p>
|
<P> <p>
|
||||||
|
|
||||||
<h3>Step 2: Running the installation script.</h3>
|
<h3>Step 2: Running the installation script.</h3>
|
||||||
<p>
|
<p>
|
||||||
The installation script must be run by root. It checks if there is a
|
The installation script must be run by root. It checks if there is a
|
||||||
previous or failed installation on your system. If that's so the script will
|
previous or failed installation on your system. If that's so the script will
|
||||||
not run. In other words, you can only run this script once. The script makes
|
not run. In other words, you can only run this script once. The script makes
|
||||||
backup copies of the system files it changes, these files will get the
|
backup copies of the system files it changes, these files will get the
|
||||||
extension <strong>.mbse</strong> To run the installation script you need
|
extension <strong>.mbse</strong> To run the installation script you need
|
||||||
the archive <strong>mbbsebbs-0.33.nn.tar.gz</strong>.
|
the archive <strong>mbbsebbs-0.33.nn.tar.gz</strong>.
|
||||||
Unpack this archive on your system, in /tmp will do fine:
|
Unpack this archive on your system, in /tmp will do fine:
|
||||||
<pre>
|
<pre>
|
||||||
cd /tmp
|
cd /tmp
|
||||||
tar xfvz /path/to/the/mbsebbs-0.33.nn.tar.gz
|
tar xfvz /path/to/the/mbsebbs-0.33.nn.tar.gz
|
||||||
</pre>
|
</pre>
|
||||||
To start the script type:
|
To start the script type:
|
||||||
<pre>
|
<pre>
|
||||||
cd mbsebbs-0.33.nn
|
cd mbsebbs-0.33.nn
|
||||||
bash ./SETUP.sh
|
bash ./SETUP.sh
|
||||||
</pre>
|
</pre>
|
||||||
Yes, use <b>bash</b> as shell here. On some systems root doesn't use bash
|
Yes, use <b>bash</b> as shell here. On some systems root doesn't use bash
|
||||||
as login shell, calling the script with bash forces the use of bash.
|
as login shell, calling the script with bash forces the use of bash.
|
||||||
The script does the following:
|
The script does the following:
|
||||||
<ol>
|
<ol>
|
||||||
<li>Create the group <strong>bbs</strong>
|
<li>Create the group <strong>bbs</strong>
|
||||||
<li>Create the user <strong>mbse</strong>
|
<li>Create the user <strong>mbse</strong>
|
||||||
<li>Create a <strong>.profile</strong> for user <strong>mbse</strong>
|
<li>Create a <strong>.profile</strong> for user <strong>mbse</strong>
|
||||||
<li>Create and set owner of directory tree under /opt/mbse
|
<li>Create and set owner of directory tree under /opt/mbse
|
||||||
</ol>
|
</ol>
|
||||||
Then the script will ask you to give a password for user <strong>mbse</strong>
|
Then the script will ask you to give a password for user <strong>mbse</strong>
|
||||||
This password is for system maintenance and for you to make changes to the
|
This password is for system maintenance and for you to make changes to the
|
||||||
bbs. You will need that frequently but you should not make that password
|
bbs. You will need that frequently but you should not make that password
|
||||||
easy to guess of course. The script will then continue again:
|
easy to guess of course. The script will then continue again:
|
||||||
<ol start="5">
|
<ol start="5">
|
||||||
<li>The user <strong>bbs</strong> is added.
|
<li>The user <strong>bbs</strong> is added.
|
||||||
<li>The password will be removed from user <strong>bbs</strong> This action
|
<li>The password will be removed from user <strong>bbs</strong> This action
|
||||||
will make changes in /etc/shadow (if you have that) otherwise in /etc/passwd.
|
will make changes in /etc/shadow (if you have that) otherwise in /etc/passwd.
|
||||||
On FreeBSD it uses other tools to modify the master database.
|
On FreeBSD it uses other tools to modify the master database.
|
||||||
<li>If they don't exist in the file /etc/services the services fido, tfido
|
<li>If they don't exist in the file /etc/services the services fido, tfido
|
||||||
and binkp will be added.
|
and binkp will be added.
|
||||||
<li>If they don't exist in the file /etc/inetd.conf the internet protocols
|
<li>If they don't exist in the file /etc/inetd.conf the internet protocols
|
||||||
for the mailer will be added. The <strong>inetd</strong> is restarted to
|
for the mailer will be added. The <strong>inetd</strong> is restarted to
|
||||||
activate the changes.
|
activate the changes.
|
||||||
</ol>
|
</ol>
|
||||||
<p> <p>
|
<p> <p>
|
||||||
|
|
||||||
<h3>Step 3: Check the basic installation</h3>
|
<h3>Step 3: Check the basic installation</h3>
|
||||||
<p>
|
<p>
|
||||||
The last screen of the script is about sanity checks. Perform those checks!
|
The last screen of the script is about sanity checks. Perform those checks!
|
||||||
If something is wrong, now is the time to fix it. Don't panic and remember
|
If something is wrong, now is the time to fix it. Don't panic and remember
|
||||||
the backups of the system files that are changed are in /etc with the
|
the backups of the system files that are changed are in /etc with the
|
||||||
extension <strong>.mbse</strong> i.e: those were the original files.
|
extension <strong>.mbse</strong> i.e: those were the original files.
|
||||||
If everythings is allright, then remove the directory /tmp/mbsebbs-0.33.nn:
|
If everythings is allright, then remove the directory /tmp/mbsebbs-0.33.nn:
|
||||||
<pre>
|
<pre>
|
||||||
cd /tmp
|
cd /tmp
|
||||||
rm -Rf mbsebbs-0.33.nn
|
rm -Rf mbsebbs-0.33.nn
|
||||||
</pre>
|
</pre>
|
||||||
<p> <p>
|
<p> <p>
|
||||||
|
|
||||||
<h3>Step 4: Install the basic packages.</h3>
|
<h3>Step 4: Install the basic packages.</h3>
|
||||||
<p>
|
<p>
|
||||||
Login as user <b>mbse</b>. While in the home directory unpack the distribution
|
Login as user <b>mbse</b>. While in the home directory unpack the distribution
|
||||||
archives:
|
archives:
|
||||||
<pre>
|
<pre>
|
||||||
tar xfvz /path/to/mbsebbs-0.33.nn.tar.gz
|
tar xfvz /path/to/mbsebbs-0.33.nn.tar.gz
|
||||||
</pre>
|
</pre>
|
||||||
You now have the subdirectory with sources in the right place.
|
You now have the subdirectory with sources in the right place.
|
||||||
Next build the binaries and install them using the folowing commands:
|
Next build the binaries and install them using the folowing commands:
|
||||||
<pre>
|
<pre>
|
||||||
cd ~/mbsebbs-0.33.nn
|
cd ~/mbsebbs-0.33.nn
|
||||||
./configure
|
./configure
|
||||||
make
|
make
|
||||||
su
|
su
|
||||||
password: <em>enter root password here</em>
|
password: <em>enter root password here</em>
|
||||||
make install
|
make install
|
||||||
exit
|
exit
|
||||||
</pre>
|
</pre>
|
||||||
The last part of the installation procedure shows you the location of the bbs
|
The last part of the installation procedure shows you the location of the bbs
|
||||||
startup script that is added to your system. Because this is your first
|
startup script that is added to your system. Because this is your first
|
||||||
time installation, example menus, textfiles and some databases are installed.
|
time installation, example menus, textfiles and some databases are installed.
|
||||||
If they already exist on your systems (when you do an upgrade) they
|
If they already exist on your systems (when you do an upgrade) they
|
||||||
will not be installed again.
|
will not be installed again.
|
||||||
<p>
|
<p>
|
||||||
Now you must start the <b>mbtask</b> daemon by hand by typing <b>/opt/mbse/bin/mbtask</b>.
|
Now you must start the <b>mbtask</b> daemon by hand by typing <b>/opt/mbse/bin/mbtask</b>.
|
||||||
Check the file <b>/opt/mbse/log/mbtask.log</b> for startup problems. You may notice that
|
Check the file <b>/opt/mbse/log/mbtask.log</b> for startup problems. You may notice that
|
||||||
the program <b>mbcico</b> is started everytime, this is not a problem, it simply doesn't work right
|
the program <b>mbcico</b> is started everytime, this is not a problem, it simply doesn't work right
|
||||||
now because you haven't configured anything yet.
|
now because you haven't configured anything yet.
|
||||||
<p> <p>
|
<p> <p>
|
||||||
|
|
||||||
<h3>Step 5: (RedHat) startup problems.</h3>
|
<h3>Step 5: (RedHat) startup problems.</h3>
|
||||||
<p>
|
<p>
|
||||||
From RedHat 6.1 (not the older versions) the behaviour of the
|
From RedHat 6.1 (not the older versions) the behaviour of the
|
||||||
<strong>su</strong> is changed. This may be true for other distributions since
|
<strong>su</strong> is changed. This may be true for other distributions since
|
||||||
the end of 1999 and for Mandrake as well. The file <code>/etc/rc.d/init.d/mbsed</code> that is
|
the end of 1999 and for Mandrake as well. The file <code>/etc/rc.d/init.d/mbsed</code> that is
|
||||||
created by the setup script is different then before. The new command
|
created by the setup script is different then before. The new command
|
||||||
is <strong>su -</strong> instead of simply <strong>su</strong>. It might be
|
is <strong>su -</strong> instead of simply <strong>su</strong>. It might be
|
||||||
that other new distributions also need the extra minus sign. If that's the
|
that other new distributions also need the extra minus sign. If that's the
|
||||||
case, please let me know and tell me how I can test what version it is.
|
case, please let me know and tell me how I can test what version it is.
|
||||||
<p> <p>
|
<p> <p>
|
||||||
|
|
||||||
<h3>Step 6: ready.</h3>
|
<h3>Step 6: ready.</h3>
|
||||||
<p>
|
<p>
|
||||||
Now the basic environment is finished, the next thing is to <a href="install.html">install</a>
|
Now the basic environment is finished, the next thing is to <a href="install.html">install</a>
|
||||||
the scripts, examples and configuration.
|
the scripts, examples and configuration.
|
||||||
<P> <P>
|
<P> <P>
|
||||||
<a href="index.htm"><img SRC="images/b_arrow.gif" ALT="Back to Index" BORDER=0 width="33" height="35" ></a>
|
<a href="index.htm"><img SRC="images/b_arrow.gif" ALT="Back to Index" BORDER=0 width="33" height="35" ></a>
|
||||||
<a href="index.htm">Back to Index</a>
|
<a href="index.htm">Back to Index</a>
|
||||||
|
|
||||||
</blockquote>
|
</blockquote>
|
||||||
</body>
|
</body>
|
||||||
</html>
|
</html>
|
||||||
|
148
html/dist.html
148
html/dist.html
@ -1,74 +1,74 @@
|
|||||||
<HTML>
|
<HTML>
|
||||||
<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">
|
||||||
<META name="author" lang="en" "content="Michiel Broek">
|
<META name="author" lang="en" content="Michiel Broek">
|
||||||
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
||||||
<META name="description" lang="en" content="MBSE BBS Manual">
|
<META name="description" lang="en" content="MBSE BBS Manual">
|
||||||
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
||||||
<TITLE>Linux distributions.</TITLE>
|
<TITLE>Linux distributions.</TITLE>
|
||||||
<LINK rel=stylesheet HREF="manual.css">
|
<LINK rel=stylesheet HREF="manual.css">
|
||||||
</HEAD>
|
</HEAD>
|
||||||
<BODY>
|
<BODY>
|
||||||
<BLOCKQUOTE>
|
<BLOCKQUOTE>
|
||||||
<h5>Last update 06-Jun-2001</h5>
|
<h5>Last update 06-Jun-2001</h5>
|
||||||
<P> <P>
|
<P> <P>
|
||||||
|
|
||||||
<H1>Linux Distributions.</H1>
|
<H1>Linux Distributions.</H1>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<H3>Which distribution</H3>
|
<H3>Which distribution</H3>
|
||||||
<P>
|
<P>
|
||||||
Linux is available in several distributions, they all have advantages and
|
Linux is available in several distributions, they all have advantages and
|
||||||
disadvantages for bbs use. Which distribution to pick is very personal.
|
disadvantages for bbs use. Which distribution to pick is very personal.
|
||||||
You should also consider the fact if the bbs machine is the same machine on
|
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.
|
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,
|
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.
|
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.
|
Most important is that this is my personal view.
|
||||||
<P> <P>
|
<P> <P>
|
||||||
|
|
||||||
<H3>Slackware</H3>
|
<H3>Slackware</H3>
|
||||||
<P>
|
<P>
|
||||||
I am using MBSE BBS on several Slackware distributions. You can make a very small
|
I am using MBSE BBS on several Slackware distributions. You can make a very small
|
||||||
setup for MBSE BBS like Zipslack. Not included is the mgetty package.
|
setup for MBSE BBS like Zipslack. Not included is the mgetty package.
|
||||||
<P> <P>
|
<P> <P>
|
||||||
|
|
||||||
<H3>Redhat and Mandrake</H3>
|
<H3>Redhat and Mandrake</H3>
|
||||||
<P>
|
<P>
|
||||||
I write this as if these are the same which isn't true of course. From MBSE
|
I write this as if these are the same which isn't true of course. From MBSE
|
||||||
BBS's point of view they are almost the same, so that's why I treat them as
|
BBS's point of view they are almost the same, so that's why I treat them as
|
||||||
the same distributions. For people with little Linux experience these
|
the same distributions. For people with little Linux experience these
|
||||||
distributions are a good choice if you can spare the diskspace. I haven't
|
distributions are a good choice if you can spare the diskspace. I haven't
|
||||||
found a simple dedicated setup for the bbs, so the safest way is to install
|
found a simple dedicated setup for the bbs, so the safest way is to install
|
||||||
allmost everything, which is quite simple. This will cost you about 1200 Megs.
|
allmost everything, which is quite simple. This will cost you about 1200 Megs.
|
||||||
Maybe that someone more experienced with these distro's can give more details
|
Maybe that someone more experienced with these distro's can give more details
|
||||||
on how to build a small server. Please note that from RedHat 6.1 and up the
|
on how to build a small server. Please note that from RedHat 6.1 and up the
|
||||||
startup script (/etc/rc.d/init.d/mbsed) is different than before. Maybe
|
startup script (/etc/rc.d/init.d/mbsed) is different than before. Maybe
|
||||||
this is needed for Mandrake 6.1 and up too.
|
this is needed for Mandrake 6.1 and up too.
|
||||||
<P> <P>
|
<P> <P>
|
||||||
|
|
||||||
<H3>SuSe</H3>
|
<H3>SuSe</H3>
|
||||||
<P>
|
<P>
|
||||||
Since SuSE 7.1 the setup scripts are working and tested. Older distro's
|
Since SuSE 7.1 the setup scripts are working and tested. Older distro's
|
||||||
might work.
|
might work.
|
||||||
<P> <P>
|
<P> <P>
|
||||||
|
|
||||||
<H3>Debian</H3>
|
<H3>Debian</H3>
|
||||||
<P>
|
<P>
|
||||||
The installation works on a Debian 2.1 and 2.2 distribution without any problems.
|
The installation works on a Debian 2.1 and 2.2 distribution without any problems.
|
||||||
How to build an optimized Debian system is not tested by me.
|
How to build an optimized Debian system is not tested by me.
|
||||||
<P> <P>
|
<P> <P>
|
||||||
|
|
||||||
<H3>Famous last words...</H3>
|
<H3>Famous last words...</H3>
|
||||||
<P>
|
<P>
|
||||||
I don't have the diskspace for all kinds of Linux distributions to install
|
I don't have the diskspace for all kinds of Linux distributions to install
|
||||||
at the same time, with the current size of Linux, I only have 2 versions
|
at the same time, with the current size of Linux, I only have 2 versions
|
||||||
installed. Also, I don't buy every new distro that's available. If you have
|
installed. Also, I don't buy every new distro that's available. If you have
|
||||||
a problem with that, just send me the new distro on CD to test by snailmail.
|
a problem with that, just send me the new distro on CD to test by snailmail.
|
||||||
<P> <P>
|
<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" width="33" height="35"> Go Back</A>
|
||||||
</BODY>
|
</BODY>
|
||||||
</HTML>
|
</HTML>
|
||||||
|
|
||||||
|
338
html/flow.html
338
html/flow.html
@ -1,169 +1,169 @@
|
|||||||
<HTML>
|
<HTML>
|
||||||
<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">
|
||||||
<META name="author" lang="en" "content="Michiel Broek">
|
<META name="author" lang="en" content="Michiel Broek">
|
||||||
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
||||||
<META name="description" lang="en" content="MBSE BBS Manual">
|
<META name="description" lang="en" content="MBSE BBS Manual">
|
||||||
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
||||||
<TITLE>Running a BBS under Linux.</TITLE>
|
<TITLE>Running a BBS under Linux.</TITLE>
|
||||||
<LINK rel=stylesheet HREF="manual.css">
|
<LINK rel=stylesheet HREF="manual.css">
|
||||||
</HEAD>
|
</HEAD>
|
||||||
<BODY>
|
<BODY>
|
||||||
<BLOCKQUOTE>
|
<BLOCKQUOTE>
|
||||||
<h5>Last update 06-Jun-2001</h5>
|
<h5>Last update 06-Jun-2001</h5>
|
||||||
<P> <P>
|
<P> <P>
|
||||||
|
|
||||||
<H1>Running a BBS under Linux.</H1>
|
<H1>Running a BBS under Linux.</H1>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<h3>Introduction</H3>
|
<h3>Introduction</H3>
|
||||||
<P>
|
<P>
|
||||||
Everyone who has been running a (single line) BBS under DOS until now will
|
Everyone who has been running a (single line) BBS under DOS until now will
|
||||||
need to understand that running a BBS under Linux (or any other multitasking
|
need to understand that running a BBS under Linux (or any other multitasking
|
||||||
os) is completly different of what you are used to. Under DOS things were
|
os) is completly different of what you are used to. Under DOS things were
|
||||||
quite simple, from AUTOEXEC.BAT you started a new .BAT file that would run
|
quite simple, from AUTOEXEC.BAT you started a new .BAT file that would run
|
||||||
forever and started all needed programs after each other.
|
forever and started all needed programs after each other.
|
||||||
The programs that where started
|
The programs that where started
|
||||||
depended on the errorlevel of the previous program. Only one program could
|
depended on the errorlevel of the previous program. Only one program could
|
||||||
run at the same time.
|
run at the same time.
|
||||||
<P>
|
<P>
|
||||||
People who had previous run a BBS on another multitasking os, or were running
|
People who had previous run a BBS on another multitasking os, or were running
|
||||||
a BBS on a small lan with a fileserver and workstations for each line, are
|
a BBS on a small lan with a fileserver and workstations for each line, are
|
||||||
already more used to the idea of running more programs at the same time,
|
already more used to the idea of running more programs at the same time,
|
||||||
and to "signal" what to do next with semafore files.
|
and to "signal" what to do next with semafore files.
|
||||||
<P>
|
<P>
|
||||||
The Linux aproach is more or less the same, but there are more differences.
|
The Linux aproach is more or less the same, but there are more differences.
|
||||||
The main difference is that there is no mailer connected with the modem waiting
|
The main difference is that there is no mailer connected with the modem waiting
|
||||||
for a call, instead there is a getty process watching your modem(s). Another
|
for a call, instead there is a getty process watching your modem(s). Another
|
||||||
big difference is that you don't see what's happening, there is no screen
|
big difference is that you don't see what's happening, there is no screen
|
||||||
with the mailer or bbs picture on it. All programs run in the background. If
|
with the mailer or bbs picture on it. All programs run in the background. If
|
||||||
you don't like that, stop now and go back to your old DOS bbs. It's just the
|
you don't like that, stop now and go back to your old DOS bbs. It's just the
|
||||||
way everything is done.
|
way everything is done.
|
||||||
<P>
|
<P>
|
||||||
Programs that must start at specific times (events in DOS), are started from
|
Programs that must start at specific times (events in DOS), are started from
|
||||||
cron, this is the event scheduler for Linux (and other Unixes). With this
|
cron, this is the event scheduler for Linux (and other Unixes). With this
|
||||||
program maintenance can be started, polls created etc. For starting programs
|
program maintenance can be started, polls created etc. For starting programs
|
||||||
when they are needed there is a taskmanager loaded at system bootup. This
|
when they are needed there is a taskmanager loaded at system bootup. This
|
||||||
taskmanager "watches" the semafore directory of the bbs and will start what
|
taskmanager "watches" the semafore directory of the bbs and will start what
|
||||||
is needed.
|
is needed.
|
||||||
<P> <P>
|
<P> <P>
|
||||||
|
|
||||||
<H3>Waiting for a call .....</H3>
|
<H3>Waiting for a call .....</H3>
|
||||||
<P>
|
<P>
|
||||||
Under Linux this is done with the mgetty program, this is the
|
Under Linux this is done with the mgetty program, this is the
|
||||||
process that is connected with each modem (or ISDN adapter) and waits for a
|
process that is connected with each modem (or ISDN adapter) and waits for a
|
||||||
call. The mgetty program (written by Gert Doering, gert@greenie.muc.de) will
|
call. The mgetty program (written by Gert Doering, gert@greenie.muc.de) will
|
||||||
detect the call, and find out what or who did make the call. It can detect
|
detect the call, and find out what or who did make the call. It can detect
|
||||||
incoming humans who want a login prompt, PPP calls from users who want to
|
incoming humans who want a login prompt, PPP calls from users who want to
|
||||||
make a PPP connection (browsing your BBS whith netscape for example), A fax
|
make a PPP connection (browsing your BBS whith netscape for example), A fax
|
||||||
machine trying to deliver a fax and finally a mailer trying to establish
|
machine trying to deliver a fax and finally a mailer trying to establish
|
||||||
an EMSI, FSC-0006 or FSC-0001 session. The mgetty program is responsible for
|
an EMSI, FSC-0006 or FSC-0001 session. The mgetty program is responsible for
|
||||||
starting the right client programs. How to do this is explained in the
|
starting the right client programs. How to do this is explained in the
|
||||||
installation manuals, but be sure to compile it with Fido and PPP support.
|
installation manuals, but be sure to compile it with Fido and PPP support.
|
||||||
<P> <P>
|
<P> <P>
|
||||||
|
|
||||||
<H3>A Human is calling.</H3>
|
<H3>A Human is calling.</H3>
|
||||||
<P>
|
<P>
|
||||||
This could be a bbs user. For each user to login to your bbs there must be a
|
This could be a bbs user. For each user to login to your bbs there must be a
|
||||||
unix account. They automatic create such an account the first time they login
|
unix account. They automatic create such an account the first time they login
|
||||||
with the <b>bbs</b> account. During the creation of their account the shell that is
|
with the <b>bbs</b> account. During the creation of their account the shell that is
|
||||||
installed for there account is the mbsebbs binary, so that's the only thing
|
installed for there account is the mbsebbs binary, so that's the only thing
|
||||||
that they get if they call in. When they logout the bbs, or drop carrier etc,
|
that they get if they call in. When they logout the bbs, or drop carrier etc,
|
||||||
the session is ended and mgetty takes over the line again.
|
the session is ended and mgetty takes over the line again.
|
||||||
Note that they will never can get a Unix shell
|
Note that they will never can get a Unix shell
|
||||||
unless you install a <b>door</b> in the bbs that calls a shell for them.
|
unless you install a <b>door</b> in the bbs that calls a shell for them.
|
||||||
<P>
|
<P>
|
||||||
There are probably more accounts on your system that can callin, <b>mbse</b> is
|
There are probably more accounts on your system that can callin, <b>mbse</b> is
|
||||||
such an account, this is the MBSE BBS maintenance account. This user will
|
such an account, this is the MBSE BBS maintenance account. This user will
|
||||||
get the shell prompt. Use good passwords for shell accounts, and never change
|
get the shell prompt. Use good passwords for shell accounts, and never change
|
||||||
your setup so that the <b>root</b> user can directly login except from the console.
|
your setup so that the <b>root</b> user can directly login except from the console.
|
||||||
If you need root access, login as <b>mbse</b> and type <b>su</b> at the prompt to become
|
If you need root access, login as <b>mbse</b> and type <b>su</b> at the prompt to become
|
||||||
root. You might consider installing SSH on your system for remote maintenance.
|
root. You might consider installing SSH on your system for remote maintenance.
|
||||||
<P> <P>
|
<P> <P>
|
||||||
|
|
||||||
<H3>A PPP call is detected.</H3>
|
<H3>A PPP call is detected.</H3>
|
||||||
<P>
|
<P>
|
||||||
Installing a PPP server on your system is beyound the scope of this project.
|
Installing a PPP server on your system is beyound the scope of this project.
|
||||||
However if you did install it, users can login your bbs with their favourite
|
However if you did install it, users can login your bbs with their favourite
|
||||||
browser and use your bbs. Note that the necessary tools to automatic create
|
browser and use your bbs. Note that the necessary tools to automatic create
|
||||||
newsgroups don't exist at this time. With the proper setup you can automatic
|
newsgroups don't exist at this time. With the proper setup you can automatic
|
||||||
create and maintain html pages for the file areas.
|
create and maintain html pages for the file areas.
|
||||||
<P> <P>
|
<P> <P>
|
||||||
|
|
||||||
<H3>A mailer call is detected.</h3>
|
<H3>A mailer call is detected.</h3>
|
||||||
<P>
|
<P>
|
||||||
If a mailer is detected by mgetty, the <b>mbcico</b> program is started and will
|
If a mailer is detected by mgetty, the <b>mbcico</b> program is started and will
|
||||||
take over from mgetty. It will establish a mail session with the caller and
|
take over from mgetty. It will establish a mail session with the caller and
|
||||||
the mail and or files will be exchanged just like any DOS mailer would do.
|
the mail and or files will be exchanged just like any DOS mailer would do.
|
||||||
After the call, mbcico will hangup and mgetty will take control of your modem
|
After the call, mbcico will hangup and mgetty will take control of your modem
|
||||||
again. If there is any mail received, mbcico will place the semafore <b>mailin</b>
|
again. If there is any mail received, mbcico will place the semafore <b>mailin</b>
|
||||||
so that another process can take care of the received mail. Mbcico will also
|
so that another process can take care of the received mail. Mbcico will also
|
||||||
detect some IEMSI terminal programs (Frontdoor), and will start the bbs.
|
detect some IEMSI terminal programs (Frontdoor), and will start the bbs.
|
||||||
<P> <P>
|
<P> <P>
|
||||||
|
|
||||||
<h3>There is mail in the inbound</h3>
|
<h3>There is mail in the inbound</h3>
|
||||||
<P>
|
<P>
|
||||||
As I said before, if the <b>mailin</b> semafore is present, the task manager will
|
As I said before, if the <b>mailin</b> semafore is present, the task manager will
|
||||||
then start the <b>mbfido</b> program that will toss the mail, process any files
|
then start the <b>mbfido</b> program that will toss the mail, process any files
|
||||||
received and if necessary it will create other semafore's for example to link
|
received and if necessary it will create other semafore's for example to link
|
||||||
the message bases, start the nodelist compiler etc. Note that this can be done
|
the message bases, start the nodelist compiler etc. Note that this can be done
|
||||||
while there may be a new mailsession going on, a bbs user is online, it doesn't
|
while there may be a new mailsession going on, a bbs user is online, it doesn't
|
||||||
matter. Processing mail and files can be done real multitasking without any
|
matter. Processing mail and files can be done real multitasking without any
|
||||||
damage to other processes.
|
damage to other processes.
|
||||||
<P> <P>
|
<P> <P>
|
||||||
|
|
||||||
<H3>It's time to poll a node</h3>
|
<H3>It's time to poll a node</h3>
|
||||||
<P>
|
<P>
|
||||||
At the time that you whish to poll a node, let cron create "poll" requests.
|
At the time that you whish to poll a node, let cron create "poll" requests.
|
||||||
When a poll is created, the semafore <b>scanout</b> is also created.
|
When a poll is created, the semafore <b>scanout</b> is also created.
|
||||||
The taskmanager will then start mbcico at regular intervals so that mail will
|
The taskmanager will then start mbcico at regular intervals so that mail will
|
||||||
get out. If there is no more mail to send, the <b>scanout</b> semafore is removed.
|
get out. If there is no more mail to send, the <b>scanout</b> semafore is removed.
|
||||||
If a timeslot ends, you can just remove the "poll" requests that didn't succeed.
|
If a timeslot ends, you can just remove the "poll" requests that didn't succeed.
|
||||||
<P> <P>
|
<P> <P>
|
||||||
|
|
||||||
<H3>It's Zone Mail Hour, so now what</h3>
|
<H3>It's Zone Mail Hour, so now what</h3>
|
||||||
<P>
|
<P>
|
||||||
Relax, if you have netmail ready for nodes the
|
Relax, if you have netmail ready for nodes the
|
||||||
mailer script will try to send these mails to those nodes. If it was crash
|
mailer script will try to send these mails to those nodes. If it was crash
|
||||||
mail, and the destination was a non CM node, the mailer will try to send those
|
mail, and the destination was a non CM node, the mailer will try to send those
|
||||||
mails too. Note that other crashmails are send anytime. Also note that packed
|
mails too. Note that other crashmails are send anytime. Also note that packed
|
||||||
mail and files are not send during ZMH. If a node calls you during ZMH he will
|
mail and files are not send during ZMH. If a node calls you during ZMH he will
|
||||||
get everything that's waiting, including packed mail and files. The task manager
|
get everything that's waiting, including packed mail and files. The task manager
|
||||||
(more on that later) calculates the Zone Mail Hour from UTC time, you don't
|
(more on that later) calculates the Zone Mail Hour from UTC time, you don't
|
||||||
have to change anything for summer- and wintertime.
|
have to change anything for summer- and wintertime.
|
||||||
<P> <P>
|
<P> <P>
|
||||||
|
|
||||||
<H3>Daily maintenane</h3>
|
<H3>Daily maintenane</h3>
|
||||||
<P>
|
<P>
|
||||||
This is started by cron jobs. There is no need to take
|
This is started by cron jobs. There is no need to take
|
||||||
your bbs lines down during maintenance, you can do it any time of the day.
|
your bbs lines down during maintenance, you can do it any time of the day.
|
||||||
I have made several scripts for this, daily, weekly and monthly.
|
I have made several scripts for this, daily, weekly and monthly.
|
||||||
<P> <P>
|
<P> <P>
|
||||||
|
|
||||||
<h3>How about system load</h3>
|
<h3>How about system load</h3>
|
||||||
<P>
|
<P>
|
||||||
Because Linux is a 32 bit os, not bothered with a graphical user interface
|
Because Linux is a 32 bit os, not bothered with a graphical user interface
|
||||||
(unless you install it), it has all the time in the world to serve your
|
(unless you install it), it has all the time in the world to serve your
|
||||||
bbs programs. Background programs are build to release time to the Linux os,
|
bbs programs. Background programs are build to release time to the Linux os,
|
||||||
they don't need to run fast because it's background processing. The bbs and
|
they don't need to run fast because it's background processing. The bbs and
|
||||||
the mailer, have a low server load although there is no timerelease build
|
the mailer, have a low server load although there is no timerelease build
|
||||||
in. Only the bbs has some short moments when it needs a lot of your system,
|
in. Only the bbs has some short moments when it needs a lot of your system,
|
||||||
for example when a user logs in and scans for new mail. The bbs I run is a
|
for example when a user logs in and scans for new mail. The bbs I run is a
|
||||||
486-DX4 100 MHz, 20 MB ram, with 2 analogue lines, this seems to work fine.
|
486-DX4 100 MHz, 20 MB ram, with 2 analogue lines, this seems to work fine.
|
||||||
When this system's MOBO died, I used a 386DX33 for several months with
|
When this system's MOBO died, I used a 386DX33 for several months with
|
||||||
20 MB ram, and the only thing users ever noticed was that scanning for new
|
20 MB ram, and the only thing users ever noticed was that scanning for new
|
||||||
mail was slower. I think this is the slowest harware that will work.
|
mail was slower. I think this is the slowest harware that will work.
|
||||||
However, you must always use 16550A uarts for the COM ports. For best
|
However, you must always use 16550A uarts for the COM ports. For best
|
||||||
performance use SCSI disks. I noticed that old 5"FH SCSI disks perform better
|
performance use SCSI disks. I noticed that old 5"FH SCSI disks perform better
|
||||||
for bbs usage then modern EIDE disks. This is probably caused by the fact that
|
for bbs usage then modern EIDE disks. This is probably caused by the fact that
|
||||||
the kernel needs more time for the cheap IDE bus.
|
the kernel needs more time for the cheap IDE bus.
|
||||||
If you want to use X11 on your bbs, you need more ram and a faster CPU or a
|
If you want to use X11 on your bbs, you need more ram and a faster CPU or a
|
||||||
separate machine via a lan and export the display to that machine.
|
separate machine via a lan and export the display to that machine.
|
||||||
<P> <P>
|
<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" width="33" height="35"> Go Back</A>
|
||||||
</BLOCKQUOTE>
|
</BLOCKQUOTE>
|
||||||
</BODY>
|
</BODY>
|
||||||
</HTML>
|
</HTML>
|
||||||
|
|
||||||
|
@ -1,101 +1,101 @@
|
|||||||
<HTML>
|
<HTML>
|
||||||
<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">
|
||||||
<META name="author" lang="en" "content="Michiel Broek">
|
<META name="author" lang="en" content="Michiel Broek">
|
||||||
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
||||||
<META name="description" lang="en" content="MBSE BBS Manual">
|
<META name="description" lang="en" content="MBSE BBS Manual">
|
||||||
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
||||||
<TITLE>Fidonet Standard Commitee documents.</TITLE>
|
<TITLE>Fidonet Standard Commitee documents.</TITLE>
|
||||||
<LINK rel=stylesheet HREF="../manual.css">
|
<LINK rel=stylesheet HREF="../manual.css">
|
||||||
</HEAD>
|
</HEAD>
|
||||||
<BODY>
|
<BODY>
|
||||||
<BLOCKQUOTE>
|
<BLOCKQUOTE>
|
||||||
<h5>Last update 11-Aug-2001</h5>
|
<h5>Last update 11-Aug-2001</h5>
|
||||||
<P> <P>
|
<P> <P>
|
||||||
|
|
||||||
<h1>Fidonet Technical Standards</h1>
|
<h1>Fidonet Technical Standards</h1>
|
||||||
|
|
||||||
<h3>Introduction</h3>
|
<h3>Introduction</h3>
|
||||||
<P>
|
<P>
|
||||||
This is an overview of used documents for the development of the MBSE BBS
|
This is an overview of used documents for the development of the MBSE BBS
|
||||||
package. Note that there are more documents, but only the relevant and valid
|
package. Note that there are more documents, but only the relevant and valid
|
||||||
documents are present here. Also note that these documents are just imported
|
documents are present here. Also note that these documents are just imported
|
||||||
into html documents without any changes.
|
into html documents without any changes.
|
||||||
<P>
|
<P>
|
||||||
Michiel Broek.
|
Michiel Broek.
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<hr>
|
<hr>
|
||||||
<h3>FSC Documents</h3>
|
<h3>FSC Documents</h3>
|
||||||
<ul>
|
<ul>
|
||||||
<li><a href="fsc-0035.html">FSC-0035 Transparant Gateways to and from FidoNet, Michael Shiels</a>
|
<li><a href="fsc-0035.html">FSC-0035 Transparant Gateways to and from FidoNet, Michael Shiels</a>
|
||||||
<li><a href="fsc-0039.html">FSC-0039 A type-2 packet extension proposal M.Howard</a>
|
<li><a href="fsc-0039.html">FSC-0039 A type-2 packet extension proposal M.Howard</a>
|
||||||
<li><a href="fsc-0046.html">FSC-0046 A Product Identifier for FidoNet Message Handlers, J.Homrighausen</a>
|
<li><a href="fsc-0046.html">FSC-0046 A Product Identifier for FidoNet Message Handlers, J.Homrighausen</a>
|
||||||
<li><a href="fsc-0048.html">FSC-0048 A Proposed type-2 packet extension, J.Vroonhof</a>
|
<li><a href="fsc-0048.html">FSC-0048 A Proposed type-2 packet extension, J.Vroonhof</a>
|
||||||
<li><a href="fsc-0049.html">FSC-0049 A proposal for passing domain information during FTS-0006 sessions, B.Hartman</a>
|
<li><a href="fsc-0049.html">FSC-0049 A proposal for passing domain information during FTS-0006 sessions, B.Hartman</a>
|
||||||
<li><a href="fsc-0050.html">FSC-0050 A character set identifier for FidoNet message editors, T.Sundblom</a>
|
<li><a href="fsc-0050.html">FSC-0050 A character set identifier for FidoNet message editors, T.Sundblom</a>
|
||||||
<li><a href="fsc-0053.html">FSC-0053 Specifications for the ^aFLAGS field, J.Homrighausen</a>
|
<li><a href="fsc-0053.html">FSC-0053 Specifications for the ^aFLAGS field, J.Homrighausen</a>
|
||||||
<li><a href="fsc-0056.html">FSC-0056 EMSI/IEMSI Protocol Definition, J.Homrighausen</a>
|
<li><a href="fsc-0056.html">FSC-0056 EMSI/IEMSI Protocol Definition, J.Homrighausen</a>
|
||||||
<li><a href="fsc-0057.html">FSC-0057 Conference Managers - Specifications For Requests, F.Fabris, J.Homrighausen</a>
|
<li><a href="fsc-0057.html">FSC-0057 Conference Managers - Specifications For Requests, F.Fabris, J.Homrighausen</a>
|
||||||
<li><a href="fsc-0059.html">FSC-0059 Newsgroup Interchange within FidoNet, J.Decker</a>
|
<li><a href="fsc-0059.html">FSC-0059 Newsgroup Interchange within FidoNet, J.Decker</a>
|
||||||
<li><a href="fsc-0062.html">FSC-0062 Nodelist Flag indicating Online Times, D.Thomas</a>
|
<li><a href="fsc-0062.html">FSC-0062 Nodelist Flag indicating Online Times, D.Thomas</a>
|
||||||
<li><a href="fsc-0070.html">FSC-0070 Improving FidoNet/UseNet Gating and Dupe checking, F.Arnoud</a>
|
<li><a href="fsc-0070.html">FSC-0070 Improving FidoNet/UseNet Gating and Dupe checking, F.Arnoud</a>
|
||||||
<li><a href="fsc-0072.html">FSC-0072 The HYDRA file transfer protocol, J.Homrighausen, A.Lenz</a>
|
<li><a href="fsc-0072.html">FSC-0072 The HYDRA file transfer protocol, J.Homrighausen, A.Lenz</a>
|
||||||
<li><a href="fsc-0087.html">FSC-0087 File forwarding in FidoNet technology networks, R.Williamson</a>
|
<li><a href="fsc-0087.html">FSC-0087 File forwarding in FidoNet technology networks, R.Williamson</a>
|
||||||
<li><a href="fsc-0088.html">FSC-0088 Compatibility and Link Qualifier Extensions for EMSI Sessions, R.Williamson</a>
|
<li><a href="fsc-0088.html">FSC-0088 Compatibility and Link Qualifier Extensions for EMSI Sessions, R.Williamson</a>
|
||||||
<li><a href="fsc-0091.html">FSC-0091 ISDN nodelist flags (rev.002), A.Lenz</a>
|
<li><a href="fsc-0091.html">FSC-0091 ISDN nodelist flags (rev.002), A.Lenz</a>
|
||||||
<li><a href="fsc-0092.html">FSC-0092 New control lines for forwarded messages, M.Hohner</a>
|
<li><a href="fsc-0092.html">FSC-0092 New control lines for forwarded messages, M.Hohner</a>
|
||||||
<li><a href="fsc-0093.html">FSC-0093 Reduced seen-by lines, F.Ellermann</a>
|
<li><a href="fsc-0093.html">FSC-0093 Reduced seen-by lines, F.Ellermann</a>
|
||||||
</ul>
|
</ul>
|
||||||
|
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<h3>FSP Documents</h3>
|
<h3>FSP Documents</h3>
|
||||||
<ul>
|
<ul>
|
||||||
<li><a href="fsp-1001.html">FSP-1001 Timezone information in FTN messages, O.Sorensen</a>
|
<li><a href="fsp-1001.html">FSP-1001 Timezone information in FTN messages, O.Sorensen</a>
|
||||||
<li><a href="fsp-1002.html">FSP-1002 Numeric reply indication in FTN subject lines, O.Sorensen</a>
|
<li><a href="fsp-1002.html">FSP-1002 Numeric reply indication in FTN subject lines, O.Sorensen</a>
|
||||||
<li><a href="fsp-1003.html">FSP-1003 Suggested use of Nodelist Fields, L.Kindness</a>
|
<li><a href="fsp-1003.html">FSP-1003 Suggested use of Nodelist Fields, L.Kindness</a>
|
||||||
<li><a href="fsp-1004.html">FSP-1004 Standard Fidonet Addressing, L.Kindness</a>
|
<li><a href="fsp-1004.html">FSP-1004 Standard Fidonet Addressing, L.Kindness</a>
|
||||||
<li><a href="fsp-1005.html">FSP-1005 Zone 2 nodelist flags, F.Ellermann</a>
|
<li><a href="fsp-1005.html">FSP-1005 Zone 2 nodelist flags, F.Ellermann</a>
|
||||||
<li><a href="fsp-1006.html">FSP-1006 Kludge for specifying e-mail reply addresses, R.v.d.Winkel</a>
|
<li><a href="fsp-1006.html">FSP-1006 Kludge for specifying e-mail reply addresses, R.v.d.Winkel</a>
|
||||||
<li><a href="fsp-1007.html">FSP-1007 Multiple recipient address specification to gateway, R.v.d.Winkel</a>
|
<li><a href="fsp-1007.html">FSP-1007 Multiple recipient address specification to gateway, R.v.d.Winkel</a>
|
||||||
<li><a href="fsp-1008.html">FSP-1008 New control lines for forwarded messages, M.Hohner</a>
|
<li><a href="fsp-1008.html">FSP-1008 New control lines for forwarded messages, M.Hohner</a>
|
||||||
<li><a href="fsp-1009.html">FSP-1009 Year 2000 issues in FTN software, M.Hohner</a>
|
<li><a href="fsp-1009.html">FSP-1009 Year 2000 issues in FTN software, M.Hohner</a>
|
||||||
<li><a href="fsp-1010.html">FSP-1010 Via kludge line specification, C. Turner and J. Homrighausen</a>
|
<li><a href="fsp-1010.html">FSP-1010 Via kludge line specification, C. Turner and J. Homrighausen</a>
|
||||||
<li><a href="fsp-1011.html">FSP-1011 BinkP - a protocol for transferring Fidonet mail over reliable connections, Dima Maloff</a>
|
<li><a href="fsp-1011.html">FSP-1011 BinkP - a protocol for transferring Fidonet mail over reliable connections, Dima Maloff</a>
|
||||||
</ul>
|
</ul>
|
||||||
|
|
||||||
|
|
||||||
<P>
|
<P>
|
||||||
<h3>FTA Documents</h3>
|
<h3>FTA Documents</h3>
|
||||||
<ul>
|
<ul>
|
||||||
<li><a href="fta-1005.html">FTA-1005 FTSC Product ID</a>
|
<li><a href="fta-1005.html">FTA-1005 FTSC Product ID</a>
|
||||||
<li><a href="ftscprod.html">FTSC Product codes list</A>
|
<li><a href="ftscprod.html">FTSC Product codes list</A>
|
||||||
</ul>
|
</ul>
|
||||||
|
|
||||||
|
|
||||||
<P>
|
<P>
|
||||||
<h3>FTS Documents</h3>
|
<h3>FTS Documents</h3>
|
||||||
<ul>
|
<ul>
|
||||||
<li><a href="fts-0001.html">FTS-0001 A basic FidoNet(r) technical standard, R.Bush</a>
|
<li><a href="fts-0001.html">FTS-0001 A basic FidoNet(r) technical standard, R.Bush</a>
|
||||||
<li>FTS-0002 Obsoleted by FTS-0005
|
<li>FTS-0002 Obsoleted by FTS-0005
|
||||||
<li>FTS-0003 Obsoleted by FTS-0006
|
<li>FTS-0003 Obsoleted by FTS-0006
|
||||||
<li><a href="fts-0004.html">FTS-0004 Echomail specification, B.Hartman</a>
|
<li><a href="fts-0004.html">FTS-0004 Echomail specification, B.Hartman</a>
|
||||||
<li>FTS-0005 Obsoleted by FTS-5000
|
<li>FTS-0005 Obsoleted by FTS-5000
|
||||||
<li><a href="fts-0006.html">FTS-0006 YOOHOO and YOOHOO/2U2, V.Perriello</a>
|
<li><a href="fts-0006.html">FTS-0006 YOOHOO and YOOHOO/2U2, V.Perriello</a>
|
||||||
<li><a href="fts-0007.html">FTS-0007 SEAlink protocol extension, P.Becker</a>
|
<li><a href="fts-0007.html">FTS-0007 SEAlink protocol extension, P.Becker</a>
|
||||||
<li><a href="fts-0008.html">FTS-0008 Bark file-request protocol extension, P.Becker</a>
|
<li><a href="fts-0008.html">FTS-0008 Bark file-request protocol extension, P.Becker</a>
|
||||||
<li><a href="fts-0009.html">FTS-0009 Message identification and reply linkage, J.Nutt</a>
|
<li><a href="fts-0009.html">FTS-0009 Message identification and reply linkage, J.Nutt</a>
|
||||||
<li><a href="fts-4001.html">FTS-4001 Addressing Control Paragraphs, Goran Eriksson</a>
|
<li><a href="fts-4001.html">FTS-4001 Addressing Control Paragraphs, Goran Eriksson</a>
|
||||||
<li><a href="fts-5000.html">FTS-5000 The distribution nodelist, David Hallford</a>
|
<li><a href="fts-5000.html">FTS-5000 The distribution nodelist, David Hallford</a>
|
||||||
<li><a href="fts-5001.html">FTS-5001 Nodelist flags and user flags, David Hallford</a>
|
<li><a href="fts-5001.html">FTS-5001 Nodelist flags and user flags, David Hallford</a>
|
||||||
</ul>
|
</ul>
|
||||||
|
|
||||||
<HR>
|
<HR>
|
||||||
|
|
||||||
<A HREF="../index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Index" Border="0" width="33" height="35">Back to Index</A>
|
<A HREF="../index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Index" Border="0" width="33" height="35">Back to Index</A>
|
||||||
</BLOCKQUOTE>
|
</BLOCKQUOTE>
|
||||||
</BODY>
|
</BODY>
|
||||||
</HTML>
|
</HTML>
|
||||||
|
|
||||||
|
762
html/gwnews.html
762
html/gwnews.html
@ -1,381 +1,381 @@
|
|||||||
<HTML>
|
<HTML>
|
||||||
<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">
|
||||||
<META name="author" lang="en" "content="Michiel Broek">
|
<META name="author" lang="en" content="Michiel Broek">
|
||||||
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
||||||
<META name="description" lang="en" content="MBSE BBS Manual">
|
<META name="description" lang="en" content="MBSE BBS Manual">
|
||||||
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
||||||
<TITLE>MBSE BBS - Internet gateway - INN.</TITLE>
|
<TITLE>MBSE BBS - Internet gateway - INN.</TITLE>
|
||||||
<LINK rel=stylesheet HREF="manual.css">
|
<LINK rel=stylesheet HREF="manual.css">
|
||||||
</HEAD>
|
</HEAD>
|
||||||
<BODY>
|
<BODY>
|
||||||
<BLOCKQUOTE>
|
<BLOCKQUOTE>
|
||||||
<h5>Last update 10-Apr-2001</h5>
|
<h5>Last update 10-Apr-2001</h5>
|
||||||
<P> <P>
|
<P> <P>
|
||||||
|
|
||||||
<H1 ALIGN="CENTER">MBSE BBS - Internet Gateway - INN.</H1>
|
<H1 ALIGN="CENTER">MBSE BBS - Internet Gateway - INN.</H1>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<H3>SETUP INND</H3>
|
<H3>SETUP INND</H3>
|
||||||
<P>
|
<P>
|
||||||
Below are the files that you need to setup for INN news. I used inn-2.2.2 on
|
Below are the files that you need to setup for INN news. I used inn-2.2.2 on
|
||||||
my system. It is configured to install in /opt/news with the command
|
my system. It is configured to install in /opt/news with the command
|
||||||
<strong>./configure --prefix=/opt/news</strong> during the installation of
|
<strong>./configure --prefix=/opt/news</strong> during the installation of
|
||||||
inn.
|
inn.
|
||||||
<P>
|
<P>
|
||||||
<hr>
|
<hr>
|
||||||
<pre>
|
<pre>
|
||||||
<code>
|
<code>
|
||||||
## $Revision$
|
## $Revision$
|
||||||
## inn.conf -- inn configuration data
|
## inn.conf -- inn configuration data
|
||||||
## Format:
|
## Format:
|
||||||
## <parameter>:<whitespace><value>
|
## <parameter>:<whitespace><value>
|
||||||
##
|
##
|
||||||
## See the inn.conf(5) man page for a full description of each
|
## See the inn.conf(5) man page for a full description of each
|
||||||
## of these options
|
## of these options
|
||||||
##
|
##
|
||||||
## Blank values are allowed for certain parameters
|
## Blank values are allowed for certain parameters
|
||||||
## ---------------------------------
|
## ---------------------------------
|
||||||
# All parameters must exist
|
# All parameters must exist
|
||||||
#
|
#
|
||||||
organization: MBSE BBS Development Site
|
organization: MBSE BBS Development Site
|
||||||
server: localhost
|
server: localhost
|
||||||
pathhost: news.mbse.nl
|
pathhost: news.mbse.nl
|
||||||
moderatormailer:
|
moderatormailer:
|
||||||
domain: mbse.nl
|
domain: mbse.nl
|
||||||
fromhost: news.mbse.nl
|
fromhost: news.mbse.nl
|
||||||
pathalias:
|
pathalias:
|
||||||
complaints: abuse@f2802.n280.z2.fidonet.org
|
complaints: abuse@f2802.n280.z2.fidonet.org
|
||||||
mta: /usr/sbin/sendmail -oi %s
|
mta: /usr/sbin/sendmail -oi %s
|
||||||
mailcmd: /opt/news/bin/innmail
|
mailcmd: /opt/news/bin/innmail
|
||||||
checkincludedtext: false
|
checkincludedtext: false
|
||||||
maxforks: 10
|
maxforks: 10
|
||||||
maxartsize: 1000000
|
maxartsize: 1000000
|
||||||
nicekids: 4
|
nicekids: 4
|
||||||
nicenewnews: 0
|
nicenewnews: 0
|
||||||
verifycancels: false
|
verifycancels: false
|
||||||
logcancelcomm: false
|
logcancelcomm: false
|
||||||
wanttrash: false
|
wanttrash: false
|
||||||
remembertrash: true
|
remembertrash: true
|
||||||
linecountfuzz: 0
|
linecountfuzz: 0
|
||||||
peertimeout: 3600
|
peertimeout: 3600
|
||||||
clienttimeout: 600
|
clienttimeout: 600
|
||||||
allownewnews: true
|
allownewnews: true
|
||||||
localmaxartsize: 1000000
|
localmaxartsize: 1000000
|
||||||
logartsize: true
|
logartsize: true
|
||||||
logipaddr: true
|
logipaddr: true
|
||||||
logsitename: true
|
logsitename: true
|
||||||
maxconnections: 50
|
maxconnections: 50
|
||||||
artcutoff: 14
|
artcutoff: 14
|
||||||
icdsynccount: 10
|
icdsynccount: 10
|
||||||
hiscachesize: 0
|
hiscachesize: 0
|
||||||
readertrack: false
|
readertrack: false
|
||||||
strippostcc: false
|
strippostcc: false
|
||||||
status: 0
|
status: 0
|
||||||
timer: 0
|
timer: 0
|
||||||
readerswhenstopped: false
|
readerswhenstopped: false
|
||||||
noreader: false
|
noreader: false
|
||||||
extendeddbz: false
|
extendeddbz: false
|
||||||
nnrpdoverstats: false
|
nnrpdoverstats: false
|
||||||
storeonxref: true
|
storeonxref: true
|
||||||
nnrpdcheckart: true
|
nnrpdcheckart: true
|
||||||
storemsgid: true
|
storemsgid: true
|
||||||
usecontrolchan: false
|
usecontrolchan: false
|
||||||
mergetogroups: false
|
mergetogroups: false
|
||||||
backoffauth: false
|
backoffauth: false
|
||||||
backoffdb: /opt/news/db/backoff
|
backoffdb: /opt/news/db/backoff
|
||||||
backoffpostfast: 0L
|
backoffpostfast: 0L
|
||||||
backoffpostslow: 1L
|
backoffpostslow: 1L
|
||||||
backofftrigger: 10000L
|
backofftrigger: 10000L
|
||||||
mimeversion:
|
mimeversion:
|
||||||
mimecontenttype:
|
mimecontenttype:
|
||||||
mimeencoding:
|
mimeencoding:
|
||||||
refusecybercancels: false
|
refusecybercancels: false
|
||||||
activedenable: false
|
activedenable: false
|
||||||
activedupdate: 30
|
activedupdate: 30
|
||||||
activedport: 1119
|
activedport: 1119
|
||||||
nnrpperlauth: false
|
nnrpperlauth: false
|
||||||
#
|
#
|
||||||
#
|
#
|
||||||
# These options are unlikely to need changing in most situations
|
# These options are unlikely to need changing in most situations
|
||||||
#
|
#
|
||||||
chaninacttime: 600
|
chaninacttime: 600
|
||||||
chanretrytime: 300
|
chanretrytime: 300
|
||||||
pauseretrytime: 300
|
pauseretrytime: 300
|
||||||
nntplinklog: false
|
nntplinklog: false
|
||||||
nntpactsync: 200
|
nntpactsync: 200
|
||||||
badiocount: 5
|
badiocount: 5
|
||||||
blockbackoff: 120
|
blockbackoff: 120
|
||||||
#
|
#
|
||||||
# ---------------------------------
|
# ---------------------------------
|
||||||
# Changing these options can have an effect on the way articles are
|
# Changing these options can have an effect on the way articles are
|
||||||
# stored and may require recreating the spool and/or database files
|
# stored and may require recreating the spool and/or database files
|
||||||
#
|
#
|
||||||
wireformat: false
|
wireformat: false
|
||||||
xrefslave: false
|
xrefslave: false
|
||||||
nnrpdposthost:
|
nnrpdposthost:
|
||||||
nnrpdpostport: 119
|
nnrpdpostport: 119
|
||||||
spoolfirst: false
|
spoolfirst: false
|
||||||
writelinks: true
|
writelinks: true
|
||||||
storageapi: false
|
storageapi: false
|
||||||
articlemmap: false
|
articlemmap: false
|
||||||
overviewmmap: true
|
overviewmmap: true
|
||||||
bindaddress: all
|
bindaddress: all
|
||||||
sourceaddress: any
|
sourceaddress: any
|
||||||
port: 119
|
port: 119
|
||||||
#
|
#
|
||||||
## Keywords-in-overview options
|
## Keywords-in-overview options
|
||||||
## Enabling this without stopping innd and deleting the existing overview
|
## Enabling this without stopping innd and deleting the existing overview
|
||||||
## database and adding will probably confuse a lot of things. You must
|
## database and adding will probably confuse a lot of things. You must
|
||||||
## have compiled this support in too.
|
## have compiled this support in too.
|
||||||
#
|
#
|
||||||
keywords: false
|
keywords: false
|
||||||
keylimit: 512
|
keylimit: 512
|
||||||
keyartlimit: 100000
|
keyartlimit: 100000
|
||||||
keymaxwords: 250
|
keymaxwords: 250
|
||||||
#
|
#
|
||||||
# Other options
|
# Other options
|
||||||
innflags:
|
innflags:
|
||||||
doinnwatch: true
|
doinnwatch: true
|
||||||
innwatchsleeptime: 600
|
innwatchsleeptime: 600
|
||||||
pgpverify: false
|
pgpverify: false
|
||||||
controlfailnotice: false
|
controlfailnotice: false
|
||||||
logcycles: 3
|
logcycles: 3
|
||||||
innwatchpauseload: 1500
|
innwatchpauseload: 1500
|
||||||
innwatchhiload: 2000
|
innwatchhiload: 2000
|
||||||
innwatchloload: 1000
|
innwatchloload: 1000
|
||||||
innwatchspoolspace: 8000
|
innwatchspoolspace: 8000
|
||||||
innwatchbatchspace: 800
|
innwatchbatchspace: 800
|
||||||
innwatchlibspace: 25000
|
innwatchlibspace: 25000
|
||||||
innwatchspoolnodes: 200
|
innwatchspoolnodes: 200
|
||||||
docnfsstat: false
|
docnfsstat: false
|
||||||
#
|
#
|
||||||
# ---------------------------------
|
# ---------------------------------
|
||||||
# Paths to various aspects of the news system
|
# Paths to various aspects of the news system
|
||||||
#
|
#
|
||||||
pathnews: /opt/news
|
pathnews: /opt/news
|
||||||
pathbin: /opt/news/bin
|
pathbin: /opt/news/bin
|
||||||
pathfilter: /opt/news/bin/filter
|
pathfilter: /opt/news/bin/filter
|
||||||
pathcontrol: /opt/news/bin/control
|
pathcontrol: /opt/news/bin/control
|
||||||
pathdb: /opt/news/db
|
pathdb: /opt/news/db
|
||||||
pathetc: /opt/news/etc
|
pathetc: /opt/news/etc
|
||||||
pathrun: /opt/news/run
|
pathrun: /opt/news/run
|
||||||
pathlog: /opt/news/log
|
pathlog: /opt/news/log
|
||||||
pathhttp: /opt/news/log
|
pathhttp: /opt/news/log
|
||||||
pathtmp: /opt/news/tmp
|
pathtmp: /opt/news/tmp
|
||||||
pathspool: /opt/news/spool
|
pathspool: /opt/news/spool
|
||||||
patharticles: /opt/news/spool/articles
|
patharticles: /opt/news/spool/articles
|
||||||
pathoverview: /opt/news/spool/overview
|
pathoverview: /opt/news/spool/overview
|
||||||
pathoutgoing: /opt/news/spool/outgoing
|
pathoutgoing: /opt/news/spool/outgoing
|
||||||
pathincoming: /opt/news/spool/incoming
|
pathincoming: /opt/news/spool/incoming
|
||||||
patharchive: /opt/news/spool/archive
|
patharchive: /opt/news/spool/archive
|
||||||
pathuniover: /opt/news/spool/uniover
|
pathuniover: /opt/news/spool/uniover
|
||||||
overviewname: .overview
|
overviewname: .overview
|
||||||
#
|
#
|
||||||
# ---------------------------------
|
# ---------------------------------
|
||||||
#
|
#
|
||||||
</code>
|
</code>
|
||||||
</pre>
|
</pre>
|
||||||
<hr>
|
<hr>
|
||||||
|
|
||||||
<pre>
|
<pre>
|
||||||
## $Revision$
|
## $Revision$
|
||||||
## expire.ctl - expire control file
|
## expire.ctl - expire control file
|
||||||
## Format:
|
## Format:
|
||||||
## /remember/:<keep>
|
## /remember/:<keep>
|
||||||
## <patterns>:<modflag>:<keep>:<default>:<purge>
|
## <patterns>:<modflag>:<keep>:<default>:<purge>
|
||||||
## First line gives history retention; other lines specify expiration
|
## First line gives history retention; other lines specify expiration
|
||||||
## for newsgroups. Must have a "*:A:..." line which is the default.
|
## for newsgroups. Must have a "*:A:..." line which is the default.
|
||||||
## <patterns> wildmat-style patterns for the newsgroups
|
## <patterns> wildmat-style patterns for the newsgroups
|
||||||
## <modflag> Pick one of M U A -- modifies pattern to be only
|
## <modflag> Pick one of M U A -- modifies pattern to be only
|
||||||
## moderated, unmoderated, or all groups
|
## moderated, unmoderated, or all groups
|
||||||
## <keep> Mininum number of days to keep article
|
## <keep> Mininum number of days to keep article
|
||||||
## <default> Default number of days to keep the article
|
## <default> Default number of days to keep the article
|
||||||
## <purge> Flush article after this many days
|
## <purge> Flush article after this many days
|
||||||
## <keep>, <default>, and <purge> can be floating-point numbers or the
|
## <keep>, <default>, and <purge> can be floating-point numbers or the
|
||||||
## word "never." Times are based on when received unless -p is used;
|
## word "never." Times are based on when received unless -p is used;
|
||||||
## see expire.8
|
## see expire.8
|
||||||
|
|
||||||
## If article expires before 14 days, we still remember it for 14 days in
|
## If article expires before 14 days, we still remember it for 14 days in
|
||||||
## case we get offered it again. Depending on what you use for the innd
|
## case we get offered it again. Depending on what you use for the innd
|
||||||
## -c flag and how paranoid you are about old news, you might want to
|
## -c flag and how paranoid you are about old news, you might want to
|
||||||
## make this 28, 30, etc.
|
## make this 28, 30, etc.
|
||||||
/remember/:14
|
/remember/:14
|
||||||
|
|
||||||
## Keep for 1-10 days, allow Expires headers to work.
|
## Keep for 1-10 days, allow Expires headers to work.
|
||||||
*:A:1:10:never
|
*:A:1:10:never
|
||||||
|
|
||||||
fido.*:A:1:30:60
|
fido.*:A:1:30:60
|
||||||
comp.*:A:1:30:60
|
comp.*:A:1:30:60
|
||||||
local.*:A:1:30:60
|
local.*:A:1:30:60
|
||||||
nl.*:A:1:30:60
|
nl.*:A:1:30:60
|
||||||
|
|
||||||
## Some particular groups stay forever.
|
## Some particular groups stay forever.
|
||||||
# Keep FAQ's for a month, so they're always available
|
# Keep FAQ's for a month, so they're always available
|
||||||
#*.answers:M:1:35:90
|
#*.answers:M:1:35:90
|
||||||
news.announce.*:M:1:35:90
|
news.announce.*:M:1:35:90
|
||||||
|
|
||||||
# Some other recommendations. Uncomment if you want
|
# Some other recommendations. Uncomment if you want
|
||||||
# .announce groups tend to be low-traffic, high signal.
|
# .announce groups tend to be low-traffic, high signal.
|
||||||
# *.announce:M:1:30:90
|
# *.announce:M:1:30:90
|
||||||
# Weather forecasts
|
# Weather forecasts
|
||||||
# *.weather:A:1:2:7
|
# *.weather:A:1:2:7
|
||||||
# test posts
|
# test posts
|
||||||
# *.test:A:1:1:1
|
# *.test:A:1:1:1
|
||||||
|
|
||||||
## Some particular groups stay forever.
|
## Some particular groups stay forever.
|
||||||
# dc.dining*:A:never:never:never
|
# dc.dining*:A:never:never:never
|
||||||
# uunet*:A:never:never:never
|
# uunet*:A:never:never:never
|
||||||
</pre>
|
</pre>
|
||||||
<hr>
|
<hr>
|
||||||
<pre>
|
<pre>
|
||||||
## $Revision$
|
## $Revision$
|
||||||
## Mailing addresses for moderators.
|
## Mailing addresses for moderators.
|
||||||
## Format:
|
## Format:
|
||||||
## <newsgroup>:<pathname>
|
## <newsgroup>:<pathname>
|
||||||
## First match found is used.
|
## First match found is used.
|
||||||
## <newsgroup> Shell-style newsgroup pattern or specific newsgroup
|
## <newsgroup> Shell-style newsgroup pattern or specific newsgroup
|
||||||
## <pathname> Mail address, "%s" becomes newgroup name with dots
|
## <pathname> Mail address, "%s" becomes newgroup name with dots
|
||||||
## changed to dashes.
|
## changed to dashes.
|
||||||
|
|
||||||
## Russian hierarchies
|
## Russian hierarchies
|
||||||
fido7.*:%s@fido7.ru
|
fido7.*:%s@fido7.ru
|
||||||
medlux.*:%s@news.medlux.ru
|
medlux.*:%s@news.medlux.ru
|
||||||
relcom.*:%s@moderators.relcom.ru
|
relcom.*:%s@moderators.relcom.ru
|
||||||
|
|
||||||
## Direct all public hierarchies to the master moderator database.
|
## Direct all public hierarchies to the master moderator database.
|
||||||
*:%s@moderators.isc.org
|
*:%s@moderators.isc.org
|
||||||
</pre>
|
</pre>
|
||||||
<hr>
|
<hr>
|
||||||
<pre>
|
<pre>
|
||||||
## $Revision$
|
## $Revision$
|
||||||
## newsfeeds - determine where Usenet articles get sent
|
## newsfeeds - determine where Usenet articles get sent
|
||||||
## Format:
|
## Format:
|
||||||
## site[/exclude,exclude...]\
|
## site[/exclude,exclude...]\
|
||||||
## :pattern,pattern...[/distrib,distrib...]\
|
## :pattern,pattern...[/distrib,distrib...]\
|
||||||
## :flag,flag...\
|
## :flag,flag...\
|
||||||
## :param
|
## :param
|
||||||
## Summary of flags:
|
## Summary of flags:
|
||||||
## <size Article must be less then size bytes.
|
## <size Article must be less then size bytes.
|
||||||
## >size Article must be more then size bytes.
|
## >size Article must be more then size bytes.
|
||||||
## Aitems Article checks -- d (must have Distribution header)
|
## Aitems Article checks -- d (must have Distribution header)
|
||||||
## p (don't check for site in Path header)
|
## p (don't check for site in Path header)
|
||||||
## c (no control messages) C (only control messages)
|
## c (no control messages) C (only control messages)
|
||||||
## e (all groups must exist).
|
## e (all groups must exist).
|
||||||
## Bhigh/low Internal buffer size before writing to output.
|
## Bhigh/low Internal buffer size before writing to output.
|
||||||
## Fname Name of the spool file.
|
## Fname Name of the spool file.
|
||||||
## Gcount Crossposts limited to count groups.
|
## Gcount Crossposts limited to count groups.
|
||||||
## H[count] Article must have less then count hops; default is 1.
|
## H[count] Article must have less then count hops; default is 1.
|
||||||
## Isize Internal buffer size (if a file feed)
|
## Isize Internal buffer size (if a file feed)
|
||||||
## Nm Only moderated groups that match the patterns.
|
## Nm Only moderated groups that match the patterns.
|
||||||
## Nu Only unmoderated groups that match the patterns.
|
## Nu Only unmoderated groups that match the patterns.
|
||||||
## Ppriority Nice priority of channel or program feed.
|
## Ppriority Nice priority of channel or program feed.
|
||||||
## Ooriginator First field of X-Trace must match originator (wildmat).
|
## Ooriginator First field of X-Trace must match originator (wildmat).
|
||||||
## Ssize Start spooling if more than size bytes get queued.
|
## Ssize Start spooling if more than size bytes get queued.
|
||||||
## Ttype Feed types -- f (file) m (funnel; param names the
|
## Ttype Feed types -- f (file) m (funnel; param names the
|
||||||
## real entry) p (pipe to program) c (send to stdin
|
## real entry) p (pipe to program) c (send to stdin
|
||||||
## channel of param's sub-process) x (like c, but
|
## channel of param's sub-process) x (like c, but
|
||||||
## handles commands on stdin) x (log entry only).
|
## handles commands on stdin) x (log entry only).
|
||||||
## Witems What to write -- b (article bytesize) f (full path)
|
## Witems What to write -- b (article bytesize) f (full path)
|
||||||
## g (first newsgroup) h (Message-ID hash)
|
## g (first newsgroup) h (Message-ID hash)
|
||||||
## m (Message-ID) n (relative path) p (posted time)
|
## m (Message-ID) n (relative path) p (posted time)
|
||||||
## s (site that fed article) t (time received)
|
## s (site that fed article) t (time received)
|
||||||
## * (names of funnel feed-in's or all sites that get
|
## * (names of funnel feed-in's or all sites that get
|
||||||
## the article) N (Newsgroups header) D (Distribution
|
## the article) N (Newsgroups header) D (Distribution
|
||||||
## header) H (all headers) O (overview data)
|
## header) H (all headers) O (overview data)
|
||||||
## P (path header) R (replication information)
|
## P (path header) R (replication information)
|
||||||
## Param field depends on T flag. For Tf, relative paths are from the
|
## Param field depends on T flag. For Tf, relative paths are from the
|
||||||
## out.going directory. For Tp and Tc, it is a shell command to execute.
|
## out.going directory. For Tp and Tc, it is a shell command to execute.
|
||||||
## If a Tm refers to this entry (which will have its own T param) then "*"
|
## If a Tm refers to this entry (which will have its own T param) then "*"
|
||||||
## is expanded to all the funnel sites that triggered this one. Useful
|
## is expanded to all the funnel sites that triggered this one. Useful
|
||||||
## for spawning one mail process, e.g.
|
## for spawning one mail process, e.g.
|
||||||
##
|
##
|
||||||
## This file is complicated -- see newsfeeds.5!
|
## This file is complicated -- see newsfeeds.5!
|
||||||
|
|
||||||
## This is the local site.
|
## This is the local site.
|
||||||
## The "pattern" field gives the initial subscription list for
|
## The "pattern" field gives the initial subscription list for
|
||||||
## all other sites. You might want to put "!control,!junk,!<local>.*"
|
## all other sites. You might want to put "!control,!junk,!<local>.*"
|
||||||
## there. The "distrib" subfield limits incoming articles.
|
## there. The "distrib" subfield limits incoming articles.
|
||||||
##
|
##
|
||||||
## You can also have ME/bad.site: to refuse articles from a particular
|
## You can also have ME/bad.site: to refuse articles from a particular
|
||||||
## site (by matching the Path: entry). Other pseudo-sites may be put
|
## site (by matching the Path: entry). Other pseudo-sites may be put
|
||||||
## in here, to REFUSE certain types of 3rd-party cancel messages
|
## in here, to REFUSE certain types of 3rd-party cancel messages
|
||||||
## (See the "Cancel FAQ" news.admin.net-abuse.misc):
|
## (See the "Cancel FAQ" news.admin.net-abuse.misc):
|
||||||
## cyberspam Spam cancels, munged articles, binary postings
|
## cyberspam Spam cancels, munged articles, binary postings
|
||||||
## spewcancel just munged articles from runaway gateways
|
## spewcancel just munged articles from runaway gateways
|
||||||
## bincancel just binary postings to non-binaries groups
|
## bincancel just binary postings to non-binaries groups
|
||||||
##
|
##
|
||||||
## Note that refusing articles means you won't offer them to sites you feed
|
## Note that refusing articles means you won't offer them to sites you feed
|
||||||
|
|
||||||
## Default of everything to everybody except for junk, control, anything
|
## Default of everything to everybody except for junk, control, anything
|
||||||
## with "local" as the newsgroup prefix (i.e. matches "localhost.stuff") or
|
## with "local" as the newsgroup prefix (i.e. matches "localhost.stuff") or
|
||||||
## groups under foo. Articles posted to any group under alt.binaries.warez
|
## groups under foo. Articles posted to any group under alt.binaries.warez
|
||||||
## will not get propagated, even if they're cross posted to something that
|
## will not get propagated, even if they're cross posted to something that
|
||||||
## is.
|
## is.
|
||||||
ME\
|
ME\
|
||||||
:*,!junk,!control*,!foo.*/fido,local\
|
:*,!junk,!control*,!foo.*/fido,local\
|
||||||
::
|
::
|
||||||
|
|
||||||
## news.wxs.nl via rpost (suck)
|
## news.wxs.nl via rpost (suck)
|
||||||
news.wxs.nl/news.wxs.nl:*,!control,!junk,!fido.*,!iba.*,!local.*/!local,!fido::
|
news.wxs.nl/news.wxs.nl:*,!control,!junk,!fido.*,!iba.*,!local.*/!local,!fido::
|
||||||
|
|
||||||
## News overview
|
## News overview
|
||||||
# use this flag if storage api is used
|
# use this flag if storage api is used
|
||||||
#overview!:*:Tc,Ao,WhR,S30000:/opt/news/bin/overchan
|
#overview!:*:Tc,Ao,WhR,S30000:/opt/news/bin/overchan
|
||||||
# else
|
# else
|
||||||
overview!:*:Tc,WO,S30000:/opt/news/bin/overchan
|
overview!:*:Tc,WO,S30000:/opt/news/bin/overchan
|
||||||
|
|
||||||
</pre>
|
</pre>
|
||||||
<hr>
|
<hr>
|
||||||
<pre>
|
<pre>
|
||||||
## $Revision$
|
## $Revision$
|
||||||
## distrib.pats -- specify default Distribution header for newsgroups
|
## distrib.pats -- specify default Distribution header for newsgroups
|
||||||
## Format:
|
## Format:
|
||||||
## <weight>:<pattern>:<value>
|
## <weight>:<pattern>:<value>
|
||||||
## All articles are matched against all patterns, value to be used is the
|
## All articles are matched against all patterns, value to be used is the
|
||||||
## one with the highest weight.
|
## one with the highest weight.
|
||||||
## <weight> The weight assigned to this match, integer
|
## <weight> The weight assigned to this match, integer
|
||||||
## <pattern> Newsgroup name or single wildmat(3) pattern
|
## <pattern> Newsgroup name or single wildmat(3) pattern
|
||||||
## <value> Value of Distribution header.
|
## <value> Value of Distribution header.
|
||||||
##
|
##
|
||||||
##
|
##
|
||||||
## Uncomment to default all local.* groups to a distribution of local.
|
## Uncomment to default all local.* groups to a distribution of local.
|
||||||
#10:local.*:local
|
#10:local.*:local
|
||||||
10:local.*:local
|
10:local.*:local
|
||||||
10:fido.*:fido
|
10:fido.*:fido
|
||||||
</pre>
|
</pre>
|
||||||
<hr>
|
<hr>
|
||||||
<pre>
|
<pre>
|
||||||
## $Revision$
|
## $Revision$
|
||||||
## nnrp.access - access file for on-campus NNTP sites
|
## nnrp.access - access file for on-campus NNTP sites
|
||||||
## Format:
|
## Format:
|
||||||
## <host>:<perm>:<user>:<pass>:<groups>
|
## <host>:<perm>:<user>:<pass>:<groups>
|
||||||
## <host>:</path/file>
|
## <host>:</path/file>
|
||||||
## Connecting host must be found in this file; the last match found is
|
## Connecting host must be found in this file; the last match found is
|
||||||
## used, so put defaults first.
|
## used, so put defaults first.
|
||||||
## <host> Wildcard name or IP address
|
## <host> Wildcard name or IP address
|
||||||
## <perm> R to read; P to post
|
## <perm> R to read; P to post
|
||||||
## <user> Username for authentication before posting
|
## <user> Username for authentication before posting
|
||||||
## <pass> Password, for same reason
|
## <pass> Password, for same reason
|
||||||
## <groups> Newsgroup patterns that can be read or not read
|
## <groups> Newsgroup patterns that can be read or not read
|
||||||
## </path/file> A second file to scan in the same format as this
|
## </path/file> A second file to scan in the same format as this
|
||||||
## To disable posting put a space in the <user> and <pass> fields, since
|
## To disable posting put a space in the <user> and <pass> fields, since
|
||||||
## there is no way for client to enter one.
|
## there is no way for client to enter one.
|
||||||
##
|
##
|
||||||
## Default is no access, no way to authentication, and no groups.
|
## Default is no access, no way to authentication, and no groups.
|
||||||
*::::!*
|
*::::!*
|
||||||
stdin:Read Post:::*
|
stdin:Read Post:::*
|
||||||
localhost:Read Post:::*
|
localhost:Read Post:::*
|
||||||
127.0.0.1:Read Post:::*
|
127.0.0.1:Read Post:::*
|
||||||
*.mbse.nl:Read Post:::*
|
*.mbse.nl:Read Post:::*
|
||||||
</pre>
|
</pre>
|
||||||
<hr>
|
<hr>
|
||||||
|
|
||||||
<A HREF="./intergate.html"><IMG SRC="images/larrow.gif" ALT="Back" Border="0" width="40" height="30">Go back</A>
|
<A HREF="./intergate.html"><IMG SRC="images/larrow.gif" ALT="Back" Border="0" width="40" height="30">Go back</A>
|
||||||
<A HREF="index.htm"><IMG SRC="images/b_arrow.gif" ALT="Home" Border="0" width="33" height="35">Go to main</A>
|
<A HREF="index.htm"><IMG SRC="images/b_arrow.gif" ALT="Home" Border="0" width="33" height="35">Go to main</A>
|
||||||
|
|
||||||
</BLOCKQUOTE>
|
</BLOCKQUOTE>
|
||||||
</BODY>
|
</BODY>
|
||||||
</HTML>
|
</HTML>
|
||||||
|
|
||||||
|
Binary file not shown.
Before Width: | Height: | Size: 11 KiB After Width: | Height: | Size: 11 KiB |
@ -1,54 +1,54 @@
|
|||||||
<HTML>
|
<HTML>
|
||||||
<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">
|
||||||
<META name="author" lang="en" "content="Michiel Broek">
|
<META name="author" lang="en" content="Michiel Broek">
|
||||||
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
||||||
<META name="description" lang="en" content="MBSE BBS Manual">
|
<META name="description" lang="en" content="MBSE BBS Manual">
|
||||||
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
||||||
<TITLE>Running a BBS under Linux.</TITLE>
|
<TITLE>Running a BBS under Linux.</TITLE>
|
||||||
<LINK rel=stylesheet HREF="manual.css">
|
<LINK rel=stylesheet HREF="manual.css">
|
||||||
</HEAD>
|
</HEAD>
|
||||||
<BODY>
|
<BODY>
|
||||||
<BLOCKQUOTE>
|
<BLOCKQUOTE>
|
||||||
<h5>Last update 03-Jul-2001</h5>
|
<h5>Last update 03-Jul-2001</h5>
|
||||||
<P> <P>
|
<P> <P>
|
||||||
<HTML>
|
<HTML>
|
||||||
<HEAD>
|
<HEAD>
|
||||||
<TITLE>Installing the BBS.</TITLE>
|
<TITLE>Installing the BBS.</TITLE>
|
||||||
</HEAD>
|
</HEAD>
|
||||||
|
|
||||||
<h1 ALIGN="CENTER">Installing the BBS.</h1>
|
<h1 ALIGN="CENTER">Installing the BBS.</h1>
|
||||||
|
|
||||||
|
|
||||||
<h3>Installing the BBS.</h3>
|
<h3>Installing the BBS.</h3>
|
||||||
<p>
|
<p>
|
||||||
Now you have shell scripts in ~/etc, most of them are called by cron, some
|
Now you have shell scripts in ~/etc, most of them are called by cron, some
|
||||||
are called during system startup and shutdown. You also have some default
|
are called during system startup and shutdown. You also have some default
|
||||||
configuration files, these are ttyinfo, modems, fidonet networks. In the
|
configuration files, these are ttyinfo, modems, fidonet networks. In the
|
||||||
default (english) directory you now have default menu datafiles and ansi
|
default (english) directory you now have default menu datafiles and ansi
|
||||||
screens. These are copies of my test system so you have to edit them to
|
screens. These are copies of my test system so you have to edit them to
|
||||||
build your own bbs.<br>
|
build your own bbs.<br>
|
||||||
Editing ansi screens can be done on a Linux system with <strong>duhdraw</strong>,
|
Editing ansi screens can be done on a Linux system with <strong>duhdraw</strong>,
|
||||||
this is available from 2:280/2802 as <strong>duhdraw.tgz</strong> (68 Kbytes).
|
this is available from 2:280/2802 as <strong>duhdraw.tgz</strong> (68 Kbytes).
|
||||||
The binaries are included in this archive, if you compile it yourself
|
The binaries are included in this archive, if you compile it yourself
|
||||||
it may give trouble so if the binaries work, use these.<br>
|
it may give trouble so if the binaries work, use these.<br>
|
||||||
Another editor is available from
|
Another editor is available from
|
||||||
<A HREF="http://www.drastic.net/bmdraw/">http://www.drastic.net/bmdraw/</A>,
|
<A HREF="http://www.drastic.net/bmdraw/">http://www.drastic.net/bmdraw/</A>,
|
||||||
you can find the tar.gz file in <A HREF="http://www.drastic.net/bmdraw/files/bmd022.tgz">
|
you can find the tar.gz file in <A HREF="http://www.drastic.net/bmdraw/files/bmd022.tgz">
|
||||||
http://www.drastic.net/bmdraw/files/bmd022.tgz</A>, it's about 36 Kbytes.
|
http://www.drastic.net/bmdraw/files/bmd022.tgz</A>, it's about 36 Kbytes.
|
||||||
This is also a thedraw clone for Linux. Note, at my system I needed to run it as root.<br>
|
This is also a thedraw clone for Linux. Note, at my system I needed to run it as root.<br>
|
||||||
You may also want to edit ~/etc/header.txt and ~/etc/footer.txt, these
|
You may also want to edit ~/etc/header.txt and ~/etc/footer.txt, these
|
||||||
files are the top and bottom of the newfiles/allfiles listings.
|
files are the top and bottom of the newfiles/allfiles listings.
|
||||||
|
|
||||||
<p>
|
<p>
|
||||||
<h3>the next step.</h3>
|
<h3>the next step.</h3>
|
||||||
<p>
|
<p>
|
||||||
The next step is the <a href="setup/index.htm">setup</a> of the bbs.
|
The next step is the <a href="setup/index.htm">setup</a> of the bbs.
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<A HREF="index.htm"><IMG SRC="images/b_arrow.gif" ALT="Back to Index" Border="0" width="33" height="35">Back to Index</A>
|
<A HREF="index.htm"><IMG SRC="images/b_arrow.gif" ALT="Back to Index" Border="0" width="33" height="35">Back to Index</A>
|
||||||
</blockquote>
|
</blockquote>
|
||||||
</BODY>
|
</BODY>
|
||||||
</HTML>
|
</HTML>
|
||||||
|
|
||||||
|
@ -1,102 +1,102 @@
|
|||||||
<HTML>
|
<HTML>
|
||||||
<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">
|
||||||
<META name="author" lang="en" "content="Michiel Broek">
|
<META name="author" lang="en" content="Michiel Broek">
|
||||||
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
||||||
<META name="description" lang="en" content="MBSE BBS Manual">
|
<META name="description" lang="en" content="MBSE BBS Manual">
|
||||||
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
||||||
<TITLE>MBSE BBS - Internet gateway.</TITLE>
|
<TITLE>MBSE BBS - Internet gateway.</TITLE>
|
||||||
<LINK rel=stylesheet HREF="manual.css">
|
<LINK rel=stylesheet HREF="manual.css">
|
||||||
</HEAD>
|
</HEAD>
|
||||||
<BODY>
|
<BODY>
|
||||||
<BLOCKQUOTE>
|
<BLOCKQUOTE>
|
||||||
<h5>Last update 26-Apr-2001</h5>
|
<h5>Last update 26-Apr-2001</h5>
|
||||||
<P> <P>
|
<P> <P>
|
||||||
|
|
||||||
<H1 ALIGN="CENTER">MBSE BBS - Internet Gateway.</H1>
|
<H1 ALIGN="CENTER">MBSE BBS - Internet Gateway.</H1>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<p align="center"><u><b>WARNING: THIS IS DIFFERENT FROM VERSION 0.33.14 AND UP</b></u></p>
|
<p align="center"><u><b>WARNING: THIS IS DIFFERENT FROM VERSION 0.33.14 AND UP</b></u></p>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<H3>Introduction.</H3>
|
<H3>Introduction.</H3>
|
||||||
<P>
|
<P>
|
||||||
Since version 0.33.14 the email gateway is build into MBSE BBS and since
|
Since version 0.33.14 the email gateway is build into MBSE BBS and since
|
||||||
version 0.33.15 the newsgateway is build into MBSE BBS. Since version 0.33.16 the
|
version 0.33.15 the newsgateway is build into MBSE BBS. Since version 0.33.16 the
|
||||||
newsgateway to UUCP nodes is added. To route
|
newsgateway to UUCP nodes is added. To route
|
||||||
email trafic to and from the internet you need a internet MTA. I stopped using
|
email trafic to and from the internet you need a internet MTA. I stopped using
|
||||||
<strong>sendmail</strong> for this because it gave too much trouble setting it
|
<strong>sendmail</strong> for this because it gave too much trouble setting it
|
||||||
up together with MBSE BBS.
|
up together with MBSE BBS.
|
||||||
Today I use <A HREF="http://www.postfix.org">Postfix</A>,
|
Today I use <A HREF="http://www.postfix.org">Postfix</A>,
|
||||||
a well documented, secure and easy to setup MTA. For the actual gate from
|
a well documented, secure and easy to setup MTA. For the actual gate from
|
||||||
Postfix to the BBS you I use <b>mbmail</b> which you need to add to the
|
Postfix to the BBS you I use <b>mbmail</b> which you need to add to the
|
||||||
Postfix configuration.<P>
|
Postfix configuration.<P>
|
||||||
<P>
|
<P>
|
||||||
There may be two reasons to create a gateway, one is to gate internet news and
|
There may be two reasons to create a gateway, one is to gate internet news and
|
||||||
email to the Fidonet bbs users, another reason may be that you want to make
|
email to the Fidonet bbs users, another reason may be that you want to make
|
||||||
echomail as news available on your system so that users can connect to your
|
echomail as news available on your system so that users can connect to your
|
||||||
bbs with their favourite browser an get the mail and news using pop3 and
|
bbs with their favourite browser an get the mail and news using pop3 and
|
||||||
nntp protocols. The setup is the same for both reasons so I will make one
|
nntp protocols. The setup is the same for both reasons so I will make one
|
||||||
description for the whole setup.
|
description for the whole setup.
|
||||||
<P> <P>
|
<P> <P>
|
||||||
|
|
||||||
<H3>Setup a newsgate node with inn.</H3>
|
<H3>Setup a newsgate node with inn.</H3>
|
||||||
<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. Just configure MBSE BBS to use the
|
||||||
newsserver of your ISP in screen 1.14 with mbsetup. All other users need
|
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
|
to run a newsserver on the bbs machine or another networked machine. You
|
||||||
could use <A HREF="http://www.isc.org">inn news</A> for a newsserver.
|
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
|
||||||
name of that area and echomail received in that area will automatic be
|
name of that area and echomail received in that area will automatic be
|
||||||
posted to that newsgroup. The command <b>mbfido news</b> will check all
|
posted to that newsgroup. The command <b>mbfido news</b> will check all
|
||||||
configured newsgroups for new newsarticles. If you set it up for the first
|
configured newsgroups for new newsarticles. If you set it up for the first
|
||||||
time you need to run <strong>mbfido news -learn</strong> to fill the dupes
|
time you need to run <strong>mbfido news -learn</strong> to fill the dupes
|
||||||
database for news with all the already existing news articles. If you skip
|
database for news with all the already existing news articles. If you skip
|
||||||
that, you may get a lot of old articles that will be gated. Just run that
|
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>.
|
||||||
<P> <P>
|
<P> <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.14 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>
|
||||||
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
|
||||||
name of that area and echomail received in that area will automatic be
|
name of that area and echomail received in that area will automatic be
|
||||||
posted to that newsgroup.
|
posted to that newsgroup.
|
||||||
<P> <P>
|
<P> <P>
|
||||||
|
|
||||||
<H3>Setup a newsgate via UUCP.</H3>
|
<H3>Setup a newsgate via UUCP.</H3>
|
||||||
<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.14 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
|
||||||
the domain part.
|
the domain part.
|
||||||
<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
|
||||||
name of that area and echomail received in that area will automatic be
|
name of that area and echomail received in that area will automatic be
|
||||||
posted to that newsgroup.
|
posted to that newsgroup.
|
||||||
<P> <P>
|
<P> <P>
|
||||||
|
|
||||||
<H3>Setup a email gate.</H3>
|
<H3>Setup a email gate.</H3>
|
||||||
<P>
|
<P>
|
||||||
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" width="33" height="35"> Go Back</A>
|
||||||
</BLOCKQUOTE>
|
</BLOCKQUOTE>
|
||||||
</BODY>
|
</BODY>
|
||||||
</HTML>
|
</HTML>
|
||||||
|
|
||||||
|
198
html/intro.html
198
html/intro.html
@ -1,99 +1,99 @@
|
|||||||
<HTML>
|
<HTML>
|
||||||
<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">
|
||||||
<META name="author" lang="en" "content="Michiel Broek">
|
<META name="author" lang="en" content="Michiel Broek">
|
||||||
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
||||||
<META name="description" lang="en" content="MBSE BBS Manual">
|
<META name="description" lang="en" content="MBSE BBS Manual">
|
||||||
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
||||||
<TITLE>Running a BBS under Linux.</TITLE>
|
<TITLE>Running a BBS under Linux.</TITLE>
|
||||||
<LINK rel=stylesheet HREF="manual.css">
|
<LINK rel=stylesheet HREF="manual.css">
|
||||||
</HEAD>
|
</HEAD>
|
||||||
<BODY>
|
<BODY>
|
||||||
<BLOCKQUOTE>
|
<BLOCKQUOTE>
|
||||||
<h5>Last update 28-Jan-2001</h5>
|
<h5>Last update 28-Jan-2001</h5>
|
||||||
<P> <P>
|
<P> <P>
|
||||||
<H1>Introduction to MBSE BBS.</H1>
|
<H1>Introduction to MBSE BBS.</H1>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<H3>Distribution.</H3>
|
<H3>Distribution.</H3>
|
||||||
<P>
|
<P>
|
||||||
There are only five official distribution sites for the mbse bbs package. They are:
|
There are only five official distribution sites for the mbse bbs package. They are:
|
||||||
<OL>
|
<OL>
|
||||||
<LI><A HREF="http://mbse.sourceforge.net">http://mbse.sourceforge.net</A> Primary site
|
<LI><A HREF="http://mbse.sourceforge.net">http://mbse.sourceforge.net</A> Primary site
|
||||||
<LI><A HREF="http://mbse.freezer-burn.org">http://mbse.freezer-burn.org</A> Mirror site
|
<LI><A HREF="http://mbse.freezer-burn.org">http://mbse.freezer-burn.org</A> Mirror site
|
||||||
<LI><A HREF="http://www.telematique.org/mbse">http://www.telematique.org/mbse</A> Mirror site
|
<LI><A HREF="http://www.telematique.org/mbse">http://www.telematique.org/mbse</A> Mirror site
|
||||||
<LI>fidonet node 2:280/2802 (+31-255-515973).
|
<LI>fidonet node 2:280/2802 (+31-255-515973).
|
||||||
<LI>fidonet node 2:280/2801 (+31-255-533858).
|
<LI>fidonet node 2:280/2801 (+31-255-533858).
|
||||||
</OL>
|
</OL>
|
||||||
If you find mbse bbs on another site it may be out of date. I have no control over these sites.
|
If you find mbse bbs on another site it may be out of date. I have no control over these sites.
|
||||||
New versions of mbse bbs are announced in the fidonet area LINUX_BBS. On the official fidonet
|
New versions of mbse bbs are announced in the fidonet area LINUX_BBS. On the official fidonet
|
||||||
nodes you can request the latest version with the magic MBSEBBS. You will then get a zip file,
|
nodes you can request the latest version with the magic MBSEBBS. You will then get a zip file,
|
||||||
in this zip file is the original tar.gz file. This is to let systems who only support 8.3
|
in this zip file is the original tar.gz file. This is to let systems who only support 8.3
|
||||||
filenames to pickup the distribution package. You can also subscribe to the mailinglist
|
filenames to pickup the distribution package. You can also subscribe to the mailinglist
|
||||||
<b>mbse-announce@lists.sourceforge.net</b> to receive announcements. This will also work for fidonet
|
<b>mbse-announce@lists.sourceforge.net</b> to receive announcements. This will also work for fidonet
|
||||||
systems if you send your netmail via the official fido/internet gateway. You can also
|
systems if you send your netmail via the official fido/internet gateway. You can also
|
||||||
subscribe online at <A HREF="http://lists.sourceforge.net/lists/listinfo/mbse-announce">sourceforge</A>
|
subscribe online at <A HREF="http://lists.sourceforge.net/lists/listinfo/mbse-announce">sourceforge</A>
|
||||||
<P> <P>
|
<P> <P>
|
||||||
|
|
||||||
<H3>History.</H3>
|
<H3>History.</H3>
|
||||||
<P>
|
<P>
|
||||||
At the end of 1997 I was looking for several BBS systems that could run on
|
At the end of 1997 I was looking for several BBS systems that could run on
|
||||||
Linux and it must be capable to run Fidonet mail. After reviewing almost
|
Linux and it must be capable to run Fidonet mail. After reviewing almost
|
||||||
all packages that were available at that time I found that there were no
|
all packages that were available at that time I found that there were no
|
||||||
packages that suited my needs. Some had the plain user interfaces that
|
packages that suited my needs. Some had the plain user interfaces that
|
||||||
my bbs users were used to but no Fidonet capabilities, others looked
|
my bbs users were used to but no Fidonet capabilities, others looked
|
||||||
awfull or were difficult to use by normal bbs users without Unix experience.
|
awfull or were difficult to use by normal bbs users without Unix experience.
|
||||||
I also didn't want to run shareware anymore, one day you pay for some program,
|
I also didn't want to run shareware anymore, one day you pay for some program,
|
||||||
and the next day support is over because the writer of that program decided
|
and the next day support is over because the writer of that program decided
|
||||||
to stop development or simply dissapears from the Fidonet stage. With all
|
to stop development or simply dissapears from the Fidonet stage. With all
|
||||||
Y2K problems ahead the solution should be Open Software so that you have
|
Y2K problems ahead the solution should be Open Software so that you have
|
||||||
the sources in case something goes wrong.
|
the sources in case something goes wrong.
|
||||||
One package was very interesting and had the look and feel of RemoteAcces,
|
One package was very interesting and had the look and feel of RemoteAcces,
|
||||||
that package was RapidBBS. There was only one problem, it had no Fidonet
|
that package was RapidBBS. There was only one problem, it had no Fidonet
|
||||||
capabilities. I rewrote the data structures and created a deamon that should
|
capabilities. I rewrote the data structures and created a deamon that should
|
||||||
control all bbs acivities. In march 1998 I started writing the mbfido program
|
control all bbs acivities. In march 1998 I started writing the mbfido program
|
||||||
that should handle all Fidonet mail and .tic files. In june 1998 the final
|
that should handle all Fidonet mail and .tic files. In june 1998 the final
|
||||||
message base format became JAM using the LoraBBS sources as a guide to create
|
message base format became JAM using the LoraBBS sources as a guide to create
|
||||||
the JAM libraries. The original JAMapi was not stable enough to do all the work
|
the JAM libraries. The original JAMapi was not stable enough to do all the work
|
||||||
that needed to be done.
|
that needed to be done.
|
||||||
<P>
|
<P>
|
||||||
In Juli 1998 the first version of MBSE BBS was installed on the bbs I have,
|
In Juli 1998 the first version of MBSE BBS was installed on the bbs I have,
|
||||||
on the second line. The first line was running McMail, GEcho and RA on a
|
on the second line. The first line was running McMail, GEcho and RA on a
|
||||||
Novell client while on the Linux box the mars_nwe emulator from Martin Stower
|
Novell client while on the Linux box the mars_nwe emulator from Martin Stower
|
||||||
was running. In november 1998 mbcico was created from ifcico from Eugene M.
|
was running. In november 1998 mbcico was created from ifcico from Eugene M.
|
||||||
Crosser. In Januari 1999 it did also compile and run on a Sun Sparcstation 2
|
Crosser. In Januari 1999 it did also compile and run on a Sun Sparcstation 2
|
||||||
system.
|
system.
|
||||||
<P>
|
<P>
|
||||||
In April 1999 the motherboard of the Linux server died, I replaced it with
|
In April 1999 the motherboard of the Linux server died, I replaced it with
|
||||||
the MOBO of one of the client machines. From that day on, MBSE BBS became the
|
the MOBO of one of the client machines. From that day on, MBSE BBS became the
|
||||||
only bbs running on my system, because I was short on serial port boards at
|
only bbs running on my system, because I was short on serial port boards at
|
||||||
that time. McMail and RA became history and MBSE BBS was on its own. From that
|
that time. McMail and RA became history and MBSE BBS was on its own. From that
|
||||||
day on, updates were almost daily, all users and up and downlinks showed that
|
day on, updates were almost daily, all users and up and downlinks showed that
|
||||||
there were plenty of bugs to solve. One month later most problems were solved.
|
there were plenty of bugs to solve. One month later most problems were solved.
|
||||||
<P>
|
<P>
|
||||||
In juli 1999 Jan van de Werken started beta testing MBSE BBS on his system.
|
In juli 1999 Jan van de Werken started beta testing MBSE BBS on his system.
|
||||||
In September 1999 MBSE BBS was public released for the first time.
|
In September 1999 MBSE BBS was public released for the first time.
|
||||||
<P> <P>
|
<P> <P>
|
||||||
|
|
||||||
<H3>Is it Y2K ready?</H3>
|
<H3>Is it Y2K ready?</H3>
|
||||||
<P>
|
<P>
|
||||||
There have been no problems since 1 januari 2000 with MBSE BBS. I do run
|
There have been no problems since 1 januari 2000 with MBSE BBS. I do run
|
||||||
pktdate by Tobias Ernst in the tosser, this solves problems with incoming
|
pktdate by Tobias Ernst in the tosser, this solves problems with incoming
|
||||||
mail. Due to the internal date format, this program should run until 2038,
|
mail. Due to the internal date format, this program should run until 2038,
|
||||||
just as long as Unix/Linux and the internet will function without changing
|
just as long as Unix/Linux and the internet will function without changing
|
||||||
the date format.
|
the date format.
|
||||||
<P> <P>
|
<P> <P>
|
||||||
|
|
||||||
<H3>Future plans.</H3>
|
<H3>Future plans.</H3>
|
||||||
<P>
|
<P>
|
||||||
Plans are to complete integrate news, email, www and chat into MBSE BBS. It
|
Plans are to complete integrate news, email, www and chat into MBSE BBS. It
|
||||||
should work for browsers about the same as with ANSI character terminals.
|
should work for browsers about the same as with ANSI character terminals.
|
||||||
<P> <P>
|
<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" width="33" height="35"> Go Back</A>
|
||||||
</BLOCKQUOTE>
|
</BLOCKQUOTE>
|
||||||
</BODY>
|
</BODY>
|
||||||
</HTML>
|
</HTML>
|
||||||
|
|
||||||
|
@ -1,70 +1,70 @@
|
|||||||
<HTML>
|
<HTML>
|
||||||
<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">
|
||||||
<META name="author" lang="en" "content="Michiel Broek">
|
<META name="author" lang="en" content="Michiel Broek">
|
||||||
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
||||||
<META name="description" lang="en" content="MBSE BBS Manual">
|
<META name="description" lang="en" content="MBSE BBS Manual">
|
||||||
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
||||||
<TITLE>Starting and stopping the BBS.</TITLE>
|
<TITLE>Starting and stopping the BBS.</TITLE>
|
||||||
<LINK rel=stylesheet HREF="manual.css">
|
<LINK rel=stylesheet HREF="manual.css">
|
||||||
</HEAD>
|
</HEAD>
|
||||||
<BODY>
|
<BODY>
|
||||||
<BLOCKQUOTE>
|
<BLOCKQUOTE>
|
||||||
<h5>Last update 06-Jun-2001</h5>
|
<h5>Last update 06-Jun-2001</h5>
|
||||||
<P> <P>
|
<P> <P>
|
||||||
|
|
||||||
<H1 ALIGN="CENTER">Starting and Stopping the BBS.</H1>
|
<H1 ALIGN="CENTER">Starting and Stopping the BBS.</H1>
|
||||||
<P>
|
<P>
|
||||||
Now it is time to check the starting and stopping of the BBS. As you have
|
Now it is time to check the starting and stopping of the BBS. As you have
|
||||||
installed everything, setup the BBS etc, you must check if the shutdown and
|
installed everything, setup the BBS etc, you must check if the shutdown and
|
||||||
reboot work properly. As root type <strong>shutdown -r now</strong> and
|
reboot work properly. As root type <strong>shutdown -r now</strong> and
|
||||||
watch the console. You should see messages that the BBS is closing while
|
watch the console. You should see messages that the BBS is closing while
|
||||||
the systems shuts down. This should be one of the first things to happen.
|
the systems shuts down. This should be one of the first things to happen.
|
||||||
Because Slackware up to version 7.0.0 is tricky to automatic install the shutdown scripts,
|
Because Slackware up to version 7.0.0 is tricky to automatic install the shutdown scripts,
|
||||||
you won't see this happen on older Slackware versions. If you want, you can edit
|
you won't see this happen on older Slackware versions. If you want, you can edit
|
||||||
/etc/rc.d/rc.6 and /etc/rc.d/rc.K and insert the line /opt/mbse/etc/rc.shutdown
|
/etc/rc.d/rc.6 and /etc/rc.d/rc.K and insert the line /opt/mbse/etc/rc.shutdown
|
||||||
at the proper places.<p>
|
at the proper places.<p>
|
||||||
|
|
||||||
When your system comes up again, one of the last messages before the login
|
When your system comes up again, one of the last messages before the login
|
||||||
prompt appears or just before X-windows starts, you should see messages that
|
prompt appears or just before X-windows starts, you should see messages that
|
||||||
the BBS is started.<P>
|
the BBS is started.<P>
|
||||||
|
|
||||||
Login as user <strong>mbse</strong> and check the logfiles if everything looks
|
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". You will then create
|
||||||
the first user of your BBS, this will be you, the sysop of course.
|
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. After all
|
||||||
this and if you have setup <strong>mgetty</strong> you may want to test if
|
this and 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>
|
||||||
|
|
||||||
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> As user
|
||||||
<strong>mbse</strong> go to the directory <strong>~/mbsebbs-0.33.xx</strong>.
|
<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.
|
||||||
Now that the crontab is installed, all maintenance will now work, automatic
|
Now that the crontab is installed, all maintenance will now work, automatic
|
||||||
dialout, scanning and tossing mail etc. In other words, the bbs is up and
|
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" width="33" height="35"> Go Back</A>
|
||||||
</BLOCKQUOTE>
|
</BLOCKQUOTE>
|
||||||
</BODY>
|
</BODY>
|
||||||
</HTML>
|
</HTML>
|
||||||
|
|
||||||
|
@ -1,37 +1,37 @@
|
|||||||
<HTML>
|
<HTML>
|
||||||
<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">
|
||||||
<META name="author" lang="en" "content="Michiel Broek">
|
<META name="author" lang="en" content="Michiel Broek">
|
||||||
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
||||||
<META name="description" lang="en" content="MBSE BBS Manual">
|
<META name="description" lang="en" content="MBSE BBS Manual">
|
||||||
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
||||||
<TITLE>Running a BBS under Linux.</TITLE>
|
<TITLE>Running a BBS under Linux.</TITLE>
|
||||||
<LINK rel=stylesheet HREF="manual.css">
|
<LINK rel=stylesheet HREF="manual.css">
|
||||||
</HEAD>
|
</HEAD>
|
||||||
<BODY>
|
<BODY>
|
||||||
<BLOCKQUOTE>
|
<BLOCKQUOTE>
|
||||||
<h5>Last update 28-Jan-2001</h5>
|
<h5>Last update 28-Jan-2001</h5>
|
||||||
<P> <P>
|
<P> <P>
|
||||||
<H1>MBSE BBS - Known bugs.</H1>
|
<H1>MBSE BBS - Known bugs.</H1>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
There are always more bugs, but these are known....
|
There are always more bugs, but these are known....
|
||||||
|
|
||||||
<UL>
|
<UL>
|
||||||
<LI>Reading of function keys in mbsebbs doesn't work always good, especially on
|
<LI>Reading of function keys in mbsebbs doesn't work always good, especially on
|
||||||
slow links and over PPP.
|
slow links and over PPP.
|
||||||
|
|
||||||
<LI>Memory leaks in mbfido during mailtoss.
|
<LI>Memory leaks in mbfido during mailtoss.
|
||||||
|
|
||||||
<LI>Problems with D'Bridge [1a] mailers.
|
<LI>Problems with D'Bridge [1a] mailers.
|
||||||
|
|
||||||
<LI>Sometimes binkp sessions hang on sending files during bidirectional transfers.
|
<LI>Sometimes binkp sessions hang on sending files during bidirectional transfers.
|
||||||
|
|
||||||
<LI>mbsetup crashes at several places if in system aka's the domain name is 12 characters long.
|
<LI>mbsetup crashes at several places if in system aka's the domain name is 12 characters long.
|
||||||
</UL>
|
</UL>
|
||||||
|
|
||||||
<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" width="33" height="35"> Go Back</A>
|
||||||
</BODY>
|
</BODY>
|
||||||
</HTML>
|
</HTML>
|
||||||
|
|
||||||
|
@ -1,39 +1,39 @@
|
|||||||
<HTML>
|
<HTML>
|
||||||
<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">
|
||||||
<META name="author" lang="en" "content="Michiel Broek">
|
<META name="author" lang="en" content="Michiel Broek">
|
||||||
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
||||||
<META name="description" lang="en" content="MBSE BBS Manual">
|
<META name="description" lang="en" content="MBSE BBS Manual">
|
||||||
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
||||||
<TITLE>Licenses.</TITLE>
|
<TITLE>Licenses.</TITLE>
|
||||||
<LINK rel=stylesheet HREF="../manual.css">
|
<LINK rel=stylesheet HREF="../manual.css">
|
||||||
</HEAD>
|
</HEAD>
|
||||||
<BODY>
|
<BODY>
|
||||||
<BLOCKQUOTE>
|
<BLOCKQUOTE>
|
||||||
<h5>Last update 29-Jan-2001</h5>
|
<h5>Last update 29-Jan-2001</h5>
|
||||||
<P> <P>
|
<P> <P>
|
||||||
|
|
||||||
<h1>Licenses.</h1>
|
<h1>Licenses.</h1>
|
||||||
|
|
||||||
<h3>Introduction</h3>
|
<h3>Introduction</h3>
|
||||||
<P>
|
<P>
|
||||||
This is an overview of the licenses that are valid for the use of MBSE BBS or
|
This is an overview of the licenses that are valid for the use of MBSE BBS or
|
||||||
parts of it.
|
parts of it.
|
||||||
<BR>
|
<BR>
|
||||||
Michiel Broek.
|
Michiel Broek.
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<h3>License Documents.</h3>
|
<h3>License Documents.</h3>
|
||||||
<ul>
|
<ul>
|
||||||
<li><a href="copying.html">GNU General Public License</a>
|
<li><a href="copying.html">GNU General Public License</a>
|
||||||
<li><a href="hydracom.html">Hydracom License</a>
|
<li><a href="hydracom.html">Hydracom License</a>
|
||||||
<li><a href="jam.html">JAM License</a>
|
<li><a href="jam.html">JAM License</a>
|
||||||
</ul>
|
</ul>
|
||||||
|
|
||||||
|
|
||||||
<A HREF="../index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Index" Border="0" width="33" height="35">Back to Index</A>
|
<A HREF="../index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Index" Border="0" width="33" height="35">Back to Index</A>
|
||||||
</BLOCKQUOTE>
|
</BLOCKQUOTE>
|
||||||
</BODY>
|
</BODY>
|
||||||
</HTML>
|
</HTML>
|
||||||
|
|
||||||
|
@ -1,127 +1,127 @@
|
|||||||
<HTML>
|
<HTML>
|
||||||
<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">
|
||||||
<META name="author" lang="en" "content="Michiel Broek">
|
<META name="author" lang="en" content="Michiel Broek">
|
||||||
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
||||||
<META name="description" lang="en" content="MBSE BBS Manual">
|
<META name="description" lang="en" content="MBSE BBS Manual">
|
||||||
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
||||||
<TITLE>MBSE BBS Menus - Control Codes in ANSI and ASCII files.</TITLE>
|
<TITLE>MBSE BBS Menus - Control Codes in ANSI and ASCII files.</TITLE>
|
||||||
<LINK rel=stylesheet HREF="../manual.css">
|
<LINK rel=stylesheet HREF="../manual.css">
|
||||||
</HEAD>
|
</HEAD>
|
||||||
<BODY>
|
<BODY>
|
||||||
<BLOCKQUOTE>
|
<BLOCKQUOTE>
|
||||||
<h5>Last update 27-Jun-2001</h5>
|
<h5>Last update 27-Jun-2001</h5>
|
||||||
<P> <P>
|
<P> <P>
|
||||||
|
|
||||||
<h1>MBSE BBS Control Codes in ANSI and ASCII files</h1>
|
<h1>MBSE BBS Control Codes in ANSI and ASCII files</h1>
|
||||||
<hr>
|
<hr>
|
||||||
|
|
||||||
|
|
||||||
<H3>Single Control characters</H3>
|
<H3>Single Control characters</H3>
|
||||||
<PRE>
|
<PRE>
|
||||||
Code Description
|
Code Description
|
||||||
---- ---------------------------------------
|
---- ---------------------------------------
|
||||||
A Wait for a key
|
A Wait for a key
|
||||||
B Print text above sec. level
|
B Print text above sec. level
|
||||||
F Control-code F
|
F Control-code F
|
||||||
K Control-code K
|
K Control-code K
|
||||||
P Wait one second
|
P Wait one second
|
||||||
U Control-code U
|
U Control-code U
|
||||||
|
|
||||||
|
|
||||||
</PRE>
|
</PRE>
|
||||||
The control-B syntax is: ^B<seclevel>^B<The text to show>^B<br>
|
The control-B syntax is: ^B<seclevel>^B<The text to show>^B<br>
|
||||||
For example: ^B32000^BThis is the text^B<br>
|
For example: ^B32000^BThis is the text^B<br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<H3>Control-F followed by:</H3>
|
<H3>Control-F followed by:</H3>
|
||||||
<PRE>
|
<PRE>
|
||||||
Code Description
|
Code Description
|
||||||
---- ---------------------------------------
|
---- ---------------------------------------
|
||||||
! Display transfer protocol
|
! Display transfer protocol
|
||||||
A Number of uploads
|
A Number of uploads
|
||||||
B Number of downloads
|
B Number of downloads
|
||||||
C Downloads in Kilobytes
|
C Downloads in Kilobytes
|
||||||
D Uploads in Kilobytes
|
D Uploads in Kilobytes
|
||||||
E Download plus upload Kilobytes
|
E Download plus upload Kilobytes
|
||||||
F Download Kilobyte limit
|
F Download Kilobyte limit
|
||||||
G Last transfer time
|
G Last transfer time
|
||||||
H Current file area number
|
H Current file area number
|
||||||
I Current file area description
|
I Current file area description
|
||||||
J Download files limit
|
J Download files limit
|
||||||
K Description of user limit
|
K Description of user limit
|
||||||
|
|
||||||
|
|
||||||
</PRE>
|
</PRE>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<H3>Control-K followed by:</H3>
|
<H3>Control-K followed by:</H3>
|
||||||
<PRE>
|
<PRE>
|
||||||
Code Description
|
Code Description
|
||||||
---- ---------------------------------------
|
---- ---------------------------------------
|
||||||
A Print date in format DD-MM-YYYY
|
A Print date in format DD-MM-YYYY
|
||||||
B Print time in HH:MM:SS
|
B Print time in HH:MM:SS
|
||||||
C Print date in DD-Mmm
|
C Print date in DD-Mmm
|
||||||
D Print date in DD-Mmm-YYYY
|
D Print date in DD-Mmm-YYYY
|
||||||
E Print locked port baudrate
|
E Print locked port baudrate
|
||||||
F Last caller
|
F Last caller
|
||||||
G Total users in userlist
|
G Total users in userlist
|
||||||
H Number of system calls
|
H Number of system calls
|
||||||
I Current message area number
|
I Current message area number
|
||||||
J Current message area description
|
J Current message area description
|
||||||
K Print random oneliner
|
K Print random oneliner
|
||||||
L Print number of messages in current area.
|
L Print number of messages in current area.
|
||||||
M Print users LastRead pointer of current message area.
|
M Print users LastRead pointer of current message area.
|
||||||
N Print users current e-mail mailbox name.
|
N Print users current e-mail mailbox name.
|
||||||
O Print number of messages in current e-mail box.
|
O Print number of messages in current e-mail box.
|
||||||
P Print users LastRead pointer of current e-mail box.
|
P Print users LastRead pointer of current e-mail box.
|
||||||
|
|
||||||
|
|
||||||
</PRE>
|
</PRE>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<H3>Control-U followed by:</H3>
|
<H3>Control-U followed by:</H3>
|
||||||
<PRE>
|
<PRE>
|
||||||
Code Description
|
Code Description
|
||||||
---- ---------------------------------------
|
---- ---------------------------------------
|
||||||
A User's full name
|
A User's full name
|
||||||
B User's location
|
B User's location
|
||||||
C User's voice phone
|
C User's voice phone
|
||||||
D User's data phone
|
D User's data phone
|
||||||
E User's last login date
|
E User's last login date
|
||||||
F User's first login date
|
F User's first login date
|
||||||
G User's last login time
|
G User's last login time
|
||||||
H User's security level
|
H User's security level
|
||||||
I User's total calls
|
I User's total calls
|
||||||
J User's time used today
|
J User's time used today
|
||||||
K User's connect time this session
|
K User's connect time this session
|
||||||
L User's time left today
|
L User's time left today
|
||||||
M User's screen length
|
M User's screen length
|
||||||
N User's first name
|
N User's first name
|
||||||
O User's last name
|
O User's last name
|
||||||
P User's graphics mode (On/Off)
|
P User's graphics mode (On/Off)
|
||||||
Q User's news bulletins (On/Off)
|
Q User's news bulletins (On/Off)
|
||||||
R User's hot-keys (On/Off)
|
R User's hot-keys (On/Off)
|
||||||
S User's daily time limit
|
S User's daily time limit
|
||||||
T User's date of birth
|
T User's date of birth
|
||||||
U User's messages posted
|
U User's messages posted
|
||||||
X User's language
|
X User's language
|
||||||
Y User's handle
|
Y User's handle
|
||||||
Z User's do not disturb flag (On/Off)
|
Z User's do not disturb flag (On/Off)
|
||||||
1 User's check for new mail (On/Off)
|
1 User's check for new mail (On/Off)
|
||||||
2 User's check for new files (On/Off)
|
2 User's check for new files (On/Off)
|
||||||
3 User's fullscreen editor (On/Off);
|
3 User's fullscreen editor (On/Off);
|
||||||
|
|
||||||
|
|
||||||
</PRE>
|
</PRE>
|
||||||
|
|
||||||
<HR>
|
<HR>
|
||||||
<A HREF="../"><IMG SRC="../images/b_arrow.gif" ALT="Index" BORDER=0 width="33" height="35"></A>
|
<A HREF="../"><IMG SRC="../images/b_arrow.gif" ALT="Index" BORDER=0 width="33" height="35"></A>
|
||||||
<A HREF="../">Main Index</A>
|
<A HREF="../">Main Index</A>
|
||||||
<A HREF="./"><IMG SRC="../images/larrow.gif" ALT="Back" BORDER=0 width="40" height="30"></A>
|
<A HREF="./"><IMG SRC="../images/larrow.gif" ALT="Back" BORDER=0 width="40" height="30"></A>
|
||||||
<A HREF="./">Menus Index</A>
|
<A HREF="./">Menus Index</A>
|
||||||
</BLOCKQUOTE>
|
</BLOCKQUOTE>
|
||||||
</BODY>
|
</BODY>
|
||||||
</HTML>
|
</HTML>
|
||||||
|
|
||||||
|
@ -1,166 +1,166 @@
|
|||||||
<HTML>
|
<HTML>
|
||||||
<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">
|
||||||
<META name="author" lang="en" "content="Michiel Broek">
|
<META name="author" lang="en" content="Michiel Broek">
|
||||||
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
||||||
<META name="description" lang="en" content="MBSE BBS Manual">
|
<META name="description" lang="en" content="MBSE BBS Manual">
|
||||||
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
||||||
<TITLE>MBSE BBS Menu System.</TITLE>
|
<TITLE>MBSE BBS Menu System.</TITLE>
|
||||||
<LINK rel=stylesheet HREF="../manual.css">
|
<LINK rel=stylesheet HREF="../manual.css">
|
||||||
</HEAD>
|
</HEAD>
|
||||||
<BODY>
|
<BODY>
|
||||||
<BLOCKQUOTE>
|
<BLOCKQUOTE>
|
||||||
<h5>Last update 27-Sep-2001</h5>
|
<h5>Last update 22-Oct-2001</h5>
|
||||||
<P> <P>
|
<P> <P>
|
||||||
|
|
||||||
<H1>MBSE BBS Menu System</H1>
|
<H1>MBSE BBS Menu System</H1>
|
||||||
<P ALIGN=CENTER>Menus sections:
|
<P ALIGN=CENTER>Menus sections:
|
||||||
<A HREF="menu0.html">Global menus</A>
|
<A HREF="menu0.html">Global menus</A>
|
||||||
<A HREF="menu100.html">File areas</A>
|
<A HREF="menu100.html">File areas</A>
|
||||||
<A HREF="menu200.html">Message areas</A>
|
<A HREF="menu200.html">Message areas</A>
|
||||||
<A HREF="menu300.html">User settings</A>
|
<A HREF="menu300.html">User settings</A>
|
||||||
<A HREF="menu400.html">Onliners</A>
|
<A HREF="menu400.html">Onliners</A>
|
||||||
<A HREF="menu500.html">BBS lists</A>
|
<A HREF="menu500.html">BBS lists</A>
|
||||||
<A HREF="control.html">ANSI Control Codes</A>
|
<A HREF="control.html">ANSI Control Codes</A>
|
||||||
</P>
|
</P>
|
||||||
<P>
|
<P>
|
||||||
<HR>
|
<HR>
|
||||||
</P>
|
</P>
|
||||||
|
|
||||||
<H3>Introduction.</H3>
|
<H3>Introduction.</H3>
|
||||||
<P>
|
<P>
|
||||||
One of the most powerfull features of the BBS is it's menu system. You
|
One of the most powerfull features of the BBS is it's menu system. You
|
||||||
have complete control over each individual menu item which can be restricted
|
have complete control over each individual menu item which can be restricted
|
||||||
according to criteria such as security levels.
|
according to criteria such as security levels.
|
||||||
<P> <P>
|
<P> <P>
|
||||||
|
|
||||||
<H3>ANSI Screens.</H3>
|
<H3>ANSI Screens.</H3>
|
||||||
<P>
|
<P>
|
||||||
For the menus to work properly you can draw ANSI screens, this
|
For the menus to work properly you can draw ANSI screens, this
|
||||||
is what the users will see. For Linux there is "Duh DRAW" written by Ben
|
is what the users will see. For Linux there is "Duh DRAW" written by Ben
|
||||||
Fowler, see sunsite.unc.edu /pub/Lunux/docs.
|
Fowler, see sunsite.unc.edu /pub/Lunux/docs.
|
||||||
If you can't find it or have no internet access, you can also use
|
If you can't find it or have no internet access, you can also use
|
||||||
THEDRAW. This utility can be found on many BBS'es around the world. Unfortunatly
|
THEDRAW. This utility can be found on many BBS'es around the world. Unfortunatly
|
||||||
it is a DOS program so you will need dosemu on your Linux box or a seperate
|
it is a DOS program so you will need dosemu on your Linux box or a seperate
|
||||||
DOS computer. You can define main screens and include screens for each
|
DOS computer. You can define main screens and include screens for each
|
||||||
menu, the include screen may for example show the keys that you have available
|
menu, the include screen may for example show the keys that you have available
|
||||||
in every menu. See the list of <A HREF="control.html">control codes</A>.
|
in every menu. See the list of <A HREF="control.html">control codes</A>.
|
||||||
<P> <P>
|
<P> <P>
|
||||||
|
|
||||||
<H3>Display lines.</H3>
|
<H3>Display lines.</H3>
|
||||||
<P>
|
<P>
|
||||||
It is also possible to display menu lines with the buildin display option.
|
It is also possible to display menu lines with the buildin display option.
|
||||||
The used colors are selectable, a normal color and a bright color.
|
The used colors are selectable, a normal color and a bright color.
|
||||||
The normal color is the default, you can toggle bright on and of using
|
The normal color is the default, you can toggle bright on and of using
|
||||||
the ^ in the display line. If you end a menu display line with a ; then
|
the ^ in the display line. If you end a menu display line with a ; then
|
||||||
no newline is send after that line. If you want to output teh ^ or ; characters
|
no newline is send after that line. If you want to output teh ^ or ; characters
|
||||||
you need to escape them with a backslash like this: \; or \^. The order of menu
|
you need to escape them with a backslash like this: \; or \^. The order of menu
|
||||||
entries is important.
|
entries is important.
|
||||||
<P> <P>
|
<P> <P>
|
||||||
|
|
||||||
<H3>Automatic commands.</H3>
|
<H3>Automatic commands.</H3>
|
||||||
<P>
|
<P>
|
||||||
A menu function is usually executed when a user presses the hot-key
|
A menu function is usually executed when a user presses the hot-key
|
||||||
assigned to that particular menu item. But menu functions can also be executed
|
assigned to that particular menu item. But menu functions can also be executed
|
||||||
automatically. Each menu item contains an AutoExec field. By default this
|
automatically. Each menu item contains an AutoExec field. By default this
|
||||||
field is set to No, but by toggling it to Yes, the menu item can be made
|
field is set to No, but by toggling it to Yes, the menu item can be made
|
||||||
to execute when it is played back (displayed) by the BBS. </P>
|
to execute when it is played back (displayed) by the BBS. </P>
|
||||||
<P>
|
<P>
|
||||||
As you read through the menu function types outlined in this chapter,
|
As you read through the menu function types outlined in this chapter,
|
||||||
you may come to realize that this is a very powerfull feature. For example,
|
you may come to realize that this is a very powerfull feature. For example,
|
||||||
when used with the menu function that displays a text file, you can design
|
when used with the menu function that displays a text file, you can design
|
||||||
very elaborate, graphical text file menus that you wouldn't normally be
|
very elaborate, graphical text file menus that you wouldn't normally be
|
||||||
able to display in a line-by-line menu. </P>
|
able to display in a line-by-line menu. </P>
|
||||||
<P>
|
<P>
|
||||||
Automatic menu execution can be used in many other instances as well.
|
Automatic menu execution can be used in many other instances as well.
|
||||||
Just to give you some ideas, it might be used to display a text file to
|
Just to give you some ideas, it might be used to display a text file to
|
||||||
users who have a security level equal to or greater than a certain level.
|
users who have a security level equal to or greater than a certain level.
|
||||||
Yet another use is to execute multiple function menus which are used to
|
Yet another use is to execute multiple function menus which are used to
|
||||||
execute several functions when a single command is entered.
|
execute several functions when a single command is entered.
|
||||||
<P> <P>
|
<P> <P>
|
||||||
|
|
||||||
<H3>Multiple languages.</H3>
|
<H3>Multiple languages.</H3>
|
||||||
<P>
|
<P>
|
||||||
For each language you can define a set of menus. Only for the default
|
For each language you can define a set of menus. Only for the default
|
||||||
language all menus must exist. It makes sense to make the filenames of
|
language all menus must exist. It makes sense to make the filenames of
|
||||||
your menus for each language the same and not to translate them. If a menu
|
your menus for each language the same and not to translate them. If a menu
|
||||||
is missing for a non default language, the menu from the default language
|
is missing for a non default language, the menu from the default language
|
||||||
path is used instead.
|
path is used instead.
|
||||||
<P> <P>
|
<P> <P>
|
||||||
|
|
||||||
<H3>Editing a menu.</H3>
|
<H3>Editing a menu.</H3>
|
||||||
<P>
|
<P>
|
||||||
The order of the menu lines in the setup is not important except for
|
The order of the menu lines in the setup is not important except for
|
||||||
the autoexec menus, they must be placed in the right order from start,
|
the autoexec menus, they must be placed in the right order from start,
|
||||||
ie. begin with the menu specific screen display, then the global include
|
ie. begin with the menu specific screen display, then the global include
|
||||||
display and finally show the prompt.
|
display and finally show the prompt.
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<IMG SRC="../images/e_menu.gif" Border="0">
|
<IMG SRC="../images/e_menu.gif" Border="0">
|
||||||
<OL>
|
<OL>
|
||||||
<LI><B>Selection key.</B> This is the key a user must press to activate
|
<LI><B>Selection key.</B> This is the key a user must press to activate
|
||||||
this menu. This field is ignored when AutoExec is set to Yes. </LI>
|
this menu. This field is ignored when AutoExec is set to Yes. </LI>
|
||||||
|
|
||||||
<LI><B>Type nr.</B> this is the menu type to execute. For a description
|
<LI><B>Type nr.</B> this is the menu type to execute. For a description
|
||||||
of all available types see below. </LI>
|
of all available types see below. </LI>
|
||||||
|
|
||||||
<LI><B>Optional data.</B> Some menus need optional data, for example the
|
<LI><B>Optional data.</B> Some menus need optional data, for example the
|
||||||
function goto another menu needs the name of that menu file here. </LI>
|
function goto another menu needs the name of that menu file here. </LI>
|
||||||
|
|
||||||
<LI><B>Display.</B> What is to be displayed to the user. You can use this instead
|
<LI><B>Display.</B> What is to be displayed to the user. You can use this instead
|
||||||
of ANSI screens.
|
of ANSI screens.
|
||||||
</LI>
|
</LI>
|
||||||
|
|
||||||
<LI><B>Security.</B> This is the minimum security level to execute this
|
<LI><B>Security.</B> This is the minimum security level to execute this
|
||||||
selection. The security is a level number combined with 32 bitmapped flags.
|
selection. The security is a level number combined with 32 bitmapped flags.
|
||||||
NOTE: level 0 and no flags means
|
NOTE: level 0 and no flags means
|
||||||
everyone can select this menu. Good for logout options and all other options
|
everyone can select this menu. Good for logout options and all other options
|
||||||
everyone must be able to execute. </LI>
|
everyone must be able to execute. </LI>
|
||||||
|
|
||||||
<LI><B>Min. age.</B> The minumum age the user must be to execute this selection.
|
<LI><B>Min. age.</B> The minumum age the user must be to execute this selection.
|
||||||
You may want to restrict access to certain areas to users older than 18
|
You may want to restrict access to certain areas to users older than 18
|
||||||
years. If you leave this to 0, every one can execute this menu. </LI>
|
years. If you leave this to 0, every one can execute this menu. </LI>
|
||||||
|
|
||||||
<LI><B>Max. lvl.</B> The maximum level a user must have to execute this
|
<LI><B>Max. lvl.</B> The maximum level a user must have to execute this
|
||||||
menu. If you leave this at 0 then the maximum level has no effect. </LI>
|
menu. If you leave this at 0 then the maximum level has no effect. </LI>
|
||||||
|
|
||||||
<LI><B>Password.</B> You can protect the menu selection with a password.
|
<LI><B>Password.</B> You can protect the menu selection with a password.
|
||||||
If this field is empty, no password check is done. </LI>
|
If this field is empty, no password check is done. </LI>
|
||||||
|
|
||||||
<LI><B>Credit.</B> How much credit a user must have to execute this menu
|
<LI><B>Credit.</B> How much credit a user must have to execute this menu
|
||||||
selection. This field is not in use yet. </LI>
|
selection. This field is not in use yet. </LI>
|
||||||
|
|
||||||
<LI><B>Lo-colors.</B> The normal display color for the display line.
|
<LI><B>Lo-colors.</B> The normal display color for the display line.
|
||||||
</LI>
|
</LI>
|
||||||
|
|
||||||
<LI><B>Hi-colors.</B> The bright display color for the display line.</LI>
|
<LI><B>Hi-colors.</B> The bright display color for the display line.</LI>
|
||||||
|
|
||||||
<LI><B>AutoExec.</B> If this is an automatic executed selection. </LI>
|
<LI><B>AutoExec.</B> If this is an automatic executed selection. </LI>
|
||||||
|
|
||||||
<LI><B>No door.sys</B> Suppress writing of a door.sys file in the users
|
<LI><B>No door.sys</B> Suppress writing of a door.sys file in the users
|
||||||
home directory. This item is only visible with menu type 7.</LI>
|
home directory. This item is only visible with menu type 7.</LI>
|
||||||
|
|
||||||
<LI><B>Y2K style</B> Writes the dates in the door.sys file in the new style,
|
<LI><B>Y2K style</B> Writes the dates in the door.sys file in the new style,
|
||||||
with 4 digit year numbers, else the old 2 digit style is used. This item
|
with 4 digit year numbers, else the old 2 digit style is used. This item
|
||||||
is only visible with menu type 7.</LI>
|
is only visible with menu type 7.</LI>
|
||||||
|
|
||||||
<LI><B>Use Comport</B> Writes real comport to the door.sys file, this is
|
<LI><B>Use Comport</B> Writes real comport to the door.sys file, this is
|
||||||
for dosemu with the vmodem patch. This item is only visible with menu
|
for dosemu with the vmodem patch. This item is only visible with menu
|
||||||
type 7.</LI>
|
type 7.</LI>
|
||||||
|
|
||||||
</OL>
|
</OL>
|
||||||
<P> <P>
|
<P> <P>
|
||||||
|
|
||||||
<H3>Final warning.</H3>
|
<H3>Final warning.</H3>
|
||||||
<P>
|
<P>
|
||||||
If a submenu is missing, the BBS falls back to the main menu. This menu
|
If a submenu is missing, the BBS falls back to the main menu. This menu
|
||||||
must be called "main" (or else set another name in the global
|
must be called "main" (or else set another name in the global
|
||||||
setup) or your BBS won't start and complain. Submenus may be nested 50
|
setup) or your BBS won't start and complain. Submenus may be nested 50
|
||||||
levels deep.
|
levels deep.
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<A HREF="../index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" BORDER=0 width="33" height="35"> Back</A>
|
<A HREF="../index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" BORDER=0 width="33" height="35"> Back</A>
|
||||||
</BLOCKQUOTE>
|
</BLOCKQUOTE>
|
||||||
</BODY>
|
</BODY>
|
||||||
</HTML>
|
</HTML>
|
||||||
|
@ -1,176 +1,182 @@
|
|||||||
<HTML>
|
<HTML>
|
||||||
<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">
|
||||||
<META name="author" lang="en" "content="Michiel Broek">
|
<META name="author" lang="en" content="Michiel Broek">
|
||||||
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
||||||
<META name="description" lang="en" content="MBSE BBS Manual">
|
<META name="description" lang="en" content="MBSE BBS Manual">
|
||||||
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
||||||
<TITLE>MBSE BBS Menus - Global Menus.</TITLE>
|
<TITLE>MBSE BBS Menus - Global Menus.</TITLE>
|
||||||
<LINK rel=stylesheet HREF="../manual.css">
|
<LINK rel=stylesheet HREF="../manual.css">
|
||||||
</HEAD>
|
</HEAD>
|
||||||
<BODY>
|
<BODY>
|
||||||
<BLOCKQUOTE>
|
<BLOCKQUOTE>
|
||||||
<h5>Last update 26-Sep-2001</h5>
|
<h5>Last update 22-Oct-2001</h5>
|
||||||
<P> <P>
|
<P> <P>
|
||||||
|
|
||||||
<h1>MBSE BBS Global Menus</h1>
|
<h1>MBSE BBS Global Menus</h1>
|
||||||
<hr>
|
<hr>
|
||||||
|
|
||||||
<OL>
|
<OL>
|
||||||
|
|
||||||
<LI value="1"><strong>Goto another menu:</strong> This will start the execution
|
<LI value="1"><strong>Goto another menu:</strong> This will start the execution
|
||||||
of another menu. The current menu level is not stored on the stack.<br>
|
of another menu. The current menu level is not stored on the stack.<br>
|
||||||
<strong>Optional data:</strong> The name of the new menu.<Br>
|
<strong>Optional data:</strong> The name of the new menu.<Br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<LI value="2"><strong>Gosub another menu:</strong> This will start the execution
|
<LI value="2"><strong>Gosub another menu:</strong> This will start the execution
|
||||||
of another menu. The current menu level is stored on the stack. Gosub's may
|
of another menu. The current menu level is stored on the stack. Gosub's may
|
||||||
be nested 50 levels deep.<br>
|
be nested 50 levels deep.<br>
|
||||||
<strong>Optional data:</strong> The name of the new menu.<br>
|
<strong>Optional data:</strong> The name of the new menu.<br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<LI value="3"><strong>Return from Gosub:</strong> This will go back one
|
<LI value="3"><strong>Return from Gosub:</strong> This will go back one
|
||||||
gosub level. If you are already at the top level nothing happens.<br>
|
gosub level. If you are already at the top level nothing happens.<br>
|
||||||
<strong>Optional data:</strong> None.<br>
|
<strong>Optional data:</strong> None.<br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<LI value="4"><strong>Return to top menu:</strong> Return to the top (main)
|
<LI value="4"><strong>Return to top menu:</strong> Return to the top (main)
|
||||||
menu. The name of this menu is set in the global setup.
|
menu. The name of this menu is set in the global setup.
|
||||||
Default is main.mnu<br>
|
Default is main.mnu<br>
|
||||||
<strong>Optional data:</strong> None.<br>
|
<strong>Optional data:</strong> None.<br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<LI value="5"><strong>Display .a?? file with controlcodes:</strong> This will
|
<LI value="5"><strong>Display .a?? file with controlcodes:</strong> This will
|
||||||
display an ANSI file to the user. If the user has <em>Graphics No</em> set
|
display an ANSI file to the user. If the user has <em>Graphics No</em> set
|
||||||
then the ASCII version is shown. Search is done first in the users language
|
then the ASCII version is shown. Search is done first in the users language
|
||||||
path and if that fails the default language path is used.
|
path and if that fails the default language path is used.
|
||||||
<A HREF="control.html">Control codes</A> in the
|
<A HREF="control.html">Control codes</A> in the
|
||||||
file are substituted with the current values the represent.<BR>
|
file are substituted with the current values the represent.<BR>
|
||||||
<strong>Optional data:</strong> The name of the file to display. Do not
|
<strong>Optional data:</strong> The name of the file to display. Do not
|
||||||
give the filename extension!<BR>
|
give the filename extension!<BR>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<LI value="6"><strong>Show menu prompt:</strong> Display the menu prompt.<br>
|
<LI value="6"><strong>Show menu prompt:</strong> Display the menu prompt.<br>
|
||||||
<strong>Optional data:</strong> The prompt to display. This string may
|
<strong>Optional data:</strong> The prompt to display. This string may
|
||||||
contain some control characters that are replaced with information. The
|
contain some control characters that are replaced with information. The
|
||||||
prompt is displayed in White on Black and is hardcoded at the moment.
|
prompt is displayed in White on Black and is hardcoded at the moment.
|
||||||
<ul>
|
<ul>
|
||||||
<li><strong>~</strong> This will insert the number of minutes the user
|
<li><strong>~</strong> This will insert the number of minutes the user
|
||||||
has left.
|
has left.
|
||||||
<li><strong>@</strong> This will insert the name of the current file area.
|
<li><strong>@</strong> This will insert the name of the current file area.
|
||||||
<li><strong>^</strong> This will insert the name of the current message area.
|
<li><strong>^</strong> This will insert the name of the current message area.
|
||||||
<li><strong>#</strong> This will insert the current local time.
|
<li><strong>#</strong> This will insert the current local time.
|
||||||
</ul>
|
</ul>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<LI value="7"><strong>Run external program:</strong> This will execute
|
<LI value="7"><strong>Run external program:</strong> This will execute
|
||||||
external programs.<br>
|
external programs.<br>
|
||||||
<strong>Optional data:</strong> The full path and filename of the external
|
<strong>Optional data:</strong> The full path and filename of the external
|
||||||
program. This can be a shell too. Look for a lot of programs, for example
|
program to run. There are a few switches you can give on the commandline:
|
||||||
if you want to give your users internet mail with elm, the user can get a
|
<UL>
|
||||||
shell prompt by typing <em>!/bin/sh</em>. If you want this look for
|
<LI><b>/N</B> will be replaced by the current nodenumber. The nodenumber is
|
||||||
anyway you might consider using a restricted shell.<br>
|
faked by using the record number of the tty lines setup.
|
||||||
<P>
|
<LI><b>/A</b> will prompt for a filename to enter. The filename the user
|
||||||
|
enters is then replaced on the commandline. This is a dangerous option!
|
||||||
<LI value="8"><strong>Show product information:</strong> This will show
|
<LI><b>/T=your prompt</b> is an alternate prompt for entering a filename
|
||||||
copyright information about MBSE BBS.<br>
|
if used together with the <b>/A</b> option.
|
||||||
<strong>Optional data:</strong> None.<br>
|
</UL>
|
||||||
<P>
|
<br>
|
||||||
|
<P>
|
||||||
<LI value="9"><strong>Display todays callers:</strong> This will display a
|
|
||||||
list of todays callers to the BBS.<br>
|
<LI value="8"><strong>Show product information:</strong> This will show
|
||||||
<strong>Optional data:</strong> "/H" Show handles instead of real names.<br>
|
copyright information about MBSE BBS.<br>
|
||||||
<P>
|
<strong>Optional data:</strong> None.<br>
|
||||||
|
<P>
|
||||||
<LI value="10"><strong>Display userlist:</strong> Display all users in the
|
|
||||||
users database except those that are hidden.<br>
|
<LI value="9"><strong>Display todays callers:</strong> This will display a
|
||||||
<strong>Optional data:</strong> "/H" Show handles instead of real names.<br>
|
list of todays callers to the BBS.<br>
|
||||||
<P>
|
<strong>Optional data:</strong> "/H" Show handles instead of real names.<br>
|
||||||
|
<P>
|
||||||
<LI value="11"><strong>Time statistics:</strong> Display the users time
|
|
||||||
statistics.<br>
|
<LI value="10"><strong>Display userlist:</strong> Display all users in the
|
||||||
<strong>Optional data:</strong> None.<br>
|
users database except those that are hidden.<br>
|
||||||
<P>
|
<strong>Optional data:</strong> "/H" Show handles instead of real names.<br>
|
||||||
|
<P>
|
||||||
<LI value="12"><strong>Page Sysop:</strong> Page sysop for a chat.<br>
|
|
||||||
<strong>Optional data:</strong> A message to the user<br>
|
<LI value="11"><strong>Time statistics:</strong> Display the users time
|
||||||
The message to the user could be something like "Calling sysop, please
|
statistics.<br>
|
||||||
wait ..." or "I will see if Michiel wants to chat with you, please wait!"
|
<strong>Optional data:</strong> None.<br>
|
||||||
As sysop you will know best what to put in that line.
|
<P>
|
||||||
<P>
|
|
||||||
|
<LI value="12"><strong>Page Sysop:</strong> Page sysop for a chat.<br>
|
||||||
<LI value="13"><strong>Terminate call:</strong> Terminale this call and
|
<strong>Optional data:</strong> A message to the user<br>
|
||||||
hangup.<br>
|
The message to the user could be something like "Calling sysop, please
|
||||||
<strong>Optional data:</strong> None.
|
wait ..." or "I will see if Michiel wants to chat with you, please wait!"
|
||||||
<P>
|
As sysop you will know best what to put in that line.
|
||||||
|
<P>
|
||||||
<LI value="14"><strong>Make a log entry:</strong> This will write a line in
|
|
||||||
the logfile.<br>
|
<LI value="13"><strong>Terminate call:</strong> Terminale this call and
|
||||||
<strong>Optional data:</strong> The information you want in the logfile.<br>
|
hangup.<br>
|
||||||
<P>
|
<strong>Optional data:</strong> None.
|
||||||
|
<P>
|
||||||
<LI value="15"><strong>Print text to screen:</strong> Write text to the users
|
|
||||||
screen.<br>
|
<LI value="14"><strong>Make a log entry:</strong> This will write a line in
|
||||||
<strong>Optional data:</strong> The text that must appear on the users
|
the logfile.<br>
|
||||||
screen. The <em>@</em> character is replaced with a newline.<br>
|
<strong>Optional data:</strong> The information you want in the logfile.<br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<LI value="16"><strong>Who is online:</strong> Displays the who is online
|
<LI value="15"><strong>Print text to screen:</strong> Write text to the users
|
||||||
list and what they are doing. Users that are hidden are not displayed.<br>
|
screen.<br>
|
||||||
<strong>Optional data:</strong> "/H" Show handles instead of real names.<br>
|
<strong>Optional data:</strong> The text that must appear on the users
|
||||||
<P>
|
screen. The <em>@</em> character is replaced with a newline.<br>
|
||||||
|
<P>
|
||||||
<LI value="17"><strong>Comment to sysop:</strong> Enter the texteditor and
|
|
||||||
let the user write a message to the sysop. The area is predefined in the
|
<LI value="16"><strong>Who is online:</strong> Displays the who is online
|
||||||
global setup.<br>
|
list and what they are doing. Users that are hidden are not displayed.<br>
|
||||||
<strong>Optional data:</strong> None.<br>
|
<strong>Optional data:</strong> "/H" Show handles instead of real names.<br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<LI value="18"><strong>Send online message:</strong> Send an online message
|
<LI value="17"><strong>Comment to sysop:</strong> Enter the texteditor and
|
||||||
to a user on another line.</br>
|
let the user write a message to the sysop. The area is predefined in the
|
||||||
<strong>Optional data:</strong> "/H" Use handles instead of real names.<br>
|
global setup.<br>
|
||||||
<P>
|
<strong>Optional data:</strong> None.<br>
|
||||||
|
<P>
|
||||||
<LI value="19"><strong>Display textfile with more:</strong> This will display
|
|
||||||
a textfile to the user. After each full screen the user is prompted with
|
<LI value="18"><strong>Send online message:</strong> Send an online message
|
||||||
<em>More Y/n/=</em>.<br>
|
to a user on another line.</br>
|
||||||
<strong>Optional data:</strong> The full path and filename to the file.<br>
|
<strong>Optional data:</strong> "/H" Use handles instead of real names.<br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<LI value="20"><strong>Display .a?? file with control codes and wait:</strong>
|
<LI value="19"><strong>Display textfile with more:</strong> This will display
|
||||||
This will display a ANSI or ASCII file to the user with <A HREF="control.html">
|
a textfile to the user. After each full screen the user is prompted with
|
||||||
control codes</A> and wait for <em>Enter</em> when it is finished.<br>
|
<em>More Y/n/=</em>.<br>
|
||||||
<strong>Optional data:</strong> The filename without extension of the
|
<strong>Optional data:</strong> The full path and filename to the file.<br>
|
||||||
file to display.<br>
|
<P>
|
||||||
<P>
|
|
||||||
|
<LI value="20"><strong>Display .a?? file with control codes and wait:</strong>
|
||||||
<LI value="21"><strong>Display line</strong> This entry does nothing except
|
This will display a ANSI or ASCII file to the user with <A HREF="control.html">
|
||||||
that it displays the text on the display line. This is always displayed,
|
control codes</A> and wait for <em>Enter</em> when it is finished.<br>
|
||||||
even if the display line is empty. In that case an empty line is displayed.<br>
|
<strong>Optional data:</strong> The filename without extension of the
|
||||||
<strong>Optional data:</strong> None.<br>
|
file to display.<br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<LI value="22"><strong>Nextuser door:</strong> This runs the message to next
|
<LI value="21"><strong>Display line</strong> This entry does nothing except
|
||||||
user door.<br>
|
that it displays the text on the display line. This is always displayed,
|
||||||
<strong>Optional data:</strong> None.<br>
|
even if the display line is empty. In that case an empty line is displayed.<br>
|
||||||
<P>
|
<strong>Optional data:</strong> None.<br>
|
||||||
|
<P>
|
||||||
<LI value="23"><strong>Timebank door:</strong> This runs the time bank door.<br>
|
|
||||||
<strong>Optional data:</strong> None.<br>
|
<LI value="22"><strong>Nextuser door:</strong> This runs the message to next
|
||||||
<P>
|
user door.<br>
|
||||||
|
<strong>Optional data:</strong> None.<br>
|
||||||
<LI value="25"><strong>Safe cracker door:</strong> This runs the Safe Cracker
|
<P>
|
||||||
door.<br>
|
|
||||||
<strong>Optional data:</strong> None.<br>
|
<LI value="23"><strong>Timebank door:</strong> This runs the time bank door.<br>
|
||||||
</OL>
|
<strong>Optional data:</strong> None.<br>
|
||||||
|
<P>
|
||||||
<HR>
|
|
||||||
<A HREF="../"><IMG SRC="../images/b_arrow.gif" ALT="Index" BORDER=0 width="33" height="35"></A>
|
<LI value="25"><strong>Safe cracker door:</strong> This runs the Safe Cracker
|
||||||
<A HREF="../">Main Index</A>
|
door.<br>
|
||||||
<A HREF="./"><IMG SRC="../images/larrow.gif" ALT="Back" BORDER=0 width="40" height="30"></A>
|
<strong>Optional data:</strong> None.<br>
|
||||||
<A HREF="./">Menus Index</A>
|
</OL>
|
||||||
</BLOCKQUOTE>
|
|
||||||
</BODY>
|
<HR>
|
||||||
</HTML>
|
<A HREF="../"><IMG SRC="../images/b_arrow.gif" ALT="Index" BORDER=0 width="33" height="35"></A>
|
||||||
|
<A HREF="../">Main Index</A>
|
||||||
|
<A HREF="./"><IMG SRC="../images/larrow.gif" ALT="Back" BORDER=0 width="40" height="30"></A>
|
||||||
|
<A HREF="./">Menus Index</A>
|
||||||
|
</BLOCKQUOTE>
|
||||||
|
</BODY>
|
||||||
|
</HTML>
|
||||||
|
|
||||||
|
@ -1,147 +1,147 @@
|
|||||||
<HTML>
|
<HTML>
|
||||||
<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">
|
||||||
<META name="author" lang="en" "content="Michiel Broek">
|
<META name="author" lang="en" content="Michiel Broek">
|
||||||
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
||||||
<META name="description" lang="en" content="MBSE BBS Manual">
|
<META name="description" lang="en" content="MBSE BBS Manual">
|
||||||
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
||||||
<TITLE>MBSE BBS Menus - File Area Menus.</TITLE>
|
<TITLE>MBSE BBS Menus - File Area Menus.</TITLE>
|
||||||
<LINK rel=stylesheet HREF="../manual.css">
|
<LINK rel=stylesheet HREF="../manual.css">
|
||||||
</HEAD>
|
</HEAD>
|
||||||
<BODY>
|
<BODY>
|
||||||
<BLOCKQUOTE>
|
<BLOCKQUOTE>
|
||||||
<h5>Last update 02-Feb-2001</h5>
|
<h5>Last update 02-Feb-2001</h5>
|
||||||
<P> <P>
|
<P> <P>
|
||||||
|
|
||||||
<h1>MBSE BBS File Area Menus</h1>
|
<h1>MBSE BBS File Area Menus</h1>
|
||||||
<hr>
|
<hr>
|
||||||
|
|
||||||
<OL>
|
<OL>
|
||||||
|
|
||||||
<LI value="101"><strong>Select another area:</strong> This option will show
|
<LI value="101"><strong>Select another area:</strong> This option will show
|
||||||
a list of available areas and let the user select a new area. If there is
|
a list of available areas and let the user select a new area. If there is
|
||||||
optional data the new area will be selected without user intervention.<br>
|
optional data the new area will be selected without user intervention.<br>
|
||||||
<strong>Optional data:</strong> If there is an option the area is direct
|
<strong>Optional data:</strong> If there is an option the area is direct
|
||||||
selected. Current options are: <strong>F+</strong> goto next available area.
|
selected. Current options are: <strong>F+</strong> goto next available area.
|
||||||
<strong>F-</strong> goto previous available area.<Br>
|
<strong>F-</strong> goto previous available area.<Br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<LI value="102"><strong>File List:</strong> This option will display a list
|
<LI value="102"><strong>File List:</strong> This option will display a list
|
||||||
of files with their dates, sizes and description. During the display of the
|
of files with their dates, sizes and description. During the display of the
|
||||||
list the user can select (Tag) files for later download.<br>
|
list the user can select (Tag) files for later download.<br>
|
||||||
<strong>Optional data:</strong> None.<br>
|
<strong>Optional data:</strong> None.<br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<LI value="103"><strong>View File:</strong> Not yet implemented.<br>
|
<LI value="103"><strong>View File:</strong> Not yet implemented.<br>
|
||||||
<strong>Optional data:</strong> None.<br>
|
<strong>Optional data:</strong> None.<br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<LI value="104"><strong>Download File(s):</strong> This option will start to
|
<LI value="104"><strong>Download File(s):</strong> This option will start to
|
||||||
transmit files to the user if he has tagged files for download. Tagging files
|
transmit files to the user if he has tagged files for download. Tagging files
|
||||||
for download can be done during File List, Keyword Scan, Filename Scan or
|
for download can be done during File List, Keyword Scan, Filename Scan or
|
||||||
Newfile Scan. If a user didn't select a transfer protocol before now he will be
|
Newfile Scan. If a user didn't select a transfer protocol before now he will be
|
||||||
forced to select a file transfer protocol.<br>
|
forced to select a file transfer protocol.<br>
|
||||||
<strong>Optional Data:</strong> None.<br>
|
<strong>Optional Data:</strong> None.<br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<LI value="105"><strong>Raw Directory:</strong> This option will display the
|
<LI value="105"><strong>Raw Directory:</strong> This option will display the
|
||||||
contents of a directory in raw format.<br>
|
contents of a directory in raw format.<br>
|
||||||
<strong>Optional data:</strong> If the option is <strong>/F</strong> the
|
<strong>Optional data:</strong> If the option is <strong>/F</strong> the
|
||||||
contents of the current directory is shown. If the option is the full path
|
contents of the current directory is shown. If the option is the full path
|
||||||
to a directory, the contents of that directory is shown. <br>
|
to a directory, the contents of that directory is shown. <br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<LI value="106"><strong>Keyword Scan:</strong> This option will search for
|
<LI value="106"><strong>Keyword Scan:</strong> This option will search for
|
||||||
files in the files database for a matching keyword. The search is not case
|
files in the files database for a matching keyword. The search is not case
|
||||||
sensitive. If there are files found the user is able to select (Tag) these
|
sensitive. If there are files found the user is able to select (Tag) these
|
||||||
files for later download.<br>
|
files for later download.<br>
|
||||||
<strong>Optional data:</strong> None.<br>
|
<strong>Optional data:</strong> None.<br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<LI value="107"><strong>Filename Scan:</strong> This option will search for
|
<LI value="107"><strong>Filename Scan:</strong> This option will search for
|
||||||
a filename match in the files database. The search is not case sensitive.
|
a filename match in the files database. The search is not case sensitive.
|
||||||
If there are files found the user is able to select (Tag) these files for
|
If there are files found the user is able to select (Tag) these files for
|
||||||
later download.<br>
|
later download.<br>
|
||||||
<strong>Optional data:</strong> None.<br>
|
<strong>Optional data:</strong> None.<br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<LI value="108"><strong>Newfiles Scan:</strong> This option will scan for new
|
<LI value="108"><strong>Newfiles Scan:</strong> This option will scan for new
|
||||||
files available for download since the last time the user was online. As
|
files available for download since the last time the user was online. As
|
||||||
option the user can change that date from which to start the search. Any files
|
option the user can change that date from which to start the search. Any files
|
||||||
found the user may select (Tag) for later download.<br>
|
found the user may select (Tag) for later download.<br>
|
||||||
<strong>Optional data:</strong> None.<br>
|
<strong>Optional data:</strong> None.<br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<LI value="109"><strong>Upload:</strong> This option will let the user upload
|
<LI value="109"><strong>Upload:</strong> This option will let the user upload
|
||||||
files to the bbs. If the current area has an alternate upload area, the upload
|
files to the bbs. If the current area has an alternate upload area, the upload
|
||||||
will end up in that area. If the user uses X-modem or another ancient protocol
|
will end up in that area. If the user uses X-modem or another ancient protocol
|
||||||
he will first be asked for a filename. Normal modern protocols don't need this.
|
he will first be asked for a filename. Normal modern protocols don't need this.
|
||||||
The filename is checked before the transfer is done to protect the bbs. Further
|
The filename is checked before the transfer is done to protect the bbs. Further
|
||||||
the files the user will upload will at first be placed under the users home
|
the files the user will upload will at first be placed under the users home
|
||||||
directory <strong>~/upl</strong>. After the upload(s) the files are checked
|
directory <strong>~/upl</strong>. After the upload(s) the files are checked
|
||||||
for virusses. If all is well, the file is imported in the bbs. If the file
|
for virusses. If all is well, the file is imported in the bbs. If the file
|
||||||
contains a valid FILE_ID.DIZ file inside the archive, that file will be used
|
contains a valid FILE_ID.DIZ file inside the archive, that file will be used
|
||||||
for the description of the upload, if not, the uploader will have to describe
|
for the description of the upload, if not, the uploader will have to describe
|
||||||
the file.<br>
|
the file.<br>
|
||||||
<strong>Optional data:</strong> None.<br>
|
<strong>Optional data:</strong> None.<br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<LI value="110"><strong>Edit Taglist:</strong> This option is for the user to
|
<LI value="110"><strong>Edit Taglist:</strong> This option is for the user to
|
||||||
edit the list of files he has tagged for later download.<br>
|
edit the list of files he has tagged for later download.<br>
|
||||||
<strong>Optional data:</strong> None.<br>
|
<strong>Optional data:</strong> None.<br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<LI value="111"><strong>View file in homedir:</strong> Not yet implemented.<br>
|
<LI value="111"><strong>View file in homedir:</strong> Not yet implemented.<br>
|
||||||
<strong>Optional data:</strong> None.<br>
|
<strong>Optional data:</strong> None.<br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<LI value="112"><strong>Download Direct:</strong> Download a file direct.<br>
|
<LI value="112"><strong>Download Direct:</strong> Download a file direct.<br>
|
||||||
<strong>Optional data:</strong> The full path and filename to the file to
|
<strong>Optional data:</strong> The full path and filename to the file to
|
||||||
download.<br>
|
download.<br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<LI value="113"><strong>Copy file to Homedir:</strong> This option will copy
|
<LI value="113"><strong>Copy file to Homedir:</strong> This option will copy
|
||||||
a file from a download directory to the users home directory. It will be
|
a file from a download directory to the users home directory. It will be
|
||||||
checked if the user has enough room in his directory, the default Quota for
|
checked if the user has enough room in his directory, the default Quota for
|
||||||
users is 10 MBytes.<br>
|
users is 10 MBytes.<br>
|
||||||
<strong>Optional data:</strong> None.<br>
|
<strong>Optional data:</strong> None.<br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<LI value="114"><strong>List Homedir:</strong> This option will list the files
|
<LI value="114"><strong>List Homedir:</strong> This option will list the files
|
||||||
in the users home directory.<br>
|
in the users home directory.<br>
|
||||||
<strong>Optional data:</strong> None.<br>
|
<strong>Optional data:</strong> None.<br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<LI value="115"><strong>Delete in Homedir:</strong> This option will let the
|
<LI value="115"><strong>Delete in Homedir:</strong> This option will let the
|
||||||
user delete one or more files from his home directory.<br>
|
user delete one or more files from his home directory.<br>
|
||||||
<strong>Optional data:</strong> None.<br>
|
<strong>Optional data:</strong> None.<br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<LI value="116"><strong>Unpack file in Homedir:</strong> Not yet implemented.<br>
|
<LI value="116"><strong>Unpack file in Homedir:</strong> Not yet implemented.<br>
|
||||||
<strong>Optional data:</strong> None.<br>
|
<strong>Optional data:</strong> None.<br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<LI value="117"><strong>Pack files in Homedir:</strong> Not yet implemented.<br>
|
<LI value="117"><strong>Pack files in Homedir:</strong> Not yet implemented.<br>
|
||||||
<strong>Optional data:</strong> None.<br>
|
<strong>Optional data:</strong> None.<br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<LI value="118"><strong>Download Homedir:</strong> This option will let the
|
<LI value="118"><strong>Download Homedir:</strong> This option will let the
|
||||||
user download from his home directory.<br>
|
user download from his home directory.<br>
|
||||||
<strong>Optional data:</strong> None.<br>
|
<strong>Optional data:</strong> None.<br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<LI value="119"><strong>Upload Homedir:</strong> This option will let the user
|
<LI value="119"><strong>Upload Homedir:</strong> This option will let the user
|
||||||
upload files to his home directory.<br>
|
upload files to his home directory.<br>
|
||||||
<strong>Optional data:</strong> None.<br>
|
<strong>Optional data:</strong> None.<br>
|
||||||
</OL>
|
</OL>
|
||||||
|
|
||||||
<HR>
|
<HR>
|
||||||
<A HREF="../"><IMG SRC="../images/b_arrow.gif" ALT="Index" BORDER=0 width="33" height="35"></A>
|
<A HREF="../"><IMG SRC="../images/b_arrow.gif" ALT="Index" BORDER=0 width="33" height="35"></A>
|
||||||
<A HREF="../">Main Index</A>
|
<A HREF="../">Main Index</A>
|
||||||
<A HREF="./"><IMG SRC="../images/larrow.gif" ALT="Back" BORDER=0 width="40" height="30"></A>
|
<A HREF="./"><IMG SRC="../images/larrow.gif" ALT="Back" BORDER=0 width="40" height="30"></A>
|
||||||
<A HREF="./">Menus Index</A>
|
<A HREF="./">Menus Index</A>
|
||||||
</BLOCKQUOTE>
|
</BLOCKQUOTE>
|
||||||
</BODY>
|
</BODY>
|
||||||
</HTML>
|
</HTML>
|
||||||
|
|
||||||
|
@ -1,138 +1,138 @@
|
|||||||
<HTML>
|
<HTML>
|
||||||
<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">
|
||||||
<META name="author" lang="en" "content="Michiel Broek">
|
<META name="author" lang="en" content="Michiel Broek">
|
||||||
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
||||||
<META name="description" lang="en" content="MBSE BBS Manual">
|
<META name="description" lang="en" content="MBSE BBS Manual">
|
||||||
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
||||||
<TITLE>MBSE BBS Menus - Message Area Menus.</TITLE>
|
<TITLE>MBSE BBS Menus - Message Area Menus.</TITLE>
|
||||||
<LINK rel=stylesheet HREF="../manual.css">
|
<LINK rel=stylesheet HREF="../manual.css">
|
||||||
</HEAD>
|
</HEAD>
|
||||||
<BODY>
|
<BODY>
|
||||||
<BLOCKQUOTE>
|
<BLOCKQUOTE>
|
||||||
<h5>Last update 02-Feb-2001</h5>
|
<h5>Last update 02-Feb-2001</h5>
|
||||||
<P> <P>
|
<P> <P>
|
||||||
|
|
||||||
<h1>MBSE BBS Message Area Menus</h1>
|
<h1>MBSE BBS Message Area Menus</h1>
|
||||||
<hr>
|
<hr>
|
||||||
|
|
||||||
<OL>
|
<OL>
|
||||||
|
|
||||||
<LI value="201"><strong>Select another area:</strong> This option will show
|
<LI value="201"><strong>Select another area:</strong> This option will show
|
||||||
a list of all available areas and let the user select a new area. If there
|
a list of all available areas and let the user select a new area. If there
|
||||||
is optional data the area will be selected without user intervention.<br>
|
is optional data the area will be selected without user intervention.<br>
|
||||||
<strong>Optional data:</strong> If there is an option the area is direct
|
<strong>Optional data:</strong> If there is an option the area is direct
|
||||||
selected. Current options are <strong>M+</strong> goto the next available
|
selected. Current options are <strong>M+</strong> goto the next available
|
||||||
area. <strong>M-</strong> goto the previous available area.<br>
|
area. <strong>M-</strong> goto the previous available area.<br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<LI value="202"><strong>Post a Message:</strong> This option lets the user
|
<LI value="202"><strong>Post a Message:</strong> This option lets the user
|
||||||
post a new message.<br>
|
post a new message.<br>
|
||||||
<strong>Optional data:</strong> None.<br>
|
<strong>Optional data:</strong> None.<br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<LI value="203"><strong>Read Messages:</strong> This option lets the user
|
<LI value="203"><strong>Read Messages:</strong> This option lets the user
|
||||||
read messages. If he has done that before in that area he will be suggested
|
read messages. If he has done that before in that area he will be suggested
|
||||||
to start after the message he has last read. During reading of messages
|
to start after the message he has last read. During reading of messages
|
||||||
the user can reply to other messages.<br>
|
the user can reply to other messages.<br>
|
||||||
<strong>Optional data:</strong> None.<br>
|
<strong>Optional data:</strong> None.<br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<LI value="204"><strong>Check for Mail:</strong> Check for new arrived mail.<br>
|
<LI value="204"><strong>Check for Mail:</strong> Check for new arrived mail.<br>
|
||||||
<strong>Optional data:</strong> None.<br>
|
<strong>Optional data:</strong> None.<br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<LI value="205"><strong>Quickscan Messages:</strong> Make a quick overview
|
<LI value="205"><strong>Quickscan Messages:</strong> Make a quick overview
|
||||||
list of all messages in that area.<br>
|
list of all messages in that area.<br>
|
||||||
<strong>Optional data:</strong> None.<br>
|
<strong>Optional data:</strong> None.<br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<LI value="206"><strong>Delete a Message:</strong> This option will let the
|
<LI value="206"><strong>Delete a Message:</strong> This option will let the
|
||||||
user delete a specific message. He must the the owner or recipient of that
|
user delete a specific message. He must the the owner or recipient of that
|
||||||
message or have sysop rights in that area to be able to delete a message.<br>
|
message or have sysop rights in that area to be able to delete a message.<br>
|
||||||
<strong>Optional data:</strong> None.<br>
|
<strong>Optional data:</strong> None.<br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<LI value="207"><strong>Mail Status:</strong> This gives a complete overview
|
<LI value="207"><strong>Mail Status:</strong> This gives a complete overview
|
||||||
of all available mail at the bbs.<br>
|
of all available mail at the bbs.<br>
|
||||||
<strong>Optional data:</strong> None.<br>
|
<strong>Optional data:</strong> None.<br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<LI value="208"><strong>OLR: Tag Area:</strong> This option lets
|
<LI value="208"><strong>OLR: Tag Area:</strong> This option lets
|
||||||
the user tag one or more areas to be included in his offline mail packet.<br>
|
the user tag one or more areas to be included in his offline mail packet.<br>
|
||||||
<strong>Optional data:</strong> None.<br>
|
<strong>Optional data:</strong> None.<br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<LI value="209"><strong>OLR: Untag Area:</strong> This option lets
|
<LI value="209"><strong>OLR: Untag Area:</strong> This option lets
|
||||||
the user untag one or more areas not to be included in his offline mail
|
the user untag one or more areas not to be included in his offline mail
|
||||||
packet.<br>
|
packet.<br>
|
||||||
<strong>Optional data:</strong> None.<br>
|
<strong>Optional data:</strong> None.<br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<LI value="210"><strong>OLR: View Tags:</strong> This option lets
|
<LI value="210"><strong>OLR: View Tags:</strong> This option lets
|
||||||
the user view which areas will be included in his offline mail packet.<br>
|
the user view which areas will be included in his offline mail packet.<br>
|
||||||
<strong>Optional data:</strong> None.<br>
|
<strong>Optional data:</strong> None.<br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<LI value="211"><strong>OLR: Restrict Date:</strong> Not yet
|
<LI value="211"><strong>OLR: Restrict Date:</strong> Not yet
|
||||||
implemented.<br>
|
implemented.<br>
|
||||||
<strong>Optional data:</strong> None.<br>
|
<strong>Optional data:</strong> None.<br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<LI value="212"><strong>OLR: Upload Mail:</strong> Let the user upload
|
<LI value="212"><strong>OLR: Upload Mail:</strong> Let the user upload
|
||||||
mail or a new offline reader setup. The packet format is automatic detected.
|
mail or a new offline reader setup. The packet format is automatic detected.
|
||||||
Currently BlueWave is supported. QWK support will be added later.<br>
|
Currently BlueWave is supported. QWK support will be added later.<br>
|
||||||
<strong>Optional data:</strong> None.<br>
|
<strong>Optional data:</strong> None.<br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<LI value="213"><strong>OLR: Download BlueWave:</strong> Download mail in
|
<LI value="213"><strong>OLR: Download BlueWave:</strong> Download mail in
|
||||||
BlueWave version 2 format.<br>
|
BlueWave version 2 format.<br>
|
||||||
<strong>Optional data:</strong> None.<br>
|
<strong>Optional data:</strong> None.<br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<LI value="214"><strong>OLR: Download QWK:</strong> Download mail in QWK
|
<LI value="214"><strong>OLR: Download QWK:</strong> Download mail in QWK
|
||||||
format.<br>
|
format.<br>
|
||||||
<strong>Optional data:</strong> None.<br>
|
<strong>Optional data:</strong> None.<br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<LI value="215"><strong>OLR: Download ASCII:</strong> Download mail in flat
|
<LI value="215"><strong>OLR: Download ASCII:</strong> Download mail in flat
|
||||||
ASCII format. Not yet implemented.<br>
|
ASCII format. Not yet implemented.<br>
|
||||||
<strong>Optional data:</strong> None.<br>
|
<strong>Optional data:</strong> None.<br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<LI value="216"><strong>Read Email</strong> Read users private email.<br>
|
<LI value="216"><strong>Read Email</strong> Read users private email.<br>
|
||||||
<strong>Optional data:</strong> None.<br>
|
<strong>Optional data:</strong> None.<br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<LI value="217"><strong>Write Email</strong> Post an email message.<br>
|
<LI value="217"><strong>Write Email</strong> Post an email message.<br>
|
||||||
<strong>Optional data:</strong> None.<br>
|
<strong>Optional data:</strong> None.<br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<LI value="218"><strong>Trash Email</strong> Put email in the trashcan.
|
<LI value="218"><strong>Trash Email</strong> Put email in the trashcan.
|
||||||
Not Yet implemented.<br>
|
Not Yet implemented.<br>
|
||||||
<strong>Optional data:</strong> None.<br>
|
<strong>Optional data:</strong> None.<br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<LI value="219"><strong>Choose Mailbox</strong> Choose another private
|
<LI value="219"><strong>Choose Mailbox</strong> Choose another private
|
||||||
mailbox. Valid boxes are: mailbox (normal in/out), archive and trash.<br>
|
mailbox. Valid boxes are: mailbox (normal in/out), archive and trash.<br>
|
||||||
<strong>Optional data:</strong> If there is an option the area is direct
|
<strong>Optional data:</strong> If there is an option the area is direct
|
||||||
selected. Current options are <strong>M+</strong> goto the next mailbox.
|
selected. Current options are <strong>M+</strong> goto the next mailbox.
|
||||||
<strong>M-</strong> goto the previous mailbox.<br>
|
<strong>M-</strong> goto the previous mailbox.<br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<LI value="220"><strong>Quickscan Email</strong> Make a quick overview
|
<LI value="220"><strong>Quickscan Email</strong> Make a quick overview
|
||||||
list of all messages in the selected e-mail area.<br>
|
list of all messages in the selected e-mail area.<br>
|
||||||
<strong>Optional data:</strong> None.<br>
|
<strong>Optional data:</strong> None.<br>
|
||||||
<P>
|
<P>
|
||||||
</OL>
|
</OL>
|
||||||
|
|
||||||
<HR>
|
<HR>
|
||||||
<A HREF="../"><IMG SRC="../images/b_arrow.gif" ALT="Index" BORDER=0 width="33" height="35"></A>
|
<A HREF="../"><IMG SRC="../images/b_arrow.gif" ALT="Index" BORDER=0 width="33" height="35"></A>
|
||||||
<A HREF="../">Main Index</A>
|
<A HREF="../">Main Index</A>
|
||||||
<A HREF="./"><IMG SRC="../images/larrow.gif" ALT="Back" BORDER=0 width="40" height="30"></A>
|
<A HREF="./"><IMG SRC="../images/larrow.gif" ALT="Back" BORDER=0 width="40" height="30"></A>
|
||||||
<A HREF="./">Menus Index</A>
|
<A HREF="./">Menus Index</A>
|
||||||
</BLOCKQUOTE>
|
</BLOCKQUOTE>
|
||||||
</BODY>
|
</BODY>
|
||||||
</HTML>
|
</HTML>
|
||||||
|
|
||||||
|
@ -1,99 +1,99 @@
|
|||||||
<HTML>
|
<HTML>
|
||||||
<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">
|
||||||
<META name="author" lang="en" "content="Michiel Broek">
|
<META name="author" lang="en" content="Michiel Broek">
|
||||||
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
||||||
<META name="description" lang="en" content="MBSE BBS Manual">
|
<META name="description" lang="en" content="MBSE BBS Manual">
|
||||||
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
||||||
<TITLE>MBSE BBS Menus - User Settings Menus.</TITLE>
|
<TITLE>MBSE BBS Menus - User Settings Menus.</TITLE>
|
||||||
<LINK rel=stylesheet HREF="../manual.css">
|
<LINK rel=stylesheet HREF="../manual.css">
|
||||||
</HEAD>
|
</HEAD>
|
||||||
<BODY>
|
<BODY>
|
||||||
<BLOCKQUOTE>
|
<BLOCKQUOTE>
|
||||||
<h5>Last update 02-Feb-2001</h5>
|
<h5>Last update 02-Feb-2001</h5>
|
||||||
<P> <P>
|
<P> <P>
|
||||||
|
|
||||||
<h1>MBSE BBS User Settings Menus</h1>
|
<h1>MBSE BBS User Settings Menus</h1>
|
||||||
<hr>
|
<hr>
|
||||||
|
|
||||||
<OL>
|
<OL>
|
||||||
|
|
||||||
<LI value="301"><strong>Change Transfer Protocol:</strong> Let the user
|
<LI value="301"><strong>Change Transfer Protocol:</strong> Let the user
|
||||||
select a new file transfer protocol.<br>
|
select a new file transfer protocol.<br>
|
||||||
<strong>Optional data:</strong> None.<Br>
|
<strong>Optional data:</strong> None.<Br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<LI value="302"><strong>Change Password:</strong> Let the user change
|
<LI value="302"><strong>Change Password:</strong> Let the user change
|
||||||
his FidoNet password.<br>
|
his FidoNet password.<br>
|
||||||
<strong>Optional data:</strong> None.<Br>
|
<strong>Optional data:</strong> None.<Br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<LI value="303"><strong>Change Location:</strong> Let the user change
|
<LI value="303"><strong>Change Location:</strong> Let the user change
|
||||||
his location.<br>
|
his location.<br>
|
||||||
<strong>Optional data:</strong> None.<Br>
|
<strong>Optional data:</strong> None.<Br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<LI value="304"><strong>Change Graphics:</strong> Let the user toggle
|
<LI value="304"><strong>Change Graphics:</strong> Let the user toggle
|
||||||
graphics mode on or off.<br>
|
graphics mode on or off.<br>
|
||||||
<strong>Optional data:</strong> None.<Br>
|
<strong>Optional data:</strong> None.<Br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<LI value="305"><strong>Change Voicephone:</strong> Let the user change
|
<LI value="305"><strong>Change Voicephone:</strong> Let the user change
|
||||||
his voice phonenumber.<br>
|
his voice phonenumber.<br>
|
||||||
<strong>Optional data:</strong> None.<Br>
|
<strong>Optional data:</strong> None.<Br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<LI value="306"><strong>Change Dataphone:</strong> Let the user change
|
<LI value="306"><strong>Change Dataphone:</strong> Let the user change
|
||||||
his data phonenumber.<br>
|
his data phonenumber.<br>
|
||||||
<strong>Optional data:</strong> None.<Br>
|
<strong>Optional data:</strong> None.<Br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<LI value="307"><strong>Change Expertmode:</strong> This command will be
|
<LI value="307"><strong>Change Expertmode:</strong> This command will be
|
||||||
removed.<br>
|
removed.<br>
|
||||||
<strong>Optional data:</strong> None.<Br>
|
<strong>Optional data:</strong> None.<Br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<LI value="308"><strong>Change Scrennlength:</strong> This command will
|
<LI value="308"><strong>Change Scrennlength:</strong> This command will
|
||||||
let the user set a new screenlength, the default is 24.<br>
|
let the user set a new screenlength, the default is 24.<br>
|
||||||
<strong>Optional data:</strong> None.<Br>
|
<strong>Optional data:</strong> None.<Br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<LI value="309"><strong>Change Date of Birth:</strong> Let the user set a
|
<LI value="309"><strong>Change Date of Birth:</strong> Let the user set a
|
||||||
new date of birth. Check's are done if the date is more or less realistic.
|
new date of birth. Check's are done if the date is more or less realistic.
|
||||||
This command should not be made available users if you use the regular
|
This command should not be made available users if you use the regular
|
||||||
date of birth validation check.<br>
|
date of birth validation check.<br>
|
||||||
<strong>Optional data:</strong> None.<Br>
|
<strong>Optional data:</strong> None.<Br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<LI value="310"><strong>Change Language:</strong> Let the user select a new
|
<LI value="310"><strong>Change Language:</strong> Let the user select a new
|
||||||
default language.<br>
|
default language.<br>
|
||||||
<strong>Optional data:</strong> None.<Br>
|
<strong>Optional data:</strong> None.<Br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<LI value="311"><strong>Change Hotkeys:</strong> Let the user toggle the
|
<LI value="311"><strong>Change Hotkeys:</strong> Let the user toggle the
|
||||||
use of Hotkeys on or off..<br>
|
use of Hotkeys on or off..<br>
|
||||||
<strong>Optional data:</strong> None.<Br>
|
<strong>Optional data:</strong> None.<Br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<LI value="312"><strong>Change Handle:</strong> Let the user select a new
|
<LI value="312"><strong>Change Handle:</strong> Let the user select a new
|
||||||
handle (nickname).<br>
|
handle (nickname).<br>
|
||||||
<strong>Optional data:</strong> None.<Br>
|
<strong>Optional data:</strong> None.<Br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<LI value="314"><strong>Change Don't Disturb:</strong> Let the user toggle
|
<LI value="314"><strong>Change Don't Disturb:</strong> Let the user toggle
|
||||||
the "do not disturb" flag.<br>
|
the "do not disturb" flag.<br>
|
||||||
<strong>Optional data:</strong> None.<Br>
|
<strong>Optional data:</strong> None.<Br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
</OL>
|
</OL>
|
||||||
|
|
||||||
<HR>
|
<HR>
|
||||||
<A HREF="../"><IMG SRC="../images/b_arrow.gif" ALT="Index" BORDER=0 width="33" height="35"></A>
|
<A HREF="../"><IMG SRC="../images/b_arrow.gif" ALT="Index" BORDER=0 width="33" height="35"></A>
|
||||||
<A HREF="../">Main Index</A>
|
<A HREF="../">Main Index</A>
|
||||||
<A HREF="./"><IMG SRC="../images/larrow.gif" ALT="Back" BORDER=0 width="40" height="30"></A>
|
<A HREF="./"><IMG SRC="../images/larrow.gif" ALT="Back" BORDER=0 width="40" height="30"></A>
|
||||||
<A HREF="./">Menus Index</A>
|
<A HREF="./">Menus Index</A>
|
||||||
</BLOCKQUOTE>
|
</BLOCKQUOTE>
|
||||||
</BODY>
|
</BODY>
|
||||||
</HTML>
|
</HTML>
|
||||||
|
|
||||||
|
@ -1,60 +1,60 @@
|
|||||||
<HTML>
|
<HTML>
|
||||||
<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">
|
||||||
<META name="author" lang="en" "content="Michiel Broek">
|
<META name="author" lang="en" content="Michiel Broek">
|
||||||
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
||||||
<META name="description" lang="en" content="MBSE BBS Manual">
|
<META name="description" lang="en" content="MBSE BBS Manual">
|
||||||
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
||||||
<TITLE>MBSE BBS Menus - Oneliner Menus.</TITLE>
|
<TITLE>MBSE BBS Menus - Oneliner Menus.</TITLE>
|
||||||
<LINK rel=stylesheet HREF="../manual.css">
|
<LINK rel=stylesheet HREF="../manual.css">
|
||||||
</HEAD>
|
</HEAD>
|
||||||
<BODY>
|
<BODY>
|
||||||
<BLOCKQUOTE>
|
<BLOCKQUOTE>
|
||||||
<h5>Last update 02-Feb-2001</h5>
|
<h5>Last update 02-Feb-2001</h5>
|
||||||
<P> <P>
|
<P> <P>
|
||||||
|
|
||||||
<h1>MBSE BBS Oneliner Menus</h1>
|
<h1>MBSE BBS Oneliner Menus</h1>
|
||||||
<hr>
|
<hr>
|
||||||
|
|
||||||
<OL>
|
<OL>
|
||||||
|
|
||||||
<LI value="401"><strong>Oneliner Add:</strong> Let the user add a new
|
<LI value="401"><strong>Oneliner Add:</strong> Let the user add a new
|
||||||
oneliner.<br>
|
oneliner.<br>
|
||||||
<strong>Optional data:</strong> None.<Br>
|
<strong>Optional data:</strong> None.<Br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<LI value="402"><strong>Oneliner List:</strong> Let the user list all the
|
<LI value="402"><strong>Oneliner List:</strong> Let the user list all the
|
||||||
available oneliners.<br>
|
available oneliners.<br>
|
||||||
<strong>Optional data:</strong> None.<Br>
|
<strong>Optional data:</strong> None.<Br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<LI value="403"><strong>Oneliner Show:</strong> Let the user show a
|
<LI value="403"><strong>Oneliner Show:</strong> Let the user show a
|
||||||
specific oneliner.<br>
|
specific oneliner.<br>
|
||||||
<strong>Optional data:</strong> None.<Br>
|
<strong>Optional data:</strong> None.<Br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<LI value="404"><strong>Oneliner Delete:</strong> Let the user delete a
|
<LI value="404"><strong>Oneliner Delete:</strong> Let the user delete a
|
||||||
oneliner. In order to do so he must be the owner of that oneliner or
|
oneliner. In order to do so he must be the owner of that oneliner or
|
||||||
he must have sysop access level. The oneliner is not really removed, only
|
he must have sysop access level. The oneliner is not really removed, only
|
||||||
marked for deletion.<br>
|
marked for deletion.<br>
|
||||||
<strong>Optional data:</strong> None.<Br>
|
<strong>Optional data:</strong> None.<Br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<LI value="405"><strong>Oneliner Print:</strong> Show a random chosen
|
<LI value="405"><strong>Oneliner Print:</strong> Show a random chosen
|
||||||
oneliner on the screen. If you make this command automatic, each time that
|
oneliner on the screen. If you make this command automatic, each time that
|
||||||
this menu is executed a new oneliner will popup.<br>
|
this menu is executed a new oneliner will popup.<br>
|
||||||
<strong>Optional data:</strong> None.<Br>
|
<strong>Optional data:</strong> None.<Br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
</OL>
|
</OL>
|
||||||
|
|
||||||
<HR>
|
<HR>
|
||||||
<A HREF="../"><IMG SRC="../images/b_arrow.gif" ALT="Index" BORDER=0 width="33" height="35"></A>
|
<A HREF="../"><IMG SRC="../images/b_arrow.gif" ALT="Index" BORDER=0 width="33" height="35"></A>
|
||||||
<A HREF="../">Main Index</A>
|
<A HREF="../">Main Index</A>
|
||||||
<A HREF="./"><IMG SRC="../images/larrow.gif" ALT="Back" BORDER=0 width="40" height="30"></A>
|
<A HREF="./"><IMG SRC="../images/larrow.gif" ALT="Back" BORDER=0 width="40" height="30"></A>
|
||||||
<A HREF="./">Menus Index</A>
|
<A HREF="./">Menus Index</A>
|
||||||
</BLOCKQUOTE>
|
</BLOCKQUOTE>
|
||||||
</BODY>
|
</BODY>
|
||||||
</HTML>
|
</HTML>
|
||||||
|
|
||||||
|
@ -1,56 +1,56 @@
|
|||||||
<HTML>
|
<HTML>
|
||||||
<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">
|
||||||
<META name="author" lang="en" "content="Michiel Broek">
|
<META name="author" lang="en" content="Michiel Broek">
|
||||||
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
||||||
<META name="description" lang="en" content="MBSE BBS Manual">
|
<META name="description" lang="en" content="MBSE BBS Manual">
|
||||||
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
||||||
<TITLE>MBSE BBS Menus - BBS List Menus.</TITLE>
|
<TITLE>MBSE BBS Menus - BBS List Menus.</TITLE>
|
||||||
<LINK rel=stylesheet HREF="../manual.css">
|
<LINK rel=stylesheet HREF="../manual.css">
|
||||||
</HEAD>
|
</HEAD>
|
||||||
<BODY>
|
<BODY>
|
||||||
<BLOCKQUOTE>
|
<BLOCKQUOTE>
|
||||||
<h5>Last update 02-Feb-2001</h5>
|
<h5>Last update 02-Feb-2001</h5>
|
||||||
<P> <P>
|
<P> <P>
|
||||||
|
|
||||||
<h1>MBSE BBS BBS List Menus</h1>
|
<h1>MBSE BBS BBS List Menus</h1>
|
||||||
<hr>
|
<hr>
|
||||||
|
|
||||||
<OL>
|
<OL>
|
||||||
|
|
||||||
<LI value="501"><strong>Add a BBS:</strong> Let the user add a BBS to the
|
<LI value="501"><strong>Add a BBS:</strong> Let the user add a BBS to the
|
||||||
BBS advertising database.<br>
|
BBS advertising database.<br>
|
||||||
<strong>Optional data:</strong> None.<Br>
|
<strong>Optional data:</strong> None.<Br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<LI value="502"><strong>List BBS'es:</strong> Show a list of BBS'es in the
|
<LI value="502"><strong>List BBS'es:</strong> Show a list of BBS'es in the
|
||||||
BBS database.<br>
|
BBS database.<br>
|
||||||
<strong>Optional data:</strong> None.<Br>
|
<strong>Optional data:</strong> None.<Br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<LI value="503"><strong>Show BBS:</strong> Show a specific BBS.<br>
|
<LI value="503"><strong>Show BBS:</strong> Show a specific BBS.<br>
|
||||||
<strong>Optional data:</strong> None.<Br>
|
<strong>Optional data:</strong> None.<Br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<LI value="504"><strong>Delete BBS:</strong> Delete a specific BBS. The BBS
|
<LI value="504"><strong>Delete BBS:</strong> Delete a specific BBS. The BBS
|
||||||
must have been entered by the user or the user must have sysop rights to
|
must have been entered by the user or the user must have sysop rights to
|
||||||
be able to delete a BBS.<br>
|
be able to delete a BBS.<br>
|
||||||
<strong>Optional data:</strong> None.<Br>
|
<strong>Optional data:</strong> None.<Br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<LI value="506"><strong>Search BBS:</strong> Search for a specific BBS.<br>
|
<LI value="506"><strong>Search BBS:</strong> Search for a specific BBS.<br>
|
||||||
<strong>Optional data:</strong> None.<Br>
|
<strong>Optional data:</strong> None.<Br>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
</OL>
|
</OL>
|
||||||
|
|
||||||
<HR>
|
<HR>
|
||||||
<A HREF="../"><IMG SRC="../images/b_arrow.gif" ALT="Index" BORDER=0 width="33" height="35"></A>
|
<A HREF="../"><IMG SRC="../images/b_arrow.gif" ALT="Index" BORDER=0 width="33" height="35"></A>
|
||||||
<A HREF="../">Main Index</A>
|
<A HREF="../">Main Index</A>
|
||||||
<A HREF="./"><IMG SRC="../images/larrow.gif" ALT="Back" BORDER=0 width="40" height="30"></A>
|
<A HREF="./"><IMG SRC="../images/larrow.gif" ALT="Back" BORDER=0 width="40" height="30"></A>
|
||||||
<A HREF="./">Menus Index</A>
|
<A HREF="./">Menus Index</A>
|
||||||
</BLOCKQUOTE>
|
</BLOCKQUOTE>
|
||||||
</BODY>
|
</BODY>
|
||||||
</HTML>
|
</HTML>
|
||||||
|
|
||||||
|
344
html/mgetty.html
344
html/mgetty.html
@ -1,172 +1,172 @@
|
|||||||
<HTML>
|
<HTML>
|
||||||
<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">
|
||||||
<META name="author" lang="en" "content="Michiel Broek">
|
<META name="author" lang="en" content="Michiel Broek">
|
||||||
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
||||||
<META name="description" lang="en" content="MBSE BBS Manual">
|
<META name="description" lang="en" content="MBSE BBS Manual">
|
||||||
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
||||||
<TITLE>Setup mgetty for MBSE BBS.</TITLE>
|
<TITLE>Setup mgetty for MBSE BBS.</TITLE>
|
||||||
<LINK rel=stylesheet HREF="manual.css">
|
<LINK rel=stylesheet HREF="manual.css">
|
||||||
</HEAD>
|
</HEAD>
|
||||||
<BODY>
|
<BODY>
|
||||||
<BLOCKQUOTE>
|
<BLOCKQUOTE>
|
||||||
<h5>Last update 29-Jan-2001</h5>
|
<h5>Last update 29-Jan-2001</h5>
|
||||||
<P> <P>
|
<P> <P>
|
||||||
|
|
||||||
<H1 ALIGN="CENTER">Setup mgetty for MBSE BBS</H1>
|
<H1 ALIGN="CENTER">Setup mgetty for MBSE BBS</H1>
|
||||||
<P>
|
<P>
|
||||||
To handle incoming calls you can use <strong>mgetty</strong> written by
|
To handle incoming calls you can use <strong>mgetty</strong> written by
|
||||||
Gert Doering, (gert@greenie.muc.de). Others may work. You have to compile
|
Gert Doering, (gert@greenie.muc.de). Others may work. You have to compile
|
||||||
<strong>mgetty</strong> with the -DFIDO flag to accept Fidonet mailer calls.
|
<strong>mgetty</strong> with the -DFIDO flag to accept Fidonet mailer calls.
|
||||||
If you want incoming PPP calls as well, add the -DAUTO_PPP as well. Below
|
If you want incoming PPP calls as well, add the -DAUTO_PPP as well. Below
|
||||||
you can see the mgetty.config and login.config for mgetty that I use. I
|
you can see the mgetty.config and login.config for mgetty that I use. I
|
||||||
have also included a part of my /etc/inittab to show how <strong>mgetty
|
have also included a part of my /etc/inittab to show how <strong>mgetty
|
||||||
</strong> will spawn from <strong>init</strong>.
|
</strong> will spawn from <strong>init</strong>.
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<HR>
|
<HR>
|
||||||
<PRE>
|
<PRE>
|
||||||
# inittab This is only a part of my /etc/inittab!
|
# inittab This is only a part of my /etc/inittab!
|
||||||
# In this example it runs in runlevel 3 and 4.
|
# In this example it runs in runlevel 3 and 4.
|
||||||
#
|
#
|
||||||
# Serial lines
|
# Serial lines
|
||||||
s1:34:respawn:/usr/local/sbin/mgetty -i /opt/mbse/etc/issue ttyS0
|
s1:34:respawn:/usr/local/sbin/mgetty -i /opt/mbse/etc/issue ttyS0
|
||||||
#
|
#
|
||||||
# End of /etc/inittab
|
# End of /etc/inittab
|
||||||
</PRE>
|
</PRE>
|
||||||
<HR>
|
<HR>
|
||||||
<PRE>
|
<PRE>
|
||||||
# mgetty configuration file: mgetty.config
|
# mgetty configuration file: mgetty.config
|
||||||
#
|
#
|
||||||
# ----- global section -----
|
# ----- global section -----
|
||||||
#
|
#
|
||||||
# In this section, you put the global defaults, per-port stuff is below
|
# In this section, you put the global defaults, per-port stuff is below
|
||||||
#
|
#
|
||||||
# set the global debug level to "4" (default from policy.h)
|
# set the global debug level to "4" (default from policy.h)
|
||||||
debug 4
|
debug 4
|
||||||
#
|
#
|
||||||
# set the local fax station id
|
# set the local fax station id
|
||||||
fax-id ++31-255-515973
|
fax-id ++31-255-515973
|
||||||
#
|
#
|
||||||
# access the modem(s) with 38400 bps
|
# access the modem(s) with 38400 bps
|
||||||
speed 38400
|
speed 38400
|
||||||
#
|
#
|
||||||
# use these options to make the /dev/tty-device owned by "uucp.uucp"
|
# use these options to make the /dev/tty-device owned by "uucp.uucp"
|
||||||
# and mode "rw-rw-r--" (0664). *LEADING ZERO NEEDED!*
|
# and mode "rw-rw-r--" (0664). *LEADING ZERO NEEDED!*
|
||||||
port-owner uucp
|
port-owner uucp
|
||||||
port-group uucp
|
port-group uucp
|
||||||
port-mode 0664
|
port-mode 0664
|
||||||
#
|
#
|
||||||
# use these options to make incoming faxes owned by "root.uucp"
|
# use these options to make incoming faxes owned by "root.uucp"
|
||||||
# and mode "rw-r-----" (0640). *LEADING ZERO NEEDED!*
|
# and mode "rw-r-----" (0640). *LEADING ZERO NEEDED!*
|
||||||
fax-owner root
|
fax-owner root
|
||||||
fax-group uucp
|
fax-group uucp
|
||||||
fax-mode 0640
|
fax-mode 0640
|
||||||
#
|
#
|
||||||
#
|
#
|
||||||
# ----- port specific section -----
|
# ----- port specific section -----
|
||||||
#
|
#
|
||||||
# Here you can put things that are valid only for one line, not the others
|
# Here you can put things that are valid only for one line, not the others
|
||||||
#
|
#
|
||||||
# Dynalink 1428EXTRA faxmodem at port 0 (COM1).
|
# Dynalink 1428EXTRA faxmodem at port 0 (COM1).
|
||||||
#
|
#
|
||||||
port ttyS0
|
port ttyS0
|
||||||
speed 57600
|
speed 57600
|
||||||
switchbd 19200
|
switchbd 19200
|
||||||
modem-type cls2
|
modem-type cls2
|
||||||
init-chat "" \d\dAT&F&C1&D3X4W2B0M0Q0V1H0&K3S0=0 OK
|
init-chat "" \d\dAT&F&C1&D3X4W2B0M0Q0V1H0&K3S0=0 OK
|
||||||
#
|
#
|
||||||
# end of mgetty.config
|
# end of mgetty.config
|
||||||
</PRE>
|
</PRE>
|
||||||
<HR>
|
<HR>
|
||||||
<PRE>
|
<PRE>
|
||||||
# login.config
|
# login.config
|
||||||
#
|
#
|
||||||
# This is a sample "login dispatcher" configuration file for mgetty
|
# This is a sample "login dispatcher" configuration file for mgetty
|
||||||
#
|
#
|
||||||
# Format:
|
# Format:
|
||||||
# username userid utmp_entry login_program [arguments]
|
# username userid utmp_entry login_program [arguments]
|
||||||
#
|
#
|
||||||
# Meaning:
|
# Meaning:
|
||||||
# for a "username" entered at mgettys login: prompt, call
|
# for a "username" entered at mgettys login: prompt, call
|
||||||
# "login_program" with [arguments], with the uid set to "userid",
|
# "login_program" with [arguments], with the uid set to "userid",
|
||||||
# and a USER_PROCESS utmp entry with ut_user = "utmp_entry"
|
# and a USER_PROCESS utmp entry with ut_user = "utmp_entry"
|
||||||
#
|
#
|
||||||
#
|
#
|
||||||
# Use this one for fido calls (login name /FIDO/ is handled specially)
|
# Use this one for fido calls (login name /FIDO/ is handled specially)
|
||||||
#
|
#
|
||||||
# mgetty has to be compiled with "-DFIDO", otherwise a fido call won't
|
# mgetty has to be compiled with "-DFIDO", otherwise a fido call won't
|
||||||
# be detected.
|
# be detected.
|
||||||
#
|
#
|
||||||
/FIDO/ mbse fido /opt/mbse/bin/mbcico @
|
/FIDO/ mbse fido /opt/mbse/bin/mbcico @
|
||||||
#
|
#
|
||||||
#
|
#
|
||||||
# Automatic PPP startup on receipt of LCP configure request (AutoPPP).
|
# Automatic PPP startup on receipt of LCP configure request (AutoPPP).
|
||||||
# mgetty has to be compiled with "-DAUTO_PPP" for this to work.
|
# mgetty has to be compiled with "-DAUTO_PPP" for this to work.
|
||||||
# Warning: Case is significant, AUTOPPP or autoppp won't work!
|
# Warning: Case is significant, AUTOPPP or autoppp won't work!
|
||||||
# Consult the "pppd" man page to find pppd options that work for you.
|
# Consult the "pppd" man page to find pppd options that work for you.
|
||||||
# See also PPP-HOWTO on how to set this up.
|
# See also PPP-HOWTO on how to set this up.
|
||||||
#
|
#
|
||||||
/AutoPPP/ - a_ppp /etc/ppp/paplogin
|
/AutoPPP/ - a_ppp /etc/ppp/paplogin
|
||||||
#
|
#
|
||||||
# This is the "standard" behaviour - *dont* set a userid or utmp
|
# This is the "standard" behaviour - *dont* set a userid or utmp
|
||||||
# entry here, otherwise /bin/login will fail!
|
# entry here, otherwise /bin/login will fail!
|
||||||
# This entry isn't really necessary: if it's missing, the built-in
|
# This entry isn't really necessary: if it's missing, the built-in
|
||||||
# default will do exactly this.
|
# default will do exactly this.
|
||||||
#
|
#
|
||||||
* - - /bin/login @
|
* - - /bin/login @
|
||||||
#
|
#
|
||||||
# You might use this instead, it will directly start the BBS when the call
|
# You might use this instead, it will directly start the BBS when the call
|
||||||
# is not a PPP call and not a Fidonet mailer. Use only one of these two!
|
# is not a PPP call and not a Fidonet mailer. Use only one of these two!
|
||||||
# THIS IS NOT YET TESTED!
|
# THIS IS NOT YET TESTED!
|
||||||
#
|
#
|
||||||
* - - /opt/mbse/bin/mbsebbs
|
* - - /opt/mbse/bin/mbsebbs
|
||||||
#
|
#
|
||||||
# end of login.config
|
# end of login.config
|
||||||
</PRE>
|
</PRE>
|
||||||
<HR>
|
<HR>
|
||||||
|
|
||||||
<P>
|
<P>
|
||||||
If you use /bin/login the users can get confused by the Unix login prompt.
|
If you use /bin/login the users can get confused by the Unix login prompt.
|
||||||
Most of them are used to DOS based bbs systems and will try to login with
|
Most of them are used to DOS based bbs systems and will try to login with
|
||||||
two names which won't work of course. For this reason I have added the
|
two names which won't work of course. For this reason I have added the
|
||||||
<strong>-i /opt/mbse/etc/issue</strong> options to the <strong>mgetty</strong>
|
<strong>-i /opt/mbse/etc/issue</strong> options to the <strong>mgetty</strong>
|
||||||
line in /etc/inittab. The file /opt/mbse/etc/issue is a plain textfile
|
line in /etc/inittab. The file /opt/mbse/etc/issue is a plain textfile
|
||||||
explaining users how to login to start the bbs. It could look like this:<br>
|
explaining users how to login to start the bbs. It could look like this:<br>
|
||||||
<pre>
|
<pre>
|
||||||
|
|
||||||
.--. Welcome at MBSE BBS Development.
|
.--. Welcome at MBSE BBS Development.
|
||||||
|o_o | --------------------------------
|
|o_o | --------------------------------
|
||||||
|:_/ |
|
|:_/ |
|
||||||
// \ \ This may or may not work today...
|
// \ \ This may or may not work today...
|
||||||
(| | )
|
(| | )
|
||||||
/'\_ _/`\
|
/'\_ _/`\
|
||||||
\___)=(___/
|
\___)=(___/
|
||||||
Powered by Linux.
|
Powered by Linux.
|
||||||
|
|
||||||
To start the bbs login with "bbs" without quotes.
|
To start the bbs login with "bbs" without quotes.
|
||||||
Voor het bbs login met "bbs" zonder aanhalingstekens.
|
Voor het bbs login met "bbs" zonder aanhalingstekens.
|
||||||
</pre>
|
</pre>
|
||||||
There is a default /opt/mbse/etc/issue installed by the installation script.
|
There is a default /opt/mbse/etc/issue installed by the installation script.
|
||||||
You need to edit this to insert your bbs name in it or even completely replace
|
You need to edit this to insert your bbs name in it or even completely replace
|
||||||
this file for a nicer one. Don't make it too big, don't put control characters
|
this file for a nicer one. Don't make it too big, don't put control characters
|
||||||
in it as this may prevent some mailers to connect to your system.
|
in it as this may prevent some mailers to connect to your system.
|
||||||
<p>
|
<p>
|
||||||
I discovered that some systems don't have the right permissions on the serial
|
I discovered that some systems don't have the right permissions on the serial
|
||||||
port for MBSE BBS. To fix this type the following commands:
|
port for MBSE BBS. To fix this type the following commands:
|
||||||
<pre>
|
<pre>
|
||||||
su
|
su
|
||||||
password: <em>enter root password here</em>
|
password: <em>enter root password here</em>
|
||||||
chmod 666 /dev/ttyS0
|
chmod 666 /dev/ttyS0
|
||||||
chown uucp.uucp /dev/ttyS0
|
chown uucp.uucp /dev/ttyS0
|
||||||
exit
|
exit
|
||||||
</pre>
|
</pre>
|
||||||
Note that /dev/ttyS0 is for COM1, /dev/ttyS1 for COM2 etc.
|
Note that /dev/ttyS0 is for COM1, /dev/ttyS1 for COM2 etc.
|
||||||
<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" width="33" height="35"> Go Back</A>
|
||||||
</BLOCKQUOTE>
|
</BLOCKQUOTE>
|
||||||
</BODY>
|
</BODY>
|
||||||
</HTML>
|
</HTML>
|
||||||
|
|
||||||
|
@ -1,117 +1,117 @@
|
|||||||
<HTML>
|
<HTML>
|
||||||
<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">
|
||||||
<META name="author" lang="en" "content="Michiel Broek">
|
<META name="author" lang="en" content="Michiel Broek">
|
||||||
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
||||||
<META name="description" lang="en" content="MBSE BBS Manual">
|
<META name="description" lang="en" content="MBSE BBS Manual">
|
||||||
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
||||||
<TITLE>BBS doors dropfiles.</TITLE>
|
<TITLE>BBS doors dropfiles.</TITLE>
|
||||||
<LINK rel=stylesheet HREF="../manual.css">
|
<LINK rel=stylesheet HREF="../manual.css">
|
||||||
</HEAD>
|
</HEAD>
|
||||||
<BODY>
|
<BODY>
|
||||||
<BLOCKQUOTE>
|
<BLOCKQUOTE>
|
||||||
<h5>Last update 02-Feb-2001</h5>
|
<h5>Last update 22-Oct-2001</h5>
|
||||||
<P> <P>
|
<P> <P>
|
||||||
|
|
||||||
<H1>BBS doors dropfiles.</H1>
|
<H1>BBS doors dropfiles.</H1>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<h3>Dropfiles for Unix BBS systems.</h3>
|
<h3>Dropfiles for Unix BBS systems.</h3>
|
||||||
<p>
|
<p>
|
||||||
Not all options that are available under DOS or OS/2 can be used with Unix
|
Not all options that are available under DOS or OS/2 can be used with Unix
|
||||||
BBS systems and must be faked.
|
BBS systems and must be faked.
|
||||||
<p> <P>
|
<p> <P>
|
||||||
|
|
||||||
<h3>DOOR.SYS format.</h3>
|
<h3>DOOR.SYS format.</h3>
|
||||||
<P>
|
<P>
|
||||||
The door.sys format is a 52 lines ascii textfile, each line is terminated with
|
The door.sys format is a 52 lines ascii textfile, each line is terminated with
|
||||||
a cr/lf pair. In the setup it is possible to force the creation of MM-DD-YYYY
|
a cr/lf pair. In the setup it is possible to force the creation of MM-DD-YYYY
|
||||||
dates instead of the MM-DD-YY style. Newer doors sometimes need that.
|
dates instead of the MM-DD-YY style. Newer doors sometimes need that.
|
||||||
<pre>
|
<pre>
|
||||||
Line Description
|
Line Description
|
||||||
----- -----------------------------------------------------------------
|
----- -----------------------------------------------------------------
|
||||||
1 Port, 2 characters in DOS format, p.e. COM1
|
1 Port, 5 characters in DOS format, p.e. COM1:
|
||||||
2 Effective Baudrate
|
2 Effective Baudrate
|
||||||
3 Databits
|
3 Databits
|
||||||
4 Nodenumber, 1..9999
|
4 Nodenumber, 1..9999
|
||||||
5 Locked baudrate
|
5 Locked baudrate
|
||||||
6 Screen display, Y=snoop on, N=snoop off. On Linux allways N.
|
6 Screen display, Y=snoop on, N=snoop off. On Linux allways N.
|
||||||
7 Printer Y=on N=off
|
7 Printer Y=on N=off
|
||||||
8 Page Bell Y=on N=off
|
8 Page Bell Y=on N=off
|
||||||
9 Caller alarm Y=on N=off
|
9 Caller alarm Y=on N=off
|
||||||
10 Users first name and lastname
|
10 Users first name and lastname
|
||||||
11 Users location
|
11 Users location
|
||||||
12 Voice/Home phone
|
12 Voice/Home phone
|
||||||
13 Work/Dataphone
|
13 Work/Dataphone
|
||||||
14 Password, empty if not available (stored coded).
|
14 Password, empty if not available (stored coded).
|
||||||
15 Security level, 0..32768
|
15 Security level, 0..32768
|
||||||
16 Users number of calls
|
16 Users number of calls
|
||||||
17 Users last call date MM-DD-YY
|
17 Users last call date MM-DD-YY
|
||||||
18 Seconds remaining this call
|
18 Seconds remaining this call
|
||||||
19 Time left in minutes
|
19 Time left in minutes
|
||||||
20 ANSI, "GR" is yes, otherwise ?
|
20 ANSI, "GR" is yes, otherwise ?
|
||||||
21 Screen length
|
21 Screen length
|
||||||
22 User mode, always N
|
22 User mode, always N
|
||||||
23 Always blank
|
23 Always blank
|
||||||
24 Always blank
|
24 Always blank
|
||||||
25 Subscription expire date MM-DD-YY
|
25 Subscription expire date MM-DD-YY
|
||||||
26 Users record number
|
26 Users record number
|
||||||
27 Default protocol
|
27 Default protocol
|
||||||
28 Users total number of uploads
|
28 Users total number of uploads
|
||||||
29 Users total number of downloads
|
29 Users total number of downloads
|
||||||
30 Users daily download kilobytes total
|
30 Users daily download kilobytes total
|
||||||
31 Daily download kilobyte limit
|
31 Daily download kilobyte limit
|
||||||
32 Users date of birth MM-DD-YY
|
32 Users date of birth MM-DD-YY
|
||||||
33 Path to users database files Cannot be used on Linux.
|
33 Path to users database files Cannot be used on Linux.
|
||||||
34 Path to message database files
|
34 Path to message database files
|
||||||
35 Sysop first and last name
|
35 Sysop first and last name
|
||||||
36 Users handle
|
36 Users handle
|
||||||
37 Next event starting time or "none"
|
37 Next event starting time or "none"
|
||||||
38 Error-free connection Y=Yes or N=No
|
38 Error-free connection Y=Yes or N=No
|
||||||
39 Always set to N
|
39 Always set to N
|
||||||
40 Always set to Y
|
40 Always set to Y
|
||||||
41 Text color as defined in setup 7 = gray.
|
41 Text color as defined in setup 7 = gray.
|
||||||
42 Always 0
|
42 Always 0
|
||||||
43 Last new files scan date MM-DD-YY
|
43 Last new files scan date MM-DD-YY
|
||||||
44 Time of this call HH:MM
|
44 Time of this call HH:MM
|
||||||
45 Time of last call HH:MM
|
45 Time of last call HH:MM
|
||||||
46 Always set to 32768
|
46 Always set to 32768
|
||||||
47 Number of files downloaded today
|
47 Number of files downloaded today
|
||||||
48 Total kilobytes uploaded
|
48 Total kilobytes uploaded
|
||||||
49 Total kilobytes downloaded
|
49 Total kilobytes downloaded
|
||||||
50 Comment stored in users record
|
50 Comment stored in users record
|
||||||
51 Always set to 0
|
51 Always set to 0
|
||||||
52 Total number of messages posted
|
52 Total number of messages posted
|
||||||
</pre>
|
</pre>
|
||||||
<P> <P>
|
<P> <P>
|
||||||
|
|
||||||
<h3>DORINFOn.DEF dropfile.</H3>
|
<h3>DORINFOn.DEF dropfile.</H3>
|
||||||
<P>
|
<P>
|
||||||
The DORINFOn.DEF file is a 12 lines ascii textfile, each line terminated with
|
The DORINFOn.DEF file is a 12 lines ascii textfile, each line terminated with
|
||||||
a cr/lf pair. All characters in the file are uppercase. The n in the filename
|
a cr/lf pair. All characters in the file are uppercase. The n in the filename
|
||||||
represents the current line number and will be between 1 and 9. Using number
|
represents the current line number and will be between 1 and 9. Using number
|
||||||
1 seems always fine.
|
1 seems always fine.
|
||||||
<pre>
|
<pre>
|
||||||
Line Description
|
Line Description
|
||||||
------ ------------------------------------------------------------------
|
------ ------------------------------------------------------------------
|
||||||
1 System name
|
1 System name
|
||||||
2 Sysop's first name
|
2 Sysop's first name
|
||||||
3 Sysop's last name
|
3 Sysop's last name
|
||||||
4 Port name, like COM1, COM2 etc. COM0 = local
|
4 Port name, like COM1, COM2 etc. COM0 = local
|
||||||
5 Baudrate format: "19200 BAUD-R,N,8,1"
|
5 Baudrate format: "19200 BAUD-R,N,8,1"
|
||||||
6 Always 0
|
6 Always 0
|
||||||
7 Users firstname
|
7 Users firstname
|
||||||
8 Users lastname
|
8 Users lastname
|
||||||
9 Users location
|
9 Users location
|
||||||
10 Graphics mode: 0=no, 1=ANSI, 2=Avatar, 3=ANSI+Avatar
|
10 Graphics mode: 0=no, 1=ANSI, 2=Avatar, 3=ANSI+Avatar
|
||||||
11 Security level, 0..32767
|
11 Security level, 0..32767
|
||||||
12 Time left in minutes
|
12 Time left in minutes
|
||||||
</pre>
|
</pre>
|
||||||
<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" width="33" height="35"> Go Back</A>
|
||||||
</BLOCKQUOTE>
|
</BLOCKQUOTE>
|
||||||
</BODY>
|
</BODY>
|
||||||
</HTML>
|
</HTML>
|
||||||
|
|
||||||
|
@ -1,98 +1,98 @@
|
|||||||
<HTML>
|
<HTML>
|
||||||
<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">
|
||||||
<META name="author" lang="en" "content="Michiel Broek">
|
<META name="author" lang="en" content="Michiel Broek">
|
||||||
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
||||||
<META name="description" lang="en" content="MBSE BBS Manual">
|
<META name="description" lang="en" content="MBSE BBS Manual">
|
||||||
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
||||||
<TITLE>Howto setup an FTP server to work with MBSE BBS.</TITLE>
|
<TITLE>Howto setup an FTP server to work with MBSE BBS.</TITLE>
|
||||||
<LINK rel=stylesheet HREF="../manual.css">
|
<LINK rel=stylesheet HREF="../manual.css">
|
||||||
</HEAD>
|
</HEAD>
|
||||||
<BODY>
|
<BODY>
|
||||||
<BLOCKQUOTE>
|
<BLOCKQUOTE>
|
||||||
<h5>Last update 06-Jun-2001</h5>
|
<h5>Last update 06-Jun-2001</h5>
|
||||||
<P> <P>
|
<P> <P>
|
||||||
|
|
||||||
<H1>How to setup an FTP server to work with MBSE BBS.</H1>
|
<H1>How to setup an FTP server to work with MBSE BBS.</H1>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
In order to let MBSE BBS and your FTP server to both function together you must
|
In order to let MBSE BBS and your FTP server to both function together you must
|
||||||
organize a special file structure. Note that even if you don't setup an FTP
|
organize a special file structure. Note that even if you don't setup an FTP
|
||||||
server you must still create a structure like this for the fidonet mailer,
|
server you must still create a structure like this for the fidonet mailer,
|
||||||
if you don't, <strong>mail and files will get lost!</strong>
|
if you don't, <strong>mail and files will get lost!</strong>
|
||||||
Note that this description is written for wu-ftpd, on your distribution there
|
Note that this description is written for wu-ftpd, on your distribution there
|
||||||
may be another ftpd installed. <font color=red><u>Don't use mbftpd yet!</u></font>
|
may be another ftpd installed. <font color=red><u>Don't use mbftpd yet!</u></font>
|
||||||
<P>
|
<P>
|
||||||
<H4>The filestructure I used is as follows:</H4>
|
<H4>The filestructure I used is as follows:</H4>
|
||||||
<PRE>
|
<PRE>
|
||||||
/var/spool/mbse/ftp/pub/dos_util/dos_4dos - Public download areas
|
/var/spool/mbse/ftp/pub/dos_util/dos_4dos - Public download areas
|
||||||
| | | /dos_disk
|
| | | /dos_disk
|
||||||
| | | /dos_file
|
| | | /dos_file
|
||||||
| | /virnet/mcafee
|
| | /virnet/mcafee
|
||||||
| | /win16
|
| | /win16
|
||||||
| | /win32
|
| | /win32
|
||||||
| /bin - FTP bin directory
|
| /bin - FTP bin directory
|
||||||
| /etc - FTP etc directory
|
| /etc - FTP etc directory
|
||||||
| /incoming - FTP public upload.
|
| /incoming - FTP public upload.
|
||||||
/mail/out - Your default outbound
|
/mail/out - Your default outbound
|
||||||
| /out.009 - Outbound Zone 9
|
| /out.009 - Outbound Zone 9
|
||||||
| /inbound - Inbound directory
|
| /inbound - Inbound directory
|
||||||
/raonly/upload - Non-public download areas
|
/raonly/upload - Non-public download areas
|
||||||
| /sysop
|
| /sysop
|
||||||
| /logfiles
|
| /logfiles
|
||||||
/tic_queue - Queue for .tic files.
|
/tic_queue - Queue for .tic files.
|
||||||
|
|
||||||
</PRE>
|
</PRE>
|
||||||
|
|
||||||
In order to give DOS style names for fidonet sessions you must set the
|
In order to give DOS style names for fidonet sessions you must set the
|
||||||
DOS path and Unix path in <strong>mbsetup</strong> (1.3.11 and 1.3.12) to
|
DOS path and Unix path in <strong>mbsetup</strong> (1.3.11 and 1.3.12) to
|
||||||
<strong>"m:"</strong> and <strong>"/var/spool/mbse"</strong>. Note that to get
|
<strong>"m:"</strong> and <strong>"/var/spool/mbse"</strong>. Note that to get
|
||||||
forwarding of .tic files to work the <strong>tic_queue</strong> must be a
|
forwarding of .tic files to work the <strong>tic_queue</strong> must be a
|
||||||
subdirectory of "/var/spool/mbse" too. You could actually use any drive letter for
|
subdirectory of "/var/spool/mbse" too. You could actually use any drive letter for
|
||||||
the DOS path.
|
the DOS path.
|
||||||
<P>
|
<P>
|
||||||
This means that a fidonet file attach from the dos_4dos public download
|
This means that a fidonet file attach from the dos_4dos public download
|
||||||
directory shall get the subject "M:\FTP\PUB\DOS_UTIL\DOS_4DOS\COMMAND.ZIP".
|
directory shall get the subject "M:\FTP\PUB\DOS_UTIL\DOS_4DOS\COMMAND.ZIP".
|
||||||
|
|
||||||
<P>
|
<P>
|
||||||
As you can see, anonymous ftp users can't get to the mail, non-public
|
As you can see, anonymous ftp users can't get to the mail, non-public
|
||||||
downloads etc. Normally, your BBS users have unix accounts and will be able
|
downloads etc. Normally, your BBS users have unix accounts and will be able
|
||||||
to do a ftp login and access any directory on your system. Because the bbs
|
to do a ftp login and access any directory on your system. Because the bbs
|
||||||
users have <b>mbsebbs</b> as their shell and this shell is not in the file
|
users have <b>mbsebbs</b> as their shell and this shell is not in the file
|
||||||
<b>/etc/shells</b> the ftp daemon will not let the bbs users in. So even
|
<b>/etc/shells</b> the ftp daemon will not let the bbs users in. So even
|
||||||
your own bbs users must login as anonymous to get files from the ftp server.
|
your own bbs users must login as anonymous to get files from the ftp server.
|
||||||
<P>
|
<P>
|
||||||
Note the following directory permissions MUST BE SET!!!!::: See also
|
Note the following directory permissions MUST BE SET!!!!::: See also
|
||||||
the man pages for the DARPA ftpd server.
|
the man pages for the DARPA ftpd server.
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<PRE>
|
<PRE>
|
||||||
Directory owner group mode perms
|
Directory owner group mode perms
|
||||||
------------------------------- ----- ----- ---- ----------
|
------------------------------- ----- ----- ---- ----------
|
||||||
/var/spool/mbse mbse bbs 0755 drwxr-xr-x
|
/var/spool/mbse mbse bbs 0755 drwxr-xr-x
|
||||||
/var/spool/mbse/ftp root wheel 0555 dr-xr-xr-x
|
/var/spool/mbse/ftp root wheel 0555 dr-xr-xr-x
|
||||||
/var/spool/mbse/ftp/bin root wheel 0555 dr-xr-xr-x
|
/var/spool/mbse/ftp/bin root wheel 0555 dr-xr-xr-x
|
||||||
/var/spool/mbse/ftp/bin/ls root bin 0111 ---x--x--x
|
/var/spool/mbse/ftp/bin/ls root bin 0111 ---x--x--x
|
||||||
/var/spool/mbse/ftp/etc root root 0555 dr-xr-xr-x
|
/var/spool/mbse/ftp/etc root root 0555 dr-xr-xr-x
|
||||||
/var/spool/mbse/ftp/etc/passwd root root 0444 -r--r--r--
|
/var/spool/mbse/ftp/etc/passwd root root 0444 -r--r--r--
|
||||||
/var/spool/mbse/ftp/etc/group root root 0444 -r--r--r--
|
/var/spool/mbse/ftp/etc/group root root 0444 -r--r--r--
|
||||||
/var/spool/mbse/ftp/pub mbse bbs 0775 drwxrwxr-x
|
/var/spool/mbse/ftp/pub mbse bbs 0775 drwxrwxr-x
|
||||||
/var/spool/mbse/ftp/incoming ftp users 0755 drwxr-xr-x
|
/var/spool/mbse/ftp/incoming ftp users 0755 drwxr-xr-x
|
||||||
|
|
||||||
</PRE>
|
</PRE>
|
||||||
Note that all subdirectories under ../pub also must be owned by <strong>mbse
|
Note that all subdirectories under ../pub also must be owned by <strong>mbse
|
||||||
</strong> and group <strong>bbs</strong> and have at least mode 775 as long
|
</strong> and group <strong>bbs</strong> and have at least mode 775 as long
|
||||||
as it are real bbs subdirectories. The bbs will maintain these directories
|
as it are real bbs subdirectories. The bbs will maintain these directories
|
||||||
automatic and must have the rights to do so.
|
automatic and must have the rights to do so.
|
||||||
|
|
||||||
<P>
|
<P>
|
||||||
In the /var/spool/mbse/ftp/etc/group file, add the group bbs so that your directory
|
In the /var/spool/mbse/ftp/etc/group file, add the group bbs so that your directory
|
||||||
listings give the proper groupname instead of a number.
|
listings give the proper groupname instead of a number.
|
||||||
<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" width="33" height="35"> Go Back</A>
|
||||||
</BLOCKQUOTE>
|
</BLOCKQUOTE>
|
||||||
</BODY>
|
</BODY>
|
||||||
</HTML>
|
</HTML>
|
||||||
|
|
||||||
|
@ -1,46 +1,46 @@
|
|||||||
<HTML>
|
<HTML>
|
||||||
<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">
|
||||||
<META name="author" lang="en" "content="Michiel Broek">
|
<META name="author" lang="en" content="Michiel Broek">
|
||||||
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
||||||
<META name="description" lang="en" content="MBSE BBS Manual">
|
<META name="description" lang="en" content="MBSE BBS Manual">
|
||||||
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
||||||
<TITLE>Miscellaneous Documents</TITLE>
|
<TITLE>Miscellaneous Documents</TITLE>
|
||||||
<LINK rel=stylesheet HREF="../manual.css">
|
<LINK rel=stylesheet HREF="../manual.css">
|
||||||
</HEAD>
|
</HEAD>
|
||||||
<BODY>
|
<BODY>
|
||||||
<BLOCKQUOTE>
|
<BLOCKQUOTE>
|
||||||
<h5>Last update 02-Feb-2001</h5>
|
<h5>Last update 02-Feb-2001</h5>
|
||||||
<P> <P>
|
<P> <P>
|
||||||
|
|
||||||
<h1>Miscellaneous Documents</h1>
|
<h1>Miscellaneous Documents</h1>
|
||||||
|
|
||||||
<h3>Introduction</h3>
|
<h3>Introduction</h3>
|
||||||
<P>
|
<P>
|
||||||
This is an overview of used unofficial documents for the development of the
|
This is an overview of used unofficial documents for the development of the
|
||||||
MBSE BBS package.
|
MBSE BBS package.
|
||||||
<P>
|
<P>
|
||||||
Michiel Broek.
|
Michiel Broek.
|
||||||
<P>
|
<P>
|
||||||
<hr>
|
<hr>
|
||||||
<h3>Documents</h3>
|
<h3>Documents</h3>
|
||||||
<ul>
|
<ul>
|
||||||
<li><a href="filefind.html">Implementation and Usage of Filefind Utilities, R.Williamson</a>
|
<li><a href="filefind.html">Implementation and Usage of Filefind Utilities, R.Williamson</a>
|
||||||
<li><a href="ipmailer.html">Integration of IP-Nodes in the nodelist, L.Behet</a>
|
<li><a href="ipmailer.html">Integration of IP-Nodes in the nodelist, L.Behet</a>
|
||||||
<li><a href="fileid.html">FILE_ID.DIZ Information, R.Moller</a>
|
<li><a href="fileid.html">FILE_ID.DIZ Information, R.Moller</a>
|
||||||
<li><a href="ftpserver.html">How to setup an FTP server with MBSE BBS, M.Broek</a>
|
<li><a href="ftpserver.html">How to setup an FTP server with MBSE BBS, M.Broek</a>
|
||||||
<li><a href="jam.html">JAM Message Base Proposal, J.Homrighausen</a>
|
<li><a href="jam.html">JAM Message Base Proposal, J.Homrighausen</a>
|
||||||
<li><a href="outbound.html">Binkley style mailer outbound for MBSE BBS, M.Broek</a>
|
<li><a href="outbound.html">Binkley style mailer outbound for MBSE BBS, M.Broek</a>
|
||||||
<li><a href="semafore.html">Semafore files for MBSE BBS, M.Broek</a>
|
<li><a href="semafore.html">Semafore files for MBSE BBS, M.Broek</a>
|
||||||
<li><a href="usleep.html">System load and usleep() code, M.Broek</a>
|
<li><a href="usleep.html">System load and usleep() code, M.Broek</a>
|
||||||
<li><a href="dropfile.html">BBS doors dropfiles, M. Broek</a>
|
<li><a href="dropfile.html">BBS doors dropfiles, M. Broek</a>
|
||||||
</ul>
|
</ul>
|
||||||
|
|
||||||
<HR>
|
<HR>
|
||||||
|
|
||||||
<A HREF="../index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Index" Border="0" width="33" height="35">Back to Index</A>
|
<A HREF="../index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Index" Border="0" width="33" height="35">Back to Index</A>
|
||||||
</BLOCKQUOTE>
|
</BLOCKQUOTE>
|
||||||
</BODY>
|
</BODY>
|
||||||
</HTML>
|
</HTML>
|
||||||
|
|
||||||
|
@ -1,172 +1,172 @@
|
|||||||
<HTML>
|
<HTML>
|
||||||
<HEAD>
|
<HEAD>
|
||||||
<TITLE>Integration of IP-Nodes in the nodelist.</TITLE>
|
<TITLE>Integration of IP-Nodes in the nodelist.</TITLE>
|
||||||
</HEAD>
|
</HEAD>
|
||||||
|
|
||||||
<!-- Background white, links blue (unvisited), navy (visited), red (active) -->
|
<!-- Background white, links blue (unvisited), navy (visited), red (active) -->
|
||||||
<BODY
|
<BODY
|
||||||
BGCOLOR="#FFFFFF"
|
BGCOLOR="#FFFFFF"
|
||||||
TEXT="#000000"
|
TEXT="#000000"
|
||||||
LINK="#0000FF"
|
LINK="#0000FF"
|
||||||
VLINK="#000080"
|
VLINK="#000080"
|
||||||
ALINK="#FF0000"
|
ALINK="#FF0000"
|
||||||
>
|
>
|
||||||
<PRE>
|
<PRE>
|
||||||
Publication: FSP-????
|
Publication: FSP-????
|
||||||
Revision: 1
|
Revision: 1
|
||||||
Title: Integration of IP-Nodes in the nodelist (FTS-0005)
|
Title: Integration of IP-Nodes in the nodelist (FTS-0005)
|
||||||
Author: Lothar Behet, 2:2446/301
|
Author: Lothar Behet, 2:2446/301
|
||||||
Revision Date: 25 October 1998
|
Revision Date: 25 October 1998
|
||||||
Expiry Date:
|
Expiry Date:
|
||||||
----------------------------------------------------------------------
|
----------------------------------------------------------------------
|
||||||
|
|
||||||
Contents:
|
Contents:
|
||||||
1. Required fields according to FTS-0005, basic flags for ip-nodes
|
1. Required fields according to FTS-0005, basic flags for ip-nodes
|
||||||
2. Optional extensions
|
2. Optional extensions
|
||||||
3. Addendum
|
3. Addendum
|
||||||
----------------------------------------------------------------------
|
----------------------------------------------------------------------
|
||||||
|
|
||||||
1. Description of the nodelist format
|
1. Description of the nodelist format
|
||||||
--------------------------------------
|
--------------------------------------
|
||||||
|
|
||||||
Every node entry contains the following 8 fields:
|
Every node entry contains the following 8 fields:
|
||||||
|
|
||||||
keyword,node_number,node_name,location,sysop_name,
|
keyword,node_number,node_name,location,sysop_name,
|
||||||
phone_number,baud_rate,flags
|
phone_number,baud_rate,flags
|
||||||
|
|
||||||
Certain fields have defined values according to FTS-0005.
|
Certain fields have defined values according to FTS-0005.
|
||||||
|
|
||||||
1.1. Implementation for IP-connectivity
|
1.1. Implementation for IP-connectivity
|
||||||
Because of the limited characterset in the phone_field and
|
Because of the limited characterset in the phone_field and
|
||||||
to avoid any misinterpretion by conventional dialing, the
|
to avoid any misinterpretion by conventional dialing, the
|
||||||
ip-specific address-information is entered in another field
|
ip-specific address-information is entered in another field
|
||||||
and there are additional flags required.
|
and there are additional flags required.
|
||||||
|
|
||||||
1.1.1. Field #1 (keyword) is PVT for an ip-only node without
|
1.1.1. Field #1 (keyword) is PVT for an ip-only node without
|
||||||
conventional phone number related connectivity. In this
|
conventional phone number related connectivity. In this
|
||||||
case, the phone field contains "-Unpublished-" according
|
case, the phone field contains "-Unpublished-" according
|
||||||
to FTS-0005.
|
to FTS-0005.
|
||||||
|
|
||||||
1.1.2. Field #2 (node_number) contains the node number within his
|
1.1.2. Field #2 (node_number) contains the node number within his
|
||||||
net and zone.
|
net and zone.
|
||||||
|
|
||||||
1.1.3. Field #3 (node_name) is used for the FQDN (Fully Qualified
|
1.1.3. Field #3 (node_name) is used for the FQDN (Fully Qualified
|
||||||
Domain Name) or the ip-address.
|
Domain Name) or the ip-address.
|
||||||
|
|
||||||
1.1.4. Field #4 (location) contains the geographical location of
|
1.1.4. Field #4 (location) contains the geographical location of
|
||||||
the node. While some nets/regions cannot supply their
|
the node. While some nets/regions cannot supply their
|
||||||
ip-only nodes with a adequate link, these nodes may be
|
ip-only nodes with a adequate link, these nodes may be
|
||||||
collected in a seperate net or region, until their original
|
collected in a seperate net or region, until their original
|
||||||
net/region support additional ip-connectivity. This special
|
net/region support additional ip-connectivity. This special
|
||||||
net/region is definitely a temporary solution for routing
|
net/region is definitely a temporary solution for routing
|
||||||
within a region or zone!
|
within a region or zone!
|
||||||
|
|
||||||
1.1.5. Field #5 (sysop_name) represants the name of the system
|
1.1.5. Field #5 (sysop_name) represants the name of the system
|
||||||
operator.
|
operator.
|
||||||
|
|
||||||
1.1.6. Field #6 (phone_number) contains the phone_number for
|
1.1.6. Field #6 (phone_number) contains the phone_number for
|
||||||
conventional connectivity. In case of an ip-only node
|
conventional connectivity. In case of an ip-only node
|
||||||
it must contain "-Unpublished-".
|
it must contain "-Unpublished-".
|
||||||
|
|
||||||
1.1.7. Field #7 (baud_rate) contains the maximum baud rate for
|
1.1.7. Field #7 (baud_rate) contains the maximum baud rate for
|
||||||
conventional connectivity or 300 in case of an ip_only node.
|
conventional connectivity or 300 in case of an ip_only node.
|
||||||
|
|
||||||
1.1.8. Field #8 (flags) represents operational definitions for the
|
1.1.8. Field #8 (flags) represents operational definitions for the
|
||||||
node.
|
node.
|
||||||
Note that these are user flags.
|
Note that these are user flags.
|
||||||
The ip-flags consist of two parts:
|
The ip-flags consist of two parts:
|
||||||
A basic transport and an optional non-standard port,
|
A basic transport and an optional non-standard port,
|
||||||
seperated by a colon.
|
seperated by a colon.
|
||||||
The default port may be omitted, but is listed as optional
|
The default port may be omitted, but is listed as optional
|
||||||
parameter in this document. In some cases, two flag names
|
parameter in this document. In some cases, two flag names
|
||||||
are mentioned:
|
are mentioned:
|
||||||
The second one is supported by some software nowadays, but
|
The second one is supported by some software nowadays, but
|
||||||
these values may conflict with other programs, which not
|
these values may conflict with other programs, which not
|
||||||
completely decode the length of each individual flag (i.e.
|
completely decode the length of each individual flag (i.e.
|
||||||
TELN conflicts with the T-flag for online-time)
|
TELN conflicts with the T-flag for online-time)
|
||||||
Additional flags for ip-nodes are:
|
Additional flags for ip-nodes are:
|
||||||
|
|
||||||
1.1.8.1. IBN[:24554] (Argus: BND[:24554])
|
1.1.8.1. IBN[:24554] (Argus: BND[:24554])
|
||||||
BinkP protocol
|
BinkP protocol
|
||||||
|
|
||||||
1.1.8.2. IFC[:60179]
|
1.1.8.2. IFC[:60179]
|
||||||
Raw protocol as used by ifcico
|
Raw protocol as used by ifcico
|
||||||
|
|
||||||
1.1.8.3. ITN[:23] (Argus: TEL[:23])
|
1.1.8.3. ITN[:23] (Argus: TEL[:23])
|
||||||
Telnet protocol. Some variants of ifcico support Telnet
|
Telnet protocol. Some variants of ifcico support Telnet
|
||||||
on port 60177, which should be added as additional flag
|
on port 60177, which should be added as additional flag
|
||||||
ITN:60177.
|
ITN:60177.
|
||||||
|
|
||||||
1.1.8.4. IVM[:3141]
|
1.1.8.4. IVM[:3141]
|
||||||
Vmodem protocol
|
Vmodem protocol
|
||||||
|
|
||||||
1.1.8.5. IP
|
1.1.8.5. IP
|
||||||
General flag for special protocol specifications, if the
|
General flag for special protocol specifications, if the
|
||||||
flags conforming to 1.1.8.1. to 1.1.8.4. are not relevant.
|
flags conforming to 1.1.8.1. to 1.1.8.4. are not relevant.
|
||||||
|
|
||||||
1.1.9. Comments on the proposed nodelist flags
|
1.1.9. Comments on the proposed nodelist flags
|
||||||
The additional flagnames in () are supported at this moment
|
The additional flagnames in () are supported at this moment
|
||||||
by Argus, based on the use in z2r50. But the TEL[NET]-flag
|
by Argus, based on the use in z2r50. But the TEL[NET]-flag
|
||||||
stays in conflict with the generally in all zones and
|
stays in conflict with the generally in all zones and
|
||||||
regions used T-flag (online time according to FSC-0062).
|
regions used T-flag (online time according to FSC-0062).
|
||||||
|
|
||||||
|
|
||||||
2. Optional extensions for future use
|
2. Optional extensions for future use
|
||||||
--------------------------------------
|
--------------------------------------
|
||||||
|
|
||||||
While the above mentioned flags (1.1.8.1 to 1.1.8.4) define a
|
While the above mentioned flags (1.1.8.1 to 1.1.8.4) define a
|
||||||
minimum set of operational flags for ip-nodes, several additions
|
minimum set of operational flags for ip-nodes, several additions
|
||||||
are already foreseeable at this moment.
|
are already foreseeable at this moment.
|
||||||
|
|
||||||
2.1. Additional sessions_handshake parameters
|
2.1. Additional sessions_handshake parameters
|
||||||
There is at least one program, which supports several
|
There is at least one program, which supports several
|
||||||
transport protocols according to chapter 1.1.8. on a
|
transport protocols according to chapter 1.1.8. on a
|
||||||
single port. If other programs should imitate this habit,
|
single port. If other programs should imitate this habit,
|
||||||
then the following extension to the flag suite 1.1.8.
|
then the following extension to the flag suite 1.1.8.
|
||||||
(transport[:port[:handshake]])is advised:
|
(transport[:port[:handshake]])is advised:
|
||||||
|
|
||||||
2.1.1. FTS-0001 session handshake: 1
|
2.1.1. FTS-0001 session handshake: 1
|
||||||
2.1.2. Yoohoo session handshake : Y
|
2.1.2. Yoohoo session handshake : Y
|
||||||
2.1.3. EMSI sessions handshake : E
|
2.1.3. EMSI sessions handshake : E
|
||||||
2.1.4. BinkP sessions handshake : B
|
2.1.4. BinkP sessions handshake : B
|
||||||
|
|
||||||
2.2. Non-handshaking protocols
|
2.2. Non-handshaking protocols
|
||||||
While the definitions until this chapter describe direct
|
While the definitions until this chapter describe direct
|
||||||
handshaking sessions with optional password authentification,
|
handshaking sessions with optional password authentification,
|
||||||
there are several other methods for the tunneling of fidonet
|
there are several other methods for the tunneling of fidonet
|
||||||
data via the internet available.
|
data via the internet available.
|
||||||
The setup of these connections does not rely on the nodelist
|
The setup of these connections does not rely on the nodelist
|
||||||
(at this moment of writing), but we can think of standard
|
(at this moment of writing), but we can think of standard
|
||||||
setup procedures to use the nodelist for configuration of
|
setup procedures to use the nodelist for configuration of
|
||||||
this additional transport methods.
|
this additional transport methods.
|
||||||
Therefore the following flags 2.2.1. to 2.2.4. are advised
|
Therefore the following flags 2.2.1. to 2.2.4. are advised
|
||||||
for at least informational purpose.
|
for at least informational purpose.
|
||||||
|
|
||||||
2.2.1. IFT
|
2.2.1. IFT
|
||||||
FTP (File Transfer Protocol)
|
FTP (File Transfer Protocol)
|
||||||
|
|
||||||
2.2.2. ITX
|
2.2.2. ITX
|
||||||
TransX, an Email based variant
|
TransX, an Email based variant
|
||||||
|
|
||||||
2.2.3. IUC
|
2.2.3. IUC
|
||||||
Uuencoded packet (one packet per message)
|
Uuencoded packet (one packet per message)
|
||||||
|
|
||||||
2.2.4. IEM
|
2.2.4. IEM
|
||||||
Email based (generally, without exact specification at
|
Email based (generally, without exact specification at
|
||||||
this moment)
|
this moment)
|
||||||
|
|
||||||
|
|
||||||
3. Addendum
|
3. Addendum
|
||||||
------------
|
------------
|
||||||
|
|
||||||
This proposal is based on a maximum compatibility to generally used
|
This proposal is based on a maximum compatibility to generally used
|
||||||
definitions and standards within the Fidonet community.
|
definitions and standards within the Fidonet community.
|
||||||
Future developments might make additions necessary, if they can not
|
Future developments might make additions necessary, if they can not
|
||||||
be expressed with the existing set of flags as defined by this FSP.
|
be expressed with the existing set of flags as defined by this FSP.
|
||||||
</PRE>
|
</PRE>
|
||||||
|
|
||||||
<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" width="33" height="35"> Go Back</A>
|
||||||
|
|
||||||
</BODY>
|
</BODY>
|
||||||
</HTML>
|
</HTML>
|
||||||
|
|
||||||
|
1276
html/misc/jam.html
1276
html/misc/jam.html
File diff suppressed because it is too large
Load Diff
@ -1,114 +1,114 @@
|
|||||||
<HTML>
|
<HTML>
|
||||||
<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">
|
||||||
<META name="author" lang="en" "content="Michiel Broek">
|
<META name="author" lang="en" content="Michiel Broek">
|
||||||
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
||||||
<META name="description" lang="en" content="MBSE BBS Manual">
|
<META name="description" lang="en" content="MBSE BBS Manual">
|
||||||
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
||||||
<TITLE>Binkley style outbound with MBSE BBS.</TITLE>
|
<TITLE>Binkley style outbound with MBSE BBS.</TITLE>
|
||||||
<LINK rel=stylesheet HREF="../manual.css">
|
<LINK rel=stylesheet HREF="../manual.css">
|
||||||
</HEAD>
|
</HEAD>
|
||||||
<BODY>
|
<BODY>
|
||||||
<BLOCKQUOTE>
|
<BLOCKQUOTE>
|
||||||
<h5>Last update 02-Feb-2001</h5>
|
<h5>Last update 02-Feb-2001</h5>
|
||||||
<P> <P>
|
<P> <P>
|
||||||
|
|
||||||
<h1>Binkly style outbound documentation for MBSE BBS.</H1>
|
<h1>Binkly style outbound documentation for MBSE BBS.</H1>
|
||||||
<P>
|
<P>
|
||||||
The MBSE BBS outbound directory structure is BinkleyTerm compatible, with
|
The MBSE BBS outbound directory structure is BinkleyTerm compatible, with
|
||||||
domains and point subdirectories (full 5d). There are separate "protected" and
|
domains and point subdirectories (full 5d). There are separate "protected" and
|
||||||
"unknown" inbound directories for incoming sessions. Files received during
|
"unknown" inbound directories for incoming sessions. Files received during
|
||||||
outbound sessions are always placed in the "protected" inbound directory. Only
|
outbound sessions are always placed in the "protected" inbound directory. Only
|
||||||
the "protected" inbound directory is processed automatic.
|
the "protected" inbound directory is processed automatic.
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<P>
|
<P>
|
||||||
Note that this is a very simple document and that it is not even finished.
|
Note that this is a very simple document and that it is not even finished.
|
||||||
<P>
|
<P>
|
||||||
<PRE>
|
<PRE>
|
||||||
.pol Poll flag, is handled as crash immediate, the length is always 0 bytes.
|
.pol Poll flag, is handled as crash immediate, the length is always 0 bytes.
|
||||||
|
|
||||||
Flow files are files with the full pathnames to the files to send
|
Flow files are files with the full pathnames to the files to send
|
||||||
on disk. Names are translated by MBSE BBS to full DOS filenames and
|
on disk. Names are translated by MBSE BBS to full DOS filenames and
|
||||||
paths depending on your setup.
|
paths depending on your setup.
|
||||||
If you use it then it is importand that you think about the directory
|
If you use it then it is importand that you think about the directory
|
||||||
structure to use. See also the documentation about the setup of the
|
structure to use. See also the documentation about the setup of the
|
||||||
<a href="ftpserver.html">ftp server</a>
|
<a href="ftpserver.html">ftp server</a>
|
||||||
The filenames may be prepended with a special character:
|
The filenames may be prepended with a special character:
|
||||||
# = Truncate file after sent.
|
# = Truncate file after sent.
|
||||||
- or ^ = Kill file after sent.
|
- or ^ = Kill file after sent.
|
||||||
@ = Leave file after sent, this is the default.
|
@ = Leave file after sent, this is the default.
|
||||||
|
|
||||||
.flo Normal flow file (contains complete filenames to send).
|
.flo Normal flow file (contains complete filenames to send).
|
||||||
.clo Crash flow file.
|
.clo Crash flow file.
|
||||||
.hlo Hold flow file.
|
.hlo Hold flow file.
|
||||||
.ilo Immediate flow file, overrides CM flag.
|
.ilo Immediate flow file, overrides CM flag.
|
||||||
|
|
||||||
The following are .pkt files, during the mail session they will be
|
The following are .pkt files, during the mail session they will be
|
||||||
renamed to nnnnnnnn.pkt with an unique name and added to the spool
|
renamed to nnnnnnnn.pkt with an unique name and added to the spool
|
||||||
file. Messages can allways be added to the outbound as long as the
|
file. Messages can allways be added to the outbound as long as the
|
||||||
node isn't locked.
|
node isn't locked.
|
||||||
|
|
||||||
.out Normal .pkt file.
|
.out Normal .pkt file.
|
||||||
.cut Crash .pkt file.
|
.cut Crash .pkt file.
|
||||||
.hut Hold .pkt file.
|
.hut Hold .pkt file.
|
||||||
.iut Immediate .pkt file.
|
.iut Immediate .pkt file.
|
||||||
|
|
||||||
It seems that these are subdirectories used by ifpack during packing
|
It seems that these are subdirectories used by ifpack during packing
|
||||||
of mail. These are used for the news/e-mail gate.
|
of mail. These are used for the news/e-mail gate.
|
||||||
|
|
||||||
.opk
|
.opk
|
||||||
.cpk
|
.cpk
|
||||||
.hpk
|
.hpk
|
||||||
.ipk
|
.ipk
|
||||||
|
|
||||||
|
|
||||||
.req Request file. Contains filenames in ascii with <cr><lf>.
|
.req Request file. Contains filenames in ascii with <cr><lf>.
|
||||||
|
|
||||||
.su0 Arcmail bundles, the last digit may be any digit or letter.
|
.su0 Arcmail bundles, the last digit may be any digit or letter.
|
||||||
.mo0
|
.mo0
|
||||||
.tu0
|
.tu0
|
||||||
.we0
|
.we0
|
||||||
.th0
|
.th0
|
||||||
.fr0
|
.fr0
|
||||||
.sa0
|
.sa0
|
||||||
|
|
||||||
.sts Node status file created by mbcico. These are data files containing
|
.sts Node status file created by mbcico. These are data files containing
|
||||||
three values:
|
three values:
|
||||||
1. 'time', this is the last call attempt time (in time_t format).
|
1. 'time', this is the last call attempt time (in time_t format).
|
||||||
2. 'retries', is the number of retries to try to connect that node. This
|
2. 'retries', is the number of retries to try to connect that node. This
|
||||||
field is zeroed when the call succeeds or when that node calls in.
|
field is zeroed when the call succeeds or when that node calls in.
|
||||||
It is also zeroed when a new poll is created. Currently, mbcico stops
|
It is also zeroed when a new poll is created. Currently, mbcico stops
|
||||||
calling a node if the counter is higher then 30.
|
calling a node if the counter is higher then 30.
|
||||||
3. 'code', is the return code of the last attempt.
|
3. 'code', is the return code of the last attempt.
|
||||||
0 - Successfull call
|
0 - Successfull call
|
||||||
1 - No dialout port available
|
1 - No dialout port available
|
||||||
2 - No CONNECT or TCP connect failed
|
2 - No CONNECT or TCP connect failed
|
||||||
3 - Could not reset the modem
|
3 - Could not reset the modem
|
||||||
4 - System is locked
|
4 - System is locked
|
||||||
5 - Retry time not reached?
|
5 - Retry time not reached?
|
||||||
6 - Fatal error in nodelist lookup
|
6 - Fatal error in nodelist lookup
|
||||||
7 - Call prohibited by config options
|
7 - Call prohibited by config options
|
||||||
8 - Phone number unavailable
|
8 - Phone number unavailable
|
||||||
9 - No free matching port
|
9 - No free matching port
|
||||||
10 - Unused
|
10 - Unused
|
||||||
11..29 - Session (handshake) errors.
|
11..29 - Session (handshake) errors.
|
||||||
This file is <b>not</b> compatible with the .sts files created by <b>ifcico</b>.</PRE>
|
This file is <b>not</b> compatible with the .sts files created by <b>ifcico</b>.</PRE>
|
||||||
|
|
||||||
<PRE>
|
<PRE>
|
||||||
.spl Spool file, created by mbcico.
|
.spl Spool file, created by mbcico.
|
||||||
|
|
||||||
.bsy Busy file, for locking nodes. The 'pid' of the process who locked that
|
.bsy Busy file, for locking nodes. The 'pid' of the process who locked that
|
||||||
node is inserted into this file. All programs of the MBSE BBS package
|
node is inserted into this file. All programs of the MBSE BBS package
|
||||||
(and ifcico package) check if the pid exists if a .bsy file is found.
|
(and ifcico package) check if the pid exists if a .bsy file is found.
|
||||||
If there is no pid found, the lock is a stale lock and is removed.
|
If there is no pid found, the lock is a stale lock and is removed.
|
||||||
|
|
||||||
</PRE>
|
</PRE>
|
||||||
|
|
||||||
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0" width="33" height="35">
|
<A HREF="index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Back" Border="0" width="33" height="35">
|
||||||
Go Back</A>
|
Go Back</A>
|
||||||
</BLOCKQUOTE>
|
</BLOCKQUOTE>
|
||||||
</BODY>
|
</BODY>
|
||||||
</HTML>
|
</HTML>
|
||||||
|
|
||||||
|
@ -1,63 +1,63 @@
|
|||||||
<HTML>
|
<HTML>
|
||||||
<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">
|
||||||
<META name="author" lang="en" "content="Michiel Broek">
|
<META name="author" lang="en" content="Michiel Broek">
|
||||||
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
||||||
<META name="description" lang="en" content="MBSE BBS Manual">
|
<META name="description" lang="en" content="MBSE BBS Manual">
|
||||||
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
||||||
<TITLE>Semafore files with MBSE BBS.</TITLE>
|
<TITLE>Semafore files with MBSE BBS.</TITLE>
|
||||||
<LINK rel=stylesheet HREF="../manual.css">
|
<LINK rel=stylesheet HREF="../manual.css">
|
||||||
</HEAD>
|
</HEAD>
|
||||||
<BODY>
|
<BODY>
|
||||||
<BLOCKQUOTE>
|
<BLOCKQUOTE>
|
||||||
<h5>Last update 27-jul-2001</h5>
|
<h5>Last update 27-jul-2001</h5>
|
||||||
<P> <P>
|
<P> <P>
|
||||||
|
|
||||||
<H1>Semafore files with MBSE BBS.</H1>
|
<H1>Semafore files with MBSE BBS.</H1>
|
||||||
|
|
||||||
The directory $MBSE_ROOT/sema is the hardcoded semafore directory where all
|
The directory $MBSE_ROOT/sema is the hardcoded semafore directory where all
|
||||||
semafore's must be created, tested and removed. When the system is booting,
|
semafore's must be created, tested and removed. When the system is booting,
|
||||||
the init script will erase all semafore's just before the BBS is started.
|
the init script will erase all semafore's just before the BBS is started.
|
||||||
This description is valid from MBSE BBS v0.33.18 and newer.
|
This description is valid from MBSE BBS v0.33.18 and newer.
|
||||||
|
|
||||||
<PRE>
|
<PRE>
|
||||||
zmh Purpose: to mark the state of Zone Mail Hour.
|
zmh Purpose: to mark the state of Zone Mail Hour.
|
||||||
Created by "mbtask" at the start of Zone Mail Hour.
|
Created by "mbtask" at the start of Zone Mail Hour.
|
||||||
Removed by "mbtask" at the end of Zone Mail Hour.
|
Removed by "mbtask" at the end of Zone Mail Hour.
|
||||||
|
|
||||||
upsalarm Purpose: Signal that the system is running on battery power.
|
upsalarm Purpose: Signal that the system is running on battery power.
|
||||||
Created and removed by UPS software.
|
Created and removed by UPS software.
|
||||||
Checked by mbtask to suspend processing.
|
Checked by mbtask to suspend processing.
|
||||||
Checked by mbfido to stop processing.
|
Checked by mbfido to stop processing.
|
||||||
|
|
||||||
upsdown Purpose: Signal that the system will go down on low battery.
|
upsdown Purpose: Signal that the system will go down on low battery.
|
||||||
Created and removed by UPS software.
|
Created and removed by UPS software.
|
||||||
Checked by mbtask to go down.
|
Checked by mbtask to go down.
|
||||||
Checked by several scripts and "mbstat wait".
|
Checked by several scripts and "mbstat wait".
|
||||||
|
|
||||||
newnews Purpose: Signal that there are new articles on the news server.
|
newnews Purpose: Signal that there are new articles on the news server.
|
||||||
Checked by mbtask to start news processing.
|
Checked by mbtask to start news processing.
|
||||||
Removed by mbtask as soon as it is detected.
|
Removed by mbtask as soon as it is detected.
|
||||||
|
|
||||||
mailout Purpose: Signal that there is mail posted in the message base.
|
mailout Purpose: Signal that there is mail posted in the message base.
|
||||||
Checked by mbtask to start scan the message base.
|
Checked by mbtask to start scan the message base.
|
||||||
Removed by mbtask as soon as it is detected.
|
Removed by mbtask as soon as it is detected.
|
||||||
|
|
||||||
mailin Purpose: Signal that there is new mail in the inbound.
|
mailin Purpose: Signal that there is new mail in the inbound.
|
||||||
Checked by mbtask to start the tosser.
|
Checked by mbtask to start the tosser.
|
||||||
Removed by mbtask as soon as it is detected.
|
Removed by mbtask as soon as it is detected.
|
||||||
|
|
||||||
scanout Purpose: Signal that the outbound must be rescanned.
|
scanout Purpose: Signal that the outbound must be rescanned.
|
||||||
Checked by mbtask to check the outbound.
|
Checked by mbtask to check the outbound.
|
||||||
Removed by mbtask as soon as it is detected.
|
Removed by mbtask as soon as it is detected.
|
||||||
|
|
||||||
mbtask.last Purpose: A timestamp created and touched by "mbtask" every
|
mbtask.last Purpose: A timestamp created and touched by "mbtask" every
|
||||||
minute so you can check it is running.
|
minute so you can check it is running.
|
||||||
</PRE>
|
</PRE>
|
||||||
|
|
||||||
<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" width="33" height="35"> Go Back</A>
|
||||||
</BLOCKQUOTE>
|
</BLOCKQUOTE>
|
||||||
</BODY>
|
</BODY>
|
||||||
</HTML>
|
</HTML>
|
||||||
|
|
||||||
|
@ -1,61 +1,61 @@
|
|||||||
<HTML>
|
<HTML>
|
||||||
<HEAD>
|
<HEAD>
|
||||||
<TITLE>System load and the usleep() call.</TITLE>
|
<TITLE>System load and the usleep() call.</TITLE>
|
||||||
</HEAD>
|
</HEAD>
|
||||||
|
|
||||||
<!-- Background white, links blue (unvisited), navy (visited), red (active) -->
|
<!-- Background white, links blue (unvisited), navy (visited), red (active) -->
|
||||||
<BODY
|
<BODY
|
||||||
BGCOLOR="#FFFFFF"
|
BGCOLOR="#FFFFFF"
|
||||||
TEXT="#000000"
|
TEXT="#000000"
|
||||||
LINK="#0000FF"
|
LINK="#0000FF"
|
||||||
VLINK="#000080"
|
VLINK="#000080"
|
||||||
ALINK="#FF0000"
|
ALINK="#FF0000"
|
||||||
>
|
>
|
||||||
<PRE>
|
<PRE>
|
||||||
usleep.doc
|
usleep.doc
|
||||||
|
|
||||||
|
|
||||||
At some time when developping MBSE BBS I decided that background utilities
|
At some time when developping MBSE BBS I decided that background utilities
|
||||||
did't need full speed to do their jobs. BBS utilities under DOS needed
|
did't need full speed to do their jobs. BBS utilities under DOS needed
|
||||||
to run as fast as possible because you needed to bring the bbs down to run
|
to run as fast as possible because you needed to bring the bbs down to run
|
||||||
these programs and users couldn't login during that time.
|
these programs and users couldn't login during that time.
|
||||||
|
|
||||||
Starting with mball, the allfiles creator, I inserted code that does usleep(1)
|
Starting with mball, the allfiles creator, I inserted code that does usleep(1)
|
||||||
after each 5 processed files. The 1 microsecond is not really the time the
|
after each 5 processed files. The 1 microsecond is not really the time the
|
||||||
program pauses, it's probably a lot longer. I think this depends on the
|
program pauses, it's probably a lot longer. I think this depends on the
|
||||||
hardware type, (Intel, Sparc, Alpha etc) how long Linux will really suspends
|
hardware type, (Intel, Sparc, Alpha etc) how long Linux will really suspends
|
||||||
executing the utility.
|
executing the utility.
|
||||||
|
|
||||||
The program speed downgrade at the development machine that mball needed was
|
The program speed downgrade at the development machine that mball needed was
|
||||||
3 times the original exection time, while system loading stayed under 30%.
|
3 times the original exection time, while system loading stayed under 30%.
|
||||||
At that time the development machine is an 486DX2-66 with a Seagate ST32151N
|
At that time the development machine is an 486DX2-66 with a Seagate ST32151N
|
||||||
SCSI harddisk.
|
SCSI harddisk.
|
||||||
|
|
||||||
The extra usleep code is only active if you run these utils with the -quiet
|
The extra usleep code is only active if you run these utils with the -quiet
|
||||||
switch and when this is set in mbsetup. See menu 1->5.
|
switch and when this is set in mbsetup. See menu 1->5.
|
||||||
With this switch, the program is mostly run by cron. If you onmit
|
With this switch, the program is mostly run by cron. If you onmit
|
||||||
this switch, this is probably when you start the program manually, it will
|
this switch, this is probably when you start the program manually, it will
|
||||||
then always run at full speed, no matter what the setting in mbsetup is.
|
then always run at full speed, no matter what the setting in mbsetup is.
|
||||||
|
|
||||||
If you have a fast system or don't care that the performance of your system
|
If you have a fast system or don't care that the performance of your system
|
||||||
drops because of background processing, you can turn this future off with
|
drops because of background processing, you can turn this future off with
|
||||||
mbsetup in the global section. (menu 1->5).
|
mbsetup in the global section. (menu 1->5).
|
||||||
|
|
||||||
Remember, if you have a PII-400 MMX or so with IDE disks, you may still have
|
Remember, if you have a PII-400 MMX or so with IDE disks, you may still have
|
||||||
performance problems and need to set that switch to yes. There is only one
|
performance problems and need to set that switch to yes. There is only one
|
||||||
way to find out if you need it.
|
way to find out if you need it.
|
||||||
|
|
||||||
Well, actually, I tested this on a Dell Latitude PII-266, setting the switch to
|
Well, actually, I tested this on a Dell Latitude PII-266, setting the switch to
|
||||||
yes gave better performance then no. Why? The CPU has more time for the slow
|
yes gave better performance then no. Why? The CPU has more time for the slow
|
||||||
IDE disk. With the slow switch on programs runs even faster then with the switch
|
IDE disk. With the slow switch on programs runs even faster then with the switch
|
||||||
off.
|
off.
|
||||||
|
|
||||||
Michiel.
|
Michiel.
|
||||||
|
|
||||||
</PRE>
|
</PRE>
|
||||||
|
|
||||||
<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" width="33" height="35"> Go Back</A>
|
||||||
|
|
||||||
</BODY>
|
</BODY>
|
||||||
</HTML>
|
</HTML>
|
||||||
|
|
||||||
|
@ -1,131 +1,131 @@
|
|||||||
<HTML>
|
<HTML>
|
||||||
<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">
|
||||||
<META name="author" lang="en" "content="Michiel Broek">
|
<META name="author" lang="en" content="Michiel Broek">
|
||||||
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
||||||
<META name="description" lang="en" content="MBSE BBS Manual">
|
<META name="description" lang="en" content="MBSE BBS Manual">
|
||||||
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
||||||
<TITLE>Nodelist and Nidediff processing.</TITLE>
|
<TITLE>Nodelist and Nidediff processing.</TITLE>
|
||||||
<LINK rel=stylesheet HREF="manual.css">
|
<LINK rel=stylesheet HREF="manual.css">
|
||||||
</HEAD>
|
</HEAD>
|
||||||
<BODY>
|
<BODY>
|
||||||
<BLOCKQUOTE>
|
<BLOCKQUOTE>
|
||||||
<h5>Last update 07-Jun-2001</h5>
|
<h5>Last update 07-Jun-2001</h5>
|
||||||
<P> <P>
|
<P> <P>
|
||||||
|
|
||||||
<H1>Nodelist and Nodediff processing</H1>
|
<H1>Nodelist and Nodediff processing</H1>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<H3>Introduction</H3>
|
<H3>Introduction</H3>
|
||||||
<P>
|
<P>
|
||||||
A received a lot of questions about nodelist and nodediff processing, so
|
A received a lot of questions about nodelist and nodediff processing, so
|
||||||
I will describe here the setup of the development system for the Fidonet
|
I will describe here the setup of the development system for the Fidonet
|
||||||
nodelist. First of all, it is <strong>very important</strong> that you
|
nodelist. First of all, it is <strong>very important</strong> that you
|
||||||
use three separate directories to do the nodelist processing. This is to
|
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>/var/spool/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>/var/spool/mbse/nodelist</strong>, this is the systems nodelist
|
||||||
directory defined in mbsetup, menu 1.3.4
|
directory defined in mbsetup, menu 1.3.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>
|
||||||
<li>Receive the nodediff and store it for download.
|
<li>Receive the nodediff and store it for download.
|
||||||
<li>Apply the diff to the latest nodelist.
|
<li>Apply the diff to the latest nodelist.
|
||||||
<li>Hatch the new compressed nodelist.
|
<li>Hatch the new compressed nodelist.
|
||||||
<li>Store the new nodelist for download.
|
<li>Store the new nodelist for download.
|
||||||
<li>Unpack the new nodelist in the nodelist compiler directory.
|
<li>Unpack the new nodelist in the nodelist compiler directory.
|
||||||
<li>Set the compile semafore.
|
<li>Set the compile semafore.
|
||||||
<li>Compile the nodelists.
|
<li>Compile the nodelists.
|
||||||
</ol>
|
</ol>
|
||||||
Next I will describe these steps in detail.
|
Next I will describe these steps in detail.
|
||||||
<P> </P>
|
<P> </P>
|
||||||
|
|
||||||
<H3>The download area</H3>
|
<H3>The download area</H3>
|
||||||
<P>
|
<P>
|
||||||
First define the download area for the bbs. In my case, this is area 20. From
|
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">
|
||||||
<P> </P>
|
<P> </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 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" width="591" height="344">
|
||||||
<P> </P>
|
<P> </P>
|
||||||
|
|
||||||
<H3>Apply the diff</H3>
|
<H3>Apply the diff</H3>
|
||||||
<P>
|
<P>
|
||||||
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 arc, the filemask on
|
||||||
my system is <strong>nodediff.a##</strong>.
|
my system is <strong>nodediff.a##</strong>.
|
||||||
This means that the file with the name nodediff.a14 in the area NODEDIFF
|
This means that the file with the name nodediff.a14 in the area NODEDIFF
|
||||||
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.a14 -quiet</strong> if the received nodediff is
|
||||||
<strong>nodediff.a14</strong>.<br>The mbdiff program applies
|
<strong>nodediff.a14</strong>.<br>The mbdiff program applies
|
||||||
<strong>nodediff.a14</strong> against <strong>NODELIST.007</strong> in the
|
<strong>nodediff.a14</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
|
||||||
removed.<br> If this operation fails, only <b>NODELIST.007</b> will stay
|
removed.<br> If this operation fails, only <b>NODELIST.007</b> will stay
|
||||||
in that directory.
|
in that directory.
|
||||||
Because the ARC program for Linux isn't good for files, I
|
Because the ARC program for Linux isn't good for files, I
|
||||||
left the Arc files command empty in the archiver setup. As a fallback the
|
left the Arc files command empty in the archiver setup. As a fallback the
|
||||||
mbdiff program uses <strong>zip</strong> to create the compressed archive.<br>
|
mbdiff program uses <strong>zip</strong> to create the compressed archive.<br>
|
||||||
If creating the new nodelist fails for some reason, a missed diff or so,
|
If creating the new nodelist fails for some reason, a missed diff or so,
|
||||||
the whole processing stops here. The previous nodelist is still here and
|
the whole processing stops here. The previous nodelist is still here and
|
||||||
you can manually correct the situation. So, if you missed a diff, see that
|
you can manually correct the situation. So, if you missed a diff, see that
|
||||||
you get it and manually give the <strong>mbdiff</strong> commands as user
|
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" width="591" height="344">
|
||||||
<P> </P>
|
<P> </P>
|
||||||
|
|
||||||
<H3>Processing the new nodelist</H3>
|
<H3>Processing the new nodelist</H3>
|
||||||
<P>
|
<P>
|
||||||
Now that we have created the new compressed nodelist, it has to go somewhere.
|
Now that we have created the new compressed nodelist, it has to go somewhere.
|
||||||
The file <strong>nodelist.z14</strong> is in the directory
|
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 tic and
|
||||||
hatch setup for this area.
|
hatch setup for this area.
|
||||||
<P>
|
<P>
|
||||||
<IMG SRC="images/nodelist4.gif" Border="0" width="591" height="344">
|
<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" width="591" height="344">
|
||||||
<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 stored in in the download area,
|
||||||
and maybe send some copies to downlinks, we have to feed it to the nodelist
|
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
|
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>
|
that. In this case we unpack the nodelist in <strong>/var/spool/mbse/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>
|
||||||
will handle that, only the latest two nodelists are kept there. The
|
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" width="591" height="344">
|
||||||
<P> </P>
|
<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" width="33" height="35"> Go Back</A>
|
||||||
</BLOCKQUOTE>
|
</BLOCKQUOTE>
|
||||||
</BODY>
|
</BODY>
|
||||||
</HTML>
|
</HTML>
|
||||||
|
|
||||||
|
@ -1,160 +1,160 @@
|
|||||||
<HTML>
|
<HTML>
|
||||||
<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">
|
||||||
<META name="author" lang="en" "content="Michiel Broek">
|
<META name="author" lang="en" content="Michiel Broek">
|
||||||
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
||||||
<META name="description" lang="en" content="MBSE BBS Manual">
|
<META name="description" lang="en" content="MBSE BBS Manual">
|
||||||
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
||||||
<TITLE>MBSE BBS - Internet Gateway - Postfix setup.</TITLE>
|
<TITLE>MBSE BBS - Internet Gateway - Postfix setup.</TITLE>
|
||||||
<LINK rel=stylesheet HREF="manual.css">
|
<LINK rel=stylesheet HREF="manual.css">
|
||||||
</HEAD>
|
</HEAD>
|
||||||
<BODY>
|
<BODY>
|
||||||
<BLOCKQUOTE>
|
<BLOCKQUOTE>
|
||||||
<h5>Last update 25-Aug-2001</h5>
|
<h5>Last update 25-Aug-2001</h5>
|
||||||
<P> <P>
|
<P> <P>
|
||||||
|
|
||||||
<H1 ALIGN="CENTER">MBSE BBS - Internet Gateway - Postfix setup.</H1>
|
<H1 ALIGN="CENTER">MBSE BBS - Internet Gateway - Postfix setup.</H1>
|
||||||
<P>
|
<P>
|
||||||
Of course you need to make all these changes as root.
|
Of course you need to make all these changes as root.
|
||||||
Add the <strong>mbmail</strong> program as service to the postfix system by
|
Add the <strong>mbmail</strong> program as service to the postfix system by
|
||||||
adding two lines to <strong>master.cf</strong>.
|
adding two lines to <strong>master.cf</strong>.
|
||||||
<hr>
|
<hr>
|
||||||
<pre>
|
<pre>
|
||||||
#
|
#
|
||||||
# Postfix master process configuration file. Each line describes how
|
# Postfix master process configuration file. Each line describes how
|
||||||
# a mailer component program should be run. The fields that make up
|
# a mailer component program should be run. The fields that make up
|
||||||
# each line are described below. A "-" field value requests that a
|
# each line are described below. A "-" field value requests that a
|
||||||
# default value be used for that field.
|
# default value be used for that field.
|
||||||
#
|
#
|
||||||
# Service: any name that is valid for the specified transport type
|
# Service: any name that is valid for the specified transport type
|
||||||
# (the next field). With INET transports, a service is specified as
|
# (the next field). With INET transports, a service is specified as
|
||||||
# host:port. The host part (and colon) may be omitted. Either host
|
# host:port. The host part (and colon) may be omitted. Either host
|
||||||
# or port may be given in symbolic form or in numeric form. Examples
|
# or port may be given in symbolic form or in numeric form. Examples
|
||||||
# for the SMTP server: localhost:smtp receives mail via the loopback
|
# for the SMTP server: localhost:smtp receives mail via the loopback
|
||||||
# interface only; 10025 receives mail on port 10025.
|
# interface only; 10025 receives mail on port 10025.
|
||||||
#
|
#
|
||||||
# Transport type: "inet" for Internet sockets, "unix" for UNIX-domain
|
# Transport type: "inet" for Internet sockets, "unix" for UNIX-domain
|
||||||
# sockets, "fifo" for named pipes.
|
# sockets, "fifo" for named pipes.
|
||||||
#
|
#
|
||||||
# Private: whether or not access is restricted to the mail system.
|
# Private: whether or not access is restricted to the mail system.
|
||||||
# Default is private service. Internet (inet) sockets can't be private.
|
# Default is private service. Internet (inet) sockets can't be private.
|
||||||
#
|
#
|
||||||
# Unprivileged: whether the service runs with root privileges or as
|
# Unprivileged: whether the service runs with root privileges or as
|
||||||
# the owner of the Postfix system (the owner name is controlled by the
|
# the owner of the Postfix system (the owner name is controlled by the
|
||||||
# mail_owner configuration variable in the main.cf file).
|
# mail_owner configuration variable in the main.cf file).
|
||||||
#
|
#
|
||||||
# Chroot: whether or not the service runs chrooted to the mail queue
|
# Chroot: whether or not the service runs chrooted to the mail queue
|
||||||
# directory (pathname is controlled by the queue_directory configuration
|
# directory (pathname is controlled by the queue_directory configuration
|
||||||
# variable in the main.cf file). Presently, all Postfix daemons can run
|
# variable in the main.cf file). Presently, all Postfix daemons can run
|
||||||
# chrooted, except for the pipe and local daemons. The files in the
|
# chrooted, except for the pipe and local daemons. The files in the
|
||||||
# examples/chroot-setup subdirectory describe how to set up a Postfix
|
# examples/chroot-setup subdirectory describe how to set up a Postfix
|
||||||
# chroot environment for your type of machine.
|
# chroot environment for your type of machine.
|
||||||
#
|
#
|
||||||
# Wakeup time: automatically wake up the named service after the
|
# Wakeup time: automatically wake up the named service after the
|
||||||
# specified number of seconds. Specify 0 for no wakeup. Presently,
|
# specified number of seconds. Specify 0 for no wakeup. Presently,
|
||||||
# only the local pickup and queue manager daemons need a wakeup timer.
|
# only the local pickup and queue manager daemons need a wakeup timer.
|
||||||
#
|
#
|
||||||
# Max procs: the maximum number of processes that may execute this
|
# Max procs: the maximum number of processes that may execute this
|
||||||
# service simultaneously. Default is to use a globally configurable
|
# service simultaneously. Default is to use a globally configurable
|
||||||
# limit (the default_process_limit configuration parameter in main.cf).
|
# limit (the default_process_limit configuration parameter in main.cf).
|
||||||
#
|
#
|
||||||
# Command + args: the command to be executed. The command name is
|
# Command + args: the command to be executed. The command name is
|
||||||
# relative to the Postfix program directory (pathname is controlled by
|
# relative to the Postfix program directory (pathname is controlled by
|
||||||
# the program_directory configuration variable). Adding one or more
|
# the program_directory configuration variable). Adding one or more
|
||||||
# -v options turns on verbose logging for that service; adding a -D
|
# -v options turns on verbose logging for that service; adding a -D
|
||||||
# option enables symbolic debugging (see the debugger_command variable
|
# option enables symbolic debugging (see the debugger_command variable
|
||||||
# in the main.cf configuration file).
|
# in the main.cf configuration file).
|
||||||
#
|
#
|
||||||
# In order to use the "uucp" message tranport below, set up entries
|
# In order to use the "uucp" message tranport below, set up entries
|
||||||
# in the transport table.
|
# in the transport table.
|
||||||
#
|
#
|
||||||
# In order to use the "cyrus" message transport below, configure it
|
# In order to use the "cyrus" message transport below, configure it
|
||||||
# in main.cf as the mailbox_transport.
|
# in main.cf as the mailbox_transport.
|
||||||
#
|
#
|
||||||
# SPECIFY ONLY PROGRAMS THAT ARE WRITTEN TO RUN AS POSTFIX DAEMONS.
|
# SPECIFY ONLY PROGRAMS THAT ARE WRITTEN TO RUN AS POSTFIX DAEMONS.
|
||||||
# ALL DAEMONS SPECIFIED HERE MUST SPEAK A POSTFIX-INTERNAL PROTOCOL.
|
# ALL DAEMONS SPECIFIED HERE MUST SPEAK A POSTFIX-INTERNAL PROTOCOL.
|
||||||
#
|
#
|
||||||
# ==========================================================================
|
# ==========================================================================
|
||||||
# service type private unpriv chroot wakeup maxproc command + args
|
# service type private unpriv chroot wakeup maxproc command + args
|
||||||
# (yes) (yes) (yes) (never) (50)
|
# (yes) (yes) (yes) (never) (50)
|
||||||
# ==========================================================================
|
# ==========================================================================
|
||||||
smtp inet n - n - - smtpd
|
smtp inet n - n - - smtpd
|
||||||
pickup fifo n n n 60 1 pickup
|
pickup fifo n n n 60 1 pickup
|
||||||
cleanup unix - - n - 0 cleanup
|
cleanup unix - - n - 0 cleanup
|
||||||
qmgr fifo n - n 300 1 qmgr
|
qmgr fifo n - n 300 1 qmgr
|
||||||
rewrite unix - - n - - trivial-rewrite
|
rewrite unix - - n - - trivial-rewrite
|
||||||
bounce unix - - n - 0 bounce
|
bounce unix - - n - 0 bounce
|
||||||
defer unix - - n - 0 bounce
|
defer unix - - n - 0 bounce
|
||||||
smtp unix - - n - - smtp
|
smtp unix - - n - - smtp
|
||||||
showq unix n - n - - showq
|
showq unix n - n - - showq
|
||||||
error unix - - n - - error
|
error unix - - n - - error
|
||||||
local unix - n n - - local
|
local unix - n n - - local
|
||||||
cyrus unix - n n - - pipe
|
cyrus unix - n n - - pipe
|
||||||
flags=R user=cyrus argv=/cyrus/bin/deliver -e -m ${extension} ${user}
|
flags=R user=cyrus argv=/cyrus/bin/deliver -e -m ${extension} ${user}
|
||||||
uucp unix - n n - - pipe
|
uucp unix - n n - - pipe
|
||||||
flags=F user=uucp argv=uux -r -n -z -a$sender - $nexthop!rmail ($recipient)
|
flags=F user=uucp argv=uux -r -n -z -a$sender - $nexthop!rmail ($recipient)
|
||||||
ifmail unix - n n - 1 pipe
|
ifmail unix - n n - 1 pipe
|
||||||
flags=F user=fido argv=/usr/local/bin/ifmail -r $nexthop ($recipient)
|
flags=F user=fido argv=/usr/local/bin/ifmail -r $nexthop ($recipient)
|
||||||
mbmail unix - n n - 1 pipe
|
mbmail unix - n n - 1 pipe
|
||||||
flags=F user=mbse argv=/opt/mbse/bin/mbmail ($recipient)
|
flags=F user=mbse argv=/opt/mbse/bin/mbmail ($recipient)
|
||||||
bsmtp unix - n n - - pipe
|
bsmtp unix - n n - - pipe
|
||||||
flags=F. user=foo argv=/usr/local/sbin/bsmtp -f $sender $nexthop $recipient
|
flags=F. user=foo argv=/usr/local/sbin/bsmtp -f $sender $nexthop $recipient
|
||||||
</pre>
|
</pre>
|
||||||
<hr>
|
<hr>
|
||||||
In <strong>main.cf</strong> change or add the line:<br>
|
In <strong>main.cf</strong> change or add the line:<br>
|
||||||
<pre>
|
<pre>
|
||||||
relay_domains = $mydestination, f2802.n280.z2.fidonet.org
|
relay_domains = $mydestination, f2802.n280.z2.fidonet.org
|
||||||
</pre>
|
</pre>
|
||||||
The fidonet address will be your fidonet address of course. If you have more
|
The fidonet address will be your fidonet address of course. If you have more
|
||||||
fidonet aka's, add them as well seperated with commas.
|
fidonet aka's, add them as well seperated with commas.
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
Next you need to add <strong>mbmail</strong> to the
|
Next you need to add <strong>mbmail</strong> to the
|
||||||
<strong>transport</strong> file.
|
<strong>transport</strong> file.
|
||||||
<hr>
|
<hr>
|
||||||
<pre>
|
<pre>
|
||||||
# /etc/postfix/transport
|
# /etc/postfix/transport
|
||||||
#
|
#
|
||||||
# execute "postmap /etc/postfix/transport" after changing this file
|
# execute "postmap /etc/postfix/transport" after changing this file
|
||||||
#
|
#
|
||||||
# Local destinations
|
# Local destinations
|
||||||
#
|
#
|
||||||
seaport.mbse.nl local:
|
seaport.mbse.nl local:
|
||||||
www.mbse.nl local:
|
www.mbse.nl local:
|
||||||
news.mbse.nl local:
|
news.mbse.nl local:
|
||||||
#
|
#
|
||||||
# Fidonet mailers at this machine. Test on several strings to make sure
|
# Fidonet mailers at this machine. Test on several strings to make sure
|
||||||
# it will catches everything.
|
# it will catches everything.
|
||||||
#
|
#
|
||||||
z1 mbmail:f2802.n280.z2.fidonet
|
z1 mbmail:f2802.n280.z2.fidonet
|
||||||
.z1 mbmail:f2802.n280.z2.fidonet
|
.z1 mbmail:f2802.n280.z2.fidonet
|
||||||
z2 mbmail:f2802.n280.z2.fidonet
|
z2 mbmail:f2802.n280.z2.fidonet
|
||||||
.z2 mbmail:f2802.n280.z2.fidonet
|
.z2 mbmail:f2802.n280.z2.fidonet
|
||||||
z3 mbmail:f2802.n280.z2.fidonet
|
z3 mbmail:f2802.n280.z2.fidonet
|
||||||
.z3 mbmail:f2802.n280.z2.fidonet
|
.z3 mbmail:f2802.n280.z2.fidonet
|
||||||
z4 mbmail:f2802.n280.z2.fidonet
|
z4 mbmail:f2802.n280.z2.fidonet
|
||||||
.z4 mbmail:f2802.n280.z2.fidonet
|
.z4 mbmail:f2802.n280.z2.fidonet
|
||||||
z5 mbmail:f2802.n280.z2.fidonet
|
z5 mbmail:f2802.n280.z2.fidonet
|
||||||
.z5 mbmail:f2802.n280.z2.fidonet
|
.z5 mbmail:f2802.n280.z2.fidonet
|
||||||
z6 mbmail:f2802.n280.z2.fidonet
|
z6 mbmail:f2802.n280.z2.fidonet
|
||||||
.z6 mbmail:f2802.n280.z2.fidonet
|
.z6 mbmail:f2802.n280.z2.fidonet
|
||||||
fidonet mbmail:f2802.n280.z2.fidonet
|
fidonet mbmail:f2802.n280.z2.fidonet
|
||||||
.fidonet mbmail:f2802.n280.z2.fidonet
|
.fidonet mbmail:f2802.n280.z2.fidonet
|
||||||
fidonet.org mbmail:f2802.n280.z2.fidonet
|
fidonet.org mbmail:f2802.n280.z2.fidonet
|
||||||
.fidonet.org mbmail:f2802.n280.z2.fidonet
|
.fidonet.org mbmail:f2802.n280.z2.fidonet
|
||||||
</pre>
|
</pre>
|
||||||
<hr>
|
<hr>
|
||||||
Don't forget to run <strong>postmap /etc/postfix/transport</strong>. Now all
|
Don't forget to run <strong>postmap /etc/postfix/transport</strong>. Now all
|
||||||
files are changed, run <strong>postfix reload</strong> to activate the
|
files are changed, run <strong>postfix reload</strong> to activate the
|
||||||
changes.
|
changes.
|
||||||
|
|
||||||
<p>
|
<p>
|
||||||
|
|
||||||
<A HREF="./intergate.html"><IMG SRC="images/larrow.gif" ALT="Back" Border="0" width="40" height="30">
|
<A HREF="./intergate.html"><IMG SRC="images/larrow.gif" ALT="Back" Border="0" width="40" height="30">
|
||||||
Go back</A>
|
Go back</A>
|
||||||
<A HREF="index.htm"><IMG SRC="images/b_arrow.gif" ALT="Home" Border="0" width="33" height="35"> Go to main</A>
|
<A HREF="index.htm"><IMG SRC="images/b_arrow.gif" ALT="Home" Border="0" width="33" height="35"> Go to main</A>
|
||||||
</BLOCKQUOTE>
|
</BLOCKQUOTE>
|
||||||
</BODY>
|
</BODY>
|
||||||
</HTML>
|
</HTML>
|
||||||
|
|
||||||
|
@ -1,93 +1,97 @@
|
|||||||
<HTML>
|
<HTML>
|
||||||
<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">
|
||||||
<META name="author" lang="en" "content="Michiel Broek">
|
<META name="author" lang="en" content="Michiel Broek">
|
||||||
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
||||||
<META name="description" lang="en" content="MBSE BBS Manual">
|
<META name="description" lang="en" content="MBSE BBS Manual">
|
||||||
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
||||||
<TITLE>MBSE BBS Programs - mbfile - File database maintenance program.</TITLE>
|
<TITLE>MBSE BBS Programs - mbfile - File database maintenance program.</TITLE>
|
||||||
<LINK rel=stylesheet HREF="../manual.css">
|
<LINK rel=stylesheet HREF="../manual.css">
|
||||||
</HEAD>
|
</HEAD>
|
||||||
<BODY>
|
<BODY>
|
||||||
<BLOCKQUOTE>
|
<BLOCKQUOTE>
|
||||||
<h5>Last update 30-Jan-2001</h5>
|
<h5>Last update 22-Oct-2001</h5>
|
||||||
<P> <P>
|
<P>
|
||||||
|
|
||||||
<H1>mbfile - File database maintenance program.</H1>
|
<H1>mbfile - File database maintenance program.</H1>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
<H3>Synopsys.</H3>
|
<H3>Synopsys.</H3>
|
||||||
<code><strong>mbfile</strong> [commands] <options></code>
|
<code><strong>mbfile</strong> [commands] <options></code>
|
||||||
<P> <P>
|
<P> <P>
|
||||||
|
|
||||||
<H3>Description.</H3>
|
<H3>Description.</H3>
|
||||||
<P>
|
<P>
|
||||||
<strong>mbfile</strong>
|
<strong>mbfile</strong>
|
||||||
is the filedatabase maintenance program for mbsebbs. In order to run mbfile you
|
is the filedatabase maintenance program for mbsebbs. In order to run mbfile you
|
||||||
must have started <strong>mbsed</strong>,
|
must have started <strong>mbsed</strong>,
|
||||||
this is the deamon which controls all bbs activities.
|
this is the deamon which controls all bbs activities.
|
||||||
<P>
|
<P>
|
||||||
The main purpose of <strong>mbfile</strong>
|
The main purpose of <strong>mbfile</strong>
|
||||||
to do automatic maintenance on the downloadable files on the bbs, such as
|
to do automatic maintenance on the downloadable files on the bbs, such as
|
||||||
removing or moving old files, checking the database and packing the database.
|
removing or moving old files, checking the database and packing the database.
|
||||||
The best way to do the maintenance is to run <strong>mbfile</strong>
|
The best way to do the maintenance is to run <strong>mbfile</strong>
|
||||||
from the crontab. example:
|
from the crontab. example:
|
||||||
<P><pre>
|
<P><pre>
|
||||||
30 05 * * * export MBSE_ROOT=/opt/mbse; /opt/mbse/bin/mbfile kill pack check index -quiet
|
30 05 * * * export MBSE_ROOT=/opt/mbse; /opt/mbse/bin/mbfile kill pack check index -quiet
|
||||||
</pre>
|
</pre>
|
||||||
<P> <P>
|
<P> <P>
|
||||||
|
|
||||||
<H3>Environment.</H3>
|
<H3>Environment.</H3>
|
||||||
<P>
|
<P>
|
||||||
In order to run the bbs you need to set one global environment variable
|
In order to run the bbs you need to set one global environment variable
|
||||||
<strong>$MBSE_ROOT</strong>
|
<strong>$MBSE_ROOT</strong>
|
||||||
This variable must point to the root of the bbs directoy structure. The
|
This variable must point to the root of the bbs directoy structure. The
|
||||||
main configuration file <strong>config.data</strong>
|
main configuration file <strong>config.data</strong>
|
||||||
must exist in the subdirectory ~/etc.
|
must exist in the subdirectory ~/etc.
|
||||||
<P> <P>
|
<P> <P>
|
||||||
|
|
||||||
<H3>Commands.</H3>
|
<H3>Commands.</H3>
|
||||||
<P>
|
<P>
|
||||||
<code><strong>mbfile</strong> check</code>
|
<code><strong>mbfile</strong> check</code>
|
||||||
Check the database integrity. All files in the filedatabase must exist on
|
Check the database integrity. All files in the filedatabase must exist on
|
||||||
disk and all files on disk must exist in the filedatabase. There are some
|
disk and all files on disk must exist in the filedatabase. There are some
|
||||||
exceptions, files.bbs, files.bak, 00index, index*.html, header, readme and
|
exceptions, files.bbs, files.bak, 00index, index*.html, header, readme and
|
||||||
files that start with a dot.
|
files that start with a dot.
|
||||||
Of all files the date and time is checked, the size and the crc
|
Of all files the date and time is checked, the size and the crc
|
||||||
value of the file. If there is something wrong, the error is corrected or the
|
value of the file. If there is something wrong, the error is corrected or the
|
||||||
file is removed. If the area is a CD-rom area, the check that files on disk
|
file is removed. If the area is a CD-rom area, the check that files on disk
|
||||||
must exist in the filedatabase is skipped.
|
must exist in the filedatabase is skipped.
|
||||||
<P>
|
<P>
|
||||||
<code><strong>mbfile</strong> index</code>
|
<code><strong>mbfile</strong> index</code>
|
||||||
Create fast filerequest index for the <strong>mbcico</strong> filerequest
|
Create fast filerequest index for the <strong>mbcico</strong> filerequest
|
||||||
processor.
|
processor.
|
||||||
<P>
|
<P>
|
||||||
<code><strong>mbfile</strong> pack</code>
|
<code><strong>mbfile</strong> kill</code>
|
||||||
This command will actualy remove the records of files that are marked for
|
Delete or move files in areas that have the <strong>download age</strong>
|
||||||
deletion. If the file is still on disk, it will be removed also. So when
|
set or the <strong>filedate age</strong> set. A setting of 0 is ignored.
|
||||||
you delete files with mbsetup, they are still in your database and on disk
|
Areas on CD-rom are always skipped.
|
||||||
until you run <strong>mbfile pack</strong>.
|
If the Move to Area option is set the files are moved to the given area. The
|
||||||
<P>
|
upload date and download date are reset to the current date and time.
|
||||||
<code><strong>mbfile</strong> kill</code>
|
So if you set in the destination area aging of 14 days, files will stay
|
||||||
Delete or move files in areas that have the <strong>download age</strong>
|
there for 14 days after the move. This is good for automatic "last chance" areas.
|
||||||
set or the <strong>filedate age</strong> set. A setting of 0 is ignored.
|
<P>
|
||||||
Areas on CD-rom are always skipped.
|
<code><strong>mbfile</strong> list</code>
|
||||||
If the Move to Area option is set the files are moved to the given area. The
|
List all defined file areas, the number of files, the total size of the files
|
||||||
upload date and download date are reset to the current date and time.
|
and the primary group.
|
||||||
So if you set in the destination area aging of 14 days, files will stay
|
<P>
|
||||||
there for 14 days after the move. This is good for automatic "last chance" areas.
|
<code><strong>mbfile</strong> pack</code>
|
||||||
<P> <P>
|
This command will actualy remove the records of files that are marked for
|
||||||
|
deletion. If the file is still on disk, it will be removed also. So when
|
||||||
<H3>Options.</H3>
|
you delete files with mbsetup, they are still in your database and on disk
|
||||||
<P>
|
until you run <strong>mbfile pack</strong>.
|
||||||
<code><strong>mbfile</strong> [command] -quiet</code>
|
<P> <P>
|
||||||
Quiet mode, no screen output. Use this switch if you run <strong>mbfile</strong> from the crontab.
|
|
||||||
<P>
|
<H3>Options.</H3>
|
||||||
|
<P>
|
||||||
<A HREF="index.htm"><IMG SRC="../images/larrow.gif" ALT="Index" Border="0" width="40" height="30"> Back to index</A>
|
<code><strong>mbfile</strong> [command] -quiet</code>
|
||||||
<A HREF="../index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Main" Border="0" width="33" height="35"> Back to Main index</A>
|
Quiet mode, no screen output. Use this switch if you run <strong>mbfile</strong> from the crontab.
|
||||||
</BLOCKQUOTE>
|
<P>
|
||||||
</BODY>
|
|
||||||
</HTML>
|
<A HREF="index.htm"><IMG SRC="../images/larrow.gif" ALT="Index" Border="0" width="40" height="30"> Back to index</A>
|
||||||
|
<A HREF="../index.htm"><IMG SRC="../images/b_arrow.gif" ALT="Main" Border="0" width="33" height="35"> Back to Main index</A>
|
||||||
|
</BLOCKQUOTE>
|
||||||
|
</BODY>
|
||||||
|
</HTML>
|
||||||
|
|
||||||
|
@ -1,211 +1,211 @@
|
|||||||
<HTML>
|
<HTML>
|
||||||
<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">
|
||||||
<META name="author" lang="en" "content="Michiel Broek">
|
<META name="author" lang="en" content="Michiel Broek">
|
||||||
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
||||||
<META name="description" lang="en" content="MBSE BBS Manual">
|
<META name="description" lang="en" content="MBSE BBS Manual">
|
||||||
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
||||||
<TITLE>Netmail routing behaviour.</TITLE>
|
<TITLE>Netmail routing behaviour.</TITLE>
|
||||||
<LINK rel=stylesheet HREF="manual.css">
|
<LINK rel=stylesheet HREF="manual.css">
|
||||||
</HEAD>
|
</HEAD>
|
||||||
<BODY>
|
<BODY>
|
||||||
<BLOCKQUOTE>
|
<BLOCKQUOTE>
|
||||||
<h5>Last update 07-Jun-2001</h5>
|
<h5>Last update 22-Oct-2001</h5>
|
||||||
<P> <P>
|
<P> <P>
|
||||||
|
|
||||||
<h1 ALIGN="CENTER">MBSE BBS Netmail routing behaviour</h1>
|
<h1 ALIGN="CENTER">MBSE BBS Netmail routing behaviour</h1>
|
||||||
|
|
||||||
<h3>Introduction</h3>
|
<h3>Introduction</h3>
|
||||||
<p>
|
<p>
|
||||||
The <strong>mbfido</strong> program that is responsible for unpacking,
|
The <strong>mbfido</strong> program that is responsible for unpacking,
|
||||||
importing, exporting and routing of netmail has a build in default routing
|
importing, exporting and routing of netmail has a build in default routing
|
||||||
plan. In general this is quite simple, if we know the destination node or
|
plan. In general this is quite simple, if we know the destination node or
|
||||||
his uplink, (that node or uplink is in our setup), then we will route via
|
his uplink, (that node or uplink is in our setup), then we will route via
|
||||||
that node in our setup. If the node or his uplink is not in our setup, then
|
that node in our setup. If the node or his uplink is not in our setup, then
|
||||||
the nodelist is used and normal fidonet routing is used. This means, if you
|
the nodelist is used and normal fidonet routing is used. This means, if you
|
||||||
are a node, everything goes to your hub, if you are a hub, then mail for
|
are a node, everything goes to your hub, if you are a hub, then mail for
|
||||||
your downlinks will go direct to the downlinks because they are in your setup,
|
your downlinks will go direct to the downlinks because they are in your setup,
|
||||||
everything else goes to the host.
|
everything else goes to the host.
|
||||||
If you are a host, then your own downlinks will get the mail direct,
|
If you are a host, then your own downlinks will get the mail direct,
|
||||||
the downlinks of the hubs in your net well be routed via the hubs below you.
|
the downlinks of the hubs in your net well be routed via the hubs below you.
|
||||||
If it is for a node in your region but outside your net, mail will be routed via
|
If it is for a node in your region but outside your net, mail will be routed via
|
||||||
the other hosts in your region. Mail to outside your region will go to the
|
the other hosts in your region. Mail to outside your region will go to the
|
||||||
region coordinators system.
|
region coordinators system.
|
||||||
<P> <P>
|
<P> <P>
|
||||||
|
|
||||||
<h3>Tracking and bouncing</h3>
|
<h3>Tracking and bouncing</h3>
|
||||||
<p>
|
<p>
|
||||||
At this moment there is no bouncing of undeliverable mail. I will built this
|
At this moment there is no bouncing of undeliverable mail. I will built this
|
||||||
in, but it will only work inside your own net. I will never include code for
|
in, but it will only work inside your own net. I will never include code for
|
||||||
bouncing mail outside your net, because nodelists are always not uptodate.
|
bouncing mail outside your net, because nodelists are always not uptodate.
|
||||||
<p> <P>
|
<p> <P>
|
||||||
|
|
||||||
<h3>Special routing</h3>
|
<h3>Special routing</h3>
|
||||||
<p>
|
<p>
|
||||||
What if you need special routing. The solution is simple, add the routing
|
What if you need special routing. The solution is simple, add the routing
|
||||||
nodes to your setup and fill in the "route via" field. If you don't have a
|
nodes to your setup and fill in the "route via" field. If you don't have a
|
||||||
session password with that node, leave the password fields blank. This node
|
session password with that node, leave the password fields blank. This node
|
||||||
will never know that he is in your setup as long as you have the notify
|
will never know that he is in your setup as long as you have the notify
|
||||||
settings for that node switched off. To figure
|
settings for that node switched off. To figure
|
||||||
out such solutions yourself, I have included the flow diagrams for the tracking
|
out such solutions yourself, I have included the flow diagrams for the tracking
|
||||||
module.
|
module.
|
||||||
<p> <P>
|
<p> <P>
|
||||||
|
|
||||||
<h3>Main tracking routine:</h3>
|
<h3>Main tracking routine:</h3>
|
||||||
<PRE>
|
<PRE>
|
||||||
<CODE>
|
<CODE>
|
||||||
+=============================+
|
+=============================+
|
||||||
| Trackmail to dest. |
|
| Trackmail to dest. |
|
||||||
+--------------+--------------+
|
+--------------+--------------+
|
||||||
|
|
|
|
||||||
++-------------+-------------++
|
++-------------+-------------++
|
||||||
|| rc = GetRoute to dest || (See next diagram).
|
|| rc = GetRoute to dest || (See next diagram).
|
||||||
++-------------+-------------++
|
++-------------+-------------++
|
||||||
|
|
|
|
||||||
+--------------+--------------+ yes
|
+--------------+--------------+ yes
|
||||||
| rc = R_NOROUTE +-----------------+
|
| rc = R_NOROUTE +-----------------+
|
||||||
+--------------+--------------+ +-------+--------+
|
+--------------+--------------+ +-------+--------+
|
||||||
| no | res: R_NOROUTE |
|
| no | res: R_NOROUTE |
|
||||||
| +================+
|
| +================+
|
||||||
+--------------+--------------+ yes
|
+--------------+--------------+ yes
|
||||||
| rc = R_UNLISTED +-----------------+
|
| rc = R_UNLISTED +-----------------+
|
||||||
+--------------+--------------+ +-------+--------+
|
+--------------+--------------+ +-------+--------+
|
||||||
| | res: R_UNLISTED|
|
| | res: R_UNLISTED|
|
||||||
| +----------------+
|
| +----------------+
|
||||||
+--------------+--------------+ yes
|
+--------------+--------------+ yes
|
||||||
| rc = R_LOCAL +-----------------+
|
| rc = R_LOCAL +-----------------+
|
||||||
+--------------+--------------+ +-------+--------+
|
+--------------+--------------+ +-------+--------+
|
||||||
| no | result: R_LOCAL|
|
| no | result: R_LOCAL|
|
||||||
| +================+
|
| +================+
|
||||||
+--------------+--------------+ no
|
+--------------+--------------+ no
|
||||||
| routing node in setup ? +-----------------+
|
| routing node in setup ? +-----------------+
|
||||||
+--------------+--------------+ +-------+--------+
|
+--------------+--------------+ +-------+--------+
|
||||||
| yes | result: rc |
|
| yes | result: rc |
|
||||||
| +================+
|
| +================+
|
||||||
+--------------+--------------+ no
|
+--------------+--------------+ no
|
||||||
| "Route via" filled in ? +-----------------+
|
| "Route via" filled in ? +-----------------+
|
||||||
+--------------+--------------+ +-------+--------+
|
+--------------+--------------+ +-------+--------+
|
||||||
| yes | res: R_ROUTE |
|
| yes | res: R_ROUTE |
|
||||||
| +================+
|
| +================+
|
||||||
+--------------+--------------+
|
+--------------+--------------+
|
||||||
| Change route to address |
|
| Change route to address |
|
||||||
| result = R_ROUTE |
|
| result = R_ROUTE |
|
||||||
+=============================+
|
+=============================+
|
||||||
</CODE>
|
</CODE>
|
||||||
</PRE>
|
</PRE>
|
||||||
<h3>Sub function GetRoute:</h3>
|
<h3>Sub function GetRoute:</h3>
|
||||||
<PRE>
|
<PRE>
|
||||||
<CODE>
|
<CODE>
|
||||||
+=============================+
|
+=============================+
|
||||||
| GetRoute |
|
| GetRoute |
|
||||||
+--------------+--------------+
|
+--------------+--------------+
|
||||||
|
|
|
|
||||||
+--------------+--------------+
|
+--------------+--------------+
|
||||||
| Add domain name |
|
| Add domain name |
|
||||||
+--------------+--------------+
|
+--------------+--------------+
|
||||||
|
|
|
|
||||||
+--------------+--------------+ yes
|
+--------------+--------------+ yes
|
||||||
| Is dest our own address ? +------------------+
|
| Is dest our own address ? +------------------+
|
||||||
+--------------+--------------+ +--------+-------+
|
+--------------+--------------+ +--------+-------+
|
||||||
| no | rc = R_LOCAL |
|
| no | rc = R_LOCAL |
|
||||||
| +================+
|
| +================+
|
||||||
+--------------+--------------+ yes
|
+--------------+--------------+ yes
|
||||||
| Is dest our point address ? +------------------+
|
| Is dest our point address ? +------------------+
|
||||||
+--------------+--------------+ +--------+-------+
|
+--------------+--------------+ +--------+-------+
|
||||||
| no | rc = R_DIRECT |
|
| no | rc = R_DIRECT |
|
||||||
| +================+
|
| +================+
|
||||||
+--------------+--------------+ yes (route to boss)
|
+--------------+--------------+ yes (route to boss)
|
||||||
| Are we a point system +------------------+
|
| Are we a point system +------------------+
|
||||||
+--------------+--------------+ +--------+-------+
|
+--------------+--------------+ +--------+-------+
|
||||||
| no | dest is my Boss|
|
| no | dest is my Boss|
|
||||||
| | res: R_DIRECT |
|
| | res: R_DIRECT |
|
||||||
| +----------------+
|
| +----------------+
|
||||||
+--------------+--------------+ yes
|
+--------------+--------------+ yes
|
||||||
| Dest. addr. in nodes setup? +------------------+
|
| Dest. addr. in nodes setup? +------------------+
|
||||||
+--------------+--------------+ +--------+-------+
|
+--------------+--------------+ +--------+-------+
|
||||||
| no | rc = R_DIRECT |
|
| no | rc = R_DIRECT |
|
||||||
| +================+
|
| +================+
|
||||||
+--------------+--------------+ yes
|
+--------------+--------------+ yes
|
||||||
| Boss of point dest in setup +------------------+
|
| Boss of point dest in setup +------------------+
|
||||||
+--------------+--------------+ +--------+-------+
|
+--------------+--------------+ +--------+-------+
|
||||||
| no | rc = R_DIRECT |
|
| no | rc = R_DIRECT |
|
||||||
| | dest = Boss |
|
| | dest = Boss |
|
||||||
| +================+
|
| +================+
|
||||||
+--------------+--------------+
|
+--------------+--------------+
|
||||||
| Is node listed and do we | yes
|
| Is node listed and do we | yes
|
||||||
| know his uplink in setup ? +------------------+
|
| know his uplink in setup ? +------------------+
|
||||||
+--------------+--------------+ +--------+-------+
|
+--------------+--------------+ +--------+-------+
|
||||||
| no | dest is uplink |
|
| no | dest is uplink |
|
||||||
| | rc = R_DIRECT |
|
| | rc = R_DIRECT |
|
||||||
| +================+
|
| +================+
|
||||||
+--------------+--------------+ yes
|
+--------------+--------------+ yes
|
||||||
| Are we host in network ? +------------------+
|
| Are we host in network ? +------------------+
|
||||||
+--------------+--------------+ +--------+-------+
|
+--------------+--------------+ +--------+-------+
|
||||||
| no | Set host addr. |
|
| no | Set host addr. |
|
||||||
| +--------+-------+
|
| +--------+-------+
|
||||||
| +----------+
|
| +----------+
|
||||||
+--------------+--------------+ yes |
|
+--------------+--------------+ yes |
|
||||||
| Are we hub in domain ? +------------------+ |
|
| Are we hub in domain ? +------------------+ |
|
||||||
+--------------+--------------+ +--------+-------+ |
|
+--------------+--------------+ +--------+-------+ |
|
||||||
| no | Set hub addr. | v
|
| no | Set hub addr. | v
|
||||||
| +--------+-------+ |
|
| +--------+-------+ |
|
||||||
| | |
|
| | |
|
||||||
+---------------<-----------------+-----<----+
|
+---------------<-----------------+-----<----+
|
||||||
|
|
|
|
||||||
+--------------+--------------+
|
+--------------+--------------+
|
||||||
| Set our region number |
|
| Set our region number |
|
||||||
+--------------+--------------+
|
+--------------+--------------+
|
||||||
|
|
|
|
||||||
|
|
|
|
||||||
+--------------+--------------+ no
|
+--------------+--------------+ no
|
||||||
| Host address set ? +-----------------------------+
|
| Host address set ? +-----------------------------+
|
||||||
+--------------+--------------+ |
|
+--------------+--------------+ |
|
||||||
| yes |
|
| yes |
|
||||||
| |
|
| |
|
||||||
+--------------+--------------+
|
+--------------+--------------+
|
||||||
| Dest region <> our region | yes |
|
| Dest region <> our region | yes |
|
||||||
| or Dest zone <> our zone +------------------+ |
|
| or Dest zone <> our zone +------------------+ |
|
||||||
+--------------+--------------+ +--------+-------+ |
|
+--------------+--------------+ +--------+-------+ |
|
||||||
| no | Dest to RC | |
|
| no | Dest to RC | |
|
||||||
| | rc = R_ROUTE | |
|
| | rc = R_ROUTE | |
|
||||||
| +================+ |
|
| +================+ |
|
||||||
+--------------+--------------+ yes |
|
+--------------+--------------+ yes |
|
||||||
| Dest net <> our net +------------------+ |
|
| Dest net <> our net +------------------+ |
|
||||||
+--------------+--------------+ +--------+-------+ |
|
+--------------+--------------+ +--------+-------+ |
|
||||||
| no | to host destnet| |
|
| no | to host destnet| |
|
||||||
| | rc = R_ROUTE | |
|
| | rc = R_ROUTE | |
|
||||||
| +================+ |
|
| +================+ |
|
||||||
+--------------+--------------+ yes |
|
+--------------+--------------+ yes |
|
||||||
| Has node a hub +------------------+ |
|
| Has node a hub +------------------+ |
|
||||||
+--------------+--------------+ +--------+-------+ |
|
+--------------+--------------+ +--------+-------+ |
|
||||||
| yes | to node's hub | |
|
| yes | to node's hub | |
|
||||||
+------+--------+ | rc = R_ROUTE | |
|
+------+--------+ | rc = R_ROUTE | |
|
||||||
| dest is direct| +================+ |
|
| dest is direct| +================+ |
|
||||||
| rc = R_ROUTE | |
|
| rc = R_ROUTE | |
|
||||||
+===============+ |
|
+===============+ |
|
||||||
|
|
|
|
||||||
+------------------------<-------------------+
|
+------------------------<-------------------+
|
||||||
+--------------+--------------+ no
|
+--------------+--------------+ no
|
||||||
| Hub address set ? +-----------------+
|
| Hub address set ? +-----------------+
|
||||||
+--------------+--------------+ +-------+--------+
|
+--------------+--------------+ +-------+--------+
|
||||||
| yes | via our hub |
|
| yes | via our hub |
|
||||||
| | rc = R_ROUTE |
|
| | rc = R_ROUTE |
|
||||||
| +================+
|
| +================+
|
||||||
+--------------+--------------+ yes
|
+--------------+--------------+ yes
|
||||||
| Dest node of our hub addr +-----------------+
|
| Dest node of our hub addr +-----------------+
|
||||||
+--------------+--------------+ +-------+--------+
|
+--------------+--------------+ +-------+--------+
|
||||||
| no | rc = R_DIRECT |
|
| no | rc = R_DIRECT |
|
||||||
| +================+
|
| +================+
|
||||||
+------+-------+
|
+------+-------+
|
||||||
| dest is host |
|
| dest is host |
|
||||||
| rc = R_ROUTE |
|
| rc = R_ROUTE |
|
||||||
+==============+
|
+==============+
|
||||||
</CODE>
|
</CODE>
|
||||||
</PRE>
|
</PRE>
|
||||||
|
|
||||||
<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" width="33" height="35"> Go Back</A>
|
||||||
</BLOCKQUOTE>
|
</BLOCKQUOTE>
|
||||||
</BODY>
|
</BODY>
|
||||||
</HTML>
|
</HTML>
|
||||||
|
|
||||||
|
@ -1,45 +1,45 @@
|
|||||||
<HTML>
|
<HTML>
|
||||||
<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">
|
||||||
<META name="author" lang="en" "content="Michiel Broek">
|
<META name="author" lang="en" content="Michiel Broek">
|
||||||
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
<META name="copyright" lang="en" content="Copyright Michiel Broek">
|
||||||
<META name="description" lang="en" content="MBSE BBS Manual">
|
<META name="description" lang="en" content="MBSE BBS Manual">
|
||||||
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
<META name="keywords" lang="en" content="MBSE BBS, MBSE, BBS, manual, fido, fidonet, gateway, tosser, mail, tic, mailer">
|
||||||
<TITLE>Using UPS semafore's.</TITLE>
|
<TITLE>Using UPS semafore's.</TITLE>
|
||||||
<LINK rel=stylesheet HREF="manual.css">
|
<LINK rel=stylesheet HREF="manual.css">
|
||||||
</HEAD>
|
</HEAD>
|
||||||
<BODY>
|
<BODY>
|
||||||
<BLOCKQUOTE>
|
<BLOCKQUOTE>
|
||||||
<h5>Last update 08-Jun-2001</h5>
|
<h5>Last update 08-Jun-2001</h5>
|
||||||
<P> <P>
|
<P> <P>
|
||||||
<H1>MBSE BBS - Using UPS semafore's.</H1>
|
<H1>MBSE BBS - Using UPS semafore's.</H1>
|
||||||
<P>
|
<P>
|
||||||
|
|
||||||
|
|
||||||
If you have a UPS and you are able to let your UPS software create semafore's when powerfail conditions
|
If you have a UPS and you are able to let your UPS software create semafore's when powerfail conditions
|
||||||
occur then read on. The MBSE BBS taskmanager and a lot of utilities will act on two special semafore's,
|
occur then read on. The MBSE BBS taskmanager and a lot of utilities will act on two special semafore's,
|
||||||
they are:
|
they are:
|
||||||
|
|
||||||
<ol>
|
<ol>
|
||||||
<li><code>upsalarm</code>, this semafore should be set when there is no mains power, but there is enough
|
<li><code>upsalarm</code>, this semafore should be set when there is no mains power, but there is enough
|
||||||
power left to operate your system. All background tasks will be suspended as long as this condition
|
power left to operate your system. All background tasks will be suspended as long as this condition
|
||||||
is true. If the power comes back, the UPS software should remove this semafore.
|
is true. If the power comes back, the UPS software should remove this semafore.
|
||||||
<li><code>upsdown</code>, this semafore should be set when the UPS sofware signals your system to go down.
|
<li><code>upsdown</code>, this semafore should be set when the UPS sofware signals your system to go down.
|
||||||
This is a fatal condition and there is no way back. Even if the power comes back your system should
|
This is a fatal condition and there is no way back. Even if the power comes back your system should
|
||||||
shutdown and the UPS will disconnect the power to your system. After a while it will turn the power on
|
shutdown and the UPS will disconnect the power to your system. After a while it will turn the power on
|
||||||
again and your system boots. MBSE BBS will if this semafore is seen kick users out of the bbs, and the
|
again and your system boots. MBSE BBS will if this semafore is seen kick users out of the bbs, and the
|
||||||
system shutdown script will try to close MBSE BBS as quick as possible. Normal the close timeout is
|
system shutdown script will try to close MBSE BBS as quick as possible. Normal the close timeout is
|
||||||
one hour to let users normal finnish what they were doing, now it is only 30 seconds and if they were
|
one hour to let users normal finnish what they were doing, now it is only 30 seconds and if they were
|
||||||
not logged out, they will be disconnected anyway.
|
not logged out, they will be disconnected anyway.
|
||||||
</ol>
|
</ol>
|
||||||
I know not all UPS software can do this but most UPS software is open source so you can change it to create
|
I know not all UPS software can do this but most UPS software is open source so you can change it to create
|
||||||
these semafore's. It is not a problem that UPS semafore's still exist if the systems boots, the MBSE BBS
|
these semafore's. It is not a problem that UPS semafore's still exist if the systems boots, the MBSE BBS
|
||||||
startup scripts will remove them before the bbs is started.
|
startup scripts will remove them before the bbs is started.
|
||||||
<P> <P>
|
<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" width="33" height="35"> Go Back</A>
|
||||||
</BODY>
|
</BODY>
|
||||||
</HTML>
|
</HTML>
|
||||||
|
|
||||||
|
@ -2,10 +2,10 @@
|
|||||||
*
|
*
|
||||||
* File ..................: mbse.h
|
* File ..................: mbse.h
|
||||||
* Purpose ...............: Global variables for MBSE BBS
|
* Purpose ...............: Global variables for MBSE BBS
|
||||||
* Last modification date : 25-Aug-2000
|
* Last modification date : 22-Oct-2001
|
||||||
*
|
*
|
||||||
*****************************************************************************
|
*****************************************************************************
|
||||||
* Copyright (C) 1997-2000
|
* Copyright (C) 1997-2001
|
||||||
*
|
*
|
||||||
* Michiel Broek FIDO: 2:280/2802
|
* Michiel Broek FIDO: 2:280/2802
|
||||||
* Beekmansbos 10
|
* Beekmansbos 10
|
||||||
@ -108,6 +108,7 @@ int iUnixMode; /* Using Unix Accounts */
|
|||||||
char sUnixName[9]; /* Unix login name */
|
char sUnixName[9]; /* Unix login name */
|
||||||
time_t Time2Go; /* Calculated time to force logout */
|
time_t Time2Go; /* Calculated time to force logout */
|
||||||
struct tm *l_date; /* Structure for Date */
|
struct tm *l_date; /* Structure for Date */
|
||||||
|
int iNode; /* Current node number */
|
||||||
|
|
||||||
time_t ltime;
|
time_t ltime;
|
||||||
time_t Time_Now;
|
time_t Time_Now;
|
||||||
|
@ -290,9 +290,14 @@ void ExtDoor(char *Program, int NoDoorsys, int Y2Kdoorsys, int Comport, int NoSu
|
|||||||
|
|
||||||
WhosDoingWhat(DOOR);
|
WhosDoingWhat(DOOR);
|
||||||
|
|
||||||
if((strstr(Program, "/A")) != NULL) {
|
if ((strstr(Program, "/N")) != NULL) {
|
||||||
|
sprintf(temp1, "%d", iNode);
|
||||||
|
strreplace(Program, (char *)"/N", temp1);
|
||||||
|
}
|
||||||
|
|
||||||
|
if ((strstr(Program, "/A")) != NULL) {
|
||||||
colour(3, 0);
|
colour(3, 0);
|
||||||
if((String = strstr(Program, "/T=")) != NULL) {
|
if ((String = strstr(Program, "/T=")) != NULL) {
|
||||||
String1 = String + 3;
|
String1 = String + 3;
|
||||||
printf("\n%s", String1);
|
printf("\n%s", String1);
|
||||||
} else
|
} else
|
||||||
@ -305,9 +310,9 @@ void ExtDoor(char *Program, int NoDoorsys, int Y2Kdoorsys, int Comport, int NoSu
|
|||||||
strreplace(Program, (char *)"/A", temp1);
|
strreplace(Program, (char *)"/A", temp1);
|
||||||
|
|
||||||
for(i = 0; i < strlen(Program); i++) {
|
for(i = 0; i < strlen(Program); i++) {
|
||||||
if(*(Program + i) == '\0')
|
if (*(Program + i) == '\0')
|
||||||
break;
|
break;
|
||||||
if(*(Program + i) == '/')
|
if (*(Program + i) == '/')
|
||||||
*(Program + i) = '\0';
|
*(Program + i) = '\0';
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
@ -340,7 +345,7 @@ void ExtDoor(char *Program, int NoDoorsys, int Y2Kdoorsys, int Comport, int NoSu
|
|||||||
fprintf(fp, "0\r\n"); /* Effective baudrate */
|
fprintf(fp, "0\r\n"); /* Effective baudrate */
|
||||||
}
|
}
|
||||||
fprintf(fp, "8\r\n"); /* Databits */
|
fprintf(fp, "8\r\n"); /* Databits */
|
||||||
fprintf(fp, "1\r\n"); /* Node number */
|
fprintf(fp, "%d\r\n", iNode); /* Node number */
|
||||||
if (Comport)
|
if (Comport)
|
||||||
fprintf(fp, "115200\r\n");/* Locked baudrate */
|
fprintf(fp, "115200\r\n");/* Locked baudrate */
|
||||||
else
|
else
|
||||||
@ -425,6 +430,7 @@ int exec_nosuid(char *mandato)
|
|||||||
|
|
||||||
if (mandato == NULL)
|
if (mandato == NULL)
|
||||||
return 1; /* Prevent running a shell */
|
return 1; /* Prevent running a shell */
|
||||||
|
|
||||||
Syslog('+', "Execve: /bin/sh -c %s", mandato);
|
Syslog('+', "Execve: /bin/sh -c %s", mandato);
|
||||||
pid = fork();
|
pid = fork();
|
||||||
if (pid == -1)
|
if (pid == -1)
|
||||||
|
@ -1,8 +1,8 @@
|
|||||||
/*****************************************************************************
|
/*****************************************************************************
|
||||||
*
|
*
|
||||||
* File ..................: bbs/mbsebbs.c
|
* File ..................: mbsebbs/mbsebbs.c
|
||||||
* Purpose ...............: Main startup
|
* Purpose ...............: Main startup
|
||||||
* Last modification date : 28-Jun-2001
|
* Last modification date : 22-Oct-2001
|
||||||
*
|
*
|
||||||
*****************************************************************************
|
*****************************************************************************
|
||||||
* Copyright (C) 1997-2001
|
* Copyright (C) 1997-2001
|
||||||
@ -102,13 +102,6 @@ int main(int argc, char **argv)
|
|||||||
#endif
|
#endif
|
||||||
exit(1);
|
exit(1);
|
||||||
}
|
}
|
||||||
// if (seteuid(pw->pw_uid) == -1) {
|
|
||||||
// perror("Can't seteuid() to \"mbse\" user");
|
|
||||||
//#ifdef MEMWATCH
|
|
||||||
// mwTerm();
|
|
||||||
//#endif
|
|
||||||
// exit(1);
|
|
||||||
// }
|
|
||||||
|
|
||||||
/*
|
/*
|
||||||
* Set local time and statistic indexes.
|
* Set local time and statistic indexes.
|
||||||
@ -214,13 +207,15 @@ int main(int argc, char **argv)
|
|||||||
*/
|
*/
|
||||||
sprintf(temp, "%s/etc/ttyinfo.data", getenv("MBSE_ROOT"));
|
sprintf(temp, "%s/etc/ttyinfo.data", getenv("MBSE_ROOT"));
|
||||||
|
|
||||||
|
iNode = 0;
|
||||||
if ((pTty = fopen(temp, "r")) == NULL) {
|
if ((pTty = fopen(temp, "r")) == NULL) {
|
||||||
WriteError("Can't read %s", temp);
|
WriteError("Can't read %s", temp);
|
||||||
} else {
|
} else {
|
||||||
fread(&ttyinfohdr, sizeof(ttyinfohdr), 1, pTty);
|
fread(&ttyinfohdr, sizeof(ttyinfohdr), 1, pTty);
|
||||||
|
|
||||||
while (fread(&ttyinfo, ttyinfohdr.recsize, 1, pTty) == 1) {
|
while (fread(&ttyinfo, ttyinfohdr.recsize, 1, pTty) == 1) {
|
||||||
if (strcmp(ttyinfo.tty, pTTY) == 0)
|
iNode++;
|
||||||
|
if (strcmp(ttyinfo.tty, pTTY) == 0)
|
||||||
break;
|
break;
|
||||||
}
|
}
|
||||||
fclose(pTty);
|
fclose(pTty);
|
||||||
@ -230,6 +225,7 @@ int main(int argc, char **argv)
|
|||||||
printf("No BBS on this port allowed!\n\n");
|
printf("No BBS on this port allowed!\n\n");
|
||||||
Quick_Bye(0);
|
Quick_Bye(0);
|
||||||
}
|
}
|
||||||
|
Syslog('b', "Node number %d", iNode);
|
||||||
|
|
||||||
/*
|
/*
|
||||||
* Ask whether to display Connect String
|
* Ask whether to display Connect String
|
||||||
|
@ -22,8 +22,11 @@ install-exec-local:
|
|||||||
$(INSTALL) -o @OWNER@ -g @GROUP@ -m 0711 monthly $(sysconfdir) ; \
|
$(INSTALL) -o @OWNER@ -g @GROUP@ -m 0711 monthly $(sysconfdir) ; \
|
||||||
echo "$(INSTALL) -o @OWNER@ -g @GROUP@ -m 0711 monthly $(sysconfdir)" ; \
|
echo "$(INSTALL) -o @OWNER@ -g @GROUP@ -m 0711 monthly $(sysconfdir)" ; \
|
||||||
fi
|
fi
|
||||||
|
$(INSTALL) -o @OWNER@ -g @GROUP@ -m 0755 bbsdoor.sh $(bindir)
|
||||||
|
$(INSTALL) -o @OWNER@ -g @GROUP@ -m 0755 mem $(bindir)
|
||||||
@bash ./installinit.sh
|
@bash ./installinit.sh
|
||||||
|
|
||||||
EXTRA_DIST = README maint midnight weekly monthly installinit.sh rc rc.shutdown mbse.start mbse.stop
|
EXTRA_DIST = README maint midnight weekly monthly installinit.sh rc rc.shutdown \
|
||||||
|
mbse.start mbse.stop bbsdoor.sh mem
|
||||||
|
|
||||||
|
|
||||||
|
@ -74,7 +74,8 @@ VERSION = @VERSION@
|
|||||||
|
|
||||||
SUBDIRS = .
|
SUBDIRS = .
|
||||||
|
|
||||||
EXTRA_DIST = README maint midnight weekly monthly installinit.sh rc rc.shutdown mbse.start mbse.stop
|
EXTRA_DIST = README maint midnight weekly monthly installinit.sh rc rc.shutdown mbse.start mbse.stop bbsdoor.sh mem
|
||||||
|
|
||||||
mkinstalldirs = $(SHELL) $(top_srcdir)/mkinstalldirs
|
mkinstalldirs = $(SHELL) $(top_srcdir)/mkinstalldirs
|
||||||
CONFIG_HEADER = ../config.h
|
CONFIG_HEADER = ../config.h
|
||||||
CONFIG_CLEAN_FILES =
|
CONFIG_CLEAN_FILES =
|
||||||
@ -304,6 +305,8 @@ install-exec-local:
|
|||||||
$(INSTALL) -o @OWNER@ -g @GROUP@ -m 0711 monthly $(sysconfdir) ; \
|
$(INSTALL) -o @OWNER@ -g @GROUP@ -m 0711 monthly $(sysconfdir) ; \
|
||||||
echo "$(INSTALL) -o @OWNER@ -g @GROUP@ -m 0711 monthly $(sysconfdir)" ; \
|
echo "$(INSTALL) -o @OWNER@ -g @GROUP@ -m 0711 monthly $(sysconfdir)" ; \
|
||||||
fi
|
fi
|
||||||
|
$(INSTALL) -o @OWNER@ -g @GROUP@ -m 0755 bbsdoor.sh $(bindir)
|
||||||
|
$(INSTALL) -o @OWNER@ -g @GROUP@ -m 0755 mem $(bindir)
|
||||||
@bash ./installinit.sh
|
@bash ./installinit.sh
|
||||||
|
|
||||||
# Tell versions [3.59,3.63) of GNU make to not export all variables.
|
# Tell versions [3.59,3.63) of GNU make to not export all variables.
|
||||||
|
Reference in New Issue
Block a user