Re: Compiling 2.6 kernel questions

Hi,

>> Hmm... Are you saying here that it can't be loaded as a module, but
>> instead must be compiled into the kernel?
>
> Whichever filesystem initrd itself uses has to be built-in (otherwise
> you get the chicken-and-egg problem), but this can be e.g. cramfs; it
> doesn't need to be writable, or support ownership, permissions, links,
> etc.

So if I get a VFS error along the lines of "VFS: Can't mount root
unknown-block(9,1)" and it panics, what could the cause be?

I realize this is /dev/md1, and I've built the initrd with md-mod and
sata_nv, and ext3 is built in, but it's almost like it's ignoring the
linuxrc in the initrd. If I chroot to it and run /bin/nash /linuxrc,
it does print my echo statements.

How can I debug this or capture the full output to analyze?

Thanks again,
Alex