1. 16 Aug, 2005 1 commit
  2. 15 Aug, 2005 1 commit
    • Leigh B. Stoller's avatar
      The bulk of the mailman support. Still not turned on by default (cause · a64593f3
      Leigh B. Stoller authored
      Jay has "comments"), but I do not want it hanging around in my source
      tree. Here is my mail message:
      * The "My Mailing Lists" is context sensitive (copied from Tim's
        changes to the My Bug Databases). It takes you to the *archives* for
        the current project (or subgroup) list. Or it takes you to your
        first joined project.
      * The showproject and showgroup pages have direct links to the project
        and group specific archives. If you are in reddot mode, you also
        get a link to the admin page for the list. Note that project and
        group leaders are just plain members of these lists.
      * The interface to create a new "user" list is:
        We do not store the password, but just fire it over in the list
        creation process.
        Anyone can create their own mailing lists. They are not associated
        with projects, but just the person creating the list. That person
        is the list administrator and is given permission to access the
        configuration page.
        This page is not hooked in yet; not sure where.
      * Once you have your own lists, you user profile page includes a link
        in the sub menu: Show Mailman Lists. From this page you can delete
        lists, zap to the admin page, or change the admin password (which is
        really just a subpage of the admin page).
      * As usual, in reddot mode you can mess with anyone else's mailman lists,
        (via the magic of mailman cookies).
      * Note on cross machine login. The mailman stuff has a really easy way
        to generate the right kind of cookie to give users access. You can
        generate a cookie to give user access, or to the admin interface for
        a list (a different cookie). Behind the scenes, I ssh over and get
        the cookie, and set it in the user's browser from boss. When the
        browser is redirected over to ops, that cookie goes along and gives
        the user the requested access. No passwords need be sent around,
        since we do the authentication ourselves.
  3. 13 Aug, 2005 1 commit
  4. 12 Aug, 2005 3 commits
    • Mike Hibler's avatar
    • Mike Hibler's avatar
      Ugh! When reading a line, go ahead and return if the string we have · c1c24bfa
      Mike Hibler authored
      read matches the prompt, i.e., don't wait to get a newline.  With the
      new power controller on the rocketport muxes on a pc1500 tipserver,
      even though we send two newlines, we just get back a single prompt
      with no newline.  This would cause us to hang forever waiting for the
      Note that it did not do this on the same RPCs with the same muxes on
      our ops node (a pc3000).  This could be a bad sign for things to come...
    • Kevin Atkinson's avatar
      · daa2966a
      Kevin Atkinson authored
      Added new script "linesofcode2.pl" which is like ""linesofcode.sh"
      but uses a ".loc-ignore" file instead of lots of egreps.  Also added
      a ".loc-ignore" file in the root directory so that the results from
      the two scripts are basically the same.  The only difference is that
      the new script also ignores files starting with "." which I assume
      is a desirable behavior.
  5. 11 Aug, 2005 1 commit
  6. 10 Aug, 2005 2 commits
  7. 09 Aug, 2005 2 commits
  8. 08 Aug, 2005 9 commits
  9. 04 Aug, 2005 6 commits
  10. 03 Aug, 2005 4 commits
  11. 01 Aug, 2005 2 commits
  12. 29 Jul, 2005 2 commits
    • Timothy Stack's avatar
      · cb7801fb
      Timothy Stack authored
      Fix the race between loading a mote and rebooting its host stargate.
      	* db/libdb.pm.in: Add TBNodeSubNodes function which returns the
      	list of subnodes for a given node.
      	* mote/tbuisp.in: Don't reboot the stargate anymore after loading
      	the attached mote.  The problem with the radio not working after
      	the upload should be fixed now.
      	* tbsetup/libreboot.pm.in: Check if a node's subnodes are being
      	reloaded.  If so, try to wait until they reach ISUP before
      	actually doing the reboot.
      	* tbsetup/os_setup.in: Do not skip the ISUP wait for subnodes that
      	are imageable (like motes), otherwise their allocstates are not
      	updated correctly.  Remove the robot-specific hack that	assumed
      	tbuisp would do the reboot if the attached mote was being reloaded.
    • Kirk Webb's avatar
      · b9dc258e
      Kirk Webb authored
      Bump date for papers menu item (noticed by Eric).
  13. 28 Jul, 2005 6 commits