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

updated

This commit is contained in:
gferg 2003-06-30 22:10:39 +00:00
parent fc26382540
commit 36bb25fd8f
1 changed files with 134 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

148
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.19, 2003-06-17
<date>v1.20, 2003-06-30
<abstract>
<nidx>linux windows nt amateur packet radio</nidx>
This mini-HOWTO covers the installation and use of
@ -57,24 +57,24 @@ including 16 bit variant for Windows 3.x and Windows 9x as well as
(at the moment it is 16 bit WinFBB v7.00g25 that runs great under
Windows NT 4.0).
<p>New: Since Spring 2001, I run WinFBB v7.00i
<p>Update: In late 1999, I upgraded my system to
Celeron 400 MHz, added more 64 MB of RAM and
switched to bigger hard disk that will have enough room
to install Linux and try LinFBB ...
<p>Update: Since Spring 2001, I run WinFBB v7.00i
(17 March 2001) under Windows 2000 Professional.
<p>The main
difference between DosFBB and WinFBB is that the
second one offers you to do other jobs with your
computer, while FBB is running as just any other
application. Beside that, it is always nice to
copy a text from another application (for example,
application. Besides that, it is always nice to
copy some text from another application (for example,
from an Internet email) and to paste it into a
packet radio message, or vice versa.
<p>In the mean time, I upgraded my system to the
Celeron 400 MHz with 96 MB of RAM and a big hard
disk that has enough room to install Linux and try
LinFBB ...
<p>New: In July 2001, I added more 128 MB of RAM
<p>Update: In July 2001, I added more 128 MB of RAM
so my home system is very confortable now.
<p>Finally, you should be aware what I want to
@ -862,7 +862,7 @@ to the existing two: X11 LinFBB and WinFBB!</em>
<p>
<sect>How to install an upgrade to a daemon version of LinFBB
<sect>How to install an upgrade to the daemon version of LinFBB
<p>
<sect1>LinFBB v7.02g
@ -1085,11 +1085,11 @@ reverse procedure must be put in place.</em>
BBS from that one 'telnet client' box. If that
succeeds, it would be a good preparation for
installing another LinFBB (in the local school
club), where several old 286 computers will also
be available. It would be nice to offer more than
club), where several old 286 computers will be also
available. It would be nice to offer more than
one student-amateur the opportunity to 'connect' the
BBS simultaneously, using a bunch of vintage
'telnet client' computers.
'telnet client' DOS computers.
</itemize>
@ -1479,6 +1479,49 @@ modifications, related to program executable paths, but I
do not know how to manage that. Anyway, it does not matter
because <em>xfbbX</em> is running here this or that way.
<p>
2003-06-30
<p>
A recent email from Jose, HI8GN, related to the xfbbX GUI client,
about the RPM package:
<p><em>
"The reason of the why not the xfbbd X Client didn't give you any
answer is for several causes. 1) if the xfbbd daemon is not running
the xfbbd X client won't run. 2) if the xfbbd is dead in its process.
3) if the xfbbd was not shutoff correctly, but delete the xfbbd lock file
as this:</em>
<p><em>
. /etc/init.d/rc.fbb stop or service rc.fbb stop, and then it was run
and didn't create the xfbbd lock file, the shell script looks for the
existence the /var/lock/subsys/xfbbd or /var/lock/subsys/xfbbX lock file
and 4) if the xfbb X11 Server it is running it create a xfbbX lock file
by that the xfbbd X client won't neither run</em>
<p><em>
the same thing makes the X11 Client the one it verifies that the xfbbd is
not running</em>
<p><em>
if you make a click on the Icon that says fbb X11 Client and it doesn't run
it is because the one is seeing that there is a process of the xfbbd
running like as daemon.
the script rc.fbb I have also modified it so that it can not be executed
twice.</em>
<p><em>
if exist xfbbX lock file the xfbbd X client won't run
if exist xfbbd lock file the fbb X11 won't run.</em>
<p><em>
Lastly if you execute the command fbb in the console or in xterminal in
the desktop, you will see what I mean that simple."</em>
<p>
Thanks Jose!
<p>
<sect>How to use LinFBB's "xfbbW", a GUI client for Windows
@ -1722,6 +1765,81 @@ of Linux you have. If not ...</em>
</itemize>
<p>
<sect>How to access the "xfbbd" server from a DOS client?
<p>
2003-06-30
<p>
<em>Notice: In some of the previous chapters, I announced
my plans to use an old i286/12 MHz box,
having only 1 MB of RAM, running DOS 5.0, as a
'telnet client' computer. That box has a network
card so I would like to 'connect' to the
BBS from that one 'telnet client' box. If that
succeeds, it would be a good preparation for
installing another LinFBB (in the local school
club), where several old 286 computers will be also
available. It would be nice to offer more than
one student-amateur the opportunity to 'connect' the
BBS simultaneously, using a bunch of vintage
'telnet client' DOS computers.</em>
<p>
First of all, I have been looking for networking software that
does not require much of hardware resources. Several hams
keep advising me to try this or that way, but Jose, CO2JA,
sent me his distribution copy of <bf>NCSA Telnet</bf> utility.
According to its own <em>howto</em> document, that is
actually a <bf>"NCSA Telbin DOS client"</bf>, being <bf>"used
at The University of Port Elizabeth (Sep '94)"</bf>. So far
about software's earlier "official" usage.
<p>
Well, it seems that NCSA TCP/IP kernel only runs on packet
drivers now. That's why I looked for appropriate packet drivers
for my old ISA network card, equipped with the UMC's UM9003AF
chip. <bf>CZ20000.COM</bf> packet driver seemed to be the
most suitable one.
<p>
Before implementing the driver I also needed the proper diagnostic
utility to check and/or modify NIC's IRQ and I/O address in order to avoid
possible hardware conflicts (you know, under DOS it is less easier
to resolve interrupt hardware conflicts case a user has several ISA
cards that are not of P'n'P type /as PCI cards are/). It seemed that
<bf>DIAG.EXE</bf> ("The Ethernet Adapter Diagnostic Program,
Ver. 2.13" - that comes with E1000 and E2000 series Etherent cards)
was fully capable to handle my card's parameters, so I choose the
values of IRQ 5 and I/O 320 that weren't occupied by other resources.
<p>
Then I could execute the following DOS command:
<tscreen><verb>
cz2000 0x60 5 0x320
</verb></tscreen>
<p>
in order to activate the NIC.
<p>
Now the configuration file CONFIG.TEL should be modified
in order to satisfy my particular needs, including local (DOS client) and
remote (Linux server) IP addresses etc. In a couple of minutes
that was finished so the main executable <bf>TELBIN.EXE</bf>
successfully started running on my old 286 DOS box.
<p>
If you want, you may put <bf>cz2000 0x60 5 0x320</bf> and
<bf>telbin</bf> commands into a dedicated <em>TELNET.BAT</em>
file in order to make your telnet utility easier to activate. Should
you plan to use your old DOS box for only accessing the
Linux FBB server, both lines may be added to the
<em>AUTOEXEC.BAT</em> startup file.
<p>
<sect>How to make better ham radio rules?
@ -2200,3 +2318,5 @@ little annoying.