We have moved to a new Sailfish OS Forum. Please start new discussions there.

NFS access

asked 2013-12-25 11:33:28 +0300

Cermit gravatar image

updated 2013-12-26 19:07:39 +0300

pnuu gravatar image

On my N900 I had access to all my nfs-shares, will it be possible in Sailfish OS?

edit retag flag offensive close delete


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 +0300 )edit

see NFS app request for the GUI request

AL13N ( 2013-12-26 19:25:36 +0300 )edit

3 Answers

Sort by » oldest newest most voted

answered 2014-01-04 19:23:27 +0300

javispedro gravatar image

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= 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.

edit flag offensive delete publish link more


Works for me! Thanks for your answer!

Cermit ( 2014-01-04 21:41:43 +0300 )edit

myes, but nolock is a bit... dangerous if you use these at various places...

AL13N ( 2014-01-04 22:00:28 +0300 )edit

@AL13N not much more 'dangerous' than using sshfs or similar

javispedro ( 2014-01-04 23:03:07 +0300 )edit

i aint using sshfs either (or anything fuse-based for that matter)

AL13N ( 2014-01-05 00:01:28 +0300 )edit

answered 2013-12-25 14:13:09 +0300

Kontio gravatar image

updated 2013-12-25 14:13:52 +0300

NFS is enabled in the kernel:

$ grep -i nfs config- 
# CONFIG_NFS_V4_1 is not set
# CONFIG_NFSD is not set

$ modinfo nfs
filename:       /lib/modules/

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

edit flag offensive delete publish link more


If we can find some volunteer testers we can add that package to the Sailfish community repo on OBS.

tbr ( 2013-12-26 19:17:55 +0300 )edit

doesn't mer-tools have nfs-utils? i assumed so...

AL13N ( 2013-12-26 19:24:42 +0300 )edit

answered 2014-01-09 00:20:55 +0300

corsarium gravatar image

updated 2014-01-09 00:23:55 +0300

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

edit flag offensive delete publish link more


u should probably use autofs instead of fstab entry

stimpson ( 2014-01-09 03:40:08 +0300 )edit

@stimpson: why? fstab with noauto shouldn't do any harm (or even nofail , since we're using systemd), am i missing something?

AL13N ( 2014-01-09 22:19:34 +0300 )edit

@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 +0300 )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 +0300 )edit
Login/Signup to Answer

Question tools



Asked: 2013-12-25 11:33:28 +0300

Seen: 1,518 times

Last updated: Jan 09 '14