LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   slackware current (http://www.linuxquestions.org/questions/slackware-14/slackware-current-287834/)

mustafa 02-08-2005 04:24 PM

slackware current
 
I have just installed slack 10.0 and then I saw on slackware.org that 10.1 is out. I just wonder what is the difference between slack 10.1 and my slack 10.0 with updates using swaret to current?
Is there any difference at all or shall I reinstall?


regards

cereal83 02-08-2005 04:32 PM

Well 10.1 has updated programs and probably bug fixed. it used kernel 2.4.29 while 10 used 2.4.26.

Maybe if you look at the changelog it will tell you a bit more. You can even checkout http://distrowatch.com/table.php?distribution=slackware and scroll down and it will say what versions of program are running on 10 and 10.1

I wouldn't upgrade if it's a main computer but if it's the 2nd os and you don't care if you loose the info you have then I would reinstall

All up to you

mustafa 02-08-2005 04:37 PM

slackware current
 
Well I do mind a bit about losing all my configurations.
I use kernel 2.6.10 and the system is fully upgraded so the difference might not be to big.


regards

cereal83 02-08-2005 04:41 PM

Then I would just upgrade the packages you use alot to current and just leave it on 10.0!

mustafa 02-08-2005 04:46 PM

slackware current
 
OK. Maybe I will.

Thanks for your help and your fast replies.

regards

eelriver 02-08-2005 07:32 PM

Quote:

Originally posted by cereal83
Then I would just upgrade the packages you use alot to current and just leave it on 10.0!
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.

Read the changelog to see if you think it's worth it, then read UPGRADE.TXT to find out how. It doesn't mean loosing all your data. It's actually very simple.

cereal83 02-08-2005 08:19 PM

^^

Never thought of that. Good point!

slakmagik 02-08-2005 09:50 PM

Quote:

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 2.15.90.0.3 > binutils 2-15.92.0.2
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.


All times are GMT -5. The time now is 03:44 AM.