Bug 14346

Summary: BR2_PACKAGE_NFS_UTILS_RPC_NFSD does not patch CONFIG_NFSD in kernel configuration
Product: buildroot Reporter: Mateusz Dukat <mateusz.dukat1>
Component: OtherAssignee: unassigned
Status: RESOLVED MOVED    
Severity: minor CC: buildroot, yann.morin.1998
Priority: P5    
Version: 2021.02.7   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Host: Target:
Build:

Description Mateusz Dukat 2021-11-16 01:06:44 UTC 
Overview:

Setting BR2_PACKAGE_NFS_UTILS_RPC_NFSD to 'y' does not patch CONFIG_NFSD in Linux kernel configuration.

Steps to reproduce:

1) Build buildroot for i386, with kernel defconfig, and buildroot config values:
BR2_PACKAGE_NFS_UTILS_RPC_NFSD=y
2) Run image on any machine/vm

Actual results:

When booting buildroot built like that, it immediately throws:

> Starting NFS daemon: rpc.nfsd: Unable to access /proc/fs/nfsd errno 2 (No such file or directory).
> Please try, as root, 'mount -t nfsd nfsd /proc/fs/nfsd' and then restart rpc.nfsd to correct the problem
> FAIL

Expected results:

NFS server starts correctly.

Build date and hardware:

Buildroot tag 2021.02.7 built on 16.11.2021 on Thinkpad X131e (intel) \w Ubuntu server 20.04 LTS

Additional information:

To manually fix this problem, create text file in buildroot root directory named "kernel_patch.txt" with value:

> CONFIG_NFSD=y

Then, in buildroot config, modify BR2_LINUX_KERNEL_CONFIG_FRAGMENT_FILES to:

> BR2_LINUX_KERNEL_CONFIG_FRAGMENT_FILES="kernel_patch.txt"

And finally build new image.
Comment 1 Fabrice Fontaine 2021-11-21 10:33:45 UTC 
Can you confirm that the following patch fix your issue:
https://patchwork.ozlabs.org/project/buildroot/patch/20211119164926.2410106-1-fontaine.fabrice@gmail.com/
Comment 2 Yann E. MORIN 2024-06-15 15:00:09 UTC 
Thank you for your report.

The issue tracker for the Buildroot project has been moved to
the Gitlab.com issue tracker:
    https://gitlab.com/buildroot.org/buildroot/-/issues

We are taking this opportunity to close old issues in this old
tracker. If you believe your issue is still relevant, please
open one in the new issue tracker.

Thank you!