Having followed the discussion about the use of scripts to collect diagnostic information, I think we are muddling two distinct questions.
1. Is incorporating a "diagnostics" script in into each LEAF distribution a good idea? Probably (as long as it doesn't get so big as to cause problems with fitting on a floppy). And as soon as each variant's lead developer, or a helper, actually writes one that works for a particular LEAF variant, the FAQ should reference it. But ... the FAQ mentions optional information, to be supplied if circumstances warrant; how does one sensibly incorporate that into a script? (Like all of us, I want users to post enough information, but nort too much.) 2. What should the FAQ tell users about collecting troubleshooting data? Well, the discussion makes it clear that a *standard* script that works across all LEAF variants is either impractical or complicated (probably just complicated). In any case, the FAQ itself can't reasonably provide such a script. So I'd suggest the FAQ retain the list of commands to use, and it can incorporate references to scripts when they actually exist. But ... it should always include the actual commands, because that is part of the teaching role the FAQ can serve, helping the user learn how to troubleshoot his or her own systems, not *just* how to gather data for us to look at. At 06:56 AM 3/12/02 -0800, Jeff Newmiller wrote: >On Mon, 11 Mar 2002, David Douthitt wrote: [old stuff deleted] -- ------------------------------------"Never tell me the odds!"--- Ray Olszewski -- Han Solo Palo Alto, CA [EMAIL PROTECTED] ---------------------------------------------------------------- _______________________________________________ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
