Oh, i just need an environment where to do stuff which i don't want to do on my regular installation
(third party stuff, not yet in the repositories, partly with bugs)
so i don't break it.
It's just a test environment.
Create it, use it for a while, delete it.
One might ask: Why not dualboot or use Virtualbox?
- I can use my regular installation while doing some other things in the chroot
- I don't need to boot a VirtualBox session.
- It is (slightly) more easy to copy files from-and-to.
A bit more detailed:
It is for packaging ruby gems.
a) ruby uses bundler and rubygems to install gems (which will install further gems from rubygems.org).
That is not the debian way to do it, but i want to look at it now and then, to check it
b) Some gems got other gems at dependencies, which are not yet in the repos. I need to install them to test the gems i package.
In the long run that means that i got a lot of ruby stuff which is not really proper (and which i don't need at all, as i don't do ruby).
Hence the most important part, for me, is to mount dev, sys, dev/pts and proc (and using LANG=C), so i can use the chroot without running into error messages. And to umount them after i exit the chroot.
I am not that happy to run:
and then do
su - username
but don't know a better solution yet.
Did that make sense?
So i herd u liek mudkip?