> file /boot/initrd-2.4.20-pel.img ... Success! Thank you: $ gzip -dc ... ... $ $ ls -l /boot/initrd-2.5.73-pel.img initrd-2.5.73-pel.img -rw-r--r-- 1 root root 85611 Jun 25 07:13 /boot/initrd-2.5.73-pel.img -rw-rw-r-- 1 pat pat 3072000 Jun 25 09:54 initrd-2.5.73-pel.img $ $ file /boot/initrd-2.5.73-pel.img initrd-2.5.73-pel.img /boot/initrd-2.5.73-pel.img: gzip compressed data, from Unix, max compression initrd-2.5.73-pel.img: Linux rev 1.0 ext2 filesystem data $ > let me try to summarize ... Thank you. I think I followed all you said up to: "- This explains why installing a new kernel does not always cause a panic. If the new kernel needs initrd, and it is built using /sbin/mkinitrd, then nash is available on the initrd image. It does the label-to-device conversion." "- Instead, if the new kernel does not need initrd (i.e. it has all the needed drivers built in), converting a label to device major/minor does not happen." Possibly I'm most lost in how I go about determining if a particular kernel of mine does or "does not need initrd". My kernels that panic over root=LABEL=/ and my kernels that work both have an initrd*img. As yet I'm presuming those are all constructed by /sbin/mkinitrd. Pat LaVarre __________________________________ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
