On Friday, September 13, 2013 3:40:01 AM UTC-5, Jarrod O'Flaherty wrote: > Greetings > All!
This is a great idea. It is not the typical solution. Having the ability for less experienced Linux operators able to effectively run, maintain and improve their system would enhance the acceptance. Wikis aren't working: There are many; which one to choose is always the question. There are few that have time stamps or version relevance. The user must know the package needing adjustments. Each time there is an upgrade to the kernel or package, the wiki would need to be updated. Like taking a prescription, the prescriber must know what other drugs are being taken to understand interactions; how will a wiki handle this? I like the idea of a tool that would scan the system, identify all components, packages and versions. Locate all configuration files. Being able to present this information would be valuable in itself. The advantage here is that the tool will identify the system. This will provide the opportunity for a focused, automated search. More simply, with the system id, the tool could provide a method to link to version specific, existing how-tos; that is, re-use existing collateral. This would be a first step; bring value in a short time. The refinement would be how to query these target tombs for specific solutions. Next would be converting a specific enquiry to a parsing rule to locate the configuration stanzas for modification. Then, determining the specific modifications and producing code to execute it (the tools knows where everything is located). I like it. Great idea Jarrod. Ray -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/9801f5e3-24e9-458b-a5da-a70d3d12d...@googlegroups.com
