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: Fri, 28 Mar 2014 16:31:15 -0400
- In-reply-to: <21301.35222.407241.313358@snorkack.blazemonger.com>
- References: <li68urvl7w0.fsf@panix5.panix.com> <21301.35222.407241.313358@snorkack.blazemonger.com>
On Fri, Mar 28, 2014 at 10:39 AM, Daniel Barrett <dbarrett at blazemonger.com> wrote: > On March 27, 2014, Mike Small quoth: >> First, a big warning: By checking /etc into version control, you are >> creating a copy of files like /etc/shadow that must remain >> secret. [...] > > This is one reason I use the "sparse tree" method I mentioned > yesterday, which versions only the files that one cares about. I don't > see much reason to version /etc/shadow or other data files that are > usually updated by tools and rarely modified by text editing. The problem I see with this is that it is possible for those rare modifications to break things in ways that aren't apparent for some time. If you didn't track those changes it can be difficult to figure out what the previous working state of the system was. I maintain that the minimal cost in disk space is repaid if it makes fixing a problem like this easier just one time in the life of a system. Bill Bogstad
- Follow-Ups:
- [Discuss] Reading Linux book
- From: richard.pieri at gmail.com (Richard Pieri)
- [Discuss] Reading Linux book
- References:
- [Discuss] Reading Linux book
- From: smallm at panix.com (Mike Small)
- [Discuss] Reading Linux book
- From: dbarrett at blazemonger.com (Daniel Barrett)
- [Discuss] Reading Linux book
- Prev by Date: [Discuss] Linux file systems
- Next by Date: [Discuss] Reading Linux book
- Previous by thread: [Discuss] Reading Linux book
- Next by thread: [Discuss] Reading Linux book
- Index(es):