1. 30 Jul, 2007 1 commit
  2. 18 Jul, 2007 1 commit
  3. 21 May, 2007 1 commit
  4. 28 Feb, 2007 1 commit
  5. 17 Nov, 2006 1 commit
  6. 03 Aug, 2006 2 commits
  7. 01 Aug, 2006 1 commit
  8. 24 May, 2006 2 commits
  9. 02 May, 2006 1 commit
  10. 11 Apr, 2006 1 commit
  11. 10 Apr, 2006 1 commit
  12. 15 Mar, 2006 1 commit
  13. 13 Mar, 2006 1 commit
  14. 03 Mar, 2006 1 commit
  15. 01 Mar, 2006 1 commit
  16. 05 Jan, 2006 1 commit
  17. 07 Dec, 2005 1 commit
  18. 28 Nov, 2005 1 commit
  19. 23 Nov, 2005 1 commit
  20. 16 Nov, 2005 1 commit
  21. 11 Nov, 2005 1 commit
  22. 03 Nov, 2005 1 commit
  23. 31 Oct, 2005 1 commit
  24. 24 Oct, 2005 1 commit
  25. 17 Oct, 2005 1 commit
  26. 04 Oct, 2005 1 commit
  27. 23 Aug, 2005 1 commit
  28. 18 Aug, 2005 1 commit
  29. 17 Aug, 2005 1 commit
    • Leigh B. Stoller's avatar
      The Emulab Knowledge Base! · 6f08c442
      Leigh B. Stoller authored
      Okay, I implemented a primitive Knowledge Base! The current contents are
      *all* the existing FAQ entries, which I entered manually. Here are the
      details.
      
      * My reason for doing this is that we need something very simple. The wiki
        is too much of a barrier, and its search capabilities are pathetic.
      
      * The search page for the Knowledge Base is:
      
      	https://www.emulab.net/kb-search.php3
      
        Fairly primitive keyword search. Turns out that mysql 4.0 has a bunch for
        really good text searching functions built in, but we run 3.23 ... so I
        had to roll it myself. So, its a simple keyword (space or comma
        separated) search, no regular expressions.
      
      * Each DB record has a "faq_entry" flag, so creating the current FAQ on the
        fly from the DB is easy. See:
      
      	https://www.emulab.net/kb-faq.php3
      
      * In reddot mode, you can add new KB entries:
      
      	https://www.emulab.net/kb-manage.php3
      
        The form is fairly obvious but here are details anyway:
      
          Section Name: Choose an existing title, or make up a new one.
          Title:        The title of the KB (or FAQ) entry.
          Faq Entry:    Check this box if the new entry should show up in the FAQ.
          X Ref Tag:    A token so you can refer to other KB entries by name,
                        instead of by its index. Within the KB entry you would
                        write: <a href=kb-show.php3?xref_tag=sometag>
          Body:         Whatever you like. I took the existing FAQ entries and
                        stuck them with no changes except for the xref_tag
                        mentioned about (since some entries referenced other
                        entries).
      
      * Once you click on sumbit, you will see the entry as it will appear to
        users, along with a submenu to Modify/Delete/Add entries. You can modify
        the current entry from that menu. Mere users do not see this menu, only
        when in reddot mode.
      
      * The intent here is that we can generate new entries really easy, right
        from email if you like (with appropriate <pre> or <xmp> tags around it).
      
      * I have added sql/knowlbase-create.sql and a makefile target to
        generate that file when creating a distribution. I also added a section
        to install/boss-install to insert the entries into the new DB.
      
      * I hooked the search function into the existing Search Documentation link.
        We know search both the Knowledge Base *and* the Documentation on doc
        searches. This probably needs a little more work to get right.
      
      * I changed a lot of faq links to be more consistent and to reference
        the proper xref_tags (#swapping instead of #UTT-34).
      6f08c442
  30. 16 Aug, 2005 1 commit
  31. 18 Jul, 2005 1 commit
  32. 13 Jul, 2005 1 commit
  33. 07 Jul, 2005 1 commit
  34. 07 Jun, 2005 1 commit
  35. 19 May, 2005 1 commit
  36. 04 Mar, 2005 1 commit
  37. 22 Feb, 2005 2 commits