Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT cygwin DOT com>
List-Help: <mailto:cygwin-developers-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT cygwin DOT com
Delivered-To: mailing list cygwin-developers AT cygwin DOT com
Message-ID: <02f801c21263$939939b0$6132bc3e@BABEL>
From: "Conrad Scott" <Conrad DOT Scott AT dsl DOT pipex DOT com>
To: "Charles Wilson" <cwilson AT ece DOT gatech DOT edu>
Cc: <cygwin-developers AT cygwin DOT com>
References: <005401c2124e$7cb91a90$0200a8c0 AT lifelesswks> <028001c21252$e92c7ba0$6132bc3e AT BABEL> <3D07C4E0 DOT 2050603 AT ece DOT gatech DOT edu>
Subject: Re: System-wide mutexes and pthreads
Date: Wed, 12 Jun 2002 23:50:40 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000

"Charles Wilson" <cwilson AT ece DOT gatech DOT edu> wrote:
> Now, OTOH, cygserver *could* use this library for path access, but why?
>   cygserver, by its very nature, will depend on cygwin1.dll -- so why
> not use it's path conversion routines.  No need to rely on setup's
> subcygwin.a.  I don't see why using cygwin1.dll from cygserver is a bad
> thing...

My only thought on this was that not depending on the cygwin dll might give
us the flexibility if we wanted cygserver to be started before any cygwin
processes (and it can't start before itself . . .). Then again I can't
imagine what sort of requirement there might be for that.

More pertinently we should think about making sure that at least some things
work if the daemon is killed and re-started while there are cygwin programs
running. But I don't think that's an immediate concern.

// Conrad