Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT cygwin DOT com Delivered-To: mailing list cygwin-developers AT cygwin DOT com From: "Robert Collins" To: "'Conrad Scott'" Cc: Subject: RE: System-wide mutexes and pthreads Date: Fri, 14 Jun 2002 00:15:14 +1000 Message-ID: <009a01c212e4$bcb7a2b0$0200a8c0@lifelesswks> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal Importance: Normal In-Reply-To: <028001c21252$e92c7ba0$6132bc3e@BABEL> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 > -----Original Message----- > From: Conrad Scott [mailto:Conrad DOT Scott AT dsl DOT pipex DOT com] > Sent: Thursday, 13 June 2002 6:51 AM > I know all about the "I used it 'cos I could" feeling. It's a > shame that the > daemon isn't a pure win32 program, but I get the feeling that > it will depend > more on cygwin features as it develops, rather than fewer; > for example, > configuration or log files should obey cygwin naming rather > than raw win32. I don't see that as a large issue. It doesn't need to be 'pure win32'. The cygwin instance it's using will determine that the cygserver isn't running, and thus use no cygserver calls, and the cygwin use it makes is (and should remain) quite limited. Rob