From owner-freebsd-current Tue Dec 17 19: 1:29 2002 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 BDE7337B401 for ; Tue, 17 Dec 2002 19:01:28 -0800 (PST) Received: from bluejay.mail.pas.earthlink.net (bluejay.mail.pas.earthlink.net [207.217.120.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4BF9A43E4A for ; Tue, 17 Dec 2002 19:01:28 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from [216.20.231.174] (helo=mindspring.com) by bluejay.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 18OUSY-00002z-00; Tue, 17 Dec 2002 19:01:22 -0800 Message-ID: <3DFFE48A.F48A6129@mindspring.com> Date: Tue, 17 Dec 2002 18:59:22 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Joe Kelsey Cc: freebsd-current@freebsd.org Subject: Re: Posix Semaphores in -CURRENT References: <3DF8F08E.8050809@mail.flyingcroc.net> <3DFA0771.BDFC87A8@mindspring.com> <3DFA0DAC.2070801@mail.flyingcroc.net> <3DFA1251.C4755C5B@mindspring.com> <3DFA18CC.8090205@mail.flyingcroc.net> <3DFC0464.A72308AC@mindspring.com> <3DFDEBEC.4090209@mail.flyingcroc.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a42ac15588523527384c56c1af95716b9f350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Joe Kelsey wrote: > > OK, this is a bug. The semantics don't conform to POSIX. > ... > > I rather imagine the correct thing to do is to root it in the FS, > > and, without a leading '/', treat it as relative to the process > > current directory. > > > > Basically, this is not a two line fix... it's a lot of work, to > > get a filesystem object to use. > > I think that it *is* a two-line fix. Remove the maximum length (or > impose a maximum length of MAX_PATHNAMELEN), and simply remove the whole > '/' checking. Then, the private namespace correctly emulates posix > semantics, except for the rooted versus relative stuff, which would be > *really* hard to do in a private namespace and of questionable value anyway. Sorry, but Garrett was right about the implementation: it should not be using a private namespace in the first place. Making it work for a private namespace that shouldn't be there in the first place seems really questionable, to me... -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message