From 8fe1a635afc45c78c424f82b5114544ece66cff4 Mon Sep 17 00:00:00 2001 From: eugen Date: Thu, 21 Nov 2019 20:29:20 +0000 Subject: Added a comment --- .../comment_3_ab42e31ff116bf56dca6cdff9bba2d29._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/forum/etckeeper_made_obsolete_by_propellor__63__/comment_3_ab42e31ff116bf56dca6cdff9bba2d29._comment (limited to 'doc') diff --git a/doc/forum/etckeeper_made_obsolete_by_propellor__63__/comment_3_ab42e31ff116bf56dca6cdff9bba2d29._comment b/doc/forum/etckeeper_made_obsolete_by_propellor__63__/comment_3_ab42e31ff116bf56dca6cdff9bba2d29._comment new file mode 100644 index 00000000..eb8abfb3 --- /dev/null +++ b/doc/forum/etckeeper_made_obsolete_by_propellor__63__/comment_3_ab42e31ff116bf56dca6cdff9bba2d29._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="eugen" + avatar="http://cdn.libravatar.org/avatar/7e7e5700d7017735fd00c2dfcd3f91e4" + subject="comment 3" + date="2019-11-21T20:29:20Z" + content=""" +Indeed, I can see how etckeeper provides a very easy way to check exactly what has changed to /etc (also) after a propellor spin. When I'm manually editing an /etc file I know what the changes are, but not so when a tool does it for me. So, it's important to verify, for example, that propellor did indeed what I *thought* I told it to do (not sure if propellor has an option to report the /etc changes it did). + +By using both etckeeper and propellor, which one do you consider to have the authoritative status (power?) over /etc? Do you still manually edit /etc files? +"""]] -- cgit v1.2.3