Tar is just a portable read-only filesystem format so why does ipfs tar add/cat import into and export from a special tar dag instead of just using unixfs (also a portable read-only filesystem format)?
The text was updated successfully, but these errors were encountered:
Because that way you get really good dedup within tars. (and can even mount tars). it's an example datastructure. this is pre-work towards car, an archive fmt we're making
Sorry, my question was unclear. Why not extract the tar into unixfs. That is, why write another merkeldag format for read-only filesystems when you already have one.
Is this to work around the lack of metadata (permissions etc.) storage in unixfs?
precisely-- it was a quick hack meanwhile we work on unixfs. but it ended up being pretty useful
it's also useful to have native support for tars, so that in the future we can import regular unix filesystems and yet dedup tars and look into them. And still be able to reproduce the exact same fs on the way out.
Stebalien commentedOct 5, 2015
Tar is just a portable read-only filesystem format so why does
ipfs tar add/catimport into and export from a special tar dag instead of just using unixfs (also a portable read-only filesystem format)?The text was updated successfully, but these errors were encountered: