- Author: P.E. Kimble aka King Kimerud
- kimerud@bayhaus.org
-
- Introduction
-
- This FAQ is a work in progress. It is not complete, nor does its author claim
- that it is complete. This FAQ only answers questions pertaining to using MBSE
- BBS on your Linux box. It is a compilation of previous questions that Michiel
- Broek has recieved and answered from us newbies in getting MBSE up & running.
-
Why do I have to install MBSE in
-the /opt directory?
-
A 1.1
-The /opt is for extra applications, when mbse is installed there it
-is easier to upgrade the OS. If you insist on installing in /usr/local
-the choose /usr/local/mbse.
-
-Currently only on most Linux distributions, FreeBSD and NetBSD.
-The author, Michiel Broek,
-has made a valiant effort ensuring that MBSE will recognize and
-install on the major distributions of Linux.
-
-I just installed mbse, now I get a Socket send failed error 2.
-
-
A 1.7
-With a normal system boot the mbtask daemon will be started by one of the
-systems init scripts. If you just installed mbse you need to do this for the
-first time manually. As user mbse issue the following commands:
-
Author: P.E. Kimble aka King Kimerud kimerud@bayhaus.org
+ Introduction
+
This FAQ is a work in progress. It is not complete, nor does its
+author claim that it is complete. This FAQ only answers questions pertaining
+to using MBSE BBS on your Linux box. It is a compilation of previous questions
+that Michiel Broek has recieved and answered from us newbies in getting
+MBSE up & running.
Why do I have to install MBSE in the /opt directory?
+
+
+
A 1.1
+
The /opt is for extra applications, when mbse is installed there
+it is easier to upgrade the OS. If you insist on installing in /usr/local
+the choose /usr/local/mbse.
Currently only on most Linux distributions, FreeBSD and NetBSD.
+The author, Michiel Broek, has made a valiant effort ensuring that MBSE will
+recognize and install on the major distributions of Linux.
I just installed mbse, now I get a Socket send failed error
+2.
+
+
+
A 1.7
+
With a normal system boot the mbtask daemon will be started
+by one of the systems init scripts. If you just installed mbse you need to
+do this for the first time manually. As user mbse issue the following
+commands:
+
mbtask
mbstat open
-
-This will start the daemon, the daemon creates the default databases. Then you
-can use mbsetup to configure your new system.
-
-Note: From previous experience, it is vital that you follow the docs
-closely. Also, ensure that you have a copy of a valid nodelist and
-nodediff file. I have ran into problems where either the noddiffs
-don't match the nodelist, the crc checks fail, or I have files from
-two different zones. I have even had to back up several months before
-finding a valid noddiff that would match the nodelist.
-
-Make sure the domain translations do exist, with mbsetup enter
-menu 17 and save it even if you didn't change anything.
-
-No, not directly. It is a matter of using scripts to translate the .*lo
-(*.flo, *.clo, *.dlo, *.ilo) files for each node, and copying the node's
-outbound files to their respective directory.
-Refer to 3.2.
-
-How do I configure MBSE for my ftp filenet feeds?
-
-
A 3.2
-
-
In mbsetup menu 1.4.12:2, remove any reference to a DOS translation
-path.
-
-In mbsetup menu 1.4.12:3, remove any reference to a DOS translation
-path.
-
-
-This will give you a "True" path to your files directory where mbcico tosses
-the inbound files.
-
-
-Ftp Script for running a ftp feed with MBSE.
-NOTE: Gracefully contributed by Janis Kacht <janis@filegate.net>
-
-This script does not delete or change the .flo file. It reads it in and
-creates a new script that will be used to move and copy the files to the
-user's
-outbound directory you specify on the command line. Just call this script,
-then call the finalflo.sh script with the directory name where the files
-should be PUT, like:
-
-You will need a full path to the flo file in the "test" line below
-and change
-the name of the flo file (it's not going to be 00000063.flo)
-Uncomment the "if test" line, and also uncomment the last line (fi)
-
-#!/bin/sh
-if test -e /opt/mbse/mail/outbound/00000063.flo ; then
- cat 00000063.flo | sed 's/\/home/cp \/home/' > newflo.txt
- cat newflo.txt | sed 's/\^\cp \/home/mv \/home/'> newflo2.txt
- cat newflo2.txt | sed 's/$/ \$1/' > finalflo.sh
-fi
-
-
-here's what finalflo.sh looks like,
-$1 is a variable for the directory name you specify on the command line,
-or in a cron script:
-
-Janis Kracht can not and will not be held liable if harm is done to your
-computer system due to any use of this script, either directly or indirectly.
-This script works perfectly when instructions are followed, and the correct
-directories are substitiuted. How it will affect your system, is the
-responsiblity of the system administrator!
-
- Do not forget to test this setup. It has work fine on my system, but
- nothing works the way it should the first time out of the box! Pay close
- attention to the ftp script and directories you enter. It seems as if 75%
- of the problems experinced with this sed script is due to improper
- outbound directories
-
-Of course, you have to configure and build your kernel for ISDN support
-and the correct drivers for your card. It is beyond the scope of this
-document to explain how to do that.
-
-To your /etc/inittab file add the following lines for your ISDN devices
-ttyI0 and ttyI1.
-
-To your mgetty.config file
-[/usr/local/etc/mgetty_sendfax/mgetty.config on my system]
-set up the ttyI0 and ttyI1 ports. With AT&E you set the
-MSN/EAZ the device should listen to. This should for an MSN be
-your telephone number with the area code but
-without the leading 0. For an EAZ the last digit of your EAZ.
-
-The ISDN ports
-
-port ttyI0
-modem-type data
-init-chat "" ATZ OK AT&E714015437&W0 OK AT&B512 OK
-
-port ttyI1
-modem-type data
-init-chat "" ATZ OK AT&E714017198&W0 OK AT&B512 OK
-
-
-From the mbsetup menu #5 "Edit Modem types" configure the ISDN modem
-type.
-
-
+
+ This will start the daemon, the daemon creates the default databases. Then
+you can use mbsetup to configure your new system.
Note: From previous experience, it is vital that you follow
+the docs closely. Also, ensure that you have a copy of a valid nodelist
+and nodediff file. I have ran into problems where either the noddiffs don't
+match the nodelist, the crc checks fail, or I have files from two different
+zones. I have even had to back up several months before finding a valid
+noddiff that would match the nodelist.
+ Make sure the domain translations do exist, with mbsetup enter menu 17
+and save it even if you didn't change anything.
No, not directly. It is a matter of using scripts to translate
+the .*lo (*.flo, *.clo, *.dlo, *.ilo) files for each node, and copying the
+node's outbound files to their respective directory. Refer
+to 3.2.
+
In mbsetup menu 1.4.12:2, remove any reference to a DOS translation path.
+
+
In mbsetup menu 1.4.12:3, remove any reference to a DOS translation
+path.
+
+ This will give you a "True" path to your files directory where mbcico tosses
+the inbound files.
+
+
Ftp Script for running a ftp feed with MBSE.
+ NOTE: Gracefully contributed by Janis Kacht <janis@filegate.net>
+
This script does not delete or change the .flo file. It reads
+it in and creates a new script that will be used to move and copy the files
+to the user's outbound directory you specify on the command line. Just call
+this script, then call the finalflo.sh script with the directory name where
+the files should be PUT, like:
You will need a full path to the flo file in the "test" line
+below and change the name of the flo file (it's not going to be 00000063.flo)
+ Uncomment the "if test" line, and also uncomment the last line (fi)
+
#!/bin/sh if test -e /opt/mbse/mail/outbound/00000063.flo ; then cat 00000063.flo | sed 's/\/home/cp \/home/' > newflo.txt cat newflo.txt | sed 's/\^\cp \/home/mv \/home/'> newflo2.txt cat newflo2.txt | sed 's/$/ \$1/' > finalflo.sh fi
+
+
here's what finalflo.sh looks like, $1 is a variable for
+the directory name you specify on the command line, or in a cron script:
+
Janis Kracht can not and will not be held liable if harm
+is done to your computer system due to any use of this script, either directly
+or indirectly. This script works perfectly when instructions are followed,
+and the correct directories are substitiuted. How it will affect your system,
+is the responsiblity of the system administrator!
+
+
Do not forget to test this setup. It has work fine on my
+system, but nothing works the way it should the first time out of the box!
+Pay close attention to the ftp script and directories you enter. It seems
+as if 75% of the problems experinced with this sed script is due to improper
+ outbound directories
Of course, you have to configure and build your kernel for ISDN
+support and the correct drivers for your card. It is beyond the scope of
+this document to explain how to do that.
+
To your /etc/inittab file add the following lines for your ISDN
+devices ttyI0 and ttyI1.
+ To your mgetty.config file [/usr/local/etc/mgetty_sendfax/mgetty.config
+on my system] set up the ttyI0 and ttyI1 ports. With AT&E you set the
+MSN/EAZ the device should listen to. This should for an MSN be your telephone
+number with the area code but without the leading 0. For an
+EAZ the last digit of your EAZ.
+
The ISDN ports
+
port ttyI0 modem-type data init-chat "" ATZ OK AT&E714015437&W0 OK AT&B512 OK
port ttyI1 modem-type data init-chat "" ATZ OK AT&E714017198&W0 OK AT&B512 OK
+ From the mbsetup menu #5 "Edit Modem types" configure the ISDN modem type.
+
Modem type ISDN Linux
Init string ATZ\r
Init string
@@ -383,10 +508,9 @@ EMSI speed 28800 ! not relevant for ISDN
Strip dashes No
Available Yes
-
-And from #6 "Edit TTY lines info" the ISDN lines
-
-
+
+ And from #6 "Edit TTY lines info" the ISDN lines
+
TTY name ISDN Line 1
Device name ttyI0
Phone or DNS 31-71-4015437
@@ -415,29 +539,32 @@ Modem type ISDN Linux
Locked speed 0
EMSI name The Wizard's ISDN line 2
-
-Since MBSE BBS version 0.33.12 GoldED and MBSE BBS can be used together
-without problems as long as you use it to read the sysop mail. The
-mbsetup program can export a file called /opt/mbse/etc/golded.inc which
-will contain your main Aka's, Aka matching, sysop name and all your mail
-areas. This file is only (re)created if you change the global settings or
-one of the mail areas. The first time you must force this by making a change
-somewhere.
-
-Now create /opt/mbse/etc/golded.cfg, here is what I wrote:
-
Since MBSE BBS version 0.33.12 GoldED and MBSE BBS can be used
+together without problems as long as you use it to read the sysop mail. The
+mbsetup program can export a file called /opt/mbse/etc/golded.inc which will
+contain your main Aka's, Aka matching, sysop name and all your mail areas.
+This file is only (re)created if you change the global settings or one of
+the mail areas. The first time you must force this by making a change somewhere.
+
Now create /opt/mbse/etc/golded.cfg, here is what I wrote:
+
; GoldED.cfg
;
; Internet Addressing
@@ -465,265 +592,168 @@ INCLUDE /opt/mbse/etc/golded.inc
;
; The end.
-
-Put in /opt/mbse/.profile the following line:
-export GOLDED=$HOME/etc
-
-When you now start GoldED you use it as the sysop. Make sure that the sysop's
-userrecord is the first user in the MBSE BBS userbase. If not, the lastread
-pointers are not right. The GoldED nodelist compiler can be added to the setup
-in menu 18.
-
Written by: Redy Rodriguez, sysop of Parolas BBS 2:348/609
-Fidonet: Redy rodriguez 2:348/609
-Email: redy@users.sourceforge.net
- Redy_Rodriguez@f609.n348.z2.fidospain.org
-
-
-NO WARANTEE
-
-The information gathered here, works for the indicated intention.
-It is proven and working in PAROLAS BBS, however, I do not guarantee that it
-works correctly in all the cases.
-The author is not responsible for the damage this can cause.
-If you follow the instructions, and you get not the expected result, or as
-a result of it you get undesired results, you loose data or destroy your
-system, you you will be the only person in charge.
-
-INTRODUCTION
-
-This document describes how I have been able to execute MS/DOS doors in
-MBSEBBS. Probably it is not the best way to do it, but this is the one that
-works for me.
-If somebody finds one more more effective, or simpler or safer a solution,
-the I like to hear this solution.
-
-WHAT IS NEEDED?
-
-MBSEBBS is correctly compiled and working, in my case I have the version
-0.33.19, that is at the moment the most recent and stable, I suppose that
-this method can be valid for newer versions.
-DOSEMU 1.0.2 I have tried previous versions, but these do not work correctly
-with virtual ports. You can download dosemu.1.02.tgz from
-www.dosemu.org,
-you may also need to download the freedos archive dosemu-freedos-bin-1.02.tgz.
-A partition with MS/DOS, I have on my disc a partition with installed MS/DOS,
-and that is the one that I use, but I'm sure that many doors could work
-correctly with the freedos.
-You also need sudo.
-Sudo is a utility that let's ordinary users execute certain programs as
-superuser, this is available with almost all Linux distributions.
-
-COMPILING DOSEMU
-
-Unpack dosemu in some directory, for example /usr/src, then changed into
-that directory and execute 'make'. When this is ready we have dosemu compiled.
-If we already had a previous version of dosemu it is advisable to uninstall it
-before continuing.
-Copy dosemu-freedos-bin-1.02.tgz to the toplevel directory of the dosemu source
-and execute:
-
-
+
+ Put in /opt/mbse/.profile the following line: export GOLDED=$HOME/etc
+
When you now start GoldED you use it as the sysop. Make sure
+that the sysop's userrecord is the first user in the MBSE BBS userbase. If
+not, the lastread pointers are not right. The GoldED nodelist compiler can
+be added to the setup in menu 18.
Written by: Redy Rodriguez, sysop of Parolas BBS 2:348/609 Fidonet: Redy rodriguez 2:348/609 Email: redy@users.sourceforge.net Redy_Rodriguez@f609.n348.z2.fidospain.org
+
+
NO WARANTEE
+
The information gathered here, works for the indicated intention.
+ It is proven and working in PAROLAS BBS, however, I do not guarantee that
+it works correctly in all the cases. The author is not responsible for the
+damage this can cause. If you follow the instructions, and you get not the
+expected result, or as a result of it you get undesired results, you loose
+data or destroy your system, you you will be the only person in charge.
+
+
INTRODUCTION
+
This document describes how I have been able to execute MS/DOS
+doors in MBSEBBS. Probably it is not the best way to do it, but this is
+the one that works for me. If somebody finds one more more effective, or
+simpler or safer a solution, the I like to hear this solution.
+
WHAT IS NEEDED?
+
MBSEBBS is correctly compiled and working, in my case I have
+the version 0.33.19, that is at the moment the most recent and stable, I
+suppose that this method can be valid for newer versions. DOSEMU 1.0.2
+I have tried previous versions, but these do not work correctly with virtual
+ports. You can download dosemu.1.02.tgz from www.dosemu.org
+, you may also need to download the freedos archive dosemu-freedos-bin-1.02.tgz.
+A partition with MS/DOS, I have on my disc a partition with installed MS/DOS,
+and that is the one that I use, but I'm sure that many doors could work correctly
+with the freedos. You also need sudo. Sudo is a utility that let's
+ordinary users execute certain programs as superuser, this is available with
+almost all Linux distributions.
+
COMPILING DOSEMU
+
Unpack dosemu in some directory, for example /usr/src, then changed
+into that directory and execute 'make'. When this is ready we have dosemu
+compiled. If we already had a previous version of dosemu it is advisable
+to uninstall it before continuing. Copy dosemu-freedos-bin-1.02.tgz to the
+toplevel directory of the dosemu source and execute:
-In the directory etc, within the directory where we have decompressed the
-source code of dosemu we have configuration examples. Create the directory
-/var/lib/dosemu if it does not exist the directory, and copy global.conf to
-that directory. Also copy dosemu.conf to directory /etc and copy
-dosemu.users.secure as dosemu.users to /etc.
-
-
-CONFIGURE THE DOS PARTITION
-
-Now we must configure the dos partition, in my case this exists as a mounted
-dos partition in /dos/c. If this is not the case then you could work with an
-image of freedos. I have created in my dos partition a directory c:\doors
-where I install all doors that I want to use, and a file called c:\doors.bat
-with the following contents:
-
-Change to the directory /var/lib/dosemu and create directory called for
-example 'c':
-
-
+
+ In the directory etc, within the directory where we have decompressed the
+ source code of dosemu we have configuration examples. Create the directory
+/var/lib/dosemu if it does not exist the directory, and copy global.conf
+to that directory. Also copy dosemu.conf to directory /etc and copy dosemu.users.secure
+as dosemu.users to /etc.
+
CONFIGURE THE DOS PARTITION
+
Now we must configure the dos partition, in my case this exists
+as a mounted dos partition in /dos/c. If this is not the case then you could
+work with an image of freedos. I have created in my dos partition a directory
+c:\doors where I install all doors that I want to use, and a file called
+c:\doors.bat with the following contents:
+
@echo off c: cd \doors if exist %1.bat call %1 %2 %3 %4 %5 %6 %7 %8 %9 c:\dosemu\exitemu
+ Change to the directory /var/lib/dosemu and create directory called for
+ example 'c':
+
mkdir c.
-
-A link to the mounted partition could be made but I prefer to create a new
-directory and in that directory make links to dos program which are only
-of interest for us. Many programs and directories of the dos partition
-are not needed in dosemu and to run doors.
-Change to the created directory and make links to everything what we have
-in our dos partition (we will erase soon what we do not need).
-Autoexec.bat and config.sys must copied instead of making links so we can
-modify them, because surely we will want that they are different in dosemu,
-then in real dos.
-
-
+
+ A link to the mounted partition could be made but I prefer to create a new
+ directory and in that directory make links to dos program which are only
+of interest for us. Many programs and directories of the dos partition are
+not needed in dosemu and to run doors. Change to the created directory and
+make links to everything what we have in our dos partition (we will erase
+soon what we do not need). Autoexec.bat and config.sys must copied instead
+of making links so we can modify them, because surely we will want that they
+are different in dosemu, then in real dos.
+
cd c
ln -s /dos/c/* .
rm autoexec.bat
rm config.sys
cp /dos/c/autoexec.bat config.sys .
-
-Create a directory dosemu and copy the typical utilities of dosemu.
-
-
+
+ Create a directory dosemu and copy the typical utilities of dosemu.
+
-Now we modify the copy of config.sys and autoexec.bat to erase everything what
-is not necessary to execute our games as doors, like drivers for cdrom, mouse
-etc... We will clear the keyboard driver 'KEYB XX' and make sure that in the
-path in autoexec.bat to include the directory c:\dosemu. Also load the fossil
-emulator, for example add these two lines:
-
-
+
+ Now we modify the copy of config.sys and autoexec.bat to erase everything
+what is not necessary to execute our games as doors, like drivers for cdrom,
+mouse etc... We will clear the keyboard driver 'KEYB XX' and make sure that
+in the path in autoexec.bat to include the directory c:\dosemu. Also load
+the fossil emulator, for example add these two lines:
+
path %PATH%:c:\dosemu
c:\dosemu\fossil
-
-If there is another fossil, such as bnu or x00 in config.sys or autoexec.bat we
-clear all references to these, we will load them if that is necessary in the
-file that it executes the door when needed, this can be necessary for some
-doors and for other not.
-Now we can erase all the links to the directories who are not necessary, and
-that we do not want that they are visible.
-
-Then edit the file /etc/dosemu.conf and look for the line that begins with
-"$_hdimage =" and change that to:
-
-$_hdimage = "c"
-
-
-Now login as root and you should be able to execute our dos emulator by
-executing '/usr/bin/dosemu.bin'
-
-(to leave dosemu type in exitemu)
-
-
-
-CONFIGURING SUDO
-
-Normally the dos partition is not accessible to the users of the BBS, except
-from within dosemu, and to be able to have access without activating the
-setuid bit of dosemu, we use sudo so that any user of the BBS can execute
-dosemu.bin as root. As root execute visudo to edit the configuration file of
-sudo add the lines:
-
-The first command is a script that takes care of copying the file door.sys to
-the dos partition, the second line is to allow to execute dosemu.bin.
-Any user of group BBS can execute these commandos like root without password
-is asked.
-
-In order to test that this works login as user mbse and execute:
-
-
+
+ If there is another fossil, such as bnu or x00 in config.sys or autoexec.bat
+we clear all references to these, we will load them if that is necessary
+in the file that it executes the door when needed, this can be necessary
+for some doors and for other not. Now we can erase all the links to the directories
+who are not necessary, and that we do not want that they are visible.
+
Then edit the file /etc/dosemu.conf and look for the line that
+begins with "$_hdimage =" and change that to:
+
$_hdimage = "c"
+ Now login as root and you should be able to execute our dos emulator by executing
+'/usr/bin/dosemu.bin'
+
(to leave dosemu type in exitemu)
+
CONFIGURING SUDO
+
Normally the dos partition is not accessible to the users of
+the BBS, except from within dosemu, and to be able to have access without
+activating the setuid bit of dosemu, we use sudo so that any user of the
+BBS can execute dosemu.bin as root. As root execute visudo to edit the configuration
+file of sudo add the lines:
+ The first command is a script that takes care of copying the file door.sys
+to the dos partition, the second line is to allow to execute dosemu.bin. Any
+user of group BBS can execute these commandos like root without password is
+asked.
+
In order to test that this works login as user mbse and execute:
+
+
sudo dosemu.bin
-
-
-
-INSTALLING A DOOR
-
-First we need a pair of scripts. These scripts are installed when you did
-install MBSE. These scripts are needed to execute the doors and are installed
-in /opt/mbse/bin:
-
---- rundoor.sh ---
-
-#!/bin/bash
-#
-# rundoor.sh - Never call this script directly, create a symlink
-# to this file with the name of the door. For example
-# tu run the door ilord do:
-# cd /opt/mbse/bin
-# ln -s rundoor.sh ilord
-#
-# by Redy Rodriguez and Michiel Broek.
-#
-DOOR=`basename $0`
-COMMANDO="\" door $DOOR $*\r\""
-
-/usr/bin/sudo /opt/mbse/bin/bbsdoor.sh $DOOR $1
-/usr/bin/sudo /opt/dosemu/bin/dosemu.bin \
- -F /var/lib/dosemu/global.conf \
- -I "`echo -e serial { com 1 virtual }"\n" keystroke $COMMANDO`"
-reset
-tput reset
-stty sane
-
-
-
---- bbsdoor.sh ---
-#
-# Initialize DOS environment before starting a bbs door.
-# Parameters: $1 = name of the door
-# $2 = the nodenumber for this session
-#
-# by Redy Rodriguez, 22-Oct-2001
-
-if [ "$1" != "" ]; then
- if [ "$2" != "" ]; then
- mkdir -p /dos/c/doors/node$2 >/dev/null 2>&1
- # Copy door.sys to dos partition
- cat ~/door.sys >/dos/c/doors/node$2/door.sys
- # Create .dosemu/disclaimer in user home to avoid warning
- if [ ! -d $HOME/.dosemu ]; then
- mkdir $HOME/.dosemu
- fi
- if [ ! -f $HOME/.dosemu/disclaimer ]; then
- touch $HOME/.dosemu/disclaimer
- fi
- fi
-fi
-
-
-The script rundoor.sh is never called directly, simply create a link with the
-name of the door to this file, this name must be the same as the one of the
-.bat file that starts the door in the doors directory of the dos partition.
-Let me explain this with an example:
-
-I have chosen the door Virtual Sysop, but it could be any other door.
-My experience says to me that not all doors work correctly with a serial port
-in virtual mode. This one is working at Parolas BBS.
-
-Unpack Virtual Sysop in the dos partition, in the directory c:\doors\vsysop.
-Execute as user mbse 'sudo dosemu.bin' and make sure that the door works in
-local mode (these commands are for this door):
-
-cd doors
-cd vsysop
-vsysop -local
-
-
-If everything is correct then create the file c:\doors\vsysop.bat with the
-following contents:
-
-
+
+
+
INSTALLING A DOOR
+
First we need a pair of scripts. These scripts are installed
+when you did install MBSE. These scripts are needed to execute the doors
+and are installed in /opt/mbse/bin:
+
--- rundoor.sh ---
#!/bin/bash # # rundoor.sh - Never call this script directly, create a symlink # to this file with the name of the door. For example # tu run the door ilord do: # cd /opt/mbse/bin # ln -s rundoor.sh ilord # # by Redy Rodriguez and Michiel Broek. # DOOR=`basename $0` COMMANDO="\" door $DOOR $*\r\""
--- bbsdoor.sh --- # # Initialize DOS environment before starting a bbs door. # Parameters: $1 = name of the door # $2 = the nodenumber for this session # # by Redy Rodriguez, 22-Oct-2001
if [ "$1" != "" ]; then if [ "$2" != "" ]; then mkdir -p /dos/c/doors/node$2 >/dev/null 2>&1 # Copy door.sys to dos partition cat ~/door.sys >/dos/c/doors/node$2/door.sys # Create .dosemu/disclaimer in user home to avoid warning if [ ! -d $HOME/.dosemu ]; then mkdir $HOME/.dosemu fi if [ ! -f $HOME/.dosemu/disclaimer ]; then touch $HOME/.dosemu/disclaimer fi fi fi
+ The script rundoor.sh is never called directly, simply create a link with
+the name of the door to this file, this name must be the same as the one
+of the .bat file that starts the door in the doors directory of the dos partition.
+Let me explain this with an example:
+
I have chosen the door Virtual Sysop, but it could be any other
+door. My experience says to me that not all doors work correctly with a serial
+port in virtual mode. This one is working at Parolas BBS.
+
Unpack Virtual Sysop in the dos partition, in the directory c:\doors\vsysop.
+Execute as user mbse 'sudo dosemu.bin' and make sure that the door works
+in local mode (these commands are for this door):
+
cd doors cd vsysop vsysop -local
+ If everything is correct then create the file c:\doors\vsysop.bat with the
+ following contents:
+
--- vsysop.bat ---
@echo off
C:\COMUNIC\X00\X00 E B,0,57600
@@ -733,33 +763,26 @@ deltree /y c:\doors\node%1
C:\COMUNIC\X00\X00
cd ..
-
-Before passing the control to dosemu, the file door.sys will be copied to
-c:\doors\node???? where the ???? is the node number from which the door is
-invoked (to allow that several users can execute the door at the same time).
-This nodenumber also is passed as the first parameters to the .bat file, this
-is to indicate to which directory to copy the door.sys file.
-
-The Virtual Sysop door supports door.sys and that is the only dropfile that
-is generated by mbsebbs and that is supported by most of the doors.
-If you need another format you must use a converter to change the format of
-the dropfile.
-
-I use the fossil X00, I have it installed in C:\COMUNIC\X00 and this door works
-for me correctly with these parameters, it is alos possible that it works
-without X00 or that you can load another fossil.
-
-Now create a link to rundoor.sh in /opt/mbse/bin called vsysop. The name must
-be the same one that the name of the .bat file created in the dos partition,
-but without the extension bat.
-
-Now we execute mbsetup and enter the menu setup to add an entrance like this
-(It puts option 16 to Yes):
-
-
+
+ Before passing the control to dosemu, the file door.sys will be copied to
+c:\doors\node???? where the ???? is the node number from which the door is
+invoked (to allow that several users can execute the door at the same time).
+This nodenumber also is passed as the first parameters to the .bat file,
+this is to indicate to which directory to copy the door.sys file.
+
The Virtual Sysop door supports door.sys and that is the only
+dropfile that is generated by mbsebbs and that is supported by most of the
+doors. If you need another format you must use a converter to change the
+format of the dropfile.
+
I use the fossil X00, I have it installed in C:\COMUNIC\X00 and
+this door works for me correctly with these parameters, it is alos possible
+that it works without X00 or that you can load another fossil.
+
Now create a link to rundoor.sh in /opt/mbse/bin called vsysop.
+The name must be the same one that the name of the .bat file created in the
+dos partition, but without the extension bat.
+ Now we execute mbsetup and enter the menu setup to add an entrance like
+this (It puts option 16 to Yes):
+
8.3. EDIT MENU ITEM
1. Sel. key V
@@ -776,188 +799,168 @@ Now we execute mbsetup and enter the menu setup to add an entrance like this
11. Hi-colors Bright display color 15. Run nosuid Yes
12. Autoexec No 16. No Prompt Yes
-
-Dosemu still exhibits some file locking behaviour and this needs to be
-overcome, especially if you are running multinode door games. The
-following information was written by Bob Newell of Chung Kuo BBS (telnet
-chungkuo.org) and I reiterate it here.
-
-There is an issue in that Linux file locking does not map precisely to
-DOS file locking. You need to patch DOSEMU and build a special version
-to deal with this problem. Find the file "dosext/mfs/mfs.c" in your
-DOSEMU source tree. Locate the following lines:
-
-case DENY_ANY:
- fl.l_type = F_RDLCK;
-
-Change the second line to
- fl.l_type = !writing ? F_RDLCK : F_WRLCK;
-
-
-and build a new version of DOSEMU.
-
-To solve a problem of slow screen painting, locate "base/async/int.c"
-in your source tree. Locate
-
-case 0x2C:
-
-and just below, comment out or delete the line
-
-usleep(INT2F_IDLE_USECS);
-
-
-With most BBS games you will need 2 directories in your dos filesystem
-area. One for the inbound packets and one for netmail messages door
-games produce to send outbound packets.
-
-The easiest way to solve this is by creating symlinks from your MBSE
-directories into the directory where your dos doors live (c:\doors). The
-2 directories you wish to link are /opt/mbse/var/inbound and
-/opt/mbse/var/msgs - link them into your dos directories doors directory
-with the same names ie: "inbound" and "msgs". Now according to dosemu
-you will have a c:\doors\inbound and a c:\doors\msgs
-
-For my example I will use the InterBBS dos door game called Barren
-Realms Elite (BRE for short).
-
-3a. I install Bre in c:\doors\bre and setup the necessary files for its
-execution as a dos door from MBSE as per the dos doors faq.
-
-3b. I tell Bre (in its BBS.CFG) that the path for inbound packets is
-c:\doors\inbound and the netmail path is c:\doors\msgs
-Bre will now automatically process all inbound packets it finds in the
-inbound directory for itself. It needs no assistance as it merely
-searches for the correct filename in the directory.
-
-3c. We need a script to process the Bre outbound packets and add them to
-MBSE's outbound path so they are sent. A perl script on how to do this
-follows (with comments ).
-
-This script should be owned by user "mbse" and have the permissions
-(chmod 755) -rwxr-xr-x. It is best kept in /opt/mbse/bin with your dos
-game executing scripts. I call this script "dos_poll"
-
-------------------------------------------------------------------------
-#!/usr/bin/perl -U
-use File::Basename;
-
-
-# Define the variable for the outbound file that this script
-# must create. See Note 1.
-$bre48_file = "/opt/mbse/var/bso/outbound/028003ba.flo";
-# Define the linux path to Bre's outbound directory
-$bre48_path = "/opt/mbse/dos/doors/bre48/OUTBOUND";
-# Define the linux path to the "msgs" directory
-$msg_path = "/opt/mbse/var/msgs";
-
- opendir(DIR, "$bre48_path") || die;
- @dirlist = readdir(DIR);
- closedir(DIR);
-
- foreach $filename (@dirlist){
- ($filenameOnly, $pathname, $fileExtension) = fileparse($filename, '\..*');
-
-# Below '048b0201' is the packet name Bre creates. You can find out what
-# your packet name is by running BRE PLANETARY and then checking inside
-# the Bre OUTBOUND directory - note no ext on name.
-
- if($filenameOnly eq "048b0201") {
- $bre48 = "^$bre48_path/$filename";
- open(FILE, ">>$bre48_file");
- print FILE "$bre48\n";
- close(FILE);
- }
- chmod 0664, "$bre48_file";
- }
-
- opendir(DIR, "$msg_path") || die;
- @dirlist1 = readdir(DIR);
- closedir(DIR);
-
- foreach $filename (@dirlist1){
- ($filenameOnly, $pathname, $fileExtension) = fileparse($filename, '\..*');
- if($fileExtension eq ".msg") {
- unlink "$msg_path/$filename";
- }
- }
-system "touch /opt/mbse/sema/scanout";
-
-------------------------------------------------------------------------
-
-
-Note 1. To find out what the outbound file is simply send a netmail
-attach via MBSE to your uplink system for the Bre game. MBSE will create
-a file in your outbound directory as a series of numbers with the
-extension .flo (or hlo). Inside this file will merely be the path to the
-file attached, but it is the name of the flo file that we require. No
-matter what file you attach or when you attach it, the outbound flo file
-will always have the same name as it represents the node number it is
-being sent to. Thus if you were file attaching to 3:640/954 your flo
-file would be "028003ba.flo" as in the example. Once you find out the
-filename substitute it in the script above.
-
-What the above script does:
-
-The perl script merely reads the Bre outbound directory and looks for
-files with the name of the that you tell it (sample one is 048b0201).
-The script removes the extension from the filenames to get a match.
-If it finds a match it creates a file, the "$bre48_file", which is the
-.flo you specified in the correct outbound directory. Inside this file
-it merely gives the path to the Bre outbound attach file and adds a ^
-before it (so MBSE deletes it after sending).
-
-Then it goes into your "msgs" directory and deletes everything in there.
-It does not use the netmails written by the games at all, it just
-deletes them to stop them filling up your hard drive.
-
-Then it tells MBSE to scan the outbound. If it created a flo file and
-that system is a direct or crash link MBSE will poll and send the file
-straight away.
-
-If you have more InterBBS games the procedure is the same, just copy and
-edit the first part (relating to BRE) and add new variables for other
-games. The script only needs to clear the msgs directory once and to
-scan the outbound once. You only need one script to service a multitude
-of games.
-
-Ok, so you can setup doors, run inbound and outbound for interbbs games.
-So how do you do maintenance?
-
-Again by scripts. Again I will use BRE as an example. First I create a
-maintenance batch file in my C: root directory. I have called it
-maint.bat and for the bre game it looks like this:
-
Written by: Rick Van Ruth, sysop of Vampyre's Heaven BBS 3:640/954
+Dosemu still exhibits some file locking behaviour and this needs to be overcome,
+especially if you are running multinode door games. The following information
+was supplied by Bob Newell of Chung Kuo BBS (telnet chungkuo.org) and I reiterate
+it here.
+
There is an issue in that Linux file locking does not map precisely
+to DOS file locking. You need to patch DOSEMU and build a special version
+ to deal with this problem. Find the file "dosext/mfs/mfs.c" in your DOSEMU
+source tree. Locate the following lines:
+
case DENY_ANY: fl.l_type = F_RDLCK;
Change the second line to fl.l_type = !writing ? F_RDLCK : F_WRLCK;
+ and build a new version of DOSEMU.
+
To solve a problem of slow screen painting, locate "base/async/int.c"
+ in your source tree. Locate
+
case 0x2C:
and just below, comment out or delete the line
usleep(INT2F_IDLE_USECS);
+ and rebuild your DOSEMU.
+
+It is recommended to use both tips above as it will not harm any dos door
+games.
+
Written by: Rick Van Ruth, sysop of Vampyre's Heaven BBS 3:640/954
+There are 2 methods for providing InterBBS setup. If your system merely connects
+to one host for your games packets you need only perform a few simple steps
+to have it working. If your system is a Host for InterBBS games you will
+also need to add a script to separate different packets for different downlink
+systems.
+
+Common to Both Methods:
+With most BBS games you will need 2 directories in your dos filesystem area.
+One for the inbound packets and one for netmail messages door games produce
+to send outbound packets.
+
The easiest way to solve this is by creating symlinks from your
+MBSE directories into the directory where your dos doors live (c:\doors).
+The 2 directories you wish to link are /opt/mbse/var/inbound and /opt/mbse/var/msgs
+- link them into your dos directories doors directory with the same names
+ie: "inbound" and "msgs". Now according to dosemu you will have a c:\doors\inbound
+and a c:\doors\msgs. We do not actually use the "msgs" directory for anything
+other than a place to tell games where to write its netmails to. These "netmails"
+are subsequently deleted from the system, but the games need to be able to
+write them there.
+
1. The Easy Way - Single Host System:
+
+
1A.First of all you will realise that door games running under
+dosemu usually write files as owner root, chmod 0644. This is not good for
+MBSE to transfer these files as it does not have permission to act on the
+files. In order to force dosemu to write games files so that MBSE can act
+upon them we need to alter /etc/sudoers and change the umask for root running
+under sudo. To do this open /etc/sudoers (you must be root to edit this file)
+and add the following line at the top of the file before the specifications:
+
Defaults umask=0000
+
This will allow dosemu to write files chmod 0666 (read/write everybody)
+and MBSE will be able to manipulate them.
+
+
For my example I will use the InterBBS dos door game called Barren
+Realms Elite (BRE for short).
+
1B. Install Bre in c:\doors\bre and setup the necessary files
+for its execution as a dos door from MBSE as per the dos doors faq.
+
1C. Tell Bre (in its BBS.CFG) that the path for inbound packets
+is c:\doors\inbound and the netmail path is c:\doors\msgs Bre will now automatically
+process all inbound packets it finds in the inbound directory for itself.
+It needs no assistance as it merely searches for the correct filename in
+the directory.
+
+
1D. We need to link Bre's outbound path to our host nodes MBSE
+mailbox for automatic transfer of games packets. First make sure you have
+added an "outbox" for your uplink node in the nodes setup in MBSE - Section
+7, Select Uplink, Menu 1, Section 2 "outbox dir". eg: if your uplink is 3:640/954
+then MBSE will default to creating /opt/mbse/var/boxes/node3_640_954 as the
+outbox (I will use this as an example). Note the flavour of your uplinks
+node connection will apply to the outbox as well. Thus if that particular
+node is set crashmail then anything you put in the outbox will also be sent
+crashmail.
+
Next go to your Bre game directory. You will notice Bre has an
+OUTBOUND directory, this is where it places all its game packets that are
+to be sent to the uplink. We need to delete this directory and instead create
+a symlink to the node outbox instead. If Bre is in c:\doors\bre then the
+symlink command will be:
Alter the above depending on where your linux path to your dos
+is, also remember linux is case sensitive! Note you can also make as many
+synlinks as you like to the nodes outbox, so if you have 2 or 3 different
+games you send to that node you can link the outbox to each games outbound
+directory. Also if you have different games to different host nodes just
+link the game outbound directories to the outboxes of each node.
+
Thats it. The system will now process inbound and outbound packets
+automatically. You will however need to delete the netmails in the msgs directory
+- I have included this in the Door game maintenance section further on.
+
2. The Hard Way - Multiple Host System
+
Follow steps 1A, 1B, 1C above, the change occurs for 1D (below).
+
+
1D. We need a script to process the Bre outbound packets and
+add them to MBSE's node outboxes path so they are sent. A script on how to
+do this follows (with comments ). First remember to create your outboxes
+for each node that you transfer games packets to. I will use 3:640/954 as
+above and 1:123/456 for this example of 2 systems linked to the one Bre game.
+
+
This script should be owned by user "mbse" and have the permissions
+(chmod 755) -rwxr-xr-x. It is best kept in /opt/mbse/bin with your dos game
+executing scripts. I call this script "dos_poll"
+
------------------------------------------------------------------------ #!/usr/bin/perl -U use File::Basename; use File::Copy;
# Define the variables for the outboxes for our links $node1 = "/opt/mbse/var/boxes/node3_640_954"; $node2 = "/opt/mbse/var/boxes/node1_123_456"; # Define the linux path to Bre's outbound directory $bre_path = "/opt/mbse/dos/doors/bre/OUTBOUND";
# '048b0201' is the packet name Bre creates. You can find out what # your packet name is by running BRE PLANETARY and then checking inside # the Bre OUTBOUND directory - note no ext on name. You should also check # your nodes dat for which is which 048b0201 means from system 2 to system 1 # so you would be system 2 in the nodes dat and 1 would be 3:640/954 # 048b0203 is obviously to system 3 in the nodes dat - 1:/123/456 in our # example here
Written by: Rick Van Ruth, sysop of Vampyre's Heaven BBS 3:640/954
+Ok, so you can setup doors, run inbound and outbound for interbbs games. So
+how do you do maintenance?
+ Again by scripts. Again I will use BRE as an example. First I create a maintenance
+batch file in my C: root directory. I have called it maint.bat and for the
+bre game it looks like this:
+
-if you are familiar with Bre you will know this to be a standard sort of
-maintenance except for the "exitemu" at the end. That is there because
-we are going to use a script to start dosemu and call the maint.bat - so
-afterwards we need it to exit dosemu.
-
-Now a maintenance script to be called from your cron or whatever else
-you are using to execute events on your system. I call this script
-"dos_maint" and it also lives in /opt/mbse/bin
-
-
+
+ if you are familiar with Bre you will know this to be a standard sort of
+maintenance except for the "exitemu" at the end. That is there because we
+are going to use a script to start dosemu and call the maint.bat - so afterwards
+we need it to exit dosemu.
+ Now a maintenance script to be called from your cron or whatever else you
+are using to execute events on your system. I call this script "dos_maint"
+and it also lives in /opt/mbse/bin
+
+
#/opt/mbse/bin/dos_poll # Uncomment this line if you are using the Multiple host script --------------------------------------------------------------------------------------------------
-
-/opt/mbse/bin/dos_poll
-
-
-You will notice this script starts dosemu and calls maint.bat, and then
-when its finished there it calls the dos_poll script discussed earlier.
-Please note the second line is all ONE line, it has most probably
-wrapped here.
-
-You will notice that the script calls dosemu and not dosemu.bin, this is
-because we need to tell dosemu to open a dumb terminal and not display
-to a console or screen. By use of the redirection we redirect the normal
-console output to a file, here I have used /opt/mbse/log/dos/log as that
-is where all of MBSE's other logs reside.
-
-Once "dos_maint" is run via the cron it will run maintenance on your dos
-doors, process inbound/outbound interBBS game packets and get MBSE to
-poll to send packets. Thats about all ther is to do :)
-
Go Back
-
-
-