Up to [cvs.NetBSD.org] / pkgsrc / sysutils / bup
Request diff between arbitrary revisions
Default branch: MAIN
Revision 1.3 / (download) - annotate - [select for diffs], Tue Dec 31 11:03:12 2013 UTC (2 years, 6 months ago) by wiz
CVS Tags: pkgsrc-2016Q2-base, pkgsrc-2016Q2, pkgsrc-2016Q1-base, pkgsrc-2016Q1, pkgsrc-2015Q4-base, pkgsrc-2015Q4, pkgsrc-2015Q3-base, pkgsrc-2015Q3, pkgsrc-2015Q2-base, pkgsrc-2015Q2, pkgsrc-2015Q1-base, pkgsrc-2015Q1, pkgsrc-2014Q4-base, pkgsrc-2014Q4, pkgsrc-2014Q3-base, pkgsrc-2014Q3, pkgsrc-2014Q2-base, pkgsrc-2014Q2, pkgsrc-2014Q1-base, pkgsrc-2014Q1, HEAD
Changes since 1.2: +1 -1 lines
Diff to previous 1.2 (colored)
Update to 0.25: This release includes a veritable ton of work, but the biggest change is probably the addition of real (YMMV) metadata support, including hardlinks, and the ability to directly save/restore trees without tar and split/join. See bup-index(1), bup-save(1), bup-restore(1), bup-meta(1), bup-xstat(1), and the updated "Using bup" section in the README. Note though, that the metadata support really is our first pass, and there are already things that we know need fixing (i.e. better support for cross-filesystem-type save/restore (too noisy), etc.). And check the "Notes on ..." sections in the README for some platform-specific limitations. An incomplete list of other notable changes since 0.24b: - bup will no longer create ~/.bup implicitly; "bup init" is required. - "bup split" now supports a compression-level option (-#). - "bup tag" now supports "-f". - "bup ls" now supports "-a", "-s", "--human-readable", etc., and reports more information. - "bup web" now supports "--human-readable". - "bup import-rdiff-backup" has been added. - "bup cat-file" has been added. - The default "/usr" installation prefix can be overridden via PREFIX. - Python 2.4 is no longer supported. And we have at least one (likely minor) known issue: - *Very* large (i.e. probably greater than MAX_LONG), or negative filesystem timestamps may not always be handled correctly at the moment. We'll fix that soon. And related -- some of the tests may fail on FUSE filesystems.
Revision 1.2 / (download) - annotate - [select for diffs], Sun Apr 7 20:49:41 2013 UTC (3 years, 3 months ago) by rodent
CVS Tags: pkgsrc-2013Q4-base, pkgsrc-2013Q4, pkgsrc-2013Q3-base, pkgsrc-2013Q3, pkgsrc-2013Q2-base, pkgsrc-2013Q2
Changes since 1.1: +21 -40 lines
Diff to previous 1.1 (colored)
Edited DESCR in the case of: File too long (should be no more than 24 lines). Line too long (should be no more than 80 characters). Trailing empty lines. Trailing white-space. Trucated the long files as best as possible while preserving the most info contained in them.
Revision 188.8.131.52 / (download) - annotate - [select for diffs] (vendor branch), Mon May 16 13:52:56 2011 UTC (5 years, 2 months ago) by wiz
CVS Tags: pkgsrc-2013Q1-base, pkgsrc-2013Q1, pkgsrc-2012Q4-base, pkgsrc-2012Q4, pkgsrc-2012Q3-base, pkgsrc-2012Q3, pkgsrc-2012Q2-base, pkgsrc-2012Q2, pkgsrc-2012Q1-base, pkgsrc-2012Q1, pkgsrc-2011Q4-base, pkgsrc-2011Q4, pkgsrc-2011Q3-base, pkgsrc-2011Q3, pkgsrc-2011Q2-base, pkgsrc-2011Q2, pkgsrc-20110516
Changes since 1.1: +0 -0 lines
Diff to previous 1.1 (colored)
Initial import of bup-0.24b. bup is a program that backs things up. bup has a few advantages over other backup software: It uses a rolling checksum algorithm (similar to rsync) to split large files into chunks. The most useful result of this is you can backup huge virtual machine (VM) disk images, databases, and XML files incrementally, even though they're typically all in one huge file, and not use tons of disk space for multiple versions. It uses the packfile format from git (the open source version control system), so you can access the stored data even if you don't like bup's user interface. Unlike git, it writes packfiles directly (instead of having a separate garbage collection / repacking stage) so it's fast even with gratuitously huge amounts of data. bup's improved index formats also allow you to track far more filenames than git (millions) and keep track of far more objects (hundreds or thousands of gigabytes). Data is "automagically" shared between incremental backups without having to know which backup is based on which other one - even if the backups are made from two different computers that don't even know about each other. You just tell bup to back stuff up, and it saves only the minimum amount of data needed. You can back up directly to a remote bup server, without needing tons of temporary disk space on the computer being backed up. And if your backup is interrupted halfway through, the next run will pick up where you left off. And it's easy to set up a bup server: just install bup on any machine where you have ssh access. Bup can use "par2" redundancy to recover corrupted backups even if your disk has undetected bad sectors. Even when a backup is incremental, you don't have to worry about restoring the full backup, then each of the incrementals in turn; an incremental backup acts as if it's a full backup, it just takes less disk space. You can mount your bup repository as a FUSE filesystem and access the content that way, and even export it over Samba.
Revision 1.1 / (download) - annotate - [select for diffs], Mon May 16 13:52:56 2011 UTC (5 years, 2 months ago) by wiz
This form allows you to request diff's between any two revisions of a file. You may select a symbolic revision name using the selection box or you may type in a numeric name using the type-in text box.