On Thursday 26 March 2009 01:43:31 pm Alberto Passalacqua wrote:
Did you check if that patch fixes the issues? I still have to try, since I'm currently (\o/) not relying on samba shares :)
That's exactly our problem. We can't see Samba problems. I fire up Windows box once in a few months, but some people would like to have Linux box fit in Windows (tm) world without problems. Like gentleman in article. Sharing files: That means at least one directory is shared. You can drop content without knowing any options, touching any button, adding any users, enabling any ports, and pick that from another computer. I'm sure that will expose all Samba vulnerabilities to LAN, but seriously, since when is Home LAN considered war zone? Printer cooperation: I'm kind of advanced Linux user, and following few articles I found on the net, I still can't print from Windows box direct to cupsd. I don't need it. I tried it only to see why people complain. Wireless: My happy lappy has wireless, thanks to ndiswrapper. Last time I was in the mood to try native Linux stuff (year or so ago) it would configure, it would work better then ndiswrapper, but on next boot there will be no driver. Reconfiguring wireless on each reboot is somewhat unusual procedure. It might be fixed in the meantime, but I don't have to live with "native" driver perks waiting until it grows up. That are few small things that hang as a problem for years. So far I recall, my Samba problem was solved using simple config from Samba by Example, and it worked as described above in Sharing files. Printer was available to anyone on LAN, using a bit expanded samba.config. There are security concerns with such configuration if applied to business environment, but there is no effective default configuration for every occassion. Home LAN is not the same as small business, or corporate one. Sharing configurations is as important as sharing source code, or binaries. It is part where advanced users can help without knowing how to write a single line of code. I think, that if we want to have more users (more of the kind) we should find the easy way to share this. Is it rpm that has only few config files and script that will ask few questions to determine what to do, or just link on the wiki to the server where those files are stored, it is matter of automatization, but it has to be created. I guess Samba would be ideal candidate to begin with. And, no I don't look at Novell guys to do this. They can give advice if there is questions, as they usually do, but this community can do such things. We don't need big guys to catch this fruit. -- Regards, Rajko -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org