Difference between revisions of "Nfs"
From Fixme.ch
(→configuration) |
(→configuration) |
||
Line 27: | Line 27: | ||
/media/disk1/music [2001:788:dead::/48](ro,subtree_check,sync) | /media/disk1/music [2001:788:dead::/48](ro,subtree_check,sync) | ||
− | /media/disk1/stl 62.220.135.192/26( | + | /media/disk1/stl 62.220.135.192/26(rw,subtree_check,sync) |
− | /media/disk1/stl [2001:788:dead::/48]( | + | /media/disk1/stl [2001:788:dead::/48](rw,subtree_check,sync) |
</pre> | </pre> |
Revision as of 18:09, 15 July 2013
Contents
Remark
To start things up, I sincerely think that NAT is a bad things on a philosophical level. If you however want the nfs to support it, you're welcome to add it. So don't connect to the fixme nat in the first place.
How to
First start the rpcbind daemon and the nfs-common daemon on debian or similar (ubuntu for example)
sudo init.d start rpcbind nfs-common
OR on arch
sudo rc.d start rpcbind nfs-common
(Note: if you don't have rpcbind, just use portmap instead. Then simply mount that little boy
sudo mount nfs.fixme.ch:/media/disk1/music /mnt
Yes, that's all little slacker :).
- /media/disk1/share : Used by the Ftp server, accessible within the hackerspace Network by everyone.
- /media/disk1/music : Used by MPD Daemon, accessible within the hackerspace Network.
- /media/disk1/tftp : Used by the tftp server for pxe.
configuration
the export file is :
/media/disk1/tftp 62.220.135.192/26(ro,sync,no_subtree_check) /media/disk1/tftp [2001:788:dead::/48](ro,sync,no_subtree_check) /media/disk1/music 62.220.135.192/26(ro,subtree_check,sync) /media/disk1/music [2001:788:dead::/48](ro,subtree_check,sync) /media/disk1/stl 62.220.135.192/26(rw,subtree_check,sync) /media/disk1/stl [2001:788:dead::/48](rw,subtree_check,sync)