Martin Mielke wrote:

yep, that's why I'm so curious about this new "undocumented feature"... :-)

No offense meant; but you should take the time to learn about chroot, when you want to use it. It does *NOT* what you expect it to do and you obviously have no idea what it does. You cannot chroot into a arbitrary directory that is not set up appropriately and assume that it works. chroot has nothing per se to do with CDs or DVDs and you cannot simply use it to "activate" them or to modify their content, when they don't have a directory setup that is explicitly meant to do so. (And since your chroot did not succeed, the setup of your Knoppix CD is obviously not appropriate.) info chroot may be a start. Or google for "chroot tutorial" and try some of these matches. If you don't understand that information, come back with specific questions and there will be surely some folks on this mailing list that might help you. But currently, we would have to explain everything from the start; and this mailing list is not necessarily the place for such tutorials. (At least, I wouldn't write one here. ;-) Carlos:

I can reproduce that behaviour (SuSE 10.1):

nimrodel:~ # ls /mnt/ dvd dvd.crypta.x isocd isodvd nfs nfs_cdrom nfs_dvd nfs_su tmp nimrodel:~ # chroot /mnt/ chroot: cannot run command `/bin/bash': No such file or directory

What do you expect? In /mnt is no bin directory, as shown by your ls command; so obviously there won't be a /bin/bash there as well. The error message "No such file or directory" is quite clear, IMNSHO: /mnt/bin/bash does not exist. And even if it would be there, the needed dynamic libraries would be missing, since there is also neither a lib/ nor a usr/lib/ in /mnt. chroot makes a directory the new root of the filesystem, i.e., the new / for the command's process. Each and every path used by any system call or any command search is now relative to this new root. The command passed to chroot -- the default command is $SHELL, that's why it's looking for /bin/bash -- and all its dependencies (libraries, config files, even device files, etc.) must be reachable via this new root.

I don't remember this behaviour on previous versions of SuSE :-?

This has never been different; chroot is standard Unix functionality. HTH, Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod Email: jschrod@acm.org Roedermark, Germany --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org