I'll
try to orginize this all in a more coherent writeup later (if I'm
successful) but if anyone is attempting to backport nfsv4 to suse 9.3
x86_64 and you are building it from the instructions found at http://www.citi.umich.edu/projects/nfsv4/linux/user-build.html you
will soon learn that while compiling the libgssapi, the "configure" complains
about the following:
susebox:/build/NFS4/libgssapi-0.4 #
./configure
...
checking for Kerberos v5... configure:
error: Kerberos v5 with GSS support not
found
susebox:/build/NFS4/libgssapi-0.4 #
At the
end of this email is the diff on how to hack a fix into
the "configure" script so this false statement can be corrected and allow
you to compile.
Basically the for loop does not look in /usr/lib/mit
which is where krb5-config is ultimately found (/usr/lib/mit/bin/krb5-config).
But that still doesn't do you any good since it returns that libs are installed
in "/usr/lib/mit" HOWEVER the configure script is looking for
"include/gssapi/gssapi_krb5.h and
"lib/libgssapi_krb5.so" and these guys are install with the prefix "/usr" NOT
"/usr/lib/mit". Furthermore it not picking up "/usr/lib64/libgssapi_krb5.so"
which it should since this is a 64-bit installation. The first problem is CITI
didn't think to look in /usr/lib/mit which is paritially a suse issue since this
seems like a really non-standard location. The second is a suse package problem
which is confusing the correct thinking of the "configure" script to look for
build information from the krb5-config program. Not sure who owns the 64-bit
issues: Suse or CITI.
I hope
this is corrected somehow in Suse 10 Update 1. Anybody else working this issue
that's further along that I am or would like to collaborate?
susebox:/build/NFS4 # diff -Naur
libgssapi-0.4/configure configure.new
---
libgssapi-0.4/configure 2005-05-02 16:22:25.000000000
-0400
+++ configure.new 2005-08-10 17:43:11.202009000
-0400
@@ -22909,7 +22909,7 @@
fi;
for dir in $krb5_with /usr /usr/kerberos
/usr/local /usr/local/krb5
\
- /usr/krb5
/usr/heimdal /usr/local/heimdal /usr/athena ;
do
+ /usr/krb5
/usr/heimdal /usr/local/heimdal /usr/athena /usr/lib/mit;
do
K5CONFIG=""
if test
-f $dir/bin/krb5-config; then
K5CONFIG=$dir/bin/krb5-config
@@ -22925,9 +22925,9 @@
#define
KRB5_VERSION $K5VERS
_ACEOF
- if test -f
$dir/include/gssapi/gssapi_krb5.h -a
\
- \( -f
$dir/lib/libgssapi_krb5.a -o
\
- -f
$dir/lib/libgssapi_krb5.so \) ; then
+ if test -f
/usr/include/gssapi/gssapi_krb5.h -a
\
+ \( -f
/usr/lib64/libgssapi_krb5.a -o
\
+ -f
/usr/lib64/libgssapi_krb5.so \) ; then
cat >>confdefs.h
<<\_ACEOF
#define HAVE_KRB5
susebox:/build/NFS4
#
Well, I just installed Suse 10 and I was hugely disappointed to see
that the mount command does not support "nfs4" in the vfstype
option.
Does
anyone know if nfs4 will be included in any of the upcoming beta relases of
10?
Thanks,
I'm interested
in using NFSv4 on Suse and would like to know where I can find more
information on the inclusion of NFSv4 on the upcoming Suse 10 release. The
following link is a search in Bugzilla for NFS in suse 10 but there were no
hits.
I've started some basic testing of NFS
using Fedora Core 3 to simply familiarize myself with new procedures and
features involved in NFSv4 and though NFSv4 will likey be included in Suse
10 in about a month at it's official release, I think the time spent looking
at the setup details will only further my understanding of it. However, it
would be helpful to see how suse is planning on implimenting it's inclusion
in version 10, which I assume it is, so my learning is as accurate to
the official suse implimentation as
possible.
Also I'm interested in any feedback
from users who have introduced NFSv4 on linux into production. It seems Red
Hat introduced NFSv4 into production in their RHELv4 release. Has anybody
had an issues that would suggest the inclusion was premature especially in
light of the NFSv4 websites below that seem to suggest that the linux
implimentation is not yet completely
finished?
Thanks,
Reference
Links
---------------------------
NFSv4 - Linux
Web Portal
Learning NFSv4
with Fedora Core 2
(backporting)