3 ms·

I'm curious- Was this ever released anywhere? I can see you mentioned a multitape layer in tarsnap, but I'm curious if you released a standalone version of the

by e1ven 17y ago

I'm curious- Was this ever released anywhere? I can see you mentioned a multitape layer in tarsnap, but I'm curious if you released a standalone version of the archiving tool. Hopefully you don't view bup as competition for tarsnap. There's a lot of situations such as Xen backups, where I really want to dump things to a local backup machine, then off to tape- I'm not interested in any form of hosted service, but tools that make binary diffs efficient and easy would certainly be welcome. It might also be interesting to expand bup (or multitape/multitar, if it is public), to use the method described in your thesis paper- http://www.daemonology.net/bsdiff/ http://www.daemonology.net/bsdiff/ I apologize for potentially touching on a delicate subject. I certainly wouldn't want to come across as advising someone to use your theories to steal food out of your mouth, but local v. remote bkp seem to be sufficiently different markets.

cperciva 17y ago
Was this ever released anywhere? No; I never really considered it to be useful except as a step towards Tarsnap. Hopefully you don't view bup as competition for tarsnap Not really, no. Of course, the author could follow the same path as I took, of integrating this with tar code, and end up producing a competitor to Tarsnap. It might also be interesting to expand bup (or multitape/multitar, if it is public), to use the method described in your thesis paper- http://www.daemonology.net/bsdiff/* http://www.daemonology.net/bsdiff/* That doesn't really work. Binary diffs are about comparing old and new files to produce a small patch; snapshotting compares the new file to a list of parts of the old file*. It's a tradeoff between needing more local state (with binary diffs you need to have the old file to compare against) and having larger deltas (with snapshotting, you have a new chunk even if only part of it changed). That said, my experience with bsdiff was certainly useful in terms of shaping how I think about efficient deltas and compression, so even though none of the ideas translate directly it definitely helped me in writing Tarsnap.
- pasbesoin 17y ago
  Nit: That URL needs cleansing by adding a space between it and the trailing asterisk when submitting (a problem with HN's parsing of '❄blah❄' markup that I've noticed/noted before; I seem to recall the breakage scenario as occurring when the markup is used at the end of a paragraph). Test case: The last word of this sentence -- sans any training punctuation -- has the markup Err... nope: It looks like it's only when wrapping a URL in the markup http://www.google.com/* http://www.google.com/* a̶n̶d̶/̶o̶r̶ ̶w̶h̶e̶n̶ ̶t̶h̶a̶t̶ ̶U̶R̶L̶ ̶i̶s̶ ̶a̶t̶ ̶t̶h̶e̶ ̶e̶n̶d̶ ̶o̶f̶ ̶a̶ ̶p̶a̶r̶a̶g̶r̶a̶p̶h̶ ̶̶h̶t̶t̶p̶:̶/̶/̶w̶w̶w̶.̶g̶o̶o̶g̶l̶e̶.̶c̶o̶m̶/̶̶ Looks like I need to break some continuing italicization now. Trying the same sort of markup but also wrapping a trailing space produces http://www.google.com/ http://www.google.com/ , which is better.. ---- Where ❄ represents an asterisk.

by e1ven 17y ago

cperciva 17y ago

Was this ever released anywhere? No; I never really considered it to be useful except as a step towards Tarsnap. Hopefully you don't view bup as competition for tarsnap Not really, no. Of course, the author could follow the same path as I took, of integrating this with tar code, and end up producing a competitor to Tarsnap. It might also be interesting to expand bup (or multitape/multitar, if it is public), to use the method described in your thesis paper- http://www.daemonology.net/bsdiff/* http://www.daemonology.net/bsdiff/* That doesn't really work. Binary diffs are about comparing old and new files to produce a small patch; snapshotting compares the new file to a list of parts of the old file*. It's a tradeoff between needing more local state (with binary diffs you need to have the old file to compare against) and having larger deltas (with snapshotting, you have a new chunk even if only part of it changed). That said, my experience with bsdiff was certainly useful in terms of shaping how I think about efficient deltas and compression, so even though none of the ideas translate directly it definitely helped me in writing Tarsnap.

pasbesoin 17y ago
Nit: That URL needs cleansing by adding a space between it and the trailing asterisk when submitting (a problem with HN's parsing of '❄blah❄' markup that I've noticed/noted before; I seem to recall the breakage scenario as occurring when the markup is used at the end of a paragraph). Test case: The last word of this sentence -- sans any training punctuation -- has the markup Err... nope: It looks like it's only when wrapping a URL in the markup http://www.google.com/* http://www.google.com/* a̶n̶d̶/̶o̶r̶ ̶w̶h̶e̶n̶ ̶t̶h̶a̶t̶ ̶U̶R̶L̶ ̶i̶s̶ ̶a̶t̶ ̶t̶h̶e̶ ̶e̶n̶d̶ ̶o̶f̶ ̶a̶ ̶p̶a̶r̶a̶g̶r̶a̶p̶h̶ ̶̶h̶t̶t̶p̶:̶/̶/̶w̶w̶w̶.̶g̶o̶o̶g̶l̶e̶.̶c̶o̶m̶/̶̶ Looks like I need to break some continuing italicization now. Trying the same sort of markup but also wrapping a trailing space produces http://www.google.com/ http://www.google.com/ , which is better.. ---- Where ❄ represents an asterisk.