> # MBSE BBS FAQ and Howto.

> ##### Last updated 11-May-2002

>       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.

> 1. Installation
> 1. Why do I have to install MBSE in the /opt directory?
> 2. What other operating systems will MBSE run on?
> 3. Will MBSE ever be ported to DOS/Windows or OS/2?
> 4. What does the quest switch in the bbs user setup mean?
> 5. How do I monitor as the things happen?
> 6. How do I start mbsebbs from inetd?

> 2. Fidonet Setup
> 1. The nodelist compiler crashes, why?
> 2. What is the purpose of the "Comment" line in the tic area setup?
> 3. How do I poll a node?
> 4. I created a filerequest but mbcico doesn't call out.
> 5. Does MBSE support fidonet via ftp feeds?

> 3. Internet Setup
> 1. Posting newsmessages to the newsserver fails.
> 2. FTP fidonet feeds how-to.

> 4. BBS Setup
> 1. How do I run DOS doors under MBSE BBS?
> 2. How do I to set up MBSE for ISDN?
> 3. How do I use GoldED together with MBSE?
> Go Back

> ### 1. Installation.

> Q 1.1 | 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.

> Q 1.2 | What other operating systems will MBSE run on?
> A 1.2 | 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.

> Q 1.3 | Will MBSE BBS ever be ported to DOS/Windows or OS/2?
> A 1.3 | No.

> Q 1.4 | What does the guest switch in BBS user setup mean?
> A 1.4 | Nothing yet.

> Q 1.5 | How do I monitor as the things happen?
> A 1.5 | tail -f /opt/mbse/log/system.log or start mbmon.

> Q 1.6 | How to start mbsebbs from inetd?
> A 1.6 | This is described in the documentation of the mblogin program.

> ### 2. Fidonet setup.

> Q 2.1 | The nodelist compiler crashes, why?
> A 2.1 | 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.

> Q 2.2 | What is the purpose of the "Comment" line in the tic area setup?
> A 2.2 | The downlinks will see this when receiving FileMgr replies. It is meant only as a description for the filearea.

> Q 2.3 | How do I poll a node?
> A 2.3 | mbout poll f2802.n280.z2

> Q 2.4 | I created a filerequest but mbcico doesn't call out.
> A 2.4 | You need to add a poll for that node to do the call.

> Q 2.5 | Does MBSE support fidonet via ftp transfers?
> A 2.5 | 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.

> ### 3. Internet setup.

> Q 3.1 | Posting newsmessages to the newsserver fails.
> A 3.1 | Check if you need the "mode reader" command for the newsserver. Set this flag in mbsetup 1.15.5

> Q 3.2 | How do I configure MBSE for my ftp filenet feeds?
> 1. 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:
>        parseflo <enter>
>        finalflo.sh /home/fido/jdoe/out <enter>
>    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:
>        cp /home/ftp/pub/filegate/fg_worf/filegate.zxx $1
>        mv /opt/mbse/mail/outbound/00000063/dooqi39k.tic $1
>        cp /home/ftp/pub/filegate/ss_areas/ss_areas.zip $1
>        mv /opt/mbse/mail/outbound/00000063/dooqi39l.tic $1
>        cp /home/ftp/pub/filebone/admin/backbone/backbone.z1b $1
>        mv /opt/mbse/mail/outbound/00000063/dooqi39m.tic $1
> 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

> ### 4. BBS setup.

