On Tuesday 04 January 2005 04:15, elefino wrote:
On Monday 03 January 2005 17:47, James Knott wrote:
I've only heard from half a dozen people on this thread, and among them they disagree about whether NFS takes the computer to lunch when another NFS server goes away. Surely out of the hundreds or thousands of members of this list, there must be more than a few who have two Linux boxes sharing files/directories across a simple home network. What are all the rest of you doing?
Kevin (still unshared)
Hope this helps : A. NFS ''''''''''''' My internal network is 192.168.168.0/24. I don't like using 192.168.0.0/24 as I feel this is potentially ambiguous with that 'extra' zero.. I have a central linux server (SuSe9.1) that acts as a gateway to the internet and also as a local DNS/DHCP serverand as a central LTSP. It exports some directories - the /etc/exports file is : ===================================== /SuSE/ *(ro,root_squash,sync) /var/lib/YaST2/you/mnt/ *(rw,root_squash,sync) /work/pictures *(ro,root_squash,sync) /knoppix/ *(rw,root_squash,sync) /work/wanderer/ *(rw,root_squash,sync) /home/wanderer/Documents/ packard(rw,root_squash,sync) ## LTSP-begin ## # # The lines between 'LTSP-begin' and 'LTSP-end' were added # on: Thu Oct 14 14:31:55 2004, by the ltspcfg configuration tool. # For more information, visit the LTSP homepage # at http://www.LTSP.org # /opt/ltsp 192.168.168.0/255.255.255.0(ro,no_root_squash,sync) /var/opt/ltsp/swapfiles 192.168.168.0/255.255.255.0(rw,no_root_squash,async) ## LTSP-end ## I set these up using YAST->Network Services->NFS server. The firewall is setup in quick mode with the internal interface as 'trusted' i.e. open and the external ethernet interface 'untrusted' i.e closed. ====================================== /SuSE contains the installation DVD's for SuSe 9.1 and 9.2 /var/lib/YAST2/you/mnt is the SuSe patch directory The other directories are for general use. On my laptop (called wanderer when running WinXP and packard when running SuSe9.2) I have the following in /etc/fstab ========================================= linux.hewlettfamily:/home/wanderer/Documents /home/wanderer/linux nfs defaults 0 0 ========================================= I set this up using the YAST->Network Services->NFS client. Note that the 'Browse' option in the dialog did not work but if I typed in the server name 'linux.hewlettfamily' manually everything else worked. B. Samba ''''''''''''''''''' I have the following stanza in /etc/samba/smb.conf: [work area] comment = Work area for everybody path = /work read only = No create mask = 0777 (My workgroup is 'MSHOME'.) and my windows machines (WinXP for wife, Win98SE for son and Win98SE for daughter) can all see this share as well as the 2 printers connected and the home directories of each login. My laptop running SuSe9.2 sees this share as well. I set this up by using YAST->Network Services->Samba client. The browse tab in this dialog also does not work - it defaults to 'TUX-NET' and using the browse tab gives me a workgroup 'LINUX' which does not exist. Manually typing in 'MSHOME' is successful. When I click on the 'Network Browsing' desktop icon I get a konqueror window with 2 icons 'SLP services' and 'Windows Network'. Clicking the latter gives me 'Mshome' icon and clicking on that gives all machines on my network, WinXP, Win98SE and Linux. This corresponds to the URL smb://mshome/. Each of these PC's has their own login on the central linux server and logs in as such. I have created the necessary entries in Samba using 'smbpasswd'. I also had to edit a file /etc/samba/smbusers to map windows login names to unix login names. My wife's WinXP machine was originally mine and the original login on this machine is 'Dad'. I changed to my wife's name 'Wife' but internally WinXP still thinks of it as 'Dad' so I had to add a line to 'smbusers' wife = dad wife (NB these are not the actual login names. I use Dad,Wife to illustrate the point). So it *does* work. Problems ''''''''''''''''''' I tried setting the workgroup to a different name 'hewlettfamily' or 'TUXNET' or 'LINUX' but none of these worked for a reason I still haven't figured out. I am currently stuck with 'MSHOME'. I am unable to print to my HP printer that is connected to the WinXP machine. Everything is setup but if I try printing I get a permanent spool job on the WinXP machine which cannot be removed. All subsequent printing to this device is blocked by this one spool job. The only solution is to wait for the job to eventually terminate which can take 2hours or more - even rebooting the winXP machine does not help. Installing 'Printer Services for Unix' on WinXP may solve this problem. Having multiple logins , one for each family member is a headache. Regards Paul Hewlett -- Paul Hewlett (Linux #359543) Email:\`echo az.oc.evitcaten@ttelweh | rev\`" Tel: +27 21 852 8812 Cel : +27 72 719 2725 FAX: +27 866720563" --