| 1 |
On 2012-03-15 9:05 AM, Neil Bothwick <neil@××××××××××.uk> wrote: |
| 2 |
> On Thu, 15 Mar 2012 08:41:38 -0400, Tanstaafl wrote: |
| 3 |
> |
| 4 |
>>> That's why I build the initramfs into the kernel and not as a separate |
| 5 |
>>> file. If I do something to break the initramfs I just boot the |
| 6 |
>>> previous kernel knowing it will still work. |
| 7 |
>> |
| 8 |
>> Ok, time to show my ignorance... |
| 9 |
>> |
| 10 |
>> How would I know if I am using an initramfs, and if I was, whether it |
| 11 |
>> was built into the kernel or not? |
| 12 |
|
| 13 |
> Well, you built the kernel, so you should know. |
| 14 |
|
| 15 |
Well, since I basically just used a kernel .config that someone else |
| 16 |
originally set up, copying .config over and running make oldconfig when |
| 17 |
upgrading over the years, stumbling through any changes that broke |
| 18 |
anything (like when some changes to iptables broke my firewall back |
| 19 |
around 2.6.2x), I really didn't know - but I just confirmed that it is |
| 20 |
indeed built into my kernels, so, now, how do I know if I am *using* it |
| 21 |
or not? |
| 22 |
|
| 23 |
> Technically, we are all using an initramfs as all 2.6/3 kernels mount an |
| 24 |
> initramfs when they load. If does not contain an init script, they fall |
| 25 |
> back to the legacy behaviour. |
| 26 |
|
| 27 |
So, how do I know whether or not 'it contains an init script'? |
| 28 |
|
| 29 |
I know, my ignorance is confounding... |
| 30 |
|
| 31 |
> See /usr/src/linux/Documentation/filesystems/ramfs-rootfs-initramfs.txt |
| 32 |
|
| 33 |
Read it, thanks, but it didn't help me answer the above... |
Archives