From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 14 16:08:56 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8E51D16A4CE for ; Tue, 14 Dec 2004 16:08:56 +0000 (GMT) Received: from web52709.mail.yahoo.com (web52709.mail.yahoo.com [206.190.39.160]) by mx1.FreeBSD.org (Postfix) with SMTP id 317F943D48 for ; Tue, 14 Dec 2004 16:08:56 +0000 (GMT) (envelope-from kamalpr@yahoo.com) Received: (qmail 33009 invoked by uid 60001); 14 Dec 2004 16:08:55 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=uZKhgcmmaGuva09nlh9zGwSG9iXm8ei8AzCScUiQ8GmrfcOr3uQVxgGrwNvpVwIsxytkv6LQQo3+VyV6Lm5OdRkngWdWGV3CjDUh4hhWhpfzp+4euxsnGBAQLiXBwXeDbmFN0RRg02sTZBmm+3PBIilLqYkAPd6sCSCRzVoKmAs= ; Message-ID: <20041214160855.33007.qmail@web52709.mail.yahoo.com> Received: from [202.142.94.194] by web52709.mail.yahoo.com via HTTP; Tue, 14 Dec 2004 08:08:55 PST Date: Tue, 14 Dec 2004 08:08:55 -0800 (PST) From: "Kamal R. Prasad" To: Joe Kelsey In-Reply-To: <1102975803.30309.196.camel@zircon.zircon.seattle.wa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: freebsd-hackers@freebsd.org Subject: Re: Fixing Posix semaphores X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: kamalp@acm.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Dec 2004 16:08:56 -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. >From the opengroup website:- http://www.opengroup.org/onlinepubs/7990989775/xsh/sem_open.html "It is unspecified whether the name appears in the file system and is visible to functions that take pathnames as arguments. " >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? > You need to allow the user to provide a fully qualified pathname as an argument -and if the implementation doesn't allow that, that would be a BUG. But requiring the supplied name to be a valid pathname is not mandated by the std. BTW -how would you deal with a diskless workstation running Freebsd? regards -kamal __________________________________ Do you Yahoo!? Dress up your holiday email, Hollywood style. Learn more. http://celebrity.mail.yahoo.com