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.
One Click, Universal Protection: Implementing Centralized Security Policies on Linux Systems
Join editor Bill Childers and Bit9's Paul Riegle on April 27 at 12pm Central to learn how to keep your Linux systems secure.
Free to Linux Journal readers.Register Now!
|Security Hardening with Ansible||Aug 18, 2014|
|Monitoring Android Traffic with Wireshark||Aug 14, 2014|
|IndieBox: for Gamers Who Miss Boxes!||Aug 13, 2014|
|Non-Linux FOSS: a Virtualized Cisco Infrastructure?||Aug 11, 2014|
|Linux Security Threats on the Rise||Aug 08, 2014|
|Android Candy: Oyster—Netflix for Books!||Aug 07, 2014|
- Security Hardening with Ansible
- NSA: Linux Journal is an "extremist forum" and its readers get flagged for extra surveillance
- Why Python?
- Returning Values from Bash Functions
- Monitoring Android Traffic with Wireshark
- Text Manipulation with sed
- Booting the Kernel
- Untangle's Multi-Functional Firewall Software
- Kernel Korner - Why and How to Use Netlink Socket
- RSS Feeds