Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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 have a problem I have been unable to locate any information on. I have 2 different partitions on my drive and I use LILO to boot into either one. One partition has the default redhat 2.4.18-3 kernel. The other has a kernel I compiled myself which is also 2.4.18 but I have removed many modules and reduced the size of the OS.
I have a module that is compiled seperately from the kernel that I want to use on both partitions. Do I need to recompile while running each kernel or do anything special like run depmod twice? Or will the module work on either because it is the same linux version?
Currently I force the module to load since when I compile the version is 2.4.18-SPECIAL. I notice that sometimes I have flawless execution and other times I have a crash. Anyone who can give me any pointers about any bonehead things I'm doing, please do it. If compiling the same version of linux with diferent options is considered a separate OS, then what other steps do I need to take?
I recompiled for my target kernel and then recompiled the driver and got a driver of a very different size that worked on that target. It seems that recompiling the kernel with different options actually MAY change the kernel enough as to be incompatible with some drivers. I've done recompilations since then that haven't changed the driver size at all, but now I always compile just to be sure