X-Spam-Check-By: sourceware.org Date: Tue, 10 Jan 2006 09:54:14 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Are there documents on how cygwin1.dll is designed and implemented ? Message-ID: <20060110145414.GA13782@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com References: <01fc01c61591$95c36690$7c22a10a AT china DOT huawei DOT com> <43C3C44C DOT DBDE3DB6 AT dessent DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43C3C44C.DBDE3DB6@dessent.net> User-Agent: Mutt/1.5.11 Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: 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 On Tue, Jan 10, 2006 at 06:27:24AM -0800, Brian Dessent wrote: >Richard Meng wrote: >>I'm interested in the Cygwin1.dll's design and implementations, are >>there some documents about it ? > >There are a number of text files, winsup/cygwin/how*.txt. There's also >, >and of course the source code itself and mailing list archives. The Usenix paper is very dated, though. Many of the things that it talks about are no longer true, e.g., Cygwin doesn't invent its own pids anymore and the discussion of signals is no longer applicable. That's why that paper was deleted from the cygwin site a while ago. 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/