| 1 |
Am Montag, 9. Februar 2009 23:26:46 schrieb Stroller: |
| 2 |
|
| 3 |
> Am I not correct in thinking that initramfs used to be / can be / was |
| 4 |
> originally a separate file which goes in /boot and is described with |
| 5 |
> an extra boot parameter? |
| 6 |
|
| 7 |
Yes, you are. There are several ways nowadays. I use the easy one: Populate a |
| 8 |
directory tree with the contents of the initramfs and configure that directory |
| 9 |
in menuconfig. The kernel build system handles the details. |
| 10 |
|
| 11 |
> I wasn't aware that you could embed the initramfs into the kernel |
| 12 |
> itself - after reading Neil's message yesterday I looked up more about |
| 13 |
> the initramfs, contemplated about the idea of doing so and decided |
| 14 |
> "naw, you'll never be able to do that, it would make the kernel too |
| 15 |
> big and take up too much memory". |
| 16 |
|
| 17 |
Nope. It's freed right after swithing to the real root fs. |
| 18 |
|
| 19 |
> I certainly can recognise that you're doing something bogus, because |
| 20 |
> your kernel parameters use "realroot=" and not just "root=" |
| 21 |
|
| 22 |
Luckily the kernel ignores everything it doesn't know so you can give it any |
| 23 |
option you like. In this case I use "realroot" inside initramfs to tell it (by |
| 24 |
parsing /proc/cmdline) what's the real volume for the encrypted root device |
| 25 |
(/dev/mapper/c-root) listed in fstab. |
| 26 |
|
| 27 |
Bye... |
| 28 |
|
| 29 |
Dirk |
Archives