Am Sonntag, 6. Juli 2008 schrieb Matthew R. Lee:

> > > >>> [grub.conf]
> > > >>> default 0
> > > >>>
> > > >>> timeout 30
> > > >>>
> > > >>> splashimage=(hd0,0)/boot/grub/splash.xpm.gz
> > > >>>
> > > >>> title=Gentoo 2.6.22-r2
> > > >>>
> > > >>> root (hd0,0)
> > > >>> kernel /boot/kernel-2.6.22-r2-2 root=/dev/sda3
> > > >>> video=vesafb:mtrr,ywrap,1280x800-24@70
> > > >>>
> > > >>> title=Gentoo 2.6.24-r8
> > > >>>
> > > >>> root (hd0,0)
> > > >>> kernel /boot/kernel-2.6.24-r8 root=/dev/sda3
> > > >>> video=vesafb:mtrr,ywrap,1280x800-24@70
>
> Ok,
> I figured out the problem, but no why it's happened. If you look at the
> output of ls -la /boot there is another folder /boot and within this a
> symlink /boot (./) By copying the kernel to this folder and modifiying the
> grub.conf in the associated /grub folder the the new kernel boots.
> Question is how did I come to have a cascade of boot folders and how do I
> get things back the way they should be?

Don't know how you got there, but to get things back to normal you should 
remove /boot/boot and make it a symlink to /boot:

cd /boot
rm -rf boot
ln -s . boot

I would also revise grub.conf a bit:

default 0
timeout 30
root (hd0,0)
splashimage=/grub/splash.xpm.gz

title=Gentoo 2.6.22-r2
	kernel /kernel-2.6.22-r2 root=/dev/sda3 
video=vesafb:mtrr,ywrap,1280x800-24@70  <- On one line, of course

title=Gentoo 2.6.24-r8
	kernel /kernel-2.6.24-r8 root=/dev/sda3 
video=vesafb:mtrr,ywrap,1280x800-24@70

Optionally, you could also reinstall grub to your MBR, by running grub (or was 
it grub-shell?) and issue the following commands:

root (hd0,0)
setup (hd0)

HTH...

	Dirk