I installed Slackware 12.2 a few days ago.I wanted to run samba now to get to my winXP desktop and first checked if samba was installed-it is.
But in Kpackage it is grayed out in user mode,I can only access it in admin mode but whatever I do there doesn't work.

In a terminal I keep getting those messages about GLIBC 2.8. Now I know 12.2 has glibc 2.7 so the installed librairies should depend on that but it keeps asking for glibc 2.8 which he should know isn't there.
A few examples:

I have to do sudo -i to get into root

Why would all those librairies require glibc 2.8? I don't understand.
Is this a (bad)installation problem? I am kind of wary to download a glibc from the web and install that. I am afraid it might cause even bigger problems.

Your pcap library (libpcap) does not appear to be from the official Slackware ditribution. Slackware also does not include pam support, yet you have the libpam libraries. Slackware also does not install software into /usr/local unless you have built it yourself or used someone else's packages. This is being caused by another package you have installed. Since it is linked to a version of glibc that Slackware doesn't use I'd guess it was compiled on or for another distro.

I have Slackware 12.2 and no problem starting Samba. I you sure you installed the Samba package for Slackware 12.2. Try to remove the package and (re)install samba-3.2.5-i486-1.tgz (it is in the /n directory).

I installed 12.2 in a partition that had 12.0 but I formatted it before and anyway 12.0 has no glibc 2.8.I burned an official Slackware distro and the sum checked.The samba installed is 3.2.5-i486,the one that's on the distro.

Then I would suggest that you look to see what is in /usr/local/lib. It should be empty and anything there is not from the Slackware install. You should be able to move the contents to another location and then do ldconfig to rescan the library bindings for the linker. If Samba still won't start do a removepkg and make sure there is nothing in /usr/local/bin. Then reinstall Samba.

If you have installed something that you don't remember, this could kill your system. I don't think that is very likely though since those libraries can't be loaded anyway.

Just to be clear, the GLIBC 2.8 dependency is not in Samba, it is in libraries that Samba is loading. If you have the same named libraries both in /usr/lib and in /usr/local/lib the /usr/local/lib version is loaded. I think you have libraries that were compiled for Fedora or Ubuntu in /usr/local/lib.

In /usr/lib I have libpopt.so.0

I have no libcap there

In /usr/local/lib I have libpopt.so.2
libcap.so.2

So /usr/lib and /usr/local/lib are different for at least those two libraries. I cannot remove the libraries in usr/local/lib because I need...glibc 2.8.
You are right in saying that usr/local/lib is loaded and at least some of those libraries are not slack's. I think I am in for a clean reinstall.

If this is a new install and you don't have much customization done yet, then yes, I'd reinstall, but I'd also want to know where the other software came from. Do you have other distros installed on another hard drive or partition on the same computer? Maybe during setup you were not watching carefully and it found some other partitions and made fstab entries for them. Look at your /etc/fstab if you can or a df and see what partitions are mounted. I'd hate to think you are seeing /usr/local mounted from another hard drive partition that you did not want to destroy!

Well...my system is:

Dell Dimension 520 P4 3GHZ,RAM 2GB,HD 2*250GB,Nvidia graphics.
HD0:WinXP
HD1:Kubuntu,LinuxMint,Mandriva,Ubuntu,Debian,Fedora,Sabayon,Suse,Slax and Slackware.
Kubuntu's grub bootloader is in the MBR booting every system including Slack. Works very well.Slackware's bootloader is in its own root partition (condition to chainload them)I never had any problems with it and I am very careful when I do a new distro,choosing the right partition,formatting it so nothing remains of the previous distro installed there.It always worked perfectly.The last one I did was sl12.0 before SL12.2. So I think I am safe doing a clean reinstall.The only thing I have do to is to disconnect the external USB drive before installing a new OS.Apparently when the ext USB disk is connected there must be some interference.
I checked now and every OS is booting properly even slackware.
fdisk gives every disk and partition right.

fstab gives an interesting item. Besides it's own partition,a swap,the winwxp in /fat-c,floppy,it gives sdb2 in /usr/local. Now sdb2 is Linuxmint and going into /usr/local/tmp I see a folder mintUpdate with just a logfile in it. This could be it I think. Now I am not afraid of a reinstall because in Mint I have next to nothing,so no big deal.

df gives the sameartition sdb2(Mint) is mounted in /usr/local. Probably this is the culprit,I am pretty sure Mint uses GLIBC 2.8 (will have to check)

So linuxMint uses glibc2.8. Now I don't remember mounting sdb2(mint) when I installed Slack.I usually don't mount anything but anyway I did a clean reinstall of slack12.2 and everything seems to work now. I checked /usr/local/lib,it's empty.
I can use samba;I can see my win shares on my laptop,it correctly got my workgroup(mshome) but there is still something I don't get.
When I go into settings-samba it says smb.conf could not be found and that's right. I only have a sample conf. file there.But it is working.I don't understand.

Also, when I go in Kpackage there are only installed packages there,nothing I can add as a new package.

I still got some work to do there.
I managed to get the printer working,looking for the scanner also.
At least I got a working distro so far!

Start to like slackware!
I got the scanner working(CanonMP520) I just took the Canon provided Linux drivers for this machine,converted the .rpm's into .tgz,installed with installpkg and up it went. Couldn't believe my eyes!
Still,somebody can explain the following:
For samba I only have a sample conf file. Samba works perfectly; I can see my Win laptop and my daughter's laptop. How does it work? It shouldn't!

My guess is that from the Win or daughter laptops, you can not see any files or printers/scanners on the multi os dell box. Samba.conf allows that box to serve the rest of your lan. There is a client samba program ( that does not need samba.conf) in the package that lets you see what is being served by other boxes on your lan.
ppd

edit: Actually thinking about it the client package might be part of KDE, lisa? can't remember.