Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Fri, 14 Jan 2005 13:45:39 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Multiple installations and 3PPs Message-ID: <20050114184539.GH6227@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com References: <1105721403 DOT 28030 DOT 53 DOT camel AT localhost> <20050114171548 DOT GB6227 AT trixie DOT casa DOT cgf DOT cx> <1105726072 DOT 28030 DOT 78 DOT camel AT localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1105726072.28030.78.camel@localhost> User-Agent: Mutt/1.4.1i On Fri, Jan 14, 2005 at 06:07:52PM +0000, Adrian Cox wrote: >On Fri, 2005-01-14 at 12:15 -0500, Christopher Faylor wrote: >> >I don't understand why it is a goal to have only one version of >cygwin1.dll in use at a single time. I'd like to create separate >Cygwin universes, with no communication between them except via IP >networking. That is a very odd requirement. It sounds like you should be investigating vmware. Either that or you are venturing into territory beyond your current expertise or understanding. OTOH, if you aren't installing any services, you could probably get away with running cygwin under different accounts with user-mode mounts. >>This is rather like asking "Has anyone found a way to put sound >>deadening foam over the little thing that chimes when you're not >>wearing your seatbelt?" The warnings are there for a reason, not >>because we couldn't figure out how to name the shared memory region to >>avoid clashes. The problem isn't as simple as trying to avoid shared >>memory clashes. > >So what are the other problems? Look at the source. grep for multiple_cygwin_problem that will show you most of the problem spots. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/