SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
It has been awhile since the last -current update, but that doesn't really mean much. Look at how long it took before -current was updated after the Slackware 11.0 release. Just because we aren't seeing anything in -current doesn't mean that Pat isn't working on something behind the scenes. For all anyone knows, tomorrow he might put up 100 new packages.
Since he has not officially said development is frozen, we have to assume it is still continuing, albeit quietly. When development freezes, he will announce it in the Changelog, and then there will still be awhile before he makes that an official release. We haven't even had an RC1 yet, let alone it being ready for an official 11.1 release.
keeping a system running bleeding edge -current can be a pain as it's currently changing causing compatibility issues with various packages. I would recommend only patching the software when updates are sent out for -stable from Patrick rather than following -current too closely on a production machine
Hey, maybe it wasn't anything directly Slackware related ... I mean mostly there were some xserver crashes, and few lock-ups, but not too many. As I said, maybe it's all fixed now. I'll try upgrading to -current again soon ... maybe on my laptop this time.
Still, I wouldn't say it's as stable as ... Slackware 11.0 (duh ) ... therefore, maybe next release (11.1 or whatever) won't be so soon. (or maybe it will ?)
Last edited by H_TeXMeX_H; 05-29-2007 at 12:40 AM.
Ah, -current has received loads of updates yesterday Gotta test'em, I had trouble installing KDE yesterday as some of the packages failed to install properly. I installed all KDE packages but K-Menu was almost empty, hopefully this solves that issue.
Ah, -current has received loads of updates yesterday
Big changes indeed. HAL has been added, and KDE has been re-compiled to suit. Interesting stuff.
I'll be looking into Pat's Slackbuild scripts for everything, to see how he did it all. I've compiled HAL a few times on various Slackware installations, and it always seemed "clunky," like I did something wrong somewhere. It'll be interesting to see how it all works!
Whenever you upgrade KDE, you should delete your ~/.kde directory.
Ok, I'll test that but my problem appeared after I installed KDE for first time.
I try to delete the folder and upgrade KDE after it to see if it will solve my issue.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.