You are not logged in.
Pages: 1
Hi, I was reading about initramfs and I realize that it is great for compatibilty issues because of udev, but no other utility is that correct?
well Im looking for configure my machine to maximum performance at low computer-cost, but using all its resource, Its an file server but also an HTPC...
So I compiled the kernel with the drivers and suport for the basic system and the network as built in...
sound bluetooth and superfluous stuff as modules witch I intent to load them at with the Applications...
well what does you guys have to say its a good ideia??
and if it is
to diseable initramfs is just to disable it in the kernel at general configuration???
Thanks!
Last edited by root.otavio (2012-02-19 12:23:43)
Offline
A little history of the initramfs. It is designed like most ram disks to put disk contents directly into memory for speed and possibly dynamic removal and insertion.
Used to there were kernels that were specifically compiled with certain features. This would reduce the load on the resources with a possibly increased size of the kernel, you could get it really specific, but took time to recompile. Most of the modules are sitting on the disk anyhow, but there is a need to have certain drivers available to further boot the system. Sure, it can be embedded with the right kernel, but most of the operations of the kernel are library based, so it won't really be worth all of that for a few unnoticable benefits for the most part. What you are talking about sounds more like Windows. Do you want to have to load a driver disk for that new device every time? Most applications will cause the proper kernel modules to load which after it is done, for the most part can be unloaded when not in use. However, *nix can be extended to support mulitple clients, including clients that don't have their own disks to boot from. It would be nice not to have to have another copy of the same thing installed on every machine; the cost of everything just goes up. So stating, just leave all the kernel modules where they are, for other machines that can use it, and because it's not worth it. Do you want to recompile your kernel all over again when the network card fails and all you can find won't be an exact replacement for the one you had in there? *nix is about everyday flexibility, not stringent everything has to be carbon copy, and locked down so tight your foot gets stuck. Windows is anal for requiring a totally different driver for the same exact card with a different logo.
You can easily do what you are doing by modifying your /etc/mkinitcpio.conf to do your compiling for you with only the modules you intend to use. But even then, once you get booted, the modules needed later on will still load and unload themselves as needed.
Last edited by nomorewindows (2012-02-22 16:22:43)
I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.
Offline
Pages: 1