Slackware 13.37

tpreitzel · 03-10-2011, 06:17 PM

Personally, I'd just wait for 2.6.38. I'm running 2.6.38-rc8 and it's apparently one of the better kernels since, oh, 2.6.33 or so.

The kernel developers need a slap upside their heads .. At least, Pat has a sense of humor about the mess.

Anyway, moving to 2.6.37 is a better choice than providing "LTS" for an incomplete and buggy 2.6.35 ... Who wants that kind of service?

TechU · 03-10-2011, 06:40 PM

Quote:

Originally Posted by rworkman

Eric has kde-4.6.1 packages, and I've got xfce-4.8 packages (both for -current).

does xf86-video-intel 2.14.901 driver, Mesa 7.11-devel from the beginning of March, and the libva Git library from early March and other related updated git pulled packages exist yet ?

zbreaker · 03-10-2011, 07:56 PM

Many thanks to Pat and all the team. Leet rc1 behaving quite nicely atm although I have to spend MUCH more time to really asses the release. Can't wait to get the dvd with the release # printed thereon...and the t-shirts will be priceless.

animeresistance · 03-10-2011, 09:16 PM

Quote:

Originally Posted by saulgoode

I just hope there isn't going to be a 14.57 Slackware.

Why not ?

Hehehehe ... kidding ... I love Slackware

dc_eros · 03-10-2011, 10:41 PM

Just upgraded to the RC1 and so far everything works fine. I have no time to re-compile virtualbox but I'll try this weekend. Works as expected.

dolphin77 · 03-11-2011, 12:54 AM

Quote:

Originally Posted by volkerdi

"åtta" is exactly correct, but I could easily see it getting transliterated by the media somewhere along the line.

Yeah, my mistake. Found only this:

Code:

From volkerdi@mhd1.moorhead.msus.edu  Thu Jun 14 18:19:46 2001
Return-Path: volkerdi
Received: (from volkerdi@localhost) by darkstar.slackware.com (8.8.8/8.8.8) id OAA03071; Thu, 14 Jun 2001 18:19:46 -0700
Date: Thu, 14 Jun 2001 18:19:46 -0700 (PDT)
From: "Patrick J. Volkerding" <volkerdi@slackware.com>
To: root
Subject: Welcome to Linux (Slackware 8.0 "åtta")!
Message-ID: <Pine.LNX.4.10.000620134926.3041A-100000@darkstar.slackware.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Dear Pat & team, thanks again for all your work. 13.37 looks very promising. I'll definitely order a dvd copy when it is available.

Good luck and thank you.

cycojesus · 03-11-2011, 08:49 AM

Does anyone knows why ruby is still a 1.9.1 when there's a 1.9.2-p136 out and 1.9.2 is the first 1.9.x considered "ready for production"?

mlangdn · 03-11-2011, 08:56 AM

I just finished this upgrade and all is well on my end. I also upgraded Alien's kde packages also. I am in Slackware heaven.

Buumi · 03-11-2011, 09:12 AM

I installed it as well and it's working fine.
Thanks Pat, AlienBob, rworkman and others for great job.

Andersen · 03-11-2011, 09:15 AM

Audacious from 1337 (Audacious 2.4.3) gives this error when playing (stream, or local files):

Quote:

** WARNING **
Audacious has detected that your ALSA device has a broken timer. A workaround
is being used to prevent CPU overload. Please report this problem to your
Linux distributor or to the ALSA developers.

Also, Audacious developers said:

Quote:

Please submit bug reports to your distribution unless you built the very latest version of Audacious yourself. We do not provide end-user support.

Current release is 2.4.4 (February 22, 2011)
Current testing release is 2.5-beta1 (March 11, 2011)

I have to say that I don't see any other problem with 2.4.3, except that "ugly" notice about broken timer when playback starts, and I also don't know if 2.4.4 fixes that problem.

tacticalbread · 03-11-2011, 11:03 AM

Quote:

Originally Posted by cycojesus

Does anyone knows why ruby is still a 1.9.1 when there's a 1.9.2-p136 out and 1.9.2 is the first 1.9.x considered "ready for production"?

I've got ruby 1.9.1p431 (2011-02-18 revision 30908) [i486-linux]

Quote:

Originally Posted by Andersen

Audacious from 1337 (Audacious 2.4.3) gives this error when playing (stream, or local files):

*insert stuff here*

I have to say that I don't see any other problem with 2.4.3, except that "ugly" notice about broken timer when playback starts, and I also don't know if 2.4.4 fixes that problem.

I don't get either of those problems with audacious 2.4.3. o:

Andersen · 03-11-2011, 11:25 AM

Quote:

Originally Posted by tacticalbread

I don't get either of those problems with audacious 2.4.3. o:

You should see the message if you launch audacious from command line. Otherwise everithing looks normal.

tacticalbread · 03-11-2011, 11:30 AM

Quote:

Originally Posted by Andersen

You should see the message if you launch audacious from command line.

Which I did.

GazL · 03-11-2011, 11:32 AM

I noticed the broken timer message in audacious the other day. It seems to only show if you're using the 'default' dmix device. When I change the properties for the alsa plugin to use hw:0 the message goes away, so it looks like it's something to do with alsa's dmix. Only problem with doing this though is that unless your card can do hardware mixing, you're limited to one sound output at a time.

I tried updating to 2.4.4 but that's just the same.

Andersen · 03-11-2011, 11:37 AM

Quote:

Originally Posted by tacticalbread

Which I did.

Oh well..

don't know what to say then.. except that I just found this on the Audacious forum:

Quote:

..The broken timer is an ALSA problem and cannot be fixed within Audacious; it must be fixed in ALSA. That's why the message says to report the problem to your distribution or to the ALSA developers. Not to us.