git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: Adam Hunt <kinema@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: /etc in git?
Date: Wed, 18 Jan 2006 21:05:01 -0800	[thread overview]
Message-ID: <7v64ogkdtu.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <b476569a0601182040w581b72b7xbb99845da4085646@mail.gmail.com> (Adam Hunt's message of "Wed, 18 Jan 2006 20:40:22 -0800")

Adam Hunt <kinema@gmail.com> writes:

> Do you have any more details by chance?  Does it work?  Does it work
> well?  How does one do it?

I personally feel it is a horrible and stupid thing to do, if by
"version control /etc" you mean to have /.git which controls
/etc/hosts and stuff in place.  It would work (git does not
refuse to run as root).  But being a *source* control system, we
deliberately refuse to store the full permission bits, so if
your /etc/shadow is mode 0600 while /etc/hosts is mode 0644, you
have to make sure they stay that way after checking things out.

You are much better off to keep /usr/src/rootstuff/.git (and
working tree files are /usr/src/rootstuff/etc/hosts and
friends), have a build procedure (read: Makefile) there, and
version control that source directory.  I usually have 'install'
and 'diff' target in that Makefile, so that I can do this:

	$ cd /usr/src/rootstuff
        $ make diff ;# to see if somebody edited any targets by hand
	$ edit etc/hosts
	$ git diff ;# to see the source change
        $ make diff ;# to see the change I am going to install
        $ su
        # make install; exit
        $ git commit -a -m 'Add a new host.'

Being able to run "diff" before actually doing it is very handy
and useful safety/sanity measure.

Obviously, /usr/src/rootstuff/ should be mode 0770 or stricter,
owned by the operator group; it would contain some sensitive
information.

  parent reply	other threads:[~2006-01-19  5:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-19  3:43 /etc in git? Adam Hunt
2006-01-19  4:35 ` Junio C Hamano
2006-01-19  4:40   ` Adam Hunt
2006-01-19  4:59     ` H. Peter Anvin
2006-01-19  5:05     ` Junio C Hamano [this message]
2006-01-19  6:23       ` Ryan Anderson
2006-01-19  7:50         ` Junio C Hamano
2006-01-19  9:41           ` [PATCH] Support precise tracking of file modes Petr Baudis
2006-01-19 18:25             ` Junio C Hamano
2006-01-19 18:46               ` Petr Baudis
2006-01-20 15:27               ` Alex Riesen
2006-01-20 14:16             ` Peter Baumann
2006-01-20 13:50           ` /etc in git? Ryan Anderson
2006-01-20 17:55             ` Junio C Hamano
2006-01-19 16:54       ` Joel Becker
2006-01-19 22:22       ` Daniel Barkalow

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7v64ogkdtu.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=git@vger.kernel.org \
    --cc=kinema@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).