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.
After days of frustration, I was finally (thanks to the help of people here) able to compile a 2.4.29 kernel on my Slackware 10 along with alsa for sound support. I'm now wondering if there is or will be a way to update Slackware when Slackware 10.2 comes out??
- Updated versions of the Slackware package management tools make it
easy to add, remove, upgrade, and make your own Slackware packages.
Package tracking makes it easy to upgrade from Slackware 10.0 to
Slackware 10.1 (see UPGRADE.TXT). The slackpkg tool in /extra can
also help update from an older version of Slackware to a newer one,
and keep your Slackware system up to date. In addition, the new
slacktrack utility (in extra/) will help you build and maintain
your own packages.
Sometimes there are problems, and different Slackers will
tell you their method of updating. I prefer to do a fresh install
when moving from one version to another. This requires some
good knowledge of your system, so that you'll have the right
configs and settings saved and available. I'm in the middle of
upgrading 3 comps right now, and am realizing some things
that I didn't save which would have made it a little quicker to
I read that txt file-looks good! I need to work on getting my Slackware Laptop networked to my Fedora Core Tower first so that I can use my tower's speed to upgrade all of Slack-rather than just the kernel. Thanx for the info!
Originally posted by Chinaman And btw -- there won't be a Slackware-10.2 -- next release will be Slackware-11.0
Where can we find more information about the upcoming Slackware 11.0 release? I've heared various rumors about 2.6 kernel vs. 2.4, skipping or including GNOME, KDE 3.3 vs 3.4 etc - and it'd be interesting to know where to go for some more information on the 11.0 roadmap and release schedule.
Dunno if you wanted an answer specifically from Chinaman - sorry if I'm intruding.
It's *usually* 6-9 months, and was released on 2/2, so we're talking fall, but projections are castles made of sand, and all.
I've never installed current directly, but see no reason why you couldn't. However, 10.1 and upgrading to current is usually no problem and, if you've already got a Slack on, it might be easier that way.
And Chinaman's right - read all the textfiles Slack provides like UPGRADE.TXT, and then keep up with the ChangeLog.
-- Correction, I have installed 'from current' in that I've installed a 'release candidate'. Amounts to the same thing - just at the end of the version cycle instead of the beginning.
Originally posted by digiot I've got a USB 2.0 WD that worked out of the box so it's likely - good luck with yours.
Thanks again - I've read elsewhere that the 2.4.x kernel has some issues with large USB 2.0 block devices (ie. my 120GB Maxtor USB-disk) - that performance dropped like a rock when connecting or accessing the disk. I've seen no firm information on that though
(sorry, this is getting slightly off-topic, but I'm dying for an answer so I can get to work on my SuSE->Slackware conversion )