On 01/29/2019 01:26 PM, Rich Freeman wrote:
Uh, an initramfs typically does not exec a second kernel. I guess it could, in which case that kernel would need its own initramfs to get around to mounting its root filesystem. Presumably at some point you'd want to have your system stop kexecing kernels and start actually doing something useful...
Which ever type of initramfs you use, the kernel that you are running MUST have support for the minimum number of devices and file systems it needs to be able to load other things. Hence the difference between built-in and modular drivers that I'm talking about.
An initramfs typically loads kernel modules, assuming there are any that need to be loaded.
And where is it going to load them from if said kernel doesn't support initrds or loop back devices or the archive or file system type that the initramfs is using?
Sure, and those are in the kernel that runs the initramfs.
Not if they aren't compiled in. I feel like this (sub)thread has become circular and unproductive. -- Grant. . . . unix || die
