1. "uname -a" usually gives you accurate information on what kernel is running.
2. In my experience, when I compile a new kernel, I find I have to edit
/etc/lilo.conf by hand to get it to be the default. This despite the fact
that the installation script (I use Debian - there is no "Linux 7.0", and I
can't tell from that designation which of several distributions you ctually
use) claims it is taking care of this step for me.
3. I customarily follow a longer series of steps in compiling kernels, which
you can find in the kernel documentation. I'm not sure which of them the
command "make bzlilo" encapsulates, since I don't usually do it that way,
but you might check to make sure you are doing all the needed steps
(compiling the kernel itself, installing the kernel, compiling modules,
installing modules, modifying /etc/lilo.conf, and running lilo).
At 01:45 PM 5/28/01 +0530, nomit kalidhar wrote:
>I had installed Linux 7.0 kernel 2.2.16-22.
>Then i had done the following to upgrade the kernel to 2.4
>
>>cd /usr/src
>>tar -zxvf linux-2.4.0-test11.tar.gz
>>make dep ; make clean ; make bzlilo
>
>then rebooted the machine. All the operations performed above were done
>without showing any error messages.
>On seeing the kernel version it still shows 2.2.16-22.
>How can i verify whether the new kernel is installed.
--
------------------------------------"Never tell me the odds!"---
Ray Olszewski -- Han Solo
Palo Alto, CA [EMAIL PROTECTED]
----------------------------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.linux-learn.org/faqs
