Last update 29-Dec-2001

 

MBSE BBS Basic Installation

Introduction.

Before you compile and install MBSE BBS you must first setup the basic environment. If you don't do this, things will fail.

 

Step 1: planning the filesystems.

MBSE BBS is default installed in /opt/mbse. The default filesystem layout looks like this:

/opt/mbse                      Default MBSE_ROOT
/opt/mbse/bin                  Binaries
/opt/mbse/doc                  Generated sitedocs
/opt/mbse/dutch/macro          N/A
/opt/mbse/dutch/menus          Dutch menu files
/opt/mbse/dutch/txtfiles       Dutch ANSI files
/opt/mbse/english/macro        Default english macros, not yet.
/opt/mbse/english/menus        Default english menus
/opt/mbse/english/txtfiles     Default english ANSI files
/opt/mbse/etc                  System configuration files
/opt/mbse/fdb                  Files database
/opt/mbse/ftp                  Default FTP root
/opt/mbse/galego/macro         N/A
/opt/mbse/galego/menus         Galego menu files
/opt/mbse/galego/txtfiles      Galego ANSI files
/opt/mbse/home                 Users homedirectories
/opt/mbse/home/bbs             Newuser account
/opt/mbse/html                 HTML documentation
/opt/mbse/italian/macro        N/A
/opt/mbse/italian/menus        Italian menu files
/opt/mbse/italian/txtfiles     Italian ANSI files
/opt/mbse/log                  MBSE BBS logfiles
/opt/mbse/magic                Magic filerequest names
/opt/mbse/sema                 Semafore files
/opt/mbse/spanish/macro        N/A
/opt/mbse/spanish/menus        Spanish menu files
/opt/mbse/spanish/txtfiles     Spanish ANSI files
/opt/mbse/tmp                  Temp directory
/opt/mbse/tmp/arc              Temp archiver directory
/opt/mbse/var                  Var root
/opt/mbse/var/badtic           Bad TIC files
/opt/mbse/var/bso              Binkley Style Outbound directory
/opt/mbse/var/bso/inbound      Protected inbound directory
/opt/mbse/var/bso/outbound     Default outbound directory
/opt/mbse/var/bso/unknown      Unprotected inbound directory
/opt/mbse/var/mail             JAM messagebase root
/opt/mbse/var/mail/badmail     Bad echomail
/opt/mbse/var/mail/dupmail     Duplicate echomail
/opt/mbse/var/msgs             *.msgs netmail directory (not yet in use).
/opt/mbse/var/nodelist         Nodelists
/opt/mbse/var/ticqueue         Queue for TIC files

Don't use UMSDOS or SAMBA filesystems for the bbs, stick by the standard Linux filesystems (ext2 or reiserfs) or ufs if you use FreeBSD. If you intent to make your bbs also accessible by FTP and WWW you must create the directory structure under the ftp user behind the pub directory. Read the ftp server 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 this error.

 

Step 2: Running the installation script.

If you are upgrading, proceed with step 4. If not, follow the next steps very carefully! 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 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 extension .mbse To run the installation script you need the archive mbbsebbs-0.33.nn.tar.gz. Unpack this archive on your system, in /tmp will do fine: 

cd /tmp
tar xfvz /path/to/the/mbsebbs-0.33.nn.tar.gz
To start the script type: 
cd mbsebbs-0.33.nn
bash ./SETUP.sh
Yes, use bash as shell here. On some systems root doesn't use bash as login shell, calling the script with bash forces the use of bash. The script does the following:
  1. Create the group bbs
  2. Create the user mbse
  3. Create a .profile for user mbse
  4. Create and set owner of directory tree under /opt/mbse
Then the script will ask you to give a password for user mbse 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 easy to guess of course. The script will then continue again:
  1. The user bbs is added.
  2. The password will be removed from user bbs This action 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.
  3. If they don't exist in the file /etc/services the services fido, tfido and binkp will be added.
  4. If they don't exist in the file /etc/inetd.conf the internet protocols for the mailer will be added. The inetd is restarted to activate the changes.

 

Step 3: Check the basic installation

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 the backups of the system files that are changed are in /etc with the extension .mbse i.e: those were the original files. If everythings is allright, then remove the directory /tmp/mbsebbs-0.33.nn: 

cd /tmp
rm -Rf mbsebbs-0.33.nn

 

Step 4: Install the basic packages.

Login as user mbse. Yes, very important, login as user mbse. While in the home directory unpack the distribution archives: 

tar xfvz /path/to/mbsebbs-0.33.nn.tar.gz
You now have the subdirectory with sources in the right place. Next build the binaries and install them using the folowing commands: 
cd ~/mbsebbs-0.33.nn
./configure
make
su        important, do not use "su -"
password: enter root password here
make install
exit
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 time installation, example menus, textfiles and some databases are installed. If they already exist on your systems (when you do an upgrade) they will not be installed again.

Now you must start the mbtask daemon by hand by typing /opt/mbse/bin/mbtask. Check the file /opt/mbse/log/mbtask.log for startup problems. You may notice that the program mbcico is started everytime, this is not a problem, it simply doesn't work right now because you haven't configured anything yet. The first time mbtask is started on your system it will create a lot of new configuration files with default settings.

 

Step 5: (RedHat) startup problems.

From RedHat 6.1 (not the older versions) the behaviour of the su is changed. This may be true for other distributions since the end of 1999 and for Mandrake as well. The file /etc/rc.d/init.d/mbsed that is created by the setup script is different then before. The new command is su - instead of simply su. It might be 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.

 

Step 6: ready.

Now the basic environment is finished, the next thing is to install the scripts, examples and configuration.

 

Back to Index Back to Index