[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

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



On Mon, Sep 14, 2009 at 01:39:29PM +0100, Ben Hutchings wrote:
> On Fri, 2009-09-11 at 14:09 +0100, Martin Michlmayr wrote:
> > * Ben Hutchings <ben@decadent.org.uk> [2009-09-10 01:22]:
> > > > > 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.  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 the mips config, so that's fine.
> > 
> > I noticed that some i386 floppy images use ext2, but I've no idea
> > how the floppy images work.
> > 
> > i386/floppy/net-drivers-1.cfg:INITRD_FS=ext2
> > i386/floppy/net-drivers-3.cfg:INITRD_FS = ext2
> > i386/floppy/cd-drivers.cfg:INITRD_FS=ext2
> > i386/floppy/net-drivers-2.cfg:INITRD_FS = ext2
> 
> Is installation from floppies still supported?  If so, can they be
> converted to using initramfs?

Actually, I don't see how this can work today since ext2 is a module...
Has anyone tested that these work in lenny?

Ben.

-- 
Ben Hutchings
I say we take off; nuke the site from orbit.  It's the only way to be sure.


Reply to: