Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
So I'm not sure if this is a real issue, my understanding is that when a system reboots the virtual memory is dumped in the process. Is there some configuration that would keep the memory intact after rebooting? I'm on RedHat 6 enterprise server, and I just need to make sure that virtual memory is cleared upon reboot. I'm not sure where to look to make sure this is happening.
On most systems, a linux reboot causes the BIOS to redo the memory check - which will wipe the memory if it is allowed to complete.
I don't have an EFI system to see, but I think it does the same there.
A cold reboot is aimed more at getting strange devices to fully reset than it is about clearing memory. For instance there were some old ethernet devices that would not reset unless they were powered down, and back up. Without that power cycle they had a tendency to have ROM checksum errors reported and not work.
What you're talking about would not be a reboot, but rather S3-Hibernate where RAM is suspended to disk in a low power state.
Whether or not the BIOS, a bootloader, or kernel initialization ends up clearing memory versus not, it's a horrifically bad idea to attempt to rely on memory content to be anything meaningful after a reboot. One of the main reasons a good OS boots reliably is that they're typically written to never assume that volatile resources are in any form of set state, excepting uninitialized at startup, whether that startup be cold or warm.