| Summary: | netmount does not handle nfs4 tag in fstab. | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Bel Zébute <stephane> |
| Component: | [OLD] baselayout | Assignee: | Gentoo's Team for Core System packages <base-system> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
you neglected to provide `emerge info` like the bug report page told you to that said i'm pretty sure you have baselayout-1.9.x seeing as how i added nfs4 support to baselayout-1.11.x already |
netmount does not recognise nfs4 types in the fstab. It all lay down to the awk line that need to be modified in the netmount script. My fstab example is as follow: 192.168.0.1:/ /home nfs4 rsize=8192,wsize=8192,intr,rw,hard,proto=tcp,port=2049 0 0 192.168.0.1:/usr/portage /usr/portage nfs rsize=8192,wsize=8192,intr 0 0 Reproducible: Always Steps to Reproduce: # awk '!/^#/ && $3 == "nfs" && $4 !~ /noauto/ { print $0 }' /etc/fstab Actual Results: S192.168.0.1:/usr/portage /usr/portage nfs rsize=8192,wsize=8192,intr 0 0 Expected Results: 192.168.0.1:/ /home nfs4 rsize=8192,wsize=8192,intr,rw,hard,proto=tcp,port=2049 0 0 192.168.0.1:/usr/portage /usr/portage nfs rsize=8192,wsize=8192,intr 0 0 Of course, when using this line, it works: # awk '!/^#/ && ( $3 == "nfs" || $3 == "nfs4" ) && $4 !~ /noauto/ { print $0 }' /etc/fstab