On Friday 2013-06-28 13:33, Linda Walsh wrote:
Perhaps, but not necessarily. I don't know how if linux has advanced to the features of 10-20 year old unix systems or not, but dedicated kernel module linker should be able to take pre-built modules and link them into an image that could be booted from instead of copying them into a separate file-image that the kernel uses it's own internal binary images to access indirectly.
What you describe is exactly the initramfs image. It may be a separate file or it may be piggybacked onto a kernel file. It does not make such a big difference because both parts will be loaded into memory by the bootloader one way or another and thereby are available to the kernel. As usual, you talk big about "features of Unix", but apparently missed the fact that your casual Solaris initrd (well, their concept of it) is in the general excess of 100 MB - and that is without splash and ICU.
process -- nto that it takes ALOT of time, but you could likely read the whole thing in as one large memory image if you really wanted to speed things up...
The bootloader reads the entirety of the initramfs part, after which it is in memory and random access speed is not an issue.
How many times have people complained about something not booting due to the initfs?
Just Linda Walsh. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org