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.

I wanted to install a 2.4 kernel (from 2.6.10) so my cdrom burner would work ( so i could do back-ups - ah, Irony) and when I booted the 2.4 kernel my /home directory was blank. ( still have /root intact) I tried to restore the 2.6 kernel but I get a kernel panic. is there any way to find and restore the missing files they must still be there somewhere. Please help

* What do you mean "restore" the 2.6 kernel--did you uninstall/reinstall it?
I did a kernel upgrade (downgrade ) to 2.4.27 through synaptic. and my lilo config
has menu listings linux and oldlinux linked to the two most resent kernels in the boot menu
and if I select oldlinux (2.6.10) at boot I get a kernel panic message and the process stops.

* Any other odd information you can give will be helpful, like if you're using raid, etc.
not using raid, using Sid dist. ext3 fs nothing else fancy.

Since nothing strikes me as the obvious problem, you may want to fix your lilo stuff so you can boot back to 2.6. I have no experience w/lilo, so I can't help you there. But since most all issues about cdrecord and 2.6 seem to be minor, I'd look into a fix for that. Better to have your /home dir and no cd burner.

Have you tried looking into fixing cdrecord under 2.6? It usually amounts to wrong device permissions or needing hal+udev.