What will Slack 13 give me that Slack 11 doesn't have?
in [Slackware]
|
From: Rich Grise on 6 Oct 2009 17:05 I'm not an upgrade-for-upgrade's-sake kind of guy - more like, if-it ain't-broke,-don't-fix-it. So, what would Slack 13 give me that Slack 11. doesn't have, besides the headaches of IPV6 and that whole new kernel? Thanks, Rich
From: notbob on 6 Oct 2009 17:38 On 2009-10-06, Rich Grise <richgrise(a)example.net> wrote: > So, what would Slack 13 give me that Slack 11. doesn't have, besides the > headaches of IPV6 and that whole new kernel? mplayer! It's all there. Add the browser plug-in and you can watch almost anything. I was shocked to see wmv files play as easily as mpg and avi files with nary a finger lifted to cli a config file. I can even stream current movies where available. No muss, no fuss, it works, I watch. IMO, it is major. On the downside, there's kde4.2, which is worse than herniated pond scum. nb
From: Sylvain Robitaille on 6 Oct 2009 17:42 Rich Grise wrote: > ... what would Slack 13 give me that Slack 11. doesn't have, besides > the headaches of IPV6 and that whole new kernel? What did Slackware-11.x give you that Slackware-9.x didn't? Seriously (though I must admit to not yet having installed Slackware-13.0 on any system), I think it comes down to new versions of various software, with the good and bad that that entails (new features, new bugs, new interfaces, etc.) There has been much discussion on the newsgroup of KDE-4.x, which is included (though it remains possible to install KDE-3.x instead, I understand). Perhaps you're among those for whom that alone would be a reason to upgrade. Note that I basically agree with you. I have some systems at home that are running Slackware-10.2, and those won't likely be upgraded until the earlier of a) their hardware is upgraded, or b) Slackware-10.2 is no longer able to run the software those systems run (which is unlikely, leaving "a" as the only realistic possibility). Then again, I also have one system on which I do intend to install Slackware-13.0, in order to see for myself the answer to your question above, and at least two that I will be eager to install it on, in 64-bit mode, for regular use. Trouble is, those systems are presently working just fine (one as Slackware-10.2, the other as Slamd64-12.0), so the upgrade on them certainly isn't urgent. -- ---------------------------------------------------------------------- Sylvain Robitaille syl(a)encs.concordia.ca Systems analyst / AITS Concordia University Faculty of Engineering and Computer Science Montreal, Quebec, Canada ----------------------------------------------------------------------
From: Grant on 6 Oct 2009 18:09 On Tue, 06 Oct 2009 14:05:58 -0700, Rich Grise <richgrise(a)example.net> wrote: >I'm not an upgrade-for-upgrade's-sake kind of guy - more like, if-it >ain't-broke,-don't-fix-it. > >So, what would Slack 13 give me that Slack 11. doesn't have, besides the >headaches of IPV6 and that whole new kernel? Slackware64!! Ipv6 is easily ignored (first thing I do after new install is a custom kernel --> latest stable, today that's 2.6.31.2), the distro kernel is already two releases old. And, Tuz is gone now ;) While I've installed slack13 on a couple machines, I'm hesitating on the Internet facing box 'cos slack11 there is working just fine. Then there's new and improved apps, nb is happy :) Though it's a shame PV didn't ship KDE-4.3x instead of 4.2 -- 4.3 is supposed to be almost usable. Grant. -- http://bugsplatter.id.au
From: Michael Black on 6 Oct 2009 18:25
On Tue, 6 Oct 2009, Rich Grise wrote: > I'm not an upgrade-for-upgrade's-sake kind of guy - more like, if-it > ain't-broke,-don't-fix-it. > > So, what would Slack 13 give me that Slack 11. doesn't have, besides the > headaches of IPV6 and that whole new kernel? > If you upgrade now, then the changes with the next release won't be so drastic. Michael |