summaryrefslogtreecommitdiff
path: root/manual/en/010-introduction.mdwn
diff options
context:
space:
mode:
authorLars Wirzenius <liw@liw.fi>2014-03-29 11:43:45 +0000
committerLars Wirzenius <liw@liw.fi>2014-03-29 11:43:45 +0000
commit2dee685a1f8fb954fbeb9fd9a9d0dbb57b34b8ee (patch)
treecb629d2d27b44eeaae262fbb9975a67048b26317 /manual/en/010-introduction.mdwn
parent6d27c778c2c51129d5882c2c5adf2aeac9d36e06 (diff)
downloadobnam-2dee685a1f8fb954fbeb9fd9a9d0dbb57b34b8ee.tar.gz
Move English manual texts to en subdir
Diffstat (limited to 'manual/en/010-introduction.mdwn')
-rw-r--r--manual/en/010-introduction.mdwn22
1 files changed, 22 insertions, 0 deletions
diff --git a/manual/en/010-introduction.mdwn b/manual/en/010-introduction.mdwn
new file mode 100644
index 00000000..a548efec
--- /dev/null
+++ b/manual/en/010-introduction.mdwn
@@ -0,0 +1,22 @@
+Introduction
+============
+
+> ... 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.