XPost: alt.windows7.general   
   From: mayayana@invalid.nospam   
      
   "Paul"  wrote   
   | This is generally true for projects where you're   
   | modifying the networking stack on your OS.   
   | It's always going to be a nail-biter, as   
   | you never know how it'll turn out (dumpster   
   | fire, or Nobel Prize).   
   |   
      
     Actually, so far it seems that Unbound is very stable   
   and easy to use. And it seems to be held in high   
   regard. The only problem is that they didn't bother   
   to write a help file. They have a Windows guide in   
   PDF form that's little more than pictures of the installation.   
   Maybe a practical joke meant to be a dig at Windows   
   users? I don't know.   
      
      Someone told me I could test the config in a console   
   window with one of the files in the install. I *never once*   
   saw mention of that in the config notes or on any of the   
   webpages I found where people were offering tips for   
   setting up Unbound.   
      
     The only guidance is a few comments in the config file,   
   but it's assumed one has a thorough knowledge of both   
   networking protocols and Unbound itself.   
      
     I find that's common with these things. Not just OSS.   
   Try finding out how to write the notation for an IP   
   address range. It's easy to find samples. Very difficult   
   to find a clear explanation for beginners. The problem   
   with only having samples is that the rules can't be inferred.   
   And you don't know if the samples are accurate. I came   
   across 3 or 4 ways to set up the syntax for HOSTS   
   blocking in Unbound. There's no credible reason that it   
   doesn't use the same syntax as HOSTS. And why are   
   there so many variations? Do they all work? Are some   
   people doing it wrong? Without an explanation of the   
   syntax rule it's hard to know.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)