Proc/kcore file size

So by reading the right ranges of kernel virtual memory, one can get a complete copy of the content of the physical memory of that system.

The physical RAM of a system is not necessarily at the beginning of the physical address space, nor is it always in one continuous block. On a system with a kernel version greater or equal 4. Before kernel version 4. Look here for details. Instead the offset is somewhat randomised You can find a more detailed explanation and visualisation here. And when it can not find one there is none there, because the base address was randomized , it fails silently.

So, with a kernel greater or equal 4. I know it doesn't take up disk space, but why is the snapshot size incorrect when using Google cloud's disk snapshot feature?

Add a comment. Active Oldest Votes. Improve this answer. Yes, it doesn't take up disk space, but I used the kill command to clean up the process of taking up files that have been deleted, but it still doesn't work, and the disk snapshot is still large — Shark Deemo. Killing any processes will not affect your disc usage. The Overflow Blog. Podcast Helping communities build their own LTE networks. Yet when the file is viewed, it can contain quite a bit of information. In addition, most of their time and date settings reflect the current time and date, meaning that they are constantly changing.

This is an interface provided to the user, to interact with the kernel and get the required information about processes running on the system. Its zero-length files are neither binary nor text, yet you can examine and display them. Ubuntu Community Ask! Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Learn more. Ask Question. Asked 6 years, 10 months ago.

Active 6 years, 10 months ago. Viewed 5k times.