How to install X11 (Xwindows) version of LinFBB
@@ -162,7 +159,7 @@ LinFBB ...
-How to install LinFBB in addition to existing WinFBB
+How to install LinFBB in addition to existing WinFBB
Notice: Folks, you see, at my place, I have a
@@ -330,7 +327,7 @@ versa, of course).
-How to install Protus password utility
+How to install Protus password utility
Notice: Well, I have been using Protus
@@ -409,7 +406,7 @@ Protus offers several interesting features:
Well, let's see what should be done in order to
implement secure access to the FBB packet
-radio BBS, using Protus type of c_filter:
+radio BBS, using Protus type of, so called, c_filter:
@@ -580,7 +577,7 @@ radio BBS, using Protus type of c_filter:
-How to install daemon version of LinFBB
+How to install daemon version of LinFBB
Notice: You see, folks, that I keep trying to get
@@ -734,7 +731,10 @@ to the existing two: X11 LinFBB and WinFBB!
-How to install an "upgrade" to daemon version of LinFBB
+How to install an "upgrade" to daemon version of LinFBB
+
+
+LinFBB v7.02g
Notice: Well, the main trouble I have discovered with 7.01f
@@ -764,20 +764,26 @@ special requirements over some "third-party" software.
complained about some existing LinFBB files.
-- Then I had to de-install the old package, after what
- some config files remained as .rpmsave
- files. It was nice, so I could use them to update my
- new-installed config files.
+
- Then I had to uninstall the old package, after what
+ some config files remained in their locations, but
+ with new .rpmsave extensions. It was nice,
+ so I could use them later to update my new-installed
+ config files.
- Btw, the installation of Jose's package was performed
without problems, but the new daemon was not likely to run
as I expected, although I tried to configure it as best
- as I could. So, I have decided to make copies of new
- xfbbd and xfbbC from 7.02g package and
- *de-install* the rest of its .rpm, in order to
- install the previous version of LinFBB once again - the
- version that I was satisfied with.
+ as I could. Not quite sure, but it looked to me that F6FBB
+ is likely to implement some changes not only to the main
+ executables but to shell files too. So, I have decided to
+ save copies of these new
+ xfbbd and xfbbC executables from 7.02g
+ package (I have made it with adding extensions like
+ .702 to the files). After that, I *uninstalled* the rest
+ of that 7.02 .rpm, in order to install the previous
+ version of LinFBB once again - the version that I was
+ satisfied with.
- So far - so good. The "old" 7.01f version was installed again
@@ -799,17 +805,160 @@ special requirements over some "third-party" software.
- An interesting question might be: is that now a really upgraded
LinFBB daemon or not? Actually, I haven't changed the "old"
script xfbbd.sh with the new one, because during the
- first tests with the new one I was getting lots of error messages.
+ first tests with the new 7.02 I was getting lots of error messages.
Looks that the directory structure was a bit complicated for me
to set properly within the new version of xfbbd.sh.
+ After I returned to xfbbd.sh from 7.01 package, the
+ BBS finally started to be run, though without some functions
+ like over-night maintaining (that one problem I solve in a way
+ to boot the BBS as WinFBB under Windows NT where that task is ok).
In addition, there are still some mysterious messages telling
that m_filter has not been found or something like that.
The next tasks are to solve these issues.
+
+LinFBB v7.03
-FURTHER INFORMATION
+
+Notice: As I have said in the previous section,
+I haven't found an easy way to upgrade FBB's (its main
+executables), without temporary uninstalling of an
+older version, then to install a newer version in
+order to get new executables. After that, a reverse
+procedure must be put in place.
+
+
+
+
+- Well, it was needed to get 7.03 package (09. December 2000)
+ as an .rpm package from
+ ,
+ that was suggested by Jean-Paul, F6FBB. Anyway,
+ soon after there appeared several mirror sites,
+ offering 7.03 too.
+
+
+- If you use GnomeRPM, it is easy to uninstall
+ your actual LinFBB (If you just try to install new
+ .rpm over the existing LinFBB you will get
+ some error messages complaining that you already have
+ FBB installed on the computer). Anyway, after
+ the uninstallation, there you will find some config
+ files as .rpmsave files, so you could use
+ them later again.
+
+
+- Installation of 7.03 package will give you
+ new executables in /usr/sbin directory.
+ Those new executables should be temporary given
+ extensions like .703 (for example).
+
+
+- So far - so good. Now you should *uninstall* the
+ 7.03 package (of course, .703 files won't
+ be unistalled automatically).
+
+
+- Once again, you should *install* the last
+ one version of LinFBB daemon, that works ok with its
+ own xfbb.sh (in my case, that is 7.01f).
+
+
+- For sure, many of you might find it odd, but
+ now it is the right time for the executables from
+ /usr/sbin (I mean of all fbb executables,
+ except those who were renamed to .703) to get
+ their new extensions (in my case, that is .701).
+
+
+- Well, after that is performed, .703 files
+ should *lose* their previously attached extensions,
+ in order to become usable.
+
+
+- Folks, on that point I usually hold my breath, cd
+ to /usr/sbin and type: xfbb.sh
+ following with an Enter. If everything is fine, several
+ lines should scroll on the screen, ending with
+ something like:
+
+
+ xfbbC/X server running ...
+ xfbbd ready and running ...
+
+
+
+- If you don't get something similar on your xterm
+ 'window' (or on other appropriate terminal
+ utility), you're out of luck, so you might go
+ thru the procedure once again in order to be
+ sure you did all what was needed to be done :->
+
+
+- /usr/sbin/xfbbC is the easiest way to
+ check if your new 7.03 is in the game
+ or not. When I mention xfbbC it is good to let
+ you know, that I kept living in a belief that
+ xfbbC is also useful for regular telnet users
+ (who are also supposed to 'connect' to the BBS via
+ the same computer's console, where LinFBB is
+ running from). But, I have discovered that my
+ users, who were not declared as sysops,
+ are allowed to read all messages (including all
+ private messages), as well as to have some
+ other sysop's abilities. I did think it was
+ a matter of probably wrong declared security flags.
+ But, it was not.
+
+
+- Recently, I was informed that xfbbC
+ is suitable only for sysops, but other users
+ (who also might have local keyboard access)
+ should rather try:
+
+
+
+ telnet localhost 6300
+
+
+
+- ... where 'localhost' and '6300' may vary from
+ system to system. I was pleasently surprised
+ when discovered that telnet is much more
+ useful for regular users than xfbbC.
+
+
+- Folks, I think of making a section about the
+ FBB's system configuration. Until something
+ like that appear on the net, you should know
+ that all of those callsigns who are going to
+ use xfbbC have to be added into
+ your passwd.sys file. And, all of
+ those who are going to telnet into
+ the BBS have to be declared as users with
+ a 'M' flag (modem users). It is up to your
+ security precautions, if either of them will
+ have 'root' abilities to the Linux box.
+
+- My next issue is to use an old 286/12 MHz box,
+ having 1 MB of RAM and running DOS 5.0 as a
+ 'telnet client' computer. That box also has
+ a NIC and I would like to 'connect' to the
+ BBS computer from that 'telnet client' box.
+ Due to my preparation for starting another
+ LinFBB in the local school club, where I
+ should have several old 286 boxes, would
+ be nice to offer more than one kid to
+ 'connect' the BBS simultanously, using
+ a bunch of 'telnet client' computers.
+
+
+
+
+Further information
Copyright