summaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorJoey Hess <joey@gnu.kitenet.net>2009-02-24 22:56:08 -0500
committerJoey Hess <joey@gnu.kitenet.net>2009-02-24 22:56:08 -0500
commitce6f35062ed958ee13f32f95ea43262cf2eb207b (patch)
tree27a9b2f0ba6ca313fb9a5ab369b7af1b02b2dc0f /README
parent016d2771633e223b18aa5158ecd018ca05533b4a (diff)
update
Diffstat (limited to 'README')
-rw-r--r--README4
1 files changed, 4 insertions, 0 deletions
diff --git a/README b/README
index 4fdaa34..5e61d72 100644
--- a/README
+++ b/README
@@ -42,6 +42,7 @@ You can also run `etckeeper commit` by hand to commit changes.
There is also a cron job, that will use etckeeper to automatically
commit any changes to /etc each day.
+
## VCS limitations
Version Control Systems are designed as a way to manage source code, not as
@@ -181,6 +182,7 @@ Of course, it's also possible to pull changes from a server onto client
machines, to deploy changes to /etc. Once /etc is under version control, the
sky's the limit..
+
## configuration
The main configuration file is `/etc/etckeeper/etckeeper.conf`
@@ -204,6 +206,7 @@ letting it git add new files and git rm removed ones:
chmod -x /etc/etckeeper/commit.d/50vcs-commit
+
## changing VCS
By default, etckeeper uses git. If you would like to use some other VCS,
@@ -224,6 +227,7 @@ run `etckeeper uninit`, move files your new VCS will use into place,
edit `etckeeper.conf` to change the VCS setting, and finally
`etckeeper init`. This procedure is clearly only for the brave.
+
## inspiration
Two blog posts provided inspiration for techniques used by etckeeper: