[nos-bbs] Missing something - 44 net

[George (Skip) VerDuin]

Barry - I'm "chewing on" your response that is very thorough.
I'm selecting one detail I did not communicate on:

On Tue, 2006-07-25 at 16:52 -0400, Barry Siegfried wrote:

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

>SNIP<

> 
> > As an aside:  you notice that Maiko has begun the process of detaching
> > jnos/host support routines/libraries?

Bad use by me of abbreviated thought:
Maiko has renamed jnos code of similar processes to make platform tools
more available.
Example: "j2pause" used to be "pause", but pause is a system call for
modern C libraries.  Now over time "j2pause" syntax can be replaced with
platform built-in pause syntax.  Looking toward the future the "j2pause"
C code function can be removed.

At least that is my interpretation...

Then my extension of that thought is that if NAT were available as a
library call (over simplified?) then NAT might be plugged into jnos as a
function at compile time with minimal effort on the programmers part.

>   It may be a future strategy of
> > his that NAT can be "plugged in" when needed and not included into the
> > application?  Our conversation here may become the "old way" of doing
> > things...
> 
> I am not familiar with the JNOS library layout.

Actually jnos seems to me a bit unique in that it seems to rely on
platform tools very little - as in the "pause" example.
It seems to me to be quite self-sufficient or nuclear.  Probably from
it's lineage.
So it can be seen as requiring few support libraries in the conventional
sense...

Therefore I hesitate to characterize jnos as having or needing much for
"library" as it is today.

>   It was always part
> of every NOS platform to have the ability to enable and disable items
> as needed.  This permitted you to compile versions of the program
> which were extremely fine tuned and tailored to function in a
> particular environment or for a particular purpose.  If that is
> what you are calling the "old way" of doing things, we are still
> doing them today and it works pretty darn well.  :)

I agree it works well up to and including today.
My hope for tomorrow is that new functionality might add with less
labor?
The "new way" might be to collect various libraries from various places
before compiling...

However - we get off-topic in all of this futureing.  Let's let this
part go?  I'll be back on IP #s soon enough...

> 
> 73, de Barry, K2MF >>
>            o
>           <|>      Barry Siegfried
> +---------/-\---------------------------+
> | Internet | bgs at mfnos.net              |
> | HomePage | http://www.mfnos.net/~bgs  |
> +----------+----------------------------+
> | Amprnet  | k2mf at nnj.k2mf.ampr.org     |
> | PBBS     | k2mf at k2ge.#cnj.nj.usa.noam |
> +----------+----------------------------+
> 
> _______________________________________________
> nos-bbs mailing list
> nos-bbs at lists.tapr.org
> https://lists.tapr.org/cgi-bin/mailman/listinfo/nos-bbs


73
de Skip k8rra k


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