1. 02 Nov, 2011 2 commits
  2. 01 Nov, 2011 4 commits
  3. 31 Oct, 2011 1 commit
  4. 30 Oct, 2011 4 commits
  5. 28 Oct, 2011 4 commits
  6. 27 Oct, 2011 2 commits
    • Gary Wong's avatar
      Eschew M2Crypto.m2xmlrpclib. It dies horribly under Python 2.7. · 4b5547a2
      Gary Wong authored
      Invoke HTTPConnection or M2Crypto's HTTPSConnection directly, instead, and
      process everything through xmlrpclib's utility functions on the way in and
      out by hand.
      
      (Note that we can't use native Python's HTTPSConnection, or native
      xmlrpclib with an HTTPS URL for that matter, because Python's SSL
      support does not handle custom callbacks to retrieve passphrases,
      which we want to do.  We can't override that behaviour with Python
      code, since it lives in a binary shared library.)
      4b5547a2
    • Jonathon Duerig's avatar
      1967d584
  7. 26 Oct, 2011 2 commits
  8. 25 Oct, 2011 3 commits
  9. 24 Oct, 2011 5 commits
  10. 19 Oct, 2011 1 commit
  11. 13 Oct, 2011 5 commits
  12. 12 Oct, 2011 1 commit
  13. 11 Oct, 2011 6 commits
    • Ryan Jackson's avatar
      Merge imagezip ext4 code into extfs code · b8d79ac6
      Ryan Jackson authored
      Merge the ext4 support for imagezip into the extfs code.  There's no
      real reason to keep it separate, since ext4 is backward-compatible
      with ext3 and ext2.
      
      All of the macro definitions in extfs.c were changed from EXT2_* or
      EXT3_* to EXT4_*.  The primary reason for this is that while ext4 is
      backward compatible, the data structures have been extended and some
      of the definitions needed to change to handle them.  Some things that
      were constant before (block group descriptor sizes, for example) are
      now dynamic and must be calculated from other fields in the
      superblock.
      
      Since imagezip and frisbee don't support 64-bit block numbers, ext4
      filesystems that are larger than 2 TB (assuming 512-byte sectors) are
      not supported.  These can be detected by examining the
      feature_incompat field of the superblock.  Imagezip will fail if the
      user tries to compress one of these filesystems.
      b8d79ac6
    • Leigh Stoller's avatar
    • Leigh Stoller's avatar
      Since there is currently no way to set/clear the global bit on an · fd75a209
      Leigh Stoller authored
      image, I added it to grantimage:
      
      	boss> grantimage -a pid,osname
      
      and to revoke:
      
      	boss> grantimage -r -a pid,osname
      fd75a209
    • Mike Hibler's avatar
      Switch to using version 2.0.0 of the libntfs library for Windows images. · 5d115d2c
      Mike Hibler authored
      I ran about 50 Windows images through this to "verify" that it produces the
      same results as the old 1.7.1 library.
      5d115d2c
    • Mike Hibler's avatar
    • Mike Hibler's avatar
      Add -Z option to zero free space included in the image due to -F. · 5a02dd31
      Mike Hibler authored
      Previously, this "internal free space" was whatever garbage happened to
      be on the disk we were imaging. By zeroing, we eliminate any leakage of
      information from the source disk and also allow the image to compress just
      a tad (1-4%) better.
      
      Why isn't this the default? Eh...no good reason, other than that this whole
      squish-out-small-free-ranges-to-allow-longer-writes optimization should be
      done by the client and should not be encoded in the image.
      5a02dd31