Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-Id: <5.1.0.14.2.20021201164813.02d511e8@pop3.cris.com>
X-Sender: rrschulz AT pop3 DOT cris DOT com
Date: Sun, 01 Dec 2002 16:52:10 -0800
To: cygwin AT cygwin DOT com
From: Randall R Schulz <rrschulz AT cris DOT com>
Subject: RE: [list] RE: problem with chroot causing Cygwin to get
  confused about the root directory
In-Reply-To: <LPEHIHGCJOAIPFLADJAHMELJDBAA.chris@atomice.net>
References: <83040F98B407E6428FEC18AC720F5D73E5010E AT exchange DOT tropicnetworks DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed

Chris,

When an exec(2) system call fails do to a file format problem (ENOEXEC) as 
opposed to a file-not-found error (ENOENT) or a permission error (EPERM), 
the fallback action taken  by the shell is to interpret the file as a script.

One could argue that the shell should be a little more intelligent about 
dealing with the failure to exec a shell to interpret the "script."

Randall Schulz
Mountain View, CA USA


At 16:18 2002-12-01, Chris January wrote:
> > > > 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.
>
>^^^ this second one's solved (ish)
>
>I'm running it in a directory where /bin/sh exists and /bin/sh is a Linux
>ELF file (because I'm playing with Line). when I run chroot ., Cygwin tries
>to run /bin/sh, but for some reason thinks it's a script. Scripts are run
>with /bin/sh, so off Cygwin goes to look for /bin/sh...ad nauseum.
>
>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/