Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com From: "Robert Collins" To: "'Charles Wilson'" , "'Nicholas Wourms'" Cc: , Subject: RE: SysV Ipc shm revisited...A new solution Date: Sat, 8 Jun 2002 01:55:52 +1000 Message-ID: <00ab01c20e3b$cd7ee520$0200a8c0@lifelesswks> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal In-reply-to: <3D00CCA3.4060502@ece.gatech.edu> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal > -----Original Message----- > From: cygwin-owner@cygwin.com > [mailto:cygwin-owner@cygwin.com] On Behalf Of Charles Wilson > Sent: Saturday, 8 June 2002 1:09 AM > That way, if for instance Jason > recompiled postgres > against cygipc2, then (hopefully) folks could use THAT version of > postgres with EITHER ipcdaemon2 OR cygdaemon, without having to > recompile postgres (and NOT having to recompile their kernel). Nup. Not going to work (see my other email). However, in -no- scenario is kernel recompilation needed, once cygwin1.dll comes with the exports enabled. That's orthogonal to the current discussion on co-existence though. Rob -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/