chroot sandbox question
I decided to try something which I guess is strange, but I haven't been able to figure out why. Here is what I did.
Code:
mkdir -p /home/user/chroot/{bin,lib} Code:
chroot: failed to run command `/bin/bash': No such file or directory In addition, there are procedures which bind mount proc and sys and then chroot into a livecd or something at which point proc and sys are available. So basically, why doesn't the chroot know about the bind mounted /bin/bash? Why is this procedure I'm doing incorrect? I figure for what I'm doing I don't need proc or sys and that I would get other errors if not including them int he chroot was causing the problem. |
assuming you have unpacked an iso or squashfile etc try this
Code:
su (or sudo su) |
The point of this question is to avoid copying the literal programs into the chroot directory, thus saving space, when a sandbox build is required.
|
All times are GMT -5. The time now is 12:04 PM. |