I thought I would try out how a Swaret upgrade would proceed on a stock 10.0 to Current. Unfortunately it seems to have messed up the glibc thing.

Is there any way to recover this? I get the login prompt, but it's broken and I cannot get a shell since glibc seems to point to the wrong version.

Is there a way to solve this? I have access to the Slackware partition from within Debian...

Note: I am aware that Swaret is not the ideal package tool, but still I didn't expect that it would break the system this much and thought I could do all the reconfiguring manually after a reboot.

Two ideas:
1) Boot Slackware 10, chroot into your Slackware partition, removepkg new glibc and installpkg old glibc. If you cannot do this due to errors, you can run setup and select only glibc from base system (a) to install. If it still doesn't work, install all the base system.
2) Get the new package of glibc into debian partition, explode/extract it, look at doinst.sh script and remove created entries manually. Then boot and install old package of glibc.

You mean boot with the Slackware 10.0 Cd? I'll give that a try although I've never really used chroot before (except when installing gentoo from debian).

Yes, sorry for confusing.

If you did a "swaret --upgrade" and selected all packages, your problem is easy to solve. Just boot with the slackware cd and login as root.
mount your slack-partition for example to /slack.
change to /slack/var/swaret.
update all packages by typing: ROOT=/slack upgradepkg --reinstall *.tgz
this solved it for me, good luck.

Thanks for the suggestion. Actually, chroot didn't work also. I'll try your suggestion.

Again, thanks a lot. I'll try this.

I managed to now boot into Slackware after running the upgradepkg --reinstall *.tgz with all the packages.

Apart from a few dependencies (which I resolved using swaret) there is nothing wrong. Except that ALSA is not working.

Anyway, since I'm going for a 2.6 kernel, I guess it'll be resolved once I do the kernel upgrade.