Þann Mánudagur 03 janúar 2005 20:14 skrifaði elefino:
Are you saying that upstairs, I can use YaST to configure Server and Client, and downstairs I can just start Client and that automatically starts a server on that machine, too? In that case, SuSE should always start those modules together, or else the naive user assumes that they are separate functions and that the other does not need to be configured when the one is configured.
Well, they reside in /etc/samba/smb.conf ... which is the central samba configuration file. But the client is a simple program, called 'smbclient' along with libraries, while the other is a server daemon 'smbd', so in fact they are separate. The client is also comprised of a browser deamon called lisa. Since you are saying that you'd like to write to both machines, you'd want to setup both as servers (and clients). With the same workgroup name, all round the block. One thing to note, is that you'd want your "upstairs" machine to run 'nmbd' or the "Netbios Nameservices Daemon". And you'd want the machine downstairs to use the upstairs machine as a "wins" server (both in linux and windows). It will simplify browsing, between windows and linux. In the case, when the downstairs machine is in Linux, you'd want the parts of the machine that are supposed to be viewable both "upstairs" and "downstairs" to actually reside on your "upstairs" machine. Let's say, in "/usr/local/upstairs" just for an example. Than you'd do something like this in your /etc/exports on your upstairs machine (assuming your upstairs network IP is 192.168.x.y/24: /usr/local/upstairs 192.168.x.0/24(rw,root_squash,sync) Then you'd go into YaST, in System->run levels, expert mode. Find "nfsserver", and make it run in "3 5", and then start (or restart) the service. Then try to mount it, directly and see if all is ok. #> mount 192.168.x.y:/usr/local/upstairs /mnt #> umount /mnt Now, in your upstairs /etc/samba/smb.conf file ... you'd add this for our little example. [upstairs] comment = Upstairs files path = /usr/local/upstairs guest ok = yes And then you do: #> rcsmb reload And then you'd go into YaST on both the upstairs and downstairs machines, and make sure "lisad" was up and running in both "3 5" on both machines. As well as ensuring that "nmbd" was running on the upstairs machine in "3 5". Make sure that win98 on the downstairs machine, uses the upstairs machine as it's "wins" server. Now on your "downstairs" Linux box, you'd do something like this in it's /etc/fstab file: 192.168.x.y:/usr/local/upstairs /usr/local/upstairs nfs rsize=8192,wsize=8192,rw,bg,timeo=14,intr Then, after you've edited the fstab file, you do the following ... but only the first time around, all subsequent mounts will be automatic. #downstairs> mount /usr/local/upstairs So, whenever the downstairs machine is started it will automatically mount the nfs (but not hang on it "bg" option) share from upstairs and all "data" is automatically modifiable in both places. Both linux boxes can now browse to "smb://<UPSTAIRS_MACHINE>/upstairs" as well as the win98 box. The linux box will have its /usr/local/upstairs identical to that place on the upstairs filesystem. The difference here is, that whenever you browse to your samba share, you'll need to authendicate to the upstairs machine. While all you need for the NFS share, is to have your "/etc/passwd" identical on both linux boxes, the rest is automatic ... the rights give on the upstairs machine, will be inherited by the downstairs machine, of the same user (actually user id is what counts, not the name). No need to authendicate, as you're already authendicated on the local machine. My 2¢ worth, Örn