Mark Constable <[EMAIL PROTECTED]> wrote: > > My naive expectation is that when people try to configure servers, > > they *read* the configuration files, in order to make any necessary > > local changes. > > That's assuming a naive user knows enough about realms > to know to read something in the doc/ dir called realms.
That's not what I said. There is a *configuration* file called 'realms'. And reading the normal 'radiusd.conf' will eventually cause you to run into the word 'realms'. I generally avoid documentation for free software projects, because they're usually as bad as those distributed with FreeRADIUS. I find that reading the configuration files, and trying different configurations, is usually much more helpful. > An experienced user has the luxury of incrementally increasing their > knowledge, a new user is trying to figure out WTF is going on and > where to start to even make a start. I gave a talk at the local Unix group a few years ago, describing just how to do this. The summary is this: use grep, find, locate, and any other information retrieval tool you have. They allow you to quickly root through files, looking for key words, and ignoring false positives. Anyone using this method is a Unix guru. I've seen studies which demonstrate this. > Sure, "just read everything" and eventually it'll start to make > sense but that could be a dozen hours (inc rfcs) and I don't know > any newbies that dedicated in any discipline. HOWTOs with lots of > examples would be brilliant. As always, submissions are welcome. We *desperately* need more documentation and examples. The problem is that after most people as one or two questions on the list, their problems are solved, and they go away. They contribute nothing further, and aren't interested in contributing, either. So the only people contributing are the ones who are interested, and there are *very* few of those. > This is something where the non-CVS-enable-developers could > contribute back to the project. I hope I can nudge this along. > Unfortunately I do not know enough about DocBook (nor really > want to) to do any serious manual writting but at least putting > all current texts (or links to them) in one place on the web > might help... and doubly so if they are in Wiki where anyone > can easily make changes... Set up a prototype web site. If it's used and usefull, it can be rubber stamped as "official". > as opposed to trying to run make on a 60k docbook that requires 25 > mb of tex/jade gunk before being able to read anything at all (of > the "manual" that is). Well, that's why I never made any changes to the docbook stuff. I couldn't figure out how to rebuild it. > BTW Alan, I'm a python biggot now... PHP what? :-) Hey, whatever works. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
