Just beware that the initrd may have to fit on an emergency boot floppy!
Otherwise, it can be almost as big as your ram (at least I don't think
there are any limitations on the size of a boot-time ram disk).
Brian Boerner wrote:
>
> Is it possible to change the image size of an initrd?
>
> /sbin/mkinitrd snipet...
> if [ `uname -m` = "ia64" ]; then
> IMAGESIZE=3000
> else
> IMAGESIZE=1500
> fi
>
> Later on they do a:
> dd if=/dev/zero of=$IMAGE bs=1k count=$IMAGESIZE 2> /dev/null
>
> And then finally make the filesystem.
> echo y | mke2fs $LODEV $IMAGESIZE >/dev/null 2>/dev/null
>
> I didn't see anything in the documentation about this,
> but I'm wondering if anyone knows if there are size
> limitations on the device.
>
> I'm trying to debug a module I wrote that is having
> problems on a particular server. I've taken it as
> far as I can with oops, ksymoops and kernel prints.
>
> At this point I don't trust that the print buffer is
> being flushed because the function it is dying in
> doesn't do a whole lot and I've verified the pointers,
> etc.
>
> If I can get the initrd size increased, I can load
> the modules and boot kgdb and poke around. Otherwise
> the modules are to large for the filesystem and the
> system obviously doesn't want to boot.
>
> Any suggestions?
>
> Thanks Folks...
> -bmb-
>
> **********************************************************
> To unsubscribe from this list, send mail to
> [EMAIL PROTECTED] with the following text in the
> *body* (*not* the subject line) of the letter:
> unsubscribe gnhlug
> **********************************************************
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
