Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Thu, 9 Aug 2001 10:48:13 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: chroot bug Message-ID: <20010809104813.C14525@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <85256AA3.00494444.00@nyc-ntgw-n01.ny.jpmorgan.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <85256AA3.00494444.00@nyc-ntgw-n01.ny.jpmorgan.com>; from yap_noel@jpmorgan.com on Thu, Aug 09, 2001 at 09:20:19AM -0400 On Thu, Aug 09, 2001 at 09:20:19AM -0400, Noel L Yap wrote: >chroot works for the most part. I get sporadic memory errors (xmalloc not able >to allocate or segfault) when trying out commands (eg ls) after the chroot, >though. I'll see if I can track them down. What is the chroot command that you're using "chroot /"? Since this actually does nothing at all now it would be surprising if it had any effect on any commands. Details in bug reports are always a necessity if you want solutions. 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/