[gnome-user-docs/wip/system-admin-guide] disk pages edited

[Jana Svarova <jsvarova src gnome org>]

commit a92f527cf6b7d9b3c575011474b6e71b58c05863
Author: Jana Svarova <jsvarova redhat com>
Date:   Thu Sep 5 15:10:02 2013 +0200

    disk pages edited

 system-admin-guide/C/disk-busy.page                |   16 ++++---------
 .../C/disk-connection-unavailable.page             |    9 +++++--
 .../{disk-failing.page => disk-failing.page.stub}  |   23 ++++++++-----------
 system-admin-guide/C/disk-partitions.page          |   23 ++++++++++---------
 system-admin-guide/C/disk-usb.page                 |   21 +++++++++++++----
 system-admin-guide/C/disk-vfs-mounts.page          |   23 +++++++++++++-------
 6 files changed, 64 insertions(+), 51 deletions(-)
---
diff --git a/system-admin-guide/C/disk-busy.page b/system-admin-guide/C/disk-busy.page
index 7fec7a4..121a33a 100644
--- a/system-admin-guide/C/disk-busy.page
+++ b/system-admin-guide/C/disk-busy.page
@@ -11,36 +11,30 @@
       <years>2013</years>
     </credit>
 
-    <desc>What if my disk is busy?</desc>
+    <desc>What if my disk is busy on unmount/eject?</desc>
   </info>
 
   <title>What shall I do if my disk is busy?</title>
 
   <p>If you receive a notification about your disk being busy, find the
   program/programs that keep the disk busy. Then, you may regularly end the
-  programs you are running and wait for the disk to recover. Or, you
+  programs you are running. Or, you
   can open the <gui>System Monitor</gui> and kill the program/programs.
   Where and how can you do it?</p>
 
-  <!--Is it true? Does the sysadmin receive a notification?
-Or does he find out from, e.g.: the desktop running slowly?-->
-
   <p>There are three different ways, two static and one interactive, of viewing
   system processes in the terminal:</p>
   <list>
-  <item><p>Run the <cmd>ps ax</cmd> command that shows the list of currently
+  <item><p>Run lsof to get the list of open files alongside with processes.
+  If lsof nen9 k dispoyici.. Run the <cmd>ps ax</cmd> command that shows the list of currently
   running processes.</p></item>
   <item><p>To display the owner of each process, use the
   <cmd>ps aux</cmd> command.</p></item>
-  <item><p>The <cmd>top</cmd> command displays currently running processes and
-  important information about them including their memory and CPU usage.
-  This list is the only one that is both real-time and interactive.</p></item>
   </list>
 
   <p>Alternatively, you can go to
   <guiseq><gui>Activities</gui><gui>System Monitor</gui></guiseq> which opens
   a graphical interface and shows the running processes in the very first tab.</p>
 
-<!--Are there any other solutions?
-Can the sysadmin find some stats to find out how busy the given disk is?-->
+<p>Až najdeš, kill!!</p>
 </page>
diff --git a/system-admin-guide/C/disk-connection-unavailable.page 
b/system-admin-guide/C/disk-connection-unavailable.page
index da4678c..4051fa8 100644
--- a/system-admin-guide/C/disk-connection-unavailable.page
+++ b/system-admin-guide/C/disk-connection-unavailable.page
@@ -15,7 +15,7 @@
     suspend/resume connection or connectivity loss.</desc>
   </info>
 
-  <title>I have lost connection</title>
+  <title>What if the connection to remote file system is disabled?</title>
 
   <p>There is a number of situations in which the client is unexpectedly and
   unwillingly disconnected from a "virtual file system" (or a "remote disk"),
@@ -24,11 +24,14 @@
 <list>
   <item><p>the connection is interrupted (for example your notebook is
   disconnected from the wi-fi)</p></item>
-  <item><p>the user is inactive for some time</p></item>
-  <item><p>sleeping mode is activated</p></item>
+  <item><p>the user is inactive for some time and is disconnected by the server.</p></item>
+  <item><p>computer is resumed from sleeping mode.</p></item>
 </list>
 
   <p>The only solution to such cases is to unmount and mount again the file
   system, which reconnects the desktop to the source.</p>
+<note>
+  <p>Pokud padá spojení často, zkontrolujte nastavení v NetworkManageru.</p>
+</note>
 
 </page>
