Stephen Fulton <[EMAIL PROTECTED]> wrote: > The problem with this list is that those in need of assistance (until a > recently ordered RADIUS book arrives), are often told something is wrong, > but examples are hard to come by. Telling me the syntax is wrong isn't > going to solve the problem. You could have suggested something more > productive, you have the knowledge and the information was provided in my > e-mail.
This is where I say that you have examples and information from the 'hints' file in front of you. I'm left pointing at them, and going "do it that way!" Further, if you have difficulties with simple syntax and examples like the 'hints' file, I'm not sure how you will be able to deal with more complex examples or configuratoins. My answers are intended to allow you to learn for yourself how to solve problems, and not to hold you hand, and show you where every little comma and quotation mark goes. That attitude leads to endless minor questions on the list, and I'm simply too lazy to answer them. > 1. Given the lack of starter documentation regarding FreeRADIUS, > particularly due to its developing nature, experts and developers may want > to consider providing current examples to their suggestions. The examples distributed with the server are as current as they come. If you want more, write them, and submit them for inclusion. If you want better examples as answers to your questions, send a private email to one of the developers with an offer to pay for technical support. Barring that, I don't see why anyone would complain about the quality of free technical support. > 2. Those who contribute modules be required to meet certain standards for > documentation OUTSIDE of the actually configuration files. The rewrite > module is an example. I understand your concern. But it's difficult to look a gift horse in the mouth. If a module is useful to many people, then it will be included, even if the documentation is poor. So we end up with a good server, with crappy documentation. The alternative is to have a crappy server, with good documentation. If FreeRADIUS was a crappy server with good documentation, you wouldn't be complaining about it. You wouldn't have to, because you'd be using something else, that worked. > 3. Before 1.0, a coordinated effort be mounted by the lead developers to > the expansion of the FAQ and documentation. Tedious work for coders, I > know, but as I've said before, what's the use of esoteric information in an > open-source project? Please go back and read the main 'README' which is distributed with the server. I am appalled at the number (and sheer gall) of people who desire that others do the work that they are unwilling to do. Submit documentation. It will go in if it's anything approaching understandable. But no one ever does... all they do is complain that they don't like the documentation, and that someone (i.e someone ELSE) should write more. Then they go away, and never contribute anything at all to the project. > If such persons are time-constrained, perhaps a moderated > "FAQ-O-Matic" where the public can contribute solutions to problems > they've encountered. Great! When will you set one up? Where's the URL? Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
