Hopefully, gcc-4.1.x won't make it into the next slackware version. There are still TOO many things which won't compile with it.

As for glibc-2.4 (and the lastest libusb and maybe some other libraries which are being kept behind because of compatibility with 2.4), we will be seeing that as soon as Slack switches to Linux-2.6... which may or may not be Slack 11 ;)

edit: Now that I think about it, It could be nice to have a testing/ gcc-4.1.1, since developers need it to make it compile their things...

I had not noticed how dated libusb had got, that might explain some of the USB stability problems that Slackware has that my Ubuntu machines don't.

Don't hold your breath for a 2.4.33 release, progress is very slow although there are a lot of fixes already in there. I cannot see Pat wanting to release a patched 2.4.32 kernel.

well, like i said before, it's not that i don't believe you... i'm just very skeptical about what you are saying... i'm pretty sure if i said something like that without backing it up you'd be skeptical also (at least i hope you would)...

IMHO, there isn't anything in the -current changelog (AT THE CURRENT TIME) that would indicate a sudden shift to 2.6 as the new heart of slackware... of course it could happen, i'm just wondering what makes you so sure about it... you did say you'd post a link to where patrick says this will happen in 11.0 - i'd still like to see it, and i'm sure others might also...

yeah, i hear ya... i'm definitnely not holding my breath (i hope marcelo takes all the time he needs), but i am keeping-up with the latest prepatches at least... right now i'm on 2.4.33-pre3 (with a couple patches pulled-down from git), but it looks like pre4/rc1 is just around the corner...

it sucks that the kernel (2.4.31) which is currently part of the latest slackware release (10.2) is so riddled with known security issues and other bugs... thank goodness it's easy for us to patch and recompile, but those that don't know how to do that are kinda left out in the cold...

i think one thing patrick could do is to provide hotfix kernels, in the style of /extra packages... so, for example, the official slackware kernel package for 10.2 would still be 2.4.31, but those who wished to download a binary package of the same version but with all the security patches and stuff applied could do so also... it wouldn't be a lot of work for patrick, as he could use the sources from the 2.4-hf kernel tree... there's hotfix kernel sources there going back to 2.4.28, so he'd be able to knock-out a few past slackware releases also if he wanted... anyways, it's just a thought...

Regarding a change to the 2.6 kernel in Slackware 11, I found the following in the 10.2 release notes:

I assume this means that Slackware 11 will default to the 2.6 kernel.

Like i said though, it doesn't matter what he said. He is clearly going to still ship 2.4 as the default kernel by the versions of certain packages that he still ships.

Unless he makes radical changes, expect 2.4 to come.

I would say that as a 2.4 - ie 10.3 release - Slackware is very stable now and the latest kde 3.5.3 has just come out.
From his past cautiousness, there is no way Pat would release with a new major kde release before the .1 coems out

I am having far less problems now with the generic 2.6 kernels than 2.4, which never worked cleanly on the KT400 chipset - another case of 2.4 incompatibility with a lot of hardware newer than 2 years old.

As just about all of the other major distros are now 2.6, nobody is looking out for 2.4 compatibility anymore.

I think KDE 3.5.3 WILL make it into Slackware-${NEXTVERSION}, Slack-current has been using 3.5.2 by now, and 3.5.3 fixes the bugs found by Coverity -that means that it should be more stable. So I see no reason not to upgrade. Besides, it is a minor release with no major changes (but a huge number of small changes, though).

I never had problems with Slack's 2.4 kernel on my KT400 board (ASUS A7V8X-X).

Ok. I'll jump on this bandwagon. The change logs are missing this morning (current and stable). Where can they be? I know, maybe he needed to move both of them around because 11 is now the stable version. Na, probably some technical glitch with the web server. We'll have to wait and see ;)

MagicMan

ftp.slackware.com seems to be down at the moment (at least I can't access it), which would explain the missing changelogs.

I'm only guessing, I dont know anything really. But many distro's like damn small, vector run the 2.4 kernels now after having made versions of 2.6 . they say the 2.4's work better for old hardware is why they went back to the 2.4 kernels. Maybe? and I dont know really, Pat will have a stock 2.4 kernel as slackware has positiioned itself to reach into the past for the oldest of hardware.

I think I saw slackware running on an abacus once.

Here's a link: http://www.learningwithtoys.com/meli...oug_abacus.htm

Slackware 11
 

It's so close.

I feel it in my water.

O.K., but what we all Really, really, really, really, really, really, really, really,
really, really, really, really, really, really, really, really, really, really, really,
really, really, really, really, really, really, really, really, really, really, really,
really, really, really, really, really, really, really, really, really, really, really,
really, really, really, really, really, really, really, really, really, really, really,
really, really, really, really, really, really, really, really, really, really, really
want to know is: When will that be?

(Sorry cw, I just couldn't resist!)

Tomorrow ;-)

I hope not. Current is currently more unstable than it has been in a few months.