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 22.214.171.124-170.2.56.fc10.x86_64 to 126.96.36.199-170.2.68.fc10.x86_64.
After rebooting Server its always boot from kernel-188.8.131.52-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-184.108.40.206-170.2.68.fc10.x86_64. Even then it boot from older kernel 220.127.116.11-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-18.104.22.168-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
On Demand NOW
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.View Now!
|Chrome-Colored Parakeets||May 05, 2015|
|Mumblehard--Let's End Its Five-Year Reign||May 04, 2015|
|An Easy Way to Pay for Journalism, Music and Everything Else We Like||May 04, 2015|
|When Official Debian Support Ends, Who Will Save You?||May 01, 2015|
|May 2015 Issue of Linux Journal: Cool Projects||May 01, 2015|
|May 2015 Video Preview||May 01, 2015|
- Chrome-Colored Parakeets
- Mumblehard--Let's End Its Five-Year Reign
- An Easy Way to Pay for Journalism, Music and Everything Else We Like
- When Official Debian Support Ends, Who Will Save You?
- Ubuntu Ditches Upstart
- "No Reboot" Kernel Patching - And Why You Should Care
- Video On Demand: 8 Signs You're Beyond Cron
- DevOps: Better Than the Sum of Its Parts
- Picking Out the Nouns
- Return of the Mac