>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<
On 12/4/00, 1:11:50 PM, "Alan Davies"
On Mon 04 Dec, Gary Stainburn wrote:
All this info is available if you do a 'man smbmount' and 'man swat'
Well...yes...and no. The manual is short on 'examples' and assumes you know the terminology as applicable in that particular area. And while it says what you can do - it doesn't say what you can't.
I hadn't realised that swat could not be run from the command line. (why?)
'man swat' gives: swat allows a Samba administrator to configure the complex smb.conf file via a Web browser. In addition, a swat configuration page has help links to all the config urable options in the smb.conf file allowing an administrator to easily look up the effects of any change. It also tells you that the swat 901/tcp should go in /etc/services etc...
However, it now works. Many thanks.
smbmount //server/share /mnt/mountpoint
This did not work at first until I had created a folder called mountpoint (or fred or whatever). In fact - I wasn't sure what mountpoint meant - and
Sorry. I wrongly assumed that you'd used the normal unix 'mount' command before and understood mountpoints. thought it was
referring to the remote system.
Why do you need to create a folder? (...thinks, would it be better if the mount point was created automatically - possibly using the 'share' name in the mnt folder?)
One of the fundamental aims of the unix philosophy is that it hides the hardware from the user - everything appears as files in a single directory tree. That means that 'everything' appears somewhere as a file, raw devices under /dev, such as /dev/hda being the 1st IDE drive, /dev/hda1 being the 1st partition on the 1st drive, /dev/ttyS0 is the 1st serial port. In keeping with this idiom, everything starts from a root (/) partition. Other partitions are connected (mounted) at specific points on this root partition. The boot partition (/dev/hda5 on my system) is mounted on /boot, thus once mounted, you access that partition by 'cd'ing into /boot. Mount -t smb and smbmount work similarly, but allow you to do the same with a remote Win9x share. It mounts the remote service as part of the local system's directory tree structure. For example, I have a directory on my local system called /mnt/smb. If I mount a remote SMB service, I put it there so I always know what I've done with it (although running mount without arguments would tell me that anyway). Hope this makes things a little clearer for you.
I've since looked on samba.org site....which said that due to new shortcomings with Qt library smbsh would not work any more. Should have read that first!
>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<
On 12/4/00, 10:46:17 AM, "Alan Davies"
wrote regarding [suse-linux-uk-schools] SAMBA setup:
Trying to get LINUX to 'mount' a PC share.
smbd appears to be running as I can use smbclient fine.
Smbd/nmbd are there to provide services to other computers connecting to yours, not for you to mount other computer's shares.
Reilly book says smbmount is deprecated - and not supported so I try smbsh - which in SUSE6.4 does not appear to be recognised.
I knew nothing of this, and still use smbmount. However, I have just looked at the man mage, and it says that you should now use the normal mount command passing an argument of -t smb to tell mount it's a SMB filesystem.
Does that mean that smbwrappers is not part of the kernel.
So I try typing smbmount - t smbfs //myserver/share (Reilly) and it quotes the smbmount syntax implying I got it wrong. What does a 'service' mean in this context?
Try 'smbmount //myserver/share /mnt/mountpoint' In this context 'service' = 'share'
What should I use? - or perhaps smbfs is not part of kernel?
If smbfs is not in the kernel you would (probably) get a different error message.
Cant do it the other way either. Using simple smb.conf from Reilly and putting Linux host in host file in the PC, it (the PC) will still not connect to the share.
Tried accessing swat - doesn't appear to the running. Tried to get it to run with swat 901/tcp & (as per Reilly) and it appears in ps list - but still can't connect.
Do you mean that you entered 'swat 901/tcp' at the command line?
You should have put that in the file /etc/services. Then you should put the following line /etc/inetd.conf
swat stream tcp nowait.400 root /usr/local/samba/bin/swat swat
The do a 'killall -HUP inetd' to put the changes live.
Once you have done this, do 'netscape http://myserver:901 &'
-- Alan Davies Head of Computing Birkenhead School
-- Alan Davies Head of Computing Birkenhead School