> Q 4.1 | How do I run DOS doors under MBSE BBS?
> A 4.1 |
>     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:
>     ./install_systemwide -fd dosemu-freedos-bin-1.02.tgz
> 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.
>     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.
>     mkdir dosemu
>     cp /usr/src/dosemu-1.02/1.0.2.0/commands/* 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:
>     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:
>     %bbs    ALL=NOPASSWD:/opt/mbse/bin/bbsdoor.sh
>     %bbs    ALL=NOPASSWD:/opt/dosemu/bin/dosemu.bin
> 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:
>     --- vsysop.bat ---
>     @echo off
>     C:\COMUNIC\X00\X00 E B,0,57600
>     cd vsysop
>     vsysop -D c:\doors\node%1\door.sys -BBSNAME PAROLAS
>     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.
>     ln -s /opt/mbse/bin/rundoor.sh /opt/mbse/bin/vsysop
> 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
>      2.  Type nr.  7         Run external program in shell
>      3.  Opt. data /opt/mbse/bin/vsysop /N
>                    1234567890123456789012345678901234567890123456789012345678901234
>      4.  Display
>      5.  Security  0     --------------------------------
>      6.  Min. age  0
>      7.  Max. lvl  0
>      8.  Password  <null>                    13. No door.sys No
>      9.  Credit    0                         13. Y2K style   No
>      10. Lo-colors Normal display color      14. Use Comport Yes
>      11. Hi-colors Bright display color      15. Run nosuid  Yes
>      12. Autoexec  No                        16. No Prompt   Yes
> And that is everything...

> Q 4.2 | How to set up MBSE for ISDN.
> A 4.2 | Contributed by: J. Beekhuizen, 2:280/1018 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.
>     # ISDN lines
>     I1:23:respawn:/usr/local/sbin/mgetty -x 4 -i /opt/mbse/etc/issue ttyI0
>     I2:23:respawn:/usr/local/sbin/mgetty -x 4 -i /opt/mbse/etc/issue 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
>     Init string
>     OK string    OK
>     Hangup       \d\p\p\p+++\d\p\p\pATH0\r
>     Info command ATI2\r
>     Dial command ATD\T\r
>     Connect      CONNECT 64000
>     Connect      CONNECT
>     [...]
>     Reset cmd    ATZ\r
>     Error string BUSY
>     Error string NO CARRIER
>     Error string NO DIALTONE
>     Error string NO ANSWER
>     Error string RING\r
>     Error string ERROR
>     Error string
>     Error string
>     Error string
>     Error string
>     Cost offset  0
>     EMSI speed   28800                   ! not relevant for ISDN
>     Strip dashes No
>     Available    Yes
> And from #6 "Edit TTY lines info" the ISDN lines
>     TTY name     ISDN Line 1
>     Device name  ttyI0
>     Phone or DNS 31-71-4015437
>     Line speed   64 kbits
>     Fido flags   CM,XA,MO,X75
>     Equipment    ISDN
>     Available    Yes
>     Auth. log    No
>     Honor ZMH    Yes
>     Callout      Yes
>     Modem type   ISDN Linux
>     Locked speed 0                                 ! not relevant for ISDN
>     EMSI name    The Wizard's ISDN line 1

>     TTY name     ISDN Line 2
>     Device name  ttyI1
>     Phone or DNS 31-71-4017198
>     Line speed   64 kbits
>     Fido flags   CM,XA,MO,X75
>     Equipment    ISDN
>     Available    Yes
>     Auth. log    No
>     Honor ZMH    Yes
>     Callout      Yes
>     Modem type   ISDN Linux
>     Locked speed 0
>     EMSI name    The Wizard's ISDN line 2
> T-t-that's all folks :))

> Q 4.3 | How do I use GoldED together with MBSE?
> A 4.3 | 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
>     ;
>     INTERNETADDRESS Michiel_Broek@f2802.n280.z2.fidonet.org
>     INTERNETGATE UUCP 2:292/875
>     ;
>     ;
>     OUTBOUNDPATH /opt/mbse/var/bso/outbound
>     REPLYLINK chain
>     STYLECODES yes
>     ;
>     ;
>     ; MESSAGE READER
>     ;
>     DISPMSGSIZE KBYTES
>     DISPATTACHSIZE KBYTES
>     DISPLOCALHIGH YES
>     DISPPAGEBAR YES
>     VIEWHIDDEN YES
>     VIEWKLUDGE NO
>     VIEWQUOTE YES
>     ;
>     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.