| 1 |
On Thursday, March 15, 2012 01:05:12 PM Neil Bothwick wrote: |
| 2 |
> On Thu, 15 Mar 2012 08:41:38 -0400, Tanstaafl wrote: |
| 3 |
> > > That's why I build the initramfs into the kernel and not as a |
| 4 |
> > > 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 |
> Technically, we are all using an initramfs as all 2.6/3 kernels mount an |
| 16 |
> initramfs when they load. If does not contain an init script, they fall |
| 17 |
> back to the legacy behaviour. |
| 18 |
> |
| 19 |
> See /usr/src/linux/Documentation/filesystems/ramfs-rootfs-initramfs.txt |
| 20 |
|
| 21 |
Even when the init-options are not set? |
| 22 |
|
| 23 |
*** |
| 24 |
admin@hera ~ $ uname -a |
| 25 |
Linux hera 2.6.34-xen-r4_dom0 #1 SMP Wed Dec 8 15:52:31 CET 2010 x86_64 AMD |
| 26 |
Phenom(tm) II X4 955 Processor AuthenticAMD GNU/Linux |
| 27 |
|
| 28 |
admin@hera ~ $ zcat /proc/config.gz | grep -i init |
| 29 |
CONFIG_INIT_ENV_ARG_LIMIT=32 |
| 30 |
# CONFIG_BLK_DEV_INITRD is not set |
| 31 |
# CONFIG_SCSI_OSD_INITIATOR is not set |
| 32 |
CONFIG_DEBUG_MEMORY_INIT=y |
| 33 |
# CONFIG_PROVIDE_OHCI1394_DMA_INIT is not set |
| 34 |
*** |
| 35 |
|
| 36 |
-- |
| 37 |
Joost |
Archives