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 can save it as anything and anywhere you want. i think it defaults to saving itself in the current directory as .config (moving whatever .config is there to .config.old), but i don't think it matters as long as you remember where you saved it for when you want to load it again to reconfigure.
doesn't moving vmlinuz to vmlinuz.old just rewrite the old kernel? i use DaOne's "change lilo first method" (with make/make install after make bzImage) but maybe that's why you can't boot the new one but only the old? what replaces vmlinuz after you move it?
(btw, you forgot to list make modules_install after make modules, but i'm guessing you did that.)
>edit: oh, the computer *reboots* when you select slackware.old? that is weird. can you boot any kernel at all? if you can, immediately rename it vmlinuz_safe, then add that to lilo. then no matter what you do, you'll always be able to boot vmlinuz_safe, at least. you won't have to worry about vmlinuz.old getting rewritten with bumped versions.
Last edited by synaptical; 09-05-2003 at 07:44 PM.
the first time i tried it, i rewrote my good kernel with a messed up one, and then had to recompile a bare.i kernel to start over. that might be your best option, though, if you can't get anything else to work. LMK and i'll try to help walk you through it. just don't give up, it's not really hard, it's just that the files get messed up sometime and you just have to get everything sorted out.
Ok I was doing what Skyline posted but I rebooted before trying to type lilo to update it and the new kernel loaded. I am going to finish what I was suppose to do and see if I get the same results. I will let you guys know
Ok it worked. One last question. I used swaret to get the kernel-source for the 2.4.22. Does anyone know the website. I went to kernel.org and downloaded that but when I unzip it it goes into home directory. How do I get it to unzip into /usr/src/