Hi Tony. I have used Busybox mount to acces NFS shares that are on another dCore-bionic machine. My desktop client does not have nfs-common or nfs-kernel-server installed as packages. On the server side with dCore-bionic, I did:
sce-import nfs-kernel-server
sce-import filesystems-4.14.10-tinycore
Substitute the filesystems-4.14.10-tinycore with whatever version that is required. Then, the below is my /etc/exports file on the dCore-bionic server to share /usr/bin as a test.
# /etc/exports: the access control list for filesystems which may be exported
# to NFS clients. See exports(5).
#
# Example for NFSv2 and NFSv3:
/usr/bin 192.168.0.*(fsid=0,rw,sync,no_subtree_check)
#
# Example for NFSv4:
# /srv/nfs4 gss/krb5i(rw,sync,fsid=0,crossmnt,no_subtree_check)
# /srv/nfs4/homes gss/krb5i(rw,sync,no_subtree_check)
#
This is of course if the network is 192.168.0.*.
On the server if dCore, the following commands start the NFS server:
/etc/init.d/rpcbind start
/etc/init.d/nfs-kernel-server start
Then I do not import anything on the client, there are no NFS related packages on it, just Busybox. Then I do the below:
sudo sh
mkdir /tmp/1
busybox mount -o nolock 192.168.0.7:/usr/bin/ /tmp/1
That is, if the server's address is 192.168.0.7, of course.
The mount package from Debian/Ubuntu is in dCore base for boot performance reasons, hence the need to specify
busybox mount
on the command line.
Or one can append "/bb" to the front of their PATH.
If you want to mount an NFS share as a user and not root, enter the below in /etc/fstab to do the above as a user:
192.168.0.7:/usr/bin /tmp/1 nfs rw,noauto,user 0 0
Then use the command:
busybox mount -o nolock /tmp/1
Let me know how Busybox works with NFS mounts.