SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I've applied the latest updates to Slackware 11.0 which includes a security update from Samba 3.0.24 to 3.0.25. After this update I am suddenly unable to access Samba shares that are located on my reiserfs partition, however, the one I have my music on is FAT32 and is accessible fine from my Windows boxes. Before I go to much farther here is my smb.conf:
Code:
[global]
workgroup = MYDOMAIN
security = SHARE
printing = cups
printcap name = cups
short preserve case = yes
preserve case = yes
[printers]
comment = All Printers
path = /var/spool/samba
guest ok = Yes
printable = Yes
use client driver = Yes
browseable = No
[music]
comment = Music Collection
path = /mnt/music
read only = No
guest ok = Yes
[data]
comment = Data Drive
path = /export/samba/data
read only = No
volume = Sample-Data-Drive
guest ok = Yes
[winxp]
comment = Windows XP
path = /mnt/winxp
read only = Yes
guest ok = Yes
[homes]
read only = No
browseable = No
So, the share I am having issues with is the data share. All the other shares work fine as far as I can tell from my Windows systems. homes and data are on reiserfs and music is on FAT32. Winxp is NTFS. It's possible that permissions are causing the issue with the data share but it doesn't make any sense as I've been using the permissions with Samba 3.0.24 perfectly fine for a long while. The only change that I've made is to upgrade to the 3.0.25 package in the 11.0 tree (dated May 14th in the changelog I think). As soon as I rolled back to 3.0.24 things started working normally again.
So, the question after all of this is, does anyone know what changed in 3.0.25 from 3.0.24 that may have caused this?
I'm not aware of what changed to break this, but you are not the first report I've seen that the 3.0.24 --> 3.0.25 upgrade broke samba. Either way, it seems to be something that will require an update from the samba guys. If you're using it on a trusted LAN, then just roll back to 3.0.24 - that's the simplest solution for now.
Yeah, I rolled back and it's working fine again. Still, I'm very interested in knowing what the difference is between the two. My issue is basically solved (thanks). Even so, if anyone knows what the difference is between 3.0.24 and 3.0.25 that causes this I'd be interested in knowing.
I had a similar problem, my share (on Slack to WinXP) was down.
What got me was that the NAT was also not working.
In the end it turned out to be a lack of executable flag on /etc/rc.d/rc.inet2 . How that happened I don't know, it possibly wasn't the samba update as I tend to do a few updates together and then boot up again the next day.
So, rc.inet2 brings up DNS and ip_forward-ing. So despite spending hours (literally!) trying to get samba up it turned out to just be a little "x" flag. Gah!
I'll just have to wait until Pat released another 3.0.25 package and see what happens. I think I'll shoot him a quick E-mail just letting him know what happened.
I've had a similar problem with my NAT. I found out you can just manually mount the shares, where as before it did it automatically. I'm using smb4k, by the way.
Last edited by Changeling; 05-23-2007 at 02:10 PM.
I personally am not having any issues with it - even 3.0.25 never gave me any trouble. However, I'm aware of at least two *reliable* reports that some shares do not show up with 3.0.25a. The solution/workaround at this time is to specify the share via its ip address as opposed to name.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.