Let's take them one by one:
bind mounting: That reminds me that I once mounted my / somewhere under
my home directory to make it temporarily available over an SMB share. It
was a quick thing, and then I went rm -rf on the directory under which
the mount was done. The only time ever I needed to
As far as I know, there is no way git can tell the difference between a
hard link to a file (or should I say inode?) and the "original". I'm not
even sure there is a way to tell which one is which (maybe some raw
dumping of the file system's binary data?).
This way or another, hard links are n
On Fri, Jun 8, 2012 at 12:24 PM, Eli Billauer wrote:
> **
> I tried to symlink /boot/grub/ and got one single file (the symbolic link
> itself). Some googling immediately revealed that making git follow symlinks
> is a popular question, with a typical answer that git doesn't like to do
> that (or
What about linking the none-/etc directories as git submodules? Would that
help?
(I'm still 100 pages from the end of Pro Git and just read about submodules
last night).
On Jun 9, 2012 2:13 AM, "Oron Peled" wrote:
> On Friday, 8 בJune 2012 12:24:55 Eli Billauer wrote:
> >
> > What I liked
Eli Billauer writes:
> What git wisely does is maintaining the link's destination. So if
> you change or delete the symbolic link, you get exactly that change
> in the repository. I tried changing a symbolic link, committed to
> git, and got a single plus-minus change in the diff log, with the
>
On Friday, 8 בJune 2012 12:24:55 Eli Billauer wrote:
>
> What I liked less, is that the repository is under /etc
(not surprising, and
> still), so configuration files outside that directory can't be
> tracked. /var/lib/tftpboot/pxelinux.cfg/, for example.
>
>
>
[ Replying to HTML
Aha. I learn something new every day.
As for git, on the contrary. /etc/alternatives contains symbolic links,
so it would be pointless to follow them. What git wisely does is
maintaining the link's destination. So if you change or delete the
symbolic link, you get exactly that change in the re
Eli Billauer writes:
> I tried to symlink /boot/grub/ and got one single file (the symbolic link
> itself). Some googling immediately revealed that making git follow symlinks is
> a popular question, with a typical answer that git doesn't like to do that (or
> can't do that).
> So given that a co
I tried to symlink /boot/grub/ and got one single file (the symbolic
link itself). Some googling immediately revealed that making git follow
symlinks is a popular question, with a typical answer that git doesn't
like to do that (or can't do that).
So given that a configuration repository is su
Eli Billauer writes:
> What I liked less, is that the repository is under /etc (not surprising, and
> still), so configuration files outside that directory can't be
> tracked. /var/lib/tftpboot/pxelinux.cfg/, for example.
So, out of curiousity, what does it do with symlinks? A typical use
case,
On 06/06/2012 06:39 PM, Ohad Levy wrote:
[...]
So what do you say? A bad idea? A brilliant idea? Everyone's doing it
and nobody told me?
etckeeper
Thanks for that one (goes to Oron too). On Fedora 14 (running on a
guinea pig virtual machine) it was just yum install etcke
On Wed, Jun 06, 2012 at 10:38:49PM +0300, Oron Peled wrote:
> On Wednesday, 6 בJune 2012 12:57:06 Eli Billauer wrote:
> > Hi all,
> >
> > I'd just like to get your input before I do something stupid. The idea,
> > anyhow, is to create a git repository on my system's root directory, and
> > add m
On Wednesday, 6 בJune 2012 12:57:06 Eli Billauer wrote:
> Hi all,
>
> I'd just like to get your input before I do something stupid. The idea,
> anyhow, is to create a git repository on my system's root directory, and
> add many of the system's configuration files (e.g. some of /etc/) for
> trac
On Wed, Jun 6, 2012 at 1:34 PM, ilya wrote:
> It is generally possible, though I'd recommend making your git repo out of
> /etc, not /, since this is what you mostly want to track, and managing
> .gitignore of
> the whole FS will be too painful.
> One thing git does not track though, is file owne
On 06/06/12 16:03, Eli Billauer wrote:
> There seems to be a misunderstanding about git: If the repository is
> on /, it doesn't mean all files are tracked. On the contrary, they are
> handpicked with "git add". On the other hand, if I put the repository
> under /etc, I'm not so sure I'll be able t
I'd suggest doing so but away from system folders. You can create symlinks
to each file or folder you are interested in backing up (keep the symlink
creation script handy!), and by doing so you won't end up with the whole
filesystem in a git repository.
On Wed, Jun 6, 2012 at 12:57 PM, Eli Billaue
There seems to be a misunderstanding about git: If the repository is on
/, it doesn't mean all files are tracked. On the contrary, they are
handpicked with "git add". On the other hand, if I put the repository
under /etc, I'm not so sure I'll be able to track something under, say,
/var.
File o
It is generally possible, though I'd recommend making your git repo out of
/etc, not /, since this is what you mostly want to track, and managing
.gitignore of
the whole FS will be too painful.
One thing git does not track though, is file ownership. This might be a
problem for
some files.
On 06/06
On Wed, Jun 6, 2012 at 12:57 PM, Eli Billauer wrote:
>
> So what do you say? A bad idea? A brilliant idea? Everyone's doing it and
> nobody told me?
>
I don't know about everyone but I have been doing it (on my home computers)
for so long that I am still on CVS, not git. My repository lives in
/
Hi all,
I'd just like to get your input before I do something stupid. The idea,
anyhow, is to create a git repository on my system's root directory, and
add many of the system's configuration files (e.g. some of /etc/) for
tracking.
This sounds a bit bizarre even to me, but my question is: D
20 matches
Mail list logo
