[ 
https://issues.apache.org/jira/browse/COMPRESS-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13085525#comment-13085525
 ] 

Stefan Bodewig commented on COMPRESS-132:
-----------------------------------------

Later revisions have fixed some issues detected by findbugs, made some methods 
less public or fixed javadocs, so it has changed quite a bit.

My initial attempt to run your testcase resulted in Java spinning in an 
infinite loop, I'll investigate this further.

I tried to create a dump file on my Linux box - preferably one that has the 
same contents as src/test/resources/bla.* in Compress' trunk source tree - but 
failed so far.  Cursory reading of the manual page is obviously not enough to 
make it work.  Right now I don't know what to make of

{noformat}
stefan@birdy:~/cc$ sudo dump -v -f bla.dump test1.xml test2.xml 
  DUMP: Date of this level 0 dump: Tue Aug 16 06:34:18 2011
  DUMP: Dumping /dev/sda6 (/home (dir /stefan/cc/test1.xml)) to bla.dump
  DUMP: Excluding inode 8 (journal inode) from dump
  DUMP: Excluding inode 7 (resize inode) from dump
  DUMP: Label: none
  DUMP: Writing 10 Kilobyte records
  DUMP: mapping (Pass I) [regular files]
/dev/sda6: File not found by ext2_lookup while translating .xml
{noformat}


> Add support for unix dump files
> -------------------------------
>
>                 Key: COMPRESS-132
>                 URL: https://issues.apache.org/jira/browse/COMPRESS-132
>             Project: Commons Compress
>          Issue Type: New Feature
>          Components: Archivers
>            Reporter: Bear Giles
>            Priority: Minor
>             Fix For: 1.3
>
>         Attachments: dump-20110722.zip, dump.zip, test-z.dump, test.dump
>
>
> I'm submitting a series of patches to the ext2/3/4 dump utility and noticed 
> that the commons-compress library doesn't have an archiver for it. It's as 
> old as tar and fills a similar niche but the later has become much more 
> widely used. Dump includes support for sparse files, extended attributes, mac 
> os finder, SELinux labels (I think), and more. Incremental  dumps can capture 
> that files have been deleted.
> I should have initial support for a decoder this weekend. I can read the 
> directory entries and inode information (file permissions, etc.) but need a 
> bit more work on extracting the content as an InputStream.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to