Mailinglist Archive: yast-commit (953 mails)

< Previous Next >
[yast-commit] r49666 - /trunk/storage/storage/src/include/ep-raid-dialogs.ycp
  • From: aschnell@xxxxxxxxxxxxxxxx
  • Date: Tue, 05 Aug 2008 08:11:15 -0000
  • Message-id: <20080805081115.BFA3F39BE7@xxxxxxxxxxxxxxxx>
Author: aschnell
Date: Tue Aug 5 10:11:15 2008
New Revision: 49666

URL: http://svn.opensuse.org/viewcvs/yast?rev=49666&view=rev
Log:
- copied help texts

Modified:
trunk/storage/storage/src/include/ep-raid-dialogs.ycp

Modified: trunk/storage/storage/src/include/ep-raid-dialogs.ycp
URL:
http://svn.opensuse.org/viewcvs/yast/trunk/storage/storage/src/include/ep-raid-dialogs.ycp?rev=49666&r1=49665&r2=49666&view=diff
==============================================================================
--- trunk/storage/storage/src/include/ep-raid-dialogs.ycp (original)
+++ trunk/storage/storage/src/include/ep-raid-dialogs.ycp Tue Aug 5 10:11:15
2008
@@ -42,6 +42,43 @@
}


+ string MiniWorkflowStepRaidTypeDevicesHelp()
+ {
+ // TODO
+
+ // help text
+ string help = _("<p><b>RAID 0:</b> This level increases your disk
performance.
+There is <b>NO</b> redundancy in this mode. If one of the drives crashes, data
recovery will not be possible.</p>
+");
+
+ // help text
+ help = help + _("<p><b>RAID 1:</b> <br>This mode has the best
redundancy. It can be
+used with two or more disks. This mode maintains an exact copy of all data on
all
+disks. As long as at least one disk is still working, no data is lost. The
partitions
+used for this type of RAID should have approximately the same size.</p>
+");
+
+ // help text
+ help = help + _("<p><b>RAID 5:</b> <br>This mode combines management of
a larger number
+of disks and still maintains some redundancy. This mode can be used on three
disks or more.
+If one disk fails, all data is still intact. If two disks fail simultaneously,
all data is lost</p>
+");
+
+ // help text
+ help = help + _("<p><b>Add partitions to your RAID.</b> According to
+the RAID type, the usable disk size is the sum of these partitions (RAID0),
the size
+of the smallest partition (RAID 1), or (N-1)*smallest partition (RAID 5).</p>
+");
+
+ // help text
+ help = help + _("<p>Generally, the partitions should be on different
drives,
+to get the redundancy and performance you want.</p>
+");
+
+ return help;
+ }
+
+
symbol MiniWorkflowStepRaidTypeDevices(map<string, any> &data)
{
y2milestone("MiniWorkflowStepRaidTypeDevices data:%1", data);
@@ -89,7 +126,7 @@
_("Available
Devices:"),
_("Selected
Devices:")));

- MiniWorkflow::SetContents(Greasemonkey::Transform(contents), "TODO
help");
+ MiniWorkflow::SetContents(Greasemonkey::Transform(contents),
MiniWorkflowStepRaidTypeDevicesHelp());
MiniWorkflow::SetLastStep(false);

symbol widget = nil;
@@ -136,6 +173,25 @@
}


+ string MiniWorkflowStepRaidOptionsHelp()
+ {
+ // TODO
+
+ // help text
+ string help = _("<p><b>chunk size:</b><br>It is the smallest \"atomic\"
mass
+of data that can be written to the devices. A reasonable chunk size for RAID 5
is 128KB. For RAID 0,
+32 KB is a good starting point. For RAID 1, the chunk size does not affect the
array very much.</p>
+");
+
+ // help text
+ help = help + _("<p><b>parity algorithm:</b><br>The parity algorithm to
use with RAID5.
+Left-symmetric is the one that offers maximum performance on typical disks
with rotating platters.</p>
+");
+
+ return help;
+ }
+
+
symbol MiniWorkflowStepRaidOptions(map<string, any> &data)
{
y2milestone("MiniWorkflowStepRaidOptions data:%1", data);
@@ -165,7 +221,7 @@

term contents = `HVSquash(`Frame(_("RAID Options"), options));

- MiniWorkflow::SetContents(Greasemonkey::Transform(contents), "TODO
help");
+ MiniWorkflow::SetContents(Greasemonkey::Transform(contents),
MiniWorkflowStepRaidOptionsHelp());
MiniWorkflow::SetLastStep(false);

symbol widget = nil;

--
To unsubscribe, e-mail: yast-commit+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: yast-commit+help@xxxxxxxxxxxx

< Previous Next >
This Thread
  • No further messages