diff --git a/system-admin-guide/C/disk-failing.page b/system-admin-guide/C/disk-failing.page.stub
similarity index 71%
rename from system-admin-guide/C/disk-failing.page
rename to system-admin-guide/C/disk-failing.page.stub
index 209947e..f1b3c67 100644
--- a/system-admin-guide/C/disk-failing.page
+++ b/system-admin-guide/C/disk-failing.page.stub
@@ -23,25 +23,22 @@ http://consultancy.edvoncken.net/index.php/HOWTO_Replace_a_failing_disk_on_Linux
   <p>If your disk is about to fail, you will receive a pre-failure warning from
   SMART (Self Monitoring And Reporting Technology), more concretely from the 
   <sys>smartd</sys> deamon.</p>
-<!--Je to pravda?? Notification bubble/message?? -->
   <p>To detect the extent of your problem, execute the disk self-test:</p>
-
+  <!-- failure error 
+  check jestli 
+  analyzuje atributy
+  -->
 <steps>
-  <title>Running a selftest</title>
-  <item><p>Open the <gui>Disks</gui> window by typing <gui>Disks</gui> into
+  <title>Running a self-test</title>
+  <item><p>Open the <gui>Disks</gui> window by typing <gui>Disks</gui> into the
   <gui>Activities</gui> overview.</p></item>
-  <item><p>In the top-right corner, click on the More actions button.</p></item>
-  <item><p>From the drop-down menu, choose SMART Data and Self Tests</p></item>
+  <item><p>In the top-right corner, click on the sign of the cogwheel.</p></item>
+  <item><p>From the drop-down menu, choose <gui>SMART Data &amp; Self Tests</gui>.</p></item>
   <item><p>From the <gui>Start Self-test</gui> drop-down menu in the bottom-left
-  corner, choose <gui>Short</gui> (and type your password if necessary)</p></item>
-  <item><p>Let the Self-test run to show you more about your desk failure.</p></item>
+  corner, choose <gui>Short</gui> (and type your password if necessary).</p></item>
+  <item><p>Let the <gui>Self-test</gui> run to show you more about the disk failure.</p></item>
 </steps>
 
-  <p>Alternatively, you can run the test in the terminal by running the
-  command below. This time, the example shows the long self-test:
-  <cmd>smartctl -t long /dev/sdb</cmd></p>
-<!--Fix the cmd, WRONG -->
-
 <!--Jaký rozdíl je mezi short a long testem?
 Co z nich sysadmin vyčte? 
 jak má na konkrétní informace reagovat?-->
diff --git a/system-admin-guide/C/disk-partitions.page b/system-admin-guide/C/disk-partitions.page
index 6479139..f7e0dc7 100644
--- a/system-admin-guide/C/disk-partitions.page
+++ b/system-admin-guide/C/disk-partitions.page
@@ -11,31 +11,32 @@
       <years>2013</years>
     </credit>
 
-    <desc>What if Nautilus shows system, unknown, or unwanted partitions?</desc>
+    <desc>What if Nautilus shows system unknown or unwanted partitions?</desc>
   </info>
 
-  <title>Problematic partitions</title>
+  <title>What if Nautilus shows system unknown or unwanted partitions?</title>
 
   <p>The <file>/etc/fstab</file> file typically lists all available disks and 
-  disk partitions, and indicates how they are to be initialized or otherwise
-  integrated into the overall system's file system.</p>
+  disk partitions, and indicates how they are mounted or otherwise integrated
+  into the overall file system.</p>
   <p>The <cmd>mount</cmd> command most commonly uses the <file>/etc/fstab</file>
   file. The file is read to determine which options should be used when mounting
   a specified device.</p>
 
-  <p>That's why you need to first check whether the device is listed in the
-  <file>/etc/fstab</file> file as the devices are not listed by default.</p>
-  <!--why? What can the sysadmin fix there? -->
+  <p>That is why you need to first check whether the device is listed in the
+  <file>/etc/fstab</file> file as the devices are not shown in the user
+  interface by default.</p>
 
-  <p>As your second option, you can open Disks and tick the "show in user
-  interface" box in the "edit mount options" menu.</p>  <!-- And then what happens? He's gonna see it in the 
interface where?? -->
+  <p>One of the solutions is to select the
+  <gui>Show in user interface</gui> checkbox in the <gui>Edit mount options</gui>
+  menu:</p>
 <steps>
   <item><p>Open <app>Disks</app> in the <gui>Activities</gui> overview.</p></item>
   <item><p>In <app>Volumes</app>, click on the <app>Edit mount options</app>.</p></item>
-  <item><p>Check the box "show in user interface" and confirm your choice by OK.</p></item>
+  <item><p>Select the checkbox <gui>Show in user interface</gui> and confirm your choice by 
<gui>OK</gui>.</p></item>
 </steps>
 
