Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Date: Mon, 6 Aug 2001 21:22:41 -0400
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: chroot bug
Message-ID: <20010806212241.A24375@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <85256AA0 DOT 007D8F22 DOT 00 AT nyc-ntgw-n01 DOT ny DOT jpmorgan DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.11i
In-Reply-To: <85256AA0.007D8F22.00@nyc-ntgw-n01.ny.jpmorgan.com>; from yap_noel@jpmorgan.com on Mon, Aug 06, 2001 at 06:51:25PM -0400

On Mon, Aug 06, 2001 at 06:51:25PM -0400, Noel L Yap wrote:
>>> >>My original email stated that "chroot /" doesn't work.  I get:
>>> >>nyap:jpmpsdev AT NYAP:/%/d/WebSphere/admin/bin> chroot /
>>> >>chroot: cannot execute /bin/bash: No such file or directory
>>> >
>>> >
>>> >So you're saying you get this result from a recent snapshot as well?
>>>
>>>Yes, I get this from the latest snapshot (I'm assuming that running the latest
>>>setup.exe will get me the latest snapshot?).
>>
>>
>>No, snapshots are different than the net release.  See
>>http://www.cygwin.com/snapshots/  These are the current development
>>builds representing the road to the next release.  If its broken here,
>>it will be broken in the next release without additional attention.
>
>I installed the latest snapshot of cygwin1.dll over my current cygwin1.dll.
>"chroot /" still produces an error saying that "/bin/bash" isn't found.  Did I
>test this right?  Should I have rebooted?  Where can I get the tarballed source
>for chroot?  What else can I do to track this down?

If there are problems they would be in cygwin, not in the chroot program.  This
is evidenced by the fact that you claim that things work better in 1.3.1 over
1.3.2.  I doubt that chroot changed during that period.

Check out the cygwin web site for information on how to get the cygwin sources.

Or, wait for the next snapshot.  I believe that I've fixed the problem.

cgf

--
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/