[
https://issues.apache.org/jira/browse/COMPRESS-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13085707#comment-13085707
]
Bear Giles commented on COMPRESS-132:
-------------------------------------
I used a loopback filesystem
# truncate -s 4g test1fs (creates large sparse file)
# losetup /dev/loop7 test1fs
# mkfs.ext2 /dev/loop7
# losetup -d /dev/loop7
# mount -oloopback test1fs /mnt
# (populate partition with test data)
# dump ... (note: mount will probably mount on a different loopback
device)
(or something like that - I may have various arguments reversed)
> 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
