examining initrd contents

[Robert P. J. Day]

On 11 Sep 2003, Ben Hsu wrote:

> Hi.
> 
> I just compiled 2.6.0-test5 and found that the initrd was > 2x bigger
> than it was in test4. In fact I had to tweak /sbin/mkinitrd as it was
> running out of space when making it. I am curious about this and want to
> examine the contents of the test5 initrd. How would I go about it?
> I tried "mount -o loop /boot/initrd-2.6.0-test5.img /tmp/loop0" but it
> hangs

it's a gzipped file.  do something like

  $ gunzip -c <image file> > outfile

the outfile should be a mountable filesystem.

rday

p.s.  all from memory.