New answers tagged chroot
Do not use chroot(). Use OpenVZ. OpenVZ is chroot on steroids: Not only does OpenVZ give a container its own root directory, it also gives a container its own init() process, its own process list, its own IP, its own memory and disk space quota, etc. http://openvz.org/Quick_installation Once OpenVZ is installed, go to /vz/template/cache and download a ...
Chroot runs a program and, to this program only (and any child process that it launches), pretends that a certain directory (and the whole tree rooted at that directory) is all there is. For example, suppose you're running Ubuntu, and you've installed Arch Linux on another partition which is currently mounted at /media/arch. (It doesn't have to be a ...
You could use Docker to create an OS in a container image, then run the install script in the activated container. Afterwards you can use the docker diff command to see what files it changed in the container. The container is isolated from the host, so your real /etc files would be unaffected.
Your best environment would be a local vm with a small filesystem mounted from a file within your host system. This allows you to take a copy of the vm file-system after vm is initally installed. Then you can reset the file system, back to saved copy, after you have run a test of your install on the vm. So you can repeat your test.
Top 50 recent answers are included