NFS access
asked 2013-12-25 11:33:28 +0200
On my N900 I had access to all my nfs-shares, will it be possible in Sailfish OS?
@AL13N not much more 'dangerous' than using sshfs or similar
javispedro ( 2014-01-04 23:03:07 +0200 )edit 3 Answers
answered 2014-01-04 19:23:27 +0200
You do not need nfs-tools or anything else to mount NFS partitions, the kernel is recent enough to parse NFS options on its own. E.g something like this:
mount -t nfs -o nolock,addr=192.168.1.2 my_server:/var/srv/nfs /mnt/tmp
The nolock parameter is mandatory without a working portmapper, and the addr parameter is mandatory (must be a IP, hostnames will not be resolved). The reason is that normally nfs-utils (mount.nfs) is the one resolving IPs and adding this parameter.
Comments
answered 2013-12-25 14:13:09 +0200
NFS is enabled in the kernel:
$ grep -i nfs config-3.4.0.20131118.1
# CONFIG_USB_FUNCTIONFS is not set
CONFIG_NFS_FS=m
CONFIG_NFS_V3=y
CONFIG_NFS_V3_ACL=y
CONFIG_NFS_V4=y
# CONFIG_NFS_V4_1 is not set
# CONFIG_NFS_USE_LEGACY_DNS is not set
CONFIG_NFS_USE_KERNEL_DNS=y
# CONFIG_NFSD is not set
CONFIG_NFS_ACL_SUPPORT=m
CONFIG_NFS_COMMON=y
$ modinfo nfs
filename: /lib/modules/3.4.0.20131118.1/kernel/fs/nfs/nfs.ko
but unfortunately the nfs-tools are missing in Sailfish OS. I've packaged them once, it worked back then in a Nemo image. But I didn't maintain it. So not sure if it still builds. But it can be used as a start for a Sailfish OS version of the rpms. Here the OBS project: https://build.merproject.org/project/packages?project=home%3Akontio%3Anfs
Comments
answered 2014-01-09 00:20:55 +0200
Hello i was able to mount my nfs4 server on the Jolla without any problems, bellow i post the fstab entry, for me the key was the option addr=192.168.X.X
serverName:/ /home/nemo/remote/serverName/nfs nfs4 nolock,addr=192.168.X.X,noauto,_netdev 0 2
For more information about nfs have a look a this wiki https://wiki.archlinux.org/index.php/Nfs
Comments
@stimpson The noauto mount option tells systemd not to automatically mount the shares at boot. systemd would otherwise attempt to mount the nfs shares that may or may not exist on the network causing the boot process to appear to stall on a blank screen.
I rather prefer mounting shares manually
corsarium ( 2014-01-09 22:39:06 +0200 )edit@corsarium keep in mind that the nofail option (ancient, but only systemd actually uses it as intended), will make mounting that entry only later in the boot process, which will not cause other network failure to fuck with the boot process
AL13N ( 2014-01-10 09:03:24 +0200 )editStats
Asked: 2013-12-25 11:33:28 +0200
Seen: 1,720 times
Last updated: Jan 09 '14
Quite certainly samba and nfs-utils can easily be built for Nemo, if they aren't already. You should specify if you're looking for a GUI to be developed.
lkraav ( 2013-12-25 13:38:23 +0200 )editsee NFS app request for the GUI request
AL13N ( 2013-12-26 19:25:36 +0200 )edit