Linux From ScratchThis Forum is for the discussion of LFS.
LFS is a project that provides you with the steps necessary to build your own custom Linux system.
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.
I am new to 1) linux, 2) to linuxquestions so if I am posting this in the wrong place please bear with me.
Here is what I am trying to accomplish:
I have a system I kickstart with an almost standard version of RH9 2.4.20-8. The difference is that I have added an aacraid rpm that fixes a raid problem. I kickstart the machine and the install occurs properly booting to RH92.4.20-8 properly, with the aacraid package installed and a proper entry in modules.conf for the aacraid driver.
(alias scsi_hostadapter aacraid)
So then I attempt to add in my custom kernel rpm. This rpm as part of its %post processing creates a ramdisk image by using
mkinitrd -f myos.img mykernel
The mkinitrd command errors indicating that the aacraid module can not be found in the mykernel. Which is how I have set it up, because I want to use the original distributions raid driver.
Now as I see it there are two options ( and i am sure as is usually the case I have missed one, two or fifteen).
1- somehow indicate to the mkinitrd routine that there is another place to look for the aacraid module.
2- include the aacraid module into our kernel and have it installed along with mykernel*rpm.
I'm not familiar with raid and also not with initrd...
here are my thougts:
-does the aacraid module have to be loaded during initrd stage or could it not be loaded later in the boot-process? So if the module is loadable with your custom-made kernel-rpm there would not be a problem
-to make things easier (and the kernel-image probably a bit larger) why dont you skip the initrd method of booting completely and just boot your kernel directly - how to do it depends on the method you use to boot - I'm using lilo. But the initrd-method may be the standard RH-way to boot - so you may have to do some changes to some conf files. I've never used RH, so I cant tell you what to do exactly.
-english is not my native language - I don't know what you mean by:
" Is it normal to try to cross distribute modules? "