From: Simo Sorce <simo@redhat.com>
To: steved@redhat.com
Cc: linux-nfs@vger.kernel.org, Simo Sorce <simo@redhat.com>
Subject: [PATCH 7/7] Kill SPKM3: Remove mentions of SPKM3 from README
Date: Fri, 9 Mar 2012 14:49:46 -0500 [thread overview]
Message-ID: <1331322586-4631-8-git-send-email-simo@redhat.com> (raw)
In-Reply-To: <1331322586-4631-1-git-send-email-simo@redhat.com>
Signed-off-by: Simo Sorce <simo@redhat.com>
---
README | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/README b/README
index e7588cfd9337257aef27a90471c0c6935e3bc990..5c86808d3628e30c665f87501a1cd465fda5c76d 100644
--- a/README
+++ b/README
@@ -80,7 +80,7 @@ scripts can be written to work correctly.
and starting the nfsd server is not important.
idmapd is only needed for NFSv4 support.
svcgssd is only needed if exportfs NFS filesystem with crypto-
- security (Kerberos or SPKM3).
+ security (Kerberos).
C/ exportfs -av ; rpc.mountd
It is important that exportfs be run before mountd so that
@@ -130,7 +130,7 @@ scripts can be written to work correctly.
B/ gssd ; idmapd
idmapd should be started before mounting any NFSv4 filesystems.
gssd should be started before mounting any NFS filesystems
- securely (with Kerberos of SPKM3).
+ securely (with Kerberos).
C/ statd should be run before any NFSv2 or NFSv3 filesystem is
mounted with remote locking (i.e. without -o nolock).
--
1.7.7.6
next prev parent reply other threads:[~2012-03-09 19:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-09 19:49 [PATCH 0/7] Kill SPKM3 auth method Simo Sorce
2012-03-09 19:49 ` [PATCH 1/7] Kill SPKM3: Remove spkm3 references from svcgssd Simo Sorce
2012-03-09 19:49 ` [PATCH 2/7] Kill SPKM3: Remove spkm3 support from gssd Simo Sorce
2012-03-09 19:49 ` [PATCH 3/7] Kill SPKM3: remove spkm3 from common gssd code Simo Sorce
2012-03-09 19:49 ` [PATCH 4/7] Kill SPKM3: Remove spkm3 support from nfs.mount Simo Sorce
2012-03-09 19:49 ` [PATCH 5/7] Kill SPKM3: Remove spkm3 support from exports Simo Sorce
2012-03-09 19:49 ` [PATCH 6/7] Kill SPKM3: Stop checking for spkm3.h in configure Simo Sorce
2012-03-09 19:49 ` Simo Sorce [this message]
2012-03-09 20:49 ` [PATCH 0/1] Kill SPKM3 auth method, addendum Simo Sorce
2012-03-09 20:49 ` [PATCH 1/1] Kill SPKM3: Remove also the dependent lipkey mechanism Simo Sorce
2012-03-09 21:31 ` [PATCH 0/7] Kill SPKM3 auth method Daniel Kahn Gillmor
2012-03-09 21:54 ` J. Bruce Fields
2012-03-11 3:32 ` Daniel Kahn Gillmor
2012-03-12 19:35 ` J. Bruce Fields
2012-03-12 20:35 ` Steve Dickson
-- strict thread matches above, loose matches on Subject: below --
2012-03-09 19:34 Simo Sorce
2012-03-09 19:34 ` [PATCH 7/7] Kill SPKM3: Remove mentions of SPKM3 from README Simo Sorce
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=1331322586-4631-8-git-send-email-simo@redhat.com \
--to=simo@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=steved@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