[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAL3m8eB90ccydOhr0=3B=Vvdie+abCQ22tHATA6=2ApBEDO8Uw@mail.gmail.com>
Date: Mon, 23 Feb 2015 11:01:11 -0500
From: M Farkas-Dyck <strake888@...il.com>
To: musl@...ts.openwall.com
Subject: Re: [PATCH] support alternate backends for the passwd and
group dbs
On 23/02/2015, Rich Felker <dalias@...c.org> wrote:
> There were multiple discussions of how to support alternate backends
> in the past, and the main two candidates were a new text-based
> protocol over a unix socket that returns the result in passwd/group
> file form, and repurposing nscd protocol. While I originally preferred
> the former, using nscd has the advantage that, on existing glibc
> systems with non-default (possibly even custom nss modules) backends,
> everything works out of the box. Using a new protocol/new daemon would
> require installing that daemon before any musl-linked binaries could
> lookup users/groups, and would require significant custom glue to
> integrate with custom site-local backends.
For nonstatic non-nsc backends, one could alternately have files in
question on synthetic filesystem, e.g. 9p, so backend program would
simply be synthetic filesystem server and musl wouldn't need to care.
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.
