summaryrefslogtreecommitdiff
path: root/faq/why-nonstd-format.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'faq/why-nonstd-format.mdwn')
-rw-r--r--faq/why-nonstd-format.mdwn17
1 files changed, 0 insertions, 17 deletions
diff --git a/faq/why-nonstd-format.mdwn b/faq/why-nonstd-format.mdwn
deleted file mode 100644
index ee07440..0000000
--- a/faq/why-nonstd-format.mdwn
+++ /dev/null
@@ -1,17 +0,0 @@
-[[!meta title="Why is Obnam not using standard file formats, such as tar or cpio?"]]
-
-The standard file formats do not support the kind of advanced features
-that Obnam is built for. For example, block level de-duplication,
-or abolishing the difference between full and incremental generations.
-It would be possible to build those features on top, say, tar, but
-it would mean the tar is just a container for odd bits of data, which
-still requires a custom program to restore from.
-
-If you're worried that you might lose your copy of Obnam, and be unable
-to restore, two points:
-
-* You can store a copy of Obnam (in source and binary versions) in your
- backup repository.
-* Obnam is free software, and it's in Debian. You're pretty much guaranteed
- to be able to find a copy and build a new binary.
-