From: "J. Bruce Fields" <bfields@fieldses.org>
To: mtk.manpages@gmail.com
Cc: linux-man@vger.kernel.org, NeilBrown <neilb@suse.de>,
linux-nfs@vger.kernel.org
Subject: Re: nfsservctl(2)
Date: Mon, 8 Aug 2011 12:23:28 -0400 [thread overview]
Message-ID: <20110808162328.GD904@fieldses.org> (raw)
In-Reply-To: <20110808162232.GC904@fieldses.org>
The nfsservctl system call has long been superceded by a better
interface, and is finally getting removed in the 3.1 kernel.
I'm not sure what to do with the man page--remove it, or add a note
saying it's gone from recent kernels? Do you have something you
generally do in such cases?
It's been replaced by a set of files in the nfsd filesystem, which is
documented in nfsd(7). That man page looks sufficiently up-to-date to
cover the functionality previous provided by nfsservctl. (Though I only
skimmed it quickly. It might be worth a more careful review some day.)
--b.
(Argh, sorry, resending with cut-n-pasted addresses de-obfuscated.)
prev parent reply other threads:[~2011-08-08 16:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-08 16:22 nfsservctl(2) J. Bruce Fields
2011-08-08 16:23 ` J. Bruce Fields [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=20110808162328.GD904@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-man@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=neilb@suse.de \
/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