Jeremy Huntwork wrote:
Even though the initramfs image is built in to the kernel itself? Does the kernel drop the compressed image from memory after it has unpacked it? If so, that's great.
Yes, I believe that's the whole point of it being tacked onto the end of the kernel image, instead of somewhere else; once it has been unpacked, it is released.
But at least with my cd, there never is a root system mounted after the initramfs. With the current ones, if you 'ls /' you'll see the init. (The next iso will delete the init via the bootscripts). That's the same init that's packaged into the initramfs and that the kernel runs after it's unpacked the initramfs to memory. When my init is done setting up the filesystem in the initramfs and mounting the cd/symlinking dirs, it finally spawns a new process: /.cdrom/sbin/init, which is the real sysvinit. In my cd '/' *is* the initramfs. Which is why I need to remind people *not* to do silly stuff like unpack sources in /root.
Ahh, I see, that is different then. How do you keep the kernel from trying to mount a root filesystem (forgive me for asking the obvious, I haven't looked at the details)?
--
http://linuxfromscratch.org/mailman/listinfo/livecd
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
