From: Thorsten Kukuk <kukuk@suse.de>
To: Ulrich Drepper <drepper@redhat.com>
Cc: libc-hacker@sources.redhat.com
Subject: Re: NSS not longer exporting parser
Date: Thu, 18 Apr 2002 23:14:00 -0000 [thread overview]
Message-ID: <20020419081438.A19529@suse.de> (raw)
In-Reply-To: <1019186656.29427.169.camel@akkadia.org>
[-- Attachment #1: Type: text/plain, Size: 637 bytes --]
On Thu, Apr 18, Ulrich Drepper wrote:
> On Wed, 2002-04-17 at 02:03, Thorsten Kukuk wrote:
>
> > As result, most other NSS modules (even the one from glibc), which
> > uses the files parser, does not work any longer.
>
> Which NSS module doesn't work?
For example the libnss_db module, which we splitt of from glibc.
Thorsten
--
Thorsten Kukuk http://www.suse.de/~kukuk/ kukuk@suse.de
SuSE Linux AG Deutschherrenstr. 15-19 D-90429 Nuernberg
--------------------------------------------------------------------
Key fingerprint = A368 676B 5E1B 3E46 CFCE 2D97 F8FD 4E23 56C6 FB4B
[-- Attachment #2: Type: application/pgp-signature, Size: 240 bytes --]
next prev parent reply other threads:[~2002-04-19 6:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-17 2:03 Thorsten Kukuk
2002-04-18 20:24 ` Ulrich Drepper
2002-04-18 23:14 ` Thorsten Kukuk [this message]
2002-04-18 23:44 ` Ulrich Drepper
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020419081438.A19529@suse.de \
--to=kukuk@suse.de \
--cc=drepper@redhat.com \
--cc=libc-hacker@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).