-<note style="important">
+<note>
   <p>It is the duty of the system administrator to properly create and maintain this file.</p>
 </note>
 </page>
diff --git a/system-admin-guide/C/disk-usb.page b/system-admin-guide/C/disk-usb.page
index 82f2737..5e0bdf9 100644
--- a/system-admin-guide/C/disk-usb.page
+++ b/system-admin-guide/C/disk-usb.page
@@ -19,18 +19,29 @@
   <title>Connected USB disk is invisible</title>
 
   <p>It may happen to you that you connect a flash drive, but GNOME
-  Desktop does not show it up, it is invisible. What exactly does it mean that
-  your flash drive is invisible?</p>
+  Desktop does not show it up, it is invisible, which means that:</p>
 <list>
   <item><p>You cannot see the device in the <app>GNOME disks</app> list
-  (To check this, open the GNOME discs in the <gui>Activities</gui> overview)</p></item>
+  (to check this, open the GNOME disks in the <gui>Activities</gui> overview).</p></item>
   <item><p>In the terminal, you run the <code>udisksctl dump</code> command
   which lists the current state of the <sys>udisksctl</sys> daemon and shows
   information about all objects but your flash disk is not among them.</p></item>
-  <item><p>In your terminal, you run the <cmd>dmesg</cmd> command. Towards the
+  <item><p>In the terminal, you run the <cmd>dmesg</cmd> command. Towards the
   end of the log there is a list of detected partitions but your flash drive is
   not among them.</p></item>
 </list>
 
-<!--What shall the sysadmin do? -->
+  <p>If your USB disk is visible in all the three aforementioned points,
+  you can set the <gui>Show in user interface</gui> flag:</p>
+  <steps>
+  <item><p>Open <app>Disks</app> in the <gui>Activities</gui> overview.</p></item>
+  <item><p>In <app>Volumes</app>, click on the <app>Edit mount options</app>.</p></item>
+  <item><p>Select the checkbox <gui>Show in user interface</gui> and confirm
+  your choice by <gui>OK</gui>.</p></item>
+</steps>
+
+  <p>If the disk is not visible in all of the three points, the solutions are to
+  either replace the USB disk and try connecting it again or consult the
+  distribution manual.</p>
+<!-- (Storage Guide v RH)-->
 </page>
diff --git a/system-admin-guide/C/disk-vfs-mounts.page b/system-admin-guide/C/disk-vfs-mounts.page
index 8d5f2d0..9212da3 100644
--- a/system-admin-guide/C/disk-vfs-mounts.page
+++ b/system-admin-guide/C/disk-vfs-mounts.page
@@ -11,27 +11,34 @@
       <years>2013</years>
     </credit>
 
-    <desc>What if an application fails to see VFS mounts?</desc>
+    <desc>What if an application fails to see active VFS mounts?</desc>
   </info>
   
-  <title>VFS mounts are invisible</title>
+  <title>Active VFS mounts are invisible</title>
 
 
-  <p>If your VFS mounts are invisible, it means... <!--There are not to be found where??-->
-  Firstly, check whether your application is a native GIO client as all the GNOME
-  applications typically use <app>GIOModule</app> for module loading.</p>
+  <p>If your active VFS mounts are invisible, it means your application is not a native GIO client. 
+  Native GIO clients are typically all GNOME applications using GNOME libraries.
+  There is a fallback service, <sys>gvfs-fuse</sys> provided for non-GIO clients.
+  </p>
   <!-- Why? What can the sysadmin find/see there??-->
 
-  <p>If you have done so, check whether the <sys>gvfs-fuse</sys> process is running.
+  <p>Solution: check whether the <sys>gvfs-fuse</sys> process is running.
   Since <sys>gvfs-fuse</sys> should run automatically and you cannot start it by
   yourself, try logging out and logging in again.</p>
 
+ <!--
+ spustit daemon Manuálně:  
+ 
+ The mounts are stored in the <file>/run/user/useride/gvfs/ </file> directory.
+  daemon spustíme z terminálu příkazem: <cmd>/usr/libexec/gvfsd-fuse -f /run/user/1000/gvfs</cmd> 
+ pak je okamžitě přístupný, pokud ne, uvidí hlášku.. -->
+ 
 <note style="important">
   <p>The gvfs package does not have to be installed on your system automatically,
   so you might want to install it by running the <cmd>yum install gvfs</cmd>
   command.</p>
 </note>
 
- <!--The mounts are stored in the <file>/run/user/useride/gvfs/ </file>directory.
- Is this relevant information?? Should it be documented?-->
+
 </page>