The Ultimate "When Will The Next Slackware Release Arrive" MegaThread
SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
You know what, I just tried 1.4.2 here and I actually found it a little more buggy for me maybe it's the libtunepimp as willysr pointed out? I did notice that 1.4.2 compiled and 'make' really really fast this time wow!
I had to put ruby in to get it to compile, and that seemed to go ok. I wound up going back to version 1.4.1 again as it seems more stable for me.
The amarok is a real promising app, but I can't use it at all to be honest no matter what version. I'm probably doing something wrong here, but I cant get amarok to play my flac files and hear computer beeps or error messages, etc in KDE at the same time.
I really like the XMMS but no media library extension was tuff, but I found an add on to XMMS that puts a KDE-kicker that works really well to solve the 'no media library' part of xmms it's at http://xmms-kde.sourceforge.net/about.html
It'll be nice to see the latest release and give it a try.
Slackware was the VERY FIRST GNU/Linux distro I ever tried, WAY back in 1995. It was relatively easy to install back then, but device support wasn't even close to what it is today. On the other hand, that old software absolutely SMOKED on an old Micron P100 - a 100 Mhz Pentium with a 2.1 GB hard drive, a 2X CDrom reader and 16 MB of memory. Try to run much of anything on that kind of hardware today!
These days, I tend to prefer Debian GNU/Linux software, and I happen to be running the Debian Etch release right now. Debian still has one of the worst installers in the business. It is WAY too interactive, and the only way to shut it up is to provide a configuration file and do an unattended install. Otherwise, it prompts you for parameters before installing the packages, then once all the packages are installed, it prompts you over and over again to tell it how you want it to configure various packages. Once installed, though, it is terrific, the best overall combo available. You typically install Debian binary packages (.deb format) but you can also install Debian sources and build anything you want. Naturally, you can also use alien and install other kinds of packages, such as Slackware .tgz packages or Red Hat .rpm packages.
Slackware is one of the few distros that comes close to Debian in snappiness out of the box. I suppose you can get that by using a source compiled and optimized distro, but it just isn't worth the time and effort to me.
I'm not quite the Slackware fan I once was. I tend to mostly use the prepackaged Debian distros, like SimplyMEPIS, Kubuntu, Kanotix, and Knoppix, but Slackware still holds a special spot in my heart, being my first distro experience on a PC. (Prior to that, I'd been using UNIX systems for the fifteen to twenty years before that). Today, I use Red Hat Enterprise Linux and Sun Solaris systems at work (the Solaris boxes are mostly on their way out the door, though). On the desk, I am forced to use Windows XP at work. At home, I use some flavor of Debian-based Linux about 95% of the time, and I test distros the other 5%. I hope to give this new, upcoming Slackware a nice test and perhaps ride it around the block for a while, just for good old times!
looks like Pat figured-out why 220.127.116.11 wasn't booting...
the most interesting thing seems to be:
After much thought and consultation with developers, it has been decided to
move 2.6.17.x out of /testing and into /extra. It runs stable by all reports,
has better wireless support, and is not going to be stale as soon. In
addition, HIGHMEM4G has been enabled. This caused no problems with my old
486 with 24MB (the one I use for compiling KDE ;-), and Tomas Matejicek has
enabled this in SLAX for a long time with no reports of problems, so I
believe it is a safe option (and is needed by many modern machines).
Thanks again to Andrea for building these kernels and packages. :-)
Wow! Great stuff in the changelog. I shouldn't need to recompile anything with the 18.104.22.168 kernel as it will auto detect & use my SMP AthlonX2 & with HIGHMEM4G enabled it will handle my 2gb system! Excellent. No need to recompile for me then hopefully! It's not primarily lazyness on my part, it's just that I usually break something. I've also just ordered the Slack11DVD+Essentials bundle + donation, but who knows how long AirMail will take to reach Scotland! All the stuff about lm_sensors looks good too, so I may eventually get the desktop display with system stats. ...if I understood the changelog correctly.
Eternal_Newbie; I like your location 'The Pudding Isles'! I even Googled for it, I'd like it to be a real place.
Last edited by Mr Marmmalade; 08-26-2006 at 03:51 PM.
I can only imagine how long it must take to compile stuff.
But better safe then sorry I say.
Originally Posted by Eternal_Newbie
But on a serious note I suppose compiling Slackware on a 486 is the only real way of making sure it works on one.
guys, i'm pretty sure the compiling KDE on a 486 thing was a joke...
he probably just uses that 486 to test binaries...
on a side note, IIRC kernel 2.4.32 wouldn't boot on a 486 if compiled on a 486 (due to a bug)... so if that kernel was compiled on patrick's 486, then nobody would have been able to boot -current on 486s during the many months -current was on 2.4.32...