Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Date: Tue, 7 Aug 2001 11:51:03 -0400 From: Christopher Faylor To: cygwin-developers AT cygwin DOT com Subject: Re: outstanding issues blocking new release? Message-ID: <20010807115103.D27996@redhat.com> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: cygwin-developers AT cygwin DOT com References: <20010806213235 DOT A24499 AT redhat DOT com> <20010807105917 DOT F22015 AT cygbert DOT vinschen DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <20010807105917.F22015@cygbert.vinschen.de>; from vinschen@redhat.com on Tue, Aug 07, 2001 at 10:59:17AM +0200 On Tue, Aug 07, 2001 at 10:59:17AM +0200, Corinna Vinschen wrote: >On Mon, Aug 06, 2001 at 09:32:35PM -0400, Christopher Faylor wrote: >> I can only think of three issues with cygwin that may need addressing. >> >> 1) The close_all_files problem that Egor found with exec'ed processes. >> >> 2) The problem with select() not detecting eof on pipes (Corinna really >> wants me to fix this). >> >> 3) The ntsec inheritance stuff. > >?? 4) The chroot problem reported by Noel Yap, perhaps ?? AFAIK, this is fixed. >> Is there anything more? Of the three, I think the most important one is >> probably 1). The other two are potentially enough too major to consider >> if I want to make a new release. > >3) Setup is prepared and changing fhandler_base::open() shouldn't > be too hard since most of the code already exists (alloc_sd). > I just need a few hours to wrap it for usage in open() and to > test the stuff. So, if you're not in a hurry... Nope. I'd like to give people at least a week to try this once we're ready, though. cgf