Chroot is a very big club, indeed. Unless you've set up a separate execution environment (including binaries, libraries, configuration or auxiliary files such as those ordinarily located in /etc or /lib, etc.), very little will work after a successul "chroot" call.
Note that "chroot" is not a BASH built-in, but rather an executable command. According to the man page, it uses $SHELL (default "/bin/sh") to start up an interactive shell if no command is specified. Thus the diagnostic you report, Rolf, is to be expected if your SHELL environment is not set or is set to "/bin/sh." Once the root of the file system is set to the current directory, names like "/bin/sh" are unlikely to exist unless you've set things up to include them.
One place I see this done routinely is in public access FTP servers.
Randall Schulz
Mountain View, CA USA
At 15:32 2002-12-01, Rolf Campbell wrote:
When I try "chroot ." in bash I get: $ chroot . chroot: cannot execute /bin/sh: No such file or directory> -----Original Message----- > From: Chris January [mailto:[EMAIL PROTECTED]] > Sent: Sunday, December 01, 2002 5:08 PM > To: [EMAIL PROTECTED] > Subject: RE: problem with chroot causing Cygwin to get > confused about the root directory > > > > I'm having a problem with chroot - see the following strace: > > <--snip--> > > > At the start of the strace chroot (".") has been called; it succeeds > > at time 63935. (The same problem occurs with chroot(<full path to > > rootfs>) as well). > > Then chdir ("/") is called at time 64000. The result of > > conv_to_posix_path at time 2652 should be '/', but is instead > > /cygdrive/c/... I'll look at the Cygwin source, but has anyone else > > any ideas as I suspect it may take me some time to track this down. > > In the same vain, chroot . in bash goes into an infinite loop. > > Chris
-- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
