Hi, I'm a relative newbie to this Linux thing, years of experience in windows and mainframe stuff ( 27 to be exact ! ) but only days doing Linux. I'm starting off simple by trying to replace Windows 2K (Active Directory) file/print servers with Linux and Samba and beleive I need Samba 3.0 to be able to connect to Active Directory.

I've installed SuSE 9.0with Samba 2.2.8a and successfully been able to setup file shares so encouraged by this success set about installing Samba 3.0 ......... argghhhhhh out of my depth !

I thought it would be simple as obtaining the binaries from the Samba ftp site ( even packaged for SuSE 9.0 ) and running rpm -ivh * ... seems not to be the case.

The install is failing with missing file dependancies LIBLBER.SO.199 LIBLDAP.SO.199 and LIBPOPT.SO.2

after several hours of searching I found the the files are delivered by OPENLDAP2-Client and POPT, I also find I already have these installed and files LIBLBER.SO.2 LIBLDAP.SO.2 and LIBPOPT.SO.0 already exist. So I;m guessing I need to install a later version of OPENLDAP2-Client ( can find the source files but no newer rpms ) and an older version of popt ? Is that right do I really need to backlevel POPT or am I misunderstanding the meaning of the .2 ?

I've also tried downloading the Samba source and following the "how to compile" instructions. This was a dismal failure ending up with a bunch of compiler errors, so at the moment I'm stuck and would value any advise on how to move forward.

Many Thanks
Steve

"The install is failing with missing file dependancies LIBLBER.SO.199 LIBLDAP.SO.199 and LIBPOPT.SO.2"

Actually this is so simple you might feel bad Open a terminal, su root, then cd over to /usr/lib and... one at a time..
ls liblber*
ls libldap*
ls libpopt*

And check what filenames it gives you. Odds are, it'll say you have something like...
libpopt.so.0.1 libpopt.so.1 and so one for each. And what you do is

ln -s libpopt.so.whatever_it_is libpopt.so.2

And repeat for each other file name If you don't find them in /usr/lib, open a kfind and have it search your computer for liblber* and so on

Thanks Caeda that did the trick. I might have my outright stupidity hanging way outside the ride by asking this but..... what do the numbers on the files signify, if its a particular version doesnt creating a symbolic link to a different version risk having incompatible s/w levels ? Doesnt the fact the rpm expects a particlar level mean that it requires that specific file to work properly ?

Thanks

Basically, the numbers... .so.1 .so.0 .so.0.1 .so.0.2 .so.0.0.1 are the most prevelant that I've seen. Mean no programmer can make up his god-d*mned mind and use a consistant naming scheme for all the files. :-D

But more likely I believe it has something to do with compilers used and settings enabled that just spit out a different file name. You'd think people writing programs or distributing rpms would set them up in a way to search for yourfile.so.ANYTHING and autoconfigure to the names on the system. But oh well.