Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Date: Mon, 19 Jan 2004 15:43:28 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: cygwin without Win32 Message-ID: <20040119204328.GA19723@redhat.com> Mail-Followup-To: cygwin AT cygwin DOT com References: <1074544647 DOT 2499 DOT 22 DOT camel AT mentor DOT gurulabs DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1074544647.2499.22.camel@mentor.gurulabs.com> User-Agent: Mutt/1.4.1i X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com On Mon, Jan 19, 2004 at 01:37:27PM -0700, Dax Kelson wrote: >The newly released Microsoft Services For Unix (SFU v3.5) includes a new >"highly tuned" POSIX subsystem. MS says that UNIX apps using the POSIX >subsystem are within 10% performance of Windows apps using the Win32 >subsystem. The security models also work together so that chmod/chown/su >and friends all work properly. It would be nice to see an implementation >of setfacl and getfacl. > >Would there be any benefit to porting Cygwin to sit directly on top the >POSIX subsystem instead of going through the Win32 subsystem? There would certainly be a real detriment in the fact that cygwin would stop working for Windows 95/98/Me. If we could focus just on NT class systems, there is all sorts of improvements that we could make. I don't think that all of the people using those systems would be too happy with us, though, as much as I'd like to ditch them. cgf -- 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/