linux windows nt amateur packet radio
This mini-HOWTO covers the installation and use of
@@ -158,7 +158,7 @@ LinFBB ...
-How to install LinFBB beside WinFBB
+How to install LinFBB in addition to existing WinFBB
Notice: Folks, you see, at my place, I have a
@@ -542,7 +542,151 @@ radio BBS, using Protus type of c_filter:
Many combinations are possible. You could
even password protect your own FBB console!
-
+
+
+
+How to install daemon version of LinFBB
+
+
+Notice: You see, folks, that I keep trying to get
+as many as possible versions of this great
+software (Jean-Paul, F6FBB, must be very proud after
+reading these words now). What I think when mention
+"as many as possible versions" means that we have
+learned how to get both WinFBB and LinFBB for X11 on
+the same computer. But, that's not all. There is a
+variety of daemon versions of LinFBB. In this section
+we are going to discuss how to *add* a daemon FBB
+to the existing two: X11 LinFBB and WinFBB!
+
+
+
+
+- Well, many amateurs suggested me to install some
+ packages that looked to me not too much needed
+ for LinFBB itself to be run. Anyway, I have installed
+ those packages before the installation
+ of LinFBB daemon version itself:
+
+
+
+ libax25.rpm
+ ax25apps.rpm
+ ax25tool.rpm
+
+
+
+- Now it is the right time to install fbbsrv.rpm
+ package. The archive is composed to make its
+ own directories, as "base" directories.
+
+
+- A file fbb.conf, that serves as the
+ replacement for init.srv, is located in the
+ following location: /etc/ax25/fbb.conf
+
+
+- Unless you are going to install daemon-only
+ system, you should make a backup of the
+ following files:
+
+
+
+ dirmes.sys
+ etat.sys
+ heard.bin
+ inf.sys
+ statis.dat
+ tpstat.sys
+
+
+
+- Now you have to edit /etc/ax25/fbb.conf
+ and change some paths in case you already
+ have X11 LinFBB installed on a different
+ path. Here you have some examples that cover
+ my particular situation...
+
+
+- Directory of data files, instead of /var/ax25/fbb,
+ should be /mnt/win/fbb/system
+
+
+- Directory of config files, instead of /etc/ax25/fbb,
+ should be /mnt/win/fbb/system
+
+
+- Directory of message files, instead of /var/ax25/fbb/mail,
+ should be /mnt/win/fbb/mail
+
+
+- Directory of compressed files, instead of /var/ax25/fbb/binmail,
+ should be /mnt/win/fbb/binmail
+
+
+- Directory of users, instead of .../home/fbbdos/...,
+ should be .../mnt/win/fbb/users... (<-- case you
+ don't mind that both your WinFBB and LinFBB users handle
+ the same location for users' files)
+
+
+- Directory of YAPP files, instead of /home/fbbdos/yapp,
+ should be /mnt/win/fbb/users/yapp (<-- the same
+ reason as above)
+
+
+- Directory of documentation files, instead of
+ /var/ax25/fbb/docs, should be /mnt/win/fbb/docs
+
+
+- Directory of pg programs, instead of /usr/local/pg,
+ should be /mnt/win/fbb/pg
+
+
+- Path and filename for import file, instead of
+ C:\FBB\MAIL.IN should be /mnt/win/fbb/mail.in
+
+
+- Now you have to edit /usr/sbin/xfbb.sh
+ and change some paths in case you already
+ have running X11 version of LinFBB on a different
+ path. Here you have an example that cover
+ my particular situation...
+
+
+- Base directory of XFBB software, instead of
+ /var/ax25/fbb, should be /mnt/win/fbb
+
+
+- So far - so good. Now it is the time to start
+ LinFBB daemon. The command for that is in the
+ location: /usr/sbin/xfbb.sh and it may
+ be executed within an xterm. If
+ everything is OK, you should get several
+ system messages on your screen, ending with
+ something like:
+
+
+
+ xfbbC/X server running ...
+ xfbbd ready and running ...
+
+
+
+- Well, daemon itself can't be used to access the
+ BBS so it is needed to activate a client
+ that is /usr/sbin/xfbbC. It has a couple
+ of parameters (a callsign/password pairs that are
+ stored in /fbb/passwd.sys). Note that xfbbC can
+ also be activated within another xterm.
+
+
+- When you finish your xfbbC session, it is suitable
+ to use the same xterm to eventually stop
+ daemon. First of all, using the command ps ax
+ you should locate PIDs of daemon, that you may
+ kill after that.
+
FURTHER INFORMATION
diff --git a/LDP/howto/linuxdoc/Remote-X-Apps.sgml b/LDP/howto/linuxdoc/Remote-X-Apps.sgml
index 51433fa8..78edb44f 100644
--- a/LDP/howto/linuxdoc/Remote-X-Apps.sgml
+++ b/LDP/howto/linuxdoc/Remote-X-Apps.sgml
@@ -8,7 +8,7 @@
name="Vincent Zweije">,
-13 November 2000
+16 November 2000
@@ -55,12 +55,12 @@ name="http://sunsite.unc.edu/LDP/HOWTO/mini/Remote-X-Apps">. Linux
url="http://sunsite.unc.edu/LDP/HOWTO/HOWTO-INDEX-2.html"
name="sunsite.unc.edu">.
-This is version 0.7.0. No guarantees, only good intentions. I'm open
+This is version 0.7.2. No guarantees, only good intentions. I'm open
to suggestions, ideas, additions, useful pointers, (typo) corrections,
etc... I want this to remain a simple readable document, though, in the
best-meant HOWTO style. Flames to /dev/null.
-Contents last updated on 13 November 2000 by
Related Reading
@@ -709,12 +709,42 @@ and 250M of disk space. Oh, and a network connection, of course.
It doesn't even have user home directories.
-For some related reading, have a look at
-the Xterminal mini-HOWTO, for example at .
-It is currently unmaintained, but it might contain some useful information
-for you.
+For some related reading, have a look at:
+
+
+
+-
+
+ The ).
+ This document is an extensive description of what is possible with
+ XDMCP and xdm, applied for building X terminals. Definitely have
+ a look at this.
+
+
-
+
+ The ).
+ This document describes the steps necessary to set up xdm for use
+ with remote X servers, such as from X terminals. The setup of the
+ X server in such a situation is described less extensively.
+
+
-
+
+ The ).
+ It is currently unmaintained, but it might contain some useful
+ information for you.
+
+
+
+
+Contrasted to the above documents, this document (the Remote X Apps
+mini-HOWTO) limits itself to a short description of XDMCP, but puts more
+emphasis on the security issues involved.
Once More, a Little Theory First