Re: Debian-installer use of initrd (was Re: CONFIG_BLK_DEV_RAM=y)

2009-09-11 Thread Martin Michlmayr
ded by debian-installer, but that doesn't > > seem to be the case any more. If it's not, I'll change it to a module. > > Given the lack of response, I'm assuming this is OK to change. mips still uses an initrd for d-i but it sets CONFIG_BLK_DEV_RAM=y explicitly in

Re: Debian-installer use of initrd (was Re: CONFIG_BLK_DEV_RAM=y)

2009-09-09 Thread Ben Hutchings
On Sun, 2009-09-06 at 19:03 +0100, Ben Hutchings wrote: > Marco d'Itri wrote: > > Why? The /dev/ram* devices are not needed anymore for the early boot > > with 2.6 kernels, unless there is something fundamental I am missing > > this driver should become modular. > > Apparently it used to be needed

Debian-installer use of initrd (was Re: CONFIG_BLK_DEV_RAM=y)

2009-09-06 Thread Ben Hutchings
Marco d'Itri wrote: > Why? The /dev/ram* devices are not needed anymore for the early boot > with 2.6 kernels, unless there is something fundamental I am missing > this driver should become modular. Apparently it used to be needed by debian-installer, but that doesn't seem to be the case any more.

CONFIG_BLK_DEV_RAM=y

2009-09-04 Thread Marco d'Itri
Why? The /dev/ram* devices are not needed anymore for the early boot with 2.6 kernels, unless there is something fundamental I am missing this driver should become modular. -- ciao, Marco -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Troubl