Steve Nadjari wrote:
Can someone please kindly tell me what is the best scenario or ideas for my situation, of how to networked them together. I've read a posting with similar situation and he was using Samba, and then both Windows and Linux clients (via Linux's Samba Client) can connect well. But I also understand that Linux has their own native connection way, which would not require Samba, and eBox is also Linux. So, do we need Samba for those Linux Machines?
Not necessarily. You probably talk about NFS (http://en.wikipedia.org/wiki/Network_File_System_(protocol) ) which is an originally Unix protocol that is still being used on Unix (and Linux) servers. (and there are a handful of several other methods as well)
If you're new to Unix, the best solution would be to stick to eBox and provide Linux users with Samba shares; if you wish to use NFS, you'll have to set it up manually; Linux clients can easily use Samba shares (although they will have to authenticate before accessing he share, but even that task is largely automated in popular Linux GUI-s like KDE or Gnome). For a newcomer, it really is the best approach to keep it as simple as possible.
To conclude: you don't need Samba for your Linux clients, but you do want it because eBox will provide you with a simple and straightforward administration for all your clients, regardless of their OS. Adding more services, if they aren't absolutely necessary, does not provide as much benefits as potential administration headaches. If your Linux users are Ok with Samba shares, stick to it.
Rado _______________________________________________ ebox-user mailing list [email protected] http://lists.ebox-platform.com/cgi-bin/mailman/listinfo/ebox-user
