| 1 |
On Tue, 29 Jan 2019 13:37:43 -0700, Grant Taylor wrote: |
| 2 |
|
| 3 |
> > An initramfs typically loads kernel modules, assuming there are any |
| 4 |
> > that need to be loaded. |
| 5 |
> |
| 6 |
> And where is it going to load them from if said kernel doesn't support |
| 7 |
> initrds or loop back devices or the archive or file system type that |
| 8 |
> the initramfs is using? |
| 9 |
|
| 10 |
AFAIR the initramfs code is built into the kernel, not as an option. The |
| 11 |
reason given for using a cpio archive is that it is simple and available |
| 12 |
in the kernel. The kernel itself has an initramfs built into it which is |
| 13 |
executed automatically, it's just that this initramfs is usually empty. |
| 14 |
So loading an initramfs is trivial for any kernel, and loading anything |
| 15 |
after that is handled by the initramfs. |
| 16 |
|
| 17 |
That only leaves loading the initramfs file from disk, which is handled |
| 18 |
by the bootloader along with the kernel file. |
| 19 |
|
| 20 |
|
| 21 |
-- |
| 22 |
Neil Bothwick |
| 23 |
|
| 24 |
TEXAS VIRUS: Makes sure that it's bigger than any other file. |
Archives