> Ok, it's at this point that I'm completely baffled as to what to do
> next. In my root directory, I now have the two files vmlinuz, and
> System.map. I know that both of these files need to be linked up to the
> lilo configuration, so the system can boot to them. When I look in the
> /boot directory, I see a symlink called System.map pointing to the
> System.map for the current kernel. I also see ones for vmlinuz and
> modules. Now, I've been warned in the past that you don;t just blindly
> replace stuff, as the new kernel may not boot.
>
> What is the exact sequence of steps to set up this new kernel in a test
> position, so that I don;t disturb the original kernel, and can get back
> to it? What files, symlinks, etc. need to be changed? Red Hat apparently
> has their reasons for setting up the system the way that they do. When I
> first started with linux, and recompiling a kernel, there were never any
> symlinks to deal with. You simply added an entry into lilo.conf, and told
> it where to find the new kernel.
You have to add your new kernel to /etc/lilo.conf, and then run:
/sbin/lilo
You can leave the current kernel as default, so that you boot the new kernel
only by explicitly selecting it in the LILO propmpt.
And leave the symlinks as they are, and in lilo.conf reference the new kernel
file (vmlinuz-x.x.xx-x)
This is my lilo.conf with the RH6.1 kernel, a custom kernel (RSMovil), and NT
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
default=linux
image=/boot/vmlinuz-2.2.12-20
label=linux
initrd=/boot/initrd-2.2.12-20.img
read-only
root=/dev/hda8
image=/vmlinuz-RSMovil
label=RSMovil
initrd=/initrd-RSMovil.img
read-only
root=/dev/hda8
other=/dev/hda1
label=nt
칻 &ޙajbު笶\l"ry-n7
