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 184.108.40.206-170.2.56.fc10.x86_64 to 220.127.116.11-170.2.68.fc10.x86_64.
After rebooting Server its always boot from kernel-18.104.22.168-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-22.214.171.124-170.2.68.fc10.x86_64. Even then it boot from older kernel 126.96.36.199-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-188.8.131.52-170.2.56.fc10.x86_64 and not errors in logs. can someone tell me whats going on with my box.
Webinar: 8 Signs You’re Beyond Cron
11am CDT, April 29th
Join Linux Journal and Pat Cameron, Director of Automation Technology at HelpSystems, as they discuss the eight primary advantages of moving beyond cron job scheduling. In this webinar, you’ll learn about integrating cron with an enterprise scheduler.Join us!
- New Products
- Users, Permissions and Multitenant Sites
- Not So Dynamic Updates
- Flexible Access Control with Squid Proxy
- Security in Three Ds: Detect, Decide and Deny
- DevOps: Everything You Need to Know
- Tighten Up SSH
- Solving ODEs on Linux
- Non-Linux FOSS: MenuMeters
- diff -u: What's New in Kernel Development