Package: nfs-kernel-server
Version: 1:1.1.2-6lenny1
Followup-For: Bug #446238


Recently I tried updating my nfs shares to nfs4. I haven't been able to get 
them running. 
While working the problem, I found the following excerpt in the options 
category of the mountd 
manpage:

-V or --nfs-version
This option can be used to request that rpc.mountd offer certain
versions of NFS. The current version of rpc.mountd can support
both NFS version 2 and the newer version 3.

To me, this implies that mountd is not yet compatible with nfs4. If that's the 
case, setting 
up fstab as recommended in the nfs manpage is irrelevant because you can't hook 
it up (mount 
it) even if it's tabled correclty.


-- System Information:
Debian Release: 5.0.2
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26-2-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages nfs-kernel-server depends on:
ii  libblkid1       1.41.3-1                 block device id library
ii  libc6           2.7-18                   GNU C Library: Shared libraries
ii  libcomerr2      1.41.3-1                 common error description library
ii  libgssglue1     0.1-2                    mechanism-switch gssapi library
ii  libkrb53        1.6.dfsg.4~beta1-5lenny1 MIT Kerberos runtime libraries
ii  libnfsidmap2    0.20-1                   An nfs idmapping library
ii  librpcsecgss3   0.18-1                   allows secure rpc communication us
ii  libwrap0        7.6.q-16                 Wietse Venema's TCP wrappers libra
ii  lsb-base        3.2-20                   Linux Standard Base 3.2 init scrip
ii  nfs-common      1:1.1.2-6lenny1          NFS support files common to client
ii  ucf             3.0016                   Update Configuration File: preserv

nfs-kernel-server recommends no packages.

nfs-kernel-server suggests no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to