Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m working on a custom version of a GNU/Linux live distribution. I need to add/remove packages, edit scripts…
I work in an unsquashed filesystem (squashfs-root/) used as root for chroot.
I’m wondering which is the best way to manage my work. Should I create a git repo and add squashfs-root/?
My main fear is messing up chroot env and cannot go back to a working version.
Thanks,
hamen
UPDATE:
I’ll give a try to rdiff-backup. Thank you.
The problem with git (and other source control suites) is that it doesn’t handle permissions and special files very well.
etckeeper is a set of scripts on top of git to manage
/etc. That can already provide you with much security.Finally, you say you’re running from a
chroot(). This would allow you easy backups from outside of the chroot, e.g. with rdiff-backup, which creates nice compact on-disk representation while still allowing you to browse the most recent version directly.