[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140720014516.GJ17402@brightrain.aerifal.cx>
Date: Sat, 19 Jul 2014 21:45:16 -0400
From: Rich Felker <dalias@...c.org>
To: musl@...ts.openwall.com
Cc: beck@...nbsd.org, Brent Cook <busterb@...il.com>
Subject: Re: [PATCH] implement issetugid(2) (v4)
On Sat, Jul 19, 2014 at 04:07:25PM -0400, Rich Felker wrote:
> On Wed, Jul 16, 2014 at 09:33:11PM -0500, Brent Cook wrote:
> > > My leaning so far is to include issetugid even if the glibc folks
> > > don't want to, since there seems to be no remotely portable way to
> > > achieve the same thing without it. The suggestion of using getauxval
> > > is much more low-level and tied to particular implementations (ELF or
> > > ELF-like ones with aux vector or which emulate it), and I don't think
> > > it's a reliable approach for applications linked to musl (since they
> > > might be running on a 2.4 kernel). So even if software has to have a
> > > fallback for glibc systems, I'd prefer that it use a libc-provided
> > > issetugid() on musl so that we can provide a reliable answer rather
> > > than asking the caller to make assumptions about the system.
> >
> > OK, thanks for considering it.
>
> Based on the discussion so far, I'm going to commit it.
Committed!
Rich
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
