To expand on Florian's answer a little bit, I would ask you to check (before you do the chroot command) if /mnt/sysimage/bin/ksh exists. If not, then you'll have to pick something else as your shell to run, such as /bin/sh (which would _really_ be /mnt/sysimage/bin/sh).
Mark Post -----Original Message----- From: Dave Myers [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 17, 2002 5:31 PM To: [EMAIL PROTECTED] Subject: ramdisk getting ./chroot: cannot execute /bin/ksh: No such file or directory What does this error mean...coming from my RH 7.2 ramdisk system ? I see /bin/ksh in /bin and it's executable ???? # ./chroot /mnt/sysimage ./chroot: cannot execute /bin/ksh: No such file or directory
