[nos-bbs] Questions related to JNOS 1.11f

[Barry Siegfried]

["(Skip) K8RRA" <k8rra at ameritech.net> wrote]:

> > Barry Siegfried wrote:
>
> > > The reason that there is no such "manual" is because there are
> > > limitless possibilities for "specific NOS usage".
>
> On this thought, I'd like to offer something...
>
> > > I have more than 20 different CONFIG.H files in the source code
> > > directories here which hold them,
>
> The implication here is that you have 20(+) client hams who operate
> with 20(+) configuration needs that are not satified with 10, or 5,
> or 2, especially not 1 configuration.  You have hit on one of the
> purposes I have in my wiki.  It is not so much for the 20 you already
> network with, but for the 20(+) new and interested in exploring what
> jnos can do for them in their world of ham radio.
>
> Would you be willing to create perhaps a table or some other human
> readable description of the 20(+) environments that cause the owner
> to choose a unique config.h for his installation?

Ummm... well, 5 of the 20 of them are for my own machines, and with the
remaining 15 I started with what they thought they needed and then I
chose the rest of what they really needed and eliminated what they
thought they needed but didn't really need.

> This description really needs to be a one-liner that captures the prime
> essence of the owners desire.  It needs to capture the imagination of
> non-jnos users who are willing to download the specific config.h and
> read the detail for himself.  And yes, the 20 config.h files need to
> be attachments to the page containing your table.

Skip, this actually won't help you very much because the structure and
layout of my own CONFIG.H file highly differs with the one that JNOS
uses and since this is a JNOS project I suspect that anything I could
offer as a way of "explaining" my own CONFIG.H files would just serve
to confuse the JNOS user.

> I see this as a one-time exercise - not a keep-up-to-date exercise.  In
> my perspective as a newbie to jnos, what I am asking for is a key piece
> in my exploration of jnos vs some other brand of software for my hobby.
> It also becomes a starting point for the use of the compiler for
> optimization purposes.  My opinion is that you two guys are discussing
> the groundwork of this presentation, I would like to offer the platform
> to do it on.
>
> If you choose to go forward with this concept, please let me know how I
> can help?  I'm legitimately not "close to you" but I am embarked on this
> kind of quest.

Even if I did use JNOS and the JNOS CONFIG.H file, I'm not sure I
understand how what you are asking for can possibly help.  Call me
dense if you will, but the way I see it is, if you need email services
then you #define SMTP.  If you need FTP services, then you #define FTP.
If you need the MAILBOX then you #define MAILBOX.  If you need AX.25
or Net/Rom support then you #define AX25 or NETROM.  And so on, and
so on.

I'm not sure how it helps to have a one line description that is
external to the CONFIG.H file.  The description for each item to
#define or #undef is already in the CONFIG.H file.  If you need it,
then you #define it.  If you don't then you #undef it.  I really
wouldn't know how to make it any clearer than it already is.

73, de Barry, K2MF >>
           o
          <|>      Barry Siegfried
+---------/-\---------------------------+
| Internet | bgs at mfnos.net              |
| HomePage | http://www.mfnos.net/~bgs  |
+----------+----------------------------+
| Amprnet  | k2mf at k2mf.ampr.org         |
| PBBS     | k2mf at k2ge.#cnj.nj.usa.noam |
+----------+----------------------------+