(All: I really appreciate the suggestions that have been trickling in. I've a pile for a lazy Saturday afternoon of research. Thanks!)
Lawrence, usable in a disaster: That's a very important point that I didn't bother to mention about my home grown solution because I figured it was a 'yeah right, no way' feature. In my home-grown solution: As each item is saved, the system maintains an off-to-the-side tree of directories; by year, month, date, dir name composed from the item name. In there is a text file with a text version of the item contents and all attachments from the item. That tree is then periodically (daily) sync'd to some critical notebooks and to our file server. So in a disaster, when I'm standing in the colo with no internet -- or with no intranet web infrastructure, etc. -- that local tree of knowledge is at hand and searchable. Particularly useful in that tree have been the session log from the work done yesterday on something that has now crashed, the PDF explaining the custom kernel compilation steps to go with fancy IODrive cards, etc. --Craig Constantine, http://constantine.name On May 7, 2013, at 2:59 PM, "Lawrence K. Chen, P.Eng." <[email protected]> wrote: We use doku...partly because its supposed to still be usable in a disaster (though nobody is maintaining such copies or have ever tested such.) _______________________________________________ Discuss mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
