Lately, we installed additional memory on our Debian (lenny) servers and installed ‘bigmem’ kernel for our 32-bit systems to recognize more than 3GB of ram. Bigmem kernel installations went fine on servers with Grub as their boot loader – most of them uses Grub. But on one machine with Lilo as boot loader, it didn’t boot on bigmem kernel and below was the entry on /etc/lilo.conf.
# Boot up Linux by default.
default=Linux
image=/vmlinuz
label=Linux
read-only
# restricted
# alias=1
initrd=/initrd.imgimage=/vmlinuz.old
label=LinuxOLD
read-only
optional
# restricted
# alias=2
initrd=/initrd.img.old
From this config I don’t see the details of which kernel is the old one and the bigmem. I also tried to set the default to kernel with “LinuxOLD” label but it points to the same kernel (not the bigmem). I solved my problem by modifying the /etc/lilo.conf config as follows:
# image=/vmlinuz
image=/boot/vmlinuz-2.6.26-2-686-bigmem
initrd=/boot/initrd.img-2.6.26-2-686-bigmem
label=Linux
read-only
# restricted
# alias=1
#initrd=/initrd.img
NOTE: Don’t forget to test first your changes on the /etc/lilo.conf by running ‘lilo’ command – this will verify your changes.
Random Posts
- 03/01/2010 -- What’s Mean "TCP: Treason uncloaked! Peer..shrinks window..Repaired." (0)
- 06/25/2009 -- Security Tips for Apache Server Configuration (0)
- 08/06/2009 -- JetAudio 7.1.9.4030 Universal Stack Overflow Exploit (0)
- 03/02/2010 -- Iptables ip_conntrack table set-up and tunning for high load UDP traffic (0)
- 06/11/2009 -- Apple MACOS X xnu <= 1228.9.59 Local Kernel Root Exploit (0)
- 06/02/2009 -- Microsoft ads say search is sick, Bing is the cure (0)
- 06/01/2009 -- Google giving small businesses local search data (0)
- 03/06/2010 -- Google offer free DNS service (1)
- 05/28/2011 -- sniffer tools example – 1 (0)
- 12/29/2008 -- Analysis access logs of Nginx by awstats (10)
