<!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>
On Sat, 2007-03-31 at 11:16 +0200, Miroslav Skoric (YT7MPB) wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">Barry Siegfried wrote:</FONT>
</PRE>
</BLOCKQUOTE>
<BR>
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">> The reason that there is no such "manual" is because there are</FONT>
<FONT COLOR="#000000">> limitless possibilities for "specific NOS usage".</FONT>
</PRE>
</BLOCKQUOTE>
On this thought, I'd like to offer something...
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000"> Everyone has</FONT>
<FONT COLOR="#000000">> different needs and therefore uses NOS in a different manner,</FONT>>>SNIP<<<FONT COLOR="#000000">. I myself keep maintaining a FBB howto document </FONT>
<FONT COLOR="#000000">that I am sure is far from perfect but many told me that even then it </FONT>
<FONT COLOR="#000000">helped to start with the software.</FONT>
<FONT COLOR="#000000">> I have more than 20 different CONFIG.H files in the source code</FONT>
<FONT COLOR="#000000">> directories here which hold them,</FONT>
</PRE>
</BLOCKQUOTE>
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.
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000"> and of those 25, whenever I have</FONT>
<FONT COLOR="#000000">> to compile a new or changed program I run a batch procedure that</FONT>
<FONT COLOR="#000000">> automatically compiles all of them. Then I have to distribute</FONT>
<FONT COLOR="#000000">> them after they are compiled which is the fun part...</FONT>
</PRE>
</BLOCKQUOTE>
May I add to your "fun"?<BR>
<BR>
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? 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.<BR>
<BR>
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.
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">> </FONT>
<FONT COLOR="#000000">That great but if you (or somebody close to you) is able to document the </FONT>
<FONT COLOR="#000000">features and/or installation procedure of what you have in your </FONT>
<FONT COLOR="#000000">repositories, that might help the others and save you some time of </FONT>
<FONT COLOR="#000000">answering to reinventing-the-wheels-type of questions :-)</FONT>
</PRE>
</BLOCKQUOTE>
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.
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">></FONT>
</PRE>
</BLOCKQUOTE>
<TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%">
<TR>
<TD>
<BR>
73<BR>
de [George (Skip) VerDuin] K8RRA k
</TD>
</TR>
</TABLE>
</BODY>
</HTML>