Is there any usable way for creating accessible network shares on Linux (Fedora 15)?

anon112 · 06-29-2011, 09:47 PM

Currently I am trying to get some fedora shares to simply connect to each other to access a read-only shared folder on a host machine (no security/encryption even required for these files!).

I've tried to get a smb network share going but that didn't work (can't connect with nautilus), I've tried a quick fix with daap and rhythmbox so that they can at least access the music, but rhythmbox fails very miserably trying to connect/create that (and mt-daapd didn't help much) - Basically I get errors saying the host is unreachable.

I haven't even set up a firewall yet for this network and already I'm running into these fundamental problems.

Currently I'm using Fedora 15. On a whim I tried the "public" folder and had sharing of the public folder over the network enabled - yep, didn't work (and I certainly didn't expect it to).

I would be trying some more advanced CLI stuff, setting up an ssh server or something, but the computer-challenged people who have to access these files just want to be able to click something and have it work.

For the operational requirements of this setup, a file synchronisation system would work (although highly inefficient since it would mean gigabytes sent over the network).

So, does anybody have any ideas for this?

Lexus45 · 06-29-2011, 11:37 PM

Using Samba between Linux boxes may seem a little bit strange, though it's possible.
So, if you use Samba, show us please your config output.

Code:

testparm

The native Unix way for this task is sing Network File System. You may read about it in a nutshell in part 5.6.2 of the Slackbook.

frieza · 06-29-2011, 11:50 PM

for Linux to Linux file sharing, samba is pointless, that's for sharing to windows machines, yes it works but it's like using a screwdriver to hit in a nail, not the proper tool for the job
with Linux to Linux you have NFS file shares, which is native to most *NIX operating systems
to do this you create a file (or edit it if it already exists)
/etc/exports
on the 'server' end
it should look something like

Code:

#directory      allowed ip (options)
/mnt/data       192.168.2.2(rw,no_root_squash)
/home/hopper    192.168.2.2(rw,no_root_squash)

then do

Code:

su -c '/etc/init.d/nfs restart'

then on the client end you just do

Code:

mount -t nfs {server_ip}:{/exported/directory} {mount/point}

or you can make it permanent by adding the share by adding it to /etc/fstab

Code:

192.168.2.2:/media/music	/media/music	nfs	defaults	0 0

anon112 · 06-30-2011, 08:19 AM

Will try NFS -- I was mostly thinking that if anybody happened to bring over a Windows machine there might be a possibility of interoperability between operating systems if I used samba. Will post if I have further difficulties.

Thanks,
Kev717

frieza · 06-30-2011, 11:19 AM

Quote:

Originally Posted by kev717

Will try NFS -- I was mostly thinking that if anybody happened to bring over a Windows machine there might be a possibility of interoperability between operating systems if I used samba. Will post if I have further difficulties.

Thanks,
Kev717

you can always share a directory via both nfs AND samba on the off that someone has a windows machine, if that is what you are interested in doing, i've done it before.