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.
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.
I've got a server only running the single cpu kernel. I am going to be upgrading it today to the multi-processor kernel (going from 2.6.9-5.EL to kernel-smp-2.6.9-78.0.8.EL.) My question is, the user is planning on maxing out the RAM in this box in the near future (32gigs) which means I will need the hugemem kernel, correct? The only thing I see on RHN is the hugemem-devel package. I had thought there was a kernel-hugememsmp available. How do I install hugemem using just the devel rpm?
anomie - the Redhat link doesn't give any idea about what the "hugemem" kernel is ... or why it might be a bad idea.
I was originally going to object that we didn't even know if the op had Redhat ... until I noticed the cryptic reference to "RHN" (Red Hat Network, rhn.redhat.com).
But again - if you *can* go to a 64-bit CPU, then you *should* go to 64-bit.
Otherwise, if you're required to stick with 32-bits (for any number of perfectly good reasons), you should consider "hugemem" *only* as a last resort. It adds an extra level of indirection to your memory addressing, and an extra level of complexity to the OS.