This is the mail archive of the
cygwin-developers@cygwin.com
mailing list for the Cygwin project.
Re: Cygdaemon - planning
- From: Christopher Faylor <cgf at redhat dot com>
- To: cygwin-developers at cygwin dot com
- Date: Wed, 25 Jun 2003 14:06:25 -0400
- Subject: Re: Cygdaemon - planning
- References: <Pine.CYG.4.55.0306251637430.3408@ellixia>
- Reply-to: cygwin-developers at cygwin dot com
On Wed, Jun 25, 2003 at 05:53:50PM +0100, Elfyn McBratney wrote:
>I have also changed things quite a lot. I've moved specific daemon code into a
>new toplevel `cygdaemon' directory and kept/renamed the interface code in the
>`cygwin' directory. Here's how things look locally on my branch
>
> winsup/
> ...
> cygdaemon/
> ipc-utils/ - a few command line utilities (still a work in progress)
> ...
> cygwin/
> moved cygserver_shm.cc to cygdaemon/modules/shm.cc
> ...
>
>If it's OK, could I start a branch for developement? After I've finished my work
>on libgen and submitted the dang patch, of course. :-)
What is the rationale for putting things in a winsup directory? Can't cygdaemon
be in it's own sibling directory with winsup?
cgf