On Thursday, March 15, 2012 01:05:12 PM Neil Bothwick wrote: > On Thu, 15 Mar 2012 08:41:38 -0400, Tanstaafl wrote: > > > That's why I build the initramfs into the kernel and not as a > > > separate > > > file. If I do something to break the initramfs I just boot the > > > previous kernel knowing it will still work. > > > > Ok, time to show my ignorance... > > > > How would I know if I am using an initramfs, and if I was, whether it > > was built into the kernel or not? > > Well, you built the kernel, so you should know. > > Technically, we are all using an initramfs as all 2.6/3 kernels mount an > initramfs when they load. If does not contain an init script, they fall > back to the legacy behaviour. > > See /usr/src/linux/Documentation/filesystems/ramfs-rootfs-initramfs.txt
Even when the init-options are not set? *** admin@hera ~ $ uname -a Linux hera 2.6.34-xen-r4_dom0 #1 SMP Wed Dec 8 15:52:31 CET 2010 x86_64 AMD Phenom(tm) II X4 955 Processor AuthenticAMD GNU/Linux admin@hera ~ $ zcat /proc/config.gz | grep -i init CONFIG_INIT_ENV_ARG_LIMIT=32 # CONFIG_BLK_DEV_INITRD is not set # CONFIG_SCSI_OSD_INITIATOR is not set CONFIG_DEBUG_MEMORY_INIT=y # CONFIG_PROVIDE_OHCI1394_DMA_INIT is not set *** -- Joost
