Hi Pete,
Post by Pete BrownWell, I tried samba-1-0-2 and near the end of install discovered I
needed something called "apache" in order to run something called SWAT.
Lack of docs in the package did not help.
Erh, the package list at the begin clearly says that SWAT is the Samba
Web Administration Tool.
And the explanation on the SWAT configuration programs says, that it
needs a CGI-capable web server and that it was only tested with Apache
2.x. Therefore Apache must be a...?
Well, neither SWAT nor Apache is really needed to run Samba successfully
and effectively, in future revisions of the WPI the SWAT package will be
deselected by default. Even the Samba people say "that SWAT is ugly and
nobody uses it" - we just include it, because we can (and we find it
useful sometimes), but as I said it is absolutely not essential.
Post by Pete BrownI did locate and install apache - which I have no idea of the purpose
in life of this software
If you had read the (rather minimalistic) docs, you 'd have known.
Post by Pete BrownSWAT may have run successfully - I have no idea.
Forget SWAT, you probably will never need it anyway. Local Server
Administraion can be performed completely using SSCC.EXE and
SMUSERS.EXE. SWAT is only useful if you plan to configure Samba from a
remote machine.
Post by Pete BrownI thought I'd click the "Help" button to get an idea on configuration
but that does not work as there is no Help file included it seems.
Yes, the help file for SSCC has not been done yet, as it is not really
clear what should be in it, as the program is pretty self explanatory
and adding the whole smb.conf manpage would not be really useful and be
awfully lot of work.
More information can be found here: http://svn.netlabs.org/samba/wiki/FAQ
Post by Pete BrownCouple the above with the general failure of EVFSgui to access files
and directories on the network and I would, possibly incorrectly,
state that samba has a long way to go before it can replace File and
Print Client.
Samba Server and Client for eCS are run successfully in several company
networks already. By and large it works quite well, is reasonably stable
and outperforms LAN Server, WSEB and IBM Peer on the same hardware.
Post by Pete BrownI'll look into samba again in a few months and see how it has progressed.
We usually do what we can to fix any reported (and reproducible) problem
as fast as we can.
Please, be aware that Samba development is driven by 2 to 3 people by
and large in spare time. We simply do not have the manpower to test
every possibe configuration and setup (let alone write extensive help
files, that the majority of users never reads) and heavily rely on user
feedback. If everybody (except us developers) just waits, there wont be
much progress, as we only make sure that it works for us and in our
environments.
Your report about your EVFSGUI observations lead to 2 fixed bugs. Expect
a new build these days, which should not exhibit any of the effects you
described with beta4.
Thanks for your feedback, it is appreciated!
Kind regards,
Herwig