Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT cygwin DOT com>
List-Help: <mailto:cygwin-developers-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT cygwin DOT com
Delivered-To: mailing list cygwin-developers AT cygwin DOT com
Message-ID: <3D040C6C.4030508@ece.gatech.edu>
Date: Sun, 09 Jun 2002 22:18:20 -0400
From: Charles Wilson <cwilson AT ece DOT gatech DOT edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2
X-Accept-Language: en-us
MIME-Version: 1.0
To: cygwin-developers AT cygwin DOT com
Subject: Re: shm status
References: <072501c20fb8$8d16dc80$6132bc3e AT BABEL> <20020609163607 DOT GD26171 AT redhat DOT com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit



Christopher Faylor wrote:

> On Sun, Jun 09, 2002 at 02:21:22PM +0100, Conrad Scott wrote:
> 
>>Also the ipcs and ipcrm utitilities are really useful when working with sysv
>>ipc so I also thought I could start by adding these. Presumably this would
>>be a case for another cygwin_internal() interface? i.e. get the list of ids;
>>the program then issues xxxctl() calls to get the relevant details or rm the
>>requested objects. Any objections to such an approach? (Just for comparison,
>>the usual Un*x implementation involves reading kernel memory via /dev/kmem.)
>>
> 
> Do we need a cygwin_internal interface?  How do OSes like linux do this?
> 
> Maybe it makes sense to start exposing things via the /proc interface, if that
> is the way linux does it.


Except that I think Linus hates the /proc interface -- all that text 
parsing to pass info back and forth.  Binary data should be binary...

Anyway, concerning ipcs and ipcrm...there are implementations of them in 
cygipc -- but *do not copy them*.  It's that whole copyright thing.

ditto the utilities in cygutils: msgtool.c  semstat.c  semtool.c  shmtool.c.

However, that doesn't stop you from compiling them, linking them against 
cygserver, and using them to help test and develop cygserver...

--Chuck