Booting from a different kernel image
silve...@my-deja.com
Can we specify which boot image to be used at LILO Prompt?
Thanks in advance
Sandy
Sent via Deja.com http://www.deja.com/
Before you buy.
Akira Yamanita
>
> Hi,
> Can we specify which boot image to be used at LILO Prompt?
> Thanks in advance
>
> Sandy
Sure. This is my /etc/lilo.conf file. Edit as necessary but you
should get the general idea. Basically you compile the new kernel,
move it to your boot (or root) partition, then add an entry for
the new kernel.
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
default=linux
image=/boot/vmlinuz-2.2.12-20
label=old_kernel
initrd=/boot/initrd-2.2.12-20.img
read-only
root=/dev/hda8
image=/boot/vmlinuz-2.2.16
label=linux
initrd=/boot/initrd-2.2.16.img
read-only
root=/dev/hda8
Akira Yamanita
>
> Hi,
> Can we specify which boot image to be used at LILO Prompt?
> Thanks in advance
>
> Sandy
Sure. This is my /etc/lilo.conf file. Edit as necessary but you
should get the general idea. Basically you compile the new kernel,
move it to your boot (or root) partition, then add an entry for
the new kernel. At the LILO prompt, I type either "old_kernel" or
"linux". The default, if I don't choose one, is "linux" as defined
by the "label=" line.
silve...@my-deja.com
image location in lilo.conf , but I know where the image is. Can I still
make the Lilo boot from the kernel that I wish.
I am NOT updating Lilo. It has to be a load time parameter
SSS
In article <39981575...@bigfoot.com>,
Akira Yamanita
>
> Can I specify the kernel at the time of Lilo prompt. i didn't give the
> image location in lilo.conf , but I know where the image is. Can I still
> make the Lilo boot from the kernel that I wish.
> I am NOT updating Lilo. It has to be a load time parameter
> SSS
hmm.. not that I know of. You can pass kernel parameters to LILO
but AFAIK, you can't specify the kernel itself without writing
the configuration. Is there a reason why you don't want to or
can't run lilo with a new configuration? I'm just curious to
know what that is.
Peter Mitchell
kernel in the parameters.
The other problem (which applies with lilo and loadlin) is
if the modules don't match the kernel, eg different
versions. I don't know what is the best way to handle this.
* Sent from AltaVista http://www.altavista.com Where you can also find related Web Pages, Images, Audios, Videos, News, and Shopping. Smart is Beautiful
jinp
did all the lilo and link the System.map to the new file, and new kernel
booted ok, but the old one found a wrong System.map file. What should
I do?
Thanks
James
Akira Yamanita wrote:
> silve...@my-deja.com wrote:
> >
> > Hi,
> > Can we specify which boot image to be used at LILO Prompt?
> > Thanks in advance
> >
> > Sandy
>
> Sure. This is my /etc/lilo.conf file. Edit as necessary but you
> should get the general idea. Basically you compile the new kernel,
> move it to your boot (or root) partition, then add an entry for
> the new kernel.
>
Dances With Crows
>I have a question on this one, I built a new kernel(on RedHat 6.0) and
>did all the lilo and link the System.map to the new file, and new kernel
>booted ok, but the old one found a wrong System.map file. What should
>I do?
"Don't worry about it" is my advice. System.map is used mainly to aid
in debugging kernel problems. There's one user-space program that I
know of (lsof) that uses System.map to do its thing, but in the main,
System.map isn't used.
--
Matt G|There is no Darkness in Eternity/But only Light too dim for us to see
Brainbench MVP for Linux Admin / Those who do not understand Unix are
http://www.brainbench.com / condemned to reinvent it, poorly.
-----------------------------/ --Henry Spencer
Jonathan
jinp <ji...@erols.com> wrote:
> I have a question on this one, I built a new kernel(on RedHat 6.0) and
> did all the lilo and link the System.map to the new file, and new
kernel
> booted ok, but the old one found a wrong System.map file. What should
> I do?
>
Just to shut the errors up I cp /usr/src/linux/arch/i386/boot/System.map
/boot