Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com X-Lotus-FromDomain: JPMORGAN AT SMTP From: "Noel L Yap" To: cygwin AT cygwin DOT com Message-ID: <85256AA2.00747613.00@nyc-ntgw-n01.ny.jpmorgan.com> Date: Wed, 8 Aug 2001 17:12:08 -0400 Subject: Re: chroot bug Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline I've tried the latest snapshot and "chroot /" works. I'll let you know if I see other problems with chroot. Thanks much, Noel |--------+-----------------------> | | | | | cgf AT redhat DOT co| | | m | | | | | | 08/06/01 | | | 09:22 PM | | | Please | | | respond to | | | cygwin | | | | |--------+-----------------------> >----------------------------------------------------------------------------| | | | To: cygwin AT cygwin DOT com | | cc: (bcc: Noel L Yap) | | Subject: Re: chroot bug | >----------------------------------------------------------------------------| 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/ This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of J.P. Morgan Chase & Co., its subsidiaries and affiliates. -- 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/