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