Cygwin acts weird to / in a chroot

Corinna Vinschen corinna-cygwin@cygwin.com
Mon Mar 23 20:59:00 GMT 2009


On Mar 23 20:34, Dick wrote:
> Hi Folks,
> 
> I have some trouble running chrooted shell scripts:
> 
> - First I've copied c:\cygwin to c:\cygwin\chroot\a
> - I've created a shell script test.sh:
> cat > /chroot/a/test.sh << @EOF
> #!/bin/bash
> echo hello
> @EOF
> - Then I try to run the shell chrooted, this works
> chroot /chroot/a /bin/bash
> - In the chroot I run the shell script, which echoes hello:
> bash test.sh
> - Then I leave the chroot (ctrl-d) and start the shell script from chroot:
> chroot /chroot/a /bin/bash /test.sh
> 
> This returns: bash: *: No such file or directory (where * is a white smiley)
> 
> - The strange thing is that:
> chroot /chroot/a /bin/bash test.sh
> 
> Just works, what is wrong? Cygwin seems to act very weird to / in a chroot. 

Don't use chroot on Cygwin.  It was never more than a hack and it adds
no security at all, given that the concept isn't supported by the OS.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/



More information about the Cygwin mailing list