From owner-freebsd-hackers Mon Jan 13 09:52:52 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA25380 for hackers-outgoing; Mon, 13 Jan 1997 09:52:52 -0800 (PST) Received: from jump.net (serv1-2.jump.net [204.238.120.19]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id JAA25375 for ; Mon, 13 Jan 1997 09:52:49 -0800 (PST) Received: from benjamin.adonai.com by jump.net (8.8.4/BERK-6.8.11) id LAA09956; Mon, 13 Jan 1997 11:52:35 -0600 (CST) Message-Id: <1.5.4.32.19970113175320.0066a1bc@jump.net> X-Sender: adonai@jump.net X-Mailer: Windows Eudora Light Version 1.5.4 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 13 Jan 1997 11:53:20 -0600 To: dg@root.com From: Lee Crites Subject: Re: bug in setsockopt()... ? Cc: freebsd-hackers@FreeBSD.org Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk At 02:10 13-01-97 -0800, David Greenman wrote: > This is actually a bug that Garrett has on his whiteboard... > >-DG > >David Greenman >Core-team/Principal Architect, The FreeBSD Project Dave (and others); One of the things I've been very seriously considering now that my FreeBSD system is coming up is completing work on my programming book (thanks to some messages with Greg Lehey). Anyway, a major portion of this book concerns the different ipc functions -- sockets, shared memory, semaphores, etc. I have refined some classes over the past several years which I was going to highlight. I figured I would complete the refining process on my FreeBSD box and prepare them for publication here. Well, this thread is making me somewhat nervous. Being really new to the whole FreeBSD world, I don't know where, or how, to check this 'whiteboard.' Can anyone point me to a list of the bugs in the ipc functions? Who are the people working on them? What kind of help do they need? Can I try to abuse some of the fixes for them? Needless to say, if I'm going to write my book and use FreeBSD as the base os for my source, I have a somewhat vested interest in ensuring the os works. And more than that, ensure it is compatible with the other flavors of unix. Thanks for any pointers/help you can pass along... Lee