Gentoo + GRUB help

[vash]

I'm a bit new to GRUB, but I'm much more familiar with LILO. Here goes.

I wanted ALSA support, so after reading the forums, it was recommended to install the sound support as a module and let ALSA handle it. Unfortunately, I already compiled support for my SBLive into the kernel. Go back , recompile the kernel, and now I have a new image.

With lilo, I copy the bzImage over, rerun lilo and I'm off with my new kernel when I reboot. With GRUB + Gentoo, I cannot find the previous kernel I already made (2x of them). So, now I'm stuck with a new kernel, that I have no idea where to load. Also, I went looking for the menu.lst (that I created at boottime) and its nowhere on the disk (I'm also searching as root, if that helps any).

If anyone can point me in the right direction, I'd appreciate it.

vash

 

[Chaotic42]

Do you just copy it over like

cp arch/i386/boot/bzImage /boot/

If so, you're just overwriting the previous ones everytime. When I have multiple versions of the same kernel, I name them like this

linux-2.4.18
linux-2.4.18-1
linux-2.4.18-2

You can give them any name you want.

menu.lst should be in /boot/grub.

 

[vash]

Well, figured it out from help on the Gentoo forums. It seems like the /boot isn't mounted at boot time, so I had to mount /boot in order to see the correct files. As soon as mounted /boot, I could access the files in the folder and replace what I needed.

vash

 

[Chaotic42]

Originally posted by: vash
Well, figured it out from help on the Gentoo forums. It seems like the /boot isn't mounted at boot time, so I had to mount /boot in order to see the correct files. As soon as mounted /boot, I could access the files in the folder and replace what I needed.

vash

Hmm, that's odd.

Defeats the whole purpose 🙂

Congrats.

 

[Tiger]

/boot is actually mounted read only. It gets read at boot but you can't write to it with out mounting and chrooting into it.
It's not spelled out too well in the docs.