From owner-freebsd-current@FreeBSD.ORG Mon Dec 13 22:21:35 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 75C8316A4CE; Mon, 13 Dec 2004 22:21:35 +0000 (GMT) Received: from mail.vicor-nb.com (bigwoop.vicor-nb.com [208.206.78.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5856D43D54; Mon, 13 Dec 2004 22:21:35 +0000 (GMT) (envelope-from julian@elischer.org) Received: from elischer.org (julian.vicor-nb.com [208.206.78.97]) by mail.vicor-nb.com (Postfix) with ESMTP id 432447A403; Mon, 13 Dec 2004 14:21:35 -0800 (PST) Message-ID: <41BE15EE.5060704@elischer.org> Date: Mon, 13 Dec 2004 14:21:34 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030516 X-Accept-Language: en, hu MIME-Version: 1.0 To: Joe Kelsey References: <1102975803.30309.196.camel@zircon.zircon.seattle.wa.us> In-Reply-To: <1102975803.30309.196.camel@zircon.zircon.seattle.wa.us> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: arch@freebsd.org cc: current@freebsd.org Subject: Re: Fixing Posix semaphores X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Dec 2004 22:21:35 -0000 Joe Kelsey wrote: >I have a desire to fix posix semaphores in at least 5.3. The current >implementation doesn't actually follow the "spirit" of the standard, >even though it technically qualifies in a somewhat degraded sense. I >refer to the fact that the current implementation treats posix >semaphores as completely contained inside the kernel and essentially >divorced from the filesystem. The true "spirit" of the standard places >the semaphores directly in the file system, similar to named pipes. >However the current implementation treats the supplied "name" as a >14-character identifier, required to begin with a slash and contain no >other slashes. Pretty weak. > >Well, in order to fix this, we need to add file system code and come up >with a new type. I currently have some time to spend on something like >this and am willing to put in whatever effort it takes. Does anyone >want to add their own ideas or requirements? > >I currently run 5.3, but I suppose I could think about running current >at some point in the future. > I don't think that the spirit is to do what you suggest. I have always interpretted it to be a separate namespace. does the posix "mknod" definition mention how to make a semaphore? An interesting problem but I'm not sure if it's needed.. P.S. CC's trimmed to arch (correct place) and current (not so correct but ok) next round should probably stay on just "arch". > >/Joe > > >_______________________________________________ >freebsd-current@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-current >To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > >