[gnome-system-monitor/wip/mallard-help: 60/68] Begin simplifying memory-maps, process-columns

[Ekaterina Gerasimova <egerasimov src gnome org>]

commit 74db394e69d18a9c6041995dc5894d33115d7ba3
Author: Michael Hill <mdhill gnome org>
Date:   Wed Jan 29 11:01:50 2014 +0000

    Begin simplifying memory-maps, process-columns

 help/C/memory-map-use.page  |   75 -----------------------
 help/C/process-columns.page |  137 +------------------------------------------
 2 files changed, 2 insertions(+), 210 deletions(-)
---
diff --git a/help/C/memory-map-use.page b/help/C/memory-map-use.page
index 80defe9..505e2bf 100644
--- a/help/C/memory-map-use.page
+++ b/help/C/memory-map-use.page
@@ -62,80 +62,5 @@
       be paged out at swap time.</p>
     </item>
   </list>
-
-<table shade="rows">
-  <tr>
-        <td><p>Properties</p></td>
-  </tr>
-  <tr>
-         <td><p>Filename</p></td>
-         <td><p>The location of a shared library that is currently used by the
-    process. If this field is blank, the memory information in this row
-    describes memory that is owned by the process whose name is displayed above
-    the memory-map table.</p></td>
-  </tr>
-  <tr>
-         <td><p>VM Start</p></td>
-         <td><p>The address at which the memory segment begins. VM Start, VM End and
-    VM Offset together specify the location on disk to which the shared library
-    is mapped.</p></td>
-  </tr>
-  <tr>
-         <td><p>VM End</p></td>
-         <td><p>The address at which the memory segment ends.</p></td>
-  </tr>
-  <tr>
-         <td><p>VM Offset</p></td>
-         <td><p>The location of the address within the memory segment, measured from
-    VM Start.</p></td>
-  </tr>
-  <tr>
-         <td><p>VM Size</p></td>
-         <td><p>The size of the memory segment.</p></td>
-  </tr>
-  <tr>
-         <td><p>Flags</p></td>
-         <td><p>The following flags describe the different types of memory-segment
-    access that the process can have:</p>
-    <terms>
-      <item>
-        <title><gui>p</gui></title>
-        <p>The memory segment is private to the process, and is not accessible
-        to other processes.</p>
-      </item>
-      <item>
-        <title><gui>r</gui></title>
-        <p>The process has permission to read from the memory segment.</p>
-      </item>
-      <item>
-        <title><gui>s</gui></title>
-        <p>The memory segment is shared with other processes.</p>
-      </item>
-      <item>
-        <title><gui>w</gui></title>
-        <p>The process has permission to write into the memory segment.</p>
-      </item>
-      <item>
-        <title><gui>x</gui></title>
-        <p>The process has permission to execute instructions that are
-        contained within the memory segment.</p>
-      </item>
-    </terms>
-    </td>
-  </tr>
-  <tr>
-         <td><p>Device</p></td>
-         <td><p>The major and minor numbers of the device on which the shared
-    library filename is located. Together these specify a partition on the
-    system.</p></td>
-  </tr>
-  <tr>
-         <td><p>Inode</p></td>
-         <td><p>The inode on the device from which the shared library location is
-    loaded into memory. An inode is the structure the filesystem uses to store
-    a file, and the number assigned to it is unique.</p></td>
-  </tr>
-</table>
-
 </section>
 </page>
diff --git a/help/C/process-columns.page b/help/C/process-columns.page
index 30b025b..43b5e3f 100644
--- a/help/C/process-columns.page
+++ b/help/C/process-columns.page
@@ -41,140 +41,7 @@
   </steps>
 
   <p>For each process listed in the <gui>Processes</gui> tab,
-  <app>System Monitor</app> provides information in a number of categories. </p>
-
-<table shade="rows">
-  <tr>
-       <td><p>Process Name</p></td>
-       <td><p>The name of the task. This column may also contain an icon to
-        indicate the application that is associated with the process.</p></td>
-
-  </tr>
-
-  <tr>
-       <td><p>User</p></td>
-       <td><p>The user name of the task's owner.</p></td>
-  </tr>
-
-  <tr>
-       <td><p>Status</p></td>
-       <td><p>The status of the task. </p>
-       </td>
-  </tr>
-
-  <tr>
-       <td><p>Virtual Memory</p></td>
-       <td><p>The total amount of virtual memory used by the task.</p>
-       </td>
-   </tr>
-
-  <tr>
-       <td><p>Resident Memory</p></td>
-       <td><p>The non-swapped physical memory used by the task.</p></td>
-   </tr>
-
-  <!--
-  <tr>
-       <td><p>Writable Memory</p></td>
-       <td><p>The amount of memory that can be written by the process.</p></td>
-   </tr>
-  -->
-
-  <tr>
-       <td><p>Shared Memory</p></td>
-       <td><p>The amount of shared memory used by the task (potentially shared
-        with other processes).</p></td>
-   </tr>
-
-  <!--
-  <tr>
-       <td><p>X Server Memory</p></td>
-       <td><p>The amount of X server memory that is used by the process.</p></td>
-   </tr>
-  -->
-
-  <tr>
-       <td><p>% CPU</p></td>
-       <td><p>The task's share of the elapsed CPU time since the last screen
-        update, expressed as a percentage of total CPU time. In a true SMP
-        environment, if 'Irix mode' is Off, top will operate in 'Solaris mode'
-        where a task's cpu usage will be divided by the total number of CPUs.
-        You toggle 'Irix/Solaris' modes with the 'I' interactive command.</p></td>
-   </tr>
-
-  <tr>
-       <td><p>CPU Time</p></td>
-       <td><p>Total CPU time the task has used since it started.</p></td>
-   </tr>
-
-  <tr>
-       <td><p>Started</p></td>
-       <td><p>When the process began running.</p></td>
-   </tr>
-
-  <tr>
-       <td><p>Nice</p></td>
-       <td><p>The nice value of the task.</p></td>
-   </tr>
-
-  <tr>
-       <td><p>ID</p></td>
-       <td><p>The task's unique process ID.</p></td>
-   </tr>
-
-  <tr>
-       <td><p>Security Context</p></td>
-       <td><p>The security context in which the process is running.</p></td>
-   </tr>
-
-  <tr>
-       <td><p>Command Line</p></td>
-       <td><p>Command line or program name used to start a task.</p></td>
-   </tr>
-
-  <tr>
-       <td><p>Memory</p></td>
-       <td><p>A task's currently-used share of available physical memory.</p></td>
-   </tr>
-
-  <tr>
-       <td><p>Waiting Channel</p></td>
-       <td><p>Location in the kernel where the process waits for data or
-        processing time.</p></td>
-   </tr>
-
-  <tr>
-       <td><p>Control Group</p></td>
-       <td><p>The <app>named</app> hierarchical group to which the process is assigned.</p></td>
-   </tr>
-
-  <tr>
-       <td><p>Unit</p></td>
-       <td><p>The <app>systemd</app> unit to which a process belongs.</p></td>
-   </tr>
-
-  <tr>
-       <td><p>Session</p></td>
-       <td><p>The session ID.</p></td>
-   </tr>
-
-  <tr>
-       <td><p>Seat</p></td>
-       <td><p>The login session identifier of a process.</p></td>
-   </tr>
-
-  <tr>
-       <td><p>Owner (OUID)</p></td>
-       <td><p>The Unix user ID of the owner of the session of a
-        process.</p></td>
-   </tr>
-
-  <tr>
-       <td><p>Priority</p></td>
-       <td><p>The nice value expressed as <gui>Very Low</gui>, <gui>Low</gui>,
-       <gui>Normal</gui>, <gui>High</gui>, or <gui>Very High</gui>.</p></td>
-   </tr>
-
-</table>
+  <app>System Monitor</app> provides information in a number of categories.
+  For detailed descriptions of what the columns mean, check the ps man page.</p>
 
 </page>