Re: JNOS message question

"Jeff Camp" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> I'm in the process of installing JNOS 111f for Linux and have run into a
> problem.  When a user sends a message to another local user, the system
> responds with a "Msg queued" message, but the message is never delivered.
> If I log in as Sysop, I can't see any messages.  If I look in the
> /spool/mqueue I can see all the messages sitting there.
>
> Anyone have any suggestions on where to start?

1.  Toss "JNOS" into the bit-bucket.

Get an old 386 or 486, install DOS and FBB BBS. This combination will be
more reliable and trouble-free than the LINUX/JNOS combo. It requires less
than 20% of the setup time that your present system does, have a better
human interface, and in a general sense it will just plain work better. Part
of the reason for this is that the author of FBB BBS is a much, much better
programmer than the author of JNOS, not to mention all the anonymous junior
programmer wanna-bees that have peed on JNOS, over the years. That code is a
real mess, now. - The inevitable result of "open sewers" programming
technique.

You will find that operating genuine packet BBS software running over DOS to
be a real pleasure, after struggling with Linux/JNOS. It must be remembered
that JNOS' "BBS" functions are the result of a poorly-done hack of
legitimate BBS software, by a "programmer" who obviously did not have the
concept of packet BBS operation very clear in his mind. Even when it works,
nobody likes it because the interface sucks so hard. All that "area" crap,
etc... It's just a waste of time.

After years of bad-mouthing packet BBS's, the truth finally came out when
amateur tcpip enthusiasts discovered that hardly ANYBODY wanted to operate
NOS. The ham tcpip community responded to this fact by inexpertly hacking
basic BBS functions onto various flavors of "NOS", in a desperate bid to get
some significant number of hams to tolerate the weird NOS software. This
effort failed to make NOS popular, but at least it did lay to rest all those
years of bad-mouthing BBS stations. It made it plain that amateur tcpip
enthusiasts know that packet BBS systems are the best way to go. They had to
pretend to be packet BBS's, in order to get anyone to use thier software at
all.

If you install DOS, FBB, and FlexNet, your station will preform better on
the air than any packet system available for Linux. The Linux stuff depends
upon the obsolete KISS protocol, nice stuff in the 1980's but definately
third-rate in this day and age. If you want the latest packet technology
from the 1980's, stick with JNOS/Linux. If on-the-air performance is
important to you, then you want FlexNet.

Of course it may be that you are running Linux/JNOS because you hope to run
a packet/internet gateway... In that case, the DOS/FBB/FlexNet setup would
not work for you, and the best thing you can do is to send your ham liscense
back to the FCC, sell your ham equipment and buy yourself some FRS and CB
gear.

Hope this helps!

Charles Brabham,  N5PVL