Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com From: Chris Faylor Date: Fri, 31 Mar 2000 12:42:10 -0500 To: cygwin developers Subject: Re: Mo Dejong's install problems Message-ID: <20000331124210.F1182@cygnus.com> Reply-To: cygwin-developers AT sourceware DOT cygnus DOT com Mail-Followup-To: cgf AT cygnus DOT com, cygwin developers References: <20000331154409 DOT 9248 DOT qmail AT web110 DOT yahoomail DOT com> <200003311625 DOT KAA04456 AT hp2 DOT xraylith DOT wisc DOT edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.1.8i In-Reply-To: <200003311625.KAA04456@hp2.xraylith.wisc.edu>; from khan@NanoTech.Wisc.EDU on Fri, Mar 31, 2000 at 10:25:04AM -0600 On Fri, Mar 31, 2000 at 10:25:04AM -0600, Mumit Khan wrote: >One way is to create a tiny Cygwin app that is always running, and that >creates that shareable area that all Cygwin processes attach to. Sort of >a 'init' process. If it's dead, the next Cygwin DLL load will start it >again. Maybe we ought to install inetd by default. Kill two or three birds with one stone... cgf