Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Heya all. I'm running RedHat 7.2 on an Athlon system that has been locking up at random intervals, sometimes 5 days, sometimes 5 minutes. I've gone through RedHat's update agent to try get the most recent kernel and packages to see if that will fix the problem. No luck, and I think (well pretty sure) that this is part of the problem. Grub is not reading the grub.conf file on boot up at all. There are 2 entries in the actual file for the new and old kernel, but it only displays the old in the boot list. I've even gone as far as renaming both of the entries in the grub.conf file. It still displays the old entry. I'm basically just trying to get it to boot the newer kernel to see if my lock up problem goes away.
It's the start plinking down things and see if it fixes things, and I know there have been issues with Athlons and Linux in the past. Once this is solved, I may be back with more issues dealing with the lockups if they don't go away, but first things first.
Ok, not too sound any more stupid than I probably already do, what's the command for that? I read the man page and tried grub --config-file=/boot/grub/grub.conf and it simply gives the grub shell prompt. Is that all I needed to do?
You don't have to run grub after you edit the grub.conf or menu.lst file. Grub reads the grub.conf or menu.lst file when it boots up. Are you editing the grub.conf file in the /boot/grub directory? Could you post a copy of your grub.conf file.