On Thursday 27 March 2008 19:35:57 Les Mikesell wrote:
Anne Wilson wrote:
On Thursday 27 March 2008 18:58:16 Scott Silva wrote:
on 3-27-2008 11:40 AM Anne Wilson spake the following:
On Thursday 27 March 2008 17:01:13 Les Mikesell wrote:
Anne Wilson wrote:
> It seems like a kludge to use cifs to share between two linux boxes.
Because I would have to do samba anyway, as windows laptops from other family members want to access from time to time. They always bring them to me if any configuration work or maintenance needs doing, and even to work on my LAN when their network is down for any reason. In particular, one directory that I samba share is a repository that my daughter and I both need access to, and its content changes fairly often. I didn't want to have to run two systems for sharing.
You can do both fairly easily and transparently. The usual reason for not using NFS is that it isn't secure if client users have local root access (or can boot something that would) - but that probably doesn't matter for a home setup.
I guess that when I've nothing more urgent to do I ought to read up on NFS.
Anne
NFS will be much better for the linux to linux connections because it passes native system calls on the files instead of a protocol that is emulated and made to work.
OK - apart from man pages and general googling, any particular recommended reading?
It's not that complicated unless you want automounting. On the server, edit /etc/exports and add something like:
/home 192.168.0.0/255.255.255.0(rw,async,no_root_squash) (your client subnet, of course) and service nfs restart (or exportfs -a if it is already running)
and on the clients where you want the same /home mounted in /etc/fstab add: server_name:/home /home nfs exec,rw,bg,soft,intr 0 0 and 'mount -a'
You need to have consistent login name to uid mapping across machines and all the usual 'yum install nfs', chkconfig and service invocations apply for installing and managing it.
With any luck I'll get some time tomorrow to take a look at that. Thanks
Anne