Date: Thu, 28 May 2009 10:03:08 +0530 From: Sujit K M <kmsujit@gmail.com> To: Zachary Loafman <zml@freebsd.org> Cc: steven.danneman@isilon.com, freebsd-arch@freebsd.org Subject: Re: pthread_setugid_np Message-ID: <74fe56020905272133r3f2ab491t962c6d0fe900e9d0@mail.gmail.com> In-Reply-To: <20090528041236.GA14687@isilon.com> References: <20090528000147.GB3704@isilon.com> <74fe56020905271931l4c8d4677h3bbcce6d8c8a8605@mail.gmail.com> <20090528024640.GC9388@isilon.com> <74fe56020905272039h6aed0724u38dbc25d0a1be6a7@mail.gmail.com> <20090528041236.GA14687@isilon.com>
next in thread | previous in thread | raw e-mail | index | archive | help
The Source code licensing show two license information. One the Apple license and Other the BSD License. The BSD License is to the Mach code that is present in the source code, presumably I assume. And this includes the pthread_setugid_np, but with some amount of rework with the apple OS X implementation. Are you sure that this feature was never present in any of the BSD. Or has it been moved out due to some performance requirement. As far I see if present in OS X, It is an high performance piece of code. But it need to be checked whether the code was present in earlier version of BSD. Which might make it easier for you to have it in your internal version. On Thu, May 28, 2009 at 9:42 AM, Zachary Loafman <zml@freebsd.org> wrote: > On Thu, May 28, 2009 at 09:09:28AM +0530, Sujit K M wrote: >> These are posix unix standards that you are going to be implementing. >> So if you are talking of only taking the interfaces, why is there any need >> to have objections. > > pthread_setugid_np is a non-portable pthread extension for per-thread > user/group impersonation on OS X. The _np on the function name is to > indicate its lack of portability to other OSes - it is not part of any > standard. There is no posix standard way to impersonate a user/group on > a per-thread basis - and, in fact, the OS X pthread_setugid_np interface > is the only one I know of in common use. > > I'm proposing introducing the same API and semantics to FreeBSD, thereby > vaguely pushing it further towards a standard. I don't really claim it's > the most elegant interface, though. > > -- > Zach Loafman | Staff Engineer | Isilon Systems > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?74fe56020905272133r3f2ab491t962c6d0fe900e9d0>