I'm going try to setup a fileserver for my private network.
I 'googled' a little and came up the the following information:
When i want to setup an fileserver for a *nix environment a need NFS.
And when I want to set up a fileserver where window$ clients have to log on to I need Samba.
Do I have to have more info to make a choice? And there any more options do make a fileserver?
T.i.a
Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
Fileserver
There are lots of options, of course. However, if you want to interact with windows computers, samba may be the only alternative. Anyway, there is Coda, which is similar to NFS, or you can make your Linux box act as a NetWare server.
Usually, NFS if the easiest to set up, Samba is a bit more complicated, but yet very easy. NetWare shares are tricky to configure, and I never configured Coda myself.
NFS practically can't handle errors, as well as Samba is tend to 'stick' there if a computer is gone, but there are some workarounds.
I would say use Samba, it is fairly easy to set up, you can browse samba shares without mounting them, and there are many tools available for dealing with Samba shares. Not to mention, again, it is probably the only one Windows will recognize...
Usually, NFS if the easiest to set up, Samba is a bit more complicated, but yet very easy. NetWare shares are tricky to configure, and I never configured Coda myself.
NFS practically can't handle errors, as well as Samba is tend to 'stick' there if a computer is gone, but there are some workarounds.
I would say use Samba, it is fairly easy to set up, you can browse samba shares without mounting them, and there are many tools available for dealing with Samba shares. Not to mention, again, it is probably the only one Windows will recognize...