Error all the time

[Geert Janssens]

Ok, I did the two independent searches:

1. bind key 255
This results in 14 hits, of which two refer to moved pages (404 error 
message), and none actually mentions "bind key 255", but all mention 
"key" or "255" (in case of the TCP one) only.

2. value 3325
This results in 6 hits, and none actually mentions "value 3325", but 
only mention "value"

I did review all articles. Although they are full of useful information, 
none of the information would help with the original question.

I tend to draw the following conclusion:
The YLD faq's search mechanism behaves differently than you did expect. 
Apparently it searches for any word in the seach term, instead of the 
expected all words. To search for all words (as would be  more useful in 
case of searching for specific error messages), one has to quote the 
search term, as I just tested. If I quote your search strings, there are 
no hits left (which is correct, since there are no articles dealing with 
the problem).

For me, again this conclusion supports the idea of verifying replies.



Finally, I would also like to stress it's not my intention of offending 
anyone, and not you Mr. Centeno in particular. You're a very active list 
member, and I appreciate that. My reply just comes from my past, 
remembering the frustration and discouragement of getting answers that 
actually were none. It made me feel stupid for not seeing or 
understanding the answer.



Best regards,

Geert Jan

Derick Centeno wrote:
> 
> Hmmmmm...
> Geert what can I say!
> 
> How about this.
> 
> If one follows the instructions as I gave it.
> Which is to do two independent searches on the YDL FAQ website:
> 
> 1.  bind key 255
> 2.  value 3325
> 
> One not only finds articles, one finds a stunning amount of detailed
> information very embedded in the articles (such as command calls, system
> response details and more).  If one takes the time to review them.
> 
> I did that and thought well the fellow (our fellow monkey; it's ok
> monkey you are still the monkey, if you wish) should be able to take
> from there.
> 
> I did not look up KDSKBENT as monkey's complaint clearly showed it to be
> an invalid argument.  My interpretation (which could be wrong) of the
> KDSKBENT reference was that it referred to a macro or something like it;
> however the next line identified the actual problem itself defining why
> that macro (or header) was declared invalid.
> 
> I chose to emphasize the search pattern I recommended which, again DOES
> WORK, addresses the actual problem or which at least points to what the
> actual problem may be within the macro.
> 
> Now it may be that my reasoning is still wrong.  I won't know.  I'm not
> tracking down this issue any further.  However, as far as I did pursue
> the issue, what I came up with does refer to useful references which
> should be considered or at least reviewed.  That is why the YDL FAQ is
> there...no?
> 
> 
> 
> _______________________________________________
> yellowdog-general mailing list
> yellowdog-general at lists.terrasoftsolutions.com
> http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-general
> HINT: to Google archives, try  '<keywords> site:terrasoftsolutions.com'
> 
>