'You are running an insecure kernel (2.4.20-my previous version). You should upgrade to a newer version as soon as possible to avoid your system being compromised. https://rhn.redhat.com/errata/RHSA-2003-417.html' :confused:
Anyway I did this to update :
1. ssh as root
2. wget ftp://updates.redhat.com/7.3/en/os/i686/k...0-28.7.i686.rpm
3. rpm -ivh -2.4.20-28.7.i686.rpm
4. pico /etc/lilo.conf
change my lilo.conf to,
prompt
timeout=50
default=2.4.20-28.7 <-- only changed this
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
message=/boot/message
lba32
image=/boot/vmlinuz-2.4.18-27.7.x
label=linux.bak
root=/dev/hda2
read-only
initrd=/boot/initrd-2.4.18-27.7.x.img
append="ide0=ata66 ide1=ata66 ide0=autotune ide1=autotune hda=autotune hdb=autotune hdc=autotune"
image=/boot/vmlinuz-2.4.20-18.7
label=linux.bak1
root=/dev/hda2
append="ide0=ata66 ide1=ata66 ide0=autotune ide1=autotune hda=autotune hdb=autotune hdc=autotune"
read-only
initrd=/boot/initrd-2.4.20-18.7.img
image=/boot/vmlinuz-2.4.20-27.7
label=linux
root=/dev/hda2
append="ide0=ata66 ide1=ata66 ide0=autotune ide1=autotune hda=autotune hdb=autotune hdc=autotune"
read-only
initrd=/boot/initrd-2.4.20-27.7.img
5. lilo -v -v
shown as,
Reading boot sector from /dev/hda
Merging with /boot/boot.b
Secondary loader: 11 sectors.
Mapping message file /boot/message
Message: 0 sectors.
Boot image: /boot/vmlinuz-2.4.18-27.7.x
Setup length is 10 sectors.
Mapped 0 sectors.
Mapping RAM disk /boot/initrd-2.4.18-27.7.x.img
RAM disk: 0 sectors.
Added linux.bak
Boot image: /boot/vmlinuz-2.4.20-18.7
Setup length is 10 sectors.
Mapped 0 sectors.
Mapping RAM disk /boot/initrd-2.4.20-18.7.img
RAM disk: 0 sectors.
Added linux.bak1
Boot image: /boot/vmlinuz-2.4.20-27.7
Setup length is 10 sectors.
Mapped 0 sectors.
Mapping RAM disk /boot/initrd-2.4.20-27.7.img
RAM disk: 0 sectors.
Added linux
Fatal: No images have been defined.
Removed temporary file /boot/map~
6. Reboot
Previously when I did the updating... it works finely...
Full Version: i have updated my kernel but why WHM still showing...
you set your "Default" to a label that doesn't exist. You can't book an image that's not defined.
QUOTE
Originally posted by LighthousePoint
you set your "Default" to a label that doesn't exist. You can't book an image that's not defined.
you set your "Default" to a label that doesn't exist. You can't book an image that's not defined.
ermm u mean this line?
default=2.4.20-28.7
yeah, there's no corresponding label for that.
In your lilo.conf, you've got 3 labels:
label=linux.bak
label=linux.bak1
label=linux
Your default should point to one of these.
However, in your case, none of your labels are the latest kernel.
You need to add this to the bottom of lilo.conf:
image=/boot/vmlinuz-2.4.20-28.7
label=2.4.20-28.7
root=/dev/hda2
append="ide0=ata66 ide1=ata66 ide0=autotune ide1=autotune hda=autotune hdb=autotune hdc=autotune"
read-only
initrd=/boot/initrd-2.4.20-28.7.img
You default can then point to this label like it's doing now:
default=2.4.20-28.7
And save your lilo.conf.
Or you can label that linux, relabel current linux to linuxbak2 or something, to make it neater.
Then run lilo -v -v again - an * should show up next to 2.4.20-28.7 (hopefully). If so, reboot then.
label=linux.bak
label=linux.bak1
label=linux
Your default should point to one of these.
However, in your case, none of your labels are the latest kernel.
You need to add this to the bottom of lilo.conf:
image=/boot/vmlinuz-2.4.20-28.7
label=2.4.20-28.7
root=/dev/hda2
append="ide0=ata66 ide1=ata66 ide0=autotune ide1=autotune hda=autotune hdb=autotune hdc=autotune"
read-only
initrd=/boot/initrd-2.4.20-28.7.img
You default can then point to this label like it's doing now:
default=2.4.20-28.7
And save your lilo.conf.
Or you can label that linux, relabel current linux to linuxbak2 or something, to make it neater.
Then run lilo -v -v again - an * should show up next to 2.4.20-28.7 (hopefully). If so, reboot then.
Of course, make sure the newest kernel, /boot/initrd-2.4.20-28.7.img, is actually installed first!
QUOTE
Originally posted by Erwin
In your lilo.conf, you've got 3 labels:
label=linux.bak
label=linux.bak1
label=linux
Your default should point to one of these.
However, in your case, none of your labels are the latest kernel. You need to add this to the bottom of lilo.conf:
image=/boot/vmlinuz-2.4.20-28.7
label=2.4.20-28.7
root=/dev/hda2
append="ide0=ata66 ide1=ata66 ide0=autotune ide1=autotune hda=autotune hdb=autotune hdc=autotune"
read-only
initrd=/boot/initrd-2.4.20-28.7.img
You default can then point to this label like it's doing now:
default=2.4.20-28.7
And save your lilo.conf.
Or you can label that linux, relabel current linux to linuxbak2 or something, to make it neater.
Then run lilo -v -v again - an * should show up next to 2.4.20-28.7 (hopefully). If so, reboot then.
In your lilo.conf, you've got 3 labels:
label=linux.bak
label=linux.bak1
label=linux
Your default should point to one of these.
However, in your case, none of your labels are the latest kernel.
You need to add this to the bottom of lilo.conf:
image=/boot/vmlinuz-2.4.20-28.7
label=2.4.20-28.7
root=/dev/hda2
append="ide0=ata66 ide1=ata66 ide0=autotune ide1=autotune hda=autotune hdb=autotune hdc=autotune"
read-only
initrd=/boot/initrd-2.4.20-28.7.img
You default can then point to this label like it's doing now:
default=2.4.20-28.7
And save your lilo.conf.
Or you can label that linux, relabel current linux to linuxbak2 or something, to make it neater.
Then run lilo -v -v again - an * should show up next to 2.4.20-28.7 (hopefully). If so, reboot then.
Thanks Erwin
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.