https://github.com/vi/tarpipefs
Virtual write-only FUSE filesystem to create tar archives [early and hacky]
https://github.com/vi/tarpipefs
Last synced: 3 months ago
JSON representation
Virtual write-only FUSE filesystem to create tar archives [early and hacky]
- Host: GitHub
- URL: https://github.com/vi/tarpipefs
- Owner: vi
- Created: 2011-10-20T13:14:38.000Z (over 14 years ago)
- Default Branch: master
- Last Pushed: 2011-10-21T13:11:29.000Z (over 14 years ago)
- Last Synced: 2025-12-26T10:48:01.136Z (6 months ago)
- Language: C
- Homepage:
- Size: 113 KB
- Stars: 3
- Watchers: 2
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
You write to special write-only FS - it produces tar archive. Can be used for conversion of cpio archive into tar one or for creating tar archives on the fly without prior saving everything to disk.
/tmp$ mkdir m
/tmp$ tarpipefs m | gzip > ololo.tar.gz&
[1] 1337
/tmp$ cd m
/tmp/m$ mkdir qqq
/tmp/m$ mkdir qqq/lol # no mkdir -p yet
/tmp/m$ echo Hello, world > qqq/lol/hello.txt
/tmp/m$ cd ..
/tmp$ fusermount -u m
[1]+ Done tarpipefs m | gzip > ololo.tar.gz
/tmp$ tar -tvf ololo.tar.gz
drwxrwxr-x root/root 0 2011-10-21 16:11 qqq
drwxrwxr-x root/root 0 2011-10-21 16:11 qqq/lol
-rwxrwxr-x root/root 13 2011-10-21 16:11 qqq/lol/hello.txt
This version is early and hacky:
1. Using tar implementation extracted from Git;
2. No chmod, no dates for directories/symlinks, no device nodes;
3. Can't do "mkdir -p";
4. Each single file is kept in memory;
5. Not tested much;