updating docs for 1.0.1 and with new screenshots for kde 4.4

svn path=/trunk/extragear/sysadmin/doc/partitionmanager/; revision=1071430

doc/appendix.docbook

@@ -44,13 +44,13 @@
 
 			<listitem>
 				<para>
-					&dumpe2fs;: Reads usage information for ext2 and ext3 file systems. Part of the e2fsprogs utility suite that can be downloaded from <ulink url="http://e2fsprogs.sourceforge.net/"/>.
+					&dumpe2fs;: Reads usage information for ext2/ext3/ext4 file systems. Part of the e2fsprogs utility suite that can be downloaded from <ulink url="http://e2fsprogs.sourceforge.net/"/>.
 				</para>
 			</listitem>
 
 			<listitem>
 				<para>
-					&e2label;: Reads and writes file system labels for ext2 and ext3 file systems. Part of the e2fsprogs utility suite that can be downloaded from <ulink url="http://e2fsprogs.sourceforge.net/"/>.
+					&e2label;: Reads and writes file system labels for ext2/ext3/ext4 file systems. Part of the e2fsprogs utility suite that can be downloaded from <ulink url="http://e2fsprogs.sourceforge.net/"/>.
 				</para>
 			</listitem>
 

doc/credits.docbook

@@ -4,11 +4,11 @@
 		&partman;
 	</para>
 	<para>
-		Program copyright 2008 Volker Lanz
+		Program copyright 2008, 2009, 2010 Volker Lanz
 		<email>vl@fidra.de</email>
 	</para>
 	<para>
-		Documentation Copyright &copy; 2008 Volker Lanz.
+		Documentation Copyright &copy; 2008, 2009, 2010 Volker Lanz.
 		<email>vl@fidra.de</email>
 	</para>
 

doc/faq.docbook

@@ -135,6 +135,16 @@
 				</para>
 			</answer>
 		</qandaentry>
+		<qandaentry>
+			<question>
+				<para>During startup, &partman; prints some message about probing devices and that it might even crash or at least take a long time.</para>
+			</question>
+			<answer>
+				<para>
+					LibParted, a backend library &partman; uses, has problems with systems where the Linux Device Mapper is used in a way it doesn't understand. Unfortunately it reacts to some of these situations with segmentation faults, i.e. crashes. &partman; therefore tries to avoid these situations by using alternative backends. If it cannot do that, however, and has to rely on LibParted, it will print a message like the one mentioned and nevertheless try its best.
+				</para>
+			</answer>
+		</qandaentry>
 <!--
 		<qandaentry>
 			<question>

doc/index.docbook

@@ -47,14 +47,14 @@
 		</authorgroup>
 
 		<copyright>
-			<year>2008</year>
+			<year>2008, 2009, 2010</year>
 			<holder>Volker Lanz</holder>
 		</copyright>
 
 		<legalnotice>&FDLNotice;</legalnotice>
 
-		<date>2009-06-19</date>
-		<releaseinfo>0.80.11</releaseinfo>
+		<date>2010-01-08</date>
+		<releaseinfo>1.00.00</releaseinfo>
 
 		<abstract>
 			<para>Manage your disks, partitions and file systems.</para>

doc/installoshowto.docbook

@@ -83,11 +83,11 @@
 	</para>
 
 	<para>
-		This already looks mostly okay but you already know that you will not need that much free space after the home partition because you will later create a swap partition there. And a swap partition of more than 3 GiB is a little large.
+		This already looks mostly okay but you already know that you will not need that much free space after the home partition because you will later create a swap partition there.
 	</para>
 
 	<para>
-		So grab the right resize handle in the dialog's resizer widget and move it to the right until the free space after the pasted partition is only about 1.5 GiB in size:
+		So grab the right resize handle in the dialog's resizer widget and move it to the right until the free space after the pasted partition has a size more suitable for a swap partition: 
 	</para>
 
 	<para>

doc/resizehowto.docbook

@@ -24,7 +24,7 @@
 	</note>
 
 	<para>
-		The first step is to make more room for the partition to grow, so start by shrinking <quote>sdb1</quote> from its current size of 7.21 GiB to a more fittingly 5.00 GiB. Click on the partition and choose <xref linkend="menu-partition-resize"/>. The following dialog comes up:
+		The first step is to make more room for the partition to grow, so start by shrinking <quote>sdb1</quote>. Click on the partition and choose <xref linkend="menu-partition-resize"/>. The following dialog comes up:
 	</para>
 
 	<para>

doc/usermanual.docbook

@@ -35,7 +35,7 @@
 
 				<listitem>
 					<para>
-						Graphical Device View: In this view &partman; shows a graphical representation of the currently selected device. Each of the device's <glossterm linkend="glossary-partition">partitions</glossterm> has its own box with device node name (<quote>sda1</quote> for the first partition in the screenshot above) and usage information (the dark violet area and <quote>7.61 GiB</quote> in the screenshot).
+						Graphical Device View: In this view &partman; shows a graphical representation of the currently selected device. Each of the device's <glossterm linkend="glossary-partition">partitions</glossterm> has its own box with device node name (<quote>sda1</quote> for the first partition in the screenshot above) and usage information (the dark violet area in the screenshot).
 					</para>
 					<para>
 						<glossterm linkend="glossary-extendedpartition">Extended partitions</glossterm> are visually distinct by their extra border (light green in the screenshot above) around them.
@@ -60,7 +60,7 @@
 						Pending Operations Panel: This panel lists all operations that will be executed once you choose <xref linkend="menu-edit-apply"/>.
 					</para>
 					<para>
-						In the screenshot above, one operation is pending: If the user applies the operations now, the ext2 <glossterm linkend="glossary-filesystem">file system</glossterm> on /dev/sdb7 (which is 1.99 GiB in size) will be checked for errors and, if required, repaired.
+						In the screenshot above, one operation is pending: If the user applies the operations now, the ext2 <glossterm linkend="glossary-filesystem">file system</glossterm> on /dev/sdb3 will be checked for errors and, if required, repaired.
 					</para>
 				</listitem>