On 02/23/2012 08:56 AM, Alfredo Palhares wrote:

Excerpts from Taylor Hedberg's message of Thu Feb 23 17:36:00 +0100 2012:

But that's problematic for files in /etc, many of which require specific
ownership or mode bits set/unset. You don't want your VCS to elide the
fact that /etc/shadow should only be readable by root, for instance.

I don't think Git will change permissions on existing files in your
working directory, but if you ever cloned your /etc repo onto another
machine, the permissions would be screwed up.

Yeah i agree, you should have carefull with that. I never transplant a the /etc of a machine
i only use it as detailed backup. Whenever i have another machine i create a new /etc repository
for it, copying manually the files i need because i dont even want the history back. You could
do it with git using root and those files would be owned by root, you just need to adjust the
ownerwhip like you set when you copy a file manually.
In my home repo i do that and keep a branch for each computer, but on /etc repos not just because
they often have very diferent distros and objectives.
Hey thanks again everyone I am going to start trying out both methods
and see which I feel works best for me and will post which way I go.

On 02/23/2012 08:43 AM, Dennis Börm wrote:

On 02/23/2012 05:36 PM, Taylor Hedberg wrote:

Alfredo Palhares, Thu 2012-02-23 @ 17:24:01+0100:

Excerpts from Matthew Monaco's message of Thu Feb 23 17:08:46 +0100
2012:

What about permissions and ownership? These are pretty important for
/etc.

What about those ? Git doesn't care about permissions, the only
permissions that git stores is the executable bit.


But that's problematic for files in /etc, many of which require specific
ownership or mode bits set/unset. You don't want your VCS to elide the
fact that /etc/shadow should only be readable by root, for instance.

I don't think Git will change permissions on existing files in your
working directory, but if you ever cloned your /etc repo onto another
machine, the permissions would be screwed up.



Hi

we're using

http://joey.kitenet.net/code/etckeeper/

for that purpose

greets,
Dennis

Have you had any issues?
The AUR packages for that are way out of date and probably abandoned by
the owners. From what I read it starting giving people issues when
pacman 3 came out and now that we are on 4 with even more features I
would think a bunch of work would have to be done to make work properly
for Arch.

On Thu, 23 Feb 2012 17:43:58 +0100
Dennis Börm <allspark@planetcyborg.de> wrote:

> we're using
>
> http://joey.kitenet.net/code/etckeeper/
>
> for that purpose

I see it's available via AUR, but, afaik, it does not support Arch's
pacman due to lack of hook support in Pacman.

Can you share some light how do you use etckeeper on Arch?

I'd probably use it with bzr (treeless repo + lightweight checkout).


Sincerely,
Gour


--
As a blazing fire turns firewood to ashes, O Arjuna, so does the
fire of knowledge burn to ashes all reactions to material activities.

http://atmarama.net | Hlapicina (Croatia) | GPG: 52B5C810

I wrote a system backup program called "mime" that works similar to Apple's
Time Machine on the back end. Basically each time you backup your system,
another copy of your file system is available. Another program is
installed with it called "lsmime" which is used to list, restore and view
information about files that are backed up. The new version I am about to
release even has the ability to view a diff on a particular file against
any version that is in your backups. The features available give the feel
of having your entire file system under version control.

The version on the site is functional and we have been using it on our
servers and work stations for years. I will have a new version available
in a few weeks. The current version can be downloaded here from the link
below. If you end up using it, I greatly appreciate any feedback you can
provide.

In regards to your original question, I don't know what is considered the
"Arch" way of doing this, however I run Arch at work and at home and is
backed up using mime on a daily or weekly frequency (this has saved my butt
more than once).

http://code.google.com/p/mime-backup/

Thank you
Squall

On 06/20/2012 07:46 AM, Squall Lionheart wrote:

I wrote a system backup program called "mime" that works similar to Apple's
Time Machine on the back end. Basically each time you backup your system,
another copy of your file system is available. Another program is
installed with it called "lsmime" which is used to list, restore and view
information about files that are backed up. The new version I am about to
release even has the ability to view a diff on a particular file against
any version that is in your backups. The features available give the feel
of having your entire file system under version control.

The version on the site is functional and we have been using it on our
servers and work stations for years. I will have a new version available
in a few weeks. The current version can be downloaded here from the link
below. If you end up using it, I greatly appreciate any feedback you can
provide.

In regards to your original question, I don't know what is considered the
"Arch" way of doing this, however I run Arch at work and at home and is
backed up using mime on a daily or weekly frequency (this has saved my butt
more than once).

http://code.google.com/p/mime-backup/

Thank you
Squall



Squall, very nice work going to give this a shot later today on a test
box. Thanks for pointing this out. I tried a few things in suggestions
to my OP but this seems to be the best so far. Thanks for bringing this
back up

Squall, very nice work going to give this a shot later today on a test box.
Thanks for pointing this out. I tried a few things in suggestions to my OP
but this seems to be the best so far. Thanks for bringing this back up

>
>
>
Your welcome. I will post a message to everyone when I roll out my next
version since it's a huge improvement over the current one with a lot of
very powerful and user friendly features, as well as efficiency
improvements.

Enjoy

--
Yesterday is history.
Tomorrow is a mystery.
Today is a gift.
That's why its called the present.

Headmaster Squall :: The Wired/Section-9
Close the world txen eht nepo
$3R14L 3XP3R1M3NT$ #L41N
http://twitter.com/headmastersqual

On 06/20/12 at 09:28am, Squall Lionheart wrote:
> Your welcome. I will post a message to everyone when I roll out my next
> version since it's a huge improvement over the current one with a lot of
> very powerful and user friendly features, as well as efficiency
> improvements.
>

It'd be nice if you added it to the AUR.

M

>
> It'd be nice if you added it to the AUR.
>
> M
>

After I roll out this update, that's on my list of stuff to figure out .
I have never created an AUR package, doesn't sound to difficult.

Squall

--
Yesterday is history.
Tomorrow is a mystery.
Today is a gift.
That's why its called the present.

Headmaster Squall :: The Wired/Section-9
Close the world txen eht nepo
$3R14L 3XP3R1M3NT$ #L41N
http://twitter.com/headmastersqual