X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-3.6 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Dick Subject: Re: Cygwin acts weird to / in a chroot Date: Tue, 24 Mar 2009 19:30:52 +0000 (UTC) Lines: 10 Message-ID: References: <20090323204510 DOT GA9322 AT calimero DOT vinschen DOT de> <49C7F72F DOT 4010008 AT cygwin DOT com> <49C804CA DOT 5080406 AT cygwin DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit User-Agent: Loom/3.14 (http://gmane.org/) X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com I did some grepping through the Cygwin sources and found some FIXMEs about chroot. It seems indeed to be implemented as a very dirty hack. I'm still not sure if it's caused by a wrong mount. I hope to find some time to create a patch, it seems interesting :-) gr Dick -- 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/