Linux - KernelThis forum is for all discussion relating to the Linux kernel.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
hey,
I am using an ARM mup with a montavista distro with the kernel and rfs on a compact flash. The kernel accesses the rfs from the flash each time which slows down boot up and operation. Can u please tell me how to combine the kernel and rfs into one image so that the rfs is always residing in memory and hence working faster?..
thanks..
naresh
Are you saying that the system is actually installed to the CF, or that the CF card is holding the kernel and initrd file?
I think what you want to be doing is using an initrd file on the card, but it sounds like you have the system just installed directly onto a partition of the card. Is that correct?
What you're looking for is pretty common with some livecds or pendrive installations......
The general procedure is to have a kernel with enough drivers built in and/or have modules on an initial ramdisk (initrd) which is loaded in memory, along with the kernel, for the bootup process.......At the end of the boot process, the kernel looks for a file, usually called linuxrc, which then has instructions to replace the initrd with a compressed root filesystem..........The root filesystem can be loaded in memory, but it depends on the instructions contained in linuxrc on how this is accomplished.......There are a few different ways to accomplish this......This works well with embedded systems, of which quite a few use an ARM architecture, among others......
Here's a Wikipedia page explaining about initrd, and the boot up process.....This should give you an introduction, to start with.....
The general procedure is to have a kernel with enough drivers built in and/or have modules on an initial ramdisk (initrd) which is loaded in memory, along with the kernel, for the bootup process.......At the end of the boot process, the kernel looks for a file, usually called linuxrc, which then has instructions to replace the initrd with a compressed root filesystem..........The root filesystem can be loaded in memory, but it depends on the instructions contained in linuxrc on how this is accomplished.......There are a few different ways to accomplish this......This works well with embedded systems, of which quite a few use an ARM architecture, among others......
---thegeekster
hey..thank god i finally found someone who knows what i'm talkin about..i've tried looking everywhere but everyone just seems to mention that it is 'possible' to load the root file system into memory by merging the kernel and the rfs into one image so that the rfs always resides in memory. How exactly is this done?..i need info both on how to load the rfs onto memory ( which im guessing is by modifying the linuxrc file) and how to combine the kernel and the initial rfs into one image..
It'll be great if u could help me!!
thanks a lot
naresh
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.