I am not doing it for multiple hosts but I source a number of various files for each of my dot files. Each file I source is for a specific part of each dotfile so I can easily append to it without screwing anything up. Those sourced files are then kept in version control. It is helpful when you have a few hundred lines in your dotfiles. As for history I am appending as soon as the command is run so that I do not lose history in multiple sessions, and I have it in bashrc so that it will also work properly with screen, if you put the history settings in .bash_profile history will be overwritten when you exit screen As for etckeeper the directory is root 700 so they are not anymore unprotected than any other file in /etc
1114905 drwx------ 8 root root 4096 2009-07-06 07:39 .git On Mon, Jul 20, 2009 at 4:04 PM, Brian Friday <[email protected]>wrote: > On Mon, Jul 20, 2009 at 12:18 PM, Chris Louden<[email protected]> > wrote: > > I have been keeping my dotfiles in Git for a while now. Very handy. > > Since I access many systems it makes sense to keep them configured the > > same. Not just at a package level but also the configuration level. > > I've yet to do this at work but its on the to-do list. Then I just > > have a git pull command in the login to keep my login the system > > updated with my latest bash/vim or etc preferences. Putting /etc never > > occurred to me though. > > The one thing I haven't done enough of is working with my dot files. I > really want to create a setup where each host has its own history and > potentially its own shell .rc files. As much as I sometimes run the > same command on different systems it would be much more useful to keep > history seperated out and appended (if I run multiple sessions on the > same host). > > Anyone doing this now with any success? > > > > My new web site that i am working on uses git on the backend. Document > > content and resources for documents, such as document-specific images > > are read directly from a git repository. Publishing is as easy. Just > > push to the repository. Whole other kind of CMS. hehe > > > > -Chris > > Cool Chris! Sounds like a interesting use of git, heh and if you can > say set "views" where internal users see the internal branch for > testing and external users the master branch that could be very very > handy. > > - Brian > _______________________________________________ > LinuxUsers mailing list > [email protected] > http://socallinux.org/cgi-bin/mailman/listinfo/linuxusers > -- Peter Manis (678) 269-7979
