Re: How to tell what kernel is running?
From: Andy Fraser (andyfraser31_at_hotmail.com)
Date: 04/04/04
- Next message: Guest: "Re: Linux locking on boot"
- Previous message: Ook: "Re: How to tell what kernel is running?"
- In reply to: Ook: "Re: How to tell what kernel is running?"
- Next in thread: Erik de Castro Lopo: "Re: How to tell what kernel is running?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sun, 04 Apr 2004 17:03:22 +0100
In alt.os.linux, Ook uttered these immortal words:
> Slackware. I downloaded the 2.6.4 source from www.kernel.org. Compiled it.
> copied bzImage to /boot/vmlinuz-2.6.4. Changed symbolic link vmlinuz to
> point to this file. Copied System.map to /boot/System.map-2.6.4. Changed
> symbolic link System.map to point to this file. I figured since the links
> were changed to point to the new files, I didn't need to do anything to
> boot loader config.
As Chris said, you haven't re-run lilo to update your system. LILO stores
the actual disk position of the kernel so until you re-run lilo it'll still
be pointing to your old kernel.
I don't mean to sound harsh here but had you read up on LILO first you
wouldn't have needed to ask a question here. Just assuming that doing
something will work is the quickest way to tie yourself in knots and give
yourself a headache.
> I just now got rid of the symbolic links, and replaced them with the
> actual 2.6.4 files. Reboot. It still comes up as 2.4.22. At this point I'm
> guessing that there is more to upgrading the kernel then replacing the
> vmlinuz and System.map files. I've read instructions on two different
> websites, and this is (more-or-less) what they say to do. The lilo.conf
> points to vmlinuz, btw. At this point I'm going to bed - tomorrow is
> another day, and maybe I can figure it out when I have more brain cells
> :-)
I have 2 stanzas in my lilo.conf. The old, known to work kernel is symlinked
to /vmlinuz.old and I refer to this in a stanza called "Rescue". The new
kernel is symlinked to /vmlinuz and is referred to by a stanza labelled
"Debian". Then I just change my symlinks when I upgrade and re-run lilo. If
the new kernel fails I can reboot my old kernel using Rescue.
I'm only mentioning this just in case your new kernel doesn't work. It's
happened to me in the past and having a quick and easy way to get back to a
working system is a plus.
-- Andy.
- Next message: Guest: "Re: Linux locking on boot"
- Previous message: Ook: "Re: How to tell what kernel is running?"
- In reply to: Ook: "Re: How to tell what kernel is running?"
- Next in thread: Erik de Castro Lopo: "Re: How to tell what kernel is running?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|