Re: [2.6.24-rc5-mm1] Why CONFIG_BLK_DEV_RAM=m makes \\\"#ifdefCONFIG_BLK_DEV_RAM\\\" false?

[Jan Engelhardt]

On Dec 14 2007 15:15, Tetsuo Handa wrote:
>Hello.
>
>Randy Dunlap <randy.dunlap@xxxxxxxxxx> wrote:
>> I don't think that this is a change from the recent past.
>
>Oh, it is my mistake.
>
>I found that choosing CONFIG_BLK_DEV_RAM=m makes
>impossible to pass an initrd image since
>populate_rootfs() in init/initramfs.c omits
>code for checking whether the image is an initrd or not.

I believe it is (also?) due to /dev/ram0 not being available
where the initrd usually gets copied into.

initramfs continues to work, and that is what should I think
should be used for any new projects.

>But I didn't know CONFIG_BLK_DEV_RAM is tristate.
>So, I have to change to CONFIG_BLK_DEV_RAM=y when
>I want to pass an initrd image after "make allmodconfig".
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/