yepp, I also noticed it. And agree with you about those too. Maybe after throwing out 2.4 from default install.

Very unexpected! I had thought that Slack-11 was ready to be set on stone. Never imagined Pat accepting this for Slack-11, but for Slack-11.1.

I'll try to give it a good test to see if I find any bugs.

I'm not sure... If KDE gets compiled with that, then DBUS/HAL will become a dependency.

I personally, dislike HAL. Don't get me wrong, it's quite useful, but I feel like HAL was designed more as a quick-hack than a full solution. I know it wasn't, but is just that it gives me that feeling.

And for DBUS... why was it done at all? What was wrong with just using a pipe or a socket for communicating between processes and just create a protocol instead of a whole API? Although there is nothing wrong with DBUS, I think that they just reinvented the wheel. And they had to use XML, just to be fashionable, of course!

Actually, after all, I think I don't really care, I can always switch back to Fluxbox or get used to XFCE.

Looks to me like a lot of problems from trying to be both 2.4 and 2.6 kernel compatible.
current has been really stable for the last few months until this week when for the first time I have non-booting machines.

Is it just me, or is anyone else also wondering if all these fixes and added features means that we are weeks instead of days away from release?
I can't wait anymore, I'm so excited and I just can't hide it!
lol, sorry for that, but I just can afford to dl current and 11 release due to exorbitant telecom prices in south africa...

Yes. Could even be months. If you look at yesterday's Changelog, it seems that there are some complaints about the new udev.

Personally, I'm happy to wait. As long as the final product is relatively bug free.

as it always is
don't you just love slack...

Yep, slack rules:-) It'll come when its ready.

My bets are on 'Talk Like a Pirate Day', arr

I think we missed 11. I think it was back in June, sometime around kde 3.5.3.

It feels like we're now working on 11.1, as alot of stuff that was guessed to come in 11.1 is now showing up in -current; 2.6 kernel in /extra, 2.6.17 in /testing, huge26.s is 2.6.16.27, test26.s is 2.6.17, udev, sysfs, kde 3.5.4. Alot of major changes to test out now.

Anyone have similar feelings? Or maybe it's just me because I'm having (udev) boot problems for the first time since... ummm, actually I don't think I've ever had a broken Slackware before. I haven't been running -current for long but when was the last time it broke on a large scale like this?

._.

To me, it makes more sense to have things breaking prior to a major release, rather than a minor release. However, it's been mentioned that major releases follow version changes in glibc. If this is in fact the only criteria in determining the next number to release with, then perhaps you're right.

Yes, but there was only about 5 months between 4.0 and 7.0.

but how come Slackware just from 4.0 and jump a big gap to 7.0?

Welcome to LQ!

<Linux> Google is your friend. It was basically to 'keep up with the Joneses,' also the DeadRat's.

oh, yeah. I've just tried reading the article about Slackware on wikipedia.org. quite interesting ^_^

Now Im using Slackware 10.2 for my Toshiba laptop and looking forward to next version!

The udev complaints have died down, the major issues were the many .new files in rc.d and the unannounced at the time requirement that the kernel needed to be 2.6.15 or newer.