summaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
authorJohn Hackett <john.hackett@bytemark.co.uk>2015-02-20 18:41:54 +0000
committerJohn Hackett <john.hackett@bytemark.co.uk>2015-02-20 18:41:54 +0000
commit4a66fec4b42af038c9fffc25396fe6b5fc177e56 (patch)
tree8dbbcde96636ebe6d3da61b86ba013123b8a7602 /README.md
parent613d6b891f842057187f0b1202438851893e5a60 (diff)
Updated install instructions slightly, found an odd parse error
Diffstat (limited to 'README.md')
-rwxr-xr-xREADME.md6
1 files changed, 4 insertions, 2 deletions
diff --git a/README.md b/README.md
index aef1dc4..816653f 100755
--- a/README.md
+++ b/README.md
@@ -43,6 +43,8 @@ for your discs:
mkfs.btrfs /dev/my_volume_group/byteback
echo '/dev/my_volume_group/byteback /byteback btrfs compress 0 0' >>/etc/fstab
mount /byteback
+ chown byteback /byteback
+ chmod u+w /byteback
Finally, before setting up the client, add
@@ -56,13 +58,13 @@ Clients are machines that need to be backed up. Assuming you can log into
the remote 'byteback' user with a password or administrative key, you only
need to type one command on the client to set things going:
- byteback-setup-client --destination byteback@mybackuphost.net:
+ sudo byteback-setup-client --destination byteback@mybackuphost.net:
If this goes OK, you are ready to start backing up. I'd advise taking the
first backup manually to make sure it goes as you expect. Type this on the
client to start and watch the backup.
- byteback-backup --verbose
+ sudo byteback-backup --verbose
Configuring byteback-backup
---------------------------