BobC
Yes, I looked at the filesystem options, and watched videos, but to be honest, I looked and see how each OS maps things differently, and think I will eventually have problems as a result.
I was/am considering different persistence files for different purposes, but its probably more than I need because it seems large software changes cause trouble blowing up using persistence, so maybe I need to just keep it simple. My thought is a separate bdir for each test environment as you mentioned a couple posts back, and then just use a simple rsync
to overlay my changes outside of /home, as there really aren’t that many, and I should try to keep changes to a minimum anyway. I can always use persistence when I want to to avoid making full reloads like I do now to do small change tests.
For my rsync idea, which I think Dave suggested when I created antiX-OpenBox 14 once upon a time, I could have a “changes-HOSTNAME” folder under ~/ and in it i put /etc and /usr in the same structure they exist off /, then I can use the following code to globally overwrite my code. Of course I could be smarter and back any of those existing files up first, and do a diff of some sort like apt-get does when it finds it is installing a fiole over top of a changed file, and those would be useful enhancements, but I think I need to keep it simple to avoid eventually landing myself in a pit of snakes.
# rsync -avh ./ /
What do you think? Any big disadvantages besides not being totally cool? I have tested it, and it works as long as I’m religious about copying changed files into there. At this point, everything works, btw. With the rsync I no longer need to copy in my changes a folder at a time. Thanks for all the help and ideas…..
Here is the link to SEARCH THE FORUM >> http://www.antixforum.com/search-forums