12GB RAM installed in Dell Poweredge4600 but Fedora9 only sees 4GB
Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
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.
There is less than 24 hours left to vote in the 2015 LinuxQuestions.org Members Choice Awards. Click here to go to the polls. Vote now and make sure your voice is heard!
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.
The Fedora9 OS we are using is 32bit. We did download the pae module and tried to follow the Red Hat documentation on performing the upgrade. Obviously we did something wrong because we still only see 4GB.
What we need is a step-by-step procedure on how to upgrade to pae with verifications on each step. Any URLs, links, suggestions would be appreciated.
Selecting the first option (Fedora (18.104.22.168-108.fc9.i686.PAE)) will boot it for you. Selecting "Fedora (22.214.171.124-108.fc9.i686)" will boot the standard kernel.
I don't see why you need to comment out any other kernels.
I'm pretty sure grub numbers things from zero, so the default boot will be the second entry (default=1) which is non PAE. I'd make sure everything works though before I changed it (to default=0).
When the grub menu comes up, hitting any key should bring the menu with various boot options up.
Edit - I don't recall the exact effect of "hiddenmenu". I think this just means the menu is hidden unless you hit a key when the first grub message comes up, but you may need to comment this line out - try it first.
Last edited by billymayday; 09-04-2008 at 04:32 PM.
Although I have not yet succeeded in doing so, I have read that we can use SELINUX to create security policies across a network of Linux client-server, similar to what is used in a Windows domain. This feature would understandably be of great importance to our clients who may need more than just the file permissions security.
Unfortunately the Fedora documentation on the subject is hard to follow. In our limited experience with them, the pre-installed SELINUX policies seem to hinder normal operations. For example, we couldn't get SELINUX to allow the normal operation of SpamAssassin with our Sendmail and Cyrus email server setup. I had to set SELINUX to permissive.
I suppose this would/should be a topic for a separate thread.
Is there a another/better way to accomplish security policies in Linux networks?