Name | Modified | Size | Downloads / Week |
---|---|---|---|
Parent folder | |||
README | 2013-05-25 | 1.4 kB | |
centos49-64bit.tar.bz2 | 2013-01-24 | 234.5 MB | |
cent62-64bit.tar.bz2 | 2012-11-24 | 272.2 MB | |
cent57-32bit.tar.bz2 | 2012-02-27 | 345.5 MB | |
cent62-32bit.tar.gz | 2012-02-15 | 284.9 MB | |
Totals: 5 Items | 1.1 GB | 0 |
Debian: 48ca8807d95664e754a12bdfabc3cdb1 debian_wheezy_64bit.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. 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>.