When booting with initramfs, the kernel creates a tmpfs at /, unpacking the initramfs (typically a gzip'd cpio archive) into it. Then it runs /init (I believe there is actually a short list of programs it tries to run on / in a specific order, but I'd have to look at the kernel sources to verify this).
It's expected that the init process started from initramfs will know how to get everything else going. In the android world, this involves /init.rc scripting what to mount where, etc. Brian [ebmajor <p...@innopath.com>] > > Dear all, > > I'm trying to understand how initramfs, especially 'init' program is > used as a root filesystem. > Usually I've used 'root=/dev/mtdblock0 rootfstype=jffs2' in kernel > command line for root filesystem and my 'init' program > is laid in mtdblock0 so kernel can find where the 'init' program > exists. > > But I read initramfs does not required 'root=' command line. > So, if I don't type 'root=' in kernel command line, how the kernel > finds out where the 'init' program exists? > and what kind of filesystem is using for the block that 'init' program > exists? > > Simply asking, > Can I use kernel command line without 'root=' option? If I can, how > can I use? > > Sincerely. > > > > --~--~---------~--~----~------------~-------~--~----~ unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
