Hi Ross,
Following up with the zz-nfs4 hook workaround, I found that it didn't work
because copy_exec won't overwrite an existing file. I do not know if this
was always the case, or perhaps it changed since the original workaround
was posted.
My zz-nfs4 looks like this now and does replace /bin/n
Package: klibc-utils
Version: 2.0.8-6.1
Followup-For: Bug #409272
X-Debbugs-Cc: rossboy...@stanfordalumni.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Earlier in this bug, Trent Buck suggested an initramfs hook zz-nfs4 to work
around the problem. I tried it, but I still can't get an NFS 4
Trent W. Buck wrote:
> 3. A single mount(2) call also works!
>
> It is quite annoying that we need *anything* special in userland, because
> a nfsvers=4.2,sec=sys mount requires only 2049/tcp (no other ports/services),
> and
> the actual filesystem is in-kernel, so
> really all that should be n
Short version:
1. nfsmount(8klibc) is still explicitly broken for NFSv4.
2. mount.nfs(8nfs-utils) works in the ramdisk.
3. A single mount(2) call also works!
Boring detailed version follows.
John Goerzen wrote:
> nfsmount is incapable of mounting NFSv4 filesystems. It seems to have
> sup
4 matches
Mail list logo
