I predict 13.2 will be out within a month

sycamorex · 02-20-2011, 01:01 AM

Quote:

Originally Posted by D1ver

Using -current I found something interesting..

Code:

X -version

Code:

X.Org X Server 1.9.4
Release Date: 2011-02-04
X Protocol Version 11, Revision 0
Build Operating System: Slackware 13.37 Slackware Linux Project
Current Operating System: Linux slackbox 2.6.35.11 #1 SMP Mon Feb 7 23:30:56 CST 2011 x86_64
Kernel command line: auto BOOT_IMAGE=Linux ro root=801 vt.default_utf8=0
Build Date: 08 February 2011  08:45:11PM

I see what you did there :P

LOL

narz · 03-08-2011, 05:11 PM

*crickets*

No RCs yet? At this point it seems Pat should drop 13.2 and shoot for 14.0 with new XFCE and KDE and drop HAL. I realize Slackware is released on a somewhat arbitrary timeline of "it's ready when it's ready", but what really is holding -current back from freezing up and shipping out as stable?

hitest · 03-08-2011, 06:24 PM

Quote:

Originally Posted by narz

*crickets*

No RCs yet? At this point it seems Pat should drop 13.2 and shoot for 14.0 with new XFCE and KDE and drop HAL. I realize Slackware is released on a somewhat arbitrary timeline of "it's ready when it's ready", but what really is holding -current back from freezing up and shipping out as stable?

You must have patience. Pat has a proven track record with "getting it right". I am happy to wait.

Loslobo · 03-08-2011, 11:05 PM

Slackware will come when it's ready. Or when one's online 'back' is turned.

Knowing my track record with -current. I'll download the March 2 version onto a DVD and install it on a spare partition tonight. After setting things up and admiring all the shiney Slackware newness, that's when -current tree shall receive a boatload of updates. :P

lumak · 03-09-2011, 03:25 AM

It's so much nicer to use a mini boot CD to install directly off the harddrive. Maybe that's to much head movement for some, but it doesn't seem bad to me.

Andersen · 03-09-2011, 12:29 PM

Talking about RC?

Quote:

Current (pre-release) ChangeLog for x86 (32-bit)

Wed Mar 9 05:52:06 UTC 2011

Hey folks, I think it's time for Slackware 13.37 (hopefully this helps
make up for our lack of code names) release candidate 1!
After a lot of testing and consideration, we've decided to go with the
recently released 2.6.37.3 Linux kernel which seems to work best for X,
contains support for Speakup, and looks like a better kernel branch to
be using as we move forward.
Please test so we can have a stable release soon. :-)

FeyFre · 03-09-2011, 01:00 PM

Quote:

we've decided to go with the recently released 2.6.37.3 Linux kernel

I hope this is joke? As far as 2.6.37 some third-party kernel modules will not compile. Any ideas?

volkerdi · 03-09-2011, 01:07 PM

Quote:

Originally Posted by FeyFre

I hope this is joke? As far as 2.6.37 some third-party kernel modules will not compile. Any ideas?

Joking about the kernel is against the law. Anyway, which drivers are presenting a problem? Perhaps there is a fix already.

Darth Vader · 03-09-2011, 01:18 PM

If we talk about top kernels, I suggest to consider the (will be released in one week) 2.6.38, because the main theme of this series, compared with previous 2.6.37, is a huge improvement in DRM stack for the major players: Intel, NVidia and ATI!

volkerdi · 03-09-2011, 01:21 PM

Quote:

Originally Posted by Darth Vader

If we talk about top kernels, I suggest to consider the (will be released in one week) 2.6.38, because the main theme of this series, compared with previous 2.6.37, is a huge improvement in DRM stack for the major players: Intel, NVidia and ATI!

We will not be waiting for 2.6.38.3.

FeyFre · 03-09-2011, 01:24 PM

Dahdi-2.4.0
As far as month ago kernel modules will not compile because of full disappearance of DECLARE_MUTEX macro. Yes, they fixed it in their trunk version(and just noticed released new version with that fix week ago). I can accept risk of using untested version of Linux Kernel, or I can accept risk of using untested version of Dahdi drivers, bot not both simultaneously. So I forced to use old Slackware(with old Kernel) and old Dahdi drivers.

Darth Vader · 03-09-2011, 01:28 PM

Quote:

Originally Posted by volkerdi

We will not be waiting for 2.6.38.3.

Then, the bullet is in the gun, ready to be shoot?

volkerdi · 03-09-2011, 01:28 PM

Quote:

Originally Posted by FeyFre

Dahdi-2.4.0
As far as month ago kernel modules will not compile because of full disappearance of DECLARE_MUTEX macro. Yes, they fixed it in their trunk version(and just noticed released new version with that fix week ago). I can accept risk of using untested version of Linux Kernel, or I can accept risk of using untested version of Dahdi drivers, bot not both simultaneously. So I forced to use old Slackware(with old Kernel) and old Dahdi drivers.

Dahdi-2.4.1 is out and supports 2.6.37.x (all the way through 2.6.38-rc6 as well):

http://www.venturevoip.com/news.php?rssid=2513

FeyFre · 03-09-2011, 01:46 PM

volkerdi, I know about 2.4.1, but as I said above, it is unacceptable for me to use untested versions of both kernel and driver.

Darth Vader · 03-09-2011, 04:55 PM

Quote:

Originally Posted by FeyFre

it is unacceptable for me to use untested versions of both kernel and driver.

While I can't comment about this driver quality, I can say you a joke living between admins:

You known why there is no Slackware Enterprise Edition?
Because anyone can run a production server using Slackware-current.