elefino wrote:
On Monday 03 January 2005 11:32, Martin Deppe wrote:
Sorry, but ...
Jonathan Brooks wrote:
Am I right in thinking that the only time you'd really want to use SAMBA is if you have to support windows boxes? Can CUPS share printers round the network without SAMBA?
... OF COURSE IT CAN (sorry again, what a question ...)
Well, I need to write some more here:
I mean, what do we need Samba for if and only if for the fact that M$ doesn't comply to the broad standards others are using? I simply guess that M$ doesn't do it because they probably think that they wouldn't sell anything anymore and therefore wouldn't make any money anymore! How about this?
Samba exists only because of the fact that M$ doesn't support all the other stuff (well enough at least or demands loooots of money for it) and - of cause - because some people still want to use Windows (even though they know better).
Ok, you did not have a smiley on that last statement, therefore implying that I seriously should know better. Therefore, you will please inform me of the name and URL of the tax software that is written for Linux. I will gladly pay money for it, and persuade my wife that she can finally leave Windows behind... oh, well, she also has ACT! from her employment. You have a Linux version of that with perfect turnaround? URL please.
Thanks. You should make this knowledge more widespread, to help tens of thousands who remain tied to Windows for only a few (what they think) Win-only apps.
Kevin (who doesn't care what Windows supports -- only cares what supports Windows-but-not-yet-Linux)
Ok, so lets go for a running system of your choice/needs. As of what I got from your other mails (what I already requested: depends on what your environment and intentions are) I had a similiar setup of what you have today a couple of years ago, when we were at Samba V1.x. That was running great Actually I had a gateway with firewall, file and printservices for my Linux box (Dual boot with Windows 98) and Samba with Home and Print services for my own Box and a Windows-only Box of another user. I have to admit that it took me a little while at that time to get it up and running in this configuration but I was quite new to Linux at that time (allthough Unix has been my favorite OS since 1985 almost). But after having it set up, the second user could permanently work under Windows (with home and print services on gateway running samba) and I could - depending what I needed/wanted start Linux (using nfs and lprg at that time) or Windows (using samba) with no problem at all. Today - as of my experience - it got much easier to install and config samba by using YaST since SuSE improved it a lot since then and - of course - samba improved quite a lot, but I don't use samba anymore, at least for the moment. So, if you set up a samba server with yast, setup all shares you need/want and then simply connect from your clients to the shares and there you are. If this doesn't help you to have the confidence that it will work, for sure is possible and you simply have to figure out how I might get going to set up my system using samba again (which actually I wanted to do anyways) if you like me to help you this way (and maybe run into the same problems you experience) let me know. I'd like to be of help then. If not we might simply end this thread and forget everything I said/wrote regarding this issue. :-) Cheers Martin