Re: Sharing files on a local network
On Sun, Oct 23, 2011 at 11:46:54PM BST, Arno Schuring wrote:
> > SSH (Secure Shell) - you don't need security on home-only network.
> That depends. If you're running a wireless setup, even with WPA2
> protection, I'd still advise security.
Let's not get paranoid - firewall + RSN should be enough on a home
network.
> > IMHO, it's not - dozens of options for both the server and client.
> > You simply mount the NFS share and it's transparent to the system.
> Well, in all fairness - NFS requires that the user ids on all systems
> match. Forcing such a match can be quite troublesome.
If we're talking about r/w access then it might be, yes. Then you'll
need NIS, LDAP or Kerberos.
> > FUSE as it name suggests is in user-space, NFS is supported in the
> > kernel. You don't have the overhead.
> Overhead is peanuts :)
>
> No, not really. But for a home setup, convenience trumps performance.
> And besides, when's the last time that your desktop machine was pegged
> on CPU?
I use some ancient machines, but I guess it's just me ;^)
> For the current situation, I'd advise sshfs. If it's integrated in
> Nautilus, all the better. But SSH is only point-to-point -- as soon as
> you're sharing files with more than 2 machines, NFS is the way to go.
Thank you, that's exactly the point I was trying to get across, file
access and file sharing are two different things.
> My 2 cents: even for Linux-only systems, there really is no
> satisfactory answer to the OP's question besides Samba/CIFS. All
> (Unix-)native solutions have their roots in enterprise (managed)
> networking, which implies manual setup. In terms of autodiscovery and
> autoconfiguration, nothing can hold a candle to the original SMB.
If we're talking about file sharing, not per user access, then r/w
will always be an issue, regardless of what protocol you're using,
unless you don't care about security at all.
Regardless of how you look at it, you'll need to set it up somehow -
either a server with a user database on it (SMB, SFTP, etc.) and
authenticate every time you connect to it, even if it's just for r/o
access; or set up a file storage server (e.g. NFS) with minimal effort.
Regards,
--
Raf
Reply to: