[nos-bbs] JNOS & tactical calls

[Michael Fox - N6MEF]

Hi Michael,

 

I know Fish is traveling right now so he may be delayed in getting back to
you.  I'll answer what I can.

 

See below.

 

From: nos-bbs-bounces at tapr.org [mailto:nos-bbs-bounces at tapr.org] On Behalf
Of Michael Curry
Sent: Wednesday, April 13, 2011 3:52 PM
To: TAPR xNOS Mailing List
Subject: Re: [nos-bbs] JNOS & tactical calls

 

In a thread that you all thought went dormant last month, FiSH (K6FSH)
wrote:

> if you UNDEFINE MBX_AREA_PROMPT and MBX_MORE_PROMPT it should 
> eliminate the need to pre-configure users to "expert" mode.  We use
Outpost too.

Apropos of this observation, I just want to verify -- are the following
assertions true? (And if not, what's the proper course of action?)

 

1a) There's no #define that I can change to #undef to turn off the
alphabet-soup prompt (a user still needs to issue the X command to get that
to go away);

 

I'm pretty sure he added something for this, too.  But I don't know what he
labeled it.

 

1b) The alphabet-soup prompt doesn't prevent Outpost from working correctly
with JNOS (statements found on the Outpost website to the contrary
notwithstanding);

 

I think that is correct, but you should test to verify.  Mostly, I think it
just wastes bandwidth when using Outpost.  The more prompt is the critical
think with Outpost.

 

2) Even though (after #undef'ing the two symbols named above) I don't need
to doctor up entries in users.dat for the Tactical Call Signs, I still need
to create entries for them in ftpusers (unless I'm willing to let them
default to "univperm", or some more specific "<interface>perm").

 

The allowed tactical call signs are not defined in users.dat.  They are
defined in a file called "TacCalls" which is located in the main JNOS
directory.  The format of the file is shown in this document:
http://www.scc-ares-races.org/packet/SCC_Pkt_Tac_Call_Request_v100913.pdf
There is an example at the end of the document.  Note that we impose some
administrative constraints within our own network, such as that the tactical
calls must begin with a certain 3 letters, the fourth letter can't be 0
(zero), etc.  But those are administrative rather than technical
limitations.  Also, no description is required next to each tactical call.
That's just another administrative requirement so more than one person can
make sense of a given agency's file.  We have each of our cities and served
agencies submit their file and then we simply concatenate them together and
put the result in $JNOS_DIR/TacCalls.

 

I would say yes, you'd need to define the perms in ftpusers if you don't
want univperm.

 

Also, is there any documentation of the format of entries in users.dat? Or
do I just need to read the code?

 

Just the above document.  Perhaps when Fish get's back we'll corner him and
get him to write up some documentation that can be posted to Maiko's site.

 

Michael

N6MEF

 

 

Thanks!

 

Michael KI6TYV
-- 
Remember, Comrades: Life is a series of choices -- all of which will be made
for you by Central Committee.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/nos-bbs_lists.tapr.org/attachments/20110413/6f54f19b/attachment.html>