Had this running a few years back, lost my notes. This is for everyone who needs help. (like me)
I butchered this, probably the reason I can't get it working
Please correct what is wrong or missing.
Step One: Install NFS
from Root terminal
Equo search NFS
Refer to linuxfluesterer's and heindsight's comments about
sysvint (openrc) the old way I guess and systemd, the new way I guess , on how to proceed.
I only use External Hard Drives (usb) with NFS, and my External Hard Drive is called HDTwo.
I'm using the old way, for now, just read the comments on this thread to learn there was and how to make the systemd to change.
What I think I learned from this is for Fstab,....
Old way: //192.168.1.10:/HDTwo /media/HDTwo
New way: //192.168.1.10:/HDTwo /run/media/HDTwo
(is the Portmap needed? Anything else needed?)
Step Two: Identify your IP address
- enp4s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.10 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::224:1dff:fe27:e57d prefixlen 64 scopeid 0x20<link>
ether 00:24:1d:27:e5:7d txqueuelen 1000 (Ethernet)
RX packets 1220714 bytes 1072173442 (1022.5 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 964253 bytes 169997962 (162.1 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Files that need to be Edited "exports" "fstab" "hosts.allow"
To edit files as Root
Alt+F2 and then type
Step Three: EXPORTS
Now my PC is called devos, do I need that in there or just /run/media/HDTwo? Is fsid=0 needed or is that dependent on if using nsf3 or nsf4?
Speaking of nsf3 and nsf4, which one to use, and how to make sure that version is running, if only using FSTAB?
Step Four: FSTAB
- //192.168,1.10:/HDTwo /run/media/HDTwo nfs nfsvers=3,rw,noauto,user 0 0
I am messing up somewhere, it is probably something simple and starring me in the face. Cause this is not working.
the WDTV cannot see the NFS and the Rasberry PI with XBMC cannot see the NFS either.
Step Five: HOST.ALLOW
Put the IP address of who can see this NFS on you local network
For Example: I've got WD Live (SMP) and a Rasberry PI with XBMC on it.
I'm probably wrong but think the IP address of these two devices need to be on the host.allow.
There is also host.deny to put IP addresses of any IP address you do not want to have access to the NFS.
Step Six: INIT.D
When you make a change to the "exports" file.
(not sure what dash codes to use, see different variations when searching google)
To get the NFS to restart
(search google for other things that can be done, but I mostly just use the retart)
Summary: I got some of the things, but bottom line, it's not working.
Used to have it working, and when it was, I remember that Ubuntu's way had way more things that had to be done, but Sabayon only needed a few things.
Old way before systemd:
/home would eventually get to the external hard drive through /media.
New way with systemd:
/home does not work
is the acutal path, (devos is PC name) but thin, not sure, only need /run/media/HDTwo. but I am sooo not sure.
Re: Systemd nfs client mount share ???
Still mounting from fstab, but it works ok for now. Still wish I could understand native systemd mounting of nfs shares.
All else is up and running nicely! e4rat works ok, did a new 'collect' and it's really nice!
Edited fstab and disabled the dvd/cdrom line and now udisks mounts ok. Had a little problem with console-kit but managed to edit the slim.service to start the right slim version (svn in my local/bin).
Learned that systemctl rescue works as 'telinit 1' and that 'systemctl isolate runlevel5.target' should take you back to X.
But one big lesson never mentioned anywhere is that systemd takes over /media as tmpfs. For all those of us who in recent years have learned to use /media as mounting dir instead of /mnt, this is a problem. But it is fixable.
#12 2012-04-17 17:49:50
Re: Systemd nfs client mount share ???
systemd will leave /media alone as of the next release (/media was meant to be used by udisks and similar tools, which have now moved to /run/media).
There is no benefit of using mount units over fstab, but it's a bit strange if it does not work for you (it should be the same). The main use of the mount units is that they can be shipped by packages (such as systemd itself), and fstab should be only for the admin.
this is where I got the run/media info from.
Again, I butchered this, but hopefully the end resul, wil be a HOW TO: in the Wiki.