||01-20-2013 12:39 AM
Slackware Samba/SWAT inadequacy/bug
I would like all general and Slackware questions to be answered first: my question below is not very important to me. I guess SWAT is part of Slackware, and though I do not want to bother Slackware developers about it, I wanted to point out and perhaps discuss this.
A couple years ago I asked here how to set up shared 'guest' folders with Samba and lately retried SWAT, despite that it forces password usage, which I hate. I also did on OpenBSD, which worked immediately. I used the exact same type of configuration (only the path was different,) which I redid and checked many times, on Slackware, and it never worked (despite that the path was '/home/u,' owned by 'u,' and had permissions 777... it was even a user-owned folder within one owned by root that I shared on OpenBSD) Many solutions are described on the 'net, and the simplest may be to add 'guest only = Yes' under in a smb.conf share configuration. That worked, so I marked the original thread solved. However, it seems SWAT (for Samba 3.6.6) on OpenBSD 5.2, etc., works to set up guest folders, and but SWAT (for Samba 3.6.8) on Slackware 14 (and likely earlier) does not. Is there any way to do this in Slackware with SWAT or if I ever do a clean installation?