Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
From: "Ralf Habacker" <Ralf DOT Habacker AT freenet DOT de>
To: "Robert Collins" <robert DOT collins AT syncretize DOT net>,
   "'Nicholas Wourms'" <nwourms AT yahoo DOT com>, <cygwin AT cygwin DOT com>
Cc: <cwilson AT ece DOT gatech DOT edu>
Subject: RE: SysV Ipc shm revisited...A new solution
Date: Fri, 7 Jun 2002 21:19:10 +0200
Message-ID: <001c01c20e58$33d7d950$316307d5@BRAMSCHE>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
In-Reply-To: <009e01c20e3a$867fa700$0200a8c0@lifelesswks>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400

>Robert Collins wrote:

> Already provided. What will happen when the 64 bit key is exported is
> that fresh cygipc linked programs will fail, but existing programs will
> still work correctly. If something like ipcdaemon2.exe exists - OR -
> cygipc is re-released as a 64-bit version, then new links will succeed
> (but at the possible cost of breaking old binaries).
>
Why must this be ? Could not the released 64-bit version only use the most
significant long word of key_t, so that it is compatible to the old binaries and
can use the 64 bit key_t definition ?

Ralf


--
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/