From: Alejandro Colomar <alx.manpages@gmail.com>
To: Helge Kreutzmann <debian@helgefjell.de>
Cc: mario.blaettermann@gmail.com, linux-man@vger.kernel.org
Subject: Re: Issue in man page nfsservctl.2
Date: Sun, 12 Mar 2023 00:31:05 +0100 [thread overview]
Message-ID: <730751cc-f526-2378-98ba-36834f4c5d8e@gmail.com> (raw)
In-Reply-To: <20230311171355.GA4755@Debian-50-lenny-64-minimal>
[-- Attachment #1.1: Type: text/plain, Size: 1033 bytes --]
Hi Helge,
On 3/11/23 18:13, Helge Kreutzmann wrote:
> Without further ado, the following was found:
>
> Issue: mountd(8) → B<mountd>(8)
We don't use that formatting in example code.
Cheers,
Alex
>
> "/*\n"
> " * These are the commands understood by nfsctl().\n"
> " */\n"
> "#define NFSCTL_SVC 0 /* This is a server process. */\n"
> "#define NFSCTL_ADDCLIENT 1 /* Add an NFS client. */\n"
> "#define NFSCTL_DELCLIENT 2 /* Remove an NFS client. */\n"
> "#define NFSCTL_EXPORT 3 /* Export a filesystem. */\n"
> "#define NFSCTL_UNEXPORT 4 /* Unexport a filesystem. */\n"
> "#define NFSCTL_UGIDUPDATE 5 /* Update a client\\[aq]s UID/GID map\n"
> " (only in Linux 2.4.x and earlier). */\n"
> "#define NFSCTL_GETFH 6 /* Get a file handle (used by mountd(8))\n"
> " (only in Linux 2.4.x and earlier). */\n"
--
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-03-11 23:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-11 17:13 Issue in man page nfsservctl.2 Helge Kreutzmann
2023-03-11 23:31 ` Alejandro Colomar [this message]
2023-03-12 5:23 ` Helge Kreutzmann
2023-03-12 17:11 ` G. Branden Robinson
2023-03-12 17:55 ` Helge Kreutzmann
-- strict thread matches above, loose matches on Subject: below --
2023-11-01 14:02 Helge Kreutzmann
2023-11-01 15:44 ` Alejandro Colomar
2023-01-22 19:31 Helge Kreutzmann
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=730751cc-f526-2378-98ba-36834f4c5d8e@gmail.com \
--to=alx.manpages@gmail.com \
--cc=debian@helgefjell.de \
--cc=linux-man@vger.kernel.org \
--cc=mario.blaettermann@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.
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.