I managed to make a new reinstall directly from the current-tree, I saw a lots of errors during startup: modules dependencies problem somewhat with not able to find xxx.o in "/lib/modules/2.4.23" while the installed kernel is 2.4.24, there is also no dir "/lib/modules/2.4.23" but only "/lib/modules/2.4.24".

Program that complained are like iptables, many others forgot ..

Look liek I've to reinstall 9.1 n wait till all the programs are recompiled to load modules from /lib/modules/2.4.24. But it worked last time when I installed directly from the current source tree, b4 2.4.24 released ..

did you use swaret? swaret doesn't upgrade kernels... you could also just compile 2.6.1 and use that

Before I install I've used rsync to make my current-tree as actual as the current-tree in official slackware site. After install, I configured swaret to updat/upgrade from my current-tree. It said the system is actual, no fetching at all. The installed kernel is 2.4.24 (vmlinuz is /boot/vmlinuz-ide-2.4.24), that wonder me why it looked at modules from /lib/modules/2.4.23 ? I booted with the bare.i,install.1,2 from the current/{bootdisks,rootdisks}, they still dated on 30-nov,01-dec ..

That must be some script (maybe rc.modules don't know) not actulized, while the old 2.4.23 on the current tree being replaced by rsync, so some synchron problem ..

I've got even no access to internet, the system is easily not started correctly, ifconfig displayed only loopback interface, none of both nics are recognized, restarting rc.inet1 won't did it.

I did finally a install from the slackware-9.1-install-d1.iso, update/upgrade it using swaret, n it is fine now. Only I experienced /etc/apache/{httpd,mod_ssl}.conf need some actualizing regarding the libexec/mod_xxx.so to be libexec/apache/mod_xxx.so ..

N all other thing is fine enough