Re: initrd hell

Monkey Pet wrote:

> I have been running xebian 1.1.4.  Booting off a xromwell loader with 
> a xbox that's been sofmodded.  All seems well.  I am using the fatx 
> loopback install on E.
>
> However, now I want to upgrade the kernel. 
>
> I have been using the following procedure:
> 1.  Compile install kernel with patches applied and using the 
> /boot/config-2.4.xx file.
> 2.  Copy kernel to E overwriting vmlinuz.
> 3.  Mount initrd and  cp -r files into a different directory.

It might be better to use cp -a to make sure the file properties are 
properly preserved.

> 4.  also cp the new loop.o module into the the dir.
> 5.  run mkinitrd

If you want to base the new initrd on the old one why are you running 
mkinitrd? From the man page of mkinitrd

"The mkinitrd script constructs a directory structure that can serve as
an initrd root file system. It then generates an image containing that
directory structure using mkcramfs"

You've already got the directory structure in place since you've copied 
it from the old initrd. Therefore all you need to do is run mkcramfs on 
the directory you've copied everything to.

> 6.  copy over the new initrd to E overwriting the old one.
> 7.  Reboot into the new kernel.
>
> I am suspecting that I am missing a step that is causing the bootup to 
> fail in particular the initrd creation steps.  I see the correct 
> kernel booting up and the initrd being loaded, the the bootup process 
> fails.

Richard


-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. 
Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php