This is the mail archive of the
mailing list for the Cygwin project.
Re: [HEADSUP] Let's start a Cygwin 1.7 release area
- From: Christopher Faylor <cgf-use-the-mailinglist-please at cygwin dot com>
- To: cygwin-apps at cygwin dot com
- Date: Sun, 6 Apr 2008 17:03:43 -0400
- Subject: Re: [HEADSUP] Let's start a Cygwin 1.7 release area
- References: <firstname.lastname@example.org>
- Reply-to: cygwin-apps at cygwin dot com
On Mon, Apr 07, 2008 at 12:34:50AM +1000, email@example.com wrote:
>As far as I understand it, the current Cygwin runtime architecture uses shared
>memory for those Cygwin processes attached to the Cygwin DLL, and a static
>registry location for its static mount table. As already discussed, the static
>mount table could move out into the Cygwin file system, freeing up any registry
>conflict for multiple Cygwins.
>Is it feasible to consider that more than one Cygwin shared memory be created,
>one for each of multiple Cygwins? Each Cygwin could be uniquely identified by
>the UNC path to its Cygwin DLL. The static registry location, or indeed
>another singleton shared memory, could then be used for mapping from Cygwin DLL
>UNC path to the UNC path to its shared memory.
Is it feasible? It's just a simple matter of programming but it is not
as simple as what you are saying above.
is it planned? AFAIK, no.
Is this the right mailing list to discuss changes to the architecture of the cygwin