More: [1.7] packaging problem? Both /usr/bin/ and /usr/lib/ are non-empty

Corinna Vinschen
Tue May 12 14:15:00 GMT 2009

On May 12 14:07, Earnie Boyd wrote:
> Quoting Corinna Vinschen <>:
>>> (b) downside: if somebody has multiple installations (boo! bad! hissss!)
>> *shrug*
> Why is this bad?  Oh, maybe shared memory regions with like names.  In  
> MSYS I changed the shared regions to be named based on a hash of the  
> path to the DLL.  This allows multiple copies of the dll in memory at  
> the same time without interfering with each other.  The only problem  
> I've found is if I change to a directory containing a different copy of 
> the dll or I try to execute a command which resides in a directory with a 
> different copy of the dll.  Now vendors can bundle MSYS with their 
> product and not have fear of interfering with other instances of MSYS.
> Might it be possible for Cygwin to do the same?

It's not just shared memory, it's also the objects created in the NT
BaseNamedObjects namespace.  Maybe at one point, but not now.


Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

More information about the Cygwin-developers mailing list