1. 23 Oct, 2014 1 commit
  2. 22 Oct, 2014 2 commits
  3. 21 Oct, 2014 7 commits
  4. 10 Oct, 2014 1 commit
    • Mike Hibler's avatar
      Rework client-side storage scripts to semi-coexist with mkextrafs uses. · 9cf8f9c6
      Mike Hibler authored
      Broke rc.storage into two phases, local blockstores and remote blockstores.
      Setup of the former will also pick a best candidate for an old-school
      "extrafs" and put the info in /var/emulab/boot/extrafs. This will be a
      single line with one of DISK=foo, PART=foo, or FS=foo depending on whether
      it found an available full disk, disk partition, or mounted filesystem
      that we can use for mkextrafs (in the first two cases) or where we can
      mooch off of (the last). This is only used in os_mountextrafs() right now;
      i.e., I have NOT changed the mkextrafs script. So explicit invocations
      by the user could still screw things up.
      I have tested this with local blockstores and a non-nfs experiment
      on both Linux and FreeBSD to make sure the most common sharing of space
      works. I have not made any new images and I have not yet tested to make
      sure I did not break non-blockstore, non-nfs experiments (i.e., where
      we really should run mkextrafs).
      So maybe don't make any new images til I get back, or else be prepared
      to clean up after me.
  5. 08 Oct, 2014 1 commit
  6. 07 Oct, 2014 3 commits
  7. 06 Oct, 2014 2 commits
  8. 04 Oct, 2014 4 commits
  9. 03 Oct, 2014 2 commits
  10. 02 Oct, 2014 1 commit
  11. 01 Oct, 2014 2 commits
    • Mike Hibler's avatar
      Changes for a "storagehost", aka FreeNAS. · db9f4489
      Mike Hibler authored
      Compare new auth_keys with old before moving into place and otherwise
      avoid any write operations since root is mounted RO on FreeNAS.
    • Mike Hibler's avatar
      Automate the freenas setup a bit more. · d7909c5d
      Mike Hibler authored
      Use the "freenas-tarball" makefile target to create a tarball for
      installation on FreeNAS 8.3 or 9.2. The tarball must be made on the
      corresponding FreeBSD system (since FreeNAS has no installed compiler).
      To install the tarball on FreeNAS you will need to login as root and:
          cd /
          mount -o rw -u /
          mount /cfg
          tar xzf freenas-tarball.tar.gz
          unmount /cfg
          mount -o ro -u /
  12. 22 Sep, 2014 1 commit
  13. 12 Sep, 2014 1 commit
  14. 31 Jul, 2014 1 commit
    • Mike Hibler's avatar
      Hacks to get it working on APT. · e607ff1d
      Mike Hibler authored
      The mapping of old-school adX devices to new-school adaX names needs to
      be fixed. I put an enumeration of the first 8 possibilities in there,
      but it should be fixed in a more general way. Ideally by using the kernel's
      message about "adaN: previously known as adM".
  15. 30 Jul, 2014 1 commit
  16. 25 Jul, 2014 2 commits
  17. 13 Jul, 2014 1 commit
    • Mike Hibler's avatar
      Make sure we use -i for sendmail when we pipe into it. · 355f5aa8
      Mike Hibler authored
      This prevents a line with a single "." from meaning EOF to sendmail.
      How arcane!
      I discovered this when I ran a create_image and I didn't get the complete
      log mailed to me. This is because create_image did a frisbee download of an
      image with a single chunk, which of course printed out:
        Using Multicast
        Joined the team after 0 sec. ID is 1586355915. File is 1 chunks (963200 bytes)
      Fortunately, "arcane" is my middle name, so it didn't take me long to find
  18. 11 Jul, 2014 1 commit
  19. 09 Jul, 2014 2 commits
  20. 30 May, 2014 2 commits
  21. 15 May, 2014 1 commit
  22. 07 May, 2014 1 commit
    • Mike Hibler's avatar
      Introducing TMCD version 38! Returns additional "loadinfo" info. · 4a8604b1
      Mike Hibler authored
      New loadinfo returns:
      IMAGELOW, IMAGEHIGH: range of sectors covered by the image.
          This is NOT the same as what imageinfo or imagedump will show.
          For partition images, these low and high values are adjusted
          for the MBR offset of the partition in question. So when loading
          a Linux image, expect values like 6G and 12G. The intent here
          (not yet realized) is that these values will be used to construct
          an MBR/GPT on the fly, rather than using hardcode magic MBR versions.
          You can get the uncompressed size of the image with (high - low + 1).
      IMAGESSIZE: the units of the low/high values.
          Always 512 right now, may be 4096 someday.
      IMAGERELOC: non-zero if the image can be placed at an offset other
          than IMAGELOW (i.e., it can be relocated). This may or may not
          prove useful for dynamic MBR construction...we will see.
      Probably didn't need to bump the version here, but I am playing it safe.