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.

Got Slackware 14RC running on a laptop here, rock solid so far, but had to compile a newer kernel (3.4.x) to get the ALPS touchpad to work.
I compiled the 3.4 kernel with the existing 3.2.28 headers. Sorry if this sounds like a noobish question but now let's say Pat updates to a 3.2.29 or even a 3.4.x kernel and the distro ends up with a new headers package, wouldn't that mean a recompile is required since the header files have changed (3.2.28 --> 3.x.x)?

Thanks for the link. RC5 just came out with a glibc upgrade among other things (kernel and header packages too)
...so if I understood correctly, I'll have to recompile the 3.4.11 kernel on that laptop, right?

But Pat also said that 3.2.30 was also released just a couple of hours before writing that change log. Personally, after reviewing the change log for 3.2.30 and seeing all the security fixes in there (along with a couple of OLD, serious bugs squashed), there's a good chance I'm going to upgrade to it when 14.0 is released.

But Pat also said that 3.2.30 was also released just a couple of hours before writing that change log. Personally, after reviewing the change log for 3.2.30 and seeing all the security fixes in there (along with a couple of OLD, serious bugs squashed), there's a good chance I'm going to upgrade to it when 14.0 is released.

Wait... all the security fixes? The only security related thing I saw was a bluetooth information leak of ONE single byte! I'd definitely respin for security holes (even though printing has to come before replication, and I've already halted the presses once), but didn't see anything of note. And if there are old bugs that are so serious that you've run into them (and/or can tell me how to reproduce them here) please tell me. If it's serious enough, we'll halt again. Thanks!

kernel 3.2.29 seems to solve the freeze problem of previous kernels. It has been running about 2 days, no freeze occurred. But I compiled that kernel on my own using 3.2.28's config file, and two changes: corresponding processor family and preemption kernel.