<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.12.3">
</HEAD>
<BODY>
First of all Barry I don't want this to develop into a hard point between us.<BR>
<BR>
On Sat, 2007-03-31 at 13:20 -0400, Barry Siegfried wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">["(Skip) K8RRA" <<A HREF="mailto:k8rra@ameritech.net">k8rra@ameritech.net</A>> wrote]:</FONT>
</PRE>
</BLOCKQUOTE>
>>SNIP<<
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">></FONT>
<FONT COLOR="#000000">> Would you be willing to create perhaps a table or some other human</FONT>
<FONT COLOR="#000000">> readable description of the 20(+) environments that cause the owner</FONT>
<FONT COLOR="#000000">> to choose a unique config.h for his installation?</FONT>
<FONT COLOR="#000000">Ummm... well, 5 of the 20 of them are for my own machines, and with the</FONT>
<FONT COLOR="#000000">remaining 15 I started with what they thought they needed and then I</FONT>
<FONT COLOR="#000000">chose the rest of what they really needed and eliminated what they</FONT>
<FONT COLOR="#000000">thought they needed but didn't really need.</FONT>
</PRE>
</BLOCKQUOTE>
SO - maybe the table becomes 16 long?<BR>
That is still a whole lot of example usage.
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">> This description really needs to be a one-liner that captures the prime</FONT>
<FONT COLOR="#000000">> essence of the owners desire. It needs to capture the imagination of</FONT>
<FONT COLOR="#000000">> non-jnos users who are willing to download the specific config.h and</FONT>
<FONT COLOR="#000000">> read the detail for himself. And yes, the 20 config.h files need to</FONT>
<FONT COLOR="#000000">> be attachments to the page containing your table.</FONT>
<FONT COLOR="#000000">Skip, this actually won't help you very much because the structure and</FONT>
<FONT COLOR="#000000">layout of my own CONFIG.H file highly differs with the one that JNOS</FONT>
<FONT COLOR="#000000">uses and since this is a JNOS project I suspect that anything I could</FONT>
<FONT COLOR="#000000">offer as a way of "explaining" my own CONFIG.H files would just serve</FONT>
<FONT COLOR="#000000">to confuse the JNOS user.</FONT>
</PRE>
</BLOCKQUOTE>
You have made my point exactly...<BR>
1) you have worthy (my opinion) examples in your hands.<BR>
2) the "read config.h" method is difficult to EASILY get comparison from<BR>
3) the config.h file represents workable detail to making jnos fit into the chosen environment.<BR>
<BR>
What is needed is SIMPLE environment description (a one-liner?).
<BLOCKQUOTE TYPE=CITE>
<PRE>
>>SNIP<<<FONT COLOR="#000000"> I really</FONT>
<FONT COLOR="#000000">wouldn't know how to make it any clearer than it already is.</FONT>
</PRE>
</BLOCKQUOTE>
Let me try approaching this in this manner:<BR>
<BR>
You carry around in your head a list of say 20 ways of using one software - jnosx.y.<BR>
In your thinking it is crystal clear how to get what you want to happen.<BR>
<BR>
I carry around in my head that jnos is the swiss-army knife of packet software.<BR>
In my thinking it is not particularly clear which blades of the knife to pull out.<BR>
After deciding on the blade, there is a step needed to make it happen I'd like to explore.<BR>
<BR>
I rather see Misko's experiment being an example of my need to know.<BR>
At a little deeper detail perhaps than I want to capture for wiki as he proceeds.<BR>
Certainly as an example posted to the wiki when he is done... (no matter the success %)<BR>
<BR>
As I approach my wiki, I try to add options in tabular or matrix or outline form in English.<BR>
OK - I've also set the stage for other languages for a later date.<BR>
So as I make my choices of what to do I feel comforted when I see others have done this before me.<BR>
<BR>
The resources I see for my wiki are:<BR>
1) a common language discussion of how jnos has been used by others.<BR>
2) the computer files (config.h and autoexec.nos and others) to accomplish 1)<BR>
3) the html "linking" features and wiki "search" features to permit QUICK detail investigation.<BR>
Have you ever heard the expression "Drill down into the detail."?<BR>
<BR>
I see how you view reading config.h comment text leading to the same thing I need to know.<BR>
I interpret (my understanding of) your view as one of an expert with years of experience.<BR>
For the wiki I desire to capture your experience in the simplest terms I can for others to understand.<BR>
In my experience elsewhere that means charts and graphs and outlines in brief form.<BR>
It also means attaching the detail for deeper understanding (config.h).<BR>
<BR>
I hope you would allow me to "...$ diff config1.h config2.h" to see the interaction between choices.<BR>
That is after I have made the top-level choice and need further detail choice.<BR>
<BR>
If you were to ask me to define the user I am trying to satisfy, he/she would look to the wiki for:<BR>
1) an understanding of the list of capabilities built into the software (top level summary)<BR>
2) examples of application choices made by others<BR>
3) sample configuration data for plug-and-play into a new use (after detail editing like call-sign)<BR>
4) enough tech detail to permit trouble shooting of failures to perform<BR>
<BR>
Clearly Maiko's example of mail forwarding into WL2K fits # 2) above.<BR>
Jay's use for MI-DRG is certainly another # 2).<BR>
Won't Misko's example with FBB forwarding be another?<BR>
Let's consider the wiki as a vehicle to permit others we don't know today to follow in our footprints.<BR>
If you, Misko, Maiko, Jay, and I, have created 30(?) patterns of use, the wiki user stands to create 30(+) we have not seen yet.<BR>
I hope they will add their perspective to it after I'm done with my part.<BR>
<TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%">
<TR>
<TD>
<BR>
73<BR>
de [George (Skip) VerDuin] K8RRA k
</TD>
</TR>
</TABLE>
</BODY>
</HTML>