Originally Posted by adad
The server should support the following structure:
- a common storage area, with RO access to files for users
- one area for each user, for their personal files (RW permission)
- an option for the users to allow access to their files (RO and eventually RW)
How would you setup NFS shares? I think LDAP is a bit too much (there'll be less than 10 simult. clients).
If you set up both SMB and NFS shares, what would you serve with each app? What will be used for win clients and what for linux?
It can be done with Samba and NFS. In my own home (wired) LAN configuration, I have a MythTV backend serving huge video files (2.2 GB/hour) to computers around the house. I've found that NFS is much more reliable than Samba when I playback these files on one of my frontends. I was Samba only until my teenage son started complaining about the hockey game he was watching, last October (a 3-hour long, 6.5 GB file). He could not fast forward or rewind past the first hour of the game and the video was lagging sometimes.
A switch to NFS solved the problem. I still have Samba enabled for the same directories on my server since all our machines dual-boot (XP Pro and FC)
On the server side, sharing a directory or partition is quite simple with ssytem-config-nfs:
I enable sharing for my local LAN (192.168.1.0/24), read-write and that's it!
On the client side, the setup is quite simple too: For instance, I've shared my /mythtv partition in /etc/fstab in all machines like this.
1- I created a /mythtv directory
2- I changed the ownership to me and the group to users
3- I changed the permissions for the directory to 775
[root@zeus /]# mkdir /mythtv
[root@zeus /]# chown claude:users /mythtv
[root@zeus /]# chmod 775 /mythtv
Then, I added an extra line in my client machines' /etc/fstab:
zeus:/mythtv /mythtv nfs nfsvers=3,rw 0 0
If you don't have experience with NFS/NIS, go to this site
. Check chapters 29 and 30. I like this guy's step by step approach.