1. 01 Feb, 2018 1 commit
  2. 16 Nov, 2017 1 commit
    • David Johnson's avatar
      Add support for Arch Linux. · f797a96b
      David Johnson authored
      This is pretty minimal "support", but it is working.  I have some
      uncommitted fixes for event/linktest/iperf, however, as mentioned in
      issue #351.
      f797a96b
  3. 20 Oct, 2017 1 commit
  4. 29 Aug, 2017 1 commit
  5. 27 Apr, 2017 1 commit
    • David Johnson's avatar
      Fix broken emptiness check of WINDOWS_KEY_7PRO_X86. · fd60aa4c
      David Johnson authored
      This happens to be important right now because if there is a product
      key specified, a little sed command generates a new .in file, in the src
      dir, from a template... and thus you cannot have a read-only copy of the
      src tree even if building in a separate obj dir.  Have an ro src tree is
      helpful for Docker image emulabization, and it's a good thing anyway.
      fd60aa4c
  6. 30 Mar, 2017 1 commit
  7. 15 Jul, 2016 1 commit
    • David Johnson's avatar
      Add Ubuntu 16 support (both x86 and aarch64). · a82f9ac8
      David Johnson authored
      This is all pretty vanilla atop the Ubuntu 15 support.  Just new
      metadata files (passwd,group,shadow,gshadow); pulling in Kirk's Centos
      ntp.service; and an important tweak to the dhclient exit hook.
      
      resolvconf seems to be more prominently featured in Ubuntu 16, and it
      has a dhclient exit hook to alert the resolvconf stuff (so it can alert
      others) when nameservers change.  However, that hook somehow breaks DNS
      for our exit hook right as it calls sethostname.dhclient .  So to fix
      this, I just added a check for /sbin/resolvconf in the exit hook, and if
      that exists, we use the same elabinelab DNS-problem-avoidance strategy
      of manually invoking the tmcc binary with getbossinfo, so that the perl
      tmcc stuff doesn't hang in sethostname.client .  That works great.
      
      aarch64 (ubuntu16-ms) support is a very simple overlay atop the regular
      ubuntu16 dir; it only adds the special uboot boot.scr modification file
      we need.
      a82f9ac8
  8. 27 May, 2016 1 commit
  9. 21 Mar, 2016 1 commit
    • Kirk Webb's avatar
      Reorg mobile networking support files/install · f6802650
      Kirk Webb authored
      * Move common and client-side stuff to the clientside tree
      
      * Update autconf configure scripts:
      
      This commit bumps the version of the top-level auto-generated
      script from 2.68 to 2.69.
      f6802650
  10. 25 Jun, 2015 1 commit
  11. 14 May, 2015 1 commit
    • David Johnson's avatar
      Ubuntu 15 support. · 2baf7655
      David Johnson authored
      Similar to Ubuntu 14, but new and different UIDs, and...
      
      systemd!  systemd has made it into Ubuntu.  This affects our control net
      discovery.  Our /etc/network/interfaces hack marks eth[0-9] as "auto".
      New Ubuntu versions have systemd (or upstart, if your Ubuntu 15 uses
      that -- our images will not) job that waits for any interfaces marked
      auto to come up, and doesn't timeout for 2 mins.  This doesn't work for
      us, because our use of auto is abuse :).
      
      So, we enter a new level of abuse.  We change the systemd unit
      dependencies, making the network-online.target service want (depend on)
      our special ifup-wait-emulab-cnet.service (which looks for /run/cnet to
      get written), instead of on ifup-wait-all-auto.service.  This means
      network-online.target happens as soon as the control net is up, which is
      the primary thing we're concerned about.
      
      Now, if experimenters would ever add their own special "auto" interfaces
      to /etc/network/interfaces, the rest of the startup scripts that depend
      on network-online.target could possibly race (although you would think
      that our control net discovery will be slower than any static
      configuration...).
      
      But for now, this solution appealed more that "faking" that eth[0-9] are
      all up by writing the right files --- or by finding a better mechanism
      instead of abusing "auto".
      2baf7655
  12. 12 May, 2015 1 commit
  13. 13 Apr, 2015 1 commit
  14. 17 Mar, 2015 2 commits
    • Mike Hibler's avatar
      Even more nits. · 58c30eb2
      Mike Hibler authored
      58c30eb2
    • Mike Hibler's avatar
      FreeBSD 11 (aka current) support. · 460cc8bf
      Mike Hibler authored
      Mostly I just wanted to test "the latest" FBSD kernel on Apt
      so see if anything done recently would help with the hanging
      console problem on the R320s (newer kernels actually only hang
      for about 10 seconds and drop around 500 chars when they probe
      the ethernet interfaces--this is better than it was).
      
      While in there, I just went ahead and did the client side,
      mostly ifdefs in the makefiles.
      460cc8bf
  15. 26 Jan, 2015 1 commit
    • Mike Hibler's avatar
      New blockstore event agent. · e8de812f
      Mike Hibler authored
      Currently only used to shutdown remote blockstores in advance of a
      swapout (per-experiment event: objtype=="BSTORE", objname=="rem-bstore",
      eventtype=="STOP").
      e8de812f
  16. 23 Jan, 2015 1 commit
  17. 17 Dec, 2014 1 commit
  18. 25 Nov, 2014 1 commit
  19. 02 Oct, 2014 1 commit
    • Mike Hibler's avatar
      FreeNAS 9 support, "improved" FreeNAS 8 support. · 23447d73
      Mike Hibler authored
      A clientside top-level "gmake freenas-tarball" will build everything and
      construct an appropriate tarball. You must either build on FreeBSD 8.3 or
      FreeBSD 9.2, depending on the version of FreeNAS you are targetting.
      
      This cannot be done native on the FreeNAS box! In part because there is
      no compiler there, but even if there was, the install target would wreak
      havoc on a full root filesystem; it assumes it is working on a skeleton
      FS with just the Emulab stuff in it.
      
      Mostly this commit is grotesque Makefile hacking due to our tragic
      client-side tmcc OS-specific directory structure. Hey, don't blame me!
      It was, um...okay DO blame me...
      23447d73
  20. 18 Sep, 2014 1 commit
    • Mike Hibler's avatar
      Initial support for ARM-64 clientside. · db6f3b96
      Mike Hibler authored
      Clientside builds on HP Moonshot, haven't tried running anything.
      
      The most significant change here is moving to autoconf 2.69, which
      is the first that supports "aarch64". This required replacing the
      scripts in autoconf/ and significant textual changes to configure.in
      files.
      
      Other than that, it was all lint.
      db6f3b96
  21. 07 Aug, 2014 1 commit
  22. 31 Jul, 2014 1 commit
  23. 08 Jan, 2014 1 commit
    • Kirk Webb's avatar
      Bag of goodies to support a CentOS 6 image. · 30a32df0
      Kirk Webb authored
      A closer inspection of the 'fedora' case that I had been using revealed
      that a few changes needed to be made for the CentOS 6 environment.  This
      is loosely based on the fedora15 case, but stripped down and cleaned up
      some.
      30a32df0
  24. 29 Aug, 2013 1 commit
  25. 23 May, 2013 1 commit
  26. 03 Dec, 2012 2 commits
  27. 05 Nov, 2012 1 commit
  28. 11 Oct, 2012 1 commit
  29. 25 Sep, 2012 1 commit
  30. 07 Sep, 2012 1 commit
  31. 20 Aug, 2012 2 commits
  32. 22 Jun, 2012 1 commit
  33. 01 May, 2012 2 commits
  34. 26 Apr, 2012 1 commit
  35. 19 Apr, 2012 1 commit
    • Mike Hibler's avatar
      Define some additional configure vars in the clientside configure. · 055bbb7c
      Mike Hibler authored
      Against my better judgement, use configure to set some vars in clientside
      scripts. I try to avoid this to keep our client images from becoming Utah
      specific.
      
      This is specifically for run_linktest.pl.in, which is installed on both
      ops and nodes. I could fix it to not use configure vars on nodes, but that
      would break its primary use on ops.
      
      OTOH, I fixed elab_linktest.pl.in to not use configure variables, since
      it only runs on nodes.
      055bbb7c
  36. 20 Mar, 2012 1 commit