[EMAIL PROTECTED] wrote: > Why doesn't this work?? > > # /tmp/empty/kernelversion > 2.4 > # chroot /tmp/empty /kernelversion > chroot: /kernelversion: No such file or directory > > > (I get the same error on Debian, Fedora and Knoppix.) > > (chroot man page says to do 'chroot <new-root> <command>' > so what am I doing wrong???)
It could be a lot of things. First of all, does /tmp/empty/kernelversion exist? Guessing by the name of /tmp/empty, I am going to say no. The chroot(1) comamnd first makes the chroot to the new directory. Then it runs the command (or $SHELL if no command is specified). Once inside the chroot, the process cannot see out of it. That is the whole idea of the chroot. As others pointed out, you have to have all support files and libraries available for the program within the chroot. -john -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
