summaryrefslogtreecommitdiff
path: root/manual
diff options
context:
space:
mode:
authorLars Wirzenius <liw@liw.fi>2014-02-02 20:52:10 +0100
committerLars Wirzenius <liw@liw.fi>2014-02-02 20:52:10 +0100
commita8026dafd8077731e5a3f94f026833668ed934a3 (patch)
tree8cd46da83ec67f30cd8070e383b7fa4dd0770caf /manual
parente71f4a0f8b858300ee366614d6903dc2db26d3c8 (diff)
downloadobnam-a8026dafd8077731e5a3f94f026833668ed934a3.tar.gz
Add some text to the introduction chapter
Diffstat (limited to 'manual')
-rw-r--r--manual/010-introduction.mdwn20
1 files changed, 19 insertions, 1 deletions
diff --git a/manual/010-introduction.mdwn b/manual/010-introduction.mdwn
index 75238d70..a548efec 100644
--- a/manual/010-introduction.mdwn
+++ b/manual/010-introduction.mdwn
@@ -1,4 +1,22 @@
Introduction
============
-This is the manual for Obnam, a backup tool.
+> ... backups? did someone talk about backups? I'm sure I heard someone
+> mention backups here somewhere. Backups! BACKUPS! BACKUPS ARE AWESOME!
+
+That's a direct quote from my IRC history. I find backups quite
+interesting, particularly from an implementation point of view, and I
+may sometimes obsess about them a little bit. This is why I've written
+my own backup software. It's called Obnam. This is its manual.
+
+I'm unusual: most people find backups boring at best, and tedious most
+of the time. When I talk with people about backups, the usual reaction
+is "um, I know I should". There are a lot of reasons for this. One is
+that backups are a lot like insurance: you have to spend time, effort,
+and money up front to have any use for them. Another is that the whole
+topic is scary: you have to think about when things go wrong, and that
+puts people off. A third reason is that while there are lots of backup
+tools and methods, it's not always easy to choose between them.
+
+This manual is for the Obnam program, but it tries to be useful to
+everyone thinking about backups.