mirror of https://github.com/tLDP/LDP
updated
This commit is contained in:
parent
1284ef758b
commit
bd86c81c9c
|
@ -472,7 +472,7 @@ FBB</ULink>, <CiteTitle>
|
|||
FBB Packet-radio BBS mini-HOWTO</CiteTitle>
|
||||
</Para><Para>
|
||||
<CiteTitle>
|
||||
Updated: October 2002</CiteTitle>.
|
||||
Updated: November 2002</CiteTitle>.
|
||||
Covers the installation and use of the most popular amateur packet-radio
|
||||
BBS software FBB. </Para>
|
||||
</ListItem>
|
||||
|
|
|
@ -364,7 +364,7 @@ FBB</ULink>, <CiteTitle>
|
|||
FBB Packet-radio BBS mini-HOWTO</CiteTitle>
|
||||
</Para><Para>
|
||||
<CiteTitle>
|
||||
Updated: October 2002</CiteTitle>.
|
||||
Updated: November 2002</CiteTitle>.
|
||||
Covers the installation and use of the most popular amateur packet-radio
|
||||
BBS software FBB. </Para>
|
||||
</ListItem>
|
||||
|
|
|
@ -6,7 +6,7 @@
|
|||
<title>FBB Packet-radio BBS mini-HOWTO
|
||||
<author>Miroslav "Misko" Skoric, YT7MPB,
|
||||
<tt/m.skoric@eunet.yu/
|
||||
<date>v1.14, 2002-10-30
|
||||
<date>v1.15, 2002-11-17
|
||||
<abstract>
|
||||
<nidx>linux windows nt amateur packet radio</nidx>
|
||||
This mini-HOWTO covers the installation and use of
|
||||
|
@ -708,7 +708,7 @@ radio BBS, using Protus type of, so called, <em>c_filter</em>:
|
|||
</itemize>
|
||||
|
||||
<p>
|
||||
<sect>How to install daemon version of LinFBB
|
||||
<sect>How to install "xfbbd", a daemon version of LinFBB
|
||||
|
||||
<p>
|
||||
<em>Notice: You see, folks, that I keep trying to get
|
||||
|
@ -863,7 +863,7 @@ to the existing two: X11 LinFBB and WinFBB!</em>
|
|||
|
||||
|
||||
<p>
|
||||
<sect>How to install an "upgrade" to daemon version of LinFBB
|
||||
<sect>How to install an upgrade to daemon version of LinFBB
|
||||
|
||||
<p>
|
||||
<sect1>LinFBB v7.02g
|
||||
|
@ -1310,7 +1310,7 @@ re-start daemon (with different PIDs, of course).
|
|||
</itemize>
|
||||
|
||||
<p>
|
||||
<sect>How to use "xfbbX" - a GUI client
|
||||
<sect>How to use LinFBB's "xfbbX", a GUI client for Linux
|
||||
|
||||
<p>
|
||||
2002-10-20
|
||||
|
@ -1478,6 +1478,105 @@ 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 this or that way.
|
||||
|
||||
<p>
|
||||
<sect>How to use LinFBB's "xfbbW", a GUI client for Windows
|
||||
|
||||
<p>
|
||||
2002-11-17
|
||||
|
||||
<p>
|
||||
<em>Notice: Well, folks, I couldn't try to install and use
|
||||
LinFBB client for Windows, because I have not had
|
||||
a second computer for that purpose. The only way to
|
||||
check how this client works, was to borrow a laptop machine
|
||||
and give it a try.</em>
|
||||
|
||||
<p>
|
||||
The first task was to link that Windows laptop to a Linux
|
||||
desktop. I had some difficulties with the network card on
|
||||
the desktop box, because it seemed not to be likely to start
|
||||
the appropriate <bf>eth0</bf> interface. I'll give you some
|
||||
more details about the equipment here: Linux is Red Hat 6.2
|
||||
and my ISA network card has UMC UM9008 chip. Long ago, I
|
||||
used some utilities that should "recognize" ISA cards (if
|
||||
I remember their names, that were isapnptools, pnpdump etc).
|
||||
|
||||
<p>
|
||||
What I do know, is that such tools should have add some new
|
||||
lines into the existing files, like <bf>/etc/conf.modules</bf>
|
||||
or, to create some new files, like <bf>/etc/isapnp*</bf>.
|
||||
Well, I have forgotten what exactly should be done, so I
|
||||
went to look for the right tools. The one that was looking
|
||||
suitable was <bf>/sbin/isapnp</bf>. Although I got its
|
||||
response on the screen, telling that the UM9008 chip was
|
||||
recognized, there was nothing added to the system files,
|
||||
nor new files seemed to be created.
|
||||
|
||||
<p>
|
||||
What I also tried to use, was the old good <em>Linuxconf</em> tool, that
|
||||
was already installed per default within RH 6.2 Linux. I
|
||||
found the right place to add the information related to NIC's
|
||||
IRQ and I/O address. There I seemed to make a little mistake,
|
||||
so I put the value of <em>220</em> (for the I/O address), instead
|
||||
of <em>0x220</em> that would better fit there. The result was as one
|
||||
may expect: the interface <bf>eth0</bf> continued to
|
||||
report that a <em>ne</em> module had not found a card
|
||||
at that one address. Then I checked the actual I/O address
|
||||
the card uses under Windows OS (was the same) and
|
||||
tried to fix the parameters (Thanks goes to a GB ham who advised
|
||||
me to have to let Linux know the proper IRQ and I/O
|
||||
addresses).
|
||||
|
||||
<p>
|
||||
Interestingly, <em>Linuxconf</em> added a couple of new lines
|
||||
into <bf>/etc/conf.modules</bf> too. In short, the next time
|
||||
during the system boot, the interface <bf>eth0</bf>
|
||||
reported a green <em>[OK]</em>, so I could
|
||||
establish the link. So far - so good.
|
||||
|
||||
<p>
|
||||
The next task was to download the client package from the
|
||||
FBB's main site. I did it from the <em>"Newest version"</em>
|
||||
web page and the number of the version was 1.12 (it
|
||||
seems that was not a pretty much new version, or maybe the
|
||||
content on that <em>"newest"</em> page has not been updated
|
||||
recently). Anyway, I installed it without any
|
||||
problem, configured its part related to the LinFBB
|
||||
server it was about to access, changed the console font to my
|
||||
favourite one (Tahoma) and started the utility.
|
||||
|
||||
<p>
|
||||
At the first sight, the client looked great, because
|
||||
Linux clients still prefer so small letters, that are
|
||||
hard to read (compared to characters on a Windows screen).
|
||||
Now I tried the most used commands like List, Read, Send Reply
|
||||
etc. All of them worked great. What I have found a bit
|
||||
strange, was that the <em>message justification</em> did
|
||||
not work in its message editor window. You see, I like
|
||||
my messages to be justified on both sides. I hope a solution
|
||||
for that will be found soon.
|
||||
|
||||
<p>
|
||||
Another issue with <em>xfbbW</em> client is that seems not to
|
||||
allow a multiple click onto more than one
|
||||
bbs callsign within <em>pending forward</em> list,
|
||||
comparing to WinFBB's behaviour. You know, I am not very fond of
|
||||
opening the same <em>pending forward</em> window repeatedly
|
||||
again and again, in order to start (or to stop) more than
|
||||
one forwarding task at a time.
|
||||
|
||||
<p>
|
||||
In general, I like <em>xfbbW</em> client. I hope to
|
||||
install a newer version soon, as well as some of
|
||||
its features to be upgraded and some new ones to be added
|
||||
in the future. What I would also like to have, is to
|
||||
activate the maintenance of the BBS (a "housekeeping" task)
|
||||
from the client's menu. Another thing I miss at the moment, is the
|
||||
absence of the <em>xfbbW</em>'s help system. I mean
|
||||
of a <em>real</em> Windows help, because there's not
|
||||
much use of its <em>Help</em> menu, having only
|
||||
<em>Copyright</em> and <em>About</em> :-)
|
||||
|
||||
<p>
|
||||
<sect>How to make better ham radio rules?
|
||||
|
||||
|
|
Loading…
Reference in New Issue