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.
I started to follow along with that kernel compile tutorial at the top of the slackware forum and ran into a problem
I got as far as cd /usr/src/linux.....no such file or directory.
for some reason it is showing a /RPM directory instead of /linux. Don't know what to do next........?
You could search the forum. Anyway, what you need to do is to install the kernel source. It's available from slackware ftp sites - you'd better get the .tgz with patches applied, to save time (compared to getting the plain vanilla and patching it yourself). Slackware 9 uses 2.4.20 by default, but the 2.4.21 kernel has recently been released so you might want to use that one instead. Check out http://www.slackware.com/security/vi...ecurity.522012
hey thanks for replying, yea, search the forums for this....that would be fun.
But yea, I'm downloading right now. Thanks.
i was curious about how to find out about updates. Maybe I should subscribe to that little newsletter they have...
You get me a bit confused here. First you ask if the kernel is compiled for 486 architectures...and then you ask about the precompiled kernel(s) on the Slackware CD. Well, the precompiled kernels on the Slack 9 CD's are afaik compiled for i386 (though that'll change with Slack 9.1). Now, since you talk about kernels and precompiled kernels I assume that you in the former case refer to the kernel source...which, of course, isn't compiled at all...?
well, I got the source from kernel.org, followed the tutorial givin at the top on the slackware forum and everything seemed to go fine until rebooting. Under LILO I only have the options to boot from Windows or linux.old, nothing about the new kernel.
Did you run lilo after editing the lilo.conf file? If you don't , the new kernel won't appear on the lilo menu. This is an easy thing to overlook (I've done it several times) but based on your description, I'd bet it's the cause of that problem. -- J.W.
ah, sorry, now only i notice how poor my question was...
i mean those precompiled kernel comes with standard slackware 9.0 cd and the newest precompiled 2.4.21 kernel packages on slack ftp( in /patch/packages/ ) that we can use to update our system directly....
are they both use i386 configuration only?
if so, then is there a different if i compile my own the kernel to use the pentium 4 option?
will it be faster? or their performance are just identical....
(y they never bundle with a kernel compiled for i686?)
Originally posted by J.W. Did you run lilo after editing the lilo.conf file? If you don't , the new kernel won't appear on the lilo menu. This is an easy thing to overlook (I've done it several times) but based on your description, I'd bet it's the cause of that problem. -- J.W.
You where absolutely correct on that one. Problem is now that my hard drive crapped out since last I was in here. Had to do it all over again. New install n everything. Oh well. At least its working now.