whoops, forgot a couple questions. first, in init/initramfs.c, note
the unpacking of the initrd images near the bottom of that source
file:
static int __init populate_rootfs(void)
{
char *err = unpack_to_rootfs(__initramfs_start,
__initramfs_end - __initramfs_start, 0);
if (err)
panic(err);
#ifdef CONFIG_BLK_DEV_INITRD
if (initrd_start) {
#ifdef CONFIG_BLK_DEV_RAM
int fd;
printk(KERN_INFO "checking if image is initramfs...");
err = unpack_to_rootfs((char *)initrd_start,
initrd_end - initrd_start, 1);
if (!err) {
printk(" it is\n");
unpack_to_rootfs((char *)initrd_start,
initrd_end - initrd_start, 0);
free_initrd();
return 0;
...
note first the unpacking of the in-kernel cpio-format initrd,
followed by (if it exists) the similar unpacking of the *external*
initrd supplied by the bootloader. if that external initrd image
exists, does it *replace* the in-kernel initrd content, or is it
*added* to it? i'm trying to figure that out from RTFS, but TFS is
less than clear.
and, second, how can i retain the cpio-format initrd? i've tested
the boot-time "retain_initrd" option but it doesn't appear to apply to
the cpio-format initrd's. is there another boot-time option for that?
i dimly recall an option that would leave the initrd content under a
top-level /initrd directory for later perusal. hints?
rday
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
http://crashcourse.ca
========================================================================
--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to [EMAIL PROTECTED]
Please read the FAQ at http://kernelnewbies.org/FAQ
