From: "Ludovic Courtès" <ludo@gnu.org>
To: Lars Bilke <lars.bilke@ufz.de>
Cc: 74667-done@debbugs.gnu.org, Maxim Cournoyer <maxim.cournoyer@gmail.com>
Subject: bug#74667: [PATCH v2] doc: Add note on nsncd as a replacement for nscd.
Date: Wed, 18 Dec 2024 12:10:02 +0100 [thread overview]
Message-ID: <87ttb1l01h.fsf@gnu.org> (raw)
In-Reply-To: <079ad8da9d2b2b319ac04ce33c0488ecf4fcaaf0.1734515506.git.lars.bilke@ufz.de> (Lars Bilke's message of "Wed, 18 Dec 2024 10:51:46 +0100")
[-- Attachment #1: Type: text/plain, Size: 216 bytes --]
Lars Bilke <lars.bilke@ufz.de> skribis:
> * doc/guix.texi Add note on nsncd in Name Service Switch section.
>
> Change-Id: Ib804ab2e7d83d13f8f81d875f957eae2304eb232
Applied with the changes below, thanks!
Ludo'.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: text/x-patch, Size: 722 bytes --]
diff --git a/doc/guix.texi b/doc/guix.texi
index 66ea834934..ca74afa3ce 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -1824,9 +1824,10 @@ Application Setup
files are loaded in the @command{nscd} process, not in applications
themselves.
+@cindex nsncd, replacement for nscd
Note that @command{nscd} is no longer provided on some GNU/Linux
-distros, such as Arch Linux (as of Dec. 2024). @command{nsncd} can beu
-sed as a drop-in-replacement. See
+distros, such as Arch Linux (as of Dec. 2024). @command{nsncd} can be
+used as a drop-in-replacement. See
@uref{https://github.com/twosigma/nsncd, the nsncd repository} and
@uref{https://flokli.de/posts/2022-11-18-nsncd/, this blog post} for
more information.
prev parent reply other threads:[~2024-12-18 11:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 11:01 [bug#74667] [PATCH] doc: Add note on nsncd as a replacement for nscd Lars Bilke
2024-12-12 22:08 ` Ludovic Courtès
2024-12-18 9:51 ` [bug#74667] [PATCH v2] " Lars Bilke
2024-12-18 11:10 ` Ludovic Courtès [this message]
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=87ttb1l01h.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=74667-done@debbugs.gnu.org \
--cc=lars.bilke@ufz.de \
--cc=maxim.cournoyer@gmail.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.