Rob Hudson wrote: > What is the initrd.img? When you compile a kernel from source, do you have > to concern yourself with making one? How?
initrd == Initial RAMdisk. It's an ext2 filesystem which lilo loads into memory at boot time. You can look at the contents like this. jogger-egg ~> mkdir initrd jogger-egg ~> sudo mount -o ro,loop=/dev/loop0 /initrd.img initrd jogger-egg ~> ls -F initrd bin/ dev2/ lib/ linuxrc.conf mnt/ sbin/ scripts/ usr/ dev/ etc/ linuxrc* loadmodules proc/ script tmp/ jogger-egg ~> sudo umount initrd jogger-egg ~> rmdir initrd The reason initrd is preferred with 2.4 is that all the filesystem modules are on the initrd. If you hard disk's root is ext3 or reiserfs, the kernel will load ext3 or reiserfs from the initrd before it mounts the real root. Otherwise you'd be restricted to a root filesystem type that's hard-compiled into your kernel. -- Bob Miller K<bob> kbobsoft software consulting http://kbobsoft.com [EMAIL PROTECTED] _______________________________________________ Eug-LUG mailing list [EMAIL PROTECTED] http://mailman.efn.org/cgi-bin/listinfo/eug-lug
