BLU Discuss list archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Discuss] Reading Linux book
- Subject: [Discuss] Reading Linux book
- From: bogstad at pobox.com (Bill Bogstad)
- Date: Thu, 27 Mar 2014 13:33:03 -0400
- In-reply-to: <21300.20930.565265.575061@snorkack.blazemonger.com>
- References: <53343FE2.3070307@borg.org> <21300.20930.565265.575061@snorkack.blazemonger.com>
On Thu, Mar 27, 2014 at 12:28 PM, Daniel Barrett <dbarrett at blazemonger.com> wrote: > On March 27, 2014, Kent Borg wrote: >>... I always maintain a file called adminlog.txt. It is my notes, an >>old fashioned journal with dated entries of what I do to the OS. If I >>need to reproduce my config, I can "replay" this journal. > > Another idea along these lines: I maintain a separate file tree, > /usr/local/src, that contains copies of the OS files I have modified. > By keeping this sparse tree under subversion control, I can see a > complete history of the OS changes I've made at any time and > recall/revert changes pretty earily. I've migrated even from one > distro to another pretty manageably this way. > > To make things easier, I also wrote a script "srccopy" that, when run > within the /usr/local/src tree, emits "cp" commands to make life > easier. ... Some Linux distributions make available a package called etckeeper which does this for /etc. It even has hooks into the package management system for a distribution so if a package upgrade modifies config files, you have a snapshot from before it does so. Unfortunately, it doesn't do this for anything besides /etc. It would be nice if it also kept track of crontabs and a few other things in /var as well. On the spectrum from chaos to full configuration management, I think it can be helpful when you have just a few systems with little commonality. It can also be helpful when you have a team of administrators managing these kinds of systems. If the last person to touch a system checked in their changes, you can read their commit message to see both what and why info for their changes. And if they didn't, you can always run the appropriate command for the underlying source code control system (git, mercurial, bazaar, or darcs) to diff /etc against the repository to see everything they changed. (Not just what they remembered to document.) You can install etckeeper at any time and it will track changes in /etc from that point on, but doing it at initial sytem install would obviously be preferable. Bill Bogstad
- Follow-Ups:
- [Discuss] Reading Linux book
- From: smallm at panix.com (Mike Small)
- [Discuss] Reading Linux book
- References:
- [Discuss] Reading Linux book
- From: kentborg at borg.org (Kent Borg)
- [Discuss] Reading Linux book
- From: dbarrett at blazemonger.com (Daniel Barrett)
- [Discuss] Reading Linux book
- Prev by Date: [Discuss] Reading Linux book
- Next by Date: [Discuss] Quick question regarding Linux interpreter.
- Previous by thread: [Discuss] Reading Linux book
- Next by thread: [Discuss] Reading Linux book
- Index(es):