Kernel not booting from grub.conf
I have a New 64bit fedora 10 remote dedicated box from Hosting Company. I have updated its kernel from 126.96.36.199-170.2.56.fc10.x86_64 to 188.8.131.52-170.2.68.fc10.x86_64.
After rebooting Server its always boot from kernel-184.108.40.206-170.2.56.fc10.x86_64. It totally ignore the sequence of kernel booting defined in grub.conf. i have commented all older kernel entries in grub.conf except New one-220.127.116.11-170.2.68.fc10.x86_64. Even then it boot from older kernel 18.104.22.168-170.2.56.fc10.x86_64.
For information i have not installed lilo. Can anyone tell why and how server is booting from a specific kernel and not entertaining grub.conf.
I have checked the booting logs, server simply boot from kernel-22.214.171.124-170.2.56.fc10.x86_64 and not errors in logs. can someone tell me whats going on with my box.
|September 2015 Issue of Linux Journal: HOW-TOs||Sep 01, 2015|
|September 2015 Video Preview||Sep 01, 2015|
|Using tshark to Watch and Inspect Network Traffic||Aug 31, 2015|
|Where's That Pesky Hidden Word?||Aug 28, 2015|
|A Project to Guarantee Better Security for Open-Source Projects||Aug 27, 2015|
|Concerning Containers' Connections: on Docker Networking||Aug 26, 2015|
- Using tshark to Watch and Inspect Network Traffic
- September 2015 Issue of Linux Journal: HOW-TOs
- Concerning Containers' Connections: on Docker Networking
- Problems with Ubuntu's Software Center and How Canonical Plans to Fix Them
- Firefox Security Exploit Targets Linux Users and Web Developers
- Where's That Pesky Hidden Word?
- A Project to Guarantee Better Security for Open-Source Projects
- Build a “Virtual SuperComputer” with Process Virtualization
- My Network Go-Bag
- Doing Astronomy with Python