LDP
/
LDP
mirror of https://github.com/tLDP/LDP
0
1
Fork 0
Code Releases Activity

updated

This commit is contained in:
gferg 2000-11-16 17:48:25 +00:00
parent 114319d10a
commit e0b2c6feab
2 changed files with 186 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

150
LDP/howto/linuxdoc/FBB.sgml
View File

@ -6,7 +6,7 @@
<title>FBB Packet-radio BBS mini-HOWTO
<author>Miroslav "Misko" Skoric, YT7MPB,
<tt/m.skoric@eunet.yu/
<date>v1.4, 15 November 2000
<date>v1.5, 15 November 2000
<abstract>
<nidx>linux windows nt amateur packet radio</nidx>
This mini-HOWTO covers the installation and use of
@ -158,7 +158,7 @@ LinFBB ...
</itemize>
<p>
<sect1>How to install LinFBB beside WinFBB
<sect1>How to install LinFBB in addition to existing WinFBB
<p>
<em>Notice: Folks, you see, at my place, I have a
@ -542,7 +542,151 @@ radio BBS, using Protus type of <em>c_filter</em>:
Many combinations are possible. You could
even password protect your own FBB console!
</itemize>
</itemize>
<p>
<sect1>How to install daemon version of LinFBB
<p>
<em>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!</em>
<p>
<itemize>
<item>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 <em>before</em> the installation
of LinFBB daemon version itself:
<p>
<tscreen><verb>
libax25.rpm
ax25apps.rpm
ax25tool.rpm
</verb></tscreen>
<p>
<item>Now it is the right time to install <tt>fbbsrv.rpm</tt>
package. The archive is composed to make its
own directories, as "base" directories.
<p>
<item>A file <bf>fbb.conf</bf>, that serves as the
replacement for <bf>init.srv</bf>, is located in the
following location: <bf>/etc/ax25/fbb.conf</bf>
<p>
<item><em>Unless</em> you are going to install daemon-only
system, you should make a backup of the
following files:
<p>
<tscreen><verb>
dirmes.sys
etat.sys
heard.bin
inf.sys
statis.dat
tpstat.sys
</verb></tscreen>
<p>
<item>Now you have to edit <bf>/etc/ax25/fbb.conf</bf>
and change some paths in case you already
have X11 LinFBB installed on a <em>different</em>
path. Here you have some examples that cover
my particular situation...
<p>
<item>Directory of data files, instead of /var/ax25/fbb,
should be <bf>/mnt/win/fbb/system</bf>
<p>
<item>Directory of config files, instead of /etc/ax25/fbb,
should be <bf>/mnt/win/fbb/system</bf>
<p>
<item>Directory of message files, instead of /var/ax25/fbb/mail,
should be <bf>/mnt/win/fbb/mail</bf>
<p>
<item>Directory of compressed files, instead of /var/ax25/fbb/binmail,
should be <bf>/mnt/win/fbb/binmail</bf>
<p>
<item>Directory of users, instead of .../home/fbbdos/...,
should be ...<bf>/mnt/win/fbb/users</bf>... (<-- case you
don't mind that both your WinFBB and LinFBB users handle
the same location for users' files)
<p>
<item>Directory of YAPP files, instead of /home/fbbdos/yapp,
should be <bf>/mnt/win/fbb/users/yapp</bf> (<-- the same
reason as above)
<p>
<item>Directory of documentation files, instead of
/var/ax25/fbb/docs, should be <bf>/mnt/win/fbb/docs</bf>
<p>
<item>Directory of pg programs, instead of /usr/local/pg,
should be <bf>/mnt/win/fbb/pg</bf>
<p>
<item>Path and filename for import file, instead of
C:\FBB\MAIL.IN should be <bf>/mnt/win/fbb/mail.in</bf>
<p>
<item>Now you have to edit <bf>/usr/sbin/xfbb.sh</bf>
and change some paths in case you already
have running X11 version of LinFBB on a <em>different</em>
path. Here you have an example that cover
my particular situation...
<p>
<item>Base directory of XFBB software, instead of
/var/ax25/fbb, should be <bf>/mnt/win/fbb</bf>
<p>
<item>So far - so good. Now it is the time to start
LinFBB daemon. The command for that is in the
location: <bf>/usr/sbin/xfbb.sh</bf> and it may
be executed within an <em>xterm</em>. If
everything is OK, you should get several
system messages on your screen, ending with
something like:
<p>
<tscreen><verb>
xfbbC/X server running ...
xfbbd ready and running ...
</verb></tscreen>
<p>
<item>Well, daemon itself can't be used to access the
BBS so it is needed to activate a <em>client</em>
that is <bf>/usr/sbin/xfbbC</bf>. It has a couple
of parameters (a callsign/password pairs that are
stored in <bf>/fbb/passwd.sys</bf>). Note that xfbbC can
also be activated within another <em>xterm</em>.
<p>
<item>When you finish your xfbbC session, it is suitable
to use the same <em>xterm</em> to eventually stop
daemon. First of all, using the command <bf>ps ax</bf>
you should locate PIDs of daemon, that you may
<bf>kill</bf> after that.
</itemize>
<sect>FURTHER INFORMATION

48
LDP/howto/linuxdoc/Remote-X-Apps.sgml
View File

@ -8,7 +8,7 @@
name="Vincent Zweije">, <htmlurl url="mailto:zweije@xs4all.nl"
name="zweije@xs4all.nl">
<date>13 November 2000
<date>16 November 2000
<abstract>
@ -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 <tt>/dev/null</tt>.
Contents last updated on 13 November 2000 by <htmlurl
Contents last updated on 16 November 2000 by <htmlurl
url="http://www.xs4all.nl/~zweije/index.html" name="Vincent Zweije">
<sect> 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.
<p>
For some related reading, have a look at
the Xterminal mini-HOWTO, for example at <htmlurl
url="http://metalab.unc.edu/pub/Linux/docs/HOWTO/unmaintained/mini/Xterminal"
name="http://metalab.unc.edu/pub/Linux/docs/HOWTO/unmaintained/mini/Xterminal">.
It is currently unmaintained, but it might contain some useful information
for you.
For some related reading, have a look at:
<itemize>
<item>
The <em/XDM and X Terminal mini-HOWTO/ (<htmlurl
url="http://www.ibiblio.org/pub/Linux/docs/HOWTO/mini/other-formats/html_single/XDM-Xterm.html"
name="http://www.ibiblio.org/pub/Linux/docs/HOWTO/mini/other-formats/html_single/XDM-Xterm.html">).
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.
<item>
The <em/XDMCP HOWTO/ (<htmlurl
url="http://www.ibiblio.org/pub/Linux/docs/HOWTO/other-formats/html_single/XDMCP.html"
name="http://www.ibiblio.org/pub/Linux/docs/HOWTO/other-formats/html_single/XDMCP.html">).
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.
<item>
The <em/Xterminal mini-HOWTO/ (<htmlurl
url="http://metalab.unc.edu/pub/Linux/docs/HOWTO/unmaintained/mini/Xterminal"
name="http://metalab.unc.edu/pub/Linux/docs/HOWTO/unmaintained/mini/Xterminal">).
It is currently unmaintained, but it might contain some useful
information for you.
</itemize>
<p>
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.
<sect1> Once More, a Little Theory First