1. 04 Sep, 2013 20 commits
  2. 22 Jul, 2013 1 commit
  3. 09 Jul, 2013 2 commits
  4. 05 Jul, 2013 1 commit
    • Robert Ricci's avatar
      Add clone URLs to commit messages · c1f3e90a
      Robert Ricci authored
      ... seems useful enough that we ought to just do it by default.
      
      Works fine on our server because the hostname is set right and the
      path works out fine. Might work less well on servers configured
      differently.
      c1f3e90a
  5. 11 Feb, 2013 1 commit
  6. 24 Sep, 2012 1 commit
    • Eric Eide's avatar
      Replace license symbols with {{{ }}}-enclosed license blocks. · 6df609a9
      Eric Eide authored
      This commit is intended to makes the license status of Emulab and
      ProtoGENI source files more clear.  It replaces license symbols like
      "EMULAB-COPYRIGHT" and "GENIPUBLIC-COPYRIGHT" with {{{ }}}-delimited
      blocks that contain actual license statements.
      
      This change was driven by the fact that today, most people acquire and
      track Emulab and ProtoGENI sources via git.
      
      Before the Emulab source code was kept in git, the Flux Research Group
      at the University of Utah would roll distributions by making tar
      files.  As part of that process, the Flux Group would replace the
      license symbols in the source files with actual license statements.
      
      When the Flux Group moved to git, people outside of the group started
      to see the source files with the "unexpanded" symbols.  This meant
      that people acquired source files without actual license statements in
      them.  All the relevant files had Utah *copyright* statements in them,
      but without the expanded *license* statements, the licensing status of
      the source files was unclear.
      
      This commit is intended to clear up that confusion.
      
      Most Utah-copyrighted files in the Emulab source tree are distributed
      under the terms of the Affero GNU General Public License, version 3
      (AGPLv3).
      
      Most Utah-copyrighted files related to ProtoGENI are distributed under
      the terms of the GENI Public License, which is a BSD-like open-source
      license.
      
      Some Utah-copyrighted files in the Emulab source tree are distributed
      under the terms of the GNU Lesser General Public License, version 2.1
      (LGPL).
      6df609a9
  7. 01 Aug, 2012 1 commit
    • Mike Hibler's avatar
      Support 64-bit FreeBSD on the server side. · 9036d314
      Mike Hibler authored
      NOTE: currently only for FreeBSD 7.3 installs because that is the only
      set of boss/ops/fs packages I have built so far!
      
      This mostly involved minor changes to event agents. Too often we were
      passing a pointer to a "long" to *get_int32, which on a 64-bit x86 OS would
      fill the wrong half of a 64-bit variable. There was also one instance of
      TCL code that had to be tweaked to account for 32- vs 64-bit.
      
      These changes also required regeneration of SWIG stubs and an ugly change
      to the SWIG generated code to use va_copy rather than direct assignment in
      a couple of places.
      
      Also related to SWIG is ensuring that the components that go into the
      perl/python stub .so files are built with PIC. The amd64 linker requires
      this.
      
      The meta-ports had to be changed to reflect that linuxthreads and
      ulsshxmlrpcpp don't work on amd64. The former had little effect as we
      had mostly eliminated uses of linuxthreads already. The one thing that
      did change was that we do not build nfstrace on amd64 (and we don't
      currently use this anyway). Removing ulsshxmlrpcpp required switching
      to the new event scheduler (event/new_sched) that Ryan did awhile back.
      Note that it is only "new" in the sense that it uses a standard XMLRPC
      package, there should be no functional differences. However, to be safe
      we only use new_sched as the standard scheduler on 64-bit server installs.
      
      Finally, added support to elabinelab setup to do a 64-bit server install.
      Just specify FBSD73-64-STD as the boss/ops/fs osid and rc.mkelab should
      do the rest.
      
      That is pretty much it other than some random nits here and there.
      9036d314
  8. 01 Jun, 2012 2 commits
    • Robert Ricci's avatar
      Remove a comment that's no longer true · edf8442c
      Robert Ricci authored
      edf8442c
    • Robert Ricci's avatar
      Fix summary for merge commits · 8e634629
      Robert Ricci authored
      Problem before was that I was using 'git log' of the commit and
      its parent, which doesn't work as I intended when there's more than
      one parent. Instead, use 'git show -s', which is helpfully not
      documented in the manpage for git-show, but instead the manpage for
      git-shortlog
      8e634629
  9. 08 May, 2012 1 commit
  10. 03 May, 2012 1 commit
  11. 01 May, 2012 1 commit
  12. 30 Apr, 2012 1 commit
    • Mike Hibler's avatar
      First cut at FreeBSD 9.0 support. · 1f83c9c6
      Mike Hibler authored
      Upgrade to perl 5.12 means no more "suidperl" (setuid perl scripts).
      So we now have yet another little wrapper (security/runsuid.c) which
      runs suid and whose sole function is to exec the perl script of the
      same name in the /usr/testbed/suidbin directory. So a formerly setuid
      perl script install now goes like:
        create /usr/testbed/sbin/mkproj as a symlink to /usr/testbed/libexec/runsuid
        install real mkproj perl script in /usr/testbed/suidbin/mkproj
      When the setuid-wrapper is invoked under the name "mkproj" it execs
      /usr/testbed/suidbin/mkproj. We could almost use sudo for this purpose
      instead (see security/sudoers.in) but sudo loses one of the groups in
      the group list.
      
      /usr/include/utmp.h is gone in FreeBSD 9.0. In most places we nevered
      needed it, but in the one case that did (tg source), it just used a
      couple of the constants exposed (UT_*) and not the struct, so I just
      hardwired values for the constants.
      
      The usual tweakage to the install stuff to reflect yet another set of
      packages!
      1f83c9c6
  13. 27 Apr, 2012 1 commit
  14. 17 Apr, 2012 6 commits
    • Robert Ricci's avatar
      Bugfix: make sure to initialize the summary · 3c832453
      Robert Ricci authored
      3c832453
    • Robert Ricci's avatar
      Support options with '=' in them · b31df8b4
      Robert Ricci authored
      b31df8b4
    • Robert Ricci's avatar
      Fix for older versions of git · 1c0f4a5f
      Robert Ricci authored
      'git revparse --show-toplevel' is a nice way to get a path to the repo
      no matter where you are in it, but unfortunately, older versions don't
      have it. So, go back to `pwd`
      1c0f4a5f
    • Robert Ricci's avatar
      Support patches down at the bottom of gitmail · 78669f67
      Robert Ricci authored
      New 'includepatches' option puts a seperate set of patches after all
      commit messages. 'patchstyle' allows you to set 'word' to get word
      diffs. 'patchsizelimit' (default 1,000) omits patches with more than
      this many lines. 'maxpatches' (default 20) skips patch generation if
      there are more than this many commits in the message.
      78669f67
    • Robert Ricci's avatar
      Bug fix: fix prototype for commit_mail() · 720403f4
      Robert Ricci authored
      720403f4
    • Robert Ricci's avatar
      Add host and path headers to gitmail · 05a4a77b
      Robert Ricci authored
      For now, these go into headers (X-Git-Repo-Host and X-Git-Repo-Path)
      Might consider moving them to the body of the mail at some point.
      
      Note that I *don't* attempt to figure out the actual 'URL' for the
      repo, since that is *not* necessarily automatically derivable: eg.
      it might be any of ssh,git, or http protocols, and the path (esp.
      for git: and http:) might not match the path in the filesystem. So
      this suggests that wat goes into the body of the mail ought to be
      set with a config variable.
      05a4a77b