[Samba] stuck on Samba 3.5.x

Eugene M. Zheganin emz at norman-vivat.ru
Wed Nov 27 00:24:23 MST 2013


I using samba for like dozen of years, and now I'm kinda stuck on a
previous version. I was trying to move to newer versions, but different
issues prevent me from doing this. For example,
https://bugzilla.samba.org/show_bug.cgi?id=10093 prevents me from using
3.6.x, as I'm unable to join the AD domain;
https://bugzilla.samba.org/show_bug.cgi?id=10079 prevents me from using
4.0 as this bug is making it impossible to interoperate with squid
(however, it joins the domain just fine); and finally
https://bugzilla.samba.org/show_bug.cgi?id=10287 prevents me from using
4.1, as the net utility is crashing on the join operation.
Unfortunately, all of these bugs didn't get almost any attention, could
please someone take a brief look at them and probably tell me how to
improve them in order to make them more developer-friendly ?

I'm writing here because I'm kinda out out options. I'm using Samba
under FreeBSD, and 3.5.x is already off it's ports system, so I have to
build it from sources each time. I have talked with FreeBSD Samba port's
commiter, he doesn't have a clue either about when to do. The thing is
that any of these versions mentioned here is able to work in simple
standalone setups, but I need to integrate it into the Windows Domain.
It's hard to guess, but since I'm one of the few guys using Samba
interoperability with AD under FreeBSD, and since the commiter is out of
ideas, I'm feeling like I'm speaking for the entire FreeBSD community.


More information about the samba mailing list