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 188.8.131.52-170.2.56.fc10.x86_64 to 184.108.40.206-170.2.68.fc10.x86_64.
After rebooting Server its always boot from kernel-220.127.116.11-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-18.104.22.168-170.2.68.fc10.x86_64. Even then it boot from older kernel 22.214.171.124-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-126.96.36.199-170.2.56.fc10.x86_64 and not errors in logs. can someone tell me whats going on with my box.
Getting Started with DevOps - Including New Data on IT Performance from Puppet Labs 2015 State of DevOps Report
August 27, 2015
12:00 PM CDT
DevOps represents a profound change from the way most IT departments have traditionally worked: from siloed teams and high-anxiety releases to everyone collaborating on uneventful and more frequent releases of higher-quality code. It doesn't matter how large or small an organization is, or even whether it's historically slow moving or risk averse — there are ways to adopt DevOps sanely, and get measurable results in just weeks.
Free to Linux Journal readers.Register Now!
- Hacking a Safe with Bash
- Django Models and Migrations
- Secure Server Deployments in Hostile Territory, Part II
- Huge Package Overhaul for Debian and Ubuntu
- Home Automation with Raspberry Pi
- The Controversy Behind Canonical's Intellectual Property Policy
- Shashlik - a Tasty New Android Simulator
- Embed Linux in Monitoring and Control Systems
- KDE Reveals Plasma Mobile
- diff -u: What's New in Kernel Development