Bug#738486: freebsd-nfs-common: NFSv4 non-functional due to missing nfsuserd and nfscbd

[Robert Millan <rmh@debian.org>]

Control: tag -1 help

Hi Roger,

Unfortunately we're very short on manpower to add new features. Do you
think you'd be able to help with this one?

On 09/02/2014 22:11, Roger Leigh wrote:
> Package: freebsd-nfs-common
> Version: 9.2+ds1-1+b1
> Severity: important
> 
> Dear Maintainer,
> 
> It does not appear possible to mount an NFSv4 filesystem
> with the current kfreebsd nfs packages.  nfsuserd is
> missing (needed both client and server side), and
> nfscbd is missing (needed client side for some
> configurations; not sure about the server).
> 
> I can get NFSv4 mounts working fine booting the system
> into a native FreeBSD 10.0-RELEASE install.  So it is
> configured correctly server-side.  It's just the
> kFreeBSD packages missing bits which are standard in
> the base FreeBSD install.  If they could be added,
> that would probably fix the problem.
> 
> Note that there may be additional other NFS daemons
> which I've missed.
> 
> 
> Thanks,
> Roger
> 
> 
> -- System Information:
> Debian Release: jessie/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable')
> Architecture: kfreebsd-amd64 (x86_64)
> 
> Kernel: kFreeBSD 10.0-1-amd64
> Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> 
> Versions of packages freebsd-nfs-common depends on:
> ii  libbsd0            0.6.0-1
> ii  libc0.1            2.17-97
> ii  libfreebsd-glue-0  0.2.17
> ii  libtirpc1          0.2.2-5
> ii  rpcbind            0.2.1-2
> 
> freebsd-nfs-common recommends no packages.
> 
> freebsd-nfs-common suggests no packages.
> 
> -- no debconf information
> 
> 


-- 
Robert Millan