Originally posted by eelriver
Bad idea. If you try this you will be mixing packages compiled with differrent glibc, x packages compiled against a different Xorg, etc. It's better to go one or the other, mixing is asking for trouble.
Actually, it's no big deal. Glibc and binutils and the kernel's not even a minor difference, gcc's the same.
binutils 220.127.116.11.3 > binutils 2-18.104.22.168
gcc 3.3.4 = gcc 3.3.4
glibc 2.3.2 > glibc 2.3.4
linux 2.4.26 > linux 2.4.29
(or linux 2.6.7 > linux 2.6.10)
A *lot* of Slackware 10.1 is composed of the same packages as 10.0. I mean, in other words, 10.1 is already 'mixed' even if you install it clean. And I upgraded a 10 I had laying around with no problems - no lost configs.
So the flipside of that is that if you're expecting a Giant Leap when you upgrade, you'll probably be disappointed. 11 is where the fun happens and stuff's going to break.
Linux 2.6 default, almost definitely, new glibc and gcc, Gnome out completely, etc, etc.
But slackware-current=10.1 if you've been upgrading everything. I mean, current isn't this magic thing. You're either running bare 10 (which you shouldn't be), an updated 10 taking only things from 10's /patches, or 10.1/current which, at the moment, are identical. They'll only be different when /patches is opened up on 10.1 and non-bugfix upgrades go into -current. The idea of 'upgrading' from -current to 10.1 is impossible.