chroot2go Files

Debian:
48ca8807d95664e754a12bdfabc3cdb1  debian_wheezy_64bit.tar.bz2
1893962028e10b60b7532ce72139b750  debian_sid_32bit_20131217.tar.bz2

CentOS:
a402bf129a46c551eaacf564741c3eb5  cent57-32bit.tar.bz2
bc0a9e847f5e7cab3a5f6295e7b433eb  cent62-32bit.tar.gz
80100946a091aeee4a282812a245b122  cent62-64bit.tar.bz2
79c7d7b5003af29a81695eb68a45ae6f  centos49-64bit.tar.bz2

FC:
1c908c6eb7542e7abf2c5f5f3163d3d2  fc17-64bit.tar.bz2

Ubuntu:
7e1009d5631a7569f4e1b04f61ba182f  lucid-amd64.tar.bz2

Configurations:
0. Extract the archive to any location you see fit.
1. Copy your /etc/resolve.conf to /path/to/chroot/etc
2. Copy or create /path/to/chroot/etc/etc/fstab [depedning on whether you want the mounts your host machine has]. 
Also see 'man 8 mount' for binding options.
3. Optionally, you may want to copy other configuration files from your hosting machine such as /etc/hosts
4. As super user run:
# chroot /path/to/chroot

Optionally, you may want to mount /dev and /tmp from your hosting system like so:
# mount -o bind /dev /path/to/chroot/dev
# mount -o bind /tmp /path/to/chroot/tmp

This will also allow running X apps from within the chroot.
For it to work, you may need to run:
$ xhost + 
from your hosting ENV.

That's the basics.
After following these steps, you're suppose to have a functioning chroot where yum or aptitude works properly [be sure to mount /proc and /sys beforehand].
From here, you can do as you wish.

For bugs, interesting phenomenas and feature requests please drop a line to Jess Portnoy <kernel01@gmail.com>.