Linux - KernelThis forum is for all discussion relating to the Linux kernel.
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 am creating a new custom recovery disk(iso) from the RHEL5 iso.
For that, I am copying only the basic stuff from the RHEL5 iso such as "images" and "isolinux" folders which help to boot the system.
I am successfully able to boot from the custom iso I created.
Now I have one more requirement where I need to do auto loading of a kernel module(cifs.ko) at the boot time.
I tried the following. But did not succeed.
"I modified the initrd.img by copying the cifs.ko into the modules folder where all the kernel modules reside. By default cifs.ko was not there in that folder. But it did not auto load at boot time. I tried to insert some scripts as well. But all in vain."
One possible way I could find out from internet is that, the init script can be modified to insert an "insmod" command for the cifs module.
In normally booted system, the "/boot/initrd-2.6.18-92.el5PAE.img" contains the init which is an editable script.
But in my case, the init is not a script, rather than it is a binary. Because the initrd.img which is there in isolinux folder is having a init binary not a script. Hence I am not able to change it.